How to CCMS for SolMan and PI

How to Guide :: Setup CentralMonitoring for SAP PI Systems

How to Guide :: Setup Central Monitoring for SAP PI Systems

CONFIDENTIAL PAGE 2 OF 22 14/06/2009 23:53:30

Document Control Section

Title How to Guide :: Setup Central Monitoring for SAP PI Systems

Version DRAFT version

Task How to Guide

File Name PI - CEN - sent_new_working.doc

Path D:\My Documents

Author

Template

Created Monday, May 25 2009

Last Author

Last Edited 1931

Print Date Sunday, 14 June 2009

Number of Pages 22

Comments

Revision Date Revision Description

Status

Target Readership : SAP System Administrator; Support Engineers

Approved By: Date / /

Name and Title:



TABLE OF CONTENTS

I. INTRODUCTION 4

A. CCMS (COMPUTING CENTER MANAGEMENT SYSTEM) 4

B. CCMS MONITORING FOR PI 5

II. PRE-REQUISITES 6

III. STEP BY STEP PROCEDURE 7

A. STEP TO BE DONE ON THE PI SYSTEM ( SATELLITE SYSTEM ) 7

B. STEP TO BE DONE ON SOLUTION MANAGER SYSTEM ( CEN SYSTEM ) 8

C. CONFIGURE THE GRMG SCENARIO FOR JAVA COMPONENTS 13

D. CREATE A CUSTOM VIEW FOR MONITORING THE ALERTS 15

E. THE MONITORING TOOLS 19

IV. CHECKLIST 21

V. REFERENCES 22

A. NOTES 22

B. GUIDES 22



I. Introduction

a. CCMS (Computing Center Management System)

With the monitoring architecture of the CCMS (Computing Center Management System), SAP provides amonitoring architecture to make all required information available in a central monitoring system (CEN), andtherefore to make the administrators’ work easier. Problems are displayed as soon as they occur; the logfiles can also be accessed from one location, which reduces the time required for error identification andcorrection.

SAP’s Monitoring Infrastructure has the following benefits :

Central monitoring

Large landscapes can be centrally monitored at a low total cost of operation.

Full scalability

Landscapes with only a few components or a large number of components can be efficiently monitored.

Preventive monitoring with alerts

No admin activity is required except in case of alerts. Alert notifications (e-mail, SMS …) can betriggered automatically.

Assisted problem detection and resolution

From the central system, administrators can drill down to a monitored component to remove the causeof an alert using predefined analysis functions.

SAP’s Monitoring Infrastructure provide the two main tools :

1) SAP NetWeaver Administrator (NWA)

Java WebDynpro application, available as of SAP NetWeaver ´04 Support Package 12

On SAP NetWeaver ´04, 7.0: Administration of Java components, central monitoring

Two important Roles for NWA:

a) Local NWA role (as of 7.1) for Administration of local AS Java, additional component-specificfunctions

b) Central NWA role - Fully integrated into SAP Solution Manager

2) SAP Solution Manager 7.0 (based on SAP NetWeaver 7.0)

Before SPS 15: support-focused, includes monitoring and reporting, no administration

As of SPS 15 (available since February 2008): All functions of SAP NetWeaver Administrator’s centralrole are merged into SAP Solution Manager 7.0. SAP Solution Manager will be enhanced byadministrative functions with Enhancement Package 1.



b. CCMS monitoring For PI

The SAP Computing Center Management System (CCMS) provides a special alert monitor for SAP NetWeaverPI, which can be used to monitor the PI ABAP and Java components (including the Business Process Engine)centrally. The CCMS Monitor can also provide information on the monitored components, the alert monitoralso provides information on the qRFC queues relevant for PI. These queues ensure that messages in PI areprocessed exactly once only, and that they are processed in chronological order.

The CCMS Monitor for PI :

Makes use of basic SAP NetWeaver Application Server (AS) monitoring services such as PMI, CCMS, andAlert Framework

Requires that these basic services are provided by one central monitoring server

Queries the System Landscape Directory (SLD) for information about distributed process integrationcomponents and their communication addresses

Provides central Web browser access to monitoring UIs through the Runtime Workbench

For effective PI monitoring, following are the components needs to be monitored :

1. Component Monitoring

2. Message Monitoring

3. End-to-End Monitoring and Configuration

4. Performance Monitoring

5. Index Administration

6. Alert Configuration and Alert Inbox

7. Cache Monitoring

There are two main ways to configure the PI monitoring

1. Runtime workbench ( for monitoring an individual PI installation )

2. NetWeaver Administrator ( for monitoring multiple Pi Installation )

You can access both the methods by http://<host?:<port>/dir, under Configuration and MonitoringNetWeaver Administrator / Runtime Workbench .



II. Pre-requisites

1. Define the central monitoring system in the exchange profile. Specify the following parameters

1.1. com.sap.aii.rwb.server.centralmonitoring.r3.ashost ( fully qualified host name )

