Resolving The Problem

The Launcher, or Event Server, has a robust command line utility that allows control of the Launcher and any separate system process running under it. The command line utility name is launcher.sh.



The following code shows the UNIX launcher.sh and eventserver.sh command usage. Click on each option link to go to example usage and resulting output.

The examples are illustrated with V8.1 of the product and use the following values:

• LauncherName is aix5264
• systemname is simple
• examples that use separate launcher processes with multiple systems, systems are named simple and simple_2

launcher.sh (or eventserver.sh)


[-start]
[-stop [listenerport [hostname]]]
[-pause [listenerport [timeout [hostname]]]]
[-resume [listenerport [timeout [hostname]]]]
[-status LauncherName systemname]
[{-summary -history -statusinfo -configuration -all -xml} Launchername systemname]
[-startsystem Launchername {systemname -all}]
[-stopsystem Launchername {systemname -all}]
[-pausesystem Launchername {systemname -all}]
[-resumesystem Launchername {systemname -all}]

Definition of options:

[listenerport] - optional; the listening port specified in Launcher Administration; default is 5015

[hostname] - optional; the host name or IP address of where the launcher process is running

[timeout] - optional; the amount of time in seconds that the command line is blocked if the Launcher has not paused or resumed

Launchername - required; the name of the Launcher specified in the Management Console run on the UNIX server

systemname - required; the name of the system or group of systems specified in Launcher Administration; if not running under seperate launcher processes mode the systemname is CompoundSystem

Note: In V8.0 and V8.0.1 only, the eventserver.sh command line utility needs patch EC68152 to work correctly with separate system processes. You must request this patch from technical support. To request a patch Open a PMR, include versioning information, and refer to patch EC68152 in the problem description.


This option starts the Java Launcher. If "Automatic startup" is selected in Launcher Administration, then all systems or groups of systems defined are started.

CMD: launcher.sh -start
Successfully started Launcher

Back to top

This option stops the Java Launcher and all systems or groups of systems defined.

CMD: launcher.sh -stop 6161
Attempting to shut down launcher on port 6161 ...
Launcher listening on port 6161 shutdown.

Back to top

This option pauses all systems or groups of systems defined.

CMD: launcher.sh -pause 6161
Successfully paused Launcher

Back to top

This option resumes all systems or groups of systems defined.

CMD: launcher.sh -resume 6161
Successfully resumed Launcher

Back to top

This option shows the status for a system or defined group of systems. Execution mode of separate Launcher processes must be set.

CMD: launcher.sh -status aix5264 simple
Status of the system "simple" on the server "aix5264" and port "6161" is "System Stopped"

CMD: launcher.sh -status aix5264 simple
Status of the system "simple" on the server "aix5264" and port "6161" is "System Started"


When running in single launcher process mode, CompoundSystem must be specified as the system name.

CMD: launcher.sh -status aix5264 CompoundSystem
Status of the system "CompoundSystem" on the server "aix5264" and port "6161" is "System Started"

Back to top

This option shows the summary information for a system or defined group of systems. Execution mode of separate Launcher processes must be set.

CMD: launcher.sh -summary aix5264 simple
***********************************************************************
Time: 9/18/06, 6:14:48 PM
Host: aix5264
Port: 8000
Launcher Name: simple

Summary
-------

Memory Usage: 0
CPU Usage: 0
System Status: Running
Active Component Maps: 20
Active Listeners Up: 1
Active Listeners Down: 0
Active Connections: 0
Start Time: 12:30:29
Success Time: 01:05:56
Failure Time: 00:15
Up Time: 03:35
Pending Initialization: 295
Pending Initialization Maximum: 481
Pending Resource: 0
Pending Connection: 0
Pending Total Maps: 295
History Successes: 185
History Failures: 1
History Total Maps: 186
History Connection Failures: 0
History Deadlocks Detected: 0
History Function Failures: 1

***********************************************************************

Back to top

This option shows the history information for a system or defined group of systems. Execution mode of separate Launcher processes must be set.

CMD: launcher.sh -history aix5264 simple

***********************************************************************
Time: 9/18/06, 6:16:43 PM
Host: aix5264
Port: 8000
Launcher Name: simple

History
-------

Map Failures
------------
Component: genericMap
Map: /usr/app/wtx81/maps/genericMap.mmc
System: System1
Card: 0
Card Error: 0
Map Error: 30

