Вы находитесь на странице: 1из 9

Tools for Monitoring

This section lists and shortly describes the tools available for monitoring SAP NetWeaver PI.
The monitoring frequency depends on the volume of messages processed. You should check the various monitors at
least once a day. It is also important that you frequently check the message queues to make sure that the overall
message flow is working. If there are problems in a specific queue, no messages in this queue are processed.
Monitoring Tools:
Tool Description
SAP NetWeaver
Administrator for PI
Entry point for monitoring an entire SAP NetWeaver PI system landscape comprising ABAP
and Java systems.
Can be accessed from the PI Tools start page or at:http://<host>:<port>/nwapi.
More information: PI Monitoring with SAP NetWeaver Administrator.
SAP NetWeaver
Administrator (local)
Entry point for monitoring your local SAP NetWeaver system.
Can be accessed at http://<host>:<port>/nwa.
More information: Working with SAP NetWeaver Administrator.
Runtime Workbench (RWB) Entry point for PI monitoring purposes.
Can be accessed from the PI Tools start page or athttp://<host>:<port>/rwb.
More information: PI Monitoring.
Computing Center
Management System
Used to monitor the different components (Java and ABAP parts) of usage
type PI.
Can be accessed from within component monitoring in the Runtime Workbench.
More information: Configuring the CCMS Alert Monitorand CCMS Alert Monitor.
Transaction SXMB_MONI Additional monitoring functions for the Integration Engine to be accessed from your SAP Easy
Access menu underProcess Integration Monitoring Integration Engine Monitoring.
More information: Monitoring Messages.
Additional monitoring functions for the Business Process Engine (BPE) to be accessed from
your SAP Easy Access menu under Process Integration Monitoring Process Engine
More information: Monitoring Integration Processes.

Most of the PI monitoring functions can be accessed with both the SAP NetWeaver Administrator and the Runtime
More informationen about central monitoring with CCMS: Monitoring Setup Guide for SAP NetWeaver
7.0 atservice.sap.com/operationsNW70 Monitoring.

