ccmsping

Availability Monitoring with CCMSPING

HE

LP

.BC

CC

M

SAP NetWeaver 04 SP Stack 11

SAP Online Help 22.04.2005

Copyright © Copyright 2004 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

Availability Monitoring with CCMSPING 690 2


Icons in Body Text

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help → General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation. Example text Emphasized words or phrases in body text, graphic titles, and table

titles.

EXAMPLE TEXT Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.



Availability Monitoring with CCMSPING.................................................................................... 5 Installing Availability Agent CCMSPING................................................................................ 7

Changing the Monitoring Frequency and Timeouts of CCMSPING................................. 10

Adding Systems to the Availability Monitoring Manually.................................................. 11

Finding and Correcting Errors with CCMSPING .............................................................. 12

Configuring Availability Monitoring....................................................................................... 15 Creating and Changing Monitoring Rules ........................................................................ 18

Changing Monitoring Setting of Servers and Groups ...................................................... 21

Using Multiple CCMSPING Agents .................................................................................. 22

Creating and Changing a Monitoring Pause .................................................................... 24

Monitoring System Groups with CCMSPING................................................................... 25

Availability and Performance Overview Monitor .................................................................. 27



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 [page 7]). 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 Monitor.

As of SAP NetWeaver 04 SP Stack 11, CCMSPING has the option –push, which extends the function of CCMSPING. The following new functions are available to you if you register CCMSPING with the –push option:

• CCMSPING actively sends availability data to CEN once a minute; you can make this interval longer as desired. Without this option, CEN only requests the availability data from CCMSPING every five minutes.

• You can register multiple CCMSPING agents with one CEN for the monitoring of your system landscape. This means that, in addition to a load balancing for availability monitoring, you can also have certain systems monitored by multiple CCMSPING agents, and therefore check accessibility.

• You can call the Java message server as well as the ABAP message server for availability monitoring. This means that you can monitor the availability of both ABAP and Java systems.

Features 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 agent’s 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. 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 Basis 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. 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.

• You can monitor Java instances for their availability. In this case, the corresponding message server is queried as to whether the instance is reported as active. In the case of double-stack systems, you can use both the Java and the ABAP message servers for the monitoring, if the availability monitoring is appropriately configured.

Availability monitoring is independent of monitoring of other objects in the Alert Monitor. You do not need to register a remote system in the central monitoring system to be able to monitor its availability.

The availability agent also waits for a short time (timeout) in case a system or an application server is temporarily unavailable.

CEN

CEN

Monitored ABAP System

ABAPMessage Server

AnwendungsserverAnwendungsserverABAPApplication Servers

Monitored Java System

Java Message Server

AnwendungsserverAnwendungsserverJava Instances

• System available?• List of active application servers• Basic performance attributes of theactive application servers

Logon check:possible to log

on to the server?

• System available?

• List of the activeapplicationservers

beliebiger Host

CCMSPING

Functional Principle of the Availabi lity Agent CCMSPING

Availabilitymonitoringconfiguration data

Any Host

CCMSPINGAlso possible to usemultiple CCMSPINGsfor availabilitymonitoring

You can also use other techniques for availability monitoring:

• Availability Monitoring with the GRMG [external]

• Triggering a Heartbeat Alert if No Values Are Reported [external]



Installing Availability Agent CCMSPING You must install the availability agent CCMSPING in your monitored IT environment before you can use availability monitoring with CCMSPING.

If you want to monitor systems with a release status below SAP Web Application Server 6.10, see SAP Note 415447.

Prerequisites For the –push option, you require a user with which this transfer can take place. The user requires authorization only for certain function modules, which do not themselves perform any additional authorization check. We recommend that you use the user CSMREG for this purpose (see Creating the CSMREG User [external]).

Procedure ...

1. Log on to the Software Center of the SAP Service Marketplace at http://service.sap.com/swdc with your SAP user name and password.

2. In the navigation bar, choose Download → Support Packages and Patches → Entry by Application Group → SAP NetWeaver → SAP NETWEAVER → SAP NETWEAVER 04 → ABAP Server → SAP KERNEL 6.40 32/64-BIT → <operating system> → Database Independent.

CCMSPING is backward-compatible in relation to the SAP Basis release. This means that:

• The release of the agent may be higher than the release of the central monitoring system (CEN) with which the agent is communicating. We do, however, recommend that you use as high a release status as possible for the CEN.

• The release of the agent can be higher than the SAP Basis release of the monitored SAP system.

3. In this directory, you will find the archive CCMAGENT.SAR. Download this file.

4. Decompress the archive with the SAPCAR tool. Take SAP Note 212876 into account.

