Tivoli Tivoli Monitoring Applications:...

Tivoli® IBM Tivoli Monitoring for Applications: mySAP.com

Feature Pack 1 Documentation Supplement

Version 5.1.0, Feature Pack 1

SC32-9195-00

��

Note

Before using this information and the product it supports, read the information in “Notices,” on page 83.

First Edition (October 2004)

This edition applies to Feature Pack 1 of IBM Tivoli Monitoring for Applications: mySAP.com and to all subsequent

releases and modifications until otherwise indicated in new editions.

© Copyright International Business Machines Corporation 2004. All rights reserved.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract

with IBM Corp.

Contents

About this supplement . . . . . . . . v

Chapter 1. New features . . . . . . . . 1

Support for Linux for zSeries endpoints . . . . . 1

Monitoring short dump information . . . . . . 2

Event information . . . . . . . . . . . 3

Chapter 2. Work process resource

models . . . . . . . . . . . . . . . 5

mySAP Background Work Process Status . . . . . 7

mySAP Dialog Work Process Status . . . . . . 17

mySAP Enqueue Work Process Status . . . . . 26

mySAP Long Running Work Process . . . . . . 35

mySAP Spool Work Process Status . . . . . . . 42

mySAP Update Work Process Status . . . . . . 51

mySAP Update2 Work Process Status . . . . . . 61

Resource model indication attributes . . . . . . 70

Return codes . . . . . . . . . . . . . . 70

Status resource models logged information . . . . 72

Chapter 3. Tasks . . . . . . . . . . 75

Configure Event Adapter . . . . . . . . . . 76

Link JRE . . . . . . . . . . . . . . . 81

Appendix. Notices . . . . . . . . . . 83

Trademarks . . . . . . . . . . . . . . 84

Index . . . . . . . . . . . . . . . 85

© Copyright IBM Corp. 2004 iii

iv IBM Tivoli Monitoring for Applications: mySAP.com: Feature Pack 1 Documentation Supplement

About this supplement

This supplement documents the new features added to IBM® Tivoli® Monitoring

for Applications: mySAP.com in Feature Pack 1.

For information about applying this Feature Pack, see the README file that is

included with the Feature Pack.

The following books provide additional information about using IBM Tivoli

Monitoring for Applications: mySAP.com:

IBM Tivoli Monitoring for Applications, Version 5.1.0: mySAP.com User’s Guide,

SC23-4812

Provides information about how to manage mySAP.com systems with IBM

Tivoli Monitoring for Applications: mySAP.com. This guide also discusses

how to use tasks and resource models to monitor endpoints, and provides

information about the Tivoli Enterprise™ Data Warehouse reports shipped

with this product.

IBM Tivoli Monitoring for Applications, Version 5.1.0: mySAP.com Reference Guide,

SC23-4813

Provides detailed information about the tasks, resource models, and

commands provided by IBM Tivoli Monitoring for Applications:

mySAP.com.

IBM Tivoli Monitoring for Applications, Version 5.1.0: Installation and Setup Guide,

GC23-4810

Provides information about installing the IBM Tivoli Monitoring for

Applications product, including environment deployment and installation

troubleshooting information.

The full product library is available in the Tivoli Information Center.

© Copyright IBM Corp. 2004 v

vi IBM Tivoli Monitoring for Applications: mySAP.com: Feature Pack 1 Documentation Supplement

Chapter 1. New features

The following new features have been added to IBM Tivoli Monitoring for

Applications: mySAP.com:

v Support for Linux™ for zSeries endpoints

v Short dump monitoring

v Work process monitoring

This feature pack provides a fundamental restructuring of the data provider code

(code contained in the mySAPdp.jar and mySAPdpGate.jar files). These data

providers are required to run the resource models in this feature pack and to

obtain the new Linux for zSeries endpoint support. The data providers in this

feature pack are not compatible with the data providers in the base product, and

the two must never be intermixed. The restructured data providers are used on all

platforms.

When running this feature pack, you will see a new Java process running on the

endpoint. The new java process is the result of the data provider restructuring. The

data provider restructuring enables the IBM Tivoli Monitoring engine to run with

one Java™ Runtime Environment (JRE) version (such as 1.3.1) while the data

providers run a different JRE version (such as 1.4 or higher).

The restructured data provider code should be transparent to existing endpoint

operating systems (aix4-r1, hpux-10, solaris2, linux-ix86, w32-ix86). When the

feature pack is installed, the new data providers are deployed, and they use the

same JRE as the IBM Tivoli Monitoring engine.

The Linux for zSeries support and short dump monitoring are discussed in the

following sections in this chapter. Work process monitoring, which is provided by

seven new resource models, is discussed in Chapter 2, “Work process resource

models,” on page 5.

For more information about IBM Tivoli Monitoring for Applications: mySAP.com,

visit the technical information center, located at

http://publib.boulder.ibm.com/tividd/td/MonitoringforApplications5.1.html.

Support for Linux for zSeries endpoints

Feature Pack 1 adds support for Linux for zSeries endpoints. These Linux for

zSeries endpoints have the full range of functions as other endpoints; however

they require a different version of the Java Runtime Environment (JRE) than do

other endpoints (JRE version 1.4 or higher 64-bit instead of the JRE version 1.3.1 or

higher required by the IBM Tivoli Monitoring product). Because of this, IBM Tivoli

Monitoring for Applications: mySAP.com provides a task to link to the required

JRE.

Use the following steps to set up Linux for zSeries endpoints for monitoring:

1. Install a JRE version 1.3.1 or higher on the endpoint for IBM Tivoli Monitoring

use.

2. Run the DMLinkJRE task.

a. From the Tivoli Desktop, click Desktop �TMR Connections.

© Copyright IBM Corp. 2004 1

http://publib.boulder.ibm.com/tividd/td/MonitoringforApplications5.1.html

b. Click Top Level Policy Regions.

c. Double-click TivoliDefaultMw2kRegion to open this policy region.

d. Double-click IBM Tivoli Monitoring Tasks to open the task library.

e. Double-click DMLinkJre.

f. Select the endpoint or endpoints that you want to link to the Java software.

g. Click Execute to display the Configure Task Arguments dialog box.

h. Type the fully-qualified path to the top-level directory of the Java software.

For example, if the Java software is installed in the /usr/java/bin/java

directory path, type this value in the text field:

/usr/java

i. Click Set & Execute.3. Install a JRE version 1.4 or higher 64-bit version on the endpoint.

4. Discover or define the application servers for the endpoint. See the IBM Tivoli

Monitoring for Applications: mySAP.com User’s Guide for information.

5. Run the Link JRE task:

a. Open the mySAP Configuration Tasks task library.

b. Double-click Link JRE.

c. Select the endpoint or endpoints against which you want to run the task.

d. Click Execute.

e. Type the directory where JRE version 1.4 is installed in the Java Runtime

Environment Directory field.

f. Click Set & Execute to run the task.

Note: You must have r3_admin authorization to run this task.

6. Stop and restart the IBM Tivoli Monitoring engine by running the following

commands:

wdmcmd -e endpoint -restart

If you are not sure if a Linux for zSeries endpoint has been correctly linked to the

required JRE, run the Check Status task. This task has been updated to report this

new information.

Monitoring short dump information

Feature Pack 1 adds the ability to monitor when short dumps (also called ABAP

memory dumps) occur. Short dumps occur when an ABAP program fails. Short

dumps provide basic information about which program failed and what the error

was. The Syslog event adapter processes short dump information and calls a new

short dump analysis program, which converts the new entries into Tivoli

Enterprise Console events.

The new short dump monitoring provides the following capabilities:

v Report short dumps when the number of occurrences meet or exceed a threshold

v Generate different events for different error codes

v Generate different events for different users

v Configure event thresholds and severities to customize when events are

generated

v Escalate event reporting

2 IBM Tivoli Monitoring for Applications: mySAP.com: Feature Pack 1 Documentation Supplement

Short dump monitoring is disabled by default. Use the Configure Event Adapter

task to enable this monitoring. A new option, Enable Short Dumps, has been

added to the task interface. Click this option when you run the task. See the

“Configure Event Adapter” on page 76 for more information about this task.

You can customize how the short dump monitoring program reacts to specific

error codes by editing the associated wr3sdump.cl file. This is similar to modifying

how the Syslog event adapter responds to different syslog events, as described in

“Chapter 7, Using the Syslog event adapter” in the IBM Tivoli Monitoring for

Applications: mySAP.com User’s Guide.

To control how the monitoring reacts to error codes, you specify the specific error

code, the severity level for the error code, a minimum number of occurrences for