Map Failures
-----------------
Component: genericMap
Function Name: Failed at Run function
Argument: genericRunMap
Reason: 8

***********************************************************************

Back to top

This option shows the status information for a system or defined group of systems. Execution mode of separate Launcher processes must be set.

CMD: launcher.sh -statusinfo aix5264 simple


***********************************************************************
Time: 9/18/06, 6:18:21 PM
Host: aix5264
Port: 8000
Launcher Name: simple

Status
------

Active Components
------------------
Component: genericMap
Map: /usr/app/wtx81/maps/genericMap.mmc
System: System1
State: Validating input
Card: 1
Resource:


Active Components
------------------
Component: genericMap
Map: /usr/app/wtx81/maps/genericMap.mmc
System: System1
State: Validating input
Card: 1
Resource:


Active Components
------------------
Component: genericMap
Map: /usr/app/wtx81/maps/genericMap.mmc
System: System1
State: Running Map genericRunMap
Card: 4
Resource: genericRunMap


Pending Components
------------------
Component: genericMap
Map: /usr/app/wtx81/maps/genericMap.mmc
System: System1
State: Initialization Pending
Card: 4
Reason: OK to run map
Resource Type: SINK
Resource Name:

***********************************************************************

Back to top

This option shows the configuration information for a system or defined group of systems. Execution mode of separate Launcher processes must be set.

CMD: launcher.sh -configuration aix5264 simple

***********************************************************************
Time: 9/18/06, 6:19:26 PM
Host: aix5264
Port: 8000
Launcher Name: simple

Configuration
-------------

System
------
Maximum Concurrent Maps: 20
Maximum Concurrent Maps Per Watch: 20
Pending Initialization High: 0
Pending Initialization Low: 0

Adapter Connections
-------------------
Adapter: (default)
Idle Time: 00:00
Keep Time: 00:00
Keep Minimum: 0
Advisory Limit: 4
Mandatory Limit: 0

***********************************************************************

Back to top

This option shows the all information -- summary, history, status, configuration, and xml -- for a system or defined group of systems. Execution mode of separate Launcher processes must be set.

Back to top

This option shows xml information for a system or defined group of systems. Execution mode of separate Launcher processes must be set.

CMD: launcher.sh -xml aix5264 simple

<?xml version="1.0"?>
<!DOCTYPE Launcher SYSTEM "/usr/app/wtx81/config/snapshot.dtd">
<Launcher LauncherName="simple" HostName="aix5264" Port="8000" DateTimeStamp="9/18/06, 6:21:10 PM">
</Launcher>

Back to top

This option starts a system or defined group of systems or all. The Java Launcher remains running. Execution mode of separate Launcher processes must be set.

CMD: launcher.sh -startsystem aix5264 simple
System "simple" has successfully responded with response "System Started" for the request "Start System"

CMD: launcher.sh -startsystem aix5264 -all
System "simple" has successfully responded with response "System Started" for the request "Start System"
System "simple_2" has successfully responded with response "System Started" for the request "Start System"

Back to top

This option stops a system or defined group of systems or all. The Java Launcher remains running. Execution mode of separate Launcher processes must be set.

CMD: launcher.sh -stopsystem aix5264 simple
System "simple" has successfully responded with response "System Stopped" for the request "Stop System"

CMD: launcher.sh -stopsystem aix5264 -all
System "simple" has successfully responded with response "System Stopped" for the request "Stop System"
System "simple_2" has successfully responded with response "System Stopped" for the request "Stop System"

Back to top

This option pauses a system or defined group of systems or all. The Java Launcher remains running. Execution mode of separate Launcher processes must be set.

CMD: launcher.sh -pausesystem aix5264 simple
System "simple" has successfully responded with response "System Paused" for the request "Pause System"

CMD: launcher.sh -pausesystem aix5264 -all
System "simple" has successfully responded with response "System Paused" for the request "Pause System"
System "simple_2" has successfully responded with response "System Paused" for the request "Pause System"

Back to top

This option resumes a system or defined group of systems or all. The Java Launcher remains running. Execution mode of separate Launcher processes must be set.

CMD: launcher.sh -resumesystem aix5264 simple
System "simple" has successfully responded with response "System Started" for the request "Resume System"

CMD: launcher.sh -resumesystem aix5264 -all
System "simple" has successfully responded with response "System Started" for the request "Resume System"
System "simple_2" has successfully responded with response "System Started" for the request "Resume System"

Back to top