1.8 Monitoring WEBES Processes

Hl25Q/1.8 Monitoring WEBES Processesu,

™

2 (
: " 1.8 Monitoring WEBES Processes

You can monitor the WEBES Director process using the following command:

desta status

Ú This command generates a brief message describing the current state of the DESTA Director process. The states that may be reported are given here:

(.The Director's status could not be determined.
(The Director is NOT running.
(}The Director's status file indicates it is running, but the process ID was not found, so the Director process is NOT running.
(The Director is running.
(The Director is starting up.
(The Director is shutting down.

ò If the status is undetermined, or you want more detailed information about sub-processes, you may want to use the monitoring procedures specific to your operating system.

2
P ;  Note
:
f With UNIX and Windows, the WEBES processes are listed using the name java. Other applications running on your system may also be listed using the name java. Therefore, when using the procedures described here, it is important to make sure that the processes in question are WEBES processes.

8 Tru64 UNIX

9 All WEBES processes are Java-based, using the Java Runtime Environment bundled with WEBES. All WEBES processes run under the java executable. The processes currently running can be displayed with the command:

2ps ugxww | grep com.compaq.svctools | grep -v grep

This searches for a command parameter included in every WEBES process command, instead of searching for java which could show other non-WEBES Java-based applications as well.

e Example output is shown here:

ßroot      17671  0.3  0.2 2.09M 392K ttyp1    S N 16:06:57     0:00.04 ksh /usr/opt/compaq/svctools/bin/desta exec com.compaq.svctools.ca.cli.CLIInterpreter analyze /usr/opt/compaq/svctools/ca/examples/gs320_uce_ivp.errlog
root      17751 0.0 5.0 22.4M 13M ttyp1    I N 16:06:21     0:02.13 /usr/opt/compaq/svctools/jre/bin/../bin/alpha/native_threads/java -DSvctools.Home=/usr/opt/compaq/svctools -DSwcc.Home=/var/adm -Xms8M -Xmx128M com.compaq.svctools.desta.util.DESTAProcessWrapper
root      18097 0.0 12.0 57.1M 30M ttyp1    S N 16:06:17     0:12.11 /usr/opt/compaq/svctools/jre/bin/../bin/alpha/native_threads/java -DSvctools.Home=/usr/opt/compaq/svctools -DSwcc.Home=/var/adm -Xms8M -Xmx128M com.compaq.svctools.desta.core.DESTAController
Croot      18155 73.4 6.5 33.4M 17M ttyp1    U N 16:06:57     0:03.89 /usr/opt/compaq/svctools/jre/bin/../bin/alpha/native_threads/java -DSvctools.Home=/usr/opt/compaq/svctools -DSwcc.Home=/var/adm -Xms8M -Xmx128M com.compaq.svctools.ca.cli.CLIInterpreter analyze /usr/opt/compaq/svctools/ca/examples/gs320_uce_ivp.errlog

µ In this example, process 18097 is the main Director process, started with the DESTAController Java class. Process 17751 is a subprocess of the Director (subprocesses start with the DESTAProcessWrapper Java class). Process 18155 and its parent Korn shell script wrapper process 17671 are a CLI command analyzing an example event log.

8OpenVMS

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

h4show system te
e

E(r(or sho sys for short)E

1e Example output is shown here:
e

reLOpenVMS V7.1-2 on node FIGARO 16-MAR-2001 15:32:50.14 Uptime 14 21:05:23o"
vM Pid    Process Name    State Pri      I/O       CPU       Page flts Pagesor
rM00000101 SWAPPER         HIB     16        0   0 00:04:10.34         0      0o""
;M00000106 IPCACP          HIB     10       10   0 00:00:00.00        30     23rg
=M00000107 ERRFMT          HIB      8    33813   0 00:00:10.05       189     61ni
iM00000109 OPCOM           HIB      7     1709   0 00:00:00.30       416     41,iT
/...+az
O00000797 DESTA Director HIB      6   110831   0 00:03:14.75    112196   8192 Mf=
AP0000079A JOHNSON_3       HIB      6    37957   0 00:01:22.05      7612   1102 MSb
>P000006B5 THOMAS_1        HIB      4     8967   0 00:00:03.04     11610   1771 MS t

d‰ In the above example, the DESTA Director parent process is shown. That process has also spawned a subprocess named JOHNSON_3, since the user JOHNSON started the Director, but the relation is not apparent from the output. Other WEBES processes, such as Compaq Analyze Command Line Interface commands, appear named after the user that started them, such as THOMAS_1 in this example, although it is not apparent that the process is a WEBES process.
h

o8Windows

D> Use the Windows Task Manager to monitor processes in Windows. Start the Task Manager by pressing Ctrl+Alt+Del, and then pressing the Task Manager button. Once the Task Manager window appears, click the Processes tab to view the running processes.

T® All WEBES processes are Java-based, using the Java Runtime Environment bundled with WEBES. All WEBES processes appear in the Task Manager list as java.exe. However, not all java.exe processes are guaranteed to be WEBES processes. Other non-WEBES Java-based applications may also 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 or High priority. However, other non-WEBES Java processes may also run at Low priority. Because the Director runs as a Windows service, there is an additional process named DESTAService.ex, which wraps the Director's java.exe processes and runs for the lifetime of the Director. The DESTAService.ex process also runs at Low priority.

" If the Base Priority column is not shown in the Task Manager list, chose Select Columns from the View pull-down menu. In the window that appears, click Base Priority, then OK.

i
· N

h SE

P	; Note
	: f With UNIX and Windows, the WEBES processes are listed using the name java. Other applications running on your system may also be listed using the name java. Therefore, when using the procedures described here, it is important to make sure that the processes in question are WEBES processes.