an error code during the monitoring cycle that triggers the event, and an optional

event class. Severity levels are expressed by encoded values, as shown in the

following table:

Value Corresponding event severity level

10 Unknown

20 Harmless

30 Warning

40 Minor

50 Critical

60 Fatal

For example:

<ABEND code> <severity> <occurrences> <event class>

DEFAULT 30 3

RFC_CONNECTION 40 2

MEMORY_SHORTAGE 50 1 SAP_ShortDump_MEMORY_SHORTAGE

With these settings, a SAP_ShortDump_Default warning event is generated when

three errors occur for errors other than RFC_CONNECTION and

MEMORY_SHORTAGE during the monitoring cycle. If two or more

RFC_CONNECTION errors occur, a minor event is generated under class

SAP_ShortDump_Default. If one or more MEMORY_SHORTAGE errors occurs, a

critical event is generated under class SAP_ShortDump_MEMORY_SHORTAGE.

Event information

IBM Tivoli Monitoring for Applications: mySAP.com provides two Tivoli Enterprise

Console event classes to represent the events processed from short dump

information:

v SAP_ShortDump

v SAP_ShortDump_Default

SAP_ShortDump is an intermediate class for all short dump leaf classes. This class

defines all the slot values shown below. This class also serves as the base class for

event rule processing.

SAP_ShortDump_Default is the default leaf class. It is a child of the

SAP_ShortDump class. It is the default class for all short dump events.

Chapter 1. New features 3

The short dump class files enable you to define your own classes for error

conditions. If you add new event classes to the short dump class file, you must

also define those event classes to the event server. It is recommended that you

name your new event classes using the format:

SAP_ShortDump_<error_code>

For example, to define an event class for the RFC_TIMEOUT error code, name the

event class SAP_ShortDump_RFC_TIMEOUT.

It is also recommended that you make your new event classes children of the

intermediate class SAP_ShortDump. This enables your new event classes to inherit

all the short dump event attributes, and it enables your new event classes to be

processed by the SAP_ShortDump rules.

The following table defines the event slots for the SAP_ShortDump class:

Table 1. Short dump monitoring event slots

Slot name Description

shortDumpDate Date of the first short dump with this error

code.

shortDumpTime Time of the first short dump with this error

code.

shortDumpCount Number of short dumps with this error code

during the monitoring cycle.

shortDumpThreshold Minimum number of occurrences of this

short dump with this error code that trigger

an event.

shortDumpUserName The mySAP user ID that is associated with

the short dump.

shortDumpClient The SAP client number under which this

short dump occurred.

shortDumpErrorCode The error code that triggered this event. This

information is also in the message slot.

shortDumpHost The host name of the host on which the

short dump occurred.


Chapter 2. Work process resource models

The following resource models have been added to IBM Tivoli Monitoring for

Applications: mySAP.com. These resource models monitor the status and

performance of SAP work processes.

v “mySAP Background Work Process Status” on page 7

v “mySAP Dialog Work Process Status” on page 17

v “mySAP Enqueue Work Process Status” on page 26

v “mySAP Long Running Work Process” on page 35

v “mySAP Spool Work Process Status” on page 42

v “mySAP Update Work Process Status” on page 51

v “mySAP Update2 Work Process Status” on page 61

Six of these resource models, the ″Status″ resource models, focus on monitoring the

number of work processes in each of four states: Running, Waiting, Stopped,

Completed. The monitoring is controlled with a user-specified threshold for each

state. The threshold can be specified as an absolute number (Count thresholds) or

as a percentage of the total work processes (Percent thresholds). This combination

of states and threshold options offers eight different monitoring conditions.

In addition to the eight basic states, the Status resource models monitor for two

additional conditions. They monitor growing queues of work, indicating that the

work processes are not keeping up with the demand. They monitor for program

failures in work processes, reporting the work processes that have more than a

specified number of program failures.

The six status resource models are essentially the same with respect to the types of

conditions to monitor and how they are configured. There are six resource models

to support the six different work process types: Background, Dialog, Enqueue,

Spool, Update, and Update2. You configure and deploy each resource model to

application servers running those particular work process types.

Note: Deploying a Status resource model to an application server that does not

run that type of work process will result in resource model stopped

conditions, denoted by error code 18.

While each Status resource model can monitor ten conditions, as noted above, you

can use the resource model parameters to fine tune the conditions to be monitored.

For example, you can deploy the Dialog resource model to monitor only Stopped

and Completed conditions.

The seventh work process resource model is the Long Running Work Process

resource model. This resource model is used to monitor for programs that are

running longer than expected. You configure this resource with a time threshold

for each of the six work process types: Background, Dialog, Enqueue, Spool,

Update, and Update2. When a long running program is detected, the event reports

the work process running the program and the name of the program that is

running too long.


Like the Status resource models, the Long Running Work Process resource model

also has a configurable parameter that allows you to fine tune the work processes

to be monitored for long running conditions. You do this by enabling only those

work process types you want monitored.

Note: Before you deploy these resource models in your environment, evaluate

your environment configuration. Deploying all of these resource models to

all endpoints might increase the IBM Tivoli Monitoring engine workload

and affect the overall performance of your environment. Consider

customizing the deployment of these resource models. For example, if you

have an endpoint with a high number of critical dialog work processes but

few spool work processes, deploy the Dialog Work Process Status resource

model to that endpoint, but not the Spool Work Process Status resource

model.

A new set of profiles have been added to the ″mySAP App Server Monitors″

profile manager, to provide a set of default work process resource model

configurations:

v mySAP Background Work Process Status

v mySAP Dialog Work Process Status

v mySAP Enqueue Work Process Status

v mySAP Long Running Work Process

v mySAP Spool Work Process Status

v mySAP Update Work Process Status (contains both the Update and Update2

resource models)

See the IBM Tivoli Monitoring for Applications: mySAP.com User’s Guide for

information about distributing these profiles.

The following information supplements the resource model documentation

provided by the IBM Tivoli Monitoring for Applications: mySAP.com Reference Guide.

For more information about resource models, including how to customize and

deploy them, see the IBM Tivoli Monitoring for Applications: mySAP.com User’s Guide.


mySAP Background Work Process Status

Description

Monitors background work processes on an SAP application server. Background

work processes run programs that can be executed without user interaction

(background jobs). This resource model monitors the count and percent values for

the different states of a background work process:

v Running

v Waiting

v Stopped

v Completed

The following properties are also monitored:

v Queue length (percentage)

v Failed programs

The following table shows the key characteristics of this resource model:

Resource model overview

Internal name mySAP_BackgroundWPStatus

Category mySAP

Indications Background Work Process Running

Background Work Process Running Percent

Background Work Process Stopped

Background Work Process Stopped Percent

Background Work Process Completed

Background Work Process Completed Percent

Background Work Process Waiting

Background Work Process Waiting Percent

Background Work Process Queue

Background Work Process Program Failures

Tasks and built-in actions None

Default cycle time 3 minutes (180 seconds)

Target managed resource

mySAPAppServer

Indications and events

The following table summarizes the indications for this resource model, the events

associated with the indications, the default severity of the events, and where to

find a detailed description of the indication.

Indication Generated event Default

severity

Clearing

events

“Background Work

Process Running

indication” on page 8

SAP_BackgroundWpRunning MINOR Yes

Chapter 2. Work process resource models 7


severity

Clearing

events

“Background Work

Process Running

Percent indication” on

page 9

SAP_BackgroundWpRunningPercent MINOR Yes

“Background Work

Process Stopped


SAP_BackgroundWpStopped CRITICAL Yes

“Background Work

Process Stopped Percent


SAP_BackgroundWpStoppedPercent CRITICAL Yes

“Background Work

Process Completed


SAP_BackgroundWpCompleted CRITICAL Yes

“Background Work

Process Completed

Percent indication” on

page 11

SAP_BackgroundWpCompletedPercent CRITICAL Yes

“Background Work

Process Waiting


SAP_BackgroundWpWaiting MINOR Yes

“Background Work

Process Waiting Percent


SAP_BackgroundWpWaitingPercent MINOR Yes

“Background Work

Process Queue


SAP_BackgroundWpQueue CRITICAL Yes

“Background Work

Process Program Failure


SAP_BackgroundWpProgramFailures CRITICAL Yes

Background Work Process Running indication

Occurs when the number of running background work processes is greater than or

equal to the Running threshold.

When the indication occurs often enough to trigger an event, the event delivers a

message to the Tivoli Enterprise Console in the following format:

Count exceeded: count=@wp_running@, threshold=@threshold@

See “Resource model indication attributes” on page 70 for the attributes of this

indication.

