CCMS Agents Features, Installation and Operation

CCMS Agents

SAP AG CCMS Agents: Features, Installation, and Operation January 15, 2007

Page 1 of 115

Version 4.7 (Patch Collection 2006/5)January 15, 2007

CCMS Agents:Features, Installation, and Operation

SAP AGNeurottstr. 16

D-69190 Walldorf

CCMS Agents


Page 2 of 115

Copyright© Copyright 2007 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software componentsof other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint®, and SQL Server® are registeredtrademarks of Microsoft Corporation.

IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA®, AIX®, S/390®, AS/400®,OS/390®, OS/400® iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®,Netfinity®, Tivoli®, Informix, and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USAand/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1® und Motif® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®,MultiWin®, and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide WebConsortium, Massachusetts Institute of Technology.

JAVA® is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technologyinvented and implemented by Netscape.

SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentioned herein aswell as their respective logos are trademarks or registered trademarks of SAP AG in Germany and severalother countries all over the world. All other product and service names mentioned are trademarks of theirrespective companies.

CCMS Agents


Page 3 of 115

Contents0. Structure and Use of this Document................................................................. 71. Introduction......................................................................................................... 82. Functional Principle of the CCMS Agents ........................................................ 92.1. SAPCCMSR .................................................................................................................... 9

2.2. SAPCCMSR with Option j2ee ....................................................................................... 102.2.1 Examples.................................................................................................................. 10

2.2.1.1 Monitored System with no ABAP Instances........................................................................ 10

2.2.1.2 Monitored System with J2EE and ABAP Instances ............................................................ 11

2.2.1.3 Monitored System with Java and ABAP Instances, and a CEN......................................... 12

2.3. SAPCCM4X .................................................................................................................. 12

2.4. SAPCM3X..................................................................................................................... 13

2.5. Communication.............................................................................................................. 13

3. Installing CCMS Agents for NetWeaver Components.................................... 153.1. Installing an Agent on an ABAP Instance....................................................................... 17

3.2. Installing an Agent on a Java Instance (Java Standalone System) ................................... 18

3.3. Installing an Agent on a Java Instance (Double-Stack System) ....................................... 203.4. Installing an Agent on a SAP Web AS 6.20 Java Instance/Other Hosts........................... 22

4. Installing and Registering the CCMS Agents for Experts ............................. 244.1. Prerequisites for the Installation ..................................................................................... 24

4.2. Downloading the CCMS Agents .................................................................................... 25

4.3. Copying the CCMS Agent to the Desired Directory ....................................................... 26

4.4. Creating the Required Configuration Files...................................................................... 264.4.1 Configuration File for Monitoring Log Files............................................................. 274.4.2 Configuration File for Monitoring Operating System Data........................................ 274.4.3 Profile File of the CCMS Agents .............................................................................. 27

4.4.3.1 Structure of the Profile File ................................................................................................... 27

4.4.3.2 Example Profile File .............................................................................................................. 29

4.4.4 SAPCCMSR.INI: Configuration File for the CCMS Agents ..................................... 294.4.4.1 Structure of the SAPCCMSR.INI Configuration File ......................................................... 30

4.4.4.2 Example SAPSSMSR.INI Agent Configuration File .......................................................... 32

4.5. Registering the CCMS Agents........................................................................................ 32

CCMS Agents


Page 4 of 115

4.5.1 Creating the CSMREG User ..................................................................................... 334.5.2 Automatically Creating the CSMCONF Start File..................................................... 344.5.3 Registration with the Agent Registration Tool .......................................................... 344.5.4 Registering the CCMS Agents in Dialog................................................................... 354.5.5 Alternative: Dialog-Free Registration of CCMS Agents............................................ 38

4.5.5.1 Structure of the CSMCONF Start File.................................................................................. 38

4.5.5.2 Example CSMCONF Start File............................................................................................. 41

4.5.6 Registering SAPCCMS with the Option -j2ee........................................................... 414.5.6.1 Registering SAPCCMS with the Option -j2ee in Dialog .................................................... 42

4.5.6.2 Dialog-Free Registration of SAPCCMS with the Option -j2ee .......................................... 42

4.5.6.3 Creating Customizing Destination for SAPCCMSR –j2ee................................................. 43

4.5.7 Starting the Agent..................................................................................................... 454.5.8 SAPCCM4X: Creating the RFC Connections ........................................................... 45

4.6. Working Directory and Log Files of the CCMS Agents.................................................. 474.6.1 Working Directory.................................................................................................... 474.6.2 Log Files .................................................................................................................. 484.6.3 Trace Files................................................................................................................ 49

5. Advanced Functions of the CCMS Agents ..................................................... 505.1. Monitoring Log Files ..................................................................................................... 51

5.1.1 Types of Monitored Log Files................................................................................... 515.1.2 Structure of the Log File Template of the Log File Agent ......................................... 53

5.1.2.1 General Settings for the Monitored Log Files...................................................................... 53

5.1.2.2 Monitored Search Pattern in the Monitored Log Files ........................................................ 56

5.1.2.3 Search Pattern to be Output in the Monitored Log Files ..................................................... 56

5.1.3 Example Log File Templates .................................................................................... 575.1.3.1 Oracle Alert Log .................................................................................................................... 58

5.1.3.2 Trace Files of the SAP Work Processes ............................................................................... 58

5.1.3.3 Log File of the SAPCCMSR CCMS Agent ......................................................................... 59

5.1.3.4 Log File for the Backups of an Oracle Database ................................................................. 61

5.1.4 Display for Log File Monitoring in the Alert Monitor............................................... 615.2. Setting Up the Sending and Receiving of SNMP Traps Using CCMS Agents................. 63

5.2.1 Adjusting the Configuration File for Sending SNMP Traps ...................................... 645.2.2 Adjusting the Configuration File for Receiving SNMP Traps ................................... 675.2.3 Displaying Received SNMP Traps in the Alert Monitor............................................ 68

CCMS Agents


Page 5 of 115

5.3. Event Log Monitoring with CCMS Agents..................................................................... 695.3.1 Structure of the Event Log Template ........................................................................ 715.3.2 Displaying the Event Log Monitoring in the Alert Monitor....................................... 73

5.4. Monitoring Operating System Data with CCMS Agents................................................. 755.4.1 Operating System Data Displayed in the Alert Monitor ............................................ 765.4.2 Configuring the Monitoring of Operating System Data............................................. 765.4.3 Structure of the SAPOSCOL Filter File oscolfile.txt ................................................. 775.4.4 Example SAPOSCOL Filter File oscolfile.txt ........................................................... 795.4.5 Monitoring Selected Processes.................................................................................. 81

5.5. Alert Logging for CCMS Agents.................................................................................... 845.5.1 Activating the Alert Logging .................................................................................... 855.5.2 Structure of the Alert Log File .................................................................................. 855.5.3 Example Alert Log File ............................................................................................ 86

5.6. Displaying File Contents in the Alert Monitor ................................................................ 865.6.1 Example of Defining Displayable File Contents (SAPCCMSR.INI) ......................... 875.6.2 Assigning the Required Analysis Method ................................................................. 87

5.7. Transferring GRMG Customizing Files to CEN............................................................. 88

5.8. Including Additional Functions in CCMS Agents........................................................... 88

5.9. Registering with Multiple Central Monitoring Systems .................................................. 895.9.1 Start File CSMCONF with Multiple Central Monitoring Systems............................. 89

5.10. Monitoring Multiple Systems with an Identical System ID......................................... 90

5.11. Transferring Distributed Statistics Records with CCMS Agents ................................. 92

6. Displaying Agent Data in the Central Monitoring System............................. 936.1. Monitoring Contexts of the CCMS Agents in the Monitoring System............................. 93

6.2. Creating CCMS Agent Monitors in the Central Monitoring System ............................... 946.2.1 SAPCM3X: Creating a Rule-Based Monitor............................................................. 946.2.2 SAPCCMSR: Creating a Rule-Based Monitor .......................................................... 95

6.3. Self-Monitoring of the CCMS Agents ............................................................................ 96

6.4. Displaying Agent Data in the Topology Display............................................................. 976.4.1 Calling the Display of Agent Data in the Topology Display...................................... 976.4.2 Data Displayed About CCMS Agents ....................................................................... 986.4.3 Commands in the Topology Display....................................................................... 100

7. Controlling the CCMS Agents........................................................................ 102

CCMS Agents


Page 6 of 115

7.1. Deregistering CCMS Agents ........................................................................................ 102

7.2. Starting and Stopping CCMS Agents ........................................................................... 103

7.3. Displaying the Status of a CCMS Agent....................................................................... 103

7.4. Displaying the Version of a CCMS Agent .................................................................... 104

8. Questions and Answers ................................................................................. 1058.1. General ........................................................................................................................ 105

8.2. SAPCCMSR/SAPCM3X ............................................................................................. 106

8.3. SAPCCMSR –j2ee....................................................................................................... 107

8.4. SAPCCM4X ................................................................................................................ 108

9. Additional Information.................................................................................... 1099.1. SAP Service Marketplace and SAP Library.................................................................. 109

9.2. Important SAP Notes About CCMS Agents ................................................................. 110

9.3. Copyright ..................................................................................................................... 113

CCMS Agents


Page 7 of 115

0. Structure and Use of this Document

The sections of this document cover the following:

Sections 1 and 2

These sections contain an introduction to the meaning and functions of the CCMS agents.

Section 3

This section contains the installation and registration of CCMS agents for the most importantmonitored components. If you want to use CCMS agents to monitor software components inthe context of a standard installation, follow the procedures in this section.

Section 4

This section describes the installation and registration of CCMS agents in general terms. Inmost cases, you will not require this information, since the procedures in section 3 will besufficient. However, since many of the advanced functions of the CCMS agents (section 5)have a direct influence on the installation and registration of the agents, you should workthrough this section if you want to individually tailor the advanced functions of the CCMSagents.

Section 5

This section describes how you can use the advanced functions of the CCMS agents for yourindividual monitoring tasks. These include, for example, the monitoring of log files, sendingand receiving SNMP traps, monitoring processes, or displaying the contents of files.

Section 6

This section describes how monitoring information that is transferred to the centralmonitoring system CEN using CCMS agents is displayed in CEN. It also introduces the mostimportant functions for monitoring and controlling CCMS agents from CEN.

Section 7

This section contains the functions for controlling CCMS agents locally.

Section 8

This section contains a summary of possible problems and their solutions in the context ofCCMS agents.

Section 9

This section contains the most important additional information about CCMS agents.

CCMS Agents


Page 8 of 115

1. Introduction

The monitoring architecture provides an infrastructure for monitoring your IT environment andits components. Monitoring data is stored in the shared memory of every server with a runningSAP instance or a running agent.

Read and write access from the central monitoring system is possible in two different ways:

Using a defined ABAP interface, in the case of an SAP instance

Using the CCMS agent, in the case of any server on which the agent is installed and active

CCMS agents are independent processes with an interface through RFC to a central monitoringsystem and an interface to the shared memory. They therefore allow you to:

Include SAP components that do not have an ABAP interface, such as the J2EE Engine or theInternet Transaction Server (ITS)

Include components that are not part of the SAP environment

Make available an alternative connection route to a shared memory segment

Optimize performance when reading and writing monitoring attributes and alerts, by using thepush technology

Connect to a shared memory segment without requiring a free work process

Agents also make entirely new monitoring functions possible within the monitoring architecture:

You can monitor any log files.

You can monitor processes at operating system level. The actual monitoring is performedusing the operating system collector SAPOSCOL. For detailed information about it, see[SAPOsCol].

You can create central auto-reactions in which an auto-reaction method is started in thecentral monitoring system as a reaction to an alert in a monitored system. For detailedinformation about it, see [AutoRea].

Agents monitor network data, including:

- The configuration of the network environment, such as an interface or Domain NameSystem (DNS)

- Network metrics, such as the length of time taken for a DNS address resolution

CCMS Agents


Page 9 of 115

2. Functional Principle of the CCMS Agents

The runtime information for the monitoring objects is stored in monitoring segments. A CCMSagent always uses exactly one monitoring segment that is either in its local process memory or inthe local shared memory.

2.1. SAPCCMSR

This agent monitors components on which there is no active SAP instance (such as log files,TREX, stand-alone databases, or operating system components). SAPCCMSR is closelyconnected with the monitoring central monitoring system.

After its installation, the CCMS agent SAPCCMSR attempts to attach itself to a monitoringsegment in shared memory when it is started. If this segment does not yet exist, the agent createsit. SAPCCMSR always works in a shared memory segment that is independent of running SAPsystems. The central monitoring system must have a release status of at least SAP Basis 4.6B.

Central MonitoringSystem

Any Instance (SAP/Non-SAP)

SAPOSCOL

Log

RZ20

DLL

SAPCCMSR

Application

ApplicationShared Memory

CCMS Agents


Page 10 of 115

2.2. SAPCCMSR with Option j2ee

The functional principle of SAPCCMSR has been extended in case the SAPCCMSR CCMSagent is monitoring a J2EE Engine. In a case of this type, it must be possible that the monitoringsegment of the SAPCCMSR agent does not belong to the central monitoring system. This isachieved by extending the system term to include Java components (such as J2EE Cluster). TheSAPCCMSR agent with the -j2ee option exists for this purpose.

To use SAPCCMSR with option j2ee, you need a central monitoring system as ofSAP Web AS 6.40 Support Package 1.The monitored J2EE Instance requires at least SAP Web AS 6.30 Support Package 4.

It is easier to understand the other steps if you use the following analogies:

ABAP Java

ABAP System J2EE Cluster

Application server J2EE Engine

Work process Virtual Machine (VM)

A system is no longer only a quantity of classical application servers with an ABAP runtimeenvironment, but simply a number of associated components that have a common system name.Combinations of ABAP instances and Java instances can also create a system, if all of these partsare combined under one system ID.

You specify the system ID and the system number of the monitored Java instanceduring the registration of the agent using the instance's profile (see Profile File of theCCMS Agents [page 27]).

When monitoring, it should be possible to display the data for the ABAP instances and the Javainstances of the same system in a central CCMS under the system ID of the monitored system. Asfar as possible, a Java instance should not be different from an ABAP instance; it should also bepossible to monitor all instances with the same system ID locally as one system unit.

2.2.1 Examples

2.2.1.1 Monitored System with no ABAP InstancesSAPCCMSR monitors an instance of a Java system and registers itself with a central systemCEN. The connection to CEN is also the primary RFC connection.

CCMS Agents


Page 11 of 115

Host D

Monitored System ABC(with no ABAP Engines)

Central Monitoring System CEN

Host A

J2EE EngineHostA_ABC_33

sapccmsr-j2ee

Host B

J2EE EngineHostA_ABC_33

sapccmsr-j2ee

ABC

HostA_ABC_33HostB_ABC_33HostC_ABC_33

Alert Monitor

Agents for Remote SAP SystemsSystemABCABCABC

DestinationSAPCCMSR.HostA.33SAPCCMSR.HostB.33SAPCCMSR.HostC.33

Topology Display

CCMS

Host C

J2EE EngineHostC_ABC_33

sapccmsr-j2ee

CEN is the primary central system in each case

2.2.1.2 Monitored System with J2EE and ABAP InstancesSAPCCMSR monitors an instance of a system in which there is still at least one ABAP instance.In this case, the agent must be primarily registered with the local system, so that the system canbe monitored locally as one unit.

System ABC (with J2EE and ABAP Engines)

Host AJ2EE Engine

HostC_ABC_33

sapccmsr-j2ee

ABAP EngineHostC_ABC_33

primäre RFC-Verbindung

Host BJ2EE Engine

HostC_ABC_33

sapccmsr-j2ee



Host CJ2EE Engine

HostC_ABC_33

sapccmsr-j2ee


Primary central system

ABC


Alert Monitor

Agents for Local SAP System ABCDestinationSAPCCMSR.HostA.33SAPCCMSR.HostB.33SAPCCMSR.HostC.33

Topology Display

CCMS

Segment NameSAP_CCMS_HostA_ABC_33_XSAP_CCMS_HostB_ABC_33_XSAP_CCMS_HostC_ABC_33_X

CCMS Agents


Page 12 of 115

2.2.1.3 Monitored System with Java and ABAP Instances, and a CENIn addition to the case described above, the local system, to which the Java instance belongs, canbe monitored by a central monitoring system CEN:

System ABC (with Java and ABAP Engines)

Host AJ2EE Engine

HostC_ABC_33

sapccmsr-j2ee



Host D

ABC


Alert Monitor

Agents for Remote SAP SystemsSystemABCABCABC

DestinationSAPCCMSR.HostA.33SAPCCMSR.HostB.33SAPCCMSR.HostC.33

Topology Display

CCMS

Host BJ2EE Engine

HostC_ABC_33

sapccmsr-j2ee



Host CJ2EE Engine

HostC_ABC_33

sapccmsr-j2ee


ABC


Alert Monitor

CCMS

Agents for the Local SAP System ABCDestinationSAPCCMSR.HostA.33SAPCCMSR.HostB.33SAPCCMSR.HostC.33

Topology Display

Segmen NameSAP_CCMS_HostA_ABC_33_XSAP_CCMS_HostB_ABC_33_XSAP_CCMS_HostC_ABC_33_X

Local MonitoringSystem ABC

CentralMonitoring

System CEN

PrimaryCentral System

Secondary Central System

2.3. SAPCCM4X

This agent improves the monitoring of ABAP instances with SAP Basis 4.X or higher. Thecentral monitoring system must have a release status of at least SAP Basis 4.6C. This agentprovides an alternative connection route to the monitoring information in the shared memory ofan ABAP instance. As this alternative connection method does not require a free work process,the access method is independent of error states of the SAP instance and is therefore more robust.

Systems as of SAP Basis 4.0 have their own CCMS monitoring architecture runtimeenvironment. This means that they have their own monitoring segment in the shared memory areaof the running system. After its installation, the SAPCCM4X agent attempts to attach itself to andto work with this monitoring segment in shared memory when it is started.

CCMS Agents


Page 13 of 115

If this segment does not exist (that is, if the monitored system is not running), the agent does notcreate it, to avoid interfering with the shared memory management in the restarting system. Inthis case, the SAPCCM4X agent works with the monitoring segment that it creates in its processmemory and the contents of which it synchronizes with the monitored system. SAPCCM4Xconstantly checks whether the monitored system is active again, and when it is, works with themonitoring segment in the shared memory again, after synchronization.

The central monitoring system automatically first attempts to read data from the monitoredsystem through the RFC destination of the CCMS agent. If the agent is not active, the systemreads the monitoring data from the monitored SAP instance using the standard RFC, aspreviously (for more information, see SAP Note 322075). Note that even if you are using theSAPCCM4X agent, you still continue to need the standard RFC connection anyway.

Central MonitoringSystem

RZ20

SAP R/3 4.X Instance

SAPCCM4X

DispatcherRZ20

Shared Memory

2.4. SAPCM3X

This agent allows the monitoring of SAP instances with SAP Basis 3.X through the CCMSmonitoring architecture. These systems do not have their own CCMS monitoring architectureruntime environment. SAPCM3X therefore works always works with a monitoring segment thatit creates in its main memory (for more information, see SAP Note 308061).

2.5. Communication

A CCMS agent communicates with the central monitoring system using RFC.

CCMS Agents


Page 14 of 115

As an RFC server, it provides access to the data in the monitoring segment. This access is, forexample, used in transaction RZ20. The agent automatically creates the local configurationfiles and the RFC destination in the central system during its registration.

You can set the frequency of the query by the monitoring architecture in the Alert Monitor.To do this, call transaction RZ20, select a node in the desired monitor, choose Properties and,on the Methods tab page, correct the value for Start the data collection method every.

The maximum frequency of this query depends on whether the underlying program isan ABAP program or a C program. In the case of ABAP programs, the maximumfrequency is five minutes, while the maximum frequency for C programs (andtherefore for CCMS agents) is one minute.

As an RFC client, it independently sends alerts and values for the monitoring attributes to thecentral monitoring SAP System (push technology). This data is then stored in a cache there toallow the system to display it more quickly or triggers central auto-reaction methods there.This improves performance as the central monitoring system then no longer needs toperiodically query the agents.

The central monitoring system must have a release status of at least SAP Web AS 6.10 forautomatic reporting of alerts. As of this release, activation of the push technology ismandatory. As of SAP Web AS 6.20, the agents also automatically report monitoringattribute values.

All CCMS agents can process several tasks simultaneously (multi-thread procedure). This meansthat they can simultaneously:

Automatically collect data

Process requests as an RFC server

Send data to the central system as an RFC client

CCMS Agents


Page 15 of 115

3. Installing CCMS Agents for NetWeaver Components

The sections of this process describe how you can install and register the appropriate CCMSagent in the context of a standard installation of SAP NetWeaver components [Support, Tutor].

These descriptions therefore extend the process Installing and Registering the CCMS Agents forExperts [page 24], which describes the installation and registration of CCMS agents in generalterms, and which explains all individual settings.

C11

Java Addin

CentralInstance

SAP NetWeaver 04 Dual Stack

SAPCCM4X

SAPCCMSR

Java Addin

DialogInstance

SAPCCM4X

SAPCCMSR

Java Addin 6.20 J2EE

SAP Web AS 6.20Java standalone

SAPCCMSR

6.20 J2EE

C12

CentralInstance

ABAP standalone

SAPCCM4XDialog

Instance

SAPCCM4X

J2E

CentralInstance

SAP NetWeaver 04Java standalone

SAPCCMSRDialog

Instance

SAPCCMSR

External

TREX, BC, Third Party, etc.

SAPCCMSR

CentralMonitoring System

Legend sapccmsr –j2ee connection (primary)

sapccm4x connectionABAP connection

sapccmsr 99 connection

sapccmsr –j2ee connection (secondary)ABAP SystemJAVA SystemExternal System

DBDB

All Possible Central Monitoring Scenarios with CCMS Agents

CEN(6.40+ ABAP)

CCMS Agents


Page 16 of 115

Prerequisites

The following prerequisites must be fulfilled in every case for the installation and registration ofa CCMS agent:

You have a central monitoring system (CEN). If possible, reserve a separate SAP system formonitoring and system management. Do not use a production system for this, to avoidunnecessary load on the system. If you are using a separate SAP system, you can easily keep thisat the newest status with regard to release or Support Package status, and profit from the newestdevelopments in the areas of monitoring and system management.

There is a CSMREG user in CEN. If this is not yet the case, create the user by proceeding asfollows (see also Creating the CSMREG User [page 33]):

a. In CEN, call transaction RZ21 and choose Technical Infrastructure Configure CentralSystem Create CSMREG User.

b. Enter and reenter any password for this user, and confirm your entries by choosing(Create CSMREG).

During the registration of the agent, you require the connection data from the agent to CEN.We recommend that you generate this data in a CSMCONF file in CEN before theregistration. To do this, proceed as follows:

a. In CEN, call transaction RZ21, and choose Technical Infrastructure Configure CentralSystem Create CSMCONF Start File for Agents.

b. Save the file at a location that is centrally available, since you require the file for all agentregistrations.

You have the required executables for the CCMS agents. To download these, proceed asdescribed in Downloading the CCMS Agents [page 25].

Process

To install a CCMS agent for one of the following components, follow the description under theappropriate link:

Installing an Agent on an ABAP Instance [page 17]

Installing an Agent on a Java Instance (Java Standalone System) [page 18]

Installing an Agent on a Java Instance (Double-Stack System) [page 20]

Installing an Agent on a SAP Web AS 6.20 Java Instance/Other Hosts [page 22]

If you want to monitor a system with CCMS agents, you need an agent for everyinstance of the system (central instance and potential dialog instances). For Javastandalone systems and double-stack systems, this is automatically insured. In the case

CCMS Agents


Page 17 of 115

of ABAP systems, you need to install the appropriate agent for every instance of thesystem.

3.1. Installing an Agent on an ABAP Instance

To monitor an ABAP instance of an SAP system, use the CCMS agent SAPCCM4X. This agentcreates an alternative connection route between the monitored instance and CEN. Since thisalternative connection route no longer requires a free work process, the access route isindependent of error states of the ABAP instance and therefore more robust.

