The following tables list the Rendition Engine and Content Platform Engine ports information for LIQUENT.
Port name | Transport level protocol | Default port number | From | To |
---|---|---|---|---|
LIQUENT input port | TCP/IP | 2867 (COM Repository only) | Content Platform Engine and Rendition Engine | Rendition Engine |
LIQUENT notify port | TCP/IP | 2868 | Rendition Engine | Content Platform Engine and Rendition Engine |
LIQUENT event port | TCP/IP | 2869 | Content Platform Engine and Rendition Engine | Rendition Engine |
LIQUENT admin port | TCP/IP | 2870 | Content Platform Engine and Rendition Engine | Rendition Engine |
LIQUENT file transfer port | TCP/IP | 2871 | Content Platform Engine and Rendition Engine | Content Platform Engine and Rendition Engine |
LIQUENT job queue port | TCP/IP | 2872 | Rendition Engine | Rendition Engine |
Port name | Reply or Response to requestor? | Long lived sessions? | Load Balancer? | Supports SSL? |
---|---|---|---|---|
LIQUENT input port | Yes | No | No | No |
LIQUENT notify port | Yes | No | No | No |
LIQUENT event port | Yes | No | No | No |
LIQUENT admin port | Yes | No | No | No |
LIQUENT file transfer port | Yes | No | No | No |
LIQUENT job queue port | Yes | No | No | No |
Port name | Notes® |
---|---|
LIQUENT input port | The port allows for distributed processing of jobs on the Rendition Engine servers when there are more than one Rendition Engine server. A Rendition Engine server or Rendition Engine client (Content Platform Engine Publishing server) on which a job is submitted makes the load balancing decision on where to run the job. If the job is sent to another Rendition Engine server for execution then it uses the other Rendition Engine server's input port to do so. |
LIQUENT notify port | The port is also related to the distributed processing of jobs on the Rendition Engine servers. When a job is sent to another Rendition Engine server, then the originating Rendition Engine server or Rendition Engine client (Content Platform Engine Publishing server) is notified on this port by the other Rendition Engine server when the other Rendition Engine server has finished processing the job. One case of this is when the Rendition Engine server is notifying the Rendition Engine client (Content Platform Engine Publishing server) that a conversion job has completed. |
LIQUENT event port | The port is used by each Rendition Engine server to send or receive events. These events are used by the Rendition Engine server to keep each other informed of current activities. The LIQUENT Domain Manager on the Rendition Engine server uses these events for the job status display. |
LIQUENT admin port | The port is used by each Rendition Engine server for internal administrative functions. The primary use is for each Rendition Engine server to publish its current activity statistics (for example, how busy the business services are) for use by other Rendition Engine servers to make load balancing decisions. |
LIQUENT file transfer port | This port is used for transferring source, temporary, and result files between Rendition Engine servers as well as between Rendition Engine servers and Rendition Engine clients (Content Platform Engine Publishing servers). |
LIQUENT job queue port | This port is for job queuing by the render business service on all Rendition Engine servers. |
The above port numbers are the default values set by the Rendition Engine installer for the COM Repository in the LIQUENT Vista domain, which represents the Rendition Engine server itself. When a Content Platform Engine Publishing server is configured to point to the Rendition Engine server, one must create a "Java Repository" in the LIQUENT Vista domain that represents the Content Platform Engine Publishing server as a Java™ client to the Rendition Engine server, and this repository will also have the same default port number values.
The database port number is not specified directly by the Rendition Engine server’s LIQUENT software, but it is specified for the Rendition Engine client in the Content Platform Engine Publishing server's Rendition Engine Connection object (for the JDBC connection from the Rendition Engine client module to the Rendition Engine database server).