The following table describes the default settings for this indication.

Setting Default value

Send indications to Tivoli Enterprise Console Yes

Send indications to Tivoli Business Systems

Manager

No

Occurrences 5

Holes 0

Associated tasks and built-in actions None


Note: If you have Tivoli Business Systems Manager configured for your systems,

Tivoli Enterprise Console automatically forwards events to Tivoli Business

Systems Manager. Do not change the configuration of the indication to send

events to Tivoli Business Systems Manager.

Background Work Process Running Percent indication

Occurs when the number of running background work processes is greater than or

equal to the Running Percent threshold.



Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@


indication.





Manager

No

Occurrences 5

Holes 0






Background Work Process Stopped indication

Occurs when the number of stopped background work processes is greater than or

equal to the Stopped threshold.



Count exceeded: count=@wp_stopped@, threshold=@threshold@


indication.





Manager

No

Occurrences 2

Holes 0








Background Work Process Stopped Percent indication

Occurs when the percentage of stopped background work processes is greater than

or equal to the Stopped Percent threshold.





indication.





Manager

No

Occurrences 2

Holes 0






Background Work Process Completed indication

Occurs when the number of completed dialog work processes is greater than or

equal to the Completed threshold.



Count exceeded: count=@wp_completed@, threshold=@threshold@


indication.





Manager

No



Occurrences 2

Holes 0






Background Work Process Completed Percent indication

Occurs when the percentage of completed dialog work processes is greater than or

equal to the Completed Percent threshold.





indication.





Manager

No

Occurrences 2

Holes 0






Background Work Process Waiting indication

Occurs when the number of background work processes in the waiting state is less

than or equal to the Waiting threshold.



Count exceeded: count=@wp_waiting@, threshold=@threshold@


indication.







Manager

No

Occurrences 5

Holes 0






Background Work Process Waiting Percent indication

Occurs when the percentage of background work processes in the waiting state is

less than or equal to the Waiting Percent threshold.





indication.





Manager

No

Occurrences 5

Holes 0






Background Work Process Queue indication

Occurs when the number of background work items in the queue is greater than or

equal to the Queued Work threshold.



Count exceeded: count=@wp_queue_count@, threshold=@threshold@


indication.






Manager

No

Occurrences 5

Holes 0






Background Work Process Program Failure indication

Occurs when the number of background work process program failures is greater

than or equal to the Program Failure threshold.



Count exceeded: count=@wp_failures@, threshold=@threshold@, pid=@wp_pid@,

number=@wp_number@


indication.





Manager

No

Occurrences 1

Holes 0






Thresholds

The following table lists the thresholds that you can set for the resource model. For

each threshold it shows the name, a short description, and the default value:

Threshold name Description Default value

Running The maximum number of

running work processes

before an indication is

triggered.

5



Running Percent The maximum percentage of

work processes in the

running state at a given time


triggered.

95

Stopped The maximum number of

stopped work processes at a

given time before an

indication is triggered.

1

Stopped Percent The maximum percentage of


stopped state at a given time


triggered.

10

Completed The maximum number of

completed work processes at

a given time before an


1

Completed Percent The maximum percentage of


completed state at a given

time before an indication is

triggered.

10

Waiting The minimum number of

waiting work processes at a



0

Waiting Percent The minimum number of

waiting work processes at a



0

Queued Work The maximum number of

work items in the queue at a



2

Program Failures The maximum number of

program failures at a given


triggered..

1

Parameters

The following table lists the parameters that can be set for the Background work

process status resource model. The table shows the name, a short description, and

the default value for each parameter:


Parameter Description Default value

Work process

states to

monitor

Identifies the different work

process states for which to

monitor. If a value is set to

″True,″ that state is monitored.

Completed True

Completed Percent True

Program Failures True

Queue True

Running True

Running Percent True

Stopped True

Stopped Percent True

Waiting False

Waiting Percent False

Logging

See “Status resource models logged information” on page 72 for a list of the

properties that are logged for this resource model.

Return codes

See “Return codes” on page 70 for the return codes for this resource model.

CLI example

The following example uses the wdmeditprf command to add the mySAP

Background Work Status resource model to a profile:

wdmeditprf -P $PROFILE -add mySAP_BackgroundWPStatus -c 180 \

-Log -LogDisable -p 12:00 -Agg yes -ap 00:15 -NoMin -NoMax -Avg \

-t Thr_Queue_max 10.000000 \

-t Thr_Stopped_max 1.000000 \

-t Thr_Completed_max 1.000000 \

-t Thr_Waiting_min 0.000000 \

-t Thr_Stopped_Percent_max 10.000000 \

-t Thr_Running_Percent_max 95.000000 \

-t Thr_Waiting_Percent_min 0.000000 \

-t Thr_Running_max 5.000000 \

-t Thr_Completed_Percent_max 10.000000 \

-t Thr_Program_Failures_max 1.000000 \

-AddPar Par_State_eqs "running_percent" \

-AddPar Par_State_eqs "stopped_percent" \

-AddPar Par_State_eqs "completed_percent" \

-AddPar Par_State_eqs "running_count" \

-AddPar Par_State_eqs "stopped_count" \

-AddPar Par_State_eqs "completed_count" \

-AddPar Par_State_eqs "program_failures" \

-AddPar Par_State_eqs "queue" \

-e SAP_BackgroundWpWaiting \

-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \

-e SAP_BackgroundWpWaitingPercent \


-e SAP_BackgroundWpStoppedPercent \

-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \

-e SAP_BackgroundWpStopped \


-e SAP_BackgroundWpCompletedPercent \


-e SAP_BackgroundWpCompleted \


-e SAP_BackgroundWpRunning \


-e SAP_BackgroundWpQueue \


-e SAP_BackgroundWpRunningPercent \



-e SAP_BackgroundWpProgramFailures \

-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec


mySAP Dialog Work Process Status

Description

Monitors dialog work processes on an SAP application server. Dialog work

processes handle requests from a user to execute dialog steps. This resource model

monitors the count and percent values for the different states of the dialog work

process:

v Running

v Waiting

v Stopped

v Completed



v Failed programs



Internal name mySAP_DialogWPStatus

Category mySAP

Indications Dialog Work Process Running

Dialog Work Process Running Percent

Dialog Work Process Stopped

Dialog Work Process Stopped Percent

Dialog Work Process Completed

Dialog Work Process Completed Percent

Dialog Work Process Waiting

Dialog Work Process Waiting Percent

Dialog Work Process Queue

Dialog Work Process Program Failures




mySAPAppServer






severity

Clearing

events

“Dialog Work Process

Running indication” on

page 18

SAP_DialogWpRunning MINOR Yes



severity

Clearing

events


Running Percent


SAP_DialogWpRunningPercent MINOR Yes


Stopped indication” on

page 19

SAP_DialogWpStopped CRITICAL Yes


Stopped Percent


SAP_DialogWpStoppedPercent CRITICAL Yes


Completed indication”

on page 20

SAP_DialogWpCompleted CRITICAL Yes


Completed Percent


SAP_DialogWpCompletedPercent CRITICAL Yes


Waiting indication” on

page 21

SAP_DialogWpWaiting MINOR Yes


Waiting Percent


SAP_DialogWpWaitingPercent MINOR Yes


Queue indication” on

page 22

SAP_DialogWpQueuePercent CRITICAL Yes


Program Failure


SAP_DialogWpProgramFailures CRITICAL Yes

Dialog Work Process Running indication

Occurs when the number of running dialog work processes is greater than or equal

to the Running threshold.





indication.





Manager

No

Occurrences 5

Holes 0







Dialog Work Process Running Percent indication

Occurs when the percentage of running dialog work processes is greater than or






indication.





Manager

No

Occurrences 5

Holes 0






Dialog Work Process Stopped indication

Occurs when the number of stopped dialog work processes is greater than or equal

to the Stopped threshold.





indication.





Manager

No

Occurrences 2

Holes 0







Dialog Work Process Stopped Percent indication

Occurs when the percentage of stopped dialog work processes is greater than or

equal to the Stopped Percent threshold.





indication.





Manager

No

Occurrences 2

Holes 0






Dialog Work Process Completed indication

Occurs when the number of completed dialog work processes is greater than or






indication.





Manager

No

Occurrences 2

Holes 0







Dialog Work Process Completed Percent indication

Occurs when the percentage of completed dialog work processes is greater than or






indication.





Manager

No

Occurrences 2

Holes 0






Dialog Work Process Waiting indication

Occurs when the number of dialog work processes in the waiting state is less than

or equal to the Waiting threshold.





indication.





Manager

No

Occurrences 5

Holes 0







