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 TrueSight Server Automation, see TrueSight-Server-Automation-ports.

Required Application Server ports

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

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
    • {{code language="none"}}
      set authServer AuthSvcPort
      {{/code}}
    • 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 TrueSight Server Automation Console to AppServerLauncher communication:

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.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*