Profile File of the CCMS agents (SAP Library

Profile File of the CCMS agents

Use

During the registration of a CCMS agent, you specify a profile path with pf=<profile path>. This is mandatory for agent SAPCCM4X, and the profile file must be that of the monitored instance. For agents SAPCM3X and SAPCCMSR, on the other hand, the specification of a profile file is optional. For these agents, use the profile file to:

Change the size of the monitoring segment

Change the working directory of the agent

Set a virtual name for the host

Declare the location of the operating system collector SAPOSCOL to the agent; this allows you to start SAPOSCOL for a remote system using the agent (see Controlling SAPOSCOL from the SAP System)

Activate and deactivate the trace for the monitoring architecture

Structure

The important profile parameters for the agents are:

Profile Parameter	Description	Default Value
alert/ MONI_SEGM_SIZE	Monitoring segment in the shared memory in bytes; only for SAPCCMSR (see Functions of the CCMS Agents)	See SAP Note 135503
DIR_PERF	Working directory of the CCMS agents and SAPOSCOL	See Working Directory and Log Files of the CCMS Agents
exe/saposcol	Complete path of SAPOSCOL
alert/TRACE	Trace for monitoring architecture data; set this trace only if expressly told to do so by Support	1 (Trace deactivated)
SAPLOCALHOST	Virtual host name used for addressing the local host of the agent

Profile Parameter SAPLOCALHOST

In the context of high availability solutions, there can be various hosts, one of which is used as a replacement for emergencies or maintenance periods, but which should be addressed by the same name.

If a CCMS agent is installed on each of these hosts, the context name of the monitoring data (which also contains the name of the host) should be identical, irrespective of which host is currently running. You can ensure this by setting an identical profile parameter SAPLOCALHOST in the profile file of the CCMS agent. Take this into account with the SAPCCMSR agent in particular, as the SAPCCM4X agent uses the profile parameters of the SAP application server by default.

If you set an identical virtual host name SAPLOCALHOST, the different hosts can access the same monitoring segment during alternating operation. This is not a problem technically, as the complete contents of a segment are saved in three files (ALMTTREE, ALALERTS, and ALPERFHIS) during operation and when a host is shutdown, and it is therefore only necessary that all hosts access the same AL* files.

Example

You register the CCMS agent SAPCCMSR on Windows NT and specify a profile file with the parameter pf=. This has the following content:

# Monitoring segment of the shared memory in bytes
# (For the default size, see SAP Note 135503)
alert/MONI_SEGM_SIZE = 20000000

# Working directory of the agent
# (Default for Windows NT: \\host\saploc\prfclog\sapccmsr)
DIR_PERF = c:\ccms-agenten\sapccmsr

# Path and complete name of the operating system collector SAPOSCOL
# (required so that the agent can control the collector)
exe/saposcol = c:\saploc\saposcol.exe