Sie sind auf Seite 1von 4

Monitoring with the Generic Request and Message


Availability Monitoring with CCMSPING :

Installing an Agent on a Java Instance (Java Standalone System):

Creating the CSMREG User

A user with specific, greatly restricted authorizations is required to monitor remote
systems for the monitoring architecture. We recommend that you create and use the
user CSMREG for this purpose. You require this user for the following tasks, for
Performing the data collection in the monitored systems (see Monitoring Multiple
Systems: Defining RFC Connections)
Pushing the monitoring data from monitored systems that are connected to the
central monitoring system using CCMS agents (see Installing/Registering the
CCMS Agents for Experts)
Registering a System Component Repository (SCR)with a central repository
The CSMREG user must be created in all monitored systems; it is not created

1. Choose CCMS Configuration Alert Monitor, or call transaction RZ21.
2. Choose Technical Infrastructure Configure Central System Create CSMREG
3. Enter any password for this user.

Availability Monitoring with CCMSPING

With this function, you can monitor whether remote systems and their instances are
available for work from the Alert Monitor of your central monitoring system (CEN).
Important performance attributes for the dialog system are also collected on the
ABAP instances as of SAP Web Application Server 6.10.
Availability monitoring uses the alert and display functions of the monitoring
architecture. However, for data collection (that is, to determine whether a remote
system is active and available), availability monitoring uses the CCMS agent
CCMSPING (see also Installing Availability Agent CCMSPING). This agent is a
stand-alone program that runs outside the SAP system. By using an agent, you can
efficiently monitor the availability of a large number of systems from a central
location, without an inactive system causing an error in the display of the Alert

Availability monitoring has the following functions:
You can monitor selected systems for their availability. A system is regarded as
available if the message server responds to the availability agents query and at least
one application server is registered as active with the message server.

You can monitor ABAP application servers for their availability. You can use the
following monitoring methods to do this:

CCMSPING checks the availability of the application server at the

message server of the corresponding system once a minute. With this
monitoring method, an application server is regarded as active, if the server is
reported as active at the message server. This method is very fast and suitable
for centrally monitoring the availability of hundreds of systems. The
monitoring also displays the following performance attributes for monitored
application servers (as of CCMSPING with release status SAP Web AS 6.20):
Dialog response time
Number of users logged on
Standardized dialog response time (as of SAP release 4.5B)
You can check the availability of application servers using an RFC call
directly to the server. This is done using a data collection method of the
monitoring architecture, which is called every five minutes. With this
monitoring method, an application server is regarded as available if a free
dialog work process responds to this call; that is, if it is possible to log on to
this server.
You can monitor logon groups for their availability. A logon group is
regarded as available, if it is possible to log on to the application server with
the best dialog system quality (see Logon Load Balancing).

Configuring Availability Monitoring

You can customize the availability monitoring with CCMSPING for ABAP and Java
systems in a number of ways. The following functions are available:

You can activate and deactivate availability monitoring for particular systems

You can define the type of availability monitoring for application servers and
logon groups of an SAP system. When doing so, you can both create and change
monitoring rules, in accordance with which the servers and groups of the system are
monitored, and change the monitoring settings of servers and groups individually.

Logon groups exist only for ABAP application servers.

You can activate and deactivate availability monitoring for systems groups. You
can also decide whether these settings should also automatically apply for systems
that are later added to the relevant system group (see Monitoring System Groups with
If you have installed multiple CCMSPING agents, you can decide which
CCMSPING is responsible for the monitoring of a system. This is, for example,
useful for the monitoring of distributed system landscapes (see Using Multiple
You can select time periods in which the availability of selected systems is not
checked (see Creating and Changing a Monitoring Pause)
You can add new systems to the list of systems that can be checked using
availability monitoring.

You have performed the Installation of the Availability Agent CCMSPING.

Process Flow
1. Choose CCMS Configuration Alert Monitor, or call transaction RZ21.
2. The Monitoring: Properties and Methods screen appears. Choose Technical
Infrastructure Availability Monitoring Configure CCMSPING Monitoring.

3. The Configure Availability and Performance Overview screen appears. The screen
shows monitored and unmonitored systems in two lists, where you can display for the
monitoring of the monitoring systems by expanding the subtree for the corresponding

The configuration of the availability and performance overview is also set as the
analysis method for the nodes of the Availability and Performance Overview Monitor.
This means that you can display this screen by double-clicking a node in this monitor.

Use the CCMS agent SAPCCMSR with Option j2ee to transfer monitoring data for a
Java instance to a central monitoring system (CEN). You can display this monitoring
data both in the Alert Monitor and in the local Java system ( Monitoring service
of the Visual Administrator).