boom SAPMPI 2 - bes-worldline.com · Chapter 4. Concept 4.1. CCMS Pattern 4.1.1. Pattern Definition SAPMPI Patterns are used to map the SAP ccms data to the appropriate boom Policies

boom SAPMPI 2.40User Manual

Worldline Germany GmbH

Version 2.40, 2018-03-01

Table of Content1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2.1. SAPJCo3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2.2. SAP User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3.1. SAP Java Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3.1.1. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3.1.2. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3.2. Boom Agent Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3.2.1. Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

3.2.2. Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3.3. SAPMPI Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3.4. Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

3.5. De-Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

4. Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4.1. CCMS Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4.1.1. Pattern Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4.1.2. Pattern Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4.1.2.1. Configuration using Discover-All Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4.1.2.2. Configuration via SAP GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

4.2. CCMS Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4.2.1. Pattern Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4.2.2. Performance Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.3. CCMS Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.3.1. Monitor Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.3.2. Indication Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

4.3.3. Additional Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4.4. Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4.4.1. Run Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

4.4.2. Action List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

5. Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

5.1. SAP Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

5.2. Property Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5.2.1. SAP_ccms_config.props . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

5.2.2. SAP_ccms_pattern.props . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5.2.3. SAP_ccms_perf.props . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

5.3. Trigger Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

5.4. Configuration Steps Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

6. Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

6.1. More Connection Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

6.2. Example Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

6.3. Example Proptery Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

7. Copyright & Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

8. Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Chapter 1. IntroductionThe boom SAPMPI connects to the Computing Center Management System (CCMS) on a SAP system via the RFCinterface. Once connected it can access any CCMS data that are available on this system. All data that can beaccessed can also be monitored.

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


© Copyright 2018, Worldline Germany GmbH 1 of 37

Chapter 2. Requirements

2.1. SAPJCo3The SAPJCo3 supports SAP (R/3) systems from Release 3.1H upwards, and other mySAP components that have BAPIor 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 Server2008 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]


2 of 37 © Copyright 2018, Worldline Germany GmbH

• 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]

2.2. SAP UserIn order to access the CCMS of a SAP System you need a valid SAP RFC user with the access rights listest below:

Access Rights Description Option Value

S_RFC Authorization Check for RFC access Activity Name of RFC to beprotected

Type of RFC object to beprotected

* (or execute)

SALX, SXHC, SXMI, SYST FUGR (Function group)

S_XMI_LOG Internal accessauthorization for XMI log

Access method for XMI log *

S_XMI_PROD Auth. for externalmanagement interfaces(XMI)

XMI logging: companyname

Product

Interface ID Worldline GmbH

boom *



Chapter 3. Installation

3.1. SAP Java ConnectorFirst you have to download the SAP Java Connector 3.0 installation files from SAP Service Marketplace atservice.sap.com/connectors.

Because the SAP JCo Package contains native libraries, make sure you select the correct package according to youroperation system and the installed java version! See SAP note #1077727 for detailed information on supportedplatforms.

This download has to be done because SAP does not allow the redistribution of any connector!

3.1.1. Linux

The SAPJCo3 package for Linux contains exactly 2 files - 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:

ldd libsapjco3.so

Result example:

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)

If necessary check also the library path and all symbolic links!

3. Check if SAPJCo3 is running correctly:

java –jar sapjco3.jar –stdout

The result should not contain any errors or exceptions!



3.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)

sapjco3.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 errors or exceptions!

3.2. Boom Agent Configuration

3.2.1. Linux

Installation Steps:

1. stop boom agent

/etc/init.d/boom_agt stop

2. modify the boom agent startup script /boom_agent/boom_agt as described here:

Find all: -jar boom_agent.jarReplace with: -cp boom_agent.jar:sapjco3.jar com.blixx.agent.AgentEngine

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

/etc/init.d/boom_agt start



3.2.2. Windows

Installation Steps:

1. stop boom agent windows service

2. modify the boom agent startup script /boom_agent/boom_agt.cmd as described here:

Find all: -jar boom_agent.jarReplace with: -cp boom_agent.jar;sapjco3.jar com.blixx.agent.AgentEngine

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 windows service

3.3. SAPMPI PackageExtract the SAPMPI Package SAPJCo-v2.40.zip to a temporary directory and import all necessary components to theboom server using the Import MPI View of the boom GUI.



3.4. UpgradeUpgrade Steps:

1. Stop SAPMPI by un-deploying the SAPTrigger Policy.

2. Upload new sapmonitor.jar file via the boom UI:



This file can be found in:

SAPMPI_v2.40\packages\SAPMPI\jars\sapmonitor.jar

3. Re-deploy SAPMPI Package:

4. Start SAPMPI by deploying the SAPTrigger Policy.

3.5. De-InstallationDe-Installation Steps:

Please process the following steps to correctly remove the SAPMP Package!

1. Un-Deploy all deployed SAPMPI related elements like:

a. Assignments

b. Packages

c. single deployed Policies

2. Delete all SAPMPI related elements from the Boom GUI:

a. Policies

b. Assignments

c. Packages

d. Actions

3. Delete the following SAPMPI related files manually from the /boom_agent/spi/ directory:



a. logfiles (TRIGGER_*.log and COLLECTOR_*.log)

b. SAPMPI propery files (*.props)

c. SAPMPI instance files (*.lprops)

4. Delete all sapjco libraries in /boom_agent:

a. Linux: sapjco3.jar, libsapjco3.so

b. Windows: sapjco3.jar, sapjco3.dll

5. Undo changes in the boom agent startup script. Please see chapter Boom Agent Configuration for moreinformation.



Chapter 4. Concept

4.1. CCMS Pattern

4.1.1. Pattern Definition

SAPMPI Patterns are used to map the SAP ccms data to the appropriate boom Policies. That means a pattern has tobe created 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 ‘|’:

Example:

N4S::srv-sap01_N4S_42::Dialog::SAP_UsersLoggedIn|SAP_Dialog_UsersLoggedIn

<KEY>

The <KEY> is used to identify the SAP value. It consists of the following 4 attributes:

• <SYSID>

• <MTCNAME>

• <OBJECTNAME>

• <MTNAMESHRT>

All attributes are separated by two colons → ::

<POLICYNAME>

The <POLICYNAME> defines which policy is responsible for which value. If we take the example from above, thePolicy that is processing the data is named SAP_Dialog_UsersLoggedIn.

<POLICYNAME> = SAP_Dialog_UsersLoggedIn

4.1.2. Pattern Configuration

There are 2 possibilities to get all necessary information to be able to create patterns. You can get this informationfrom the SAP GUI or you can use the DiscoverAll (*::*::*::*) method.

4.1.2.1. Configuration using Discover-All Method

After the first installation of the SAP MPI this is a nice and easy way to get all necessary information to build thepattern property file. Just activate the DiscoverAll pattern in the SAP_ccms_pattern.props and run the SAPMPI. Usingthis pattern, you will get all available data out of the SAP System. Please note, that this might take a while.

DiscoverAll pattern => *::*::*::*

Configuration Steps:



1. The Trigger Policy must be linked to the correct property files.

2. Check configuration in the SAP_ccms_config.props file.

3. Deploy the "SAPMPI" Assignment on the boom agent. This assignment contains the SAPMPI Binary Packagetogether with all basic policies belonging to the SAPMPI.

When you are running the Discover-All method you will get indication for all available ccms data. Since the SAPMPItries to fetch all available data, it can take a while to get the result.

The indication object is exactly the KEY we need for our pattern Oen the indication details by double-click on thiselement and copy the Object to your SAP_ccms_pattern.props file.

4.1.2.2. Configuration via SAP GUI

Another possibility to get the pattern details is via the SAP GUI. If you want to add just a few more elements to yourproperty 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 backslash "\" . If the MTE Class contains 4elements, than this is exactly what we need for our <KEY>. If the MTE Class Properties contains more than 4elements, you have to take the first two and the last two elements.

Example:

Property => N4S\srv-sap01_N4S_42\R3Services\Dialog\UsersLoggedIn<KEY> => N4S::srv-sap01_N4S_42::Dialog::UsersLoggedIn

4.2. CCMS Performance Data

4.2.1. Pattern Definition

The Pattern contains of exactly 4 elements:

<PerformanceClassName>|<Type>|<ColumnName>|<PolicyName>

Element Name Description

PerformanceClassName name of the table in the performance database

Type data type (DOUBLE or BIGINT)

ColumnName column name

PolicyName linked boom policy

Example:



#----------------------------------------------# BUFFERS# <PerformanceClassName>|<Type>|<ColumnName>|<PolicyName>#----------------------------------------------SAP_BUFFER|DOUBLE|ProgramDirectoryUsed|SAP_Program_DirectoryUsedSAP_BUFFER|DOUBLE|ProgramHitRatio|SAP_Program_HitRatioSAP_BUFFER|DOUBLE|ProgramSpaceUsed|SAP_Program_SpaceUsedSAP_BUFFER|DOUBLE|ProgramSwap|SAP_Program_Swap

4.2.2. Performance Storage

4.3. CCMS Policies



4.3.1. Monitor Policy

When defining a Monitor Policy you have to make sure that:

• Policy with Reset is set to YES

• Monitor Type is set to EXTERNAL

• De-Duplicate KeyOnly is activated for all conditions.

4.3.2. Indication Policy



Every Indication Policy must have minimum 2 conditions in order to cover the all situations:

1. Empty SAP MTE ClassA MTE Class is empty when the SAP Field does not contain any message. That means there is no Error or anyother message available for this Policy in the SAP System. In this case the Indication will be sent withseverity=unknown.

2. SAP MTE Class contains some dataThis can be an error or any other message that is available in the SAP System. In this case some text will befetched from the SAP System and sent as an indication with severity=normal. This text can be both, normalinformation or even an error message.