Dialog Work Process Waiting Percent indication

Occurs when the percentage of dialog work processes in the working state is less

than or equal to the Waiting Percent threshold.





indication.





Manager

No

Occurrences 5

Holes 0






Dialog Work Process Queue indication

Occurs when the percentage of dialog work queued is greater than or equal to the

Queued Work Percent threshold.



Percent exceeded: percent=@wp_queue_percent@, threshold=@threshold@


indication.





Manager

No

Occurrences 5

Holes 0







Dialog Work Process Program Failure indication

Occurs when the number of dialog work process program failures is greater than

or equal to the Program Failure threshold.




number=@wp_number@


indication.





Manager

No

Occurrences 1

Holes 0






Thresholds







triggered.

20



running state at a given time


triggered.

95


stopped work processes


triggered.

1





stopped state at a given time


triggered.

10


completed work processes


triggered.

1





triggered.

10


waiting work processes


triggered.

0

Waiting Percent The minimum number of



triggered.

0

Queued Work Percent The maximum percentage of

work processes in the queue

at a given time before an


2


program failures before an


1

Parameters

The following table lists the parameters that can be set for the Dialog work process

status resource model. The table shows the name, a short description, and the

default value for each parameter:


Work process

states to

monitor



monitor. If the value is set to

″True,″ the state is monitored.

Completed True



Queue True

Running True


Stopped True


Waiting False


Logging




Return codes


CLI example

The following example uses the wdmeditprf command to add the mySAP Dialog

Work Process Status resource model to a profile:

wdmeditprf -P $PROFILE -add mySAP_DialogWPStatus -c 180 \

-Log -LogDisable -p 03:00 -Agg no -ap 00:15 -NoMin -NoMax -Avg \




-t Thr_Queue_Percent_max 2.000000 \













-AddPar Par_State_eqs "queue_percent" \


-e SAP_DialogWpRunning \


-e SAP_DialogWpCompletedPercent \


-e SAP_DialogWpQueue \


-e SAP_DialogWpCompleted \


-e SAP_DialogWpProgramFailures \


-e SAP_DialogWpRunningPercent \


-e SAP_DialogWpStoppedPercent \


-e SAP_DialogWpWaitingPercent \


-e SAP_DialogWpWaiting \


-e SAP_DialogWpStopped \



mySAP Enqueue Work Process Status

Description

Monitors the enqueue work process on an SAP application server. The enqueue

work process administers a lock table in the shared memory area. The lock table

contains the logical database locks for the R/3 System and is an important part of

the SAP logical unit of work (LUW) concept. This resource model monitors the

count and percent values for the different states of an Enqueue work process:

v Running

v Waiting

v Stopped

v Completed



v Failed programs



Internal name mySAP_EnqueueWPStatus

Category mySAP

Indications Enqueue Work Process Running

Enqueue Work Process Running Percent

Enqueue Work Process Stopped

Enqueue Work Process Stopped Percent

Enqueue Work Process Completed

Enqueue Work Process Completed Percent

Enqueue Work Process Waiting

Enqueue Work Process Waiting Percent

Enqueue Work Process Queue

Enqueue Work Process Program Failures




mySAPAppServer







severity

Clearing

events

“Enqueue Work Process

Running indication”

SAP_EnqueueWpRunning MINOR Yes


Running Percent


SAP_EnqueueWpRunningPercent MINOR Yes



page 28

SAP_EnqueueWpStopped CRITICAL Yes


Stopped Percent


SAP_EnqueueWpStoppedPercent CRITICAL Yes



on page 29

SAP_EnqueueWpCompleted CRITICAL Yes


Completed Percent


SAP_EnqueueWpCompletedPercent CRITICAL Yes



page 30

SAP_EnqueueWpWaiting MINOR Yes


Waiting Percent


SAP_EnqueueWpWaitingPercent MINOR Yes



page 31

SAP_EnqueueWpQueuePercent CRITICAL Yes


Program Failure


SAP_EnqueueWpProgramFailures CRITICAL Yes

Enqueue Work Process Running indication

Occurs when the number of running enqueue work processes is greater than or






indication.





Manager

No

Occurrences 3

Holes 0








Enqueue Work Process Running Percent indication

Occurs when the percentage of running enqueue work processes is greater than or






indication.





Manager

No

Occurrences 3

Holes 0






Enqueue Work Process Stopped indication

Occurs when the number of stopped enqueue work processes is greater than or






indication.





Manager

No



Occurrences 2

Holes 0






Enqueue Work Process Stopped Percent indication

Occurs when the percentage of stopped enqueue work processes is greater than or






indication.





Manager

No

Occurrences 2

Holes 0






Enqueue Work Process Completed indication

Occurs when the number of completed enqueue work processes is greater than or






indication.







Manager

No

Occurrences 2

Holes 0






Enqueue Work Process Completed Percent indication

Occurs when the percentage of completed enqueue work processes is greater than

or equal to the Completed Percent threshold.





indication.





Manager

No

Occurrences 2

Holes 0






Enqueue Work Process Waiting indication

Occurs when the number of enqueue work processes in the waiting state is less






indication.






Manager

No

Occurrences 5

Holes 0






Enqueue Work Process Waiting Percent indication

Occurs when the percentage of enqueue work processes in the waiting state is less






indication.





Manager

No

Occurrences 5

Holes 0






Enqueue Work Process Queue indication

Occurs when the percentage of enqueue work queued is greater than or equal to

the Queued Work Percent threshold.





indication.






Manager

No

Occurrences 5

Holes 0






Enqueue Work Process Program Failure indication

Occurs when the number of enqueue work process program failures is greater than





number=@wp_number@


indication.





Manager

No

Occurrences 1

Holes 0






Thresholds







triggered.

2





running state before an


95




triggered.

1



stopped state before an


10




triggered.

1





triggered.

10




triggered.

0

Waiting Percent The minimum percentage of


waiting state at a given time


triggered.

0





2




1

Parameters

The following table lists the parameters that can be set for the Enqueue work





Work process

states to

monitor



monitor. If a value is set to


Completed True



Queue True

Running False

Running Percent False

Stopped True


Waiting False


Logging



Return codes


CLI example

The following example uses the wdmeditprf command to add the mySAP

Enqueue Work Process Status resource model to a profile:

wdmeditprf -P $PROFILE -add mySAP_EnqueueWPStatus -c 180 \


















-e SAP_EnqueueWpCompleted \


-e SAP_EnqueueWpWaiting \


-e SAP_EnqueueWpStopped \


-e SAP_EnqueueWpCompletedPercent \


-e SAP_EnqueueWpRunning \


-e SAP_EnqueueWpRunningPercent \


-e SAP_EnqueueWpProgramFailures \


-e SAP_EnqueueWpQueue \


-e SAP_EnqueueWpStoppedPercent \


-e SAP_EnqueueWpWaitingPercent \

-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec


mySAP Long Running Work Process

Description

Monitors the run time for a work processes on an SAP application server. The

following work processes are monitored:

v Background

v Dialog

v Enqueue

v Spool

v Update

v Update2

Thresholds are defined for each of the work processes.



Internal name mySAP_LongRunningWorkProcess

Category mySAP

Indications Background Work Process Run Time

Dialog Work Process Run Time

Enqueue Work Process Run Time

Spool Work Process Run Time

Update Work Process Run Time

Update2 Work Process Run Time




mySAPAppServer






severity

Clearing

events


Run Time indication”

on page 36

SAP_DialogWpRunTime MINOR Yes

“Background Work

Process Run Time


SAP_BackgroundWpRunTime MINOR Yes

“Update Work Process


on page 38

SAP_UpdateWpRunTime CRITICAL Yes



severity

Clearing

events

“Update2 Work Process


on page 38

SAP_Update2WpRunTime CRITICAL Yes

“Spool Work Process


on page 37

SAP_SpoolWpRunTime MINOR Yes



on page 37

SAP_EnqueueWpRunTime CRITICAL Yes

Background Work Process Run Time indication

Occurs when the run time for a background work process is greater than or equal

to the Background Elapsed Time threshold.



Run time exceeded: runtime=@wp_runtime@, threshold=@threshold@,

program=@wp_program@, pid=@wp_pid@, number=@wp_number@


indication.





Manager

No

Occurrences 1

Holes 0






Dialog Work Process Run Time indication

Occurs when the run time for a dialog work process is greater than or equal to

Dialog Elapsed Time threshold.






indication.






Manager

No

Occurrences 1

Holes 0






Enqueue Work Process Run Time indication

Occurs when the run time for an enqueue work process is greater than or equal to

the Enqueue Elapsed Time threshold.






