Availability Monitoring with CCMSPING

SAP NetWeaver 04 SP Stack 11

HELP.BCCCM

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

SAP Online Help

22.04.2005

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 Example text Description 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 EXAMPLE TEXT Emphasized words or phrases in body text, graphic titles, and table titles. 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. 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. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER.

Example text

Example text <Example text>

EXAMPLE TEXT

Availability Monitoring with CCMSPING

690

3

.............. 21 Using Multiple CCMSPING Agents ........................................................... 18 Changing Monitoring Setting of Servers and Groups ................................................................... 25 Availability and Performance Overview Monitor ....2005 Availability Monitoring with CCMSPING ......................................... 11 Finding and Correcting Errors with CCMSPING ........ 22 Creating and Changing a Monitoring Pause .............................................................................................. 10 Adding Systems to the Availability Monitoring Manually..............................................................SAP Online Help 22................................................................................................. 27 Availability Monitoring with CCMSPING 690 4 ...................................................... 24 Monitoring System Groups with CCMSPING............................................................................................................... 7 Changing the Monitoring Frequency and Timeouts of CCMSPING......................................... 5 Installing Availability Agent CCMSPING..................................................................... 12 Configuring Availability Monitoring............................. 15 Creating and Changing Monitoring Rules ................................................04..........

20): Dialog response time Number of users logged on Standardized dialog response time (as of SAP Basis 4. an application server is regarded as active. you can monitor whether remote systems and their instances are available for work from the Alert Monitor of your central monitoring system (CEN). to determine whether a remote system is active and available). 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 also have certain systems monitored by multiple CCMSPING agents. You can monitor ABAP application servers for their availability. This is done using a data collection method of the monitoring architecture. • • 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. which extends the function of CCMSPING. without an inactive system causing an error in the display of the Alert Monitor. Availability monitoring uses the alert and display functions of the monitoring architecture. in addition to a load balancing for availability monitoring. that is. This method is very fast and suitable for centrally monitoring the availability of hundreds of systems.5B) You can check the availability of application servers using an RFC call directly to the server. if it is possible to log on to this server. You can call the Java message server as well as the ABAP message server for availability monitoring. you can make this interval longer as desired. You can register multiple CCMSPING agents with one CEN for the monitoring of your system landscape.04. for data collection (that is. an application server is regarded as available if a free dialog work process responds to this call. CCMSPING has the option –push.10. As of SAP NetWeaver 04 SP Stack 11. The monitoring also displays the following performance attributes for monitored application servers (as of CCMSPING with release status SAP Web AS 6. With this monitoring method. Important performance attributes for the dialog system are also collected on the ABAP instances as of SAP Web Application Server 6. This agent is a stand-alone program that runs outside the SAP system. This means that. and therefore check accessibility.SAP Online Help 22. • Availability Monitoring with CCMSPING 690 5 . if the server is reported as active at the message server.2005 Availability Monitoring with CCMSPING With this function. This means that you can monitor the availability of both ABAP and Java systems. CEN only requests the availability data from CCMSPING every five minutes. 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. you can efficiently monitor the availability of a large number of systems from a central location. However. Without this option. With this monitoring method. By using an agent. availability monitoring uses the CCMS agent CCMSPING (see also Installing Availability Agent CCMSPING [page 7]).

Functional Principle of the Availability Agent CCMSPING Any Host beliebiger Host Also possible to use multiple CCMSPINGs for availability monitoring CCMSPING CCMSPING CEN CEN • System available? • List of active application servers • Basic performance attributes of the active application servers • System available? • List of the active application servers Availability monitoring configuration data Monitored ABAP System ABAP Message Server Logon check: possible to log on to the server? Monitored Java System Java Message Server Anwendungsserver Anwendungsserver ABAP Application Ser vers Anwendungsserver Anwendungsserver Java Instances 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] Availability Monitoring with CCMSPING 690 6 .2005 You can monitor logon groups for their availability. You do not need to register a remote system in the central monitoring system to be able to monitor its availability. In this case. if the availability monitoring is appropriately configured. you can use both the Java and the ABAP message servers for the monitoring. if it is possible to log on to the application server with the best dialog system quality.SAP Online Help 22.04. Availability monitoring is independent of monitoring of other objects in the Alert Monitor. The availability agent also waits for a short time (timeout) in case a system or an application server is temporarily unavailable. In the case of double-stack systems. • You can monitor Java instances for their availability. A logon group is regarded as available. the corresponding message server is queried as to whether the instance is reported as active.

• 3. We recommend that you use the user CSMREG for this purpose (see Creating the CSMREG User [external]). and it is not necessary to install the agent on a host with an SAP system. Under Microsoft Windows.com/swdc with your SAP user name and password. ensure that a share is released on the host with the name saploc. Log on to the Software Center of the SAP Service Marketplace at http://service.10. 1. recommend that you use as high a release status as possible for the CEN. and that the directory \\host\saploc\prfclog exists.sap. however.2005 Installing Availability Agent CCMSPING You must install the availability agent CCMSPING in your monitored IT environment before you can use availability monitoring with CCMSPING. Download this file. which do not themselves perform any additional authorization check. see SAP Note 415447. 6. In distributed environments. 2. 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. CCMSPING is backward-compatible in relation to the SAP Basis release.. you can also use multiple CCMSPING agents for your availability monitoring (see Using Multiple CCMSPING Agents [page 22]). we recommend that you do not install the agent on a host on which an SAP system is running. you require a user with which this transfer can take place. Decompress the archive with the SAPCAR tool.04. Install CCMSPING with the following call: ccmsping [-push] [-n<instance number>] -R The two options have the following meaning: Availability Monitoring with CCMSPING 690 7 . The user requires authorization only for certain function modules.. 5. 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. You can install CCMSPING on any host in your IT environment.SAR.SAP Online Help 22. Take SAP Note 212876 into account.40 32/64-BIT → <operating system> → Database Independent. 4. If you want to monitor a very large number of systems (>100=. Procedure . Prerequisites For the –push option. In this directory. The release of the agent can be higher than the SAP Basis release of the monitored SAP system. you will find the archive CCMAGENT. We do. If you want to monitor systems with a release status below SAP Web Application Server 6.

CEN only requests the availability data from CCMSPING every five minutes.04. CCMSPING uses the instance number 00. You can call the Java message server as well as the ABAP message server for availability monitoring. in addition to a load balancing for availability monitoring.SAP Online Help 22. this is shown in square brackets. group hostname of message server system number route string Logon group (only for load balancing) Host name of an application server in CEN (only without load balancing) Instance number of the above application server (only without load balancing) 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) Availability Monitoring with CCMSPING 690 8 . If you want to use this default value. Language (such as en = English. • • -n<instance number> Use this option if you want to install multiple CCMSPING agents on one host. It activates the following new functions: • CCMSPING actively sends availability data to CEN once a minute. This means that you can monitor the availability of both ABAP and Java systems. You can register multiple CCMSPING agents with one CEN. Enter the following data during the installation (if there is a default value for an entry. since you can then find possible error messages more easily in the CCMS Selfmonitoring monitor (see Finding and Correcting Errors with CCMSPING [page 12]). you can also have certain systems monitored by multiple CCMSPING agents. 7. By default. Then assign different instance numbers (between 00 and 100) for the instances of CCMSPING. Without this option. and therefore check accessibility. you can make this interval longer as desired. de = German) Host name of the message server in CEN Should load balancing be used [Y/N]? We recommend that you register CCMSPING with a fixed application server. This means that. this user is used once to create an RFC connection to CCMSPING.2005 Option -push Meaning The option is available to you for CENs as of SAP NetWeaver 04 SP Stack 11. simply press the ENTER key): Parameter R/3 system ID client user language hostname of message server use Load Balancing Meaning System ID of CEN Valid client in CEN Valid user in CEN.

