7).SAP XI -- RunTime Workbench

Runtime Workbench overview:

Central point of access: XI Runtime
Workbench
Smooth integration with CCMS
Easy Configuration
􀂄Exploiting System Landscape Directory
􀂄Consistent look-and-feel in UI
Improved Error Handling
􀂄Errors classified by error cause.


􀂄 The Runtime Workbench is a tool for monitoring the XI, and all of its components, processes, and
messages, centrally through a java-based interface.
􀂄 The Runtime Workbench unifies many of the monitoring architectures available in SAP solutions into a
single, coherent, web-based interface.The Runtime Workbench offers a central view of all components
and processes.
􀂄 The Runtime Workbench provides for Component Monitoring, Message Monitoring, End-to-End
Monitoring, and Performance Monitoring.
􀂄 There is also an interface for Monitoring and Alert configuration.
􀂄 It integrates with CCMS; for instance, CCMS alerts relevant to the XI can be viewed from the RWB.


Monitoring – Message Monitoring:
􀂄 Message monitoring can be used to find and diagnose errors with specific XI messages.
􀂄 Capabilities are similar to transaction SXI_MONITOR.
􀂄 The message monitoring infrastructure is also used by the end-to-end monitor.
􀂄 Of course, message monitoring is only available for asynchronous messages, unless the XI Pipeline is
configured to persist synchronous (Best Effort) messages.



Monitoring – Component Monitoring:

􀂄 The Runtime Workbench gives you a view of the availability and status of all XI components, including
de-central adapter engines.
􀂄 Allows to monitor ABAP and Java components from a unified UI.


Monitoring – Performance Analysis:


􀂄 The Runtime Workbench Performance Analysis Tool shows performance statistics for user-defined
selection criteria.
􀂄 Allows to see the latency as well as the throughput. This is important for ongoing sizing of the XI.


Monitoring - Alerting:

􀂄 Message alerting allows to set conditions for triggering alerts. This allows for notification of the correct
parties for specific classes of errors.


RWB – Component Monitoring:

Component Monitoring:
>>Monitoring of ABAP and Java
components
>>Central viewing of component‘s
connection status in a specific
domain.
>>Ping of system and sending of
messages to components via a
self-test area.

>>>You use component monitoring in the following cases:
􀁹 If you want to get an overview of the status of the individual components of SAP Exchange
Infrastructure (XI).
􀁹 If you want to call the configuration data of individual XI components.
􀁹 If you want to use test messages to check whether XI runtime is functioning correctly

>>> Use the Component Monitoring in the Runtime Workbench to display and monitor the following XI
components:
􀁹 The Integration Engines
􀁹 The Adapter Engines
􀁹 The Integration Directory
􀁹 The Integration Repository
􀁹 The Runtime Workbench itself.

􀂄 Use the CCMS status to limit the number of components that are displayed. This means that the system
only displays those components with the selected status (all, red, red & yellow).
􀂄 The CCMS status is based on information from the SAP Computing Center Management System
(CCMS). It is displayed by means of a symbol, which can be red, yellow, green, or gray.


Component Monitoring features:

􀂄 Component monitoring provides two views for displaying the components. When you choose Display, the
default view is the table view. This view displays all the XI components maintained in the System
Landscape Directory, their current CCMS status, and the name and type of the component.
􀂄 The system can only display those XI components that are correctly maintained in the System Landscape
Directory.
􀂄 To switch to the tree view, choose Display as Tree. This view sorts the components by component type.
You can select a component from those displayed and do the following:
􀁹 Call information on the current status of the component
􀁹 Call information on the configuration of the component
􀂄 You can also do the following, irrespective of which components are selected:
􀁹 Check that the XI runtime is functioning correctly.


Sending Test Messages:

􀂄 You use this function to send test messages to the Integration Server, irrespective of the XI components
you have selected. To do this, you must specify the necessary data for the message header on the Test
Message tab page, and provide a message payload. After you have specified and sent the test message, the
following result is returned:
􀁹 The message status in the form of a green symbol (OK), or a red symbol (error) with error status.
􀁹 An option to navigate to the message monitoring of the Runtime Workbench.
􀂄 You can persist the header and payload of a test message in the database and call them from there at a later
point in time


RWB – Message Monitoring:

Harmonization of different message monitors
􀂄Integration Engine
􀂄Adapter Framework (J2EE).
All message monitoring centrally accessible
through RWB.
Monitoring locally available as well
􀂄at least for partner connectivity kit.


>>>You use message monitoring in the following cases:
􀁹 To track the status of messages
􀁹 To find errors that have occurred and establish what caused them.

>>>Message monitoring enables you to use the following functions:
􀁹 Display and manage messages
􀁹 Filter the displayed messages by specific criteria
􀁹 Configure the message display.

􀂄 To display the messages for the selected component, choose Display.
􀂄 To update the message display, choose Update.
􀂄 To display all available information for a specific message in the form of a table, choose Details.


RWB – End-to-End Monitoring/Configuration:


>>You use end-to-end monitoring in the following cases:
􀁹 If you want to monitor message processing steps in a number of components (to be configured).
􀁹 If you want to monitor the path of individual messages through these components, from start to end.
􀁹 The central tool for end-to-end monitoring is the Runtime Workbench, which you call from the initial
screen of SAP Exchange Infrastructure (XI).

