You are on page 1of 115

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

................................5................ 5........................ 38 4...3....................... 50 Monitoring Log Files.. and Operation Page 4 of 115 January 15..............4 4..............................................58 5....5.....6..............................................................................................................6 Registering SAPCCMS with the Option -j2ee ..............1.................................................... 53 5..............4 Display for Log File Monitoring in the Alert Monitor ................. 49 5......................................1..........5 Creating the CSMREG User............47 4..........................3 Trace Files .........3 Search Pattern to be Output in the Monitored Log Files ............1......................... 47 4..... Installation...2 Adjusting the Configuration File for Receiving SNMP Traps ................................................61 5....59 5.2 Structure of the Log File Template of the Log File Agent ...........................................1 Adjusting the Configuration File for Sending SNMP Traps ..... 48 4.........................................2...........................2 Example CSMCONF Start File ......................................2 Log Files .......................42 4......................................1 General Settings for the Monitored Log Files .......5. Working Directory and Log Files of the CCMS Agents....51 5.........6..................1 Structure of the CSMCONF Start File........ 51 5........................1 Registering SAPCCMS with the Option -j2ee in Dialog .2 4............... 2007 ..2...................5....3 Log File of the SAPCCMSR CCMS Agent ...................... 35 Alternative: Dialog-Free Registration of CCMS Agents.42 4......5..................................53 5.................................................................63 5..........................................................2 Monitored Search Pattern in the Monitored Log Files ................................ 45 4.......... 33 Automatically Creating the CSMCONF Start File..41 4..............................................CCMS Agents 4...3.............3 Creating Customizing Destination for SAPCCMSR –j2ee .........1 Types of Monitored Log Files .5......5..2.2....................................................................3 Example Log File Templates.......6......................5...........................6....................................5............6...........................2 Trace Files of the SAP Work Processes ......................................4 Log File for the Backups of an Oracle Database ............2................5...... 68 SAP AG CCMS Agents: Features..................... 34 Registration with the Agent Registration Tool ............. 41 4.1.......1............................2 Dialog-Free Registration of SAPCCMS with the Option -j2ee..................................................1.................................3........5........................................................................ 57 5............7 Starting the Agent ................38 4....6....................1.............................1...........................................8 SAPCCM4X: Creating the RFC Connections...............58 5..............6...........5..........1.............................................................................1......2.5...........................................3..... 64 5...................... 67 5........................................................... Advanced Functions of the CCMS Agents .....1................................................... 34 Registering the CCMS Agents in Dialog...56 5..... 45 4.........................................2...................5.......3 Displaying Received SNMP Traps in the Alert Monitor..5.............1 Working Directory.............1 Oracle Alert Log ...............................1 4.. Setting Up the Sending and Receiving of SNMP Traps Using CCMS Agents.................. 61 5..........................3 4......1............................................56 5...43 4.

.................69 5........ 87 5.......................................2 Data Displayed About CCMS Agents .......1 SAPCM3X: Creating a Rule-Based Monitor ........3 Commands in the Topology Display .............93 Creating CCMS Agent Monitors in the Central Monitoring System ............................................................................................94 6.................8...............................................75 5....... 73 5...3...4................2 Structure of the Alert Log File.5.INI). Installation.... Displaying File Contents in the Alert Monitor...............................88 Registering with Multiple Central Monitoring Systems ....6....................92 Displaying Agent Data in the Central Monitoring System ............................................................. 76 Structure of the SAPOSCOL Filter File oscolfile.......2.3..2....5..............90 Transferring Distributed Statistics Records with CCMS Agents.........................................6.............................9......................................................................................................1 Activating the Alert Logging................. Event Log Monitoring with CCMS Agents...... 81 5.2 SAPCCMSR: Creating a Rule-Based Monitor.................. 71 5...... 86 5................1 Example of Defining Displayable File Contents (SAPCCMSR.......................... 102 CCMS Agents: Features...........1....97 6........ 89 Monitoring Multiple Systems with an Identical System ID..........1 5................ 5.. 94 6................ SAP AG Controlling the CCMS Agents ....... and Operation Page 5 of 115 January 15.................................3.................................4...1 Structure of the Event Log Template..................4...... 77 Example SAPOSCOL Filter File oscolfile......................................9....txt................2. 76 Configuring the Monitoring of Operating System Data ...................................................................89 5.................................................88 Including Additional Functions in CCMS Agents .............. 85 5..............................................................7................2 5................... 5...4.......................................5 Operating System Data Displayed in the Alert Monitor .................... 95 6......... 87 5..4 5........4................4............................................86 5........ 6................txt ....... Self-Monitoring of the CCMS Agents ......10..........6.................................................3 5...............................CCMS Agents 5.... 79 Monitoring Selected Processes .................1 Calling the Display of Agent Data in the Topology Display.................... 6... 85 5............ 6............ 100 7..................................................................... 5.. 97 6............. Alert Logging for CCMS Agents ... Monitoring Operating System Data with CCMS Agents .............3..................2 Displaying the Event Log Monitoring in the Alert Monitor.........4.................96 Displaying Agent Data in the Topology Display ......................... 6.....................1 Start File CSMCONF with Multiple Central Monitoring Systems ................4.......................................................... 5..............................................3 Example Alert Log File ..................5................................................................... 2007 ...11..........2 Assigning the Required Analysis Method . 93 Monitoring Contexts of the CCMS Agents in the Monitoring System .....4................ Transferring GRMG Customizing Files to CEN.. 98 6..............................4......84 5..........................................................5...................

..................................................................... 9.............................................3..... 8.......................... Deregistering CCMS Agents.............4... 105 General ..............105 SAPCCMSR/SAPCM3X ........ 8..... 7............CCMS Agents 7........... 9..........................2..............................................................103 Displaying the Version of a CCMS Agent .............................3......................................1............................ 7..........109 Important SAP Notes About CCMS Agents .............. and Operation Page 6 of 115 January 15.............................1......106 SAPCCMSR –j2ee ..................................... 2007 ...................................................................................................102 Starting and Stopping CCMS Agents.................................................2.....1......... 7..........................................................................................................................2........................104 Questions and Answers ...............................................110 Copyright.......4..................................................... Installation...............113 SAP AG CCMS Agents: Features....................107 SAPCCM4X ...............108 Additional Information...................................................... 9............................... 9....................... 8.... 109 SAP Service Marketplace and SAP Library............ 8................................................................................................... 8.....103 Displaying the Status of a CCMS Agent..3.............................

Section 7 This section contains the functions for controlling CCMS agents locally. It also introduces the most important functions for monitoring and controlling CCMS agents from CEN. you should work through this section if you want to individually tailor the advanced functions of the CCMS agents. since the procedures in section 3 will be sufficient. and Operation Page 7 of 115 January 15.CCMS Agents 0. the monitoring of log files. you will not require this information. Installation. Section 5 This section describes how you can use the advanced functions of the CCMS agents for your individual monitoring tasks. SAP AG CCMS Agents: Features. for example. since many of the advanced functions of the CCMS agents (section 5) have a direct influence on the installation and registration of the agents. Section 3 This section contains the installation and registration of CCMS agents for the most important monitored components. In most cases. Section 4 This section describes the installation and registration of CCMS agents in general terms. or displaying the contents of files. monitoring processes. These include. Section 6 This section describes how monitoring information that is transferred to the central monitoring system CEN using CCMS agents is displayed in CEN. 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. follow the procedures in this section. If you want to use CCMS agents to monitor software components in the context of a standard installation. Section 9 This section contains the most important additional information about CCMS agents. 2007 . Section 8 This section contains a summary of possible problems and their solutions in the context of CCMS agents. sending and receiving SNMP traps. However.

Installation.CCMS Agents 1. 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. see [SAPOsCol]. For detailed information about it. in the case of an SAP instance Using the CCMS agent. Agents monitor network data. 2007 . see [AutoRea]. The actual monitoring is performed using the operating system collector SAPOSCOL. including: . 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.Network metrics. 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. Introduction The monitoring architecture provides an infrastructure for monitoring your IT environment and its components. such as an interface or Domain Name System (DNS) . You can monitor processes at operating system level. by using the push technology Connect to a shared memory segment without requiring a free work process You can monitor any log files. 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. For detailed information about it. They therefore allow you to: • • • • • • • Include SAP components that do not have an ABAP interface. 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 CCMS Agents: Features. and Operation Page 8 of 115 January 15.The configuration of the network environment.

A CCMS agent always uses exactly one monitoring segment that is either in its local process memory or in the local shared memory.6B. SAPCCMSR This agent monitors components on which there is no active SAP instance (such as log files. stand-alone databases. the agent creates it. Installation.1.CCMS Agents 2. and Operation Page 9 of 115 January 15. SAPCCMSR always works in a shared memory segment that is independent of running SAP systems. If this segment does not yet exist. the CCMS agent SAPCCMSR attempts to attach itself to a monitoring segment in shared memory when it is started. or operating system components). 2007 . Any Instance (SAP/Non-SAP) SAPOSCOL Shared Memory Central Monitoring System RZ20 Application Log SAPCCMSR DLL Application SAP AG CCMS Agents: Features. The central monitoring system must have a release status of at least SAP Basis 4. SAPCCMSR is closely connected with the monitoring central monitoring system. After its installation. TREX. 2. Functional Principle of the CCMS Agents The runtime information for the monitoring objects is stored in monitoring segments.

and Operation Page 10 of 115 January 15. The SAPCCMSR agent with the -j2ee option exists for this purpose. but simply a number of associated components that have a common system name. 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. When monitoring. it must be possible that the monitoring segment of the SAPCCMSR agent does not belong to the central monitoring system. it should also be possible to monitor all instances with the same system ID locally as one system unit. 2007 . you need a central monitoring system as of SAP Web AS 6. if all of these parts are combined under one system ID. a Java instance should not be different from an ABAP instance. To use SAPCCMSR with option j2ee.2.2.1 Examples Monitored System with no ABAP Instances SAPCCMSR monitors an instance of a Java system and registers itself with a central system CEN.CCMS Agents 2. 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]). The connection to CEN is also the primary RFC connection.1. SAPCCMSR with Option j2ee The functional principle of SAPCCMSR has been extended in case the SAPCCMSR CCMS agent is monitoring a J2EE Engine. Combinations of ABAP instances and Java instances can also create a system. As far as possible. SAP AG CCMS Agents: Features.30 Support Package 4. 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. This is achieved by extending the system term to include Java components (such as J2EE Cluster). In a case of this type. The monitored J2EE Instance requires at least SAP Web AS 6.1 2. 2.40 Support Package 1.2. Installation.

and Operation Page 11 of 115 January 15.HostB.1. so that the system can be monitored locally as one unit.2.HostA.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.HostC.33 SAPCCMSR. In this case. 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 primäre RFC-Verbindung -j2ee sapccmsr primäre RFC-Verbindung -j2ee Primary central system CCMS Alert Monitor ABC HostA_ABC_33 HostB_ABC_33 HostC_ABC_33 Topology Display Agents for Local SAP System ABC Destination SAPCCMSR.33 SAPCCMSR.HostB. 2007 . Installation.33 Segment Name SAP_CCMS_HostA_ABC_33_X SAP_CCMS_HostB_ABC_33_X SAP_CCMS_HostC_ABC_33_X SAP AG CCMS Agents: Features.HostC.33 SAPCCMSR.33 SAPCCMSR.HostA. the agent must be primarily registered with the local system.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.33 CEN is the primary central system in each case 2.

HostB.3.6C.33 Central Monitoring System CEN 2. This agent provides an alternative connection route to the monitoring information in the shared memory of an ABAP instance.33 SAPCCMSR. the local system.HostA.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 ABC HostA_ABC_33 HostB_ABC_33 HostC_ABC_33 Secondary Central System Topology Display Agents for Remote SAP Systems System ABC ABC ABC Destination SAPCCMSR.33 SAPCCMSR. 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 primäre RFC-Verbindung -j2ee sapccmsr primäre RFC-Verbindung -j2ee CCMS Topology Display HostA_ABC_33 HostB_ABC_33 HostC_ABC_33 Agents for the Local SAP System ABC Destination SAPCCMSR.33 SAPCCMSR.1.2. 2007 .33 SAPCCMSR. and a CEN In addition to the case described above. This means that they have their own monitoring segment in the shared memory area of the running system. SAPCCM4X This agent improves the monitoring of ABAP instances with SAP Basis 4. Installation. the access method is independent of error states of the SAP instance and is therefore more robust. to which the Java instance belongs.CCMS Agents 2.X or higher.3 Monitored System with Java and ABAP Instances. The central monitoring system must have a release status of at least SAP Basis 4. Systems as of SAP Basis 4.HostC.HostC. As this alternative connection method does not require a free work process. After its installation.HostB. SAP AG CCMS Agents: Features. and Operation Page 12 of 115 January 15.0 have their own CCMS monitoring architecture runtime environment. the SAPCCM4X agent attempts to attach itself to and to work with this monitoring segment in shared memory when it is started.HostA.

SAP R/3 4.X through the CCMS monitoring architecture. to avoid interfering with the shared memory management in the restarting system. 2007 . if the monitored system is not running). SAP AG CCMS Agents: Features.CCMS Agents If this segment does not exist (that is. SAPCCM4X constantly checks whether the monitored system is active again. Installation. you still continue to need the standard RFC connection anyway. 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. as previously (for more information. SAPCM3X This agent allows the monitoring of SAP instances with SAP Basis 3. the agent does not create it. 2. works with the monitoring segment in the shared memory again. SAPCM3X therefore works always works with a monitoring segment that it creates in its main memory (for more information.4. These systems do not have their own CCMS monitoring architecture runtime environment. after synchronization. and when it is. and Operation Page 13 of 115 January 15.5. In this case. Communication A CCMS agent communicates with the central monitoring system using RFC. The central monitoring system automatically first attempts to read data from the monitored system through the RFC destination of the CCMS agent. see SAP Note 322075). see SAP Note 308061). Note that even if you are using the SAPCCM4X agent.X Instance Dispatcher RZ20 Central Monitoring System RZ20 SAPCCM4X Shared Memory 2. the system reads the monitoring data from the monitored SAP instance using the standard RFC. If the agent is not active.

CCMS Agents • As an RFC server. call transaction RZ20. As of SAP Web AS 6. the agents also automatically report monitoring attribute values.10 for automatic reporting of alerts. 2007 . select a node in the desired monitor. for example. The central monitoring system must have a release status of at least SAP Web AS 6. This access is. and Operation Page 14 of 115 January 15. As of this release. 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. All CCMS agents can process several tasks simultaneously (multi-thread procedure). used in transaction RZ20. it provides access to the data in the monitoring segment. The maximum frequency of this query depends on whether the underlying program is an ABAP program or a C program. on the Methods tab page. while the maximum frequency for C programs (and therefore for CCMS agents) is one minute. This improves performance as the central monitoring system then no longer needs to periodically query the agents.20. Installation. In the case of ABAP programs. activation of the push technology is mandatory. 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 CCMS Agents: Features. it independently sends alerts and values for the monitoring attributes to the central monitoring SAP System (push technology). You can set the frequency of the query by the monitoring architecture in the Alert Monitor. choose Properties and. To do this. • As an RFC client. the maximum frequency is five minutes. The agent automatically creates the local configuration files and the RFC destination in the central system during its registration. correct the value for Start the data collection method every.

and which explains all individual settings. Central Instance Central Monitoring System CEN (6. etc.20 J2EE SAP Web AS 6. 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. Third Party.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 CCMS Agents: Features. These descriptions therefore extend the process Installing and Registering the CCMS Agents for Experts [page 24]. and Operation Page 15 of 115 January 15.CCMS Agents 3. Tutor]. Installation. All Possible Central Monitoring Scenarios with CCMS Agents C11 SAPCCM4X SAPCCMSR SAPCCM4X Dialog Instance External TREX.20 J2EE 6. which describes the installation and registration of CCMS agents in general terms. 2007 .40+ ABAP) SAPCCMSR SAPCCMSR Java Addin SAPCCMSR 6. BC.

