PlugIn <file path> [<directory for loading additional dll>]

Shared library of the agent to be loaded; multiple plug-ins are possible. The file path must not contain any spaces.

Some plug-ins, such as itsmon.dll, require in turn additional shared libraries, which are stored in a particular directory. In this case, specify the directory as a second parameter, as otherwise the CCMS agent only searches for these libraries in its working directory, meaning that they might not be loaded.

LogFile <file path>

Configuration file for monitoring log files (log file template); you can specify one configuration file for each log file

LogFileDir <directory path>

See Monitoring Log Files with CCMS Agents

You may only specify one directory LogFileDir in the configuration file.

LogfileParam DelTree

If you specify Deltree, obsolete elements for which no log file exists any longer are deleted from the shared memory

OsColFile <file path>

Specifies a SAPOSCOL filter file for filtering out subtrees of the operating system monitoring; the subtrees are then no longer stored in shared memory

ViewDirList <file path>

Files for which the agent has explicit permission to read for display in the Alert Monitor

AlertLog <file path>

Full path of a log file for detected alerts (specify the filename without suffix, the suffix .log is automatically set)

AlertLogLevel <level>

Scope of the alert logging

PushCycleMinutes <n>

Optional parameter that specifies how frequently the agent automatically reports values to the central monitoring system:

n=1:     Default, values are reported every minute
n=0:     Values are never reported
n<30:   Values are reported every n minutes
n³30:   Values are reported every 30 minutes

LongSid
<target system>

If you want to monitor multiple systems with identical system IDs  in your system landscape, specify a unique name for the system of the agent here. The first three characters of the name should correspond to the system ID of the monitored system (only for agent SAPCCM4X).

TrapSendFile
<file path>

Complete path of the configuration file for sending the SNMP traps (see Customizing the Configuration File for Sending SNMP Traps; for a general description of SNMP functions for CCMS agents, see Setting Up the Sending and Receiving SNMP Traps Using CCMS Agents)

TrapReceiveFile <file path>

Complete path of the configuration file for receiving the SNMP traps (see Adjusting the Configuration File for Receiving SNMP Traps)

GrmgDir

You can use the GRMG (Generic Request and Message Generator) to monitor the availability of technical components or of steps in business processes  (see Monitoring with the Generic Request and Message Generator). In this case, both Customizing information and availability requests and responses are exchanged as XML files.

A Customizing file specifies which component(s) are to be monitored, and how. To transfer this information to the central monitoring system, Customizing files are automatically transferred with the prefix GRMG_ from the directory GrmgDir and the associated scenario is started.

The default value is \\host\saploc\PRFCLOG\grmg for Microsoft Windows or /usr/sap/tmp for UNIX.

Although you can change the directory by setting the parameter GrmgDir, we do not recommend that you do so. Changing the parameter might mean that SAP components that are instrumented for the monitoring are no longer monitored.

EventLogMon [On|Off]

EventLogMon <file path>

EventLogResolveMessages [On|Off]

See Event Log Monitoring with CCMS Agents