Default Port Allocations

The ports through which Caplin Platform components communicate with each other, and with external entities, are defined in configuration files. Here we've listed the default port settings that are used in the following situations:

  • when the Caplin Platform is shipped as part of a Caplin Trader install kit.
  • when the Caplin Platform is shipped independently of Caplin Trader.

Contents:

Default Liberator ports

The following table shows the default port allocations used by Liberator, and the configuration items you can set to change these allocations. When Liberator is shipped as part of a Caplin Trader install kit, the default port allocations are explicitly defined in the configuration files (column A in the table). When Liberator is supplied for use with other client technologies, the port allocations are not defined in the shipped configuration files, so Liberator uses its default values (column B in the table), unless you explicitly change them by adding entries to the configuration files.

  (A) Liberator port, as configured in Caplin Trader installation kit (B) Default Liberator port Configuration item Notes
HTTP clients 50180 8080 http-port
(set in rttpd.conf)
HTTP: Port 50180/8080 is typically assigned only if Liberator is downstream from a hardware SSL wrapper, otherwise you should normally change the HTTP port to 80 (this allows traffic to pass through an unmodified firewall and be accessible to clients).
HTTPS clients 50181 4443 https-port
(set in rttpd.conf)
In live operation, connections from HTTPS clients are typically allocated to port 443 (this allows traffic to pass through an unmodified firewall and be accessible to clients), unless the Liberator is deployed behind port translation hardware.
Client socket connections 50182 15000 direct-port
(set in rttpd.conf)
This port is typically used in Caplin Platform deployments where the client is not browser-based. It is not normally used in Caplin Trader projects.
Client socket connections using SSL not used 15001 directssl-port
(set in rttpd.conf)

This port is typically used in Caplin Platform deployments where the client is not browser-based. It is not normally used in Caplin Trader projects.

To enable client socket connections using SSL, you must set the configuration item
directssl-enable.

Transformer & Integration Adapters 50100 0 datasrc-port
(set in rttpd.conf)
The Caplin Platform default of 0 means that no Integration Adapters can connect to Liberator. To allow such connections, set datasrc-port to a unique non-zero value.
Caplin Management Console (RMI Registry) 50120 1099 rmi-registry-port
(set in rttpd.conf)
 
Caplin Management Console (RMI Client) 50130 1100 rmi.client.port
(set in java.conf)
 

Default Transformer ports

The following table shows the default port allocations used by Transformer, and the configuration items you can set to change these allocations. When Transformer is shipped as part of a Caplin Trader install kit, the default port allocations are explicitly defined in the configuration files with the values shown in column A of the table. When Transformer is supplied for use with other client technologies, the port allocations defined in the shipped configuration files are different – see column B of the table.

  (A) Transformer port, as configured in the Caplin Trader installation kit (B) Default Transformer port Configuration item Notes
Integration Adapters 50101 25010 datasrc-port
(set in transformer.conf)
 
UDP command interface port1 50161 10010 udp-port
(set in transformer.conf)
This port is not normally used in Caplin Trader projects.
Caplin Management Console (RMI Registry) 50121 1099 rmi-registry-port
(set in transformer.conf)
 
Caplin Management Console (RMI Client) 50131 1100 rmi.client.port
(set in java.conf)