02 Monitoring Concepts PDF

End Monitoring in Detail
Author: Offer Amram
1
Objectives
After completing this session, you will be able to:
Know monitoring concepts in general
Configure and use the End to end monitoring
Perform monitoring
© SAP AG 2004, End to End Monitoring, Offer Amram / 2
2
Monitoring Concepts in General
Solution Manager
End to End
Configuration of the End to End
Performance monitoring
3
End to End - Monitoring
SAP CRM SAP R/3

Different perspectives:
System monitoring
System administrator
Focus on single components SAP APO
Systems have to operate
reliably
Technical Process Monitoring Create Order

Process administrator Sales Fulfill-
Order ment
Focus on end-to-end process
flow
Cross component
Performance/Throughput Check
Availability
For ensuring availability, reliability and performance of IT Landscapes it is

necessary to monitor the IT landscape.
2 different perspectives:
System monitoring checks the actual status of the components of the IT landscape. Main
focus: availability/reliability of the component
Process monitoring checks the dynamic flow of a process across components. Main focus:
Performance/throughput of the end-to-end process
4
System Monitoring
Detection of error situations in a system
Detailed error analysis
SAP R/3 SAP CRM SAP CRM

Logistics Germany France
SAP R/3
Finance SAP APO SAP BW
System Communication
Database Consistency
Performance …
Alert: Number of open requests
in queue exceeds threshold !!! (activ agents)
Customers need an infrastructure, which delivers

z Detailed and aggregated monitoring data for all important components of the system landscape
z System availability information
z (technical) repository for all components
z Statistical information of all ABAP and Non-ABAP components
z Easy-to-configure notification service in case of critical system situations
z Integration of 3. party management data into the SAP view
Notifies errors on components

Alerts are sent to users
No information about which process instance is effected
5
Process Monitoring
Real time monitoring for business critical processes

Process orientated presentation
Process orientated general key figures
z Finished
z Canceled
z Open
z Average Duration
z ..
Process orientated analysis in a heterogeneous system landscape
Already during development and testing
More key figures
z Performance
z Throughput
z Errors
Instances
In deep detail if necessary
Process identification
Tools
Documentation
Customers need an infrastructure, which delivers

z A business process oriented view to the system landscape
z The possibility to trace a single business process running over several components of a system landscape
z ONE detailed description of the business components, process and interfaces
z Answers about, which business process is affected in case of an error, and what to do
6
Benefits of Process Monitoring
Efficient monitoring and reporting of processes
Error analysis during development, testing and in productive

systems
Measuring of process performance
Benchmarking of processes
Identifying bottlenecks within a process flow
Process based service level agreements
Process based accounting
Efficient monitoring and reporting of processes:

Error analysis during development, testing and in productive systems:
Measuring of process performance:
Benchmarking of processes:
Identifying bottlenecks within a process flow:
Process based service level agreements:
Process based accounting:
7
Business Process vs. Technical Process
Business Process
Flow of business actions
Flexible
Mainly controlled by customizing
Wider scope
Longer periods
Contains multiple technical processes
Technical Process
Flow of technical steps
Static with few variations
Mainly controlled by coding
Smaller scope
Shorter periods
8
Definition: Process and Process Steps
Business Sales Order

Process Management
Enter Sales Check Create Order Billing

Business
Order Item Availability Fulfillment
Process Sales Order
Steps
Technical
IDoc- TRFC IDoc- Call
Process Out- In- Appli-
Steps bound bound cation
9
Example: Technical Steps in ALE Process
System A System B
Application
ALE API
Create IDoc
asynchronous R
(configurable)
Process IDocs tRFC

R IDoc-
create tRFC
Inbound
queue entry asynchronous
(always) R
asynchronous
(configurable)
IDoc-selection
and start of
application
R
asynchronous
(configurable)
Post document
and update
IDoc-status
10
Monitoring – Current Situation
Focus on System Monitoring

System status
Thresholds
Alerts
User: System Administrator
Limited Process Monitoring

Flow of technical process steps
within a process instance
User: Process Administrator
Single transactions only
Asynchronous processes not CRM R/3
supported
Difficult to relate events to
business objects / processes
APO
11
Example: Current Situation ALE Monitoring
System monitoring tools:

ALE / IDoc Monitors
WE02 and BD87
tRFC-Monitor
SM58
CCMS monitoring objects

