CCMS Agents: Features, Installation, and Operation

Transcription

1 Version 4.7 (Patch Collection 2006/5) January 15, 2007 CCMS Agents: Features, Installation, and Operation SAP AG Neurottstr. 16 D Walldorf Page 1 of 115

2 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 Server TM 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. Page 2 of 115

3 Contents 0. Structure and Use of this Document Introduction Functional Principle of the CCMS Agents SAPCCMSR SAPCCMSR with Option j2ee Examples Monitored System with no ABAP Instances Monitored System with J2EE and ABAP Instances Monitored System with Java and ABAP Instances, and a CEN SAPCCM4X SAPCM3X Communication Installing CCMS Agents for NetWeaver Components Installing an Agent on an ABAP Instance Installing an Agent on a Java Instance (Java Standalone System) Installing an Agent on a Java Instance (Double-Stack System) Installing an Agent on a SAP Web AS 6.20 Java Instance/Other Hosts Installing and Registering the CCMS Agents for Experts Prerequisites for the Installation Downloading the CCMS Agents Copying the CCMS Agent to the Desired Directory Creating the Required Configuration Files Configuration File for Monitoring Log Files Configuration File for Monitoring Operating System Data Profile File of the CCMS Agents Structure of the Profile File Example Profile File SAPCCMSR.INI: Configuration File for the CCMS Agents Structure of the SAPCCMSR.INI Configuration File Example SAPSSMSR.INI Agent Configuration File Registering the CCMS Agents...32 Page 3 of 115

4 4.5.1 Creating the CSMREG User Automatically Creating the CSMCONF Start File Registration with the Agent Registration Tool Registering the CCMS Agents in Dialog Alternative: Dialog-Free Registration of CCMS Agents Structure of the CSMCONF Start File Example CSMCONF Start File Registering SAPCCMS with the Option -j2ee Registering SAPCCMS with the Option -j2ee in Dialog Dialog-Free Registration of SAPCCMS with the Option -j2ee Creating Customizing Destination for SAPCCMSR j2ee Starting the Agent SAPCCM4X: Creating the RFC Connections Working Directory and Log Files of the CCMS Agents Working Directory Log Files Trace Files Advanced Functions of the CCMS Agents Monitoring Log Files Types of Monitored Log Files Structure of the Log File Template of the Log File Agent General Settings for the Monitored Log Files Monitored Search Pattern in the Monitored Log Files Search Pattern to be Output in the Monitored Log Files Example Log File Templates Oracle Alert Log Trace Files of the SAP Work Processes Log File of the SAPCCMSR CCMS Agent Log File for the Backups of an Oracle Database Display for Log File Monitoring in the Alert Monitor Setting Up the Sending and Receiving of SNMP Traps Using CCMS Agents Adjusting the Configuration File for Sending SNMP Traps Adjusting the Configuration File for Receiving SNMP Traps Displaying Received SNMP Traps in the Alert Monitor Page 4 of 115

5 5.3. Event Log Monitoring with CCMS Agents Structure of the Event Log Template Displaying the Event Log Monitoring in the Alert Monitor Monitoring Operating System Data with CCMS Agents Operating System Data Displayed in the Alert Monitor Configuring the Monitoring of Operating System Data Structure of the SAPOSCOL Filter File oscolfile.txt Example SAPOSCOL Filter File oscolfile.txt Monitoring Selected Processes Alert Logging for CCMS Agents Activating the Alert Logging Structure of the Alert Log File Example Alert Log File Displaying File Contents in the Alert Monitor Example of Defining Displayable File Contents (SAPCCMSR.INI) Assigning the Required Analysis Method Transferring GRMG Customizing Files to CEN Including Additional Functions in CCMS Agents Registering with Multiple Central Monitoring Systems Start File CSMCONF with Multiple Central Monitoring Systems Monitoring Multiple Systems with an Identical System ID Transferring Distributed Statistics Records with CCMS Agents Displaying Agent Data in the Central Monitoring System Monitoring Contexts of the CCMS Agents in the Monitoring System Creating CCMS Agent Monitors in the Central Monitoring System SAPCM3X: Creating a Rule-Based Monitor SAPCCMSR: Creating a Rule-Based Monitor Self-Monitoring of the CCMS Agents Displaying Agent Data in the Topology Display Calling the Display of Agent Data in the Topology Display Data Displayed About CCMS Agents Commands in the Topology Display Controlling the CCMS Agents Page 5 of 115