and choose Technical Infrastructure → Configure Central System → Create CSMCONF Start File for Agents. call transaction RZ21 and choose Technical Infrastructure → Configure Central System → Create CSMREG User. you need an agent for every instance of the system (central instance and potential dialog instances). 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. b. this is automatically insured. since you require the file for all agent registrations. and confirm your entries by choosing (Create CSMREG). proceed as follows: a. If possible. and Operation Page 16 of 115 January 15. Do not use a production system for this. We recommend that you generate this data in a CSMCONF file in CEN before the registration. you require the connection data from the agent to CEN. reserve a separate SAP system for monitoring and system management. To do this. you can easily keep this at the newest status with regard to release or Support Package status. In CEN. If you are using a separate SAP system. In CEN.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). In the case SAP AG CCMS Agents: Features. 2007 .20 Java Instance/Other Hosts [page 22] If you want to monitor a system with CCMS agents. For Java standalone systems and double-stack systems. You have the required executables for the CCMS agents. Save the file at a location that is centrally available. to avoid unnecessary load on the system. create the user by proceeding as follows (see also Creating the CSMREG User [page 33]): a. If this is not yet the case. call transaction RZ21. • There is a CSMREG user in CEN. proceed as described in Downloading the CCMS Agents [page 25]. Installation. Enter and reenter any password for this user. To download these. and profit from the newest developments in the areas of monitoring and system management. • During the registration of the agent. b.

In this case. If the monitored system is connected to CEN through WAN or telephony. This agent creates an alternative connection route between the monitored instance and CEN. 3. Procedure 1. Copy the start file CSMCONF to the working directory of SAPCCM4X. Installation. You can also use advanced functions (see Advanced Functions of the CCMS Agents [page 50]). Since this alternative connection route no longer requires a free work process. 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. Installing an Agent on an ABAP Instance To monitor an ABAP instance of an SAP system.1. SAP AG CCMS Agents: Features. Log on to the host of the ABAP instance as <SID>adm (UNIX) or SAPService<SID> (Microsoft Windows).CCMS Agents of ABAP systems. to ensure that the agent can access the shared memory. you need to install the appropriate agent for every instance of the system. 4. 3. enter the command sapccm4x –R pf=<profile path>. performance problems can occur due to increased network traffic. the access route is independent of error states of the ABAP instance and therefore more robust. 2007 . and use that one. 2. use the command sapccm4x –v to check which of the executables has the more current status. and Operation Page 17 of 115 January 15. create it. In the directory of the executable. use the CCMS agent 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. we do not recommend that you connect the monitored system with SAPCCM4X. for example to monitor specific processes or log files on the host of the monitored instance.

20 Java Instance/Other Hosts [page 22]. CCMS Agents: Features. follow the procedure described under Installing an Agent on a Java Instance (Double-Stack System) [page 20].2. Confirm the specifications by pressing the ENTER key in each case.20. 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. To do this. If problems occur during the registration of the agent on a Microsoft Windows platform. You only need to register the agent once for each Java system with CEN and to start the agent.CCMS Agents <profile path> specifies the instance profile of the monitored instance. follow the procedure described under Installing an Agent on a SAP Web AS 6. If you want to use the agent to monitor a J2EE Engine of a double-stack system (ABAP/Java). 3. For J2EE Engines with a release status of SAP Web AS 6. During the registration. Under UNIX. proceed as described in SAP Note 817714. By default. and Operation Page 18 of 115 January 15. The agent is part of the installation package of the Engine. Installation. • Note that this description applies only for monitored J2EE Engines as of SAP NetWeaver 04 SP Stack 12. You only need to enter two parameters yourself: The password for the administration user in CEN. 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 . under which you created the CSMCONF file. 2007 • • SAP AG . the system displays specifications from the CSMCONF to you again for confirmation. The password for the CSMREG user 6. 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. you must ensure yourself that SAPCCM4X is automatically started again when the host is restarted.

2. in the Monitoring service of the Visual Administrator (see below).CCMS Agents Procedure 1. and log on with your user as the J2EE Engine administrator. The name can be a maximum of eight characters long. choose Cluster → <SysID> → Dispatcher → Services → Monitoring. 6. The access data for the two required users in CEN is determined from the start file and displayed in the relevant fields. No.>/sapccmsr You can also save the start file in any directory that you can access from your local host. If necessary. Installation. Start the Visual Administrator by calling the start script go (UNIX) or go. In the Password column. 4. In this case. 3. In the navigation bar. The name must not contain an underscore (_). and choose the CCMS Agent Configuration tab page. If you want to monitor multiple systems with the same system ID. 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 Change …button. and enter in this input field an identifier for the system that is unique in your monitored system landscape. If necessary. 2007 .bat (Microsoft Windows). enter the passwords for the CEN Administration User and the CEN CSMREG User.>\sapccmsr UNIX: /usr/sap/ccms/<SysID>_<Inst. The CEN Administration User is the user with administrator authorization with which you created the CSMCONF start file. 7. you need to specify where you have saved the file during the registration of the agent. To do this. errors are highlighted in red. and specify the path for the start file. select the Long SID indicator. and Operation Page 19 of 115 January 15. The file is then automatically copied to the above directory. Log on to the host of a J2EE Engine of the system as <SID>adm. you can change the user name or the client. Copy the start file CSMCONF to the following directory: Windows: [drive]:\usr\sap\ccms\<SysID>_<Inst. Choose the Register button. 5. however. No. This “long system ID” must fulfill the following conditions: The first three characters must be the system ID. The registration log is displayed. SAP AG CCMS Agents: Features.

For J2EE Engines with a release status of SAP Web AS 6.20. you can see the corresponding monitoring data in the Alert Monitor in CEN. choose Start → Settings → Control Panel → Administrative Tools → Services. proceed as described under Installing an Agent on a Java Instance (Java Standalone System) [page 18]. 2007 . Result The J2EE Engine is now registered with CEN. Set the Start Type to Automatic. the agent is entered as a service during the registration. Under Microsoft Windows. To do this.> by double-clicking it. Under UNIX. You only need to register and start the agent once for each system. In the case of a double-stack system. the agent is automatically started by the startsap script when you start the J2EE Engine. and is automatically started during a restart of the host. and choose Start. If you want to monitor a J2EE Engine of a standalone Java system with the agent. and Operation Page 20 of 115 January 15.<Instance No. 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]). you only need to register the agent for the relevant agent 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. on the Microsoft Windows host on which the agent is running. As of SAP NetWeaver 2004s. and secondarily with CEN. 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.20 Java Instance/Other Hosts [page 22]. The agent is part of the installation package of the Engine. however.CCMS Agents 9. The Customizing destination has also been automatically created for all Java instances (only if you have left the check box enable CCMS Customizing marked). Installation. proceed as described under Installing an Agent on a SAP Web AS 6. • • SAP AG CCMS Agents: Features. 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.3. and choose the service SAPCCMSR. the agent must be registered with two systems: primarily with the local ABAP system. If problems occur during the registration of the agent on a Microsoft Windows platform. you need to start the associated service (which was created during the installation of the J2EE Engine) yourself. proceed as described in SAP Note 817714.

Installation. The name must not contain any underscores (_). you need the access data for two users for each of these systems: one administration user and one CSMREG communication user in each system. 3. you need to specify where you have saved the file during the registration of the agent.CCMS Agents Procedure 1. 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. and choose the CCMS Agent Configuration tab page. The file is then automatically copied to the above directory.-Nr. 4. Copy the CSMCONF start file to the following directory: Windows: [drive]:\usr\sap\ccms\<SysID>_<Inst. select the Long SID indicator. you can overwrite the predefined values. 8. No. Start the Visual Administrator. 5. The name must have a maximum of eight characters. In this case. If you want to monitor multiple systems with the same system ID. you can overwrite the predefined values. and Operation Page 21 of 115 January 15.>\sapccmsr UNIX: /usr/sap/ccms/<SysID>_<Inst. 2.>/sapccmsr You can also save the start file to any directory that you can access from your local host. If necessary. choose the Change …button. To do this. If necessary. however. 6. Log on to the host of a J2EE Engine in the system as <SID>adm . The CEN Administration User is the user with administrator authorization with which you created the CSMCONF start file. and enter an ID for the system in the associated field that is unique in your monitored system landscape. choose Cluster → <SysID> → Dispatcher → Services → Monitoring. and log on with your user as a J2EE Engine administrator. If necessary. 7. in the Monitoring service of the Visual Administrator (see below). and specify the path of the start file. 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: Features. 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.bat (Microsoft Windows). 2007 . by calling the start script go (UNIX) or go. This “long system ID” must fulfill the following conditions: The first three characters need to be the system ID. Since you want to register the agent with two systems. In the navigation bar.

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].
CCMS Agents: Features, Installation, and Operation Page 22 of 115 January 15, 2007

• •

SAP AG

CCMS Agents

Procedure

1. Copy the agent’s 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 Note’s 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 CEN’s Alert Monitor.

SAP AG

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

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.
CCMS Agents: Features, Installation, and Operation Page 24 of 115 January 15, 2007

SAP AG

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. The reason for specifying multiple folders is that CCMS agents are partly dependent on the operating system release. Log on with your SAP Service Marketplace ID. 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. see [Avail].6A → SAP KERNEL 4.20 → SAP WEB AS ABAP → SAP KERNEL 6. You can determine the version of a CCMS agent with the option –v (see Displaying the Version of a CCMS Agent [page 104]).com/swdc). SAPCCM4X. • 2. and SAPCM3X.x). For more information about the availability agent. including SAPCCMSR. SAP AG CCMS Agents: Features.SAR from the SAP Software Distribution Center of the SAP Service Marketplace (http://service. This archive contains all CCMS agents. agents for SAP Web Application Server 6. and Operation Page 25 of 115 January 15. 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. Installation. You can download CCMAGENT.6D 32/64-BIT → <operating system> → Database Independent. Only if the desired archive is not in either of the above folders. Agents for a current SAP release may no longer cover all available operating system releases (for example.CCMS Agents 4.20 are supported only on HP-UX 11. 2007 .00 32/64BIT → <operating system> → Database Independent.SAR. Check the following folders in the specified order for this file and download it: In the navigation bar. You require the file CCMAGENT. there are still application servers to be monitored that are running on HP-UX 10.2. • We recommend that you use the newest version of each agent.x. Only if the desired archive does not exist in the above folder. The archive also contains the availability agent CCMSPING. Downloading the CCMS Agents 1. however.20 32/64-BIT → <operating system> → Database Independent.sap. • You can determine the version of the CCMS agents in CCMAGENT.SAR by displaying the associated Info File.

2007 . the important thing is that it is released as a share with the name saploc. Decompress the CCMAGENT.3.4. this has changed: • • To monitor a SAP instance up to release NW04 (6.00) or a host without SAP instance. create it yourself during the installation.CCMS Agents • If you require an agent for an older operating system release that is not in the folders above. 4. For decompressing the archive. If the directory does not exist.6D). restart the agent (see Starting and Stopping CCMS Agents [page 103]). you must then ensure that the agent takes these files into account. use an agent with release NW2004s (7.40). However. use the following instruction: sapcar –xvf ccmagent. SAP also provides the newest CCMS agent functions in patches to older SAP Basis releases (especially SAP Basis 4. Creating the Required Configuration Files You can also create the following configuration files after registering the CCMS agent. As of SAP NetWeaver 2004s. always use an agent with release NW04 (6.40). By default.SAR archive with the SAPCAR tool. as far as possible. 3. so you could – independent of the monitored system release – always use the latest release of the CCMS agent. and Operation Page 26 of 115 January 15. this is the directory <drive:>\usr\sap.00).To do this. To monitor a SAP instance with release NW2004s (7. SAP AG CCMS Agents: Features.sar Up to SAP NetWeaver 04 CCMS agents wer e freely backward compatible. 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. 4. Take account of SAP Note 212876 (The new archiving tool SAPCAR). Installation.

create a SAPOSCOL filter file. 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. This profile file must also be the profile for the monitored instance.txt [page 77]) 4.4.2 Configuration File for Monitoring Operating System Data If you want to configure the monitoring of operating system data individually.CCMS Agents 4.1 Configuration File for Monitoring Log Files If you want to monitor log files with the CCMS agent.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]) SAP AG CCMS Agents: Features. 4. erroneously. on the other hand. 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. and usually not necessary. with which you can explicitly activate and deactivate parts of the operating system monitoring (see Structure of the SAPOSCOL Filter File oscolfile.4.4. 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 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]. 4.3 Profile File of the CCMS Agents You specify a profile file during the registration of a CCMS agent with pf=<profile>. 2007 . information for these systems is also displayed. 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. the specification of a profile file is optional. For these agents. Installation. create one or more log file templates (see Structure of the Log File Template of the Log File Agent [page 53]). and Operation Page 27 of 115 January 15.3. Otherwise.4.

It specifies the system number of the Java instance monitored by the agent. or explicit messages that an action was successful. Take this into account with the SAPCCMSR agent in SAP AG CCMS Agents: Features. 2007 . These alerts are instead automatically written to the database of the central monitoring system with the status complete. and Operation Page 28 of 115 January 15. 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. While you can. but are intended as all-clears. irrespective of which host is currently running. It specifies the system ID of the Java instance monitored by the agent. 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. to avoid the deletion of alerts that no longer fit into the shared memory segment of the agent. in general. monitor multiple systems with identical system IDs [page 90]. the default value is 1 (trace deactivated) SAPSYSTEM This parameter is only important for the agent SAPCCMSR with Option j2ee [page 10]. Installation.CCMS Agents DIR_WORK_SAPOSCOL Working directory of SAPOSCOL exe/saposcol Complete path of SAPOSCOL alert/TRACE Trace for monitoring architecture data. If a CCMS agent is installed on each of these hosts. alert/SAVE_SUPPRESSED_ALERTS Set this profile parameter to 1. the context name of the monitoring data (which also contains the name of the host) should be identical. alert/GREEN_ALERTS=1 Set this profile parameter to 1 to be able to work with all-clears (green alerts). SAPSYSTEMNAME This parameter is only important for the agent SAPCCMSR with Option j2ee [page 10]. there can be various hosts. Ensure this by setting an identical profile parameter SAPLOCALHOST in the profile file of the CCMS agent. SAPLOCALHOST Virtual host name used for addressing the local host of the agent In the context of high availability solutions. Green alerts of this kind do not inform you of error situations. set this trace only if expressly told to do so by Support.

and Operation Page 29 of 115 January 15. This is then used for the name of the RFC destination of the agent and the monitoring segment of the agent. ALALERTS. 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. 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. the hosts work with monitoring segments with the same name.4.INI configuration file is stored in the working directory of the CCMS agent. irrespective of the agent type. Installation. meaning that the data is reported in the same tree in the Alert Monitor. If you now ensure that these AL* files are accessible from both hosts. It primarily contains path specifications that are required for the operation of the CCMS agents. as the SAPCCM4X agent uses the profile parameters of the SAP application server by default. The name of the file is always SAPCCMSR. Specify a name with a maximum length of 13 characters.4 SAPCCMSR.INI. End each line of the profile file with the ENTER key.CCMS Agents particular. 2007 SAP AG .4. 4. and ALPERFHIS during the shutdown of a host. 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] CCMS Agents: Features. In the case of alternating operation of hosts of this type. the contents of the segment are not disturbed by switching host.exe 4.INI: Configuration File for the CCMS Agents The SAPCCMSR. The content of the segment is saved to the files ALMTTREE.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.3.

2007 . obsolete elements for which no log file exists any longer. specify the directory as a second parameter. as otherwise the CCMS agent only searches for these libraries in its working directory. are deleted from the shared memory SAP AG CCMS Agents: Features.1 You can set the following parameters in SAPCCMSR. Some plug-ins.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: n≥30: 4. meaning that they might not be loaded. Installation. such as itsmon.INI: Parameter PushCycleMinutes <n> Default. and Operation Page 30 of 115 January 15. LogfileParam DelTree If you specify Deltree.dll. In this case. 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. Configuration file for monitoring log files (log file template).4. which are stored in a particular directory. 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.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.4. require in turn additional shared libraries. The file path must not contain any spaces. multiple plug-ins are possible.

and Operation Page 31 of 115 January 15. 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]. OsColFile <file path> Specifies a SAPOSCOL filter file for filtering out subtrees of the operating system monitoring.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. the suffix . We recommend that you do not change this value. see Setting Up the Sending and Receiving of SNMP Traps Using CCMS Agents63 [page 63]) See Transferring GRMG Customizing Files to CEN [page 88]. for information about the default directory. for a general description of SNMP functions for CCMS agents. 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 CCMS Agents: Features. Installation. see Transferring Distributed Statistics Records with CCMS Agents [page 92]. since the DSRs in the default directory would then no longer be read and transferred to CEN. The first three characters of the name should correspond to the system ID of the monitored system (only for agent SAPCCM4X). 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. 2007 .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.