RZ20 -> Component „ALE/EDI“
Business process monitoring tools

BPM of the Solution Managers
Integration of ALE interfaces
Based on CCMS
12
ALE Interface Monitoring
Business Process: Sales order information transferred from SAP R/3 System
X48 to SAP R/3 System DSM via ALE interface.
Solution Manager
Alert monitoring view

of business process:
Sales Order
Management
Red alert :
Interface in
critical state
Where does this information come from? …..

13
ALE Interface Monitoring - Errors
… Information based on ALE Monitoring in CCMS

Outbound: X48 RZ20 Inbound: DSM
IDoc Overview (WE05)
List of IDocs in error state
Which outbound IDoc is related with which inbound IDoc?
14
ALE Interface Monitoring - Performance
What has been the processing time of IDocs from end-to-end?

Outbound: X48 Inbound: DSM
IDoc overview (WE05) Workload Statistic (STAD)
1) Select IDoc and find 2) Search statistic records

corresponding TID with this TID
What is the average time required for processing an IDoc?

What is the minimal/maximal processing time?
15
Issues with Existing Tools
System monitoring tools

Focus on single system
Difficult to reconstruct connection between systems
Not process oriented
Read complete monitoring data from single systems
System load / performance
Instance view for objects only (e.g., IDocs)
No instance view for processes (e.g., relation between outbound and
inbound IDocs)
Different UIs and behavior of tools
Error detection and analysis is partly elaborate
E.g., relation of a tRFC error to an ALE interface
Business Process Monitoring in SAP Solution Manager

Analogous, since based on the same tools
16
End to End monitoring (E2E)
Central monitoring of technical process

instances
Flow of technical process steps
Cross-system processes
Asynchronous processes (including multiple
transactions)
Relation to business objects
Main tasks
Localization of errors and performance
bottlenecks
Single interface for monitoring multiple
technologies (XI, qRFC, ALE, …)
Documentation of process flow CRM R/3
Data Provider for SAP Solution Manager
Benefits
Faster issue resolution
Quality improvements
Easier administration and support APO
=> Reduced TCO
17
End to End monitoring
Goals
Realization of a monitoring infrastructure for technical processes
Support of cross-component and asynchronous processes
Data provider for SAP Solution Manager (Business Process
Monitoring)
Prevailing Conditions
Runs at customer sites with minimal customizing
Web user interface
Supports lower releases
Cooperation with SAP Solution Manager
No (or at most minimal) changes of existing applications
System and application load to be neglected
Unification of existing tools, especially user interface
18
End to End & SAP Solution Manager
SAP Solution Manager
Business Sales Order

Process Management
Enter Sales Check Create Order Billing

Business
Order Item Availability Fulfillment
Process Sales Order
Steps
Process Monitoring Infrastructure
Technical
IDoc- TRFC IDoc- Call
Process Out- In- Appli-
Steps bound bound cation
19
End to End monitoring and infrastructure
In the last pages we have gone through the technical concept and
infrastructure of the monitoring.
The XI End to end monitoring uses this infrastructure to monitor itself.

In the next chapter we are going to configure it and apply it.
20
Configuring the End to End Monitoring
End to End
21
Configuring the End to End Monitoring (step 0)
In order to view messages in End-to-End Monitoring of the Runtime Workbench, the

following basic configurations are necessary:
1.You need to make a few system parameter changes and
2.The systems to be monitored need to be configured in the Runtime Workbench

under Configuration.
3.On each Adapter Engine that is to be monitored, a destination called pmistore needs
to be defined using the service user for the Runtime Workbench (XIRWBUSER) for
authentication.
For further details, see the Installation Guide – SAP Exchange Infrastructure 3.0,
chapter Creating HTTP Destination pmistore in the SAP J2EE Environment.
Ensure that the service user for the Runtime Workbench (XIRWBUSER) is defined in
each component that is to be included in end-to-end monitoring.
22
End-To-End Monitoring: Configuration II
Central monitoring server to be defined in the exchange profile

The following properties need to be set in the exchange profile. They define the SAP Web
AS that provides the CCMS monitor, End to End server and Alert server for XI.
com.sap.aii.rwb.server.centralmonitoring.r3.ashost
com.sap.aii.rwb.server.centralmonitoring.r3.client
com.sap.aii.rwb.server.centralmonitoring.r3.sysnr
com.sap.aii.rwb.server.centralmonitoring.httpport
Technical user for the Runtime Workbench to be defined on all XI components