You can install CCMSPING on any host in your IT environment, and it is not necessary to install the agent on a host with an SAP system. If you want to monitor a very large number of systems (>100=, we recommend that you do not install the agent on a host on which an SAP system is running. In distributed environments, you can also use multiple CCMSPING agents for your availability monitoring (see Using Multiple CCMSPING Agents [page 22]).

5. Under Microsoft Windows, ensure that a share is released on the host with the name saploc, and that the directory \\host\saploc\prfclog exists.

6. Install CCMSPING with the following call: ccmsping [-push] [-n<instance number>] -R

The two options have the following meaning:


http://service.sap.com/swdc


Option Meaning -push The option is available to you for CENs as of SAP NetWeaver 04

SP Stack 11. It activates the following new functions:

• CCMSPING actively sends availability data to CEN once a minute; you can make this interval longer as desired. Without this option, CEN only requests the availability data from CCMSPING every five minutes.

• You can register multiple CCMSPING agents with one CEN. This means that, in addition to a load balancing for availability monitoring, you can also have certain systems monitored by multiple CCMSPING agents, and therefore check accessibility.

• You can call the Java message server as well as the ABAP message server for availability monitoring. This means that you can monitor the availability of both ABAP and Java systems.

-n<instance number>

Use this option if you want to install multiple CCMSPING agents on one host. Then assign different instance numbers (between 00 and 100) for the instances of CCMSPING. By default, CCMSPING uses the instance number 00.

7. Enter the following data during the installation (if there is a default value for an entry, this is shown in square brackets. If you want to use this default value, simply press the ENTER key):

Parameter Meaning

R/3 system ID System ID of CEN

client Valid client in CEN

user Valid user in CEN; this user is used once to create an RFC connection to CCMSPING.

language Language (such as en = English, de = German)

hostname of message server

Host name of the message server in CEN

use Load Balancing

Should load balancing be used [Y/N]?

We recommend that you register CCMSPING with a fixed application server, since you can then find possible error messages more easily in the CCMS Selfmonitoring monitor (see Finding and Correcting Errors with CCMSPING [page 12]).

group Logon group (only for load balancing)


Host name of an application server in CEN (only without load balancing)

system number Instance number of the above application server (only without load balancing)

route string Host and port of the SAProuter in the format /H/<Router Host>/S/<Router Port>/H (only if the connection to the central monitoring system goes through a router)



Parameter Meaning

trace level Should a trace be set (1,2,3) or not (0)?

Hostname of gateway

Host of the gateway, usually the message server of CEN

System number Instance number

password Password of the above user; the password is not stored, it is used only once for the logon

8. If you are installing CCMSPING with the –push option, also enter the following data about the CSMREG user:

Parameter Meaning

client Client of the CSMREG user

user Name of the user, usually CSMREG

language Language (such as en = English, de = German)


use Load Balancing

group


system number

route string

trace level

Connection data for CEN, see above

password Password for the CSMREG user; the password is stored in the secure store in an encrypted file called passwd.

9. In relation to CEN, CCMSPING functions as an RFC server that is registered at the CEN gateway. If you have successfully registered with CEN, the system displays the message Successfully registered at <SID>.

10. If you are registering CCMSPING on a Microsoft Windows host, the agent is entered and started as a service during the registration. The agent is automatically restarted at every restart. Enter the following information for this:

Parameter Meaning

Starttype of service Indicator of whether the service is to be automatically started

DomainName/UserName Account under which the service is to be started

11. For UNIX platforms, CCMSPING is not yet automatically started. Start it using the command ccmsping –DCCMS. On a UNIX platform, you must also ensure yourself that CCMSPING is automatically started after a restart of the server (for example, by entering the start command in INITTAB).

12. You have completed the installation of CCMSPING. For you to be able to check the availability of systems and application servers, two prerequisites must be fulfilled:

There must be a maintained version of the file SERVICES with the port numbers of the message servers of the monitored systems on the host on which CCMSPING is installed (see Adding Systems to the Availability Monitoring Manually [page 11]).



The required database tables must be maintained in the CEN (the system in which CCMSPING is registered). You can do this, for example, using the Upload System List button (see Configuring Availability Monitoring [page 15]).

You can also change technical settings of the CCMSPING, such as the frequency of the monitoring, or the timeouts that define how long CCMSPING waits for a response from the message servers and the application servers (see Changing the Monitoring Frequency and Timeouts of CCMSPING [page 10]).

Changing the Monitoring Frequency and Timeouts of CCMSPING In addition to configuring which systems and application servers are to be monitored by CCMSPING (see Configuring Availability Monitoring [page 15]), you can also define the frequency with which CCMSPING should perform the availability monitoring, and for how long it should wait for a response from the message servers and the application servers when it does so.

Activities Changing Timeouts and Monitoring Frequency of CCMSPING (with –push option) The technical settings of the registered availability agent CCMSPING are stored in the table ALAVLCTRL. This table is only relevant for those agents that actively report the availability values to the central monitoring system (CEN), that is, agents that were registered with the –push option (see Installing the CCMSPING Availability Agent [page 7]).

Since there is no separate user interface for maintaining the technical settings, you need to make the settings in the Data Browser (transaction SE16): ...

1. Start transaction SE16 in CEN. The Data Browser: Initial Screen appears.

2. In the Table Name field, enter ALAVLCTRL and choose (Table Contents).

3. On the Data Browser: Table ALAVLCTRL: Selection Screen, choose the (Execute) button.

4. There is a separate row for each agent that is registered with CEN. The RFC destination of the agent is displayed as its name in the PING_DEST column. The destination has the naming convention CCMSPING.<Host>.<InstNo (Default=00)> To change an entry, select the desired agent, and choose (Change). You have the following options here:

Changing the Timeout for Message Servers

To change the length of time for which a specific CCMSPING waits for a response from the ABAP and Java message servers, enter the desired wait time in milliseconds for the relevant CCMSPING as the value of the entry PING_TIMEOUT. The default value is 1500 (1.5 seconds).

Changing the Frequency of the Availability Monitoring

By default, the CCMSPING agent calls the message server once a minute for availability monitoring. It is not possible to have the monitoring performed more frequently. To have the monitoring performed less frequently, enter the desired interval in seconds for the relevant CCMSPING agent as the value of the entry PING_FREQ.



Two additional entries: TRACE and TIMESTAMP are useful for finding and correcting errors. For more information, see Finding and Correcting Errors with CCMSPING [page 12]

5. During the logon check, the CCMSPING calls the application server directly. To change the timeout for these calls, proceed as follows:

a. Start transaction RZ21 in CEN.

b. In the Methods group box, select Method Definitions and choose Display Overview.

c. Select the method CCMS_AVAIL_LOGON_CHECK, and choose Edit Data ( ).

d. The system displays the Monitoring: Methods screen. Choose change mode with the Display ↔ Change ( ) pushbutton, and choose the Parameters tab page.

e. To change the time that CCMSPING waits for the response of an application server in the case of an RFC call, enter the desired wait time in milliseconds for the RFCPING_TIMEOUT parameter. The default value is 10000 (10 seconds).

f. Save your entries.

Changing the Timeout of the Availability Agent CCMSPING (Without the –push Option) If you have registered CCMSPING without the –push option, the availability monitoring is essentially performed every five minutes. You can also register only one CCMSPING with your CEN. You can, however, change the above timeouts. To do this, follow the procedure below: ...

1. Start transaction RZ21 in CEN.

2. In the Methods group box, select Method Definitions and choose Display Overview.

3. Select the method CCMS_System_Availability and choose Edit Data ( ).

4. The system displays the Monitoring: Methods screen. Choose change mode with the Display ↔ Change ( ) pushbutton, and choose the Parameters tab page.

5. To change the time that CCMSPING waits for the response of the message server, enter the desired wait time in milliseconds for the TIMEOUT parameter. The default value is 1500 (1.5 seconds).

6. To change the time that CCMSPING waits for the response of an application server in the case of an RFC call, enter the desired wait time in milliseconds for the RFCPING_TIMEOUT parameter. The default value is 10000 (10 seconds).

7. Save your entries.

Adding Systems to the Availability Monitoring Manually To collect the availability of the systems to be monitored, CCMSPING communicates with the ABAP and the Java message servers of the corresponding systems, depending on the system type. To do this, CCMSPING requires the connection data for this server.

You do not normally need to determine the connection data for the ABAP message server yourself, since this data should be available for SAPLogon on every SAP front end in your system landscape. The data is in the services file, which contains the port numbers of the ABAP message servers in the format sapms<SysID> <Port_No.>/tcp.



This procedure describes how you can manually obtain the connection data for ABAP or Java message servers of a system to be monitored.

Procedure To manually add a new system to availability monitoring, proceed as follows: ...

1. Start transaction RZ21 in the central monitoring system, and choose the menu path Technical Infrastructure → Availability Monitoring → Configure CCMSPING Monitoring.

2. Choose the button Action→ Create System.

3. Specify the system ID of the system to be monitored, and choose the Continue button. The Connection Data and Monitoring Options screen appears

4. To monitor the system using the ABAP message server, proceed as follows: ...

a. Fill out the input fields Message Server Host Name and IP Service Name. The IP Service follows the naming convention sapms<SysID>.

b. For availability monitoring, CCMPSING requires an entry for the corresponding system in the services file on its host (in Microsoft Windows XP systems, under [Drive]:\WINDOWS\system32\drivers\etc, in UNIX systems, under /etc). The entry has the following format: sapms<SysID> <Port No.>/tcp.

c. The port number that you are looking for usually has the format 36<system number>. Enter the corresponding line in the services file, and save the file.

5. To monitor the system using the Java message server, proceed as follows: ...

a. Fill out the input fields Message Server Host Name and Message Server HTTP Port.

b. If you do not have this data, start the Visual Administrator for the desired Java system, and choose the following path in the navigation bar: Cluster → Server → Services → Message Info. If the service is not yet running, start it.

c. Choose Runtime → Parameters; you can see the host as the value of the parameter server host, the port as the value of the parameter ms/http_port.

6. If you want to set the monitoring options, follow the procedure described in Creating and Changing Monitoring Rules [page 18].

7. Save your changes.

Result The desired system is included in the list of systems that can be monitored from the monitoring architecture. You can now activate the monitoring for this system using the normal user interface. To display the availability data, expand the SAP CCMS Monitor Templates monitor set in transaction RZ20 and open the Availability and Performance Overview Monitor [page 27].

Finding and Correcting Errors with CCMSPING If problems occur during the availability monitoring with CCMSPING, work through the points below.

Prerequisites The following points apply for CCMSPING agents, which are actively reporting to the central monitoring system (registration with the –push option).



Activities What do I need to do, if CCMSPING does not provide availability values with the required frequency?

In the case of very large IT landscapes to be monitored, it is possible that CCMSPING cannot perform the entire check in one minute. In this case, you have two options:

Have the availability monitoring performed less frequently (see Changing the Monitoring Frequency and Timeouts of CCMSPING [page 10]).

Have the availability monitoring performed by multiple CCMSPING agents (see Using Multiple CCMSPING Agents [page 22]).

What do I need to do, if the logon check fails, although it is possible to log on to the application server?

Check whether the following steps improve the situation:

Increase the timeout fort he logon check (see Changing the Monitoring Frequency and Timeouts of CCMSPING [page 10]).

Check the host name resolution.

I want to activate debug tracing. What options do I have?

You have two options for activating tracing for a CCMSPING:

During the registration (see Installing the CCMSPING Availability Agent [page 7]), instead of setting the value for the Trace Level to 0, you can set it to 1,2, or 3. The agent writes the trace to a file in its working directory (\\host\saploc\prfclog\CCMSPING_<InstNo>). The actions of the CCMSPING agent itself are written in this trace.

There is an entry in the table ALAVLCTRL in CEN for each registered CCMSPING (see also Changing the Monitoring Frequency and Timeouts of CCMSPING [page 10]). Call up this table in transaction SE16, and set the TRACE entry for the desired CCMSPING.

If TRACE=1, the trace information is written to the Log log attribute of the Data Supplier monitoring object. You can find this in the CCMS Selfmonitoring Monitor, in the instance-specific subtree of the server with which CCMSPING is registered. Select the MTE and choose (Details) to display all of the messages of the trace. Actions of the ABAP infrastructure for availability monitoring are written in this trace.

C u r r e n t S t a t u s ( 20.12.2004 , 16:42:45 )

CCMS Selfmonitoring

MoniInfra_Hiost1_CEN_00

Name of the monitor

Node Display Off

CEN

Subtree withinstance-specific data

Data Supplier

CCMSPING.Host1.00: Could not access standard SLD (TX sldapicust)Log

Central monitoring system

Object with datasupplier messages

Select this MTE, and choosethe (Details) button to display all messages.

If TRACE=5, the function module for collecting the availability values of the relevant CCMSPING starts an endless loop, so that you can start debugging the ABAP processing using transaction SM50.



I have changed the configuration of the availability monitoring. How do I determine whether the responsible CCMSPING has received these changes?

The table ALAVLCTRL (see above) has a TIMESTAMP entry. The row CCMS_SYSTEM_PING_DEST contains the timestamp of your last change to the monitoring configuration in this entry, that is the last time at which you changed the monitoring settings. For each registered CCMSPING agent, the TIMESTAMP entry contains the status of its worklist, that is, the systems and instances that this CCMSPING is to monitor.

Every CCMSPING monitors this timestamp every minute. If the status of the agent is currently older than the status of the last configuration change, the agent downloads its current worklist from CEN and updates its timestamp. The TIMESTAMP entry of the agent is then the same as the corresponding entry in the row CCMS_SYSTEM_PING_DEST. You can therefore use the timestamps to check whether the agent is working with its current worklist.

How do I determine whether a CCMSPING agent is actively reporting availability values to CEN?

If you have registered a CCMSPING agent with a CEN with the –push option, the following monitoring object is displayed in the CCMS Selfmonitoring Monitor for System-Wide Data there:

C u r r e n t S t a t u s ( 20.12.2004 , 16:42:45 )

CCMS Selfmonitoring

CCMS_Selfmonitoring

Name of the monitor

-Node Display Off

CEN

Subtree with system-wide data

Availability Monitoring

CCMSPING active reporting in operationCCMSPING Technology Enabling

Central monitoring system

How do I determine which CCMSPING agents are registered with CEN with the –push option, and whether these agents are running correctly?

Agents that are registered with CEN with the –push option are monitored by the monitoring architecture. The results are displayed in the Selfmonitoring CCMS Agents Monitor. The following data is displayed there:

C u r r e n t S t a t u s ( 20.12.2004 , 16:42:45 )

Selfmonitoring CCMS Agents

CCMSPING.Host1.00 Individual agent

Name of the monitor

Display OffNode

CEN\CCMS_Selfmonitoring\...\CCMS_Agents\...

DescriptionStatusHeartbeat

CCMSPING.Host1. 00 controlling CEN Host1_local on Host1active since 18.12.2004, 10:04:58. Last test: 20.12.2004, 16:06:0951 sec

Information about the agent

Availability 100 %Agent Version patch collection 2004/6, OSS note 694057, CCMS version 20040229, 32Details 19.11.2004 16:36:20: Agent calls as [BCE:000:CSMREG], RFC_PING okList of CENs no additional Central System



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 [page 18], in accordance with which the servers and groups of the system are monitored, and change the monitoring settings of servers and groups [page 21] 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 CCMSPING [page 25]).

