Page tree

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

This topic provides information about the various ports used by BMC ProactiveNet.

Securing internal port communication

Certain BMC ProactiveNet Server ports are used for communication between processes. Some ports are used by processes running on the server only; these are internal and must not be accessed by other computers in the network (Event server).

For security reasons, BMC Software recommends that all internal ports be made accessible only via the loopback address (127.0.0.1). By default, ports that are not required by external computers are secured, that is, the properties associated with the ports are set to the loopback address.

To make the BMC ProactiveNet Server accessible to other computers in a network, certain ports on the server must be made available. From a multi-homed computer, BMC ProactiveNet Server processes can be accessed using any of the available IP addresses.

The ports that the BMC ProactiveNet Server uses are bidirectional by default. That is, the TCP/IP ports transmit and receive data and can be used to perform read and write operations.

Note

Copy the values from installationDirectory/pw/pronto/conf/pronet.conf to installationDirectory/pw/custom/conf/pronet.conf and make changes in the custom/pronet.conf file to retain the changes for upgrades.

BMC ProactiveNet Server ports

Port

Process

Properties

Default

Procedure to secure port

Multi-homed computer setup

2638

Database Server

pronet.api.database.hostname
(installationDirectory/pw/custom/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/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/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/pronet.conf)

127.0.0.1

Internal process; secured by default

Port not required by an external computer.

8093

JBoss JMS Server

In line number 74 of the amq-broker-config.xml file,
<transportConnector discoveryUri=
"multicast://default"
name="bppm-jms-broker-tcp-conn" uri="tcp://0.0.0.0:8093?
transport.useInactivityMonitor=false"/>

(installationDirectory/pw/jboss/server/
minimal_jms/deploy/
activemq-ra.rar@/amq-broker-config.xml)

 

Internal process; secured by default

Port not required by an external computer. Leaf servers use this port to communicate to the Central Monitoring Administration (CMA).

1100

JBoss JNDI

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

0.0.0.0

Set the property value to 127.0.0.1. If the BMC Atrium CMDB is integrated with BMC ProactiveNet 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 ProactiveNet Server. If you use an LDAP integration, port 389 can be accessed from the BMC ProactiveNet Server (from the server to the Active Directory port).

BMC ProactiveNet Integration Service ports

 

Port

Process

Procedure to change the port

3182

Used by the BMC ProactiveNet Integration Service.

It is also used by the BMC ProactiveNet 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\pronet.conf
During the BPPM Agent installation, users might change the port.

3183

BMC ProactiveNet Integration Service listens for the services. Used in 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.
    • km must either be loaded or preloaded.
  • Using the environment variable
    Run the following command to set the PROXYSERVERSenvironment 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 using the Administration Console.

12124

Used by the BMC ProactiveNet Integration Service to listen for communication from the Agent Controller.

This port can be changed using the BMC ProactiveNet Administration Console or CLI.

PATROL Agent to Integration Service ports

  

Port

Process

Procedure to change the port

8005

Used by JServer to shut
down the 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

8008

Tunnel Proxy port

Change the port number in the pronet.jboss.apache.port file in your operating system:

  • Microsoft Windows: pw\pronto\conf\pronet.conf
  • Linux or Solaris: pw/pronto/conf/jserv.properties

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 port number in the pronet.jboss.jms.port file in your operating system:

  • Microsoft Windows: pw\pronto\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

This is a non-configurable port. This port must be open.

12123

Agent Controller listens for 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 command pw system start
12128Jserver RMI port 

Change the value of the pronet.rmi.jserver.port property to the new port number in your operating system:

  • (Microsoft Windows): pw\pronto\conf\pronet.conf
  • (Linux/Solaris): /pw/custom/conf/pronet.conf

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 command pw system start

12134

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.

This is a non-configurable port.

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 command pw system start

15000

Connects the Agent Controller to the Rate process.
The Rate process passively listens to 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 command pw system start

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 command pw system start
  

For more information on BMC Atrium CMDB, see BMC Atrium CMDB online documentation