CCMS Agents

CCMS Agents
Version 4.7 (Patch Collection 2006/5) September 20, 2007
CCMS Agents: Features, Installation, and Operation
SAP AG Neurottstr. 16 D-69190 Walldorf

SAP AG CCMS Agents: Features, Installation, and Operation Page 1 of 115 January 15, 2007
CCMS Agents
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 the express 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 components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint, and SQL Server are registered trademarks 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 USA and/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 Web Consortium, 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 technology invented and implemented by Netscape. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and several other countries all over the world. All other product and service names mentioned are trademarks of their respective companies.
SAP AG
CCMS Agents: Features, Installation, and Operation Page 2 of 115
January 15, 2007
CCMS Agents
Contents 0. 1. 2. 2.1. 2.2. Structure and Use of this Document ................................................................. 7 Introduction ......................................................................................................... 8 Functional Principle of the CCMS Agents ........................................................ 9 SAPCCMSR .........................................................................................................................9 SAPCCMSR with Option j2ee ...........................................................................................10 2.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. 2.4. 2.5. 3. 3.1. 3.2. 3.3. 3.4. 4. 4.1. 4.2. 4.3. 4.4.
SAPCCM4X .......................................................................................................................12 SAPCM3X..........................................................................................................................13 Communication ..................................................................................................................13 Installing CCMS Agents for NetWeaver Components.................................... 15 Installing an Agent on an ABAP Instance..........................................................................17 Installing an Agent on a Java Instance (Java Standalone System) .....................................18 Installing an Agent on a Java Instance (Double-Stack System).........................................20 Installing an Agent on a SAP Web AS 6.20 Java Instance/Other Hosts............................22 Installing and Registering the CCMS Agents for Experts ............................. 24 Prerequisites for the Installation.........................................................................................24 Downloading the CCMS Agents ........................................................................................25 Copying the CCMS Agent to the Desired Directory..........................................................26 Creating the Required Configuration Files.........................................................................26 4.4.1 Configuration File for Monitoring Log Files................................................................ 27 4.4.2 Configuration File for Monitoring Operating System Data ......................................... 27 4.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....................................... 29

4.4.4.1 Structure of the SAPCCMSR.INI Configuration File .......................................................30 4.4.4.2 Example SAPSSMSR.INI Agent Configuration File ........................................................32
4.5.
SAP AG
Registering the CCMS Agents ...........................................................................................32

CCMS Agents: Features, Installation, and Operation Page 3 of 115 January 15, 2007
CCMS Agents
4.5.1 4.5.2 4.5.3 4.5.4 4.5.5
Creating the CSMREG User......................................................................................... 33 Automatically Creating the CSMCONF Start File....................................................... 34 Registration with the Agent Registration Tool ............................................................. 34 Registering the CCMS Agents in Dialog...................................................................... 35 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 ............................................................. 41

4.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 ......................................................................................................... 45 4.5.8 SAPCCM4X: Creating the RFC Connections.............................................................. 45 4.6. Working Directory and Log Files of the CCMS Agents....................................................47 4.6.1 Working Directory........................................................................................................ 47 4.6.2 Log Files ....................................................................................................................... 48 4.6.3 Trace Files .................................................................................................................... 49 5. 5.1. Advanced Functions of the CCMS Agents ..................................................... 50 Monitoring Log Files..........................................................................................................51 5.1.1 Types of Monitored Log Files ...................................................................................... 51 5.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........................................................................................ 57

5.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 ................................................. 61 5.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 ........................................ 64 5.2.2 Adjusting the Configuration File for Receiving SNMP Traps ..................................... 67 5.2.3 Displaying Received SNMP Traps in the Alert Monitor.............................................. 68
CCMS Agents
5.3.
Event Log Monitoring with CCMS Agents........................................................................69 5.3.1 Structure of the Event Log Template............................................................................ 71 5.3.2 Displaying the Event Log Monitoring in the Alert Monitor......................................... 73
5.4.
Monitoring Operating System Data with CCMS Agents ...................................................75 5.4.1 5.4.2 5.4.3 5.4.4 5.4.5 Operating System Data Displayed in the Alert Monitor .............................................. 76 Configuring the Monitoring of Operating System Data ............................................... 76 Structure of the SAPOSCOL Filter File oscolfile.txt ................................................... 77 Example SAPOSCOL Filter File oscolfile.txt.............................................................. 79 Monitoring Selected Processes ..................................................................................... 81
5.5.
Alert Logging for CCMS Agents .......................................................................................84 5.5.1 Activating the Alert Logging........................................................................................ 85 5.5.2 Structure of the Alert Log File...................................................................................... 85 5.5.3 Example Alert Log File ................................................................................................ 86
5.6.
Displaying File Contents in the Alert Monitor...................................................................86 5.6.1 Example of Defining Displayable File Contents (SAPCCMSR.INI)........................... 87 5.6.2 Assigning the Required Analysis Method .................................................................... 87
5.7. 5.8. 5.9. 5.10. 5.11. 6. 6.1. 6.2.
Transferring GRMG Customizing Files to CEN................................................................88 Including Additional Functions in CCMS Agents .............................................................88 Registering with Multiple Central Monitoring Systems ....................................................89 5.9.1 Start File CSMCONF with Multiple Central Monitoring Systems .............................. 89 Monitoring Multiple Systems with an Identical System ID...........................................90 Transferring Distributed Statistics Records with CCMS Agents...................................92 Displaying Agent Data in the Central Monitoring System ............................. 93 Monitoring Contexts of the CCMS Agents in the Monitoring System ..............................93 Creating CCMS Agent Monitors in the Central Monitoring System .................................94 6.2.1 SAPCM3X: Creating a Rule-Based Monitor ............................................................... 94 6.2.2 SAPCCMSR: Creating a Rule-Based Monitor............................................................. 95
6.3. 6.4.
Self-Monitoring of the CCMS Agents ...............................................................................96 Displaying Agent Data in the Topology Display ...............................................................97 6.4.1 Calling the Display of Agent Data in the Topology Display........................................ 97 6.4.2 Data Displayed About CCMS Agents .......................................................................... 98 6.4.3 Commands in the Topology Display .......................................................................... 100
7.
SAP AG
Controlling the CCMS Agents ........................................................................ 102

CCMS Agents
7.1. 7.2. 7.3. 7.4. 8. 8.1. 8.2. 8.3. 8.4. 9. 9.1. 9.2. 9.3.
Deregistering CCMS Agents............................................................................................102 Starting and Stopping CCMS Agents...............................................................................103 Displaying the Status of a CCMS Agent..........................................................................103 Displaying the Version of a CCMS Agent .......................................................................104 Questions and Answers ................................................................................. 105 General .............................................................................................................................105 SAPCCMSR/SAPCM3X .................................................................................................106 SAPCCMSR j2ee ...........................................................................................................107 SAPCCM4X .....................................................................................................................108 Additional Information.................................................................................... 109 SAP Service Marketplace and SAP Library.....................................................................109 Important SAP Notes About CCMS Agents ....................................................................110 Copyright..........................................................................................................................113
SAP AG
January 15, 2007
CCMS Agents
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 important monitored components. If you want to use CCMS agents to monitor software components in the 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. In most cases, you will not require this information, since the procedures in section 3 will be sufficient. 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 work through this section if you want to individually tailor the advanced functions of the CCMS agents. Section 5 This section describes how you can use the advanced functions of the CCMS agents for your individual monitoring tasks. These include, for example, the monitoring of log files, sending and receiving SNMP traps, monitoring processes, or displaying the contents of files. Section 6 This section describes how monitoring information that is transferred to the central monitoring system CEN using CCMS agents is displayed in CEN. It also introduces the most important 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 of CCMS agents. Section 9 This section contains the most important additional information about CCMS agents.
SAP AG
January 15, 2007
CCMS Agents
1.
Introduction
The monitoring architecture provides an infrastructure for monitoring your IT environment and its components. Monitoring data is stored in the shared memory of every server with a running SAP 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 monitoring system 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 the Internet 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 the push technology Connect to a shared memory segment without requiring a free work process You can monitor any log files. You can monitor processes at operating system level. The actual monitoring is performed using 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 the central monitoring system as a reaction to an alert in a monitored system. For detailed information about it, see [AutoRea]. Agents monitor network data, including: - The configuration of the network environment, such as an interface or Domain Name System (DNS) - Network metrics, such as the length of time taken for a DNS address resolution
Agents also make entirely new monitoring functions possible within the monitoring architecture:
SAP AG
January 15, 2007
CCMS Agents
2.
Functional Principle of the CCMS Agents
The runtime information for the monitoring objects is stored in monitoring segments. A CCMS agent always uses exactly one monitoring segment that is either in its local process memory or in the 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 closely connected with the monitoring central monitoring system. After its installation, the CCMS agent SAPCCMSR attempts to attach itself to a monitoring segment in shared memory when it is started. If this segment does not yet exist, the agent creates it. SAPCCMSR always works in a shared memory segment that is independent of running SAP systems. The central monitoring system must have a release status of at least SAP Basis 4.6B.
Any Instance (SAP/Non-SAP) SAPOSCOL Shared Memory Central Monitoring System RZ20 Application
Log SAPCCMSR DLL Application
SAP AG
January 15, 2007
CCMS Agents
2.2. SAPCCMSR with Option j2ee

The functional principle of SAPCCMSR has been extended in case the SAPCCMSR CCMS agent is monitoring a J2EE Engine. In a case of this type, it must be possible that the monitoring segment of the SAPCCMSR agent does not belong to the central monitoring system. This is achieved by extending the system term to include Java components (such as J2EE Cluster). The SAPCCMSR agent with the -j2ee option exists for this purpose.
To use SAPCCMSR with option j2ee, you need a central monitoring system as of SAP 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 ABAP System Application server Work process Java J2EE Cluster J2EE Engine Virtual Machine (VM)
A system is no longer only a quantity of classical application servers with an ABAP runtime environment, 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 parts are combined under one system ID.
You specify the system ID and the system number of the monitored Java instance during the registration of the agent using the instance's profile (see Profile File of the CCMS Agents [page 27]). When monitoring, it should be possible to display the data for the ABAP instances and the Java instances of the same system in a central CCMS under the system ID of the monitored system. As far as possible, a Java instance should not be different from an ABAP instance; it should also be possible to monitor all instances with the same system ID locally as one system unit.
2.2.1
2.2.1.1
Examples
Monitored System with no ABAP Instances
SAPCCMSR monitors an instance of a Java system and registers itself with a central system CEN. The connection to CEN is also the primary RFC connection.
SAP AG
January 15, 2007
CCMS Agents
Monitored System ABC (with no ABAP Engines)
Central Monitoring System CEN
Host D Host A
J2EE Engine Host B HostA_ABC_33 J2EE Engine sapccmsr Host C HostA_ABC_33 -j2ee J2EE Engine sapccmsr HostC_ABC_33 -j2ee
sapccmsr -j2ee
CCMS
Alert Monitor
ABC HostA_ABC_33 HostB_ABC_33 HostC_ABC_33
Topology Display
Agents for Remote SAP Systems
System ABC ABC ABC Destination SAPCCMSR.HostA.33 SAPCCMSR.HostB.33 SAPCCMSR.HostC.33
CEN is the primary central system in each case
2.2.1.2
Monitored System with J2EE and ABAP Instances
SAPCCMSR 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 can be monitored locally as one unit.
System ABC (with J2EE and ABAP Engines)
Host A
J2EE Engine ABAP Engine Host B HostC_ABC_33 HostC_ABC_33 J2EE Engine ABAP Engine Host C sapccmsr HostC_ABC_33 HostC_ABC_33 -j2ee J2EE Engine ABAP Engine sapccmsr HostC_ABC_33 HostC_ABC_33 primre RFC-Verbindung
-j2ee sapccmsr primre RFC-Verbindung -j2ee Primary central system
CCMS
Alert Monitor
Topology Display
Agents for Local SAP System ABC
Destination SAPCCMSR.HostA.33 SAPCCMSR.HostB.33 SAPCCMSR.HostC.33 Segment Name SAP_CCMS_HostA_ABC_33_X SAP_CCMS_HostB_ABC_33_X SAP_CCMS_HostC_ABC_33_X
SAP AG
January 15, 2007
CCMS Agents
2.2.1.3
Monitored System with Java and ABAP Instances, and a CEN
In addition to the case described above, the local system, to which the Java instance belongs, can be monitored by a central monitoring system CEN:
System ABC (with Java and ABAP Engines) Local Monitoring Alert Monitor System ABC ABC
Host A
J2EE Engine ABAP Engine Host B HostC_ABC_33 HostC_ABC_33 J2EE Engine ABAP Engine Host C sapccmsr HostC_ABC_33 HostC_ABC_33 -j2ee J2EE Engine ABAP Engine sapccmsr HostC_ABC_33 HostC_ABC_33 primre RFC-Verbindung -j2ee sapccmsr primre RFC-Verbindung -j2ee
CCMS
Topology Display
HostA_ABC_33 HostB_ABC_33 HostC_ABC_33
Agents for the Local SAP System ABC

Destination SAPCCMSR.HostA.33 SAPCCMSR.HostB.33 SAPCCMSR.HostC.33 Segmen Name SAP_CCMS_HostA_ABC_33_X SAP_CCMS_HostB_ABC_33_X SAP_CCMS_HostC_ABC_33_X
Primary Central System
Host D CCMS
Alert Monitor
Secondary Central System
Topology Display
Agents for Remote SAP Systems
System ABC ABC ABC Destination SAPCCMSR.HostA.33 SAPCCMSR.HostB.33 SAPCCMSR.HostC.33
Central Monitoring System CEN
2.3. SAPCCM4X
This agent improves the monitoring of ABAP instances with SAP Basis 4.X or higher. The central monitoring system must have a release status of at least SAP Basis 4.6C. This agent provides an alternative connection route to the monitoring information in the shared memory of an 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 runtime environment. This means that they have their own monitoring segment in the shared memory area of the running system. After its installation, the SAPCCM4X agent attempts to attach itself to and to work with this monitoring segment in shared memory when it is started.
CCMS Agents
If this segment does not exist (that is, if the monitored system is not running), the agent does not create it, to avoid interfering with the shared memory management in the restarting system. In this case, the SAPCCM4X agent works with the monitoring segment that it creates in its process memory and the contents of which it synchronizes with the monitored system. SAPCCM4X constantly checks whether the monitored system is active again, and when it is, works with the monitoring segment in the shared memory again, after synchronization. The central monitoring system automatically first attempts to read data from the monitored system through the RFC destination of the CCMS agent. If the agent is not active, the system reads the monitoring data from the monitored SAP instance using the standard RFC, as previously (for more information, see SAP Note 322075). Note that even if you are using the SAPCCM4X agent, you still continue to need the standard RFC connection anyway.
SAP R/3 4.X Instance Dispatcher
RZ20 Central Monitoring System
RZ20
SAPCCM4X
Shared Memory
2.4. SAPCM3X
This agent allows the monitoring of SAP instances with SAP Basis 3.X through the CCMS monitoring architecture. These systems do not have their own CCMS monitoring architecture runtime environment. SAPCM3X therefore works always works with a monitoring segment that it 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
As an RFC server, it provides access to the data in the monitoring segment. This access is, for example, used in transaction RZ20. The agent automatically creates the local configuration files 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 is an ABAP program or a C program. In the case of ABAP programs, the maximum frequency is five minutes, while the maximum frequency for C programs (and therefore for CCMS agents) is one minute. As an RFC client, it independently sends alerts and values for the monitoring attributes to the central monitoring SAP System (push technology). This data is then stored in a cache there to allow 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 to periodically query the agents. The central monitoring system must have a release status of at least SAP Web AS 6.10 for automatic reporting of alerts. As of this release, activation of the push technology is mandatory. As of SAP Web AS 6.20, the agents also automatically report monitoring attribute values. All CCMS agents can process several tasks simultaneously (multi-thread procedure). This means that they can simultaneously: Automatically collect data Process requests as an RFC server Send data to the central system as an RFC client
SAP AG
January 15, 2007
CCMS Agents
3.
Installing CCMS Agents for NetWeaver Components
The sections of this process describe how you can install and register the appropriate CCMS agent 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 for Experts [page 24], which describes the installation and registration of CCMS agents in general terms, and which explains all individual settings.
All Possible Central Monitoring Scenarios with CCMS Agents
C11
SAPCCM4X
SAPCCMSR SAPCCM4X Dialog Instance External TREX, BC, Third Party, etc.
Central Instance
Central Monitoring System
CEN
(6.40+ ABAP) SAPCCMSR SAPCCMSR Java Addin SAPCCMSR 6.20 J2EE 6.20 J2EE SAP Web AS 6.20 Java standalone
Java Addin
Java Addin
SAP NetWeaver 04 Dual Stack
C12
SAPCCM4X SAPCCM4X Dialog Instance SAPCCMSR Dialog Instance SAPCCMSR
J2E
Central Instance Central Instance
ABAP standalone
SAP NetWeaver 04 Java standalone
Legend
ABAP System JAVA System External System DB DB
sapccmsr j2ee connection (primary) sapccmsr j2ee connection (secondary) sapccmsr 99 connection sapccm4x connection ABAP connection
SAP AG
January 15, 2007
CCMS Agents
Prerequisites
The following prerequisites must be fulfilled in every case for the installation and registration of a CCMS agent: You have a central monitoring system (CEN). If possible, reserve a separate SAP system for monitoring and system management. Do not use a production system for this, to avoid unnecessary load on the system. If you are using a separate SAP system, you can easily keep this at the newest status with regard to release or Support Package status, and profit from the newest developments 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 as follows (see also Creating the CSMREG User [page 33]): a. In CEN, call transaction RZ21 and choose Technical Infrastructure Configure Central System 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 the registration. To do this, proceed as follows: a. In CEN, call transaction RZ21, and choose Technical Infrastructure Configure Central System Create CSMCONF Start File for Agents. b. Save the file at a location that is centrally available, since you require the file for all agent registrations. You have the required executables for the CCMS agents. To download these, proceed as described in Downloading the CCMS Agents [page 25].
Process
To install a CCMS agent for one of the following components, follow the description under the appropriate 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 every instance of the system (central instance and potential dialog instances). For Java standalone systems and double-stack systems, this is automatically insured. In the case
CCMS Agents
of ABAP systems, you need to install the appropriate agent for every instance of the system.
3.1. Installing an Agent on an ABAP Instance