PI Monitoring with SAP NetWeaver Administrator
As an alternative to the Runtime Workbench you can also use the SAP NetWeaver Administrator for PI to monitor your
integration landscape.
To be able to use the SAP NetWeaver Administrator for PI, you must first perform the following steps:
Install CCMSPING and register the system that your SAP NetWeaver Administrator is to run on.
Configure your SAP NetWeaver Administrator.
More information: Configure NWA)
If an Integration Server in your system landscape uses a different System Landscape Directory (SLD) to your
SAP NetWeaver Administrator for PI, export the contents of the SLD for this Integration Server and import it to
the SLD of SAP NetWeaver Administrator.
You must add all the ABAP and Java systems that you want to monitor with your SAP NetWeaver
To monitor the Integration Server, you require the following systems:
The corresponding ABAP system with the client that is configured as the central Integration Engine.
The Java system that acts as the central Advanced Adapter Engine.
You must also add all other advanced Adapter Engines and business systems with an Integration Engine that
are to be monitored.
More information: Adding a Monitored System to the NWA
To be able to use the SAP NetWeaver Administrator for PI, you require the following authorizations:
ABAP users must have one of the following roles:
Composite role with all authorizations
Composite role with read-only access and corresponding restricted authorizations.
Java users must have one of the following UME roles:
Role with all authorizations
Role with read-only access and corresponding restricted authorizations
The ABAP roles are automatically assigned to the Java roles.
Depending on the role assigned to the user, particular elements on the user interface are either activated or
deactivated so that only authorized users can perform the corresponding activities.
Process Flow
Start SAP NetWeaver Administrator for PI from your PI start page (http://<host>:<port>/dir) under Configuration and
Monitoring NetWeaver Administrator.
Displays an overview of the domains in your PI landscape with all the components involved.
More information: Monitoring PI Components.
Depending on the component you select, you can perform the following additional activities; however, not all tasks
listed are available for all components:
Message Monitoring
Performance Monitoring
End-to-End Monitoring
Alert Inbox
Communication Channel Monitoring
Monitoring Java Proxy Runtime
Cache Monitoring

Some of these activities are integrated directly in SAP NetWeaver Administrator, whilst some of them
open functions in the Runtime Workbench.
The following functions are provided for configuring and monitoring Web services:
Web services log viewer for logging and tracing Web services
Monitoring Web Service Sequences
Configuring Web Services, including required security settings
Depending on the selected component, additional tools enable you to do the following:
Check that Runtime Functions are Functioning
Check that cache connectivity is functioning
Index messages and administer indexes
Configure components for end-to-end monitoring
Create alert categories and alert rules
Schedule different kinds of background processing
Archive messages security settings

Some of these tools are integrated directly in SAP NetWeaver Administrator, whilst some of them are
part of the Runtime Workbench.
To start or stop PI-specific Java services (in Adapter Engines only), choose Java Services. The PI-specific services
are preselected.
More information: Starting and Stopping Java EE Services.

Working with SAP NetWeaver Administrator
SAP NetWeaver Administrator (NWA) is a Web Dynpro-based tool for administration and monitoring, offering a central
entry point to the whole SAP NetWeaver system landscape.
The SAP NetWeaver Administrator can be used in a local mode, where you are able to administer an SAP NetWeaver
system deployed and running on your local physical machine or in central mode, where you are capable of operating an
entire system landscape containing ABAP and Java systems as the application platform of SAP NetWeaver and
different usage types installed on top of the application platform.
The NWA unifies the most important administration and monitoring tools both for Java and ABAP systems. The most
important advantages of the NWA are:
You no longer need to switch between different tools for administration, troubleshooting, and problem analysis of
your entire SAP NetWeaver system landscape.
There is a central administration tool available to you landscape-wide for both Java and ABAP systems for starting
and stopping instances, checking configuration settings and logs, and monitoring error-free functioning of
The interface follows the current guidelines for interface design, is easy-to-use, task-oriented, and complete. By
using Web Dynpro, it runs in a normal browser.
The interface allows seamless navigation to other SAP NetWeaver administration tools (User Management Engine,
System Landscape Directory).
For Java, the NWA represents the crossover from various expert tools to an integrated, simple, and clear solution.
The NWA also completes the integration of the data sources for monitoring.
For ABAP, the NWA represents the crossover from many different expert transactions, some of which are difficult to
use, to integrated, centrally available information.
The NWA provides the following work centers for administration:
Operation Management
Configuration Management
Availability and Performance Management
Problem Management
SOA Management
Monitoring XML Messages
You use monitoring to monitor your systems. You can
Monitor the processing of messages and message packages
Display an overview of all defined jobs
Execute error and status tracking
You have called the transaction Integration Engine Monitoring (SXMB_MONI) and the system displays the
screen Integration Engine: Monitoring.
Process Flow
Monitoring contains a monitor for processed XML messages. This is used for determining and evaluating all messages
that are processed by the Integration Engine. The messages can be selected according to particular criteria and
displayed for evaluation purposes.
Monitoring is also used to access archived XML messages. These can also be selected according to particular criteria
and displayed for evaluation purposes. There are two ways to search for archived messages:
Using an archive
Using a message ID
In both cases the system displays a list of archived messages.
The following functions are also available:
An overview of archiving and delete jobs in the Integration Engine
An analysis of the persistence layer
A monitor for sync/async communication
For information about accessibility, see Accessibility in Process Integration (PI).
You cannot execute options in the menu that have the locked symbol ( ), because you do not have the required
The authorizations for the individual functions are tailored to requirements and are assigned as derivations of the role
SAP_XI_MONITOR. They are all based on the authorization object S_XMB_AUTH.
The authorization object S_XMB_DSP controls the display of message contents. Unless the user has the authorization
S_XMB_ADM (administrator), the system only displays XML messages for the current client.
Monitoring Integration Processes
You can monitor the execution of integration processes centrally by using the CCMS alert monitor, or you can use the
additional transactions for BPE monitoring.
CCMS Alert Monitor
SAP Computing Center Management System (CCMS) provides a central point of access for monitoring the
execution of integration processes. In CCMS, you can see at a glance whether processing is running correctly or
whether problems have occurred. If an error occurs, detailed descriptions about causes, remedies, and functions for
troubleshooting are also available.
BPE Monitoring Transactions
The Business Process Engine (BPE) executes integration processes at runtime. When an integration process is
executed, the system creates corresponding work items, just as it does during the execution of an SAP Business
Workflow. A work item can represent a process or a step in a process. You can use the BPE monitoring
transactions to display the generated work items in the Workflow log and therefore display detailed information
about the status of a process or the individual steps.
More information: Using the Workflow Log for Integration Processes
CCMS Alert Monitor: more information: CCMS Alert Monitor
BPE monitoring transactions: Transaction authorization for transaction SXMB_MONI_BPE (S_TCODE) or
administrator role (SAP_XI_BPE_ADMINISTRATOR_ABAP)
Using the CCMS Alert Monitor
Use the CCMS Alert Monitor as the central point of entry for monitoring.
More information: CCMS Alert Monitor
Using BPE Monitoring Transactions
1. Call transaction Business Process Engine Monitoring (SXMB_MONI_BPE).
2. On the Business Process Engine: Monitoring screen, call the required transaction.
The main difference between the individual BPE monitoring transactions is the selection criteria on the selection
screens. The selection screens for integration processes have the same format as those for monitoring SAP
Business Workflows but contain the following additional selection criteria for integration processes.
Service: The communication component you have created for the process in the Integration Directory
Party: The party, if defined in the Integration Directory.
The following table gives an overview of the monitoring transactions:
Description Note
Enables you to select processes using general
selection criteria such as creation date or status (for
To restrict the display of work items that
represent processes, select F in theType field.
Processes for
One Message
Enables you to select processes that process
messages with a particular message type.
Select the required message interface or
Processes for a
Enables you to select processes that process a
particular message.
Select the GUID of the message or the
message interface or namespace.
Processes with
Missed Deadlines
Enables you to select processes with deadline
monitoring where the defined deadline has been

Diagnosis of
Processes with
Enables you to select processes with errors and group
them by cause of error.
You can access container elements from the list
of processes with errors, for example. Once the
cause of the error has been corrected, you can
continue the process.
RFC Monitor Enables you to analyze processes that cannot be
continued due to a problem with a transactional RFC

Restart Process
After Error
Enables you to select processes with errors
(Error status). Once the error has been corrected, you
can continue the process.
If you want to continue all processes found,
select Continue Immediatelyon the selection
Restart Process
After System

Enables you to select and continue pending processes
(Started status). The cause of the pending processes is
outside the Business Process Engine, for example, a
system crash.
If you want to continue all processes found,
select Continue Immediatelyon the selection

3. If you want to analyze an error situation, we recommend performing the following checks first:
Check the general prerequisites for executing integration processes
More information: Checking Prerequisites for Executing Integration Processes
Check whether a runtime version of the integration process has been generated
More information: Checking the Runtime Version of an Integration Process
More Information:
In process-based monitoring, the process view of the monitor for XML messages is particularly relevant (more
information: Monitor for Processed XML Messages).
Configuring the CCMS Alert Monitor
For PI, the Computing Center Management System (CCMS) provides a special alert monitor template calledProcess
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 Process Integration from the SAP CCMS Monitor Templates within transaction RZ20.
The definition of this 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
2. Choose Maintain system groups from the Technical infrastructure menu and define the system
groupExchangeInfrastructure_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
To make performance-related alerts possible for specific sender-receiver combinations and display these alerts in the
CCMS alert monitor, you have to do the following:
Activate the writing of performance data in the respective Integration Engine.
Maintain logical sender-receiver assignments in table ALXMBPFALERT.
Activating the Writing of Performance Data
Perform the following steps to activate the writing of performance data in your Integration Engine:
1. Call transaction SXMB_ADM and choose Integration Engine Configuration Change Configuration.
2. Select category PERF, parameter MEASUREMENT_LEVEL, and set the Current Value to 1 or higher.
3. Select category PERF, parameter MEASUREMENT_PERSIST, and set the Current Value to 1.
For more information, choose the button in the Documentation column.
Maintaining Logical Sender-Receiver Assignments
Perform the following steps to maintain appropriate logical sender-receiver assignments in table ALXMBPFALERT:
1. Use the table maintenance transaction SM30 to maintain table ALXMBPFALERT.

You need the authorizations of the SAP_XI_ADMINISTRATOR role to perform this step.
2. Add a new entry to the ALXMBPFALERT table to activate the monitoring of messages.
3. In the CCMS Alert Monitor Node field, enter the name for the CCMS node to be used to monitor or display the
processing times of the messages (for example, <SenderService_ReceiverService_Application>).
4. In the Sender and Receiver frames, specify the values required to determine the messages to be monitored under
the specified monitor node or displayed in the PI Alert Monitor.
Specify fully qualified names, since generic entries with an asterisk (*) are not supported.
5. In the Alert Thresholds frame, specify the values that lead to an alert if they are exceeded by the average
processing time of messages.
6. Save your new entry.
When you save a new entry, the corresponding node is created and regularly updated every 15 minutes. By default,
the average processing time of messages also refers to the last 15 minutes.
If required, you can use the CCMS node in transaction RZ20 to change this time period as well as the threshold
values. In the PI Alert Monitor, these values are contained under the node IEngine Message Performance by
Sender/Receiver of the Integration Server system.

Changes to threshold values in the ALXMBPFALERT table only take effect on the corresponding CCMS
node if this node is newly created. For this purpose, you must use transaction RZ20 to delete any
existing node beforehand.
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
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:
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 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.
More information about GRMG: 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 AS Java 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, it should be visible in the CCMS monitor
under SAP J2EE Monitor Templates All Systems.
2. Check whether the Adapter Engine is configured to report errors to CCMS. To do so:
a. Start the SAP NetWeaver Administrator.
b. Choose Configuration Management Infrastructure Management Java System
Properties Details Services (alias: /nwa/sys-config).
c. Select the service XPI Service: AF Core.
d. Check whether the value of property CCMSEnabled is set to true (in lower case letters).
e. If it is not, change the property value to true and restart the service (Start & Stop Java EE Services).
3. Verify that the setting is effective. To do so:
a. Start the SAP NetWeaver Administrator.
b. Choose Availability and Performance Management Resource Monitoring Java System
Reports(alias: /nwa/java-sys-reports).
c. Select the report Monitor Browser.
d. Show Predefined Local J2EE Views and All.
e. Go to <SID> Server Applications. You should find a node for the Adapter Engine.
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 SAP NetWeaver Administrator of the AS Java on which the Adapter
Engine runs, and transaction RZ20 on the central monitor server:
Start the SAP NetWeaver Administrator, choose Availability and Performance Management Resource
Monitoring Java System Reports (alias: /nwa/java-sys-reports), and navigate to the Adapter Engine node.
Here you should find 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 Process Integration monitor.
You should find a node for the Adapter Engine here with the same error information as in the SAP NetWeaver
The default polling period for the monitor is 30 minutes. If you want to have shorter polling periods, you can change
them in the SAP NetWeaver Administrator as follows:
1. Choose Availability and Performance Management Resource Monitoring Java System
Reports(alias: /nwa/java-sys-reports).
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. Choose Configuration Management Infrastructure Management Java Configuration Browser.
8. Choose 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. Save the modified xml file.
11. Choose Operations Management Infrastructure Management Start & Stop Java EE Services to restart
the Monitoring service to apply the changes.
Displaying PI Alerts in CCMS
To display alerts from alert categories you defined for PI, 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 Process Integration 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.