Since we cannot distinguish between a normal and an error message, we have to carfully definethe filter section for each policy condition.

Make sure that the following attributes are set correctly:

• Application = SAP



• Indication Group = *

• Object = <KEY>

4.3.3. Additional Variables

These variables are optional and can be used inside any Policy:

Variable Name Description

Type* DOUBLE or BIGINT

<$SAPHOST> sap host

<$SAPUSER> sap user

<$SAPSYSNR> sap sysnr

<$SAPSYSID> sap sysID

<$SAPDESTINATION> sap destination

<$SAPLANG> sap language

<$MONITOR_SET> sap monitor set name

<$MONITOR_NAME> sap monitor name

<$OBJECTNAME> sap object name

<$MTNAMESHRT> sap mt name short

<$UNIT> sec, %, …

<$INFO> sap info text

<$CUSTOM_GRP_NAME> sap custom group name

<$ALERT_DATE> sap alert date

<$ALERT_TIME> sap alert time

<$ALERT_STATUS> sap alert severity

4.4. Actions

4.4.1. Run Actions

You can run actions from the boom UI:



4.4.2. Action List

GetVersion

Description Returns the version of the installed SAPMPI

Command IAction com.na.boom.sap.mon.SAPMPIAction VERSION

Optional Parameters None

SAP Add Instance

Description Use this action to add a SAP Instance to a boom agent. This Instance contains allneeded attributes to connect to the SAP System. If the connection was successfullyestablished, you will get back the connection attributes from the SAP System. All logincredentials will be saved inside a text file (password encrypted!):/boom_agent/<instanceName>.lprops. PLEASE NOTE: If the SAP System is behind aSAP 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>

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>

SAP List Instances

Description This action will list all existing SAP Instances for the selected agent(s). It will NOT testif the Instances can connect to the SAP System.

Command IAction com.na.boom.sap.mon.SAPMPIAction GET_INSTANCE



SAP List Instances


SAP Test Instance

Description To test if an existing SAP Instance is still valid. Running this action will first connectand then disconnect from the SAP System. If the connection was successful theconnection attributes from the SAP System will be reported back.

Command IAction com.na.boom.sap.mon.SAPMPIAction TEST_INSTANCE

Optional Parameters <instance_name>

SAP Test Login

Description This action will establish a connection to a SAP System using the given loginparameters. If the connection was successful, the action will disconnect and theconnection 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>

HELP

Description Displays the usage of SAPMPI Action

Command IAction com.na.boom.sap.mon.SAPMPIAction




Chapter 5. Configuration

5.1. SAP InstanceAfter the SAPMPI Package has been imported successfully, we have to make sure,that the boom agent is able toestablish a connection to the SAP System. This can be done by adding a "SAP Instance" to the boom agent.

Configuration Steps:

1. run boomUI action "SAP Add Instance"

2. adjust parameters

<client> sap client

<user> sap user name

<password> sap password

<host> sap host

<system_number> sap system number

<language> sap language

<instance> just name the instance

3. select the appropriate boom agent

4. click on executeAll required information will be stored in a text file on the boom agent side. The property file is located in theboom agent directory:

{boom_agent_home}/<instanceName>.lprops



The password is encrypted!

5. resultThe instance contains all needed attributes to connect to the SAP System. If the connection was successfullyestablished, you will get back all connection attributes from the SAP System.

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.

Standard configuration file with minimum attributes

#-------------------------# SAP Instance#-------------------------SAP_INSTANCE=<INSTANCE_NAME>#-------------------------# CCMS Monitor-Set(RZ20)#-------------------------CCMS_ENABLED=trueCCMS_MONITOR_SET=SAP CCMS Monitor TemplatesCCMS_MONITOR_NAME=*CCMS_PERF_ENABLED=true#----------------------------# DATA COLLECTOR (milliseconds)#----------------------------DB_INTERVAL = 240000#----------------------------# LOGGING#----------------------------LOGLEVEL=1MAX_LOGDAYS=2

Table 1. Connection and Login Attributes

Attribute Dfault Value Description

SAP_INSTANCE none Describes the connection attributesof the SAP

EXTCOMPANY Worldline 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

Table 2. CCMS Attributes




CCMS_ENABLED False Enable/disable CCMS monitoring

CCMS_MONITOR_SET none The name of the SAP Monitor-Set wewant to access.

CCMS_MONITOR_NAME * All SAP Monitors that can be foundinside the given SAP Monitor Set.

CCMS_SEND_INDICATIONS True Enable/disable sending messages tothe BOOM Indication Browser

CCMS_PERF_ENABLED False Enable/disable PerformanceCollection

DB_INTERVAL 60000 Interval of the data collector

Table 3. Logging Attributes


LOGLEVEL 1 loglevel

MAX_LOGDAYS 2 Number of history log files

Table 4. Optional Destination Attributes

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)

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.

Please see chapter CCMS Pattern for more information on how to define ccms pattern.

5.2.3. SAP_ccms_perf.props