indication.





Manager

No

Occurrences 1

Holes 0






Spool Work Process Run Time indication

Occurs when the run time for a spool work process is greater than or equal to the

Spool Elapsed Time threshold.







indication.





Manager

No

Occurrences 1

Holes 0






Update Work Process Run Time indication

Occurs when the run time for an update work process is greater than or equal to

the Update Elapsed Time threshold.






indication.





Manager

No

Occurrences 1

Holes 0






Update2 Work Process Run Time indication

Occurs when the run time for an update2 work process is greater than or equal to

the Update2 Elapsed Time threshold.







indication.





Manager

No

Occurrences 1

Holes 0






Thresholds




Dialog Elapsed Time The maximum amount of

time, in seconds, for the

dialog work process.

60

Background Elapsed Time The maximum amount of


background work process.

600

Update Elapsed Time The maximum amount of


update work process.

60

Update2 Elapsed Time The maximum amount of


update2 work process.

60

Spool Elapsed Time The maximum amount of


spool work process.

600

Enqueue Elapsed Time The maximum amount of


enqueue work process.

60

Parameters

The following table lists the parameters that can be set for the Long running work





Work process

types to

monitor


processes to monitor. If a

value is set to ″True,″ the

work process is monitored.

Background True

Dialog True

Enqueue True

Spool True

Update True

Update2 True

Logging

You can log data for the properties of the managed resource listed in the following

table. The table shows the context of the managed resource and the properties that

the resource model logs for the Web Health Console.

Managed resource Context Properties

mySAP_Long_Running_

Work_Process

Count

application_class

The class of the registered object.

application_label

The label of the registered object.

application_oid

The object identifier of the registered object.

application_version

The version of the mySAP software running on the

managed resource.

count_BGD

Count of all background long running work processes.

count_DIA

Count of all dialog long running work processes.

count_ENQ

Count of all enqueue long running work processes.

count_SPO

Count of all spool long running work processes.

count_UPD

Count of all update long running work processes.

count_UP2

Count of all update2 long running work processes.

process_type*

Indicates type for work process: background, dialog,

enqueue, spool, update, update2.

sub_origin*


sub_source

The label of the associated SAP system object.

Note: An asterisk (*) denotes a key property.

Return codes



CLI example

The following example uses the wdmeditprf command to add the mySAP Long

Run Work Process resource model to a profile:

wdmeditprf -P $PROFILE -add mySAP_LongRunningWorkProcess -c 180 \


-t Thr_Background_gt 600.000000 \

-t Thr_Spool_gt 600.000000 \

-t Thr_Enqueue_gt 60.000000 \

-t Thr_Update2_gt 60.000000 \

-t Thr_Dialog_gt 60.000000 \

-t Thr_Update_gt 60.000000 \

-AddPar Par_Type_eqs "DIA" \

-AddPar Par_Type_eqs "UPD" \

-AddPar Par_Type_eqs "UP2" \

-AddPar Par_Type_eqs "SPO" \

-AddPar Par_Type_eqs "ENQ" \

-AddPar Par_Type_eqs "BGD" \

-e SAP_EnqueueWpRunTime \


-e SAP_UpdateWpRunTime \


-e SAP_SpoolWpRunTime \


-e SAP_DialogWpRunTime \


-e SAP_BackgroundWpRunTime \


-e SAP_Update2WpRunTime \



mySAP Spool Work Process Status

Description

Monitors the spool work processes on an SAP application server. The spool work

processes pass sequential datasets to a printer or to optical archiving. Each

application server might contain only one spool work process. This resource model

monitors the count and percent values for the different states of a work process:

v Running

v Waiting

v Stopped

v Completed



v Failed programs



Internal name mySAP_SpoolWPStatus

Category mySAP

Indications Spool Work Process Running

Spool Work Process Running Percent

Spool Work Process Stopped

Spool Work Process Stopped Percent

Spool Work Process Completed

Spool Work Process Completed Percent

Spool Work Process Waiting

Spool Work Process Waiting Percent

Spool Work Process Queue

Spool Work Process Program Failures




mySAPAppServer






severity

Clearing

events



page 43

SAP_SpoolWpRunning MINOR Yes



severity

Clearing

events


Running Percent


SAP_SpoolWpRunningPercent MINOR Yes



page 44

SAP_SpoolWpStopped CRITICAL Yes


Stopped Percent


SAP_SpoolWpStoppedPercent CRITICAL Yes



on page 45

SAP_SpoolWpCompleted CRITICAL Yes


Completed Percent


SAP_SpoolWpCompletedPercent CRITICAL Yes



page 46

SAP_SpoolWpWaiting MINOR Yes


Waiting Percent


SAP_SpoolWpWaitingPercent MINOR Yes



page 47

SAP_SpoolWpQueue CRITICAL Yes


Program Failure


SAP_SpoolWpProgramFailures CRITICAL Yes

Spool Work Process Running indication

Occurs when the number of running spool work processes is greater than or equal

to the Running threshold.





indication.





Manager

No

Occurrences 3

Holes 0







Spool Work Process Running Percent indication

Occurs when the percentage of running spool work processes is greater than or






indication.





Manager

No

Occurrences 3

Holes 0






Spool Work Process Stopped indication

Occurs when the number of stopped spool work processes is greater than or equal

to the Stopped threshold.





indication.





Manager

No

Occurrences 2

Holes 0







Spool Work Process Stopped Percent indication

Occurs when the percentage of stopped spool work processes is greater than or






indication.





Manager

No

Occurrences 2

Holes 0






Spool Work Process Completed indication

Occurs when the number of completed spool work processes is greater than or






indication.





Manager

No

Occurrences 2

Holes 0







Spool Work Process Completed Percent indication

Occurs when the percentage of completed spool work processes is greater than or






indication.





Manager

No

Occurrences 2

Holes 0






Spool Work Process Waiting indication

Occurs when the number of spool work processes in the waiting state is less than






indication.





Manager

No

Occurrences 5

Holes 0







Spool Work Process Waiting Percent indication

Occurs when the percentage of spool work processes in the waiting state is less






indication.





Manager

No

Occurrences 5

Holes 0






Spool Work Process Queue indication

Occurs when the percentage of spool work queued is greater than or equal to the

Queued Work Percent threshold.





indication.





Manager

No

Occurrences 5

Holes 0







Spool Work Process Program Failure indication

Occurs when the number of spool work process program failures is greater than or

equal to the Program Failure threshold.




number=@wp_number@


indication.





Manager

No

Occurrences 1

Holes 0






Thresholds







triggered.

5





95




triggered.

1





10






triggered.

1





triggered.

10




triggered.

0





triggered.

0





80




1

Parameters

The following table lists the parameters that can be set for the Spool work process

status resource model. The table shows the name, a short description, and the

default value for each parameter:


Work Process

states to

monitor





Completed True



Queue True

Running True


Stopped True


Waiting False


Logging



Return codes



CLI example

The following example uses the wdmeditprf command to add the mySAP Spool


wdmeditprf -P $PROFILE -add mySAP_SpoolWPStatus -c 180 \




















-e SAP_SpoolWpCompleted \


-e SAP_SpoolWpQueue \


-e SAP_SpoolWpProgramFailures \


-e SAP_SpoolWpRunningPercent \


-e SAP_SpoolWpWaiting \


-e SAP_SpoolWpStopped \


-e SAP_SpoolWpStoppedPercent \


-e SAP_SpoolWpCompletedPercent \


-e SAP_SpoolWpWaitingPercent \


-e SAP_SpoolWpRunning \



mySAP Update Work Process Status

Description

Monitors update work processes on an SAP application server. Update work

processes run database update requests. Update requests are part of an SAP logical

unit of work (LUW) that bundles the database operations resulting from the dialog

in a database LUW for processing in the background. This resource model

monitors the count and percent values for the different states of a work process:

v Running

v Waiting

v Stopped

v Completed


v Queue time

v Failed programs



Internal name mySAP_UpdateWPStatus

Category mySAP

Indications Update Work Process Running

Update Work Process Running Percent

Update Work Process Stopped

Update Work Process Stopped Percent

Update Work Process Completed

Update Work Process Completed Percent

Update Work Process Waiting

Update Work Process Waiting Percent

Update Work Process Queue

Update Work Process Program Failures




mySAPAppServer







severity

Clearing

events


Running indication”

SAP_UpdateWpRunning MINOR Yes


Running Percent


SAP_UpdateWpRunningPercent MINOR Yes



page 53

SAP_UpdateWpStopped CRITICAL Yes


Stopped Percent


SAP_UpdateWpStoppedPercent CRITICAL Yes



