Chapter 9. Integrating Tivoli Monitoring 547
Figure 9-152 Selecting Resource Model view
8. Using the integration at the basic level of implementation that we show in this
book consists primarily of viewing the events in the Web Health Console. The
instructions in this section show how to initially access the Web Health
Console. For has detailed instructions on how to use the Web Health Console
see, IBM Tivoli Monitoring User’s Guide Version 5.1.2, SH19-4569.
The integration can also be accessed through the command line interface. Using
the wdmlseng command, you can extract an overall view of the resource model
status on one or more endpoints through the command line interface.
Example 9-10 shows how we extracted the overall resource model status for
paris in the lab for this book.
Example 9-10 Viewing overall resource model status
milan:/# wdmlseng -e paris.itsc.austin.ibm.com -verbose
Forwarding the request to the endpoint:
paris.itsc.austin.ibm.com 1187404249.8.522+#TMF_Endpoint::Endpoint#
The following profiles are running:
itm-tws.pf#milan-region
DMXFileSystem: Running
LowPercInodesAvail 100 %
LowPercSpcAvail 100 %
FragmentedFileSystem 100 %
LowKAvail 100 %
SpaceUsed: Running
SpaceLow 100 %
SpaceHigh 100 %
DirNotExist 100 %
DMXProcess: Running
HighZombieProcesses 100 %
ProcessHighCPU 100 %
ProcessKilledOrNotExisting 100 %
548 Integrating IBM Tivoli Workload Scheduler with Tivoli Products
ProcessStopped 100 %
appavail-tws.pf#milan-region
DMXProcess: Running
HighZombieProcesses 100 %
ProcessHighCPU 100 %
ProcessKilledOrNotExisting 100 %
ProcessStopped 100 %
When an indication of a resource model reaches zero percent (0%) in this output,
the resource model has determined that a problem exists.
It is also possible to retrieve detailed information about a single resource model
on an endpoint, so that the parameter associated with an event or failing
resource model is displayed. Example 9-11 shows how we used the wdmlseng
command in the lab for this book to show the Process resource model at a
detailed level when the resource model showed the ProcessKilledOrNotExisting
indication has reached zero percent.
Example 9-11 Viewing detailed resource model status
milan:/# wdmlseng -e paris.itsc.austin.ibm.com \
-p 'appavail-tws.pf#milan-region' -r DMXProcess -verbose
Forwarding the request to the endpoint:
paris.itsc.austin.ibm.com 1187404249.8.522+#TMF_Endpoint::Endpoint#
The following profiles are running:
appavail-tws.pf#milan-region
DMXProcess: Running
HighZombieProcesses 100 %
ProcessHighCPU 100 %
ProcessKilledOrNotExisting 0 %
Keys = (name=basename=jobman;) 0 %
ProcessStopped 100 %
In this example, the resource model is reporting that the jobman process no
longer exists. Details on how to use the command line interface are in IBM Tivoli
Monitoring User’s Guide Version 5.1.2, SH19-4569.
Some environments have a notification server, or the staff have pagers that can
be sent pages via e-mail. In these environments, actions can be configured for
the application status resource models to automatically e-mail or notify staff
when any of the TWS processes are stopped. We briefly discuss actions in
9.8.18, “About configuring an action” on page 528.
Get Integrating IBM Tivoli Workload Scheduler with Tivoli Products now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