􀂄 The Runtime Workbench receives the data for end-to-end monitoring from the Process Monitoring
Infrastructure (PMI), which is an SAP monitoring tool for monitoring end-to-end technical processes
involving multiple components.
􀂄 If you want to run end-to-end monitoring, proceed as follows:
1. Select and configure the components that are relevant for monitoring.
2. Send the messages whose processing you want to monitor from start to end.
3. Choose End-to-End Monitoring on the initial screen of the Runtime Workbench.
4. Choose Display.


End-To-End Monitoring at a glance:

>>>End-to-end monitoring has two views for displaying the data delivered from PMI for the individual
processing steps (technical process steps) of the messages in the configured components:
􀁹 The process overview: The process overview displays the total number of processed messages and the
number of messages with errors for each component involved. If the number of messages with errors is
greater than zero, the status of the component changes from green to red. The process overview is the
initial screen of process monitoring and contains a graphical representation of the components involved
in the process. You can open these components and display the process steps involved.
􀁹 The instance view: The instance view displays the path of a specific message through the components
involved. Detailed data is available for each individual processing step in every instance. The instance
view contains a graphical representation of all components involved in the process. It displays the status
for each of the components that the instance passes through. You can open the components to display a
view of the process steps involved with the corresponding data.


End-To-End Monitoring – Prerequisites and configuration:

Activate the Process Monitoring Infrastructure Monitoring by
setting respective configuration parameter in TC SXMB_ADM.


􀂄 To configure End-to-End Monitoring:
1. On the initial screen of the Runtime Workbench, select the Configuration tab page.
2. Enter the logon data for the monitoring server.
3. Choose Display.
4. The system displays the components of your current domain. The Integration Server is selected as the
default.
5. Select the other components that you want to use and configure them as sender or receiver, or both,
depending on the component type.
6. Select the monitoring level that you want to use for each of the selected components.
7. The monitoring level determines which tracking agents are activated for the respective component and
which monitoring data an active agent delivers.
8. Choose Save Configuration.


Performance Monitoring:

Measured data:
􀂄Throughput
􀂄Latency (“processing time”)
Selection and Aggregation by:
􀂄XI component (Integration Server, Adapter Engine)
􀂄Time range
􀂄Message attributes: Sender, receiver, message type

>>You use performance monitoring to display statistical data on the performance of message processing. The
data comes from the Integration Server (IS) or the Process Monitoring Infrastructure (PMI).
>> Use selection criteria to restrict the data that is displayed. For example, you can restrict the data to:
􀁹 The data source
􀁹 A specific component
􀁹 A message processing mode
􀁹 A specific time interval.

>>The system only displays messages that are processed successfully within the specified time interval. You can also choose Extended Search to restrict the displayed messages by using sender and receiver criteria.
If you want to display aggregated data, you must specify an aggregation interval. If you want to display detailed data, you must specify a unique sender and unique receiver.

>>> Use performance monitoring to display the following data:
􀁹 Aggregated throughput data for message processing
􀁹 Aggregated detailed data for message processing performance
􀁹 Individual detailed data for message processing performance


Alert Configuration:

􀂄 Available as of XI 3.0 SP1.
􀂄 When there is some type of failure in the system, you generate an alert; based on this alert, you can send an email,
SMS, fax, email, etc. to notify the proper person.
􀂄 The alerting capability of the Exchange Infrastructure takes advantage of the alerting infrastructure (CCMS) of the
Web Application Server, with the added capability of configuring message-oriented alerts.
􀂄 The Alert Framework provides an interface from the Basis (Web AS) Alert Framework. You use transaction
ALRTCATDEF to define the text, the priority, number of delivery, etc. for the alert.


􀂄 To configure your alerts, proceed as follows:
􀁹 To define an alert category, choose Create Alert Category.
􀁹 You can also create the alert category directly by calling transaction ALRTCATDEF. In both cases you require
the authorizations of the role SAP_XI_ADMINISTRATOR.
􀁹 Enter the following values:
- The receiver of the alert
- The title of the alert
- The text of the alert, including container variables that are filled at runtime.
- You must use the available container variables to create the required container elements. Enter the name of the
container element and the name of the ABAP Dictionary data type from the container variable. All other
entries are optional. To see the available Alert Container Variables, refer to the documentation.
- The follow-up activity: Specify the URL of the required follow-up activity. At runtime, the link address of endto-
end monitoring is always entered as the standard follow-up activity.

􀂄 Create a rule in which you use a defined alert category. To do this, proceed as follows:
􀁹 Give the rule a name.
􀁹 Select the alert category that you want to use by clicking the corresponding category in the alert
category table.
􀁹 Select the required error category and error code.
􀁹 If necessary, specify additional message attributes for the sender or receiver, or both.
􀁹 To add the new rule to the list of alert rules, choose Add Rule.
􀁹 If the check box Rule Activated is selected (default setting), the rule is automatically activated when you
add it and is displayed as active.


RWB – Cache Monitoring:

>>Cache monitoring enables you to display representations from the value mapping table that are currentlylocated in the runtime cache of the Integration Engine or Adapter Engine.
>> The following information is displayed for each representation:
􀁹 Context
􀁹 Issuing agency
􀁹 Identification schemes
􀁹 Value
􀁹 You can restrict the number of hits displayed