• 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 CCMSPING Agents [page 22]).

• You can select time periods in which the availability of selected systems is not checked (see Creating and Changing a Monitoring Pause [page 24])

• You can add new systems to the list of systems that can be checked using availability monitoring.

Prerequisites You have performed the Installation of the Availability Agent CCMSPING [page 7].

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 system:



Initial Screen for the Configuration of Availability and Performance Overview

Request a new list of ABAP systems thatcan be monitored

List of the monitoredsystems. You canchange themonitori ails forapplicat rversand lo oups foreach system.

List of the systemsthat are notmonitored

Monitoring setting forapplication servers:

Is logon possible?

Is application serverreported as activeat the respectivemessage server?

Monitoring setting forlogon groups:

Is logon possible?

ng detion se

gon gr

Drop-down menus with views and actions; you an use these to display various information about themonitored systems, system groups, application servers, and logon groups; you can also change themonitoring functions for the monitored and unmonitored systems here (see buttons below).

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 [page 27]. This means that you can display this screen by double-clicking a node in this monitor.

Displaying the Monitoring and System Data There are various views available on the Configure Availability and Performance Overview screen, with which you can display information about the monitored systems and their application servers and logon groups. To activate a view, choose the Views button, and then one of the following buttons:

Views Meaning Additional Information

