Filesystems Monitor in CCMS

This monitor displays a section of the Operating System Monitor, which displays all of the values collected by the operating system collector SAPOSCOL. You can use this monitor to monitor application servers and host systems of your choice and to check whether there is still enough free disk space available. The values are collected by the operating system collector SAPOSCOL. You can also monitor this data with the operating system monitor, which is assigned as the analysis method for most of the nodes of this monitor.

Prerequisites

To be able to display operating system data for a particular server with this monitor, the operating system collector SAPOSCOL must be installed on that server (see Installing the Operating System Collector SAPOSCOL).

Features

The monitor contains the following monitoring tree elements (MTEs):

MTE Name (MTE Class)	Meaning
Name (FilesystemName)	Name of the file system
Freespace (FilesystemFreeSpace)	Free disk space in the file system
Percentage_Used (FilesystemPercentageUsed)	Usage of the available storage space for the file system as a percentage

You can explicitly exclude file systems from the operating system collector monitoring. For more information, see Monitoring Operating System Data with CCMS Agents.

Activities

To start the monitor, follow the procedure below:

...

1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.

2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.

3. Start the Filesystems monitor from the list by double clicking it.

Operating System Monitor in CCMS

This monitor monitors operating system data for any application servers and host systems. The values are collected by the operating system collector SAPOSCOL. You can also monitor this data with the operating system monitor, which is assigned as the analysis method for most of the nodes of this monitor.

Prerequisites

To be able to display operating system data for a particular host with this monitor, the operating system collector SAPOSCOL must be installed on that server (see Installing the Operating System Collector SAPOSCOL).

Features

The monitor contains the following monitoring tree elements (MTEs):

MTE Name (MTE Class)	Meaning
CPU (CPU)	Information about the CPU of a host system
CPU_Utilization (CPU_Utilization)	Average usage of the CPU in a host system; the value shows how intensively the CPU is used and how much processing capacity is still available
5minLoadAverage (5minLoadAverage)	Average number of processes in a host system that are ready for execution but must wait to be processed by the CPU
Idle (Idle)	Idle time for all CPUs in the system
Paging (Paging)	Exchange of data pages between the main memory of a host system and the overflow store in a paging file on the hard disk; paging occurs if the main memory is not large enough for the contexts of all running processes
Page_In (Page_In)	Average number of page-ins per second; a page-in occurs if a process must access a data page that is not available in the main memory. Before the process can be continued, the operating system must retrieve the page from the paging file
Page_Out (Page_Out)	Average number of page-outs per second (page-out occurs if a page is stored out of the main memory to make room for the pages required by other processes)
Commit_Charge (Commit_Charge)	Total physical and virtual memory used by the operating system and programs (only for Microsoft Windows)
Commit_ChargeFree (CommitChargeFreeSpace)	Available commit charge: difference between the maximum available and the currently used commit charge (only for Microsoft Windows)
Commit_Percent (CommitChargePercent_Used)	Proportion of the maximum available commit charge currently used (only for Microsoft Windows)
Swap_Space (Swap_Space)	Storage space on the hard disk on which data that is not currently required is stored out of the main memory, so that there is space in the main memory for the program currently being executed (only for UNIX platforms)
Freespace (SwapFreespace)	Free swap space (only for UNIX platforms)
Percentage_Used (SwapPercentage_Used)	Percentage usage of the swap space (only for UNIX platforms)
OS_Collector (OS_Collector)	Status of the operating system collector SAPOSCOL
State (OS_COL_STATE)
Lan (Lan)	Information about a Local Area Network (LAN), broken down by the LANs installed on this host
Packets_In (LanPacketsIn)	Incoming packets per second in a LAN at the interface of a host system
Packets_Out (LanPacketsOut)	Outgoing packets per second in a LAN at the interface of a host system
Collisions (LanCollisions)	Collisions in the LAN, in which two stations transport a packet at the same time on the same channel; this leads to the destruction of both packets and means that they must be sent again
Monitored Processes (MonitoredProcessesSum)	Monitored processes on this host (see Monitoring Selected Processes with SAPOSCOL)

Activities

To start the monitor, follow the procedure below:

...

1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.

2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.

3. Start the Operating System monitor from the list by double clicking it.

Procedure if an Alert Is Triggered

The following table provides information about what to do if an alert is triggered in this monitor:

MTE Name	Procedure
CPU CPU_Utilization	Many factors could lead to an excessively high CPU utilization, and you should therefore perform a detailed analysis. If the problem was caused by too many active processes in the host system, you could, for example, transfer CPU-intensive programs to times when there is a lower system workload, or to other host systems. You could also increase the number of CPUs or upgrade the CPU(s).
5minLoadAverage	If an average of more than two processes are waiting, this indicates that the CPU is reducing the performance of the entire system. · A high value for 5minLoadAverage and a high value for CPU_Utilization can indicate that too many processes are active on this server. · A high value for 5minLoadAverage and a low value for CPU_Utilization can indicate that the main memory is too small. The processes are then waiting due to excessive paging.
Paging Page_In Page_Out	Alerts for paging suggest that too many processes are being run in a host system, or that the main memory is too small for the number of running processes. Measures that you can take are to extend the main memory, to move processes to other host systems, and to delay memory-intensive program runs to times of lower system workload. On Windows platforms (unlike UNIX platforms), a page-out is performed as a precaution even without space being required. An alert in this MTE therefore has not meaning; under Microsoft Windows, you should only take Page_In into account. Under UNIX, on the other hand, Page_Out is the critical value for evaluating the paging.
Commit_Charge Commit_ChargeFree Commit_Percent	If the available commit charge falls under the threshold value, you should increase the value of the entire commit charge in the operating system. Note, however, that a larger virtual memory causes more paging if there is not enough main memory available (see also Memory Management under Microsoft Windows).
Swap_Space Freespace Percentage_Used	If an alert is generated in this subtree, you should increase the available swap space. For guidelines about the size of the swap space, see Memory Management Under UNIX and SAP Notes 0146289 and 0146528.
OS_Collector/State	If the operating system collector is not running on a system, you should restart SAPOSCOL.

Performance Overview Monitor in CCMS

You can use the Performance Overview monitor to obtain the most important values about the performance of the application servers of your system and to identify possible causes for performance problems. The various subtrees are taken from the following monitors of the SAP CCMS Monitor Templates monitor set:

· Buffers

· Dialog Overview

· Entire System

· Operating System

Features

The monitor contains the following monitoring tree elements (MTEs):

MTE Name (MTE Class)	Meaning	Additional Information
ResponseTime (R3DialogResponseTime)	Response time of the dialog service	Dialog Overview Monitor
UsersLoggedIn (R3UsersLoggedIn)	Number of users logged on
QueueTime (R3DialogQueueTime)	Average time in the dispatcher wait queue	Entire System Monitor
Load+GenTime (R3DialogLoad+GenTime)	Average load and generation time of CUA objects
DBRequestTime (R3DialogDbReqTime)	Average time for processing logical database requests
R3RollUsed (R3RollUsed)	Usage of the roll area as a percentage. The roll area is a memory area of a fixed, configurable size that belongs to a work process; it contains user-specific data and is the first memory that a work process obtains.	SAP Roll Area
EsAct (R3MemMgmtEsAct)	Utilization of the extended memory as a percentage. The extended memory contains the largest part of the user context. The page management of this memory is performed not by the operating system, but directly by the SAP system.	SAP Extended Memory
HeapAct (R3MemMgmtHeapAct)	Utilization of the private memory as a percentage. A work process is only assigned private memory if the roll area and extended memory are occupied; the work process is then reserved for the current user context until the end of the transaction (PRIV mode). Performance problems occur if too many dialog work processes are running in PRIV mode.	Private Memory
Program\Swap (R3BufferProgramSwap)	Swap rate of the program buffer	SAP Buffer
CPU_Utilization (CPU_Utilization)	Average utilization of the CPU on a host as a percentage	Operating System Monitor
Page_In (Page_In)	Average number of page-ins per second
Page_Out (Page_Out)	Average number of page-outs per second

Activities

To start the monitor, follow the procedure below:

...

1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.

2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.

3. Start the Performance Overview monitor from the list by double clicking it.

Security Monitor in CCMS

Use

You can use this monitor to monitor messages in the Security Audit Log, broken down into various areas, and to monitor security-relevant messages in the system log (see also Comparing the Security Audit Log and the System Log).

Prerequisites

You must have activated the Security Audit Log (transaction SM19).

Features

The monitor contains the following monitoring tree elements (MTEs):