on page 54

SAP_UpdateWpCompleted CRITICAL Yes


Completed Percent


SAP_UpdateWpCompletedPercent CRITICAL Yes



page 55

SAP_UpdateWpWaiting MINOR Yes


Waiting Percent


SAP_UpdateWpWaitingPercent MINOR Yes



page 56

SAP_UpdateWpQueue CRITICAL Yes


Program Failure


SAP_UpdateWpProgramFailures CRITICAL Yes

Update Work Process Running indication

Occurs when the number of running update work processes is greater than or






indication.





Manager

No

Occurrences 3

Holes 0








Update Work Process Running Percent indication

Occurs when the percentage of running update work processes is greater than or






indication.





Manager

No

Occurrences 3

Holes 0






Update Work Process Stopped indication

Occurs when the number of stopped update work processes is greater than or






indication.





Manager

No



Occurrences 2

Holes 0






Update Work Process Stopped Percent indication

Occurs when the percentage of stopped update work processes is greater than or






indication.





Manager

No

Occurrences 2

Holes 0






Update Work Process Completed indication

Occurs when the number of completed update work processes is greater than or






indication.







Manager

No

Occurrences 2

Holes 0






Update Work Process Completed Percent indication

Occurs when the percentage of completed update work processes is greater than or






indication.





Manager

No

Occurrences 2

Holes 0






Update Work Process Waiting indication

Occurs when the number of update work processes in the waiting state is less than






indication.






Manager

No

Occurrences 5

Holes 0






Update Work Process Waiting Percent indication

Occurs when the percentage of update work processes in the waiting state is less






indication.





Manager

No

Occurrences 5

Holes 0






Update Work Process Queue indication

Occurs when the queue time is greater than or equal to the Queued Work Time

threshold.



Time exceeded: time=@wp_queue_time@, threshold=@threshold@


indication.






Manager

No

Occurrences 5

Holes 0






Update Work Process Program Failure indication

Occurs when the number of update work process program failures is greater than





number=@wp_number@


indication.





Manager

No

Occurrences 1

Holes 0






Thresholds







triggered.

4







95




triggered.

1





10




triggered.

1





triggered.

10




triggered.

0





triggered.

0

Queued Work Time The maximum amount of

time a work process can be

in the queue before an


500




1

Parameters

The following table lists the parameters that can be set for the Update work





Work Process

states to

monitor





Completed True



Queue True

Running True


Stopped True


Waiting False


Logging



Return codes


CLI example

The following example uses the wdmeditprf command to add the mySAP Update


wdmeditprf -P $PROFILE -add mySAP_UpdateWPStatus -c 180 \


-t Thr_Queue_Time_max 500.000000 \

















-AddPar Par_State_eqs "queue_time" \

-e SAP_UpdateWpQueue \


-e SAP_UpdateWpRunningPercent \


-e SAP_UpdateWpWaiting \


-e SAP_UpdateWpStopped \


-e SAP_UpdateWpWaitingPercent \


-e SAP_UpdateWpStoppedPercent \


-e SAP_UpdateWpProgramFailures \


-e SAP_UpdateWpCompleted \


-e SAP_UpdateWpRunning \



-e SAP_UpdateWpCompletedPercent \



mySAP Update2 Work Process Status

Description

Monitors the update2 work process on an SAP application server. This resource

model monitors the count and percent values for the different states of an Update2

work process:

v Running

v Waiting

v Stopped

v Completed


v Queue time

v Failed programs



Internal name mySAP_Update2WPStatus

Category mySAP

Indications Update2 Work Process Running

Update2 Work Process Running Percent

Update2 Work Process Stopped

Update2 Work Process Stopped Percent

Update2 Work Process Completed

Update2 Work Process Completed Percent

Update2 Work Process Waiting

Update2 Work Process Waiting Percent

Update2 Work Process Queue

Update2 Work Process Program Failures




mySAPAppServer






severity

Clearing

events



page 62

SAP_Update2WpRunning MINOR Yes



severity

Clearing

events


Running Percent


SAP_Update2WpRunningPercent MINOR Yes



page 63

SAP_Update2WpStopped CRITICAL Yes


Stopped Percent


SAP_Update2WpStoppedPercent CRITICAL Yes



on page 64

SAP_Update2WpCompleted CRITICAL Yes


Completed Percent


SAP_Update2WpCompletedPercent CRITICAL Yes



page 65

SAP_Update2WpWaiting MINOR Yes


Waiting Percent


SAP_Update2WpWaitingPercent MINOR Yes



page 66

SAP_Update2WpQueue CRITICAL Yes


Program Failure


SAP_Update2WpProgramFailures CRITICAL Yes

Update2 Work Process Running indication

Occurs when the number of running update2 work processes is greater than or






indication.





Manager

No

Occurrences 3

Holes 0







Update2 Work Process Running Percent indication

Occurs when the percentage of running update2 work processes is greater than or






indication.





Manager

No

Occurrences 3

Holes 0






Update2 Work Process Stopped indication

Occurs when the number of stopped update2 work processes is greater than or






indication.





Manager

No

Occurrences 2

Holes 0







Update2 Work Process Stopped Percent indication

Occurs when the percentage of stopped update2 work processes is greater than or






indication.





Manager

No

Occurrences 2

Holes 0






Update2 Work Process Completed indication

Occurs when the number of completed update2 work processes is greater than or






indication.





Manager

No

Occurrences 2

Holes 0







Update2 Work Process Completed Percent indication

Occurs when the percentage of completed update2 work processes is greater than

or equal to the Completed Percent threshold.





indication.





Manager

No

Occurrences 2

Holes 0






Update2 Work Process Waiting indication

Occurs when the number of update2 work processes in the waiting state is less






indication.





Manager

No

Occurrences 5

Holes 0







Update2 Work Process Waiting Percent indication

Occurs when the percentage of update2 work processes in the waiting state is less






indication.





Manager

No

Occurrences 5

Holes 0






Update2 Work Process Queue indication

Occurs when the queue time is greater than or equal to the Queued Work Time

threshold.



Time exceeded: time=@wp_queue_time@, threshold=@threshold@


indication.





Manager

No

Occurrences 5

Holes 0







Update2 Work Process Program Failure indication

Occurs when the number of update2 work process program failures is greater than





number=@wp_number@


indication.





Manager

No

Occurrences 1

Holes 0






Thresholds







triggered.

4





95




triggered.

1





10






triggered.

1





triggered.

10




triggered.

0





triggered.

0

Queued Work Time The maximum amount of

time a work process can be

in the queue before an


500




1

Parameters

The following table lists the parameters that can be set for the Update2 work




Work process

states to

monitor





Completed True



Queue True

Running True


Stopped True


Waiting False


Logging



Return codes



CLI example

The following example uses the wdmeditprf command to add the mySAP Update2


wdmeditprf -P $PROFILE -add mySAP_Update2WPStatus -c 180 \


-t Thr_Queue_Time_max 500.000000 \

















-AddPar Par_State_eqs "queue_time" \

-e SAP_Update2WpStoppedPercent \


-e SAP_Update2WpWaitingPercent \


-e SAP_Update2WpWaiting \


-e SAP_Update2WpProgramFailures \


-e SAP_Update2WpStopped \


-e SAP_Update2WpCompletedPercent \


-e SAP_Update2WpQueue \


-e SAP_Update2WpCompleted \


-e SAP_Update2WpRunning \


-e SAP_Update2WpRunningPercent \



Resource model indication attributes

The indications for these resource model have some or all of the following

attributes:

application_class


application_label


application_oid


application_version

The version of the mySAP software running on the managed resource.

sub_origin


threshold

The threshold value used to trigger an indication.

wp_completed

Count of completed work processes.

wp_failures

Count of failing work processes.

wp_number

The process number for the work process.

wp_pid The process ID for the work process.

wp_queue_count

The number of work items in the queue.

wp_queue_percent

Queue length utilization (percent value).

wp_queue_time

The amount of time a work process spends in the queue.

wp_running

Count of running work processes.

wp_stopped

Count of stopped work processes.

wp_total

Count of all work processes of this type.

wp_waiting

Count of waiting work processes.

Return codes

Table 2 on page 71 contains a listing of resource model return codes, their

description, and actions for resolving each code. The return code number is

displayed in the IBM Tivoli Monitoring Web Health Console status field. You can

also display it using the wdmlseng command.


Table 2. Resource model return codes

Return

code

Logged

code

Description Action

01 401 There is a fatal error. The

resource model is unable to

start.

None. IBM Tivoli Monitoring will

try to run the resource model

every three minutes.

10 210 The resource model is unable

