Peer communications are established through HTTP and TCP ports. BMC Atrium Orchestrator communications require unique port assignments for each component, and each component has specific port requirements.
The web server requires two ports: one for standard communications, and a second to receive shutdown commands. Different components can use the same port, provided they are installed on different computers. A port number must be available exclusively on the computer. The following table lists the default ports for BMC Atrium Orchestrator.
Port requirements for BMC Atrium Orchestrator components
Port description |
Protocol |
Components |
Default port |
---|---|---|---|
Communications port |
SSL or TCP |
Access Manager 1 |
61616 |
JMX RMI service port |
|
Access Manager |
1099 |
HTTP port |
HTTP |
Access Manager, repository, primary CDP, AP, graphing components 1 |
8080 |
Shutdown port |
HTTP |
primary CDP, repository 1 |
8005 |
Peer communications port |
JMS with SSL |
primary CDP 1 |
8501 |
Peer communications port |
JMS with SSL |
secondary CDP (HA-CDP) 2 |
8503 |
Peer communications port |
JMS with SSL |
AP: The installation program sets the start of the default port range by adding 2 to the primary CDP port number. It sets the end of the default port range by adding 256 to the starting port range. The first available port in the range becomes the listening port for the AP. 2 |
8503-8759 |
Peer communications port |
JMS with SSL |
LAP: The installation program sets the start of the default port range by adding 2 to the primary CDP port number. It sets the end of the default port range by adding 256 to the starting port range. The first available port in the range becomes the listening port for the LAP. 2 |
8503-8759 |
JMX RMI service port |
|
|
1089 |
|
|
^ 1 You can set this port value during installation.^ |
|
2 Comments
Matthew Highcove
Deepa Bhat