Availability Monitoring with CCMSPING 690 9 . If you are installing CCMSPING with the –push option.2. the agent is entered and started as a service during the registration. 12. Meaning Client of the CSMREG user Name of the user. you must also ensure yourself that CCMSPING is automatically started after a restart of the server (for example. the system displays the message Successfully registered at <SID>. CCMSPING is not yet automatically started. CCMSPING functions as an RFC server that is registered at the CEN gateway. You have completed the installation of CCMSPING. Start it using the command ccmsping –DCCMS. see above 9. also enter the following data about the CSMREG user: Parameter client user language hostname of message server use Load Balancing group hostname of message server system number route string trace level password Password for the CSMREG user. the password is stored in the secure store in an encrypted file called passwd. usually CSMREG Language (such as en = English. On a UNIX platform. The agent is automatically restarted at every restart.3) or not (0)? Host of the gateway. If you are registering CCMSPING on a Microsoft Windows host. de = German) Connection data for CEN. If you have successfully registered with CEN. 10.SAP Online Help 22. 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]). by entering the start command in INITTAB). For UNIX platforms. usually the message server of CEN Instance number Password of the above user. the password is not stored. Enter the following information for this: Parameter Starttype of service DomainName/UserName Meaning Indicator of whether the service is to be automatically started Account under which the service is to be started 11.2005 Parameter trace level Hostname of gateway System number password Meaning Should a trace be set (1. In relation to CEN.04. it is used only once for the logon 8.

4.5 seconds). and for how long it should wait for a response from the message servers and the application servers when it does so. There is a separate row for each agent that is registered with CEN. (Execute) 3. 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. 1. you need to make the settings in the Data Browser (transaction SE16): . agents that were registered with the – push option (see Installing the CCMSPING Availability Agent [page 7]). and choose (Change).04. choose the button.. such as the frequency of the monitoring. You can do this. The destination has the naming convention CCMSPING. On the Data Browser: Table ALAVLCTRL: Selection Screen. You can also change technical settings of the CCMSPING.SAP Online Help 22.2005 The required database tables must be maintained in the CEN (the system in which CCMSPING is registered). The default value is 1500 (1. using the Upload System List button (see Configuring Availability Monitoring [page 15]). Changing the Frequency of the Availability Monitoring By default. the CCMSPING agent calls the message server once a minute for availability monitoring. for example. 2. In the Table Name field. 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. that is. 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]).. Availability Monitoring with CCMSPING 690 10 . It is not possible to have the monitoring performed more frequently. you can also define the frequency with which CCMSPING should perform the availability monitoring. enter the desired wait time in milliseconds for the relevant CCMSPING as the value of the entry PING_TIMEOUT. 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]). Since there is no separate user interface for maintaining the technical settings. enter the desired interval in seconds for the relevant CCMSPING agent as the value of the entry PING_FREQ. The Data Browser: Initial Screen appears. This table is only relevant for those agents that actively report the availability values to the central monitoring system (CEN).<Host>. enter ALAVLCTRL and choose (Table Contents). The RFC destination of the agent is displayed as its name in the PING_DEST column.<InstNo (Default=00)> To change an entry. To have the monitoring performed less frequently. select the desired agent. Start transaction SE16 in CEN.

