Configuring Availability Monitoring with
CCMSPING
Use
You have to configure the CCMS Agent for monitoring PI systems. With this function, you can monitor whether remote systems and their instances are available for work from the NetWeaver Administrator of your central monitoring system (CEN).
Procedure
Adding Remote System to CCMSPING Availability Monitoring
1. Log on to the central ABAP system.
2. Execute RZ21 transaction.
3. Navigate to Technical Infrastructure → Availability Monitoring → Configure CCMSPING Availability Monitoring.
4. In Monitored Systems Area, choose Monitoring.
5. Choose Create Systems. A pop-up to enter the system details displays.
6. Enter the system name in the Value field. Choose Continue.
7. In the Connection Data: ABAP Message Server area, enter the following:
a. Host name of central service instance in the Message Server host name field.
b. Message server port in the IP Service Name field.
8. In the Connection Data: Java Message Server area, enter the following:
a. Host name of central service instance in the Message Server host name field
b. msgHTTP port of central service instance in the Message Server HTTP Port field.
9. In the Monitoring Options for Application Servers area:
a. Choose Monitor All Application Servers
b. Select the Ping Monitoring and Check logon options.
10. In the Monitoring Options for Logon Groups area choose Choose Activate Check for All Groups, Including New Groups option.
11. In the Destination of Responsible CCMSPING area select the RFC destination of CCMSPING agent.
12. Choose Copy Connection Data and Options.
Registering Agents of Remote System (applicable for Managed Systems)
...
1. Log on to the central ABAP system.
2. Execute RZ21 transaction.
3. In Topology area choose System Overview.
4. Choose Display Overview
5. Choose Edit mode.
6. Choose Create Entry.
7. In the Type of Component to be Monitored field, chose the Double Stack, Java, or ABAP.
a. If you have selected the component type as ABAP, enter the following in the Monitored Systems area:
i. SID of the system in the System ID field.
ii. message server host in the Message Server field.
iii. log on group to be used in the Logon Group field.
iv. client number of the system in the Client field.
v. administrator user details in the User Name field
vi. password of the administrator user in the Password field.
b. If you have selected the component type as Java, enter the following in the Monitored Systems area:
i. SID of the system in the System ID field.
ii. message server host in the Message Server field.
iii. msgHTTP port of central service instance in the Message Server HTTP Port field.
c. If you have selected the component type as Double Stack, enter the following in the Monitored Systems area:
i. SID of the system in the System ID field.
ii. ABAP message server host in the Message Server field.
iii. log on group to be used in the Logon Group field.
iv. client number of the system in the Client field.
v. ABAP administrator user details in the User Name field
vi. password of the administrator user in the Password field.
8. Leave the default values as it is in the RFC Connections to Monitored System Details area.
9. In CSMREG user of Central System area, enter the user details that can be an administrator or a user with SAP_BC_CSMREG authorization.
To edit the client and user name choose Change button.
CSMREG is the default user name.
10. In the Operating System user on the Host of the Monitored System area, enter the OS user (<sid>adm user) credentials of the Monitored System.
11. Choose Save.
12. Log on to the central the ABAP system.
13. Execute SE37 transaction on the central ABAP system.
14. Enter the Function Module name SCSM_EDS_RESET_MAPPING_CACHES.
15. Choose Test/Execute(F8).
16. Leave the default input parameters and choose Execute(F8).