6 7.1. Deregistering CCMS Agents Starting and Stopping CCMS Agents Displaying the Status of a CCMS Agent Displaying the Version of a CCMS Agent Questions and Answers General SAPCCMSR/SAPCM3X SAPCCMSR j2ee SAPCCM4X Additional Information SAP Service Marketplace and SAP Library Important SAP Notes About CCMS Agents Copyright Page 6 of 115

7 0. Structure and Use of this Document The sections of this document cover the following: Sections 1 and 2 These sections contain an introduction to the meaning and functions of the CCMS agents. Section 3 This section contains the installation and registration of CCMS agents for the most important monitored components. If you want to use CCMS agents to monitor software components in the context of a standard installation, follow the procedures in this section. Section 4 This section describes the installation and registration of CCMS agents in general terms. In most cases, you will not require this information, since the procedures in section 3 will be sufficient. However, since many of the advanced functions of the CCMS agents (section 5) have a direct influence on the installation and registration of the agents, you should work through this section if you want to individually tailor the advanced functions of the CCMS agents. Section 5 This section describes how you can use the advanced functions of the CCMS agents for your individual monitoring tasks. These include, for example, the monitoring of log files, sending and receiving SNMP traps, monitoring processes, or displaying the contents of files. Section 6 This section describes how monitoring information that is transferred to the central monitoring system CEN using CCMS agents is displayed in CEN. It also introduces the most important functions for monitoring and controlling CCMS agents from CEN. Section 7 This section contains the functions for controlling CCMS agents locally. Section 8 This section contains a summary of possible problems and their solutions in the context of CCMS agents. Section 9 This section contains the most important additional information about CCMS agents. Page 7 of 115

8 1. Introduction The monitoring architecture provides an infrastructure for monitoring your IT environment and its components. Monitoring data is stored in the shared memory of every server with a running SAP instance or a running agent. Read and write access from the central monitoring system is possible in two different ways: Using a defined ABAP interface, in the case of an SAP instance Using the CCMS agent, in the case of any server on which the agent is installed and active CCMS agents are independent processes with an interface through RFC to a central monitoring system and an interface to the shared memory. They therefore allow you to: Include SAP components that do not have an ABAP interface, such as the J2EE Engine or the Internet Transaction Server (ITS) Include components that are not part of the SAP environment Make available an alternative connection route to a shared memory segment Optimize performance when reading and writing monitoring attributes and alerts, by using the push technology Connect to a shared memory segment without requiring a free work process Agents also make entirely new monitoring functions possible within the monitoring architecture: You can monitor any log files. You can monitor processes at operating system level. The actual monitoring is performed using the operating system collector SAPOSCOL. For detailed information about it, see [SAPOsCol]. You can create central auto-reactions in which an auto-reaction method is started in the central monitoring system as a reaction to an alert in a monitored system. For detailed information about it, see [AutoRea]. Agents monitor network data, including: - The configuration of the network environment, such as an interface or Domain Name System (DNS) - Network metrics, such as the length of time taken for a DNS address resolution Page 8 of 115

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

10 2.2. SAPCCMSR with Option j2ee The functional principle of SAPCCMSR has been extended in case the SAPCCMSR CCMS agent is monitoring a J2EE Engine. In a case of this type, it must be possible that the monitoring segment of the SAPCCMSR agent does not belong to the central monitoring system. This is achieved by extending the system term to include Java components (such as J2EE Cluster). The SAPCCMSR agent with the -j2ee option exists for this purpose. To use SAPCCMSR with option j2ee, you need a central monitoring system as of SAP Web AS 6.40 Support Package 1. The monitored J2EE Instance requires at least SAP Web AS 6.30 Support Package 4. It is easier to understand the other steps if you use the following analogies: ABAP ABAP System Application server Work process Java J2EE Cluster J2EE Engine Virtual Machine (VM) A system is no longer only a quantity of classical application servers with an ABAP runtime environment, but simply a number of associated components that have a common system name. Combinations of ABAP instances and Java instances can also create a system, if all of these parts are combined under one system ID. You specify the system ID and the system number of the monitored Java instance during the registration of the agent using the instance's profile (see Profile File of the CCMS Agents [page 27]). When monitoring, it should be possible to display the data for the ABAP instances and the Java instances of the same system in a central CCMS under the system ID of the monitored system. As far as possible, a Java instance should not be different from an ABAP instance; it should also be possible to monitor all instances with the same system ID locally as one system unit Examples Monitored System with no ABAP Instances SAPCCMSR monitors an instance of a Java system and registers itself with a central system CEN. The connection to CEN is also the primary RFC connection. Page 10 of 115

