Ports that can be configured after installation

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-when-installing-Infrastructure-Management.

Infrastructure Management ports

Port	Process	Properties	Default	Procedure to secure port	Multi-homed computer setup
2638	Database Server	pronet.api.database.hostname (installationDirectory/pw/custom/conf/pronet.conf)	127.0.0.1	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.
12124	Local Agent	pronet.apps.agent.localhostaddress (installationDirectory/pw/custom/conf/pronet.conf)	127.0.0.1	Internal process	Set the IP address of the required server as the value of the property. The port is not required by an external computer.
15000	Rate	pronet.rate.hostIp (installationDirectory/pw/custom/conf/pronet.conf)	127.0.0.1	Internal process used by JServer; secured by default	Port not required by an external computer.
9149	JServer Event Server	pronet.jserver.event.hostIp (installationDirectory/pw/custom/conf/pronet.conf)	127.0.0.1	Internal process used by JServer; secured by default	Port not required by an external computer.
12141	Log Server	pronet.apps.logging.logServer.hostname (installationDirectory/pw/custom/conf/pronet.conf)	127.0.0.1	Internal process; secured by default	Port not required by an external computer.
8093	JBoss JMS Server	Note 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. (Microsoft Windows) Use the following command to stop TrueSight Infrastructure Management: pw sys stop 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 In the \pw\wildfly\standalone\deployments folder: Open the activemq-rar.rar file and extract the amq-broker-config.xml file. Take a backup of the amq-broker-config.xml file. In the amq-broker-config.xml file, update the URI attribute of transportConnector property to the new port number: <transportConnector name="bppm-jms-broker-tcp-conn" uri="tcp://0.0.0.0:8093? transport.useInactivityMonitor=false"/> </transportConnectors> After the change, save amq-broker-config.xml the file and add it to the activemq-rar.rar file in the \pw\wildfly\standalone\deployments folder again. In the \pw\wildfly\standalone\deployments folder: Take a backup of the amqbootstrap.sar file outside of the current directory. Open the amqbootstrap.sar file and extract the jboss-service.xml file that is located in the amqbootstrap.sar\META-INF directory. In the jboss-service.xml file, update the BrokerPort attribute to 8094. The default is 8093, which is shown below: <attribute name="BrokerPort">8093</attribute> Save the jboss-sesrvice.xml file and add it to the amqbootstrap.sar file in the amqbootstrap.sar\META-INF location, in the \pw\wildfly\standalone\deployments directory. Use the following command to start TrueSight Infrastructure Management: pw sys start (Linux or Solaris) Use the following command to stop TrueSight Infrastructure Management: pw sys stop 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 In the \pw\wildfly\standalone\deployments folder: Open the activemq-rar.rar file and extract the amq-broker-config.xml file. Take a backup of the amq-broker-config.xml file. In the amq-broker-config.xml file, update the URI attribute of transportConnector property to the new port number: <transportConnector name="bppm-jms-broker-tcp-conn" uri="tcp://0.0.0.0:8093? transport.useInactivityMonitor=false"/> </transportConnectors> After the change, save amq-broker-config.xml the file and add it to the activemq-rar.rar file in the \pw\wildfly\standalone\deployments folder again. 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"; In the \pw\wildfly\standalone\deployments folder: Take a backup of the amqbootstrap.sar file outside of the current directory. Open the amqbootstrap.sar file and extract the jboss-service.xml file that is located in the amqbootstrap.sar\META-INF directory. In the jboss-service.xml file, update the BrokerPort attribute to 8094. The default is 8093, which is shown below: <attribute name="BrokerPort">8093</attribute> Save the jboss-sesrvice.xml file and add it to the amqbootstrap.sar file in the amqbootstrap.sar\META-INF location, in the \pw\wildfly\standalone\deployments directory. Use the following command to start TrueSight Infrastructure Management: pw sys start		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.
1100	JBoss JNDI	Notes Take a back up of all the files before you add or change the port numbers in them. 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. In the In the installationDirectory\pw\custom\conf\pronet.conf file, add the value for JBoss JNDI port as shown below: pronet.jndi.port=1100 java.naming.provider.url=http-remoting://localhost:1100 pronet.ps.JNPServers=localhost:1100 In the installationDirectory\pw\wildfly\standalone\configuration\standalone-full.xml file, change the JBoss JNDI port value to the new port number. <socket-binding name="http" port="${jboss.http.port:1100}"/> In the installationDirectory\pw\server\etc\pserver.conf file, change the JBoss JNDI port value to the new port number. JNPServers=<hostname>:1100 In the **installationDirectory\pw\server\etc\pclient.conf file, change the JBoss JNDI port value to the new port number. JNPServers=<hostname>:1100 Note: When you run publish commands, if there are any JMS related connection errors, replace the hostname with localhost both in pserver.conf and pclient.conf files as shown in the following example, and restart the pserver. #pserver.conf and pclient.conf** JNPServers=localhost:1100	0.0.0.0	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.

Integration Service ports

Port	Process	Procedure to configure the port
3183	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 INTEGRATONSERVICES environment variable: set INTEGRATONSERVICES=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/integration/integrationServices" = { REPLACE="tcp:<IntegrationServiceHost>:<StagingAdapterPort>"} Note You can also change the Staging Adapter port number using the administration console.

PATROL Agent to Integration Service ports

Port	Process	Procedure to configure the port
8005	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
8009	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
8093	JMS Server port	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
9149	JServer port	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.
12123	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.
12130	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.
12134	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.
12141	Log Server port	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.
15000	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.
45000	Message Server port	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:

Port	Description	Procedure to configure the port
1828	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.
1851	Used as a gateway from an embedded cell to the 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.
12126	Agent Controller call back port that is used by the Integration Service to send data back to the 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.