Start of Content Area

Procedure documentation Configuring the CCMS Alert Monitor  Locate the document in its SAP Library structure

Use

For PI, the Computing Center Management System (CCMS) provides a special alert monitor template called Exchange Infrastructure.

You use this alert monitor to monitor the ABAP and Java components (including the Business Process Engine) of your process integration landscape centrally, and to identify different categories of system errors and application errors in the various interfaces and interface namespaces of the components involved.

Besides the information on the monitored components, the alert monitor also provides information on the qRFC queues and alert categories relevant for PI, as well as on adapter-specific errors.

Creating a System Group

You have to define the system group ExchangeInfrastructure_Systems to obtain monitoring information when you call the CCMS alert monitor Exchange Infrastructure from the SAP CCMS Monitor Templates within transaction RZ20.

The definition of the Exchange Infrastructure monitor includes a rule for the uppermost node of the monitor tree. This rule determines the systems of system group ExchangeInfrastructure_Systems that are to be displayed.

This system group must be created and contained in the system from which all systems of your PI landscape are to be centrally monitored, that is, in the central monitoring server.

The system group is maintained with transaction RZ21. Two steps are required:

...

       1.      Choose Technical infrastructure Configure Central System Create remote monitoring entry and maintain all systems of your PI landscape.

       2.      Choose Technical infrastructure Configure Central System Maintain system groups and define the system group ExchangeInfrastructure_Systems consisting of the remote systems created before.

If the local system in which you configure your monitor is part of this group, you can include it in the group by specifying its system ID. You do not need any remote monitoring for this system.

Enabling Performance Alerts for Specific Sender-Receiver Combinations

Perform the following steps if you want to create performance-related alerts for specific sender-receiver combinations and display these alerts in the CCMS alert monitor:

...

       1.      Use the table maintenance transaction SM30 to maintain appropriate logical sender-receiver assignments in table ALXMBPFALERT.

       2.      Specify threshold values for the triggering of alerts for each of these assignments.

Configuring the CCMS Heartbeat Monitor for Java Components

You can use the Generic Request and Message Generator (GRMG) to monitor the availability of PI Java components in your landscape. You define the required configuration settings in a GRMG customizing file, which is then transferred to the monitoring system. A template for such a CRMG customizing file is provided with SAP Note 634771. Use this template and refer to this note for more information.

Perform the following steps if you want to monitor the heartbeat of an installed PI Java component, for example an Adapter Engine:

...

       1.      Define a CRMG scenario for the Java component to be monitored.

Any Java component to be monitored has to be defined as a GRMG scenario. You do this by writing a corresponding XML specification and importing it with transaction GRMG.

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

The template contains a scenario section for each PI Java component.

                            b.      Delete the scenario definitions for the components you do not want to monitor.

                            c.      Call transaction SM59 and create HTTP Connections to External Server for each scenario you defined in the previous step.

                            d.      Specify the host name and the HTTP port of your J2EE Engine as Target Host and Service No. The Path Prefix for each scenario is described in the GRMG template file. Use the user PIRWBUSER for the Logon/Security specifications.

                            e.      Update the scenstarturl entry of the GRMG customizing file for each component with the component's HTTP destination.

Note

When writing your XML, it is always the text between the desc tags that appears in the CCMS user interface.

Ensure that you fill in the other tags as well (just like in the example), since the GRMG framework needs all these entries.

       2.      Call transaction GRMG to upload your XML document once you have finished and saved your XML specification.

For a better display in the alert monitor, we recommend that you do this in the system that belongs to the Integration Server. However, you can also do it in the central monitoring system. In this case, you have to add this system to the system group ExchangeInfrastructure_Systems.

       3.      Log on to the central server of the system to which you have uploaded your XML document (the server that hosts the enqueue service).

       4.      Call transaction GRMG to start the scenarios.

Also use transaction GRMG if you want to stop the CCMS heartbeat monitor configured for a particular Java component while keeping other heartbeat monitors.

Note

For more information about GRMG, see Activating and Customizing Monitoring with the GRMG.