The technical user for the Runtime Workbench (XIRWBUSER) as defined in the exchange
profile needs to be available on all XI components that are to be monitored centrally. This
service user is defined by the following properties which are initially set during installation:
com.sap.aii.rwb.serviceuser.name
com.sap.aii.rwb.serviceuser.pwd
com.sap.aii.rwb.serviceuser.language
ITS plug-in running on the Integration Server and central monitoring server.
To allow navigation from the Runtime Workbench to ABAP monitoring transactions, for
example to RZ20, the ITS plug-in needs to run on the Integration Server and on the central
monitoring server.
Use transaction SICF to check whether the ITS service is activated. You may also
have to set profile parameter em/plobal_area_mb to 256 to allow proper ITS
operation.
23
End-To-End Monitoring: Configuration III
Activation of required SICF services
In addition to ITS, additional SICF services have to be activated on the central monitoring server in order to allow proper
operation of end-to-end monitoring and alerting. You may activate the required services by executing the report
RSXMB_ACTIVATE_ICF_SERVICES.
Alternatively, you can manually activate the services listed below by transaction SICF.
SICF services to be activated
Function Path to SICF Service
ITS plugin /sap/bc/gui/sap/its/webgui
End-to-end monitoring /sap/bc/bsp/sap/spi_monitor

/sap/bc/bsp/sap/spi_admin
/sap/public/bsp/sap/public/graphics/jnet_handler
/sap/public/bsp/sap/public/graphics/mimes
/sap/bc/bsp/sap/public/graphics
/sap/bc/graphics/net
/sap/bc/bsp/sap/graph_bsp_test
/sap/bc/bsp/sap/graph_bsp_test/Mimes
Alerting
/sap/bc/bsp/sap/sxms_alertrules
/sap/bc/bsp/sap/alertinbox
/sap/bc/bsp/sap/alertinbox
/sap/bc/bsp/sap/alertsubscription
/sap/bc/bsp/sap/alertpersonalize
/sap/bc/bsp/sap/alertpersonalize_rules
24
End-To-End Monitoring: Configuration IV
Consistent content of the SLD
The Runtime Workbench as well as other services, i.e. the MDM, the directory cache
refresh, read component and addressing information from the SLD. There are two
complementary ways to provide the SLD with XI-specific content:
Manually
You define business systems by using the Business Landscape UI of the SLD.
Before that, the technical systems need to be described in the SLD.
Configure SLD bridges to have the technical systems register themselves

automatically with the SLD.
Automatically
XI components register themselves with the SLD as soon as they are started up.
This type of self-registration does not require SLD bridges.
25
End-To-End Monitoring: Prerequisites
Activate End to End Monitoring by setting respective configuration

parameter in SXMB_ADMIN
To active the collection of performance data needed for the monitoring this
parameter has to be set to “1”.
A “0” here will deactivate the collection of data for the End to End monitoring.
26
End-To-End Monitoring: Configuration I
Here you can see the status of

the monitoring.
monitoring as a sending or
Select component to be Select the monitoring level receiving party
monitored
After configuration, choose button „Save Configuration“ to activate the End To End
monitoring.
Currently when you save the new settings the old settings are deleted.
Before you can start to user the end to end monitoring you need to configure it. The changes you make will be
noted by the system, this information is the user and the time of the saving of the configuration change.
Therefore you first steps in the system need to be in the Configuration menu. Here you have to make a few
choices.
When you start the configuration screen all components that are registered in the SLD and associated with the
domain of the Integration Server are displayed. This means that any components that are “outside this
domain” can’t be monitored via the End to End monitoring.
Going from left to right:
1) In the display a list of all systems/components that are stored in the SLD are displayed. Here you can
activate the monitoring for a component. You also see on type of component and its name.
2) The monitoring level is a setting as to how much data is gathered for the particular component. There are
three levels (low , medium, high) of data collection. According to the component you choose to monitor the
amount of data can vary. Some component have multiple measuring points, others have two. So the amount
of data depends on how much data you care to have for your analysis.
3) The next choice you have to make is what “path” you wish to monitor. You can choose the incoming,
outgoing or both sorts of messages for that particular component. As not all components are both sending
and also receivers.
4) The last section depends on what components you have chosen to have monitored.
For ALE there are more entries that need to be done, in this case you have the choice to monitor the defined
ports of the ALE communication. If you leave this entry blank then by default the system will monitor all
appropriate dialog on the component.
5) When you save the settings the current status is that the old settings are overwritten and also the data
gathered is also deleted.
6) You also have the option to deactivate the Monitoring, this option lets you stop the End to End monitoring
completely. No data is gathered from the agents nor sent to the central End to End server and aggregated.
27
Possible Errors
If you get following error