You can also use advanced functions (see Advanced Functions of the CCMS Agents [page 50]),for example to monitor specific processes or log files on the host of the monitored instance.

If the monitored system is connected to CEN through WAN or telephony,performance problems can occur due to increased network traffic. In this case, we donot recommend that you connect the monitored system with SAPCCM4X.

Procedure

1. Log on to the host of the ABAP instance as <SID>adm (UNIX) or SAPService<SID>(Microsoft Windows), to ensure that the agent can access the shared memory.

2. Copy the start file CSMCONF to the working directory of SAPCCM4X. This is in thefollowing location:

Windows: [drive]:\usr\sap\<SysID>\<instance directory>\log\sapccm4x

UNIX: /usr/sap/<SysID>/<instance directory>/log/sapccm4x

If the directory does not exist, create it.

3. Copy the executable SAPCCM4X to the following directory:

Windows: [drive]:\usr\sap\<SysID>\SYS\exe\run

UNIX: /usr/sap/<SysID>/SYS/exe/run

If there is already an executable SAPCCM4X in this directory, use the commandsapccm4x –v to check which of the executables has the more current status, and usethat one.

4. In the directory of the executable, enter the commandsapccm4x –R pf=<profile path>.

CCMS Agents


Page 18 of 115

<profile path> specifies the instance profile of the monitored instance. Bydefault, this is:

Windows: [drive]:\usr\sap\<SysID>\SYS\profile\<SysID>_<Name of the instance directory>_<Host>

UNIX: /usr/sap/<SysID>/SYS/profile/<SysID>_<Name of the instance directory>_<Host>

5. During the registration, the system displays specifications from the CSMCONF to you againfor confirmation. Confirm the specifications by pressing the ENTER key in each case. Youonly need to enter two parameters yourself:

The password for the administration user in CEN, under which you created theCSMCONF file.

The password for the CSMREG user

6. Under UNIX, you must ensure yourself that SAPCCM4X is automatically started again whenthe host is restarted. To do this, enter the following command in the inittab(/etc/inittab):

/usr/sap/<SysID>/SYS/exe/run/sapccm4x -DCCMS pf=<profile path>

Result

You have set up an additional connection route between the monitored ABAP instance and CENusing the CCMS agent SAPCCM4X .

3.2. Installing an Agent on a Java Instance (Java Standalone System)

The monitoring data for the J2EE Engine is transferred to CEN using the CCMS agentSAPCCMSR. The agent is part of the installation package of the Engine; You only need toregister the agent once for each Java system with CEN and to start the agent.

Note that this description applies only for monitored J2EE Engines as of SAPNetWeaver 04 SP Stack 12. For J2EE Engines with a release status of SAP WebAS 6.20, follow the procedure described under Installing an Agent on a SAP WebAS 6.20 Java Instance/Other Hosts [page 22].

If you want to use the agent to monitor a J2EE Engine of a double-stack system(ABAP/Java), follow the procedure described under Installing an Agent on a JavaInstance (Double-Stack System) [page 20].

If problems occur during the registration of the agent on a Microsoft Windowsplatform, proceed as described in SAP Note 817714.

CCMS Agents


Page 19 of 115

Procedure

1. Log on to the host of a J2EE Engine of the system as <SID>adm.

2. Copy the start file CSMCONF to the following directory:

Windows: [drive]:\usr\sap\ccms\<SysID>_<Inst. No.>\sapccmsr

UNIX: /usr/sap/ccms/<SysID>_<Inst. No.>/sapccmsr

You can also save the start file in any directory that you can access from your localhost. In this case, however, you need to specify where you have saved the file duringthe registration of the agent. To do this, in the Monitoring service of the VisualAdministrator (see below), choose the Change …button, and specify the path for thestart file. The file is then automatically copied to the above directory.

3. Start the Visual Administrator by calling the start script go (UNIX) or go.bat (MicrosoftWindows), and log on with your user as the J2EE Engine administrator.

4. In the navigation bar, choose Cluster <SysID> Dispatcher Services Monitoring,and choose the CCMS Agent Configuration tab page.

5. If you want to monitor multiple systems with the same system ID, select the Long SIDindicator, and enter in this input field an identifier for the system that is unique in yourmonitored system landscape. This “long system ID” must fulfill the following conditions:

The first three characters must be the system ID.

The name can be a maximum of eight characters long.

The name must not contain an underscore (_).

6. The access data for the two required users in CEN is determined from the start file anddisplayed in the relevant fields. If necessary, you can change the user name or the client.

7. In the Password column, enter the passwords for the CEN Administration User and the CENCSMREG User. The CEN Administration User is the user with administrator authorizationwith which you created the CSMCONF start file.

If necessary, you can use the Information button to answer the following questions:

Is the instance profile of the instance to be monitored valid?

Is the utilized CSMCONF start file valid?

What is the version of the SAPCCMSR CCMS agent?8. Choose the Register button. The registration log is displayed; errors are highlighted in red.

CCMS Agents


Page 20 of 115

9. Under UNIX, the agent is automatically started by the startsap script when you start theJ2EE Engine. Under Microsoft Windows, the agent is entered as a service during theregistration, and is automatically started during a restart of the host.

As of SAP NetWeaver 2004s, however, you need to start the associated service (which wascreated during the installation of the J2EE Engine) yourself. To do this, on the MicrosoftWindows host on which the agent is running, choose Start Settings Control PanelAdministrative Tools Services, and choose the service SAPCCMSR.<Instance No.> bydouble-clicking it. Set the Start Type to Automatic, and choose Start.

Result

The J2EE Engine is now registered with CEN; you can see the corresponding monitoring data inthe Alert Monitor in CEN.

The Customizing destination has also been automatically created for all Java instances (only ifyou have left the check box enable CCMS Customizing marked), so that you can also change thethreshold values for the monitoring data from the Alert Monitor (see Creating CustomizingDestination for SAPCCMSR –j2ee [page 43]).

3.3. Installing an Agent on a Java Instance (Double-Stack System)

The monitoring data for the J2EE Engine is transferred to CEN using the SAPCCMSR CCMSagent. The agent is part of the installation package of the Engine; you only need to register theagent for the relevant agent with CEN and to start the agent.

This procedure describes the registration of a CCMS agent that is to monitor a J2EE Engine thatis part of a double-stack system of ABAP and Java instances.

In the case of a double-stack system, the agent must be registered with two systems: primarilywith the local ABAP system, and secondarily with CEN. You only need to register and start theagent once for each system.

Note that this description applies only for monitored J2EE Engines as of SAPNetWeaver 04 SP Stack 12. For J2EE Engines with a release status of SAP WebAS 6.20, proceed as described under Installing an Agent on a SAP Web AS 6.20Java Instance/Other Hosts [page 22].

If you want to monitor a J2EE Engine of a standalone Java system with the agent,proceed as described under Installing an Agent on a Java Instance (JavaStandalone System) [page 18].

If problems occur during the registration of the agent on a Microsoft Windowsplatform, proceed as described in SAP Note 817714.

CCMS Agents


Page 21 of 115

Procedure

1. Log on to the host of a J2EE Engine in the system as <SID>adm .

2. Copy the CSMCONF start file to the following directory:

Windows: [drive]:\usr\sap\ccms\<SysID>_<Inst.-Nr.>\sapccmsr

UNIX: /usr/sap/ccms/<SysID>_<Inst. No.>/sapccmsr

You can also save the start file to any directory that you can access from your localhost. In this case, however, you need to specify where you have saved the file duringthe registration of the agent. To do this, in the Monitoring service of the VisualAdministrator (see below), choose the Change …button, and specify the path of thestart file. The file is then automatically copied to the above directory.

3. Start the Visual Administrator, by calling the start script go (UNIX) or go.bat (MicrosoftWindows), and log on with your user as a J2EE Engine administrator.

4. In the navigation bar, choose Cluster <SysID> Dispatcher Services Monitoring,and choose the CCMS Agent Configuration tab page.

5. If you want to monitor multiple systems with the same system ID, select the Long SIDindicator, and enter an ID for the system in the associated field that is unique in yourmonitored system landscape. This “long system ID” must fulfill the following conditions:

The first three characters need to be the system ID.

The name must have a maximum of eight characters.

The name must not contain any underscores (_).

6. Since you want to register the agent with two systems, you need the access data for two usersfor each of these systems: one administration user and one CSMREG communication user ineach system.

7. Specify the access data for these users for the local ABAP system by making all of the entriesfor Local Administration User and Local CSMREG User in the relevant rows. If necessary,you can overwrite the predefined values.

8. Enter the access data for these users for CEN by making all of the entries for CENAdministration User and CEN CSMREG User in the relevant rows. If necessary, you canoverwrite the predefined values. The CEN Administration User is the user with administratorauthorization with which you created the CSMCONF start file.

If necessary, you can use the Information button to answer the following questions:

Is the instance profile of the instance to be monitored valid?

Is the utilized CSMCONF start file valid?

CCMS Agents


Page 22 of 115

What is the version of the SAPCCMSR CCMS agent?

9. Choose the Register button. The registration log appears; errors are highlighted in red.

10. Under UNIX, the agent is automatically started by the startsap script when you start theJ2EE Engine. Under Microsoft Windows, the agent is entered as a service during theregistration, and is automatically started during a restart of the host.

As of SAP NetWeaver 2004s, however, you need to start the associated service (which wascreated during the installation of the J2EE Engine) yourself. To do this, on the MicrosoftWindows host on which the agent is running, choose Start Settings Control PanelAdministrative Tools Services, and choose the service SAPCCMSR.<Instance No.> bydouble-clicking it. Set the Start Type to Automatic, and choose Start.

Result

The J2EE Engine is now registered with the local ABAP system and with CEN; you can see thecorresponding monitoring data in the Alert Monitors of the two systems.

The Customizing destination has also been automatically created for all Java instances (only ifyou have left the check box enable CCMS Customizing marked), so that you can also change thethreshold values for the monitoring data from the Alert Monitor (see Creating CustomizingDestination for SAPCCMSR –j2ee [page 43]).

3.4. Installing an Agent on a SAP Web AS 6.20 Java Instance/OtherHosts

Use the CCMS agent SAPCCMSR to monitor one of the following components centrally:

An instance of a J2EE Engine with a release status of SAP Web AS 6.20

A host on which SAP standalone components or non-SAP components (such as a database)are running

The agent transfers the monitoring data to a CEN.

Note that this description applies only for monitored J2EE Engines with a releasestatus of SAP Web AS 6.20. In the case of J2EE Engines as of SAP NetWeaver04, proceed as described under Installing an Agent on a Java Instance (JavaStandalone System) [page 18] or Installing an Agent on a Java Instance (Double-Stack System) [page 20].

If you want to monitor a TREX host with the agent, proceed as described in SAPNote 704349.

The operating system collector SAPOSCOL must also be running on themonitored host [SAPOsCol].

CCMS Agents


Page 23 of 115

Procedure

1. Copy the agent’s executable to the following directory; if the directory does not exist, createit:

UNIX: /usr/sap/ccms/bin

Windows: \\<host>\saploc\prfclog

The saploc directory can also have another name; the important thing is that it isreleased as a share with the name saploc; by default, it is the directory<drive:>\usr\sap. If the directory does not exist, create it yourself.

2. Save the CSMCONF start file to the following directory; if the directory does not exist, createit:

Windows: \\<host>\saploc\prfclog\sapccmsr

UNIX: /usr/sap/tmp/sapccmsr

3. Call SAP Note 730629 (CCMS Agents: Java Interface for Registration). Copy the filecsmagent.jar from the Note’s attachment to a temporary directory on the host to bemonitored.

4. Start the Java tool by entering the following command at the operating system prompt in theabove temporary directory:java -jar csmagent.jar

5. Select the radio button Standalone/TREX/SAP J2EE Engine 6.20. The input fields AgentConfiguration File and Agent Executable should be filled with the correct values.

6. In the Password for Administration User input field, enter the password for the user in CENwith administrator authorization under which you created the CSMCONF start file.

7. In the Password for CSMREG User input field, enter the password for the CSMREG user inCEN.

8. Choose the Register button. Check the registration log. Errors are highlighted in red.

9. Under UNIX, you must ensure yourself that the agent is automatically started again when yourestart the host. To do this, enter the following command in the inittab:

su - <SID>adm -c '/usr/sap/ccms/bin/sapccmsr -DCCMS'

Result

The J2EE Engine or the monitored host is now registered with CEN; you can see thecorresponding monitoring data in CEN’s Alert Monitor.

CCMS Agents


Page 24 of 115

4. Installing and Registering the CCMS Agents for Experts

This section describes the installation and registration of CCMS agents in generalterms, with all settings. In most cases, however, you will only want to register SAPNetWeaver components with a CEN using CCMS agents. These standard proceduresare described in Installing CCMS Agents for NetWeaver Components [page 15]

4.1. Prerequisites for the Installation

You must first clarify which of the CCMS agents is suitable for your system:

CCMS Agent Suitable for:

SAPCCMSR Components with no SAP instance and J2EE Engines with SAP Web AS6.20; Central monitoring system as of SAP Basis 4.6B

SAPCCMSR withthe option –j2ee

Java instances as of SAP NetWeaver 04;Central monitoring system as of SAP NetWeaver 04

SAPCCM4X ABAP instances as of SAP Basis 4.X;Central monitoring system as of SAP Basis 4.6C

SAPCM3X SAP systems with SAP Basis 3.X

When installing a CCMS agent under Microsoft Windows NT or MicrosoftWindows 2000, you require administrator rights on the relevant host.

Install SAPCCM4X and SAPCM3X using the user <SID>adm (UNIX) orSAPService<SID> (Microsoft Windows) of the monitored system to ensure thatthe agent can access the shared memory.

If multiple SAP R/3 3.X systems are running on one host, note the followingpoints:

Install only one SAPCM3X agent for each host.

If you specify a profile, the agent monitors only one system; therefore, do notspecify a profile (with pf=) when starting the agent.

So that the agent can read the shared memory segments of all of the systems,install the agent with the root user.

For SAPCCM4X and SAPCCMSR with Option j2ee [page 10], you have toregister one agent per monitored instance.

CCMS Agents


Page 25 of 115

4.2. Downloading the CCMS Agents

1. You require the file CCMAGENT.SAR. This archive contains all CCMS agents, includingSAPCCMSR, SAPCCM4X, and SAPCM3X.

We recommend that you use the newest version of each agent. You can determinethe version of a CCMS agent with the option –v (see Displaying the Version of aCCMS Agent [page 104]).

The archive also contains the availability agent CCMSPING. For moreinformation about the availability agent, see [Avail].

