boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 2
Legal Notice
The information contained in this document is subject to change without notice.
Warranty
blue elephant systems GmbH makes no warranty of any kind with regard to this document, including, but not
limited to, the implied warranties of merchantability and fitness for a particular purpose. blue elephant
systems GmbH shall not be held liable for errors contained herein or direct, indirect, special, incidental or
consequential damages in connection with the furnishing, performance, or use of this material whether
based on warranty, contract, or other legal theory.
Copyright Notices
©Copyright 2014 blue elephant systems GmbH.
This document contains proprietary information and is protected by copyright. All rights are reserved. No part
of this document may be copied, reproduced, translated to another language, transferred to electronic
media, or transferred into machine readable format without the prior written consent of blue elephant
systems GmbH.
Trademark Notices
Java™ is a U.S. trademark of Sun Microsystems, Inc.
Linux is a U.S. registered trademark of Linus Torvalds.
Microsoft®, Windows®, Windows®2000, Windows Server™ 2003, Windows Server 2008
Windows Vista and Windows NT® are either registered trademarks or trademarks of Microsoft Corporation in
the Unites states and/or other countries.
UNIX is a registered trademark of the Open Group.
Sun™ and Solaris™ are trademarks of Sun Microsystems, Inc.
Written and developed by blue elephant systems GmbH, Germany.
Contact
blue elephant systems GmbH Zettachring 2 D-70567 Stuttgart Germany http://www.blue-elephant-systems.com Phone: +49 711 400425-00
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 3
Table of Contents
1. Overview 5
2. SAPJCo3 Requirements 6
3. SAP User Login 7
4. SAPMPI Installation 8
4.1 SAP Java Connector 3.0 8
4.1.1 Linux 8
4.1.2 Windows 9
4.2 Boom Agent Configuration 9
4.2.1 Linux 9
4.2.2 Windows 10
4.3 SAPMPI Package 11
5. SAPMPI Configuration 12
5.1 SAP Instance 12
5.2 Property Files 12
5.2.1 SAP_ccms_config.props 12
5.2.2 SAP_ccms_pattern.props 14
5.2.3 SAP_ccms_perf.props 14
5.3 Trigger Policy 15
6. Installation & Configuration Steps Summary 16
7. New in Version 2.20 17
8. SAPMPI Actions 18
9. CCMS Pattern 20
9.1 Pattern Definition 20
9.1.1 Attribute <KEY> 20
9.1.2 Attribute <POLICYNAME> 20
9.2 Pattern Configuration 21
9.2.1 Configuration using the DiscoverAll Method 21
9.2.2 Configuration using SAP GUI 22
10. CCMS Performance Data 23
10.1 Configuration 23
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 4
10.2 Performance Storage 24
11. CCMS Policies 25
11.1 Monitor Policy 25
11.2 Indication Policy 26
11.3 Optional/Additional Variables 27
12. SAPMPI Deinstallation 28
13. Appendix 29
13.1 More Connection Attributes 29
13.2 Example Policies 31
13.3 Property Files 33
13.3.1 Default Configuration File 33
13.3.2 Default CCMS Pattern File 33
13.3.3 Default CCMS PerformancFile 35
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 5
1. Overview The boom SAPMPI connects to a Computing Center Management System (CCMS) on a SAP system via the
RFC interface. The SAPMPI has access to any CCMS data that are available on the specific system and is
able to monitor all these values.
How does it work:
first the SAPMPI connects to an existing CCMS system via TCP/IP using the RFC Interface
it then establishes an XMI (external Monitoring Interface) session
calls various XAL (external Interface for Alert Management) functions to retrieve monitoring objects
matches these objects against the requested pattern
fetches any applicable status and performance data
ends the XMI session
and finally disconnects from the CCMS
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 6
2. SAPJCo3 Requirements The SAPJCo3 supports SAP (R/3) systems from Release 3.1H upwards, and other mySAP components that
have BAPI or RFMs (Remote Function Modules).
JCo3.0 Release with Java 5 Standard Edition
Windows x86 32-Bit (Versions: Windows XP, Windows Server 2003, Windows Vista, Windows 7) [SUN
JSE 1.5.0]
Windows x64 64-Bit (Versions: Windows Server 2003, Windows Vista, Windows Server 2008, Windows
Server 2008 R2, Windows 7) [SUN JSE 1.5.0]
Windows Itanium 64-Bit (Versionen: Windows Server 2003, Windows Server 2008, Windows Server 2008
R2) [SUN JSE 1.5.0]
Linux x86 32-Bit (Versions: SuSE SLES9, SuSE SLES10, RedHat EL4, RedHat EL5) [SUN JSE 1.5.0]
Linux x86 64-Bit (Versions: SuSE SLES9, SuSE SLES10, RedHat EL4, RedHat EL5) [SUN JSE 1.5.0]
Linux Itanium 64-Bit (Versionen: SuSE SLES9, SuSE SLES10, RedHat EL4, RedHat EL5) [SUN JSE
1.5.0]
Linux zSeries 64-Bit (Versions: SuSE SLES9, SuSE SLES10, RedHat EL5) [IBM JSE 1.5.0]
Linux Power PC 64-Bit (Versions: SuSE SLES9, SuSE SLES10, RedHat EL4, RedHat EL5) [IBM JSE
1.5.0]
AIX 64-Bit (Versionen: 5.2, 5.3, 6.1, 7.1) [IBM JSE 1.5.0]
HP-UX PA-RISC (Versionen: HP-UX B11.11, B11.23, B11.31) [HP JSE 1.5.0]
HP-UX Itanium (Versionen: HP-UX B11.23, B11.31) [HP JSE 1.5.0]
Solaris SPARC 64-Bit (Versionen: Solaris 9, 10) [SUN JSE 1.5.0]
Solaris x64 (Version: Solaris 10) [SUN JSE 1.5.0]
Apple MAC OS Intel 32-Bit (Versionen: 10.4, 10.5) [Apple JSE 1.5.0]
Apple MAC OS Intel 64-Bit (Versionen: 10.4, 10.5) [Apple JSE 1.5.0]
z/OS 64 Bit (Versionen: 1.8, 1.9) [IBM JSE 1.5.0]
IBM i 64-Bit (Versionen: V5R4, V6R1) [IBM JSE
JCo3.0 Release with Java 6 Standard Edition
Windows x86 32-Bit (Versions: Windows XP, Windows Server 2003, Windows Vista, Windows Server
2008, Windows 7) [SUN JSE 1.6.0]
Windows x64 64-Bit (Versions: Windows XP, Windows Server 2003, Windows Vista, Windows Server
2008, Windows Server 2008 R2, Windows 7) [SUN JSE 1.6.0]
Windows Itanium 64-Bit (Versionen: Windows Server 2003, Windows Server 2008, Windows Server 2008
R2, Windows 7) [SUN JSE 1.6.0]
Linux x86 32-Bit (Versionen: SuSE SLES10, RedHat EL5) [SUN JSE 1.6.0]
Linux x86 64-Bit (Versionen: SuSE SLES10, RedHat EL5) [SUN JSE 1.6.0]
Linux Itanium 64-Bit (Versionen: SuSE SLES10, RedHat EL5) [SUN JSE 1.6.0]
Linux zSeries 64-Bit (Versionen: SuSE SLES10, RedHat EL5) [IBM JSE 1.6.0]
Linux Power PC 64-Bit (Versions: SuSE SLES10, RedHat EL5) [IBM JSE 1.6.0]
AIX 64-Bit (Versionen: 5.3, 6.1, 7.1) [IBM JSE 1.6.0]
HP-UX Itanium (Versionen: HP-UX B11.23, B11.31) [HP JSE 1.6.0]
Solaris SPARC 64-Bit (Versionen: Solaris 10) [SUN JSE 1.6.0]
Solaris x64 (Version: Solaris 10) [SUN JSE 1.6.0]
Apple MAC OS Intel 64-Bit (Version: 10.5) [Apple JSE 1.6.0]
z/OS 64 Bit (Versionen: 1.8, 1.9) [IBM JSE 1.6.0]
IBM i 64-Bit (Versionen: V6R1, V7R1) [IBM JSE 1.6.0]
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 7
3. SAP User Login In order to access the CCMS of a SAP System you will require a valid SAP RFC user with the following
access rights:
Description Option VALUE
S_RFC
Authorization
Check for RFC access Activity * (or execute)
Name of RFC to be protected SALX, SXHC, SXMI, SYST
Type of RFC object to be
protected
FUGR
(Function group)
S_XMI_LOG Internal access authorization
for XMI log Access method for XMI log *
S_XMI_PROD Auth. for external
management interfaces
(XMI)
XMI logging: company name Blue Elephant Systems GmbH
Product boom
Interface ID *
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 8
4. SAPMPI Installation
4.1 SAP Java Connector 3.0 First you have to download the SAP JCo installation files from SAP Service Marketplace at
service.sap.com/connectors.
Because the SAP JCo Package contains native libraries, make sure you select the correct package according
to your operation system and the installed java version! See SAP note #1077727 for detailed information on
supported platforms.
PLEASE NOTE: This download has to be done because SAP does not allow the redistribution of any connector!
4.1.1 Linux
The SAPJCo3 package for Linux contains exactly one jar and one library file:
OS FILES DESCRIPTION
Linux sapjco3.jar JCo Java library (platform independent)
libsapjco3.so The JCo runtime library is used by the JCo Java library (platform
dependent).
Installation steps:
1. Unzip SAPJCo-xxx.zip and put both libraries in the /boom_agent/ directory.
2. Check the library dependencies with ldd libsapjco3.so
You might also check library path and symbolic links.
3. Check if SAPJCo3 is running correctly:
java –jar sapjco3.jar –stdout
The result should not contain any exceptions!
root@boom:/opt/boom_agent# ldd libsapjco3.so
linux-gate.so.1 => (0xb7771000)
libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb70cc000)
librt.so.1 => /lib/i686/cmov/librt.so.1 (0xb70c3000)
libuuid.so.1 => /lib/libuuid.so.1 (0xb70be000)
libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb6f77000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb6e82000)
libm.so.6 => /lib/i686/cmov/libm.so.6 (0xb6e5c000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb6e3e000)
libpthread.so.0 => /lib/i686/cmov/libpthread.so.0
(0xb6e24000)
/lib/ld-linux.so.2 (0xb7772000)
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 9
4.1.2 Windows
The SAPJCo3 package for windows contains exactly one jar and one library file:
OS FILES DESCRIPTION
Windows sapjco3.jar JCo Java library (platform independent)
libsapjco3.dll The JCo runtime library is used by the JCo Java library (platform
dependent).
Installation steps:
1. Unzip SAPJCo-xxx.zip and put both libraries in the /boom_agent/ directory.
2. Check if SAPJCo3 is running correctly:
java –jar sapjco3.jar –stdout
The result should not contain any exceptions!
4.2 Boom Agent Configuration
4.2.1 Linux
Change the boom agent startup script /boom_agent/boom_agt:
1. Stop the boom agent!
2. Change the boom agent startup script.
Please note: The example line can look slightly different for every boom agent. There might be also
multiple lines affected!
Find all: -jar boom_agent.jar
Replace with: -cp boom_agent.jar:sapjco3.jar com.blixx.agent.AgentEngine
PLEASE NOTE: The separator for Linux between boom_agent.jar and spjco3.jar is a colon (:) !
Example old line:
nohup java -DBOOMAGENTPROC -jar boom_agent.jar 2>&1 >boom_agent_start.log &
New line:
nohup java -DBOOMAGENTPROC -cp boom_agent.jar:sapjco3.jar com.blixx.agent.AgentEngine 2>&1 >boom_agent_start.log &
3. Start boom agent!
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 10
4.2.2 Windows
Change the boom agent startup script /boom_agent/boom_agt.cmd:
1. Stop the boom agent service!
2. Change the boom agent startup script.
Please note: The example line can look slightly different for every boom agent. There might be also
multiple lines affected!
Find all: -jar boom_agent.jar
Replace with: -cp boom_agent.jar;sapjco3.jar com.blixx.agent.AgentEngine
PLEASE NOTE: The separator for Windows between boom_agent.jar and spjco3.jar is a semicolon (;) !
Example old line:
START "boom_agent" /i java -jar boom_agent.jar
New line:
START "boom_agent" /i java -cp boom_agent.jar;sapjco3.jar com.blixx.agent.AgentEngine
3. Start boom agent service!
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 11
4.3 SAPMPI Package
Extract the SAPMPI Package SAPMPI_v2.xx.zip to a temporary directory and import all necessary
components to the boom server using the Import MPI View of the boom GUI.
PLEASE NOTE: Make sure you only import the necessary elements. One example is the SAPMPI-Basic Binary
Package. This package is only needed once and can be deployed multiple times.
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 12
5. SAPMPI Configuration
5.1 SAP Instance
The next step after the SAPMPI Package has been imported successfully is to make sure, that the boom
agent is able to establish a connection to the SAP System. This can be done by adding a SAP Instance to the
boom agent.
To add a SAP Instance you have to open the Action View in the boom GUI and double-click on the Action
SAP Add Instance:
adjust Optional
Parameters
select the appropriate
boom agent
click on execute
All required information will be stored in a text file on the boom agent side. The property file is located in the
boom agent directory:
/boom_agent/<instanceName>.lprops
PLEASE NOTE: The password is encrypted!
For more information about Actions see Chapter New in Version 2.20
1. Fix:
Timestamp does now consider Daylight Saving Time.
2. Alert Severity:
The SAP Alert Status (severity) is now fetched from SAP and accessible inside the Policy via optional
Variable <$ALERT_STATUS>.
For more information see Chapter 11.3 Optional/Additional Variables.
SAPMPI Actions.
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 13
5.2 Property Files
5.2.1 SAP_ccms_config.props
All parameters that are needed to connect to a SAP System are defined in the SAP_ccms_config.props.
This is a standard configuration file with minimum attributes:
Connection and Login Attributes:
ATTRIBUTE DEFAULT VALUE DESCRIPTION
SAP_INSTANCE none Describes the connection attributes of the SAP
System. For more information see Chapter SAP Instance.
EXTCOMPANY Blue Elephant
Systems GmbH
Optional
EXTPRODUCT boom Optional
INTERFACE XAL Optional
EXTERNAL_USER_NAME SAPMPI Optional
VERSION 1.0 Optional
MAX_TREE_DEPTH 0 Optional
VIS_ON_USR_LEVEL 3 Optional
CCMS Attributes:
ATTRIBUTE DEFAULT VALUE DESCRIPTION
CCMS_ENABLED False Enable/disable CCMS monitoring
CCMS_MONITOR_SET none The name of the SAP Monitor-Set we want to
#-------------------------
# SAP Instance
#-------------------------
SAP_INSTANCE=<INSTANCE_NAME>
#-------------------------
# CCMS Monitor-Set(RZ20)
#-------------------------
CCMS_ENABLED=true
CCMS_MONITOR_SET=SAP CCMS Monitor Templates
CCMS_MONITOR_NAME=*
CCMS_PERF_ENABLED=true
#----------------------------
# DATA COLLECTOR (milliseconds)
#----------------------------
DB_INTERVAL = 240000
#----------------------------
# LOGGING
#----------------------------
LOGLEVEL=1
MAX_LOGDAYS=2
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 14
access.
CCMS_MONITOR_NAME * All SAP Monitors that can be found inside the
given SAP Monitor Set.
CCMS_SEND_INIDCATIONS True Enable/disable sending messages to the BOOM
Indication Browser
CCMS_PERF_ENABLED False Enable/disable Performance Collection
DB_INTERVAL 60000 Interval of the data collector
Logging Attributes:
ATTRIBUTE DEFAULT VALUE DESCRIPTION
LOGLEVEL 1
MAX_LOGDAYS 2 Number of history log files
Optional Destination Attributes:
You can add any available SAP connection properties that are available for SAP JCo3. The properties must
be places right after the line SAP_INSTANCE=<INSTANCE_NAME>.
PLEASE NOTE: The properties must be the same that the JCo3 libraries expect.
ATTRIBUTE DESCRIPTION
jco.client.trace Enable/disable RFC trace (0 or 1)
jco.client.lcheck Enable/Disable logon check at open time, 1 (enable) or 0 (disable)
…
For more information about additional connection attributes see Chapter More Connection Attributes.
5.2.2 SAP_ccms_pattern.props
All values you want to fetch from the SAP System must be defined in the SAP_ccms_pattern.props:
#------------------------------------------
# BUFFERS
#------------------------------------------
*::*::Program::DirectoryUsed|SAP_Program_DirectoryUsed
*::*::Program::HitRatio|SAP_Program_HitRatio
*::*::Program::SpaceUsed|SAP_Program_SpaceUsed
*::*::Program::Swap|SAP_Program_Swap
… etc.
For more Information on how to define CCMS Pattern see Chapter CCMS Pattern.
5.2.3 SAP_ccms_perf.props
All values want to see as performance data must be defined in the SAP_ccms_perf.props:
#----------------------------------------------
# BUFFERS
#----------------------------------------------
SAP_BUFFER|DOUBLE|ProgramDirectoryUsed|SAP_Program_DirectoryUsed
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 15
SAP_BUFFER|DOUBLE|ProgramHitRatio|SAP_Program_HitRatio
SAP_BUFFER|DOUBLE|ProgramSpaceUsed|SAP_Program_SpaceUsed
SAP_BUFFER|DOUBLE|ProgramSwap|SAP_Program_Swap
… etc.
For more Information on how to configure performance data see Chapter CCMS Performance Data.
5.3 Trigger Policy
Make sure that the defined property files in the Monitor Call are correct!
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 16
6. Installation & Configuration Steps Summary Before you start with the configuration of the SAPMPI, make sure that the boom agent you are going to deploy
the SAPMPI has the SAPJCo3 Connector installed. The best and easiest configuration sequence is:
1. Deploy the SAPMPI-Basic Assignments (contains sapmonitor.jar library).
Make sure the boom agent is still running correctly.
2. Deploy the SAPMPI Actions.
3. Run action “Get Version” to test if the SAPMPI is working at all.
4. Run action “SAP Add Instance” and add all necessary SAP Instances.
Here you can see if the boom agent is able to connect correctly to the SAP System.
If there are some problems here, please re-check you login credentials.
If the SAP Instance has been added successfully, you can go on with the following steps:
5. Adjust the following property files:
o SAP_ccms_config.props
o SAP_ccms_pattern.props.
PLEASE NOTE: The SAP_ccms_perf.props must be configured and deployed after all data are fetched
and processed correctly. Otherwise we might have a lot of unusable data in the boom Performance
Database!
6. Deploy the SAPMPI Assignments. Make sure the package contains the following elements:
o SAPMPI Binary Package
o all necessary Policies
o PLEASE NOTE: During installation and configuration of the SAPMPI, it might be better NOT to
include the Trigger Policy here!
7. Check the Policy Interval: The best interval for configuration might be 1 minute.
8. Deploy the Trigger Policy.
Depending on the defined Trigger Policy Interval and on the amount of data that have to be fetched from the
SAP System, it might take a while until you can see the first indications in the Indication Browser.
9. If there are some SAP data missing, check the following:
o SAP_ccms_pattern.props -> check if the key and the Policy Name is correctly
o Check if the defined Policy exists and is deployed
o In case of an Indication Policy, check the field Object in the Filter section.
This field must contain exactly the key you have defined in the pattern file.
If all CCMS data are fetched correctly, you can go on with the following steps:
10. Configure the SAP_ccms_perf.props file
11. Activate the performance data inside the Trigger Policy
12. Redeploy the Trigger Policy
If all Performance Data are correctly collected in the boom performance database, you can do the last steps:
13. Un-Deploy the Trigger Policy
14. Check/update the Policy Interval
15. Move the Trigger Policy to the SAPMPI Assignment and select Redeploy when you will be asked.
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 17
7. New in Version 2.20 3. Fix:
Timestamp does now consider Daylight Saving Time.
4. Alert Severity:
The SAP Alert Status (severity) is now fetched from SAP and accessible inside the Policy via optional
Variable <$ALERT_STATUS>.
For more information see Chapter 11.3 Optional/Additional Variables.
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 18
8. SAPMPI Actions
Name Get Version
Description Returns the version of the installed SAPMPI
Command IAction com.na.boom.sap.mon.SAPMPIAction VERSION
Optional Parameters None
Name SAP Add Instance
Description Use this action to add a SAP Instance to a boom agent. This Instance contains
all needed attributes to connect to the SAP System. If the connection was
successfully established, you will get back the connection attributes from the
SAP System.
All login credentials will be saved inside a text file (password encrypted!):
/boom_agent/<instanceName>.lprops.
PLEASE NOTE: If the SAP System is behind a SAP router, we have to use a
router string.
Command IAction com.na.boom.sap.mon.SAPMPIAction ADD_INSTANCE
Optional Parameters <client> <user> <password> <host> <System_number> <language>
<instance_name>
Name SAP Delete Instance
Description Use this action if you want to remove an existing SAP Instance from a boom
agent.
Command IAction com.na.boom.sap.mon.SAPMPIAction DELETE_INSTANCE
Optional Parameters <instance_name>
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 19
Name SAP List Instances
Description This action will list all existing SAP Instances for the selected agent(s). It will
NOT test if the Instances can connect to the SAP System.
Command IAction com.na.boom.sap.mon.SAPMPIAction GET_INSTANCE
Optional Parameters none
Name SAP Test Instance
Description To test if an existing SAP Instance is still valid. Running this action will first
connect and then disconnect from the SAP System. If the connection was
successful the connection attributes from the SAP System will be reported
back.
Command IAction com.na.boom.sap.mon.SAPMPIAction TEST_INSTANCE
Optional Parameters <instance_name>
Name SAP Test Login
Description This action will establish a connection to a SAP System using the given login
parameters. If the connection was successful, the action will disconnect and
the connection attributes from the SAP System will be reported back.
Command IAction com.na.boom.sap.mon.SAPMPIAction TEST_CONNECTION
Optional Parameters <client> <user> <password> <host> <port> <language>
Name HELP
Description Displays the usage of SAPMPI Action
Command IAction com.na.boom.sap.mon.SAPMPIAction
Optional Parameters None
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 20
9. CCMS Pattern
9.1 Pattern Definition SAPMPI Patterns are used to map the SAP data to the appropriate Policies. That means you have to create a
pattern for each SAP value you want to monitor. No indication will be generated without this mapping.
The SAPMPI Pattern consists of the two elements <KEY> and <POLICYNAME> that are separated by ‘|’.
The <KEY> is used to identify the SAP value and consists of the 4 attributes separated by two colons -> :: .
The <POLICYNAME> defines which boom Policy will handle the SAP data.
Example:
N4S::srv-sap01_N4S_42:: Dialog::SAP_UsersLoggedIn|SAP_Dialog_UsersLoggedIn
9.1.1 Attribute <KEY>
The <KEY> is used to identify the SAP value. It consists of the following 4 attributes:
1. <SYSID>
2. <MTCNAME>
3. <OBJECTNAME>
4. <MTNAMESHRT>
All attributes are separated by two colons -> ::.
There are 2 possibilities to get all necessary data to be able to create patterns. You can get all data from the
SAP GUI or use can use the DiscoverAll (*::*::*::*) pattern.
9.1.2 Attribute <POLICYNAME>
The <POLICYNAME> defines which policy is responsible for which value. If we take the example from above,
the Policy that is processing the data is named SAP_Dialog_UsersLoggedIn.
<POLICYNAME> = SAP_Dialog_UsersLoggedIn
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 21
9.2 Pattern Configuration There are two possibilities how to get all necessary information to be able to configure all CCMS Patterns.
9.2.1 Configuration using the DiscoverAll Method
After the first installation of the SAP MPI this is a nice and easy way to get all necessary information to build
the pattern property file. Just activate the DiscoverAll pattern in the SAP_ccms_pattern.props and run the
SAPMPI. Using this pattern, you will get all available data out of the SAP System. Please note, that this might
take a while.
DiscoverAll pattern = *::*::*::*
Steps:
The Trigger Policy must be linked to the correct property files.
Check Data Pre-Selection in the SAP_ccms_config.props file.
The SAPMPI Assignment containing the Binary Package and Basic Policies must be deployed on the
boom agent.
The indication object is exactly the KEY we need for out pattern! Just open the indication details by double-
click on this element and copy the Object to your SAP_ccms_pattern.props file.
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 22
9.2.2 Configuration using SAP GUI
Another possibility how to get the pattern details is via the SAP GUI. If you want to add just a few more
elements to your property file, this way is recommended.
Open the SAP GUI and go to the MTE Class you want to monitor. Right click on the value to open the
Property Dialog:
The MTE Class Properties contain multiple elements separated by /. If the MTE Class contains 4 elements,
than this is exactly what we need for our <KEY>. If the MTE Class Properties contains more than 4 elements,
you have to take the first two and the last two elements like in our example:
<KEY> = N4S::srv-sap01_N4S_42::Dialog::UsersLoggedIn
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 23
10. CCMS Performance Data
10.1 Configuration
The Pattern contains of exactly 4 elements:
<PerformanceClassName>|<Type>|<ColumnName>|<PolicyName>
Performance Class Name Table name in the Performance Database.
Type DOUBLE|BIGINT
Column Name Column name
Policy Name Responsible Policy
Example:
#----------------------------------------------
# BUFFERS
#----------------------------------------------
SAP_BUFFER|DOUBLE|ProgramDirectoryUsed|SAP_Program_DirectoryUsed
SAP_BUFFER|DOUBLE|ProgramHitRatio|SAP_Program_HitRatio
SAP_BUFFER|DOUBLE|ProgramSpaceUsed|SAP_Program_SpaceUsed
SAP_BUFFER|DOUBLE|ProgramSwap|SAP_Program_Swap
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 24
10.2 Performance Storage
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 25
11. CCMS Policies
11.1 Monitor Policy
When defining a Monitor Policy you have to make sure that:
1. Policy with Reset is set to YES
2. Monitor Type is set to EXTERNAL
3. De-Duplicate KeyOnly is activated for all conditions.
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 26
11.2 Indication Policy
Every Indication Policy must have minimum 2 conditions in order to cover the following 2 situations:
1. Empty SAP MTE Class
MTE Class is empty if the SAP Field does not contain any message. That means there is no Error or
any other message available for this Policy in the SAP System.
In this case the Indication will be sent with severity=unknown.
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 27
2. SAP MTE Class contains some data
That means there is an error or any other message available in the SAP System. In this case, some
text will be fetched from the SAP System and sent as an indication with severity=normal.
PLEASE NOTE: The Filter Section has to be defined carefully for each condition inside an Indication Policy.
Make sure that:
Application is set to SAP
Indication Group is set to *
Object is set to your <KEY>
11.3 Optional/Additional Variables Our additional variables or also called “Magic Variables” can be used inside any Policy:
Variable Name Description
<$SAPHOST>
<$SAPUSER>
<$SAPSYSNR>
<$SAPSYSID>
<$SAPDESTINATION>
<$SAPLANG>
<$MONITOR_SET>
<$MONITOR_NAME>
<$OBJECTNAME>
<$MTNAMESHRT>
<$UNIT> sec, %, …
<$INFO>
<$CUSTOM_GRP_NAME>
<$ALERT_DATE>
<$ALERT_TIME>
<$ALERT_STATUS>
SAP Alert Severity
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 28
12. SAPMPI Deinstallation Please process the following steps to correctly remove the SAPMP Package:
1. Un-Deploy all deployed SAPMPI elements like:
Assignments, single deployed Policies and Packages
2. Remove all existing SAP Instances from the boom agent using SAPMPI Actions:
Run Action SAP List Instances to get a list of all existing SAP Instances on this boom agent.
Remove all listed SAP Instances one by one using the SAPMPI Action SAP Delete Instance.
Run Action SAP List Instances again to make sure all existing SAP Instances have been
removed.
3. Delete manually all SAPMPI Elements from the Boom GUI:
Assignments, Policies, Packages and Actions.
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 29
13. Appendix
13.1 More Connection Attributes PLEASE NOTE: The following attributes are optional and normally not needed! Before you add any optional
connection attributes to your SAP_ccms_config.props file, try to run the SAPMPI. Here a list of supported attributes that can be used for a client connection to a remote SAP system. Depending on the type of middleware layer loaded, the properties that need to be provided by the implementation of the DestinationDataProvider (com.sap.conn.jco.ext.DestinationDataProvider) may vary.
ATTRIBUTE DESCRIPTION jco.destination.auth_type authentication type - configured user or current user
jco.client.user_id Logon user, used by JCo runtime.
jco.client.client SAP client
Three-digit client number; preserve leading zeros if they appear in the
number
jco.client.user Logon user
jco.client.alias_user Logon user alias
jco.client.passwd Logon password
jco.client.lang Logon language
ISO two-character language code (for example, EN, DE, FR),
or SAP-specific single-character language code. As a result,
only the first two characters are ever used, even if a longer
string is entered. The default is EN.
jco.client.saprouter If the connection needs to be made through a firewall using a
SAPRouter, specify the SAPRouter parameters in the
following format: /H/hostname/S/portnumber/H/
jco.client.sysnr SAP system number
jco.client.ashost SAP application server
jco.client.mshost SAP message server
jco.client.msserv optional: SAP message server port to use instead of the
default sapms<sysid>
jco.client.gwhost Host name of the SAP gateway
Example: GWHOST=hs0311
jco.client.gwserv Gateway service
jco.client.r3name Name of the SAP system
jco.client.group Group name of the SAP application servers
jco.client.tpname Program ID of external server program
jco.client.tphost Host of external server program
jco.client.type Type of remote host 2 = R/2, 3 = R/3, E = External
jco.client.trace Enable/disable RFC trace (0 or 1)
jco.client.cpic_trace Enable/disable CPIC trace (-1 [take over environment value], 0
no trace, 1,2,3 different amount of trace)
jco.client.codepage Identifies the initial code page in SAP notation. A code page is used whenever character data is processed on the application server, appears on the front end, or is rendered by a printer.
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 30
Four-digit SAP code page number
jco.client.mysapsso2 Indicates whether or not to use the specified SAP Cookie
Version 2 as the login ticket instead of user ID and password.
User: $MYSAPSSO2$
Password: Base64-encoded ticket
Login with single sign-on is based on secure network
connection (SNC) encryption and can only be used in
combination with an SNC.
jco.client.x509cert Indicates whether or not to use the specified X509 certificate
as the login certificate instead of user ID and password.
User: $X509CERT$
Password: Base64-encoded ticket
Login with X509 is based on secure network connection (SNC)
encryption and can only be used in combination with an SNC.
jco.client.snc_mode Secure network connection (SNC) mode, 0 (off) or 1 (on)
jco.client.snc_partnername SNC partner, e.g. p:CN=R3, O=XYZ-INC, C=EN
jco.client.snc_qop SNC level of security, 1 to 9
jco.client.snc_myname SNC name. Overrides default SNC partner
jco.client.snc_lib Path to library which provides SNC service
jco.client.dsr Enables or disables jDSR monitoring (off=0, on=1).
jco.destination.peak_limit Maximum number of active connections that can be created
for a destination simultaneously (OSS Notes 314530, 316877).
jco.destination.pool_capacity Maximum number of idle connections kept open by the
destination. A value of 0 has the effect that there is no
connection pooling.
jco.destination.expiration_time Time in ms after that the connections hold by the internal pool
can be closed (default is 600000msec=10min).
jco.destination.expiration_check_period Interval in ms with which the timeout checker thread checks
the connections in the pool for expiration
jco.destination.max_get_client_time Max time in ms to wait for a connection, if the max allowed
number of connections is allocated by the application (default
is 30000msec=30sec).
jco.destination.repository_destination Specifies which destination should be used as repository, i.e.
use this destination's repository
jco.destination.repository.user Optional: If repository destination is not set, and this property
is set, it will be used as user for repository calls. This allows
using a different user for repository lookups
jco.destination.repository.passwd The password for a repository user. Mandatory, if a repository
user should be used.
jco.destination.repository.snc_mode Enables or disables secure network connection mode
0=off 1=on
Optional: If SNC is used for this destination, it is possible to
turn it off for repository connections, if this property is set to 0.
Defaults to the value of jco.client.snc_mode
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 31
13.2 Example Policies
CATEGORY POLICIES
SAPMPI Basic SAP_Discover_indi.msg.xml
SAP_Discover_mon.mon.xml
SAPMPI Trigger Policy SAPTrigger_ccms.mon.xml
Background Processing SAP_Background_AbortedJobs.msg.xml
SAP_Background_ProgramErrors.msg.xml
SAP_BgService_SystemWideFreeBPWP.mon.xml
SAP_BgService_SystemWideQueueLength.mon.xml
Buffers SAP_CUA_DirectoryUsed.mon.xml
SAP_CUA_HitRatio.mon.xml
SAP_CUA_SpaceUsed.mon.xml
SAP_CUA_Swap.mon.xml
SAP_FieldDescription_DirectoryUsed.mon.xml
SAP_FieldDescription_HitRatio.mon.xml
SAP_FieldDescription_SpaceUsed.mon.xml
SAP_FieldDescription_Swap.mon.xml
SAP_GenericKey_DirectoryUsed.mon.xml
SAP_GenericKey_HitRatio.mon.xml
SAP_GenericKey_SpaceUsed.mon.xml
SAP_GenericKey_Swap.mon.xml
SAP_InitialRecords_DirectoryUsed.mon.xml
SAP_InitialRecords_HitRatio.mon.xml
SAP_InitialRecords_SpaceUsed.mon.xml
SAP_InitialRecords_Swap.mon.xml
SAP_Program_DirectoryUsed.mon.xml
SAP_Program_HitRatio.mon.xml
SAP_Program_SpaceUsed.mon.xml
SAP_Program_Swap.mon.xml
SAP_Screen_DirectoryUsed.mon.xml
SAP_Screen_HitRatio.mon.xml
SAP_Screen_SpaceUsed.mon.xml
SAP_Screen_Swap.mon.xml
SAP_ShortNameTAB_DirectoryUsed.mon.xml
SAP_ShortNameTAB_HitRatio.mon.xml
SAP_ShortNameTAB_SpaceUsed.mon.xml
SAP_ShortNameTAB_Swap.mon.xml
SAP_SingleRecord_DirectoryUsed.mon.xml
SAP_SingleRecord_HitRatio.mon.xml
SAP_SingleRecord_SpaceUsed.mon.xml
SAP_SingleRecord_Swap.mon.xml
SAP_TableDefinition_DirectoryUsed.mon.xml
SAP_TableDefinition_HitRatio.mon.xml
SAP_TableDefinition_SpaceUsed.mon.xml
SAP_TableDefinition_Swap.mon.xml
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 32
CATEGORY POLICIES
Dialog SAP_Dialog_DBRequestTime.mon.xml
SAP_Dialog_DialogSteps.mon.xml
SAP_Dialog_EndedWpDIA.mon.xml
SAP_Dialog_ErrorFreqInWpDIA.mon.xml
SAP_Dialog_ErrorsInWpDIA.mon.xml
SAP_Dialog_FrontEndNetTime.mon.xml
SAP_Dialog_FrontendResponseTime.mon.xml
SAP_Dialog_GuiCallbackTime.mon.xml
SAP_Dialog_Load-GenTime.mon.xml
SAP_Dialog_LogonLoadQuality.mon.xml
SAP_Dialog_LongRunners.mon.xml
SAP_Dialog_MonitoringTime.mon.xml
SAP_Dialog_NumberOfWpDIA.mon.xml
SAP_Dialog_PrivModeUtilisation.mon.xml
SAP_Dialog_ProgramErrors.msg.xml
SAP_Dialog_QueueLength.mon.xml
SAP_Dialog_QueueTime.mon.xml
SAP_Dialog_ResponseTime.mon.xml
SAP_Dialog_ResponseTime_StdTran.mon.xml
SAP_Dialog_RollTime.mon.xml
SAP_Dialog_UsersLoggedIn.mon.xml
SAP_Dialog_Utilisation.mon.xml
FileSystem SAP_FreeSpace_C.mon.xml
Operating System SAP_CPU_Utilization.mon.xml
Oracle SAP_Oracle_FreeSpace_PSAPIDE
SAP_Oracle_FreeSpace_PSAPIDE700
SAP_Oracle_FreeSpace_PSAPIDEFACT
SAP_Oracle_FreeSpace_PSAPIDEODS
SAP_Oracle_FreeSpace_PSAPIDEUSR
SAP_Oracle_FreeSpace_PSAPTEMP
SAP_Oracle_FreeSpace_PSAPUNDO
SAP_Oracle_FreeSpace_SYSAUX
SAP_Oracle_FreeSpace_SYSTEM
Spool System SAP_Spool_FrontendWaitTime.mon.xml
SAP_Spool_Status.msg.xml
SAP_Spool_UsedNumbers.mon.xml
Syslog SAP_R3Syslog_AbapErrorInUpdate.msg.xml
SAP_R3Syslog_Background.msg.xml
SAP_R3Syslog_BasisSystem.msg.xml
SAP_R3Syslog_CCMS.msg.xml
SAP_R3Syslog_Communication.msg.xml
SAP_R3Syslog_Database.msg.xml
SAP_R3Syslog_Security.msg.xml
SAP_R3Syslog_SyslogFreq.mon.xml
System Errors SAP_R3Abap_Shortdumps.msg.xml
SAP_R3Abap_ShortdumpsFreq.mon.xml
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 33
13.3 Property Files
13.3.1 Default Configuration File
#-------------------------
# SAP Instance
#-------------------------
SAP_INSTANCE=<INSTANCE_NAME>
#-------------------------
# CCMS Montior-Set(RZ20)
#-------------------------
CCMS_ENABLED=true
CCMS_MONITOR_SET=SAP CCMS Monitor Templates
CCMS_MONITOR_NAME=*
CCMS_PERF_ENABLED=true
#----------------------------
# DATA COLLECTOR (milliseconds)
# 1min=60.000 5min=300.000
# 1h=3.600.000 5h=18.000.000
#----------------------------
DB_INTERVAL = 60000
#----------------------------
# LOGGING
#----------------------------
LOGLEVEL=3
MAX_LOGDAYS=2
13.3.2 Default CCMS Pattern File #------------------------------------------
# CCMS PATTERN
#------------------------------------------
# pattern -> <key>|<PolicyName>
# key -> <SYSID>::<MTCNAME>::<OBJECTNAME>::<MTNAMESHRT>
#----------------------------------------
# <SYSID>: Name of SAP System
# <MTCNAME>: Name of Monitoring Context
# <OBJECTNAME>: Name of Monitoring Object
# <MTNAMESHRT>: Short Name of Monitoring Type
#----------------------------------------
# *::*::Dialog::ProgramErrors|SAP_Dialog_ProgramErrors
#------------------------------------------
# DISCOVER ALL
#------------------------------------------
#*::*::*::*
#------------------------------------------
# Background Processing
#------------------------------------------
*::*::Background::AbortedJobs|SAP_Background_AbortedJobs
*::*::Background::ProgramErrors|SAP_Background_ProgramErrors
*::Background::BackgroundService::SystemWideFreeBPWP|SAP_BgService_SystemWideFreeBPWP
*::Background::BackgroundService::SystemWideQueueLength|SAP_BgService_SystemWideQueueLength
#------------------------------------------
# BUFFERS
#------------------------------------------
*::*::CUA::DirectoryUsed|SAP_CUA_DirectoryUsed
*::*::CUA::HitRatio|SAP_CUA_HitRatio
*::*::CUA::SpaceUsed|SAP_CUA_SpaceUsed
*::*::CUA::Swap|SAP_CUA_Swap
#------------------------------------------
#*::*::FieldDescription::DirectoryUsed|SAP_FieldDescription_DirectoryUsed
#*::*::FieldDescription::HitRatio|SAP_FieldDescription_HitRatio
#*::*::FieldDescription::SpaceUsed|SAP_FieldDescription_SpaceUsed
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 34
#*::*::FieldDescription::Swap|SAP_FieldDescription_Swap
#------------------------------------------
*::*::GenericKey::DirectoryUsed|SAP_GenericKey_DirectoryUsed
*::*::GenericKey::HitRatio|SAP_GenericKey_HitRatio
*::*::GenericKey::SpaceUsed|SAP_GenericKey_SpaceUsed
*::*::GenericKey::Swap|SAP_GenericKey_Swap
#------------------------------------------
*::*::InitialRecords::DirectoryUsed|SAP_InitialRecords_DirectoryUsed
*::*::InitialRecords::HitRatio|SAP_InitialRecords_HitRatio
*::*::InitialRecords::HitRatio|SAP_InitialRecords_HitRatio_MultiPattern
*::*::InitialRecords::SpaceUsed|SAP_InitialRecords_SpaceUsed
*::*::InitialRecords::Swap|SAP_InitialRecords_Swap
#------------------------------------------
*::*::Program::DirectoryUsed|SAP_Program_DirectoryUsed
*::*::Program::HitRatio|SAP_Program_HitRatio
*::*::Program::SpaceUsed|SAP_Program_SpaceUsed
*::*::Program::Swap|SAP_Program_Swap
#------------------------------------------
*::*::Screen::DirectoryUsed|SAP_Screen_DirectoryUsed
*::*::Screen::HitRatio|SAP_Screen_HitRatio
*::*::Screen::SpaceUsed|SAP_Screen_SpaceUsed
*::*::Screen::Swap|SAP_Screen_Swap
#------------------------------------------
*::*::ShortNameTAB::DirectoryUsed|SAP_ShortNameTAB_DirectoryUsed
*::*::ShortNameTAB::HitRatio|SAP_ShortNameTAB_HitRatio
*::*::ShortNameTAB::SpaceUsed|SAP_ShortNameTAB_SpaceUsed
*::*::ShortNameTAB::Swap|SAP_ShortNameTAB_Swap
#------------------------------------------
*::*::SingleRecord::DirectoryUsed|SAP_SingleRecord_DirectoryUsed
*::*::SingleRecord::HitRatio|SAP_SingleRecord_HitRatio
*::*::SingleRecord::SpaceUsed|SAP_SingleRecord_SpaceUsed
*::*::SingleRecord::Swap|SAP_SingleRecord_Swap
#------------------------------------------
*::*::TableDefinition::DirectoryUsed|SAP_TableDefinition_DirectoryUsed
*::*::TableDefinition::HitRatio|SAP_TableDefinition_HitRatio
*::*::TableDefinition::SpaceUsed|SAP_TableDefinition_SpaceUsed
*::*::TableDefinition::Swap|SAP_TableDefinition_Swap
#------------------------------------------
# Dialog
#------------------------------------------
*::*::Dialog::DBRequestTime|SAP_Dialog_DBRequestTime
*::*::Dialog::DialogSteps|SAP_Dialog_DialogSteps
*::*::Dialog::EndedWpDIA|SAP_Dialog_EndedWpDIA
*::*::Dialog::ErrorFreqInWpDIA|SAP_Dialog_ErrorFreqInWpDIA
*::*::Dialog::ErrorsInWpDIA|SAP_Dialog_ErrorsInWpDIA
*::*::Dialog::FrontEndNetTime|SAP_Dialog_FrontEndNetTime
*::*::Dialog::FrontendResponseTime|SAP_Dialog_FrontendResponseTime
*::*::Dialog::GuiCallbackTime|SAP_Dialog_GuiCallbackTime
*::*::Dialog::Load+GenTime|SAP_Dialog_Load-GenTime
*::*::Dialog::LogonLoadQuality|SAP_Dialog_LogonLoadQuality
*::*::Dialog::LongRunners|SAP_Dialog_LongRunners
*::*::Dialog::MonitoringTime|SAP_Dialog_MonitoringTime
*::*::Dialog::NumberOfWpDIA|SAP_Dialog_NumberOfWpDIA
*::*::Dialog::PrivMode Utilisation|SAP_Dialog_PrivModeUtilisation
*::*::Dialog::ProgramErrors|SAP_Dialog_ProgramErrors
*::*::Dialog::QueueLength|SAP_Dialog_QueueLength
*::*::Dialog::QueueTime|SAP_Dialog_QueueTime
*::*::Dialog::ResponseTime|SAP_Dialog_ResponseTime
*::*::Dialog::ResponseTime(StandardTran.)|SAP_Dialog_ResponseTime_StdTran
*::*::Dialog::RollTime|SAP_Dialog_RollTime
*::*::Dialog::UsersLoggedIn|SAP_Dialog_UsersLoggedIn
*::*::Dialog::Utilisation|SAP_Dialog_Utilisation
#------------------------------------------
# Filesystems
#------------------------------------------
*::*::C:::Freespace|SAP_FreeSpace_C
#------------------------------------------
# Operating System
#------------------------------------------
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 35
*::*::CPU::CPU_Utilization|SAP_CPU_Utilization
#------------------------------------------
# ORACLE
#------------------------------------------
*::Oracle::PSAPIDE::Free space|SAP_Oracle_FreeSpace_PSAPIDE
*::Oracle::PSAPIDE700::Free space|SAP_Oracle_FreeSpace_PSAPIDE700
*::Oracle::PSAPIDEFACT::Free space|SAP_Oracle_FreeSpace_PSAPIDEFACT
*::Oracle::PSAPIDEODS::Free space|SAP_Oracle_FreeSpace_PSAPIDEODS
*::Oracle::PSAPIDEUSR::Free space|SAP_Oracle_FreeSpace_PSAPIDEUSR
*::Oracle::PSAPTEMP::Free space|SAP_Oracle_FreeSpace_PSAPTEMP
*::Oracle::PSAPUNDO::Free space|SAP_Oracle_FreeSpace_PSAPUNDO
*::Oracle::SYSAUX::Free space|SAP_Oracle_FreeSpace_SYSAUX
*::Oracle::SYSTEM::Free space|SAP_Oracle_FreeSpace_SYSTEM
#------------------------------------------
# Spool System
#------------------------------------------
*::Spool::SpoolNumbers::UsedNumbers|SAP_Spool_UsedNumbers
*::Spool::*::Status|SAP_Spool_Status
*::Spool::Frontend::WaitTime|SAP_Spool_FrontendWaitTime
#------------------------------------------
# Syslog
#------------------------------------------
*::*::Update::AbapErrorInUpdate|SAP_R3Syslog_AbapErrorInUpdate
*::*::R3Syslog::Background|SAP_R3Syslog_Background
*::*::R3Syslog::BasisSystem|SAP_R3Syslog_BasisSystem
*::*::R3Syslog::CCMS|SAP_R3Syslog_CCMS
*::*::R3Syslog::Communication|SAP_R3Syslog_Communication
*::*::R3Syslog::Database|SAP_R3Syslog_Database
*::*::R3Syslog::Security|SAP_R3Syslog_Security
*::*::R3Syslog::SyslogFreq|SAP_R3Syslog_SyslogFreq
#------------------------------------------
# System Errors
#------------------------------------------
*::*::R3Abap::Shortdumps|SAP_R3Abap_AbapShortdumps
*::*::R3Abap::Shortdumps Frequency|SAP_R3Abap_ShortdumpsFreq
13.3.3 Default CCMS PerformancFile #----------------------------------------------
# CCMS PERFORMANCE DATA
#----------------------------------------------
# <PerformanceClassName>|<Type>|<ColumnName>|<PolicyName>
#----------------------------------------------
# PLEASE NOTE:
# - possible DataTypes: DOUBLE, BIGINT
# - don't use: brackets, +, -, space, ...
# or any other special characters for column names
# - All Policies that are referenced here must exist and must be activated in the pattern.props!
#----------------------------------------------
# The first 2 columns in the perf db are added automatically:
# Col1: HOST -> <$AGENT_HOST>
# Col2: INSTANCE -> SAP Instance Name
#----------------------------------------------
# PERF ALL
#----------------------------------------------
#*|*|*|*
#------------------------------------------
# BACKGROUND RROCESSING
#------------------------------------------
SAP_BACKGROUND|DOUBLE|SystemWideFreeBPWP|SAP_BgService_SystemWideFreeBPWP
SAP_BACKGROUND|DOUBLE|SystemWideQueueLength|SAP_BgService_SystemWideQueueLength
#------------------------------------------
# BUFFERS
#------------------------------------------
SAP_BUFFER|DOUBLE|ProgramDirectoryUsed|SAP_Program_DirectoryUsed
SAP_BUFFER|DOUBLE|ProgramSpaceUsed|SAP_Program_SpaceUsed
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 36
SAP_BUFFER|DOUBLE|ProgramHitRatio|SAP_Program_HitRatio
SAP_BUFFER|DOUBLE|ProgramSwap|SAP_Program_Swap
SAP_BUFFER|DOUBLE|GenKeyDirectoryUsed|SAP_GenericKey_DirectoryUsed
SAP_BUFFER|DOUBLE|GenKeySpaceUsed|SAP_GenericKey_SpaceUsed
SAP_BUFFER|DOUBLE|GenKeyHitRatio|SAP_GenericKey_HitRatio
SAP_BUFFER|DOUBLE|GenKeySwap|SAP_GenericKey_Swap
SAP_BUFFER|DOUBLE|SingleRecordDirectoryUsed|SAP_SingleRecord_DirectoryUsed
SAP_BUFFER|DOUBLE|SingleRecordSpaceUsed|SAP_SingleRecord_SpaceUsed
SAP_BUFFER|DOUBLE|SingleRecordHitRatio|SAP_SingleRecord_HitRatio
SAP_BUFFER|DOUBLE|SingleRecordSwap|SAP_SingleRecord_Swap
SAP_BUFFER|DOUBLE|ScreenDirectoryUsed|SAP_Screen_DirectoryUsed
SAP_BUFFER|DOUBLE|ScreenSpaceUsed|SAP_Screen_SpaceUsed
SAP_BUFFER|DOUBLE|ScreenHitRatio|SAP_Screen_HitRatio
SAP_BUFFER|DOUBLE|ScreenSwap|SAP_Screen_Swap
SAP_BUFFER|DOUBLE|CUADirectoryUsed|SAP_CUA_DirectoryUsed
SAP_BUFFER|DOUBLE|CUASpaceUsed|SAP_CUA_SpaceUsed
SAP_BUFFER|DOUBLE|CUAHitRatio|SAP_CUA_HitRatio
SAP_BUFFER|DOUBLE|CUASwap|SAP_CUA_Swap
SAP_BUFFER|DOUBLE|TableDefDirectoryUsed|SAP_TableDefinition_DirectoryUsed
SAP_BUFFER|DOUBLE|TableDefSpaceUsed|SAP_TableDefinition_SpaceUsed
SAP_BUFFER|DOUBLE|TableDefHitRatio|SAP_TableDefinition_HitRatio
SAP_BUFFER|DOUBLE|TableDefSwap|SAP_TableDefinition_Swap
SAP_BUFFER|DOUBLE|FieldDescDirectoryUsed|SAP_FieldDescription_DirectoryUsed
SAP_BUFFER|DOUBLE|FieldDescSpaceUsed|SAP_FieldDescription_SpaceUsed
SAP_BUFFER|DOUBLE|FieldDescHitRatio|SAP_FieldDescription_HitRatio
SAP_BUFFER|DOUBLE|FieldDescSwap|SAP_FieldDescription_Swap
SAP_BUFFER|DOUBLE|InitRecordsDirectoryUsed|SAP_InitialRecords_DirectoryUsed
SAP_BUFFER|DOUBLE|InitRecordsSpaceUsed|SAP_InitialRecords_SpaceUsed
SAP_BUFFER|DOUBLE|InitRecordsHitRatio|SAP_InitialRecords_HitRatio
SAP_BUFFER|DOUBLE|InitRecordsSwap|SAP_InitialRecords_Swap
SAP_BUFFER|DOUBLE|ShortNameDirectoryUsed|SAP_ShortNameTAB_DirectoryUsed
SAP_BUFFER|DOUBLE|ShortNameSpaceUsed|SAP_ShortNameTAB_SpaceUsed
SAP_BUFFER|DOUBLE|ShortNameHitRatio|SAP_ShortNameTAB_HitRatio
SAP_BUFFER|DOUBLE|ShortNameSwap|SAP_ShortNameTAB_Swap
#------------------------------------------
# DIALOG
#------------------------------------------
SAP_DIALOG|BIGINT|DBRequestTime|SAP_Dialog_DBRequestTime
SAP_DIALOG|BIGINT|ResponseTime|SAP_Dialog_ResponseTime
SAP_DIALOG|BIGINT|DialogSteps|SAP_Dialog_DialogSteps
SAP_DIALOG|BIGINT|EndedWpDIA|SAP_Dialog_EndedWpDIA
SAP_DIALOG|BIGINT|ResponseTimeStdTran|SAP_Dialog_ResponseTime_StdTran
SAP_DIALOG|BIGINT|ErrorFreqInWpDIA|SAP_Dialog_ErrorFreqInWpDIA
SAP_DIALOG|BIGINT|ErrorsInWpDIA|SAP_Dialog_ErrorsInWpDIA
SAP_DIALOG|BIGINT|FrontEndNetTime|SAP_Dialog_FrontEndNetTime
SAP_DIALOG|BIGINT|FrontendResponseTime|SAP_Dialog_FrontendResponseTime
SAP_DIALOG|BIGINT|GuiCallbackTime|SAP_Dialog_GuiCallbackTime
SAP_DIALOG|BIGINT|LoadAndGenTime|SAP_Dialog_Load-GenTime
SAP_DIALOG|BIGINT|LogonLoadQuality|SAP_Dialog_LogonLoadQuality
SAP_DIALOG|BIGINT|LongRunners|SAP_Dialog_LongRunners
SAP_DIALOG|BIGINT|MonitoringTime|SAP_Dialog_MonitoringTime
SAP_DIALOG|BIGINT|NumberOfWpDIA|SAP_Dialog_NumberOfWpDIA
SAP_DIALOG|BIGINT|PrivModeUtilisation|SAP_Dialog_PrivModeUtilisation
SAP_DIALOG|BIGINT|QueueLength|SAP_Dialog_QueueLength
SAP_DIALOG|BIGINT|QueueTime|SAP_Dialog_QueueTime
SAP_DIALOG|BIGINT|RollTime|SAP_Dialog_RollTime
SAP_DIALOG|BIGINT|UsersLoggedIn|SAP_Dialog_UsersLoggedIn
SAP_DIALOG|BIGINT|Utilisation|SAP_Dialog_Utilisation
#------------------------------------------
# Filesystems
#------------------------------------------
SAP_FILESYSTEMS|DOUBLE|FreespaceC|SAP_FreeSpace_C
#------------------------------------------
# Operating System
#------------------------------------------
SAP_OPERATINGSYSTEM|DOUBLE|CPU_Utilization|SAP_CPU_Utilization
#------------------------------------------
# ORACLE
#------------------------------------------
boom SAPMPI Document
Version 2.20 2014-12-04
© 2014 Blue Elephant Systems GmbH Page 37
SAP_ORACLE|DOUBLE|PsapideFreespace|SAP_Oracle_FreeSpace_PSAPIDE
SAP_ORACLE|DOUBLE|PSAPIDE700_Freespace|SAP_Oracle_FreeSpace_PSAPIDE700
SAP_ORACLE|DOUBLE|PSAPIDEFACT_Freespace|SAP_Oracle_FreeSpace_PSAPIDEFACT
SAP_ORACLE|DOUBLE|PSAPIDEODS_Freespace|SAP_Oracle_FreeSpace_PSAPIDEODS
SAP_ORACLE|DOUBLE|PSAPIDEUSR_Freespace|SAP_Oracle_FreeSpace_PSAPIDEUSR
SAP_ORACLE|DOUBLE|PSAPTEMP_Freespace|SAP_Oracle_FreeSpace_PSAPTEMP
SAP_ORACLE|DOUBLE|PSAPUNDO_Freespace|SAP_Oracle_FreeSpace_PSAPUNDO
SAP_ORACLE|DOUBLE|SYSAUX_Freespace|SAP_Oracle_FreeSpace_SYSAUX
SAP_ORACLE|DOUBLE|SYSTEM_Freespace|SAP_Oracle_FreeSpace_SYSTEM
#------------------------------------------
# SPOOL_SYSTEM
#------------------------------------------
SAP_SPOOL_SYSTEM|BIGINT|UsedNumbers|SAP_Spool_UsedNumbers
SAP_SPOOL_SYSTEM|BIGINT|FontEndWaitTime|SAP_Spool_FrontendWaitTime
#------------------------------------------
# SYSLOG
#------------------------------------------
SAP_SYSLOG|BIGINT|SyslogFreq|SAP_R3Syslog_SyslogFreq
#------------------------------------------
# System Errors
#------------------------------------------
SAP_SYSTEM_ERRORS|BIGINT|ShortdumpsFreq|SAP_R3Abap_ShortdumpsFreq