Profile File of the CCMS Agents

Use

You specify a profile file during the registration of a CCMS agent with pf=. 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, and usually not necessary. 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 or stop SAPOSCOL for a remote system using the agent

· Activate and deactivate the trace for the monitoring architecture

With the SAPCM3X agent, ensure that you specify the profile of the monitored instance as a profile file if SAP instances with a higher release are also running on the host. Otherwise, data for these systems is also displayed, erroneously.

Structure

The important profile parameters for the agents are:

alert/MONI_SEGM_SIZE

Size of the monitoring segment in the shared memory in bytes (by default, 20.000.000 bytes; see also SAP Note 135503)

DIR_PERF

Working directory of the CCMS agent and SAPOSCOL (see Installing and Registering 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; the default value is 1 (trace deactivated)

SAPLOCALHOST

Virtual host name used for addressing the local host of the agent 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 externally addressed by the same name: only one of these should ever be in operation at any time. 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. 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. In the case of alternating operation of hosts of this type, the hosts work with monitoring segments with the same name, meaning that the data is reported in the same tree in the Alert Monitor. The contents of the segment is saved to the files ALMTTREE, ALALERTS, and ALPERFHIS during the shutdown of a host. If you now ensure that these AL* files are accessible from both hosts, the contents of the segment are not disturbed by switching host.

ipc/shm_permission_1008

If you are using the SAPCCMSR agent to monitor a host with multiple J2EE servers, you must ensure that this profile parameter has the value 10777. This means that the J2EE Servers can write tot he shared memory of the agent, even if they are not running under the same user. The first process, which creates the shared memory, must therefore set the parameter with the command ipc/shm_permission_1008=100777. This can be SAPCCMSR (in this case, add the line to the SAPCCMSR profile file), however it could also be the J2EE Engine.

Example

You are registering the CCMS agent SAPCCMSR under Microsoft Windows and specify a profile file with the parameter pf=. This would have 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 Microsoft 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