System Info View

The valid monitoring rules and the responsible CCMSPING are displayed for the monitored systems

Using Multiple CCMSPING Agents [page 22]

Group/Instance View

The settings for the monitoring options for application servers and logon groups for the monitored systems are displayed

Creating and Changing Monitoring Rules [page 18]

Administration View

Time and users of the last monitoring change are displayed

Connection View

Message server port, message server host, and router string are displayed

Availability Monitoring with CCMSPING [page 1]

Activities

Changing the Monitoring of Systems

To change the monitoring of systems, select the desired systems on the Configure Availability and Performance Overview screen by selecting the folder icon of the relevant systems. The following functions are then available to you:



Function Command Additional Information

Activating the Monitoring of Systems

In the Unmonitored Systems subscreen, choose Monitoring → Activate System Monitoring.

Activating the Uniform Monitoring of Systems

In the Unmonitored Systems subscreen, choose Monitoring → Define Uniform Monitoring.

Changing the Monitoring Rules for Systems

In the Monitored Systems subscreen, choose Monitoring → Change Connection/Options.

Changing the Uniform Monitoring of Systems

In the Monitored Systems subscreen, choose Monitoring → Use Uniform System Options.

Creating and Changing Monitoring Rules [page 18]

If you want to monitor systems using the Java message server, you must first enter the connection data. Proceed as described in Adding Systems to Availability Monitoring Manually [page 11].

Creating and Changing the Monitoring Pause for Systems

Choose Breaks → Create Monitoring Pause or Create Uniform Monitoring Pause.

Creating and Changing a Monitoring Pause [page 24]

Deactivating the Monitoring of Systems

In the Monitored Systems subscreen, choose Monitoring → Deactivate System Monitoring.

Delete Systems from the System List

Choose the button Monitoring → Delete System(s).

You can also activate and deactivate system monitoring by moving selected systems to the desired list by Drag&Drop.