To monitor an ABAP instance of an SAP system, use the CCMS agent SAPCCM4X. This agent creates an alternative connection route between the monitored instance and CEN. Since this alternative connection route no longer requires a free work process, the access route is independent 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 do not 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 the following 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 command sapccm4x v to check which of the executables has the more current status, and use that one. 4. In the directory of the executable, enter the command sapccm4x R pf=<profile path>.
SAP AG
January 15, 2007
CCMS Agents
<profile path> specifies the instance profile of the monitored instance. By
default, 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 again for confirmation. Confirm the specifications by pressing the ENTER key in each case. You only need to enter two parameters yourself: The password for the administration user in CEN, under which you created the CSMCONF file. The password for the CSMREG user 6. Under UNIX, you must ensure yourself that SAPCCM4X is automatically started again when the 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 CEN using 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 agent SAPCCMSR. The agent is part of the installation package of the Engine; You only need to register 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 SAP NetWeaver 04 SP Stack 12. For J2EE Engines with a release status of SAP Web AS 6.20, follow the procedure described under Installing an Agent on a SAP Web AS 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 Java Instance (Double-Stack System) [page 20]. If problems occur during the registration of the agent on a Microsoft Windows platform, proceed as described in SAP Note 817714.
SAP AG
CCMS Agents
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 local host. In this case, however, you need to specify where you have saved the file during the registration of the agent. To do this, in the Monitoring service of the Visual Administrator (see below), choose the Change button, and specify the path for the start 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 (Microsoft Windows), 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 SID indicator, and enter in this input field an identifier for the system that is unique in your monitored 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 and displayed 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 CEN CSMREG User. The CEN Administration User is the user with administrator authorization 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? What is the version of the SAPCCMSR CCMS agent?
8. Choose the Register button. The registration log is displayed; errors are highlighted in red.
SAP AG
January 15, 2007
CCMS Agents
9. Under UNIX, the agent is automatically started by the startsap script when you start the J2EE Engine. Under Microsoft Windows, the agent is entered as a service during the registration, and is automatically started during a restart of the host. As of SAP NetWeaver 2004s, however, you need to start the associated service (which was created during the installation of the J2EE Engine) yourself. To do this, on the Microsoft Windows host on which the agent is running, choose Start Settings Control Panel Administrative Tools Services, and choose the service SAPCCMSR.<Instance No.> by double-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 in the Alert Monitor in CEN. The Customizing destination has also been automatically created for all Java instances (only if you have left the check box enable CCMS Customizing marked), so that you can also change the threshold values for the monitoring data from the Alert Monitor (see Creating Customizing Destination 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 CCMS agent. The agent is part of the installation package of the Engine; you only need to register the agent 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 that is 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: primarily with the local ABAP system, and secondarily with CEN. You only need to register and start the agent once for each system.
Note that this description applies only for monitored J2EE Engines as of SAP NetWeaver 04 SP Stack 12. For J2EE Engines with a release status of SAP Web AS 6.20, proceed as described under Installing an Agent on a SAP Web AS 6.20 Java 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 (Java Standalone System) [page 18]. If problems occur during the registration of the agent on a Microsoft Windows platform, proceed as described in SAP Note 817714.
SAP AG
January 15, 2007
CCMS Agents
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 local host. In this case, however, you need to specify where you have saved the file during the registration of the agent. To do this, in the Monitoring service of the Visual Administrator (see below), choose the Change button, and specify the path of the start 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 (Microsoft Windows), 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 SID indicator, and enter an ID for the system in the associated field that is unique in your monitored 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 users for each of these systems: one administration user and one CSMREG communication user in each system. 7. Specify the access data for these users for the local ABAP system by making all of the entries for 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 CEN Administration User and CEN CSMREG User in the relevant rows. If necessary, you can overwrite the predefined values. The CEN Administration User is the user with administrator authorization with which you created the CSMCONF start file.
If necessary, you can use the Information button to answer the following questions:
SAP AG
Is the instance profile of the instance to be monitored valid? Is the utilized CSMCONF start file valid?
CCMS Agents
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 the J2EE Engine. Under Microsoft Windows, the agent is entered as a service during the registration, and is automatically started during a restart of the host. As of SAP NetWeaver 2004s, however, you need to start the associated service (which was created during the installation of the J2EE Engine) yourself. To do this, on the Microsoft Windows host on which the agent is running, choose Start Settings Control Panel Administrative Tools Services, and choose the service SAPCCMSR.<Instance No.> by double-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 the corresponding monitoring data in the Alert Monitors of the two systems. The Customizing destination has also been automatically created for all Java instances (only if you have left the check box enable CCMS Customizing marked), so that you can also change the threshold values for the monitoring data from the Alert Monitor (see Creating Customizing Destination for SAPCCMSR j2ee [page 43]).
3.4. Installing an Agent on a SAP Web AS 6.20 Java Instance/Other Hosts

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 release status of SAP Web AS 6.20. In the case of J2EE Engines as of SAP NetWeaver 04, proceed as described under Installing an Agent on a Java Instance (Java Standalone System) [page 18] or Installing an Agent on a Java Instance (DoubleStack System) [page 20]. If you want to monitor a TREX host with the agent, proceed as described in SAP Note 704349. The operating system collector SAPOSCOL must also be running on the monitored host [SAPOsCol].
SAP AG
CCMS Agents
Procedure
1. Copy the agents executable to the following directory; if the directory does not exist, create it: UNIX:
/usr/sap/ccms/bin
Windows: \\<host>\saploc\prfclog
The saploc directory can also have another name; the important thing is that it is released 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, create it: Windows: \\<host>\saploc\prfclog\sapccmsr UNIX:
/usr/sap/tmp/sapccmsr
3. Call SAP Note 730629 (CCMS Agents: Java Interface for Registration). Copy the file csmagent.jar from the Notes attachment to a temporary directory on the host to be monitored. 4. Start the Java tool by entering the following command at the operating system prompt in the above temporary directory:
java -jar csmagent.jar
5. Select the radio button Standalone/TREX/SAP J2EE Engine 6.20. The input fields Agent Configuration 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 CEN with 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 in CEN. 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 you restart 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 the corresponding monitoring data in CENs Alert Monitor.
SAP AG
January 15, 2007
CCMS Agents
4.
Installing and Registering the CCMS Agents for Experts
This section describes the installation and registration of CCMS agents in general terms, with all settings. In most cases, however, you will only want to register SAP NetWeaver components with a CEN using CCMS agents. These standard procedures are 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 SAPCCMSR SAPCCMSR with the option j2ee SAPCCM4X SAPCM3X Suitable for: Components with no SAP instance and J2EE Engines with SAP Web AS 6.20; Central monitoring system as of SAP Basis 4.6B Java instances as of SAP NetWeaver 04; Central monitoring system as of SAP NetWeaver 04 ABAP instances as of SAP Basis 4.X; Central monitoring system as of SAP Basis 4.6C SAP systems with SAP Basis 3.X
When installing a CCMS agent under Microsoft Windows NT or Microsoft Windows 2000, you require administrator rights on the relevant host. Install SAPCCM4X and SAPCM3X using the user <SID>adm (UNIX) or SAPService<SID> (Microsoft Windows) of the monitored system to ensure that the agent can access the shared memory. If multiple SAP R/3 3.X systems are running on one host, note the following points: Install only one SAPCM3X agent for each host. If you specify a profile, the agent monitors only one system; therefore, do not specify 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 to register one agent per monitored instance.
SAP AG
CCMS Agents
4.2. Downloading the CCMS Agents

1. You require the file CCMAGENT.SAR. This archive contains all CCMS agents, including SAPCCMSR, SAPCCM4X, and SAPCM3X.
We recommend that you use the newest version of each agent. You can determine the version of a CCMS agent with the option v (see Displaying the Version of a CCMS Agent [page 104]). The archive also contains the availability agent CCMSPING. For more information about the availability agent, see [Avail].
2. You can download CCMAGENT.SAR from the SAP Software Distribution Center of the SAP Service Marketplace (http://service.sap.com/swdc). Log on with your SAP Service Marketplace ID. Check the following folders in the specified order for this file and download it: In the navigation bar, choose Download Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP NETWEAVER 2004S Entry by Component Application Server ABAP SAP KERNEL 7.00 32/64BIT <operating system> Database Independent. Only if the desired archive does not exist in the above folder, choose Download Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NetWeaver components (< SAP NW 04) SAP WEB AS SAP WEB AS 6.20 SAP 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 Download Support Packages and Patches Archive for Support Packages and Patches Entry by Application Group SAP Application Components SAP R/3 SAP R/3 4.6A SAP KERNEL 4.6D 32/64-BIT <operating system> Database Independent. The reason for specifying multiple folders is that CCMS agents are partly dependent on the operating system release. Agents for a current SAP release may no longer cover all available operating system releases (for example, agents for SAP Web Application Server 6.20 are supported only on HP-UX 11.x; however, there are still application servers to be monitored that are running on HP-UX 10.x).
You can determine the version of the CCMS agents in CCMAGENT.SAR by displaying the associated Info File.
SAP AG
January 15, 2007
CCMS Agents
If you require an agent for an older operating system release that is not in the folders above, SAP also provides the newest CCMS agent functions in patches to older 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 SAP Note 212876 (The new archiving tool SAPCAR). For decompressing the archive, use the following instruction:
sapcar xvf ccmagent.sar
Up to SAP NetWeaver 04 CCMS agents wer e freely backward compatible, so you could independent of the monitored system release always use the latest release of the 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 with release NW04 (6.40). To monitor a SAP instance with release NW2004s (7.00) or a host without SAP instance, 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 SAPCCMSR SAPCM3X SAPCCMSR j2ee SAPCCM4X Microsoft Windows
\\<host>\saploc\prfclog \\<host>\usr\sap\ <SysID>\SYS\exe\run
UNIX
/usr/sap/ccms/bin /usr/sap/<SysID>/SYS/exe/run
The saploc directory in the path of the CCMS agent SAPCCMSR can also have another name; the important thing is that it is released as a share with the name saploc. By default, this is the directory <drive:>\usr\sap. If the directory does not 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 (see Starting and Stopping CCMS Agents [page 103]).
SAP AG
January 15, 2007
CCMS Agents
4.4.1
Configuration File for Monitoring Log Files
If you want to monitor log files with the CCMS agent, create one or more log file templates (see Structure of the Log File Template of the Log File Agent [page 53]).
4.4.2
Configuration File for Monitoring Operating System Data
If you want to configure the monitoring of operating system data individually, create a SAPOSCOL filter file, with which you can explicitly activate and deactivate parts of the operating system monitoring (see Structure of the SAPOSCOL Filter File oscolfile.txt [page 77])
4.4.3
Profile File of the CCMS Agents
You specify a profile file during the registration of a CCMS agent with pf=<profile>. This is mandatory 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]. This profile file must also be the profile for the monitored instance. Both profile files are stored under the 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 specification of 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 allows you 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 a profile 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 File
The 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
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 by Support; the default value is 1 (trace deactivated)
SAPSYSTEM
This parameter is only important for the agent SAPCCMSR with Option j2ee [page 10]. It specifies 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]. It specifies the system ID of the Java instance monitored by the agent.
While you can, in general, monitor multiple systems with identical system IDs [page 90], this is only possible to a restricted extent if you are using the -j2ee option: the system ID of the system associated with the agent (SAPSYSTEMNAME) must not match the 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 shared memory segment of the agent. These alerts are instead automatically written to the database of 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 of this kind do not inform you of error situations, but are intended as all-clears, or explicit messages 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 used as a replacement for emergencies or maintenance periods, but which should be externally addressed 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 is currently running. Ensure this by setting an identical profile parameter SAPLOCALHOST in the profile file of the CCMS agent. Take this into account with the SAPCCMSR agent in
CCMS Agents
particular, as the SAPCCM4X agent uses the profile parameters of the SAP application server by default. You should also use SAPLOCALHOST if the name of the host on which you are installing the CCMS agent is longer than 13 characters in length. Specify a name with a maximum length of 13 characters. This is then used for the name of the RFC destination of the agent and the monitoring segment of the agent.
In the case of alternating operation of hosts of this type, the hosts work with monitoring segments with the same name, meaning that the data is reported in the same tree in the Alert Monitor. The content of the segment is saved to the files ALMTTREE, ALALERTS, and ALPERFHIS during the shutdown of a host. If you now ensure that these AL* files are accessible from both hosts, the contents of the segment are not disturbed by switching host.
End each line of the profile file with the ENTER key. 4.4.3.2 Example Profile File
You are registering the CCMS agent SAPCCMSR under Microsoft Windows and specify a profile 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 Agents
The 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 primarily contains 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 the following functions: Your own settings for Monitoring Log Files [page 51] Configuring the Monitoring of Operating System Data [page 76]
SAP AG
CCMS Agents
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] Structure of the SAPCCMSR.INI Configuration File Description Optional parameter that specifies how often the agent automatically reports values to the central monitoring system:
n=1: n=0: n<30: n30:
4.4.4.1
You can set the following parameters in SAPCCMSR.INI: Parameter