1.2. com.sap.aii.rwb.server.centralmonitoring.r3.client

1.3. com.sap.aii.rwb.server.centralmonitoring.r3.sysnr

1.4. com.sap.aii.rwb.server.centralmonitoring.httpport

2. You can maintain the exchange profile parameters via the following link

http://<host:port>/webdynpro/dispatcher/sap.com/com.sap.xi.exprofui/XIProfileApp

2.1. when prompted for login, user with J2EE security role administrator is required. This J2EErole is mapped to role SAP_XI_ADMINISTRATOR_J2EE

3. Also, incase you are planning to use any user other than PIRWBUSER (default user) for runtimeworkbench, please maintain the following parameters in the exchange profile

3.1. com.sap.aii.rwb.serviceuser.name

3.2. com.sap.aii.rwb.serviceuser.pwd

3.3. com.sap.aii.rwb.serviceuser.language

4. execute the report “RSXMB_ACTIVATE_ICF_SERVICES” (see also SAP Note 517484) to activate therequired ICF services on the Central monitoring system (CEN) and the Integration server (ABAP system)

5. The content of the System Landscape Directory (SLD) must be consistent. The Runtime Workbenchand other services, for example the directory cache refresh, read component and addressinginformation from the SLD. There are two complementary ways to provide the SLD with PI-specificcontent:

5.1. Manually - You define business systems by using the Business Landscape UI of the SLD.Before you do this, the technical systems need to be described in the SLD.

5.2. Automatically - PI components register themselves with the SLD as soon as they are startedup. This type of self-registration does not require SLD bridges. Stop and restart the followingservices via NWA to trigger the self-registration of Adapter Engine and Runtime Workbench

com.sap.aii.af.appcom.sap.aii.af.cpa.appcom.sap.xi.rwb

6. Ensure the PI system is registered in the Solution Manager System. It can be the central SLD, whichboth SAP PI and SAP Solution manager system access or separate SLDs synchronized via a SLD Bridge (SLD 7.0 ) or bi-directional synchronization ( SLD 7.10 )

6.1. Logon to the Solution Manager SLD Home Technical Systems set the filter GO

6.2. The PI system should be listed. Verify the system details

Note You can either choose to perform the configuration steps using the Configuration wizards “ wizardbased Configuration” or perform them manually. For details on the “Wizard based configuration”please check :

http://help.sap.com/saphelp_nwpi71/helpdata/en/92/f418418291a854e10000000a1550b0/frameset.htm

SAP Note 923359 - Collective Note: Configuration Wizard - Template Installer

http://help.sap.com/saphelp_nwpi71/helpdata/en/92/f418418291a854e10000000a1550b0/fra



III. Step by Step Procedure

a. Step to be done on the PI system ( satellite System )

Configure CCMS for monitoring PI :

1. Logon to the PI/XI system ( satellite system from Solution Manager System ) , P71 in this case.

2. Execute the transaction RZ20 and “activate the background dispatching”

3. ensure that the background job “SAP_CCMS_MONI_BATCH_DP” is scheduled and active.

4. Now create the user which will be used for monitoring purposes

Note : You can Create a new user and use for subsequent configuration, if the CSMREG users is being usedfor some other purposes.



b. Step to be done on Solution Manager system ( CEN System )

5. logon to the Central Monitoring system (SM4 – Solution manager 7.01 with EH 1 ) with administrativeprivileges

6. execute the transaction RZ21 and from the menu option choose

7. ensure that the background job “SAP_CCMS_MONI_BATCH_DP” is scheduled and active.

8. Now from RZ21 activate the Central System dispatching

9. ensure that the background job “SAP_CCMS_CENSYS_DISPATCHER” is scheduled and active.

10. Now create the user which will be used for monitoring purposes



Note : You can Create a new user and use for subsequent configuration, if the CSMREG users is being usedfor some other purposes.

11. Now generate the Configuration file for the monitoring agents :

12. System will prompt you to save the “csmconf” file, save it at the appropriate place to be used later foragent configuration.

13. Now create the two RFC connections (via sm59) for the satellite systems with the following names<SID>_RZ20_COLLECT and <SID>_RZ20_ANALYZE.

14. Now , to create the satellite system (P71) in the Central Monitoring system (SM4), from RZ20 select themenue option

15. select the appropriate “component type” from the drop down menu e.g. “DoubleStack”

16. fillout the required details on the screen and hit save button



17. Verify that the system has been added successfully, from the RZ20, under topology click on Displayoverview” button

18. Ensure that you are able to locate the system that you have just added.



19. Now, run the transaction SXMB_ADM under “configuration” choose “Integration EngineConfiguration” and execute



20. On the next displayed screen, click on the “change configuration” button

( ) and create an entry for “CCMS_MONITORING” as follows

21. Run the transaction RZ21 to maintain the “System Groups” and from the menu options select

22. select “Maintain Groups” “Create System Group” “ExchangeInfrastructure_Systems”

23. Now highlight the newly created system group and right click to create a system under it.