All ccms values that should be stored as performance data must be defined in the SAP_ccms_perf.props:



#----------------------------------------------# BUFFERS#----------------------------------------------SAP_BUFFER|DOUBLE|ProgramDirectoryUsed|SAP_Program_DirectoryUsedSAP_BUFFER|DOUBLE|ProgramHitRatio|SAP_Program_HitRatioSAP_BUFFER|DOUBLE|ProgramSpaceUsed|SAP_Program_SpaceUsedSAP_BUFFER|DOUBLE|ProgramSwap|SAP_Program_Swap… etc.

Please see chapter CCMS Performance Data for more information on how to configureperformance data.

5.3. Trigger PolicyMake sure that the defined property files in the Monitor Call are correct:

5.4. Configuration Steps SummaryBefore you start with the configuration of the SAPMPI, make sure that the boom agent where you are going todeploy the SAPMPI has the SAPJCo3 Connector installed.



The recommended configuration sequence is:

1. deploy the SAPMPI Assignment and make sure the package contains the following elements:

a. SAPMPI Binary Package

b. all necessary SAPMPI Policies

Please make sure that you do not deploy the "Trigger Policy" during installation!

Make sure the boom agent is still running correctly.

2. Run action "Get Version" to test if the SAPMPI is working at all.

3. Run action "SAP Add Instance" to add a SAP Instances.Check the result to see if the boom agent is able to connect correctly to the SAP System.If there are some problems here, please re-check your login credentials and remove/re-add the SAP Instance ifnecessary.

If the SAP Instance has been added successfully, you can go on with step5.

4. Adjust the following property files:

a. SAP_ccms_config.props

b. SAP_ccms_pattern.props.

5. Configure "Trigger Policy":The best interval during the configuration phase might be 1 minute.

6. Deploy the "Trigger Policy".Depending on the amount of data that have to be fetched from the SAP System, it might take a while untilyou can see the first indications in the Indication Browser.

7. If there are some ccms data missing, check the following:

a. SAP_ccms_pattern.props → check if the key and the Policy Name is correct

b. Check if the the defined Policy exists and is correctly deployed

c. In case of an Indication Policy, check the Object field in the Filter section. This field must contain exactly thekey you have defined in the pattern file.

If all CCMS data are fetched correctly, you can go on with step10.

8. Configure the SAP_ccms_perf.props file.

9. Activate the performance data inside the Trigger Policy.



10. Redeploy the Trigger Policy.

If all Performance Data are correctly collected in the boom performance database, you can do the laststeps.

11. Un-Deploy the Trigger Policy

12. Check/update the Policy Interval



Chapter 6. Appendix

6.1. More Connection Attributes

The following attributes are optional and normally not needed! Before you add any optionalconnection attributes to your SAP_ccms_config.props file, make sure the SAPMPI is runningcorrectly.

Here a list of supported attributes that can be used for a client connection to a remote SAP system. Depending on thetype of middleware layer loaded, the properties that need to be provided by the implementation of theDestinationDataProvider (com.sap.conn.jco.ext.DestinationDataProvider) may vary.

Table 5. SAP Optional Connection Attributes


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 clientThree-digit client number; preserve leading zeros if they appear inthe number

jco.client.user Logon user

jco.client.alias_user Logon user alias

jco.client.passwd Logon password

jco.client.lang Logon languageISO two-character language code (for example, EN, DE, FR), or SAP-specific single-character language code. As a result, only the firsttwo characters are ever used, even if a longer string is entered. Thedefault is EN.

jco.client.saprouter If the connection needs to be made through a firewall using aSAPRouter, specify the SAPRouter parameters in the followingformat: /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 defaultsapms<sysid>

jco.client.gwhost Host name of the SAP gatewayExample: 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 notrace, 1,2,3 different amount of trace)

jco.client.codepage Identifies the initial code page in SAP notation. A code page is usedwhenever character data is processed on the application server,appears on the front end, or is rendered by a printer. Four-digit SAPcode page number

jco.client.mysapsso2 Indicates whether or not to use the specified SAP Cookie Version 2 asthe login ticket instead of user ID and password. User:$MYSAPSSO2$ Password: Base64-encoded ticket Login with singlesign-on is based on secure network connection (SNC) encryption andcan only be used in combination with an SNC.

jco.client.x509cert Indicates whether or not to use the specified X509 certificate as thelogin certificate instead of user ID and password. User: $X509CERT$Password: Base64-encoded ticket Login with X509 is based on securenetwork connection (SNC) encryption and can only be used incombination 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 adestination 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 canbe closed (default is 600000msec=10min).

jco.destination.expiration_check_period Interval in ms with which the timeout checker thread checks theconnections in the pool for expiration

jco.destination.max_get_client_time Max time in ms to wait for a connection, if the max allowed numberof connections is allocated by the application (default is30000msec=30sec).

jco.destination.repository_destination Specifies which destination should be used as repository, i.e. use thisdestination’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 adifferent user for repository lookups

