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- 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. |
1099 | RMI port required by ActiveMQ (not configurable). |
61617 | JMS broker port for ActiveMQ (Default-messaging-port). |
40001 | Port on which the RMI Registry listens for ehcache (Peer-listener-port). |
40002 | Port on which the remote objects bound in the registry receive calls for ehcache (Peer-Remote-Object-Port). |
10001 | Shutdown port (not configurable). |
61500 | Port for JMX connections (Jmx-port). |
7319 | AR Monitor RMI port for AR System Server |
7320 | AR Monitor RMI port for Mid Tier |
<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.