default = 0 if AlertLog is not set ### else default = 1 # AlertLogLevel <level> 4.4. ### 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 there is no logging of Alerts # AlertLog <full path filename. 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. 4. ### deletion. new values.INI does not yet exist when the CCMS agent is registered.5.INI Agent Configuration File If SAPCCMSR. and Operation Page 32 of 115 January 15.CCMS Agents • • Comment lines begin with the number sign (#). Enter the lines in the format <Parameter_name><space><Parameter_value>. Registering the CCMS Agents The CCMS agent makes itself known to the central monitoring system through registration. without suffix> ### ### Level of logging ### 0: no logging ### 1: Logging of Alerts ### 2: in addition log suppressed alerts. 2007 . creation. We recommend that you have the central monitoring system create the data required for this (see Automatically Creating the CSMCONF Start File [page 34]). Installation. the system creates the following file empty (containing only comments) in the working directory of the CCMS agent.2 Example SAPSSMSR. SAP AG CCMS Agents: Features. reset for any MTE) ### Parameter is optional.4.

To do this. or call transaction SU01. you can have the CSMREG automatically created in CEN. Ensure that the user type Communication (as of SAP Basis 4.CCMS Agents A prerequisite for the registration is that a CSMREG user exists in CEN (see Creating the CSMREG User [page 33]).1 Creating the CSMREG User As of SAP Web AS 6. and Operation . 3.5.6B) is selected on the Logon Data tab page.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. In earlier releases. 2007 Page 33 of 115 RFC_FUGR FUGR SALF SALS SCSM* SALH SAL_CACHE_RECEIVE RFC1 CCMS Agents: Features. 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. start transaction RZ21 and choose Technical Infrastructure → Configure Central System → Create CSMREG User. which is delivered as of SAP Basis 4. Installation. you must create the user manually using the following procedure: 1.40 SP 1 and as of 6. Create authorizations and a profile for CSMREG and assign the profile to CSMREG. Create the CSMREG user. Choose Tools → Administration → Administration → User Maintenance → Users. 4.6C) or CPIC (up to SAP Basis 4.20 SP 42. 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]. 2.

This means that if you are registering CCMS agents on different hosts. 2007 SAP AG .40 SP 1 and as of SAP Web AS 6. 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]). and Operation Page 34 of 115 January 15. Choose Technical Infrastructure → Configure Central System → Create CSMCONF Start File for Agents. Installation. 2.2 Automatically Creating the CSMCONF Start File During the registration of CCMS agents. start the registration as usual with the option –R. As of release SAP Web AS 6. or call transaction RZ21. proceed as follows: a. 4. Specify CSMCONF for the registration after the option –f. You only need to enter the passwords for the two central monitoring system users.CCMS Agents 4. 4. 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. The data is transferred from the CSMCONF file. If you are performing the registration in dialog. in dialog or dialog-free. Edit CSMCONF and enter the corresponding passwords in the parameters CEN_ADMIN_PASSWORD and CEN_CSMREG_PASSWORD. specify the agent’s Working Directory [page 47] as the location to which CSMCONF is to be written. 1. This applies irrespective of whether you want to perform the registration with the agent registration tool. You can enter the registration both in dialog and dialog-free. 3. Only the passwords used are removed. b.3 Registration with the Agent Registration Tool The agent registration tool simplifies the registration of the SAPCCMSR agent with exactly one CEN. Choose CCMS → Configuration → Alert Monitor.5. you primarily enter information about the central monitoring system and the users used for communication between the agent and the central monitoring system.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.5. To have the registration performed in dialog (see Registering the CCMS Agents in Dialog [page 35]). Its use has the following prerequisites: • • The CSMREG user exists in (see Creating the CSMREG User [page 33]) You have created the CSMCONF start file in the agent’s working directory (see Automatically Creating the CSMCONF Start File [page 34]) CCMS Agents: Features. meaning that you only need to confirm it. To have a dialog-free registration performed (see Alternative: Dialog-Free Registration of CCMS Agents [page 38]). by specifying a start file (referred to a CSMCONF in the following) in the registration call.

you enter the required connection data in the central monitoring system.20 Java Instance/Other Hosts [page 22] 4. this is shown in square brackets. In detail. Depending on the agent.4 Registering the CCMS Agents in Dialog During the registration of the agent. simply press the ENTER key): SAP AG CCMS Agents: Features. In the case of SAPCCMSR/SAPCM3X.CCMS Agents Proceed as described in the appropriate procedure below. and Operation Page 35 of 115 January 15. 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.5. you enter the following user data (if there is a default value for an entry. 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 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. 2007 . it is the full file path of the agent profile (see Profile File of the CCMS Agents [page 27]). An RFC connection to the agent is automatically created in the central monitoring system during registration. <profile path> is the full file path of the profile of the monitored instance. 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. 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). Installation. Ensure before the registration that the required configuration files are available. If you want to use this default value.

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
SAP AG CCMS Agents: Features, Installation, and Operation Page 36 of 115 January 15, 2007

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.
SAP AG CCMS Agents: Features, Installation, and Operation Page 37 of 115 January 15, 2007

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

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

January 15, 2007

1]> CEN_ADMIN_ROUTE=/H/<SAProuter host>/S/<SAProuter port>/H (optional. you can optionally specify logon data for the user under which the agent is to run as a Microsoft Windows service. User data of a user with authorization for system administration in the central monitoring system (see Registering the CCMS Agents in Dialog). 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. 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: SAP AG CCMS Agents: Features. and Operation Page 39 of 115 January 15. By default. 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.10. de> CEN_ADMIN_TRACE=<User trace [0.CCMS Agents Specification of the Central Monitoring System CEN_CONFIG CEN_SYSID=<System ID of the central monitoring system> . This user is used once to create an RFC connection to the agent in the central monitoring system. 2007 . only required in exceptional cases) . 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. such as en. 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. the <LocalSystemAccount> is used for this purpose. To do this. If your central monitoring system has a release status of at least SAP Web AS 6. the agents automatically report data to the central monitoring system. Installation. The agent is then automatically started at every restart of the server. 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> .

This period must be the only character in the line.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. see Registering with Multiple Central Monitoring Systems [page 89]. 2007 . SAP AG CCMS Agents: Features. normally CSMREG> CEN_CSMREG_PASSWORD=<Password of the above user> CEN_CSMREG_LANG=<Logon language. The following applies for all sections of the CSMCONF start file: • • • • Enter the lines in the format <Parameter_name>=<Parameter_value>. You can test the generated RFC connection of type T in transaction SM59. such as en. de> CEN_CSMREG_TRACE=<User trace [0. The passwords CEN_ADMIN_PASSWORD and CEN_CSMREG_PASSWORD are no longer contained in the configuration file in plain text after the registration. 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]> . For the SAPCCM4X agent.1]> . you can optionally assign the monitored system to a system group in the central monitoring system.). 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. Installation. and Operation Page 40 of 115 January 15. If you are registering the agent with multiple central monitoring systems. You must end the section with a period (. and for agent SAPCCMSR with Option j2ee [page 10].

2007 . # for logon load balancing.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.5. Installation. SAP AG CCMS Agents: Features. MGDSYSTEM . and not to the central monitoring system. # note.5.CCMS Agents 4. # 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 . The monitoring segment of the agent in this case belongs to the local system of the J2EE Engine. 4. 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 . and Operation Page 41 of 115 January 15.2 Example CSMCONF Start File CEN_CONFIG CEN_SYSID=CEN .5. 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 .

you must first answer the questions of whether there is at least one ABAP instance in the agent’s system (parameter SAPSYSTEMNAME of the Profile File of the CCMS Agents [page 27]). the various possible cases (see Examples [page 10]) in the CSMCONF start file are as follows: SAP AG CCMS Agents: Features. 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]).10) The data in the actual central monitoring system is then contained in the sections with the prefix CEN2. meaning that you no longer have to specify this information in the registration in dialog. no central monitoring system (CEN) exists ABAP instance exists. and a CEN [page 12] The system ID and system number of the agent’s local system are specified with the profile parameters SAPSYSTEM and SAPSYSTEMNAME.2 Dialog-Free Registration of SAPCCMS with the Option -j2ee If you want to install SAPCCMSR with the option -j2ee dialog-free.5. and Operation Page 42 of 115 January 15. central monitoring system (CEN) exists ABAP instance exists.5.1 Registering SAPCCMS with the Option -j2ee in Dialog During the registration of the CCMS agent with the option -j2ee. 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. 4. and whether there is a central monitoring system in your system landscape.6. After you have entered this information about your system landscape. 2007 . Installation. The CSMCONF start file therefore contains information about the ABAP instance of the agent’s local system in the following sections: • • • • CEN_CONFIG CEN_ADMIN_USER CEN_GATEWAY CEN_CSMREG_USER (as of SAP Web AS 6.CCMS Agents 4. The various options are described in the following chapters: Situation No ABAP instance exists. note that if there is an ABAP instance in the agent’s local system. perform the rest of the registration as described in Registering the CCMS Agents in Dialog [page 35].6. In detail.

the Customizing destination is automatically created during the registration of the agent. In the Bundles tab.J2EE. To create the Customizing destination. You only require the following procedure if you have manually registered the agent in accordance with Registering SAPCCMS with the Option -j2ee [page 41]. 2007 . SAP AG CCMS Agents: Features. and Operation Page 43 of 115 January 15. This destination is used to transfer the property changes from the Alert Monitor directly to the J2EE Engine. CEN exists ABAP instance exists. 2. To be able to change the properties of the agent nodes from the Alert Monitor. In the Program ID input field. In the Visual Administrator.<JSID>. Procedure Creating an RFC Destination in the J2EE Engine 1. create a bundle configuration.5. you must create a Customizing destination after you have registered the agent.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 must perform the following steps: • • • Create an RFC destination in the Visual Administrator of the J2EE Engine. CEN exists CSMCONF Prefix CEN: Central monitoring system Prefix CEN2 – CEN5: secondary central systems (optional) Prefix CEN: Agent’s local system Prefix CEN: Agent’s local system Prefix CEN2: Central monitoring system Prefix CEN3 – CEN5: Secondary central systems (optional) 4. 3. Create an RFC destination in the ABAP system with which you have registered the agent. Make this destination known to the monitoring architecture. Installation. where <JSID> is the (long-) SID of the monitored Java instance. no CEN exists ABAP instance exists. 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]). enter the following name: SAP.6. You can display this monitoring data both in the Alert Monitor and in the local Java system (Monitoring service of the Visual Administrator).CCMS. choose Server → Services → JCo RFC Provider → Runtime.CCMS Agents Situation No ABAP instance.

<JSID>. Switch to change mode by choosing (Display ↔ Change). Installation. choose the Agents for the Local System radio button in the Topology group box. 5.J2EE. Enter T (Start an External Program via TCP/IP) as the connection type. In the Activation Type group box. If the agent is monitoring an instance of a standalone Java system. 2007 . which you have already entered in the Visual Administrator when creating the RFC destination (see Connecting J2EE Engine to the CCMS). Making the RFC Destination Known to the Monitoring Architecture 12. as for the agent in the column J2EE Customizing Destination. 7. If the agent is monitoring a Java instance in an ABAP+Java system. If you do not have the data. and choose the Unicode radio button in the Character Width in Target System group box. choose the Agents for Remote Systems radio button in the Topology group box.<JSID>. call transaction SM59 and choose the Create button. Save your entries.<JSID> in the Program ID input field. choose the Registered Server Program radio button. where <JSID> is the system ID of the monitored Java instance. The RFC Destination screen appears. Switch to the Technical Settings tab page.CCMS Agents 4. and Operation Page 44 of 115 January 15. and choose Display Overview. To create an RFC destination.J2EE. If the agent is monitoring an instance of a standalone Java system. SAP.CCMS. 11. 10. 13. 14. and enter the name of the RFC destination created above. and enter a description of the destination. SAP AG CCMS Agents: Features.J2EE. Call transaction RZ21. and choose Display Overview.CCMS. Confirm your entries by choosing the (Enter) button. In the Gateway Options group box. Enter the name of the destination in the RFC Destination input field. 15. 8. 6. In the other input fields. this is CEN. 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. Use the naming convention SAP. 9. and enter SAP. enter the gateway information for the local ABAP system. this is the local ABAP system. enter the connection data of the central monitoring system. If the agent is monitoring a Java instance in an ABAP+Java system. Save your entries.CCMS. Switch to the Special Options tab page.

CCMS Agents Result You have now created the required RFC destination and made it known to the monitoring architecture. you must create these RFC connections yourself. In the monitored system.in this case. Installation. the agent has not yet been started. 4. If you have registered the CCMS agent under UNIX. For security reasons. You can now also change the properties of the nodes for the corresponding CCMS agent SAPCCMSR –j2ee in the Alert Monitor. These methods store values for the monitoring attributes in the shared memory of the monitored system. as the system starts the associated service.5. • Executing Analysis Methods CCMS Agents: Features. you must also ensure yourself that the CCMS agent is automatically started after a restart of the server (for example. these connections of type 3 already exist . 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.8 SAPCCM4X: Creating the RFC Connections If a SAP R/3 System is connected with the central monitoring system using the CCMS agent SAPCCM4X.7 Starting the Agent Under Microsoft Windows NT the CCMS agent is automatically 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. this user is merely an observer that must log on to this system for each query. 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. Otherwise. we recommend that you define two RFC destinations for every monitored system here.5. The monitoring system reads these values using an RFC call (and therefore a particular user name). 4. 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. by entering the start command in INITTAB). and Operation Page 45 of 115 January 15. 2007 SAP AG . you do not need to create any connections.