No Processes defined for this Domain
Æ you need to first configure the end to end monitoring!
After trying to start the end to end monitoring you

get following error it is likely that you have not
started the SICF services.
28
Using the End to End Monitoring
29
End-To-End Monitoring – Initial Screen
To start the performance measuring using he End to End you need to first choose
“End to End Monitoring”.
If you have detailed information on the participating messages you wish to monitor
you can make this choice here. There is neither value help nor wildcard support so
you need the exact spelling of any object you wish to analyze.
If you wish to get a general overview then you can simply press Display. This will
give you the largest detail of information.
30
End-To-End Monitoring: Overview
The next display then has two sections. On the left hand side you can see the
detailed information and on the right you have a overall view of the landscape and
the processes that are sending and receiving the messages.
If you click on the checkbox “display only participating components” the display
gets rid of the non-participating components in the monitoring timeframe.
31
End-To-End Monitoring: left - Overview
This is the Monitoring Status: Here you can see the time of the last
configuration change and by whom it was done. Also you can do
some basic settings here.
The choices here are if you wish to use the process view or the
instance view and if you wish only see the components that
were involved in processing messages in the time frame
chosen.
This section lets us choose an analysis timeframe.
This is the “quick view” if you had problems with the message flow.
Here we have the tally of how many errors, open, successfully finished
and in total processed messages. In addition to that the time needed
to process is also displayed. (the average, maximum and minimum
values).
The choice here is to choose the number of messages you wish to

analyze in the display below it.
Here you can take a closer look at the instance list that is selected via
the statistics or an entry in the graphical overview.
32
End-To-End Monitoring: right - Overview
The right side of display shows us ALL

components that are defined in the configuration
of the End to End monitoring. Each box
represents a component.
Notice: that in the screen there is a red

component, this means that a error has
occurred in that component. This error then
warrants further investigation by us.
If you mark the checkbox “only display

components involved in the processing” the
displayed tree is reduced to those components
that actually processed messages in the
timeframe chosen. This simplifies the view
greatly.
33
End-To-End Monitoring: Settings - General
This displays when the monitoring was

started and who the last person was to
activate it.
This button lets you (de-)activate the
End to End – monitoring.
Here you can see when the last update of the

End to End data was done by the system. You
can also see when the next update is due and
what the rhythm for the updates is.
This button lets you start a data update

immediately.
The update rhythms you can choose are:

5 minuets
10 minuets
30 minuets
60 minuets
120 minuets
For the Update you have three possible status levels for the next update
the next date/time when the update is due.
or “overdue” , the job is scheduled but has not started as yet. As soon as it can start then it will.
or “turned off” or deactivated, there is no End to End monitoring activtiy.
34
End-To-End Monitoring: Settings - Details
Notice: To set any values in this panel you need to first disable
the monitoring in the General Screen. By deactivating the
monitoring you are not deleting any performance data gathered.
In this section you can change the timeframes when the

performance data is complied for the End to End display.
Here you can configure the number of Dialog-work

processes, that End to End uses for the aggregation of
the End to End data.
In this section you can define how long the End to End keeps
the data in the system, before it starts to “compress” it. After
the defined time the system starts the compression of the
data.
Under the header “Resource management” you can choose what level of resources usage you wish to
have for End to End.
If you have defined RFC-server groups then you can assign these RFC-servers to handle the processing.
By default it is to use all RFC-servers in the defined server group.
Also you can define how many dialog work processes are to used for the processing from each server in
the Servergroup. Per default 25% of all work processes (that can be used for RFC calls) from each server
is used.
The settings under the topic “orientation values” are more along the lines of suggested values. There
are currently no defined values. These values are used to define a few internal settings for the End
to End monitoring. Currently the suggestion is to leave the settings where they are.
Number of XI-Messages per day. This value is a estimation of how many messages you expect to have
travel through the XI server.
Average duration of a XI-message: This one is how long a message will probably stay in the XI-pipeline
on average, before it arrives at the target system.
And finally the maximal time that a message can take before the End to End considers it as being open.
As a message can take a long time to get to the target system. This values basically is used to define a
limit of how long End to End will wait for the “closing” of the message. If a message takes longer then this
values it is considered to stay open, and will not the set to finished.
The next set of settings are used for defining the reorganization of End to End data. In principle you
can make any choice you wish here. Keep in mind that the longer the retention period, the more
data is stored in the system. This has of course a direct effect on the End to End monitoring
performance.
35
End-To-End Monitoring: Settings - Error Status
Here you can see the detailed log.
The status gives you a rating in form the a light.
The Short text gives you a short explanation in regards to what happened.
This section tells you in which component is responsible.
This section then is the time when the problem occurred

