Show TOC

Working Directory and Log Files of the CCMS AgentsLocate this document in the navigation structure

Definition
Caution

You no longer require CCMS agents if the following conditions are fulfilled:

  • The monitored system has a release as of SAP NetWeaver 7.0 EhP2

  • The central monitoring system (CEN) has a release as of SAP NetWeaver 7.0 EhP1

In this case, the CCMS agents' functions are performed by SAP NetWeaver Management Agents.

Run Directory

The working directory of the CCMS agent is in the following location, depending on the type of agent:

CCMS Agent

Run Directory

Alternative

SAPCCMSR

/usr/sap/tmp/sapccmsr (UNIX)

\\<host>\saploc\prfclog\sapccmsr (Microsoft Windows)

$DIR_PERF/sapccmsr (if the parameter DIR_PERF is specified)

SAPCCMSR -j2ee (up to SAP NetWeaver 7.0 EhP 1)

/usr/sap/ccms/<SysID>_<SysNo>/sapccmsr (UNIX)

\\<host>\saploc\ccms\<SysID>_<SysNo>\sapccmsr (Microsoft Windows)

$DIR_CCMS (if the parameter DIR_CCMS is specified)

SAPCCMSR -j2ee (as of SAP NetWeaver 7.0 EhP 2)

$DIR_LOGGING/sapccmsr, that is, by default <instance directory>/log/sapccmsr in UNIX notation)

SAPCCM4X

$DIR_LOGGING/sapccm4x (UNIX notation)

SAPCM3X

$DIR_PERF/sapcm3x (UNIX notation)

Note

  • The saploc directory in the path of the CCMS agent SAPCCMSR can also have another name; the important thing is that it is released as a shared with the name saploc; by default, this is the directory <drive:>\usr\sap. If the directory does not exist, create it yourself during the registration.

  • In the case of SAPCCMSR with the J2EE Option, a subdirectory <System ID>_<instance number> is created in /usr/sap/ccms (UNIX) or \\<host>\saploc\ccms (Microsoft Windows), so that the agents of different systems and numbers are separated. The files ALMTTREE, ALPERFHI, and ALALERTS are stored in this directory (since the agent manages its own shared memory, these AL* files must also be stored separately from those of possible ABAP instances with the same number.) The log files of the agent are stored in the subdirectory <System ID>_<instance number>\sapccmsr.

The working directory contains, among other things, the following configuration files:

  • CSMCONF

    Contains information about the central monitoring system; the parameters correspond to those in the start file for dialog-free installation (see Dialog-Free Registration of the CCMS Agents).

  • SAPCCMSR.INI

    Contains information about the extent to which Plug-Ins, log files, and SAPOSCOL information should be considered; this file is read when the agent is started (see CCMS Agent Configuration File SAPCCMSR.INI).

  • SAPRFC.INI

    Contains information for registration at the gateway of the central monitoring system.

    Note

    You can display all files in the working directory of the agent in the central monitoring system. You can use transaction RZ21 to do this. In the Topology group box, select one of the Agents for… radio buttons. . The Monitoring: Display Technical Topology screen appears. Now select the desired agent and then choose Working Directory of the Agent ([ ). The system displays the files of the directory. To display the contents of a file, choose the file by double-clicking it.

Log Files

If you install the CCMS agent in dialog mode, the entire system logging is performed directly to the file stdout. In the case of a dialog-free installation, the system creates a log file called <agentname>.log in the directory from which you started the registration.

A log file is also created during runtime for the CCMS agent under the name <agentname><pid>.log, and log files are created for RFC communication.

Trace Files

You can set the developer trace with the option -t when starting or registering the CCMS agent. The trace is written to the file dev_<agent name> in the working directory of the agent. Activate the trace only if specifically told to do so by support.

You can use the option -debug to have a rolling trace written to the file dev_<agent name>. This means that there is a space-saving mechanism available when detecting intermittent problems: the first megabyte of the trace is always kept in full, along with one to two megabytes at the end of the trace.

More Information