4. In the RFC Destination field. The RFC Destination dialog screen appears. CCMS Agents: Features. For more information about user CSMREG. choose Yes and choose Enter again. As the two types of requirement access the monitored system in very different ways. 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. • Executing Analysis Methods We recommend that you perform the RFC call under your own user name. In the Connection type field. 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. on which there are a few additional fields. 2007 . For Load distribution. Installation. 5. Choose Enter. enter 3 (SAP R/3 System) and in Description. and Operation Page 46 of 115 January 15. and choose Create. 2.CCMS Agents If a data collection method reports an alert. enter a short descriptive text for the RFC connection.10) or CPIC (up to SAP Basis Release 4. it must have more extensive authorizations in the target system. • Data Collection Create a CSMREG user on all systems to be monitored and ensure that the user type Communication (SAP Web Application Server 6. Call SM59 (Display and Maintain RFC Destinations). 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. enter the following names (as explained above. and also occur with very different frequencies.6D) is activated. The Technical Settings tab page appears. As this analysis method may make changes in the monitored system. you can start an analysis method. follow the procedure below : 1. we recommend that you assign different authorizations to different users during the definition of the two RFC destinations. see Creating the CSMREG User [page 33].

9. 8. To do this. Working Directory and Log Files of the CCMS Agents 4. you still need to inform the monitoring architecture that the connections to the target system now exist. the communication status was set to SHUTDOWN. On the Logon/Security tab page. 11. On the Monitored Remote SAP Systems tab page. Choose Display Overview. activate the System Overview radio button. Save the completed definition. 10. in the Topology group box. If the connection to the target system did not yet exist during the registration. and test the RFC connections. 7. set the communication status for the target system to ONLINE.6.6. Installation. start transaction RZ21. make the following entries for the users (as explained above.1 Working Directory Working Directory /usr/sap/tmp/sapccmsr (UNIX) \\<host>\saploc\prfclog\sapccmsr The working directory is in the following location. Activate change mode by choosing the Display ↔ Change ( ) pushbutton. and Operation Page 47 of 115 January 15. 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) SAP AG CCMS Agents: Features.CCMS Agents 6. 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. 4. Save your changes. Once you have defined both RFC destinations. 2007 . and.

• SAPCCMSR. so that the agents of different systems and numbers are separated.6. the entire system logging is performed directly to the file stdout. In the Topology group box. and SAPOSCOL information should be considered. In the case of SAPCCMSR with Option j2ee [page 10] . In the case of a dialog-free installation. by default. You can display all files in the working directory of the agent in the central monitoring system. choose the file by double clicking it.INI Contains information about the extent to which Plug-Ins. these AL* files must also be stored separately from those of possible ABAP instances with the same number. log files. SAP AG CCMS Agents: Features.CCMS Agents • The saploc directory in the path of the CCMS agent SAPCCMSR can also have another name. and log files are created for RFC communication.INI Contains information for registration at the gateway of the central monitoring system. The files ALMTTREE. Installation. If the directory does not exist. and Operation Page 48 of 115 January 15. • SAPRFC. The system displays the files of the directory.INI: Configuration File for the CCMS Agents [page 29]). To display the contents of a file. and ALALERTS are stored in this directory (since the agent manages its own shared memory. this file is read when the agent is started (see SAPCCMSR.install in the directory from which you started the registration. • • CSMCONF Contains data about the central monitoring system. the important thing is that it is released as a share under the name saploc. 4. a subdirectory <System ID>_<instance number> is created in /usr/sap/ccms (UNIX) or \\<host>\saploc\ccms (Microsoft Windows). . ALPERFHI.2 Log Files If you install the CCMS agent in dialog mode. it is the directory <drive:>\usr\sap. The Monitoring: Display Technical Topology screen appears. the parameters correspond to those in the start file for dialog-free installation (see Structure of the CSMCONF Start File [page 38]). A log file is also created during runtime for the CCMS agent under the name <agent_name>.log.) The log files of the agent are stored in the subdirectory <System ID>_<instance number>\sapccmsr. You can use transaction RZ21 to do this. Now select the desired agent and then choose Working Directory of the Agent ( ). 2007 . select one of the Agents for… radio buttons. the system creates a log file called <agent_name>. create it yourself during the registration.

Activate the trace only if specifically told to do so by support. The trace is written to the file dev_<agent name> in the working directory of the agent.6. 2007 .CCMS Agents 4. and Operation Page 49 of 115 January 15.3 Trace Files You can set the developer trace with the option -t when starting or registering the CCMS agent. SAP AG CCMS Agents: Features. Installation. You can use the option -debug to have a rolling trace written to the file dev_<agent name>. along with one to two megabytes at the end of the trace. 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.

INI: Configuration File for the CCMS Agents [page 29] or copy it to the relevant standard directories that the agent monitors. 2007 . Files and Directories for the Advanced Functions CCMS Agent Agent‘s Working Directory CSMCONF Start file of the agent.-No> or /usr/sap/CCMS/<SysID>_<Inst.INI Configuration file of the agent. are immediately detected and a corresponding monitoring function is started. grmg).CCMS Agents 5.ini) \\<host>\saploc\CCMS\<SysID>_<Inst.INI only become active after the agent has been restarted (see Starting and Stopping CCMS Agents [page 103]). Installation. these are automatically transferred to CEN (GRMG_*) procmon SAPCCMSR. Changes in SAPCCMSR. procmon. contains information about the central monitoring systems and their communication users \\<host>\saploc\prfclog or /usr/sap/tmp grmg Contains Customizing files. 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. Changes in the standard directories of the agent (logmon. 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. and Operation Page 50 of 115 January 15.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 CCMS Agents: Features.-No> logmon Contains log file templates that are automatically read (*logmon. on the other hand.

Prerequisites In general. it transfers it to the central monitoring system. Monitoring Log Files One of the functions of CCMS agents is monitoring log files. the last change time. If the agent finds the line for which it is searching.log) With these files. it automatically recognizes the restart of an application and in this case starts reading from the start of the file again. the agent reads newly added entries and saves its last read position. You can use this log file agent. The agent reads newly added entries and saves its last read position. It automatically recognizes the newest log files of a type. these are the files to which the <SID>adm user (UNIX) or the SAPService<SID> (Microsoft Windows) has access to. or display lines that contain a certain search pattern in the Alert Monitor.CCMS Agents 5. assign alerts to them. 5. as this agent must always run under this user. • 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. and so on). to monitor log files for particular search patterns. • Log files that are created by the application with a new name each time (such as brbackup. these are the files that the user under which the agent is running has permission to read. the agent reads newly added entries and saves its last read position. and Operation Page 51 of 115 January 15. Due to the smaller size of the log file. and display the results in the Alert Monitor.1. Installation.1. which is integrated into all agents. brconnect. you can monitor the existence and the last change date of particular log files. so that the current log file can always be monitored. 2007 . In the case of the SAPCCM4Xagent. In the case of the SAPCCMSR agent. SAP AG CCMS Agents: Features. This means that you can search any text files (such as database alert logs or ITS log files) for any text patterns. a CCMS agent can only monitor those files that it has permission to read. 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.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>. or for their existence.

2007 . to specify a configuration file for each file to be monitored that contains the details of the monitoring (log file template). • • The templates are standard files (not links. Installation.ini *<SysID>_ABAP_<InstNo>*logmon. that is by default <instance directory>\log\logmon CCMS Agents: Features. therefore. So it is assured that every agent is only monitoring the logfiles of its own monitored instance.INI: Configuration File for the CCMS Agents [page 29]).CCMS Agents You can activate the monitoring of log files in the CCMS agent configuration file SAPCCMSR. for example) that do not exceed 2 Kilobytes in size (without comments). 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.ini *<SysID>_<InstNo>*logmon.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.INI (see SAPCCMSR. SAPCCMSR. 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.INI: • The names of the templates follow the naming convention below: CCMS Agent SAPCCMSR SAPCM3X SAPCCMSR –j2ee SAPCCM4X Naming Convention *logmon. you do not need to specify these log file templates in SAPCCMSR. 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). and Operation Page 52 of 115 January 15. The templates are in the following folders. Use the parameter LogFile. The log file agent also automatically detects log file templates if these fulfill the following conditions.ini <SysID> and <InstNo> are the system ID and the instance number of the monitored ABAP or Java instance.

