Setting ports and RPC numbers
Use the Ports and Queues tab to set server ports and RPC numbers as needed to communicate with other servers, clients, and services on the network. The Server Queue region on this tab enables you to configure server queues and threads as appropriate for your server, taking advantage of the multithreaded design of BMC Remedy AR System.
In this topic:
Assigning TCP port numbers to AR System servers
You assign one TCP port number for the AR System server. All initial contact with the server is through a single port. If you run multiple servers on the same computer, each server must use a unique port.
Clients must be configured with the server port number to enable server access without the use of a portmapper. If you do not allow the server to register with a portmapper, you must assign a TCP port number for the AR System Server. For more information about configuring clients, see Configuring clients for AR System servers.
If you change the TCP port number configured for AR System Server, ensure that you also make relevant changes to the AR Server Settings parameters in BMC Remedy Mid Tier Configuration tool.
Do not assign port numbers that conflict with port numbers used by other applications or programs running on your system. If you assign conflicting port numbers, your servers might not start as expected. To find out which port numbers are in use, enter one of the following commands at the command-line prompt:
- UNIX — rpcinfo -p
- Windows — netstat -a
Client tools can use ports 0-65535.
Ports 1-1024 are reserved ports; avoid using these ports. On UNIX, port numbers within the range 1-1024 are available only for the superuser, and many of these numbers are reserved.
To set server ports and queues
- In a browser, open the AR System Administration Console, and click System > General > Server Information.
The AR System Administration: Server Information form appears.
- Click the Ports and Queues tab.
AR System Administration: Server Information form--Ports and Queues tab
(Click the image to expand it.)
Edit the options as needed:
Ports and Queues tab fields
Field name AR System Configuration Generic UI form option Description
Server TCP/IP Port
Defines the TCP/IP port number for the AR System server. Enables clients to have access to the server without a portmapper. When set to 0, which is the default, the portmapper assigns the port.
Ensure that you use the same port number (TCD-Specific-Port) for the instances of the
server_portparameter in the pluginsvr_config.xml file that is located in the <Install Dir>/pluginsvr directory.
If you set the Server TCP/IP Port field to a value less than 1024, older clients cannot connect.
Distributed Server RPC Program Number Obsolete. See Assigning an RPC program number to DSO.
Number of Selector Threads
Defines the number of threads that can be used to monitor all live client socket connections for IO activity. When the thread detects any activity, it forwards the call to the appropriate queue. The default value is 1.
Defines the JMX port number that enables administrators to connect to JVM by using Java Messaging Extensions (JMX). The default port number is 61500.
Message Broker Port
The specific port to which the JMS broker binds when sending messages to registered clients. The default port number is 61617.
Cache Peer Listener Port
Peer-listener-port Defines the port number where all ehcache instances from different servers communicate with each other. The default port number is 40001. Cache Peer Remote Port Peer-Remote-Object-Port BMC Remedy AR System version 9.1.02.001 and later. Defines the remote object port number where all ehcache instances from different servers communicate with each other. The default port number is 40002.
Alert Outbound Port
The specific TCP port to which the server binds when sending alert messages to registered clients. If multiple alert threads are started, the number represents the starting port number in a consecutive range of numbers available for the alert threads. If no port number is specified or if 0 is entered, the portmapper randomly assigns an available port to the server.
Plugin Loopback RPC Program Number
Plugin-Loopback-RPC-Socket Defines a private queue for all loopback calls from the plug-in server, regardless of which plug-in application initiates the call. For more information about Plugin Loopback RPC Socket, see Private queues for loopback calls.
Register with Portmapper
Defines whether the AR System server and the plug-in server are registered with AR System Portmapper. If the check box is
- Selected — They are registered. The server is registered if not previously registered. AR System clients can get the port number of the AR System server and the plug-in server from AR System Portmapper.
- Cleared — They are not registered. If the server was previously registered, this option removes the registration. AR System clients cannot get the port number of the AR System server and the plug-in server from the portmapper.
If you are running multiple servers on a single computer, you can select the Register with Portmapper option for one server only.
Enables you to define server queues specific to your needs. For most types of server queues, you can specify a minimum and maximum number of threads. For the escalation queue, only the maximum threads number is used, and all threads are started at startup time.
- If you do not specify a fast or list queue or specify only one thread, three threads are started to meet the minimum system requirements for each queue.
- If the server starts more threads than specified to meet system requirements for fast and list queues, it does not change the number specified.
- For all other types, if you do not specify a number, the system defaults to one minimum and one maximum thread per server queue.
Client Type to RPC Restriction Mapping
Enables you to direct all API calls from a given client type to a private queue.
Add Client RPC Mapping allows you to select the client types from the predefined list and assign them to a private queue.
To create user defined client types, select Add Custom Client Type, which displays the Client Type Registration form and allows you to create custom client types.
The settings are updated under the shared components in the Centralized Configuration form, after you click Apply. For more information, see Configuration settings N-R.
Note: You can only direct the Java API calls created using BMC Remedy AR System 9.0 Service Pack 1 or later.
- Click Apply.
Restart the server for the changes to take effect.
Configuring ports for firewall in a server group
In a server group environment, if you need to configure a firewall between AR System servers, you must allow certain ports in firewall as an exception for communication between the servers. This is required for the server group to function correctly. You must allow the following ports on each server:
<TCP port configured
AR System server TCP port (TCD-Specific-Port).
Note: Portmapper may not be used, since portmapper selects a random port that is available in the system and firewall needs a definite port to be allowed.
RMI port required by ActiveMQ (not configurable).
JMS broker port for ActiveMQ (Default-messaging-port).
Port on which the RMI Registry listens for ehcache (Peer-listener-port).
Port on which the remote objects bound in the registry receive calls for ehcache (Peer-Remote-Object-Port).
Shutdown port (not configurable).
Port for JMX connections (Jmx-port).
<Plugin servers ports>
Configurable in the ar.cfg (Plugin-Port) and the pluginsvr_config.xml file in different plugin server processes.
To configure a Microsoft Windows server for firewall
- Go to Control Panel > Windows Firewall.
- In the Windows Firewall popup, click Allow a program through Windows Firewall link.
- In the Windows Firewall Settings pop-up window, on the Exceptions tab, click Add Port and enter the input name and the required port numbers.
- Repeat step 3 above to add more port numbers.
- Click OK to close the Windows Firewall Settings window.