Installing/Registering the CCMS Agents for Experts

The CCMS agents extend the monitoring architecture by providing an alternative connection route from the central monitoring system to any other servers in addition to the ABAP interface. In doing so, they enable you to:

• Include SAP components without ABAP interfaces
• Include non-SAP components
• Optimize performance when reading and writing monitoring data
• Establish a connection route irrespective of the possible error status of the monitored SAP instance

• 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 systems with a release status of SAP R/3 3.X are running on one host, note the following points:
  • Install only one SAPCM3X agent on each host.
  • The agent only monitors one instance, if you specify a profile; therefore do not specify a profile (with pf=) when starting the agent.
  • Install the agent using the root user so that it can read the shared memory segments of all systems.
• In the case of agents SAPCCM4X and SAPCCMSR with Option -j2ee, you require a separate agent for each instance.

1. Download the desired CCMS agent from the Software Catalog of the SAPService Marketplace (more information Downloading the CCMS Agents).
2. Copy the CCMS agent that you want to install to the following directory, depending on the platform:

   CCMS Agent	Microsoft Windows	UNIX
   SAPCCMSR SAPCM3X	\\<host>\saploc\prfclog	/usr/sap/ccms/bin
   SAPCCMSR ‑j2ee SAPCCM4X	\\<host>\usr\sap\<SysID> \SYS\exe\run	/usr/sap/<SysID>/SYS/exe/run

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 during the installation.

1. If you want to monitor log files with the CCMS agent, create one or more log file templates (more information: Structure of the Log File Templates of the Log File Agent).
2. 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 (more information: Monitoring Operating System Data with CCMS Agents).
3. You specify a profile file during the registration of a CCMS agent with pf=<profile path>. 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 the j2ee Option. This profile file must also be the profile for the monitored instance. Both profile files are stored under:

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

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

   For agents SAPCM3X and SAPCCMSR without the option -j2ee, on the other hand, the specification of a profile file is optional, and usually not necessary. For information about which profile parameters you can set in a profile file of this type, refer to Profile File of the CCMS Agents.

4. Create the configuration file SAPCCMSR.INI before installing a CCMS agent if you are using at least one of the following functions:
   • Your own settings for Monitoring Log Files
   • Configuring the Monitoring of Operating System Data
   • Alert Logging for CCMS Agents
   • Using additional shared libraries
     Note

     You can also create the configuration files from points 3 to 6 after registering the CCMS agent. However, you must then ensure that the agent takes these files into account. To do this, restart the agent (more information: Controlling CCMS Agents).

5. Register the CCMS agent; by doing this, you inform the central monitoring system about the agent. We recommend that you have the central monitoring system create the data required for this (more information: Automatically Creating the CSMCONF Start File). You can perform the registration in two ways:
   • Registration with the agent registration tool; use this tool to register the SAPCCMSR agent with exactly one CEN. For the relevant procedure, refer to Installing CCMS Agents for SAP NetWeaver Components.
   • Registration in Dialog (more information: Registering CCMS Agents in Dialog)
   • Dialog-free registration using a start file (more information: Dialog-Free Registration of the CCMS Agents)
     Note

     For information about the special features of the registration of SAPCCMSR with Option j2ee are discussed in Registering SAPCCMS with the -j2ee Option.

6. Under Microsoft Windows, the agent has been entered as a service and started. The agent is automatically restarted at every restart. If you have installed the CCMS agent under UNIX, the agent has not yet been started. Start it using the appropriate command:

   Agent	Start Command
   SAPCCMSR	sapccmsr -DCCMS [pf=<profile path>]
   SAPCCMSR -j2ee	sapccmsr -j2ee -DCCMS pf=<profile path>
   SAPCCM4X	sapccm4x -DCCMS pf=<profile path>
   SAPCM3X	sapcm3x -DCCMS [pf=<profile path>]

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

7. This point applies only if you are installing agent SAPCCM4X: If the monitored system of the agent is already known to the monitoring architecture of the central monitoring system before the registration, all of the required RFC connections already exist. Otherwise, you must enter the monitored system in the central monitoring system as a remote system (more information: Registering SAP NetWeaver Components and Hosts in CEN).
8. The data transferred by the CCMS agent is now available in the central monitoring system. If you require more convenient access to this data, you can Creating CCMS Agent Monitors in the Central Monitoring System.

 CCMS Agents start page