Important

   

Starting version 8.9.03, BMC Server Automation is renamed to TrueSight Server Automation. This space contains information about BMC Server Automation 8.9.02 and previous versions. For TrueSight Server Automation 8.9.03 and later releases, see TrueSight Server Automation 8.9.

Configuring communication ports

The following sections list the port requirements for both the Application Server and the Application Server Launcher. 
For a complete list of ports used by BMC Server Automation, see BMC Server Automation ports.

Required Application Server ports

By convention the Application Server listens to the ports listed in the following table:

Traffic Type

Port Number (by convention)

Description

AuthSvcPort

9840

Listening port for the Authentication Service associated with an Application Server. If this value is set to 0, the Application Server does not run an Authentication Service. By default the Authentication Service runs and listens on port 9840. This port is used for BMC Server Automation Console to Application Server communication, and is used in conjunction with the Java Management Extensions (JMX) port 9838 (by default) to authenticate the client AppSvcPort (port 9841 by default).

AppSvcPort

9841

Listening port for the Application Service (that is, the service that accepts client connections). If this value is set to 0, the Application Server does not run an Application Service. By default the Application Service runs and listens on port 9841.

ProxySvcPort

9842

The listening port for a Network Shell Proxy Service. You must manually define a listening port for the default deployment of an Application Server. Typically, ProxySvcPort is set to 9842 for the default Application Server. When you deploy a new Application Server with its type set toNSH_PROXY or ALL, the ProxySvcPort is automatically set to the base port plus 42. You can modify this value if necessary. If this value is blank, the Application Server does not run a Network Shell Proxy Service.

RegistryPort

9836

Listening port for traffic between Application Servers that cooperate by distributing jobs to each other. This port is used in a multiple Application Server configuration for Application Server to Application Server communication. It is used in conjunction with the RMI Execution Port 9850+ (which is obtained from the MaxPort/MinPort range when the Application Server starts). This communication is used for various administration tasks, such as to pull Application Server statistics, coordinate job work item execution, update the remote heartbeat status, and so on.

To configure ports

  1. Start the Application Server Administration console, as described in Starting the Application Server Administration console.
  2. To specify a listening port, enter the following:
    set <appServerComponent> <listeningport> #
    where <appServerComponent> is the option category you want to modify, <listeningport> is the type of listening port, and # is the number of the port.

    Examples

    • set authServer AuthSvcPort
    • set appserver AppSvcPort
    • set appserver RegistryPort
    • set appserver SSLPort
  3. Restart the Application Server.

Ports used in a multiple application server deployment

By default, the following ports are used by the Application Server Launcher for BMC Server Automation Console to AppServerLauncher communication:

Traffic Type

Port Number (By default)

Description

JMX

9700

JMX listener port used by from the BMC Server Automation Console to the Application Server Launcher, usually for local traffic only.

Incoming messages

9701

Default communications port used for Application Server communication with the Application Server Launcher. Each managed Application Server uses this port to notify the Application Server Launcher that the Application Server is up and in a ready state. This communication is all local traffic for this port

To configure ports for remote execution objects

Use this procedure to configure the JMX management port. This port is required for remote access to the Application Server using JMX.

  1. Start the Application Server Administration console, as described in Starting the Application Server Administration console.
  2. To specify a port used to access JConsole, enter the following:
    set ManagementService JMXManagementPort #
  3. Restart the Application Server.
Was this page helpful? Yes No Submitting... Thank you

Comments