to start. Either the mySAP

function module is not

installed or you are using an

unsupported release of

mySAP.com.

Verify that the mySAP function

module is installed. Verify that

you are using a supported release

of mySAP.com.


to start. The resource model

is distributed to an

application server that is

remotely managed.

Distribute the resource model to a

locally managed application

server.


to start. The requested

attribute is unknown to the

data provider.

The request attribute is not

known to the data provider. IBM

Tivoli Monitoring will try to run

the resource model three times

during each monitoring cycle.



is not supported by the

operating system on which

the application server is

running.

Run the application server on a

supported operating system.



was distributed to an object

other than a

mySAPAppServer object.

Distribute the resource model to a

mySAPAppServer object.


to start. Attributes were

requested for a resource, but

an instance of that resource

cannot be found.

Contact IBM Software Support.


to start. The Monitoring Tree

Element representing these

attributes in CCMS has not

been configured.

Configure the Monitoring Tree

Element in CCMS to represent the

attributes.


to start.

A work process attribute was not

found. The application server

might not support the type of

work process that this resource

model monitors. IBM Tivoli

Monitoring will try to run the

resource model three times during

each monitoring cycle.


Table 2. Resource model return codes (continued)

Return

code

Logged

code

Description Action


to start. There is a Remote

Function Call error caused by

either an incorrect Remote

Function Call configuration

or network problems.

None. IBM Tivoli Monitoring will

try to run the resource model

three times during each cycle.


to start. The object context is

invalid.

The resource model cannot start.

The object context is invalid.


to start.

The resource model cannot start.

The data collector started in the

wrong Java Runtime Environment

(JRE) level. Run the Link JRE

task, directing the data collector

to the right JRE, and restart the

IBM Tivoli Monitoring engine.


to start. The object context is

not present. The resource

model may have been

distributed directly to an

endpoint.

Verify a valid object context.

Verify that the resource model

was distributed directly to an

endpoint.


to start. A syntax error was

detected while parsing the

parameters.

Check the parameter definitions.

Status resource models logged information

The following properties are logged for each status resource model (such as Dialog

Work Process Status):


Managed resource Context Properties

<resource_model> Count

application_class


application_label


application_oid


application_version

The version of the mySAP software running on the

managed resource.

process_state

The state of the work process.

sub_origin*


sub_source

The label of the associated SAP system object.

threshold

The threshold value used to trigger an event.

wp_completed

Count of completed work processes.

wp_error_sum

Sum of all error counts for this work process type.

wp_queue_count

The number of work items in the queue.

wp_queue_percent

Queue length utilization (percent value).

wp_queue_time

The amount of time a work process spends in the

queue.

wp_running

Count of running work processes.

wp_stopped

Count of stopped work processes.

wp_total

Count of all work processes of this type.

wp_waiting

Count of waiting work processes.

Note: An asterisk (*) denotes a key property.


Chapter 3. Tasks

The following tasks have been updated or added for this Feature Pack:

v “Configure Event Adapter” on page 76

v “Link JRE” on page 81

See the IBM Tivoli Monitoring for Applications: mySAP.com Reference Guide for more

detailed information about tasks.


Configure Event Adapter

Description

Configures the Syslog, CCMS, and IDOC event adapters.

The Configure Event Adapter task performs these actions:

v Creates a backup of the .conf file: TEC-app_server-type.conf.yyyy-mm-dd where

app_server-type is the name of the application server and type is Syslog, CCMS or

IDOC. Only one event adapter can be configured at a time, and the task creates

one backup per day.

v Updates the adapter .conf file: TEC-app_server-type.conf where app_server is the

name of the application server and type is Syslog, CCMS or IDOC.

v Stops and restarts the adapter if it is currently running.

Authorization role

r3_admin

Task library

v mySAP Configuration Tasks library

v mySAPAppServer icon: Monitoring→adapter→Configure

Note: When the task is run from the icon, the fields are already filled in.

Target endpoint

mySAPAppServer object

GUI data entry fields

This task has the following parameters:

Event Adapter Type

Check one of the following event adapters to configure:

v Syslog Adapter selects the Syslog Adapter for configuration.

v CCMS Adapter selects the CCMS Adapter for configuration.

v IDOC Adapter selects the IDOC Adapter for configuration.

Additional Information: You can configure only one adapter each time the

task is run. After selecting an adapter, the Adapter Unique Parameters

section of the dialog is refreshed to show the available parameters for the

selected adapter type.

Configuration File Source

Check one of the following options to choose how to update the

configuration file:

v Update Current File updates the current configuration file. When you

choose this option, all fields on the dialog are enabled for update. The

values that are shown on the dialog will replace values in the current

configuration file.

v Refresh From Template File replaces the current configuration file with

values from the adapter template file. When you choose this option, all

fields on the dialog are disabled. These values will be taken from the

template file.


Common Parameters

This section of the dialog lists parameters common to all adapter types.

Event Server

Type the name of the event server. The name must be of the form

@EventServer or @EventServer#region_name, where region_name is name of

an interconnected Tivoli region.

Polling Delay — Normal

The Normal polling delay specifies the length of time that the adapter

waits between polling cycles when the last cycle completed successfully.

Type a number greater than zero in the following fields:

v Minutes: Type a value from 0 to 10080.

v Seconds: Type a value from 0 to 3600.

Additional Information: The default polling delay settings for the event

adapters are:

v Syslog Adapter: 3 minutes

v CCMS Adapter: 10 minutes

v IDOC Adapter: 10 minutes

Polling Delay — RFC Error

The RFC Error polling delay specifies the length of time that the adapter

waits between polling cycles when the last cycle failed to complete

successfully because of RFC errors. The default polling delay setting is 60

minutes.

Type a number greater than zero in the following fields:

v Minutes: Type a value from 0 to 10080.

v Seconds: Type a value from 0 to 3600.

RFC Errors Until Shutdown

Type the maximum number of consecutive RFC errors permitted before the

adapter shuts down due to an unrecoverable RFC error condition. If you

enter 0, the adapter does not shut down in response to RFC errors.

Log File Size

Type the maximum size of the adapter log file in kilobytes (KB). The

number must be a positive integer.

Logging Levels

Select Trace and Error logging levels:

v Trace: Select one of the following levels of tracing information to be

logged:

– Low provides the least amount of operational detail.

—OR—

– Verbose provides the most operational detail. Select Verbose for

debugging purposes only.v Error: Select one of the following levels of error information to be

logged:

– Minor logs all errors.

– Major logs only major and fatal errors.

– Fatal logs only fatal errors.

Chapter 3. Tasks 77

RFC Timeout

The amount of time, in seconds, that the program waits for an RFC

response. If a response is not received within this time, the RFC call fails.

RFC Retry Count

The number of times that this RFC call will be retried after a failure. A

value of zero (0) indicates that no retries should be performed.

Note: The first RFC call is always attempted. This value controls only the

number of retry attempts after the first call fails.

RFC Retry Delay

The amount of time, in seconds, that the program waits before retrying a

failed RFC call. This parameter is used in conjunction with the RFC Retry

Count to provide a means for the program to successfully complete an

RFC call.

Adapter Unique Parameters

This section of the dialog lists parameters unique to each adapter type.

v Syslog Adapter:

Single Event Messages

Type the message IDs for the messages for which you only want one

event per polling cycle. Separate message IDs with spaces or commas,

for example:

AB1, AB8 A08

Additional Information: Selecting this option locally suppresses duplicate

syslog messages. Syslog messages are duplicates if they meet the

following conditions:

– The messages are processed in the same polling cycle of the adapter.

– The messages have identical values for the message ID and the

message text slots.

When the adapter is enabled for duplicate messages, an event will be

sent for the first occurrence of the message. No events will be sent for

subsequent duplicate messages. The adapter sends a single event for

these messages.

Enable short dumps

Click this option to enable the monitoring of short dump information.

See “Monitoring short dump information” on page 2 for more

information. Short dump monitoring available in Feature Pack 01.

CCMS Adapter

Alerts Per CCMS Attribute

Type the number of alerts to be reported as Tivoli events for each CCMS

attribute in the CCMS monitoring tree. Enter zero (0) to report all alerts.

Enter a number greater than zero to report that specified number of alerts.

Reported alerts are the most recent alerts for an attribute. Any alerts that

exceed this value are not reported as Tivoli events. You can configure the

CCMS Event Adapter to automatically close unreported alerts in CCMS.

See the description of the Close CCMS Alerts field.

Close CCMS Alerts

Check this box to configure the CCMS Adapter to automatically close

CCMS alerts. This option applies when the Alerts Per CCMS Attribute


