Entering content frameFunction documentation Monitoring Operating System Data with CCMS Agents Locate the document in its SAP Library structure

Use

The operating system collector Structure linkSAPOSCOL collects operating system data for any host and stores this in a segment of the shared memory. All CCMS agents can copy this data to the CCMS monitoring segment and transfer it to the central monitoring system. This means that the data is visible in the CCMS monitoring architecture and is displayed in the familiar transactions ST06 and OS07.

In this way, you can monitor the operating system data for servers without a running SAP Basis system. An expensive installation and configuration of RFCOSCOL is no longer necessary (see also Structure linkInstallation of the Operating System Collector SAPOSCOL).

Features

After the successful installation of the agent, the CCMS monitoring architecture displays the following data in the Operating System monitor:

Irrespective of this, transaction OS07 displays all data collected by SAPOSCOL. OS07 is therefore well suited to being an analysis method for the Operating System monitor. You can display this data using the RFC destination SAPCCMSR.<hostname>.99.

The agent also allows an individualized selection of subtrees for the Operation System and Filesystems monitors. You can use a filter to explicitly remove subtrees or entire components from the monitoring display. No monitoring nodes are then generated for these. Alternatively to filtering out file systems, you can activate an exclusive monitoring with which only the file systems that you explicitly specify are monitored. All other file systems are not then monitored. For these settings, the CCMS agent requires a configuration file (referred to as oscolfile.txt in the following) that you specify in the SAPCCMSR.INI file using the parameter OsColFile. You can make the following specifications in the oscolfile.txt configuration file:

After the keyword FilterOutComponent, enter the components that you do not want to be copied to the CCMS monitoring segment, and for which the system will therefore not create a subtree in the monitoring tree in transaction RZ20.

You can use the keyword FilterOutFilesystem to filter out particular file systems that are not to be copied to the CCMS monitoring segment. In this way, you can, for example, exclude particular file systems that are always 100% full from the monitoring. You can specify the file system name or a pattern with a wildcard character (*).

As an alternative to filtering out individual file systems, you can activate an exclusive monitoring. In this case, the system creates subtrees in the monitoring architecture for only the file systems that you specify with the keyword MonitorFilesystem. All other file systems are ignored. Entries with the keyword FilterOutFilesystem are also ignored.

This graphic is explained in the accompanying text

If you have installed an SAPCCM4X agent, there is already a complete Operating System monitoring tree that was created by the monitored SAP instance. In this case, you must deactivate the ABAP data collector in the monitored system. The SAPCCM4X agent then creates a new Operating System monitoring tree in accordance with oscolfile.txt when it is started:
      1. To do this, start transaction RZ21 in the system that the SAPCCM4X agent is monitoring. In the Methods group box, select Method Definitions and choose Display Overview.
      2. Change the following methods by selecting the methods and choosing Edit Data (This graphic is explained in the accompanying text):
      1. On the Release tab page, deactivate the Data Collection Method indicator and on the Control tab page, deactivate the Execute method immediately after start of a monitoring segment check box.
      2. Save the method definitions.
      3. Restart the CCMS agent.

Example

The following lines are contained in the configuration file SAPCCMSR.INI:

### Format of entries for mechanism to filter out SAPOSCOL values:
OsColFile d:\usr\sap\TVB\D26\log\sapccm4x\oscolfile.txt

The specified file oscolfile.txt contains the following lines:

#######################################################################
###
### OsColFile.txt
### Configuration file for Operating System Monitoring
###
#######################################################################

# FilterOutComponent <Component Name>
### CCMS agent does not create MTEs for <Component Name>
### Windows: <Component Name> = CPU | Lan | Commit_Charge | Paging |
### Filesystems
### UNIX: <Component Name> = CPU | Lan | SwapSpace | Paging |
### Filesystems

# FilterOutFilesystem <Filesystem Name> | <Pattern>
### CCMS agent does not create MTEs for <Filesystem Name> |<Filesystem>
### Filesystem name can contain '*' as a wildcard (<Pattern>).
### CCMS agent does not create MTEs for <Filesystem Name> | <Pattern>

# MonitorFilesystem <Name> | <Pattern> [ <MTE Class> [<Group>]]
### CCMS agent creates MTEs for this file system only. All other
### Filesystems are ignored
### Name can contain '*' as a wildcard (<Pattern>)
### Name can be an unsubstituted filesystem name e.g. $DIR_TRANS
### $DIR_PERF, if these represent file systems collected by saposcol

### <MTE Class> and <Group> are optional. If you want to specify
### your own customizing group you have to specify an MTE class, too.

This graphic is explained in the accompanying text

Contents of oscolfile.txt

Description

FilterOutComponent CPU
FilterOutComponent SwapSpace
MonitorFilesystem
/usr/sap/trans
  • Does not create subtree CPU and does not create subtree SwapSpace
  • Only creates a tree for the file system /usr/sap/trans

FilterOutComponent
Filesystems
  • Does not create a subtree for file systems

FilterOutComponent CPU
FilterOutFilesystem
/oracle/C11/sapdata*
  • Does not create a CPU subtree
  • Does not create trees for file systems that match the pattern /oracle/C11/sapdata* (such as /oracle/C11/sapdata2); all other file systems are displayed

MonitorFilesystem
/oracle/C11/sapdata*
CL_ORA GC_ORA
  • Only creates a tree for file systems that match the pattern /oracle/C11/sapdata* (such as /oracle/C11/sapdata2); the nodes are created under the MTE class CL_ORA and the attribute group CG_ORA

See also:

Installation of the CCMS Agents

Structure linkOperating System Monitor

Leaving content frame