The system displays the Monitoring: Methods screen. The data is in the services file. ). depending on the system type. Start transaction RZ21 in CEN. c. The default value is 10000 (10 seconds). e. Select the method CCMS_AVAIL_LOGON_CHECK. enter the desired wait time in milliseconds for the RFCPING_TIMEOUT parameter. Changing the Timeout of the Availability Agent CCMSPING (Without the –push Option) If you have registered CCMSPING without the –push option.2005 Two additional entries: TRACE and TIMESTAMP are useful for finding and correcting errors. To change the time that CCMSPING waits for the response of an application server in the case of an RFC call. the availability monitoring is essentially performed every five minutes. the CCMSPING calls the application server directly. To do this. f. CCMSPING communicates with the ABAP and the Java message servers of the corresponding systems. and choose the Parameters tab page. since this data should be available for SAPLogon on every SAP front end in your system landscape. To do this. enter the desired wait time in milliseconds for the TIMEOUT parameter.>/tcp. 6. proceed as follows: a. To change the timeout for these calls. 4. see Finding and Correcting Errors with CCMSPING [page 12] 5. You can. Start transaction RZ21 in CEN. Select the method CCMS_System_Availability and choose Edit Data ( ).SAP Online Help 22. In the Methods group box. and choose Edit Data ( d.04. Save your entries. change the above timeouts. 1. enter the desired wait time in milliseconds for the RFCPING_TIMEOUT parameter. To change the time that CCMSPING waits for the response of the message server. 3. The system displays the Monitoring: Methods screen. follow the procedure below: ..5 seconds). Choose change mode with the Display ↔ Change ( ) pushbutton. select Method Definitions and choose Display Overview. which contains the port numbers of the ABAP message servers in the format sapms<SysID> <Port_No. Availability Monitoring with CCMSPING 690 11 . To change the time that CCMSPING waits for the response of an application server in the case of an RFC call. Choose change mode with the Display ↔ Change ( ) pushbutton. For more information. Adding Systems to the Availability Monitoring Manually To collect the availability of the systems to be monitored. You can also register only one CCMSPING with your CEN. 5. b. however. CCMSPING requires the connection data for this server. During the logon check. Save your entries. and choose the Parameters tab page. You do not normally need to determine the connection data for the ABAP message server yourself. In the Methods group box. 2.. The default value is 1500 (1. 7. select Method Definitions and choose Display Overview. The default value is 10000 (10 seconds).

The Connection Data and Monitoring Options screen appears 4. The port number that you are looking for usually has the format 36<system number>. proceed as follows: .. and choose the menu path Technical Infrastructure → Availability Monitoring → Configure CCMSPING Monitoring. a. The entry has the following format: sapms<SysID> <Port No. Procedure To manually add a new system to availability monitoring. 7. Finding and Correcting Errors with CCMSPING If problems occur during the availability monitoring with CCMSPING. c.. start the Visual Administrator for the desired Java system. proceed as follows: . 3. You can now activate the monitoring for this system using the normal user interface. proceed as follows: . b. To monitor the system using the ABAP message server.SAP Online Help 22. Result The desired system is included in the list of systems that can be monitored from the monitoring architecture. work through the points below. which are actively reporting to the central monitoring system (registration with the –push option).. Availability Monitoring with CCMSPING 690 12 .. If you want to set the monitoring options. c. If the service is not yet running. The IP Service follows the naming convention sapms<SysID>. follow the procedure described in Creating and Changing Monitoring Rules [page 18]. Fill out the input fields Message Server Host Name and IP Service Name. Choose Runtime → Parameters. Prerequisites The following points apply for CCMSPING agents. Enter the corresponding line in the services file.>/tcp. b. 6. start it. and save the file. the port as the value of the parameter ms/http_port. expand the SAP CCMS Monitor Templates monitor set in transaction RZ20 and open the Availability and Performance Overview Monitor [page 27]. under [Drive]:\WINDOWS\system32\drivers\etc.2005 This procedure describes how you can manually obtain the connection data for ABAP or Java message servers of a system to be monitored. 2.04. Choose the button Action→ Create System. under /etc). and choose the Continue button. Specify the system ID of the system to be monitored. in UNIX systems. you can see the host as the value of the parameter server host. and choose the following path in the navigation bar: Cluster → Server → Services → Message Info. Fill out the input fields Message Server Host Name and Message Server HTTP Port. If you do not have this data. To monitor the system using the Java message server. To display the availability data. Start transaction RZ21 in the central monitoring system. Save your changes. 1.. a. CCMPSING requires an entry for the corresponding system in the services file on its host (in Microsoft Windows XP systems.. For availability monitoring. 5.

What do I need to do. or 3.04. if the logon check fails. You can find this in the CCMS Selfmonitoring Monitor.00: Could not access standard SLD (TX sldapicust) Select this MTE. 16:42:45 ) Node Display Off CCMS Selfmonitoring CEN Name of the monitor Central monitoring system Subtree with instance-specific data Object with data supplier messages CCMSPING. MoniInfra_Hiost1_CEN_00 Data Supplier Log If TRACE=5. and choose the (Details) button to display all messages.2004 . I want to activate debug tracing. it is possible that CCMSPING cannot perform the entire check in one minute. If TRACE=1.2005 Activities What do I need to do. Have the availability monitoring performed by multiple CCMSPING agents (see Using Multiple CCMSPING Agents [page 22]). C u r r e n t S t a t u s ( 20. you have two options: Have the availability monitoring performed less frequently (see Changing the Monitoring Frequency and Timeouts of CCMSPING [page 10]).2. In this case. and set the TRACE entry for the desired CCMSPING. Select the MTE and choose messages of the trace. Availability Monitoring with CCMSPING 690 13 . Actions of the ABAP infrastructure for availability monitoring are written in this trace.12. so that you can start debugging the ABAP processing using transaction SM50. The agent writes the trace to a file in its working directory (\\host\saploc\prfclog\CCMSPING_<InstNo>). Check the host name resolution. 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]).SAP Online Help 22. instead of setting the value for the Trace Level to 0. 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]). Call up this table in transaction SE16.Host1. in the instance-specific subtree of the server with which CCMSPING is (Details) to display all of the registered. The actions of the CCMSPING agent itself are written in this trace. if CCMSPING does not provide availability values with the required frequency? In the case of very large IT landscapes to be monitored. the trace information is written to the Log log attribute of the Data Supplier monitoring object. 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]). you can set it to 1. the function module for collecting the availability values of the relevant CCMSPING starts an endless loop.