set FILENAME=dev_w* and IGNORE_FILE=dev_w*.INI (see SAPCCMSR.1.2. but not the previous version of these trace files. dev_w*.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. 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. 2007 . However. and the corresponding log files are no longer monitored. and Operation Page 53 of 115 January 15.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.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.1. opens a search area DIRECTORY="<directory>" (required parameter) Directory that contains the log file FILENAME="<file name>" (required parameter) Name of the log file. since this means that the log file templates in the standard directory are no longer read. 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. we do not recommend this procedure.INI: Configuration File for the CCMS Agents [page 29]).old.old. 5. Installation. SAP AG CCMS Agents: Features. dev_w*. wildcards are permitted If you want to monitor the trace files of the work processes. 5.

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. you can define a rule-based monitor that contains the subtrees for all monitored log files. store different components in different contexts to further group the results. Regardless of whether or not you set this parameter. this is the context Files_of_<Hostname>. to avoid storing an unnecessarily large quantity of data in the monitoring architecture. its monitoring tree is deleted. and Operation Page 54 of 115 January 15.1] (Default = 0) By default. This means that different files are monitored over time. 2007 . by default. RESCANFROMBEGIN=[0. if the file size exceeds the value. allows you to differentiate between different log files with different paths. In this way. 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. an additional hierarchical level to group the monitored files. an alert is generated PREFIX="<character string>" Appears before the MTE nodes. for example. MONITOR_NEWEST_FILES=<number> (Default = 20) Maximum number of files that is to be monitored. this function allows you to differentiate between the different monitored log files. Use this parameter only if you require this additional hierarchical level. all search patterns are case sensitive (0). set IGNORE_CASE=1. IGNORE_CASE=[0. exactly <number> files with the newest change time are monitored. but the same name (the maximum length of the prefix is 8 characters) SAP AG CCMS Agents: Features. and its alerts are reset. if the number of files whose names fulfill the search criteria exceeds this number. but provides. Like the PREFIX parameter (see below). If upper and lower case are to be disregarded during the search. you can. The maximum value for <number> is also 20.CCMS Agents MONITOR_CONTEXT="<Context_name>" Name of the monitoring context to which the log file agent writes the results of the monitoring. the MTE class of the monitoring context is always CcmsFileMonitoring. Installation. unlike PREFIX. If a file is removed from monitoring because other files have a newer change date. By specifying this MTE class.

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).1] SAP AG CCMS Agents: Features.CCMS Agents SHOWNEWLINES=[0. 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). This means that even if an agent has just been registered. MTE_CLASS="<MTE class>" CHECK_EXISTENCE_ONLY=[0. or if a log file that fulfills the FILENAME condition has just been created.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).1] (Default = 0) Value=1: The Alert Monitor creates the subnode Newlines. This ensures that the alerts are processed more quickly. all parameters for monitoring and for search patterns (see below) are ignored. You can directly assign a central auto-reaction to the above node using the log file template. 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. In extreme cases. since the assignment of the central auto-reaction is otherwise performed by the program SAPMSSYT. this parameter is used to speed up the assignment of the auto-reaction method to newly-created nodes. the corresponding node is assigned the specified auto-reaction method immediately when it is created. it is even possible that. 2007 . In this case. Installation. This ensures a quicker processing of the corresponding alerts and the execution of the auto-reaction method. which only runs once an hour. that is. by default. 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. and Operation Page 55 of 115 January 15. with the traditional method assignment. the auto-reaction method is not executed at all for the first alerts for the corresponding nodes. MONITOR_LAST_FILE_MODIF=[0.

wildcards are not allowed. 5.255] Severity of the alert MESSAGECLASS_<x>="<message class>" Default = SAP-T100 Message class CMP_FROM_BEGIN_<x>=[0.GREEN] Default = YELLOW Color of the alert in the monitoring architecture Default = 0 SEVERITY_<x>=[0. 2007 .1.2. 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. only the lines that contain the relevant search pattern are copied to the agent's shared memory. PATTERN_<x>="<character string>" (PATTERN_0 is required) Search pattern in the log file (case sensitive.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.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). enter a number <x> for each search pattern in the parameter suffix of the following parameters.2. If you set this parameter and the value Last incoming message is set for the setting Display "current value" like.. and Operation Page 56 of 115 January 15. Begin with the number 0. 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.1] (Default = 0) By default. the last matching line is always displayed in the log attribute in the Current Status view in the Alert Monitor. When doing this. Installation..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. Only one SAP AG CCMS Agents: Features. If you set this parameter. This function is not ideal for displaying search patterns to which no alert is to be assigned (such as version or date information).1.CCMS Agents REPORT_MATCHING_LINES_ONLY=[0.YELLOW.

If parameters are required. You can define the name of the text attribute yourself.INI. if the search pattern is found.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. the maximum length of the pattern is 80 characters).INI file would then be superfluous. 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 Alert Monitor displays the corresponding line as the content of a separate text attribute.ini Logfile /usr/sap/tmp/sapccmsr/DEV_Wxlogmon. Installation. To do this. If the search pattern exists at several places in the log file. If a search pattern of this type is found. SAPCCMSR. the length will be truncated correspondingly.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]). SAP AG CCMS Agents: Features. meaning that only one line is displayed even in the case of multiple search patterns.ini Logfile /usr/sap/tmp/sapccmsr/SAPCCMSRlogmon.CCMS Agents log attribute is available in the Alert Monitor for all monitored search patterns. 2007 .1. 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 (. and Operation Page 57 of 115 January 15. An entry in the SAPCCMSR. wildcards are not allowed. the system displays the last position in which it is found. There is therefore a second way in which you can monitor log files for search patterns. All other parameters are optional.). APPL_INFO_<x>="<character string>" Search pattern in the log file (case sensitive. 5.ini Logfile /usr/sap/tmp/sapccmsr/BACKUPSlogmon. If the length of a parameter value exceeds its maximum length. this is highlighted. different log file templates are entered in SAPCCMSR. Obsolete subtrees are also to be deleted in RZ20. the log file agent would definitely find these templates.INI must therefore contain the following lines: Logfile /usr/sap/tmp/sapccmsr/ORAALERTlogmon. set the parameter DelTree.

3. 2007 . The agent searches through /oracle/<SID>/saptrace/background/alert_<SID>.ini would have the following content: LOGFILE_TEMPLATE DIRECTORY="/usr/sap/<SID>/<Instance name>/work" FILENAME="dev_w*" IGNORE_FILE="dev_w*.log ORA-00600 735: ORA-00600: internal error code. Installation. and Operation Page 58 of 115 January 15.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" MTE_CLASS="ORAALERT" PATTERN_0="ORA-00600" VALUE_0=RED MESSAGECLASS_0="SAP-T100" MESSAGEID_0="rt 584" .2 Trace Files of the SAP Work Processes The template /usr/sap/tmp/sapccmsr/DEV_Wxlogmon.3.1.CCMS Agents The contents of the log file templates mentioned above are shown in the following: 5.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.old" MTE_CLASS="WORKPROC" SHOWNEWLINES=1 MONITOR_FILESIZE_KB=0 PATTERN_0="ERROR" VALUE_0=RED SAP AG CCMS Agents: Features.ini would have the following content: LOGFILE_TEMPLATE DIRECTORY="/oracle/<SID>/saptrace/background" FILENAME="alert_<SID>. 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 Oracle Alert Log The template /usr/sap/tmp/sapccmsr/ORAALERTlogmon.1.

A subtree is created in the Alert Monitor for every dev_w* file. 2007 . Installation. 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.old trace files are not monitored. 5. 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.1.ini would have the following content: LOGFILE_TEMPLATE DIRECTORY="/usr/sap/tmp/sapccmsr" FILENAME="sapccmsr. the agent recognizes this using the file size and begins reading from the start of the files. and Operation Page 59 of 115 January 15. so that there would be nine subtrees for nine work processes.3 Log File of the SAPCCMSR CCMS Agent The template /usr/sap/tmp/sapccmsr/SAPCCMSRlogmon. 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.CCMS Agents MESSAGECLASS_0="SAP-T100" MESSAGEID_0="rt 584" PATTERN_1="core" VALUE_1=RED MESSAGECLASS_1="SAP-T100" MESSAGEID_1="rt 584" .log" MTE_CLASS="Log_of_sapccmsr" MONITOR_LAST_FILE_MODIF=1 PATTERN_0="ERROR" VALUE_0=RED MESSAGECLASS_0="SAP-T100" SAP AG CCMS Agents: Features.3. The system also displays the size of the files and the number of lines reported per minute: Display for this Monitoring Function in the Alert Monitor 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. Copies of the dev_w*.

log continuously for ERROR messages and returns a red alert if it finds a matching message. SAP AG CCMS Agents: Features. 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. The agent searches through /usr/sap/tmp/sapccmsr/sapccmsr. if it finds one of these patterns. Installation. so that you can see the associated version information in the corresponding subtree. The agent also searches for other search patterns to which no alert value is assigned and. The agent also displays the last change of the monitored log file.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" . 2007 . and Operation Page 60 of 115 January 15. If the search pattern exists at several places in the log file. the system displays the last line that contains the search pattern.

0 2195 Service Pack 3 pid 2004 Error 2056: M ***LOG R49=> ThCPICSyncWait. and a green message if it finds successfully.1. automatically creates new subtrees when required. 32 bit. The agent checks at regular intervals whether there are new matching files (in this case. meaning that the backup was successful. the monitor creates a subtree for each monitored file. and Operation Page 61 of 115 January 15.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]). The name of the subtree consists of a prefix SAP AG CCMS Agents: Features. The agent searches through the newest file of the format /oracle/OMA/sapbackup/*. OSS note 584136 patchno 611 intno 20020600 running on P57373 Windows NT 5.ant continuously for ERROR messages and successfully messages and returns a red alert if it finds ERROR. 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. As shown in the examples above.ant" MONITOR_NEWEST_FILES=1 MTE_CLASS="BACKUPS" PATTERN_0="ERROR" VALUE_0=RED PATTERN_1="successfully" VALUE_1=GREEN .3. whether a new backup has been started).CCMS Agents Display for this Monitoring Function in the Alert Monitor Files of Host3 Sapccmsr.ini would have the following content: LOGFILE_TEMPLATE DIRECTORY="/oracle/OMA/sapbackup" FILENAME="*.4 Log File for the Backups of an Oracle Database The template /usr/sap/tmp/sapccmsr/BACKUPSlogmon. Installation.log CCMS version 20010925. a separate node is displayed for each search pattern Time of the last change of the monitored log file 5.log Host on which a CCMS agent that monitors log files is running Subtree for the monitored log file /usr/sap/tmp/sapccmsr/sapccmsr.1. 2007 . and deletes obsolete subtrees. 5. Non-Unicode compiled at Feb 4 2003 systemid 560 (PC with Windows NT) relno 6200 patch text patch collection 2003/2. therefore. multithreaded.

this attribute is created only if you specify the parameter SHOWNEWLINES=1 in the log file template Size of the log file.CCMS Agents that you define in the configuration file described above. and the name of the file. In this way. this attribute is created only if you specify the parameter MONITOR_FILESIZE_KB≥0 in the log file template (if MONITOR_FILESIZE_KB>0.FileSize) Time of the last check of the log file. Time of the last change of the monitored log attribute. double click the Complete Name attribute in which the name of the monitored file is displayed. and Operation Page 62 of 115 January 15. Search pattern with alert value (see Monitored Search Pattern in the Monitored Log Files [page 56]). Info[<Name>] (. 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. you can differentiate between different files with the same name in the monitor.TimeStamp) New Lines in Log File (. depending on the values of the parameters in the corresponding log file template: MTE (Suffix of the MTE Class) Complete Name (. You can monitor a file for multiple search patterns (the system displays these in the monitor separated by |) Monitored Patterns (.CollCheck) File Time Stamp (. you also assign an alert threshold value to the attribute by setting) SAP AG CCMS Agents: Features. in turn. Installation. To do this.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. 2007 .ApplInfo) If you are searching for search patterns with no alert value.MatchingL) Data Collection Check (. 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]).Patterns) Lines found for pattern Lines of the log file that match the search pattern (.NewLines) Log File Size (. Every subtree. this status attribute is always colored green. consists of some or all of the following monitoring tree elements.

This enables both communication with external management platforms and monitoring of SNMP-compatible devices. Installation. Sending and Receiving of SNMP traps with CCMS agents is not possible on the platform HP64 at the moment. and Operation Page 63 of 115 January 15. In this situation. 5. To do this. Procedure 1.INI file (see SAPCCMSR.INI: Configuration File for the CCMS Agents [page 29]).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. 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 CCMS Agents: Features. When receiving SNMP traps. the recipient to which the SNMP traps are to be sent or the port at which SNMP traps are to be received.2. 2007 . When sending using agents. set the following parameters. Specify the complete path of the required configuration files in SAPCCMSR. among other things. 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. 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.Adjusting the Configuration File for Sending SNMP Traps [page 64] . For more detailed information about this. SNMP traps are always to be sent if an alert occurs in particular nodes. the agent itself sends the traps instead of starting a new process for each alert (as is the case when sending using autoreactions). which receives SNMP traps for the entire system landscape. You define here. see: . You can send and receive SNMP traps with CCMS agents. it is useful to select only one agent as the trap recipient. Adjust the relevant configuration file.Adjusting the Configuration File for Receiving SNMP Traps [page 67] 2.

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 CCMS Agents: Features. to which access rights are assigned) Indicator of whether a trap (<SPACE>) or an inform (X) is to be sent.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. 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. or 3) Receiving host for the SNMP traps Name of the community (logical group of devices within a network monitored by SNMP. To have the change in SAPCCMSR. unlike with an SNMP trap. that is. restart the agent (see Controlling the CCMS Agents [page 102]). 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. Installation.2. 3. 2007 .INI take effect. and the protocol with which they are to be sent. Ensure that the agent can access these files. such as the recipients and the port to which the traps are to be sent. You can now send alerts in the monitoring segment of a CCMS agent as SNMP traps and receive SNMP traps using CCMS agents. with an inform.1 Adjusting the Configuration File for Sending SNMP Traps You define details about the sending of the SNMP traps in the configuration file. 2c. and Operation Page 64 of 115 January 15. a value that is specified in a level with a higher value overwrites the value of a lower level. 5.

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 SAP AG CCMS Agents: Features.INI: Configuration File for the CCMS Agents [page 29]). 2007 . this parameter is only required if INFORM=0. no encryption AUTH_PROTOCOL Procedure for authenticating the message (creation of a checksum used to ensure that the message was not changed). and Operation Page 65 of 115 January 15. Example There is a template with the default settings for the configuration file in the SNMPLIB archive.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 . 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. Change this value to the path of the MIBS directory. Installation. 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. the MD5 (Message Digest 5) procedure is supported Engine ID of the application from which the SNMP traps are to be sent. no encryption (Default) authNoPriv: Authentication. the following levels are supported: NoauthNoPriv: no authentication.

Installation.CCMS Agents # valid for all [DESTINATION_x] templates # # default. 2007 . # 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=. and Operation Page 66 of 115 January 15. # 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 SAP AG CCMS Agents: Features. if parameter is not set # VERSION 1 TRANSPORT UDP # HOSTNAME localhost MIB_DIR .

you define details about the receipt of the SNMP traps in the such as the port at which the recipient is to listen. To define users. the following applies: Parameter <SECURITY_ENGINE> Description Engine ID of the application from which the SNMP traps are to be sent. You can avoid traps of this type being displaying by setting DROP_AUTH=1 UDP:162 DROP_AUTH 0 • Section [SNMP_USER] If you are using SNMP version 3. LISTEN_PORT_<x> Transport protocol and port number with which the traps are received.1. traps can be received by different ports With SNMP Version 3.2. For SNMP versions 1 and 2c. this is required to display the received traps correctly Default . in the case of incorrect authorization..CCMS Agents USER_NAME=myuser AUTH_PASSPHRASE=mypassword SECURITY_ENGINE=0x0102030405 HOSTNAME=ls3016 AUTH_PROTOCOL=MD5 5. In this configuration file. and Operation Page 67 of 115 . the user must authenticate himself or herself. create a line with the following format for each user: createUser [–e <SECURITY_ENGINE>] <USER_NAME> <AUTH_PROTOCOL> <AUTH_PASSPHRASE> When making these specifications. define one or more SNMP users which receive the SNMP traps in this section. since the engine ID is generated during the communication if INFORM=1 January 15.2 Adjusting the Configuration File for Receiving SNMP Traps You require a configuration file to set up the receiving of SNMP traps. this parameter is only required if INFORM=0. (program’s directory) Change this value to the path of the MIBS directory.. an Authentication Failure Trap is generated. by using different values of X=0.2.. Installation. leave this section empty. 2007 SAP AG CCMS Agents: Features. Make the following settings in the configuration file: • Section [SNMP_TRAPD] Parameter MIB_DIR Description Directory that contains the MIB files (Management Information Base).

17:05:18 SNMP traps sent from Host3 red 20.201. In this case.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).19.2003.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.200.2003. Installation. and Operation Page 68 of 115 January 15.3 Displaying Received SNMP Traps in the Alert Monitor You can receive SNMP traps with CCMS agents. 17:04:48 There is a log attribute for each host that receives the SNMP traps. the MD5 (Message Digest 5) procedure is supported Password of the user <AUTH_PASSPHRASE> Example The template rectraps.12.2003 . A separate message is generated for each SAP AG CCMS Agents: Features.40] SNMP-Traps Host3 [12.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=. Multiple messages are generated for each trap (each with the value red). 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. LISTEN_PORT_0=udp:162 [SNMP_USER] createUser myuser MD5 mypassword createUser -e 0x0102030405 myuser1 MD5 mypassword1 5.12.19.12. 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. 2007 .2.

12. you can use CCMS agents to monitor the Windows Event Log.12. values for the parameters that the trap contains may be displayed here.2003 20.0 = Timeticks: (1) 0:0 RFC1155-SMI::internet. System This log contains events that are reported by Microsoft Windows system components.12. in parameter TrapReceiveFile in the configuration file of the SAPCCMSR.6.12. 5. and Operation Page 69 of 115 January 15.2003 20. 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]). in turn.12.2003 20.2003 20. 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. Installation. the Event Log logs events for the following areas: Security This log contains security-related events. Depending on the MIB used.12.3.2003 20.12.1.1.12. such as file accesses and changes.INI agent.0 = OID: SAP SAP-MIB::r3maAlertSystemName = STRING: „C SAP-MIB::r3maAlertSegmentName = STRING: An SNMP trap generates multiple messages in a log attribute. Event Log Monitoring with CCMS Agents On Microsoft Windows platforms.2003 20.12.1.12.0 = Timeticks: (1) 0:0 RFC1155-SMI::internet.3.2003 20.1.1.2003 20.1.4. which you specify.4.2003 20.CCMS Agents parameter that is set in an active Management Information Base (MIB) and which was assigned a value in the SNMP trap. By default.3. The trap is completed by a message with no message text. The application developer decides in each case which events are to be logged. 2007 SAP AG . The events are divided into the following event types: • • Information Warning CCMS Agents: Features.6. or successful and failed logons. Applications This log contains events that were written by an application or program.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. You determine which events are to be logged in the corresponding security settings.0 = OID: SAP SAP-MIB::r3maAlertSystemName = STRING: „C SAP-MIB::r3maAlertSegmentName = STRING: RFC1213-MIB::sysUpTime.

that is. it is deactivated. all event log events are monitored and displayed in the Operating System monitor in the central monitoring system (CEN). You can determine the status of the agent using the option –v (see Controlling the CCMS Agents [page 102]).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.INI can contain multiple entries of this type. By default. only for security events By default. all event sources and all of their event types are monitored. by default. EventLogResolveMessages [On|Off] EventLogResolveMessages On activates the complete resolution of the event log messages. This means that you obtain more exact information at the cost of performance. Installation. this is deactivated. SAPCCMSR.CCMS Agents • • Error Success Audit and Failure Audit. which point to multiple event log templates. Process Flow To activate the monitoring of the event log. by default. 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]).INI (see Controlling the CCMS Agents [page 102]). you need to restart the agent after setting the parameters in SAPCCMSR. after you activate event log monitoring. 2007 . 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. set the following parameters in the SAPCCMSR. SAP AG CCMS Agents: Features. and Operation Page 70 of 115 January 15. To activate these settings. a more exact description of the event is obtained using additional Microsoft Windows system calls and transferred to CEN.

and Operation Page 71 of 115 January 15. and Security event logs are monitored when monitoring the Microsoft Windows Event Log. 5. Installation. MTE_CLASS="<MTE class>" (Default: CCMSEventLogCL) MTE class of the monitoring object that monitors the events of the above event log SAP AG CCMS Agents: Features. first specify which event log (Application. or Security) you want to monitor: EVENTLOG_TEMPLATE Keyword for the agent. 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 specify these event log templates in SAPCCMSR.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]). System. you need to choose a name other than Security for the Security event log. which point to multiple event log templates. System. this opens the configuration area for event log monitoring EVENTLOG_NAME=[Application. Security] (required parameter) Name of the event log to be monitored MTE_NAME="<Name of the node. all event sources (Sources) of the Application. System. Structure Monitored Event Logs In the event log template.1 Structure of the Event Log Template By default. you can instead restrict the monitoring to selected event logs or event sources.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. 2007 .3.INI can contain multiple entries of this type. By specifying one or more event log templates. and also deviate from the default alert values for the events.

depending on the event type. In this way. you can have only events from certain event sources monitored. Installation. YELLOW.<ALL>] (Default: <ALL>) Event source from the event log specified in EVENTLOG_NAME. RED. YELLOW. RED. RED. Required parameters are indicated. in this way. 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 (. YELLOW. you can set the desired alert colors individually for each source. 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. Start with the number 0. 2007 . When doing this. You want to monitor only the following event sources in the System event log: Automatic Updates Service Control Manager SAP AG CCMS Agents: Features. YELLOW. YELLOW. if the name of the event source contains a space. place the name in quotation marks INFO_<x>=[GREEN.). RED. and Operation Page 72 of 115 January 15. all other parameters are optional. 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. enter a number <x> for each desired event source in the parameter suffix of the following parameters. SOURCE_<x>=[event source.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>. 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. 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. There must not be any spaces before or after an equal sign (=).

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.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.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 . and Operation Page 73 of 115 January 15. Installation. Which event sources of which event logs are displayed in this subtree depends on the configuration of the event log monitoring. set the following entries in the SAPCCMSR.ini The event log template evtmon_appl. 2007 . 5.3.INI configuration file: EventLogMon On EventLogMon C:\usr\sap\prfclog\sapccmsr\evtmon_appl. the corresponding subtree is displayed in the Operating System monitor of the central monitoring system. To do this. SAP AG CCMS Agents: Features.

Prerequisites Event log monitoring must be active. this means that at least the parameter EventLogMon On must be set in SAPCCMSR. The subtree consists of the following MTEs: SAP AG CCMS Agents: Features. and the monitored event sources. always all sources Log attribute with events from the corresponding event log. 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]).2005 . 2007 .CCMS Agents Current -Node Display Off S t a t u s ( 20. if not restricted in the event log template. a subtree is generated that contains the name of the event log.INI: Configuration File for the CCMS Agents [page 29]. alert values either in accordance with defaults (Information = green.05. Features For each monitored event log. and Operation Page 74 of 115 January 15. its events. Warning = yellow…) or in accordance with event log template settings Integration Since the monitoring is performed by a CCMS agent. 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. Installation.

Start the Operating System monitor from the list of monitors by double-clicking it. by default. 5. For more detailed information about the operating system collector. see [SAPOsCol] and SAP Note 371023. Activities To display the subtree. the alert values have the usual values (Information = green. Start the Alert Monitor using transaction RZ20. Application. 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.ComplPath) Event Log Entries (CcmsEventLogCL. the name component CcmsEventLogCL in the above MTE class name is replaced by the value of the parameter MTE_CLASS in the template. All CCMS agents can copy this data to the CCMS monitoring segment and transfer it to the central monitoring system. Warning = yellow. On the CCMS Monitor Sets screen. Installation.CCMS Agents MTE (MTE Class) Event Logs (CCMSEventLogs) <Name of an event log> (CcmsEventLogCL) Event Log Name (CcmsEventLogCL. all sources are always monitored Monitored Sources (CcmsEventLogCL. you can also make these settings yourself in the event log template (see Structure of the Event Log Template [page 71]) Monitored event sources.Entries) Description Subtree for event log monitoring Subtree for the events of an event log (by default. the event logs System. or choose CCMS → Control/Monitoring → Alert Monitor. 3. and expand the Event Logs subtree for the desired host. 2. 2007 . This means that the data is visible in the CCMS monitoring architecture and is displayed in the familiar transactions ST06 and OS07. however. SAP AG CCMS Agents: Features. if these are not restricted in the event log template.Sources) If you have set the MTE class yourself in the event log template. proceed as follows: 1. and Operation Page 75 of 115 January 15.4. and Security are monitored) Name of the monitored event log Log attribute containing events from the corresponding event log. Error = red). expand the SAP CCMS Monitor Templates set.

<hostname>.1 Operating System Data Displayed in the Alert Monitor After the successful installation of the agent.CCMS Agents In this way. As of Patch Collection 2005/4 of the CCMS agents. transaction OS07 displays all data collected by SAPOSCOL. you can monitor the operating system data for servers without a running SAP Basis system or SAP Web AS.INI (see SAPCCMSR. 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.4.INI: Configuration File for the CCMS Agents [page 29]). and Operation Page 76 of 115 January 15. You can use a filter to explicitly remove subtrees or entire components from the monitoring display. 2007 .2 Configuring the Monitoring of Operating System Data The agent also allows an individualized selection of subtrees for the Operation System and Filesystems monitors. No monitoring nodes are then generated for these. you can activate an exclusive monitoring with which only the file systems that you explicitly specify are monitored. Alternatively to filtering out file systems. An expensive installation and configuration of RFCOSCOL is no longer necessary. 5. All other file systems are not then monitored. This simplifies Customizing. In this case.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. you can use the parameter OsColFile to specify a configuration file in which you can make these settings. OS07 is therefore well suited to being an analysis method for the Operating System monitor. UNIX) of the monitored host. 5. In the configuration file of the CCMS agent SAPCCMSR. of threshold values or the assignment of different auto-reactions depending on the function or the platform (Microsoft Windows. SAP AG CCMS Agents: Features. you can also change the names of the MTE classes for the monitored operating system data as desired.4. You can display this data using the RFC destination SAPCCMSR.99. This means that you can assign operating system data for different hosts to different MTE classes. for example. SAPCCMSR.txt in the following. Installation.

exclude particular file systems that are always 100% full from the monitoring. and Commit_Charge (Microsoft Windows only).txt You can make the following specifications in the oscolfile. for example. you can assign the operating system data for different hosts to different MTE classes. Paging.4.txt filter file: Filtering Out Components After the keyword FilterOutComponent.3 • Structure of the SAPOSCOL Filter File oscolfile. and for which the system will therefore not create a subtree in the monitoring tree in transaction RZ20. Installation. and Operation Page 77 of 115 January 15. • 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. Swap_Space (UNIX only). enter the components that you do not want to be copied to the CCMS monitoring segment. 2007 .CCMS Agents 5. Since this is done at host level. you can also set the associated MTE class and attribute group yourself for the components CPU. 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 CCMS Agents: Features. you can. In this way. Use the keyword MonitorComponent. 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.

the SAPCCM4X agent then creates a new Operating System monitoring tree in accordance with oscolfile. Other file systems are ignored. select Method Definitions and choose Display Overview. specify the wildcard character * for <LAN>. • Adjusting the Monitoring of the LAN Interfaces As of Patch Collection 2005/4. to monitor the LAN interface MS TCP. use a rule-based monitor to display only the file systems to which you have explicitly assigned this MTE class. In this case. 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. you must deactivate the ABAP data collector in the monitored system. if you want. 2007 . This means that subtrees in the monitoring architecture are only created for file systems specified after the keyword MonitorFilesystem. You can also set the MTE class and attribute group of the LAN interfaces to be monitored. SAP AG CCMS Agents: Features. Use the wildcard character * in this case too. for example. To do this. and Operation Page 78 of 115 January 15. If you have installed an SAPCCM4X agent. it is always the class FilesystemMO). there is already a complete Operating System monitoring tree that was created by the monitored SAP instance. Entries with the keyword FilterOutFilesystem are also ignored. Note also that the name for <LAN> must not contain any spaces. Installation. To do this. there is a maximum of 24 characters available to you for the name you choose. you can activate an exclusive monitoring.txt: Follow the procedure below: 1. you can simply enter MS* for <LAN>. so that you can. When it is started. In the Methods group box. In this way. enter the keyword MonitorLAN. as a workaround. 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. • Adjusting the Monitoring of File Systems As an alternative to filtering out individual file systems. for example. you can exclusively monitor specific LAN interfaces in the same way as monitoring specific file systems. Since the length of the MTE class is restricted to 40 characters. start transaction RZ21 in the system that the SAPCCM4X agent is monitoring.CCMS Agents You can see from the table that the set MTE class is used as a prefix for the associated monitoring attributes.

4 Example SAPOSCOL Filter File oscolfile. On the Release tab page. deactivate the Data Collection Method indicator and on the Control tab page. Change the following methods by selecting the methods and choosing Edit Data ( ): • • • CCMS_Fsys_Collect CCMS_OS_Collect CCMS_OS_LAN 3. Installation. Restart the CCMS agent. it does not have any filter functions. the meaning of selected configuration settings is explained in the example below: ####################################################################### ### ### OsColFile. 5.4. unlike FilterOutFilesystem and MonitorFilesystem. 5. and Operation Page 79 of 115 January 15.txt. 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.txt The following file is intended to assist you in creating the filter file oscolfile. 4. Note that with the keyword MonitorProcess. which is stored in the SAPOSCOL working directory (see [SAPOsCol]). • Set the MTE Class and Attribute Group of Monitored Processes By default. 2007 . You can change this MTE class (and the attribute group) by specifying the desired name after the keyword MonitorProcess. you only assign monitored processes to classes and groups.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 SAP AG CCMS Agents: Features. Save the method definitions. the MTE class MonitoredProcessesMo is assigned to processes that are monitored by the operating system collector SAPOSCOL. deactivate the Execute method immediately after start of a monitoring segment check box.CCMS Agents 2.

Name can contain '*' as a ### wildcard (<Pattern>). too. if these represent file systems collected by saposcol ### <MTE Class> and <Group> are optional. Examples of Configuration Parameters and their Meaning Contents of oscolfile.g. If you want to specify your own customizing ### group you have to specify the MTE class.CCMS Agents # FilterOutFilesystem <Filesystem Name> | <Pattern> ### CCMS agent does not create MTEs for <Filesystem Name> |<Filesystem> ### Filesystem name can contain '*' as a wildcard (<Pattern>). too. # MonitorProcess <Name> | <Pattern> <MTE Class> [<Group>] ### Changes the MTE Class (and the Attribute Group) of the monitoring ### objects of the monitored process <Name>. If you want to specify ### your own customizing group you have to specify the MTE class. too. ### ### 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. $DIR_TRANS ### $DIR_PERF. 2007 . ### <Group> is optional. and Operation Page 80 of 115 January 15. # MonitorComponent <Component Name> <MTE Class> [<Group>] ### CCMS agent creates MTEs with specified MTE class and customizing ### group. All other ### LAN interfaces are ignored ### Name can contain '*' as a wildcard (<Pattern>) ### <MTE Class> and <Group> are optional.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 CCMS Agents: Features. ### then the standard name is used. ### 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. If you want to specify ### your own customizing group you have to specify the MTE class. If you don't specify the customizing group. Installation.

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). Installation.CCMS Agents Contents of oscolfile. and Operation Page 81 of 115 January 15. 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. 2007 . The J2EE Engine automatically generates SAP AG CCMS Agents: Features.ini • <SysID> and <InstNo> are the system ID and the instance number of the monitored ABAP or Java instance.ini *<SysID>_ABAP_<InstNo>*procmon.5 Monitoring Selected Processes You can also use the operating system collector SAPOSCOL [SAPOsCol] to monitor the availability of selected processes.4. 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.ini *<SysID>_<InstNo>*procmon. The monitor displays the number of running processes and the CPU and memory usage for each name template. 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. broken down by different users.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). which follow the naming convention below: CCMS Agent SAPCCMSR SAPCM3X SAPCCMSR –j2ee SAPCCM4X Naming Convention *procmon.

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 CCMS Agents: Features. Installation. by default.ini). UNIX: /usr/sap/tmp/logmon). follow the procedure below: Creating the Configuration Files Create a template for the process monitoring (dev_proc or *procmon.CCMS Agents suitable templates and stores these in the specified (cross-instance) directory. • procmon and dev_proc are stored in SAPOSCOL’s working directory (Microsoft Windows: \\<host>\saploc\prfclog. Process Flow To start monitoring selected processes. 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). CCMS agents can read this data from the shared memory and display it in CEN. 2007 . The process monitoring is performed at collection intervals of one minute. the template must have the following structure: • • • The list of monitored processes begins with $PROC and ends with $. and Operation Page 82 of 115 January 15. Comment lines begin with the number sign (#).

to find the process with the path /usr/sap/tmp/saposcol) By specifying the same attribute group. Installation. you can create a rule-based monitor that contains this process. you can use the wildcard character asterisk (*) (see the example below). MTE name MTE name under which the monitoring object for the monitored process name is displayed in the alert monitor. 20 characters optional. use the rule CCMS_GET_MTE_BY_CLASS in a rule- based monitor. if you do not set this parameter. 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. max. 30 characters User MTE class To do this. Name template is used as the MTE name CCMS Agents: Features. you can use the wildcard character asterisk (*) MTE class to which the nodes are to belong. to improve the clarity of the display. 40 characters optional. it is not possible to monitor all processes by entering only the wildcard character asterisk User under whose name the process is running.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. you can easily adjust the threshold values for these monitored processes By specifying an MTE class. max. 2007 SAP AG . max. max. and specify the above MTE class there. 40 characters January 15. 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. and Operation Page 83 of 115 optional.

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. MTE name. Installation. in the Monitored Processes subtree (settings for MTE class. Setting the Threshold Values Since the expected CPU and memory usage is different for each process. You do not need to change SAPOSCOL or restart the responsible CCMS agent. the parameter values must not contain any spaces or special characters. choose Edit → Properties → Use for Individual MTE) Use a specific attribute group in the configuration file for the desired monitored process. 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. and attribute group have no effect on the output in the operating system monitor). 30 characters Enter the above parameters without quotation marks. max.CCMS Agents Parameter Attribute group Description Attribute group to which the attributes of a monitored process name are to belong. SAPOSCOL reads the contents of the configuration files every five minutes. SAP AG CCMS Agents: Features. Alert Logging for CCMS Agents You can define another log file for all CCMS agents that logs all alerts that the agent reports. The simplest way to do this is directly in the alert monitor itself. 2007 . and Operation Page 84 of 115 January 15. 5. you can simplify the maintenance of the threshold values using an assignment to an attribute group Notes optional. ensure that you adjust the threshold values of the corresponding performance attributes. but want to use other system management tools that are to be based on the data from the CCMS agents. by selecting the relevant performance attribute and choosing Properties. This is especially useful if you do not use the CCMS Monitoring Architecture to display alerts (the CCMS Monitoring Architecture has its own logging). Your changes then affect only the processes that you have assigned to this group.5.

if AlertLog is set) level=2: Also suppressed alerts. or newly created MTEs 5. deleted.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. 2007 . Use the parameters AlertLog and AlertLogLevel to do this: Parameter AlertLog <filename> Meaning Complete path of the log file (specify the filename without suffix.\<Monitoring object>\<Monitoring attribute> SAP AG CCMS Agents: Features. the suffix .5.INI: Configuration File for the CCMS Agents [page 29]).5.INI (see SAPCCMSR. reset. 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>\.log AlertLogLevel <level> Scope of the logging: level=0: No logging (default. if AlertLog is not set) level=1: New and completed alerts (default.. and Operation Page 85 of 115 January 15. new values for MTEs. Installation.CCMS Agents 5. the log file for the previous day is saved under the following name: <file name>_<date in the format YYYYMMDD>.1 Activating the Alert Logging You can activate alert logging in the CCMS agent configuration file SAPCCMSR.log is automatically set) Every day..

the name of the monitored file. there are two analysis methods that display the contents of the file or the URL in a separate window.\R3Syslog\Communication ALERT vanished [ 29|20194] for BCE\PWDF0487_BCE_26\.) SAP buffer hit rate below threshold value" for MTE 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\.CCMS Agents 5.INI: Configuration File for the CCMS Agents [page 29].\Dialog\LogonLoadQuality ALERT vanished [ 38|20196] for MTE BCE\PWDF0487_BCE_26\.3 Example Alert Log File # AlertLog file started at 20010520 # Please. Displaying File Contents in the Alert Monitor Files or Web resources can be monitored with various monitoring functions of the monitoring architecture.\Dialog\LogonLoadQuality ALERT YELLOW Sun May 20 00:02:58 2001 [ 38|20217] "71% 80% (15 Min. do not edit manually. rc: -0010" for MTE BCE\PWDF0487_BCE_26\.6. You can use the wild card character (*).INI file for the working directory of the CCMS agents (see Working Directory [page 47]) and the SAP AG CCMS Agents: Features.. When doing so. Prerequisites The text attribute must have content that fulfills one of the following prerequisites: • • The content can be interpreted as a URL. for example.5... To quickly display the contents of a file of this type or of a URL from the Alert Monitor. and Operation Page 86 of 115 January 15. Installation....\Program\HitRatio 5. ALERT RED Sun May 20 00:00:58 2001 [ 19|20215] "NiConnect failed. and the file can be accessed using a CCMS agent. 2007 . the CCMS agent only transfers files for which you have previously assigned a display authorization. is displayed as a text attribute (as in the case of Monitoring Log Files [page 51]). This analysis method is already assigned to the text attribute with the name of the monitored file. after the key word ViewDirList. You do not need to assign read authorization in the SAPCCMSR. enter the files whose display is to be allowed into SAPCCMSR.. To do this. The content can be interpreted as a file name.. For security reasons..

8. In the Method Name input field. 2007 .1 Example of Defining Displayable File Contents (SAPCCMSR. enter one of the following method names: SAP AG CCMS Agents: Features. 3.6. The Monitoring: Methods screen appears. 5. choose change mode with the Display ↔ Change ( ) pushbutton. 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.6. 2. In the Method Assignment group box.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. 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. 4. Start the Alert Monitor using transaction RZ20 or choose CCMS → Control/Monitoring → Alert Monitor. If you want to assign the analysis method to the selected MTE class. Select the desired node and choose Properties. follow the procedure below: 1. Installation. 5. 6. choose Method Name. 7.2 Assigning the Required Analysis Method Assign the appropriate analysis method to the desired text attribute. The files in these directories can always be displayed. choose Method Name. and Operation Page 87 of 115 January 15.CCMS Agents working directory of the operating system collector SAPOSCOL. and choose the Analysis tab page.ini file # File contents that can be # displayed The following can be displayed: /usr/sap/tmp/info. Start the desired monitor from the list by double clicking it.txt the file /usr/sap/tmp/info. To do this. Choose the Methods tab page and then choose the Method Assignment pushbutton. If you only want to assign the analysis method to this MTE. The Monitoring: Properties and Methods screen appears. In the Analysis Method group box.INI) # Section from the sapccmsr.

5. Installation. An example of this is an extension for monitoring the Internet Transaction Server (ITS) and cached disk subsystems. When doing so.CCMS_SHOW_URL_FROM_TEXT_ATTR. Result If the text attribute can be interpreted as a file name or a URL. Customizing files with the prefix GRMG_ are automatically transferred and the associated scenario is started. A Customizing file specifies which component(s) are to be monitored.INI Configuration File [page 30]).CCMS_SHOW_FILE_FROM_TEXT_ATTR.7. you can now display the contents of the file or the URL by choosing the attribute by double clicking it. 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]. Save your entries. Changing the parameter might mean that SAP components that are instrumented for monitoring with GRMG are no longer monitored.8. 2007 . To transfer this information to the central monitoring system. . both Customizing information and availability queries and responses are exchanged as XML files. 5. For more information. such as EMC Disc Arrays (Symmetrix). SAP AG CCMS Agents: Features. if the contents of the text attribute is to be interpreted as a URL. and it is then displayed. 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. 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 Operation Page 88 of 115 January 15. 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. see SAP Note 420213. we do not recommend this. 9.CCMS Agents . the Web browser is called at the frontend with this URL.

such as threshold values. you can define an additional monitoring system as a replacement for emergencies or maintenance periods. 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. extend the CSMCONF start file (see Alternative: Dialog-Free Registration of CCMS Agents [page 38]).9. With central auto-reactions. part of a system landscape with a central monitoring system. 2007 SAP AG . you should make the following settings when registering the agent: .Choose the central monitoring system of the landscape as the primary monitoring system. The start file initially consists of the following four sections. you cannot execute the following commands in the secondary monitoring system: • Change properties. however.CCMS Agents 5. in turn.9. which define properties and the users used by the central monitoring system: • • • CEN_CONFIG CEN_ADMIN_USER CEN_GATEWAY CCMS Agents: Features. If this system is. As an alert should always trigger exactly one action for consistency reasons. the corresponding agent also processes requests from all monitoring systems as an RFC server. without having to restart or reregister the CCMS agents for these periods.Choose the system with which the database server is associated as an additional monitoring system • In high availability solutions. central auto-reactions are performed only in the primary central monitoring system. to display threshold values. Registering with Multiple Central Monitoring Systems You can also register the CCMS agents with multiple monitoring systems. . and Operation Page 89 of 115 January 15. In detail. 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]). This means in principle that data and alerts are no longer sent just to one system. • The possibility of defining multiple monitoring systems has the following advantages: • 5. Both systems have the same status with regard to displaying data or alerts. but rather to multiple systems. of nodes that are provided with values by a CCMS agent. use the corresponding technical view of the Alert Monitor Have central auto-reaction methods executed (see AutoRea]).1 Start File CSMCONF with Multiple Central Monitoring Systems For dialog-free registration with multiple central monitoring systems. Installation. alerts in monitored systems cause an alert in the assigned central monitoring system.

and Operation Page 90 of 115 January 15.10) In the case of multiple central monitoring systems.. but which are known by the same target system ID in the monitoring architecture. create these four sections for the relevant system in the same way. you must first define the required RFC connections and specify these on the Remote Monitoring Entry screen. For every additional monitoring system. 2007 . however with the names CEN2. create these four sections as usual for the primary central monitoring system. This situation occurs in particular in very large IT landscapes or with outsourcing. it is possible to read and process data in the remote system. 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> . can no longer be clearly assigned to the corresponding system. CEN3. It is possible that you want to monitor multiple systems with identical system IDs. The nodes of the systems can then be assigned to exactly one system within the central monitoring system using the unique target system ID. . . 5. This is usually the system ID of the system (see SAPCCM4X: Creating the RFC Connections [page 45]).. you must only ensure that the first three characters of the target system ID match the system ID of the corresponding system. 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. As these three characters are the threecharacter system ID. 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). Installation. nodes from different systems.CCMS Agents • CEN_CSMREG_USER (as of SAP Web AS 6.. You should therefore assign target system IDs that are unique system landscape-wide in the case of multiple systems with an identical system ID. The monitoring architecture uses this target system ID to identify and differentiate between all monitored systems.10) If you use system groups in your central monitoring systems. However. You also enter the Target System ID of the system to be monitored. If you are using multiple central monitoring systems. Monitoring Multiple Systems with an Identical System ID If you want to monitor multiple systems. When doing this. This section contains the system group to which the monitored system is assigned. In this case. SAP AG CCMS Agents: Features. extend the MGDSYSTEM section..10.

Installation. 3. Procedure 1. You now also want to monitor an additional PRD system at the RFC destination DES5. that also has the target system ID PRD in the monitoring architecture. To be able to monitor multiple systems with an identical system ID.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]). 2. the central monitoring system requires Support Package 16 for SAP Web Application Server 6. the system ID is again supplemented by the target system ID known in the central system.INI: Configuration File for the CCMS Agents [page 29]). or call transaction RZ21. The Monitoring: Registering New Contexts for Monitoring screen appears. as described in SAPCCM4X: Creating the RFC Connections [page 45]. Choose CCMS → Configuration → Alert Monitor. Ensure that the target system ID is set as the value of the parameter LongSid in the SAPCCMSR.10.The first three characters of the target system ID match the system ID of the remote system. DES2. Specify the desired target system ID.CCMS Agents When transporting data back to the central system.PRDDES2: System PRD at destination DES2 . and Operation Page 91 of 115 January 15.INI configuration file for the CCMS agent SAPCCM4X (see SAPCCMSR.20. 2007 SAP AG . Ensure that you fulfill the following three conditions when doing so: . you do not need CCMS Agents: Features. and DES3.PRDDES1: System PRD at destination DES1 .The target system ID is unique among all monitored systems. Example • You want to monitor three systems with the system ID PRD at different RFC destinations DES1. or Support Package 28 for SAP Web Application Server 6. . 4. The rest of the procedure is the same as that for registering a system to be monitored . In this case. Choose Technical Infrastructure→ Create Remote Monitoring Entry. . You can assign the following target system IDs: . The longer target system ID is always used in the central monitoring system.PRDDES3: System PRD at destination DES3 • You are already monitoring a system with the system ID PRD at the RFC destination DES4.

PRD: System PRD at destination DES4 . this directory has the following path: • J2EE Engine and TREX as of SAP NetWeaver 2004s: UNIX: • /usr/sap/ccms/<SysID>_<Inst. You can display the data there in the Global Workload Monitor (aggregated data) and in the functional trace (unaggregated data). while it is host-specific for all other DSR components. the system overwrites the oldest statistics file.PRDNEU: System PRD at destination DES5 5. As soon as the maximum number of files has been reached. SAP AG CCMS Agents: Features.11. 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. Installation.>\dsr All other DSR components. 2007 . A specified number of files are written in each component subdirectory. No. DSRs provide you with information for a DSR component about the workload generated and the resources used in the system by actions. Transferring Distributed Statistics Records with CCMS Agents Distributed Statistics Records (DSRs) are an extension of the concept of the ABAP statistics data. and Operation Page 92 of 115 January 15.CCMS Agents to change the target system ID of the first system. It is now the task of the CCMS agent to transfer these DSRs to the primary central monitoring system CEN. Depending on the DSR component and release. A new statistics file is started hourly. specify the following target system ID for the new system: . No.>/dsr Microsoft Windows: [drive]:\usr\sap\ccms\<SysID>_<Inst. 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.

Displaying Agent Data in the Central Monitoring System The data transferred by the agent is available in the central monitoring system after registration. this segment has the contexts: . You can view all of these contexts. this method of data retrieval is better from a performance point of view. This segment has the contexts: . 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. SAPCCMSR –j2ee SAP AG CCMS Agents: Features. Monitoring Contexts of the CCMS Agents in the Monitoring System Depending on the CCMS agent.MoniInfra_<host name>_local You can view these new contexts. directly in the monitor set SAP CCMS Technical Expert Monitors in the monitor All Monitoring Contexts. the installation of the CCMS has no visible effect.MoniInfra_<host name> If you also include additional monitoring functions using plug-ins (see Including Additional Functions in CCMS Agents [page 88]). 2007 . and Operation Page 93 of 115 January 15. the monitoring segment contains additional contexts. 6. for example. • SAPCCMSR The central monitoring system creates a monitoring segment SAP_CCMS_<Hostname>. If you have activated the push technology of the CCMS agent.CCMS Agents 6. Installation.<host name> .Files_of_<host name> .Files_of_<host name>_local . • SAPCM3X The central monitoring system creates a monitoring segment SAP_CCMS_<host name>_local. the system now first attempts to use the CCMS agent to access data from the SAP instance. By default.1. directly in the monitor set SAP CCMS Technical Expert Monitors and in the monitor All Monitoring Contexts.3x_<host name>_<SID>_<System number> . However.<host name> . for example.

If you want to create a rule-based selection. Installation. sorted by topic areas. If the agent is shut down. or call transaction RZ20. Choose Monitor(set) → Create. On the Create Node screen. On the Edit Rule Nodes screen. Choose CCMS → Control/Monitoring → Alert Monitor. You can then access these monitors more quickly and more easily in the monitoring hierarchy. that is. they are displayed as obsolete if no values are reported.1 SAPCM3X: Creating a Rule-Based Monitor Note that the entries <CURRENT> and <ALL> are to be entered exactly as they are shown. 2007 . 3. they do not stand for a variable. Creating CCMS Agent Monitors in the Central Monitoring System You can also easily create rule-based monitors for the data transferred by the agent.2. The agent is simply a way of collecting data that is better from a performance point of view and more reliable. Choose Edit → Create Node.CCMS Agents The Java monitoring data is displayed in the SAP J2EE Monitor Templates monitor set. 1. the relevant data is transferred using a dialog work process again. Installing this agent does not change the existing monitoring contexts. 6. choose Rule Node. Activate the maintenance functions. choose the following rule using the F4 help: CCMS_GET_MONITORING_SEGMENT_NAMES SAP AG CCMS Agents: Features. and specify that you want to create a new monitor in an existing monitor set. 2. • 6. unlike <Hostname>. place the cursor on the New Monitor line or on a virtual node.2. Instead. The subtrees in the Alert Monitor that are created by the CCMS agent do not disappear immediately if the agent is shut down. and Operation Page 94 of 115 January 15. 4. 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.

and Operation Page 95 of 115 January 15. specify the following selection parameters: . specify the following selection parameters: .R3System = <CURRENT> .R3System = <CURRENT> . The new monitor is now part of your monitor set. Installation. you can use it in the same way as any other monitor. On the Edit Rule Nodes screen. choose Rule Node.R3System = <CURRENT> . Choose CCMS → Control/Monitoring → Alert Monitor. specify the following selection parameters: . Choose Edit → Create Node.MoniContext = <ALL> SAP AG CCMS Agents: Features.R3System = <CURRENT> . 2. Repeat this procedure from point 3.MoniSegment = SAP_CCMS_<host name> . or call transaction RZ20. specify the following selection parameters: . Save your new monitor by choosing Save or Generate Monitor.MoniSegment = SAP_CCMS_<host name>_local 6. choose the following rule using the F4 help: CCMS_GET_MONITORING_SEGMENT_NAMES 5. The system prompts you to enter a name for your monitor. but this time choose the following rule on the Edit Rule Nodes screen: CCMS_GET_MONITORING_CONTEXT_NAMES On the Edit Rule Nodes screen. place the cursor on the New Monitor line or on a virtual node. and specify that you want to create a new monitor in an existing monitor set.MoniSegment = SAP_CCMS_<host name> 6. 6.MoniSegment = SAP_CCMS_<host name>_local . The monitor is then automatically saved. Repeat this procedure from point 3. 2007 . 4. On the Edit Rule Nodes screen. On the Create Node screen. Choose Monitor(set) → Create.MoniContext = <ALL> 7. On the Edit Rule Nodes screen.2. Activate the maintenance functions. but this time choose the following rule on the Edit Rule Nodes screen: CCMS_GET_MONITORING_CONTEXT_NAMES On the Edit Rule Nodes screen. If you want to create a rule-based selection.CCMS Agents 5.2 SAPCCMSR: Creating a Rule-Based Monitor 1. 3.

Save your new monitor by choosing Save or Generate Monitor. the monitor provides the following information about the agent. 32 20. 23:18:48. without you having to make any additional settings. 16:06:09 3221 sec 100 % Patch collection 2003/2.02. as this data appears immediately in transactions ST06 and OS07 and in the Operating System monitor of the Alert Monitor (transaction RZ20). RFC_PING ok Single agent Information about the agent SAPCCMSR.CCMS Agents 7.2001. Last test: 20.2003.00 Description Status Heartbeat Availability Agent Version Details SAPCCM4X. SAP Note 584136. CCMS version 20010925.2003 . 32 20.. Last test: 20. The new monitor is now part of your monitor set.02. and Operation Page 96 of 115 January 15. Use this monitor to monitor the CCMS agents in your IT landscape.3.02. 10:04:58.02. 6.. you can use it in the same way as any other monitor. The system prompts you to enter a name for your monitor.2003.\CCMS_Agents\. 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.2003 16:36:20: Agent calls as [BCE:000:CSMREG].08..Host2. 2007 .99 Description Status Heartbeat Availability Agent Version Details SAPCCM4X.02. CCMS version 20010925.Host2. 16:42:45 ) -Node Display Off Selfmonitoring CCMS Agents Name of the monitor CEN\CCMS_Selfmonitoring\. Installation. You do not need to create your own monitors for any of the CCMS agents to display data in the operating system monitor.08.Host1. 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. 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. In addition to the RFC destination of the agent.00 controlling C11 C11_Host2_01 on Host2 Inactive since 17. SAP Note 584136. The monitor is then automatically saved.99 controlling CEN Host1 on Host1 active since 18.2003 16:36:20: Agent calls as [BCE:000:CSMREG]. 16:06:10 0 sec 0% Patch collection 2003/2.. SAPCCMSR.Host1.2001. RFC_PING ok SAP AG CCMS Agents: Features.

Installation. To do this. and Operation Page 97 of 115 January 15.Status) Heartbeat (CsmTaskCcmsAgent. you can change the time period in the Properties of the MTE class) Static information about the agent used.<Name of host system>.Text) Status (CsmTaskCcmsAgent. The name of the subtree is the same as the RFC destination of the agent and has the following structure: <Type of agent>. if the agent is inactive.<System number of monitored instance> Each of these subtrees consists of the following monitoring tree elements: MTE-Name (MTE Class) Description (CsmTaskCcmsAgent.4. SAPCM3X. also the current status of the RFC connection used to do this 6. Displaying Agent Data in the Topology Display 6.4. 2007 .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. this attribute contains the value 0 sec Percentage of the time in which the agent is active (by default in the last 15 minutes. 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.CCMS Agents There is a separate subtree for each individual CCMS agent (SAPCCMSR. SAPCCM4X) that provides data to the Alert Monitor of the monitored system. follow the procedure below: SAP AG CCMS Agents: Features.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.Details) Information about the central monitoring system user to which the agent sends data and alerts as an RFC client.Heartbeat) Availability (CsmTaskCcmsAgent.

x Systems Agent Type SAPCCMSR SAPCCM4X SAPCCMSR –j2ee SAPCM3X 3. In SAP Web AS 6. choose Technical Infrastructure→ Display Topology.CCMS Agents 1. Choose the Display Overview pushbuttons (these pushbuttons and radio buttons are available to you as of SAP Web AS 6. In the Topology group box. 2007 . 2. If you require the corresponding data for remote systems. Destination RFC destination of the monitoring segment SAP AG CCMS Agents: Features. 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]. and Operation Page 98 of 115 January 15. such as SAP_CCMS_HostA_ABC_33_X. or call transaction RZ21.20. first choose System Overview (SAP Web AS 6.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. To avoid this. choose one of the following radio buttons: Radio Button Agents for Local System Agents for Remote Systems Agents for 3.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. By default. the Java segment has the suffix _X. and then choose the CCMS Agents tab page and the desired agent type). it has the name structure SAP_CCMS_<Name of the SAP Instance> or SAP_CCMS_<Host Name> for agents for the local system.4. choose Tools → CCMS → Configuration → Alert Monitor. From the SAP Easy Access Menu.10: Monitored Remote SAP Systems tab page) and choose the desired system by double clicking it. 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). 6. Installation.

2007 .Status or Segment Status Meaning Status of the monitoring segment or communication status from the point of view of the local system. This column is only relevant for the agent SAPCCMSR with the j2ee Option. This shows that the CCMS agent is registered with the local system. n/a is entered here. another instance automatically takes over this task if the original instance is no longer available. 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.CCMS Agents Column Comm. SAP AG CCMS Agents: Features. in the case of the Test Connection command). 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]). J2EE Customizing Destination This column contains an RFC destination to the J2EE Engine that the agent is monitoring.FAIL If an RFC call fails (for example. Therefore. With the CCMS agent SAPCCM4X (tab page Agents for Remote SAP Systems). In running operation. The possibilities for status are: • • • • ONLINE OFFLINE SHUTDOWN COMM. the system displays COMM. and Operation Page 99 of 115 January 15.FAIL. for all other agents. Note that directly after the registration of a CCMS agent. these administrative tasks are performed instance-independently by jobs. It is first the instance with which the agent registered. This column can also have the entry REMOTE SYSTEM when Registering with Multiple Central Monitoring Systems [page 89]. the entry REMOTE SYSTEM is only displayed after the first run of a synchronization job after a maximum of an hour. but another system is the primary monitoring system. Installation. the column title is Responsible System in this case. the system sets the status to ONLINE again. After a successful RFC call.

such as the RFC destinations and the entries in the System Component Repository. since this command applies for all agents. since. 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. Deregister Agent Deletes all entries for the selected CCMS agent in the relevant tables. To display the contents of a file. if the call is successful. choose the file by double clicking it. the system sets the status to ONLINE. Installation.CCMS Agents 6. If the RFC call is not successful. 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. Working Directory You can display all files in the working directory of the agent. This command is only available in change mode.3 Commands in the Topology Display In addition to the purely display functions. 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. which you start by choosing the Display ↔ Change pushbutton ( ). select the desired agent and then choose this pushbutton. for example. use this function primarily to remove incorrect entries and inconsistencies after changes to the system landscape. Instead. 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 system sets the status to SHUTDOWN.4. and Operation Page 100 of 115 January 15. irrespective of the selected tab page) SAP AG CCMS Agents: Features. To do this. 2007 . This function should not replace the deregistration with the agent itself (see Controlling the CCMS Agents [page 102]). The of the Agent system displays an ALV Grid Control with the files from the directory. The previous primary systems then become secondary systems (the button is in the toolbar at the top of the screen. Deregister Agent does not stop the agent. the following commands are also available to you as pushbuttons in the ALV Grid Control.

FAIL or SHUTDOWN manually. This can take a few seconds.CCMS Agents Command Change Comm. choose OFFLINE. The buttons Agent Registration. 2007 . Installation. Then refresh the display until the changes are visible in the display. and Adopt All Agents are only displayed if there are agents that are registered with multiple central monitoring systems.Status or Segment Status (change mode) Description If you no longer want to display the data from the agent in the monitoring architecture. It remains in this status until you set it to ONLINE again. and Operation Page 101 of 115 January 15. SAP AG CCMS Agents: Features. Adopt Agent. You should also ensure that the functions to switch the primary system are performed in the agent itself. Do not set COMM.

and Operation Page 102 of 115 January 15. the start file CSMCONF is deleted during the deregistration. 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.1. Installation. If the central monitoring system (CEN) with which the agent is registered has a release status of at least SAP Web AS 6. specify the parameter –U. 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. 7. 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 CCMS Agents: Features. 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).20. the system will prompt your for the logon data for CEN during the uninstall. Deregistering CCMS Agents To deregister a CCMS agent. 2007 . If you specified a profile path during registration.CCMS Agents 7.

Likewise. • Registering and Deregistering an Agent Without Installing/Uninstalling a Service (Microsoft Windows Only) Under Microsoft Windows. You should set the agent to Offline in the topology display to avoid problems in the system. you receive additional information about the release of the central monitoring SAP AG CCMS Agents: Features. for example. we recommend that you stop and restart the agent by stopping and restarting the service of the same name. In the case of a release status below SAP Web AS 6. for agent SAPCCMSR. use the option –DCCMS. 2007 .2. Displaying the Status of a CCMS Agent The status of a CCMS agent displays its working directory and the configuration directory. stop the CCMS agents SAPCCM4X and SAPCCMSR –j2ee. you would use the command sapccmsr –stop [pf=<profile path>]. This option is available as of Patch Collection 2005/5. To restart the agent later. if you want to upgrade the corresponding monitored system.INI: Configuration File for the CCMS Agents [page 29]). therefore. if the agent is running.INI configuration file (see SAPCCMSR. and Operation Page 103 of 115 January 15. It is primarily useful.20. Follow the procedure below for your operating system platform: • Under UNIX. you can display the SCR by choosing Technical Infrastructure → System Repository → Display in transaction RZ21.3.CCMS Agents • Entry in the System Component Repository (SCR). Installation. as this file is only read when the agent is started. Restart the agents again after finishing the upgrade. if you need to register or deregister an agent using a user that does not have administrator authorization on the relevant host. 7. 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. you can stop the CCMS agent using the option -stop. Under Microsoft Windows NT. 7. Starting and Stopping CCMS Agents You should always stop and restart a CCMS agent if you have made changes to its SAPCCMSR. these entries are not deleted.

multithreaded. SAP AG CCMS Agents: Features. To do this.2002 systemid 560 (PC with Windows NT) relno 6200 Patch text patch collection 2003/2.0 2195 Service Pack 2 Intel 80686 You can read the version from the release number (relno) and the patch number (patchno). Installation. with the agent SAPCCMSR): >sapccmsr –v CCMS version 20010925.CCMS Agents system in which the agent is registered. Non-Unicode compiled at Sep 17.4. 2007 . Patch text specifies the Patch Collection. 32 bit. 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. OSS note 584136 patchno 344 intno 20023800 running on P57373 Windows NT 5. call the agent with the option –status (for example. see SAP Note 202591. and Operation Page 104 of 115 January 15. Displaying the Version of a CCMS Agent Call the agent with the option –v (for example. For information about which collection contains which changes. The line running on also contains the operating system on which the agent is currently running. 32 bit * Process Id 28807 * relno 6200 * patchno 45 * intno 20020600 ***************************************************** EXITING with code 0 7.

This is usually due to incorrect configuration that applies to all RFC client programs. and Operation Page 105 of 115 January 15. which is part of the Remote Function Call Development Kit (RFC SDK). Although a template for log file monitoring exists and is entered in SAPCCMSR.CCMS Agents 8. 2007 . A service under Microsoft Windows NT or Windows 2000 always starts in the System32 directory. use the test program SAPINFO. and reregister it. the system does not display any subtrees for log files in transaction RZ20 of the central system. Questions and Answers SAP has possible solutions to the following errors that can occur when you are using the CCMS agents: 8. you must always specify these with a full path. You can use this program to check the connection to the central monitoring system without logon and password (see also SAP Note 42692). the service does not start or terminates immediately (Microsoft Windows NT or Windows 2000). Deregister the service (for example. The line containing the period must contain no other characters.). During the installation of the SAPCCMSR agent. Installation. you should first test the RFC connection to the central monitoring system. you receive an error message saying that the system cannot access a directory or that it does not exist (Microsoft Windows NT only). before you install SAPCCMSR. Therefore. You must have created the working directory \\<host>\saploc\prfclog\sapccmsr and have released the directory saploc. The agent registers error-free as a service. General Logon to the central monitoring system does not work during registration of the agent. This package is on every presentation CD. So that the system can find any existing profile files. specifying the profile with the complete path.INI. with sapccm4x –U). To do this. You should also check in the log file of the agent which files it is actually monitoring. However.1. You must end the LOGFILE_TEMPLATE with a period (. SAP AG CCMS Agents: Features. irrespective of the agent.

uninstall the CCMS agent and reinstall it.Restart the service (Microsoft Windows NT or Windows 2000). the agent is not used to collect data.When sending problem messages and queries to SAP. If you cannot solve a problem. . Installation.2.<no> in transaction SM59 of the central system. . 8.If the problem persists. . . . .Check the log file of the CCMS agent in its working directory. Perform a connection test in the transaction.Check the RFC destination of the CCMS agent in transaction SM59 in the central system. we recommend the following procedure: .Load the newest version of the CCMS agent.Check in the operating system whether the process is active. 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.Check the RFC destination SAPCCM4X. and Operation Page 106 of 115 January 15. . .Check the log files in the working directory of the CCMS agent for possible error causes.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 CCMS Agents: Features. SAPCCMSR/SAPCM3X Where is the working directory for sapccmsr. always send all log files and configuration files from the working directory of the CCMS agent.CCMS Agents After a restart.<host>. 2007 .

Connection test OK? yes no On host: is process running? yes no Analysis in CEN: Log file sapccmsr. choose Agents for Remote Systems and Display Overview. and choose Test Connection.log by double-clicking it. SAPCCMSR –j2ee Notes: Symptom: Monitoring data for a J2EE Engine are visible in the VA.log in CEN by choosing the Agent Working Directory button and then choose sapccmsr. Now select the desired agent. 2007 .log Analysis on the Host: Log file sapccmsr. Pay particular attention to errors connected to Gateway and RFC.3. Installation. but not in the CCMS The connection test is performed as follows: Call transaction RZ21 in CEN.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 CCMS Agents: Features.CCMS Agents 8. Analyze sapccmsr. and Operation Page 107 of 115 January 15.

05.05.2002 10:56:19 uw1042_ C11_01. SAPCCM4X Where is the working directory for sapccmsr.04.04.2002 Available 05. agent attached to key 13 (pool 10) 10:56:50 .05.04.Periods when the agent is connected to a shared memory segment .2002 Unavailable 05.CCMS Agents 8. agent attached to key 13 (pool 10) 10:52:56 .04.2002 10:52:56 uw1042_ C11_01.04. there is the log file available.04.log containing the following information: . agent attached to key 13 (pool 10) 10:51:25 .04.04.4.2002 10:56:29 uw1042_ C11_01.2002 11:16:20 SAP AG CCMS Agents: Features.Periods when the monitored instance is available Example (the instance was started after the agent and was then restarted again): Unavailable 05.2002 10:50:55 uw1042_ C11_01.04.05. and Operation Page 108 of 115 January 15. agent not attached 10:51:05 .04.05.2002 Available 05.05.04.04.2002 10:52:46 uw1042_ C11_01. 2007 .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.2002 Available 05.2002 10:51:05 uw1042_ C11_01. agent not attached 10:53:18 .05.2002 Unavailable 05. Installation. agent not attached 10:56:29 . agent not attached 10:50:14 .04.04.2002 Available 05.2002 uw1042_C11_01.

and choose the document SAPOSCOL: Properties. and Operation Start the SAP Service Marketplace.sap. call the SAP Library and choose SAP NetWeaver → Solution Life Cycle Management → Solution Monitoring → Monitoring in the CCMS → The Alert Monitor. SAP Service Marketplace and SAP Library If you want to follow the links to the following documents and SAP Notes. Choose the document Supportability Setup Guide . Registration. and go to the System Monitoring and Alert Management area (http://service. see: [Support] Supportability Setup Guide for SAP NetWeaver 04 SP Stack 04 Start the SAP Service Marketplace.com/nw04operation). Installation. [StdMon] Predefined Monitors for the Alert Monitor Start the SAP Service Marketplace. you require a valid password for the SAP Service Marketplace For more information. and go to the System Monitoring and Alert Management area (http://service.com/monitoring).sap.sap.com/monitoring). Choose Education & Workshops. Installation. Additional Information 9. Installation. Choose Media Library → Documentation. [AutoRea] Predefined Monitors for the Alert Monitor Start the SAP Service Marketplace. [AlMon] Online documentation for the Alert Monitor To view this documentation.com/monitoring). and Operation Page 109 of 115 January 15. and go to the SAP NetWeaver 04 Operations area (http://service.com/monitoring).SAP NetWeaver 04 Stack 04 from the list. and Customizing of CCMS Agents from the list (Direct Link).sap. [SAPOsCol] SAPOSCOL: Properties. and Customizing of CCMS Agents Start the SAP Service Marketplace.CCMS Agents 9. 2007 . and then choose Predefined Auto-Reactions for the Alert Monitor from the list (Direct Link). and then choose Installation. and go to the System Monitoring and Alert Management area (http://service. Choose Media Library SAP AG CCMS Agents: Features.sap. Registration. and Operation from the list (Direct Link).1. and go to the System Monitoring and Alert Management area (http://service. [Tutor] Installation. Choose Media Library → Documentation.

2.sap. Installation. Choose Developers´ Zone. 135503 CCMS Monitoring Architecture: Meaning of profile parameters The profile parameters of the monitoring architecture are explained in this SAP Note. [Avail] Availability Monitoring and CCMSPING Start the SAP Service Marketplace. Choose Media Library → Documentation. 202591 CCMS Monitoring Kernel Patches (composite SAP Note) This SAP Note describes the changes to the monitoring architecture through the various patch collections. Use the test tool sapinfo described in this SAP Note for testing. in addition to basic information about the CCMS agents. and go to the System Monitoring and Alert Management area (http://service.sap.com/monitoring). and choose the document Availability Monitoring and CCMSPING (Direct Link). 209834 CCMS agent technology (composite SAP Note) This SAP Note contains. [JMon] Java Monitoring API – Properties and Installation Start the SAP Service Marketplace. and choose the document Java Monitoring API – Properties and Installation (Direct Link). 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.CCMS Agents → Documentation.com/monitoring). known problems that can occur in connection with the CCMS agents. alert/ALERTS. SAP AG CCMS Agents: Features. and go to the System Monitoring and Alert Management area (http://service. 2007 . and choose the document Predefined Monitors from the list (Direct Link). [GRMG] Instrumenting Components for Monitoring with GRMG Start the SAP Service Marketplace.sap. 9. alert/MTTREE.com/monitoring). and alert/PERFHIST. and their solutions. Choose Developers´ Zone. These are: alert/MONI_SEGM_SIZE. and choose the document Instrumenting Components for Monitoring with GRMG (Direct Link). and go to the System Monitoring and Alert Management area (http://service. and Operation Page 110 of 115 January 15.

and Operation Page 111 of 115 January 15. This SAP Note describes the prerequisites for this scenario. This SAP Note describes the prerequisites for this. 502461 CRM: CCMS agent PlugIn for IPC You want to include the IPC Server component in the CCMS monitoring architecture. 498179 Enable Monitoring of InQMy/SAP J2EE Engine You want to include the SAP J2EE Engine in the CCMS monitoring architecture. 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. 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. SAP AG CCMS Agents: Features. 308061 CCMS monitoring architecture: monitor 3x systems The CCMS monitoring architecture is available as of SAP Basis 4.com components that are not described in the standard documentation (see SAP Service Marketplace and SAP Library [page 109]). 420213 Composite SAP Note: Central monitoring of mySAP. In this way. This SAP Note shows how you can do this with the SAPCCMSR agent and the appropriate PlugIn.0D using the monitoring architecture. you can define central auto-reaction methods in the monitoring architecture in the context of the central monitoring of mySAP. Installation.com components.6C. in which the alert occurs.com components This SAP Note provides current information about monitoring mySAP.10. This SAP Note shows how you can do this with the SAPCCMSR agent.0B. with which the SAP Service Marketplace files are compressed. but rather in the central monitoring system.CCMS Agents 212876 The new archiving tool SAPCAR This SAP Note explains the operation of the archiving tool SAPCAR. 429265 CCMS monitoring architecture: Central auto-reaction As of SAP Web AS 6. it is possible for reactions to events that occur in monitored components to be performed immediately in a central location. 2007 . you can also monitor systems as of SAP Basis 3. However. The auto-reaction methods are not started in the system. This SAP Note explains the procedure required to do this.

20 or a host on which SAP standalone components/non-SAP components (such as a database) are running. 734247 Registering CCMS agents for SAP Web AS Java as of 6. the monitored J2EE instance. and Operation Page 112 of 115 January 15. 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. if appropriate. Installation. as an attachment. This SAP Note explains the configuration required to do this. you must enter a large amount of information about the CEN. SAP AG CCMS Agents: Features.40 SP 1. the CCMS agent SAPCCMSR and the operating system collector SAPOSCOL must be installed and configured on the TREX host. 730629 CCMS agents: Java interface for registration You want to register the CCMS agent SAPCCMSR. 2007 . This SAP Note contains. and. If a search pattern is found. To do this. 516181 SAP Expert Monitor for EMC (SEME) You want to monitor cached disk subsystems.30 using a central monitoring system (CEN) as of SAP Web AS 6. 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. a Java tool to simplify the registration. the connection to it. that is. This SAP Note describes the steps on the TREX host. you can use CCMS agents to monitor log files. During the registration of the agent. the monitoring architecture displays a message or an alert. to search through certain files for one or more word patterns. The monitored object can be an instance of a J2EE Engine with a release status of SAP Web AS 6. 522453 RZ20: Monitoring operating system data This SAP Note describes how you can configure the collection of operating system data in the monitoring architecture.30 You want to register the CCMS agent SAPCCMSR. 704349 Activating the CCMS monitoring for TREX TREX can provide monitoring data for the CCMS using the agent technology. to centrally monitor an instance of a J2EE Engine as of SAP Web AS 6.CCMS Agents 535199 CCMS agents: Monitoring log files In the context of monitoring systems and system landscapes. 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.

Please make sure that you read all the parts. SAP AG CCMS Agents: Features. the project was based at UC Davis. to the project since 2001. This SAP Note contains.3. 902460 CCMS: Agent displays no J2EE data in RZ20 A SAPCCMSR CCMS agent has been installed for an SAP NetWeaver 2004s (7. and provides data for OS monitoring and log file monitoring. listed in 3 separate parts below. Code has been contributed to this project by many people over the years it has been in development.00) J2EE instance and registered with a central monitoring system. covering all derivative work done since then. and the monitored J2EE instance. 809007 CCMS Agents and Kernel: Patches 2005 This SAP Note describes the changes to the monitoring architecture through the patch collections during 2005.CCMS Agents During the registration of the agent. 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. Inc hold the copyright on behalf of the wider Net-SNMP community. 2007 . An additional copyright section has been added as Part 3 below also under a BSD license for the work contributed by Cambridge Broadband Ltd. a Java tool to simplify the registration. 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. 914721 CCMS Agents and Kernel: Patches 2006 This SAP Note describes the changes to the monitoring architecture through the patch collections during 2006. no monitoring data is displayed for the J2EE Engine. Up until 2001. 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. you must enter a large amount of data about the CEN. and a full list of contributors can be found in the README file under the THANKS section. From 2001 onwards. the project has been based at SourceForge. and the first part covers all code written during this time. since the CCMS Agent Configuration tab page in the Monitoring service of the dispatcher is not displayed. 929635 “CCMS Agent Configuration” tab page is missing Automatic registration of the CCMS agent from the Visual Administrator is not possible. and Networks Associates Technology. and Operation Page 113 of 115 January 15. However. the connection to it. Installation. as an attachment. The CCMS agent is displayed as ONLINE in transaction RZ21.

---. Redistribution and use in source and binary forms. 1992 by Carnegie Mellon University Derivative Work . Inc copyright notice (BSD) ----Copyright (c) 2001-2002.Part 3: Cambridge Broadband Ltd. CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE. PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. Networks Associates Technology. 1998-2000 The Regents of the University of California All Rights Reserved Permission to use.CCMS Agents ---. this list of conditions and the following disclaimer. ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. with or without modification. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES. Redistributions in binary form must reproduce the above copyright notice. INCIDENTAL. IN NO EVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL. EXEMPLARY. copyright notice (BSD) ----Portions of this code are copyright (c) 2001-2002. Redistribution and use in source and binary forms. Neither the name of the Networks Associates Technology. with or without modification. WHETHER IN CONTRACT. this list of conditions and the following disclaimer. this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. copy. INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE. and Operation Page 114 of 115 January 15. SPECIAL. 2007 SAP AG . EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. OR CONSEQUENTIAL DAMAGES (INCLUDING. BUT NOT LIMITED TO. All rights reserved. ---. STRICT LIABILITY. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT.1996. BUT NOT LIMITED TO. OR PROFITS. INDIRECT. provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation. WHETHER IN AN ACTION OF CONTRACT. 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. INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS.Part 2: Networks Associates Technology. are permitted provided that the following conditions are met: • • • Redistributions of source code must retain the above copyright notice. modify and distribute this software and its documentation for any purpose and without fee is hereby granted.Part 1: CMU/UCD copyright notice: (BSD like) ----Copyright 1989. DATA OR PROFITS. Installation. INCLUDING. 1991. NEGLIGENCE OR OTHER TORTIOUS ACTION. Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. Redistributions in binary form must reproduce the above copyright notice. LOSS OF USE. OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE. Cambridge Broadband Ltd. Inc All rights reserved. CCMS Agents: Features. 1998-2000 Copyright 1996. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. are permitted provided that the following conditions are met: • • Redistributions of source code must retain the above copyright notice. DATA.

DATA. THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. BUT NOT LIMITED TO. INCLUDING. 2007 . PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES. WHETHER IN CONTRACT. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT.CCMS Agents • The name of Cambridge Broadband Ltd. OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. SAP AG CCMS Agents: Features. Installation. OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE. STRICT LIABILITY. INDIRECT. EXEMPLARY. INCIDENTAL. OR PROFITS. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ''AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES. SPECIAL. OR CONSEQUENTIAL DAMAGES (INCLUDING. may not be used to endorse or promote products derived from this software without specific prior written permission. EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. LOSS OF USE. and Operation Page 115 of 115 January 15. BUT NOT LIMITED TO.