Show TOC

 Installing an Agent on an ABAP InstanceLocate this document in the navigation structure

Caution

CCMS agents are no longer required for purely SAP NetWeaver 7.1 landscapes; their functions are performed by SAP NetWeaver Management Agents. More information about when you still require CCMS agents for SAP NetWeaver 7.1: CCMS Agents: Central Monitoring for Components up to SAP NetWeaver 7.0.

Use

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 the central monitoring system (CEN). Since this alternative connection method no longer requires a free work process, the access route is independent of error states of the ABAP instance and is therefore more robust.

You can also use the advanced functions of the CCMS agents, for example to monitor specific processes or log files on the host of the monitored instance.

Note

This procedure also applies for double-stack systems in the case of a monitored system with release SAP NetWeaver 7.0. A separate SAPCCMSR -j2ee agent is no longer required for double-stack systems with this release, since the ABAP and Java stacks have a shared monitoring segment, meaning that agent SAPCCM4X also transfers the monitoring data for the Java instance to CEN.

Prerequisites
  • There is a communication user CSMREG in CEN.
  • You have created the CSMCONF start file for CCMS agents in CEN.
  • You have the SAPCCM4X executable; note that to monitor an ABAP instance with a release status of SAP NetWeaver 7.1, you also require an agent with this release status.
    Note

    The way in which you can fulfill the prerequisites is described in Installing CCMS Agents for SAP NetWeaver Components.

Procedure
  1. Log on to the host of the ABAP instance as <SID>adm (UNIX) or SAPService<SID> (Microsoft Windows), to ensure that the agent can access the shared memory.
  2. Copy the CSMCONF start file to the working directory of SAPCCM4X. This is in the following location:

    Microsoft 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:

    Microsoft Windows: [drive]:\usr\sap\<SysID>\SYS\exe\run

    UNIX: /usr/sap/<SysID>/SYS/exe/run

    Note

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

    <Profile path> specifies the instance profile of the monitored instance. By default, this is:

    Microsoft 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 file to you again for confirmation. Confirm the specification by pressing the ENTER key in each case. You only need to enter two parameters yourself:
    • The password for the administration user in CEN, under which you created the CSMCONF file
    • The password for the CSMREG user
  6. Under UNIX, you must ensure yourself that SAPCCM4X is automatically started again when the host is restarted. To do this, enter the following commands 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.

 CCMS Agents start page