jco.destination.repository.passwd The password for a repository user. Mandatory, if a repository usershould be used.




jco.destination.repository.snc_mode Enables or disables secure network connection mode 0=off 1=onOptional: If SNC is used for this destination, it is possible to turn itoff for repository connections, if this property is set to 0. Defaults tothe value of jco.client.snc_mode

6.2. Example PoliciesTable 6. Example Policies

Category Policies

SAPMPI Basic SAP_Discover_indi.msg.xmlSAP_Discover_mon.mon.xml

SAPMPI Trigger Policy SAPTrigger_ccms.mon.xml

Background Processing SAP_Background_AbortedJobs.msg.xmlSAP_Background_ProgramErrors.msg.xmlSAP_BgService_SystemWideFreeBPWP.mon.xmlSAP_BgService_SystemWideQueueLength.mon.xml

Buffers SAP_CUA_DirectoryUsed.mon.xmlSAP_CUA_HitRatio.mon.xmlSAP_CUA_SpaceUsed.mon.xmlSAP_CUA_Swap.mon.xmlSAP_FieldDescription_DirectoryUsed.mon.xmlSAP_FieldDescription_HitRatio.mon.xmlSAP_FieldDescription_SpaceUsed.mon.xmlSAP_FieldDescription_Swap.mon.xmlSAP_GenericKey_DirectoryUsed.mon.xmlSAP_GenericKey_HitRatio.mon.xmlSAP_GenericKey_SpaceUsed.mon.xmlSAP_GenericKey_Swap.mon.xmlSAP_InitialRecords_DirectoryUsed.mon.xmlSAP_InitialRecords_HitRatio.mon.xmlSAP_InitialRecords_SpaceUsed.mon.xmlSAP_InitialRecords_Swap.mon.xmlSAP_Program_DirectoryUsed.mon.xmlSAP_Program_HitRatio.mon.xmlSAP_Program_SpaceUsed.mon.xmlSAP_Program_Swap.mon.xmlSAP_Screen_DirectoryUsed.mon.xmlSAP_Screen_HitRatio.mon.xmlSAP_Screen_SpaceUsed.mon.xmlSAP_Screen_Swap.mon.xmlSAP_ShortNameTAB_DirectoryUsed.mon.xmlSAP_ShortNameTAB_HitRatio.mon.xmlSAP_ShortNameTAB_SpaceUsed.mon.xmlSAP_ShortNameTAB_Swap.mon.xmlSAP_SingleRecord_DirectoryUsed.mon.xmlSAP_SingleRecord_HitRatio.mon.xmlSAP_SingleRecord_SpaceUsed.mon.xmlSAP_SingleRecord_Swap.mon.xmlSAP_TableDefinition_DirectoryUsed.mon.xmlSAP_TableDefinition_HitRatio.mon.xmlSAP_TableDefinition_SpaceUsed.mon.xmlSAP_TableDefinition_Swap.mon.xml



Category Policies

Dialog SAP_Dialog_DBRequestTime.mon.xmlSAP_Dialog_DialogSteps.mon.xmlSAP_Dialog_EndedWpDIA.mon.xmlSAP_Dialog_ErrorFreqInWpDIA.mon.xmlSAP_Dialog_ErrorsInWpDIA.mon.xmlSAP_Dialog_FrontEndNetTime.mon.xmlSAP_Dialog_FrontendResponseTime.mon.xmlSAP_Dialog_GuiCallbackTime.mon.xmlSAP_Dialog_Load-GenTime.mon.xmlSAP_Dialog_LogonLoadQuality.mon.xmlSAP_Dialog_LongRunners.mon.xmlSAP_Dialog_MonitoringTime.mon.xmlSAP_Dialog_NumberOfWpDIA.mon.xmlSAP_Dialog_PrivModeUtilisation.mon.xmlSAP_Dialog_ProgramErrors.msg.xmlSAP_Dialog_QueueLength.mon.xmlSAP_Dialog_QueueTime.mon.xmlSAP_Dialog_ResponseTime.mon.xmlSAP_Dialog_ResponseTime_StdTran.mon.xmlSAP_Dialog_RollTime.mon.xmlSAP_Dialog_UsersLoggedIn.mon.xmlSAP_Dialog_Utilisation.mon.xml

FileSystem SAP_FreeSpace_C.mon.xml

Operating System SAP_CPU_Utilization.mon.xml

Oracle SAP_Oracle_FreeSpace_PSAPIDESAP_Oracle_FreeSpace_PSAPIDE700SAP_Oracle_FreeSpace_PSAPIDEFACTSAP_Oracle_FreeSpace_PSAPIDEODSSAP_Oracle_FreeSpace_PSAPIDEUSRSAP_Oracle_FreeSpace_PSAPTEMPSAP_Oracle_FreeSpace_PSAPUNDOSAP_Oracle_FreeSpace_SYSAUXSAP_Oracle_FreeSpace_SYSTEM