11 Monitored System ABC (with no ABAP Engines) Host A J2EE Engine HostA_ABC_33 Host B sapccmsr J2EE Engine -j2ee HostA_ABC_33 Host C sapccmsr J2EE Engine -j2ee HostC_ABC_33 sapccmsr -j2ee Central Monitoring System CEN Host D CCMS Alert Monitor ABC HostA_ABC_33 HostB_ABC_33 HostC_ABC_33 Topology Display Agents for Remote SAP Systems System Destination ABC SAPCCMSR.HostA.33 ABC SAPCCMSR.HostB.33 ABC SAPCCMSR.HostC.33 CEN is the primary central system in each case Monitored System with J2EE and ABAP Instances SAPCCMSR monitors an instance of a system in which there is still at least one ABAP instance. In this case, the agent must be primarily registered with the local system, so that the system can be monitored locally as one unit. System ABC (with J2EE and ABAP Engines) Host A J2EE Engine HostC_ABC_33 Host B ABAP Engine HostC_ABC_33 J2EE Engine ABAP Engine HostC_ABC_33 sapccmsr Host C HostC_ABC_33 -j2ee J2EE Engine ABAP Engine HostC_ABC_33 sapccmsr primäre RFC-Verbindung HostC_ABC_33 -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 Segment Name SAPCCMSR.HostA.33 SAP_CCMS_HostA_ABC_33_X SAPCCMSR.HostB.33 SAP_CCMS_HostB_ABC_33_X SAPCCMSR.HostC.33 SAP_CCMS_HostC_ABC_33_X Page 11 of 115

12 Monitored System with Java and ABAP Instances, and a CEN In addition to the case described above, the local system, to which the Java instance belongs, can be monitored by a central monitoring system CEN: System ABC (with Java and ABAP Engines) Host A J2EE Engine HostC_ABC_33 Host B ABAP Engine HostC_ABC_33 J2EE Engine ABAP Engine HostC_ABC_33 sapccmsr Host C HostC_ABC_33 -j2ee J2EE Engine ABAP Engine HostC_ABC_33 sapccmsr primäre RFC-Verbindung HostC_ABC_33 -j2ee sapccmsr primäre RFC-Verbindung -j2ee Primary Central System Secondary Central System Central Monitoring System CEN Local Monitoring System ABC CCMS Host D CCMS Alert Monitor ABC Alert Monitor ABC HostA_ABC_33 HostB_ABC_33 HostC_ABC_33 HostA_ABC_33 HostB_ABC_33 HostC_ABC_33 Topology Display Agents for the Local SAP System ABC Destination Segmen Name SAPCCMSR.HostA.33 SAP_CCMS_HostA_ABC_33_X SAPCCMSR.HostB.33 SAP_CCMS_HostB_ABC_33_X SAPCCMSR.HostC.33 SAP_CCMS_HostC_ABC_33_X Topology Display Agents for Remote SAP Systems System Destination ABC SAPCCMSR.HostA.33 ABC SAPCCMSR.HostB.33 ABC SAPCCMSR.HostC SAPCCM4X This agent improves the monitoring of ABAP instances with SAP Basis 4.X or higher. The central monitoring system must have a release status of at least SAP Basis 4.6C. This agent provides an alternative connection route to the monitoring information in the shared memory of an ABAP instance. As this alternative connection method does not require a free work process, the access method is independent of error states of the SAP instance and is therefore more robust. Systems as of SAP Basis 4.0 have their own CCMS monitoring architecture runtime environment. This means that they have their own monitoring segment in the shared memory area of the running system. After its installation, the SAPCCM4X agent attempts to attach itself to and to work with this monitoring segment in shared memory when it is started. Page 12 of 115

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

