BPM IFMon Capabilities

Monitoring Interfaces with Business
Process Monitoring
Keep Mission Critical Business Processes Running
Configure Interface
Monitoring in Business
Process Monitoring
As of SAP Solution Manager 7.1 SP05 and ST-A/PI 01P
2012 SAP AG. All rights reserved. 3 Customer
Configure Business Process & Interface Monitoring
The BPMon setup tool can be started from Business Process Operations work
center. Choose Setup Business Process Monitoring from the Common Tasks
section. This directly opens the setup tool in a WebGUI environment.
General Setup Procedure Load Monitoring Objects
Load the monitoring objects from the managed
system. Since two managed systems are involved in
the interface, you should load monitoring objects
from both the sending and the receiving system of
the interface.
General Setup Procedure Select Interface for Monitoring
In the navigation structure on the left-hand side
navigate to the business process you intend to
monitor and select the appropriate interface.
On the right-hand side you can add a monitoring
object for the selected interface using the Create
button. Two options exist: create the monitoring
object for the sending or the receiving Logical
Component.
General Setup Procedure Select Monitor
In the pop-up screen restrict the available monitors to
area Interfaces. Use the drop-down menu in field
Monitors to select the appropriate monitoring
object, and provide a speaking name.
Once created you can access the parameter
maintenance screen of the new monitoring object by
clicking its name in the main screen.
General Setup Procedure Select Key Figures and
Provide Filter Criteria
In tab Monitoring Configuration
of the maintenance screen you
have to provide filter criteria for
the specific monitoring object,
select the key figures you need,
and set the threshold values for
alerting per parameter set.
Each monitoring object has its
own set of filter parameters and
key figures.
General Setup Procedure Maintain Schedule and
Activate
In tab Monitoring Schedule of the
maintenance screen you have to provide
the scheduling information for the specific
monitoring object. You can choose
between a periodic schedule and fix start
and end times for the monitoring, and if
the data collection is to be executed in
dialog or in background.
Further settings can be made in the
additional tabs (like specifying alert
notifications in tab Notification).
When all relevant data is entered you
have to activate the monitoring by
pushing the buttons Generate and
Activate.
Re-Use of Interface Data in Business Process Monitoring
If a technical interface is assigned
to a business process interface it
is possible to load the attribute
values of the technical interface
into the BPMon setup tool to
configure monitoring objects.
In the parameter maintenance
screen you can use button Get
Default Values to load the
attribute data of the technical
interface into the corresponding
BPMon setup parameters.
Using the Get Default Values Button in BPMon
By clicking on button Get Default
Values all attribute values of the
chosen technical interface are mapped
into the BPMon setup parameters and
are henced used for monitoring.
If more than one technical interface is
assigned to the same business
process interface a selection screen is
shown first when pressing the Get
Default Values button. You can then
decide which of the technical
interfaces you like to map into the
corresponding monitoring object.
View Alerts in BPO Work Center
Once the monitoring is activated you can display the alerts in Business Process
Operations work centers Alert Inbox (transaction SOLMAN_WORKCENTER). All
monitoring objects available for your solution are listed together with alerting details.
View Alert History and Use Detail Display
For each monitoring object you can display the history of the previously created
alerts. Simply mark the line of the monitoring object you are interested in, and the
alert history is displayed at the bottom of the screen.
Button Detail Info enables you to jump to the managed system to view further
alerting details.
Possible Use-case Scenario in BPMon
SAP ERP - M60
Create Sales Order
(3)
Create Outbound
Delivery (6)
Post Goods Issue
(11)
Create Billing
Document (12)
Send Order
Confirmation (4)
SAP CRM - C70
Create Sales Order
(1)
EDI Subsystem - Z_EDI
Receive Order
Confirmation (5)
Create EDI Order (2)
SAP ERP Warehouse - M60
Create Outbound
Delivery (7)
Create Picking
Transfer Order (8)
Confirm Picking
Transfer Order (9)
Post Goods Issue
(10)
mBDocs Monitor on CRM
qRFC Monitor on CRM (qOUT for R3A* queues)
qRFC Monitor on ERP (qIN for CSA* queues)
tRFC Monitor for dest.
M60CLNT800
IDoc Monitor for Message Type
WHSORD
IDoc Monitor for DESADV
IDocs on WM
Workflow Monitor for
Delivery Creation
IDoc Monitor for
incoming
ORDERS IDocs
List of Available Interface Monitoring Objects
(as of ST-A/PI 01P)
IDoc Monitoring/ IDoc Reporting
BDoc Monitoring/ CRM Middeware Monitoring
Business Workflow Monitoring
RFC Availability Monitoring
tRFC Monitoring/ qRFC Monitoring/ bgRFC Monitoring
File Monitoring
SAP Batch Input Monitoring
ABAP Web Service Monitoring
SAP PI Message Monitoring
Further information on Business Process and Interface
Monitoring
Further Documentation available on SAP Service Marketplace, alias BPM
(www.service.sap.com/bpm), Media Library:
see especially Setup Guide Interface Monitoring
Available class room trainings (details at www.service.sap.com/education) :
SM300 Business Process Monitoring (5 days including certification)
E2E300 E2E Business Process Integration and Automation Management (5 days
including certification)
Best Practice document for Interface Recording to be found at SAP Service
Marketplace (www.service.sap.com/solutionmanagerbp):
Interface Documentation with SAP Solution Manager
ALE / IDoc Monitoring
ALE Processing IDoc Statuses
Receiver System (Inbound) Sender System (Outbound)
File tRFC
Work
Item
MC Record
Application
ALE layer +IDoc Basis
Message
Control
Application
ALE layer +IDoc Basis
01
25
26
30
02
03
39
12 41
50
64
61
60
66
62
53
51
54
52
Availabl e Key Figures for IDoc Monitoring
Monitoring Object / Key Figure Select Options
IDoc Monitoring
(error and backlog monitoring)
Delta monitor number of
suitable IDocs since the last data
collection
Total number monitor number
of suitable IDocs for the last x
days
On object l evel:
Direction
Port
Partner number
Partner type
Partner function
Message type
Basic type
Message code
Message function
On key figure level:
Status number(s)
Status message
qualifier
Status message ID
Status message number
Max. IDoc Age (in
hours)
Count Segment
Segment Field
Names with select
options for Field
Values
Header Field Names
with select options for
Field Values
Min. Status age (in
minutes)
Status Counter
Set-up Example Define Monitoring Object
In the parameter maintenance
screen first the filter criteria on the
header level have to be filled.
Parameters Direction and Max.
IDoc Age are mandatory.
The parameter values can be
filled in manually, or they can be
taken from the assigned technical
interface as maintained in
Solution Directory (Button Get
Default Values).
Set-up Example Selection Parameters for IDoc Contents
Two use-cases exist:
1) Parameter Field Name is filled only: Display all IDoc field contents of specified
field in Detail Display
2) Parameter Field Value is filled in addition: Data collection is restricted to the
specified field contents
Count Segment: Occurenceof selected segment (Example: Number of items in a
Delivery IDoc)
Field Name: Display all field contents of specified field (Example: Display all
partners of alerted IDocs)
Field Value: Restrict data collection on specified field content(s) (Example: Only 5
most important partners should be alerted)
Set-up Example Select Key Figures and Set Threshold
Values
There are 2 key figures available:
Delta Number Monitor: Evaluates the IDocs since the last data collector run
Total Number Monitor: Evaluates all IDocs in the system
Per key figure you can again define one or more parameter sets to facilitate
different alerting scenarios (e.g. to distinguish between intermediate and failed
IDocs). Per parameter set you the have to provide threshold values for alerting.
Set-up Example Define Parameter Set
For each parameter set you have to provide further filter criteria. In contradiction to
the filter criteria on header level which restrict the set of IDocs to be alerted based
on the control record and the data records of the IDoc, the values entered here are
used to filter out the IDocs based on their status records. Parameter Status
Number(s) is mandatory to fill.
Set-up Example Define Monitoring Schedule
In tab Monitoring Schedule
you have to define how often
alerts are going to be created
in the Alert Inbox in the BPO
work center.
Due to the size of the IDoc
tables in most customer
systems the IDoc monitoring
is performance critical. Thus,
IDoc data collection is always
executed via background job,
and it is triggered every 15
minutes independently of the
settings in the Monitoring
Schedule.
Use IDoc Monitoring in BPO Work Center
Once alerts are createdon the IDoc monitoringyou can viewthemin theAlert Inbox
in the BPO work center.
The Detail Info functionality for the IDoc Monitoring provides a list of all affected
IDocs, together with further context information. Two views exist:
Error View: Displays selected error information from the IDocs status records
Content View: Displays selected information on the IDocs payload
In addition, further actions can be started from the detail info screen, such as
displaying the IDoc in the standard transaction WE05, or reprocessing a failed IDoc.
See next slides for further information.
Detail Info Error View
Generic part:
IDoc number
Message Type
(Current) Status of IDoc on
database
Traffic Light
Age of current status
Error Resolution Time
Information on current status of IDoc:
Status Message Text
Status Message ID
Status Message Number
Detail Info Content View
Information on selected IDoc contents:
Number of segments as specifiedduringBPMon setup(indicatedin fieldCount
Segment)
Field Names andcorrespondingfieldvalues as specifiedduringBPMon setup
Detail Display Additional Features
Additional features:
All IDocs: Display the current status on the database for all IDocs that fit the
selectioncriteria
WE05 (Display IDocs): Call standard monitoring transaction WE05
Reprocess: Trigger reprocessingof IDocs via standardreport RBDPROCESS
WEINBQUEUE: Display qRFC inbound queue (for IDocs in status 75)
Start Queue: Trigger processing of qRFC inbound queue
Refresh Display
IDoc statistics: Statistical informationon displayedIDocs
Customizing Overview: Display BPMon configuration parameters
Back to overview
IDoc Reporting
Available Key Figures for IDoc Reporting
IDoc Reporting
Total number of IDocs created
Average time to process IDocs
Maximum time to process IDocs
Percentage of IDocs created
On object l evel:
Direction
Port
Partner number
Partner type
Partner function
Message type
Basic type
Initial Status number
Final Status number
Status message
qualifier
Status message ID
Message code
Message function
Selected day
Field Names with
select options for
Field Values
Status message
number
Status Counter
Relevant Status
Record
The configuration parameters are
basically the same as for the IDoc
Monitoring. Instead of setting a maximum
IDoc age you have to select whether data
is to be evaluated for the current or the
previous day (parameter Selected Day).
Set-up Example Define Key Figures
On key figure level you have to
define which IDoc statuses you
want to count (for key figures 01
and 04), or between which
statuses you want to measure the
processing time (for key figures
02 and 03).
IDoc Reporting: BW Enablement
Unlike the IDoc Monitoring monitoring object the IDoc Reporting does not offer
a detail information function.
Instead, the measured values of the key figures can be displayed in one of the
reporting tools BPMon offers (Business Process Analytics, Business Process
Operations Dashboards)
Following parameters are enabled for data aggregation:
Partner Number, Message Type, Status Number, Status Message ID, Status
Message Number
Sample use-cases:
report on the distribution of IDoc Status Numbers for all IDocs of Message Type
ORDERS sent by the same partner
aggregate the data by parameter Status Number only
Check which interfaces are affected by IDoc failures in inbound processing (IDocs
running in status 51)
aggregate the data by parameters Partner Number and Message Type, set
parameter Status Number to 51
IDoc Reporting: Setup for BW
Technically, if IDoc reporting data
should be made available for the
BPMon reporting tools, the
monitoring object has to be set up
at the Logical Component.
For each parameter the data is to
be aggregated the Group By flag
has to be set.
Display IDoc Data in BP Analytics and BPO Dashboards
Back to overview
BDoc Monitoring
SAP BDoc Monitoring Overview
Available Key Figures for BDoc Monitoring
BDoc Monitoring
Messages in error state:
Number of BDoc messages in error state
Age of oldest message in error state
Combination of Messages & Age in error state
Messages in intermediate state:
Number of BDoc messages in intermediate
state
Age of oldest message in intermediate state
Combination of Messages & Age in intermediate
state
On object l evel:
BDoc Type
Flow Context
Sender Site Name
Minimum Age (errors)
Minimum Age (intermediate)
Please note that the monitoring of the intermediate states does not include the
erroneous states as well, so you are advised to configure at least one key figure
from both status severity groups.
Set-up Example Define Monitoring Object and Select
Key Figures
Provide the filter values for the
monitoring object and select the
appropriate key figures.
Set-up Example Set Threshold Values Per Parameter Set
Per parameter set appropriate threshold values for alerting have to be set. No
further filter criteria can be maintained on key figure level.
BDoc Monitoring Detail Info
In order to see the alerted BDocs you can use button Detail info in BPMon Alert
Inbox. You are led to transaction SMW01 on the managed system which displays
the set of BDocs that suit the used selection criteria.
Back to overview
CRM Middleware Monitoring
CRM Middleware Monitoring Overview
The monitoring object "CRM Middleware Monitoring" checks five commonly used
transactions related to the area of mobile clients:
SMWMQUEUES: Queue Information for Mobile Client Sites
SMOHQUEUE: R&R-Queues
SMWP: MW Cockpit
SMWMFLOW: Message Flow Statistics
CMWQ: Mobile Client Import Failures
Available Key Figures for CRM Middleware Monitoring
CRM Middleware Monitoring
Mobile sites with overdue synchronization
Number of R&R Queues in status HOLD
Number of entries in R&R Queue
MW Cockpit
Number of BDoc messages processed
Average processing time for BDoc messages
Number of mobile sites with import failures
Direction
BDoc Type
Site range
Queue names
Older than x days
Maximum Age
Set-up Example Select Key Figures
On header evel of this
monitoring object no filter
values have to be provided.
Simply select the appropriate
key figures.
Set-up Example Set Threshold Values and Define
Parameter Sets
On key figure level filter values have to be provided, and the threshold values for
alerting have to be set per parameter set.
CRM Middl eware Monitoring Detail Info
In order to see the alerted workflows or any errors in the CRM Middleware
environment you can use button Detail info in BPMon Alert Inbox. You are led to
standard transactions of the CRM Middleware environment on the managed
system.
Back to overview
SAP Business Workflow
Monitoring
SAP Business Workflow Technology Overview
Workflows can be started
manually by an user or in
background triggered by
an event
They contain one or
several steps to be
conducted in background
or in dialog
Each step triggers a task
which refers to a method
of an object type in the
Business Object
Repository (BOR).
Availabl e Key Figures for Workflow Monitoring
Workflow Monitori ng SAP Basis rel ease dependant*
Number of work Items in status error
Number of work Items after system crash
Number of event linkages with status error
Canceled entries in workflow RFC destination
Status of workflow runtime environment
Task
Collector Mode
Workflow Monitoring general
Number of work Items in specific status
Number of events in backlog
Age of oldest incomplete work Item
Avg. age of incomplete work Item
Task/Workflow
Status
Agent assigned
Maximum age (in hours)
Object type
Event
(*Full availability of the functionality as of SAP_BASIS 6.20 SP65, 6.40 SP23, 7.0 SP17, 7.01
SP2 or SAP_BASIS 7.12)
Set-up Example Select Key Figures
On header evel of this
monitoring object no filter
values have to be provided.
Simply select the appropriate
key figures.
Note that the screenshot shows
the SAP Basis release-
dependent monitoring object,
offering all 9 available key
figures. Monitoring object
Workflow Monitoring general
only offers the first 5 key
figures.
Parameter Sets
Workflow Monitoring Detail Info
In order to see the alerted workflows or any errors in the workflow environment you
can use button Detail info in BPMon Alert Inbox. You are led to standard
transactions of the workflow environment on the managed system.
Back to overview
Availability of RFC
Connections
Remote Function Call (RFC) Principles
Remote call of a function module (RFC)
Call
Result
Calling
function ABC
in system XYZ
with parameters
1,2,3
System XYZ
Function ABC
RFC client RFC server
Processes
parameter values
1, 2, 3 and
returns results
How to Monitor RFC Calls: Error Logging
Errors have to be handled by the calling application for normal sRFC and aRFC
calls. These error situations can be monitored by BPMon usingcustomer exit
functionality. More advanced RFC technologies have their own error logging
mechanisms which are re-used by BPMon.
Sending System ReceivingSystem
Log Error
Send Data
Error Handling
Process Data
How to Moni tor RFC Calls: Heartbeat Monitoring
It canhappen that the connectionbetween the systems is unavailable. To verify this,
a PING-like mechanismcan be utilizedby BPMon: the RFC Availability Check.
Sending System ReceivingSystem
Log Error
Send Data
Error Handling
Process Data
Available Key Figures for RFC Availabilty Check
Evaluate RFC connection Monitoring
Availability of RFC connection
RFC connection
Max wait time in seconds
The monitoring object
has to be created for
the managed system
where the connection
is setup in SM59. All
connection types are
allowed.
Only one key figure is
available for which the
threshold values and
the filter values have to
be set.
No Detail Info
functionality exists for
this monitoring object.
Back to overview
tRFC Monitoring
tRFC Technology Overview
Receiver XYR Sender XYS
Call Function 'F1'
IN BACKGROUNDTASK
DESTINATION XYR
Call Function 'F2'

