Parameters of the SAPCCMSR.INI Configuration File
The SAPCCMSR.INI configuration file is stored in the Working Directory of the SAP NetWeaver Management Agents . The name of the file is always SAPCCMSR.INI, irrespective of the agent type. It primarily contains path specifications that are required for the individual configuration of central monitoring.
Note that changes to the SAPCCMSR.INI file only take effect when you restart the SAP NetWeaver management agent .
Change the configuration file if you want to use at least one of the following functions:
- Your own settings for the monitoring of log files
- Configuring the Monitoring of Operating System Data
- Central Monitoring of the Microsoft Windows Event Log
- Alert Logging for SAP NetWeaver Management Agents
- Monitoring Multiple Systems with Identical System IDs
- Using additional shared libraries
You can set the following parameters in SAPCCMSR.INI:
| Parameter | Description |
|---|---|
|
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, since otherwise the 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 Central Monitoring of Log Files Note
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 |
|
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. |
|
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 <instance directory>\log\grmg for Microsoft Windows and <instance directory>/log/grmg for UNIX. The transfer is performed only with instance agents. Note
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. |
|
alert/AGENTLOCALHOST |
If you want to run agents on different hosts with teh 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. |
|
EventLogMon [On|Off] EventLogMon <file path> EventLogResolveMessages [On|Off] |
More information: Central Monitoring of the Microsoft Windows Event Log |
Comment lines begin with the number sign (#).
Enter the lines in the format <Parameter_name><space><Parameter_value>.
If SAPCCMSR.INI does not yet exist when the agent is registered in CEN, the system creates the following file empty (containing only comments) in the working directory of the SAP NetWeaver management agent.
### Configuration file for CCMS agents SAPCCMSR and SAPCCM4X###### Format of entries for plugins:# PlugIn <full path of shared library to load>###### Format of entries for logfile monitoring:# LogFile <full path of logfile template>###### Format of entries for the option to delete trees### if no corresponding logfile exists:### This Parameter is optional, if not specified the tree still remains# LogFileParam DelTree###### Format of entries for mechanism to filter out SAPOSCOL values:# OsColFile <full path of oscolfile template>###### Name of Logfile for detected alerts### This Parameter is optional, if not specified there is no logging of Alerts# AlertLog <full path filename, without suffix>###### Level of logging (0: no logging, 1: Logging of Alerts, 2: in addition log### suppressed alerts, new values, creation, deletion, reset for any MTE)### Parameter is optional, default = 0 if AlertLog is not set else default = 1# AlertLogLevel <level>
Infrastructure of the SAP NetWeaver Management Agents Start Page