PushCycleMinutes <n>
Default, values are reported every minute Values are never report Values are reported every n minutes Values are reported every 30 minutes
PlugIn <file path> [<directory for loading additional dll>]
Shared library of the agent to be loaded; multiple plug-ins are possible. The file path must not contain any spaces. Some plug-ins, such as itsmon.dll, require in turn additional shared libraries, which are stored in a particular directory. In this case, specify the directory as a second parameter, as otherwise the CCMS agent only searches for these libraries in its working directory, meaning that they might not be loaded. Configuration file for monitoring log files (log file template); you can specify one configuration file for each log file See Types of Monitored Log Files [page 51]
LogFile <file path> LogFileDir <directory path>
You may only specify one directory LogFileDir in the Configuration file.
LogfileParam DelTree
If you specify Deltree, obsolete elements for which no log file exists any longer, are deleted from the shared memory
SAP AG
January 15, 2007
CCMS Agents
Parameter
DsrDir
Description Directory in which the agent searches for DSR statistics files to transfer them to the primary central monitoring system CEN; for information about the default directory, see Transferring Distributed 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 no longer be read and transferred to CEN.
OsColFile <file path>
Specifies a SAPOSCOL filter file for filtering out subtrees of the operating system monitoring; the subtrees are then no longer stored in shared memory Files for which the agent has explicit permission to read for display in the Alert Monitor Full path of a log file for detected alerts (specify the filename without suffix, the suffix .log is automatically set) Scope of the alert logging If you are Monitoring Multiple Systems with an Identical System ID [page 90] in your system landscape, specify a unique name for the system of the agent here. The first three characters of the name should correspond to the system ID of the monitored system (only for agent SAPCCM4X). Complete path of the configuration file for receiving the SNMP traps (see Adjusting the Configuration File for Receiving SNMP Traps [page 67]) Complete path of the configuration file for sending the SNMP traps (see Adjusting the Configuration File for Sending SNMP Traps [page 64]; for a general description of SNMP functions for CCMS agents, see Setting Up the Sending and Receiving of SNMP Traps Using CCMS Agents63 [page 63]) See Transferring GRMG Customizing Files to CEN [page 88]. See Event Log Monitoring with CCMS Agents [page 69]
ViewDirList <file path> AlertLog <file path> AlertLogLevel <level> LongSid <target system>
TrapReceiveFile <file path> TrapSendFile <file path>
GrmgDir EventLogMon [On|Off] EventLogMon <file path> EventLogResolveMessag es [On|Off]
SAP AG
January 15, 2007
CCMS Agents
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 File
If SAPCCMSR.INI does not yet exist when the CCMS agent is registered, the system creates the following 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. We recommend that you have the central monitoring system create the data required for this (see Automatically Creating the CSMCONF Start File [page 34]).
CCMS Agents
A prerequisite for the registration is that a CSMREG user exists in CEN (see Creating the CSMREG User [page 33]). You can perform the registration in different ways: Registration with the Agent Registration Tool [page 34]; use this tool for registering the SAPCCMSR 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 CCMS Agents [page 38])
For information about the special features of the registration of SAPCCMSR with Option j2ee [page 10] are discussed in Registering SAPCCMS with the Option -j2ee [page 41].
4.5.1
Creating the CSMREG User
As of SAP Web AS 6.40 SP 1 and as of 6.20 SP 42, you can have the CSMREG automatically created in CEN. To do this, start transaction RZ21 and choose Technical Infrastructure Configure 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 call transaction 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 Basis 4.6B) is selected on the Logon Data tab page. The profile should contain the following authorizations (the specified authorization object S_CCM_RECV is only relevant in connection with the CCMS System Component Repository, which is delivered as of SAP Basis 4.6C): Authorization Object Field S_RFC RFC_NAM E ACTVT S_CCM_RECV ACTVT TABLE
SAP AG
Value SALC SALP SYST 16 P0-P2 *

January 15, 2007 Page 33 of 115
RFC_FUGR FUGR SALF SALS SCSM* SALH SAL_CACHE_RECEIVE RFC1
CCMS Agents: Features, Installation, and Operation
CCMS Agents
4.5.2
Automatically Creating the CSMCONF Start File
During the registration of CCMS agents, you primarily enter information about the central monitoring system and the users used for communication between the agent and the central monitoring system. You can enter the registration both in dialog and dialog-free, by specifying a start 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 central monitoring system it is possible that you have the central monitoring system create CSMCONF for the registration of the CCMS agents. This applies irrespective of whether you want to perform the registration with the agent registration tool, in dialog or dialog-free.
If you are performing the registration in dialog, the CCMS agent creates a CSMCONF start file itself from your input and stores it in the working directory of the agent (see Working Directory [page 47]). Only the passwords used are removed. This means that if you are registering CCMS agents on different hosts, you could also perform the registration once in dialog and then add the passwords to the automatically created CSMCONF files and use this file as the template for the other registrations. 1. Choose CCMS Configuration Alert Monitor, or call transaction RZ21. 2. Choose Technical Infrastructure Configure Central System Create CSMCONF Start File for Agents; specify the agents Working Directory [page 47] as the location to which CSMCONF 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 of CCMS Agents [page 38]), proceed as follows: a. Edit CSMCONF and enter the corresponding passwords in the parameters CEN_ADMIN_PASSWORD and CEN_CSMREG_PASSWORD. b. Specify CSMCONF for the registration after the option f.
4.5.3
Registration with the Agent Registration Tool
The agent registration tool simplifies the registration of the SAPCCMSR agent with exactly one CEN. 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 agents working directory (see Automatically Creating the CSMCONF Start File [page 34])
SAP AG
CCMS Agents
Proceed as described in the appropriate procedure below, depending on which component is running 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 Dialog
During the registration of the agent, you enter the required connection data in the central monitoring system. An RFC connection to the agent is automatically created in the central monitoring system during registration. Ensure before the registration that the required configuration files are available. Depending on the agent, you perform the registration using the following command: Agent SAPCCMSR SAPCCMSR j2ee SAPCM3X SAPCCM4X Registration
sapccmsr R [pf=<profile path>] sapccmsr j2ee R pf=<profile path> sapcm3x -R [pf=<profile path>] pf=<profile path>
sapccm4x R
With SAPCCM4X and SAPCCMSR j2ee, <profile path> is the full file path of the profile of the monitored instance. In the case of SAPCCMSR/SAPCM3X, it is the full file path of the agent 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 Registering with Multiple Central Monitoring Systems [page 89]) For every central monitoring system, you must also enter a valid SAP user that is used once to create an RFC connection to the agent in the central monitoring system.
This user requires the authorization to execute transactions RZ20/21 (S_RZL_ADM with authorization field ACTVT and value 01) and to enter an RFC destination using transaction SM59 (S_ADMI_FCD with authorization field S_ADMI_FCD and value NADM). In detail, you enter the following user data (if there is a default value for an entry, this is shown in square brackets. If you want to use this default value, simply press the ENTER key):
SAP AG
January 15, 2007
CCMS Agents
Due to the high number of parameters to be entered, we recommend that you have a CSMCONF start file created in the central monitoring system in order to reduce the number of required parameters (see Creating the CSMREG User [page 33]). In this case, you only need to enter the passwords yourself, and confirm the other parameters from 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 load balancing) - 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 connections from CCMSPING to the CEN gateway (and, in the case of logon load balancing, also to 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 and is not stored For every central monitoring system, you require the connection data of the gateway (usually the message server of the central monitoring system) with which the CCMS agent communicates 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, the CCMS agent automatically sends alerts to the central monitoring system as an RFC client; as of 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 monitoring system. The user used for this purpose can be purely an RFC user and need not possess any rights at all, as it only calls a precisely defined function module that does not perform any
CCMS Agents
additional authorization checks itself. We recommend that you use the user CSMREG for this purpose (see Creating the CSMREG User [page 33]). In detail, you enter the following data for this CSMREG user for all central monitoring systems: - 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 load balancing) - 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 in an encrypted file called passwd. For the SAPCCM4X agent, and for agent SAPCCMSR with Option j2ee [page 10], you can optionally 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 and started as a service during the registration. The agent is automatically restarted at every restart. Enter the following information for this (ensure that the Services window is not open during 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. This profile is usually accessed using a share. You must therefore ensure that the account under which the service for the agent is running has the required network authorizations. You can ensure this by specifying SAPService<SID> as the account.
CCMS Agents
If you have successfully completed the registration, the system displays the message EXITING
with code 0; if an error has occurred, the system displays this.
4.5.5
Alternative: Dialog-Free Registration of CCMS Agents
You can also perform the registration of CCMS agents dialog-free by creating a start file that contains all of the information that you enter during the installation in dialog (see Registering the CCMS Agents in Dialog [page 35]). You can use any name for this start file. In the following text, it is called CSMCONF. The configuration file is always the same when installing the CCMS agent on more than one server. It therefore makes sense to install the CCMS agent using appropriate software distribution methods and to then configure it automatically. To have the registration performed dialog-free, use the option -f <file name> to specify the start file from which the system should take all installation information. Save this file in the working directory of the CCMS agent: Agent SAPCCMSR SAPCM3X SAPCCM4X 4.5.5.1 Installation Call
sapccmsr r -f <file name> [pf=<profile path>] sapcm3x -r -f <file name> [pf=<profile path>] pf=<profile path>
sapccm4x r -f <file name>
Structure of the CSMCONF Start File
The CSMCONF start file consists of a minimum of the following three sections in which you can specify the connection to the central monitoring system:
SAP AG
January 15, 2007
CCMS Agents
Specification of the Central Monitoring System

CEN_CONFIG CEN_SYSID=<System ID of the central monitoring system> .
User data of a user with authorization for system administration in the central monitoring system (see Registering the CCMS Agents in Dialog). This user is used once to create an RFC connection to the agent in the central monitoring system.
CEN_ADMIN_USER CEN_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) .
Connection data of the gateway with which the CCMS agent communicates as an RFC server
CEN_GATEWAY CEN_GATEWAY_HOST=<Host name of the gateway; usually the message server in the central system> CEN_GATEWAY_SYSNR=<System number of the gateway>
If you are installing the CCMS agent on a Microsoft Windows host, you can optionally specify logon data for the user under which the agent is to run as a Microsoft Windows service. The agent is then automatically started at every restart of the server. By default, the <LocalSystemAccount> is used for this purpose.
Information about the user under which the agent is to run as a Microsoft Windows service
SERVICE_INFO SERVICE_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> .
If your central monitoring system has a release status of at least SAP Web AS 6.10, the agents automatically report data to the central monitoring system. To do this, the agent requires an automatically 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
Information about the CSMREG user

