Launcher options

In the Options list of the Options window, when you select Launchers, the configuration options described below are displayed. These options allow you to manually configure and override connection information for each Launcher connection in the Management Console.

Override configuration

You can manually configure and override connection information for each Launcher connection in the Management Console. Typically, the Management Console relays control commands (start, stop, pause, resume, disconnect) to a Java-based Launcher service, which in turn executes the commands to the process running. However, you can manually override the typical process so that the Management Console bypasses the Java-based service and communicates directly with the process running. In this case, the Management Console can relay only limited control commands (stop, pause, resume) to the process running. The Launcher itself must be manually started from the CPU where it resides.

The following list describes the communication process that occurs when you use the override configuration option. The port numbers that are referenced are the default numbers.
  • Control information including stop, pause, and resume commands, are communicated between the Launcher process that is running and the Management Console over port 7002.
  • Status information is communicated between the Launcher process that is running and the Management Console over port 7000.
  • Monitoring information is communicated between the Launcher process that is running and the Launcher Monitor over port 7001.

To access override configuration options:

  1. In the Management Console, select Tools > Options.

    The Options window opens.

  2. From the Options list, select Launchers.

    The override configuration options appear.