Entering content frame

Object documentation Profile File of the CCMS Agents Locate the document in its SAP Library structure

Use

You specify a profile file during the registration of a CCMS agent with pf=<profile path>. This is mandatory for agent SAPCCM4X, and the profile file must be that of the monitored instance.

You must also specify a profile file for agent SAPCCMSR with the j2ee Option. This profile file must also be the profile for the monitored instance. Both profile files are stored under:

<drive>:\usr\sap\<SysID>\SYS\profile\<SysID>_<InstDir>_<Host> (Microsoft Windows)

/usr/sap/<SysID>/SYS/profile/<SysID>_<InstDir>_<Host> (UNIX)

For agents SAPCM3X and SAPCCMSR without the option –j2ee, 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

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

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 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; the default value is 1 (trace deactivated)

SAPSYSTEM

This parameter is only important for the agent SAPCCMSR with the j2ee Option. It specifies the system number of the Java instance monitored by the agent.

SAPSYSTEMNAME

This parameter is only important for the agent SAPCCMSR with the j2ee Option. It specifies the system ID of the Java instance monitored by the agent.

Caution

While you can, in general, monitor multiple systems with identical system IDs, this is only possible to a restricted extent if you are using the -j2ee option: the system ID of the system associated with the agent (SAPSYSTEMNAME) must not match the system ID of one of the central monitoring systems.

alert/SAVE_SUPPRESSED_ALERTS

Set this profile parameter to 1, to avoid the deletion of alerts that no longer fit into the shared memory segment of the agent. These alerts are instead automatically written to the database of the central monitoring system with the status complete.

alert/GREEN_ALERTS=1

Set this profile parameter to 1 to be able to work with all clears (green alerts). Green alerts of this type do not indicate error situations, but are intended as all-clears or explicit messages that an action was successful (see Structure linkWorking with All-Clears (Green Alerts)).

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.

You should also use SAPLOCALHOST if the name of the host on which you are installing the CCMS agent is longer than 13 characters in length. Specify a name with a maximum length of 13 characters. This is then used for the name of the RFC destination of the agent and the monitoring segment of the agent.

Note

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

This graphic is explained in the accompanying text

End each line of the profile file with the ENTER key.

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

This graphic is explained in the accompanying text CCMS Agents start page, Installing and Registering CCMS Agents

 

 

Leaving content frame