Monitoring System Groups

You can combine systems into system groups (see System Groups in the Alert Monitor [external]), where one system can belong to multiple system groups. In this way, you can, for example, organize systems into system groups by their function (development, quality assurance, production), their release status, or their geographic location.

In large IT environments, it can greatly simplify the configuration of availability monitoring, if you can, for example, monitor all systems in a system group with one command. You can also set up the monitoring so that changes to the systems that belong to a system group automatically cause a change in the availability monitoring of the relevant systems.

For more information about monitoring system groups, see Monitoring System Groups with CCMSPING [page 25].

Changing the Monitoring of Application Servers and Logon Groups

You can change the monitoring settings for servers and groups [page 21] on the Configure Availability and Performance Overview by selecting the relevant indicator in the ALV Tree Control.

Add New Systems to the List of ABAP Systems that Can Be Monitored

On the Configure Availability and Performance Overview screen, choose Load System List ( ). If the desired ABAP system does not appear on the list, add the system to it manually (see Add Systems to the Availability Monitoring Manually [page 11]).



The SAPMSG.INI file, which is also used for functions of SAPLOGON, is uploaded from the front end for the system list. It does not contain any standalone Java systems.

Changing Technical Settings of the Availability Agent CCMSPING

You can also change technical settings of the registered CCMSPING availability agents, such as the frequency of the monitoring, or the timeouts that define how long CCMSPING waits for a response from the message servers and the application servers (see Changing the Monitoring Frequency and Timeouts of CCMSPING [page 10]).

Result You have customized the availability monitoring to your requirements. Use the Availability and Performance Overview Monitor [page 27] from the SAP CCMS Monitor Templates monitor set to perform availability monitoring.

Creating and Changing Monitoring Rules You can create monitoring rules in the configuration of the availability monitoring with CCMSPING. You define the type of monitoring for the relevant system in these rules. You have the following options:

• Monitoring the application servers:

Ping Monitoring

With this type of monitoring, the availability agent queries the message server of the corresponding system as to whether the application server is reported as active. It does not perform a check at the monitored server itself to see whether, for example, it is possible to log on. This monitoring is possible for both Java and ABAP application servers, since CCMSPING can communicate with both the ABAP and Java message servers, depending on the communication settings of the system.

Important performance attributes from the dialog service of the server are also reported in availability monitoring for ABAP application servers (see Availability and Performance Overview Monitor [page 27]). The prerequisite for this is the existence of logon groups in the corresponding system.

Check Logon

With this monitoring type, the monitoring architecture performs an RFC call in the relevant server. Although no actual logon is performed, you can, however, determine whether it is possible to log on - since the RFC call requires a free dialog work process, in the same way as a user logging on does. This method also checks whether the database of the monitored system is functioning and is connected to the system. This monitoring is only possible for ABAP application servers.

This type of RFC call is not subject to the quotas that you can set with the various profile parameters with the prefix rdisp/rfc to prevent overloading due to RFC calls (see System Configuration for Parallel RFCs [external]).

• Monitoring the logon groups

You can check whether it is possible to log on to the currently selected ABAP application server of a logon group. This function uses the same technique to do this as Check Logon.



Prerequisites This procedure is part of the Configuring Availability Monitoring [page 15] process. It is therefore a prerequisite that you have already performed the part of the process that is to be performed before this procedure.

Procedure The system is displaying the Configure Availability and Performance Overview screen. To create or change a monitoring rule for one or more systems, follow the procedure below: ...

1. Select the desired systems by choosing the folder symbol for the corresponding systems.

Note that a system is only correctly selected when the entire line is highlighted:

Monitored Systems System Description Monitor SystemAIJC11

APO Hotpackagetest 3.0AB2B 3.0 Target

Monitored Systems System Description Monitor SystemAIJC11

APO Hotpackagetest 3.0AB2B 3.0 Target

2. Proceed as follows, depending on whether the desired systems are already monitored:

To create an availability rule for a system that has not been monitored until now, choose Monitoring → Activate System Monitoring in the Unmonitored Systems subscreen. This activates the monitoring for this system; confirm the relevant query.

To assign an identical monitoring rule to multiple systems that were not previously monitored, select these systems, and choose Monitoring → Define Uniform Monitoring.

To change the availability rule for a monitored system, choose Monitoring → Change Connection/Options in the Monitored Systems subscreen.

To assign an identical monitoring rule to multiple monitored systems, select these systems, and choose Monitoring → Use Uniform System Options.

3. The Connection Data and Monitoring Options screen appears. The screen has the following structure:



Screen for Creating and Changing a Monitoring Rule

System to which thisrule applies

Specify the connectiondata for the system; if youused a system from the list of existing systems, youonly need to enter data forthe Java message server

Monitoring options for application servers; specifies how the application servers of thesystem are monitored, by default

Monitoring options for logon groups; specifieshow the logon groups of the system aremonitored, by default

Cancel

Destination of the CCMSPING that isresponsible for the monitoring of this system

tor All Application Servers

ing Monitoring Check Logon

Options for Logon Groupsheck of L ogon Groups

Only Selected Logon Groups

atically Add New Logon Groups to the Monito ring

te Check for All Groups, Including New Groups

on of Responsible CCMSPING

Connection Data and Options

Save the settings made

This information isnot displayed ifyou have chosenuniform monitoring.

Connection Data and Monitoring Options

System

Description

Connection Data: Java Message Serve r

Message Server Host Name

Name of the IP Service

Router String

Message Server HTTP Port

Router String

Monitoring Options for Application Serve rNo M of Application Servers

Moni elected Application Servers

Auto Add New Application Servers to the Monitoring

Moni

Ping Monitoring

P

Check Logon

MonitoringNo C

Check

Autom

Activa

Destinati

Copy

Message Server Host Name

onitoring

tor Onl y S

matically

Make the following entries in this screen:

Group box Meaning

