Monitoring Availability of Services and Components Version 1.

5 June 2, 2006

Monitoring Availability of Services and Components

SAP NetWeaver 04

SAP AG Neurottstr. 16 D-69190 Walldorf

SAP AG Page 1 of 7 June 2, 2006

Monitoring Availability of Services and Components Symbols

Symbol Meaning Note

Copyright Copyright 2002 SAP AG. All rights reserved. This document, or parts of it, may not 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.

SAP AG

Page 2 of 7

June 2, 2006

Monitoring Availability of Services and Components Contents Monitoring Availability of Services and Components........................................... 4 Monitoring Services and Components by Way of RFC Destinations .......................................4 Monitoring the Availability of Components with the Network Interface Ping .........................6

SAP AG

Page 3 of 7

June 2, 2006

Monitoring Availability of Services and Components

Monitoring Availability of Services and Components

The CCMSPING agent lets you monitor the availability of SAP Systems. But you can also use the monitoring architecture to monitor the availability of components and services other than SAP Systems. You can: Monitor the availability of components and services that are accessed by way of RFC destinations from an SAP System. You can use a pre-defined CCMS data supplier method to ping any such component or service by way of its RFC destination. As with CCMSPING, the availability check is carried out automatically every five minutes. You can use CCMSPING to monitor external SAP components that use the SAP NI (Network Interface) library, including such components as ITS A-Gates and SAP routers.

Monitoring Services and Components by Way of RFC Destinations

Do the following to monitor the availability of a component or service by pinging its RFC destination: 1. Start transaction RZ21, mark Method definitions, and choose Display overview. 2. Copy the standard CCMS_RFCDest_Availability_Col method definition. You will need a separate method definition for each RFC destination that you wish to monitor. 3. Choose the Parameters tab and fill out the first two parameters as follows: Parameter name 1 Parameter value 1
RFC_DEST

The name of the RFC destination that should be pinged. The RFC destination can be of any type. Any RFC server can respond to the RFC ping that will be sent to it by way of this destination.
COLL_METHOD

Parameter name 2 Parameter value 2

The name that you chose for your new method in step 2.

4. Make sure that the other settings in the method definition are as follows: a) Execution Tab Field Type of call Call Execute method on Execute method for Setting Function module
SALK_RFCDEST_AVAILABILITY

The local server of the MTE to be processed Individual MTE

SAP AG

Page 4 of 7

June 2, 2006

Monitoring Availability of Services and Components b) Control Tab Field Execute method Startup method Execution location of startup method c) Release Tab Field Execute method as Setting Data Collection Method Setting periodically in dialog process (short-running program) Execute method immediately after monitoring segment start Only on the central instance

5. Start the monitoring of the RFC destination by re-starting the central server (the application server that offers the enqueue service) or by re-setting the monitoring segment of the central server to Warmup status.

You can reset the Warmup status by using the Technical Topology of the Monitoring Architecture. In Transaction RZ21, choose Technical Infrastructure Display Topology. Then choose Local Segments, enter change mode, mark the segment of the central server and choose Reset segment to Warmup status. The RFC destination availability MTEs are automatically added to the standard availability monitor in the SAP CCMS Monitor Templates monitor collection. You will find them under the monitoring object RFC-Destinations:

SAP AG

Page 5 of 7

June 2, 2006

Monitoring Availability of Services and Components

If the monitoring tree does not appear as it should, then you should delete the availability context and dependent trees and repeat the segment warmup procedure described above. A single deletion and warmup or restart-cycle should resolve the problem.

Monitoring the Availability of Components with the Network Interface Ping

Some SAP components are not capable of answering an RFC ping, but can respond to a lower-level network interface (NI) ping. The NI ping is implemented in an SAP program library, the Network Interface library. The following components use the NI library and can respond to an NI ping: The ITS A-Gate The SAP router

Other SAP components may also be able to respond to the NI ping. Test the component by setting up a data supplier to send pings to it. To use the NI ping to monitor availability of components, do the following: 1. Make sure that you have installed the Release 6.20 version of the CCMSPING agent. Note that the new 6.40 version of CCMSPING still has a bug and reports a missing host. 2. Determine the DNS (Domain Name Service) host name at which the component is running and the port name or number of the component on the host.

SAP AG

Page 6 of 7

June 2, 2006

Monitoring Availability of Services and Components 3. If there is a SAP router between the CCMSPING host and the component (CCMSPING must communicate with the component through one or more firewalls), then you will need the SAP router string as well. The string has the form /H/hostname/S/service/W/password. 4. To add a NI Ping target, create an entry in table CSMNIPINGCFG as follows: a) Use the Data Browser (transaction SE16) to display existing entries and to create new entries in Table CSMNIPINGCFG. b) You must specify a monitoring object name (MON OBJ NAME) and the host and the service (port). The standard ports are: ITS SAPRouter 3900 3299

5. Start the monitoring of the component by re-starting the central server or resetting the monitoring segment of the central server to Warmup status in the Segment Overview. The relevant method definition is CCMS_NI_PING_COLLECT.

This method definition is available as of SAP NetWeaver 04. The monitor appears in the standard availability monitor in the SAP CCMS Monitor Templates and looks like this:

SAP AG

Page 7 of 7

June 2, 2006