Installing/Registering the CCMS Agents for Experts

The CCMS agents expand the monitoring architecture by providing an alternative connection route from the central monitoring system to any other servers. 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> (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 CCMS agent from the Software Catalog on SAP Service Marketplace (see  Downloading CCMS Agents).
2. Copy the CCMS agent that you want to install to the following directory, depending on the platform:

   CCMS Agent	Windows	Unix
   SAPCCMSR SAPCM3X	\\<host>\saploc\prfclog	/usr/sap/ccms/bin
   SAPCCMSR with Option j2ee SAPCCM4X	\\<host>\usr\sap\<SysID> \SYS\exe\run	/usr/sap/<SysID>/SYS/exe/run

   Note

   The directory saploc 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.

3. If you want to monitor log files using CCMS agents, create one or more log file templates (see  Structure of the Log File Template of the Log File Agent).
4. 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  Monitoring Operating System Data with CCMS Agents).
5. 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. Information about which profile parameters can be set in profile files like this can be found here:  Profile File of the CCMS Agents.

6. 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:  Monitoring Files with CCMS Agents
   •  Monitoring Operating System Data with CCMS Agents
   •  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 (see  Controlling CCMS Agents).

7. 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 (see  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. You can find the procedures in this process:  Installing CCMS Agents for SAP NetWeaver Components.
   • Registration in dialog (see  Registering the CCMS Agents in Dialog)
   • Non-dialog registration using a start file (see  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.

8. 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. Restart it:

   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).

9. This point does not apply just to the installation of the agent SAPCCM4X: If the monitored system of the agent is registered before the registration of the agent in the monitoring architecture of the central monitoring system, all required RFC connections already exist. If not, you must enter the monitored system as a remote system in the central monitoring system (see Registering SAP NetWeaver Components and Hosts in CEN).
10. 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 Create Monitors for the CCMS Agents in the Central Monitoring System.

Start Page CCMS Agents