Spool System SAP_Spool_FrontendWaitTime.mon.xmlSAP_Spool_Status.msg.xmlSAP_Spool_UsedNumbers.mon.xml

Syslog SAP_R3Syslog_AbapErrorInUpdate.msg.xmlSAP_R3Syslog_Background.msg.xmlSAP_R3Syslog_BasisSystem.msg.xmlSAP_R3Syslog_CCMS.msg.xmlSAP_R3Syslog_Communication.msg.xmlSAP_R3Syslog_Database.msg.xmlSAP_R3Syslog_Security.msg.xmlSAP_R3Syslog_SyslogFreq.mon.xml

System Errors SAP_R3Abap_Shortdumps.msg.xmlSAP_R3Abap_ShortdumpsFreq.mon.xml

6.3. Example Proptery Files



Example Configuration File

#-------------------------# SAP Instance#-------------------------SAP_INSTANCE=<INSTANCE_NAME>#-------------------------# CCMS Montior-Set(RZ20)#-------------------------CCMS_ENABLED=trueCCMS_MONITOR_SET=SAP CCMS Monitor TemplatesCCMS_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=3MAX_LOGDAYS=2

Example 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#*::*::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#------------------------------------------*::*::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

Example CCMS Performance File

#----------------------------------------------# 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_SystemWideFreeBPWPSAP_BACKGROUND|DOUBLE|SystemWideQueueLength|SAP_BgService_SystemWideQueueLength#------------------------------------------# BUFFERS#------------------------------------------SAP_BUFFER|DOUBLE|ProgramDirectoryUsed|SAP_Program_DirectoryUsedSAP_BUFFER|DOUBLE|ProgramSpaceUsed|SAP_Program_SpaceUsedSAP_BUFFER|DOUBLE|ProgramHitRatio|SAP_Program_HitRatioSAP_BUFFER|DOUBLE|ProgramSwap|SAP_Program_SwapSAP_BUFFER|DOUBLE|GenKeyDirectoryUsed|SAP_GenericKey_DirectoryUsedSAP_BUFFER|DOUBLE|GenKeySpaceUsed|SAP_GenericKey_SpaceUsedSAP_BUFFER|DOUBLE|GenKeyHitRatio|SAP_GenericKey_HitRatioSAP_BUFFER|DOUBLE|GenKeySwap|SAP_GenericKey_SwapSAP_BUFFER|DOUBLE|SingleRecordDirectoryUsed|SAP_SingleRecord_DirectoryUsedSAP_BUFFER|DOUBLE|SingleRecordSpaceUsed|SAP_SingleRecord_SpaceUsedSAP_BUFFER|DOUBLE|SingleRecordHitRatio|SAP_SingleRecord_HitRatioSAP_BUFFER|DOUBLE|SingleRecordSwap|SAP_SingleRecord_SwapSAP_BUFFER|DOUBLE|ScreenDirectoryUsed|SAP_Screen_DirectoryUsedSAP_BUFFER|DOUBLE|ScreenSpaceUsed|SAP_Screen_SpaceUsedSAP_BUFFER|DOUBLE|ScreenHitRatio|SAP_Screen_HitRatioSAP_BUFFER|DOUBLE|ScreenSwap|SAP_Screen_SwapSAP_BUFFER|DOUBLE|CUADirectoryUsed|SAP_CUA_DirectoryUsedSAP_BUFFER|DOUBLE|CUASpaceUsed|SAP_CUA_SpaceUsedSAP_BUFFER|DOUBLE|CUAHitRatio|SAP_CUA_HitRatioSAP_BUFFER|DOUBLE|CUASwap|SAP_CUA_SwapSAP_BUFFER|DOUBLE|TableDefDirectoryUsed|SAP_TableDefinition_DirectoryUsedSAP_BUFFER|DOUBLE|TableDefSpaceUsed|SAP_TableDefinition_SpaceUsedSAP_BUFFER|DOUBLE|TableDefHitRatio|SAP_TableDefinition_HitRatioSAP_BUFFER|DOUBLE|TableDefSwap|SAP_TableDefinition_SwapSAP_BUFFER|DOUBLE|FieldDescDirectoryUsed|SAP_FieldDescription_DirectoryUsedSAP_BUFFER|DOUBLE|FieldDescSpaceUsed|SAP_FieldDescription_SpaceUsedSAP_BUFFER|DOUBLE|FieldDescHitRatio|SAP_FieldDescription_HitRatioSAP_BUFFER|DOUBLE|FieldDescSwap|SAP_FieldDescription_SwapSAP_BUFFER|DOUBLE|InitRecordsDirectoryUsed|SAP_InitialRecords_DirectoryUsedSAP_BUFFER|DOUBLE|InitRecordsSpaceUsed|SAP_InitialRecords_SpaceUsedSAP_BUFFER|DOUBLE|InitRecordsHitRatio|SAP_InitialRecords_HitRatioSAP_BUFFER|DOUBLE|InitRecordsSwap|SAP_InitialRecords_SwapSAP_BUFFER|DOUBLE|ShortNameDirectoryUsed|SAP_ShortNameTAB_DirectoryUsedSAP_BUFFER|DOUBLE|ShortNameSpaceUsed|SAP_ShortNameTAB_SpaceUsedSAP_BUFFER|DOUBLE|ShortNameHitRatio|SAP_ShortNameTAB_HitRatioSAP_BUFFER|DOUBLE|ShortNameSwap|SAP_ShortNameTAB_Swap#------------------------------------------# DIALOG#------------------------------------------SAP_DIALOG|BIGINT|DBRequestTime|SAP_Dialog_DBRequestTimeSAP_DIALOG|BIGINT|ResponseTime|SAP_Dialog_ResponseTimeSAP_DIALOG|BIGINT|DialogSteps|SAP_Dialog_DialogStepsSAP_DIALOG|BIGINT|EndedWpDIA|SAP_Dialog_EndedWpDIASAP_DIALOG|BIGINT|ResponseTimeStdTran|SAP_Dialog_ResponseTime_StdTranSAP_DIALOG|BIGINT|ErrorFreqInWpDIA|SAP_Dialog_ErrorFreqInWpDIASAP_DIALOG|BIGINT|ErrorsInWpDIA|SAP_Dialog_ErrorsInWpDIASAP_DIALOG|BIGINT|FrontEndNetTime|SAP_Dialog_FrontEndNetTimeSAP_DIALOG|BIGINT|FrontendResponseTime|SAP_Dialog_FrontendResponseTimeSAP_DIALOG|BIGINT|GuiCallbackTime|SAP_Dialog_GuiCallbackTime