System and Connection Data

Information about the corresponding system. For more information, see Add Systems to the Availability Monitoring Manually [page 11])

Monitoring Options for Application Servers

Settings for monitoring application servers (see above); you can choose the following radio buttons:

• No monitoring of application servers; only the system is monitored for its availability; if a server was previously monitored, this setting is deleted

• Monitor only selected application servers; with this option, only the servers that you manually select in the Group/Instance View are monitored.

• Automatically Add New Application Servers to Monitoring; with this option, the servers that currently exist are not monitored (which you can change manually in the Group/Instance View); if the rule is active, newly added servers are automatically monitored

• Monitor All Application Servers; with this option, all servers, including new servers added later are monitored.

Monitoring Options for Logon Groups

You can set whether logon groups are to be monitored; you can specify, in the same way as with the monitoring of application servers, whether newly added groups should automatically be included in the monitoring.

Destination of Responsible CCMSPING

If you have installed multiple CCMSPING agents, you can determine here which CCMSPING is responsible for the monitoring of this system (see Using Multiple CCMSPING Agents [page 22]).

4. Save your entries.



Result You have created or changed a monitoring rule for the selected systems, on the basis of which the corresponding systems will be monitored. To further refine monitoring, for example, to change the monitoring of individual application servers or logon groups, follow the instructions in Changing Monitoring Settings for Servers and Groups [page 21].

Changing Monitoring Setting of Servers and Groups You can specify in the configuration of the availability monitoring with CCMSPING whether and how application servers and logon groups of this system are monitored. You have two options here:

• You can use a monitoring rule that defines for the system how application servers and logon groups are monitored (see Creating and Changing Monitoring Rules [page 18]).

• You can modify the monitoring of individual servers and groups directly in the user interface of the ALV Tree Control. This procedure is described here.


Procedure ...

1. The system is displaying the Configure Availability and Performance Overview screen. To edit the monitoring settings (defined by the valid monitoring rules) for one or more systems, follow the procedure below:

Monitored Systems Logon Check J2EE Server Ping Server Ping Logon Group CheckAIJ

Application Servers

Logon Groups

as0030_AIJ_47as0031_AIJ_31

PUBLICSPACE

Find

Hide Column

Help

Optimal Width

Select visible items

Select all items

Deselect visible items

Deselect all items

Monitored Systems Logon Check J2EE Server Ping Server Ping Logon Group CheckAIJ

Application Servers

Logon Groups

as0030_AIJ_47as0031_AIJ_31

PUBLICSPACE

Expand the desired subtrees ...... and select the desired settings

Changing Monitoring Settings for Multiple Servers/Groups

Change Monitoring Settings for Individual Servers/Groups

Right-click the column title of the desired monitoringtype ...

... and choose the servers/groups for whichyou want to activate/deactivate monitoringin the context menu



2. To change monitoring settings for individual application servers or logon groups, expand the subtrees of the corresponding system and select the desired checkboxes.

3. To change the monitoring settings for multiple application servers or logon groups, choose the column title of the desired monitoring type with the right mouse button and choose for which servers/groups you want to activate/deactivate monitoring in the context menu.

You want to set up the Server ping for all application servers of systems J11, J12, and J13. To do this, select these systems and choose the Expand Subtree ( ) button. Now right-click Server Ping column title, and choose Select Visible Items in the context menu.

4. Save your changes.

Result You have changed the monitoring settings for the selected systems.

Using Multiple CCMSPING Agents You can use the CCMSPING agent to monitor the availability of your SAP system landscape. Normally, you only require one CCMSPING agent to monitor your entire system landscape. However, you can also use multiple CCMSPING agents. This can have the following advantages, for example:

• You can extend the availability monitoring to include accessibility monitoring. In this way, you can monitor the connections to the systems in addition to the actual monitoring of the systems.

In this scenario, it can be useful that one system is monitored by multiple CCMSPING agents, to check the accessibility of the system from various points. You can do this by combining these CCMSPING agents into an agent group, and assigning this agent group the system as the responsible CCMSPING.

• You can configure various CCMSPING agents different (such as setting the frequency of the availability monitoring differently; see Changing Technical Settings of CCMSPING [page 10]), to fulfill different requirements for availability monitoring of different systems.

• In distributed landscapes, it is possible that the response times of the RFC calls, with which the logon checks for an instance are performed, become too large. In this case, assign CCMSPING agents for which the connection to the systems to be monitored is sufficiently quick in each case.



A01

CCM

CEN

C01 C02 C03

CCMSPING

A02 A03

SPINGB01 B02 B03

CCMSPING

Multiple CCMSPING Agents in Distributed Landscapes


You can only use multiple CCMSPING agents, if you install all CCMSPING agents with the –push option (see Installing Availability Agent CCMSPING [page 7]). Without this option, the registration of an additional CCMSPING might overwrite existing registrations in CEN.

Activities Combining Multiple CCMSPING Agents into an Agent Group If you want to monitor the availability of certain systems using multiple CCMSPING agents, you need to combine the different CCMSPING agents into an agent group and then assign this group to the relevant systems as the responsible CCMSPING.

To combine multiple CCMSPING agents into an agent group, proceed as follows: ...

1. The system is displaying the Configure Availability and Performance Overview screen. Choose CCMSPING → Manage CCMSPING Groups.

2. To assign a CCMSPING agent to an agent group, choose the (Add Group Entry) button, and specify the name of the desired group on the Add Entry for Agent Group screen in the Group Name field (you can also create a new agent group in this way). Then enter the destination of the desired agent in the CCMSPING Agent field, and choose (Continue).

3. To delete the assignment of an agent to an agent group, select the desired assignment and choose (Delete Group Entry).

If you want to delete the last assignment of an agent to a particular agent group that is still assigned to systems as the Responsible CCMSPING, the system displays a corresponding warning.