24. Provide the system name <SID> ( P71 in this case )



c. Configure the GRMG scenario for JAVA Components25. To configure the GRMG for the java components, logon as the J2EE administrator ( or equivalent ) of

the solution manager ( CEN) system

http://<hostname>:<port>/nwa Configuration Management Scenarios Configuration Wizard

To create a GRMG customizing file, download the GRMG customizing template from SAP Note 634771

26. select the wizard “Setup GRMG for a Managed system” and execute it. Ensure that the wizardcompleted successfully.

27. select the wizard “Setup GRMG for the Central System” and execute it. Ensure that the wizardcompleted successfully.





d. Create a Custom View for Monitoring the alerts

28. Now Create a new monitor set for monitoring the PI/Xi system via RZ20

29. go to transaction RZ20 and select Extras Activate Maintenance Function

30. Now create a copy of the “Exchange Infrastructure” monitor set. select the monitor “SAP CCMS MonitorTemplates” “Exchange Infrastructure”, then from the menu options “Monitor (set)” copy.

31. fillup the new “monitor set name” and the monitor as “Exchange Infrastructure”.

32. A new node will be created as follows



33. Select the newly created monitor set and the from the menu options choose “Monitor (set)” create .

34. Now to create a “ Rule Based” node, from the displayed screen, select Edit Create Node

35. Select the radio button “ Rule Node” and click on continue

36. fill in the rule name as “CCMS_GET_MTE_BY_CLASS” and click on continue button



37. Do the required settings

37.1. R3System – should be the <SID> of the system that you want to monitor

37.2. MTEClass – for PI use “SXI_RWBAlerts”

37.3. Display options – as required – preffered short names

38. click on “continue button, if prompted for the user-id password of the monitored system provide that

39. The following tree should be displayed





e. The Monitoring Tools

40. For monitoring purposes you can use any of the 3 tools

40.1. RZ20 or S_B6A_52000011

40.2. Runtime work bench

http://<host?:<port>/dir under Configuration and Monitoring Runtime Workbench

OR

http://<hostname>:<port>/rwb



40.3. NetWeaver Administrator

http://<host>:<port>/dir under Configuration and Monitoring NetWeaver Administrator

OR

http://<hostname>:<port>/nwa

40.4. You can also see the alerts via http://<hostname>:<port>/nwa SOA Management -->Monitoring



IV. Checklist

Steps to be performed in PI System Done Steps to be performed in SOLMANSystem

Done

Pre-requisites

Create CEN system entry in Exchange profileof PI system.

--

Activate required CIF services, executereport RSXMB_ACTIVATE_ICF_SERVICES

Activate required CIF service, executereport RSXMB_ACTIVATE_ICF_SERVICES

Register PI components to the SLD. Check PI components are registered andaccessible in the Solution Manager systemSLD.

CCMS Configuration Steps

Activate background dispatching. Ensure thatthe background jobSAP_CCMS_MONI_BATCH_DP is scheduledand active

Activate background dispatching. Ensurethat the background jobSAP_CCMS_MONI_BATCH_DP is scheduledand active

Decide the user to be used for monitoringpurposes, default users is CRMREG users

Activate Central System Dispatching,ensure that the background job“SAP_CCMS_CENSYS_DISPATCHER” isscheduled and active

Decide the user to be used for monitoringpurposes, default users is CRMREG users

Create CSMCONF file

Ensure the RFC destinations for thesatellite (PI) system exists.

Create Satellite (PI) system in CEN(Solman)

Update the “Integration Engine”configuration, create the entry for“CCMS_MONITORING”

Update the CCMS Customizing, maintainsystem group and system

Trnx RZ20 drill down to the “ExchangeInfrastructure” tree or TrnxS_B6A_52000011 to check the alerts

Configure GRMG for Java components

Create custom view RZ20 to monitor Alets



V. References

a. Notes

SAP Note # Description

1107033 How to display Java monitoring data of NW7.1 in CCMS (NW7.0)

119735 GI for sales order with tied empties

1161912 RZ20: "SAP CCMS Technical Operations Templates" is changed

1288240 No Adapter data reported to CCMS

1131738 RWB warning 'Central CCMS monitor not available'

923359 Collective Note: Configuration Wizard - Template Installer

1107808 1107808 - Collective Note: Configuration Wizard 7.1

1297288 XI/PI CCMS Alert Monitor: Navigation to Message Monitor

764176 Error in XI due to inconsistent SLD contents

816973 ITS 7.00 - preclarification and basic problem analysis

1060264 PI Troubleshooting Guide 7.1

834534 SAP Solution Manager roles in Release 7.0

1319323 CCMS: insufficient rights in the SAP_BC_CSMREG role

730629 CCMS agents: Java interface for registration

b. Guides

Material # Description

ADM106, ADM107 Advanced System Monitoring

ADM100 SAP Technology Administration

ADM200 SAP AS Java Administration

SMO100 System Administration with SAP Solution Manager