Understanding port numbers
Port numbers identify the TCP ports from which the BMC Remedy Action Request (AR) System server and the plug-in server will run. The following topics are provided:
Portmapper registration
A portmapper is a service that runs independently of the BMC Remedy AR System server and serves as a directory of port numbers.
Depending on whether or not the server is registered with a portmapper, users must perform the following actions while logging on to BMC Remedy AR System:
- If a server is registered with a portmapper, users do not need to specify the port number in the client, because the portmapper can locate the port and direct clients to the appropriate location.
- If a server is not registered with a portmapper, or if a Port 111 firewall blocks the portmapper port, users must specify the port.
When you start the server, it opens a port to listen to. You can specify a port for the server or let the server obtain an available port dynamically.
You can register a server with a portmapper and assign a port number. For example, if you do this and do not expose the portmapper outside a firewall, clients within the firewall do not need to be configured to access the specified port number. They can access the portmapper, which directs them to the port. Clients outside the firewall must be configured to access the specified port number.
Note
The BMC Remedy AR System server does not have a default port or specific range of ports. The operating system randomly assigns ports. To ensure that the portmapper always uses the same port for the BMC Remedy AR System server, specify a port during installation or use the BMC Remedy AR System Administration Console to configure the server after you install it.
Portmapper detection
On Windows, the AR System installer searches for an existing portmapper. If a portmapper is installed and running and you choose to register with a portmapper, the BMC Remedy AR System registers the server with that portmapper. If the installer does not detect a running portmapper and you chose to register with a portmapper, the installer installs the portmapper and registers the AR System server with that portmapper.
Port number assignment
If you do not register with a portmapper, you must assign a port number to any AR System server that you want clients to access directly, and to the plug-in server.
Note
Do not assign port numbers that conflict with port numbers used by other applications or other programs running on your system. To find out which port numbers are already in use, use the netstat -na command (UNIX) or the netstat -a command (Windows) at the command prompt.
Assign port numbers greater than 1024, because:
- Port numbers within the range 1 – 1024 are available for use only by the superuser, and many of these numbers are reserved.
- BMC Remedy AR System clients earlier than version 5.0 cannot access port numbers lower than 1024.
Important
- When installing on Linux, the installation program crashes if you enter port 12333 for any port parameter, such as the Java Plug-in Server TCP Port Number or the AR System Server TCP Port Number. This a known JVM issue in version Java 2 Runtime Environment, Standard Edition 8 update 45.
- You can also add the ports to the TCD-Specific-Port and Plugin-Port parameters by using the BMC Remedy AR System Administration Console.
For more information about port numbers, go to
http://www.iana.org/assignments/port-numbers
.
Default port numbers
The port number for each application must be unique. No application can use a port number that is already assigned to another application. For BMC Remedy AR System version 9.0, the installer automatically selects the port numbers for the different components during installation. For BMC Remedy Mid Tier, installer prompts to enter a port number that you can specify the next available port.
The following default port numbers are assigned during BMC Remedy AR System installation:
Module | Port usage description | Port Number |
|---|---|---|
Email Engine | RMI | 1100 - 1149 |
Flashboards | RMI | 1150 - 1199 |
| armonitor | Default port used by AR System server for armonitor processes. You can configure this port by updating the <installfolder>/bin/ARMonitor.properties file. | 7319 |
Mid Tier | Standard Apache Tomcat ports |
|
ServletExec | 8888 (admin) | |
C Plug-in server | TCP port | Uses portmapper |
Java plug-in | TCP port | 9999 |
Carte (Pentaho) server port (for Atrium Integrator | TCP | 20000 - 20050 |
FTS Java plug-in server | TCP | 9977 - 9998 |
Java virtual machine | JMX port Used for managing the Java virtual machine to connect using jconsole, jvisualvm, etc. You can configure this port using the Administrator console or updating the Jmx-port setting in Centralized Configuration | 61500 |
| Server group cache clustering | EhCache peer listener port You can configure this port using the Administrator console or updating the Peer-listener-port setting in Centralized Configuration. | 40001 |
| Server group communication | Peer Remote Object Port Defines the remote object port number where all ehcache instances from different servers communicate with each other. Port on which the remote objects bound in the registry receive calls for ehcache. | 40002 |
| JMS broker | JMS broker port Used to start the JMS broker that is used for messaging. You can configure this port using the Administrator console or updating the default-messging-Port setting in Centralized Configuration. | 61617 |
| Shutting down the BMC Remedy AR System server | Shutdown port Used to gracefully shutdown the BMC Remedy AR System server shutdown server. You can configure this port updating the Shutdown-port setting in the Centralized Configuration file. | 10001 |
| Jetty servlet container for REST API | Jetty servlet container for REST API Port used for Jetty servlet container which now runs with in the Serverj process. You can configure this port by updating the port setting in the <installfolder>\ jetty\etc\jetty-http.xml file. | 8008 |
Important
Before proceeding to the BMC Remedy AR System server installation, ensure that none of the AR System processes, such as Carte (Pentaho), FTS, and Plugin Server are started externally. This is because the required ports might be blocked in such a case.
BMC Atrium Core ports
The following table lists the default port number for all BMC Atrium Core features:
Component | Default port number | Is the port number configurable? | Supported port number |
|---|---|---|---|
NE Plug-in port | 9555 | Yes | Any |
BMC Atrium Plug-in port | 9556 | Yes | Any |
Tomcat HTTP port | Blank | Yes | Any |
Tomcat HTTPS port | Blank | Yes | Any |
Note
If you are using a preinstalled Tomcat server, the Tomcat HTTP Port and the Tomcat HTTPS Port fields are populated with the default port numbers. You cannot change the value of these fields.
Atrium Integrator ports
The following table lists the default third-party port numbers that are used by Atrium Integrator:
Component | Default port number | Is the port number configurable? | Supported port number |
|---|---|---|---|
MS SQL Server | 1433 | Yes | Any |
Oracle server | 1521 | Yes | Any |
Related topics
| Refer to... | To know about... |
|---|---|
| |
Setting ports and RPC numbers
| Assigning TCP port numbers to AR System servers |
ar.cfg or ar.conf
| The ar.cfg (Windows) or ar.conf (UNIX) files, which contain the AR System server configuration changes and are dynamically created when you install the AR System server. |
Configuring the Java plug-in server
| How to configure the Java plug-in server in the pluginsvr_config.xml file in the pluginsvr subdirectory of your AR System server installation directory. |
Comments