Using the Launcher Monitor

To use the Monitor to view Launcher processes (systems) that are running in the Launcher, a series of steps must first take place:

  • One or more .msl files are generated and placed in the deployment directory that you specified in the Launcher Administration interface.
  • The Launcher service/daemon is running.
  • The Launcher is configured and a process is running in the Management Console.
  • From the Launcher Monitor, you must configure the server and port number where the Launcher is running.

To open the Launcher Monitor

Select Launcher Monitor from the Start > Programs menu under WebSphere® Transformation Extender n.n (where n.n represents the version number).

The Launcher Monitor window opens.

To start the Launcher Monitor

  1. From the Launcher Monitor window, select Options > Select Launcher.

    The Select Launcher window appears.

  2. Click Add.

    The Add Launcher window appears.

  3. Enter a name for the Launcher and click OK.
  4. Under User, enter the user name and password that corresponds to the server you need to connect to so that you can monitor a Launcher.
  5. Under Connection, enter the name or IP address of the server where the Launcher is running in the Server field.
    Note: The Server connection is either obtained from network configuration information or can be a TCP/IP address.
  6. In the Port field, type the port number that you want to use or accept the default port number, which is 5016.

    The port number is always the Launcher port number (configured in the Management Console) plus 1. The default port for the Launcher is 5015; therefore, the default port here is 5016. See Default Port Settings for more information about default port settings.

    On a UNIX server, the default port setting can be changed in the services file located on the machine where the Launcher is installed: /etc/services.

    On the z/OS® operating systems, the default port setting can optionally be changed in the TCPIP.ETC.SERVICES or in /etc/services, if installed.

  7. Under Timeout, enter a value (in seconds) in the Response field. This value can range from 30 to 3600 seconds, which is the time that can elapse without an initial response from the Launcher before a timeout occurs. The default setting is 30 seconds.
  8. Do one of the following activities:
    • To save this Launcher connection and close the Select Launcher window, click OK.
    • To connect to the Launcher and begin monitoring, click Connect.

      The Select System window opens.

    Notice that both .msl files are listed under System File Name. This is because if you have more than one .msl file running, all of the data consolidates into one compound system. This is the same functionality as the Management Console.

  9. Select CompoundSystem from the list (see Multiple Processes for additional information when using the multiple-processes feature) and click OK.
  10. From the Select Launcher window, click OK.

    Each map that is running in the process is displayed in an individual window as a sequentially numbered watch.