14 As an RFC server, it provides access to the data in the monitoring segment. This access is, for example, used in transaction RZ20. The agent automatically creates the local configuration files and the RFC destination in the central system during its registration. You can set the frequency of the query by the monitoring architecture in the Alert Monitor. To do this, call transaction RZ20, select a node in the desired monitor, choose Properties and, on the Methods tab page, correct the value for Start the data collection method every. The maximum frequency of this query depends on whether the underlying program is an ABAP program or a C program. In the case of ABAP programs, the maximum frequency is five minutes, while the maximum frequency for C programs (and therefore for CCMS agents) is one minute. As an RFC client, it independently sends alerts and values for the monitoring attributes to the central monitoring SAP System (push technology). This data is then stored in a cache there to allow the system to display it more quickly or triggers central auto-reaction methods there. This improves performance as the central monitoring system then no longer needs to periodically query the agents. The central monitoring system must have a release status of at least SAP Web AS 6.10 for automatic reporting of alerts. As of this release, activation of the push technology is mandatory. As of SAP Web AS 6.20, the agents also automatically report monitoring attribute values. All CCMS agents can process several tasks simultaneously (multi-thread procedure). This means that they can simultaneously: Automatically collect data Process requests as an RFC server Send data to the central system as an RFC client Page 14 of 115

15 3. Installing CCMS Agents for NetWeaver Components The sections of this process describe how you can install and register the appropriate CCMS agent in the context of a standard installation of SAP NetWeaver components [Support, Tutor]. These descriptions therefore extend the process Installing and Registering the CCMS Agents for Experts [page 24], which describes the installation and registration of CCMS agents in general terms, and which explains all individual settings. All Possible Central Monitoring Scenarios with CCMS Agents C11 SAPCCMSR SAPCCM4X Central Instance SAPCCMSR Java Addin SAPCCM4X Dialog Instance SAPCCMSR Java Addin Central Monitoring System CEN (6.40+ ABAP) Java Addin External TREX, BC, Third Party, etc. SAPCCMSR 6.20 J2EE 6.20 J2EE SAP NetWeaver 04 Dual Stack SAP Web AS 6.20 Java standalone C12 J2E SAPCCM4X Central Instance SAPCCM4X Dialog Instance SAPCCMSR Dialog Instance SAPCCMSR 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 Page 15 of 115

16 Prerequisites The following prerequisites must be fulfilled in every case for the installation and registration of a CCMS agent: You have a central monitoring system (CEN). If possible, reserve a separate SAP system for monitoring and system management. Do not use a production system for this, to avoid unnecessary load on the system. If you are using a separate SAP system, you can easily keep this at the newest status with regard to release or Support Package status, and profit from the newest developments in the areas of monitoring and system management. There is a CSMREG user in CEN. If this is not yet the case, create the user by proceeding as follows (see also Creating the CSMREG User [page 33]): a. In CEN, call transaction RZ21 and choose Technical Infrastructure Configure Central System Create CSMREG User. b. Enter and reenter any password for this user, and confirm your entries by choosing (Create CSMREG). During the registration of the agent, you require the connection data from the agent to CEN. We recommend that you generate this data in a CSMCONF file in CEN before the registration. To do this, proceed as follows: a. In CEN, call transaction RZ21, and choose Technical Infrastructure Configure Central System Create CSMCONF Start File for Agents. b. Save the file at a location that is centrally available, since you require the file for all agent registrations. You have the required executables for the CCMS agents. To download these, proceed as described in Downloading the CCMS Agents [page 25]. Process To install a CCMS agent for one of the following components, follow the description under the appropriate link: Installing an Agent on an ABAP Instance [page 17] Installing an Agent on a Java Instance (Java Standalone System) [page 18] Installing an Agent on a Java Instance (Double-Stack System) [page 20] Installing an Agent on a SAP Web AS 6.20 Java Instance/Other Hosts [page 22] If you want to monitor a system with CCMS agents, you need an agent for every instance of the system (central instance and potential dialog instances). For Java standalone systems and double-stack systems, this is automatically insured. In the case Page 16 of 115

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

