Entering content frameProcedure documentation Installing Availability Agent CCMSPING Locate the document in its SAP Library structure

Use

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

Caution

If you want to monitor systems up to SAP Web Application Server 6.10, take SAP Note 415447 into account. If you are not sure whether you have imported the kernel patches mentioned in the note for all monitored systems, use CCMSPING for SAP Basis 4.6D. You can find this program in the Software Center of the SAP Service Marketplace (see below) at http://service.sap.com/swcenter-main. In the navigation bar there, choose SAP R/3 ® ® SAP R/3 4.6C ® Binary Patches ® SAP Kernel 4.6D or SAP Kernel 4.6D 64 BIT ® <operating system> ® Database independent. If you have installed the required kernel patches, always use the newest release of CCMSPING.

Background documentation

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

Procedure

  1. Log on to the Software Center of the SAP Service Marketplace at http://service.sap.com/swcenter-main with your SAP user name and password.
  2. In the navigation bar, choose SAP WEB AS ® SAP WEB AS 6.10 ® Binary Patches ® SAP Kernel 6.20/SAP Kernel 6.20 64-BIT ® <Operating System> ® Database Independent.
  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.

This graphic is explained in the accompanying text

You must only install the agent once 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.

  1. For installations under Windows NT or Windows 2000, ensure that the directory \\host\saploc\prfclog exists and that saploc is released.
  2. Install CCMSPING with the call ccmsping –R. Enter the following data during the installation:

Parameter

Description

R/3 system ID

System ID of the central monitoring system

client

Valid client in the central monitoring system

user

Valid user in the central monitoring system

password

Associated password; the password is not stored, but rather is used only once for the logon

language

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

hostname of message server

Host name of the message server in the central monitoring system

use Load Balancing

Should load balancing be used [Y/N]?

group

Logon group (only for load balancing)

hostname of message server

Host name of an application server in the central monitoring system (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)

trace level

Should a trace be set (1,2,3) or not (0)? You set the trace both for the system and for the gateway.

  1. In relation to the central monitoring system, CCMSPING functions as an RFC server that is registered at the CEN gateway. If you have successfully logged on the central monitoring system, the system displays the message Successfully registered at SID.
  2. For Windows NT and Windows 2000, you can automatically enter CCMSPING as a service and start it. For UNIX platforms, CCMSPING is not yet automatically started. Start it using the command ccmsping –DCCMS. If the registration is successful, the system displays the message Exiting with code 0.
  3. 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).
  4. 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:
  1. To be able to use availability monitoring, you must start the startup method on the central instance of your central monitoring system. You can do this by Resetting the Monitoring Segment to WARMUP Status on this server.

See also:

Availability and Performance Overview Monitor

Leaving content frame