MTE Name (MTE Class)	Meaning
Logon (SecurityLogon)	System logon events reported by the Security Audit Log: · Successful logons, unsuccessful logon attempts, and log offs by a user · Locking of a user due to unsuccessful logon attempts, and the removal of the lock
RFCLogon (SecurityRFCLogon)	RFC/CPIC logon events reported by the Security Audit Log: · Successful RFC/CPIC logon · Unsuccessful RFC/CPIC logon attempt
TransactionStart (SecurityTransactionStart)	Transaction events reported by the Security Audit Log: · Transaction started and failed transaction start · Transaction locked or unlocked
ReportStart (SecurityReportStart)	Events connected with starting reports reported by the Security Audit Log: · Successful start · Failed start
RFCCall (SecurityRFCCall)	Events connected with calling Remote Function Calls (RFCs) reported by the Security Audit Log: · Successful call · Unsuccessful call
UserMasterRecords (SecurityUserMasterRecords)	Events connected with changes to user master records reported by the Security Audit Log: · User deleted, locked, or unlocked · User master or authorizations of a user changed · Authorization/authorization profile created, changed, or deleted
System (SecuritySystem)	Events connected to system parameter changes reported by the Security Audit Log: · Configuration of the Security Audit Log changed · Application server started or stopped
Miscellaneous (SecurityMiscellaneous)	Other events reported by the Security Audit Log: · Download of a file · Call of a digital signature · Test message
System Log Messages (R3SyslogSecurity)	Messages in the system log for the security category; you can set the category in which a message is reported, the message text, and the severity and criticality of the alert using the message ID in transaction SE92

The system records security-relevant actions in the Security Audit Log. You decide which actions are recorded there and which should trigger an alert in the Alert Monitor on the Security Audit Log configuration screen (transaction SM19).

See also Defining Filters

Activities

To start the monitor, follow the procedure below:

...

1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.

2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.

3. Start the Security monitor from the list by double-clicking it.

Spool System Monitor in CCMS

Use

You can use this monitor to check the utilization of the spool system, to identify bottlenecks, and to investigate errors. For a general introduction to the SAP spool system, see the SAP Printing Guide.

Features

System Wide Subtree

The current level of use of the number set for spool numbers, and the wait times and status attributes for the individual spool services of the system are displayed in the System Widesubtree.

The following table provides information about the monitoring tree elements (MTEs) of this subtree:

MTE Name (MTE Class)	Meaning
SpoolNumbers (R3SpoolNumbers)	Spool numbers that every output request is assigned
UsedNumbers (R3SpoolUsedNumbers)	Percentage usage of the spool numbers; you must delete old output requests before this number reaches 100 percent
Status (R3SpoolServerStatus)	Is only displayed if the spool service belongs to an SAP application server
WaitTime (R3SpoolWaitTime)	Wait time in the spool service in seconds

Spool Servers Subtree

Spool monitoring objects are displayed in the Spool Servers subtree, broken down by application server. Subtrees are only created for the servers with at least one spool work process.

Entries in the Spool Category in the System Log (R3Syslog)

Messages in the spool category of the system log are displayed in the R3Syslog log attribute; you can set the category in which a message is reported, the message text, and the severity and criticality of the alert using the message ID in transaction SE92.

SpoolService

The SpoolService monitoring object contains the most important attributes about the spool system, its utilization, and the length of the wait queues. It includes the following MTEs:

MTE Name (MTE Class)	Meaning	Remarks
Utilization (R3SpoolWpUtilisation)	Utilization of the spool work processes as a percentage
NumberOfWpSPO (R3NumberOfWpSPO)	Number of spool work processes	You set the number of these work processes using the system parameter rdisp/wp_no_spo (For recommendations, see SAP Note 108799).
ErrorsInWpSPO (R3ErrorsInWpSPO)	Number of errors in spool work processes	This MTE counts the number of errors since the monitoring segment was created (that is, since the application server was started)
ErrorFreqInWpSPO (R3ErrorFreqInWpSPO)	Number of errors in spool work processes per minute
EndedWpSPO (R3EndedWpSPO)	Number of spool work processes that terminated after errors	You can use the process overview (transaction SM50) to determine whether a work process should be started again after an error.
QueueLength (R3SpoolQueueLength)	Used area of the dispatcher queue as a percentage	Output requests are buffered in the dispatcher queue on the spool server until a free work process accepts them.
ServiceQueue (R3SpoolServiceQueue)	Used area of the spool request queue as a percentage	The spool request queue takes output requests from the dispatcher queue when a free work process in the spool server accepts the output request.
ServiceQueuePriv (R3SpoolServiceQueuePriv)	Used area of the spool request queue for processing in chronological order as a percentage	If a spool server has several spool work processes, output requests can overtake each other. To maintain the sequence of requests, there are special work process-specific request queues, each with requests for one particular output device.
ServiceQueuePages (R3SpoolServiceQueuePages)	Number of pages in the spool request queue
DeviceCacheUsed (R3SpoolDeviceCacheUsed)	Used area of the entire device cache as a percentage	The device cache contains device definitions and server assignments for all work processes. Entries are taken into the cache as required and can be removed again if the cache becomes full.
DeviceCacheFixed (R3SpoolDeviceCacheFixed)	Used area of the fixed device cache as a percentage	This area contains information about the output devices for which there are requests in the host spool system that have not yet been reported as finished. The cache must therefore contain at least as many entries as the maximum number of devices that can be concurrently used.
HostspoolListUsed (R3SpoolHostspoolListUsed)	Used area of the host spool request list as a percentage	The host spool request list limits the number of requests in the host spool that can be managed with the spool service. To minimize database accesses, the list must be stored in shared memory. It deals with status queries for the current requests.