18 <profile path> specifies the instance profile of the monitored instance. By default, this is: Windows:[drive]:\usr\sap\<SysID>\SYS\profile\ <SysID>_<Name of the instance directory>_<host> UNIX: /usr/sap/<sysid>/sys/profile/ <SysID>_<Name of the instance directory>_<host> 5. During the registration, the system displays specifications from the CSMCONF to you again for confirmation. Confirm the specifications by pressing theenter key in each case. You only need to enter two parameters yourself: The password for the administration user in CEN, under which you created the CSMCONF file. The password for the CSMREG user 6. Under UNIX, you must ensure yourself that SAPCCM4X is automatically started again when the host is restarted. To do this, enter the following command in the inittab (/etc/inittab): /usr/sap/<sysid>/sys/exe/run/sapccm4x -DCCMS pf=<profile path> Result You have set up an additional connection route between the monitored ABAP instance and CEN using the CCMS agent SAPCCM4X Installing an Agent on a Java Instance (Java Standalone System) The monitoring data for the J2EE Engine is transferred to CEN using the CCMS agent SAPCCMSR. The agent is part of the installation package of the Engine; You only need to register the agent once for each Java system with CEN and to start the agent. Note that this description applies only for monitored J2EE Engines as of SAP NetWeaver 04 SP Stack 12. For J2EE Engines with a release status of SAP Web AS 6.20, follow the procedure described under Installing an Agent on a SAP Web AS 6.20 Java Instance/Other Hosts [page 22]. If you want to use the agent to monitor a J2EE Engine of a double-stack system (ABAP/Java), follow the procedure described under Installing an Agent on a Java Instance (Double-Stack System) [page 20]. If problems occur during the registration of the agent on a Microsoft Windows platform, proceed as described in SAP Note Page 18 of 115

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

20 9. Under UNIX, the agent is automatically started by thestartsap script when you start the J2EE Engine. Under Microsoft Windows, the agent is entered as a service during the registration, and is automatically started during a restart of the host. As of SAP NetWeaver 2004s, however, you need to start the associated service (which was created during the installation of the J2EE Engine) yourself. To do this, on the Microsoft Windows host on which the agent is running, choose Start Settings Control Panel Administrative Tools Services, and choose the service SAPCCMSR.<Instance No.> by double-clicking it. Set the Start Type to Automatic, and choose Start. Result The J2EE Engine is now registered with CEN; you can see the corresponding monitoring data in the Alert Monitor in CEN. The Customizing destination has also been automatically created for all Java instances (only if you have left the check box enable CCMS Customizing marked), so that you can also change the threshold values for the monitoring data from the Alert Monitor (see Creating Customizing Destination for SAPCCMSR j2ee [page 43]) Installing an Agent on a Java Instance (Double-Stack System) The monitoring data for the J2EE Engine is transferred to CEN using the SAPCCMSR CCMS agent. The agent is part of the installation package of the Engine; you only need to register the agent for the relevant agent with CEN and to start the agent. This procedure describes the registration of a CCMS agent that is to monitor a J2EE Engine that is part of a double-stack system of ABAP and Java instances. In the case of a double-stack system, the agent must be registered with two systems: primarily with the local ABAP system, and secondarily with CEN. You only need to register and start the agent once for each system. Note that this description applies only for monitored J2EE Engines as of SAP NetWeaver 04 SP Stack 12. For J2EE Engines with a release status of SAP Web AS 6.20, proceed as described under Installing an Agent on a SAP Web AS 6.20 Java Instance/Other Hosts [page 22]. If you want to monitor a J2EE Engine of a standalone Java system with the agent, proceed as described under Installing an Agent on a Java Instance (Java Standalone System) [page 18]. If problems occur during the registration of the agent on a Microsoft Windows platform, proceed as described in SAP Note Page 20 of 115

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

22 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 thestartsap 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]) 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 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 (Double- Stack System) [page 20]. If you want to monitor a TREX host with the agent, proceed as described in SAP Note The operating system collector SAPOSCOL must also be running on the monitored host [SAPOsCol]. Page 22 of 115

