Configuring the CCMS Alert Monitor

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 Create remote monitoring entry from the

Technical infrastructure menu and maintain all systems of your PI landscape.

2. Choose Maintain system groups from the Technical infrastructure menu 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 perform the following

steps if you have installed a PI Java component, for example an Adapter Engine and you

want to monitor its heartbeat in the PI monitor of CCMS. The heartbeat will be

implemented based on the GRMG framework of CCMS.

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 template for such a CRMG customizing file is provided with SAP Note 634771. Use this

template and refer to this note for more information.

When writing your XML:

1. Note that 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 documents (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.

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 central

CCMS 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, follow the steps described in

Chapter 4.2 of the Supportability Setup Guide for SAP NetWeaver 04 on SAP

Service Marketplace at

service.sap.com/nw04operation - Cross-NW.

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

CCMS.

To do so, start the VA/NWA and select service SAP XI AF Core. The value of

property CCMS Enabled 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 VA/NWA Monitoring service.

Under Root – Applications, you should see a node for the Adapter Engine.

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 VA/NWA 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 VA/NWA.

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

VA/NWA as follows:

1. Select the Monitoring service.

2. Select an arbitrary Number of errors entries 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.

There were freshers in my team who wanted to work on sender IDOC adapter. They were searching SDN for step by step guide on ALE configurations for triggering idocs out of SAP. Hence, thought of bloging this on SDN so that it can act as a guide/checklist for XI consultants.All the configuration specified below are to be performed in the Sender SAP system• Create a Logical system for the sender SAP system and the receiving XI system using Transaction – ‘SALE’:

• Assign Client to the Sender Logical System

• Create RFC destination of type ‘3’ for SAP XI system using transaction – SM59: Make sure that the name of the RFC destination and Logical system for SAP XI is the same.

• Create a Distribution Model through ‘SALE’ transaction:

• Create a Distribution Model by selecting ‘Create Model View’:Specify the name of the model view and a description.

• For the model view created above, add the message type of the idoc that you wish to send to SAP XI using this model view. Select ‘Add Message Type’ option and then specify the sender logical system and the receiver logical system.

Save your Model view before proceeding further.• Generate the partner profiles by selecting the navigation path from the main menu, Environment –> Generate Partner profiles Upon selecting the generate partner profiles option, then execute it with the default parameters displayed on the selection screen

• From the main screen navigate through the menu option, EDIT –> MODEL VIEW –> DISTRIBUTE. Upon receiving the message shown here, it means the distribution is successful

• Go to transaction BD10 to send a material out of IDES:

• Go to transaction WE02/WE05 to check the status of the IDOC in the sendign system