loading table of contents...

9.1. Port Reference

For each application or component there is a two digit port prefix defined and for each protocol or service there is a three digit port suffix defined.

The next figure shows the deployment of the CoreMedia DXP 8 components into the boxes and the communication between the components. If you cannot read the text of the figure in the online documentation, right-click the image and select Open image in new tab from the context menu. You can also download the original YEd file from the documentation overview page below Other Documentation named CoreMedia DXP 8 Deployment Diagram.

Deployment and communication overview

Figure 9.1. Deployment and communication overview


ComponentPort Prefix
Studio40
Content Management Server41
Master Live Server42
Workflow Server43
Solr Master44
Solr Slave45
CAE Feeder Preview46
CAE Feeder Live47
Replication Live Server48
Delivery (Live CAE)49

Table 9.1. Component Port Prefix


Protocol / ServicePort Suffix
HTTP080
HTTPS443
Tomcat Shutdown005
Tomcat AJP009
Tomcat JMX Registry Port (RMI)099
Tomcat JMX Server Port (RMI)098
Tomcat Debug Port777
CORBA683
CORBA SSL684

Table 9.2. Protocol / Service Port Suffix


[Note]Note

Since the preview is always deployed together with Studio, there is no extra port prefix reserved. When started with tomcat7:run from within the workspace, the preview Tomcat process has its own HTTP port. If you want to access the preview, you have to use the port 40081.

ServicePort
MySQL3306
Mongo DB27017

Table 9.3. Third-Party Services


[Note]Note

Be advised, that this port schema's port range has its drawback of overlapping with the default ephemeral port range on most operation systems. You can however, decrease the ephemeral port range with the cost of not optimizing your TCP/IP stack. In a setup with just one CAE running per host, decreasing the range will likely not affect your systems performance, but if you are running many CAEs on one host, you should rather adapt the port filtering to use a smaller range of ports below the default ephemeral port range.

Changing the filtering can be done in root pom.xml using the port schema properties or in the packages/pom.xml using the explicit properties. There should be no hard coded ports beside the Chef test specs, which are only active in the Vagrant virtualized development mode. If there are hard coded ports in property files it is most likely, that there is also a configurable override in the Tomcat plugin configuration of the pom.xml or in the override properties in the packages hierarchy.

To decrease the ephemeral port range for CentOS, you just need to execute the following commands as root on your system:

echo "50000 65535" > /proc/sys/net/ipv4/ip_local_port_range
echo -e "\n# Increase system IP port limits\nnet.ipv4.ip_local_port_range = 50000 65535" >> /etc/sysctl.conf

Prev Up Next
 Home