23 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 Thesaploc directory can also have another name; the important thing is that it is released as a share with the namesaploc; 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 (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 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 theinittab: 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. Page 23 of 115

24 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 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 SAPCM3X 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 (withpf=) when starting the agent. So that the agent can read the shared memory segments of all of the systems, install the agent with theroot user. For SAPCCM4X and SAPCCMSR with Option j2ee [page 10], you have to register one agent per monitored instance. Page 24 of 115

25 4.2. Downloading the CCMS Agents 1. You require the file CCMAGENT.SAR. This archive contains all CCMS agents, including SAPCCMSR, SAPCCM4X, and SAPCM3X. We recommend that you use the newest version of each agent. You can determine the version of a CCMS agent with the option v (see Displaying the Version of a CCMS Agent [page 104]). The archive also contains the availability agent CCMSPING. For more information about the availability agent, see [Avail]. 2. You can download CCMAGENT.SAR from the SAP Software Distribution Center of the SAP Service Marketplace ( Log on with your SAP Service Marketplace ID. Check the following folders in the specified order for this file and download it: In the navigation bar, choose Download Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NETWEAVER SAP NETWEAVER 2004S Entry by Component Application Server ABAP SAP KERNEL /64- BIT <operating system> Database Independent. Only if the desired archive does not exist in the above folder, choose Download Support Packages and Patches Entry by Application Group SAP NetWeaver SAP NetWeaver components (< SAP NW 04) SAP WEB AS SAP WEB AS 6.20 SAP WEB AS ABAP SAP KERNEL /64-BIT <operating system> Database Independent. Only if the desired archive is not in either of the above folders, choose Download Support Packages and Patches Archive for Support Packages and Patches Entry by Application Group SAP Application Components SAP R/3 SAP R/3 4.6A SAP KERNEL 4.6D 32/64-BIT <operating system> Database Independent. The reason for specifying multiple folders is that CCMS agents are partly dependent on the operating system release. Agents for a current SAP release may no longer cover all available operating system releases (for example, agents for SAP Web Application Server 6.20 are supported only on HP-UX 11.x; however, there are still application servers to be monitored that are running on HP-UX 10.x). You can determine the version of the CCMS agents in CCMAGENT.SAR by displaying the associated Info File. Page 25 of 115

26 If you require an agent for an older operating system release that is not in the folders above, SAP also provides the newest CCMS agent functions in patches to older SAP Basis releases (especially SAP Basis 4.6D), as far as possible. 3. Decompress the CCMAGENT.SAR archive with the SAPCAR tool. Take account of SAP Note (The new archiving tool SAPCAR). For decompressing the archive, use the following instruction: sapcar xvf ccmagent.sar Up to SAP NetWeaver 04 CCMS agents wer e freely backward compatible, so you could independent of the monitored system release always use the latest release of the CCMS agent. As of SAP NetWeaver 2004s, this has changed: To monitor a SAP instance up to release NW04 (6.40), always use an agent with release NW04 (6.40). To monitor a SAP instance with release NW2004s (7.00) or a host without SAP instance, use an agent with release NW2004s (7.00) Copying the CCMS Agent to the Desired Directory Copy the CCMS agents that you want to install to the appropriate directory for your platform: CCMS Agent Microsoft Windows UNIX SAPCCMSR SAPCM3X SAPCCMSR j2ee SAPCCM4X \\<host>\saploc\prfclog /usr/sap/ccms/bin \\<host>\usr\sap\ <SysID>\SYS\exe\run /usr/sap/<sysid>/sys/exe/run Thesaploc directory in the path of the CCMS agent SAPCCMSR can also have another name; the important thing is that it is released as a share with the name saploc. By default, this is the directory<drive:>\usr\sap. If the directory does not exist, create it yourself during the installation Creating the Required Configuration Files You can also create the following configuration files after registering the CCMS agent. However, you must then ensure that the agent takes these files into account.to do this, restart the agent (see Starting and Stopping CCMS Agents [page 103]). Page 26 of 115

27 4.4.1 Configuration File for Monitoring Log Files If you want to monitor log files with the CCMS agent, create one or more log file templates (see Structure of the Log File Template of the Log File Agent [page 53]) Configuration File for Monitoring Operating System Data If you want to configure the monitoring of operating system data individually, create a SAPOSCOL filter file, with which you can explicitly activate and deactivate parts of the operating system monitoring (see Structure of the SAPOSCOL Filter File oscolfile.txt [page 77]) Profile File of the CCMS Agents You specify a profile file during the registration of a CCMS agent withpf=<profile>. This is mandatory for agent SAPCCM4X, and the profile file must be that of the monitored instance. You must also specify a profile file for agent SAPCCMSR with Option j2ee [page 10]. This profile file must also be the profile for the monitored instance. Both profile files are stored under the following paths: <drive>:\usr\sap\<sysid>\sys\profile\<sysid>_<instdir>_<host> (Windows) /usr/sap/<sysid>/sys/profile/<sysid>_<instdir>_<host> (UNIX) For SAPCM3X and SAPCCMSR without the option j2ee, on the other hand, the specification of a profile file is optional, and usually not necessary. For these agents, use the profile file to: Change the size of the monitoring segment Change the working directory of the agent Set a virtual name for the host Declare the location of the operating system collector SAPOSCOL to the agent; this allows you to start or stop SAPOSCOL for a remote system using the agent Activate and deactivate the trace for the monitoring architecture With the SAPCM3X agent, ensure that you specify the profile of the monitored instance as a profile file if SAP instances with a higher release are also running on the host. Otherwise, information for these systems is also displayed, erroneously 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 ) DIR_PERF Working directory of the CCMS agents (see Working Directory [page 47]) Page 27 of 115

28 DIR_WORK_SAPOSCOL Working directory of SAPOSCOL exe/saposcol Complete path of SAPOSCOL alert/trace Trace for monitoring architecture data; set this trace only if expressly told to do so by Support; the default value is 1 (trace deactivated) SAPSYSTEM This parameter is only important for the agent SAPCCMSR with Option j2ee [page 10]. It specifies the system number of the Java instance monitored by the agent. SAPSYSTEMNAME This parameter is only important for the agent SAPCCMSR with Option j2ee [page 10]. It specifies the system ID of the Java instance monitored by the agent. While you can, in general, monitor multiple systems with identical system IDs [page 90], this is only possible to a restricted extent if you are using the-j2ee option: the system ID of the system associated with the agent (SAPSYSTEMNAME) must not match the system ID of one of the central monitoring systems. alert/save_suppressed_alerts Set this profile parameter to 1, to avoid the deletion of alerts that no longer fit into the shared memory segment of the agent. These alerts are instead automatically written to the database of the central monitoring system with the status complete. alert/green_alerts=1 Set this profile parameter to 1 to be able to work with all-clears (green alerts). Green alerts of this kind do not inform you of error situations, but are intended as all-clears, or explicit messages that an action was successful. SAPLOCALHOST Virtual host name used for addressing the local host of the agent In the context of high availability solutions, there can be various hosts, one of which is used as a replacement for emergencies or maintenance periods, but which should be externally addressed by the same name: only one of these should ever be in operation at any time. If a CCMS agent is installed on each of these hosts, the context name of the monitoring data (which also contains the name of the host) should be identical, irrespective of which host is currently running. Ensure this by setting an identical profile parameter SAPLOCALHOST in the profile file of the CCMS agent. Take this into account with the SAPCCMSR agent in Page 28 of 115

29 particular, as the SAPCCM4X agent uses the profile parameters of the SAP application server by default. You should also usesaplocalhost if the name of the host on which you are installing the CCMS agent is longer than 13 characters in length. Specify a name with a maximum length of 13 characters. This is then used for the name of the RFC destination of the agent and the monitoring segment of the agent. In the case of alternating operation of hosts of this type, the hosts work with monitoring segments with the same name, meaning that the data is reported in the same tree in the Alert Monitor. The content of the segment is saved to the files ALMTTREE, ALALERTS, and ALPERFHIS during the shutdown of a host. If you now ensure that these AL* files are accessible from both hosts, the contents of the segment are not disturbed by switching host. End each line of the profile file with the ENTER key Example Profile File You are registering the CCMS agent SAPCCMSR under Microsoft Windows and specify a profile file with the parameterpf=. This would have the following content: # Monitoring segment of the shared memory in bytes # (For the default size, see SAP Note ) alert/moni_segm_size = # Working directory of the agent # (Default for Microsoft Windows NT: \\host\saploc\prfclog\sapccmsr) DIR_PERF = c:\ccms-agenten\sapccmsr # Path and complete name of the operating system collector SAPOSCOL # (required so that the agent can control the collector) exe/saposcol = c:\saploc\saposcol.exe SAPCCMSR.INI: Configuration File for the CCMS Agents The SAPCCMSR.INI configuration file is stored in the working directory of the CCMS agent. The name of the file is always SAPCCMSR.INI, irrespective of the agent type. It primarily contains path specifications that are required for the operation of the CCMS agents. Create the configuration file before installing a CCMS agent if you are using at least one of the following functions: Your own settings for Monitoring Log Files [page 51] Configuring the Monitoring of Operating System Data [page 76] Page 29 of 115