Displaying the Responsible CCMSPING The system is displaying the Configure Availability and Performance Overview screen. To display the CCMSPING agent or agent group responsible for your monitored systems, proceed as follows:

Choose the button Views → System Info View. The RFC destination of the responsible CCMSPING or the responsible agent group in each case is shown in the corresponding row. The destination has the following naming convention:

CCMSPING.<Host>.<instance number>

By default, <instance number> is 00.

Changing the Responsible CCMSPING To change the CCMSPING agent responsible for monitored systems, proceed as follows: ...

1. The system is displaying the Configure Availability and Performance Overview screen. Select the desired systems by choosing the folder symbol for the corresponding systems.

2. Choose CCMSPING → Change Responsible CCMSPING.

3. Choose the desired CCMSPING for the selected systems. The list of CCMSPING agents displayed in the input help contains the RFC destinations of all CCMSPING agents that are registered with this system, and also all agent groups that you have created.

4. Confirm your selection and save your changes.

You can also change the responsible CCMSPING on the Connection Data and Monitoring Options screen (see Creating and Changing Monitoring Rules [page 18]).

Creating and Changing a Monitoring Pause In the configuration of availability monitoring with CCMSPING, you can deactivate the monitoring during certain specified times, such as during the weekend or for maintenance work. You can also repeat these monitoring pauses daily or weekly.


Procedure The system is displaying the Configure Availability and Performance Overview screen. If you want to create or change a monitoring pause for monitored systems, follow the procedure below: ... ...

1. Select the desired systems by choosing the folder symbol for the corresponding systems.

2. If you have only selected one system, or want to create different monitoring pauses for the selected systems, choose the Pauses button and then Create Monitoring Pause.

If you want to create an identical monitoring pause for the selected systems, choose the Pauses button and then Create Uniform Monitoring Pause.



3. The Maintain Time not Monitored screen appears. The screen has the following structure:

Screen for Creating and Changing Monitoring PausesSystem for which the monitoring pauses apply(the field is not displayed if you create a uniform monitoring pause)

Daily monitoring pause; specify the start and end times of the pause

Weekly monitoring pause; specify the start and end time points of the pause. The pause isscheduled every week from then at the timesand on the week days of the first pause.

Single monitoring pause; specify the start and end times of the pause

Existing monitoring pauses; you can identifypauses that are repeated weekly (W) and daily(T) in the last column

Save the monitoring pause created above Cancel

Maintain Time not Monit

Name of the System

Period with no Avai lab ility Monitoring

Daily from

Weekly from

Once from

To

To

To

Start Time

End Time

Start Date

Start Time

End Date

End Time

Start Date

Start Time

End Date

End Time

Start Date Start Time End Date End Time Period ic

Save

or ed

4. You can define monitoring rules for single monitoring pauses, and pauses that are

repeated daily or weekly. The monitoring pauses that are repeated daily take effect immediately, the monitoring pauses that are repeated weekly are valid from the time specified, each time for the selected period of time and on the selected weekday.

5. Save the monitoring rule that you have created. Once you have successfully saved your rule, the system displays a success message and your rule appears in the list at the bottom of the screen. If you have selected multiple systems, and do not want to create a uniform monitoring pause, repeat these steps for all selected systems.

To change a monitoring rule, delete the rule from the list, and recreate the rule.

6. To leave the screen, choose Cancel ( )

Result The selected systems are not monitored for their availability during the specified times; that is, no corresponding alerts are generated during these time periods.

Monitoring System Groups with CCMSPING You can combine systems into system groups (see System Groups in the Alert Monitor [external]), where one system can belong to multiple system groups. In this way, you can, for example, organize systems into system groups by their function (development, quality assurance, production), their release status, or their geographic location.

You can also configure the availability monitoring to use system groups. In large IT environments, it can greatly simplify the configuration, if you can, for example, monitor all systems in a system group with one command.

You can also declare the system groups as reference system groups. A monitoring setting that is used on all systems in this group is assigned to a reference system group. If another system is later added to a reference system group of this type, this system automatically receives the monitoring settings that have been assigned to the reference system group. In the same way, a system is no longer monitored, if it is no longer a member of this reference system group.




Activities Selecting All Monitored Systems of a System Group The system is displaying the Configure Availability and Performance Overview screen. To select all monitored systems of a system group, choose System Groups → Select Systems of a Group. Choose the desired system group, and confirm your entry.

You can now make the desired availability monitoring settings for the selected systems, as described in Creating and Changing Monitoring Rules [page 18].

Adding and Deleting Reference System Groups The system is displaying the Configure Availability and Performance Overview screen. Choose System Groups → Manage Reference System Groups. A screen appears on which the existing reference system groups are displayed. The following functions are available, among others:

Use Command

Add a new reference system group

Choose (Add Reference System Group), and choose the desired system group. The Uniform Monitoring Options screen appears (see below).

Delete a reference system group

Select the desired system group and choose (Delete Reference System Group). This deletes only the reference, and not the system group itself.

You can use the listed functions to save existing system groups as reference system groups or to remove this assignment. To create or edit system groups themselves, however, use the system group maintenance. To start the system group maintenance, choose (Start System Group Maintenance).

Editing the Settings of a Reference System Group ... ...

1. The system is displaying the Configure Availability and Performance Overview screen. Choose System Groups → Manage Reference System Groups.

2. Select the desired reference system group and choose (Change Group Settings). The system displays the Uniform Monitoring Options screen.

3. You can set the monitoring options that you want to assign to the reference system group here. You do this in the same way as described in Creating and Changing Monitoring Rules [page 18].

Note that with reference system groups, only changes in the corresponding system groups influence the availability monitoring. If you assign certain monitoring options to a reference system group, these options do not apply for systems that currently belong to the system group, but only for the systems that are added to the system group as of then. In the same way, systems that are removed from the system group as of then are removed from the availability monitoring.



