This following tables provide information about ports that can be configured only after the installation of Infrastructure Management. For information about ports that can be configured during the installation of Infrastructure Management, see Ports-that-can-be-configured-during-installation.
Infrastructure Management ports
| | | | | Multi-homed computer setup |
---|
| | pronet.api.database.hostname (installationDirectory/pw/custom/conf/pronet.conf) | | Set the property value to 127.0.0.1, if it is not already set to that value. This prevents the database server from being accessed from other servers for reporting. | Set the IP address of the required server as the value of the property. |
| | pronet.apps.agent.localhostaddress (installationDirectory/pw/custom/conf/pronet.conf) | | | Set the IP address of the required server as the value of the property. The port is not required by an external computer. |
| | pronet.rate.hostIp (installationDirectory/pw/custom/conf/pronet.conf) | | Internal process used by JServer; secured by default | Port not required by an external computer. |
| | pronet.jserver.event.hostIp (installationDirectory/pw/custom/conf/pronet.conf) | | Internal process used by JServer; secured by default | Port not required by an external computer. |
| | pronet.apps.logging.logServer.hostname (installationDirectory/pw/custom/conf/pronet.conf) | | Internal process; secured by default | Port not required by an external computer. |
| | (Microsoft Windows) - In the installationDirectory\pw\custom\conf\pronet.conf file:
- Change the value of the pronet.jboss.jms.port property to the new port number
- Add pronet.jboss.jms.port.cs property and update it with the new port number
- Update the URI attribute of transportConnector property in the \pw\jboss\server\minimal_jms\conf\amq-broker-config.xml file to the new port number
<transportConnector name="bppm-jms-broker-tcp-conn" uri="tcp://0.0.0.0:8093?transport.useInactivityMonitor=false"/> </transportConnectors> (Linux or Solaris) - In the installationDirectory/pw/custom/conf/pronet.conf file:
- Change the value of the pronet.jboss.jms.port property to the new port number
- Add pronet.jboss.jms.port.cs property and update it with the new port number
- Update the URI attribute of transportConnector property in the /pw/jboss/server/minimal_jms/conf/amq-broker-config.xml file to the new port number
<transportConnector name="bppm-jms-broker-tcp-conn" uri="tcp://0.0.0.0:8093?transport.useInactivityMonitor=false"/> </transportConnectors> Change the following reference of JMS Server port in /pw/pronto/bin/startdwhouse script file to the new port number $ret = system "$ENV{'PRONTO_HOME'}/bin/runjavascripts.PortCheck 8093 300 1 > $LOGFILE 2>&1";
Before changing the JBoss JMS Server port information, delete the TrueSight Infrastructure Management Server from the TrueSight Presentation Server and add it back after making the port information changes. | | Internal process; secured by default | Port not required by an external computer. The TrueSight Infrastructure Management Servers use this port to communicate with the TrueSight Presentation Server. |
| | pronet.apps.jboss.bind.address (installationDirectory/pw/conf/pronet.conf) | | Set the property value to 127.0.0.1. If the BMC Atrium CMDB is integrated with Infrastructure Management and you change this property, then the BMC Impact Model Designer can not communicate with the publishing server. | Port not required by an external computer. |
Note
Port 389 is used by Active Directory. An LDAP server port can also be accessible from the BMC TrueSight Infrastructure Management Server. If you use an LDAP integration, port 389 can be accessed from the BMC TrueSight Infrastructure Management Server (from the server to the Active Directory port).
Integration Service ports
| | Procedure to configure the port |
---|
| Used by the Integration Service. It is also used by the administration console to communicate with Integration Service. | installationDirectory\pw\pproxy\PNS\bin\pproxsrv.exe -install -p 3182 -m 3182 is the default port number. A different port can be given in the command prompt and updated to custom\conf\pronet.conf During the installation of the Integration Service, you can specify a different port number in the command prompt and update the value in the custom\conf\pronet.conf file. |
| Integration Service listens for the services. Used in a failover configuration. | Using the command line PATROLAgent \-proxyserver tcp:<IntegrationServiceHost>: <StagingAdapterPort> \-p <PATROLAgentPort> \-km Linux/Solaris3.km
where, - <IntegrationServiceHost> is the system in which the Integration Service is running
- <StagingAdapterPort> is the port number that the PATROL Agent registers automatically with the Integration Service. The default port number is 3183.
- <PATROLAgentPort> is the port number of the PATROL Agent. The default port number is 3181.
- The TKM must either be loaded or preloaded.
Using the environment variable Run the following command to set the PROXYSERVERS environment variable: set <PROXYSERVERS>=tcp:<Integration Service Host>: <StagingAdapterPort> where, PROXYSERVERS is the environment variable. Using the PATROL Configuration Manager rule For information about PATROL Configuration Manager (PCM), see the PATROL Configuration Manager User Guide and BMC Performance Manager Consoles Release Notes. To configure the PATROL Agent using the PCM rule, run the following command: "/AgentSetup/proxy/proxyServers" = { REPLACE="tcp:<IntegrationServiceHost>:< StagingAdapterPort >"} Note You can also change the Staging Adapter port number using the administration console.
|
| Used by the Integration Service to listen to communication from the Agent Controller. | This port can be changed using the Administration Console or CLI. |
PATROL Agent to Integration Service ports
| | Procedure to configure the port |
---|
| Used by JServer to shut down the Apache Tomcat server. | Change the port number in the appropriate files for your operating system: - (Microsoft Windows): pw\pronto\conf\pronet.conf
and pw\pronto\conf\jserv.properties - (Linux or Solaris): tomcat/conf/server.xml
|
| Used by the Tomcat server to connect to Apache | Change the port number in the appropriate files for your operating system: - (Microsoft Windows): pw\pronto\conf\pronet.conf and pw\pronto\conf\jserv.properties
- (Linux or Solaris): tomcat/conf/server.xml
|
| | Change the value of the pronet.jboss.jms.port property to the new port number in the appropriate files for your operating system: - (Microsoft Windows): pw\custom\conf\pronet.conf and pw\jboss\server\minimal_jms\deploy\activemq-ra.rar@\amq-broker-config.xml
- (Linux or Solaris):
pw/jboss/server/minimal_jms/delpoy/activemq-ra.rar@/ amq-broker-config.xml
|
| | - In the \pw\custom\conf\pronet.conf file, change the value of the pronet.jserver.event.port property to the new port number.
- Restart the system by running the pw system start command.
|
| Agent Controller listens to the JServer on this port | - In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.agentcontroller.port property to the new port number.
- Restart the system by running the pw system start command.
|
| CheckPoint Monitor port Used to receive log messages. | - In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.ckpmon.lea.listenport property to the new port number.
- Restart the system by running the pw system start command.
|
| This is a TCP port that is used for communication between the Agent Controller and the Apache server for the agent. Communication is initiated when the Agent Controller starts. | - In the /pw/custom/conf/pronet.conf file, change the value of the pronet.ipc.proxy.controllerconnport property to the new port number.
- Restart the system by running the pw system start command.
|
| | - In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.logging.logServer.port property to the new port number.
- Restart the system by running the pw system start command.
|
| Connects the Agent Controller to the Rate process. The Rate process passively listens on port 15000 until the Agent Controller initiates contact. | - In the /pw/custom/conf/pronet.conf file, change the value of the pronet.rate.port property to the new port number.
- Restart the system by running the pw system start command.
|
| | - In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.messageserver.port property
to the new port number. - Restart the system by running the pw system start command.
|
Cell and Integration Service ports
The following table lists the other ports that you can configure only after the installation of Infrastructure Management:
| | Procedure to configure the port |
---|
| Used by the Central Monitoring Administration cell to accept client connections | - If the cell is running, stop the cell by entering the following command: mkill -n cell_name
- Open the mcell.dir file and change the cell port to the new port number. You must change the cell port in the mcell.dir files of all the components (cells, integrations, and so forth) that have to connect to that cell.
- Restart the cell.
|
| Used by the cell to accept client connections | - If the cell is running, stop the cell by entering the following command: mkill -n cell_name
- Open the mcell.dir file and change the cell port to the new port number. You must change the cell port in the mcell.dir files of all components (cells, integrations, and so forth) that have to connect to that cell.
- Restart the cell.
|
| Used as a gateway from an embedded cell to the BMC TrueSight Infrastructure Management Server | - Update the new changes on mcell.dir.
- Ensure that the cell is running.
- Restart TrueSight Infrastructure Management server.
- Restart BMC Event Adapter.
|
| Agent Controller call back port that is used by the Integration Service to send data back to the BMC TrueSight Infrastructure Management Server | Note Any changes to the Agent Controller call back port configuration must be made on all the Integration Services. - In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.agent.cntl.port property to the new port number.
- Restart the system by running the pw system start command.
- Repeat for all Integration Services.
- Restart the Integration Service.
|
Network-ports
Updating-port-numbers-to-change-the-Apache-HTTP-port-80-default