.2004 16:36:20: Agent calls as [BCE:000:CSMREG].04. You can therefore use the timestamps to check whether the agent is working with its current worklist.2004 .00 Description Status Heartbeat Availability Agent Version Details List of CENs Individual agent Information about the agent CCMSPING. CCMSPING.\CCMS_Agents\.SAP Online Help 22. Every CCMSPING monitors this timestamp every minute. 32 19.2004 .Host1. that is. that is the last time at which you changed the monitoring settings.12.12. the TIMESTAMP entry contains the status of its worklist.11. Last test: 20. How do I determine whether the responsible CCMSPING has received these changes? The table ALAVLCTRL (see above) has a TIMESTAMP entry.2004.Host1.12. 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.2005 I have changed the configuration of the availability monitoring. the systems and instances that this CCMSPING is to monitor.12. RFC_PING ok no additional Central System Availability Monitoring with CCMSPING 690 14 . 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. For each registered CCMSPING agent. 10:04:58. 00 controlling CEN Host1_local on Host1 active since 18. The TIMESTAMP entry of the agent is then the same as the corresponding entry in the row CCMS_SYSTEM_PING_DEST.2004. 16:42:45 ) CCMS Selfmonitoring CEN Name of the monitor Central monitoring system CCMS_Selfmonitoring Subtree with system-wide data Availability Monitoring CCMSPING Technology Enabling CCMSPING active reporting in operation How do I determine which CCMSPING agents are registered with CEN with the –push option.. 16:06:09 51 sec 100 % patch collection 2004/6. the following monitoring object is displayed in the CCMS Selfmonitoring Monitor for System-Wide Data there: C u r r e nt -Node Display Off S t a t u s ( 20. If the status of the agent is currently older than the status of the last configuration change. 16:42:45 ) Selfmonitoring CCMS Agents Name of the monitor CEN\CCMS_Selfmonitoring\. The following data is displayed there: C u r r e nt Node Display Off S t a t u s ( 20. The row CCMS_SYSTEM_PING_DEST contains the timestamp of your last change to the monitoring configuration in this entry. OSS note 694057. the agent downloads its current worklist from CEN and updates its timestamp.. CCMS version 20040229..

04. you can both create and change monitoring rules [page 18]. The Configure Availability and Performance Overview screen appears. 3. 2. and change the monitoring settings of servers and groups [page 21] individually. • • • Prerequisites You have performed the Installation of the Availability Agent CCMSPING [page 7]. useful for the monitoring of distributed system landscapes (see Using Multiple CCMSPING Agents [page 22]). This is. 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.SAP Online Help 22. 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]). for example. Choose Technical Infrastructure → Availability Monitoring → Configure CCMSPING Monitoring. The Monitoring: Properties and Methods screen appears. When doing so. where you can display for the monitoring of the monitoring systems by expanding the subtree for the corresponding system: Availability Monitoring with CCMSPING 690 15 .2005 Configuring Availability Monitoring You can customize the availability monitoring with CCMSPING for ABAP and Java systems in a number of ways. 1. in accordance with which the servers and groups of the system are monitored. you can decide which CCMSPING is responsible for the monitoring of a system. • You can activate and deactivate availability monitoring for systems groups. Process Flow .. or call transaction RZ21. If you have installed multiple CCMSPING agents. 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. Logon groups exist only for ABAP application servers. The screen shows monitored and unmonitored systems in two lists.. Choose CCMS → Configuration → Alert Monitor.

Request a new list of ABAP systems that can be monitored List of the monitored systems. choose the then one of the following buttons: Views System Info View Group/Instance View Administration View Connection View Meaning The valid monitoring rules and the responsible CCMSPING are displayed for the monitored systems The settings for the monitoring options for application servers and logon groups for the monitored systems are displayed Time and users of the last monitoring change are displayed Message server port.SAP Online Help 22. To activate a view.04. This means that you can display this screen by doubleclicking a node in this monitor. The following functions are then available to you: Availability Monitoring with CCMSPING 690 16 . application servers. message server host. with which you can display information about the monitored systems and their Views button. and router string are displayed Availability Monitoring with CCMSPING [page 1] Additional Information Using Multiple CCMSPING Agents [page 22] Creating and Changing Monitoring Rules [page 18] Activities Changing the Monitoring of Systems To change the monitoring of systems. you can also change the monitoring functions for the monitored and unmonitored systems here (see buttons below). and logon groups. system groups. You can change the monitoring details for application servers and logon groups for each system. and application servers and logon groups. Monitoring setting for application servers: Is logon possible? Is application server reported as active at the respective message server? List of the systems that are not monitored Monitoring setting for logon groups: Is logon possible? 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].2005 Initial Screen for the Configuration of Availability and Performance Overview Drop-down menus with views and actions. select the desired systems on the Configure Availability and Performance Overview screen by selecting the folder icon of the relevant systems. you an use these to display various information about the monitored systems. Displaying the Monitoring and System Data There are various views available on the Configure Availability and Performance Overview screen.

