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/configure 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

pronet.jboss.jms.port

(installationDirectory/pw/custom/conf/pronet.conf)


 

(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";

    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.

 

1100

JBoss JNDI

pronet.apps.jboss.bind.address (installationDirectory/pw/custom/conf/pronet.conf)

0.0.0.0

Set the value of the pronet.apps.jboss.bind.address property 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.

How to customize the port:

  1. In the installationDirectory\pw\custom\conf\pronet.conf file:
    • Change the value of the pronet.jndi.port property to the new port number.
    • Update the value of the java.naming.provider.url property to the new port number.
      For example, java.naming.provider.url=jnp://localhost:3000
  2. Update the value of the Port attribute in the \pw\jboss\server\minimal_jms\conf\jboss-service.xml file to the new port number:

    <attribute name="Port">3000</attribute> 
    <attribute name="RmiPort">2100</attribute> 
    <attribute name="BindAddress">${jboss.bind.address}</attribute> 
  3. Restart the system by running the pw system start command.

Port not required by an external computer.

Integration Service ports

Port

Process

Procedure to configure the port

3182

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.

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 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.

12124

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

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

  1. In the \pw\custom\conf\pronet.conf file, change the value of the pronet.jserver.event.port property to the new port number.
  2. Restart the system by running the  pw system start command.

12123

Agent Controller listens to the JServer on this port

  1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.agentcontroller.port property to the new port number.
  2. Restart the system by running the pw system start command.

12130

CheckPoint Monitor port used to receive log messages.

  1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.ckpmon.lea.listenport property to the new port number.
  2. 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.

  1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.ipc.proxy.controllerconnport property to the new port number.
  2. Restart the system by running the pw system start command.

12141

Log Server port

  1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.logging.logServer.port property to the new port number.
  2. 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.

  1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.rate.port property to the new port number.
  2. Restart the system by running the pw system start command.

45000

Message Server port

  1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.messageserver.port property
    to the new port number.
  2. 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:

PortDescriptionProcedure to configure the port
1827Used by the Central Monitoring Administration cell to accept client connections
  1. If the cell is running, stop the cell by entering the following command: mkill -n cell_name
  2. 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.
  3. Restart the cell.
1828Used by the cell to accept client connections
  1. If the cell is running, stop the cell by entering the following command: mkill -n cell_name
  2. 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.
  3. Restart the cell.
1851Used as a gateway from an embedded cell to the Infrastructure Management Server
  1. Update the new changes on mcell.dir.
  2. Ensure that the cell is running.
  3. Restart TrueSight Infrastructure Management server.
  4. Restart BMC Event Adapter.
12126Agent Controller call back port that is used by the Integration Service to send data back to the Infrastructure Management Server
  1. In the /pw/custom/conf/pronet.conf file, change the value of the pronet.apps.agent.cntl.port property to the new port number.
  2. Restart the system by running the pw system start command.
  3. Repeat for all Integration Services.
  4. Restart the Integration Service.

Note: Any changes to the Agent Controller call back port configuration must be made on all the Integration Services.

Was this page helpful? Yes No Submitting... Thank you
© Copyright 2013-2016 BMC Software, Inc.
© Copyright 2013-2016 BladeLogic, Inc.
Legal notices