number is greater than zero (0). All open CCMS alerts that exceed the

Alerts Per CCMS Attribute number will be closed.

Monitoring Set

Type the name of the CCMS monitoring set that contains the monitor you

want to observe. Type the name of the monitoring set exactly as it appears

in CCMS because this name is case sensitive. Here is an example of a

monitoring set name:

SAP CCMS Monitor Templates

Monitor

Type the name of the CCMS monitor contained in the specified monitoring

set. The CCMS Event Adapter reports alerts for all attributes in this

monitor. Type the monitor name exactly as it appears in CCMS because

this name is case sensitive. Here are examples of monitor names in the

SAP CCMS Monitor Templates monitoring set:

Background Processing

Buffers

Communications

Data Archiving

Database

Dialog Overview

Entire System

Operating System

Security

Spool System

Syslog

System Configuration

If you reconfigure the CCMS Event Adapter and you do not want to

change the name of the monitor to be observed, leave this field and the

Monitoring Set field blank.

CCMS Alert Mapping

This field is used to change the severity of events generated from CCMS

alerts. You have the following options:

Red Use the Red option to select a new event severity for CCMS red

alerts. The default value is CRITICAL.

Yellow

Use the Yellow option to select a new event severity for CCMS

yellow alerts. The default value is MINOR.

IDOC Adapter

Expiration Days

This field controls how long IDOC error conditions will be considered

valid. When an IDOC error condition is older than the number of days

specified in this field, the IDOC error will be dropped. Type the number of

days for which IDOC error conditions will considered valid. The number

must be an integer greater than or equal to zero.

Inbound Error Codes

IDOC error states are reported as two digit numbers. The meanings of the

error states are documented in SAP documentation. Use this field to

specify the set of IDOC inbound error states to be monitored. Type the

error codes as two-digit integers. Separate the error codes with commas.

Do not use spaces or blanks to separate the error codes.

Chapter 3. Tasks 79

Outbound Error Codes

IDOC error states are reported as two digit numbers. The meanings of the

error states are documented in SAP documentation. Use this field to

specify the set of IDOC outbound error states to be monitored. Type the

error codes as two-digit integers. Separate the error codes with commas.

Do not use spaces or blanks to separate the error codes.


Link JRE

Description

Links a Linux on zSeries endpoint to the required 1.4 or higher 64-bit version of

the Java Runtime Environment.

Authorization role

r3_admin

Task library

mySAP Configuration Tasks library

Target endpoint

mySAPAppServer object

GUI data entry fields

This task has the following parameters:

Java Runtime Environment Directory

Type the directory where JRE 1.4 is installed.

Chapter 3. Tasks 81

Appendix. Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in

other countries. Consult your local IBM representative for information on the

products and services currently available in your area. Any reference to an IBM

product, program, or service is not intended to state or imply that only that IBM

product, program, or service may be used. Any functionally equivalent product,

program, or service that does not infringe any IBM intellectual property right may

be used instead. However, it is the user’s responsibility to evaluate and verify the

operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter

described in this document. The furnishing of this document does not give you

any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation

North Castle Drive

Armonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM

Intellectual Property Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing

2-31 Roppongi 3-chome, Minato-ku

Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any other

country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS

PUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHER

EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED

WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS

FOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certain

transactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be

incorporated in new editions of the publication. IBM may make improvements

and/or changes in the product(s) and/or the program(s) described in this

publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for

convenience only and do not in any manner serve as an endorsement of those Web

sites. The materials at those Web sites are not part of the materials for this IBM

product and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way it

believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose

of enabling: (i) the exchange of information between independently created

programs and other programs (including this one) and (ii) the mutual use of the

information which has been exchanged, should contact:

IBM Corporation

2Z4A/101

11400 Burnet Road

Austin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,

including in some cases payment of a fee.

The licensed program described in this document and all licensed material

available for it are provided by IBM under terms of the IBM Customer Agreement,

IBM International Program License Agreement or any equivalent agreement

between us.

Trademarks

IBM, Tivoli, Tivoli Enterprise Console®, and zSeries® are trademarks or registered

trademarks of International Business Machines Corporation in the United States,

other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered

trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Linux is a trademark of Linus Torvalds in the United States, other countries, or

both.

Other company, product, and service names may be trademarks or service marks

of others.


Index

AABAP memory dumps 2

BBackground Work Process Completed

indication 10


Percent indication 11

Background Work Process Program

Failure indication 13


indication 12

Background Work Process Run Time

indication 36

Background Work Process Running

indication 8



Background work process status resource

model 7


indication 10



Background Work Process Program



indication 12


indication 8




indication 9




indication 11



parameters 14

thresholds 13


indication 9




indication 11



Cconfigure event adapter task 76

Configure Event Adapter task 3

customizing error monitoring 3

DDialog Work Process Completed

indication 20

Dialog Work Process Completed Percent

indication 21

Dialog Work Process Program Failure

indication 23


indication 22


indication 36

Dialog Work Process Running

indication 18


indication 19

Dialog work process status resource

model 17


indication 20



Dialog Work Process Program Failure

indication 23


indication 22

Dialog Work Process Running

indication 18


indication 19


indication 19


indication 20


indication 21


indication 22

parameters 24

thresholds 23


indication 19


indication 20


indication 21


indication 22

Eenabling short dump monitoring 3

endpoints 1


indication 29



Enqueue Work Process Program Failure

indication 32


indication 31


indication 37

Enqueue Work Process Running

indication 27

Enqueue Work Process Running Percent

indication 28

Enqueue work process status resource

model 26


indication 29



Enqueue Work Process Program



indication 31


indication 27




indication 28




indication 30



parameters 33

thresholds 32


indication 28

Enqueue Work Process Stopped Percent

indication 29


indication 30

Enqueue Work Process Waiting Percent

indication 31

error codes 3

JJRE version 1.4 1

Llibrary v

Link JRE task 1, 81

Linux for zSeries endpoints 1

Long Running work process status

resource model 35

Background Work Process Run Time

indication 36


indication 36


indication 37

logging 40

parameters 39


Long Running work process status

resource model (continued)Spool Work Process Run Time

indication 37

thresholds 39


indication 38


indication 38

Mmanuals v

monitoring short dumps 2

Nnew features 1

Linux for zSeries 1

short dump monitoring 2

work process resource models 5

Rresource models 5

Background work process status 7

Dialog work process status 17

Enqueue work process status 26

Long Running work process

status 35

return codes 71, 72

Spool work process status 42

Update work process status 51

Update2 work process status 61

return codesresource model 71, 72

Sshort dump monitoring

customizing 3

enabling 3

event classes 3

event slots 4

overview 2


indication 45

Spool Work Process Completed Percent

indication 46

Spool Work Process Percent Queue

indication 47

Spool Work Process Program Failure

indication 48

Spool Work Process Run Time

indication 37

Spool Work Process Running

indication 43


indication 44

Spool work process status resource

model 42

parameters 49


indication 45

Spool work process status resource

model (continued)Spool Work Process Completed


Spool Work Process Percent Queue

indication 47

Spool Work Process Program Failure

indication 48

Spool Work Process Running

indication 43


indication 44


indication 44


indication 45


indication 46


indication 47

thresholds 48


indication 44


indication 45


indication 46


indication 47

Ttask libraries

configuration tasksconfigure event adapter task 76

tasksconfigure event adapter 76

Link JRE 81

UUpdate Work Process Completed

indication 54

Update Work Process Completed Percent

indication 55

Update Work Process Program Failure

indication 57

Update Work Process Queue

indication 56


indication 38

Update Work Process Running

indication 52


indication 53

Update work process status resource

model 51

parameters 58

thresholds 57


indication 54



Update Work Process Program Failure

indication 57

Update work process status resource

model (continued)Update Work Process Queue

indication 56

Update Work Process Running

indication 52


indication 53


indication 53


indication 54


indication 55


indication 56


indication 53


indication 54


indication 55


indication 56


indication 64



Update2 Work Process Program Failure

indication 67


indication 66


indication 38

Update2 Work Process Running

indication 62

Update2 Work Process Running Percent

indication 63

Update2 work process status resource

model 61

parameters 68

thresholds 67


indication 64



Update2 Work Process Program



indication 66


indication 62




indication 63




indication 65




indication 63

Update2 Work Process Stopped Percent

indication 64



indication 65

Update2 Work Process Waiting Percent

indication 66

utility tasksconfigure event adapter task 76

Index 87

��

Printed in USA

SC32-9195-00

Tivoli Tivoli Monitoring Applications:...

Documents

Transcript of Tivoli Tivoli Monitoring Applications:...