choose → Change Connection/Options. In large IT environments. Proceed as described in Adding Systems to Availability Monitoring Manually [page 11]. In the Monitored Systems subscreen. In the Monitored Systems Monitoring subscreen. 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. where one system can belong to multiple system groups. In the Monitored Systems subscreen.04. production). Breaks → Create Choose Monitoring Pause or Create Uniform Monitoring Pause. organize systems into system groups by their function (development. add the system to it manually (see Add Systems to the Availability Monitoring Manually [page 11]). choose Load System List ( ). choose Monitoring → Use Uniform System Options. 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. choose Monitoring → Deactivate System Monitoring. Availability Monitoring with CCMSPING 690 17 . Add New Systems to the List of ABAP Systems that Can Be Monitored On the Configure Availability and Performance Overview screen. for example. If the desired ABAP system does not appear on the list. or their geographic location. if you can. In this way. monitor all systems in a system group with one command. In the Unmonitored Systems subscreen. see Monitoring System Groups with CCMSPING [page 25]. Monitoring System Groups You can combine systems into system groups (see System Groups in the Alert Monitor [external]). For more information about monitoring system groups. Choose the button Delete System(s). their release status. for example. quality assurance. you must first enter the connection data. it can greatly simplify the configuration of availability monitoring.SAP Online Help 22. Monitoring → Additional Information Creating and Changing Monitoring Rules [page 18] If you want to monitor systems using the Java message server. choose Monitoring → Define Uniform Monitoring.2005 Function Activating the Monitoring of Systems Activating the Uniform Monitoring of Systems Changing the Monitoring Rules for Systems Changing the Uniform Monitoring of Systems Creating and Changing the Monitoring Pause for Systems Deactivating the Monitoring of Systems Delete Systems from the System List Command In the Unmonitored Systems Monitoring subscreen. you can. Creating and Changing a Monitoring Pause [page 24] You can also activate and deactivate system monitoring by moving selected systems to the desired list by Drag&Drop. choose → Activate System Monitoring.

Creating and Changing Monitoring Rules You can create monitoring rules in the configuration of the availability monitoring with CCMSPING. Changing Technical Settings of the Availability Agent CCMSPING You can also change technical settings of the registered CCMSPING availability agents.2005 The SAPMSG. such as the frequency of the monitoring. is uploaded from the front end for the system list. the availability agent queries the message server of the corresponding system as to whether the application server is reported as active. 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]). It does not perform a check at the monitored server itself to see whether. Although no actual logon is performed.SAP Online Help 22.since the RFC call requires a free dialog work process. you can. which is also used for functions of SAPLOGON. 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]). for example. determine whether it is possible to log on .INI file. Use the Availability and Performance Overview Monitor [page 27] from the SAP CCMS Monitor Templates monitor set to perform availability monitoring. This function uses the same technique to do this as Check Logon. Availability Monitoring with CCMSPING 690 18 . the monitoring architecture performs an RFC call in the relevant server. however. You have the following options: • Monitoring the application servers: Ping Monitoring With this type of monitoring. in the same way as a user logging on does. since CCMSPING can communicate with both the ABAP and Java message servers. You define the type of monitoring for the relevant system in these rules. it is possible to log on. This monitoring is possible for both Java and ABAP application servers. The prerequisite for this is the existence of logon groups in the corresponding system. Result You have customized the availability monitoring to your requirements.04. • 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. It does not contain any standalone Java systems. This monitoring is only possible for ABAP application servers. This method also checks whether the database of the monitored system is functioning and is connected to the system. Check Logon With this monitoring type. 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]).

depending on whether the desired systems are already monitored: To create an availability rule for a system that has not been monitored until now. This activates the monitoring for this system.0 Target System Description APO Hotpackagetest 3.0A B2B 3. Note that a system is only correctly selected when the entire line is highlighted: Monitored Systems AIJ C11 Monitored Systems AIJ C11 System Description APO Hotpackagetest 3.SAP Online Help 22. select these systems. and choose Define Uniform Monitoring. To create or change a monitoring rule for one or more systems. confirm the relevant query. Select the desired systems by choosing the folder symbol for the corresponding systems. It is therefore a prerequisite that you have already performed the part of the process that is to be performed before this procedure. The screen has the following structure: Availability Monitoring with CCMSPING 690 19 . Proceed as follows. Monitoring → Activate System Monitoring in the Unmonitored choose Systems subscreen. Procedure The system is displaying the Configure Availability and Performance Overview screen. The Connection Data and Monitoring Options screen appears. 1. To assign an identical monitoring rule to multiple systems that were not Monitoring → previously monitored.. select Monitoring → Use Uniform System Options. To assign an identical monitoring rule to multiple monitored systems.04. and choose 3.0A B2B 3.0 Target Monitor System Monitor System 2. To change the availability rule for a monitored system. these systems. choose Monitoring → Change Connection/Options in the Monitored Systems subscreen.2005 Prerequisites This procedure is part of the Configuring Availability Monitoring [page 15] process. follow the procedure below: ..