Checking the Monitoring Settings of a System Group The system is displaying the Configure Availability and Performance Overview screen. Choose System Groups → Manage Reference System Groups. Choose (Check Consistency with Group), and specify which system group you want to check.

The system now displays a list in which you can see how which systems of a system group are monitored. In detail, the list shows:

• Systems of the group for which the availability is currently monitored

• Systems of the group for which the availability is not currently monitored

• Systems of the group for which the availability monitoring status is not known

Availability and Performance Overview Monitor With this monitor, you can perform availability monitoring for selected ABAP and Java systems and their instances. For ABAP systems, you can also monitor the availability of logon groups, and the most important performance attributes for the status of the dialog system are also displayed for the monitored ABAP instances.

For more information about selecting systems and application servers for monitoring, see Configuring Availability Monitoring [page 15].

Description of the Tree Structure of the Monitor

C u r r e n t S t a t u s ( 20.12.2004 , 17:08:45 )

Monitored systems

Availability and Performance Overview

Availability

C11

C1C12

3

Availability monitorAvailability from the point of view of the central monitoringsystem CEN

Availability: C13 on Host1

ABAP: Checked by CCMSPING.Host34.00 100%

Availability of a specific ABAP system

Status, availability, and important performance attributes of a server

-Node Display Off

Release / Description 640 – Test System 640

Instances: C13

Host1_C13_01Host2_C13_01

Instance Availability

Instances of an ABAP system (in this case, C13)

Monitored instances of the system

100 %

Dialog Resonse Time 508 msec

Users Logged On 91 UsersStandardized Response Time 213 msec

Groups: C13 Availability of the logon groups of a system

C13: PUBLICC13: SPACE

AvailabilityFavorite server for test

Monitored logon groups of the system

Host1_C13_01100 % , green 20.12.2004, 17:08:01

RFC Error Message No error reported by RFC

Logon-Check Availability 100 %

System Configuraion


SAP NetWeaver ABAP

Server Type ABAP Application Server



J2E

Availability: J2E on Host6


Availability of a specific Java system

Release / Description J2EE 6.40 System System Configuraion


SAP Web AS J2EE System

Availability and important information for a server

Instances: J2E

J2EE24215910J2EE7305500

Instance Availability

Application servers of a Java system (here: J2E)

Monitored instances of the system

100 %

Host Host6Server Type J2EE Application Server

Available J2EE Server Nodes 1HTTP Port 50000

Prerequisites Availability monitoring uses the standalone agent CCMSPING, you must therefore have performed the installation of the availability agent CCMSPING [page 7].

Features Availability of Systems

For availability monitoring, CCMSPING checks the availability of the message server of the corresponding system. A system is regarded as available if the responsible message server responds to the availability agent’s query and at least one application server is registered as active with the message server. The system availability is monitored by one or more CCMSPING agents, depending on the configuration of your availability monitoring.

MTE Name (MTE Class)

Meaning

ABAP: Checked by <Name> (Availability_SysPercent_ABAP)

Availability of the system according to information from the responsible ABAP message server; checked by specified CCMSPING

Java: Checked by <Name> (Availability_SysPercent_J2EE)

Availability of the system according to information from the responsible Java message server; checked by specified CCMSPING

Release/Description (Availability_Release)

System Configuration (Availability_SysConfig)

Additional information about the monitored system

In the case of ABAP+Java systems, if you have specified both message servers in the configuration of the availability monitoring, both availability values are displayed here.

Availability of ABAP Instances

The monitor displays the following MTEs for the monitored ABAP instances:




Meaning


Meaning

Instance Availability (Availability_InstPercent)

Percentage value of the availability (reported active to the message server), by default averaged over the last 15 minutes

Logon-Check Availability (Availability_RFCPercent)

Percentage value of the availability (server responds to RFC call), by default averaged over the last 15 minutes

Logon-Check: RFC Error Message (Availability_RFCError)

Details for the Logon-Check Availability message

Server Type (Availability_Servertype)

Type of the server; in this case: ABAP Application Server

Dialog Response Time (Availability_DiaRespTime)

Average response time for processing a dialog step

Standardized Response Time (Availability_StdRespTime)

As Dialog Response Time, but for a predefined standard transaction

Users Logged On (Availability_UsersLoggedOn)

Number of users that are logged on to an application server

For more information about the performance values for the dialog system, see Dialog Overview Monitor [external].

Availability of Java Instances

Java instances are displayed under different names, depending on which message server (ABAP or Java) is used for the availability monitoring of the system:

• In the case of monitoring purely using the ABAP message server, Java instances are displayed under the name of the assigned ABAP instance with the suffix :Java (such as: Host1_C11_00:Java). This is only possible if the relevant system is a double-stack system).

• In the case of monitoring using the Java message server, Java instances of the relevant system are displayed under their server ID with the prefix J2EE (such as J2EE7305550). This is also the case, if the monitoring is performed using both message servers.

The monitor displays the following MTEs for the monitored Java instances:


Meaning

Instance Availability (Availability_InstPercent)

Percentage value of the availability (reported active to the message server), by default averaged over the last 15 min.

Server Type (Availability_Servertype)

Type of the server; in this case: J2EE Application Server

Host (Availability_DSJ2EEHost)

HTTP Port (Availability_DSJ2EEPort)

Available J2EE Server Nodes (Availability_DSJ2EELB)

Additional information about the Java instance



Availability of Logon Groups

In the case of ABAP systems, 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 in this group. In addition to the availability of the logon groups in the last 15 minutes, the system also displays the application server of the group with the best dialog system quality in the monitor.

Analysis Method

If you double-click a node in this monitor, you start the analysis method Configure Availability and Performance Overview. (see Configuring Availability Monitoring [page 15]).

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 Availability and Performance Overview monitor from the list by double-clicking it.


ccmsping

Documents

alv tree control

important

performance

methods group

ccms selfmonitoring

performance

valid monitoring

multiple ccmsping