Profile Parameters for Central Monitoring
You can configure the configuration settings for central monitoring by transferring profile parameters of the SAP NetWeaver management agents. Depending on the agent type, the relevant profile file is available at the following path:
- In the case of the sapstartsrv instance agent, the profile file is that of the monitored instance:
<drive>:\usr\sap\<SysID>\SYS\profile\<SysID>_<InstDir>_<Host> (Microsoft Windows)
/usr/sap/<SysID>/SYS/profile/<SysID>_<InstDir>_<Host> (UNIX)
- In the case of host agents, the profile file is that of the associated framework program SAPHostControl.
[drive]:\Program Files\SAP\hostctrl\exe\host_profile (Microsoft Windows)
usr/sap/hostctrl/exe/host_profile (UNIX)
The important profile parameters for the agents are:
alert/MONI_SEGM_SIZE |
Size of the monitoring segment in bytes in shared memory (by default, 40,000,000 Bytes for non-Unicode systems and 60,000,000 Bytes for Unicode systems; see also SAP Note 135503) |
DIR_PERF |
Working directory of the SAP NetWeaver management agents and SAPOSCOL (see Working Directory of the SAP NetWeaver Management Agents) |
exe/saposcol |
Complete path of SAPOSCOL; you can use this to make the location of the operating system collector SAPOSCOL known to the agent to start or stop SAPOSCOL for a remote system using the agent |
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) |
hostexec/trace |
Trace for SAPHostControl; the default value is 0 (trace deactivated), possible values are 1, 2, and 3 |
hostexec/startoscol |
Indicator of whether SAPHostControl is to automatically start the operating system collector SAPOSCOL [true, false]; by default, SAPOSCOL is started (true) |
SAPSYSTEM |
System number of the instance monitored by the agent; in the case of host agents, the value is 99 |
SAPSYSTEMNAME |
System ID of the instance monitored by the agent; in the case of host agents, the value is SAP Caution
While you can, in general, monitor multiple systems with identical system IDs, 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 Working 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 addressed by the same name: Only one should ever be in operation at any time. If an 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 agent. Take this into account with host agents in particular, since the instance agent uses the profile parameters of the SAP application server. You should also use SAPLOCALHOST if the name of the monitored host is more 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. |
alert/AGENTLOCALHOST |
If you want to run agents on different hosts with the same host name, this is not possible with the normal registration settings, since both agents could be registered with the same RFC destination (such as SAPCCM4X.HOSTXY.00) in CEN. In this type of case, use this parameter to ensure that you have a unique host name for logging on to the gateway and the RFC destination. For more information about this parameter, refer to SAP Note 1270193. The parameter is available to you as of Patch Collection 2009/1. Note
You cannot change this parameter during running operation; if there is already a registered agent, you need to deregister the agent, set the parameter, and then reregister the agent. |
hostexec/oscol/arguments = <argument list> |
You can use this parameter to set the options of operating system collector SAPOSCOL using the profile file of the host agent. More information: Controlling SAPOSCOL from the Operating System. |
ccms/enable_agent |
By default, the monitoring function of the SAP NetWeaver management agents is started when you register the agent with a central monitoring system (more information: Registering SAP NetWeaver Components and Hosts in CEN). You can control this behavior by setting the above profile parameter: ccms/enable_agent>0: The agent is always started; that is, the data collection in the agent is activated. This is useful, for example, if you want to monitor non-ABAP instances without a CEN in the local ABAP stack. ccms/enable_agent=0: This is the default setting described above. ccms/enable_agent<0: The data collection in the agent is not activated, regardless of whether the agent is registered with a CEN. |
End each line of the profile file with the ENTER key.
Start Page Infrastructure of the SAP NetWeaver Management Agents