Installing Availability Agent
CCMSPING
Use
You must install the availability agent CCMSPING in your monitored IT environment before you can use availability monitoring with CCMSPING.
NOTE
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 (more information: Creating the CSMREG User).
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 7.0 → Entry by Component ® Application Server ABAP ® SAP KERNEL 7.00 32/64-BIT ® <operating system> → Database Independent.
CCMSPING only exists in a non-Unicode version; you can use this version irrespective of the Unicode status of CEN and the monitored systems.
NOTE
CCMSPING is backward-compatible in relation to the SAP 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 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.
NOTE
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 SAPsystem. 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).
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 –R [-push] [-n<instance number>] [pf=<profile path>]
The options have the following meaning:
Option |
Meaning |
-push |
We recommend that you use this option; it is available to you for CENs as of SAP NetWeaver 04 SP Stack 11. The options activates the following 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.
When you register a CCMSPING agent with the –push option for the first time, define this agent as the responsible agent in the Configuration of Availability Monitoring. To do this, select all monitored systems and choose the button CCMSPING → Change Responsible CCMSPING. |
-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. |
[pf=<profile path>] |
Use this option to specify a profile file with the specified path, if you want to set one of the profile parameters, which you specify in the profile file as follows: ● SAPLOCALHOST=<virtual host name> SAPLOCALHOST specifies a virtual host name with which the
agent’s host is addressed. In this way, two hosts with monitoring
segments can work with the same name (for example, in the case of alternating
operation in the context of high availability solutions), and the content of
the segment can be retained when switching hosts (more information:
You should also use SAPLOCALHOST if the name of the host on which you are installing CCMSPING is longer than 13 characters in length. Specify a name with a maximum length of 13 characters. ● DIR_PERF=<path of CCMSPING working directory> Use this parameter to change the CCMSPING working directory (by default, it is \\host\saploc\prfclog\CCMSPING_<InstNo>\ccmsping). |
Profile File of the
CCMS Agents7. 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 the application server of CEN where the CCMS_Selfmonitoring context is; this is usually the central server. You can determine this server by calling the topology display. To do this, start transaction RZ21; in the Topology group box, choose Context Display and choose Display Overview. Search for the segment name CCMS_Selfmonitoring for the context; the segment name has the naming convention SAP_CCMS_<host>_<system ID>_<instance number> (more information: Finding and Correcting Errors with CCMSPING). |
group |
Logon group (only for load balancing) |
hostname of application server |
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 |
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) |
hostname of message server use Load Balancing group hostname of application server 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 storage 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, the following prerequisites must be fulfilled:
○ When you first register a CCMSPING with the –push option, reset the monitoring segment of the central instance to WARMUP status (more information: Resetting Segment to WARMUP Status).
○ 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 (more information: Adding Systems to the Availability Monitoring Manually).
○ 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 (more information: Configuring Availability Monitoring).
NOTE
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 (more information: Changing the Monitoring Frequency and Timeouts of CCMSPING).
More Information:
Availability Monitoring with CCMSPING