Configuring RMI ports

The Impact Server opens a number of ports on a machine for Java™ Remote Method Invocation (RMI) operations.

There are a few exposed properties that you can use to control which ports are used. By default, a random port is opened on the host system that is used by the RMI registry. You can control RMI ports where a firewall exists on a network and the exact control of which ports must be opened is necessary. You specify the properties in the $IMPACT_HOME/etc/<ServerName>_server.props properties file.

Similarly Impact Servers communicate with each other using RMI ports. The ports specified here must also be open in their respective firewalls.

Note: When you install Impact, the installer asks for the RMI port information. This is done using the Install panels, or for a silent install, using the response file: responsefiles/silentInstall_response.xml or silentInstall_response_ext.xml when the NOI extension package is used.

To control which ports are used by Impact when exporting RMI objects, you must provide values for the following properties:

impact.server.rmiport: This property specifies the port that Impact uses when starting its RMI registry.
impact.rmiPortRangeStart: This property specifies the minimum value of the port number that Impact uses for its RMI registry.
impact.rmiPortRangeEnd: This property specifies the maximum value of the port number that Netcool®/Impact uses for its RMI registry.

These values should span a range of approximately 100 ports on your machine and they force Impact to open the ports in this range only. When specified the Impact Server uses this range of ports when exporting RMI objects.

Note: When you install Impact, the installer also asks for the ActiveMQBroker port information. This is also done using the Install panels, or for a silent install, using the response file: responsefiles/silentInstall_response.xml or silentInstall_response_ext.xml when the NOI extension package is used.

Important: In a cluster configuration, if Impact Servers are communicating through a firewall, the secondary Impact Server must be able to access the Name Server on the primary, and the other way round. To achieve that, open the Name Server port on the firewall. By default the ports are 9080, or 9081 for SSL for the Impact Server installation and 16310, or 16311 for SSL for the GUI Server installation.