This document gives information about HTTP/HTTPS port numbers used by CentraSite components. In general there is no need to change these values, unless your site's requirements differ from the CentraSite default values.
The document contains the following sections:
The CentraSite Registry Repository uses several port numbers that have the following default values:
| Port name | Description | Default port number |
|---|---|---|
|
XML XTS port |
The application port. |
53301 |
| ADMIN port |
The administration port. The port used for access to the CentraSite Registry Repository server for all administration actions. |
53303 |
| HTTP port | The HTTP Server port. The TCP/IP port used for HTTP access to the CentraSite Registry Repository. | 53313 |
If you wish to change these port numbers, the following locations must be updated:
The registry of the machine on which the CentraSite Registry Repository is installed.
The CAST web applications (only if the HTTP port is updated).
Important:
To avoid inconsistencies, it is important to modify the port
numbers in all locations in a single step.
To change a port number on the CentraSite Registry Repository
host
Run the command line script centrasite_setenv. This script is located in <CentraSiteInstallDir>/bin.
This ensures that environment variables and lookup paths are set correctly for the following steps.
Check the current value of the port number by using a command of the following form at the operating system command prompt:
inoadmin getproperty CentraSite "<ParameterName>"
The <ParameterName> can be any of the port names shown in the above table. Example:
inoadmin getproperty CentraSite "HTTP port"
The inoadmin program is available under the location <CentraSiteInstallDir>/bin.
Assign a new port number by using the following command at the operating system command prompt:
inoadmin setproperty CentraSite "<ParameterName>" "<NewPortNumber>" norestart
where <NewPortNumber> is the new port number that you wish to use.
Stop the CentraSite Registry Repository and start it again.
The procedure to change a configured CRR port in a CAST web application is as follows:
To change a CRR port number in a CAST web application
Open the configuration file of the web application.
See the section Changing the Certificate Configuration for the CAST Components for information about the names and locations of the configuration files for the web applications.
Note that not all of the web applications store information about the CRR port numbers.
Search for a string containing a URL of the form https://<machine>:<port>/CentraSite/CentraSite, where <machine> is the machine hosting the CRR and <port> is the currently used CRR port.
Replace the port number by the new port number.
If there are any other such URLs in the file, modify them also as required.
Ensure that you change the configuration files of all of the CAST web applications that contain CRR port numbers. When you have done this, restart the Software AG Runtime.
The default Software AG Runtime port numbers for the CAST components are 53307 for plain HTTP communication and 53308 for HTTPS communication. The port 53305 is used to provide compatibility with the previous product releases as it was used by the CRR.
The port numbers are configured in property files that are located in <SuiteInstallDir>/profiles/CTP/configuration/com.softwareag.platform.config.propsloader. If for any reason these port numbers are unsuitable (for example, your environment might require these port numbers for a non-Software AG application), you can change them in the appropriate property files in this location as follows:
com.softwareag.catalina.connector.http.pid-CentraSite.properties
This file contains parameter settings for HTTP communication.
com.softwareag.catalina.connector.https.pid-CentraSite.properties
This file contains parameter settings for HTTPS communication.
com.softwareag.catalina.connector.http.pid-CentraSite-CrrHttp.properties
This file is provided for compatibility with previous product
releases, for which different default port numbers were used.
In general, Software AG Runtime has to be restarted for the changes to take effect.