SAP_DIALOG|BIGINT|LoadAndGenTime|SAP_Dialog_Load-GenTimeSAP_DIALOG|BIGINT|LogonLoadQuality|SAP_Dialog_LogonLoadQualitySAP_DIALOG|BIGINT|LongRunners|SAP_Dialog_LongRunnersSAP_DIALOG|BIGINT|MonitoringTime|SAP_Dialog_MonitoringTimeSAP_DIALOG|BIGINT|NumberOfWpDIA|SAP_Dialog_NumberOfWpDIASAP_DIALOG|BIGINT|PrivModeUtilisation|SAP_Dialog_PrivModeUtilisationSAP_DIALOG|BIGINT|QueueLength|SAP_Dialog_QueueLengthSAP_DIALOG|BIGINT|QueueTime|SAP_Dialog_QueueTimeSAP_DIALOG|BIGINT|RollTime|SAP_Dialog_RollTimeSAP_DIALOG|BIGINT|UsersLoggedIn|SAP_Dialog_UsersLoggedInSAP_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#------------------------------------------SAP_ORACLE|DOUBLE|PsapideFreespace|SAP_Oracle_FreeSpace_PSAPIDESAP_ORACLE|DOUBLE|PSAPIDE700_Freespace|SAP_Oracle_FreeSpace_PSAPIDE700SAP_ORACLE|DOUBLE|PSAPIDEFACT_Freespace|SAP_Oracle_FreeSpace_PSAPIDEFACTSAP_ORACLE|DOUBLE|PSAPIDEODS_Freespace|SAP_Oracle_FreeSpace_PSAPIDEODSSAP_ORACLE|DOUBLE|PSAPIDEUSR_Freespace|SAP_Oracle_FreeSpace_PSAPIDEUSRSAP_ORACLE|DOUBLE|PSAPTEMP_Freespace|SAP_Oracle_FreeSpace_PSAPTEMPSAP_ORACLE|DOUBLE|PSAPUNDO_Freespace|SAP_Oracle_FreeSpace_PSAPUNDOSAP_ORACLE|DOUBLE|SYSAUX_Freespace|SAP_Oracle_FreeSpace_SYSAUXSAP_ORACLE|DOUBLE|SYSTEM_Freespace|SAP_Oracle_FreeSpace_SYSTEM#------------------------------------------# SPOOL_SYSTEM#------------------------------------------SAP_SPOOL_SYSTEM|BIGINT|UsedNumbers|SAP_Spool_UsedNumbersSAP_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



Chapter 7. Copyright & TrademarksCopyright 2000-2018

The following software may be included in this product:

NanoHTTPD; Use of any of this software is governed by the terms of the license below:

License

(The Modified BSD Licence)

Copyright © 2001,2005-2008 Jarno Elonen <[email protected]>

Redistribution and use in source and binary forms, with or without modification, are permitted providedthat the following conditions are met:

* Redistributions of source code must retain the above copyright notice, this list of conditions and thefollowing disclaimer.

* Redistributions in binary form must reproduce the above copyright notice, this list of conditions andthe following disclaimer in the documentation and/or other materials provided with the distribution.

* The name of the author may not be used to endorse or promote products derived from this software withoutspecific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUTNOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS ORSERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OFLIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING INANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

http://elonen.iki.fi/code/nanohttpd