Here you can manually set a message to done, it is then deleted fro this list.
36
End to End process viewing
37
Process view
The data flow is from top to bottom.

The data sources (senders) send the messages to the XI. There might be a number of machines in between
that also send or receive data.
In the end to end monitoring the XI system is always in the middle of the displayed landscape.
The bottom row then is the receiving systems.
Sending systems
XI system
Receiving systems
The process overview is the initial screen of the Process Monitoring and contains
the following important display functions:
Graphical display of the process flow across the components involved (for
example, XI message processing using a sending system, Integration Server and
target system)
Status display and error messages for the process flow
If an error has occurred in the monitored process during a transfer between
components, an error message is displayed, together with red status icons in the
process flow.
Display for how many process instances have run in total, and how many are
open, completed, or have errors. This gives you a quick overview of the process
status.
Selecting the number of open, incorrect or complete process instances displays a
list of the corresponding process instances. This gives you a quick overview of
process instances that have errors, for example.
38
Instance View
d view
aile
det
The instance view offers the following functions:

Detailed information about an instance of the process
This may be an instance that was selected from the instance list in the process
overview (such as one from the list of instances with errors), or it may also be the
instance that was displayed last, if the radio button Instance View was selected in
the process overview.
Graphical display of the process instance steps together with status icons
Clicking somewhere in an process instance step displays the attributes of the
process instance step. From this attribute display, you may be able to jump
directly to analysis and error correction tools.
As was the case for the process overview, you also have the option of jumping
directly to Further Settings
39
More Details via the magnifying glass
by pressing the +
The Icons are from top to bottom:

Number of instances
…that entered this step.
…that have a error.
…with no follow up step.
…that have processed correctly in this processing step.
With the help of the icons in a processing step you can see where there are
issues.
You then can click on the magnifying glass to get a more detailed view of the
processing step. Here you can decide at which step within that component you
need to do further checking.
If you click on a number in a component/step, you get the list of still available
instances contributing to this number.
40
Finding issues with End to End monitoring
If you detect errors using the End to End monitoring following

procedure is advised:
1) In the general overview you will notice a red process “box”. This
denotes an error situation within that section. Double click on the
“error flag”. On the left hand side of the display you will see a list
of the “errors” messages.
2) By choosing said message you will then lead to the instance

view. This focuses on the actual step in the overall flow.
41
Error tracking I
A number of components seem to have errors

instances, to start we choose the XI system.
After choosing the XI, we get a display of the

instances with errors within that process.
Choose a particular message that is in error
status and choose it.
42
Error tracking II
by choosi
ng the m
essage
detailed
view
By choosing the message with the error a new window is displayed on the right
hand side. it is the instance view for this process.
In this window you can again click on the step in which the error occurred.
43
Error tracking II - Attribute display
The following window contains the details about the message:

The XI-message number.
The location of the error and the error code.
plus additional information.
…
By clicking on the work icon another display is opened.
44
Error tracking III
In this display you pick the message you wish to analyze further, then click
display.
45
Error tracking IV
This last display then is close to the display generated by the sxmb_moni.
From this point on you can drive your error analysis as you wish.
46
End to End process viewing
47
How to define Performance Indicators
The problem we have in giving performance values (or suggestions) is that every
customer is different. They differ in:
number of documents
their size and complexity
mapping(s) used and their complexity
how the message is sent from one party to another
specific times needed to send and receive the messages.
and many more items
There is no easy way to suggest a general “good” value for all customers.
There are two ways to find your indicators:
1.During operations you will develop a certain number of values that you can use
as performance indicators.
2.Or your customers define a number of predefined Key Performance Indicators
(KPI).
Whatever form of definition you use, it has to be clear that all parties need to
agree to them and that they are in written form. A regular reporting on these should
also be defined.
48
starting the performance monitoring
To start the Performance monitoring use TA: SXMB_IFR a webpage is generated. There you
choose the Runtime workbench (RWB).
Then choose the item Performance Monitoring in the top row. Then you have choice of what
data source to use the End to End or the IS for the monitoring
49
difference between IS and PMI
The IS view displays the locally stored data for the specific
integration server chosen in the pull down window.
If you choose PMI, the data collected from the PMI server is
displayed according to your settings. You can also choose
other components within the landscape (as long as they are
known to the PMI ) and see their performance data.
Both IS and PMI use agents to collect the performance

