You are on page 1of 9

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.

Enabling Performance Alerts for Specific Sender-Receiver Combinations Perform the following steps if you want to create performance-related alerts for specific senderreceiver combinations and display these alerts in the CCMS alert monitor: 1. Note that it is always the text between the desc tags that appears in the CCMS user interface. You do not need any remote monitoring for this system. Any Java component to be monitored has to be defined as a GRMG scenario. Configuring the CCMS Heartbeat Monitor for Java Components perform the following steps if you have installed a PI Java component. When writing your XML: 1. Use the table maintenance transaction SM30 to maintain appropriate logical sender-receiver assignments in table ALXMBPFALERT. Choose Maintain system groups from the Technical infrastructure menu and define the system group ExchangeInfrastructure_Systems consisting of the remote systems created before. you can include it in the group by specifying its system ID. You do this by writing a corresponding XML specification and importing it with transaction GRMG. If the local system in which you configure your monitor is part of this group. 1. The heartbeat will be implemented based on the GRMG framework of CCMS. . A template for such a CRMG customizing file is provided with SAP Note 634771. Define a CRMG scenario for the Java component to be monitored. 2. Specify threshold values for the triggering of alerts for each of these assignments. Use this template and refer to this note for more information.2. for example an Adapter Engine and you want to monitor i s t heartbeat in the PI monitor of CCMS.

For a better display in the alert monitor. since the GRMG framework needs all these entries. see Activating and Customizing Monitoring with the GRMG. 2) Call transaction GRMG to upload your XML document once you have finished and saved your XML specification. Configuring CCMS Alerts for the Adapter Engine If processing of a message on the Adapter Engine fails. To notify administrators immediately of such processing failures. they can be propagated as alerts to CCMS. you can also do it in the central monitoring system. you have to add this system to the system group ExchangeInfrastructure_Systems. the message state is changed to faulty. Make sure that the J2EE engine on which the . As CCMS is the SAP standard interface to third-party monitoring tools. 4. Call transaction GRMG to start the scenarios. Configuration Steps To make use of Adapter Engine alerts. you must configure the connection to CCMS as follows: 1. However. we recommend that you do this in the system that belongs to the Integration Server. In this case. Also use transaction GRMG if you want to stop the CCMS heartbeat monitor configured for a particular Java component while keeping other heartbeat monitors.Ensure that you fill in the other tags as well (just like in the example). Log on to the central server of the system to which you have uploaded your XML documents (the server that hosts the enqueue service). For more information about GRMG. 3. these failure events may also become visible in non-SAP monitoring tools.

and transaction RZ20 on the central monitor server: Open the VA/NWA and select the Monitoring service. you should see a node for the Adapter Engine. select the VA/NWA Monitoring service.com/nw04operation . Under Root ² Applications. follow the steps described in Chapter 4. There.Adapter Engine is running is configured to be monitored by the central CCMS system. execute transaction RZ20 on your central monitor server. You should find a node for the Adapter Engine here and see the same error information as in the VA/NWA.Cross-NW. Check whether the Adapter Engine is configured to report errors to CCMS. start the VA/NWA and select service SAP XI AF Core. If not. the J2EE engine should be visible in the CCMS monitor under SAP J2EE Monitor Templates -All Systems. The value of property CCMS Enabled must be set to true (in lower case letters). Execute transaction RZ20 on the central monitor server and select the Exchange Infrastructure monitor. Alerting Once you have performed the configuration steps in the previous section. change the property value to true and restart the service.sap. To verify that the setting is effective. To do so. 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. If you want to have shorter . Accuracy The default polling period for the monitor is 30 minutes. 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. If it is not. To do so.2 of the Supportability Setup Guide for SAP NetWeaver 04 on SAP Service Marketplace at service. 2.

com . Choose Extras -Activate maintenance function to switch. Choose OK to save the modified xml file. Restart the Monitoring service to apply the changes. On the Display Configuration tab page. 4. Change the polling period to 5 minutes. . Choose Save and wait until saving is finished (be patient. 6. 2.com. 8. change the polled-by-template period to the same value as above. 5 minutes. select apps -sap.xml. 11. 10. Choose Configuration in the right-hand pane.aii.appMonitoring Configurator -monitor-configuration. since this may take a while). Select the Configuration Adapter service.polling periods. Call transaction RZ20. 2. 9.sap. In the xml file. 5. Choose Edit in the dialog box that appears. Select the Monitoring service. you have to perform the following configuration steps: 1. Select an arbitrary Number of errors entries in the monitoring tree of the Adapter Engine (leaf node). 3. 7.af. for instance. Displaying XI Alerts in CCMS to display alerts from alert categories you defined for XI. for example. you can change them in the VA/NWA as follows: 1.

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. They were searching SDN for step by step guide on ALE configurations for triggering idocs out of SAP. thought of bloging this on SDN so that it can act as a guide/checklist for XI consultants. . Hence.There were freshers in my team who wanted to work on sender IDOC adapter.

‡ 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. 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. ‡ For the model view created above.

Upon receiving the message shown here. then execute it with the default parameters displayed on the selection screen ‡ From the main screen navigate through the menu option. Environment ±> Generate Partner profiles Upon selecting the generate partner profiles option. EDIT ±> MODEL VIEW ±> DISTRIBUTE. it means the distribution is successful ‡ Go to transaction BD10 to send a material out of IDES: .Save your Model view before proceeding further. ‡ Generate the partner profiles by selecting the navigation path from the main menu.

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