JFreeChart; Use of any of this software is governed by the terms of the license below:

(C)opyright 2000-2007 by Object Refinery Limited and Contributors.

JFreeChart library is covered by LGPL.

The source code of the JFreeChart is available on demand.

The text of the license is available at http://www.gnu.org/licenses/lgpl.html and in the file lgpl-2.1.txtof this distribution.

http://www.jfree.org




The Trilead SSH for Java library is released under a BSD style license. Copyright (c) 2007 Trilead AG(http://www.trilead.com) All rights reserved. Redistribution and use in source and binary forms, with orwithout modification, are permitted provided that the following conditions are met: a.) Redistributions ofsource code must retain the above copyright notice, this list of conditions and the following disclaimer.b.) Redistributions in binary form must reproduce the above copyright notice, this list of conditions andthe following disclaimer in the documentation and/or other materials provided with the distribution. c.)Neither the name of Trilead nor the names of its contributors may be used to endorse or promote productsderived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THECOPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOTLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANYTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.Trilead SSH-2 for Java includes code that was written by Dr. Christian Plattner during his PhD at ETHZurich. The license states the following: Copyright (c) 2005 - 2006 Swiss Federal Institute of Technology(ETH Zurich), Department of Computer Science (http://www.inf.ethz.ch), Christian Plattner. All rightsreserved. Redistribution and use in source and binary forms, with or without modification, are permittedprovided that the following conditions are met: a.) Redistributions of source code must retain the abovecopyright notice, this list of conditions and the following disclaimer. b.) Redistributions in binary formmust reproduce the above copyright notice, this list of conditions and the following disclaimer in thedocumentation and/or other materials provided with the distribution. c.) Neither the name of ETH Zurichnor the names of its contributors may be used to endorse or promote products derived from this softwarewithout specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS ANDCONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THECOPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OFUSE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER INCONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USEOF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The Java implementations of the AES,Blowfish and 3DES ciphers have been taken (and slightly modified) from the cryptography package releasedby "The Legion Of The Bouncy Castle". Their license states the following: Copyright (c) 2000 - 2004 TheLegion Of The Bouncy Castle (http://www.bouncycastle.org) Permission is hereby granted, free of charge, toany person obtaining a copy of this software and associated documentation files (the "Software"), to dealin the Software without restriction, including without limitation the rights to use, copy, modify, merge,publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom theSoftware is furnished to do so, subject to the following conditions: The above copyright notice and thispermission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE ISPROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THEWARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OFCONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHERDEALINGS IN THE SOFTWARE.



The following software may be included in this product: joeSNMP is Copyright (C) 2002-2003 Blast InternetServices, Inc. All rights reserved. joeSNMP is a derivative work, containing both original code, includedcode and modified code that was published under the GNU Lesser General Public License. Copyright (C) 1999-2001 Oculan Corp. All rights reserved. Copyrights for modified and included code are included in theindividual source files. This library is free software; you can redistribute it and/or modify it under theterms of the GNU Lesser General Public License as published by the Free Software Foundation; eitherversion 2.1 of the License, or (at your option) any later version. This library is distributed in the hopethat it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY orFITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You shouldhave received a copy of the GNU Lesser General Public License along with this library; if not, write tothe Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA See:http://www.fsf.org/copyleft/lesser.html For more information contact: joeSNMP Licensing

Use of this software is governed by the license terms available on http://www.bes-worldline.com

SAP is a registered trademark of SAP AG in Germany and in several other countries.

netage solutions is a trademark of netage solutions GmbH

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, othercountries, or both.

HP and OpenView are registered trademarks of the Hewlett-Packard Company in the United States and otherjurisdictions.

Linux is a U.S. registered trademark of Linus Torvalds.

Microsoft, Windows, Windows 2000, Windows Server 2003, and Windows NT are either registered trademarks ortrademarks of Microsoft Corporation in the United States and/or other countries.

MySQL is a registered trademark of 2000-2008 MySQL AB, 2008 Sun Microsystems. in the United States, theEuropean Union and other countries. MySQL Network is a trademark of 2000-2008 MySQL AB, 2008 SunMicrosystems.

All SPARC trademarks are trademarks or registered trademarks of SPARC International, Inc. in the UnitedStates and other countries.

UNIX is a registered trademark in the United States and other countries, exclusively licensed throughX/Open Company, Ltd.

All other product names are the property of their respective trademark or service mark holders and arehereby acknowledged.



Chapter 8. ContactWorldline Germany GmbHHeadquarter:Hahnstraße 2560528 FrankfurtGermanyT: +49 69 6657-10F: +49 69 6657-1211

http://www.bes-worldline.comEmail: [email protected]



http://www.bes-worldline.com

mailto:[email protected]

Documents

boom SAPMPI 2 - bes-worldline.com · Chapter 4. Concept 4.1. CCMS Pattern 4.1.1. Pattern Definition SAPMPI Patterns are used to map the SAP ccms data to the appropriate boom Policies