2. You can download CCMAGENT.SAR from the SAP Software Distribution Center of the SAPService Marketplace (http://service.sap.com/swdc). Log on with your SAP ServiceMarketplace ID. Check the following folders in the specified order for this file and downloadit:

In the navigation bar, choose Download Support Packages and Patches Entry byApplication Group SAP NetWeaver SAP NETWEAVER SAP NETWEAVER2004S Entry by Component Application Server ABAP SAP KERNEL 7.00 32/64-BIT <operating system> Database Independent.

Only if the desired archive does not exist in the above folder, choose DownloadSupport Packages and Patches Entry by Application Group SAP NetWeaverSAP NetWeaver components (< SAP NW 04) SAP WEB AS SAP WEB AS 6.20SAP WEB AS ABAP SAP KERNEL 6.20 32/64-BIT <operating system>Database Independent.

Only if the desired archive is not in either of the above folders, choose DownloadSupport Packages and Patches Archive for Support Packages and Patches Entryby Application Group SAP Application Components SAP R/3 SAP R/3 4.6ASAP KERNEL 4.6D 32/64-BIT <operating system> Database Independent.

The reason for specifying multiple folders is that CCMS agents are partly dependent on theoperating system release. Agents for a current SAP release may no longer cover all availableoperating system releases (for example, agents for SAP Web Application Server 6.20 aresupported only on HP-UX 11.x; however, there are still application servers to be monitoredthat are running on HP-UX 10.x).

You can determine the version of the CCMS agents in CCMAGENT.SAR bydisplaying the associated Info File.

http://service.sap.com/swdc).

CCMS Agents


Page 26 of 115

If you require an agent for an older operating system release that is not in thefolders above, SAP also provides the newest CCMS agent functions in patches toolder SAP Basis releases (especially SAP Basis 4.6D), as far as possible.

3. Decompress the CCMAGENT.SAR archive with the SAPCAR tool. Take account of SAPNote 212876 (The new archiving tool SAPCAR). For decompressing the archive, use thefollowing instruction:sapcar –xvf ccmagent.sar

Up to SAP NetWeaver 04 CCMS agents wer e freely backward compatible, so youcould – independent of the monitored system release – always use the latest release ofthe CCMS agent. As of SAP NetWeaver 2004s, this has changed:

To monitor a SAP instance up to release NW04 (6.40), always use an agent withrelease NW04 (6.40).

To monitor a SAP instance with release NW2004s (7.00) or a host without SAPinstance, use an agent with release NW2004s (7.00).

4.3. Copying the CCMS Agent to the Desired Directory

Copy the CCMS agents that you want to install to the appropriate directory for your platform:

CCMS Agent Microsoft Windows UNIX

SAPCCMSRSAPCM3X

\\<host>\saploc\prfclog /usr/sap/ccms/bin

SAPCCMSR –j2eeSAPCCM4X

\\<host>\usr\sap\<SysID>\SYS\exe\run

/usr/sap/<SysID>/SYS/exe/run

The saploc directory in the path of the CCMS agent SAPCCMSR can also haveanother name; the important thing is that it is released as a share with the namesaploc. By default, this is the directory <drive:>\usr\sap. If the directory doesnot exist, create it yourself during the installation.

4.4. Creating the Required Configuration Files

You can also create the following configuration files after registering the CCMS agent. However,you must then ensure that the agent takes these files into account.To do this, restart the agent (seeStarting and Stopping CCMS Agents [page 103]).

CCMS Agents


Page 27 of 115

4.4.1 Configuration File for Monitoring Log FilesIf you want to monitor log files with the CCMS agent, create one or more log file templates (seeStructure of the Log File Template of the Log File Agent [page 53]).

4.4.2 Configuration File for Monitoring Operating System DataIf you want to configure the monitoring of operating system data individually, create aSAPOSCOL filter file, with which you can explicitly activate and deactivate parts of theoperating system monitoring (see Structure of the SAPOSCOL Filter File oscolfile.txt [page 77])

4.4.3 Profile File of the CCMS AgentsYou specify a profile file during the registration of a CCMS agent with pf=<profile>. This ismandatory for agent SAPCCM4X, and the profile file must be that of the monitored instance.

You must also specify a profile file for agent SAPCCMSR with Option j2ee [page 10]. Thisprofile file must also be the profile for the monitored instance. Both profile files are stored underthe following paths:

<drive>:\usr\sap\<SysID>\SYS\profile\<SysID>_<InstDir>_<Host> (Windows)

/usr/sap/<SysID>/SYS/profile/<SysID>_<InstDir>_<Host> (UNIX)

For SAPCM3X and SAPCCMSR without the option –j2ee, on the other hand, the specificationof a profile file is optional, and usually not necessary. For these agents, use the profile file to:

Change the size of the monitoring segment

Change the working directory of the agent

Set a virtual name for the host

Declare the location of the operating system collector SAPOSCOL to the agent; this allowsyou to start or stop SAPOSCOL for a remote system using the agent

Activate and deactivate the trace for the monitoring architecture

With the SAPCM3X agent, ensure that you specify the profile of the monitored instance as aprofile file if SAP instances with a higher release are also running on the host. Otherwise,information for these systems is also displayed, erroneously.

4.4.3.1 Structure of the Profile FileThe important profile parameters for the agents are:alert/MONI_SEGM_SIZE

Size of the monitoring segment in the shared memory in bytes (see also SAP Note 135503)

DIR_PERF

Working directory of the CCMS agents (see Working Directory [page 47])

CCMS Agents


Page 28 of 115

DIR_WORK_SAPOSCOL

Working directory of SAPOSCOL

exe/saposcol

Complete path of SAPOSCOL

alert/TRACE

Trace for monitoring architecture data; set this trace only if expressly told to do so bySupport; the default value is 1 (trace deactivated)

SAPSYSTEM

This parameter is only important for the agent SAPCCMSR with Option j2ee [page 10]. Itspecifies the system number of the Java instance monitored by the agent.

SAPSYSTEMNAME

This parameter is only important for the agent SAPCCMSR with Option j2ee [page 10]. Itspecifies the system ID of the Java instance monitored by the agent.

While you can, in general, monitor multiple systems with identical system IDs [page90], this is only possible to a restricted extent if you are using the -j2ee option: thesystem ID of the system associated with the agent (SAPSYSTEMNAME) must not matchthe system ID of one of the central monitoring systems.

alert/SAVE_SUPPRESSED_ALERTS

Set this profile parameter to 1, to avoid the deletion of alerts that no longer fit into the sharedmemory segment of the agent. These alerts are instead automatically written to the databaseof the central monitoring system with the status complete.

alert/GREEN_ALERTS=1

Set this profile parameter to 1 to be able to work with all-clears (green alerts). Green alerts ofthis kind do not inform you of error situations, but are intended as all-clears, or explicitmessages that an action was successful.

SAPLOCALHOST

Virtual host name used for addressing the local host of the agent

In the context of high availability solutions, there can be various hosts, one of which is usedas a replacement for emergencies or maintenance periods, but which should be externallyaddressed by the same name: only one of these should ever be in operation at any time.

If a CCMS agent is installed on each of these hosts, the context name of the monitoring data(which also contains the name of the host) should be identical, irrespective of which host iscurrently running. Ensure this by setting an identical profile parameter SAPLOCALHOST inthe profile file of the CCMS agent. Take this into account with the SAPCCMSR agent in

CCMS Agents


Page 29 of 115

particular, as the SAPCCM4X agent uses the profile parameters of the SAP application serverby default.

You should also use SAPLOCALHOST if the name of the host on which you are installing theCCMS agent is longer than 13 characters in length. Specify a name with a maximum lengthof 13 characters. This is then used for the name of the RFC destination of the agent and themonitoring segment of the agent.

In the case of alternating operation of hosts of this type, the hosts work withmonitoring segments with the same name, meaning that the data is reported in thesame tree in the Alert Monitor. The content of the segment is saved to the filesALMTTREE, ALALERTS, and ALPERFHIS during the shutdown of a host. If younow ensure that these AL* files are accessible from both hosts, the contents of thesegment are not disturbed by switching host.

End each line of the profile file with the ENTER key.

4.4.3.2 Example Profile FileYou are registering the CCMS agent SAPCCMSR under Microsoft Windows and specify aprofile file with the parameter pf=. This would have the following content:# Monitoring segment of the shared memory in bytes# (For the default size, see SAP Note 135503)alert/MONI_SEGM_SIZE = 20000000

# Working directory of the agent# (Default for Microsoft Windows NT: \\host\saploc\prfclog\sapccmsr)DIR_PERF = c:\ccms-agenten\sapccmsr

# Path and complete name of the operating system collector SAPOSCOL# (required so that the agent can control the collector)exe/saposcol = c:\saploc\saposcol.exe

4.4.4 SAPCCMSR.INI: Configuration File for the CCMS AgentsThe SAPCCMSR.INI configuration file is stored in the working directory of the CCMS agent.The name of the file is always SAPCCMSR.INI, irrespective of the agent type. It primarilycontains path specifications that are required for the operation of the CCMS agents.

Create the configuration file before installing a CCMS agent if you are using at least one of thefollowing functions:

Your own settings for Monitoring Log Files [page 51]

Configuring the Monitoring of Operating System Data [page 76]

CCMS Agents


Page 30 of 115

Event Log Monitoring with CCMS Agents [page 69]

Alert Logging for CCMS Agents [page 84]

Your own settings for Displaying File Contents in the Alert Monitor [page 86]

Using additional Shared Libraries (see Including Additional Functions in CCMS Agents[page 88])

Monitoring Multiple Systems with an Identical System ID [page 90]

4.4.4.1 Structure of the SAPCCMSR.INI Configuration FileYou can set the following parameters in SAPCCMSR.INI:

Parameter DescriptionPushCycleMinutes <n> Optional parameter that specifies how often the agent

automatically reports values to the central monitoring system:

n=1: Default, values are reported every minuten=0: Values are never reportn<30: Values are reported every n minutesn 30: Values are reported every 30 minutes

PlugIn <file path>[<directory forloading additionaldll>]

Shared library of the agent to be loaded; multiple plug-ins arepossible. The file path must not contain any spaces.

Some plug-ins, such as itsmon.dll, require in turn additionalshared libraries, which are stored in a particular directory. In thiscase, specify the directory as a second parameter, as otherwisethe CCMS agent only searches for these libraries in its workingdirectory, meaning that they might not be loaded.

LogFile <file path> Configuration file for monitoring log files (log file template);you can specify one configuration file for each log file

LogFileDir<directory path>

See Types of Monitored Log Files [page 51]

You may only specify one directory LogFileDir inthe Configuration file.

LogfileParam DelTree If you specify Deltree, obsolete elements for which no log fileexists any longer, are deleted from the shared memory

CCMS Agents


Page 31 of 115

Parameter DescriptionDsrDir Directory in which the agent searches for DSR statistics files to

transfer them to the primary central monitoring system CEN; forinformation about the default directory, see TransferringDistributed Statistics Records with CCMS Agents [page 92].

We recommend that you do not change this value,since the DSRs in the default directory would then nolonger be read and transferred to CEN.

OsColFile <file path> Specifies a SAPOSCOL filter file for filtering out subtrees of theoperating system monitoring; the subtrees are then no longerstored in shared memory

ViewDirList<file path>

Files for which the agent has explicit permission to read fordisplay in the Alert Monitor

AlertLog <file path> Full path of a log file for detected alerts (specify the filenamewithout suffix, the suffix .log is automatically set)

AlertLogLevel <level> Scope of the alert loggingLongSid<target system>

If you are Monitoring Multiple Systems with an IdenticalSystem ID [page 90] in your system landscape, specify a uniquename for the system of the agent here. The first three charactersof the name should correspond to the system ID of themonitored system (only for agent SAPCCM4X).

TrapReceiveFile<file path>

Complete path of the configuration file for receiving the SNMPtraps (see Adjusting the Configuration File for Receiving SNMPTraps [page 67])

TrapSendFile<file path>

Complete path of the configuration file for sending the SNMPtraps (see Adjusting the Configuration File for Sending SNMPTraps [page 64]; for a general description of SNMP functions forCCMS agents, see Setting Up the Sending and Receiving ofSNMP Traps Using CCMS Agents63 [page 63])

GrmgDir See Transferring GRMG Customizing Files to CEN [page 88].EventLogMon [On|Off]

EventLogMon <filepath>

EventLogResolveMessages [On|Off]

See Event Log Monitoring with CCMS Agents [page 69]

CCMS Agents


Page 32 of 115

Comment lines begin with the number sign (#).

Enter the lines in the format<Parameter_name><space><Parameter_value>.

4.4.4.2 Example SAPSSMSR.INI Agent Configuration FileIf SAPCCMSR.INI does not yet exist when the CCMS agent is registered, the system creates thefollowing file empty (containing only comments) in the working directory of the CCMS agent.### Configuration file for CCMS agents SAPCCMSR and SAPCCM4X###### Format of entries for plugins:# PlugIn <full path of shared library to load>###### Format of entries for logfile monitoring:# LogFile <full path of logfile template>###### Format of entries for the option to delete trees### if no corresponding logfile exists:### This Parameter is optional, if not specified the tree still remains# LogFileParam DelTree###### Format of entries for mechanism to filter out SAPOSCOL values:# OsColFile <full path of oscolfile template>###### Name of Logfile for detected alerts### This Parameter is optional, if not specified there is no logging of Alerts# AlertLog <full path filename, without suffix>###### Level of logging### 0: no logging### 1: Logging of Alerts### 2: in addition log suppressed alerts, new values, creation,### deletion, reset for any MTE)### Parameter is optional, default = 0 if AlertLog is not set### else default = 1# AlertLogLevel <level>

4.5. Registering the CCMS Agents

The CCMS agent makes itself known to the central monitoring system through registration. Werecommend that you have the central monitoring system create the data required for this (seeAutomatically Creating the CSMCONF Start File [page 34]).

CCMS Agents


Page 33 of 115

A prerequisite for the registration is that a CSMREG user exists in CEN (see Creating theCSMREG User [page 33]).

You can perform the registration in different ways:

Registration with the Agent Registration Tool [page 34]; use this tool for registering theSAPCCMSR agent with exactly one CEN

Registration in dialog (Registering the CCMS Agents in Dialog [page 35])

Dialog-free registration using a start file (Alternative: Dialog-Free Registration of CCMSAgents [page 38])

For information about the special features of the registration of SAPCCMSR withOption j2ee [page 10] are discussed in Registering SAPCCMS with the Option -j2ee[page 41].

4.5.1 Creating the CSMREG UserAs of SAP Web AS 6.40 SP 1 and as of 6.20 SP 42, you can have the CSMREG automaticallycreated in CEN. To do this, start transaction RZ21 and choose Technical InfrastructureConfigure Central System Create CSMREG User.

In earlier releases, you must create the user manually using the following procedure:

1. Choose Tools Administration Administration User Maintenance Users, or calltransaction SU01.

2. Create the CSMREG user.

3. Create authorizations and a profile for CSMREG and assign the profile to CSMREG.

Ensure that the user type Communication (as of SAP Basis 4.6C) or CPIC (up to SAP Basis4.6B) is selected on the Logon Data tab page.

The profile should contain the following authorizations (the specified authorization objectS_CCM_RECV is only relevant in connection with the CCMS System ComponentRepository, which is delivered as of SAP Basis 4.6C):

Authorization Object Field ValueRFC_FUGR FUGR

RFC_NAME

SALC SALF SALHSALP SALS SAL_CACHE_RECEIVESYST SCSM* RFC1

S_RFC

ACTVT 16

ACTVT P0-P2S_CCM_RECV

TABLE *

CCMS Agents


Page 34 of 115

4.5.2 Automatically Creating the CSMCONF Start FileDuring the registration of CCMS agents, you primarily enter information about the centralmonitoring system and the users used for communication between the agent and the centralmonitoring system. You can enter the registration both in dialog and dialog-free, by specifying astart file (referred to a CSMCONF in the following) in the registration call.

As of release SAP Web AS 6.40 SP 1 and as of SAP Web AS 6.20 SP 42 of the centralmonitoring system it is possible that you have the central monitoring system create CSMCONFfor the registration of the CCMS agents. This applies irrespective of whether you want to performthe registration with the agent registration tool, in dialog or dialog-free.

If you are performing the registration in dialog, the CCMS agent creates a CSMCONFstart file itself from your input and stores it in the working directory of the agent (seeWorking Directory [page 47]). Only the passwords used are removed.

This means that if you are registering CCMS agents on different hosts, you could alsoperform the registration once in dialog and then add the passwords to theautomatically created CSMCONF files and use this file as the template for the otherregistrations.

1. Choose CCMS Configuration Alert Monitor, or call transaction RZ21.

2. Choose Technical Infrastructure Configure Central System Create CSMCONF StartFile for Agents; specify the agent’s Working Directory [page 47] as the location to whichCSMCONF is to be written.

3. To have the registration performed in dialog (see Registering the CCMS Agents in Dialog[page 35]), start the registration as usual with the option –R.

The data is transferred from the CSMCONF file, meaning that you only need to confirm it.You only need to enter the passwords for the two central monitoring system users.

4. To have a dialog-free registration performed (see Alternative: Dialog-Free Registration ofCCMS Agents [page 38]), proceed as follows:

a. Edit CSMCONF and enter the corresponding passwords in the parametersCEN_ADMIN_PASSWORD and CEN_CSMREG_PASSWORD.

b. Specify CSMCONF for the registration after the option –f.

4.5.3 Registration with the Agent Registration ToolThe agent registration tool simplifies the registration of the SAPCCMSR agent with exactly oneCEN. Its use has the following prerequisites:

The CSMREG user exists in (see Creating the CSMREG User [page 33])

You have created the CSMCONF start file in the agent’s working directory (seeAutomatically Creating the CSMCONF Start File [page 34])

CCMS Agents


Page 35 of 115

Proceed as described in the appropriate procedure below, depending on which component isrunning on the monitored host:

Installing an Agent on a Java Instance (Java Standalone System) [page 18]

Installing an Agent on a Java Instance (Double-Stack System) [page 20]

Installing an Agent on a SAP Web AS 6.20 Java Instance/Other Hosts [page 22]

4.5.4 Registering the CCMS Agents in DialogDuring the registration of the agent, you enter the required connection data in the centralmonitoring system. An RFC connection to the agent is automatically created in the centralmonitoring system during registration. Ensure before the registration that the requiredconfiguration files are available.

Depending on the agent, you perform the registration using the following command:

Agent Registration

SAPCCMSR sapccmsr –R [pf=<profile path>]

SAPCCMSR –j2ee sapccmsr –j2ee –R pf=<profile path>

SAPCM3X sapcm3x -R [pf=<profile path>]

SAPCCM4X sapccm4x –R pf=<profile path>

With SAPCCM4X and SAPCCMSR –j2ee, <profile path> is the full file path of the profileof the monitored instance. In the case of SAPCCMSR/SAPCM3X, it is the full file path of theagent profile (see Profile File of the CCMS Agents [page 27]).

You enter the following data during the installation:

System ID of the central monitoring system

System IDs of up to four (optional) additional central monitoring systems (see Registeringwith Multiple Central Monitoring Systems [page 89])

For every central monitoring system, you must also enter a valid SAP user that is used onceto create an RFC connection to the agent in the central monitoring system.

This user requires the authorization to execute transactions RZ20/21 (S_RZL_ADMwith authorization field ACTVT and value 01) and to enter an RFC destination usingtransaction SM59 (S_ADMI_FCD with authorization field S_ADMI_FCD and valueNADM).

In detail, you enter the following user data (if there is a default value for an entry, this isshown in square brackets. If you want to use this default value, simply press the ENTERkey):

CCMS Agents


Page 36 of 115

Due to the high number of parameters to be entered, we recommend that you have aCSMCONF start file created in the central monitoring system in order to reduce thenumber of required parameters (see Creating the CSMREG User [page 33]). In thiscase, you only need to enter the passwords yourself, and confirm the other parametersfrom CSMCONF with ENTER.

- Client

- User name

- Logon language

- Host name of the message server in the central monitoring system

- Indicator of whether load balancing is to be used for logon- Name of the logon group for logon (in the case of activated load balancing)

- Host name of the application server for logon (in the case of deactivated load balancing)

- System number of the application server for logon (in the case of deactivated loadbalancing)

- Host and port of the SAProuter in the format/H/<router host>/S/<router port>/H(optional, only required in exceptional cases)

If you are using SAProuter, ensure that the SAProuter allows at least the connectionsfrom CCMSPING to the CEN gateway (and, in the case of logon load balancing, alsoto the message server of CEN) in its Route Permission Table.

- Indicator for a trace (0 = no, 1 = yes)

- Password of the user; the password is only used for the single logon described above andis not stored

For every central monitoring system, you require the connection data of the gateway (usuallythe message server of the central monitoring system) with which the CCMS agentcommunicates as an RFC server.

- Host name of the gateway

- System number of the gateway

If your central monitoring system has a release status of at least SAP Web AS 6.10, theCCMS agent automatically sends alerts to the central monitoring system as an RFC client; asof SAP Web AS 6.20, the agents also automatically report the monitoring attributes.

In both cases, the agent requires an automatically valid logon to the central monitoringsystem. The user used for this purpose can be purely an RFC user and need not possess anyrights at all, as it only calls a precisely defined function module that does not perform any

CCMS Agents


Page 37 of 115

additional authorization checks itself. We recommend that you use the user CSMREG for thispurpose (see Creating the CSMREG User [page 33]).

In detail, you enter the following data for this CSMREG user for all central monitoringsystems:

- Client

- User name; by default CSMREG- Logon language

- Host name of the message server in the central monitoring system

- Indicator of whether load balancing is to be used for logon

- Name of the logon group for logon (in the case of activated load balancing)

- Host name of the application server for logon (in the case of deactivated load balancing)

- System number of the application server for logon (in the case of deactivated loadbalancing)

- Host and port of the SAProuter in the format/H/<router host>/S/<router port>/H(optional, only required in exceptional cases)

- Indicator for a trace (0 = no, 1 = yes)

- Password for the user; the password for the CSMREG user is stored in the secure store inan encrypted file called passwd.

For the SAPCCM4X agent, and for agent SAPCCMSR with Option j2ee [page 10], you canoptionally assign the monitored system to a system group in the central monitoring system.Enter the following data:

- Name of the system group

If you are registering the CCMS agent on a Microsoft Windows host, the agent is entered andstarted as a service during the registration. The agent is automatically restarted at everyrestart. Enter the following information for this (ensure that the Services window is not openduring the input):

- Indicator of whether the service is to be automatically started

- Account under which the service is to be started

If you install the SAPCCM4X CCMS agent, you must specify a profile path. Thisprofile is usually accessed using a share. You must therefore ensure that the accountunder which the service for the agent is running has the required networkauthorizations. You can ensure this by specifying SAPService<SID> as theaccount.

CCMS Agents


Page 38 of 115

If you have successfully completed the registration, the system displays the message EXITINGwith code 0; if an error has occurred, the system displays this.

4.5.5 Alternative: Dialog-Free Registration of CCMS AgentsYou can also perform the registration of CCMS agents dialog-free by creating a start file thatcontains all of the information that you enter during the installation in dialog (see Registering theCCMS Agents in Dialog [page 35]). You can use any name for this start file. In the followingtext, it is called CSMCONF. The configuration file is always the same when installing the CCMSagent on more than one server. It therefore makes sense to install the CCMS agent usingappropriate software distribution methods and to then configure it automatically.

To have the registration performed dialog-free, use the option -f <file name> to specify thestart file from which the system should take all installation information. Save this file in theworking directory of the CCMS agent:

Agent Installation Call

SAPCCMSR sapccmsr –r -f <file name> [pf=<profile path>]

SAPCM3X sapcm3x -r -f <file name> [pf=<profile path>]

SAPCCM4X sapccm4x –r -f <file name> pf=<profile path>

4.5.5.1 Structure of the CSMCONF Start FileThe CSMCONF start file consists of a minimum of the following three sections in which you canspecify the connection to the central monitoring system:

CCMS Agents


Page 39 of 115

CEN_CONFIGCEN_SYSID=<System ID of the central monitoring system>

.

CEN_ADMIN_USERCEN_ADMIN_R3NAME=<System ID of the central monitoring system>CEN_ADMIN_MSHOST=<Host name of the message server in the central monitoring system>CEN_ADMIN_LOADBALANCING=<Load balancing using logon groups [Y, N]>CEN_ADMIN_ASHOST=<Host name of an application server (only if load balancing=N)>CEN_ADMIN_SYSNR=<System number of the above application server (only if load balancing=N)>CEN_ADMIN_GROUP=<Name of the logon group (only if load balancing=Y)>CEN_ADMIN_CLIENT=<Client in the central monitoring system>CEN_ADMIN_USERID=<User in the central monitoring system>CEN_ADMIN_PASSWORD=<Password of the above user>CEN_ADMIN_LANG=<Logon language, such as en, de>CEN_ADMIN_TRACE=<User trace [0,1]>CEN_ADMIN_ROUTE=/H/<SAProuter host>/S/<SAProuter port>/H (optional, only required in exceptional

cases).

CEN_GATEWAYCEN_GATEWAY_HOST=<Host name of the gateway; usually the message server in the central system>CEN_GATEWAY_SYSNR=<System number of the gateway>

.

User data of a user with authorization for system administration in the central monitoringsystem (see Registering the CCMS Agents in Dialog). This user is used once to create anRFC connection to the agent in the central monitoring system.

Specification of the Central Monitoring System

Connection data of the gateway with which the CCMS agent communicates as an RFCserver

If you are installing the CCMS agent on a Microsoft Windows host, you can optionally specifylogon data for the user under which the agent is to run as a Microsoft Windows service. Theagent is then automatically started at every restart of the server. By default, the<LocalSystemAccount> is used for this purpose.

SERVICE_INFOSERVICE_START_TYPE=<Indicator for whether the service is to be automatically started [auto|manual]>SERVICE_USER=<User under which the service is to be started>SERVICE_PASSWORD=<Password of the above user>

.

Information about the user under which the agent is to run as a Microsoft Windows service

If your central monitoring system has a release status of at least SAP Web AS 6.10, the agentsautomatically report data to the central monitoring system. To do this, the agent requires anautomatically valid logon to the central system (see Registering the CCMS Agents in Dialog[page 35]) and therefore an additional section in the CSMCONF start file:

CCMS Agents


Page 40 of 115

CEN_CSMREG_USERCEN_CSMREG_R3NAME=<System ID of the central monitoring system>CEN_CSMREG_MSHOST=<Host name of the message server in the central monitoring system>CEN_CSMREG_LOADBALANCING=<Load balancing using logon groups [Y, N]>CEN_CSMREG_ASHOST=<Host name of an application server for logon (only if load balancing=N)>CEN_CSMREG_SYSNR=<System number of the above application server (only if load balancing=N)>CEN_CSMREG_GROUP=<Name of the logon group (only if load balancing=Y)>CEN_CSMREG_CLIENT=<Client in the central monitoring system>CEN_CSMREG_USERID=<User in the central monitoring system, normally CSMREG>CEN_CSMREG_PASSWORD=<Password of the above user>CEN_CSMREG_LANG=<Logon language, such as en, de>CEN_CSMREG_TRACE=<User trace [0,1]>

.

Information about the CSMREG user

For the SAPCCM4X agent, and for agent SAPCCMSR with Option j2ee [page 10], you canoptionally assign the monitored system to a system group in the central monitoring system. Yourequire an additional section in the CSMCONF start file to do this (if the monitored system is notto be assigned to a system group, leave the MGDSYSTEM section empty):

MGDSYSTEMSYSTEM_GROUP=<System group in CEN to which the monitored system is assigned [optional]>

.

Information about a system group of the monitored system

The following applies for all sections of the CSMCONF start file:

Enter the lines in the format <Parameter_name>=<Parameter_value>.

You must end the section with a period (.). This period must be the only characterin the line.

The passwords CEN_ADMIN_PASSWORD and CEN_CSMREG_PASSWORD are nolonger contained in the configuration file in plain text after the registration.

You can test the generated RFC connection of type T in transaction SM59.

If you are registering the agent with multiple central monitoring systems, seeRegistering with Multiple Central Monitoring Systems [page 89].

CCMS Agents


Page 41 of 115

4.5.5.2 Example CSMCONF Start FileCEN_CONFIG CEN_SYSID=CEN.# example: does not use logon load balancingCEN_ADMIN_USER CEN_ADMIN_R3NAME=CEN CEN_ADMIN_MSHOST=cenhostx CEN_ADMIN_LOADBALANCING=N CEN_ADMIN_ASHOST=cenhost1 CEN_ADMIN_SYSNR=01 CEN_ADMIN_CLIENT=000 CEN_ADMIN_USERID=user CEN_ADMIN_PASSWORD=passwd CEN_ADMIN_LANG=en CEN_ADMIN_TRACE=0.# for logon load balancing, use# CEN_ADMIN_LOADBALANCING=Y# CEN_ADMIN_GROUP=PUBLIC# instead of CEN_ADMIN_ASHOST and CEN_ADMIN_SYSNR

CEN_GATEWAY CEN_GATEWAY_HOST=host1 CEN_GATEWAY_SYSNR=01.# note, CSMREG user should use logon load balancingCEN_CSMREG_USER CEN_CSMREG_R3NAME=CEN CEN_CSMREG_MSHOST=cenhostx CEN_CSMREG_LANG=de CEN_CSMREG_TRACE=0 CEN_CSMREG_LOADBALANCING=y CEN_CSMREG_GROUP=PUBLIC CEN_CSMREG_CLIENT=000 CEN_CSMREG_USERID=csmreg CEN_CSMREG_PASSWORD=passwd.MGDSYSTEM.

4.5.6 Registering SAPCCMS with the Option -j2eeThe CCMS agent SAPCCMSR with Option j2ee [page 10] has been especially conceived formonitoring a J2EE Engine. The monitoring segment of the agent in this case belongs to the localsystem of the J2EE Engine, and not to the central monitoring system.

CCMS Agents


Page 42 of 115

4.5.6.1 Registering SAPCCMS with the Option -j2ee in DialogDuring the registration of the CCMS agent with the option -j2ee, you must first answer thequestions of whether there is at least one ABAP instance in the agent’s system (parameterSAPSYSTEMNAME of the Profile File of the CCMS Agents [page 27]), and whether there is acentral monitoring system in your system landscape. The various options are described in thefollowing chapters:

Situation Chapter

No ABAP instance exists,central monitoring system (CEN) exists

Monitored System with no ABAP Instances [page10]

ABAP instance exists,no central monitoring system (CEN) exists

Monitored System with J2EE and ABAP Instances[page 11]

ABAP instance exists,central monitoring system (CEN) exists

Monitored System with Java and ABAP Instances,and a CEN [page 12]

The system ID and system number of the agent’s local system are specified with theprofile parameters SAPSYSTEM and SAPSYSTEMNAME, meaning that you no longerhave to specify this information in the registration in dialog.

After you have entered this information about your system landscape, perform the rest of theregistration as described in Registering the CCMS Agents in Dialog [page 35].

4.5.6.2 Dialog-Free Registration of SAPCCMS with the Option -j2eeIf you want to install SAPCCMSR with the option -j2ee dialog-free, note that if there is anABAP instance in the agent’s local system, the local system is formally its primary centralmonitoring system (see Structure of the CSMCONF Start File [page 38] and Registering withMultiple Central Monitoring Systems [page 89]). The CSMCONF start file therefore containsinformation about the ABAP instance of the agent’s local system in the following sections:

CEN_CONFIG

CEN_ADMIN_USER

CEN_GATEWAY

CEN_CSMREG_USER (as of SAP Web AS 6.10)

The data in the actual central monitoring system is then contained in the sections with the prefixCEN2.

In detail, the various possible cases (see Examples [page 10]) in the CSMCONF start file are asfollows:

CCMS Agents


Page 43 of 115

Situation CSMCONF

No ABAP instance,CEN exists

Prefix CEN: Central monitoring systemPrefix CEN2 – CEN5: secondary central systems (optional)

ABAP instance exists,no CEN exists

Prefix CEN: Agent’s local system

ABAP instance exists,CEN exists

Prefix CEN: Agent’s local systemPrefix CEN2: Central monitoring systemPrefix CEN3 – CEN5: Secondary central systems (optional)

4.5.6.3 Creating Customizing Destination for SAPCCMSR –j2eeUse the CCMS agent SAPCCMSR with Option j2ee to transfer monitoring data for a Javainstance to a central monitoring system (CEN). You can display this monitoring data both in theAlert Monitor and in the local Java system (Monitoring service of the Visual Administrator).

To be able to change the properties of the agent nodes from the Alert Monitor, you must create aCustomizing destination after you have registered the agent. This destination is used to transferthe property changes from the Alert Monitor directly to the J2EE Engine.

If you register the CCMS agent using the Visual Administrator (see Installing anAgent on a Java Instance (Java Standalone System) [page 18] and Installing an Agenton a Java Instance (Double-Stack System) [page 20]), the Customizing destination isautomatically created during the registration of the agent.

You only require the following procedure if you have manually registered the agent inaccordance with Registering SAPCCMS with the Option -j2ee [page 41].

To create the Customizing destination, you must perform the following steps:

Create an RFC destination in the Visual Administrator of the J2EE Engine.

Create an RFC destination in the ABAP system with which you have registered the agent.

Make this destination known to the monitoring architecture.

Procedure

Creating an RFC Destination in the J2EE Engine

1. In the Visual Administrator, choose Server Services JCo RFC Provider Runtime.

2. In the Bundles tab, create a bundle configuration.

3. In the Program ID input field, enter the following name: SAP.CCMS.J2EE.<JSID>, where<JSID> is the (long-) SID of the monitored Java instance.

CCMS Agents


Page 44 of 115

4. In the other input fields, enter the connection data of the central monitoring system. If you donot have the data, you can find it in the start file CSMCONF in the Working Directory [page47] of the agent

Creating an RFC Destination in the ABAP System

Create the RFC destination in the ABAP system with which you have registered theagent. If the agent is monitoring a Java instance in an ABAP+Java system, this is thelocal ABAP system. If the agent is monitoring an instance of a standalone Javasystem, this is CEN.

5. To create an RFC destination, call transaction SM59 and choose the Create button. The RFCDestination screen appears.

6. Enter the name of the destination in the RFC Destination input field. Use the namingconvention SAP.CCMS.J2EE.<JSID>, where <JSID> is the system ID of the monitoredJava instance.

7. Enter T (Start an External Program via TCP/IP) as the connection type, and enter adescription of the destination. Confirm your entries by choosing the (Enter) button.

8. Switch to the Technical Settings tab page. In the Activation Type group box, choose theRegistered Server Program radio button, and enter SAP.CCMS.J2EE.<JSID> in theProgram ID input field.

9. In the Gateway Options group box, enter the gateway information for the local ABAP system,which you have already entered in the Visual Administrator when creating the RFCdestination (see Connecting J2EE Engine to the CCMS).

10. Switch to the Special Options tab page, and choose the Unicode radio button in the CharacterWidth in Target System group box.

11. Save your entries.

Making the RFC Destination Known to the Monitoring Architecture12. Call transaction RZ21.

13. If the agent is monitoring a Java instance in an ABAP+Java system, choose the Agents for theLocal System radio button in the Topology group box, and choose Display Overview.

If the agent is monitoring an instance of a standalone Java system, choose the Agents forRemote Systems radio button in the Topology group box, and choose Display Overview.

14. Switch to change mode by choosing (Display Change), and enter the name of the RFCdestination created above, SAP.CCMS.J2EE.<JSID>, as for the agent in the column J2EECustomizing Destination.


CCMS Agents


Page 45 of 115

Result

You have now created the required RFC destination and made it known to the monitoringarchitecture. You can now also change the properties of the nodes for the corresponding CCMSagent SAPCCMSR –j2ee in the Alert Monitor.

4.5.7 Starting the AgentUnder Microsoft Windows NT the CCMS agent is automatically started, as the system starts theassociated service. If you have registered the CCMS agent under UNIX, the agent has not yetbeen started. Start it using the appropriate command:

Agent Start Command

SAPCCMSR sapccmsr –DCCMS [pf=<profile path>]

SAPCCM4X sapccm4x –DCCMS pf=<profile path>

SAPCM3X sapcm3x –DCCMS [pf=<profile path>]

Under UNIX, you must also ensure yourself that the CCMS agent is automatically started after arestart of the server (for example, by entering the start command in INITTAB).

4.5.8 SAPCCM4X: Creating the RFC ConnectionsIf a SAP R/3 System is connected with the central monitoring system using the CCMS agentSAPCCM4X, there are two RFC connection types between the systems:

A connection of type T (connection to an external program using TCP/IP) from the centralmonitoring system to the CCMS agent SAPCCM4X; this connection is created during theregistration of the agent

Two connections of type 3 (connection to an SAP R/3 System) directly from the centralmonitoring system to the monitored system to start data collection and analysis methods

If the monitored system is already known to the monitoring architecture of the central monitoringsystem before you register the agent, these connections of type 3 already exist - in this case, youdo not need to create any connections. Otherwise, you must create these RFC connectionsyourself. For security reasons, we recommend that you define two RFC destinations for everymonitored system here, as there are two requirements that are different in principle between themonitored and the monitoring systems:

Data Collection

There are data collection methods are active in the monitored system. These methods storevalues for the monitoring attributes in the shared memory of the monitored system. Themonitoring system reads these values using an RFC call (and therefore a particular username). In the monitored system, this user is merely an observer that must log on to thissystem for each query.

Executing Analysis Methods

CCMS Agents


Page 46 of 115

If a data collection method reports an alert, you can start an analysis method. As this analysismethod may make changes in the monitored system, it must have more extensiveauthorizations in the target system.

As the two types of requirement access the monitored system in very different ways, and alsooccur with very different frequencies, we recommend that you assign different authorizations todifferent users during the definition of the two RFC destinations.

Data Collection

Create a CSMREG user on all systems to be monitored and ensure that the user typeCommunication (SAP Web Application Server 6.10) or CPIC (up to SAP BasisRelease 4.6D) is activated. For more information about user CSMREG, see Creating theCSMREG User [page 33].

Executing Analysis Methods

We recommend that you perform the RFC call under your own user name.

Procedure

To define the required RFC connections to the monitored system (referred to as the “targetsystem” in the following) in the central monitoring system, follow the procedure below :

1. Call SM59 (Display and Maintain RFC Destinations), and choose Create.

2. The RFC Destination dialog screen appears. In the RFC Destination field, enter the followingnames (as explained above, you must define two RFC destinations):

RFC Destination Name of the RFC Destination

for data collection <target system ID>_RZ20_COLLECT

to start analysis methods <target system ID>_RZ20_ANALYZE

3. In the Connection type field, enter 3 (SAP R/3 System) and in Description, enter a shortdescriptive text for the RFC connection. Choose Enter.

4. The Technical Settings tab page appears, on which there are a few additional fields. For Loaddistribution, choose Yes and choose Enter again.

5. Now fill out the other fields in the Technical Settings tab page:

Field Input

Target System ID Target system ID (such as C11)

Message server Host name of the message server

Group Logon group to be used on the target system (use transaction SMLG todisplay the available groups)

Save as The message server can be internally saved either as the entered hostname or in the form of its associated IP address.

CCMS Agents


Page 47 of 115

6. On the Logon/Security tab page, make the following entries for the users (as explained above,you must define two RFC destinations):

RFC Destination Recommended User

for data collection CSMREG

to start analysis methods Current User or user of your choice

The user for the execution of the analysis methods requires an authorization for the AlertMonitor and for system administration in the target system.

7. Save the completed definition, and test the RFC connections.

8. Once you have defined both RFC destinations, you still need to inform the monitoringarchitecture that the connections to the target system now exist. To do this, start transactionRZ21, and, in the Topology group box, activate the System Overview radio button. ChooseDisplay Overview.

9. Activate change mode by choosing the Display Change ( ) pushbutton.

10. If the connection to the target system did not yet exist during the registration, thecommunication status was set to SHUTDOWN. On the Monitored Remote SAP Systems tabpage, set the communication status for the target system to ONLINE.

11. Save your changes.

4.6. Working Directory and Log Files of the CCMS Agents

4.6.1 Working DirectoryThe working directory is in the following location, depending on the type of CCMS agent:

CCMS Agent Working Directory Alternative

SAPCCMSR /usr/sap/tmp/sapccmsr (UNIX)\\<host>\saploc\prfclog\sapccmsr(Microsoft Windows)

$DIR_PERF/sapccmsr(if the DIR_PERFparameter is specified)

SAPCCMSRwith the -j2eeoption

/usr/sap/ccms/<SysID>_<SysNo>/sapccmsr (UNIX)\\<host>\saploc\ccms\<SysID>_<SysNo>\sapccmsr (Microsoft Windows)

$DIR_CCMS/<SysID>_<SysNo>/sapccmsr(if the DIR_CCMSparameter is specified)

SAPCCM4X $DIR_LOGGING/sapccm4x(UNIX notation)

SAPCM3X $DIR_PERF/sapcm3x(UNIX notation)

CCMS Agents


Page 48 of 115

The saploc directory in the path of the CCMS agent SAPCCMSR can also haveanother name; the important thing is that it is released as a share under the namesaploc; by default, it is the directory <drive:>\usr\sap. If the directory doesnot exist, create it yourself during the registration.

In the case of SAPCCMSR with Option j2ee [page 10] , a subdirectory <SystemID>_<instance number> is created in /usr/sap/ccms (UNIX) or\\<host>\saploc\ccms (Microsoft Windows), so that the agents of differentsystems and numbers are separated. The files ALMTTREE, ALPERFHI, andALALERTS are stored in this directory (since the agent manages its own sharedmemory, these AL* files must also be stored separately from those of possibleABAP instances with the same number.) The log files of the agent are stored inthe subdirectory <System ID>_<instance number>\sapccmsr.

CSMCONF

Contains data about the central monitoring system; the parameters correspond to those in thestart file for dialog-free installation (see Structure of the CSMCONF Start File [page 38]).

SAPCCMSR.INI

Contains information about the extent to which Plug-Ins, log files, and SAPOSCOLinformation should be considered; this file is read when the agent is started (seeSAPCCMSR.INI: Configuration File for the CCMS Agents [page 29]).

SAPRFC.INI

Contains information for registration at the gateway of the central monitoring system.

You can display all files in the working directory of the agent in the centralmonitoring system. You can use transaction RZ21 to do this. In the Topology groupbox, select one of the Agents for… radio buttons. . The Monitoring: Display TechnicalTopology screen appears. Now select the desired agent and then choose WorkingDirectory of the Agent ( ). The system displays the files of the directory. To displaythe contents of a file, choose the file by double clicking it.

4.6.2 Log FilesIf you install the CCMS agent in dialog mode, the entire system logging is performed directly tothe file stdout. In the case of a dialog-free installation, the system creates a log file called<agent_name>.install in the directory from which you started the registration.

A log file is also created during runtime for the CCMS agent under the name<agent_name>.log, and log files are created for RFC communication.

CCMS Agents


Page 49 of 115

4.6.3 Trace FilesYou can set the developer trace with the option -t when starting or registering the CCMS agent.The trace is written to the file dev_<agent name> in the working directory of the agent.Activate the trace only if specifically told to do so by support.

You can use the option -debug to have a rolling trace written to the file dev_<agent name>.This means that there is a space-saving mechanisms available when detecting intermittentproblems: The first megabyte of the trace is always kept in full, along with one to two megabytesat the end of the trace.

CCMS Agents


Page 50 of 115

5. Advanced Functions of the CCMS Agents

To activate advanced functions of the CCMS agents, you must usually create a correspondingconfiguration file and either reference this file in the SAPCCMSR.INI: Configuration File for theCCMS Agents [page 29] or copy it to the relevant standard directories that the agent monitors.

Changes in SAPCCMSR.INI only become active after the agent has been restarted (see Startingand Stopping CCMS Agents [page 103]). Changes in the standard directories of the agent(logmon, procmon, grmg), on the other hand, are immediately detected and a correspondingmonitoring function is started.

\\<host>\saploc\CCMS\<SysID>_<Inst.-No>or /usr/sap/CCMS/<SysID>_<Inst.-No>

logmon

dsr

CCMS Agent

Files and Directories for the Advanced Functions

Agent‘s Working DirectoryCSMCONF

SAPCCMSR.INI

Start file of the agent, containsinformation about the centralmonitoring systems and theircommunication users

Configuration file of the agent,contains many other pathspecifications for files with settingsfor advanced functions:• Monitoring log files• Sending/receiving SNMP traps• Monitoring operating system data• Alert logging of CCMS agents• Displaying file contents in the

Alert Monitor• Plug-Ins for additional functions• …

\\<host>\saploc\prfclogor /usr/sap/tmp

grmg

procmon

Contains log file templates that are automaticallyread (*logmon.ini)

Contains Customizing files, these are automaticallytransferred to CEN (GRMG_*)

Contains files that specify the processes to bemonitored (*procmon.ini)

Changes in these directories areautomatically detected by the agent

Changes to these files are detectedonly after the agent has been restarted

Contains the DSR files that are automaticallytransferred to CEN

CCMS Agents


Page 51 of 115

5.1. Monitoring Log Files

One of the functions of CCMS agents is monitoring log files. You can use this log file agent,which is integrated into all agents, to monitor log files for particular search patterns, the lastchange time, or for their existence. This means that you can search any text files (such asdatabase alert logs or ITS log files) for any text patterns, assign alerts to them, and display theresults in the Alert Monitor.

If the agent finds the line for which it is searching, it transfers it to the central monitoring system.You decide the details of the message using entries in the configuration file of the log file agent:

Color and severity of the alert or the message

Assigned message

Assigned analysis method

Specifications about the position in the alert monitoring tree

In addition, you can monitor the existence and the last change date of particular log files, ordisplay lines that contain a certain search pattern in the Alert Monitor.

Prerequisites

In general, a CCMS agent can only monitor those files that it has permission to read. In the caseof the SAPCCM4Xagent, these are the files to which the <SID>adm user (UNIX) or theSAPService<SID> (Microsoft Windows) has access to, as this agent must always run under thisuser. In the case of the SAPCCMSR agent, these are the files that the user under which the agentis running has permission to read.

5.1.1 Types of Monitored Log FilesTypes of log files that the CCMS agents can monitor:

Log files that are continuously by the application and are therefore constantly growing (suchas the Oracle alert log alert_<SID>.log)

With these files, the agent reads newly added entries and saves its last read position.

Log files that are rewritten under the same name by the application after each restart (such asthe dev_w* files of the SAP application server)

With these files, the agent reads newly added entries and saves its last read position. Due tothe smaller size of the log file, it automatically recognizes the restart of an application and inthis case starts reading from the start of the file again.

Log files that are created by the application with a new name each time (such as brbackup,brconnect, and so on).

The agent reads newly added entries and saves its last read position. It automaticallyrecognizes the newest log files of a type, so that the current log file can always be monitored.

CCMS Agents


Page 52 of 115

You can activate the monitoring of log files in the CCMS agent configuration fileSAPCCMSR.INI (see SAPCCMSR.INI: Configuration File for the CCMS Agents [page 29]).Use the parameter LogFile, to specify a configuration file for each file to be monitored thatcontains the details of the monitoring (log file template). SAPCCMSR.INI can contain multipleentries with the following format:LogFile <Full file name of the configuration file 1>LogFile <Full file name of the configuration file 2>

For each log file template, you can specify a search criterion for the name of a log file(that can apply to more than one log file) and various text patterns that are to bemonitored.

The log file agent also automatically detects log file templates if these fulfill the followingconditions; therefore, you do not need to specify these log file templates in SAPCCMSR.INI:

The names of the templates follow the naming convention below:

CCMS Agent Naming Convention

SAPCCMSRSAPCM3X

*logmon.ini

SAPCCMSR –j2ee *<SysID>_<InstNo>*logmon.ini

SAPCCM4X *<SysID>_ABAP_<InstNo>*logmon.ini

<SysID> and <InstNo> are the system ID and the instance number of the monitoredABAP or Java instance. The J2EE Engine automatically generates suitable templatesand stores these in the specified (cross-instance) directory. The system ID andinstance number are part of the naming convention since the shared memory of theCCMS agents SAPCCMSR –j2ee and SAPCCM4X are only to contain the logfilemonitoring tree for the monitored Engine (ABAP or Java).

So it is assured that every agent is only monitoring the logfiles of its own monitoredinstance.

The templates are standard files (not links, for example) that do not exceed 2 Kilobytes in size(without comments).

The templates are in the following folders, depending on the type of the agent:

Agent Directory of the Log File Templates

SAPCCMSR –j2ee

UNIX: /usr/sap/ccms/<SysID>_<InstNo>/logmon

Windows: [drive]:\usr\sap\ccms\<SysID>_<InstNo>\logmon

SAPCCM4X $DIR_LOGGING\logmon, that is by default<instance directory>\log\logmon

CCMS Agents


Page 53 of 115

Agent Directory of the Log File Templates

SAPCCMSRSAPCM3X

UNIX: /usr/sap/tmp/logmon

Windows: [drive]:\usr\sap\prfclog\logmon

You can also use the parameter LogFileDir to set the folder in which the log fileagent automatically detects log file templates in SAPCCMSR.INI (seeSAPCCMSR.INI: Configuration File for the CCMS Agents [page 29]). However,since this means that the log file templates in the standard directory are no longerread, and the corresponding log files are no longer monitored, we do not recommendthis procedure.

You can use the optional entry LogFileParam DelTree to specify that subtrees should bedeleted in the Alert Monitor if the associated log files no longer exist.

5.1.2 Structure of the Log File Template of the Log File AgentThe log file template contains information about which text files are to be analyzed in whichform.

5.1.2.1 General Settings for the Monitored Log FilesThe following parameters of the log file template apply to all log files that fulfill the conditionsfor DIRECTORY and FILENAME:LOGFILE_TEMPLATE

Key word for the agent; opens a search area

DIRECTORY="<directory>" (required parameter)

Directory that contains the log file

FILENAME="<file name>" (required parameter)

Name of the log file; wildcards are permissible

IGNORE_FILE="<file name>" (Default: not set)

Name of the log file that is to be monitored – even if the log file fulfills the FILENAMEcondition; wildcards are permitted

If you want to monitor the trace files of the work processes, dev_w*, but not theprevious version of these trace files, dev_w*.old, set FILENAME=dev_w* andIGNORE_FILE=dev_w*.old.

CCMS Agents


Page 54 of 115

MONITOR_CONTEXT="<Context_name>"

Name of the monitoring context to which the log file agent writes the results of themonitoring; by default, this is the context Files_of_<Hostname>. Regardless of whetheror not you set this parameter, the MTE class of the monitoring context is alwaysCcmsFileMonitoring. By specifying this MTE class, you can define a rule-based monitorthat contains the subtrees for all monitored log files.

In this way, you can, for example, store different components in different contexts to furthergroup the results. Like the PREFIX parameter (see below), this function allows you todifferentiate between the different monitored log files, but provides, unlike PREFIX, anadditional hierarchical level to group the monitored files. Use this parameter only if yourequire this additional hierarchical level.

MONITOR_NEWEST_FILES=<number> (Default = 20)Maximum number of files that is to be monitored; if the number of files whose names fulfillthe search criteria exceeds this number, exactly <number> files with the newest change timeare monitored.

This means that different files are monitored over time. If a file is removed from monitoringbecause other files have a newer change date, its monitoring tree is deleted, and its alerts arereset. The maximum value for <number> is also 20, to avoid storing an unnecessarily largequantity of data in the monitoring architecture.

IGNORE_CASE=[0,1] (Default = 0)By default, all search patterns are case sensitive (0). If upper and lower case are to bedisregarded during the search, set IGNORE_CASE=1.

RESCANFROMBEGIN=[0,1] (Default = 0)Specifies whether each new read operation reads the log file from the start (1) or only thelines that have been added since the log file agent last read the file (0)

MONITOR_FILESIZE_KB=<file size[KB]> (Default: FileSize is not created)Value < 0: FileSize is not created.

Value = 0: Size of the log file in KB is monitored in the node FileSize

Value > 0: The size of the log file in KB is monitored; if the file size exceeds the value, analert is generated

PREFIX="<character string>"

Appears before the MTE nodes; allows you to differentiate between different log files withdifferent paths, but the same name (the maximum length of the prefix is 8 characters)

CCMS Agents


Page 55 of 115

SHOWNEWLINES=[0,1] (Default = 0)Value=1: The Alert Monitor creates the subnode Newlines; that is, the number of lines

created per minute is reported

Value=0: Newlines is not created

AUTOREACTION_CEN="<method name>" (Default: no method)

Central auto-reaction method assigned to the nodes Lines found for Pattern and FileExistence (if they exist).

You can directly assign a central auto-reaction to the above node using the log file template.This means that even if an agent has just been registered, or if a log file that fulfills theFILENAME condition has just been created, the corresponding node is assigned the specifiedauto-reaction method immediately when it is created.

This ensures that the alerts are processed more quickly, since the assignment of the centralauto-reaction is otherwise performed by the program SAPMSSYT, which only runs once anhour, by default. In extreme cases, it is even possible that, with the traditional methodassignment, the auto-reaction method is not executed at all for the first alerts for thecorresponding nodes.

AUTOREACTION_LOC="<method name>" (Default: no method)

Local auto-reaction method assigned to the nodes Lines found for Pattern and File Existence(if they exist)

Like the parameter AUTOREACTION_CEN, this parameter is used to speed up the assignmentof the auto-reaction method to newly-created nodes. This ensures a quicker processing of thecorresponding alerts and the execution of the auto-reaction method.

MONITOR_LAST_FILE_MODIF=[0,1] (Default = 0)Specifies whether a separate performance node File Time Stamp is to be created, which thenmonitors the last change time point of the log files (1), or whether the last change time pointis not to be monitored (0)

MTE_CLASS="<MTE class>" (Default: CcmsFile<file name>)MTE class of the monitoring object that contains the attributes specified above; the MTEclass of the monitoring objects therefore depends on the name of the monitored log file

CHECK_EXISTENCE_ONLY=[0,1] (Default = 0)Specifies whether the system is to check only for the existence of the log files (1). In thiscase, all parameters for monitoring and for search patterns (see below) are ignored.

CCMS Agents


Page 56 of 115

REPORT_MATCHING_LINES_ONLY=[0,1] (Default = 0)By default, all lines of the monitored log file are reported to the log attribute Lines found forpattern – even if none of the search patterns are found in the relevant line. If you set thisparameter, only the lines that contain the relevant search pattern are copied to the agent'sshared memory.

If you set this parameter and the value Last incoming message is set for the settingDisplay "current value" like, the last matching line is always displayed in the logattribute in the Current Status view in the Alert Monitor.

5.1.2.2 Monitored Search Pattern in the Monitored Log FilesYou can specify multiple search patterns to be monitored for each of the log files that fulfils theconditions for DIRECTORY and FILENAME. When doing this, enter a number <x> for each searchpattern in the parameter suffix of the following parameters. Begin with the number 0.

PATTERN_<x>="<character string>" (PATTERN_0 is required)Search pattern in the log file (case sensitive; wildcards are not allowed, the maximum lengthof the pattern is 80 characters)

MESSAGEID_<x>="<message ID>" Default = RT 149

Message number that is assigned to the alert

VALUE_<x>=[RED,YELLOW,GREEN] Default = YELLOW

Color of the alert in the monitoring architecture

SEVERITY_<x>=[0...255] Default = 0

Severity of the alert

MESSAGECLASS_<x>="<message class>" Default = SAP-T100

Message class

CMP_FROM_BEGIN_<x>=[0,1] Default = 0

Value=1: The line must begin with the search pattern (better performance)

Value=0: The search pattern can be in any position in the line

5.1.2.3 Search Pattern to be Output in the Monitored Log FilesYou can use the parameters explained above to monitor log files for search patterns to which analert is to be assigned (such as the search pattern Error). This function is not ideal for displayingsearch patterns to which no alert is to be assigned (such as version or date information). Only one

CCMS Agents


Page 57 of 115

log attribute is available in the Alert Monitor for all monitored search patterns, meaning that onlyone line is displayed even in the case of multiple search patterns.

There is therefore a second way in which you can monitor log files for search patterns. If a searchpattern of this type is found, the Alert Monitor displays the corresponding line as the content of aseparate text attribute. You can define the name of the text attribute yourself. If the search patternexists at several places in the log file, the system displays the last position in which it is found.APPL_INFO_<x>="<character string>"

Search pattern in the log file (case sensitive; wildcards are not allowed, the maximum lengthof the pattern is 80 characters); if the search pattern is found, the system displays the line ofthe log file in which the search pattern was found in the Alert Monitor

APPL_INFO_MTE_NAME_<x>="<MTE name>"

Name of the text attribute in which the line is displayed; the complete node name isINFO[<MTE name>] (the maximum length of the name is 33 characters)

Note that you must end the file with a period (.).

If parameters are required, this is highlighted. All other parameters are optional.

If the length of a parameter value exceeds its maximum length, the length will betruncated correspondingly.

5.1.3 Example Log File TemplatesThe following log files are to be monitored:

The Oracle alert log

The trace files of the SAP work processes

The log file of the SAPCCMSR CCMS agent

The newest backup at the time

To do this, different log file templates are entered in SAPCCMSR.INI. Obsolete subtrees are alsoto be deleted in RZ20. To do this, set the parameter DelTree. SAPCCMSR.INI must thereforecontain the following lines:Logfile /usr/sap/tmp/sapccmsr/ORAALERTlogmon.iniLogfile /usr/sap/tmp/sapccmsr/DEV_Wxlogmon.iniLogfile /usr/sap/tmp/sapccmsr/SAPCCMSRlogmon.iniLogfile /usr/sap/tmp/sapccmsr/BACKUPSlogmon.iniLogFileParam DelTree

If these log file templates were stored in the folder intended for this purpose (see Types ofMonitored Log Files [page 51]), the log file agent would definitely find these templates. An entryin the SAPCCMSR.INI file would then be superfluous.

CCMS Agents


Page 58 of 115

The contents of the log file templates mentioned above are shown in the following:

5.1.3.1 Oracle Alert LogThe template /usr/sap/tmp/sapccmsr/ORAALERTlogmon.ini would have the followingcontent:LOGFILE_TEMPLATEDIRECTORY="/oracle/<SID>/saptrace/background"FILENAME="alert_<SID>.log"MTE_CLASS="ORAALERT"

PATTERN_0="ORA-00600"VALUE_0=REDMESSAGECLASS_0="SAP-T100"MESSAGEID_0="rt 584".

The agent searches through /oracle/<SID>/saptrace/background/alert_<SID>.logcontinuously for ORA-00600 messages and returns a red alert if it finds a matching message:

Complete NameMonitored Patterns

/oracle/C11/saptrace/background/alert_C11.logORA-00600

Files of Host3

Lines found for pattern

alert_C11.log

Host on which a CCMS agent that monitor log files is running

Subtree for a monitored log file

Complete name of the monitored log fileSearch pattern

Last check of the fileOriginal line with line number in which the search pattern was found

Data Collection Check Log File checked at Mon Feb 03 15:00:32 2003

Display for this Monitoring Function in the Alert Monitor

735: ORA-00600: internal error code, arguments: [12

5.1.3.2 Trace Files of the SAP Work ProcessesThe template /usr/sap/tmp/sapccmsr/DEV_Wxlogmon.ini would have the followingcontent:LOGFILE_TEMPLATEDIRECTORY="/usr/sap/<SID>/<Instance name>/work"FILENAME="dev_w*"IGNORE_FILE="dev_w*.old"MTE_CLASS="WORKPROC"SHOWNEWLINES=1MONITOR_FILESIZE_KB=0

PATTERN_0="ERROR"VALUE_0=RED

CCMS Agents


Page 59 of 115

MESSAGECLASS_0="SAP-T100"MESSAGEID_0="rt 584"

PATTERN_1="core"VALUE_1=REDMESSAGECLASS_1="SAP-T100"MESSAGEID_1="rt 584".

The agent searches through files /usr/sap/<SID>/<Instance name>/work/dev_w*continuously for ERROR and core messages and returns a red alert if it finds a matching message.Copies of the dev_w*.old trace files are not monitored.

A subtree is created in the Alert Monitor for every dev_w* file, so that there would be ninesubtrees for nine work processes. The system also displays the size of the files and the number oflines reported per minute:

Complete NameMonitored Patterns

New Lines in Log FileLog File Size

/usr/sap/C11/Host3/work/dev_w0Error

65 /min

Files of Host3


dev_w3

Host on which a CCMS agent that monitors log files is running

Subtree for one of the monitored log files

Data Collection Check Log File checked at Mon Feb 03 14:56:39 2003

45 KB


2056: M ***LOG R49=> ThCPICSyncWait, CPIC-Errorcore|

dev_w6dev_w2dev_w0dev_w1

Subtrees of the other monitored logfiles, sorted by the time of the lastchange

Size of the file

Growth of the file

When the dev_w* files are recreated after a restart of the application server, the agent recognizesthis using the file size and begins reading from the start of the files.

5.1.3.3 Log File of the SAPCCMSR CCMS AgentThe template /usr/sap/tmp/sapccmsr/SAPCCMSRlogmon.ini would have the followingcontent:LOGFILE_TEMPLATEDIRECTORY="/usr/sap/tmp/sapccmsr"FILENAME="sapccmsr.log"MTE_CLASS="Log_of_sapccmsr"MONITOR_LAST_FILE_MODIF=1PATTERN_0="ERROR"VALUE_0=REDMESSAGECLASS_0="SAP-T100"

CCMS Agents


Page 60 of 115

MESSAGEID_0="rt 584"

APPL_INFO_0="CCMS version"APPL_INFO_MTE_NAME_0="CCMS Version"APPL_INFO_1="compiled at"APPL_INFO_MTE_NAME_1="Compiled at"APPL_INFO_2="systemid"APPL_INFO_MTE_NAME_2="System ID"APPL_INFO_3="relno"APPL_INFO_MTE_NAME_3="Release"APPL_INFO_4="patch text"APPL_INFO_MTE_NAME_4="Patch Text"APPL_INFO_5="patchno"APPL_INFO_MTE_NAME_5="Patch Number"APPL_INFO_6="intno"APPL_INFO_MTE_NAME_6="internal number"APPL_INFO_7="running on"APPL_INFO_MTE_NAME_7="Host"APPL_INFO_8="pid"APPL_INFO_MTE_NAME_8="Process ID".

The agent searches through /usr/sap/tmp/sapccmsr/sapccmsr.log continuously forERROR messages and returns a red alert if it finds a matching message. The agent also displaysthe last change of the monitored log file.

The agent also searches for other search patterns to which no alert value is assigned and, if itfinds one of these patterns, displays the corresponding line as the content of a separate textattribute. This means that a line that contains the search pattern CCMS version is displayedcompletely, so that you can see the associated version information in the corresponding subtree.If the search pattern exists at several places in the log file, the system displays the last line thatcontains the search pattern.

CCMS Agents


Page 61 of 115

Complete NameINFO [CCMS Version]

File Time Stamp

/usr/sap/tmp/sapccmsr/sapccmsr.logCCMS version 20010925, 32 bit, multithreaded, Non-Unicode

Files of Host3


Sapccmsr.log

Host on which a CCMS agent that monitors log files is running

Subtree for the monitored log file

Data Collection Check Log File checked at Mon Feb 03 14:56:39 2003Mon Feb 03 14:56:37 2003


2056: M ***LOG R49=> ThCPICSyncWait, CPIC-Error

Time of the last change of themonitored log file

INFO [Compiled at]INFO [System ID]

compiled at Feb 4 2003systemid 560 (PC with Windows NT)

INFO [Release]INFO [Patch Text]

relno 6200patch text patch collection 2003/2, OSS note 584136

INFO [Patch number]INFO [internal number]

patchno 611intno 20020600

INFO [Process ID]Monitored Patterns

pid 2004Error

INFO [Host] running on P57373 Windows NT 5.0 2195 Service Pack 3

Nodes with no alert functions; a separatenode is displayed for each search pattern

5.1.3.4 Log File for the Backups of an Oracle DatabaseThe template /usr/sap/tmp/sapccmsr/BACKUPSlogmon.ini would have the followingcontent:

LOGFILE_TEMPLATEDIRECTORY="/oracle/OMA/sapbackup"FILENAME="*.ant"MONITOR_NEWEST_FILES=1MTE_CLASS="BACKUPS"PATTERN_0="ERROR"VALUE_0=REDPATTERN_1="successfully"VALUE_1=GREEN.

The agent searches through the newest file of the format /oracle/OMA/sapbackup/*.antcontinuously for ERROR messages and successfully messages and returns a red alert if it findsERROR, and a green message if it finds successfully, meaning that the backup was successful.

The agent checks at regular intervals whether there are new matching files (in this case, therefore,whether a new backup has been started), automatically creates new subtrees when required, anddeletes obsolete subtrees.

5.1.4 Display for Log File Monitoring in the Alert MonitorThe results are displayed in the Logfile Monitoring monitor of the SAP CCMS Monitors forOptional Components monitor set or in a self-defined monitor (see Creating CCMS AgentMonitors in the Central Monitoring System [page 94]). As shown in the examples above, themonitor creates a subtree for each monitored file. The name of the subtree consists of a prefix

CCMS Agents


Page 62 of 115

that you define in the configuration file described above, and the name of the file. In this way,you can differentiate between different files with the same name in the monitor. Every subtree, inturn, consists of some or all of the following monitoring tree elements, depending on the valuesof the parameters in the corresponding log file template:

MTE(Suffix of the MTEClass)

Description

Complete Name(.ComplPath)

Complete name including file path of the monitored log file from thepoint of view of the monitoring CCMS agent

You can also display the content of the monitored files inthe Alert Monitor. To do this, double click the CompleteName attribute in which the name of the monitored file isdisplayed.

Info[<Name>](.ApplInfo)

If you are searching for search patterns with no alert value, the systemdisplays the line that contains the search pattern APPL_INFO_<n> inthe text attribute Info[<APPL_INFO_MTE_NAME_<n>>] (see SearchPattern to be Output in the Monitored Log Files [page 56]).

Monitored Patterns(.Patterns)

Search pattern with alert value (see Monitored Search Pattern in theMonitored Log Files [page 56]); You can monitor a file for multiplesearch patterns (the system displays these in the monitor separated by|)

Lines found for pattern(.MatchingL)

Lines of the log file that match the search pattern

Data Collection Check(.CollCheck)

Time of the last check of the log file; this status attribute is alwayscolored green.

File Time Stamp(.TimeStamp)

Time of the last change of the monitored log attribute; this attribute isonly created if you specify the parameterMONITOR_LAST_FILE_MODIF=1 in the log file template

New Lines in Log File(.NewLines)

Growth of the monitored log file in lines per minute; this attribute iscreated only if you specify the parameter SHOWNEWLINES=1 in the logfile template

Log File Size(.FileSize)

Size of the log file; this attribute is created only if you specify theparameter MONITOR_FILESIZE_KB 0 in the log file template (ifMONITOR_FILESIZE_KB>0, you also assign an alert threshold valueto the attribute by setting)

CCMS Agents


Page 63 of 115

The MTE class is formed from the value of the parameter MTE_CLASS (which is set inthe corresponding log file template) and the suffix specified in the table.

5.2. Setting Up the Sending and Receiving of SNMP Traps UsingCCMS Agents

Simple Network Management Protocol (SNMP) functions are also integrated into the monitoringarchitecture. This enables both communication with external management platforms andmonitoring of SNMP-compatible devices. In this situation, SNMP traps are always to be sent ifan alert occurs in particular nodes.

You can send and receive SNMP traps with CCMS agents. When sending SNMP traps usingCCMS agents – unlike Sending SNMP Traps as an Auto-Reaction Method – an SNMP traps issent for all alerts in the agent's segment. When sending using agents, the agent itself sends thetraps instead of starting a new process for each alert (as is the case when sending using auto-reactions).

When receiving SNMP traps, it is useful to select only one agent as the trap recipient,which receives SNMP traps for the entire system landscape.

Sending and Receiving of SNMP traps with CCMS agents is not possible on theplatform HP64 at the moment.

Procedure

1. Adjust the relevant configuration file. You define here, among other things, the recipient towhich the SNMP traps are to be sent or the port at which SNMP traps are to be received. Formore detailed information about this, see:

- Adjusting the Configuration File for Sending SNMP Traps [page 64]

- Adjusting the Configuration File for Receiving SNMP Traps [page 67]

2. Specify the complete path of the required configuration files in SAPCCMSR.INI file (seeSAPCCMSR.INI: Configuration File for the CCMS Agents [page 29]). To do this, set thefollowing parameters, depending on whether you want to send or receive the SNMP traps:

Parameter DescriptiontrapSendFile Complete path of the configuration file for sending SNMP trapstrapReceiveFile Complete path of the configuration file for receiving SNMP traps

CCMS Agents


Page 64 of 115

Ensure that the configuration files for sending or receiving the SNMP traps contain acomplete path of the directory in which the Management Information Base (MIB)files are stored with the value of the parameter MIB_DIR. Ensure that the agent canaccess these files.

3. To have the change in SAPCCMSR.INI take effect, restart the agent (see Controlling theCCMS Agents [page 102]).

You can now send alerts in the monitoring segment of a CCMS agent as SNMP traps and receiveSNMP traps using CCMS agents.

5.2.1 Adjusting the Configuration File for Sending SNMP TrapsYou define details about the sending of the SNMP traps in the configuration file, such as therecipients and the port to which the traps are to be sent, and the protocol with which they are tobe sent.

The values in the configuration file are determined using three levels:

Predefined default values

General default values of the configuration file (section [SNMP_DEFAULT])

Special values for a recipient host ([DESTINATION_<x>] sections)

These values have increasing priority from the top of the file to the bottom; that is, a value that isspecified in a level with a higher value overwrites the value of a lower level.

You can set the following parameters in each of the above sections ([SNMP_DEFAULT] and[DESTINATION_<x>]):

Parameter Description DefaultVERSION SNMP version (1, 2c, or 3) 1

HOSTNAME Receiving host for the SNMP traps localhost

COMMUNITY Name of the community (logical group of devices within a net-work monitored by SNMP, to which access rights are assigned)

public

INFORM Indicator of whether a trap (<SPACE>) or an inform (X) is to besent; with an inform, unlike with an SNMP trap, a returnmessage is sent (as of SNMP version 2c)

<SPACE>

TIMEOUT Timeout for the request in seconds (only if INFORM=X) 1

RETRIES Number of repetitions if the timeout is exceeded (only ifINFORM=X)

5

TRANSPORT Transport log UDP

CCMS Agents


Page 65 of 115

Parameter Description DefaultPORT Port number of the recipient of the SNMP trap 162

MIB_DIR Complete path of the directory that contains the ManagementInformation Base (MIB) files

Change this value to the path of the MIBS directory.

.

Set the following parameters only if you are using SNMP version 3:

Parameter DescriptionUSER_NAME Name of the SNMP userAUTH_PASSPHRASE Password of the SNMP userSECURITY_LEVEL Security level; the following levels are supported:

NoauthNoPriv: no authentication, no encryption (Default)

authNoPriv: Authentication, no encryptionAUTH_PROTOCOL Procedure for authenticating the message (creation of a checksum used to

ensure that the message was not changed); the MD5 (Message Digest 5)procedure is supported

SECURITY_ENGINE Engine ID of the application from which the SNMP traps are to be sent;this parameter is only required if INFORM=0, since the engine ID isgenerated during the communication if INFORM=1

CONTEXT_ENGINECONTEXT_NAME

Reserved for internal use

PRIV_PROTOCOLPRIV_PASSPHRASE

Not yet supported

Specify the complete path of the adjusted configuration file in the parameter TrapSendFile(see SAPCCMSR.INI: Configuration File for the CCMS Agents [page 29]).

Example

There is a template with the default settings for the configuration file in the SNMPLIB archive.This template has the following content:##################################################################### Configuration File for trapsend_cfg executable# trapsend_cfg can send SNMP traps to more than one destination## How the values are set:## Default Template [SNMP_DEFAULT] parameters specified here are

CCMS Agents


Page 66 of 115

# valid for all [DESTINATION_x] templates## default, if parameter is not set# VERSION 1 TRANSPORT UDP# HOSTNAME localhost MIB_DIR .# PORT 162 COMMUNITY PUBLIC# TIMEOUT 1 INFORM 0# RETRIES 5## for v3 traps# USER_NAME CONTEXT_ENGINE# AUTH_PASSPHRASE CONTEXT_NAME# AUTH_PROTOCOL PRIV_PROTOCOL# SECURITY_LEVEL PRIV_PASSPHRASE# SECURITY_ENGINE## Destination Template [DESTINATION_<X>] parameters set in# [SNMP_DEFAULT] can be overwritten here for a specific destination####################################################################

# this is an example of a configuration file[SNMP_DEFAULT]HOSTNAME=ls3016MIB_DIR=.

# send SNMP v1 trap to DESTINATION_0[DESTINATION_0]VERSION=1COMMUNITY=PUBLICTIMEOUT = 3RETRIES = 2TRANSPORT =UDPHOSTNAME=ls3016

# send SNMP v2 trap to DESTINATION_1[DESTINATION_1]VERSION=2cINFORM=0

# send SNMP v3 trap to DESTINATION_2[DESTINATION_2]VERSION=3INFORM=1USER_NAME=myuserAUTH_PASSPHRASE=mypassword

# send SNMP v3 trap to DESTINATION_3[DESTINATION_3]VERSION=3INFORM=0

CCMS Agents


Page 67 of 115

USER_NAME=myuserAUTH_PASSPHRASE=mypasswordSECURITY_ENGINE=0x0102030405HOSTNAME=ls3016AUTH_PROTOCOL=MD5

5.2.2 Adjusting the Configuration File for Receiving SNMP TrapsYou require a configuration file to set up the receiving of SNMP traps. In this configuration file,you define details about the receipt of the SNMP traps in the such as the port at which therecipient is to listen. Make the following settings in the configuration file:

Section [SNMP_TRAPD]

Parameter Description DefaultMIB_DIR Directory that contains the MIB files (Management

Information Base); this is required to display thereceived traps correctly

Change this value to the path of theMIBS directory.

. (program’sdirectory)

LISTEN_PORT_<x> Transport protocol and port number with which thetraps are received; by using different values ofX=0,1,2..., traps can be received by different ports

UDP:162

DROP_AUTH With SNMP Version 3, the user must authenticatehimself or herself; in the case of incorrectauthorization, an Authentication Failure Trap isgenerated. You can avoid traps of this type beingdisplaying by setting DROP_AUTH=1

0

Section [SNMP_USER]

If you are using SNMP version 3, define one or more SNMP users which receive the SNMPtraps in this section. For SNMP versions 1 and 2c, leave this section empty.

To define users, create a line with the following format for each user:createUser [–e <SECURITY_ENGINE>] <USER_NAME> <AUTH_PROTOCOL> <AUTH_PASSPHRASE>

When making these specifications, the following applies:

Parameter Description<SECURITY_ENGINE> Engine ID of the application from which the SNMP traps are to

be sent; this parameter is only required if INFORM=0, since theengine ID is generated during the communication if INFORM=1

CCMS Agents


Page 68 of 115

Parameter Description<USER_NAME> Name of the user<AUTH_PROTOCOL> Procedure for authenticating the message (creation of a checksum

used to ensure that the message was not changed); the MD5(Message Digest 5) procedure is supported

<AUTH_PASSPHRASE> Password of the user

Example

The template rectraps.cfg for the configuration file is in the directory for_recipient ofthe SNMPLIB. It has the following content:[SNMP_TRAPD]DROP_AUTH=0MIB_DIR=.LISTEN_PORT_0=udp:162

[SNMP_USER]createUser myuser MD5 mypasswordcreateUser -e 0x0102030405 myuser1 MD5 mypassword1

5.2.3 Displaying Received SNMP Traps in the Alert MonitorYou can receive SNMP traps with CCMS agents. In this case, the received SNMP traps aredisplayed in a separate context SNMP_<hostname> in the monitoring segment of the receivingCCMS agent:

C u r r e n t S t a t u s ( 20.12.2003 , 17:08:45 )

Standard monitoring context of the agentthat was installed on Host1

System / All Monitoring Segments / All Monitoring Contexts

SAP_CCMS_Host1

Files_of_Host1

SNMP_Host1

Monitoring segment of the receiving CCMS agent

MoniInfra_Host1

Host2 [12.19.201.40]

SNMP-Traps red 20.12.2003, 17:05:18

-Node Display Off

Host3 [12.19.200.41]

Host1

SNMP-Traps red 20.12.2003, 17:04:48

Monitoring context with receiving SNMP traps

SNMP traps sent from Host2

SNMP traps sent from Host3

There is a log attribute for each host that receives the SNMP traps. Multiple messages aregenerated for each trap (each with the value red). A separate message is generated for each

CCMS Agents


Page 69 of 115

parameter that is set in an active Management Information Base (MIB) and which was assigned avalue in the SNMP trap.

You set which MIBs the receiving CCMS agent takes into account in a configurationfile (see Adjusting the Configuration File for Receiving SNMP Traps [page 67]),which you specify, in turn, in parameter TrapReceiveFile in the configuration fileof the SAPCCMSR.INI agent.

Id

SNMP_TRAP_MSC_1

Date

20.12.2003 17:05:18

Time Value

red

Message Text

RFC1213-MIB::sysUpTime.0 = Timeticks: (1) 0:0SNMP_TRAP_MSC_1 20.12.2003 17:05:18 red RFC1155-SMI::internet.6.3.1.1.4.1.0 = OID: SAPSNMP_TRAP_MSC_1 20.12.2003 17:05:18 red SAP-MIB::r3maAlertSystemName = STRING: „CSNMP_TRAP_MSC_1 20.12.2003 17:05:18 red SAP-MIB::r3maAlertSegmentName = STRING:SNMP_TRAP_MSC_1 20.12.2003 17:05:18 red

SNMP_TRAP_MSC_1 20.12.2003 17:04:12 red RFC1213-MIB::sysUpTime.0 = Timeticks: (1) 0:0SNMP_TRAP_MSC_1 20.12.2003 17:04:12 red RFC1155-SMI::internet.6.3.1.1.4.1.0 = OID: SAPSNMP_TRAP_MSC_1 20.12.2003 17:04:12 red SAP-MIB::r3maAlertSystemName = STRING: „CSNMP_TRAP_MSC_1 20.12.2003 17:04:12 red SAP-MIB::r3maAlertSegmentName = STRING:SNMP_TRAP_MSC_1 20.12.2003 17:04:12 red

An SNMP trap generates multiple messages in a log attribute.Depending on the MIB used, values for the parameters that the trapcontains may be displayed here. The trap is completed by a messagewith no message text.

5.3. Event Log Monitoring with CCMS Agents

On Microsoft Windows platforms, you can use CCMS agents to monitor the Windows EventLog. By default, the Event Log logs events for the following areas:

Security

This log contains security-related events, such as file accesses and changes, or successful andfailed logons. You determine which events are to be logged in the corresponding securitysettings.

Applications

This log contains events that were written by an application or program. The applicationdeveloper decides in each case which events are to be logged.

System

This log contains events that are reported by Microsoft Windows system components.

The events are divided into the following event types:

Information

Warning

CCMS Agents


Page 70 of 115

Error

Success Audit and Failure Audit, only for security events

By default, after you activate event log monitoring, all event log events are monitored anddisplayed in the Operating System monitor in the central monitoring system (CEN).

You can also decide the following yourself with event log templates (see Structure of the EventLog Template [page 71]):

Which event logs are to be monitored?

Which event sources are to be monitored?

Which color should alerts of the different event types have?

Prerequisites

The CCMS agent used requires at least Patch Collection 2005/3. You can determine the status ofthe agent using the option –v (see Controlling the CCMS Agents [page 102]).

Process Flow

To activate the monitoring of the event log, set the following parameters in the SAPCCMSR.INI:Configuration File for the CCMS Agents [page 29]:

Parameter MeaningEventLogMon [On|Off] EventLogMon On activates the event log monitoring on the

Microsoft Windows host of the CCMS agent; by default, it isdeactivated.

EventLogMon <file path> This parameter specifies an event log template that containsadditional configuration settings for event log monitoring (seeStructure of the Event Log Template [page 71]); by default,all event sources and all of their event types are monitored.

SAPCCMSR.INI can contain multiple entries ofthis type, which point to multiple event logtemplates.

EventLogResolveMessages[On|Off]

EventLogResolveMessages On activates the completeresolution of the event log messages, that is, a more exactdescription of the event is obtained using additional MicrosoftWindows system calls and transferred to CEN. This meansthat you obtain more exact information at the cost ofperformance. By default, this is deactivated.

To activate these settings, you need to restart the agent after setting the parameters inSAPCCMSR.INI (see Controlling the CCMS Agents [page 102]).

CCMS Agents


Page 71 of 115

Result

The Microsoft Windows Event Log is monitored and displayed as a subtree in the OperatingSystem monitor of the monitored host (see Displaying the Event Log Monitoring in the AlertMonitor [page 73]).

5.3.1 Structure of the Event Log TemplateBy default, all event sources (Sources) of the Application, System, and Security event logs aremonitored when monitoring the Microsoft Windows Event Log. By specifying one or more eventlog templates, you can instead restrict the monitoring to selected event logs or event sources, andalso deviate from the default alert values for the events.

You specify these event log templates in SAPCCMSR.INI: Configuration File for the CCMSAgents [page 29] as values of the parameter EventLogMon:EventLogMon <complete file path of the event log template>

SAPCCMSR.INI can contain multiple entries of this type, which point to multipleevent log templates.

Structure

Monitored Event LogsIn the event log template, first specify which event log (Application, System, or Security) youwant to monitor:EVENTLOG_TEMPLATE

Keyword for the agent; this opens the configuration area for event log monitoring

EVENTLOG_NAME=[Application, System, Security] (required parameter)

Name of the event log to be monitoredMTE_NAME="<Name of the node, maximum of 40 characters>"

Name of the monitoring attribute in the Alert Monitor (optional parameter)

If you are using event log monitoring with the CCMS agent SAPCCM4X, you needto choose a name other than Security for the Security event log.

MTE_CLASS="<MTE class>" (Default: CCMSEventLogCL)

MTE class of the monitoring object that monitors the events of the above event log

CCMS Agents


Page 72 of 115

Monitored Event Sources and Assignment of the Alert Colors

You can specify which events from the event log specified in EVENTLOG_NAME are to be reportedto the monitoring infrastructure by specifying the desired event source in SOURCE_<x>. Whendoing this, enter a number <x> for each desired event source in the parameter suffix of thefollowing parameters. Start with the number 0. In this way, you can set the desired alert colorsindividually for each source, depending on the event type.

SOURCE_<x>=[event source,<ALL>] (Default: <ALL>)

Event source from the event log specified in EVENTLOG_NAME; in this way, you can haveonly events from certain event sources monitored; if the name of the event source contains aspace, place the name in quotation marks

INFO_<x>=[GREEN, YELLOW, RED, INACTIVE] (Default: GREEN)

Alert color that is to be assigned to events of the event type Information of the above eventlog from the event source defined by SOURCE_<x>

WARNING_<x>=[GREEN, YELLOW, RED, INACTIVE] (Default: YELLOW)

Alert color that is to be assigned to events of the event type Warning of the above event logfrom the event source defined by SOURCE_<x>

ERROR_<x>=[GREEN, YELLOW, RED, INACTIVE] (Default: RED)

Alert color that is to be assigned to events of the event type Error of the above event logfrom the event source defined by SOURCE_<x>

SUCCAUDIT_<x>=[GREEN, YELLOW, RED, INACTIVE] (Default: GREEN)

Alert color that is to be assigned to events of the event type Success Audit of the above eventlog from the event source defined by SOURCE_<x>

FAILAUDIT_<x>=[GREEN, YELLOW, RED, INACTIVE] (Default: RED)

Alert color that is to be assigned to events of the event type Failure Audit of the above eventlog from the event source defined by SOURCE_<x>

Note that you must end the file with a period (.).

Required parameters are indicated; all other parameters are optional.

There must not be any spaces before or after an equal sign (=).

Example

You want to monitor only the following event sources in the System event log:Automatic Updates

Service Control Manager

CCMS Agents


Page 73 of 115

Events from the Automatic Updates event source should never trigger an alert, regardless of thetype of the event, but should rather always be reported as a green message. To do this, set thefollowing entries in the SAPCCMSR.INI configuration file:EventLogMon OnEventLogMon C:\usr\sap\prfclog\sapccmsr\evtmon_appl.ini

The event log template evtmon_appl.ini would have the following content:EVENTLOG_TEMPLATEEVENTLOG_NAME=SystemMTE_CLASS=EventLogSystem

SOURCE_0="Automatic Updates"INFO_0=GREENWARNING_0=GREENERROR_0=GREENSUCCAUDIT_0=GREENFAILAUDIT_0=GREEN

SOURCE_1="Service Control Manager"INFO_1=GREENWARNING_1= YELLOWERROR_1=REDSUCCAUDIT_1=GREENFAILAUDIT_1=RED

.

5.3.2 Displaying the Event Log Monitoring in the Alert MonitorIf you have activated event log monitoring using a CCMS agent for a Microsoft Windows host,the corresponding subtree is displayed in the Operating System monitor of the central monitoringsystem. Which event sources of which event logs are displayed in this subtree depends on theconfiguration of the event log monitoring.

CCMS Agents


Page 74 of 115

Operating System Name of the monitor

-Node Display Off

Host1

EventLogs

Service Control Manager: The SAPDB service failed to start beSystem

<ALL>

Host on which a CCMS agent with activated event log monitoring is running

Subtree for event log monitoring

Event Log NameEvent Log EntriesMonitored Sources

System

Norton AntiVirus: Virus definitions are currentApplication

<ALL>


Application

Security: Handle Closed: Object Server: Security Account ManSecurity

<ALL>


Security

Events in the System event log

Events in the Application event log

Events in the Security event log

Log attribute with events from the correspondingevent log; alert values either in accordance withdefaults (Information = green, Warning = yellow…) orin accordance with event log template settings

Monitored event sources; if notrestricted in the event logtemplate, always all sources

C u r r e n t S t a t u s ( 20.05.2005 , 16:42:45 )

Integration

Since the monitoring is performed by a CCMS agent, this agent must be installed and active onthe Microsoft Windows host for which the event log is to be monitored (see Registering theCCMS Agents [page 32]).

Prerequisites

Event log monitoring must be active; this means that at least the parameter EventLogMon Onmust be set in SAPCCMSR.INI: Configuration File for the CCMS Agents [page 29].

Features

For each monitored event log, a subtree is generated that contains the name of the event log, itsevents, and the monitored event sources. The subtree consists of the following MTEs:

CCMS Agents


Page 75 of 115

MTE(MTE Class)

Description

Event Logs(CCMSEventLogs)

Subtree for event log monitoring

<Name of an event log> (CcmsEventLogCL)

Subtree for the events of an event log (by default, theevent logs System, Application, and Security aremonitored)

Event Log Name (CcmsEventLogCL.ComplPath)

Name of the monitored event log

Event Log Entries (CcmsEventLogCL.Entries)

Log attribute containing events from the correspondingevent log; by default, the alert values have the usualvalues (Information = green, Warning = yellow, Error =red); however, you can also make these settings yourselfin the event log template (see Structure of the Event LogTemplate [page 71])

Monitored Sources (CcmsEventLogCL.Sources)

Monitored event sources; if these are not restricted in theevent log template, all sources are always monitored

If you have set the MTE class yourself in the event log template, the name componentCcmsEventLogCL in the above MTE class name is replaced by the value of theparameter MTE_CLASS in the template.

Activities

To display the subtree, proceed as follows:

1. Start the Alert Monitor using transaction RZ20, or choose CCMS Control/MonitoringAlert Monitor.

2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.

3. Start the Operating System monitor from the list of monitors by double-clicking it, andexpand the Event Logs subtree for the desired host.

5.4. Monitoring Operating System Data with CCMS Agents

The operating system collector SAPOSCOL collects operating system data for any host andstores this in a segment of the shared memory. All CCMS agents can copy this data to the CCMSmonitoring segment and transfer it to the central monitoring system. This means that the data isvisible in the CCMS monitoring architecture and is displayed in the familiar transactions ST06and OS07. For more detailed information about the operating system collector, see [SAPOsCol]and SAP Note 371023.

CCMS Agents


Page 76 of 115

In this way, you can monitor the operating system data for servers without a running SAP Basissystem or SAP Web AS. An expensive installation and configuration of RFCOSCOL is no longernecessary.

5.4.1 Operating System Data Displayed in the Alert MonitorAfter the successful installation of the agent, the CCMS monitoring architecture displays thefollowing data in the Operating System monitor:

Filesystems

CPU

Paging

Commit Charge (only for Microsoft Windows)

Swap Space (only for UNIX)

OS Collector

LAN

Irrespective of this, transaction OS07 displays all data collected by SAPOSCOL. OS07 istherefore well suited to being an analysis method for the Operating System monitor. You candisplay this data using the RFC destination SAPCCMSR.<hostname>.99.

5.4.2 Configuring the Monitoring of Operating System DataThe agent also allows an individualized selection of subtrees for the Operation System andFilesystems monitors. You can use a filter to explicitly remove subtrees or entire componentsfrom the monitoring display. No monitoring nodes are then generated for these. Alternatively tofiltering out file systems, you can activate an exclusive monitoring with which only the filesystems that you explicitly specify are monitored. All other file systems are not then monitored.

As of Patch Collection 2005/4 of the CCMS agents, you can also change the names of the MTEclasses for the monitored operating system data as desired. This means that you can assignoperating system data for different hosts to different MTE classes. This simplifies Customizing,for example, of threshold values or the assignment of different auto-reactions depending on thefunction or the platform (Microsoft Windows, UNIX) of the monitored host.

In the configuration file of the CCMS agent SAPCCMSR.INI (see SAPCCMSR.INI:Configuration File for the CCMS Agents [page 29]), you can use the parameter OsColFile tospecify a configuration file in which you can make these settings. In this case, SAPCCMSR.INIwould contain an entry of the type:OsColFile <configuration file for monitoring operating system data>

This SAPOSCOL filter file is referred to as oscolfile.txt in the following.

CCMS Agents


Page 77 of 115

5.4.3 Structure of the SAPOSCOL Filter File oscolfile.txtYou can make the following specifications in the oscolfile.txt filter file:

Filtering Out Components

After the keyword FilterOutComponent, enter the components that you do not want to becopied to the CCMS monitoring segment, and for which the system will therefore not create asubtree in the monitoring tree in transaction RZ20.

Filtering Out File Systems

You can use the keyword FilterOutFilesystem to filter out file systems that are not to becopied to the CCMS monitoring segment. In this way, you can, for example, excludeparticular file systems that are always 100% full from the monitoring. You can specify thefile system name or use a pattern with a wildcard character (*).

Setting the MTE Class and Attribute Group of the Monitored Operating System Data

As of Patch Collection 2005/4, you can also set the associated MTE class and attribute groupyourself for the components CPU, Paging, Swap_Space (UNIX only), and Commit_Charge(Microsoft Windows only). Since this is done at host level, you can assign the operatingsystem data for different hosts to different MTE classes. Use the keywordMonitorComponent. The syntax of the keyword is:

MonitorComponent <component name> <MTE class> [<attribute group>]

The relevant monitoring objects and monitoring attributes then have the following names:

Node Name Default MTE Class Self-Set MTE Class

CPU CPU_Utilization 5minLoadAverage Idle Number of CPUs

CPU CPU_Utilization 5minLoadAverage Idle CPU_Number

<Name> <Name>_Utilization <Name>_5minLoadAverage <Name>_Idle <Name>_CPU_Number

Paging Page_In Page_Out

Paging Page_In Page_Out

<Name> <Name>_Page_In <Name>_Page_Out

Commit_Charge CommitChargeFree Commit_Percent

Commit_Charge CommitChargeFreeSpace CommitChargePercent_Used

<Name> <Name>_FreeSpace <Name>_Percent_Used

Swap_Space Freespace Percentage_Used

Swap_Space SwapFreespace SwapPercentage_Used

<Name> <Name>_FreeSpace <Name>_Percentage_Used

CCMS Agents


Page 78 of 115

You can see from the table that the set MTE class is used as a prefix for the associatedmonitoring attributes. Since the length of the MTE class is restricted to 40 characters,there is a maximum of 24 characters available to you for the name you choose.

Adjusting the Monitoring of File Systems

As an alternative to filtering out individual file systems, you can activate an exclusivemonitoring. This means that subtrees in the monitoring architecture are only created for filesystems specified after the keyword MonitorFilesystem. Other file systems are ignored.Entries with the keyword FilterOutFilesystem are also ignored. The syntax of thekeyword is:MonitorFilesystem <file system> [<MTE class> [<attribute group>]]

You can also assign a separate MTE class or attribute group to the monitoring object of thefile systems (by default, it is always the class FilesystemMO), so that you can, for example,use a rule-based monitor to display only the file systems to which you have explicitlyassigned this MTE class.

Adjusting the Monitoring of the LAN Interfaces

As of Patch Collection 2005/4, you can exclusively monitor specific LAN interfaces in thesame way as monitoring specific file systems. You can also set the MTE class and attributegroup of the LAN interfaces to be monitored. To do this, enter the keyword MonitorLAN.The syntax of the keyword is:MonitorLAN <LAN> [<MTE class> [<attribute group>]]

If you only want to set the MTE class for all LAN subtrees in the same way as withthe keyword MonitorComponent, specify the wildcard character * for <LAN>.

Note also that the name for <LAN> must not contain any spaces. Use the wildcard character *in this case too, as a workaround. In this way, if you want, for example, to monitor the LANinterface MS TCP, you can simply enter MS* for <LAN>.

If you have installed an SAPCCM4X agent, there is already a complete OperatingSystem monitoring tree that was created by the monitored SAP instance. In this case,you must deactivate the ABAP data collector in the monitored system. When it isstarted, the SAPCCM4X agent then creates a new Operating System monitoring treein accordance with oscolfile.txt: Follow the procedure below:

1. To do this, start transaction RZ21 in the system that the SAPCCM4X agent ismonitoring. In the Methods group box, select Method Definitions and chooseDisplay Overview.

CCMS Agents


Page 79 of 115

2. Change the following methods by selecting the methods and choosing Edit Data( ):

CCMS_Fsys_Collect

CCMS_OS_Collect

CCMS_OS_LAN

3. On the Release tab page, deactivate the Data Collection Method indicator and onthe Control tab page, deactivate the Execute method immediately after start of amonitoring segment check box.

4. Save the method definitions.

5. Restart the CCMS agent.

Set the MTE Class and Attribute Group of Monitored Processes

By default, the MTE class MonitoredProcessesMo is assigned to processes that aremonitored by the operating system collector SAPOSCOL. You can change this MTE class(and the attribute group) by specifying the desired name after the keywordMonitorProcess. The syntax of the keyword is:

MonitorProcess <process name> <MTE class> [<attribute group>]

You define processes that you want to monitor in the file dev_proc, which is storedin the SAPOSCOL working directory (see [SAPOsCol]). Note that with the keywordMonitorProcess, you only assign monitored processes to classes and groups; unlikeFilterOutFilesystem and MonitorFilesystem, it does not have any filterfunctions.

5.4.4 Example SAPOSCOL Filter File oscolfile.txtThe following file is intended to assist you in creating the filter file oscolfile.txt; themeaning of selected configuration settings is explained in the example below:############################################################################# OsColFile.txt### Configuration file for Operating System Monitoring##########################################################################

# FilterOutComponent <Component Name>### CCMS agent does not create MTEs for <Component Name>### Windows: <Component Name> = CPU | Lan | Commit_Charge | Paging |### Filesystems### UNIX: <Component Name> = CPU | Lan | SwapSpace | Paging |### Filesystems

CCMS Agents


Page 80 of 115

# FilterOutFilesystem <Filesystem Name> | <Pattern>### CCMS agent does not create MTEs for <Filesystem Name> |<Filesystem>### Filesystem name can contain '*' as a wildcard (<Pattern>).### CCMS agent does not create MTEs for <Filesystem Name> | <Pattern>

# MonitorFilesystem <Name> | <Pattern> [ <MTE Class> [<Group>]]### CCMS agent creates MTEs for this file system only. All other### Filesystems are ignored### Name can contain '*' as a wildcard (<Pattern>)### Name can be an unsubstituted filesystem name e.g. $DIR_TRANS### $DIR_PERF, if these represent file systems collected by saposcol

### <MTE Class> and <Group> are optional. If you want to specify### your own customizing group you have to specify the MTE class, too.

# MonitorComponent <Component Name> <MTE Class> [<Group>]### CCMS agent creates MTEs with specified MTE class and customizing### group.### <Group> is optional. If you don't specify the customizing group,### then the standard name is used.###### Windows: <Component Name> = CPU | Commit_Charge | Paging### UNIX: <Component Name> = CPU | SwapSpace | Paging

# MonitorLAN <Name> | <Pattern> [ <MTE Class> [<Group>]]### CCMS agent creates MTEs for this LAN interfaces only. All other### LAN interfaces are ignored### Name can contain '*' as a wildcard (<Pattern>)### <MTE Class> and <Group> are optional. If you want to specify### your own customizing group you have to specify the MTE class, too.

# MonitorProcess <Name> | <Pattern> <MTE Class> [<Group>]### Changes the MTE Class (and the Attribute Group) of the monitoring### objects of the monitored process <Name>. Name can contain '*' as a### wildcard (<Pattern>). If you want to specify your own customizing### group you have to specify the MTE class, too.

Examples of Configuration Parameters and their Meaning

Contents of oscolfile.txt MeaningFilterOutComponent CPUFilterOutComponent SwapSpaceMonitorFilesystem /usr/sap/trans

Does not create subtree CPU and does not createsubtree SwapSpace

Only creates a tree for the file system/usr/sap/trans

FilterOutComponent Filesystems Does not create a subtree for file systems

CCMS Agents


Page 81 of 115

Contents of oscolfile.txt MeaningFilterOutComponent CPUFilterOutFilesystem /oracle/C11/sapdata*

Does not create a CPU subtree

Does not create trees for file systems that matchthe pattern /oracle/C11/sapdata* (such as/oracle/C11/sapdata2); all other filesystems are displayed

MonitorFilesystem /oracle/C11/sapdata* CL_ORA GC_ORA

Only creates a tree for file systems that matchthe pattern /oracle/C11/sapdata* (such as/oracle/C11/sapdata2); the nodes arecreated under the MTE class CL_ORA and theattribute group CG_ORA

MonitorProcess *disp+work MonitoredProcessesMo Kernel_Group

Creates the subtree for the *disp+workprocesses with the default MTE classMonitoredProcessesMo and the attributegroup Kernel_Group

MonitorCompontent CPU host123CPU host123CPU

Subtree CPU has the MTE class and attributegroup host123CPU, and its monitoringattributes have this name as a prefix

5.4.5 Monitoring Selected ProcessesYou can also use the operating system collector SAPOSCOL [SAPOsCol] to monitor theavailability of selected processes. The monitor displays the number of running processes and theCPU and memory usage for each name template, broken down by different users.

You can optionally set the configuration for process monitoring in the following configurationfiles (these files are called templates in the following):

File dev_proc

Files of the procmon directory, which follow the naming convention below:

CCMS Agent Naming Convention

SAPCCMSRSAPCM3X

*procmon.ini

SAPCCMSR –j2ee *<SysID>_<InstNo>*procmon.ini

SAPCCM4X *<SysID>_ABAP_<InstNo>*procmon.ini

<SysID> and <InstNo> are the system ID and the instance number of themonitored ABAP or Java instance. The J2EE Engine automatically generates

CCMS Agents


Page 82 of 115

suitable templates and stores these in the specified (cross-instance) directory. Thesystem ID and instance number are part of the naming convention since the sharedmemory of the CCMS agents SAPCCMSR –j2ee and SAPCCM4X are only tocontain the process monitoring tree for the monitored Engine (ABAP or Java).

procmon and dev_proc are stored in SAPOSCOL’s working directory (MicrosoftWindows: \\<host>\saploc\prfclog; UNIX: /usr/sap/tmp/logmon).

The process monitoring is performed at collection intervals of one minute, by default. CCMSagents can read this data from the shared memory and display it in CEN.

Process Flow

To start monitoring selected processes, follow the procedure below:

Creating the Configuration Files

Create a template for the process monitoring (dev_proc or *procmon.ini); the template musthave the following structure:

The list of monitored processes begins with $PROC and ends with $.

Comment lines begin with the number sign (#).

The lines with which you specify the monitored processes have the following structure:<Name template> [[USER=]<user>] [MTE_CLASS=<MTE class>][MTE_Name=<MTE name>] [CUSTOMGROUP=<attribute group>]

Configuration file for a UNIX host:

CCMS Agents


Page 83 of 115

# This is a test file for# monitoring processes

$PROC

# Is saposcol running?

*saposcol* CUSTOMGROUP=SAPOSCOL

# Is saposcol running# under the root user?

*saposcol* USER=root CUSTOMGROUP=SAPOSCOL

# How many work processes are running# on this host?

*disp+work* MTE_CLASS=R3WP MTE_NAME=Workprocesses

$

Start of the monitored processes

Since no user is specified, theprocesses for all users are displayed

Use * to find saposcol irrespectiveof its path (for example, to find theprocess with the path/usr/sap/tmp/saposcol)

By specifying an MTE class, youcan create a rule-based monitorthat contains this process; toimprove the clarity of the display,the monitoring object has thename ”Workprocesses” End of the monitored processes

By specifying the same attributegroup, you can easily adjust thethreshold values for thesemonitored processes

The individual parts of the lines have the following meaning:

Parameter Description NotesName template Monitored process; you can use the wildcard

character asterisk (*) (see the example below); it isnot possible to monitor all processes by enteringonly the wildcard character asterisk

mandatory,max. 40characters

User User under whose name the process is running; youcan use the wildcard character asterisk (*)

optional,max. 20characters

MTE class MTE class to which the nodes are to belong; youcan create your own monitors in which preciselythe desired processes are displayed by assigning theprocess names to an MTE class

To do this, use the ruleCCMS_GET_MTE_BY_CLASS in a rule-based monitor, and specify the aboveMTE class there.


MTE name MTE name under which the monitoring object forthe monitored process name is displayed in the alertmonitor; if you do not set this parameter, Nametemplate is used as the MTE name


CCMS Agents


Page 84 of 115

Parameter Description NotesAttributegroup

Attribute group to which the attributes of amonitored process name are to belong; you cansimplify the maintenance of the threshold valuesusing an assignment to an attribute group


Enter the above parameters without quotation marks; the parameter values must notcontain any spaces or special characters.

SAPOSCOL reads the contents of the configuration files every five minutes. You do not need tochange SAPOSCOL or restart the responsible CCMS agent.

Setting the Threshold ValuesSince the expected CPU and memory usage is different for each process, ensure that you adjustthe threshold values of the corresponding performance attributes. The simplest way to do this isdirectly in the alert monitor itself, by selecting the relevant performance attribute and choosingProperties.

There are two options available to avoid accidentally changing the threshold values for othermonitored processes:

Set the threshold value individually for the MTE (to do this, choose Edit PropertiesUse for Individual MTE)

Use a specific attribute group in the configuration file for the desired monitored process. Yourchanges then affect only the processes that you have assigned to this group.

Result

The data for the monitored processes is displayed both in the Detail analysis menu of theoperating system monitor and in the Operating System monitor, in the Monitored Processessubtree (settings for MTE class, MTE name, and attribute group have no effect on the output inthe operating system monitor).

5.5. Alert Logging for CCMS Agents

You can define another log file for all CCMS agents that logs all alerts that the agent reports.This is especially useful if you do not use the CCMS Monitoring Architecture to display alerts(the CCMS Monitoring Architecture has its own logging), but want to use other systemmanagement tools that are to be based on the data from the CCMS agents.

CCMS Agents


Page 85 of 115

5.5.1 Activating the Alert LoggingYou can activate alert logging in the CCMS agent configuration file SAPCCMSR.INI (seeSAPCCMSR.INI: Configuration File for the CCMS Agents [page 29]). Use the parametersAlertLog and AlertLogLevel to do this:

Parameter MeaningAlertLog<filename>

Complete path of the log file (specify the filename without suffix, thesuffix .log is automatically set)

Every day, the log file for the previous day is saved under thefollowing name:<file name>_<date in the format YYYYMMDD>.log

AlertLogLevel<level>

Scope of the logging:

level=0: No logging (default, if AlertLog is not set)

level=1: New and completed alerts (default, if AlertLog is set)

level=2: Also suppressed alerts, new values for MTEs, reset, deleted, ornewly created MTEs

5.5.2 Structure of the Alert Log FileEvery line of the resulting log file for alert monitoring has the following structure:<alert type> <time stamp> <alert ID> <alert short text> <MTE>

These elements have the following meaning:

Element MeaningAlert Type Type of alert; the following values are possible:

ALERT YELLOW, ALERT RED (warning or problem)

ALERT vanished (condition for the alert no longer exists)Timestamp Time of the alert (not for alert type = ALERT VANISHED)Alert ID Self-explanatoryShort text ofthe alert

Short text of the message assigned to the alert

MTE Specifies where the alert occurred:<System>\<Context>\...\<Monitoring object>\<Monitoringattribute>

CCMS Agents


Page 86 of 115

5.5.3 Example Alert Log File# AlertLog file started at 20010520# Please, do not edit manually.

ALERT RED Sun May 20 00:00:58 2001 [ 19|20215]"NiConnect failed, rc: -0010"for MTE BCE\PWDF0487_BCE_26\...\R3Syslog\Communication

ALERT vanished [ 29|20194]for BCE\PWDF0487_BCE_26\...\R3Syslog\Communication

ALERT YELLOW Sun May 20 00:01:58 2001 [ 29|20216]"88 < 100 Current value below threshold value"for MTE BCE\PWDF0487_BCE_26\...\Dialog\LogonLoadQuality

ALERT vanished [ 38|20196]for MTE BCE\PWDF0487_BCE_26\...\Dialog\LogonLoadQuality

ALERT YELLOW Sun May 20 00:02:58 2001 [ 38|20217]"71% 80% (15 Min.) SAP buffer hit rate below threshold value"for MTE BCE\PWDF0487_BCE_26\...\Program\HitRatio

5.6. Displaying File Contents in the Alert Monitor

Files or Web resources can be monitored with various monitoring functions of the monitoringarchitecture. When doing so, the name of the monitored file, for example, is displayed as a textattribute (as in the case of Monitoring Log Files [page 51]). To quickly display the contents of afile of this type or of a URL from the Alert Monitor, there are two analysis methods that displaythe contents of the file or the URL in a separate window. This analysis method is alreadyassigned to the text attribute with the name of the monitored file.

Prerequisites

The text attribute must have content that fulfills one of the following prerequisites:

The content can be interpreted as a URL.

The content can be interpreted as a file name, and the file can be accessed using a CCMSagent.

For security reasons, the CCMS agent only transfers files for which you have previously assigneda display authorization. To do this, enter the files whose display is to be allowed intoSAPCCMSR.INI: Configuration File for the CCMS Agents [page 29], after the key wordViewDirList. You can use the wild card character (*).

You do not need to assign read authorization in the SAPCCMSR.INI file for theworking directory of the CCMS agents (see Working Directory [page 47]) and the

CCMS Agents


Page 87 of 115

working directory of the operating system collector SAPOSCOL. The files in thesedirectories can always be displayed.

5.6.1 Example of Defining Displayable File Contents (SAPCCMSR.INI)

# Section from the sapccmsr.ini file

# File contents that can be

# displayed

ViewDirList /usr/sap/tmp/info.txt

ViewDirList C:\test\*

ViewDirList $DIR_PROFILE

Keyword: a file or adirectory follows, thecontent of which can bedisplayed

the file /usr/sap/tmp/info.txt

all files in thedirectory C:\test

The following can bedisplayed:

all files in the profile directory$(DIR_PROFILE)

5.6.2 Assigning the Required Analysis MethodAssign the appropriate analysis method to the desired text attribute. To do this, follow theprocedure below:

1. Start the Alert Monitor using transaction RZ20 or choose CCMS Control/MonitoringAlert Monitor.

2. Start the desired monitor from the list by double clicking it.

3. Select the desired node and choose Properties.

4. The Monitoring: Properties and Methods screen appears. Choose the Methods tab page andthen choose the Method Assignment pushbutton.

5. The Monitoring: Methods screen appears. The rest of the procedure depends on whether youwant to assign the analysis method only to this node or to the entire MTE class.

6. If you only want to assign the analysis method to this MTE, choose change mode with theDisplay Change ( ) pushbutton, and choose the Analysis tab page. In the MethodAssignment group box, choose Method Name.

7. If you want to assign the analysis method to the selected MTE class, choose the name of theMTE class in the header data of the screen by double clicking it and choose change modeusing the Display Change ( ) pushbutton. In the Analysis Method group box, chooseMethod Name.

8. In the Method Name input field, enter one of the following method names:

CCMS Agents


Page 88 of 115

- CCMS_SHOW_FILE_FROM_TEXT_ATTR, if the contents of the text attribute is to beinterpreted as a file name; the associated CCMS agent returns the contents of this filethrough RFC, and it is then displayed.

- CCMS_SHOW_URL_FROM_TEXT_ATTR, if the contents of the text attribute is to beinterpreted as a URL; the Web browser is called at the frontend with this URL.


Result

If the text attribute can be interpreted as a file name or a URL, you can now display the contentsof the file or the URL by choosing the attribute by double clicking it.

5.7. Transferring GRMG Customizing Files to CEN

You can use the Generic Request and Message Generator (GRMG) to monitor the availability oftechnical components or of steps in business processes [GRMG]. When doing so, bothCustomizing information and availability queries and responses are exchanged as XML files.

A Customizing file specifies which component(s) are to be monitored. To transfer thisinformation to the central monitoring system, Customizing files with the prefix GRMG_ areautomatically transferred and the associated scenario is started, if the relevant files are in thefollowing directory:

\\<host>\saploc\prfclog\grmg (Microsoft Windows)

/usr/sap/tmp (UNIX)

Although you can change this directory by setting the parameter GrmgDir in theSAPCCMSR-INI configuration file (see Structure of the SAPCCMSR.INIConfiguration File [page 30]), we do not recommend this. Changing the parametermight mean that SAP components that are instrumented for monitoring with GRMGare no longer monitored.

5.8. Including Additional Functions in CCMS Agents

All CCMS agents can load shared libraries that use additional data suppliers to provide additionalinformation to the central monitoring system. An example of this is an extension for monitoringthe Internet Transaction Server (ITS) and cached disk subsystems, such as EMC Disc Arrays(Symmetrix). For more information, see SAP Note 420213.

CCMS Agents


Page 89 of 115

5.9. Registering with Multiple Central Monitoring Systems

You can also register the CCMS agents with multiple monitoring systems. This means inprinciple that data and alerts are no longer sent just to one system, but rather to multiple systems;the corresponding agent also processes requests from all monitoring systems as an RFC server.

Both systems have the same status with regard to displaying data or alerts; however, you onlyhave write access to the properties of the nodes in the primary central monitoring system. Theprimary system is the system that you specify first during the registration (see Registering theCCMS Agents [page 32]). In detail, you cannot execute the following commands in thesecondary monitoring system:

Change properties, such as threshold values, of nodes that are provided with values by aCCMS agent; to display threshold values, use the corresponding technical view of the AlertMonitor

Have central auto-reaction methods executed (see AutoRea]). With central auto-reactions,alerts in monitored systems cause an alert in the assigned central monitoring system. As analert should always trigger exactly one action for consistency reasons, central auto-reactionsare performed only in the primary central monitoring system.

The possibility of defining multiple monitoring systems has the following advantages:

Operating system data for dedicated database servers should be transferred using the CCMSagent SAPCCMSR to be able to display the data in the associated system using transactionsST06/OS07 and in the monitoring architecture. If this system is, in turn, part of a systemlandscape with a central monitoring system, you should make the following settings whenregistering the agent:

- Choose the central monitoring system of the landscape as the primary monitoring system.

- Choose the system with which the database server is associated as an additionalmonitoring system

In high availability solutions, you can define an additional monitoring system as areplacement for emergencies or maintenance periods, without having to restart or reregisterthe CCMS agents for these periods.

5.9.1 Start File CSMCONF with Multiple Central Monitoring SystemsFor dialog-free registration with multiple central monitoring systems, extend the CSMCONF startfile (see Alternative: Dialog-Free Registration of CCMS Agents [page 38]). The start file initiallyconsists of the following four sections, which define properties and the users used by the centralmonitoring system:

CEN_CONFIG

CEN_ADMIN_USER

CEN_GATEWAY

CCMS Agents


Page 90 of 115

CEN_CSMREG_USER (as of SAP Web AS 6.10)

In the case of multiple central monitoring systems, create these four sections as usual for theprimary central monitoring system. For every additional monitoring system, create these foursections for the relevant system in the same way, however with the names CEN2, CEN3, ... insteadof CEN (the names of the parameters within the sections do not change):

CEN2_CONFIG

CEN2_ADMIN_USER

CEN2_GATEWAY

CEN2_CSMREG_USER (as of SAP Web AS 6.10)

If you use system groups in your central monitoring systems, extend the MGDSYSTEM section.This section contains the system group to which the monitored system is assigned. If you areusing multiple central monitoring systems, specify the system group to which the monitoredsystem is assigned for each of these systems:MGDSYSTEM SYSTEM_GROUP=<system group in primary CEN> SYSTEM_GROUP_2=<system group in secondary CEN> ...

.

5.10. Monitoring Multiple Systems with an Identical System ID

If you want to monitor multiple systems, you must first define the required RFC connections andspecify these on the Remote Monitoring Entry screen. You also enter the Target System ID of thesystem to be monitored. This is usually the system ID of the system (see SAPCCM4X: Creatingthe RFC Connections [page 45]). The monitoring architecture uses this target system ID toidentify and differentiate between all monitored systems.

It is possible that you want to monitor multiple systems with identical system IDs. This situationoccurs in particular in very large IT landscapes or with outsourcing. In this case, nodes fromdifferent systems, but which are known by the same target system ID in the monitoringarchitecture, can no longer be clearly assigned to the corresponding system.

You should therefore assign target system IDs that are unique system landscape-wide in the caseof multiple systems with an identical system ID. When doing this, you must only ensure that thefirst three characters of the target system ID match the system ID of the corresponding system.

The nodes of the systems can then be assigned to exactly one system within the centralmonitoring system using the unique target system ID. However, only the first three characters ofthe target system ID are used during access to the destination of the remote system (such as fordata collection or to execute and analysis method). As these three characters are the three-character system ID, it is possible to read and process data in the remote system.

CCMS Agents


Page 91 of 115

When transporting data back to the central system, the system ID is again supplemented by thetarget system ID known in the central system. The longer target system ID is always used in thecentral monitoring system.

To be able to monitor multiple systems with an identical system ID, the centralmonitoring system requires Support Package 16 for SAP Web Application Server6.20, or Support Package 28 for SAP Web Application Server 6.10.

Procedure

1. Choose CCMS Configuration Alert Monitor, or call transaction RZ21.

2. Choose Technical Infrastructure Create Remote Monitoring Entry.

3. The Monitoring: Registering New Contexts for Monitoring screen appears. Specify thedesired target system ID. Ensure that you fulfill the following three conditions when doing so:

- The first three characters of the target system ID match the system ID of the remotesystem.

- The target system ID is unique among all monitored systems.

- The target system ID has a maximum length of eight characters.

Note that the target system ID must not contain an underscore (_) if the agentSAPCCMSR –j2ee is registered with CEN using the Visual Administrator (seeInstalling an Agent on a Java Instance (Java Standalone System) [page 18]).

The rest of the procedure is the same as that for registering a system to be monitored , asdescribed in SAPCCM4X: Creating the RFC Connections [page 45].

4. Ensure that the target system ID is set as the value of the parameter LongSid in theSAPCCMSR.INI configuration file for the CCMS agent SAPCCM4X (see SAPCCMSR.INI:Configuration File for the CCMS Agents [page 29]).

Example

You want to monitor three systems with the system ID PRD at different RFC destinationsDES1, DES2, and DES3. You can assign the following target system IDs:

- PRDDES1: System PRD at destination DES1



You are already monitoring a system with the system ID PRD at the RFC destination DES4,that also has the target system ID PRD in the monitoring architecture. You now also want tomonitor an additional PRD system at the RFC destination DES5. In this case, you do not need

CCMS Agents


Page 92 of 115

to change the target system ID of the first system; specify the following target system ID forthe new system:

- PRD: System PRD at destination DES4

- PRDNEU: System PRD at destination DES5

5.11. Transferring Distributed Statistics Records with CCMS Agents

Distributed Statistics Records (DSRs) are an extension of the concept of the ABAP statistics data.DSRs provide you with information for a DSR component about the workload generated and theresources used in the system by actions. The following components currently write DSRs:

J2EE Engine

TREX

SAP Internet Transaction Server

SAP Business Connector

The DSRs are written to a separate directory in the file system of the DSR component. Aspecified number of files are written in each component subdirectory. A new statistics file isstarted hourly. As soon as the maximum number of files has been reached, the system overwritesthe oldest statistics file.

Depending on the DSR component and release, this directory has the following path:

J2EE Engine and TREX as of SAP NetWeaver 2004s:

UNIX: /usr/sap/ccms/<SysID>_<Inst. No.>/dsr

Microsoft Windows: [drive]:\usr\sap\ccms\<SysID>_<Inst. No.>\dsr

All other DSR components, including J2EE Engine and TREX up to SAP NetWeaver 04:

UNIX: /usr/sap/tmp/dsr

Microsoft Windows: [drive]:\usr\sap\prfclog\dsr

This means that the DSR directory is instance-specific for the DSR components J2EEEngine and TREX, while it is host-specific for all other DSR components.

It is now the task of the CCMS agent to transfer these DSRs to the primary central monitoringsystem CEN. You can display the data there in the Global Workload Monitor (aggregated data)and in the functional trace (unaggregated data).

CCMS Agents


Page 93 of 115

6. Displaying Agent Data in the Central Monitoring System

The data transferred by the agent is available in the central monitoring system after registration.

6.1. Monitoring Contexts of the CCMS Agents in the MonitoringSystem

Depending on the CCMS agent, you can find the monitoring contexts in different places in thecentral monitoring system:

SAPCCM4X

As the SAP instance was already integrated into the central monitoring system before youinstalled the CCMS agent, the installation of the CCMS has no visible effect. However, thesystem now first attempts to use the CCMS agent to access data from the SAP instance. Ifyou have activated the push technology of the CCMS agent, this method of data retrieval isbetter from a performance point of view.

SAPCM3X

The central monitoring system creates a monitoring segmentSAP_CCMS_<host name>_local. This segment has the contexts:- <host name>

- 3x_<host name>_<SID>_<System number>

- Files_of_<host name>_local

- MoniInfra_<host name>_local

You can view these new contexts, for example, directly in the monitor set SAP CCMSTechnical Expert Monitors in the monitor All Monitoring Contexts.

SAPCCMSR

The central monitoring system creates a monitoring segment SAP_CCMS_<Hostname>. Bydefault, this segment has the contexts:- <host name>

- Files_of_<host name>

- MoniInfra_<host name>

If you also include additional monitoring functions using plug-ins (see Including AdditionalFunctions in CCMS Agents [page 88]), the monitoring segment contains additional contexts.You can view all of these contexts, for example, directly in the monitor set SAP CCMSTechnical Expert Monitors and in the monitor All Monitoring Contexts.

SAPCCMSR –j2ee

CCMS Agents


Page 94 of 115

The Java monitoring data is displayed in the SAP J2EE Monitor Templates monitor set, sortedby topic areas.

6.2. Creating CCMS Agent Monitors in the Central Monitoring System

You can also easily create rule-based monitors for the data transferred by the agent. You can thenaccess these monitors more quickly and more easily in the monitoring hierarchy. Data from theCCMS agents is already displayed by default in the following standard monitors of themonitoring architecture [StdMon]:

Filesystems Monitor

Operating System Monitor

Logfile Monitoring Monitor

Selfmonitoring CCMS Agents Monitor

The following applies for the SAPCCM4X agent:

There is little point in creating your own monitor to display the data collected bythe agent. Installing this agent does not change the existing monitoring contexts.The agent is simply a way of collecting data that is better from a performancepoint of view and more reliable. If the agent is shut down, the relevant data istransferred using a dialog work process again.

The subtrees in the Alert Monitor that are created by the CCMS agent do notdisappear immediately if the agent is shut down. Instead, they are displayed asobsolete if no values are reported.

6.2.1 SAPCM3X: Creating a Rule-Based Monitor

Note that the entries <CURRENT> and <ALL> are to be entered exactly as they areshown; that is, unlike <Hostname>, they do not stand for a variable.

1. Choose CCMS Control/Monitoring Alert Monitor, or call transaction RZ20. Activatethe maintenance functions.

2. Choose Monitor(set) Create, and specify that you want to create a new monitor in anexisting monitor set.

3. If you want to create a rule-based selection, place the cursor on the New Monitor line or on avirtual node. Choose Edit Create Node. On the Create Node screen, choose Rule Node.

4. On the Edit Rule Nodes screen, choose the following rule using the F4 help:CCMS_GET_MONITORING_SEGMENT_NAMES

CCMS Agents


Page 95 of 115

5. On the Edit Rule Nodes screen, specify the following selection parameters:

- R3System = <CURRENT>

- MoniSegment = SAP_CCMS_<host name>_local

6. Repeat this procedure from point 3; but this time choose the following rule on the Edit RuleNodes screen:CCMS_GET_MONITORING_CONTEXT_NAMES

On the Edit Rule Nodes screen, specify the following selection parameters:


- MoniSegment = SAP_CCMS_<host name>_local

- MoniContext = <ALL>

7. Save your new monitor by choosing Save or Generate Monitor. The system prompts you toenter a name for your monitor. The monitor is then automatically saved. The new monitor isnow part of your monitor set; you can use it in the same way as any other monitor.

6.2.2 SAPCCMSR: Creating a Rule-Based Monitor1. Choose CCMS Control/Monitoring Alert Monitor, or call transaction RZ20. Activate

the maintenance functions.

2. Choose Monitor(set) Create, and specify that you want to create a new monitor in anexisting monitor set.

3. If you want to create a rule-based selection, place the cursor on the New Monitor line or on avirtual node. Choose Edit Create Node. On the Create Node screen, choose Rule Node.

4. On the Edit Rule Nodes screen, choose the following rule using the F4 help:CCMS_GET_MONITORING_SEGMENT_NAMES

5. On the Edit Rule Nodes screen, specify the following selection parameters:


- MoniSegment = SAP_CCMS_<host name>

6. Repeat this procedure from point 3; but this time choose the following rule on the Edit RuleNodes screen:CCMS_GET_MONITORING_CONTEXT_NAMES

On the Edit Rule Nodes screen, specify the following selection parameters:


- MoniSegment = SAP_CCMS_<host name>

- MoniContext = <ALL>

CCMS Agents


Page 96 of 115

7. Save your new monitor by choosing Save or Generate Monitor. The system prompts you toenter a name for your monitor. The monitor is then automatically saved. The new monitor isnow part of your monitor set; you can use it in the same way as any other monitor.

You do not need to create your own monitors for any of the CCMS agents to displaydata in the operating system monitor, as this data appears immediately in transactionsST06 and OS07 and in the Operating System monitor of the Alert Monitor(transaction RZ20), without you having to make any additional settings.

6.3. Self-Monitoring of the CCMS Agents

The monitor Selfmonitoring CCMS Agents in the SAP CCMS Technical Expert Monitors isavailable to you for self-monitoring of the CCMS agents. Use this monitor to monitor the CCMSagents in your IT landscape. In addition to the RFC destination of the agent, the monitor providesthe following information about the agent, among other things:

The host on which the agent was installed

The application server that the agent is checking (for agent SAPCCM4X)

How long the agent has been active or inactive, and when it was last checked

The availability of the agent

C u r r e n t S t a t u s ( 20.02.2003 , 16:42:45 )

Selfmonitoring CCMS Agents

SAPCCMSR.Host1.99 Single agent

Name of the monitor

-Node Display Off

CEN\CCMS_Selfmonitoring\...\CCMS_Agents\...

DescriptionStatusHeartbeatAvailability 100 %

SAPCCMSR.Host1.99 controlling CEN Host1 on Host1active since 18.02.2003, 10:04:58. Last test: 20.08.2001, 16:06:093221 sec

SAPCCM4X.Host2.00

Information about the agent

DescriptionStatusHeartbeatAvailability 0 %

SAPCCM4X.Host2.00 controlling C11 C11_Host2_01 on Host2Inactive since 17.02.2003, 23:18:48. Last test: 20.08.2001, 16:06:100 sec

Agent Version Patch collection 2003/2, SAP Note 584136, CCMS version 20010925, 32Details 20.02.2003 16:36:20: Agent calls as [BCE:000:CSMREG], RFC_PING ok

Agent Version Patch collection 2003/2, SAP Note 584136, CCMS version 20010925, 32Details 20.02.2003 16:36:20: Agent calls as [BCE:000:CSMREG], RFC_PING ok

CCMS Agents


Page 97 of 115

There is a separate subtree for each individual CCMS agent (SAPCCMSR, SAPCM3X,SAPCCM4X) that provides data to the Alert Monitor of the monitored system. The name of thesubtree is the same as the RFC destination of the agent and has the following structure:

<Type of agent>.<Name of host system>.<System number of monitored instance>

Each of these subtrees consists of the following monitoring tree elements:

MTE-Name(MTE Class) Description

Description(CsmTaskCcmsAgent.Text)

Information about which application server on which host ismonitored by the agent

Status(CsmTaskCcmsAgent.Status)

Information about whether the agent is active or inactiveand how long it has been in that state

Heartbeat(CsmTaskCcmsAgent.Heartbeat)

Time since the last test of whether the agent is still active;if the agent is inactive, this attribute contains the value 0sec

Availability(CsmTaskCcmsAgent.Availability)

Percentage of the time in which the agent is active (bydefault in the last 15 minutes; you can change the timeperiod in the Properties of the MTE class)

Agent Version(CsmTaskCcmsAgent.Version)

Static information about the agent used; corresponds tothe following entries when –V is displayed (seeDisplaying the Version of a CCMS Agent [page 104]):

CCMS version

systemid

relno

Patch text

Details(CsmTaskCcmsAgent.Details)

Information about the central monitoring system user towhich the agent sends data and alerts as an RFC client;also the current status of the RFC connection used to dothis

6.4. Displaying Agent Data in the Topology Display

6.4.1 Calling the Display of Agent Data in the Topology DisplayYou can use the topology display to obtain an overview of the CCMS agents that are registeredfor your local system. To do this, follow the procedure below:

CCMS Agents


Page 98 of 115

1. From the SAP Easy Access Menu, choose Tools CCMS Configuration AlertMonitor, or call transaction RZ21.

2. In the Topology group box, choose one of the following radio buttons:

Radio Button Agent TypeAgents for Local System SAPCCMSR

Agents for Remote Systems SAPCCM4XSAPCCMSR –j2ee

Agents for 3.x Systems SAPCM3X

3. Choose the Display Overview pushbuttons (these pushbuttons and radio buttons are availableto you as of SAP Web AS 6.20. In SAP Web AS 6.10, choose Technical InfrastructureDisplay Topology, and then choose the CCMS Agents tab page and the desired agent type).

The display of the agents always refers to the local system (even the Agents forRemote Systems are registered with the local system as the central monitoring system).If you require the corresponding data for remote systems, first choose SystemOverview (SAP Web AS 6.10: Monitored Remote SAP Systems tab page) and choosethe desired system by double clicking it.

6.4.2 Data Displayed About CCMS AgentsBy default, the system displays the following columns in the tab pages for the CCMS agents:

Column Meaning

System System ID of the monitored system (this column is only displayed foragents for remote SAP systems)

Segment Name Name of the monitoring segment with which the agent connects; it hasthe name structure SAP_CCMS_<Name of the SAP Instance> orSAP_CCMS_<Host Name> for agents for the local system.

If you are monitoring J2EE Engines using SAPCCMSR withOption j2ee [page 10], the normal naming convention wouldbe for both the ABAP and the Java segment of the instanceof a SAP Web Application Server to have the same segmentname. To avoid this, the Java segment has the suffix _X,such as SAP_CCMS_HostA_ABC_33_X.

Destination RFC destination of the monitoring segment

CCMS Agents


Page 99 of 115

Column Meaning

Comm.Status orSegment Status

Status of the monitoring segment or communication status from thepoint of view of the local system. The possibilities for status are:

ONLINE

OFFLINE

SHUTDOWN

COMM.FAILIf an RFC call fails (for example, in the case of the Test Connectioncommand), the system displays COMM.FAIL. After a successful RFCcall, the system sets the status to ONLINE again.

Changed By Last user to change the communication status

Changed OnChanged At

Date and time of the last change to the communication status

Responsible Server Instance that performs the internal administration tasks to control theCCMS agent. It is first the instance with which the agent registered. Inrunning operation, another instance automatically takes over this task ifthe original instance is no longer available.

This column can also have the entry REMOTE SYSTEM whenRegistering with Multiple Central Monitoring Systems [page 89]. Thisshows that the CCMS agent is registered with the local system, butanother system is the primary monitoring system. Note that directlyafter the registration of a CCMS agent, the entry REMOTE SYSTEM isonly displayed after the first run of a synchronization job after amaximum of an hour.

With the CCMS agent SAPCCM4X (tab page Agents forRemote SAP Systems), these administrative tasks areperformed instance-independently by jobs. Therefore, thecolumn title is Responsible System in this case.

J2EE CustomizingDestination

This column contains an RFC destination to the J2EE Engine that theagent is monitoring. This destination is used to transfer propertychanges for nodes of this agent from the Alert Monitor directly to theJ2EE Engine (see Creating Customizing Destination for SAPCCMSR –j2ee [page 43]).

This column is only relevant for the agent SAPCCMSR with the j2eeOption; for all other agents, n/a is entered here.

CCMS Agents


Page 100 of 115

6.4.3 Commands in the Topology DisplayIn addition to the purely display functions, the following commands are also available to you aspushbuttons in the ALV Grid Control. These commands are only available for the local system:

Command Description

Test Connection This command performs an RFC call to the selected agent and displaysthe result. If the RFC call is not successful, the system sets the status toSHUTDOWN; if the call is successful, the system sets the status toONLINE.

Working Directoryof the Agent

You can display all files in the working directory of the agent. To dothis, select the desired agent and then choose this pushbutton. Thesystem displays an ALV Grid Control with the files from the directory.To display the contents of a file, choose the file by double clicking it.

Deregister Agent Deletes all entries for the selected CCMS agent in the relevant tables,such as the RFC destinations and the entries in the System ComponentRepository. This function should not replace the deregistration with theagent itself (see Controlling the CCMS Agents [page 102]), since, forexample, Deregister Agent does not stop the agent. Instead, use thisfunction primarily to remove incorrect entries and inconsistencies afterchanges to the system landscape.

This command is only available in change mode, which youstart by choosing the Display Change pushbutton ( ).

Self-monitoring of theAgents

Switches directly to the Self-Monitoring of the CCMS Agents [page 96]Monitor; this monitor contains the most important data for monitoringthe CCMS agents in your IT landscape

Agent Registration Specifies the central monitoring system with which the CCMS agent isregistered

Adopt Agent(change mode)

Defines the local system as the primary monitoring system for theselected CCMS agent; the previous primary system then becomes thesecondary system

Adopt All Agents(change mode)

Defines the local system as the primary monitoring system for allCCMS agents that are registered with the local system. The previousprimary systems then become secondary systems (the button is in thetoolbar at the top of the screen, since this command applies for allagents, irrespective of the selected tab page)

CCMS Agents


Page 101 of 115

Command Description

Change Comm.Statusor Segment Status(change mode)

If you no longer want to display the data from the agent in themonitoring architecture, choose OFFLINE. It remains in this status untilyou set it to ONLINE again. Do not set COMM.FAIL or SHUTDOWNmanually.

The buttons Agent Registration, Adopt Agent, and Adopt All Agents are only displayedif there are agents that are registered with multiple central monitoring systems.

You should also ensure that the functions to switch the primary system are performedin the agent itself. This can take a few seconds. Then refresh the display until thechanges are visible in the display.

CCMS Agents


Page 102 of 115

7. Controlling the CCMS Agents

The following commands are available to you to control the CCMS agents directly from theoperating system input prompt:

Command Description-R [-f <start file>] [pf=<profile path>]

Registering the agent(see Registering the CCMS Agents [page 32])

-U [pf=<profile path>] Deregistering the agent-DCCMS [pf=<profile path>] Starting the agent-stop [pf=<profile path>] Stopping the agent-status [pf=<profile path>] Displaying the status of the agent-noservice Registering and deregistering without installing or

uninstalling a service (Microsoft Windows only)-V Displaying the version of the agent

You can display the list of available commands at any time by entering the name of the agentwithout commands and options at the operating system input prompt (such as sapccmsr).

7.1. Deregistering CCMS Agents

To deregister a CCMS agent, specify the parameter –U. If you specified a profile path duringregistration, specify this path during deregistration too:

CCMS Agent Deregistration Command

SAPCCMSR sapccmsr –U [pf=<profile path>]

SAPCCM4X sapccm4x –U pf=<profile path>

SAPCM3X sapcm3x –U [pf=<profile path>]

As of Patch Collection 13, the start file CSMCONF is deleted during the deregistration. If thecentral monitoring system (CEN) with which the agent is registered has a release status of at leastSAP Web AS 6.20, the system will prompt your for the logon data for CEN during the uninstall,to automatically delete the following entries for the relevant agent:

Entry in the topology display of the monitoring architecture (you can start the topologydisplay using transaction RZ21; in the Topology group box there, choose one of the radiobuttons that display the CCMS agents registered with this system)

RFC connections to the agent (Check using transaction SM59)

CCMS Agents


Page 103 of 115

Entry in the System Component Repository (SCR); you can display the SCR by choosingTechnical Infrastructure System Repository Display in transaction RZ21.

In the case of a release status below SAP Web AS 6.20, these entries are not deleted.You should set the agent to Offline in the topology display to avoid problems in thesystem.

7.2. Starting and Stopping CCMS Agents

You should always stop and restart a CCMS agent if you have made changes to itsSAPCCMSR.INI configuration file (see SAPCCMSR.INI: Configuration File for the CCMSAgents [page 29]), as this file is only read when the agent is started.

Likewise, stop the CCMS agents SAPCCM4X and SAPCCMSR –j2ee, if you want toupgrade the corresponding monitored system. Restart the agents again after finishingthe upgrade.

Follow the procedure below for your operating system platform:

Under UNIX, you can stop the CCMS agent using the option -stop, therefore, for example,for agent SAPCCMSR, you would use the commandsapccmsr –stop [pf=<profile path>].To restart the agent later, use the option –DCCMS.

Under Microsoft Windows NT, we recommend that you stop and restart the agent by stoppingand restarting the service of the same name.

Registering and Deregistering an Agent Without Installing/Uninstalling a Service(Microsoft Windows Only)

Under Microsoft Windows, you can use the –noservice option in connection with thecommands -R (register agent) and -U (deregister agent) to prevent the associated service beinginstalled during registration or uninstalled during deregistration.

This option is available as of Patch Collection 2005/5. It is primarily useful, if you need toregister or deregister an agent using a user that does not have administrator authorization on therelevant host.

7.3. Displaying the Status of a CCMS Agent

The status of a CCMS agent displays its working directory and the configuration directory; if theagent is running, you receive additional information about the release of the central monitoring

CCMS Agents


Page 104 of 115

system in which the agent is registered. To do this, call the agent with the option –status (forexample, with the agent SAPCCMSR):>sapccmsr –status

INFO: CCMS agent sapccmsr working directory is /usr/sap/tmp/sapccmsrINFO: CCMS agent sapccmsr config file is /usr/sap/tmp/sapccmsr/csmconfINFO: Checking shared memory status of sapccmsr

******** CCMS agent running on this machine: ********** sapccmsr without profile** registered at central system BCE** CCMS version 20010925, 32 bit* Process Id 28807* relno 6200* patchno 45* intno 20020600*****************************************************

EXITING with code 0

7.4. Displaying the Version of a CCMS Agent

Call the agent with the option –v (for example, with the agent SAPCCMSR):>sapccmsr –v

CCMS version 20010925, 32 bit, multithreaded, Non-Unicodecompiled at Sep 17,2002systemid 560 (PC with Windows NT)relno 6200Patch text patch collection 2003/2, OSS note 584136patchno 344intno 20023800running on P57373 Windows NT 5.0 2195 Service Pack 2 Intel 80686

You can read the version from the release number (relno) and the patch number (patchno). Theline running on also contains the operating system on which the agent is currently running.Patch text specifies the Patch Collection. For information about which collection containswhich changes, see SAP Note 202591.

CCMS Agents


Page 105 of 115

8. Questions and Answers

SAP has possible solutions to the following errors that can occur when you are using the CCMSagents:

8.1. General

Logon to the central monitoring system does not work during registration of theagent.

This is usually due to incorrect configuration that applies to all RFC client programs,irrespective of the agent.

Therefore, you should first test the RFC connection to the central monitoring system. To dothis, use the test program SAPINFO, which is part of the Remote Function Call DevelopmentKit (RFC SDK). This package is on every presentation CD. You can use this program tocheck the connection to the central monitoring system without logon and password (see alsoSAP Note 42692).

The agent registers error-free as a service. However, the service does not start orterminates immediately (Microsoft Windows NT or Windows 2000).

A service under Microsoft Windows NT or Windows 2000 always starts in the System32directory. So that the system can find any existing profile files, you must always specify thesewith a full path.

Deregister the service (for example, with sapccm4x –U), and reregister it, specifying theprofile with the complete path.

Although a template for log file monitoring exists and is entered inSAPCCMSR.INI, the system does not display any subtrees for log files intransaction RZ20 of the central system.

You must end the LOGFILE_TEMPLATE with a period (.). The line containing the periodmust contain no other characters. You should also check in the log file of the agent whichfiles it is actually monitoring.

During the installation of the SAPCCMSR agent, you receive an error messagesaying that the system cannot access a directory or that it does not exist(Microsoft Windows NT only).

You must have created the working directory \\<host>\saploc\prfclog\sapccmsr andhave released the directory saploc, before you install SAPCCMSR.

CCMS Agents


Page 106 of 115

After a restart, the agent is not used to collect data.

- Check in the operating system whether the process is active.

- Check the RFC destination SAPCCM4X.<host>.<no> in transaction SM59 of the centralsystem. Perform a connection test in the transaction.

- Check the log file of the CCMS agent in its working directory.

The service cannot be started during the registration of the agents (MicrosoftWindows only)

Ensure that the Services window is not open during the registration.

If you cannot solve a problem, we recommend the following procedure:

- Check the log files in the working directory of the CCMS agent for possible error causes.

- Restart the service (Microsoft Windows NT or Windows 2000).

- If the problem persists, uninstall the CCMS agent and reinstall it.

- Check the RFC destination of the CCMS agent in transaction SM59 in the central system.

- Load the newest version of the CCMS agent.- When sending problem messages and queries to SAP, always send all log files and

configuration files from the working directory of the CCMS agent.

8.2. SAPCCMSR/SAPCM3X

Where is the working directory for sapccmsr.ini and the log files?

$DIR_PERF/sapccmsr

Under UNIX: /usr/sap/tmp/sapccmsr

Under Microsoft Windows: \\<host>\saploc\prfclog\sapccmsr

Example (Microsoft Windows NT): C:\usr\sap\prfclog\sapccmsr(sap must be released as the share saploc)

CCMS Agents


Page 107 of 115

8.3. SAPCCMSR –j2ee

Symptom:

Monitoring data for aJ2EE Engine are

visible in the VA, butnot in the CCMS

Connectiontest OK?

yes

no

Analysis in CEN:

Log file sapccmsr.log

Problemidentified?

yes

no

On host:is processrunning?

yes

no

Start the Process

UNIX: sapccmsr –DCCMSWindows: Start the service

Problemsolved?

yes

no

Analysis on the Host:

Log file sapccmsr.log

Solve problem

Deregister and reregisterthe agent

sapccmsr -U / sapccmsr -R

OK

Notes:

The connection test is performed as follows: Call transaction RZ21 inCEN, choose Agents for Remote Systems and Display Overview.Now select the desired agent, and choose Test Connection.

Analyze sapccmsr.log in CEN by choosing the Agent WorkingDirectory button and then choose sapccmsr.log by double-clicking it.Pay particular attention to errors connected to Gateway and RFC.

CCMS Agents


Page 108 of 115

8.4. SAPCCM4X

Where is the working directory for sapccmsr.ini and the log files?

$DIR_LOGGING/sapccm4x

Example (UNIX): /usr/sap/C11/D01/log/sapccm4x

How can you display when the monitored instance was available?

In the working directory of the agent, there is the log file available.log containing thefollowing information:

- Periods when the agent is connected to a shared memory segment

- Periods when the monitored instance is available

Example (the instance was started after the agent and was then restarted again):Unavailable uw1042_C11_01, agent not attached 05.04.2002 10:50:14 - 05.04.2002 10:50:55Available uw1042_ C11_01, agent not attached 05.04.2002 10:51:05 - 05.04.2002 10:51:05Available uw1042_ C11_01, agent attached to key 13 (pool 10) 05.04.2002 10:51:25 - 05.04.2002 10:52:46Unavailable uw1042_ C11_01, agent attached to key 13 (pool 10) 05.04.2002 10:52:56 - 05.04.2002 10:52:56Unavailable uw1042_ C11_01, agent not attached 05.04.2002 10:53:18 - 05.04.2002 10:56:19Available uw1042_ C11_01, agent not attached 05.04.2002 10:56:29 - 05.04.2002 10:56:29Available uw1042_ C11_01, agent attached to key 13 (pool 10) 05.04.2002 10:56:50 - 05.04.2002 11:16:20

CCMS Agents


Page 109 of 115

9. Additional Information

9.1. SAP Service Marketplace and SAP Library

If you want to follow the links to the following documents and SAP Notes, yourequire a valid password for the SAP Service Marketplace

For more information, see:

[Support] Supportability Setup Guide for SAP NetWeaver 04 SP Stack 04Start the SAP Service Marketplace, and go to the SAP NetWeaver 04Operations area (http://service.sap.com/nw04operation). Choose the documentSupportability Setup Guide - SAP NetWeaver 04 Stack 04 from the list.

[Tutor] Installation, Registration, and Customizing of CCMS AgentsStart the SAP Service Marketplace, and go to the System Monitoring and AlertManagement area (http://service.sap.com/monitoring). Choose Education &Workshops, and then choose Installation, Registration, and Customizing ofCCMS Agents from the list (Direct Link).

[SAPOsCol] SAPOSCOL: Properties, Installation, and Operation

Start the SAP Service Marketplace, and go to the System Monitoring and AlertManagement area (http://service.sap.com/monitoring). Choose Media Library

Documentation, and choose the document SAPOSCOL: Properties,Installation, and Operation from the list (Direct Link).

[AutoRea] Predefined Monitors for the Alert MonitorStart the SAP Service Marketplace, and go to the System Monitoring and AlertManagement area (http://service.sap.com/monitoring). Choose Media Library

Documentation, and then choose Predefined Auto-Reactions for the AlertMonitor from the list (Direct Link).

[AlMon] Online documentation for the Alert MonitorTo view this documentation, call the SAP Library and choose SAP NetWeaver

Solution Life Cycle Management Solution Monitoring Monitoring inthe CCMS The Alert Monitor.

[StdMon] Predefined Monitors for the Alert Monitor

Start the SAP Service Marketplace, and go to the System Monitoring and AlertManagement area (http://service.sap.com/monitoring). Choose Media Library

http://service.sap.com/nw04operation).

http://service.sap.com/monitoring).




CCMS Agents


Page 110 of 115

Documentation, and choose the document Predefined Monitors from the list(Direct Link).

[Avail] Availability Monitoring and CCMSPINGStart the SAP Service Marketplace, and go to the System Monitoring and AlertManagement area (http://service.sap.com/monitoring). Choose Media Library

Documentation, and choose the document Availability Monitoring andCCMSPING (Direct Link).

[JMon] Java Monitoring API – Properties and InstallationStart the SAP Service Marketplace, and go to the System Monitoring and AlertManagement area (http://service.sap.com/monitoring). Choose Developers´Zone, and choose the document Java Monitoring API – Properties andInstallation (Direct Link).

[GRMG] Instrumenting Components for Monitoring with GRMGStart the SAP Service Marketplace, and go to the System Monitoring and AlertManagement area (http://service.sap.com/monitoring). Choose Developers´Zone, and choose the document Instrumenting Components for Monitoring withGRMG (Direct Link).

9.2. Important SAP Notes About CCMS Agents

042692 Test tool for RFC links: sapinfo

The RFC connection test provided in transaction SM59 is either not available ordoes not provide enough information. Use the test tool sapinfo described in thisSAP Note for testing.

135503 CCMS Monitoring Architecture: Meaning of profile parameters

The profile parameters of the monitoring architecture are explained in this SAPNote. These are: alert/MONI_SEGM_SIZE, alert/MTTREE,alert/ALERTS, and alert/PERFHIST.

202591 CCMS Monitoring Kernel Patches (composite SAP Note)

This SAP Note describes the changes to the monitoring architecture through thevarious patch collections.

209834 CCMS agent technology (composite SAP Note)This SAP Note contains, in addition to basic information about the CCMSagents, known problems that can occur in connection with the CCMS agents,and their solutions.




CCMS Agents


Page 111 of 115

212876 The new archiving tool SAPCAR

This SAP Note explains the operation of the archiving tool SAPCAR, withwhich the SAP Service Marketplace files are compressed.

308061 CCMS monitoring architecture: monitor 3x systemsThe CCMS monitoring architecture is available as of SAP Basis 4.0B.However, you can also monitor systems as of SAP Basis 3.0D using themonitoring architecture. This SAP Note explains the procedure required to dothis.

322075 Installing the CCMS agent sapccm4x failsThis SAP Note shows how you can solve a possible problem (error during theinteraction of the semaphores between the agent and the application server)during the installation of the CCMS agent SAPCCM4X on application serversup to SAP Basis 4.6C.

371023 OS07/ST06: Monitoring of operating system dataOperating system data of (any) server is to be collected with the operatingsystem collector SAPOSCOL and reported in the CCMS monitoringarchitecture or displayed in transactions ST06/OS07. This SAP Note describesthe prerequisites for this.

420213 Composite SAP Note: Central monitoring of mySAP.com componentsThis SAP Note provides current information about monitoring mySAP.comcomponents that are not described in the standard documentation (see SAPService Marketplace and SAP Library [page 109]).

429265 CCMS monitoring architecture: Central auto-reaction

As of SAP Web AS 6.10, you can define central auto-reaction methods in themonitoring architecture in the context of the central monitoring of mySAP.comcomponents. The auto-reaction methods are not started in the system, in whichthe alert occurs, but rather in the central monitoring system. In this way, it ispossible for reactions to events that occur in monitored components to beperformed immediately in a central location. This SAP Note describes theprerequisites for this scenario.

498179 Enable Monitoring of InQMy/SAP J2EE Engine

You want to include the SAP J2EE Engine in the CCMS monitoringarchitecture. This SAP Note shows how you can do this with the SAPCCMSRagent.

502461 CRM: CCMS agent PlugIn for IPC

You want to include the IPC Server component in the CCMS monitoringarchitecture. This SAP Note shows how you can do this with the SAPCCMSRagent and the appropriate PlugIn.

CCMS Agents


Page 112 of 115

535199 CCMS agents: Monitoring log files

In the context of monitoring systems and system landscapes, you can useCCMS agents to monitor log files; that is, to search through certain files for oneor more word patterns. If a search pattern is found, the monitoring architecturedisplays a message or an alert. This SAP Note explains the configurationrequired to do this.

516181 SAP Expert Monitor for EMC (SEME)

You want to monitor cached disk subsystems, such as EMC Disc Arrays(Symmetrix) with the monitoring architecture. This SAP Note shows how youcan do this with the SAPCCMSR agent and the appropriate PlugIn.

522453 RZ20: Monitoring operating system data

This SAP Note describes how you can configure the collection of operatingsystem data in the monitoring architecture.

584136 CCMS agents and kernels: Patches 2003 (composite SAP Note)This SAP Note describes the changes to the monitoring architecture through thepatch collections during 2003.

694057 CCMS agents and kernels: Patches 2004 (composite SAP Note)This SAP Note describes the changes to the CCMS agents in the patchcollections from 2004.

704349 Activating the CCMS monitoring for TREXTREX can provide monitoring data for the CCMS using the agent technology.To do this, the CCMS agent SAPCCMSR and the operating system collectorSAPOSCOL must be installed and configured on the TREX host. This SAPNote describes the steps on the TREX host.

730629 CCMS agents: Java interface for registrationYou want to register the CCMS agent SAPCCMSR. The monitored object canbe an instance of a J2EE Engine with a release status of SAP Web AS 6.20 or ahost on which SAP standalone components/non-SAP components (such as adatabase) are running.

During the registration of the agent, you must enter a large amount ofinformation about the CEN, the connection to it, and, if appropriate, themonitored J2EE instance. This SAP Note contains, as an attachment, a Java toolto simplify the registration.

734247 Registering CCMS agents for SAP Web AS Java as of 6.30You want to register the CCMS agent SAPCCMSR, to centrally monitor aninstance of a J2EE Engine as of SAP Web AS 6.30 using a central monitoringsystem (CEN) as of SAP Web AS 6.40 SP 1.

CCMS Agents


Page 113 of 115

During the registration of the agent, you must enter a large amount of dataabout the CEN, the connection to it, and the monitored J2EE instance. ThisSAP Note contains, as an attachment, a Java tool to simplify the registration.

809007 CCMS Agents and Kernel: Patches 2005This SAP Note describes the changes to the monitoring architecture through thepatch collections during 2005.

817714 Agent registration not possible with visual administrator

This SAP Note describes the manual installation of CCMS agents for a SAPNetWeaver J2EE instance or an ABAP+J2EE instance (double-stack) if it is notpossible to perform the agent registration from the Visual Administrator.

902460 CCMS: Agent displays no J2EE data in RZ20

A SAPCCMSR CCMS agent has been installed for an SAP NetWeaver 2004s(7.00) J2EE instance and registered with a central monitoring system. TheCCMS agent is displayed as ONLINE in transaction RZ21, and provides datafor OS monitoring and log file monitoring. However, no monitoring data isdisplayed for the J2EE Engine.

914721 CCMS Agents and Kernel: Patches 2006

This SAP Note describes the changes to the monitoring architecture through thepatch collections during 2006.

929635 “CCMS Agent Configuration” tab page is missingAutomatic registration of the CCMS agent from the Visual Administrator is notpossible, since the CCMS Agent Configuration tab page in the Monitoringservice of the dispatcher is not displayed. This problem can occur with thefollowing release statuses:

SAP NetWeaver 04 SP Stack 13 up to SP Stack 16

SAP NetWeaver 2004s up to SP Stack 7

9.3. Copyright

Within the functions for sending and receiving SNMP traps the CCMS agents also use coding towhich the following copyright statement applies:

Various copyrights apply to this package, listed in 3 separate parts below. Please make sure that you read all theparts. Up until 2001, the project was based at UC Davis, and the first part covers all code written during this time.From 2001 onwards, the project has been based at SourceForge, and Networks Associates Technology, Inc hold thecopyright on behalf of the wider Net-SNMP community, covering all derivative work done since then. An additionalcopyright section has been added as Part 3 below also under a BSD license for the work contributed by CambridgeBroadband Ltd. to the project since 2001.

Code has been contributed to this project by many people over the years it has been in development, and a full list ofcontributors can be found in the README file under the THANKS section.

CCMS Agents


Page 114 of 115

---- Part 1: CMU/UCD copyright notice: (BSD like) -----

Copyright 1989, 1991, 1992 by Carnegie Mellon University

Derivative Work - 1996, 1998-2000

Copyright 1996, 1998-2000 The Regents of the University of California

All Rights Reserved

Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee ishereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice andthis permission notice appear in supporting documentation, and that the name of CMU and The Regents of theUniversity of California not be used in advertising or publicity pertaining to distribution of the software without specificwritten permission.

CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARDTO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NOEVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL,INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSSOF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUSACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

---- Part 2: Networks Associates Technology, Inc copyright notice (BSD) -----

Copyright (c) 2001-2002, Networks Associates Technology, Inc

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:

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

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

Neither the name of the Networks Associates Technology, Inc nor the names of its contributors may be used toendorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ''AS IS'' AND ANYEXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALLTHE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICTLIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OFTHIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

---- Part 3: Cambridge Broadband Ltd. copyright notice (BSD) -----

Portions of this code are copyright (c) 2001-2002, Cambridge Broadband Ltd.

All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that thefollowing conditions are met:

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

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

CCMS Agents


Page 115 of 115

The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from thissoftware without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ''AS IS'' AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERBE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIALDAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 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 OROTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THEPOSSIBILITY OF SUCH DAMAGE.

Documents

CCMS Agents Features, Installation and Operation