newly added servers are automatically monitored Monitor All Application Servers. whether newly added groups should automatically be included in the monitoring. only the system is monitored for its availability. If you have installed multiple CCMSPING agents. if you used a system from the list of existing systems. Availability Monitoring with CCMSPING 690 20 . only the servers that you manually select in the Group/Instance View are monitored. with this option. the servers that currently exist are not monitored (which you can change manually in the Group/Instance View). you can choose the following radio buttons: • No monitoring of application servers. Automatically Add New Application Servers to Monitoring. Monitoring options for application servers. by default Monitoring options for logon groups.2005 Screen for Creating and Changing a Monitoring Rule Connection Data and Monitoring Options System Description System to which this rule applies Specify the connection data for the system. with this option. in the same way as with the monitoring of application servers. You can set whether logon groups are to be monitored. with this option.04. Save your entries. Including New Groups Destinati on of Responsible CCMSPIN G Copy Connection Data and Options Check Logon Check Logon This information is not displayed if you have chosen uniform monitoring. by default Destination of the CCMSPING that is responsible for the monitoring of this system Cancel Save the settings made Make the following entries in this screen: Group box System and Connection Data Monitoring Options for Application Servers Meaning Information about the corresponding system. you can determine here which CCMSPING is responsible for the monitoring of this system (see Using Multiple CCMSPING Agents [page 22]). see Add Systems to the Availability Monitoring Manually [page 11]) Settings for monitoring application servers (see above). • • • Monitoring Options for Logon Groups Destination of Responsible CCMSPING 4. if a server was previously monitored. this setting is deleted Monitor only selected application servers. including new servers added later are monitored. you only need to enter data for the Java message server Message Ser ver Host Name Name of the IP Service Router String Connection Data: Java Message Ser ve r Message Ser ver Host Name Message Ser ver HT TP Port Router String Monitoring Options for Application Serve r No Monitoring of Application Servers Moni tor Onl y S elected Application Servers Automatically Add New Application Servers to the Monitoring Ping Monitoring Moni tor All Application Servers P ing Monitoring Monitoring Options for Logon Groups No Check of L ogon Groups Check Only Selected Logon Groups Automatically Add New Logon Groups to the Monito ring Activate Check for All Groups. specifies how the logon groups of the system are monitored. specifies how the application servers of the system are monitored. you can specify. all servers. if the rule is active.SAP Online Help 22. For more information.

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]).. To edit the monitoring settings (defined by the valid monitoring rules) for one or more systems......2005 Result You have created or changed a monitoring rule for the selected systems. and choose the servers/groups for which you want to activate/deactivate monitoring in the context menu Availability Monitoring with CCMSPING 690 21 . To further refine monitoring. It is therefore a prerequisite that you have already performed the part of the process that is to be performed before this procedure... . and select the desired settings Changing Monitoring Settings for Multiple Servers/Groups Monitored Systems AIJ Application Servers as0030_AIJ_47 as0031_AIJ_31 Logon Groups PUBLIC SPACE Logon Check J2EE Server Ping Server Ping Logon Group Check Find Hide Column Optimal Width Help Select visible items Deselect vis ible items Select all items Deselect all items Right-click the column title of the desired monitoring type .SAP Online Help 22. The system is displaying the Configure Availability and Performance Overview screen. 1. You can modify the monitoring of individual servers and groups directly in the user interface of the ALV Tree Control.04.. follow the instructions in Changing Monitoring Settings for Servers and Groups [page 21]. on the basis of which the corresponding systems will be monitored. follow the procedure below: Change Monitoring Settings for Individual Servers/Groups Monitored Systems AIJ Application Servers as0030_AIJ_47 as0031_AIJ_31 Logon Groups PUBLIC SPACE Logon Check J2EE Server Ping Server Ping Logon Group Check Expand the desired subtrees . Prerequisites This procedure is part of the Configuring Availability Monitoring [page 15] process. Procedure . 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. This procedure is described here. to change the monitoring of individual application servers or logon groups. . for example..

To change the monitoring settings for multiple application servers or logon groups. Normally. To do this. To change monitoring settings for individual application servers or logon groups. 4. you only require one CCMSPING agent to monitor your entire system landscape. it is possible that the response times of the RFC calls. to check the accessibility of the system from various points. and J13. J12. see Changing Technical Settings of CCMSPING [page 10]). expand the subtrees of the corresponding system and select the desired checkboxes. In this case. In this way. and choose Select Visible Items in the context menu. become too large. In distributed landscapes. You want to set up the Server ping for all application servers of systems J11. 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. Now right-click Server Ping column title. you can also use multiple CCMSPING agents. • Availability Monitoring with CCMSPING 690 22 . assign CCMSPING agents for which the connection to the systems to be monitored is sufficiently quick in each case. it can be useful that one system is monitored by multiple CCMSPING agents. You can do this by combining these CCMSPING agents into an agent group.SAP Online Help 22. In this scenario. This can have the following advantages. • You can configure various CCMSPING agents different (such as setting the frequency of the availability monitoring differently. 3. Result You have changed the monitoring settings for the selected systems. select these systems and choose the Expand Subtree ( ) button. However. to fulfill different requirements for availability monitoring of different systems. you can monitor the connections to the systems in addition to the actual monitoring of the systems. Using Multiple CCMSPING Agents You can use the CCMSPING agent to monitor the availability of your SAP system landscape.04. Save your changes. and assigning this agent group the system as the responsible CCMSPING. with which the logon checks for an instance are performed.2005 2. for example: • You can extend the availability monitoring to include accessibility monitoring.

select the desired assignment (Delete Group Entry). 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). choose the button. The system is displaying the Configure Availability and Performance Overview screen. 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. Choose (Add Group Entry) 2.. if you install all CCMSPING agents with the –push option (see Installing Availability Agent CCMSPING [page 7]). You can only use multiple CCMSPING agents.SAP Online Help 22. proceed as follows: . and (Continue).. CCMSPING → Manage CCMSPING Groups. It is therefore a prerequisite that you have already performed the part of the process that is to be performed before this procedure. and choose 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. To combine multiple CCMSPING agents into an agent group. Then enter the destination of the desired agent in the CCMSPING Agent field. choose 3.04. Without this option. To assign a CCMSPING agent to an agent group. Availability Monitoring with CCMSPING 690 23 . the system displays a corresponding warning. To delete the assignment of an agent to an agent group.2005 Multiple CCMSPING Agents in Distributed Landscapes CEN CCMSPING A01 A02 A03 CCMSPING B01 B02 B03 CCMSPING C01 C02 C03 Prerequisites This procedure is part of the Configuring Availability Monitoring [page 15] process. 1. 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.

