Post on 04-Jun-2018
Tivoli® IBM Tivoli Monitoring for Applications: mySAP.com
Documentation Supplement for Feature Option 2
Version 5.1.0, Feature Option 2
SC32-9421-00
���
Tivoli® IBM Tivoli Monitoring for Applications: mySAP.com
Documentation Supplement for Feature Option 2
Version 5.1.0, Feature Option 2
SC32-9421-00
���
Note
Before using this information and the product it supports, read the information in Appendix B, “Notices,” on page 147.
Second Edition (March 2005)
This edition applies to Feature Option 2 of version 5, release 1, modification 0 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 2005. 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. Features and functions . . . 1
New functions . . . . . . . . . . . . . . 1
SAP BC-XAL certification . . . . . . . . . . 1
About SAP 6.40 . . . . . . . . . . . . . 1
ABAP instances . . . . . . . . . . . . 2
J2EE instances . . . . . . . . . . . . . 2
JMX server . . . . . . . . . . . . . . 3
Using new functions . . . . . . . . . . . . 3
Consistent event adapter parameters . . . . . 3
CCMS adapter event severity remapping . . . . 4
Viewing and completing CCMS alerts . . . . . 4
SAP release 6.40 support: ABAP instances . . . 4
SAP release 6.40 support: J2EE instances . . . . 5
Serviceability improvements . . . . . . . . 13
SAP 6.20 and 6.30 J2EE support . . . . . . . 14
Functions from Feature Pack 1 . . . . . . . . 14
Support for Linux for zSeries endpoints . . . . 15
Monitoring short dump information . . . . . 16
Chapter 2. Resource models . . . . . 19
Work process resource models overview . . . . . 19
JMX resource models overview . . . . . . . . 20
mySAP Background Work Process Status . . . . 24
mySAP Dialog Work Process Status . . . . . . 34
mySAP Enqueue Work Process Status . . . . . 43
mySAP JMX Application Thread Manager . . . . 52
mySAP JMX Cluster Manager . . . . . . . . 58
mySAP JMX Cluster Node Status . . . . . . . 65
mySAP JMX Configuration Manager . . . . . . 68
mySAP JMX Connections Manipulator Manager . . 71
mySAP JMX Generic Monitor . . . . . . . . 77
mySAP JMX Memory Info Service . . . . . . . 82
mySAP JMX System Thread Manager . . . . . . 85
mySAP Long Running Work Process . . . . . . 91
mySAP Spool Work Process Status . . . . . . . 98
mySAP Update Work Process Status . . . . . . 107
mySAP Update2 Work Process Status . . . . . 117
Indication attributes . . . . . . . . . . . 126
Attributes common to all Feature Option 2
resource models . . . . . . . . . . . 126
Attributes for work process resource model
indications . . . . . . . . . . . . . 126
Attributes for JMX resource model indications 127
Logged information for work process resource
models . . . . . . . . . . . . . . . 128
Return codes . . . . . . . . . . . . . 129
Chapter 3. Tasks . . . . . . . . . . 133
Check Status . . . . . . . . . . . . . 134
Configure Event Adapter . . . . . . . . . 135
Discover J2EE . . . . . . . . . . . . . 140
Link JRE . . . . . . . . . . . . . . . 141
Rediscover J2EE . . . . . . . . . . . . 142
Report Management Configuration . . . . . . 143
Appendix A. Monitoring data points
and values . . . . . . . . . . . . 145
Appendix B. Notices . . . . . . . . 147
Trademarks . . . . . . . . . . . . . . 148
Index . . . . . . . . . . . . . . . 149
© Copyright IBM Corp. 2005 iii
iv IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
About this supplement
This supplement documents the features added to IBM® Tivoli® Monitoring for
Applications: mySAP.com, Version 5.1.0 with Feature Option 2.
Feature Option 2 contains all of the functions from Feature Pack 1 and from Fix
Pack 05 and below.
For information about applying these updates, see the README file that is
included with the Feature Option.
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 at the Tivoli Information Center.
© Copyright IBM Corp. 2005 v
vi IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Chapter 1. Features and functions
This section describes the features added to IBM Tivoli Monitoring for
Applications: mySAP.com, Version 5.1.0 with Feature Option 2.
Feature Option 2 includes all Feature Pack 1 function and all maintenance through
Fix Pack 05. You can install Feature Option 2 on top of the following installations:
v Base product
v Base product with Feature Pack 1
v Base product with any fix pack up to and including Fix Pack 05
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.
New functions
Feature Option 2 provides the following capabilities in addition to Feature Pack 1:
v Consistent parameters for the event adapters
v Ability to remap CCMS adapter event severity based on CCMS alert level
v Ability to view and complete CCMS alerts. This function led to the product
being SAP BC-XAL certified.
v Support for 6.40 SAP Web Application Server
– ABAP based
– J2EE basedv Serviceability improvements for diagnosing and fixing Tivoli dependency set
problems
SAP BC-XAL certification
IBM Tivoli Monitoring for Applications: mySAP.com is certified by SAP according
to the SAP BC-XAL specification.
BC-XAL enables external system management software to read the properties and
values of monitoring attributes, as well as read and complete alerts. Through the
BC-XAL interface, the Computer Center Management System (CCMS) in SAP R/3
supports software vendors who integrate their products with existing SAP
administration tools.
Since IBM Tivoli Monitoring for Applications: mySAP.com is BC-XAL certified, it
meets SAP standards for external alert management.
About SAP 6.40
The functional capabilities of Feature Option 2 with respect to SAP 6.40 require an
understanding of the architectural changes introduced with SAP 6.40. This section
provides the background information that you need about SAP 6.40 to implement
the new SAP 6.40 monitoring capabilities.
© Copyright IBM Corp. 2005 1
ABAP instances
The traditional SAP system consisted of application servers, a database server, and
optional Internet transaction servers. These application servers are closely tied to
the ABAP language in the SAP system, and SAP monitoring and management
CCMS tools are implemented in ABAP in the SAP system. With the advent of SAP
6.40, SAP now refers to these traditional application servers as ABAP instances. For
consistency, Tivoli uses this same terminology when there is a need to distinguish
between ABAP and J2EE.
An SAP system consisted of a central instance application server, and optionally
one or more dialog instance application servers. Instances are named as
host_SID_number, for example, amsaix10_TV1_00. These same names are used
when representing these servers on the Tivoli desktop.
An ABAP instance is a complete entity containing a set of work processes (dialog,
batch, spool, update) that start and with the instance, and which share resources in
the instances. Since the characteristics of the ABAP instance are established at the
ABAP instance level, monitoring is performed at the instance level.
As ABAP based servers, external management is implemented using remote
function calls (RFC) to function modules or Business APIs (BAPIs) provided by
SAP.
J2EE instances
With SAP 6.40, SAP introduced a new type of application server instance. This
instance is built using Java™. It runs in a Java runtime environment. It has no
direct use of ABAP programs, but it provides the ability to invoke ABAP programs
as web applications. SAP refers to these new application servers as J2EE instances.
For consistency, Tivoli adopted the same terminology. The concept of an SAP
system has been expanded to include J2EE instances. An SAP system can now
consist of the following types of instances:
v ABAP instances only
v J2EE instances only
v Both ABAP and J2EE instances
When both ABAP and J2EE instances are installed on the same system, they share
a common database server.
Like ABAP instances, J2EE instances have central instances (called central services)
and Java instances. Like ABAP instances, the instances are named as
host_SID_number, for example, amsaix10_TV1_00. It is possible for an ABAP
instance and a J2EE instance to have the same name. They are distinguished in
SAP by their type. Again, these same names will be used on the Tivoli desktop,
but a new object type is introduced to distinguish them from ABAP instances.
J2EE instances can be managed at a more granular level than ABAP instances. The
work process functions are now implemented in J2EE cluster nodes. There can be
multiple cluster nodes in each J2EE instance. There is always a Dispatcher cluster
node and one or more Server cluster nodes in a J2EE instance.
J2EE cluster nodes can have different characteristics. Dispatchers are different from
servers. Memory and performance settings can be adjusted for individual cluster
nodes. Monitoring of J2EE resources is done at the J2EE cluster node level instead
of the J2EE instance level.
2 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
When there are multiple J2EE instances in an SAP system, SAP refers to the
combination of all J2EE instances as a J2EE cluster. Tivoli does not implement
monitoring at the cluster level.
JMX server
Monitoring of J2EE instances and cluster nodes is provided through Java
Management Extensions (JMX). SAP provides JMX APIs to monitor its J2EE
resources. Each J2EE instance has a monitoring agent called a JMX server. All J2EE
instances in a cluster are interconnected with their JMX servers. Hence, it is
possible to obtain information about any cluster node in the cluster by accessing
any JMX server in the cluster.
Tivoli uses the JMX APIs to obtain information about J2EE cluster nodes. This
information is used for discovery and real-time monitoring. You can configure the
Tivoli product to use different JMX servers for different J2EE instances.
Using new functions
This section provides detailed information about the functions available in Feature
Option 2.
Consistent event adapter parameters
The following three event adapters in the mySAP product have been updated:
v CCMS
v IDOC
v Syslog
To incorporate these updates, the installation script stops and restarts running
event adapters on your application servers. This restart process occurs when the
managed node hosting the endpoints is updated.
All three event adapters have the set of parameters in the following table.
Table 1. Parameters for the CCMS, IDOC, and Syslog event adapters
.conf parameter GUI label
ABH_MaxRFCErrors RFC Errors Until Shutdown
ABH_RetryCount RFC Retry Count
ABH_RetryDelay RFC Retry Delay
ABH_RFCErrorDelay Polling Delay - RFC Error Handling
ABH_RFCTimeout RFC Timeout
All event adapters now fully support all of the new configuration parameters, and
RFC error handling has been significantly enhanced and made consistent across the
event adapters.
The ability to control the sleep time in the CCMS adapter when RFC errors are
detected is now configurable using the Configure Event Adapter task. You use this
task to configure the parameter rather than manually editing the event adapter
.conf files.
Refer to “Configure Event Adapter” on page 135 or the online help for additional
information about this task and its parameters.
Chapter 1. Features and functions 3
CCMS adapter event severity remapping
This support includes the two new parameters in the table below for the CCMS
event adapter.
Table 2. Parameters for the CCMS event adapter
.conf parameter GUI label
ABH_AlertRed CCMS Alert Mapping / Red
ABH_AlertYellow CCMS Alert Mapping / Yellow
Refer to “Configure Event Adapter” on page 135 or the online help for additional
information about these parameters.
Viewing and completing CCMS alerts
IBM Tivoli Monitoring for Applications: mySAP.com Fix Pack 5 added the
following new functions and changes to the product:
v The Open option on the mySAPSystem icon has been expanded to have the
following two sub-options:
System
Opens the mySAPSystem policy region. This option replaces the
previous Open option.
CCMS
Opens a window showing the monitor sets defined in the SAP system.v The following option is available in the CCMS Monitor Sets window:
Get Monitors
Opens a window showing the monitors defined in the selected monitor
set.v The following options are available in the CCMS Monitors window:
Display Open Alerts
Opens a window showing the open alerts in the selected monitor.
Display Attributes
Opens a window showing monitoring tree elements and attributes in the
selected monitor.v The following options are available in the CCMS Alerts window:
Complete Alert
Completes the selected alert in the SAP system.
Show Status
Shows the status of the selected alert.
All other windows displayed through these new functions are output-only
windows and do not provide action options.
Note: The new functionality only works with SAP releases 4.6C, at Support
Package 28, and later.
Displaying monitor sets, monitors, and alerts might not work if these item names
contain the special characters carat (^) or backslash (\).
SAP release 6.40 support: ABAP instances
IBM Tivoli Monitoring for Applications: mySAP.com supports the SAP 6.40 ABAP
Web Application Server through the same functions, tasks, event adapters, and
4 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
resource models that are provided for earlier mySAP releases. These functions
continue to provide monitoring and management capabilities at the Web
Application Server level.
IBM Tivoli Monitoring for Applications: mySAP.com recognizes the following new
SAP applications:
v Supply Chain Management 4.0
v Supplier Relationship Management 2.0 and 3.0
v Business Warehouse 3.5
You can designate a mySAPSystem object as being one of these types. The desktop
icon will reflect the application type.
SAP release 6.40 support: J2EE instances
IBM Tivoli Monitoring for Applications: mySAP.com introduces many new
functions to support SAP J2EE instances. The goal of these new functions is to
provide you with the ability to monitor and manage at the J2EE cluster node level.
Support for J2EE instances includes the following new functions:
v “Resource models for J2EE cluster nodes”
v “J2EE objects and icons”
v Discovery tasks for “Creating J2EE objects” on page 9
Resource models for J2EE cluster nodes
The resource models were developed in collaboration with SAP to determine best
practices for the resources to be monitored. Design, capabilities, metrics, and
thresholds were reviewed and adopted for this product in cooperation with SAP.
The resources models are distributed to cluster nodes. There are different sets of
resource models for dispatcher nodes and server nodes.
Feature Option 2 provides the following new resource models to monitor the status
and performance of 6.40 Java-based Web Application Servers:
v “mySAP JMX Application Thread Manager” on page 52
v “mySAP JMX Cluster Manager” on page 58
v “mySAP JMX Cluster Node Status” on page 65
v “mySAP JMX Configuration Manager” on page 68
v “mySAP JMX Connections Manipulator Manager” on page 71
v “mySAP JMX Generic Monitor” on page 77
v “mySAP JMX Memory Info Service” on page 82
v “mySAP JMX System Thread Manager” on page 85
See “JMX resource models overview” on page 20 for more information about these
resource models.
J2EE objects and icons
Feature Option 2 provides the following two new object types to manage SAP J2EE
resources:
v mySAPJ2EEInstance
This object represents a J2EE instance. It is also a policy region. It is a member of
a mySAPSystem policy region.
v mySAPJ2EE ClusterNode
Chapter 1. Features and functions 5
This object represents a J2EE cluster node. It is a member of a
mySAPJ2EEInstance policy region.
These objects are represented on the Tivoli desktop with new icons. All J2EE icons
include a ″Java cup″ to represent their association with Java. There are two icons
for the mySAPJ2EEInstance object. One icon uses a star symbol to represent a
central instance. Another icon uses a window symbol to represent a Java instance.
Both icons provide the same set of menu functions.
J2EE instance objects are labeled using the ″SAP triplet″ format: host_SID_instance,
for example, amsaix10_TV1_00.
There is one icon for the mySAPJ2EEClusterNode object. It can represent both
dispatcher cluster nodes and server cluster nodes.
J2EE cluster node objects are labeled with an extension to the J2EE instance in
which they are members. The extension consists of the letter ″D″ for dispatcher
node or the letter ″S″ for server node, plus the node number. The node numbers
are assigned by SAP and start at 0 for both dispatchers and servers. Examples of
cluster node names in the amsaix_TV1_00 J2EE instance might be as follows:
v amsaix10_TV1_00_D0 represents a dispatcher node with number 0
v amsaix10_TV1_00_S5 represents a server node with number 5
The J2EE cluster node icon has the following four state variations:
No symbol
Cluster node is up and running
Red circle
Cluster node is down
Yellow triangle
Cluster node cannot be monitored due to a JMX configuration problem
Yellow diamond
Cluster node status cannot be accurately determined
The cluster node icon states are set by the mySAP JMX Cluster Node Status
resource model or by running the Check Status task.
J2EE icon menus
Both the J2EE instance and J2EE cluster node icons provide menu functions.
The J2EE instance icon provides the functions in Table 3.
Table 3. J2EE instance icon functions
Primary menu Lower menus Function
Operation Properties Shows characteristics of this
object
Verify JMX Checks the JMX connection
Open Opens the policy region to
show cluster nodes
Configuration Configure JMX Server Changes the JMX server and
port
Diagnostics Tivoli Logs � Endpoint Shows endpoint logs
6 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Table 3. J2EE instance icon functions (continued)
Primary menu Lower menus Function
Tivoli Logs � Callback Shows callback logs
The J2EE cluster node provides the functions in Table 4.
Table 4. J2EE cluster node icon functions
Primary menu Lower menus Function
Operation Properties Shows characteristics of this
object
Check Status Checks the status of the
cluster node
Configuration Reassign Endpoint Changes the Tivoli endpoint
on which resource models
run
Reestablish Endpoint Connects to a reinstalled
endpoint
Monitoring Profiles � Open Shows profiles distributed to
this cluster node
Diagnostics Tivoli Logs � Endpoint Shows endpoint logs
Tivoli Logs � Callback Shows callback logs
Dependencies � Check
Dependencies
Checks integrity of
dependency sets
Dependencies � Check/Fix
Dependencies
Checks integrity of
dependency sets and fixes
problems
Dependencies � Check
Endpoint Files
Compares file names listed
in dependency sets with files
installed on the endpoint
Dependencies � Push Files Pushes files associated with
the ″init″ method of this
object to the endpoint
Changes to existing icons
The product icon and the mySAPSystem icon have been modified to support new
J2EE functions.
The product icon has been modified as shown in Table 5:
Table 5. Product icon changes
Primary menu Lower menus Function
Discover (ABAP) Replaces the previous
Discover option. Used to
invoke the ABAP discovery
task
Discover (J2EE) Provides a new function for
discovering J2EE resources
Chapter 1. Features and functions 7
Table 5. Product icon changes (continued)
Primary menu Lower menus Function
Rediscover (ABAP) Replaces the previous
Rediscover option. Used to
invoke the ABAP rediscovery
task
Rediscover (J2EE) Provides a new function for
rediscovering J2EE resources
The mySAPSystem icon has been modified to include the menu items in Table 6:
Table 6. System icon changes
Primary menu Lower menus Function
Operation Verify JMX Checks the JMX connection
Configuration Configure JMX Provides means to specify
JMX configuration
parameters
New and changed tasks
The following list shows new or changed tasks in the mySAP Configuration Tasks
task library:
v “Check Status” on page 134
Changed task to support reporting of J2EE cluster nodes
v “Discover J2EE” on page 140
New task for discovering J2EE resources
v “Link JRE” on page 141
Changed task to support linking for JMX communication
v “Rediscover J2EE” on page 142
New task for rediscovering J2EE resources
v “Report Management Configuration” on page 143
Changed task to support reporting of J2EE resources
See Chapter 3, “Tasks,” on page 133 for more information about each of these
tasks.
New and changed profiles and profile managers
Feature Option 2 adds the following profile manager for monitoring J2EE cluster
nodes: mySAP J2EE Server Monitors.
Feature Option 2 adds the following profiles for monitoring J2EE cluster nodes,
which are in the mySAP J2EE Server Monitors profile manager:
v mySAP JMX Application Thread Manager
v mySAP JMX Cluster Manager
v mySAP JMX Cluster Node Status
v mySAP JMX Configuration Manager
v mySAP JMX Connections Manipulator Manager
v mySAP JMX Memory Info Service
v mySAP JMX System Thread Manager
8 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Creating J2EE objects
J2EE objects can be created using the Discover J2EE function or they can be created
manually.
To use the Discover J2EE function, invoke the function from the product icon or
run the Discover J2EE task. See “Discover J2EE” on page 140 for guidance in
completing this window. To create objects manually, use the Create option on the
appropriate policy region.
Creating a mySAP J2EE instance:
1. Double-click the mySAPSystem policy region icon to open the Policy Region
window.
2. Click Create � mySAPJ2EEInstance to display the Create mySAP J2EE Instance
window.
3. Complete the fields by providing the following information:
Instance Number
Two-digit numerical mySAP J2EE instance number
Instance Host Name
Host name on which this mySAP J2EE instance resides. The host name
cannot exceed 13 characters.
Central Instance
Yes or No, designates whether this object is a central instance4. Click Set and Execute.
Creating a mySAP J2EE cluster node:
1. Double-click the mySAPJ2EEInstance policy region icon to open the Policy
Region window.
2. Click Create � mySAPJ2EEClusterNode to display the Create mySAP J2EE
Cluster Node window.
3. Complete the fields by providing the following information:
Node Number
mySAP J2EE cluster node number. This value must consist of numbers
only and have a length of one, two, or three characters.
Cluster Node ID
Six to twelve digit cluster node identifier
Node Type
Type of cluster node: DISPATCHER or SERVER
Object Location
(Optional) Name of the managed node where you want this object to be
created. If this field is left blank, the Object Location of the associated
mySAPSystem object is used.
Tivoli Endpoint Name
(Optional) Name of the endpoint that you want to use to manage this
cluster node. The location of the endpoint determines how the cluster
node is managed:
v To manage the cluster node locally, use the name of an endpoint that
is installed on the same physical machine as the mySAP J2EE cluster
node.
Chapter 1. Features and functions 9
v To manage the system remotely, use the name of an endpoint that is
not installed on the same physical machine as the mySAP J2EE
cluster node.
v To have a suitable endpoint chosen automatically based on the
configuration of the associated mySAPSystem object, leave this field
blank.
Additional information:
v To verify the Tivoli endpoint name, use the following steps:
a. Right-click the Endpoint Manager icon on the desktop.
b. Select View � Gateways.v Terminology and general information
Physical Host Name
Name of the computer usually returned by the uname and
hostname commands
Managed Node Name
Managed resource that is running the Tivoli Framework.
Typically, this name is the name associated with the
computer’s network interface card (NIC) that Tivoli uses to
communicate with this computer.
Tivoli Endpoint Name
Managed resource that is running the Tivoli agent. Typically,
this name is the name assigned when the endpoint was
defined in the Tivoli region4. Click Set and Execute.
Configuring JMX connection information
JMX information is used for the following purposes:
v Running resource models to cluster nodes
v Running tasks to cluster nodes
v Running Discover J2EE and Rediscover J2EE tasks
If you have discovered your J2EE resources using the Discover J2EE function, JMX
server information is saved on the created or updated mySAPSystem object. You
only need to configure this JMX information if it has changed or if you want to use
different JMX servers.
If you manually created mySAPSystem objects, or if you have existing
mySAPSystem objects from ABAP discovery, then you must configure the JMX
parameters for these systems to monitor J2EE resources. Alternatively, you can use
the Discover J2EE function. If it finds J2EE resources for the SAP system, it creates
them in the appropriate SAP system and adds the JMX information to the SAP
system object.
You can configure JMX at both the system level and the J2EE instance level. You
must perform system level JMX configuration to ensure that a JMX user ID and
password is provided, and to provide a default JMX server and port.
You can perform J2EE instance level JMX configuration if you want to denote a
specific JMX server for use with cluster nodes in that J2EE instance.
The connection attributes configured for each mySAPJ2EEInstance are inherited
and used by the cluster node objects associated with it. When no
10 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
mySAPJ2EEInstance object connection information has been configured, the cluster
node object inherits the connection information from the associated mySAPSystem
object information.
Configuring mySAPSystem for JMX:
1. Right-click the mySAPSystem object icon that you want to configure.
2. Click Configure � Configure JMX to display the Configure JMX window.
3. Complete the fields using the following information:
JMX Server Information: The Host, Port, User ID, and Password fields
correspond to similar fields on the user configuration profile window of the
SAP J2EE Visual Administrator tool. Type the values that correspond to an
existing mySAP J2EE engine Administrator account.
Host Host name of the JMX server that reports information about the mySAP
J2EE instances. The host name can be simple name, fully qualified
name, or IP address.
Port Number of the port that the JMX Server uses. The port number must be
at least three numeric characters.
User ID
User ID to be used to connect to the JMX server. If you change the User
ID, you must enter a new Password.
Password
Password for the JMX User IDEndpoint Information: The Tivoli functions use endpoint information to locate
a Tivoli endpoint that is running a required version of the Java Runtime
Environment.
Endpoint Name
Endpoint to be used by the Tivoli functions. The endpoint must have
Java installed in the Java Runtime Environment Directory path.
Java Runtime Environment Directory
(Optional) Full path name to the Java installation directory (not
including the /bin directory). Use forward slashes only when entering
the path. Causes the configuration task to run the Link JRE task on the
endpoint.
On a Windows® operating system, if no drive is specified the
SystemDrive is used as a default.
Note: Access to the JMX server requires Java 1.4 or later.4. Click Set and Execute.
Configuring mySAPJ2EEInstance for JMX: This procedure configures the host
and port required to connect to a JMX server. Values provided for a J2EE instance
override the values defined at the SAP system level. This information is used when
running resource models against mySAP J2EE cluster node objects and to support
running selected tasks against mySAP J2EE instances and mySAP J2EE cluster
nodes.
If you reconfigure the host and port information, you must redistribute the
monitoring profiles to all mySAP J2EE cluster node objects in the affected mySAP
J2EE instance.
1. Right-click the mySAPJ2EEInstance object icon that you want to configure.
Chapter 1. Features and functions 11
2. Click Configure � Configure JMX Server to display the Configure JMX
window.
3. Complete the fields using the following information:
Host Host name of the JMX server that reports information about the SAP
J2EE instances. The hostname can be simple name, fully qualified
name, or IP address.
Port Number of the port that the JMX Server uses. The port number must be
at least three numeric characters.Additional information: The Tivoli functions use JMX server information to
connect to and communicate with a JMX server. The Host and Port fields in
this window correspond to similar fields in the user configuration profile
window of the SAP J2EE Visual Administrator tool. Use the values
corresponding to an existing mySAP J2EE engine Administrator account.
You can remove the host and port values at the J2EE instance level by
providing blank values for both the Host and Port fields. When these values
are not defined at the J2EE instance level, the values are obtained from the
associated SAP system object.
4. Click Set and Execute.
Compatibility
The methods of monitoring ABAP instances and J2EE instances are fundamentally
different. The resource models provided for ABAP instances do not work with
J2EE cluster nodes. Similarly, resource models provided for J2EE cluster nodes do
not work with ABAP instances. You must only distribute the resource models to
the object types for which they are designed.
The new object classes introduced with Feature Option 2 are only supported in the
Tivoli Framework environment. These object classes are not enabled for use with
Tivoli Business Systems Manager. This feature option does not provide support for
installing these classes on the Tivoli Business Systems Manager server. This feature
option does not generate Tivoli Business Systems Manager Discover and Gone
events for mySAPJ2EEInstance and mySAPJ2EEClusterNode objects.
IBM Tivoli Monitoring for Applications: mySAP.com continues to support Tivoli
Data Warehouse solely through the Data Collection Facility. No Tivoli Data
Warehouse support is provided for the resource models provided in this feature
option.
Prerequisite SAP maintenance levels
The J2EE monitoring and discovery capabilities provided with Feature Option 2 are
dependent on the following minimum SAP maintenance levels:
v Feature Option 2 SAP J2EE monitoring support is limited to systems that are at
SAP J2EE patch level (or higher) of the engine component at 6.40 SP8
(1000.6.40.8.0.20040907010533)
v Engine core component at 6.40 SP8 (1000.6.40.8.0.20040907010702)
v SAP J2EE kernel at least patched to 6.40 patch level 84589.313.
To verify your J2EE system patch level, log on to your J2EE instance at the
following Web site:
http://hostname:5xx00/sap/monitoringSystemInfo
(where xx is the instance id of the SAP J2EE system)
12 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
If the URL returns an error, it is likely that the system in question is not at the
patch level required.
Another option is to use the SAP Visual Administrator tool. Consult the following
Web site for information on configuring and using the SAP Visual Administrator:
http://help.sap.com/saphelp_erp2004/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm
Serviceability improvements
The Serviceability improvements for diagnosing dependency problems provides
new functions in the product. These changes are seen in the icon menus for the
mySAPAppServer, mySAPDBServer, mySAPITSServer, and
mySAPJ2EEClusterNode icons.
The Diagnostics menu option has been expanded to include a Dependencies
sub-option. The following Dependencies option includes the following
sub-options:
Check Definitions
Examines the defined dependency definitions (DependencyMgr instances).
This option provides a report that shows the validity of the following
dependencies:
v All expected mySAP dependencies
v ″run_task″ and ″init″ method dependencies
v mySAPJ2EEClusterNode discover method dependencies
v All dependencies
This option does not make any changes to your system.
Check/Fix Definitions
Provides the same report that is provided with the Check Definitions
option, but also attempts to fix as many problems as possible. This option
makes changes to your system. Run the Check Definitions function first
and save the report for comparison purposes.
Check Endpoint Files
Compares the list of files defined for the ″run_task″ and ″init″ methods to
the files on the endpoint. The comparison is done by file name only. This
option provides a report showing the following:
v Methods examined
v Files examined
v Location of files found
v Identification of files and the corresponding dependency set not found
on the endpoint
This option does not make any changes to your system.
Push Endpoint Files
Runs the ″init″ method to refresh files on the endpoint. The function runs
the dbcheck function on the gateway managing the endpoint to ensure
that the latest set of file definitions are stored in the gateway. The function
reports success or failure of the file push operation. This option does not
make any direct changes to your system, but it might refresh gateway file
definitions or push new files to your endpoint.
Chapter 1. Features and functions 13
The Configuration menu option has been expanded to include a Reestablish
Endpoint sub-option. If you have a situation in which an endpoint has been
deleted and reinstalled, use this option to reset the object information in the Tivoli
server. This option only works if the endpoint is reinstalled on the same computer
as the original endpoint. If you want to move the endpoint, use the existing
Reassign Endpoint function.
SAP 6.20 and 6.30 J2EE support
SAP introduced and evolved J2EE and JMX support with releases 6.20 and 6.30 as
follows:
v SAP releases 6.20 and 6.30 prior to Support Package 3 do not contain any
support for JMX. They cannot be monitored using Feature Option 2 JMX-based
resource models.
v SAP releases 6.20 and 6.30 with Support Packages 3 through 7 provided JMX
support. These support packages were pre-GA versions, so they are not
supported by IBM Tivoli Monitoring for Applications: mySAP.com.
v SAP releases 6.20 and 6.30 with Support Package 8 form SAP release 6.40. This
support level is a GA version. This level can be monitored using Feature Option
2 JMX-based resource models, as described in “Prerequisite SAP maintenance
levels” on page 12.
SAP releases 6.20 and 6.30 prior to Support Package 8 contained J2EE support even
though they did not contain JMX support. SAP provided monitoring of these
releases through its CCMS interface. SAP describes the implementation approach
for this in OSS note # 770694 ″Monitoring Java Instances with CCMS Monitoring.″
To monitor SAP 6.20 and 6.30 J2EE instances with IBM Tivoli Monitoring for
Applications: mySAP.com, you must do the following:
v Implement CCMS monitoring as described in OSS note # 770694.
v Install and configure the IBM Tivoli Monitoring for Applications: mySAP.com
CCMS event adapter to monitor alerts from the 6.20 or 6.30 SAP system. The
CCMS adapter must be configured to use a monitor set and monitor that
includes the J2EE monitoring tree elements in CCMS.
Functions from Feature Pack 1
Feature Option 2 contains the following Feature Pack 1 features:
v Support for Linux® for zSeries® endpoints
v Short dump monitoring
v Work process monitoring
Feature Pack 1 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 Feature Pack 1 and to obtain
the new Linux for zSeries endpoint support. The data providers in Feature Pack 1
are not compatible with the data providers in the base product, and the two must
never be mixed. The restructured data providers are used on all platforms.
When running Feature Pack 1, 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).
14 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
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 “Work process resource models
overview” on page 19.
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.
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:
Chapter 1. Features and functions 15
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
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 135 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
16 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
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 IBM 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.
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 7. 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.
Chapter 1. Features and functions 17
Table 7. Short dump monitoring event slots (continued)
Slot name Description
shortDumpHost The host name of the host on which the
short dump occurred.
18 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Chapter 2. Resource models
Feature Option 2 contains resource models that monitor SAP work processes and
6.40 Java-based Web Application Servers.
Work process resource models overview
The following work process resource models were added to IBM Tivoli Monitoring
for Applications: mySAP.com Feature Pack 1. These resource models monitor the
status and performance of SAP work processes:
v “mySAP Background Work Process Status” on page 24
v “mySAP Dialog Work Process Status” on page 34
v “mySAP Enqueue Work Process Status” on page 43
v “mySAP Long Running Work Process” on page 91
v “mySAP Spool Work Process Status” on page 98
v “mySAP Update Work Process Status” on page 107
v “mySAP Update2 Work Process Status” on page 117
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,
© Copyright IBM Corp. 2005 19
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 was 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.
JMX resource models overview
The following resource models were added to IBM Tivoli Monitoring for
Applications: mySAP.com Feature Option 2. These resource models monitor the
status and performance of 6.40 Java-based Web Application Servers in an SAP
environment:
v “mySAP JMX Application Thread Manager” on page 52
v “mySAP JMX Cluster Manager” on page 58
v “mySAP JMX Cluster Node Status” on page 65
v “mySAP JMX Configuration Manager” on page 68
v “mySAP JMX Connections Manipulator Manager” on page 71
v “mySAP JMX Generic Monitor” on page 77
v “mySAP JMX Memory Info Service” on page 82
v “mySAP JMX System Thread Manager” on page 85
20 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
The JMX resource models are used to monitor attributes in the dispatcher and
server J2EE cluster nodes. Deployment of these resource models requires some
understanding of the cluster node architecture.
Dispatcher and server cluster nodes contain components. Some of these
components exist in both types of cluster nodes and some exist in only one type of
cluster node. This allocation is summarized in Table 8.
Table 8. Cluster node components
Component Dispatcher Server
Application Thread Manager No Yes
Cluster Manager Yes Yes
Configuration Manager Yes Yes
Connections Manipulator
Manager
Yes No
Memory Info Service Yes Yes
(System) Thread Manager Yes Yes
There is a resource model corresponding to each type of cluster node component.
Each resource model allows you to monitor attributes unique to that component.
In addition, there is a resource model for monitoring cluster node status, and there
is a resource model provided as a tool to allow you to monitor attributes not
monitored by one of the resource models that is provided.
These resource models use monitoring data points and values suggested by SAP
for the SAP NetWeaver 04 J2EE engines. See Appendix A, “Monitoring data points
and values,” on page 145 for this information.
Monitoring with the JMX resource models involves the following three different
software components:
v Tivoli endpoint
JMX resource models run on the Tivoli endpoint. The resource models get
metrics from J2EE cluster nodes, compare metrics to thresholds, and raise
indications when potential problems are detected.
v JMX sever
JMX resource models get metrics about J2EE cluster nodes by querying a JMX
server. There is one JMX server in each J2EE instance. Since there can be
multiple J2EE instances in a cluster, there are multiple JMX servers that can
provide information about a cluster node.
v J2EE cluster node
JMX resource models monitor metrics from J2EE cluster nodes. The cluster nodes
maintain the information and make it available to external callers through the
JMX interface.
When deploying JMX resource models, it is important to check the component or
computer configurations to minimize network traffic between the components and
to minimize the risk of impaired monitoring functions if a computer is not
available. The following configurations are possible:
v Tivoli endpoint, JMX server, and J2EE cluster node all on the same computer
This configuration is likely to occur under the following conditions:
Chapter 2. Resource models 21
– You have one J2EE instance.
– You have a Tivoli endpoint installed on the J2EE instance computer.
– You have run the Discover J2EE function or you manually created J2EE
resources.
This configuration has no network traffic between the Tivoli endpoint and the
JMX server and no network traffic between the JMX server and the cluster
nodes. This is the best configuration to minimize network traffic between the
components.
v Tivoli endpoint and cluster node on the same computer; JMX server on a
different computer
This configuration is likely to occur under the following conditions:
– You have multiple J2EE instances.
– You have installed Tivoli endpoints on each J2EE instance computer.
– You have run the Discover J2EE function.
This configuration has network traffic between the Tivoli endpoint and JMX
server, and between the JMX server and the cluster node. To eliminate the
network traffic, you must, run the Configure JMX Server function to use the
JMX server on each J2EE instance computer.
v Tivoli endpoint and JMX server on one computer; cluster node on a different
computer
This configuration is likely to occur under the following conditions:
– You have multiple J2EE instances.
– You have a Tivoli endpoint installed on only one J2EE instance computer.
– You have run the Discover J2EE function.
The discover function finds all J2EE instances and cluster nodes in the cluster,
and assigns the same endpoint and JMX server for later monitoring.
This configuration has no network traffic between the Tivoli endpoint and the
JMX server, but there is network traffic between the JMX server and the cluster
nodes. There might also be additional processor utilization on the Tivoli
endpoint computer to run resource models for multiple cluster nodes.
To eliminate the network traffic, you must do the following:
– Install a Tivoli endpoint on each J2EE instance computer hosting the cluster
nodes being monitored.
– Run the Configure JMX Server function to use the JMX server on each J2EE
instance computer.v Tivoli endpoint on one computer; JMX server and cluster node on a different
computer
This configuration is likely to occur under the following conditions:
– You do not have a Tivoli endpoint installed on any J2EE instance computer.
– You have run the Discover J2EE function or manually created J2EE resources.
This configuration has network traffic between the Tivoli endpoint and JMX
server, but there is no network traffic between the JMX server and the cluster
nodes. There might also be additional processor utilization on the Tivoli
endpoint computer to run resource models for multiple cluster nodes.
To eliminate the network traffic, you must do the following:
– Install a Tivoli endpoint on each J2EE instance computer hosting the cluster
nodes being monitored.
– Run the Reassign Endpoint function for each cluster node to move the
management function to the new endpoint.
22 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
v Tivoli endpoint, JMX server, and cluster node all on different computers
This configuration is likely to occur under the following conditions:
– You have multiple J2EE instances.
– You do not have a Tivoli endpoint installed on the J2EE instance computers.
– You have run the Discover J2EE function.
This configuration has network traffic between the Tivoli endpoint and JMX
server, and between the JMX server and the cluster node.
To eliminate the network traffic, you must do the following:
– Install a Tivoli endpoint on each J2EE instance computer hosting the cluster
nodes being monitored.
– Run the Reassign Endpoint function for each cluster node to move the
management function to the new endpoint.
– Run the Configure JMX Server function to use the JMX server on the J2EE
instance computer.
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.
Chapter 2. Resource models 23
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 25
SAP_BackgroundWpRunning MINOR Yes
24 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Indication Generated event Default
severity
Clearing
events
“Background Work
Process Running
Percent indication” on
page 26
SAP_BackgroundWpRunningPercent MINOR Yes
“Background Work
Process Stopped
indication” on page 26
SAP_BackgroundWpStopped CRITICAL Yes
“Background Work
Process Stopped Percent
indication” on page 27
SAP_BackgroundWpStoppedPercent CRITICAL Yes
“Background Work
Process Completed
indication” on page 27
SAP_BackgroundWpCompleted CRITICAL Yes
“Background Work
Process Completed
Percent indication” on
page 28
SAP_BackgroundWpCompletedPercent CRITICAL Yes
“Background Work
Process Waiting
indication” on page 28
SAP_BackgroundWpWaiting MINOR Yes
“Background Work
Process Waiting Percent
indication” on page 29
SAP_BackgroundWpWaitingPercent MINOR Yes
“Background Work
Process Queue
indication” on page 29
SAP_BackgroundWpQueue CRITICAL Yes
“Background Work
Process Program Failure
indication” on page 30
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 IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_running@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Chapter 2. Resource models 25
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM 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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Background Work Process Stopped indication
Occurs when the number of stopped background work processes is greater than or
equal to the Stopped threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_stopped@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
26 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Setting Default value
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Background Work Process Completed indication
Occurs when the number of completed dialog work processes is greater than or
equal to the Completed threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_completed@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Chapter 2. Resource models 27
Setting Default value
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_waiting@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
28 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Setting Default value
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_queue_count@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
Chapter 2. Resource models 29
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_failures@, threshold=@threshold@, pid=@wp_pid@,
number=@wp_number@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
30 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
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
before an indication is
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
work processes in the
stopped state at a given time
before an indication is
triggered.
10
Completed The maximum number of
completed work processes at
a given time before an
indication is triggered.
1
Completed Percent The maximum percentage of
work processes in the
completed state at a given
time before an indication is
triggered.
10
Waiting The minimum number of
waiting work processes at a
given time before an
indication is triggered.
0
Waiting Percent The minimum number of
waiting work processes at a
given time before an
indication is triggered.
0
Queued Work The maximum number of
work items in the queue at a
given time before an
indication is triggered.
2
Program Failures The maximum number of
program failures at a given
time before an indication is
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.
Chapter 2. Resource models 31
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 “Logged information for work process resource models” on page 128 for a list
of the properties that are logged for this resource model.
Return codes
See “Return codes” on page 129 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 \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_BackgroundWpStoppedPercent \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_BackgroundWpStopped \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_BackgroundWpCompletedPercent \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_BackgroundWpCompleted \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_BackgroundWpRunning \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_BackgroundWpQueue \
-o 5 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_BackgroundWpRunningPercent \
32 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_BackgroundWpProgramFailures \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec
Chapter 2. Resource models 33
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
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_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
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
“Dialog Work Process
Running indication” on
page 35
SAP_DialogWpRunning MINOR Yes
34 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Indication Generated event Default
severity
Clearing
events
“Dialog Work Process
Running Percent
indication” on page 36
SAP_DialogWpRunningPercent MINOR Yes
“Dialog Work Process
Stopped indication” on
page 36
SAP_DialogWpStopped CRITICAL Yes
“Dialog Work Process
Stopped Percent
indication” on page 37
SAP_DialogWpStoppedPercent CRITICAL Yes
“Dialog Work Process
Completed indication”
on page 37
SAP_DialogWpCompleted CRITICAL Yes
“Dialog Work Process
Completed Percent
indication” on page 38
SAP_DialogWpCompletedPercent CRITICAL Yes
“Dialog Work Process
Waiting indication” on
page 38
SAP_DialogWpWaiting MINOR Yes
“Dialog Work Process
Waiting Percent
indication” on page 39
SAP_DialogWpWaitingPercent MINOR Yes
“Dialog Work Process
Queue indication” on
page 39
SAP_DialogWpQueuePercent CRITICAL Yes
“Dialog Work Process
Program Failure
indication” on page 40
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_running@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Chapter 2. Resource models 35
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Dialog Work Process Running Percent indication
Occurs when the percentage of running dialog work processes is greater than or
equal to the Running Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Dialog Work Process Stopped indication
Occurs when the number of stopped dialog work processes is greater than or equal
to the Stopped threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_stopped@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
36 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Dialog Work Process Completed indication
Occurs when the number of completed dialog work processes is greater than or
equal to the Completed threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_completed@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Chapter 2. Resource models 37
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Dialog Work Process Completed Percent indication
Occurs when the percentage of completed dialog work processes is greater than or
equal to the Completed Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_waiting@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
38 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Dialog Work Process Queue indication
Occurs when the percentage of dialog work queued is greater than or equal to the
Queued Work Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_queue_percent@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Chapter 2. Resource models 39
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_failures@, threshold=@threshold@, pid=@wp_pid@,
number=@wp_number@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
20
Running Percent The maximum percentage of
work processes in the
running state at a given time
before an indication is
triggered.
95
Stopped The maximum number of
stopped work processes
before an indication is
triggered.
1
40 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Threshold name Description Default value
Stopped Percent The maximum percentage of
work processes in the
stopped state at a given time
before an indication is
triggered.
10
Completed The maximum number of
completed work processes
before an indication is
triggered.
1
Completed Percent The maximum percentage of
work processes in the
completed state at a given
time before an indication is
triggered.
10
Waiting The minimum number of
waiting work processes
before an indication is
triggered.
0
Waiting Percent The minimum number of
waiting work processes
before an indication is
triggered.
0
Queued Work Percent The maximum percentage of
work processes in the queue
at a given time before an
indication is triggered.
2
Program Failures The maximum number of
program failures before an
indication is triggered.
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.
Parameter Description Default value
Work process
states to
monitor
Identifies the different work
process states for which to
monitor. If the value is set to
″True,″ the 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 “Logged information for work process resource models” on page 128 for a list
of the properties that are logged for this resource model.
Chapter 2. Resource models 41
Return codes
See “Return codes” on page 129 for the return codes for this resource model.
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_Completed_max 1.000000 \
-t Thr_Completed_Percent_max 10.000000 \
-t Thr_Program_Failures_max 1.000000 \
-t Thr_Queue_Percent_max 2.000000 \
-t Thr_Running_max 20.000000 \
-t Thr_Running_Percent_max 95.000000 \
-t Thr_Stopped_max 1.000000 \
-t Thr_Stopped_Percent_max 10.000000 \
-t Thr_Waiting_min 0.000000 \
-t Thr_Waiting_Percent_min 0.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 "queue_percent" \
-AddPar Par_State_eqs "program_failures" \
-e SAP_DialogWpRunning \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_DialogWpCompletedPercent \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_DialogWpQueue \
-o 5 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_DialogWpCompleted \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_DialogWpProgramFailures \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_DialogWpRunningPercent \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_DialogWpStoppedPercent \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_DialogWpWaitingPercent \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_DialogWpWaiting \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_DialogWpStopped \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec
42 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
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
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_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
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.
Chapter 2. Resource models 43
Indication Generated event Default
severity
Clearing
events
“Enqueue Work Process
Running indication”
SAP_EnqueueWpRunning MINOR Yes
“Enqueue Work Process
Running Percent
indication” on page 45
SAP_EnqueueWpRunningPercent MINOR Yes
“Enqueue Work Process
Stopped indication” on
page 45
SAP_EnqueueWpStopped CRITICAL Yes
“Enqueue Work Process
Stopped Percent
indication” on page 46
SAP_EnqueueWpStoppedPercent CRITICAL Yes
“Enqueue Work Process
Completed indication”
on page 46
SAP_EnqueueWpCompleted CRITICAL Yes
“Enqueue Work Process
Completed Percent
indication” on page 47
SAP_EnqueueWpCompletedPercent CRITICAL Yes
“Enqueue Work Process
Waiting indication” on
page 47
SAP_EnqueueWpWaiting MINOR Yes
“Enqueue Work Process
Waiting Percent
indication” on page 48
SAP_EnqueueWpWaitingPercent MINOR Yes
“Enqueue Work Process
Queue indication” on
page 48
SAP_EnqueueWpQueuePercent CRITICAL Yes
“Enqueue Work Process
Program Failure
indication” on page 49
SAP_EnqueueWpProgramFailures CRITICAL Yes
Enqueue Work Process Running indication
Occurs when the number of running enqueue 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 IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_running@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 3
Holes 0
44 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Setting Default value
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Enqueue Work Process Running Percent indication
Occurs when the percentage of running enqueue work processes is greater than or
equal to the Running Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 3
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Enqueue Work Process Stopped indication
Occurs when the number of stopped enqueue work processes is greater than or
equal to the Stopped threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_stopped@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Chapter 2. Resource models 45
Setting Default value
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Enqueue Work Process Stopped Percent indication
Occurs when the percentage of stopped enqueue work processes is greater than or
equal to the Stopped Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Enqueue Work Process Completed indication
Occurs when the number of completed enqueue work processes is greater than or
equal to the Completed threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_completed@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
46 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Setting Default value
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Enqueue Work Process Waiting indication
Occurs when the number of enqueue work processes in the waiting state is less
than or equal to the Waiting threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_waiting@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
Chapter 2. Resource models 47
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Enqueue Work Process Waiting Percent indication
Occurs when the percentage of enqueue work processes in the waiting state is less
than or equal to the Waiting Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Enqueue Work Process Queue indication
Occurs when the percentage of enqueue work queued is greater than or equal to
the Queued Work Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_queue_percent@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
48 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Enqueue Work Process Program Failure indication
Occurs when the number of enqueue work process program failures is greater than
or equal to the Program Failure threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_failures@, threshold=@threshold@, pid=@wp_pid@,
number=@wp_number@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
Chapter 2. Resource models 49
Threshold name Description Default value
Running The maximum number of
running work processes
before an indication is
triggered.
2
Running Percent The maximum percentage of
work processes in the
running state before an
indication is triggered.
95
Stopped The maximum number of
stopped work processes
before an indication is
triggered.
1
Stopped Percent The maximum percentage of
work processes in the
stopped state before an
indication is triggered.
10
Completed The maximum number of
completed work processes
before an indication is
triggered.
1
Completed Percent The maximum percentage of
work processes in the
completed state at a given
time before an indication is
triggered.
10
Waiting The minimum number of
waiting work processes
before an indication is
triggered.
0
Waiting Percent The minimum percentage of
work processes in the
waiting state at a given time
before an indication is
triggered.
0
Queued Work Percent The maximum percentage of
work processes in the queue
at a given time before an
indication is triggered.
2
Program Failures The maximum number of
program failures before an
indication is triggered.
1
Parameters
The following table lists the parameters that can be set for the Enqueue Work
Process Status resource model. The table shows the name, a short description, and
the default value for each parameter.
50 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
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,″ the state is monitored.
Completed True
Completed Percent True
Program Failures True
Queue True
Running False
Running Percent False
Stopped True
Stopped Percent True
Waiting False
Waiting Percent False
Logging
See “Logged information for work process resource models” on page 128 for a list
of the properties that are logged for this resource model.
Return codes
See “Return codes” on page 129 for the return codes for this resource model.
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 \
-Log -LogDisable -p 12:00 -Agg yes -ap 00:15 -NoMin -NoMax -Avg \
-t Thr_Stopped_max 1.000000 \
-t Thr_Completed_max 1.000000 \
-t Thr_Waiting_min 0.000000 \
-t Thr_Queue_Percent_max 2.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 2.000000 \
-t Thr_Completed_Percent_max 10.000000 \
-t Thr_Program_Failures_max 1.000000 \
-AddPar Par_State_eqs "stopped_percent" \
-AddPar Par_State_eqs "completed_percent" \
-AddPar Par_State_eqs "stopped_count" \
-AddPar Par_State_eqs "completed_count" \
-AddPar Par_State_eqs "queue_percent" \
-AddPar Par_State_eqs "program_failures" \
-e SAP_EnqueueWpCompleted \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_EnqueueWpWaiting \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_EnqueueWpStopped \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_EnqueueWpCompletedPercent \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_EnqueueWpRunning \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_EnqueueWpRunningPercent \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_EnqueueWpProgramFailures \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_EnqueueWpQueue \
-o 5 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_EnqueueWpStoppedPercent \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_EnqueueWpWaitingPercent \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec
Chapter 2. Resource models 51
mySAP JMX Application Thread Manager
Description
Monitors the mySAP JMX Application Thread Manager. The Application Thread
Manager is a component of server cluster nodes. The thread manager allocates
threads for the processing of user and application work requests. If all threads are
allocated to work requests, new work requests are delayed in their processing.
This resource model monitors the mySAP J2EE Application Thread Manager to
allow timely detection of thread overuse and delayed work requests. The resource
model provides monitoring of the following items:
v Percent of threads in use
v Number of requests, in the request queue, waiting for a thread
v Number of requests, not in the request queue, waiting to be added to the
request queue
v Total number of requests that can be stored in the request queue
The following table shows the key characteristics of this resource model.
Resource model overview
Internal name mySAP_JMXApplicationThreadManager
Category mySAP
Indications Usage Percent
Waiting Tasks Count
Waiting Tasks Queue Overflow
Waiting Tasks Queue Size
Tasks and built-in actions None
Default cycle time 3 minutes (180 seconds)
Target managed resource
mySAPJ2EEClusterNode, node type = Server
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
“Usage Percent
indication” on page 53
SAP_JMX_Application_Thread_Usage_Percent CRITICAL Yes
“Waiting Tasks Count
indication” on page 53
SAP_JMX_Application_Thread_Waiting_Tasks_Count CRITICAL Yes
“Waiting Tasks Queue
Overflow indication” on
page 54
SAP_JMX_Application_Thread_Waiting_Tasks
_Queue_Overflow
CRITICAL Yes
“Waiting Tasks Queue
Size indication” on page
54
SAP_JMX_Application_Thread_Waiting_Tasks_Queue_Size CRITICAL Yes
52 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Usage Percent indication
Occurs when the percent of used application threads is equal to or greater than the
Usage Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Usage: percent=@usage_percent@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Waiting Tasks Count indication
Occurs when the count of waiting tasks is equal to or greater than the Waiting
Tasks Count threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Waiting Tasks: count=@waiting_tasks_count@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
Chapter 2. Resource models 53
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Waiting Tasks Queue Overflow indication
Occurs when the count of waiting tasks queue overflow is equal to or greater than
the Waiting Tasks Queue Overflow threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Waiting Tasks Queue Overflow: count=@waiting_tasks_queue_overflow@
(threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Waiting Tasks Queue Size indication
Occurs when the waiting tasks queue size is equal to or greater than the Waiting
Tasks Queue Size threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Waiting Tasks Queue Size: count=@waiting_tasks_queue_size@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
54 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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
Usage Percent The threshold value against which
the percent of used threads is
compared. This threshold is exceeded
if the current value is equal to or
greater than this value.
100
Waiting Tasks Count The threshold value against which
the count of waiting tasks is
compared. This threshold is exceeded
if the current value is equal to or
greater than this value.
600
Waiting Tasks Queue Overflow The threshold value against which
the count of waiting tasks queue
overflow is compared. This threshold
is exceeded if the current value is
equal to or greater than this value.
100
Waiting Tasks Queue Size The threshold value against which
the count of waiting tasks queue size
is compared. This threshold is
exceeded if the current value is equal
to or greater than this value.
1000
Parameters
None
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 IBM Tivoli Monitoring Web Health Console.
Chapter 2. Resource models 55
Managed resource Context Properties
mySAP_JMX_Application_
Thread
Thread
application_class
Class of the registered object
application_label
Label of the registered object
application_oid
Object identifier of the registered object
application_version
Version of the mySAP software running on the
managed resource
sub_origin*
Label of the registered object
sub_source
Label of the associated SAP system object
usage_percent
Current usage of the thread pool, in percent
waiting_tasks_count
Number of runnable tasks waiting for available thread
from the thread pool to be executed
waiting_tasks_queue_overflow
Number of threads waiting to deposit a runnable task
in the request queue if it is full
waiting_tasks_queue_size
Capacity of the request queue where the tasks waiting
for execution are stored
threshold_usage_percent
Threshold value for comparison against the
usage_percent attribute
threshold_waiting_tasks_count
Threshold value for comparison against the
waiting_tasks_count attribute
threshold_waiting_tasks_queue_overflow
Threshold value for comparison against the
waiting_tasks_queue_overflow attribute
threshold_waiting_tasks_queue_size
Threshold value for comparison against the
waiting_tasks_queue_size attribute
Note: An asterisk (*) denotes a key property.
Return codes
See Table 9 on page 130 for the return codes for this resource model.
CLI example
The following example uses the wdmeditprf command to add the mySAP JMX
Application Thread Manager resource model to a profile:
wdmeditprf -P $PROFILE -add mySAP_JMXApplicationThreadManager -c 180 \
-Log -LogDisable -p 12:00 -Agg no -ap 00:15 -NoMin -NoMax -Avg \
-t Thr_JMX_Usage_Percent_gt 100.000000 \
-t Thr_JMX_Waiting_Tasks_Count_gt 600.000000 \
56 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
-t Thr_JMX_Waiting_Tasks_Queue_Overflow_gt 100.000000 \
-t Thr_JMX_Waiting_Tasks_Queue_Size_gt 1000.000000 \
-e SAP_JMX_Application_Thread_Waiting_Tasks_Queue_Overflow \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_JMX_Application_Thread_Waiting_Tasks_Queue_Size \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_JMX_Application_Thread_Usage_Percent \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_JMX_Application_Thread_Waiting_Tasks_Count \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec
Chapter 2. Resource models 57
mySAP JMX Cluster Manager
Description
Monitors the mySAP JMX Cluster Manager. The Cluster Manager is a component
of dispatcher and server cluster nodes. The cluster manager is responsible for
managing the communication between the elements in the cluster. It updates
information about the status of each cluster element and the services running on it.
This resource model monitors the mySAP J2EE Cluster Manager to detect excessive
session communication times and queue-full conditions for any of the five
supported session protocols. The resource model provides monitoring of the
following items:
v Average session process time
v Number of items in work queue for the following session protocols:
– Telnet
– HTTP
– JMS
– P4
– Web services
You must validate the thresholds used in this resource model for use in your
environment. Run the resource model for a couple of days to identify the optimum
thresholds for your environment. Then, adjust the threshold values.
The following table shows the key characteristics of this resource model.
Resource model overview
Internal name mySAP_JMXClusterManager
Category mySAP
Indications Telnet Session Queue Size
Average Session Process Time
Webservices Session Queue Size
P4 Session Queue Size
JMS Session Queue Size
HTTP Session Queue Size
Tasks and built-in actions None
Default cycle time 3 minutes (180 seconds)
Target managed resource
mySAPJ2EEClusterNode, node type = Dispatcher or Server
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.
58 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Indication Generated event Default
severity
Clearing
events
“Telnet Session Queue
Size indication”
SAP_JMX_Cluster_Manager_Telnet_Queue_Size CRITICAL Yes
“Average Session
Process Time
indication”
SAP_JMX_Cluster_Manager_Process_Time CRITICAL Yes
“Webservices Session
Queue Size indication”
on page 60
SAP_JMX_Cluster_Manager_Webservices_Queue_Size CRITICAL Yes
“P4 Session Queue Size
indication” on page 60
SAP_JMX_Cluster_Manager_P4_Queue_Size CRITICAL Yes
“JMS Session Queue
Size indication” on page
61
SAP_JMX_Cluster_Manager_JMS_Queue_Size CRITICAL Yes
“HTTP Session Queue
Size indication” on page
61
SAP_JMX_Cluster_Manager_HTTP_Queue_Size CRITICAL Yes
Telnet Session Queue Size indication
Occurs when the current telnet session queue size is equal to or greater than the
Telnet Session Queue Size threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Telnet Session Queue Size: size=@telnet_queue_size@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Average Session Process Time indication
Occurs when the average session process time is equal to or greater than the
Average Session Process Time threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Chapter 2. Resource models 59
Average Session Process Time: time=@session_process_time@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Webservices Session Queue Size indication
Occurs when the current webservices session queue size is equal to or greater than
the Webservices Session Queue Size threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Webservices Session Queue Size: size=@webservices_queue_size@
(threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
P4 Session Queue Size indication
Occurs when the current P4 session queue size is equal to or greater than the P4
Session Queue Size threshold.
60 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
P4 Session Queue Size: size=@p4_queue_size@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
JMS Session Queue Size indication
Occurs when the current JMS session queue size is equal to or greater than the JMS
Session Queue Size threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
JMS Session Queue Size: size=@jms_queue_size@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
HTTP Session Queue Size indication
Occurs when the current HTTP session queue size is equal to or greater than the
HTTP Session Queue Size threshold.
Chapter 2. Resource models 61
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
HTTP Session Queue Size: size=@http_queue_size@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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
JMS Session Queue Size The threshold value against which
the JMS session queue size is
compared. This threshold is exceeded
if the current value is equal to or
greater than this value.
1000
Telnet Session Queue Size The threshold value against which
the telnet session queue size is
compared. This threshold is exceeded
if the current value is equal to or
greater than this value.
1000
HTTP Session Queue Size The threshold value against which
the HTTP session queue size is
compared. This threshold is exceeded
if the current value is equal to or
greater than this value.
1000
Average Session Process Time The threshold value against which
the average session process time is
compared. This threshold is exceeded
if the current value is equal to or
greater than this value.
10000
P4 Session Queue Size The threshold value against which
the P4 session queue size is
compared. This threshold is exceeded
if the current value is equal to or
greater than this value.
1000
62 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Threshold name Description Default
value
Webservices Session Queue Size The threshold value against which
the webservices session queue size is
compared. This threshold is exceeded
if the current value is equal to or
greater than this value.
1000
Parameters
None
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 IBM Tivoli Monitoring Web Health Console.
Managed resource Context Properties
mySAP_JMX_Cluster_Manager Communication
application_class
Class of the registered object
application_label
Label of the registered object
application_oid
Object identifier of the registered object
application_version
Version of the mySAP software running on the
managed resource
sub_origin*
Label of the registered object
sub_source
Label of the associated SAP system object
http_queue_size
Number of items currently in use on the HTTP session
jms_queue_size
Number of items currently in use on the JMS session
p4_queue_size
Number of items currently in use on the P4 session
process_time
Average amount of time in milliseconds that a
message spends in the message queue of the session
communication layer. This is the amount of time
between the call of the send method and the actual
writing of the message in the socket.
telnet_queue_size
Number of items currently in use on the telnet session
webservices_queue_size
Number of items currently in use on the web services
session
Chapter 2. Resource models 63
Managed resource Context Properties
threshold_http_queue_size
Threshold value for comparison against the
http_queue_size attribute
threshold_jms_queue_size
Threshold value for comparison against the
jms_queue_size attribute
threshold_p4_queue_size
Threshold value for comparison against the
p4_queue_size attribute
threshold_process_time
Threshold value for comparison against the
process_time attribute
threshold_telnet_queue_size
Threshold value for comparison against the
telnet_queue_size attribute
threshold_webservices_queue_size
Threshold value for comparison against the
webservices_queue_size attribute
Note: An asterisk (*) denotes a key property.
Return codes
See Table 9 on page 130 for the return codes for this resource model.
CLI example
The following example uses the wdmeditprf command to add the mySAP JMX
Cluster Manager resource model to a profile:
wdmeditprf -P $PROFILE -add mySAP_JMXClusterManager -c 180 \
-Log -LogDisable -p 12:00 -Agg no -ap 00:15 -NoMin -NoMax -Avg \
-t Thr_JMX_Average_Session_Process_Time_gt 10000.000000 \
-t Thr_JMX_HTTP_Session_Queue_Size_gt 1000.000000 \
-t Thr_JMX_JMS_Session_Queue_Size_gt 1000.000000 \
-t Thr_JMX_P4_Session_Queue_Size_gt 1000.000000 \
-t Thr_JMX_Telnet_Session_Queue_Size_gt 1000.000000 \
-t Thr_JMX_Webservices_Session_Queue_Size_gt 1000.000000 \
-e SAP_JMX_Cluster_Manager_Telnet_Queue_Size \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_JMX_Cluster_Manager_Process_Time \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_JMX_Cluster_Manager_Webservices_Queue_Size \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_JMX_Cluster_Manager_JMS_Queue_Size \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_JMX_Cluster_Manager_P4_Queue_Size \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_JMX_Cluster_Manager_HTTP_Queue_Size \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec
64 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
mySAP JMX Cluster Node Status
Description
Monitors the mySAP JMX Java Cluster Node availability. Checks that a
mySAP.com J2EE cluster node is available and reports on the status of the node.
The resource model obtains status by making a JMX request to the cluster node.
The status is determined based on the results of this operation.
Use this resource model periodically to determine status.
If the resource model reports that the cluster node is not running, notify your
mySAP.com basis administrator of this problem.
The following table shows the key characteristics of this resource model.
Resource model overview
Internal name mySAP_JMXClusterNodeStatus
Category mySAP
Indications JMX Java Cluster Node Status
Tasks and built-in actions None
Default cycle time 3 minutes (180 seconds)
Target managed resource
mySAPJ2EEClusterNode, node type = Dispatcher or Server
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
“JMX Java Cluster Node
Status indication”
SAP_JMX_Java_Cluster_Node_Status CRITICAL Yes
JMX Java Cluster Node Status indication
Occurs when the Java Cluster Node Status is equal to one of the values of the Java
Cluster Node Status parameter.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
mySAP JMX Java Cluster Node of the instance @sub_origin@ is @server_status@
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Chapter 2. Resource models 65
Setting Default value
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Thresholds
None
Parameters
The following table lists the parameters that can be set for the mySAP JMX Cluster
Node Status resource model. The table shows the name, a short description, and
the default value for each parameter.
Parameter Description Default value
Java Cluster
Node Status
When the property Java Cluster Node
Status is equal to one of the values of
this parameter the event
SAP_JMX_Java_Cluster_Node_Status is
generated.
v up (up): FALSE
v down (down): TRUE
v unknown (unknown): TRUE
Note: Even though the down state
is enabled, the resource model
cannot detect and report this state
at this time.
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 IBM Tivoli Monitoring Web Health Console.
Managed resource Context Properties
mySAP_Java_Cluster_Node_
Status
Availability
application_class
Class of the registered object
application_label
Label of the registered object
application_oid
Object identifier of the registered object
application_version
Version of the mySAP software running on the
managed resource
sub_origin*
Label of the registered object
sub_source
Label of the associated SAP system object
66 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Managed resource Context Properties
server_availability
Numeric value representing a status of up. The value
is 100% if the state is up; 0% if the state is not up.
server_status
Status of the cluster node. The supported value is
″unknown.″ The ″up″ status is reported by clearing
events for the ″unknown″ status.
Note: An asterisk (*) denotes a key property.
Return codes
See Table 9 on page 130 for the return codes for this resource model.
CLI example
The following example uses the wdmeditprf command to add the mySAP JMX
Cluster Node Status resource model to a profile:
wdmeditprf -P $PROFILE -add mySAP_JMXClusterNodeStatus -c 60 \
-Log -LogDisable -p 12:00 -Agg no -ap 00:15 -NoMin -NoMax -Avg \
-AddPar Par_JMX_Java_Cluster_Node_Status_eqs "down" \
-AddPar Par_JMX_Java_Cluster_Node_Status_eqs "unknown" \
-e SAP_JMX_Java_Cluster_Node_Status \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec
Chapter 2. Resource models 67
mySAP JMX Configuration Manager
Description
Monitors the mySAP JMX Configuration Manager. The Configuration Manager is a
component of dispatcher and server cluster nodes. The Configuration Manager
enables J2EE engine modules to store and access data from a relational database
management system (RDBMS). This component uses the Open SQL for Java
framework to connect and work with the RDBMS.
This resource model monitors the mySAP J2EE Configuration Manager to detect
excessive database update times. The resource model provides monitoring of the
average time to commit database changes.
The following table shows the key characteristics of this resource model.
Resource model overview
Internal name mySAP_JMXConfigurationManager
Category mySAP
Indications Commit Duration
Tasks and built-in actions None
Default cycle time 3 minutes (180 seconds)
Target managed resource
mySAPJ2EEClusterNode, node type = Dispatcher or Server
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
“Commit Duration
indication”
SAP_JMX_Configuration_Manager_Commit_Duration CRITICAL Yes
Commit Duration indication
Occurs when the commit duration is equal to or greater than the Commit Duration
threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Commit Duration: time=@commit_duration@ ms (threshold=@threshold@ ms)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
68 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Setting Default value
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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
Commit Duration The threshold value against which
the commit duration is compared.
This threshold is exceeded if the
current value is equal to or greater
than this value.
120000
Parameters
None
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 IBM Tivoli Monitoring Web Health Console.
Managed resource Context Properties
mySAP_JMX_Configuration_
Manager
Commit_Duration
application_class
Class of the registered object
application_label
Label of the registered object
application_oid
Object identifier of the registered object
application_version
Version of the mySAP software running on the
managed resource
sub_origin*
Label of the registered object
sub_source
Label of the associated SAP system object
commit_duration
Commit duration
Chapter 2. Resource models 69
Managed resource Context Properties
threshold
Threshold value used to trigger an indication
Note: An asterisk (*) denotes a key property.
Return codes
See Table 9 on page 130 for the return codes for this resource model.
CLI example
The following example uses the wdmeditprf command to add the mySAP JMX
Configuration Manager resource model to a profile:
wdmeditprf -P $PROFILE -add mySAP_JMXConfigurationManager -c 180 \
-Log -LogDisable -p 12:00 -Agg no -ap 00:15 -NoMin -NoMax -Avg \
-t Thr_JMX_Commit_Duration_gt 120000.000000 \
-e SAP_JMX_Configuration_Manager_Commit_Duration \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec
70 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
mySAP JMX Connections Manipulator Manager
Description
Monitors the mySAP JMX Connections Manipulator Manager. The Connections
Manipulator Manager is a component of dispatcher cluster nodes. The
management of client connections in the cluster is represented in the J2EE engine
by the Connections Manipulator Manager. This manager has an indirect connection
to all services running on the dispatcher that receive or send data outside the
cluster using a socket. It provides threads in which the processing of the received
requests, their transfer from the dispatcher to the server, and the return of the
response back to the user is accomplished.
This resource model monitors the mySAP J2EE Connections Manipulator Manager
to detect excessive use of the global connections pool and to detect excessive use of
socket connections by a particular protocol. The resource model provides
monitoring of the following items:
v Current size of the connections pool
v Number of HTTP connections
v Number of IIOP connections
v Number of P4 connections
The following table shows the key characteristics of this resource model.
Resource model overview
Internal name mySAP_JMXConnectionsManipulatorManager
Category mySAP
Indications Current Pool
HTTP Connections
IIOP Connections
P4 Connections
Tasks and built-in actions None
Default cycle time 3 minutes (180 seconds)
Target managed resource
mySAPJ2EEClusterNode, node type = Dispatcher
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
“Current Pool
indication” on page 72
SAP_JMX_Connections_Current_Pool CRITICAL Yes
“HTTP Connections
indication” on page 72
SAP_JMX_Connections_HTTP CRITICAL Yes
“IIOP Connections
indication” on page 73
SAP_JMX_Connections_IIOP CRITICAL Yes
Chapter 2. Resource models 71
Indication Generated event Default
severity
Clearing
events
“P4 Connections
indication” on page 73
SAP_JMX_Connections_P4 CRITICAL Yes
Current Pool indication
Occurs when the size of current pool is equal to or greater than the Current Pool
threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Current Pool: size=@current_pool@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
HTTP Connections indication
Occurs when the count of HTTP connections is equal to or greater than the HTTP
Connections threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
HTTP Connections: count=@HTTP_count@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
72 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
IIOP Connections indication
Occurs when the count of IIOP connections is equal to or greater than the IIOP
Connections threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
IIOP Connections: count=@IIOP_count@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
P4 Connections indication
Occurs when the count of P4 connections is equal to or greater than the P4
Connections threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
P4 Connections: count=@p4_count@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Chapter 2. Resource models 73
Setting Default value
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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
Current Pool The threshold value against which
the count of current pool is
compared. This threshold is exceeded
if the current value is equal to or
greater than this value.
400
HTTP Connections The threshold value against which
the count of HTTP connections is
compared. This threshold is exceeded
if the current value is equal to or
greater than this value.
100
IIOP Connections The threshold value against which
the count of IIOP connections is
compared. This threshold is exceeded
if the current value is equal to or
greater than this value.
100
P4 Connections The threshold value against which
the count of P4 connections is
compared. This threshold is exceeded
if the current value is equal to or
greater than this value.
100
Parameters
None
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 IBM Tivoli Monitoring Web Health Console.
74 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Managed resource Context Properties
mySAP_JMX_Connections Connections
application_class
Class of the registered object
application_label
Label of the registered object
application_oid
Object identifier of the registered object
application_version
Version of the mySAP software running on the
managed resource
sub_origin*
Label of the registered object
sub_source
Label of the associated SAP system object
current_pool
Current size of the connections pool
HTTP_count
Number of HTTP connections
IIOP_count
Number of IIOP connections
p4_count
Number of P4 connections
threshold_current_pool
Current value of the Current Pool threshold
configured for this resource model
threshold_HTTP_count
Current value of the HTTP Connections threshold
configured for this resource model
threshold_IIOP_count
Current value of the IIOP Connections threshold
configured for this resource model
threshold_p4_count
Current value of the P4 Connections threshold
configured for this resource model
Note: An asterisk (*) denotes a key property.
Return codes
See Table 9 on page 130 for the return codes for this resource model.
CLI example
The following example uses the wdmeditprf command to add the mySAP JMX
Connections Manipulator Manager resource model to a profile:
wdmeditprf -P $PROFILE -add mySAP_JMXConnectionsManipulatorManager -c 180 \
-Log -LogDisable -p 12:00 -Agg no -ap 00:15 -NoMin -NoMax -Avg \
-t Thr_JMX_Current_Pool_gt 400.000000 \
-t Thr_JMX_HTTP_Connections_gt 100.000000 \
-t Thr_JMX_IIOP_Connections_gt 100.000000 \
-t Thr_JMX_P4_Connections_gt 100.000000 \
-e SAP_JMX_Connections_P4 \
Chapter 2. Resource models 75
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_JMX_Connections_IIOP \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_JMX_Connections_HTTP \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_JMX_Connections_Current_Pool \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec
76 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
mySAP JMX Generic Monitor
Description
Monitors a specified mySAP JMX Property. A J2EE cluster node makes many
attributes available through its JMX interface.
This resource model provides an easy way for you to monitor J2EE cluster node
attributes that are monitored by one of the JMX MBeans. You must specify the
″Object Name Pattern″ used to construct the Object Name to identify the JMX
MBean. For example:
ObjectName: "Object Name Pattern",
Example of Object Name Pattern:
/Kernel/System Threads Pool/ThreadPoolPercentageUsage
You can use this resource model to monitor any attribute for the following values:
v Current value
v Maximum value
v Minimum value
The following table shows the key characteristics of this resource model.
Resource model overview
Internal name mySAP_JMXGenericMonitor
Category mySAP
Indications Current value
Maximum
Minimum
Tasks and built-in actions None
Default cycle time 3 minutes (180 seconds)
Target managed resource
mySAPJ2EEClusterNode, node type = Dispatcher or Server
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
“Current value
indication” on page 78
SAP_JMX_Generic_Value CRITICAL Yes
“Maximum indication”
on page 78
SAP_JMX_Generic_Maximum CRITICAL Yes
“Minimum indication”
on page 79
SAP_JMX_Generic_Minimum CRITICAL Yes
Chapter 2. Resource models 77
Current value indication
Occurs when the current value for the specified property compares successfully
against the threshold. Use the Comparison parameter to specify how the current
value is to be compared to the threshold value.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
JMX Monitor: @object_name_pattern@, value=@value@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Maximum indication
Occurs when the maximum value for the specified property is equal to or greater
than the Maximum threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
JMX Monitor: @object_name_pattern@, maximum@maximum@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
78 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Minimum indication
Occurs when the minimum value for the specified property is equal to or less than
the Minimum threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
JMX Monitor: @object_name_pattern@, minimum=@minimum@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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
Value The threshold value against which
the specified property is compared.
This threshold value and current
value are compared using the
operator specified in the Comparison
parameter.
50
Maximum The threshold value against which
the specified property is compared.
This threshold is exceeded if the
maximum value is equal to or greater
than this value.
100
Minimum The threshold value against which
the specified property is compared.
This threshold is exceeded if the
minimum value is equal to or less
than this value.
10
Chapter 2. Resource models 79
Parameters
The following table lists the parameters that can be set for the mySAP JMX Generic
Monitor resource model. The table shows the name, a short description, and the
default value for each parameter.
Parameter Description Default value
Object
Name
Pattern
Name of the property (JMX MBean) to be monitored.
Examples:
/Kernel/System Threads Pool/ThreadPoolPercentageUsage
/Kernel/Connections Manipulator/CurrentPoolSize
/Kernel/Configuration Manager/Commit Duration
None
Comparison Defines when an indication occurs for the current value
attribute. Possible conditions are when the comparison value
is one of the following:
v Greater than the threshold
v Less than the threshold
v Equal to the threshold
v Greater than or equal to the threshold
v Less than or equal to the threshold
greater
(greater)
less (less)
equal (equal)
greater_equal
(greater or
equal)
less_equal
(less or equal)
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 IBM Tivoli Monitoring Web Health Console.
Managed resource Context Properties
mySAP_JMX_Generic Generic
application_class
Class of the registered object
application_label
Label of the registered object
application_oid
Object identifier of the registered object
application_version
Version of the mySAP software running on the
managed resource
sub_origin*
Label of the registered object
sub_source
Label of the associated SAP system object
maximum
Current maximum value for the specified MBean
Monitor
minimum
Current minimum value for the specified MBean
Monitor
80 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Managed resource Context Properties
object_name_pattern*
Name of the property (JMX MBean) to be monitored
value Current value for the specified MBean Monitor
threshold_maximum
Threshold value for the maximum parameter
threshold_minimum
Threshold value for the minimum parameter
threshold_value
Threshold value for the value parameter
Note: An asterisk (*) denotes a key property.
Return codes
See Table 9 on page 130 for the return codes for this resource model.
CLI example
The following example uses the wdmeditprf command to add the mySAP JMX
Generic Monitor resource model to a profile:
wdmeditprf -P $PROFILE -add mySAP_JMXGenericMonitor -c 180 \
-Log -LogDisable -p 12:00 -Agg no -ap 00:15 -NoMin -NoMax -Avg \
-t Thr_JMX_Generic_Max_gt 100.000000 \
-t Thr_JMX_Generic_Min_gt 10.000000 \
-t Thr_JMX_Generic_Value_lt 50.000000 \
-AddPar Par_ObjectNamePattern "/Kernel/System Threads Pool/ \
ThreadPoolPercentageUsage" \
-AddPar Par_MonitorType "greater_equal" \
-e SAP_JMX_Generic_Minimum \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_JMX_Generic_Maximum \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_JMX_Generic_Value \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec
Chapter 2. Resource models 81
mySAP JMX Memory Info Service
Description
Monitors the mySAP JMX Memory Info Service. The Memory Info Service is a
component of dispatcher server cluster nodes. This service provides a set of
properties for managing memory usage levels.
This resource model monitors the mySAP J2EE Memory Info Service to detect
excessive use of available memory. The resource model provides monitoring of
Used memory in the cluster node.
The following table shows the key characteristics of this resource model.
Resource model overview
Internal name mySAP_JMXMemoryInfoService
Category mySAP
Indications Used Memory
Tasks and built-in actions None
Default cycle time 3 minutes (180 seconds)
Target managed resource
mySAPJ2EEClusterNode, node type = Dispatcher or Server
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
“Used Memory
indication”
SAP_JMX_Memory_Info_Service CRITICAL Yes
Used Memory indication
Occurs when the amount of used memory is equal to or greater than the Used
Memory threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Used Memory: value=@used_memory@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
82 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Setting Default value
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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
Used Memory (MB) The threshold value against which
the amount of used memory is
compared. This threshold is exceeded
if the current value is equal to or
greater than this value.
160
Parameters
None
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 IBM Tivoli Monitoring Web Health Console.
Managed resource Context Properties
mySAP_JMX_Memory_Info
_Service
Memory
application_class
Class of the registered object
application_label
Label of the registered object
application_oid
Object identifier of the registered object
application_version
Version of the mySAP software running on the
managed resource
sub_origin*
Label of the registered object
sub_source
Label of the associated SAP system object
used_memory
Current, maximum, and minimum values of the
memory used
Chapter 2. Resource models 83
Managed resource Context Properties
threshold
Threshold value used to trigger an indication
Note: An asterisk (*) denotes a key property.
Return codes
See Table 9 on page 130 for the return codes for this resource model.
CLI example
The following example uses the wdmeditprf command to add the mySAP JMX
Memory Info Service resource model to a profile:
wdmeditprf -P $PROFILE -add mySAP_JMXMemoryInfoService -c 180 \
-Log -LogDisable -p 12:00 -Agg no -ap 00:15 -NoMin -NoMax -Avg \
-t Thr_JMX_Used_Memory_gt 160.000000 \
-e SAP_JMX_Memory_Info_Service \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec
84 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
mySAP JMX System Thread Manager
Description
Monitors the mySAP JMX System Thread Manager. The System Thread Manager is
a component of dispatcher and server cluster nodes. The thread manager allocates
threads for the processing of system work requests. If all threads are allocated to
work requests, new work requests are delayed in their processing.
This resource model monitors the mySAP J2EE System Thread Manager to allow
timely detection of thread overuse and delayed work requests. The resource model
provides monitoring of the following items:
v Percent of threads in use
v Number of requests, in the request queue, waiting for a thread
v Number of requests, not in the request queue, waiting to be added to the
request queue
v Total number of requests that can be stored in the request queue
The following table shows the key characteristics of this resource model.
Resource model overview
Internal name mySAP_JMXSystemThreadManager
Category mySAP
Indications Usage Percent
Waiting Tasks Count
Waiting Tasks Queue Overflow
Waiting Tasks Queue Size
Tasks and built-in actions None
Default cycle time 3 minutes (180 seconds)
Target managed resource
mySAPJ2EEClusterNode, node type = Dispatcher or Server
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
“Usage Percent
indication” on page 86
SAP_JMX_System_Thread_Usage_Percent CRITICAL Yes
“Waiting Tasks Count
indication” on page 86
SAP_JMX_System_Thread_Waiting_Tasks_Count CRITICAL Yes
“Waiting Tasks Queue
Overflow indication” on
page 87
SAP_JMX_System_Thread_Waiting_Tasks_Queue_Overflow CRITICAL Yes
“Waiting Tasks Queue
Size indication” on page
87
SAP_JMX_System_Thread_Waiting_Tasks_Queue_Size CRITICAL Yes
Chapter 2. Resource models 85
Usage Percent indication
Occurs when the percent of used application threads is equal to or greater than the
Usage Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Usage: percent=@usage_percent@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Waiting Tasks Count indication
Occurs when the count of waiting tasks is equal to or greater than the Waiting
Tasks Count threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Waiting Tasks: count=@waiting_tasks_count@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
86 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Waiting Tasks Queue Overflow indication
Occurs when the count of waiting tasks queue overflow is equal to or greater than
the Waiting Tasks Queue Overflow threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Waiting Tasks Queue Overflow: count=@waiting_tasks_queue_overflow@
(threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Waiting Tasks Queue Size indication
Occurs when the waiting tasks queue size is equal to or greater than the Waiting
Tasks Queue Size threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Waiting Tasks Queue Size: count=@waiting_tasks_queue_size@ (threshold=@threshold@)
See “Indication attributes” on page 126 for the attributes for this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Chapter 2. Resource models 87
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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
Usage Percent The threshold value against which
the percent of used threads is
compared. This threshold is exceeded
if the current value is equal to or
greater than this value.
100
Waiting Tasks Count The threshold value against which
the count of waiting tasks is
compared. This threshold is exceeded
if the current value is equal to or
greater than this value.
600
Waiting Tasks Queue Overflow The threshold value against which
the count of waiting tasks queue
overflow is compared. This threshold
is exceeded if the current value is
equal to or greater than this value.
100
Waiting Tasks Queue Size The threshold value against which
the count of waiting tasks queue size
is compared. This threshold is
exceeded if the current value is equal
to or greater than this value.
1000
Parameters
None
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 IBM Tivoli Monitoring Web Health Console.
88 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Managed resource Context Properties
mySAP_JMX_System_ Thread Thread
application_class
Class of the registered object
application_label
Label of the registered object
application_oid
Object identifier of the registered object
application_version
Version of the mySAP software running on the
managed resource
sub_origin*
Label of the registered object
sub_source
Label of the associated SAP system object
usage_percent
Current usage of the thread pool, in percent
waiting_tasks_count
Number of runnable tasks waiting for available thread
from the thread pool to be executed
waiting_tasks_queue_overflow
Number of threads waiting to deposit a runnable task
in the request queue if it is full
waiting_tasks_queue_size
Capacity of the request queue where the tasks waiting
for execution are stored
threshold_usage_percent
Threshold value for comparison against the
usage_percent attribute
threshold_waiting_tasks_count
Threshold value for comparison against the
waiting_tasks_count attribute
threshold_waiting_tasks_queue_overflow
Threshold value for comparison against the
waiting_tasks_queue_overflow attribute
threshold_waiting_tasks_queue_size
Threshold value for comparison against the
waiting_tasks_queue_size attribute
Note: An asterisk (*) denotes a key property.
Return codes
See Table 9 on page 130 for the return codes for this resource model.
CLI example
The following example uses the wdmeditprf command to add the mySAP JMX
System Thread Manager resource model to a profile:
wdmeditprf -P $PROFILE -add mySAP_JMXSystemThreadManager -c 180 \
-Log -LogDisable -p 12:00 -Agg no -ap 00:15 -NoMin -NoMax -Avg \
-t Thr_JMX_Usage_Percent_gt 100.000000 \
-t Thr_JMX_Waiting_Tasks_Count_gt 600.000000 \
Chapter 2. Resource models 89
-t Thr_JMX_Waiting_Tasks_Queue_Overflow_gt 100.000000 \
-t Thr_JMX_Waiting_Tasks_Queue_Size_gt 1000.000000 \
-e SAP_JMX_System_Thread_Waiting_Tasks_Count \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_JMX_System_Thread_Waiting_Tasks_Queue_Size \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_JMX_System_Thread_Usage_Percent \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_JMX_System_Thread_Waiting_Tasks_Queue_Overflow \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec
90 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
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.
The following table shows the key characteristics of this resource model.
Resource model overview
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
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
“Dialog Work Process
Run Time indication”
on page 92
SAP_DialogWpRunTime MINOR Yes
“Background Work
Process Run Time
indication” on page 92
SAP_BackgroundWpRunTime MINOR Yes
“Update Work Process
Run Time indication”
on page 94
SAP_UpdateWpRunTime CRITICAL Yes
Chapter 2. Resource models 91
Indication Generated event Default
severity
Clearing
events
“Update2 Work Process
Run Time indication”
on page 94
SAP_Update2WpRunTime CRITICAL Yes
“Spool Work Process
Run Time indication”
on page 93
SAP_SpoolWpRunTime MINOR Yes
“Enqueue Work Process
Run Time indication”
on page 93
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Run time exceeded: runtime=@wp_runtime@, threshold=@threshold@,
program=@wp_program@, pid=@wp_pid@, number=@wp_number@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Run time exceeded: runtime=@wp_runtime@, threshold=@threshold@,
program=@wp_program@, pid=@wp_pid@, number=@wp_number@
See “Indication attributes” on page 126 for the attributes of this indication.
92 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Run time exceeded: runtime=@wp_runtime@, threshold=@threshold@,
program=@wp_program@, pid=@wp_pid@, number=@wp_number@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Run time exceeded: runtime=@wp_runtime@, threshold=@threshold@,
program=@wp_program@, pid=@wp_pid@, number=@wp_number@
Chapter 2. Resource models 93
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Run time exceeded: runtime=@wp_runtime@, threshold=@threshold@,
program=@wp_program@, pid=@wp_pid@, number=@wp_number@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
94 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Run time exceeded: runtime=@wp_runtime@, threshold=@threshold@,
program=@wp_program@, pid=@wp_pid@, number=@wp_number@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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
Dialog Elapsed Time The maximum amount of
time, in seconds, for the
dialog work process.
60
Background Elapsed Time The maximum amount of
time, in seconds, for the
background work process.
600
Update Elapsed Time The maximum amount of
time, in seconds, for the
update work process.
60
Update2 Elapsed Time The maximum amount of
time, in seconds, for the
update2 work process.
60
Spool Elapsed Time The maximum amount of
time, in seconds, for the
spool work process.
600
Enqueue Elapsed Time The maximum amount of
time, in seconds, for the
enqueue work process.
60
Parameters
The following table lists the parameters that can be set for the Long running Work
Process Status resource model. The table shows the name, a short description, and
the default value for each parameter.
Chapter 2. Resource models 95
Parameter Description Default value
Work process
types to
monitor
Identifies the different work
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
Class of the registered object
application_label
Label of the registered object
application_oid
Object identifier of the registered object
application_version
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*
Label of the registered object
sub_source
The label of the associated SAP system object.
Note: An asterisk (*) denotes a key property.
Return codes
See “Return codes” on page 129 for the return codes for this resource model.
96 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
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 \
-Log -LogDisable -p 12:00 -Agg yes -ap 00:15 -NoMin -NoMax -Avg \
-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 \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_UpdateWpRunTime \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_SpoolWpRunTime \
-o 1 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_DialogWpRunTime \
-o 1 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_BackgroundWpRunTime \
-o 1 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_Update2WpRunTime \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec
Chapter 2. Resource models 97
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
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_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
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
“Spool Work Process
Running indication” on
page 99
SAP_SpoolWpRunning MINOR Yes
98 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Indication Generated event Default
severity
Clearing
events
“Spool Work Process
Running Percent
indication” on page 100
SAP_SpoolWpRunningPercent MINOR Yes
“Spool Work Process
Stopped indication” on
page 100
SAP_SpoolWpStopped CRITICAL Yes
“Spool Work Process
Stopped Percent
indication” on page 101
SAP_SpoolWpStoppedPercent CRITICAL Yes
“Spool Work Process
Completed indication”
on page 101
SAP_SpoolWpCompleted CRITICAL Yes
“Spool Work Process
Completed Percent
indication” on page 102
SAP_SpoolWpCompletedPercent CRITICAL Yes
“Spool Work Process
Waiting indication” on
page 102
SAP_SpoolWpWaiting MINOR Yes
“Spool Work Process
Waiting Percent
indication” on page 103
SAP_SpoolWpWaitingPercent MINOR Yes
“Spool Work Process
Queue indication” on
page 103
SAP_SpoolWpQueue CRITICAL Yes
“Spool Work Process
Program Failure
indication” on page 104
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_running@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 3
Holes 0
Associated tasks and built-in actions None
Chapter 2. Resource models 99
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Spool Work Process Running Percent indication
Occurs when the percentage of running spool work processes is greater than or
equal to the Running Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 3
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Spool Work Process Stopped indication
Occurs when the number of stopped spool work processes is greater than or equal
to the Stopped threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_stopped@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
100 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Spool Work Process Stopped Percent indication
Occurs when the percentage of stopped spool work processes is greater than or
equal to the Stopped Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Spool Work Process Completed indication
Occurs when the number of completed spool work processes is greater than or
equal to the Completed threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_completed@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Chapter 2. Resource models 101
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Spool Work Process Completed Percent indication
Occurs when the percentage of completed spool work processes is greater than or
equal to the Completed Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Spool Work Process Waiting indication
Occurs when the number of spool work processes in the waiting state is less than
or equal to the Waiting threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_waiting@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
102 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Spool Work Process Waiting Percent indication
Occurs when the percentage of spool work processes in the waiting state is less
than or equal to the Waiting Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Spool Work Process Queue indication
Occurs when the percentage of spool work queued is greater than or equal to the
Queued Work Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_queue_percent@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Chapter 2. Resource models 103
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_failures@, threshold=@threshold@, pid=@wp_pid@,
number=@wp_number@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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 before an
indication is triggered.
95
Stopped The maximum number of
stopped work processes
before an indication is
triggered.
1
Stopped Percent The maximum percentage of
work processes in the
stopped state before an
indication is triggered.
10
104 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Threshold name Description Default value
Completed The maximum number of
completed work processes
before an indication is
triggered.
1
Completed Percent The maximum percentage of
work processes in the
completed state at a given
time before an indication is
triggered.
10
Waiting The minimum number of
waiting work processes
before an indication is
triggered.
0
Waiting Percent The minimum percentage of
work processes in the
waiting state at a given time
before an indication is
triggered.
0
Queued Work Percent The maximum percentage of
work processes in the queue
at a given time before an
indication is triggered.
80
Program Failures The maximum number of
program failures before an
indication is triggered.
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.
Parameter Description Default value
Work Process
states to
monitor
Identifies the different work
process states for which to
monitor. If the value is set to
″True,″ the 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 “Logged information for work process resource models” on page 128 for a list
of the properties that are logged for this resource model.
Return codes
See “Return codes” on page 129 for the return codes for this resource model.
Chapter 2. Resource models 105
CLI example
The following example uses the wdmeditprf command to add the mySAP Spool
Work Process Status resource model to a profile:
wdmeditprf -P $PROFILE -add mySAP_SpoolWPStatus -c 180 \
-Log -LogDisable -p 12:00 -Agg yes -ap 00:15 -NoMin -NoMax -Avg \
-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_Queue_Percent_max 80.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 "queue_percent" \
-AddPar Par_State_eqs "program_failures" \
-e SAP_SpoolWpCompleted \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_SpoolWpQueue \
-o 5 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_SpoolWpProgramFailures \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_SpoolWpRunningPercent \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_SpoolWpWaiting \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_SpoolWpStopped \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_SpoolWpStoppedPercent \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_SpoolWpCompletedPercent \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_SpoolWpWaitingPercent \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_SpoolWpRunning \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec
106 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
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
The following properties are also monitored:
v Queue time
v Failed programs
The following table shows the key characteristics of this resource model.
Resource model overview
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
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.
Chapter 2. Resource models 107
Indication Generated event Default
severity
Clearing
events
“Update Work Process
Running indication”
SAP_UpdateWpRunning MINOR Yes
“Update Work Process
Running Percent
indication” on page 109
SAP_UpdateWpRunningPercent MINOR Yes
“Update Work Process
Stopped indication” on
page 109
SAP_UpdateWpStopped CRITICAL Yes
“Update Work Process
Stopped Percent
indication” on page 110
SAP_UpdateWpStoppedPercent CRITICAL Yes
“Update Work Process
Completed indication”
on page 110
SAP_UpdateWpCompleted CRITICAL Yes
“Update Work Process
Completed Percent
indication” on page 111
SAP_UpdateWpCompletedPercent CRITICAL Yes
“Update Work Process
Waiting indication” on
page 111
SAP_UpdateWpWaiting MINOR Yes
“Update Work Process
Waiting Percent
indication” on page 112
SAP_UpdateWpWaitingPercent MINOR Yes
“Update Work Process
Queue indication” on
page 112
SAP_UpdateWpQueue CRITICAL Yes
“Update Work Process
Program Failure
indication” on page 113
SAP_UpdateWpProgramFailures CRITICAL Yes
Update Work Process Running indication
Occurs when the number of running update 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 IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_running@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 3
Holes 0
108 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Setting Default value
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Update Work Process Running Percent indication
Occurs when the percentage of running update work processes is greater than or
equal to the Running Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 3
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Update Work Process Stopped indication
Occurs when the number of stopped update work processes is greater than or
equal to the Stopped threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_stopped@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Chapter 2. Resource models 109
Setting Default value
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Update Work Process Stopped Percent indication
Occurs when the percentage of stopped update work processes is greater than or
equal to the Stopped Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Update Work Process Completed indication
Occurs when the number of completed update work processes is greater than or
equal to the Completed threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_completed@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
110 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Setting Default value
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Update Work Process Completed Percent indication
Occurs when the percentage of completed update work processes is greater than or
equal to the Completed Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Update Work Process Waiting indication
Occurs when the number of update work processes in the waiting state is less than
or equal to the Waiting threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_waiting@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
Chapter 2. Resource models 111
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Update Work Process Waiting Percent indication
Occurs when the percentage of update work processes in the waiting state is less
than or equal to the Waiting Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Update Work Process Queue indication
Occurs when the queue time is greater than or equal to the Queued Work Time
threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Time exceeded: time=@wp_queue_time@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
112 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Update Work Process Program Failure indication
Occurs when the number of update work process program failures is greater than
or equal to the Program Failure threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_failures@, threshold=@threshold@, pid=@wp_pid@,
number=@wp_number@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
Chapter 2. Resource models 113
Threshold name Description Default value
Running The maximum number of
running work processes
before an indication is
triggered.
4
Running Percent The maximum percentage of
work processes in the
running state before an
indication is triggered.
95
Stopped The maximum number of
stopped work processes
before an indication is
triggered.
1
Stopped Percent The maximum percentage of
work processes in the
stopped state before an
indication is triggered.
10
Completed The maximum number of
completed work processes
before an indication is
triggered.
1
Completed Percent The maximum percentage of
work processes in the
completed state at a given
time before an indication is
triggered.
10
Waiting The minimum number of
waiting work processes
before an indication is
triggered.
0
Waiting Percent The minimum percentage of
work processes in the
waiting state at a given time
before an indication is
triggered.
0
Queued Work Time The maximum amount of
time a work process can be
in the queue before an
indication is triggered.
500
Program Failures The maximum number of
program failures before an
indication is triggered.
1
Parameters
The following table lists the parameters that can be set for the Update Work
Process Status resource model. The table shows the name, a short description, and
the default value for each parameter.
114 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Parameter Description Default value
Work Process
states to
monitor
Identifies the different work
process states for which to
monitor. If the value is set to
″True,″ the 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 “Logged information for work process resource models” on page 128 for a list
of the properties that are logged for this resource model.
Return codes
See “Return codes” on page 129 for the return codes for this resource model.
CLI example
The following example uses the wdmeditprf command to add the mySAP Update
Work Process Status resource model to a profile:
wdmeditprf -P $PROFILE -add mySAP_UpdateWPStatus -c 180 \
-Log -LogDisable -p 12:00 -Agg yes -ap 00:15 -NoMin -NoMax -Avg \
-t Thr_Queue_Time_max 500.000000 \
-t Thr_Completed_max 1.000000 \
-t Thr_Stopped_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 4.000000 \
-t Thr_Program_Failures_max 1.000000 \
-t Thr_Completed_Percent_max 10.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_time" \
-e SAP_UpdateWpQueue \
-o 5 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_UpdateWpRunningPercent \
-o 3 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_UpdateWpWaiting \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_UpdateWpStopped \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_UpdateWpWaitingPercent \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_UpdateWpStoppedPercent \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_UpdateWpProgramFailures \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_UpdateWpCompleted \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_UpdateWpRunning \
Chapter 2. Resource models 115
-o 3 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_UpdateWpCompletedPercent \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec
116 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
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
The following properties are also monitored:
v Queue time
v Failed programs
The following table shows the key characteristics of this resource model:
Resource model overview
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
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
“Update2 Work Process
Running indication” on
page 118
SAP_Update2WpRunning MINOR Yes
Chapter 2. Resource models 117
Indication Generated event Default
severity
Clearing
events
“Update2 Work Process
Running Percent
indication” on page 119
SAP_Update2WpRunningPercent MINOR Yes
“Update2 Work Process
Stopped indication” on
page 119
SAP_Update2WpStopped CRITICAL Yes
“Update2 Work Process
Stopped Percent
indication” on page 120
SAP_Update2WpStoppedPercent CRITICAL Yes
“Update2 Work Process
Completed indication”
on page 120
SAP_Update2WpCompleted CRITICAL Yes
“Update2 Work Process
Completed Percent
indication” on page 121
SAP_Update2WpCompletedPercent CRITICAL Yes
“Update2 Work Process
Waiting indication” on
page 121
SAP_Update2WpWaiting MINOR Yes
“Update2 Work Process
Waiting Percent
indication” on page 122
SAP_Update2WpWaitingPercent MINOR Yes
“Update2 Work Process
Queue indication” on
page 122
SAP_Update2WpQueue CRITICAL Yes
“Update2 Work Process
Program Failure
indication” on page 123
SAP_Update2WpProgramFailures CRITICAL Yes
Update2 Work Process Running indication
Occurs when the number of running update2 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 IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_running@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 3
Holes 0
Associated tasks and built-in actions None
118 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Update2 Work Process Running Percent indication
Occurs when the percentage of running update2 work processes is greater than or
equal to the Running Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 3
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Update2 Work Process Stopped indication
Occurs when the number of stopped update2 work processes is greater than or
equal to the Stopped threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_stopped@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Chapter 2. Resource models 119
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Update2 Work Process Stopped Percent indication
Occurs when the percentage of stopped update2 work processes is greater than or
equal to the Stopped Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Update2 Work Process Completed indication
Occurs when the number of completed update2 work processes is greater than or
equal to the Completed threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_completed@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
120 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 2
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Update2 Work Process Waiting indication
Occurs when the number of update2 work processes in the waiting state is less
than or equal to the Waiting threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_waiting@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Chapter 2. Resource models 121
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Update2 Work Process Waiting Percent indication
Occurs when the percentage of update2 work processes in the waiting state is less
than or equal to the Waiting Percent threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Percent exceeded: percent=@wp_percent_used@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Update2 Work Process Queue indication
Occurs when the queue time is greater than or equal to the Queued Work Time
threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Time exceeded: time=@wp_queue_time@, threshold=@threshold@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 5
Holes 0
Associated tasks and built-in actions None
122 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
Update2 Work Process Program Failure indication
Occurs when the number of update2 work process program failures is greater than
or equal to the Program Failure threshold.
When the indication occurs often enough to trigger an event, the event delivers a
message to the IBM Tivoli Enterprise Console in the following format:
Count exceeded: count=@wp_failures@, threshold=@threshold@, pid=@wp_pid@,
number=@wp_number@
See “Indication attributes” on page 126 for the attributes of this indication.
The following table describes the default settings for this indication.
Setting Default value
Send indications to IBM Tivoli Enterprise
Console
Yes
Send indications to IBM Tivoli Business
Systems Manager
No
Occurrences 1
Holes 0
Associated tasks and built-in actions None
Note: If you have IBM Tivoli Business Systems Manager configured for your
systems, IBM Tivoli Enterprise Console automatically forwards events to
IBM Tivoli Business Systems Manager. Do not change the configuration of
the indication to send events to IBM Tivoli Business Systems Manager.
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.
4
Running Percent The maximum percentage of
work processes in the
running state before an
indication is triggered.
95
Stopped The maximum number of
stopped work processes
before an indication is
triggered.
1
Stopped Percent The maximum percentage of
work processes in the
stopped state before an
indication is triggered.
10
Chapter 2. Resource models 123
Threshold name Description Default value
Completed The maximum number of
completed work processes
before an indication is
triggered.
1
Completed Percent The maximum percentage of
work processes in the
completed state at a given
time before an indication is
triggered.
10
Waiting The minimum number of
waiting work processes
before an indication is
triggered.
0
Waiting Percent The minimum percentage of
work processes in the
waiting state at a given time
before an indication is
triggered.
0
Queued Work Time The maximum amount of
time a work process can be
in the queue before an
indication is triggered.
500
Program Failures The maximum number of
program failures before an
indication is triggered.
1
Parameters
The following table lists the parameters that can be set for the Update2 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 the value is set to
″True,″ the 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 “Logged information for work process resource models” on page 128 for a list
of the properties that are logged for this resource model.
Return codes
See “Return codes” on page 129 for the return codes for this resource model.
124 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
CLI example
The following example uses the wdmeditprf command to add the mySAP Update2
Work Process Status resource model to a profile:
wdmeditprf -P $PROFILE -add mySAP_Update2WPStatus -c 180 \
-Log -LogDisable -p 12:00 -Agg yes -ap 00:15 -NoMin -NoMax -Avg \
-t Thr_Queue_Time_max 500.000000 \
-t Thr_Completed_max 1.000000 \
-t Thr_Stopped_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_Running_max 4.000000 \
-t Thr_Waiting_Percent_min 0.000000 \
-t Thr_Program_Failures_max 1.000000 \
-t Thr_Completed_Percent_max 10.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_time" \
-e SAP_Update2WpStoppedPercent \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_Update2WpWaitingPercent \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_Update2WpWaiting \
-o 5 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_Update2WpProgramFailures \
-o 1 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_Update2WpStopped \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_Update2WpCompletedPercent \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_Update2WpQueue \
-o 5 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_Update2WpCompleted \
-o 2 -h 0 -severity CRITICAL -NoSendTBSM -SendTec \
-e SAP_Update2WpRunning \
-o 3 -h 0 -severity MINOR -NoSendTBSM -SendTec \
-e SAP_Update2WpRunningPercent \
-o 3 -h 0 -severity MINOR -NoSendTBSM -SendTec
Chapter 2. Resource models 125
Indication attributes
All of the Feature Option 2 resource models have certain attributes in common. In
addition to the common attributes, the work process resource models have
attributes specific to the work process indications, and the JMX resource models
have attributes specific to the JMX indications.
Attributes common to all Feature Option 2 resource models
All of the Feature Option 2 resource models have the following attributes:
application_class
Class of the registered object
application_label
Label of the registered object
application_oid
Object identifier of the registered object
application_version
Version of the mySAP software running on the managed resource
sub_origin
Label of the registered object
threshold
Threshold value used to trigger an indication
Attributes for work process resource model indications
The indications for the work process resource models have one of more of the
following attributes in addition to the common attributes described in “Attributes
common to all Feature Option 2 resource models”:
wp_completed
Count of completed work processes
wp_failures
Count of failing work processes
wp_number
Process number for the work process
wp_pid Process ID for the work process
wp_queue_count
Number of work items in the queue
wp_queue_percent
Queue length utilization (percent value)
wp_queue_time
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
126 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
wp_waiting
Count of waiting work processes
Attributes for JMX resource model indications
The indications for the JMX resource models have one or more of the following
attributes in addition to the common attributes described in “Attributes common to
all Feature Option 2 resource models” on page 126:
commit_duration
Commit duration
current_pool
Current size of the connections pool
HTTP_count
Number of HTTP connections
http_queue_size
Size of the message queue in the session communication layer
IIOP_count
Number of IIOP connections
jms_queue_size
Number of items currently in use on the JMS session
maximum
Current maximum value for the specified MBean Monitor
minimum
Current minimum value for the specified MBean Monitor
p4_count
Number of P4 connections
p4_queue_size
Number of items currently in use on the P4 session
process_time
Average amount of time in milliseconds that a message spends in the
message queue of the session communication layer. This is the amount of
time between the call of the send method and the actual writing of the
message in the socket.
server_status
Status of the cluster node. The supported value is ″unknown.″
sub_source
Label of the associated SAP system object
telnet_queue_size
Number of items currently in use on the telnet session
used_memory
Current, maximum, and minimum values of the memory used
usage_percent
Current usage of the thread pool, in percent
value Current value for the specified MBean Monitor
waiting_tasks_count
Number of runnable tasks waiting for available thread from the thread
pool to be executed
Chapter 2. Resource models 127
waiting_tasks_queue_overflow
Number of threads waiting to deposit a runnable task in the request queue
if it is full
waiting_tasks_queue_size
Capacity of the request queue where the tasks waiting for execution are
stored
webservices_queue_size
Number of items currently in use on the web services session
Logged information for work process resource models
The properties in the following table are logged for each status resource model
(such as Dialog Work Process Status).
128 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Managed resource Context Properties
<resource_model> Count
application_class
Class of the registered object
application_label
Label of the registered object
application_oid
Object identifier of the registered object
application_version
Version of the mySAP software running on the
managed resource
process_state
State of the work process
sub_origin*
Label of the registered object
sub_source
Label of the associated SAP system object
threshold
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
Number of work items in the queue
wp_queue_percent
Queue length utilization (percent value)
wp_queue_time
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.
Return codes
Table 9 on page 130 contains a list of resource model return codes, their
descriptions, and actions for resolving each code. These return codes are applicable
to the work process and JMX resource models. 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.
Chapter 2. Resource models 129
Table 9. 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.
11 211 The resource model is unable
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.
12 212 The resource model is unable
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.
13 213 The resource model is unable
to start. The resource model
is not supported by the
operating system on which
the application server is
running.
Run the application server on a
supported operating system.
14 214 The resource model is unable
to start. The resource model
was distributed to an object
other than a
mySAPAppServer object.
Distribute the resource model to a
mySAPAppServer object.
15 215 The resource model is unable
to start. Attributes were
requested for a resource, but
an instance of that resource
cannot be found.
Contact IBM Software Support.
16 216 The resource model is unable
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.
18 618 The resource model is unable
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.
130 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Table 9. Resource model return codes (continued)
Return
code
Logged
code
Description Action
20 620 The resource model is unable
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.
21 621 The resource model is unable
to start. The object context is
invalid.
The resource model cannot start.
The object context is invalid.
22 222 The resource model is unable
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.
140 940 The resource model is unable
to start. The object context is
not present. The resource
model might have been
distributed directly to an
endpoint.
Verify a valid object context.
Verify that the resource model
was distributed directly to an
endpoint.
141 941 The resource model is unable
to start. A syntax error was
detected while parsing the
parameters.
Check the parameter definitions.
142 942 The resource model was
distributed to a wrong type
of cluster node. Some
resource models can be
distributed only to a
Dispatcher and others only to
a Server cluster node.
Check the type of cluster node to
which the resource model was
distributed.
Chapter 2. Resource models 131
132 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Chapter 3. Tasks
The following tasks were updated or added for Feature Option 2:
v “Check Status” on page 134
v “Configure Event Adapter” on page 135
v “Discover J2EE” on page 140
v “Link JRE” on page 141
v “Rediscover J2EE” on page 142
v “Report Management Configuration” on page 143
© Copyright IBM Corp. 2005 133
Check Status
Description
Performs the following functions:
For application server:
– Checks the current status of a mySAP.com application server and updates
the icon state if necessary.
– Checks the status of the event adapters for this application server. The task
reports which of the adapters are installed for this application server. For
each installed adapter, this task reports whether the adapter is running or
stopped. For ITS server:
Checks the current status of a mySAP.com ITS server and updates the icon
state if necessary. For cluster node:
– Checks that a JRE is configured and that the JRE is at the minimum required
level.
– Checks the current status of a mySAP.com cluster node server and updates
the icon state if necessary. For all resources:
Reports the following logging information:
- Log ID used to uniquely identify log files
- Log and log directories
Authorization role
r3_user
Task library
v mySAP Configuration Tasks task library
v App Server icon, DB Server icon, ITS Server icon, Cluster Node icon
Target endpoint
mySAP.com object: mySAPAppServer, mySAPDBServer, mySAPITSServer,
mySAPJ2EEClusterNode
GUI data entry fields
None
134 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
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.
You can use this task to control the sleep time in the CCMS adapter when RFC
errors are detected. You configure the task parameter rather than manually editing
the event adapter .conf files.
The first time that you reconfigure an existing event adapter from the icon, the
RFC Retry Count, RFC Retry Delay, and RFC Timeout values are blank. Complete
the task without specifying values for these parameters to get the default values.
The next time that you reconfigure this event adapter these values appear.
Authorization role
r3_admin
Task library
v mySAP Configuration Tasks task 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:
Chapter 3. Tasks 135
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—
136 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
– 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.
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 16 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.
Chapter 3. Tasks 137
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.
138 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
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.
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.
Chapter 3. Tasks 139
Discover J2EE
Description
Discovers J2EE systems, J2EE instances, and J2EE cluster nodes and populates the
Tivoli management desktop with the corresponding objects.
Authorization role
r3_admin
Task library
v mySAP Configuration Tasks task library
v Monitoring for mySAP icon: Discover (J2EE)
Target endpoint
Managed node in the Tivoli region
GUI data entry fields
This task has the following parameters:
JMX Server Information: The Host, Port, User ID, and Password fields correspond
to similar fields on the user configuration profile window of the SAP J2EE Visual
Administrator tool. Type the values that correspond to an existing mySAP J2EE
engine Administrator account.
Host Host name of the JMX server that reports information about the SAP J2EE
instances. The host name can be simple name, fully qualified name, or IP
address.
Port Number of the port that the JMX Server uses. The port number must be at
least three numeric characters.
User ID
User ID to be used to connect to the JMX server. If you change the User
ID, you must enter a new Password.
Password
Password for the JMX User ID
Endpoint Information: The discover function uses endpoint information to locate a
Tivoli endpoint that is running a required version of the Java Runtime
Environment.
Endpoint Name
Endpoint to be used by the discover function. The endpoint must have
Java installed in the Java Runtime Environment Directory path.
Java Runtime Environment Directory
(Optional) Full path name to the Java installation directory (not including
the /bin directory). Use forward slashes only when entering the path.
Causes the Discover task to run the Link JRE task on the endpoint. This
field can be left blank if the mySAP Link JRE task has already been run on
the endpoint.
On a Windows operating system, if no drive is specified the SystemDrive
is used as a default.
140 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Link JRE
Description
This task has the following two purposes:
v Links a Linux on zSeries endpoint to the required 1.4 or higher 64-bit version of
the Java Runtime Environment.
v Sets the Java Runtime Environment on the endpoint to the version that is
required for J2EE JMX. This version must be at least 1.4.
This task can be executed from the Tivoli desktop on endpoints managing not only
a mySAPAppServer, but also a mySAPJ2EEClusterNode.
Changes to the Link JRE task in Feature Option 2 do not require you to run the
mySAP Link JRE task on a specified Tivoli endpoint before running the Discover
task. The Discover tasks asks for the location of a JRE 1.4, then runs the mySAP
Link JRE task for you.
Authorization role
r3_admin
Task library
mySAP Configuration Tasks task library
Target endpoint
Endpoint of a mySAPAppServer object or mySAPJ2EEClusterNode object
GUI data entry fields
This task has the following parameter:
Java Runtime Environment Directory
Directory where JRE 1.4 is installed
Chapter 3. Tasks 141
Rediscover J2EE
Description
Rediscovers existing J2EE systems, servers, and cluster nodes through the J2EE
interface, and creates corresponding Tivoli objects.
Authorization role
r3_admin
Task library
v mySAP Configuration Tasks task library
v Monitoring for mySAP icon: Rediscover (J2EE)
Target endpoint
Managed node in the Tivoli region
GUI data entry fields
This task has the following parameter:
SAP Systems
List of mySAP systems (mySAPsystem objects). The list includes only those
mySAP systems that reside in the local Tivoli region, and have previously
discovered mySAP J2EE resources or have been configured using the
Configure JMX function. You can select one or more systems on which to
perform rediscovery. To perform rediscovery on all systems, select all
systems or no systems. You can use this task to create a scheduled job by
selecting no systems.
142 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Report Management Configuration
Description
Provides a list of all software objects and key parameters about each object. The
report is organized by mySAPSystem. For each mySAPSystem , information is
reported for each mySAPDBServer, mySAPAppServer, mySAPITSServer,
mySAPJ2EEInstance, and mySAPJ2EEClusterNode owned by that mySAPSystem.
The report provides the following information:
mySAPSystem
v Object label
v Object type
v mySAP SID
v mySAP release
v mySAP system type
v RFC logon user ID
v RFC logon client
v RFC logon language
v JMX server user ID
v JMX server host name
v JMX server port
v endpoint used by J2EE discover function
mySAPDBServer
v Object label
v Object type
v Database type
v Database release
v mySAP database server host name
v mySAP database server IP address
v Management mode (local or remote)
v Managing host name
mySAPAppServer
v Object label
v Object type
v mySAP application server host name
v mySAP application server IP address
v Management mode (local or remote)
v Managing host name
v RFC call string (route string/IP address)
mySAPITSServer
v Object label
v Object type
v Type of ITS Server (A-Gate, W-Date, Single-Host)
v mySAP ITS server host name
v mySAP ITS server IP address
v Management mode (local)
Chapter 3. Tasks 143
v Managing host name
mySAPJ2EEInstance
v Object label
v Object type
v mySAP J2EE instance host name
v JMX server host name
v JMX server port
mySAPJ2EEClusterNode
v Object label
v Object type
v Cluster node type
v Cluster node ID
v Management mode (local or remote)
v Managing host name
v Cluster node host name
v JMX server host name
Managed servers are shown within each system.
Authorization role
r3_user
Task library
v mySAP Configuration Tasks task library
v Monitoring for mySAP icon: Report Management Configuration
Target endpoint
Managed node in the Tivoli region
GUI data entry fields
None
Usage notes
v Use the generated report to understand at a glance which servers are locally
managed and which servers are remotely managed, and to validate that the
management configuration is as desired.
v When calling Customer Support, you might be asked to provide this report.
144 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Appendix A. Monitoring data points and values
Table 10 lists the monitoring data points provided by SAP for the SAP NetWeaver
04 J2EE engines. The data points are expressed as object names in the JMX server
for cluster nodes. All of these monitoring data points are retrieved from the JMX
server by referencing j2eeType=SAP_MonitorPerNode. The object names shown in
the table illustrate values that can be used for the Object Name Pattern in the JMX
Generic Monitor resource model.
The threshold values in the table were suggested by SAP for each data point. The
resource models in IBM Tivoli Monitoring for Applications: mySAP.com, Version
5.1.0 with Feature Option 2 use these threshold values as a base set of monitoring
best practices.
Table 10. Monitoring data points and values
Cluster
node type Object name Attribute Type Unit
SAP default
threshold
Dispatcher /Kernel/Connections Manipulator/CurrentPoolSize
Value int connections 400
Dispatcher /Kernel/Connections Manipulator/HTTPConnectionsCount
Value int connections 100
Dispatcher /Kernel/Connections Manipulator/IIOPConnectionsCount
Value int connections 100
Dispatcher /Kernel/Connections Manipulator/P4ConnectionsCount
Value int connections 100
Dispatcher
and server
/Kernel/System Threads Pool/ThreadPoolPercentageUsage
Value int % 100
Dispatcher
and server
/Kernel/System Threads Pool/WaitingTasksCount
Value int tasks 600
Dispatcher
and server
/Kernel/System Threads Pool/WaitingTasksQueueOverflow
Value int tasks 100
Dispatcher
and server
/Kernel/System Threads Pool/WaitingTasksQueueSize
Value int tasks 1000
Server /Kernel/Application Threads Pool/ThreadPoolPercentageUsage
Value int % 100
Server /Kernel/Application Threads Pool/WaitingTasksCount
Value int tasks 600
Server /Kernel/Application Threads Pool/WaitingTasksQueueOverflow
Value int tasks 100
Server /Kernel/Application Threads Pool/WaitingTasksQueueSize
Value int tasks 1000
Dispatcher
and server
/Kernel/ClusterManagement/SessionContext Communication/General (SessionContext)/AverageSessionProcess
Value int ms none
Dispatcher
and server
/Kernel/ClusterManagement/SessionContext Communication/Data Per Processors/http/CurrentSessionQueueSize
Value int sessions none
© Copyright IBM Corp. 2005 145
Table 10. Monitoring data points and values (continued)
Cluster
node type Object name Attribute Type Unit
SAP default
threshold
Dispatcher
and server
/Kernel/ClusterManagement/SessionContext Communication/Data Per Processors/jms_provider/CurrentSessionQueueSize
Value int sessions none
Dispatcher
and server
/Kernel/ClusterManagement/SessionContext Communication/Data Per Processors/p4/CurrentSessionQueueSize
Value int sessions none
Dispatcher
and server
/Kernel/ClusterManagement/SessionContext Communication/Data Per Processors/telnet/CurrentSessionQueueSize
Value int sessions none
Dispatcher
and server
/Kernel/ClusterManagement/SessionContext Communication/Data Per Processors/webservices/CurrentSessionQueueSize
Value int sessions none
Dispatcher /Services/Memory
Info/UsedMemory
Value int MB 160
Server /Services/Memory/UsedMemory Value int MB 160
Dispatcher
and server
/Kernel/Configuration Manager/Commit Duration
CurrentDuration double ms 120000
Note: The object names are a single string. When entering object names, ignore the line breaks in the table.
146 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Appendix B. 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.
© Copyright IBM Corp. 2005 147
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, the IBM logo, Tivoli, the Tivoli logo, Tivoli Enterprise Console, and zSeries
are trademarks or registered trademarks of International Business Machines
Corporation in the United States, other countries, or both.
Windows is a registered trademarks of Microsoft® 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.
148 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
Index
AABAP instances
compatibility with J2EE 12
SAP 6.40 2
support 4
ABAP memory dumps 16
alerts, CCMS 4
attributesall resource models 126
JMX resource models 127
work process resource models 126
Average Session Process Time
indication 59
BBackground Work Process Completed
indication 27
Background Work Process Completed
Percent indication 28
Background Work Process Program
Failure indication 30
Background Work Process Queue
indication 29
Background Work Process Run Time
indication 92
Background Work Process Running
indication 25
Background Work Process Running
Percent indication 26
Background Work Process Status resource
model 24
Background Work Process Completed
indication 27
Background Work Process Completed
Percent indication 28
Background Work Process Program
Failure indication 30
Background Work Process Queue
indication 29
Background Work Process Running
indication 25
Background Work Process Running
Percent indication 26
Background Work Process Stopped
indication 26
Background Work Process Stopped
Percent indication 27
Background Work Process Waiting
indication 28
Background Work Process Waiting
Percent indication 29
parameters 31
thresholds 30
Background Work Process Stopped
indication 26
Background Work Process Stopped
Percent indication 27
Background Work Process Waiting
indication 28
Background Work Process Waiting
Percent indication 29
base installation 1
CCCMS
alerts 4
event adapter 3
event severity 4
certification, SAP BC-XAL 1
changes, product icon 7
Check Status task 134
cluster nodesicon functions 7
resource models 5
Commit Duration indication 68
compatibility 12
Configure Event Adapter task 16, 135
configuringJMX information 10
mySAPJ2EEInstance for JMX 11
mySAPSystem for JMX 11
creatingJ2EE objects 9
mySAP J2EE cluster node 9
mySAP J2EE instance 9
Current Pool indication 72
Current Value indication 78
customizing error monitoring 16
Ddata points and values, Monitoring 145
dependency problems, diagnosing 13
diagnosing dependency problems 13
Diagnostics menu 13
Dialog Work Process Completed
indication 37
Dialog Work Process Completed Percent
indication 38
Dialog Work Process Program Failure
indication 40
Dialog Work Process Queue
indication 39
Dialog Work Process Run Time
indication 92
Dialog Work Process Running
indication 35
Dialog Work Process Running Percent
indication 36
Dialog Work Process Status resource
model 34
Dialog Work Process Completed
indication 37
Dialog Work Process Completed
Percent indication 38
Dialog Work Process Program Failure
indication 40
Dialog Work Process Status resource
model (continued)Dialog Work Process Queue
indication 39
Dialog Work Process Running
indication 35
Dialog Work Process Running Percent
indication 36
Dialog Work Process Stopped
indication 36
Dialog Work Process Stopped Percent
indication 37
Dialog Work Process Waiting
indication 38
Dialog Work Process Waiting Percent
indication 39
parameters 41
thresholds 40
Dialog Work Process Stopped
indication 36
Dialog Work Process Stopped Percent
indication 37
Dialog Work Process Waiting
indication 38
Dialog Work Process Waiting Percent
indication 39
Discover J2EE task 140
Eenabling short dump monitoring 16
endpoints, Linux for zSeries 15
Enqueue Work Process Completed
indication 46
Enqueue Work Process Completed
Percent indication 47
Enqueue Work Process Program Failure
indication 49
Enqueue Work Process Queue
indication 48
Enqueue Work Process Run Time
indication 93
Enqueue Work Process Running
indication 44
Enqueue Work Process Running Percent
indication 45
Enqueue Work Process Status resource
model 43
Enqueue Work Process Completed
indication 46
Enqueue Work Process Completed
Percent indication 47
Enqueue Work Process Program
Failure indication 49
Enqueue Work Process Queue
indication 48
Enqueue Work Process Running
indication 44
Enqueue Work Process Running
Percent indication 45
© Copyright IBM Corp. 2005 149
Enqueue Work Process Status resource
model (continued)Enqueue Work Process Stopped
indication 45
Enqueue Work Process Stopped
Percent indication 46
Enqueue Work Process Waiting
indication 47
Enqueue Work Process Waiting
Percent indication 48
parameters 50
thresholds 49
Enqueue Work Process Stopped
indication 45
Enqueue Work Process Stopped Percent
indication 46
Enqueue Work Process Waiting
indication 47
Enqueue Work Process Waiting Percent
indication 48
error codes 16
event adaptersCCMS
parameters 3
severity 4
IDOC parameters 3
Syslog parameters 3
Ffeatures
ABAP instances 2
ABAP instances support 4
CCMS alerts 4
compatibility, ABAP and J2EE 12
configuring JMX 10
creating J2EE objects 9
event adaptersCCMS severity 4
parameters consistency 3
Feature Option 2 1
Feature Pack 1 14
icon changes 7
icon menus 6
J2EE instances 2
J2EE instances support 5
J2EE objects and icons 5
JMX resource models 20
JMX server 3
Linux for zSeries 15
prerequisite SAP maintenance
levels 12
profile managers 8
resource models 5
SAP 6.20 and 6.30 J2EE support 14
SAP BC-XAL 1
serviceability 13
short dump monitoring 16
tasks 8
work process resource models 19
functions2EE instances support 5
ABAP instances 2
ABAP instances support 4
CCMS alerts 4
compatibility, ABAP and J2EE 12
configuring JMX 10
functions (continued)creating J2EE objects 9
event adaptersCCMS severity 4
parameters consistency 3
Feature Pack 1 14
icon changes 7
icon menus 6
J2EE cluster node icon 7
J2EE instance icon 6
J2EE instances 2
J2EE objects and icons 5
JMX server 3
new 1
prerequisite SAP maintenance
levels 12
profile managers 8
resource models 5
SAP 6.20 and 6.30 J2EE support 14
SAP BC-XAL 1
serviceability 13
tasks 8
using new 3
HHTTP Connections indication 72
HTTP Session Queue Size indication 61
Iicon changes, product 7
icon functionsJ2EE cluster node 7
J2EE instance 6
icon menus, J2EE 6
iconschanges 7
J2EE 5
IDOC event adapter 3
IIOP Connections indication 73
improvements, serviceability 13
indications, attributesall resource models 126
JMX resource models 127
work process resource models 126
installation, base 1
instance icon functions, J2EE 6
instances, compatibility 12
JJ2EE
cluster node icon functions 7
creating objects 9
icon menus 6
icons 5
instance icon functions 6
objects 5
support, SAP 6.20 and 6.30 14
J2EE cluster nodescreating 9
resource models 5
J2EE engines, NetWeaver 04 145
J2EE instancecreating 9
J2EE instancescompatibility with ABAP 12
overview 2
support 5
j2eeType=SAP_MonitorPerNode 145
Java Management Extensions 3
JMS Session Queue Size indication 61
JMXconfiguring mySAPJ2EEInstance 11
configuring mySAPSystem 11
JMX information, configuring 10
JMX Java Cluster Node Status
indication 65
JMX server 3
JRE version 1.4 15
Llibrary, product v
Link JRE task 15, 141
Linux for zSeries endpoints 15
Long Running Work Process Status
resource model 91
Background Work Process Run Time
indication 92
Dialog Work Process Run Time
indication 92
Enqueue Work Process Run Time
indication 93
logging 96
parameters 95
Spool Work Process Run Time
indication 93
thresholds 95
Update Work Process Run Time
indication 94
Update2 Work Process Run Time
indication 94
Mmaintenance levels, prerequisite SAP 12
manuals v
Maximum indication 78
Minimum indication 79
monitoringcompatibility 12
short dumps 16
Monitoring data points 145
Monitoring values 145
mySAP JMX Application Thread Manager
resource model 52
logging 55, 69
parameters 55
thresholds 55
Usage Percent indication 53
Waiting Tasks Count indication 53
Waiting Tasks Queue Overflow
indication 54
Waiting Tasks Queue Size
indication 54
mySAP JMX Cluster Manager resource
model 58
Average Session Process Time
indication 59
150 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
mySAP JMX Cluster Manager resource
model (continued)HTTP Session Queue Size
indication 61
JMS Session Queue Size
indication 61
logging 63
P4 Session Queue Size indication 60
parameters 63
Telnet Session Queue Size
indication 59
thresholds 62
Webservices Session Queue Size
indication 60
mySAP JMX Cluster Node Status
resource model 65
JMX Java Cluster Node Status
indication 65
logging 66
parameters 66
thresholds 66
mySAP JMX Configuration Manager
resource model 68
Commit Duration indication 68
parameters 69
thresholds 69
mySAP JMX Connections Manipulator
Manager resource model 71
Current Pool indication 72
HTTP Connections indication 72
IIOP Connections indication 73
logging 74
P4 Connections indication 73
parameters 74
thresholds 74
mySAP JMX Generic Monitor resource
model 77
Current Value indication 78
data points and values 145
logging 80
Maximum indication 78
Minimum indication 79
Object Name Pattern 145
parameters 80
thresholds 79
mySAP JMX Memory Info Service
resource model 82
logging 83
parameters 83
thresholds 83
Used Memory indication 82
mySAP JMX System Thread Manager
resource model 85
logging 88
parameters 88
thresholds 88
Usage Percent indication 86
Waiting Tasks Count indication 86
Waiting Tasks Queue Overflow
indication 87
Waiting Tasks Queue Size
indication 87
NNetWeaver 04 J2EE engines 145
OObject Name Pattern 145
objectscreating J2EE 9
J2EE 5
PP4 Connections indication 73
P4 Session Queue Size indication 60
prerequisite SAP maintenance levels 12
product history v
product icon changes 7
profile managerschanged 8
new 8
profileschanged 8
new 8
properties, Feature Pack 1 128
RRediscover J2EE task 142
Report Management Configuration
task 143
resource modeldata points and values 145
mySAP JMX Generic Monitor 145
Object Name Pattern 145
resource modelsBackground Work Process Status 24
Dialog Work Process Status 34
Enqueue Work Process Status 43
indication attributescommon 126
JMX 127
work process 126
J2EE cluster nodes 5
JMX 20
logged properties, Feature Pack
1 128
Long Running Work Process
Status 91
mySAP JMX Application Thread
Manager 52
mySAP JMX Cluster Manager 58
mySAP JMX Cluster Node Status 65
mySAP JMX Configuration
Manager 68
mySAP JMX Connections Manipulator
Manager 71
mySAP JMX Generic Monitor 77
mySAP JMX Memory Info Service 82
mySAP JMX System Thread
Manager 85
return codes 130
Spool Work Process Status 98
Update Work Process Status 107
Update2 Work Process Status 117
work process 19
return codes, resource model 130
SSAP 6.20 and 6.30 J2EE support 14
SAP 6.40ABAP instances 2
about 1
J2EE instances 2
support for ABAP instances 4
support for J2EE instances 5
SAP BC-XAL certification 1
SAP maintenance levels, prerequisite 12
serviceability improvements 13
short dump monitoringcustomizing 16
enabling 16
event classes 17
event slots 17
overview 16
Spool Work Process Completed
indication 101
Spool Work Process Completed Percent
indication 102
Spool Work Process Percent Queue
indication 103
Spool Work Process Program Failure
indication 104
Spool Work Process Run Time
indication 93
Spool Work Process Running
indication 99
Spool Work Process Running Percent
indication 100
Spool Work Process Status resource
model 98
parameters 105
Spool Work Process Completed
indication 101
Spool Work Process Completed
Percent indication 102
Spool Work Process Percent Queue
indication 103
Spool Work Process Program Failure
indication 104
Spool Work Process Running
indication 99
Spool Work Process Running Percent
indication 100
Spool Work Process Stopped
indication 100
Spool Work Process Stopped Percent
indication 101
Spool Work Process Waiting
indication 102
Spool Work Process Waiting Percent
indication 103
thresholds 104
Spool Work Process Stopped
indication 100
Spool Work Process Stopped Percent
indication 101
Spool Work Process Waiting
indication 102
Spool Work Process Waiting Percent
indication 103
support, SAP 6.20 and 6.30 J2EE 14
Syslog event adapter 3
Index 151
Ttasks
changed 8
Check Status 134
Configure Event Adapter 135
Discover J2EE 140
Link JRE 141
new 8
Rediscover J2EE 142
Report Management
Configuration 143
Telnet Session Queue Size indication 59
UUpdate Work Process Completed
indication 110
Update Work Process Completed Percent
indication 111
Update Work Process Program Failure
indication 113
Update Work Process Queue
indication 112
Update Work Process Run Time
indication 94
Update Work Process Running
indication 108
Update Work Process Running Percent
indication 109
Update Work Process Status resource
model 107
parameters 114
thresholds 113
Update Work Process Completed
indication 110
Update Work Process Completed
Percent indication 111
Update Work Process Program Failure
indication 113
Update Work Process Queue
indication 112
Update Work Process Running
indication 108
Update Work Process Running Percent
indication 109
Update Work Process Stopped
indication 109
Update Work Process Stopped Percent
indication 110
Update Work Process Waiting
indication 111
Update Work Process Waiting Percent
indication 112
Update Work Process Stopped
indication 109
Update Work Process Stopped Percent
indication 110
Update Work Process Waiting
indication 111
Update Work Process Waiting Percent
indication 112
Update2 Work Process Completed
indication 120
Update2 Work Process Completed
Percent indication 121
Update2 Work Process Program Failure
indication 123
Update2 Work Process Queue
indication 122
Update2 Work Process Run Time
indication 94
Update2 Work Process Running
indication 118
Update2 Work Process Running Percent
indication 119
Update2 Work Process Status resource
model 117
parameters 124
thresholds 123
Update2 Work Process Completed
indication 120
Update2 Work Process Completed
Percent indication 121
Update2 Work Process Program
Failure indication 123
Update2 Work Process Queue
indication 122
Update2 Work Process Running
indication 118
Update2 Work Process Running
Percent indication 119
Update2 Work Process Stopped
indication 119
Update2 Work Process Stopped
Percent indication 120
Update2 Work Process Waiting
indication 121
Update2 Work Process Waiting
Percent indication 122
Update2 Work Process Stopped
indication 119
Update2 Work Process Stopped Percent
indication 120
Update2 Work Process Waiting
indication 121
Update2 Work Process Waiting Percent
indication 122
Usage Percent indication 53, 86
Used Memory indication 82
WWaiting Tasks Count indication 53, 86
Waiting Tasks Queue Overflow
indication 54, 87
Waiting Tasks Queue Size indication 54,
87
Webservices Session Queue Size
indication 60
152 IBM Tivoli Monitoring for Applications: mySAP.com: Documentation Supplement for Feature Option 2
����
Printed in USA
SC32-9421-00