IN BACKGROUNDTASK
DESTINATION XYR
COMMIT WORK.
LUW1
LUW1
LUW2
ARFCSSTATE
qRFC Scheduler
ARFCRSTATE
LUW1 LUW1
Execute
Call Function 'F1'
IN BACKGROUNDTASK
DESTINATION XYR
Call Function 'F2'

IN BACKGROUNDTASK
DESTINATION XYR
COMMIT WORK.
ARFCSDATA
Available Key Figures for tRFC Monitoring
tRFC Monitoring
Entri es in cri tical state:
Number of tRFC entries in critical state
Age of oldest entry in critical state
Combination of Entries & Age in critical
state
Entri es in i ntermedi ate state:
Number of tRFC entries in interim state
Age of oldest entry in interim state
Combination of Entries & Age in interim
state
On object l evel
Client
RFC destination
Function module
User name
Minimum Age (critical)
Minimum Age (interim)
Maximum Age (days)
Considered statuses:
Critical: ANORETRY, ARETRY, CPICERR,
RETRY, SYSFAIL, VBERROR
Interim: AFINISH, CONFAIL, DEBUG,
EXECUTED, MAILED, READ, RECORDED,
SENDED, SYSLOAD, VBRECORD, VXRECORD
Please note that the interim states are not included in the monitoring of critical states. So you
are advised to setup at least one key figure for both critical and interim states, typically with
different thresholds.
Key Figures
Per parameter set appropriate threshold values for alerting have to be set. Some
key figures provide a complex alerting rating strategy, using two pairs of threshold
values (for age and for number) to calculate the rating of the alert.
No further filter criteria can be maintained on key figure level.
tRFC Monitoring Detail Info
In order to see the alerted tRFC entries you can use button Detail info in BPMon
Alert Inbox. You are led to standard transaction SM58 on the managed system.
Back to overview
qRFC Monitoring
qRFC Technology Overview
qRFC allows serialization of tRFC LUWs according to business logic
Data can be queued on sender and receiver side
LUWs are added at the end of the queue in the sequence of creation.
LUW is processed only if it is in first place. If the first queue entry stops the whole
queue is stopped.
Sender Receiver
Outbound Queue(s) Inbound Queue(s)
tRFC LUWs
tRFC LUWs
qRFC qRFC
tRFC LUWs
tRFC LUWs
Availabl e Key Figures for qRFC Monitoring
qRFC Monitoring
Status (error) monitori ng
Number of entries with critical status in group
Age of oldest critical status in group
Combination of Entries and Age in critical state
Number of entries with interim status in group
Age of oldest interim status in group
Combination of Entries and Age in interim state
Backlog monitoring
Number of individual queues in group
Total number of entries in all queues of group
Average number of entries per queue in group
Maximum number of entries per queue in group
Age of oldest entry in group
Combination of Total entries and Oldest age
On object l evel:
qRFC direction
RFC destination
Queue group
Command string of SMD qRFC backlog
coll.
Command string of SMD qRFC status coll.
Considered statuses:
Inbound:
ANORETRY, SYSFAIL, ARETRY,
CPICERR, MODIFY, NOEXEC, RETRY,
RUNNING, STOP, WAITING, WAITSTOP
Outbound:
ANORETRY, SYSFAIL, VBERROR,
ARTRY, CPICERR, EXECUTED, MODIFY,
NOSENDS, RETRY, RUNNING, STOP,
SYSLOAD, WAITING, WAITSTOP,
WAITUPDA
Key Figures
The key figures are divided into
two sets: Backlog and status
(error) key figures.
Per parameter set appropriate threshold values for alerting have to be set. Some
key figures provide a complex alerting rating strategy, using two pairs of threshold
values (for age and for number) to calculate the rating of the alert.
qRFC Monitoring Detail Info
In order to see the alerted qRFC entries you can use button Detail info in BPMon
Alert Inbox. Depending on the monitored direction you are led to standard
transactions SMQ1 (outbound qRFC) and SMQ2 (inbound qRFC), respectively, on
the managed system.
Back to overview
bgRFC Monitoring
Background RFC (bgRFC) Overview
bgRFC is a superordinateterm for the new version of tRFC and qRFC.
The background RFC (bgRFC) is offered as a replacement for the classic tRFC and
qRFC.
A parallel run of classic tRFC/qRFC and bgRFC is possible.
It is available with SAP NetWeaver 2007 (SAP Basis 7.10).
The background RFC works on the basis of units and performs better
compared to the classic tRFC and qRFC versions.
The bgRFC is based on a scheduler-driven queueing framework. This means
that remote function calls are recorded, and execution takes place at a later point
in time, which is controlled automatically by a scheduler process. Several
schedulers can be started to process bgRFC units.
bgRFC Scenarios
Outbound
Scenario
Outbound -
Inbound
Scenario
Inbound
Scenario
Depending on the type of
scenario either Outbound
or Inbound Scheduler
controls the bgRFC
processing
Available Key Figures for bgRFC Monitoring
bgRFC Monitoring
Backlog monitoring
Number of individual queues/dest.
Total Number of units in all queues/dest.
Age of oldest unit
Status (error) monitori ng
Number of erroneous queues/dest.
Total number of erroneous units
Age of oldest unit in error state
Number of locked queues/destinations
Total number of locked units
Age of oldest unit with a lock
On object l evel
Direction
bgRFC Type (QoS)
Destination
Queue Name
User Name
Program Name
Transaction Code
Key Figures
The key figures are divided into
two sets: Backlog and status
(error) key figures.
Per parameter set appropriate threshold values for alerting have to be set.
bgRFC Monitoring Detail Info
In order to see the alerted bgRFC entries you can use button Detail info in BPMon
Alert Inbox. Depending on the monitored direction you are led to standard
transaction SBGRFCCONF on the managed system.
Back to overview
File Monitoring
Available Monitoring Functionalities for File Monitoring
Two ways exist to integrate File Monitoring into Business Process Monitoring:
Use the Application Monitor File Monitoring to check files in the file system of
ABAP-based components
Use the SAPCCMSR agent to monitor non-ABAP applications or external
components
If possible to use, the Application Monitor-based version is the recommended
option.
File Monitoring via Application Monitor Overview
Managed System
ST-A/PI
File System (AL11)
Soluti on Manager
Alert Inbox
BPMon Framework
Store incoming
alerts
Application writes
flat or XML files
Run data collector
and build results
Display file
contents
Display due alerts
Call Detail Info
Available Key Figures for File Monitoring (Application
Monitor)
File Monitoring via Application Monitor
Creation time of file
File size (in kB)
File age (in minutes)
Number of files
Number of lines in file
Number of patterns nonXML
Value nonXML
Pattern XML
Value XML
On object l evel:
File path
File name
Pattern
User (File Creator)
Search pattern
Start Pattern
Value after m char.
Value length
Aggregation
Parent tag
Child tag
Pattern is tag name
XML tag name
XML parent tag
Key Figures
Parameter Set
Some key figures allow to query the content of the file (both flat or XML file type) for
certain patterns which might indicate an error situation.
File Monitoring (Application Monitor) Detail Info
In order to see the erroneous files you can use button Detail info in BPMon Alert
Inbox. A list is displayed showing all relevant files.
Available Key Figures for File Monitoring (via CCMS
Agent)
File Monitoring with CCMS agent
File existence (at a certain time)
File age (in min)
File size (in kB)
Count lines in file
Alert on a specified pattern/string
Select options:
File name
Path
Files to be ignored,
Agent scheduling (specified day and time,
specified time-window)
Note that the SAPCCMSR agent is replaced by SAPSTARTSRV agent as of SAP
Netweaver release 7.0 EhP 2. Links on how to install and configure the
SAPSTARTSRV agent can be found in Setup Guide Interface Monitoring.
File Monitoring Using CCMS Agent Overview
The SAPCCMSR agent is an executable that is installed on the managed system
and reads the file content and its metadata for alerting purpose. The data is
replicated into CCMS and can then be included into Business Process Monitoring
session of SAP Solution Manager.
Managed System (non-SAP)
SAPCCMSR
File System
Soluti on Manager
BPMon Framework /
Alert Inbox
CCMS
Create alerting
nodes in CCMS
Application writes flat
files
Run agent periodically
Send results to
registered SAP system
Pick up CCMS
content
Display due alerts
Setup of File Monitoring via SAPCCMSR Agent 1/2
1) Install the SAPCCMSR agent on your managed system. Follow the
installation guide for detailed instruction.
2) Customize the configuration files of the agent. Configuration file sapccmsr.ini
contains the paths to the single configuration files.
Setup of File Monitoring via SAPCCMSR Agent 2/2
3) Adjust the threshold values in the newly created MTEs in CCMS via push-
button Properties.
4) Include the MTEs into your Business Process Monitoring Session by selecting
CCMS Monitor as monitoring type.
Back to overview
SAP Batch Input Monitoring
SAP Batch Input Overview
Data Collector
Sequential File
Master data
Queue Dataset
Database
Master data
Batch Input Program
Function Batch Input
Available Key Figures for SAP Batch Input Monitoring
Batch Input Monitoring
Number of queues in specified status(es)
Number of errors per session
Number of transactions processed per session
Number of transactions in specified status(es)
J ob cancellation
On object l evel:
Session name
Creating program
Created by
Status(es)
Key Figures
Parameter Sets
Batch Input Monitoring Detail Info
In order to see the alerted Batch Input session entries you can use button Detail
info in BPMon Alert Inbox. You are led to standard transaction SM35 on the
managed system.
Back to overview
ABAP WebService
Monitoring
ABAP WebService Monitoring Overview
Managed System
Data Collector
(/SSA/IM_DC_IMSRT001)
Soluti on Manager
Alert Inbox
BPMon Framework
Configure ABAP
WS monitoring
Determine required time
frame
Call ABAP SRT API
Receive list of failed calls
incl transaction GUIDs
Display due alerts
Call Detail Info Create alert records
Call data collector
CL_SOAP_UTIL_DB
=>LOG_GET_DATA
DB
Store
GUIDs
Available Key Figures for ABAP WebService Monitoring
ABAP WebService Monitori ng
Delta (evaluates all WebService calls since the
last data collection)
Total (evaluates all WebService calls for the
specified days in the past)
On object l evel:
Proxy for WebService
Port
Days in the past
Key Figures
Provide the filter values for the monitoring object and select the appropriate key
figures. Both key figures count the number of failed WebService calls, either the
total amount (key figure Total), or since the last data collection (key figure Delta).
Per parameter set appropriate threshold values for alerting have to be set.
ABAP WebService Monitoring Detail Info
In order to see the alerted Batch Input session entries you can use button Detail
info in BPMon Alert Inbox. This open report SRT_UTIL_LOG on the managed
system.
Back to overview
Possible PI Integration Scenarios
Receiver System(s)
Integration Server
Sender System(s)
DB
... and more
File /
ftp
server
RFC
server
Web
Service
HTTP
server
EDI
system
DB
... and more
File /
ftp
server
RFC
server
Web
Service
HTTP
server
EDI
system
IDoc Sender
IDoc
Receiver
J 2EE Adapter Engine
PI Integration Engine
ABAP Proxy
Business Process Engine
ABAP Proxy
Components Included into Business Process Monitoring
With Business Process Monitoring it is possible to monitor specific messages on the
Integration Server running into an error status (messages of a certain type,
exchanged between a certain sender and a certain receiver combination). However,
failures in the Business Process Engine can not be detected with BPMon.
Integration Server
PI Integration Engine
ABAP Proxy
Business Process Engine
ABAP Proxy
Monitoring possible with
Business Process
Monitoring
No Monitoring possible
with Business Process
Monitoring
Comparison of Available Monitoring Capabilities
Method Advantages / Disadvantages Use-cases
Integration of
Message-based
Alerting
+ All components (ABAP- and J AVA-
based) can be monitored
- Many setup steps in different
components
- Only summary alerts
- No detail display
Easy to use if Message-based
Alerting already set up on PI
If system prerequisites not yet
fulfilled for BPMonApplication
Monitors
ABAP stack
Application
Monitor
+ Only BPMon framework used
+ Detail display available
Only Integration Engine can be
monitored
Purely ABAP-based scenarios (no
Adapter Engine involved)
Monitoring of Local Integration
Engines
ABAP & JAVA
stack Application
Monitor
+ Only BPMon framework used
+ Detail display available
+ Covers Integration Engine and
Adapter Engine(s)
- Time-Bucket based
- J AVA API is based on message
creation time difficult
interpretation of the detail display
Recommended Monitoring Object
if all system prerequisites are
fulfilled
ABAP and JAVA Stack
PI Message Monitoring (ABAP & JAVA Stack) Overview
Set up a master data collector which retrieves aggregated message data from the
managed PI system
Set up a dependent data collector which builds the alerts for each interface
separately using the aggregated message data
Managed System (PI)
Runtime Workbench (Message Display
Tool) / SXI_MONITOR
PI Framework
Soluti on Manager
Dependent Data Collector
Master Data Collector
Evaluate Data per
Time Bucket
Collect Data
Display alerted
messages
Evaluate result
when alert is due
Display alerts / pro-
active alerting
Aggregate data and
store it into time buckets
Store result into ST-
A/PI cluster table
Available Key Figures for PI Message Monitoring (ABAP
and JAVA Stack)
Master Collector for PI incl . JAVA
Selection of Time Bucket
Time Bucket (available time buckets: Current
Hour, Last Hour, Current +Last Hour, Today,
Yesterday, Current Week, Last 7 days
Dependent Collector for PI incl. JAVA
Errors
Intermediate
Cancelled
On object l evel:
Time Bucket
Logical Port to Adapter Engine
Sender Party
Sender Service
Sender IF Namespace
Sender IF Name
Receiver Party
Receiver Service
Receiver IF Name
URL to Message Display Tool
Aggregation
Set-up Example Define Master Collector
First the so-called master collector has to be set up at the Logical Component of the
managed (PI) system. The only setting which takes place here is the selection of
the Time Bucket.
Set-up Example Define Dependent Collector and Select
Key Figures
Next the so-called
dependent collector has to
be configured at the
business process interface.
Provide the PI interface
parameters, the relevant
time bucket and the name
of the Logical Port.
Select the appropriate key
figures.
Parameter Set
Set-up Example Create Logical Port
In order to get alerting data
from PI Adapter Engine
(J AVA stack) a Logical Port
has to be created in SAP
Solution Managers
SOAMANAGER as an
instance of consumer proxy
CO_DSWP_BPM_PROFILE
_PROCESSOR.
PI Message Monitoring Detail Info
In order to see the alerted PI messages you can use button Detail info in BPMon
Alert Inbox. First an overview screen opens showing the affected PI messages and
their current status. From there you can jump directly into the corresponding
standard monitoring tools (transaction SXI_MONITOR for ABAP stack, Message
Display Tool for J AVA stack).
ABAP Stack Only
Available Key Figures for PI Message Monitoring (ABAP
Stack)
PI Message Monitori ng
Delta Message Monitoring
Total Message Monitoring
On object l evel:
Sender Communication Party
Sender Service
Sender Interface Namespace
Sender Interface Name
Receiver Communication Party
Receiver Service
Receiver Interface Namespace
Receiver Interface Name
Number of messages
Status Group or Status
Number of days (initial)
Key Figures
Provide the filter values
for the monitoring
object and select the
Set-up Example Set Threhold Values and Define
Parameter Sets
PI Message Monitoring (ABAP Stack) Detail Info
In order to see the alerted PI messages you can use button Detail info in BPMon
Alert Inbox. You are led to standard transaction SXI_MONITOR on the managed
system.
Re-use of PI Message-
Based Alerting
Integration of Message-based Alerting into SAP Solution
Manager
SAP XI Engine
SAP Solution Manager
Category 1
Category 2
Category xy
ALM
Inbox
CCMS
Runtime
Workbench
Process
step 1
Alert 1
Alert 2
...
Alert n
Rule 1 Rule 2 Rule xy
...
Process
step 2
Process
step 3
Process
step xy
Category 1 =2
Category 2 =12
...
Category xy =5
Alert Categories
Assign Rules
Alert Frame-
work (ALM)
...
J ob
Available Key Figures for PI Message Monitoring (via
Message-Based Alerting)
SAP XI/PI Monitoring
Integration of the Message-Based Alerting
/ error monitoring on adapter
framework(s) and integration engine
On SAP XI/PI per rule:
Sender Party
Sender Service
Sender interface
Sender Namespace
Receiver party
Receiver Service
Receiver Interface
Receiver Namespace
On SAP Solution Manager per alert
category:
Threshold values for the number of alerts
Setup Steps for Message-based Alerting
The following steps need to be performed for setting up Message-based Alerting on
the PI system:
Create one or more alert categories in transaction /nALRTCATDEF
Create alert rules in tab Alert Configuration of Runtime Workbench for the
different interfaces to be monitored
Assign the alert rules to previously created alert categories
Enable the transfer of alerting data to PIs CCMS (one MTE per alert category)
On SAP Solution Manager side, the content of the MTEs can be included in BPMon
using the Other CCMS Monitoring functionality.
Back to overview
Thank You!
Contact information:
BPI&AM, Business Process Integration
No part of this publication may be reproduced or transmitted in any form or for any
purpose without the express permission of SAP AG. The information contained
herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain
proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of
Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5,
System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries,
zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390
Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6,
POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF,
Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere,
Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM
Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other
countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or
registered trademarks of Adobe Systems Incorporated in the United States and/or
other countries.
Oracle and J ava are registered trademarks of Oracle and/or its affiliates.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and
MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C
,
World Wide Web Consortium, Massachusetts Institute of Technology.
2012 SAP AG. All rights reserved.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects
Explorer, StreamWork, and other SAP products and services mentioned herein as
well as their respective logos are trademarks or registered trademarks of SAP AG
in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal
Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business
Objects products and services mentioned herein as well as their respective logos
are trademarks or registered trademarks of Business Objects Software Ltd.
Business Objects is an
SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other
Sybase products and services mentioned herein as well as their respective logos
are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP
company.
All other product and service names mentioned are the trademarks of their
respective companies. Data contained in this document serves informational
purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. No part of this document
may be reproduced, copied, or transmitted in any form or for any purpose without
the express prior written permission of SAP AG.
2012 SAP AG. Alle Rechte vorbehalten.
Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind,
zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche
schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation
enthaltene Informationen knnen ohne vorherige Ankndigung gendert werden.
Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte
knnen Softwarekomponenten auch anderer Softwarehersteller enthalten.
Microsoft, Windows, Excel, Outlook, und PowerPoint sind eingetragene Marken
der Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5,
System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries,
zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390
Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6,
POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,
BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF,
Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere,
Netfinity, Tivoli und Informix sind Marken oder eingetragene Marken der IBM
Corporation.
Linux ist eine eingetragene Marke von Linus Torvalds in den USA und anderen
Lndern.
Adobe, das Adobe-Logo, Acrobat, PostScript und Reader sind Marken oder
eingetragene Marken von Adobe Systems Incorporated in den USA und/oder
anderen Lndern.
Oracle und J ava sind eingetragene Marken von Oracle und/oder ihrer
Tochtergesellschaften.
UNIX, X/Open, OSF/1 und Motif sind eingetragene Marken der Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame und
MultiWin sind Marken oder eingetragene Marken von Citrix Systems, Inc.
HTML, XML, XHTML und W3C sind Marken oder eingetragene Marken des
W3C
, World Wide Web Consortium, Massachusetts Institute of Technology.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects
Explorer, StreamWork und weitere im Text erwhnte SAP-Produkte und -
Dienstleistungen sowie die entsprechenden Logos sind Marken oder eingetragene
Marken der SAP AG in Deutschland und anderen Lndern.
Business Objects und das Business-Objects-Logo, BusinessObjects, Crystal
Reports, Crystal Decisions, Web Intelligence, Xcelsius und andere im Text
erwhnte Business-Objects-Produkte und Dienstleistungen sowie die
entsprechenden Logos sind Marken oder eingetragene Marken der Business
Objects Software Ltd. Business Objects ist ein Unternehmen der SAP AG.
Sybase und Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere und
weitere im Text erwhnte Sybase-Produkte und -Dienstleistungen sowie die
entsprechenden Logos sind Marken oder eingetragene Marken der Sybase Inc.
Sybase ist ein Unternehmen der SAP AG.
Alle anderen Namen von Produkten und Dienstleistungen sind Marken der
jeweiligen Firmen. Die Angaben im Text sind unverbindlich und dienen lediglich zu
Informationszwecken. Produkte knnen lnderspezifische Unterschiede
aufweisen.
Die in dieser Publikation enthaltene Information ist Eigentum der SAP. Weitergabe
und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem
Zweck und in welcher Form auch immer, nur mit ausdrcklicher schriftlicher
Genehmigung durch SAP AG gestattet.

BPM IFMon Capabilities

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BPM IFMon Capabilities

Hochgeladen von

Copyright:

Verfügbare Formate

Monitoring Interfaces with Business

Call Function 'F2'

Call Function 'F2'

, World Wide Web Consortium, Massachusetts Institute of Technology.

Das könnte Ihnen auch gefallen