You can also repeat these monitoring pauses daily or weekly. you can deactivate the monitoring during certain specified times. 3.. Choose the desired CCMSPING for the selected systems.SAP Online Help 22.<instance number> By default. follow the procedure below: . The system is displaying the Configure Availability and Performance Overview screen.. Select the desired systems by choosing the folder symbol for the corresponding systems. and also all agent groups that you have created.<Host>. choose the Pauses button and then Create Uniform Monitoring Pause. If you have only selected one system.. <instance number> is 00.. The list of CCMSPING agents displayed in the input help contains the RFC destinations of all CCMSPING agents that are registered with this system. Availability Monitoring with CCMSPING 690 24 . It is therefore a prerequisite that you have already performed the part of the process that is to be performed before this procedure. or want to create different monitoring pauses for the selected systems. Confirm your selection and save your changes.. . 4..2005 Displaying the Responsible CCMSPING The system is displaying the Configure Availability and Performance Overview screen. Prerequisites This procedure is part of the Configuring Availability Monitoring [page 15] process. The RFC destination of the responsible Choose the button CCMSPING or the responsible agent group in each case is shown in the corresponding row. The destination has the following naming convention: CCMSPING. If you want to create or change a monitoring pause for monitored systems. Procedure The system is displaying the Configure Availability and Performance Overview screen. 1. proceed as follows: . such as during the weekend or for maintenance work. proceed as follows: Views → System Info View. Creating and Changing a Monitoring Pause In the configuration of availability monitoring with CCMSPING. Changing the Responsible CCMSPING To change the CCMSPING agent responsible for monitored systems. To display the CCMSPING agent or agent group responsible for your monitored systems. 2. If you want to create an identical monitoring pause for the selected systems. choose the Pauses button and then Create Monitoring Pause. Select the desired systems by choosing the folder symbol for the corresponding systems. 2. You can also change the responsible CCMSPING on the Connection Data and Monitoring Options screen (see Creating and Changing Monitoring Rules [page 18]).04. 1. Choose CCMSPING → Change Responsible CCMSPING.

where one system can belong to multiple system groups. delete the rule from the list. the system displays a success message and your rule appears in the list at the bottom of the screen. The Maintain Time not Monitored screen appears. To change a monitoring rule. You can also configure the availability monitoring to use system groups. quality assurance. for example. you can. You can define monitoring rules for single monitoring pauses. no corresponding alerts are generated during these time periods. specify the start and end times of the pause Existing monitoring pauses. each time for the selected period of time and on the selected weekday. Single monitoring pause. Save the monitoring rule that you have created. Once you have successfully saved your rule. and pauses that are repeated daily or weekly. To leave the screen. and recreate the rule. their release status. Availability Monitoring with CCMSPING 690 25 . and do not want to create a uniform monitoring pause. the monitoring pauses that are repeated weekly are valid from the time specified. it can greatly simplify the configuration. The monitoring pauses that are repeated daily take effect immediately. a system is no longer monitored. The screen has the following structure: Screen for Creating and Changing Monitoring Pauses Maintai n Time not Monit or ed Name of the System Period w ith no Avai lab ility Mon itorin g Daily from To Weekly from To Start Time End Time Start Date Start Time End Date End Time Once from To Start Date Start Time End Date End Time System for which the monitoring pauses apply (the field is not displayed if you create a uniform monitoring pause) Daily monitoring pause. In the same way. specify the start and end times of the pause Weekly monitoring pause. You can also declare the system groups as reference system groups. if it is no longer a member of this reference system group. Monitoring System Groups with CCMSPING You can combine systems into system groups (see System Groups in the Alert Monitor [external]). choose Cancel ( ) Result The selected systems are not monitored for their availability during the specified times. monitor all systems in a system group with one command. that is. or their geographic location. The pause is scheduled every week from then at the times and on the week days of the first pause. if you can. In this way. In large IT environments. specify the start and end time points of the pause. for example.2005 3. 6. this system automatically receives the monitoring settings that have been assigned to the reference system group. organize systems into system groups by their function (development.SAP Online Help 22. production).04. If you have selected multiple systems. you can identify pauses that are repeated weekly (W) and daily (T) in the last column Start Date Start Time End Date End Time Period ic Save Save the monitoring pause created above Cancel 4. 5. repeat these steps for all selected systems. If another system is later added to a reference system group of this type. A monitoring setting that is used on all systems in this group is assigned to a reference system group.

Activities Selecting All Monitored Systems of a System Group The system is displaying the Configure Availability and Performance Overview screen. If you assign certain monitoring options to a reference system group. systems that are removed from the system group as of then are removed from the availability monitoring. You can now make the desired availability monitoring settings for the selected systems. Select the desired reference system group and choose The system displays the Uniform Monitoring Options screen. Note that with reference system groups.. You do this in the same way as described in Creating and Changing Monitoring Rules [page 18]. To create or edit system groups themselves. The system is displaying the Configure Availability and Performance Overview screen. To start the system (Start System Group Maintenance). 3. You can set the monitoring options that you want to assign to the reference system group here. as described in Creating and Changing Monitoring Rules [page 18]. 2. It is therefore a prerequisite that you have already performed the part of the process that is to be performed before this procedure..2005 Prerequisites This procedure is part of the Configuring Availability Monitoring [page 15] process. You can use the listed functions to save existing system groups as reference system groups or to remove this assignment. System Groups → Manage Reference System Groups.. To System Groups → Select select all monitored systems of a system group.. and not the system group itself. Adding and Deleting Reference System Groups The system is displaying the Configure Availability and Performance Overview screen. The Uniform Monitoring Options screen appears (see below). and choose the desired Choose system group. Availability Monitoring with CCMSPING 690 26 . A screen appears on Choose which the existing reference system groups are displayed. . and confirm your entry. use the system group maintenance. choose Systems of a Group. 1. System Groups → Manage Reference System Groups. This deletes only the reference.SAP Online Help 22. but only for the systems that are added to the system group as of then. Choose (Change Group Settings). these options do not apply for systems that currently belong to the system group.04. Choose the desired system group. (Delete Reference Select the desired system group and choose System Group). among others: Use Add a new reference system group Delete a reference system group Command (Add Reference System Group). choose Editing the Settings of a Reference System Group . In the same way. however. group maintenance. only changes in the corresponding system groups influence the availability monitoring. The following functions are available.

