2.4.2  Monitoring from the Operating System

If the CLI returns an undetermined status, or you want more details about subprocesses, you can use the monitoring procedures specific to your operating system.

In UNIX variants and Windows, some WEBES processes are listed under the "Java" name. Be aware, however, that other applications also might use the Java name. Be careful to make sure that the processes you are monitoring really are WEBES processes, as shown in the following examples.

2.4.2.1  Tru64 UNIX

Some WEBES processes are Java-based, using the Java runtime environment (JRE) bundled with WEBES. These WEBES processes run under the java executable. Other processes are C++ based and run under their own image name. The processes currently running can be displayed with the command:

# ps ugxww | grep /usr/opt/hp/svctools | grep -v grep

This searches for the path containing all WEBES executable image names, including the "java" image in the JRE embedded in WEBES.

Example output is shown here:

root 146989 0.0 0.1 2.95M 552K pts/0 S N 16:31:43 0:00.05 /usr/opt/hp/svctools/common/wccproxy/share/WCCProxy
root 147095 0.0 3.4 22.7M 17M pts/0 S N 16:31:49 0:05.24 /usr/opt/hp/svctools/common/jre/bin/../bin/alpha/native_threads/java -classic -noverify -DSvctools.Home=/usr/opt/hp/svctools -DSwcc.Home=/var/adm -Xmx99m com.compaq.svctools.desta.core.DESTAController
root 147114 0.0 2.9 20.8M 15M pts/0 S N 16:31:53 0:03.01 /usr/opt/hp/svctools/common/jre/bin/../bin/alpha/native_threads/java -classic -noverify -DSvctools.Home=/usr/opt/hp/svctools -DSwcc.Home=/var/adm -Xmx136m com.compaq.svctools.desta.util.DESTAProcessWrapper
root 147145 0.0 0.1 3.16M 640K pts/0 S N 16:31:57 0:00.78 /usr/opt/hp/svctools/common/wccproxy/share/CAAgents -s 19 -p 3273 -1 -g
root 147148 0.0 0.1 2.92M 480K pts/0 S N 16:32:06 0:00.38 /usr/opt/hp/svctools/common/wccproxy/share/WCCAgents -s 20 -p 2877 -1 -g
jones 147172 0.0 0.1 2.30M 344K pts/1 S + 16:33:01 0:00.03 wsea analyze /usr/opt/hp/svctools/common/ca/examples/gs320_uce_ivp.errlog
jones 147180 0.1 0.1 2.49M 520K pts/1 S + 16:33:01 0:00.08 /usr/opt/hp/svctools/common/bin/desta exec com.compaq.svctools.ca.cli.CACLIInterpreter analyze /usr/opt/hp/svctools/common/ca/examples/gs320_uce_ivp.errlog
jones 147207 81.4 5.3 32.7M 27M pts/1 R + 16:33:01 0:05.60 /usr/opt/hp/svctools/common/jre/bin/../bin/alpha/native_threads/java -classic -noverify -DSvctools.Home=/usr/opt/hp/svctools -DSwcc.Home=/var/adm com.compaq.svctools.ca.cli.CACLIInterpreter analyze /usr/opt/hp/svctools/common/ca/examples/gs320_uce_ivp.errlog

In this example:

2.4.2.2  OpenVMS

Use the following command to show the processes running on an OpenVMS system:

$ show system

Example output is shown here:

OpenVMS V7.2-2 on node THIS 15-OCT-2002 15:03:52.59 Uptime 39 05:37:42
Pid      Process Name    State  Pri I/O     CPU            Page flts  Pages
...
0000F68D WCCProxy        LEF    6   353     0 00:00:00.07  504        201
0000F68E DESTA Director  HIB    5   198456  0 00:01:10.09  154670     12301 M
0000F68F SMITH_2         HIB    6   23027   0 00:02:31.40  25089      6285 MS
0000F691 CA.A.19.54240   HIB    6   341     0 00:00:00.16  422        286
0000F695 CA.A.20.54249   LEF    6   248     0 00:00:00.11  465        239
0000F698 WCC.A.1200.8989 LEF    6   201     0 00:00:00.10  382        220
0000F89C JONES_1         HIB    6   291     0 00:00:00.05  316        133 S
0000F69E JONES_2         COM    4   2656    0 00:00:07.57  73623      7357 MS
0000F342 RCM            HIB    7   0      0 00:00:00.00  23        30

In the above example, the DESTA Director parent process is shown. That process also has spawned a subprocess named SMITH_2, which only runs when needed, so named because the user SMITH started the Director, but the relation is not apparent from the output. Other WEBES processes, such as SEA CLI commands, appear named after the user that started them, such as JONES_1 and its subprocess JONES_2 in this example, although it is not apparent that they are WEBES processes. The WCCProxy process is a C++ based launcher for WEBES processes that communicates to the main Director process. The CA.A.nn.nnnn and WCC.A.nn.nnnn processes are C++ based processes launched by WCCProxy to send notifications, read the native binary event log, and send events to the main Director process. There may be more than one CA.A.nn.nnnn or WCC.A.nn.nnnn process running at a time, or none.

2.4.2.3  Windows

On Windows, press CTRL+ALT+DEL, open the Task Manager, and click the Processes tab to view running processes. WEBES Director processes consist of the following image names:

The main parent Java-based Director process is the DESTAService process, which runs as a Windows service. It spawns a subprocess when needed, which runs under the process name java.exe. The WCCProxy process is a launcher for C++ based WEBES processes that communicates to the main Director process. The CAAgents.exe and WCCAgents.exe processes are C++ based processes launched by WCCProxy to send notifications, read the native binary event log, and send events to the main Director process. There may be more than one CAAgent or WCCAgent process running at any time, or none.

All CLI commands run under the process name java.exe. However, not all java.exe processes are guaranteed to be WEBES processes. Java-based applications other than WEBES also may appear as java.exe.

You may be able to distinguish the Director set of processes from other WEBES and non-WEBES Java processes by looking at the base priority of the java.exe processes. The Director processes always run at low priority, while all other WEBES processes run at normal priority. However, other Java processes, not associated with WEBES, also may run at low priority.

If the Base Priority column is not shown in the Task Manager list:

  1. Choose View | Select Columns.
  2. Click Base Priority.
  3. Click OK.