For more information about this topic, see Monitoring the Spool System and SAP Note 118057 (Flexible Configuration of the Spool Service of an SAP R/3 System).

Processing Groups

For classification of the output requests, we recommend that you assign both the output servers and the output devices to different classes. By having different spool servers that process different types (and priorities) of requests, you can avoid, or at least control, mutual obstruction of output requests. The Processing Groups node contains the possible processing groups:

MTE Name (MTE Class)	Meaning	Remarks
ProcessingGroup Adm (R3SpoolProcessingGroupAdm)	Spool administration tasks	Examples: · Activation of delayed requests · Deletion of obsolete requests · Rerouting of requests in the case of server failure
ProcessingGroup Reg (R3SpoolProcessingGroupReg)	Normal requests	Normal requests are requests to devices that are assigned to a spool server
ProcessingGroup Fro (R3SpoolProcessingGroupFro)	Requests for front end output devices	Front end output devices are defined by the user at operating system level. In the SAP system, there must only be one output device with the access method F (Front end) that sends output to the user’s default printer.
ProcessingGroup Vol (R3SpoolProcessingGroupVol)	Requests classified as mass printing	Mass printing means very large requests. Assign these requests to a separate spool server, to avoid obstruction of other output requests.
ProcessingGroup Pro (R3SpoolProcessingGroupPro)	Requests classified as production printing	You should assign the output requests that are required for trouble-free production operation (such as receipts) to production printing. We recommend that you connect output devices for this processing group locally.
ProcessingGroup Dsk (R3SpoolProcessingGroupDsk)	Requests classified as desktop printing	You should assign printers at your workplace to the desktop printing processing group. As they are often not available, they could obstruct other tasks. We recommend that you do not use this processing group for output requests that are important for the routine operation of your company.
ProcessingGroup Tst (R3SpoolProcessingGroupTst)	Requests classified as test printing	You should assign output devices that are used to test new device types or configurations to the test printing group.

Each of the various processing groups contains the following MTEs:

MTE Name (MTE Class)	Meaning
GroupWPs (R3SpoolGroupWPs)	Number of work processes
GroupJobs (R3SpoolGroupJobs)	Number of requests
GroupPages (R3SpoolGroupPages)	Number of pages
GroupMinWPs (R3SpoolGroupMinWPs)	Reservation of work processes
GroupMaxWPs (R3SpoolGroupMaxWPs)	Restriction of the number of work processes

When reserving work processes (GroupMinWPs), note that these then remain unused even in a situation where there are no requests for this group, the other work processes are all occupied, and requests for other groups are waiting for processing. In the same way, restricting the maximum number of work processes (GroupMaxWPs) means that even if there are more requests waiting to be processed in this group, and other work processes are free, the number of work processes for this group cannot be increased.

Output Devices (Devices)

You can also monitor particular output devices that are especially important for the trouble-free production operation of your system using the monitoring architecture. You can do this in Spool Administration(transaction SPAD), by choosing the Output Attributes tab page for an output devices and selecting the Monitor using the monitoring architectureindicator (see also Output Devices in the SAP Spool System). If you have activated this monitoring for at least one output device, there are monitoring objects in the Devices subtree with the short name of the output device and the following MTEs:

MTE Name (MTE Class)	Meaning
LPQ_Time (R3MASpoolDeviceLPQTime)	Time that the output request spends in the wait queue of the output device
Pages/Min (R3MASpoolDevicePages/Min)	Print speed in pages per minute
Message (R3MASpoolDeviceMessage)	Status attribute that contains possible errors from the transfer of the output request to the host spool system

Activities

To start the monitor, follow the procedure below:

...

1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.

2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.

3. Start the Spool System monitor from the list by double-clicking it.