System Groups → Manage Reference System Groups. you can perform availability monitoring for selected ABAP and Java systems and their instances.00 ABAP: Checked by CCMSPING. Choose (Check Choose Consistency with Group). The system now displays a list in which you can see how which systems of a system group are monitored.00 Groups: C13 C13: PUBLIC C13: SPACE Availability Favorite server for test Instances: C13 Host1_C13_01 Host2_C13_01 Availability of the logon groups of a system Monitored logon groups of the system 100 % . In detail. green 20. see Configuring Availability Monitoring [page 15].12.2004 . you can also monitor the availability of logon groups. 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. and important performance attributes of a server Availability Monitoring with CCMSPING 690 27 .Host34.04.SAP Online Help 22. availability. For ABAP systems.2004. For more information about selecting systems and application servers for monitoring. C13) Monitored instances of the system 100 % 100 % ABAP Application Server No error reported by RFC 508 m sec 213 m sec 91 Users Instance Availability Logon-Check Availability Server Type RFC Error Message Dialog Resonse Time Standardized Response Time Users Logged On Status.12.2005 Checking the Monitoring Settings of a System Group The system is displaying the Configure Availability and Performance Overview screen. and specify which system group you want to check. 17:08:45 ) -Node Display Off Availability and Perform ance Overview Availability C11 C12 C13 Availability monitor Availability from the point of view of the central monitoring system CEN Monitored systems Availability: C13 on Host1 Availability of a specific ABAP system 640 – Test System 640 SAP NetWeaver ABAP 100% 100% Release / Description System Configuraion ABAP: Checked by CCMSPING. Description of the Tree Structure of the Monitor C u r r e n t S t a t u s ( 20.Host35. 17:08:01 Host1_C13_01 Instances of an ABAP system (in this case. and the most important performance attributes for the status of the dialog system are also displayed for the monitored ABAP instances.

The system availability is monitored by one or more CCMSPING agents. checked by specified CCMSPING Availability of the system according to information from the responsible Java message server.40 System SAP Web AS J2EE System 100% 0% Release / Description System Configuraion ABAP: Checked by CCMSPING. both availability values are displayed here. you must therefore have performed the installation of the availability agent CCMSPING [page 7].00 ABAP: Checked by CCMSPING. Availability of ABAP Instances The monitor displays the following MTEs for the monitored ABAP instances: Availability Monitoring with CCMSPING 690 28 . if you have specified both message servers in the configuration of the availability monitoring.2005 J2E Availability: J2E on Host6 Availability of a specific Java system J2EE 6. checked by specified CCMSPING Additional information about the monitored system In the case of ABAP+Java systems.04. CCMSPING checks the availability of the message server of the corresponding system.Host34.00 Instances: J2E J2EE24215910 J2EE7305500 Application servers of a Java system (here: J2E) Monitored instances of the system 100 % J2EE Application Server Host6 50000 1 Instance Availability Server Type Host HTT P Port Available J2EE Server Nodes Availability and important information for a server Prerequisites Availability monitoring uses the standalone agent CCMSPING. MTE Name (MTE Class) ABAP: Checked by <Name> (Availability_SysPercent_ABAP) Java: Checked by <Name> (Availability_SysPercent_J2EE) Release/Description (Availability_Release) System Configuration (Availability_SysConfig) Meaning Availability of the system according to information from the responsible ABAP message server. Features Availability of Systems For availability monitoring. 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. depending on the configuration of your availability monitoring.Host35.SAP Online Help 22.

see Dialog Overview Monitor [external].SAP Online Help 22. 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. Type of the server. Meaning Percentage value of the availability (reported active to the message server). by default averaged over the last 15 minutes Details for the Logon-Check Availability message Type of the server. by default averaged over the last 15 min. by default averaged over the last 15 minutes Percentage value of the availability (server responds to RFC call). if the monitoring is performed using both message servers. This is also the case. In the case of monitoring using the Java message server. Availability of Java Instances Java instances are displayed under different names. but for a predefined standard transaction Number of users that are logged on to an application server For more information about the performance values for the dialog system.2005 MTE Name (MTE Class) MTE Name (MTE Class) Instance Availability (Availability_InstPercent) Logon-Check Availability (Availability_RFCPercent) Logon-Check: RFC Error Message (Availability_RFCError) Server Type (Availability_Servertype) Dialog Response Time (Availability_DiaRespTime) Standardized Response Time (Availability_StdRespTime) Users Logged On (Availability_UsersLoggedOn) Meaning Meaning Percentage value of the availability (reported active to the 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 doublestack system). in this case: J2EE Application Server Additional information about the Java instance • The monitor displays the following MTEs for the monitored Java instances: MTE Name (MTE Class) Instance Availability (Availability_InstPercent) Server Type (Availability_Servertype) Host (Availability_DSJ2EEHost) HTTP Port (Availability_DSJ2EEPort) Available J2EE Server Nodes (Availability_DSJ2EELB) Availability Monitoring with CCMSPING 690 29 .04. in this case: ABAP Application Server Average response time for processing a dialog step As Dialog Response Time. Java instances of the relevant system are displayed under their server ID with the prefix J2EE (such as J2EE7305550).

. On the CCMS Monitor Sets screen. A logon group is regarded as available.. Activities To start the monitor. (see Configuring Availability Monitoring [page 15]). Start the Alert Monitor using transaction RZ20 or choose CCMS → Control/Monitoring → Alert Monitor. 3. you start the analysis method Configure Availability and Performance Overview. In addition to the availability of the logon groups in the last 15 minutes. Analysis Method If you double-click a node in this monitor. 2. follow the procedure below: . Start the Availability and Performance Overview monitor from the list by double-clicking it.2005 In the case of ABAP systems. 1. Availability Monitoring with CCMSPING 690 30 . if it is possible to log on to the application server with the best dialog system quality in this group. the system also displays the application server of the group with the best dialog system quality in the monitor. you can monitor logon groups for their availability.SAP Online Help Availability of Logon Groups 22. expand the SAP CCMS Monitor Templates set.04.

Sign up to vote on this title
UsefulNot useful