data. The IS monitors the ABAP stack, where as the PMI
agent monitors the JAVA stack. These agents can be
located six time stamps, at various points in the processing
chain. When a message reaches an agent a timestamp is
written for it (time and location).
The IS writes up to the Adapter framework has two and
each adapter has it‘s one timestamp.
The PMI monitor evaluates the sending message (from the

sender to the receiver), a response message may not
noticed by the PMI agent. Whereas the agent for the IS will
log both messages. This results in slight discrepancies
between the counters/values displayed for both PMI & IS.
50
The Performance Monitor
1) There are 4 choices to display information for both IS and PMI:

Aggregated (Overview) Throughput Æ If you choose the aggregated Throughput a
checkbox called Consolidated data appears.
Single item Throughput
Aggregated (Overview) Detail view
Single item Detail view
2) The time span for the analysis, this also changes the aggregation choices for the display.
3) The component you wish to monitor.
4) Aggregation level, this is the timeframe for the following display. This is the processing interval for
the following display.
51
aggregated Overview
• The information displayed is aggregated according to your choice. According to

what timeframe you choose the aggregation time will differ.
• Consolidated data is data that has been „compressed“ to reduce the volume of
Performance data present in the system. This data is older than a predefined
threshold and is therefore „compressed“ and then deleted from the system. You
can access the last 4 weeks worth of data in a hourly format. The last 100 days
are kept in a daily format.
This „older data“ is not included in the standard data display and by activating this
you have a option to include more historical performance data in your analysis.
• When choosing the consolidated data option, the system combines the current
data and all the data which has been consolidated for this timeframe. Therefore
giving you a much greater range of values for analysis.
Column Meaning
Interval Start/End of Interval Start and end of the interval in question
Number Number of messages processed in this interval
Size Average size of the processed messages
Latency Average processing time in seconds
Rate Number of messages processed each hour
Component Component in which message processing took place
52
aggregated Overview 2
In the screen you have a number of indicators:
1) timeframe
2) number of messages
3) the average size of a message
4) and their processing time
This then gives you the processing rate, number of messages per
hour. A unexpected deviation from the standard value in the
processing rate can be seen as a potential issue.
When this happens, compare the average size of the documents and
their volume.
The processing rate can drop when:

there is a increase in either number of messages (at a certain time)
their size of the messages
or a complex mapping is needed for the messages
You then may need to implement further steps to resolve the issue. This depends on
your specific scenario as to what you need to do.
53
single Overview
By choosing a small enough timeframe you are able to find a message

which might have a problem. A message with a large processing time
is a good candidate for further analysis. The size of a message may or
may not play role, as complex mapping can be the cause for a high
time.
The information given is the same structure as the information in the
SXMB_MONI, but when you choose the End to End you also get
information on other components.
Column Meaning
Message ID ID of processed message
Size Size of processed
message
First and last time stamp Absolute: First and last time stamp of message processing in
absolute units.
(absolute and relative) Relative: Relative to the first time stamp of the first selected
message, in s.
Latency Processing time (that is, difference between last and first time stamp) in seconds
<Time stamp> A number of time stamps (differs according to the
type of processing) that each return a specific time of processing, relative, in seconds, to the first
timestamp.
54
aggregated Detail view
You are shown the summed performance sets of all messages that fit the chosen time. According to what
component you are viewing with the End to End you have different timestamps displayed in the display.
If you are accessing the ABAP stack then six timestamps (phases in the XI-pipeline) are available.
PLSRV_RECEIVER_DETERMINATION
PLSRV_INTERFACE_DETERMINATION
PLSRV_RECEIVER_MESSAGE_SPLIT
DB_SPLITTER_QUEUING
PLSRV_MAPPING_REQUEST
PLSRV_OUTBOUND_BINDING
For a component in the End to End two timestamps are available one for entry into the component and one when
leaving the component.
If the component is a adapter then there is one timestamp.
With the given information you can analyze a particular component and its processing speed or is not working
properly.
Column Meaning
Interval Start/End of Interval Start and end of the interval in question
Number Number of messages processed in this interval
Size Average size of the processed messages
Latency Average processing time in seconds
Rate Number of messages processed each hour
<Time stamp> Specific times of processing (with minimum and maximum values, if
selected)
55
aggregated Detail view
In this particular display you have to be very specific in regards to what