Configuring CCMS Alerts for the Adapter Engine

If processing of a message on the Adapter Engine fails, the message state is changed to faulty. To notify administrators immediately of such processing failures, they can be propagated as alerts to CCMS. As CCMS is the SAP standard interface to third-party monitoring tools, these failure events may also become visible in non-SAP monitoring tools.

Configuration Steps

To make use of Adapter Engine alerts, you must configure the connection to CCMS as follows:

...

       1.      Make sure that the J2EE engine on which the Adapter Engine is running is configured to be monitored by the centralCCMS system.

To do so, execute transaction RZ20 on your central monitor server. There, the J2EE engine should be visible in the CCMS monitor under SAP J2EE Monitor Templates All Systems. If not, refer to the Monitoring Setup Guide for SAP NetWeaver 7.0 at service.sap.com/instguidesnw70 Operations Monitoring.

       2.      Check whether the Adapter Engine is configured to report errors to CCMS.

To do so, start the Visual Administrator and select service SAP XI AF Core. The value of property CCMSEnabled must be set to true (in lower case letters). If it is not, change the property value to true and restart the service.

To verify that the setting is effective, select the Visual Administrator Monitoring service. Under Root Applications, you should see a node for the Adapter Engine.

       3.      Activate the monitoring node for the Adapter Engine.

To do so, start the SAP NetWeaver Administrator and proceed as follows:

                            a.      Choose System Management Monitoring Java System Reports.

                            b.      On the Reports tab, select the report Monitor Browser and show Predefined Local J2EE Views and All.

                            c.      In the monitoring tree, navigate to <SID> Server Applications and select SAP XI Adapter Engine.

                            d.      In the details view, choose Edit Configuration Group and show Data Collection.

                            e.      Choose Enable All Children to activate all monitors of the Adapter Engine configuration group.

Alerting

Once you have performed the configuration steps in the previous section, errors that occur during message processing in the Adapter Engine should show up in both the Visual Administrator of the J2EE engine on which the Adapter Engine runs, and transaction RZ20 on the central monitor server:

      Open the Visual Administrator and select the Monitoring service.

Here you should see that the number of errors of the appropriate error category and error code increases when messages fail on the Adapter Engine.

      Execute transaction RZ20 on the central monitor server and select the Exchange Infrastructure monitor.

You should find a node for the Adapter Engine here and see the same error information as in the Visual Administrator.

Accuracy

The default polling period for the monitor is 30 minutes. If you want to have shorter polling periods, you can change them in the Visual Administrator as follows:

...

       1.      Select the Monitoring service.

       2.      Select an arbitrary Number of errors entry in the monitoring tree of the Adapter Engine (leaf node).

       3.      Choose Configuration in the right-hand pane.

       4.      Choose Edit in the dialog box that appears.

       5.      Change the polling period to 5 minutes, for instance.

       6.      Choose Save and wait until saving is finished (be patient, since this may take a while).

       7.      Select the Configuration Adapter service.

       8.      On the Display Configuration tab page, select apps sap.com com.sap.aii.af.app Monitoring Configurator monitor-configuration.xml.

       9.      In the xml file, change the polled-by-template period to the same value as above, for example, 5 minutes.

   10.      Choose OK to save the modified xml file.

   11.      Restart the Monitoring service to apply the changes.

Displaying XI Alerts in CCMS

To display alerts from alert categories you defined for XI, you have to perform the following configuration steps:

...

       1.      Call transaction RZ20.

       2.      Choose Extras Activate maintenance function to switch to change mode.

       3.      Copy the CCMS alert monitor Exchange Infrastructure under a new name.

       4.      Select the top node of your new monitor and add a new rule node

       5.      Select the rule CCMS_GET_MTE_BY_CLASS.

       6.      As R3System specify the system ID (SID) of your central monitoring server.

       7.      As MTEClass specify SXI_RWBAlerts.

       8.      Select the display option (preferably Short name).

       9.      Choose Continue to confirm your entries.

   10.      Choose Save to save the definition of your new monitor node.

 

End of Content Area