CEN_CSMREG_USER CEN_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]> .
For the SAPCCM4X agent, and for agent SAPCCMSR with Option j2ee [page 10], you can optionally assign the monitored system to a system group in the central monitoring system. You require an additional section in the CSMCONF start file to do this (if the monitored system is not to be assigned to a system group, leave the MGDSYSTEM section empty):
Information about a system group of the monitored system
MGDSYSTEM SYSTEM_GROUP=<System group in CEN to which the monitored system is assigned [optional]> .
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 character in the line. The passwords CEN_ADMIN_PASSWORD and CEN_CSMREG_PASSWORD are no longer 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, see Registering with Multiple Central Monitoring Systems [page 89].
SAP AG
January 15, 2007
CCMS Agents
4.5.5.2
Example CSMCONF Start File
CEN_CONFIG CEN_SYSID=CEN . # example: does not use logon load balancing CEN_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 balancing CEN_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 -j2ee
The CCMS agent SAPCCMSR with Option j2ee [page 10] has been especially conceived for monitoring a J2EE Engine. The monitoring segment of the agent in this case belongs to the local system of the J2EE Engine, and not to the central monitoring system.
SAP AG
January 15, 2007
CCMS Agents
4.5.6.1
Registering SAPCCMS with the Option -j2ee in Dialog
During the registration of the CCMS agent with the option -j2ee, you must first answer the questions of whether there is at least one ABAP instance in the agents system (parameter SAPSYSTEMNAME of the Profile File of the CCMS Agents [page 27]), and whether there is a central monitoring system in your system landscape. The various options are described in the following chapters: Situation No ABAP instance exists, central monitoring system (CEN) exists ABAP instance exists, no central monitoring system (CEN) exists ABAP instance exists, central monitoring system (CEN) exists Chapter Monitored System with no ABAP Instances [page 10] Monitored System with J2EE and ABAP Instances [page 11] Monitored System with Java and ABAP Instances, and a CEN [page 12]
The system ID and system number of the agents local system are specified with the profile parameters SAPSYSTEM and SAPSYSTEMNAME, meaning that you no longer have to specify this information in the registration in dialog. After you have entered this information about your system landscape, perform the rest of the registration as described in Registering the CCMS Agents in Dialog [page 35]. 4.5.6.2 Dialog-Free Registration of SAPCCMS with the Option -j2ee
If you want to install SAPCCMSR with the option -j2ee dialog-free, note that if there is an ABAP instance in the agents local system, the local system is formally its primary central monitoring system (see Structure of the CSMCONF Start File [page 38] and Registering with Multiple Central Monitoring Systems [page 89]). The CSMCONF start file therefore contains information about the ABAP instance of the agents 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 prefix CEN2. In detail, the various possible cases (see Examples [page 10]) in the CSMCONF start file are as follows:
SAP AG
January 15, 2007
CCMS Agents
Situation No ABAP instance, CEN exists ABAP instance exists, no CEN exists ABAP instance exists, CEN exists
CSMCONF Prefix CEN: Central monitoring system Prefix CEN2 CEN5: secondary central systems (optional) Prefix CEN: Agents local system Prefix CEN: Agents local system Prefix CEN2: Central monitoring system Prefix CEN3 CEN5: Secondary central systems (optional)
4.5.6.3
Creating Customizing Destination for SAPCCMSR j2ee
Use the CCMS agent SAPCCMSR with Option j2ee to transfer monitoring data for a Java instance to a central monitoring system (CEN). You can display this monitoring data both in the Alert 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 a Customizing destination after you have registered the agent. This destination is used to transfer the property changes from the Alert Monitor directly to the J2EE Engine.
If you register the CCMS agent using the Visual Administrator (see Installing an Agent on a Java Instance (Java Standalone System) [page 18] and Installing an Agent on a Java Instance (Double-Stack System) [page 20]), the Customizing destination is automatically created during the registration of the agent. You only require the following procedure if you have manually registered the agent in accordance 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.
SAP AG
January 15, 2007
CCMS Agents
4. In the other input fields, enter the connection data of the central monitoring system. If you do not have the data, you can find it in the start file CSMCONF in the Working Directory [page 47] of the agent Creating an RFC Destination in the ABAP System
Create the RFC destination in the ABAP system with which you have registered the agent. If the agent is monitoring a Java instance in an ABAP+Java system, this is the local ABAP system. If the agent is monitoring an instance of a standalone Java system, this is CEN. 5. To create an RFC destination, call transaction SM59 and choose the Create button. The RFC Destination screen appears. 6. Enter the name of the destination in the RFC Destination input field. Use the naming convention SAP.CCMS.J2EE.<JSID>, where <JSID> is the system ID of the monitored Java instance. 7. Enter T (Start an External Program via TCP/IP) as the connection type, and enter a description 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 the Registered Server Program radio button, and enter SAP.CCMS.J2EE.<JSID> in the Program 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 RFC destination (see Connecting J2EE Engine to the CCMS). 10. Switch to the Special Options tab page, and choose the Unicode radio button in the Character Width in Target System group box. 11. Save your entries. Making the RFC Destination Known to the Monitoring Architecture 12. Call transaction RZ21. 13. If the agent is monitoring a Java instance in an ABAP+Java system, choose the Agents for the Local 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 for Remote 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 RFC destination created above, SAP.CCMS.J2EE.<JSID>, as for the agent in the column J2EE Customizing Destination. 15. Save your entries.
SAP AG
January 15, 2007
CCMS Agents
Result
You have now created the required RFC destination and made it known to the monitoring architecture. You can now also change the properties of the nodes for the corresponding CCMS agent SAPCCMSR j2ee in the Alert Monitor.
4.5.7
Starting the Agent
Under Microsoft Windows NT the CCMS agent is automatically started, as the system starts the associated service. If you have registered the CCMS agent under UNIX, the agent has not yet been started. Start it using the appropriate command: Agent SAPCCMSR SAPCCM4X SAPCM3X Start Command
sapccmsr DCCMS [pf=<profile path>] sapccm4x DCCMS sapcm3x pf=<profile path>
DCCMS [pf=<profile path>]
Under UNIX, you must also ensure yourself that the CCMS agent is automatically started after a restart of the server (for example, by entering the start command in INITTAB).
4.5.8
SAPCCM4X: Creating the RFC Connections
If a SAP R/3 System is connected with the central monitoring system using the CCMS agent SAPCCM4X, there are two RFC connection types between the systems: A connection of type T (connection to an external program using TCP/IP) from the central monitoring system to the CCMS agent SAPCCM4X; this connection is created during the registration of the agent Two connections of type 3 (connection to an SAP R/3 System) directly from the central monitoring 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 monitoring system before you register the agent, these connections of type 3 already exist - in this case, you do not need to create any connections. Otherwise, you must create these RFC connections yourself. For security reasons, we recommend that you define two RFC destinations for every monitored system here, as there are two requirements that are different in principle between the monitored and the monitoring systems: Data Collection There are data collection methods are active in the monitored system. These methods store values for the monitoring attributes in the shared memory of the monitored system. The monitoring system reads these values using an RFC call (and therefore a particular user name). In the monitored system, this user is merely an observer that must log on to this system for each query. Executing Analysis Methods
SAP AG
CCMS Agents
If a data collection method reports an alert, you can start an analysis method. As this analysis method may make changes in the monitored system, it must have more extensive authorizations in the target system. As the two types of requirement access the monitored system in very different ways, and also occur with very different frequencies, we recommend that you assign different authorizations to different 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 type Communication (SAP Web Application Server 6.10) or CPIC (up to SAP Basis Release 4.6D) is activated. For more information about user CSMREG, see Creating the CSMREG 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 target system 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 following names (as explained above, you must define two RFC destinations): RFC Destination for data collection to start analysis methods Name of the RFC Destination
<target system ID>_RZ20_COLLECT <target system ID>_RZ20_ANALYZE
3. In the Connection type field, enter 3 (SAP R/3 System) and in Description, enter a short descriptive text for the RFC connection. Choose Enter. 4. The Technical Settings tab page appears, on which there are a few additional fields. For Load distribution, choose Yes and choose Enter again. 5. Now fill out the other fields in the Technical Settings tab page: Field Target System ID Message server Group Save as
SAP AG
Input Target system ID (such as C11) Host name of the message server Logon group to be used on the target system (use transaction SMLG to display the available groups) The message server can be internally saved either as the entered host name or in the form of its associated IP address.
CCMS Agents
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 for data collection to start analysis methods Recommended User CSMREG Current User or user of your choice
The user for the execution of the analysis methods requires an authorization for the Alert Monitor 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 monitoring architecture that the connections to the target system now exist. To do this, start transaction RZ21, and, in the Topology group box, activate the System Overview radio button. Choose Display 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, the communication status was set to SHUTDOWN. On the Monitored Remote SAP Systems tab page, 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 Directory
Working Directory
/usr/sap/tmp/sapccmsr (UNIX) \\<host>\saploc\prfclog\sapccmsr
The working directory is in the following location, depending on the type of CCMS agent: CCMS Agent SAPCCMSR Alternative
$DIR_PERF/sapccmsr (if the DIR_PERF
(Microsoft Windows) SAPCCMSR with the -j2ee option SAPCCM4X SAPCM3X

/usr/sap/ccms/<SysID>_<SysNo>/ sapccmsr (UNIX) \\<host>\saploc\ccms\<SysID>_<SysNo>\ sapccmsr (Microsoft Windows) $DIR_LOGGING/sapccm4x
parameter is specified)
$DIR_CCMS/<SysID> _<SysNo>/sapccmsr (if the DIR_CCMS
parameter is specified)
(UNIX notation)
$DIR_PERF/sapcm3x
(UNIX notation)
CCMS Agents
The saploc directory in the path of the CCMS agent SAPCCMSR can also have another name; the important thing is that it is released as a share under the name saploc; by default, it is the directory <drive:>\usr\sap. If the directory does not exist, create it yourself during the registration. In the case of SAPCCMSR with Option j2ee [page 10] , a subdirectory <System ID>_<instance number> is created in /usr/sap/ccms (UNIX) or \\<host>\saploc\ccms (Microsoft Windows), so that the agents of different systems and numbers are separated. The files ALMTTREE, ALPERFHI, and ALALERTS are stored in this directory (since the agent manages its own shared memory, these AL* files must also be stored separately from those of possible ABAP instances with the same number.) The log files of the agent are stored in the subdirectory <System ID>_<instance number>\sapccmsr.
CSMCONF Contains data about the central monitoring system; the parameters correspond to those in the start 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 SAPOSCOL information should be considered; this file is read when the agent is started (see SAPCCMSR.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 central monitoring system. You can use transaction RZ21 to do this. In the Topology group box, select one of the Agents for radio buttons. . The Monitoring: Display Technical Topology screen appears. Now select the desired agent and then choose Working Directory of the Agent ( ). The system displays the files of the directory. To display the contents of a file, choose the file by double clicking it.
4.6.2
Log Files
If you install the CCMS agent in dialog mode, the entire system logging is performed directly to the 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.
SAP AG
January 15, 2007
CCMS Agents
4.6.3
Trace Files
You 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 intermittent problems: The first megabyte of the trace is always kept in full, along with one to two megabytes at the end of the trace.
SAP AG
January 15, 2007
CCMS Agents
5.
Advanced Functions of the CCMS Agents
To activate advanced functions of the CCMS agents, you must usually create a corresponding configuration file and either reference this file in the SAPCCMSR.INI: Configuration File for the CCMS 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 Starting and 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 corresponding monitoring function is started.
Files and Directories for the Advanced Functions

CCMS Agent
Agents Working Directory CSMCONF

Start file of the agent, contains information about the central monitoring systems and their communication users
\\<host>\saploc\prfclog or /usr/sap/tmp grmg Contains Customizing files, these are automatically transferred to CEN (GRMG_*) procmon
SAPCCMSR.INI
Configuration file of the agent, contains many other path specifications for files with settings for 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
Contains files that specify the processes to be monitored (*procmon.ini) \\<host>\saploc\CCMS\<SysID>_<Inst.-No> or /usr/sap/CCMS/<SysID>_<Inst.-No> logmon Contains log file templates that are automatically read (*logmon.ini) dsr Contains the DSR files that are automatically transferred to CEN
Changes to these files are detected only after the agent has been restarted
Changes in these directories are automatically detected by the agent
SAP AG
January 15, 2007
CCMS Agents
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 last change time, or for their existence. This means that you can search any text files (such as database alert logs or ITS log files) for any text patterns, assign alerts to them, and display the results 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, or display 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 case of the SAPCCM4Xagent, these are the files to which the <SID>adm user (UNIX) or the SAPService<SID> (Microsoft Windows) has access to, as this agent must always run under this user. In the case of the SAPCCMSR agent, these are the files that the user under which the agent is running has permission to read.
5.1.1
Types of Monitored Log Files
Types of log files that the CCMS agents can monitor: Log files that are continuously by the application and are therefore constantly growing (such as 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 as the dev_w* files of the SAP application server) With these files, the agent reads newly added entries and saves its last read position. Due to the smaller size of the log file, it automatically recognizes the restart of an application and in this 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 automatically recognizes the newest log files of a type, so that the current log file can always be monitored.
CCMS Agents
You can activate the monitoring of log files in the CCMS agent configuration file SAPCCMSR.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 that contains the details of the monitoring (log file template). SAPCCMSR.INI can contain multiple entries 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 be monitored. The log file agent also automatically detects log file templates if these fulfill the following conditions; 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 SAPCCMSR SAPCM3X SAPCCMSR j2ee SAPCCM4X Naming Convention
*logmon.ini *<SysID>_<InstNo>*logmon.ini *<SysID>_ABAP_<InstNo>*logmon.ini
<SysID> and <InstNo> are the system ID and the instance number of the monitored
ABAP or Java instance. The J2EE Engine automatically generates suitable templates and stores these in the specified (cross-instance) directory. The system ID and instance number are part of the naming convention since the shared memory of the CCMS agents SAPCCMSR j2ee and SAPCCM4X are only to contain the logfile monitoring tree for the monitored Engine (ABAP or Java). So it is assured that every agent is only monitoring the logfiles of its own monitored instance. 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 SAPCCMSR j2ee SAPCCM4X
SAP AG
Directory of the Log File Templates UNIX:

/usr/sap/ccms/<SysID>_<InstNo>/logmon
Windows: [drive]:\usr\sap\ccms\<SysID>_<InstNo>\logmon
$DIR_LOGGING\logmon, that is by default <instance directory>\log\logmon
CCMS Agents
Agent SAPCCMSR SAPCM3X
Directory of the Log File Templates 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 file agent automatically detects log file templates in SAPCCMSR.INI (see SAPCCMSR.INI: Configuration File for the CCMS Agents [page 29]). However, since this means that the log file templates in the standard directory are no longer read, and the corresponding log files are no longer monitored, we do not recommend this procedure. You can use the optional entry LogFileParam DelTree to specify that subtrees should be deleted 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 Agent
The log file template contains information about which text files are to be analyzed in which form. 5.1.2.1 General Settings for the Monitored Log Files
The following parameters of the log file template apply to all log files that fulfill the conditions for 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>"
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 FILENAME condition; wildcards are permitted
If you want to monitor the trace files of the work processes, dev_w*, but not the previous version of these trace files, dev_w*.old, set FILENAME=dev_w* and IGNORE_FILE=dev_w*.old.
CCMS Agents
MONITOR_CONTEXT="<Context_name>"
Name of the monitoring context to which the log file agent writes the results of the monitoring; by default, this is the context Files_of_<Hostname>. Regardless of whether or not you set this parameter, the MTE class of the monitoring context is always CcmsFileMonitoring. By specifying this MTE class, you can define a rule-based monitor that contains the subtrees for all monitored log files. In this way, you can, for example, store different components in different contexts to further group the results. Like the PREFIX parameter (see below), this function allows you to differentiate between the different monitored log files, but provides, unlike PREFIX, an additional hierarchical level to group the monitored files. Use this parameter only if you require 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 fulfill the search criteria exceeds this number, exactly <number> files with the newest change time are monitored.
This means that different files are monitored over time. If a file is removed from monitoring because other files have a newer change date, its monitoring tree is deleted, and its alerts are reset. The maximum value for <number> is also 20, to avoid storing an unnecessarily large quantity 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 be disregarded 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 the lines that have been added since the log file agent last read the file (0) (Default: FileSize is not created)
MONITOR_FILESIZE_KB=<file size[KB]>
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, an alert is generated
PREFIX="<character string>"
Appears before the MTE nodes; allows you to differentiate between different log files with different paths, but the same name (the maximum length of the prefix is 8 characters)
CCMS Agents
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 File Existence (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 the FILENAME condition has just been created, the corresponding node is assigned the specified auto-reaction method immediately when it is created. This ensures that the alerts are processed more quickly, since the assignment of the central auto-reaction is otherwise performed by the program SAPMSSYT, which only runs once an hour, by default. In extreme cases, it is even possible that, with the traditional method assignment, the auto-reaction method is not executed at all for the first alerts for the corresponding 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 assignment of the auto-reaction method to newly-created nodes. This ensures a quicker processing of the corresponding 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 then monitors the last change time point of the log files (1), or whether the last change time point is not to be monitored (0) (Default: CcmsFile<file name>) MTE class of the monitoring object that contains the attributes specified above; the MTE class of the monitoring objects therefore depends on the name of the monitored log file (Default = 0) Specifies whether the system is to check only for the existence of the log files (1). In this case, all parameters for monitoring and for search patterns (see below) are ignored.
MTE_CLASS="<MTE class>"
CHECK_EXISTENCE_ONLY=[0,1]
SAP AG
January 15, 2007
CCMS Agents
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 for pattern even if none of the search patterns are found in the relevant line. If you set this parameter, only the lines that contain the relevant search pattern are copied to the agent's shared memory.
If you set this parameter and the value Last incoming message is set for the setting Display "current value" like, the last matching line is always displayed in the log attribute in the Current Status view in the Alert Monitor. 5.1.2.2 Monitored Search Pattern in the Monitored Log Files
You can specify multiple search patterns to be monitored for each of the log files that fulfils the conditions for DIRECTORY and FILENAME. When doing this, enter a number <x> for each search pattern 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 length of the pattern is 80 characters) Default = RT 149
MESSAGEID_<x>="<message ID>"
Message number that is assigned to the alert

VALUE_<x>=[RED,YELLOW,GREEN]
Default = YELLOW Color of the alert in the monitoring architecture Default = 0
SEVERITY_<x>=[0...255]
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 Files
You can use the parameters explained above to monitor log files for search patterns to which an alert is to be assigned (such as the search pattern Error). This function is not ideal for displaying search patterns to which no alert is to be assigned (such as version or date information). Only one
CCMS Agents
log attribute is available in the Alert Monitor for all monitored search patterns, meaning that only one 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 search pattern of this type is found, the Alert Monitor displays the corresponding line as the content of a separate text attribute. You can define the name of the text attribute yourself. If the search pattern exists 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 length of the pattern is 80 characters); if the search pattern is found, the system displays the line of the 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 is INFO[<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 be truncated correspondingly.
5.1.3

Example Log File Templates
The 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 also to be deleted in RZ20. To do this, set the parameter DelTree. SAPCCMSR.INI must therefore contain the following lines:
Logfile /usr/sap/tmp/sapccmsr/ORAALERTlogmon.ini Logfile /usr/sap/tmp/sapccmsr/DEV_Wxlogmon.ini Logfile /usr/sap/tmp/sapccmsr/SAPCCMSRlogmon.ini Logfile /usr/sap/tmp/sapccmsr/BACKUPSlogmon.ini LogFileParam DelTree
If these log file templates were stored in the folder intended for this purpose (see Types of Monitored Log Files [page 51]), the log file agent would definitely find these templates. An entry in the SAPCCMSR.INI file would then be superfluous.
CCMS Agents
The contents of the log file templates mentioned above are shown in the following: 5.1.3.1 Oracle Alert Log
The template /usr/sap/tmp/sapccmsr/ORAALERTlogmon.ini would have the following content:

LOGFILE_TEMPLATE DIRECTORY="/oracle/<SID>/saptrace/background" FILENAME="alert_<SID>.log" MTE_CLASS="ORAALERT" PATTERN_0="ORA-00600" VALUE_0=RED MESSAGECLASS_0="SAP-T100" MESSAGEID_0="rt 584" .
The agent searches through /oracle/<SID>/saptrace/background/alert_<SID>.log continuously for ORA-00600 messages and returns a red alert if it finds a matching message:
Display for this Monitoring Function in the Alert Monitor
Files of Host3 alert_C11.log
Host on which a CCMS agent that monitor log files is running Subtree for a monitored log file
/oracle/C11/saptrace/background/alert_C11.log ORA-00600 735: ORA-00600: internal error code, arguments: [12 Log File checked at Mon Feb 03 15:00:32 2003
Complete Name Monitored Patterns Lines found for pattern Data Collection Check
Complete name of the monitored log file Search pattern Original line with line number in which the search pattern was found Last check of the file
5.1.3.2
Trace Files of the SAP Work Processes
The template /usr/sap/tmp/sapccmsr/DEV_Wxlogmon.ini would have the following content:

LOGFILE_TEMPLATE DIRECTORY="/usr/sap/<SID>/<Instance name>/work" FILENAME="dev_w*" IGNORE_FILE="dev_w*.old" MTE_CLASS="WORKPROC" SHOWNEWLINES=1 MONITOR_FILESIZE_KB=0 PATTERN_0="ERROR" VALUE_0=RED
CCMS Agents
MESSAGECLASS_0="SAP-T100" MESSAGEID_0="rt 584" PATTERN_1="core" VALUE_1=RED MESSAGECLASS_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 nine subtrees for nine work processes. The system also displays the size of the files and the number of lines reported per minute:
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
/usr/sap/C11/Host3/work/dev_w0 | core Error 2056: M ***LOG R49=> ThCPICSyncWait, CPIC-Error Log File checked at Mon Feb 03 14:56:39 2003 65 /min 45 KB
Complete Name Monitored Patterns Lines found for pattern Data Collection Check New Lines in Log File Log File Size dev_w6 dev_w2 dev_w0 dev_w1
Subtrees of the other monitored log files, sorted by the time of the last change
Growth of the file Size of the file
When the dev_w* files are recreated after a restart of the application server, the agent recognizes this using the file size and begins reading from the start of the files. 5.1.3.3 Log File of the SAPCCMSR CCMS Agent
The template /usr/sap/tmp/sapccmsr/SAPCCMSRlogmon.ini would have the following content:

LOGFILE_TEMPLATE DIRECTORY="/usr/sap/tmp/sapccmsr" FILENAME="sapccmsr.log" MTE_CLASS="Log_of_sapccmsr" MONITOR_LAST_FILE_MODIF=1 PATTERN_0="ERROR" VALUE_0=RED MESSAGECLASS_0="SAP-T100"
CCMS Agents
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 for ERROR messages and returns a red alert if it finds a matching message. The agent also displays the last change of the monitored log file. The agent also searches for other search patterns to which no alert value is assigned and, if it finds one of these patterns, displays the corresponding line as the content of a separate text attribute. This means that a line that contains the search pattern CCMS version is displayed completely, 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 that contains the search pattern.
SAP AG
January 15, 2007
CCMS Agents

Files of Host3 Sapccmsr.log
Host on which a CCMS agent that monitors log files is running Subtree for the monitored log file
/usr/sap/tmp/sapccmsr/sapccmsr.log CCMS version 20010925, 32 bit, multithreaded, Non-Unicode compiled at Feb 4 2003 systemid 560 (PC with Windows NT) relno 6200 patch text patch collection 2003/2, OSS note 584136 patchno 611 intno 20020600 running on P57373 Windows NT 5.0 2195 Service Pack 3 pid 2004 Error 2056: M ***LOG R49=> ThCPICSyncWait, CPIC-Error Log File checked at Mon Feb 03 14:56:39 2003 Mon Feb 03 14:56:37 2003
Complete Name INFO [CCMS Version] INFO [Compiled at] INFO [System ID] INFO [Release] INFO [Patch Text] INFO [Patch number] INFO [internal number] INFO [Host] INFO [Process ID] Monitored Patterns Lines found for pattern Data Collection Check File Time Stamp
Nodes with no alert functions; a separate node is displayed for each search pattern
Time of the last change of the monitored log file
5.1.3.4
Log File for the Backups of an Oracle Database
The template /usr/sap/tmp/sapccmsr/BACKUPSlogmon.ini would have the following content:

LOGFILE_TEMPLATE DIRECTORY="/oracle/OMA/sapbackup" FILENAME="*.ant" MONITOR_NEWEST_FILES=1 MTE_CLASS="BACKUPS" PATTERN_0="ERROR" VALUE_0=RED PATTERN_1="successfully" VALUE_1=GREEN .
The agent searches through the newest file of the format /oracle/OMA/sapbackup/*.ant continuously for ERROR messages and successfully messages and returns a red alert if it finds ERROR, 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, and deletes obsolete subtrees.
5.1.4
Display for Log File Monitoring in the Alert Monitor
The results are displayed in the Logfile Monitoring monitor of the SAP CCMS Monitors for Optional Components monitor set or in a self-defined monitor (see Creating CCMS Agent Monitors in the Central Monitoring System [page 94]). As shown in the examples above, the monitor creates a subtree for each monitored file. The name of the subtree consists of a prefix
CCMS Agents
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, in turn, consists of some or all of the following monitoring tree elements, depending on the values of the parameters in the corresponding log file template: MTE (Suffix of the MTE Class) Complete Name (.ComplPath) Description
Complete name including file path of the monitored log file from the point of view of the monitoring CCMS agent
You can also display the content of the monitored files in the Alert Monitor. To do this, double click the Complete Name attribute in which the name of the monitored file is displayed. Info[<Name>] (.ApplInfo) If you are searching for search patterns with no alert value, the system displays the line that contains the search pattern APPL_INFO_<n> in the text attribute Info[<APPL_INFO_MTE_NAME_<n>>] (see Search Pattern to be Output in the Monitored Log Files [page 56]). Search pattern with alert value (see Monitored Search Pattern in the Monitored Log Files [page 56]); You can monitor a file for multiple search patterns (the system displays these in the monitor separated by |)
Monitored Patterns (.Patterns)
Lines found for pattern Lines of the log file that match the search pattern (.MatchingL) Data Collection Check (.CollCheck) File Time Stamp (.TimeStamp) New Lines in Log File (.NewLines) Log File Size (.FileSize) Time of the last check of the log file; this status attribute is always colored green. Time of the last change of the monitored log attribute; this attribute is only created if you specify the parameter MONITOR_LAST_FILE_MODIF=1 in the log file template Growth of the monitored log file in lines per minute; this attribute is created only if you specify the parameter SHOWNEWLINES=1 in the log file template Size of the log file; this attribute is created only if you specify the parameter MONITOR_FILESIZE_KB0 in the log file template (if MONITOR_FILESIZE_KB>0, you also assign an alert threshold value to the attribute by setting)
SAP AG
January 15, 2007
CCMS Agents
The MTE class is formed from the value of the parameter MTE_CLASS (which is set in the corresponding log file template) and the suffix specified in the table.
5.2. Setting Up the Sending and Receiving of SNMP Traps Using CCMS Agents
Simple Network Management Protocol (SNMP) functions are also integrated into the monitoring architecture. This enables both communication with external management platforms and monitoring of SNMP-compatible devices. In this situation, SNMP traps are always to be sent if an alert occurs in particular nodes. You can send and receive SNMP traps with CCMS agents. When sending SNMP traps using CCMS agents unlike Sending SNMP Traps as an Auto-Reaction Method an SNMP traps is sent for all alerts in the agent's segment. When sending using agents, the agent itself sends the traps instead of starting a new process for each alert (as is the case when sending using autoreactions).
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 the platform HP64 at the moment.
Procedure
1. Adjust the relevant configuration file. You define here, among other things, the recipient to which the SNMP traps are to be sent or the port at which SNMP traps are to be received. For more 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 (see SAPCCMSR.INI: Configuration File for the CCMS Agents [page 29]). To do this, set the following parameters, depending on whether you want to send or receive the SNMP traps: Parameter
trapSendFile
Description Complete path of the configuration file for sending SNMP traps
trapReceiveFile Complete path of the configuration file for receiving SNMP traps
SAP AG
January 15, 2007
CCMS Agents
Ensure that the configuration files for sending or receiving the SNMP traps contain a complete 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 can access these files. 3. To have the change in SAPCCMSR.INI take effect, restart the agent (see Controlling the CCMS Agents [page 102]). You can now send alerts in the monitoring segment of a CCMS agent as SNMP traps and receive SNMP traps using CCMS agents.
5.2.1
Adjusting the Configuration File for Sending SNMP Traps
You define details about the sending of the SNMP traps in the configuration file, such as the recipients and the port to which the traps are to be sent, and the protocol with which they are to be 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 is specified 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
VERSION HOSTNAME COMMUNITY INFORM
Description SNMP version (1, 2c, or 3) Receiving host for the SNMP traps Name of the community (logical group of devices within a network monitored by SNMP, to which access rights are assigned) Indicator of whether a trap (<SPACE>) or an inform (X) is to be sent; with an inform, unlike with an SNMP trap, a return message is sent (as of SNMP version 2c) Timeout for the request in seconds (only if INFORM=X) Number of repetitions if the timeout is exceeded (only if INFORM=X) Transport log
Default
1 localhost public <SPACE>
TIMEOUT RETRIES TRANSPORT
1 5 UDP
SAP AG
January 15, 2007
CCMS Agents
Parameter
PORT MIB_DIR
Description Port number of the recipient of the SNMP trap Complete path of the directory that contains the Management Information Base (MIB) files
Default
162 .
Change this value to the path of the MIBS directory. Set the following parameters only if you are using SNMP version 3: Parameter
USER_NAME AUTH_PASSPHRASE SECURITY_LEVEL
Description Name of the SNMP user Password of the SNMP user Security level; the following levels are supported:
NoauthNoPriv: no authentication, no encryption (Default) authNoPriv: Authentication, no encryption
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 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 is generated during the communication if INFORM=1 Reserved for internal use Not yet supported
SECURITY_ENGINE
CONTEXT_ENGINE CONTEXT_NAME PRIV_PROTOCOL PRIV_PASSPHRASE
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
# 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=ls3016 MIB_DIR=. # send SNMP v1 trap to DESTINATION_0 [DESTINATION_0] VERSION=1 COMMUNITY=PUBLIC TIMEOUT = 3 RETRIES = 2 TRANSPORT =UDP HOSTNAME=ls3016 # send SNMP v2 trap to DESTINATION_1 [DESTINATION_1] VERSION=2c INFORM=0 # send SNMP v3 trap to DESTINATION_2 [DESTINATION_2] VERSION=3 INFORM=1 USER_NAME=myuser AUTH_PASSPHRASE=mypassword # send SNMP v3 trap to DESTINATION_3 [DESTINATION_3] VERSION=3 INFORM=0
CCMS Agents
USER_NAME=myuser AUTH_PASSPHRASE=mypassword SECURITY_ENGINE=0x0102030405 HOSTNAME=ls3016 AUTH_PROTOCOL=MD5
5.2.2
Adjusting the Configuration File for Receiving SNMP Traps
You 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 the recipient is to listen. Make the following settings in the configuration file: Section [SNMP_TRAPD] Parameter
MIB_DIR
Description Directory that contains the MIB files (Management Information Base); this is required to display the received traps correctly
Default
. (programs
directory)
Change this value to the path of the MIBS directory.

LISTEN_PORT_<x>
Transport protocol and port number with which the traps are received; by using different values of X=0,1,2..., traps can be received by different ports With SNMP Version 3, the user must authenticate himself or herself; in the case of incorrect authorization, an Authentication Failure Trap is generated. You can avoid traps of this type being displaying by setting DROP_AUTH=1
UDP:162
DROP_AUTH
Section [SNMP_USER] If you are using SNMP version 3, define one or more SNMP users which receive the SNMP traps 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

<SECURITY_ENGINE>
Description 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 is generated during the communication if INFORM=1
January 15, 2007
SAP AG
CCMS Agents
Parameter
<USER_NAME> <AUTH_PROTOCOL>
Description Name of the user 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 Password of the user
<AUTH_PASSPHRASE>
Example
The template rectraps.cfg for the configuration file is in the directory for_recipient of the SNMPLIB. It has the following content:
[SNMP_TRAPD] DROP_AUTH=0 MIB_DIR=. LISTEN_PORT_0=udp:162 [SNMP_USER] createUser myuser MD5 mypassword createUser -e 0x0102030405 myuser1 MD5 mypassword1
5.2.3
Displaying Received SNMP Traps in the Alert Monitor
You can receive SNMP traps with CCMS agents. In this case, the received SNMP traps are displayed in a separate context SNMP_<hostname> in the monitoring segment of the receiving CCMS agent:
C u r r e n t S t a t u s ( 20.12.2003 , 17:08:45 )
-Node Display Off
System / All Monitoring Segments / All Monitoring Contexts SAP_CCMS_Host1 Files_of_Host1 MoniInfra_Host1 Host1 SNMP_Host1 Host2 [12.19.201.40] SNMP-Traps Host3 [12.19.200.41] SNMP-Traps
Monitoring segment of the receiving CCMS agent Standard monitoring context of the agent that was installed on Host1 Monitoring context with receiving SNMP traps SNMP traps sent from Host2
red 20.12.2003, 17:05:18
SNMP traps sent from Host3

red 20.12.2003, 17:04:48
There is a log attribute for each host that receives the SNMP traps. Multiple messages are generated for each trap (each with the value red). A separate message is generated for each
CCMS Agents
parameter that is set in an active Management Information Base (MIB) and which was assigned a value in the SNMP trap.
You set which MIBs the receiving CCMS agent takes into account in a configuration file (see Adjusting the Configuration File for Receiving SNMP Traps [page 67]), which you specify, in turn, in parameter TrapReceiveFile in the configuration file of the SAPCCMSR.INI agent.
Id SNMP_TRAP_MSC_1 SNMP_TRAP_MSC_1 SNMP_TRAP_MSC_1 SNMP_TRAP_MSC_1 SNMP_TRAP_MSC_1 SNMP_TRAP_MSC_1 SNMP_TRAP_MSC_1 SNMP_TRAP_MSC_1 SNMP_TRAP_MSC_1 SNMP_TRAP_MSC_1 Date 20.12.2003 20.12.2003 20.12.2003 20.12.2003 20.12.2003 20.12.2003 20.12.2003 20.12.2003 20.12.2003 20.12.2003 Time 17:04:12 17:04:12 17:04:12 17:04:12 17:04:12 17:05:18 17:05:18 17:05:18 17:05:18 17:05:18 Value red red red red red red red red red red Message Text RFC1213-MIB::sysUpTime.0 = Timeticks: (1) 0:0 RFC1155-SMI::internet.6.3.1.1.4.1.0 = OID: SAP SAP-MIB::r3maAlertSystemName = STRING: C SAP-MIB::r3maAlertSegmentName = STRING: RFC1213-MIB::sysUpTime.0 = Timeticks: (1) 0:0 RFC1155-SMI::internet.6.3.1.1.4.1.0 = OID: SAP SAP-MIB::r3maAlertSystemName = STRING: C SAP-MIB::r3maAlertSegmentName = STRING:
An SNMP trap generates multiple messages in a log attribute. Depending on the MIB used, values for the parameters that the trap contains may be displayed here. The trap is completed by a message with no message text.
5.3. Event Log Monitoring with CCMS Agents

On Microsoft Windows platforms, you can use CCMS agents to monitor the Windows Event Log. 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 and failed logons. You determine which events are to be logged in the corresponding security settings. Applications This log contains events that were written by an application or program. The application developer 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
SAP AG
CCMS Agents
Error Success Audit and Failure Audit, only for security events
By default, after you activate event log monitoring, all event log events are monitored and displayed 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 Event Log 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 of the 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
EventLogMon [On|Off]
Meaning
EventLogMon On activates the event log monitoring on the Microsoft Windows host of the CCMS agent; by default, it is deactivated.
EventLogMon <file path>
This parameter specifies an event log template that contains additional configuration settings for event log monitoring (see Structure 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 of this type, which point to multiple event log templates.
EventLogResolveMessages [On|Off] EventLogResolveMessages On activates the complete
resolution of the event log messages, that is, a more exact description of the event is obtained using additional Microsoft Windows system calls and transferred to CEN. This means that you obtain more exact information at the cost of performance. By default, this is deactivated.
To activate these settings, you need to restart the agent after setting the parameters in SAPCCMSR.INI (see Controlling the CCMS Agents [page 102]).
CCMS Agents
Result
The Microsoft Windows Event Log is monitored and displayed as a subtree in the Operating System monitor of the monitored host (see Displaying the Event Log Monitoring in the Alert Monitor [page 73]).
5.3.1 Structure of the Event Log Template

By default, all event sources (Sources) of the Application, System, and Security event logs are monitored when monitoring the Microsoft Windows Event Log. By specifying one or more event log templates, you can instead restrict the monitoring to selected event logs or event sources, and also deviate from the default alert values for the events. You specify these event log templates in SAPCCMSR.INI: Configuration File for the CCMS Agents [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 multiple event log templates.
Structure
Monitored Event Logs In the event log template, first specify which event log (Application, System, or Security) you want to monitor:
EVENTLOG_TEMPLATE
Keyword for the agent; this opens the configuration area for event log monitoring
EVENTLOG_NAME=[Application, System, Security]
Name of the event log to be monitored

MTE_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 need to 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
SAP AG
January 15, 2007
CCMS Agents
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 reported to the monitoring infrastructure by specifying the desired event source in SOURCE_<x>. When doing this, enter a number <x> for each desired event source in the parameter suffix of the following parameters. Start with the number 0. In this way, you can set the desired alert colors individually 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 have only events from certain event sources monitored; if the name of the event source contains a space, 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 event log 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 log from 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 log from 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 event log 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 event log from the event source defined by SOURCE_<x>

Example
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 (=).
You want to monitor only the following event sources in the System event log:
Automatic Updates Service Control Manager
CCMS Agents
Events from the Automatic Updates event source should never trigger an alert, regardless of the type of the event, but should rather always be reported as a green message. To do this, set the following entries in the SAPCCMSR.INI configuration file:
EventLogMon On EventLogMon C:\usr\sap\prfclog\sapccmsr\evtmon_appl.ini
The event log template evtmon_appl.ini would have the following content:
EVENTLOG_TEMPLATE EVENTLOG_NAME=System MTE_CLASS=EventLogSystem SOURCE_0="Automatic Updates" INFO_0=GREEN WARNING_0=GREEN ERROR_0=GREEN SUCCAUDIT_0=GREEN FAILAUDIT_0=GREEN SOURCE_1="Service Control Manager" INFO_1=GREEN WARNING_1= YELLOW ERROR_1=RED SUCCAUDIT_1=GREEN FAILAUDIT_1=RED .
5.3.2 Displaying the Event Log Monitoring in the Alert Monitor

If 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 monitoring system. Which event sources of which event logs are displayed in this subtree depends on the configuration of the event log monitoring.
SAP AG
January 15, 2007
CCMS Agents
Current
-Node Display Off
S t a t u s ( 20.05.2005 , 16:42:45 )
Operating System Host1 EventLogs System
Name of the monitor Host on which a CCMS agent with activated event log monitoring is running Subtree for event log monitoring Events in the System event log
System Service Control Manager: The SAPDB service failed to start be <ALL>
Event Log Name Event Log Entries Monitored Sources Application Event Log Name Event Log Entries Monitored Sources Security Event Log Name Event Log Entries Monitored Sources
Events in the Application event log

Application Norton AntiVirus: Virus definitions are current <ALL>
Events in the Security event log

Security Security: Handle Closed: Object Server: Security Account Man <ALL>
Monitored event sources; if not restricted in the event log template, always all sources
Log attribute with events from the corresponding event log; alert values either in accordance with defaults (Information = green, Warning = yellow) or in accordance with event log template settings
Integration
Since the monitoring is performed by a CCMS agent, this agent must be installed and active on the Microsoft Windows host for which the event log is to be monitored (see Registering the CCMS Agents [page 32]).
Prerequisites
Event log monitoring must be active; this means that at least the parameter EventLogMon On must 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, its events, and the monitored event sources. The subtree consists of the following MTEs:
SAP AG
January 15, 2007
CCMS Agents
MTE (MTE Class) Event Logs (CCMSEventLogs) <Name of an event log> (CcmsEventLogCL) Event Log Name (CcmsEventLogCL.ComplPath) Event Log Entries (CcmsEventLogCL.Entries)
Description Subtree for event log monitoring Subtree for the events of an event log (by default, the event logs System, Application, and Security are monitored) Name of the monitored event log Log attribute containing events from the corresponding event log; by default, the alert values have the usual values (Information = green, Warning = yellow, Error = red); however, you can also make these settings yourself in the event log template (see Structure of the Event Log Template [page 71]) Monitored event sources; if these are not restricted in the event log template, all sources are always monitored
Monitored Sources (CcmsEventLogCL.Sources)
If you have set the MTE class yourself in the event log template, the name component CcmsEventLogCL in the above MTE class name is replaced by the value of the parameter 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/Monitoring Alert 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, and expand 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 and stores this in a segment of the shared memory. All CCMS agents can copy this data to the CCMS monitoring segment and transfer it to the central monitoring system. This means that the data is visible in the CCMS monitoring architecture and is displayed in the familiar transactions ST06 and OS07. For more detailed information about the operating system collector, see [SAPOsCol] and SAP Note 371023.
CCMS Agents
In this way, you can monitor the operating system data for servers without a running SAP Basis system or SAP Web AS. An expensive installation and configuration of RFCOSCOL is no longer necessary.
5.4.1
Operating System Data Displayed in the Alert Monitor
After the successful installation of the agent, the CCMS monitoring architecture displays the following 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 is therefore well suited to being an analysis method for the Operating System monitor. You can display this data using the RFC destination SAPCCMSR.<hostname>.99.
5.4.2
Configuring the Monitoring of Operating System Data
The agent also allows an individualized selection of subtrees for the Operation System and Filesystems monitors. You can use a filter to explicitly remove subtrees or entire components from the monitoring display. No monitoring nodes are then generated for these. Alternatively to filtering out file systems, you can activate an exclusive monitoring with which only the file systems 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 MTE classes for the monitored operating system data as desired. This means that you can assign operating 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 the function 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 to specify a configuration file in which you can make these settings. In this case, SAPCCMSR.INI would 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.
SAP AG
January 15, 2007
CCMS Agents
5.4.3
Structure of the SAPOSCOL Filter File oscolfile.txt
You 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 be copied to the CCMS monitoring segment, and for which the system will therefore not create a subtree 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 be copied to the CCMS monitoring segment. In this way, you can, for example, exclude particular file systems that are always 100% full from the monitoring. You can specify the file 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 group yourself 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 operating system data for different hosts to different MTE classes. Use the keyword MonitorComponent. 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 CPU CPU_Utilization 5minLoadAverage Idle Number of CPUs Paging Page_In Page_Out Default MTE Class CPU CPU_Utilization 5minLoadAverage Idle CPU_Number Paging Page_In Page_Out Self-Set MTE Class <Name> <Name>_Utilization <Name>_5minLoadAverage <Name>_Idle <Name>_CPU_Number <Name> <Name>_Page_In <Name>_Page_Out
Commit_Charge Commit_Charge <Name> CommitChargeFree CommitChargeFreeSpace <Name>_FreeSpace Commit_Percent CommitChargePercent_Used <Name>_Percent_Used Swap_Space Freespace Percentage_Used Swap_Space SwapFreespace SwapPercentage_Used <Name> <Name>_FreeSpace <Name>_Percentage_Used
SAP AG
January 15, 2007
CCMS Agents
You can see from the table that the set MTE class is used as a prefix for the associated monitoring 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 exclusive monitoring. This means that subtrees in the monitoring architecture are only created for file systems specified after the keyword MonitorFilesystem. Other file systems are ignored. Entries with the keyword FilterOutFilesystem are also ignored. The syntax of the keyword is:
MonitorFilesystem <file system> [<MTE class> [<attribute group>]]
You can also assign a separate MTE class or attribute group to the monitoring object of the file 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 explicitly assigned this MTE class. Adjusting the Monitoring of the LAN Interfaces As of Patch Collection 2005/4, you can exclusively monitor specific LAN interfaces in the same way as monitoring specific file systems. You can also set the MTE class and attribute group 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 with the 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 LAN interface MS TCP, you can simply enter MS* for <LAN>.
If you have installed an SAPCCM4X agent, there is already a complete Operating System 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 is started, the SAPCCM4X agent then creates a new Operating System monitoring tree in accordance with oscolfile.txt: Follow the procedure below: 1. To do this, start transaction RZ21 in the system that the SAPCCM4X agent is monitoring. In the Methods group box, select Method Definitions and choose Display Overview.
CCMS Agents
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 on the Control tab page, deactivate the Execute method immediately after start of a monitoring 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 are monitored by the operating system collector SAPOSCOL. You can change this MTE class (and the attribute group) by specifying the desired name after the keyword MonitorProcess. 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 stored in the SAPOSCOL working directory (see [SAPOsCol]). Note that with the keyword MonitorProcess, you only assign monitored processes to classes and groups; unlike FilterOutFilesystem and MonitorFilesystem, it does not have any filter functions.
5.4.4
Example SAPOSCOL Filter File oscolfile.txt
The following file is intended to assist you in creating the filter file oscolfile.txt; the meaning 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
# 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
FilterOutComponent CPU FilterOutComponent SwapSpace MonitorFilesystem /usr/sap/trans FilterOutComponent Filesystems
Meaning Does not create subtree CPU and does not create subtree SwapSpace Only creates a tree for the file system
/usr/sap/trans
Does not create a subtree for file systems
SAP AG
January 15, 2007
CCMS Agents
Contents of oscolfile.txt
FilterOutComponent CPU FilterOutFilesystem /oracle/C11/sapdata*
Meaning Does not create a CPU subtree Does not create trees for file systems that match the pattern /oracle/C11/sapdata* (such as /oracle/C11/sapdata2); all other file systems are displayed Only creates a tree for file systems that match the pattern /oracle/C11/sapdata* (such as /oracle/C11/sapdata2); the nodes are created under the MTE class CL_ORA and the attribute group CG_ORA Creates the subtree for the *disp+work processes with the default MTE class MonitoredProcessesMo and the attribute group Kernel_Group Subtree CPU has the MTE class and attribute group host123CPU, and its monitoring attributes have this name as a prefix
MonitorFilesystem /oracle/C11/sapdata* CL_ORA GC_ORA
MonitorProcess *disp+work MonitoredProcessesMo Kernel_Group MonitorCompontent CPU host123CPU host123CPU
5.4.5
Monitoring Selected Processes
You can also use the operating system collector SAPOSCOL [SAPOsCol] to monitor the availability of selected processes. The monitor displays the number of running processes and the CPU and memory usage for each name template, broken down by different users. You can optionally set the configuration for process monitoring in the following configuration files (these files are called templates in the following): File dev_proc Files of the procmon directory, which follow the naming convention below: CCMS Agent SAPCCMSR SAPCM3X SAPCCMSR j2ee SAPCCM4X Naming Convention
*procmon.ini *<SysID>_<InstNo>*procmon.ini *<SysID>_ABAP_<InstNo>*procmon.ini
<SysID> and <InstNo> are the system ID and the instance number of the
monitored ABAP or Java instance. The J2EE Engine automatically generates

CCMS Agents
suitable templates and stores these in the specified (cross-instance) directory. The system ID and instance number are part of the naming convention since the shared memory of the CCMS agents SAPCCMSR j2ee and SAPCCM4X are only to contain the process monitoring tree for the monitored Engine (ABAP or Java). procmon and dev_proc are stored in SAPOSCOLs working directory (Microsoft Windows: \\<host>\saploc\prfclog; UNIX: /usr/sap/tmp/logmon).
The process monitoring is performed at collection intervals of one minute, by default. CCMS agents 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 must have 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:
SAP AG
January 15, 2007
CCMS Agents
Start of the monitored processes
# This is a test file for # monitoring processes $PROC
Since no user is specified, the processes for all users are displayed
# Is saposcol running? *saposcol* CUSTOMGROUP=SAPOSCOL
Use * to find saposcol irrespective of its path (for example, to find the process with the path /usr/sap/tmp/saposcol) By specifying the same attribute group, you can easily adjust the threshold values for these monitored processes By specifying an MTE class, you can create a rule-based monitor that contains this process; to improve the clarity of the display, the monitoring object has the name Workprocesses
# 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 $
End of the monitored processes
The individual parts of the lines have the following meaning: Parameter
Name template
Description Monitored process; you can use the wildcard character asterisk (*) (see the example below); it is not possible to monitor all processes by entering only the wildcard character asterisk User under whose name the process is running; you can use the wildcard character asterisk (*) MTE class to which the nodes are to belong; you can create your own monitors in which precisely the desired processes are displayed by assigning the process names to an MTE class
Notes mandatory, max. 40 characters optional, max. 20 characters optional, max. 30 characters
User
MTE class
To do this, use the rule

CCMS_GET_MTE_BY_CLASS in a rule-
based monitor, and specify the above MTE class there.

MTE name
MTE name under which the monitoring object for the monitored process name is displayed in the alert monitor; if you do not set this parameter, Name template is used as the MTE name
optional, max. 40 characters

January 15, 2007
SAP AG
CCMS Agents
Parameter
Attribute group
Description Attribute group to which the attributes of a monitored process name are to belong; you can simplify the maintenance of the threshold values using an assignment to an attribute group
Notes optional, max. 30 characters
Enter the above parameters without quotation marks; the parameter values must not contain any spaces or special characters. SAPOSCOL reads the contents of the configuration files every five minutes. You do not need to change SAPOSCOL or restart the responsible CCMS agent. Setting the Threshold Values Since the expected CPU and memory usage is different for each process, ensure that you adjust the threshold values of the corresponding performance attributes. The simplest way to do this is directly in the alert monitor itself, by selecting the relevant performance attribute and choosing Properties. There are two options available to avoid accidentally changing the threshold values for other monitored processes: Set the threshold value individually for the MTE (to do this, choose Edit Properties Use for Individual MTE) Use a specific attribute group in the configuration file for the desired monitored process. Your changes 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 the operating system monitor and in the Operating System monitor, in the Monitored Processes subtree (settings for MTE class, MTE name, and attribute group have no effect on the output in the 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 system management tools that are to be based on the data from the CCMS agents.
SAP AG
January 15, 2007
CCMS Agents
5.5.1
Activating the Alert Logging
You can activate alert logging in the CCMS agent configuration file SAPCCMSR.INI (see SAPCCMSR.INI: Configuration File for the CCMS Agents [page 29]). Use the parameters AlertLog and AlertLogLevel to do this: Parameter
AlertLog <filename>
Meaning Complete path of the log file (specify the filename without suffix, the suffix .log is automatically set)
Every day, the log file for the previous day is saved under the following 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, or
newly created MTEs
5.5.2
Structure of the Alert Log File
Every 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

Alert Type
Meaning 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 Alert ID Short text of the alert MTE
Time of the alert (not for alert type = ALERT VANISHED) Self-explanatory Short text of the message assigned to the alert Specifies where the alert occurred:
<System>\<Context>\...\<Monitoring object>\<Monitoring attribute>
SAP AG
January 15, 2007
CCMS Agents
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 monitoring architecture. When doing so, the name of the monitored file, for example, is displayed as a text attribute (as in the case of Monitoring Log Files [page 51]). To quickly display the contents of a file of this type or of a URL from the Alert Monitor, there are two analysis methods that display the contents of the file or the URL in a separate window. This analysis method is already assigned 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 CCMS agent.
For security reasons, the CCMS agent only transfers files for which you have previously assigned a display authorization. To do this, enter the files whose display is to be allowed into SAPCCMSR.INI: Configuration File for the CCMS Agents [page 29], after the key word ViewDirList. You can use the wild card character (*).
You do not need to assign read authorization in the SAPCCMSR.INI file for the working directory of the CCMS agents (see Working Directory [page 47]) and the
SAP AG
January 15, 2007
CCMS Agents
working directory of the operating system collector SAPOSCOL. The files in these directories 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 The following can be displayed: /usr/sap/tmp/info.txt the file /usr/sap/tmp/info.txt
Keyword: a file or a directory follows, the content of which can be displayed
ViewDirList
ViewDirList
C:\test\*
all files in the directory C:\test
ViewDirList
$DIR_PROFILE
all files in the profile directory $(DIR_PROFILE)
5.6.2
Assigning the Required Analysis Method
Assign the appropriate analysis method to the desired text attribute. To do this, follow the procedure below: 1. Start the Alert Monitor using transaction RZ20 or choose CCMS Control/Monitoring Alert 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 and then choose the Method Assignment pushbutton. 5. The Monitoring: Methods screen appears. The rest of the procedure depends on whether you want 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 the Display Change ( ) pushbutton, and choose the Analysis tab page. In the Method Assignment group box, choose Method Name. 7. If you want to assign the analysis method to the selected MTE class, choose the name of the MTE class in the header data of the screen by double clicking it and choose change mode using the Display Change ( ) pushbutton. In the Analysis Method group box, choose Method Name. 8. In the Method Name input field, enter one of the following method names:
CCMS Agents
- CCMS_SHOW_FILE_FROM_TEXT_ATTR, if the contents of the text attribute is to be interpreted as a file name; the associated CCMS agent returns the contents of this file through RFC, and it is then displayed. - CCMS_SHOW_URL_FROM_TEXT_ATTR, if the contents of the text attribute is to be interpreted as a URL; the Web browser is called at the frontend with this URL. 9. Save your entries.
Result
If the text attribute can be interpreted as a file name or a URL, you can now display the contents of 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 of technical components or of steps in business processes [GRMG]. When doing so, both Customizing information and availability queries and responses are exchanged as XML files. A Customizing file specifies which component(s) are to be monitored. To transfer this information to the central monitoring system, Customizing files with the prefix GRMG_ are automatically transferred and the associated scenario is started, if the relevant files are in the following directory:
\\<host>\saploc\prfclog\grmg (Microsoft Windows) /usr/sap/tmp (UNIX)
Although you can change this directory by setting the parameter GrmgDir in the SAPCCMSR-INI configuration file (see Structure of the SAPCCMSR.INI Configuration File [page 30]), we do not recommend this. Changing the parameter might mean that SAP components that are instrumented for monitoring with GRMG are 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 additional information to the central monitoring system. An example of this is an extension for monitoring the Internet Transaction Server (ITS) and cached disk subsystems, such as EMC Disc Arrays (Symmetrix). For more information, see SAP Note 420213.
SAP AG
January 15, 2007
CCMS Agents
5.9. Registering with Multiple Central Monitoring Systems

You can also register the CCMS agents with multiple monitoring systems. This means in principle 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 only have write access to the properties of the nodes in the primary central monitoring system. The primary system is the system that you specify first during the registration (see Registering the CCMS Agents [page 32]). In detail, you cannot execute the following commands in the secondary monitoring system: Change properties, such as threshold values, of nodes that are provided with values by a CCMS agent; to display threshold values, use the corresponding technical view of the Alert Monitor 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 an alert should always trigger exactly one action for consistency reasons, central auto-reactions are performed only in the primary central monitoring system. Operating system data for dedicated database servers should be transferred using the CCMS agent SAPCCMSR to be able to display the data in the associated system using transactions ST06/OS07 and in the monitoring architecture. If this system is, in turn, part of a system landscape with a central monitoring system, you should make the following settings when registering 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 additional monitoring system In high availability solutions, you can define an additional monitoring system as a replacement for emergencies or maintenance periods, without having to restart or reregister the CCMS agents for these periods.
The possibility of defining multiple monitoring systems has the following advantages:
5.9.1
Start File CSMCONF with Multiple Central Monitoring Systems
For dialog-free registration with multiple central monitoring systems, extend the CSMCONF start file (see Alternative: Dialog-Free Registration of CCMS Agents [page 38]). The start file initially consists of the following four sections, which define properties and the users used by the central monitoring system:
CEN_CONFIG CEN_ADMIN_USER CEN_GATEWAY
SAP AG
CCMS Agents
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 the primary central monitoring system. For every additional monitoring system, create these four sections for the relevant system in the same way, however with the names CEN2, CEN3, ... instead of 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 are using multiple central monitoring systems, specify the system group to which the monitored system 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 and specify these on the Remote Monitoring Entry screen. You also enter the Target System ID of the system to be monitored. This is usually the system ID of the system (see SAPCCM4X: Creating the RFC Connections [page 45]). The monitoring architecture uses this target system ID to identify and differentiate between all monitored systems. It is possible that you want to monitor multiple systems with identical system IDs. This situation occurs in particular in very large IT landscapes or with outsourcing. In this case, nodes from different systems, but which are known by the same target system ID in the monitoring architecture, 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 case of multiple systems with an identical system ID. When doing this, you must only ensure that the first 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 central monitoring system using the unique target system ID. However, only the first three characters of the target system ID are used during access to the destination of the remote system (such as for data collection or to execute and analysis method). As these three characters are the threecharacter system ID, it is possible to read and process data in the remote system.
CCMS Agents
When transporting data back to the central system, the system ID is again supplemented by the target system ID known in the central system. The longer target system ID is always used in the central monitoring system.
To be able to monitor multiple systems with an identical system ID, the central monitoring system requires Support Package 16 for SAP Web Application Server 6.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 the desired 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 remote system. - 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 agent SAPCCMSR j2ee is registered with CEN using the Visual Administrator (see Installing 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 , as described 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 the SAPCCMSR.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 destinations DES1, DES2, and DES3. You can assign the following target system IDs: - PRDDES1: System PRD at destination DES1 - PRDDES2: System PRD at destination DES2 - PRDDES3: System PRD at destination DES3
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 to monitor an additional PRD system at the RFC destination DES5. In this case, you do not need
SAP AG
CCMS Agents
to change the target system ID of the first system; specify the following target system ID for the 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 the resources 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. A specified number of files are written in each component subdirectory. A new statistics file is started hourly. As soon as the maximum number of files has been reached, the system overwrites the 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 J2EE Engine 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 monitoring system CEN. You can display the data there in the Global Workload Monitor (aggregated data) and in the functional trace (unaggregated data).
SAP AG
January 15, 2007
CCMS Agents
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 Monitoring System

Depending on the CCMS agent, you can find the monitoring contexts in different places in the central monitoring system: SAPCCM4X As the SAP instance was already integrated into the central monitoring system before you installed the CCMS agent, the installation of the CCMS has no visible effect. However, the system now first attempts to use the CCMS agent to access data from the SAP instance. If you have activated the push technology of the CCMS agent, this method of data retrieval is better from a performance point of view. SAPCM3X The central monitoring system creates a monitoring segment SAP_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 CCMS Technical Expert Monitors in the monitor All Monitoring Contexts. SAPCCMSR The central monitoring system creates a monitoring segment SAP_CCMS_<Hostname>. By default, 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 Additional Functions 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 CCMS Technical Expert Monitors and in the monitor All Monitoring Contexts. SAPCCMSR j2ee
CCMS Agents
The Java monitoring data is displayed in the SAP J2EE Monitor Templates monitor set, sorted by 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 then access these monitors more quickly and more easily in the monitoring hierarchy. Data from the CCMS agents is already displayed by default in the following standard monitors of the monitoring 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 by the 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 performance point of view and more reliable. If the agent is shut down, the relevant data is transferred using a dialog work process again. The subtrees in the Alert Monitor that are created by the CCMS agent do not disappear immediately if the agent is shut down. Instead, they are displayed as obsolete 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 are shown; that is, unlike <Hostname>, they do not stand for a variable.
1. 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 an existing monitor set. 3. If you want to create a rule-based selection, place the cursor on the New Monitor line or on a virtual 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
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 Rule Nodes screen:
CCMS_GET_MONITORING_CONTEXT_NAMES
On the Edit Rule Nodes screen, specify the following selection parameters: - R3System = <CURRENT> - MoniSegment = SAP_CCMS_<host name>_local - MoniContext = <ALL> 7. Save your new monitor by choosing Save or Generate Monitor. The system prompts you to enter a name for your monitor. The monitor is then automatically saved. The new monitor is now 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 Monitor
1. 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 an existing monitor set. 3. If you want to create a rule-based selection, place the cursor on the New Monitor line or on a virtual 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: - R3System = <CURRENT> - MoniSegment = SAP_CCMS_<host name> 6. Repeat this procedure from point 3; but this time choose the following rule on the Edit Rule Nodes screen:
CCMS_GET_MONITORING_CONTEXT_NAMES
On the Edit Rule Nodes screen, specify the following selection parameters: - R3System = <CURRENT> - MoniSegment = SAP_CCMS_<host name> - MoniContext = <ALL>
CCMS Agents
7. Save your new monitor by choosing Save or Generate Monitor. The system prompts you to enter a name for your monitor. The monitor is then automatically saved. The new monitor is now 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 display data in the operating system monitor, as this data appears immediately in transactions ST06 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 is available to you for self-monitoring of the CCMS agents. Use this monitor to monitor the CCMS agents in your IT landscape. In addition to the RFC destination of the agent, the monitor provides the 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 )
-Node Display Off Selfmonitoring CCMS Agents
Name of the monitor
CEN\CCMS_Selfmonitoring\...\CCMS_Agents\... SAPCCMSR.Host1.99 Description Status Heartbeat Availability Agent Version Details SAPCCM4X.Host2.00 Description Status Heartbeat Availability Agent Version Details SAPCCM4X.Host2.00 controlling C11 C11_Host2_01 on Host2 Inactive since 17.02.2003, 23:18:48. Last test: 20.08.2001, 16:06:10 0 sec 0% Patch collection 2003/2, SAP Note 584136, CCMS version 20010925, 32 20.02.2003 16:36:20: Agent calls as [BCE:000:CSMREG], RFC_PING ok
Single agent
Information about the agent
SAPCCMSR.Host1.99 controlling CEN Host1 on Host1 active since 18.02.2003, 10:04:58. Last test: 20.08.2001, 16:06:09 3221 sec 100 % Patch collection 2003/2, SAP Note 584136, CCMS version 20010925, 32 20.02.2003 16:36:20: Agent calls as [BCE:000:CSMREG], RFC_PING ok
SAP AG
January 15, 2007
CCMS Agents
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 the subtree 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 (CsmTaskCcmsAgent.Text) Status (CsmTaskCcmsAgent.Status) Heartbeat (CsmTaskCcmsAgent.Heartbeat) Availability (CsmTaskCcmsAgent.Availability) Agent Version (CsmTaskCcmsAgent.Version)
Description
Information about which application server on which host is monitored by the agent
Information about whether the agent is active or inactive and how long it has been in that state Time since the last test of whether the agent is still active; if the agent is inactive, this attribute contains the value 0
sec
Percentage of the time in which the agent is active (by default in the last 15 minutes; you can change the time period in the Properties of the MTE class) Static information about the agent used; corresponds to the following entries when V is displayed (see Displaying the Version of a CCMS Agent [page 104]):
CCMS version systemid relno Patch text
Details (CsmTaskCcmsAgent.Details)
Information about the central monitoring system user to which the agent sends data and alerts as an RFC client; also the current status of the RFC connection used to do this
6.4. Displaying Agent Data in the Topology Display 6.4.1 Calling the Display of Agent Data in the Topology Display
You can use the topology display to obtain an overview of the CCMS agents that are registered for your local system. To do this, follow the procedure below:
SAP AG
January 15, 2007
CCMS Agents
1. From the SAP Easy Access Menu, choose Tools CCMS Configuration Alert Monitor, or call transaction RZ21. 2. In the Topology group box, choose one of the following radio buttons: Radio Button Agents for Local System Agents for Remote Systems Agents for 3.x Systems Agent Type SAPCCMSR SAPCCM4X SAPCCMSR j2ee SAPCM3X
3. Choose the Display Overview pushbuttons (these pushbuttons and radio buttons are available to you as of SAP Web AS 6.20. In SAP Web AS 6.10, choose Technical Infrastructure Display 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 for Remote Systems are registered with the local system as the central monitoring system). If you require the corresponding data for remote systems, first choose System Overview (SAP Web AS 6.10: Monitored Remote SAP Systems tab page) and choose the desired system by double clicking it.
6.4.2
Column System
Data Displayed About CCMS Agents

Meaning System ID of the monitored system (this column is only displayed for agents for remote SAP systems) Name of the monitoring segment with which the agent connects; it has the name structure SAP_CCMS_<Name of the SAP Instance> or SAP_CCMS_<Host Name> for agents for the local system.
By default, the system displays the following columns in the tab pages for the CCMS agents:
Segment Name
If you are monitoring J2EE Engines using SAPCCMSR with Option j2ee [page 10], the normal naming convention would be for both the ABAP and the Java segment of the instance of a SAP Web Application Server to have the same segment name. 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
SAP AG
January 15, 2007
CCMS Agents
Column Comm.Status or Segment Status
Meaning Status of the monitoring segment or communication status from the point of view of the local system. The possibilities for status are: ONLINE OFFLINE SHUTDOWN COMM.FAIL
If an RFC call fails (for example, in the case of the Test Connection command), the system displays COMM.FAIL. After a successful RFC call, the system sets the status to ONLINE again. Changed By Changed On Changed At Responsible Server Last user to change the communication status Date and time of the last change to the communication status Instance that performs the internal administration tasks to control the CCMS agent. It is first the instance with which the agent registered. In running operation, another instance automatically takes over this task if the original instance is no longer available. This column can also have the entry REMOTE SYSTEM when Registering with Multiple Central Monitoring Systems [page 89]. This shows that the CCMS agent is registered with the local system, but another system is the primary monitoring system. Note that directly after the registration of a CCMS agent, the entry REMOTE SYSTEM is only displayed after the first run of a synchronization job after a maximum of an hour.
With the CCMS agent SAPCCM4X (tab page Agents for Remote SAP Systems), these administrative tasks are performed instance-independently by jobs. Therefore, the column title is Responsible System in this case. J2EE Customizing Destination This column contains an RFC destination to the J2EE Engine that the agent is monitoring. This destination is used to transfer property changes for nodes of this agent from the Alert Monitor directly to the J2EE Engine (see Creating Customizing Destination for SAPCCMSR j2ee [page 43]). This column is only relevant for the agent SAPCCMSR with the j2ee Option; for all other agents, n/a is entered here.
SAP AG
January 15, 2007
CCMS Agents
6.4.3
Commands in the Topology Display
In addition to the purely display functions, the following commands are also available to you as pushbuttons in the ALV Grid Control. These commands are only available for the local system: Command Test Connection Description This command performs an RFC call to the selected agent and displays the result. If the RFC call is not successful, the system sets the status to SHUTDOWN; if the call is successful, the system sets the status to ONLINE.
Working Directory You can display all files in the working directory of the agent. To do this, select the desired agent and then choose this pushbutton. The of the Agent system 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 Component Repository. This function should not replace the deregistration with the agent itself (see Controlling the CCMS Agents [page 102]), since, for example, Deregister Agent does not stop the agent. Instead, use this function primarily to remove incorrect entries and inconsistencies after changes to the system landscape.
This command is only available in change mode, which you start by choosing the Display Change pushbutton ( ). Self-monitoring of the Agents Agent Registration Adopt Agent (change mode) Adopt All Agents (change mode) Switches directly to the Self-Monitoring of the CCMS Agents [page 96] Monitor; this monitor contains the most important data for monitoring the CCMS agents in your IT landscape Specifies the central monitoring system with which the CCMS agent is registered Defines the local system as the primary monitoring system for the selected CCMS agent; the previous primary system then becomes the secondary system Defines the local system as the primary monitoring system for all CCMS agents that are registered with the local system. The previous primary systems then become secondary systems (the button is in the toolbar at the top of the screen, since this command applies for all agents, irrespective of the selected tab page)
SAP AG
January 15, 2007
CCMS Agents
Command Change Comm.Status or Segment Status (change mode)
Description If you no longer want to display the data from the agent in the monitoring architecture, choose OFFLINE. It remains in this status until you set it to ONLINE again. Do not set COMM.FAIL or SHUTDOWN manually.
The buttons Agent Registration, Adopt Agent, and Adopt All Agents are only displayed if there are agents that are registered with multiple central monitoring systems. You should also ensure that the functions to switch the primary system are performed in the agent itself. This can take a few seconds. Then refresh the display until the changes are visible in the display.
SAP AG
January 15, 2007
CCMS Agents
7.
Controlling the CCMS Agents
The following commands are available to you to control the CCMS agents directly from the operating system input prompt: Command
-R [-f <start file>] [pf=<profile path>] -U [pf=<profile path>] -DCCMS [pf=<profile path>] -stop [pf=<profile path>] -status [pf=<profile path>] -noservice -V
Description Registering the agent (see Registering the CCMS Agents [page 32]) Deregistering the agent Starting the agent Stopping the agent Displaying the status of the agent Registering and deregistering without installing or uninstalling a service (Microsoft Windows only) Displaying the version of the agent
You can display the list of available commands at any time by entering the name of the agent without 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 during registration, specify this path during deregistration too: CCMS Agent SAPCCMSR SAPCCM4X SAPCM3X Deregistration Command
sapccmsr U [pf=<profile path>] sapccm4x U sapcm3x pf=<profile path>
U [pf=<profile path>]
As of Patch Collection 13, the start file CSMCONF is deleted during the deregistration. If the central monitoring system (CEN) with which the agent is registered has a release status of at least SAP 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 topology display using transaction RZ21; in the Topology group box there, choose one of the radio buttons that display the CCMS agents registered with this system) RFC connections to the agent (Check using transaction SM59)
SAP AG
January 15, 2007
CCMS Agents
Entry in the System Component Repository (SCR); you can display the SCR by choosing Technical 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 the system.
7.2. Starting and Stopping CCMS Agents

You should always stop and restart a CCMS agent if you have made changes to its SAPCCMSR.INI configuration file (see SAPCCMSR.INI: Configuration File for the CCMS Agents [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 to upgrade the corresponding monitored system. Restart the agents again after finishing the 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 command sapccmsr 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 stopping and 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 the commands -R (register agent) and -U (deregister agent) to prevent the associated service being installed during registration or uninstalled during deregistration. This option is available as of Patch Collection 2005/5. It is primarily useful, if you need to register or deregister an agent using a user that does not have administrator authorization on the relevant 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 the agent is running, you receive additional information about the release of the central monitoring
CCMS Agents
system in which the agent is registered. To do this, call the agent with the option status (for example, with the agent SAPCCMSR):
>sapccmsr status INFO: CCMS agent sapccmsr working directory is /usr/sap/tmp/sapccmsr INFO: CCMS agent sapccmsr config file is /usr/sap/tmp/sapccmsr/csmconf INFO: 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-Unicode compiled at Sep 17,2002 systemid 560 (PC with Windows NT) relno 6200 Patch text patch collection 2003/2, OSS note 584136 patchno 344 intno 20023800 running 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). The line 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 contains which changes, see SAP Note 202591.
SAP AG
January 15, 2007
CCMS Agents
8.
Questions and Answers
SAP has possible solutions to the following errors that can occur when you are using the CCMS agents:
8.1. General
Logon to the central monitoring system does not work during registration of the agent.
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 do this, use the test program SAPINFO, which is part of the Remote Function Call Development Kit (RFC SDK). This package is on every presentation CD. You can use this program to check the connection to the central monitoring system without logon and password (see also SAP Note 42692).
The agent registers error-free as a service. However, the service does not start or terminates immediately (Microsoft Windows NT or Windows 2000).
A service under Microsoft Windows NT or Windows 2000 always starts in the System32 directory. So that the system can find any existing profile files, you must always specify these with a full path. Deregister the service (for example, with sapccm4x U), and reregister it, specifying the profile with the complete path.
Although a template for log file monitoring exists and is entered in SAPCCMSR.INI, the system does not display any subtrees for log files in transaction RZ20 of the central system.
You must end the LOGFILE_TEMPLATE with a period (.). The line containing the period must contain no other characters. You should also check in the log file of the agent which files it is actually monitoring.
During the installation of the SAPCCMSR agent, you receive an error message saying 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 and have released the directory saploc, before you install SAPCCMSR.
CCMS Agents
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 central system. 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 (Microsoft Windows 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 \\<host>\saploc\prfclog\sapccmsr C:\usr\sap\prfclog\sapccmsr (sap must be released as the share saploc)
Under Microsoft Windows: Example (Microsoft Windows NT):
SAP AG
January 15, 2007
CCMS Agents
8.3. SAPCCMSR j2ee

Notes:
Symptom: Monitoring data for a J2EE Engine are visible in the VA, but not in the CCMS
The connection test is performed as follows: Call transaction RZ21 in CEN, 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 Working Directory button and then choose sapccmsr.log by double-clicking it. Pay particular attention to errors connected to Gateway and RFC.
Connection test OK? yes
no
On host: is process running? yes
no
Analysis in CEN: Log file sapccmsr.log
Analysis on the Host: Log file sapccmsr.log
Start the Process UNIX: sapccmsr DCCMS Windows: Start the service
Problem identified? yes Solve problem
no
Problem solved? Deregister and reregister the agent sapccmsr -U / sapccmsr -R yes
no
OK
SAP AG
January 15, 2007
CCMS Agents
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 the following 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 05.04.2002 Available 05.04.2002 Available 05.04.2002 Unavailable 05.04.2002 Unavailable 05.04.2002 Available 05.04.2002 Available 05.04.2002 uw1042_C11_01, agent not attached 10:50:14 - 05.04.2002 10:50:55 uw1042_ C11_01, agent not attached 10:51:05 - 05.04.2002 10:51:05 uw1042_ C11_01, agent attached to key 13 (pool 10) 10:51:25 - 05.04.2002 10:52:46 uw1042_ C11_01, agent attached to key 13 (pool 10) 10:52:56 - 05.04.2002 10:52:56 uw1042_ C11_01, agent not attached 10:53:18 - 05.04.2002 10:56:19 uw1042_ C11_01, agent not attached 10:56:29 - 05.04.2002 10:56:29 uw1042_ C11_01, agent attached to key 13 (pool 10) 10:56:50 - 05.04.2002 11:16:20
SAP AG
January 15, 2007
CCMS Agents
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, you require a valid password for the SAP Service Marketplace For more information, see: [Support] Supportability Setup Guide for SAP NetWeaver 04 SP Stack 04 Start the SAP Service Marketplace, and go to the SAP NetWeaver 04 Operations area (http://service.sap.com/nw04operation). Choose the document Supportability Setup Guide - SAP NetWeaver 04 Stack 04 from the list. [Tutor] Installation, Registration, and Customizing of CCMS Agents Start the SAP Service Marketplace, and go to the System Monitoring and Alert Management area (http://service.sap.com/monitoring). Choose Education & Workshops, and then choose Installation, Registration, and Customizing of CCMS Agents from the list (Direct Link). [SAPOsCol] SAPOSCOL: Properties, Installation, and Operation Start the SAP Service Marketplace, and go to the System Monitoring and Alert Management 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 Monitor Start the SAP Service Marketplace, and go to the System Monitoring and Alert Management area (http://service.sap.com/monitoring). Choose Media Library Documentation, and then choose Predefined Auto-Reactions for the Alert Monitor from the list (Direct Link). [AlMon] Online documentation for the Alert Monitor To view this documentation, call the SAP Library and choose SAP NetWeaver Solution Life Cycle Management Solution Monitoring Monitoring in the CCMS The Alert Monitor. [StdMon] Predefined Monitors for the Alert Monitor Start the SAP Service Marketplace, and go to the System Monitoring and Alert Management area (http://service.sap.com/monitoring). Choose Media Library
SAP AG
January 15, 2007
CCMS Agents
Documentation, and choose the document Predefined Monitors from the list (Direct Link).
[Avail] Availability Monitoring and CCMSPING Start the SAP Service Marketplace, and go to the System Monitoring and Alert Management area (http://service.sap.com/monitoring). Choose Media Library Documentation, and choose the document Availability Monitoring and CCMSPING (Direct Link). [JMon] Java Monitoring API Properties and Installation Start the SAP Service Marketplace, and go to the System Monitoring and Alert Management area (http://service.sap.com/monitoring). Choose Developers Zone, and choose the document Java Monitoring API Properties and Installation (Direct Link). [GRMG] Instrumenting Components for Monitoring with GRMG Start the SAP Service Marketplace, and go to the System Monitoring and Alert Management area (http://service.sap.com/monitoring). Choose Developers Zone, and choose the document Instrumenting Components for Monitoring with GRMG (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 or does not provide enough information. Use the test tool sapinfo described in this SAP Note for testing. 135503 CCMS Monitoring Architecture: Meaning of profile parameters The profile parameters of the monitoring architecture are explained in this SAP Note. 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 the various patch collections. 209834 CCMS agent technology (composite SAP Note) This SAP Note contains, in addition to basic information about the CCMS agents, known problems that can occur in connection with the CCMS agents, and their solutions.
SAP AG
January 15, 2007
CCMS Agents
212876
The new archiving tool SAPCAR This SAP Note explains the operation of the archiving tool SAPCAR, with which the SAP Service Marketplace files are compressed.
308061
CCMS monitoring architecture: monitor 3x systems The CCMS monitoring architecture is available as of SAP Basis 4.0B. However, you can also monitor systems as of SAP Basis 3.0D using the monitoring architecture. This SAP Note explains the procedure required to do this.
322075
Installing the CCMS agent sapccm4x fails This SAP Note shows how you can solve a possible problem (error during the interaction of the semaphores between the agent and the application server) during the installation of the CCMS agent SAPCCM4X on application servers up to SAP Basis 4.6C.
371023
OS07/ST06: Monitoring of operating system data Operating system data of (any) server is to be collected with the operating system collector SAPOSCOL and reported in the CCMS monitoring architecture or displayed in transactions ST06/OS07. This SAP Note describes the prerequisites for this.
420213
Composite SAP Note: Central monitoring of mySAP.com components This SAP Note provides current information about monitoring mySAP.com components that are not described in the standard documentation (see SAP Service 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 the monitoring architecture in the context of the central monitoring of mySAP.com components. The auto-reaction methods are not started in the system, in which the alert occurs, but rather in the central monitoring system. In this way, it is possible for reactions to events that occur in monitored components to be performed immediately in a central location. This SAP Note describes the prerequisites for this scenario.
498179
Enable Monitoring of InQMy/SAP J2EE Engine You want to include the SAP J2EE Engine in the CCMS monitoring architecture. This SAP Note shows how you can do this with the SAPCCMSR agent.
502461
CRM: CCMS agent PlugIn for IPC You want to include the IPC Server component in the CCMS monitoring architecture. This SAP Note shows how you can do this with the SAPCCMSR agent and the appropriate PlugIn.
SAP AG
January 15, 2007
CCMS Agents
535199
CCMS agents: Monitoring log files In the context of monitoring systems and system landscapes, you can use CCMS agents to monitor log files; that is, to search through certain files for one or more word patterns. If a search pattern is found, the monitoring architecture displays a message or an alert. This SAP Note explains the configuration required 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 you can 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 operating system 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 the patch 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 patch collections from 2004.
704349
Activating the CCMS monitoring for TREX TREX can provide monitoring data for the CCMS using the agent technology. To do this, the CCMS agent SAPCCMSR and the operating system collector SAPOSCOL must be installed and configured on the TREX host. This SAP Note describes the steps on the TREX host.
730629
CCMS agents: Java interface for registration You want to register the CCMS agent SAPCCMSR. The monitored object can be an instance of a J2EE Engine with a release status of SAP Web AS 6.20 or a host on which SAP standalone components/non-SAP components (such as a database) are running. During the registration of the agent, you must enter a large amount of information about the CEN, the connection to it, and, if appropriate, the monitored J2EE instance. This SAP Note contains, as an attachment, a Java tool to simplify the registration.
734247
Registering CCMS agents for SAP Web AS Java as of 6.30 You want to register the CCMS agent SAPCCMSR, to centrally monitor an instance of a J2EE Engine as of SAP Web AS 6.30 using a central monitoring system (CEN) as of SAP Web AS 6.40 SP 1.
SAP AG
January 15, 2007
CCMS Agents
During the registration of the agent, you must enter a large amount of data about the CEN, the connection to it, and the monitored J2EE instance. This SAP Note contains, as an attachment, a Java tool to simplify the registration. 809007 CCMS Agents and Kernel: Patches 2005 This SAP Note describes the changes to the monitoring architecture through the patch collections during 2005. 817714 Agent registration not possible with visual administrator This SAP Note describes the manual installation of CCMS agents for a SAP NetWeaver J2EE instance or an ABAP+J2EE instance (double-stack) if it is not possible 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. The CCMS agent is displayed as ONLINE in transaction RZ21, and provides data for OS monitoring and log file monitoring. However, no monitoring data is displayed for the J2EE Engine. 914721 CCMS Agents and Kernel: Patches 2006 This SAP Note describes the changes to the monitoring architecture through the patch collections during 2006. 929635 CCMS Agent Configuration tab page is missing Automatic registration of the CCMS agent from the Visual Administrator is not possible, since the CCMS Agent Configuration tab page in the Monitoring service of the dispatcher is not displayed. This problem can occur with the following 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 to which the following copyright statement applies:
Various copyrights apply to this package, listed in 3 separate parts below. Please make sure that you read all the parts. 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 the copyright on behalf of the wider Net-SNMP community, covering all derivative work done since then. An additional copyright section has been added as Part 3 below also under a BSD license for the work contributed by Cambridge Broadband 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 of contributors can be found in the README file under the THANKS section.
CCMS Agents
---- 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 is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of CMU and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission. CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT 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 LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, 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 the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer 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 to endorse 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 ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE 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 BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ---- 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 the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
SAP AG
CCMS Agents
The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER 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 BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
SAP AG
January 15, 2007

CCMS Agents

Transféré par

Informations du document

Description originale:

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

CCMS Agents

Transféré par

Droits d'auteur :

Formats disponibles

CCMS Agents

Version 4.7 (Patch Collection 2006/5) September 20, 2007

CCMS Agents: Features, Installation, and Operation

SAP AG Neurottstr. 16 D-69190 Walldorf

CCMS Agents: Features, Installation, and Operation Page 2 of 115

January 15, 2007

4.4.4 SAPCCMSR.INI: Configuration File for the CCMS Agents....................................... 29

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

4.5.1 4.5.2 4.5.3 4.5.4 4.5.5

4.5.6 Registering SAPCCMS with the Option -j2ee ............................................................. 41

5.1.3 Example Log File Templates........................................................................................ 57

5.7. 5.8. 5.9. 5.10. 5.11. 6. 6.1. 6.2.

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

CCMS Agents: Features, Installation, and Operation Page 6 of 115

January 15, 2007

Structure and Use of this Document

CCMS Agents: Features, Installation, and Operation Page 7 of 115

January 15, 2007

CCMS Agents: Features, Installation, and Operation Page 8 of 115

January 15, 2007

Functional Principle of the CCMS Agents

Log SAPCCMSR DLL Application

CCMS Agents: Features, Installation, and Operation Page 9 of 115

January 15, 2007

2.2. SAPCCMSR with Option j2ee

CCMS Agents: Features, Installation, and Operation Page 10 of 115

January 15, 2007

Monitored System ABC (with no ABAP Engines)

Central Monitoring System CEN

CEN is the primary central system in each case

Monitored System with J2EE and ABAP Instances

CCMS Agents: Features, Installation, and Operation Page 11 of 115

January 15, 2007

Monitored System with Java and ABAP Instances, and a CEN

HostA_ABC_33 HostB_ABC_33 HostC_ABC_33

Agents for the Local SAP System ABC

Primary Central System

Secondary Central System

Central Monitoring System CEN

SAP R/3 4.X Instance Dispatcher

RZ20 Central Monitoring System

CCMS Agents: Features, Installation, and Operation Page 14 of 115

January 15, 2007

Installing CCMS Agents for NetWeaver Components

All Possible Central Monitoring Scenarios with CCMS Agents

Central Monitoring System

SAP NetWeaver 04 Dual Stack

SAP NetWeaver 04 Java standalone

CCMS Agents: Features, Installation, and Operation Page 15 of 115

January 15, 2007

3.1. Installing an Agent on an ABAP Instance

CCMS Agents: Features, Installation, and Operation Page 17 of 115

January 15, 2007

<profile path> specifies the instance profile of the monitored instance. By

default, this is: Windows: [drive]:\usr\sap\<SysID>\SYS\profile\

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

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

CCMS Agents: Features, Installation, and Operation Page 19 of 115

January 15, 2007

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

CCMS Agents: Features, Installation, and Operation Page 20 of 115

January 15, 2007

What is the version of the SAPCCMSR CCMS agent?