measurements you wish to have displayed. For this you need to use the expanded
search option.
When you have done this you need to key-in the Sender and Receiver information.
At this point is depends on what information you have and how distinctive it is.
Once you have entered the correct level of information you get the screen above.
56
Summary
Now you should be able to:
Know monitoring concepts in general
Configure and use the End to end monitoring
Perform monitoring
57

02 Monitoring Concepts PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

02 Monitoring Concepts PDF

Uploaded by

Copyright:

Available Formats

End Monitoring in Detail

Author: Offer Amram

After completing this session, you will be able to:

 Know monitoring concepts in general

 Configure and use the End to end monitoring

© SAP AG 2004, End to End Monitoring, Offer Amram / 2

SAP CRM SAP R/3

 Technical Process Monitoring Create Order

© SAP AG 2004, End to End Monitoring, Offer Amram / 4

 For ensuring availability, reliability and performance of IT Landscapes it is

Detection of error situations in a system

Detailed error analysis

SAP R/3 SAP CRM SAP CRM

© SAP AG 2004, End to End Monitoring, Offer Amram / 5

Customers need an infrastructure, which delivers

Notifies errors on components

 Real time monitoring for business critical processes

© SAP AG 2004, End to End Monitoring, Offer Amram / 6

Customers need an infrastructure, which delivers

Efficient monitoring and reporting of processes

Error analysis during development, testing and in productive

Measuring of process performance

Identifying bottlenecks within a process flow

Process based service level agreements

Process based accounting

© SAP AG 2004, End to End Monitoring, Offer Amram / 7

 Efficient monitoring and reporting of processes:

© SAP AG 2004, End to End Monitoring, Offer Amram / 8

Business Sales Order

Enter Sales Check Create Order Billing

© SAP AG 2004, End to End Monitoring, Offer Amram / 9

Process IDocs tRFC

© SAP AG 2004, End to End Monitoring, Offer Amram / 10

Focus on System Monitoring

Limited Process Monitoring

© SAP AG 2004, End to End Monitoring, Offer Amram / 11

System monitoring tools:

 CCMS monitoring objects

Business process monitoring tools

© SAP AG 2004, End to End Monitoring, Offer Amram / 12

Alert monitoring view

Where does this information come from? …..

… Information based on ALE Monitoring in CCMS

IDoc Overview (WE05)

List of IDocs in error state

Which outbound IDoc is related with which inbound IDoc?

© SAP AG 2004, End to End Monitoring, Offer Amram / 14

What has been the processing time of IDocs from end-to-end?

1) Select IDoc and find 2) Search statistic records

What is the average time required for processing an IDoc?

System monitoring tools

Business Process Monitoring in SAP Solution Manager

© SAP AG 2004, End to End Monitoring, Offer Amram / 16

Central monitoring of technical process

© SAP AG 2004, End to End Monitoring, Offer Amram / 17

© SAP AG 2004, End to End Monitoring, Offer Amram / 18

SAP Solution Manager

Business Sales Order

Enter Sales Check Create Order Billing

Process Monitoring Infrastructure

© SAP AG 2004, End to End Monitoring, Offer Amram / 19

The XI End to end monitoring uses this infrastructure to monitor itself.

© SAP AG 2004, End to End Monitoring, Offer Amram / 20

Know monitoring concepts in general

Configure and use the End to end monitoring

Technical Process Monitoring Create Order

For ensuring availability, reliability and performance of IT Landscapes it is

Customers need an infrastructure, which delivers

Notifies errors on components

Real time monitoring for business critical processes

Customers need an infrastructure, which delivers

Efficient monitoring and reporting of processes:

CCMS monitoring objects