PI Monitoring PDF

Session ID: BPI208
Process Integration Monitoring
Prasad illapani, SAP Labs, LLC

Andreas Stolz, SAP AG
Learning Objectives
As a result of this workshop, you will

be able to:
Utilize the CCMS Alert Monitor for Process Integration
Make use of the SAP Alert Framework for PI
Configure and use the PIs Message Performance Measurement
Use TRex for Message Search
SAP AG 2005, SAP TechEd 05 / BPI208 / 3
Motivation
Monitoring is a crucial part of an Operation Concept
Monitoring should cover
Availability
of your Landscape Components

Alert error situations
The following Monitoring Tools are available for the Exchange

Infrastructure 3.0
CCMS
Monitoring
Alert Framework
Runtime Workbench
Process Integration and CCMS

Process Integration and Alert Framework
Additional Techniques
Overview
SAP WebAS Java CCMS Configuration
CCMS Configuration for Process Integration
GRMG Availability Monitoring
XI Architecture Overview
XI All-in One Server
Central Monitoring
Integration Server
Integration
Directory
&
Integration
Repository
Business Process Engine
Integration Engine
System
Landscape
Directory
Adapter Engine
XI
RosettaNet,
Adapters + Connectivity
Protocol
Local
Integration Engine
IDocs
RFCs
Proxy Runtime
Proxy generation
RFC/IDoc
metadata import
Proxy
SAP
Web AS 6.20
SAP
System
File
DB
JMS
3rd Party
Apps
Apps of
Business
Partner
XI
Protocol
Partner
Connectivity
Kit
Apps of
(small)
Business
Partner
XI 3.0 Components in SAP Web AS 6.40

HTTP(s)
ICM
HTTP(s)
Central Monitoring
J2EE
ABAP
Integration Builder
(IR, ID)
Business Process
Engine
XI Tools
Runtime Workbench
JRFC
Mapping runtime
Integration Engine
Adapter Engine
SLD
OpenSQL
for Java
OpenSQL
for ABAP
Central Monitoring
Runtime
Workbench
Message
Monitoring
PMI
Component
Monitoring
CCMS
Performance
Analysis
Message Alerting
System
Landscape
Directory
Alerting Framework
Integration Server
(SAP Web AS 6.40)
Business Process Engine
Integration Engine
Adapter Engine
SAP Application
SAP Web AS 6.40
using XI proxies
(local)
Adapter
Engine
J2SE
Adapter
Engine
CEN Central Monitoring System

For each remote system, define
2 RFC destinations in
Transaction SM59:
for collecting data
for executing analysis methods.
To register a remote system,

execute Transaction RZ21,
select Technical Infrastructure
Configure Central System
Create Entry for Remote
System.
Overview
J2EE Specific CCMS Configuration

In Transaction RZ21 create the CSMREG User and the Start File
CMSCONF for the CCMS Agent Installation.
Register CCMS Agent

Using the Visual
Administrator register
the CCMS agent at the
resp. Abap Stack.
Select Dispatcher
Services Monitoring.
On the CCMS Agent
Configuration Tab enter
the Local
Administrators and
CSMREGs password.
Verify CCMSR Agent Registration and Status

Verify that the System Group
J2EE_Systems is created and
the actual J2EE System is
added.
Transaction RZ21, Menu
Technical Infrastructure
Configure Central System
Maintain System Groups
Verify that the Agents Status

is Online.
Transaction RZ21, Select
Display Overview for Agents
for Local System.
J2EE Monitoring Template
Overview
Activation of CCMS Monitoring
Activate CCMS Monitoring by

setting respective configuration
parameter in Transaction
SXMB_ADM
Change the value for Parameter

CCMS_MONITORING to 1 in the
Specific Configuration
CCMS System Group Maintenance with TC RZ21

Create system group ExchangeInfrastructure_Systems in TC
RZ21, Technical Infrastructure Configure Central System
Maintain System Groups
Create System
Group
Add Systems
Activation of qRFC - Prerequisites

Activate qRFC
monitoring.
In TC RZ21, select
Technical Infrastructure
Local Method
Execution Activate
Background
Dispatching.
Adapter Engine
Activate forwarding of
Adapter Framework
alerts to the CCMS
Alert Monitor via the
SAPCCMSR agent.
In the Visual
Administator select
Server Services
SAP XI AF Core.
On the Properties Tab
enter true as the value
for parameter
CCMSEnabled.
XI Monitoring Template
Access PIs CCMS
Monitoring template by
running either TC RZ20
or TC S_B6A_52000011
in folder Exchange
Infrastructure:
Monitoring of personal
user menu.
Overview
GRMG (Generic Request and Message Generator) Framework
(An example of GRMG scenario)
Activation of heartbeat monitoring- Prerequisites

To activate the
heartbeat monitoring
for Java components,
configure the socalled GRMG
customizing file.
For further
information please
refer to SAP Note:
634771, which
includes the PI
specific GRMG
customizing template.
GRMG Configuration file upload - Prerequisites

To upload the GRMG configuration file, execute TC: GRMG
Customizing GRMG Scenarios

To monitor the availability of an instrumented application with
GRMG, you must first customize and start the corresponding GRMG
scenarios by using TC: GRMG
Adjusting Frequency for individual Scenarios

By default, GRMG availability monitoring is performed every ten minutes for
all monitored scenarios, you can change this by using TC: RZ21
XI CCMS Heartbeats
Demo
Demo

PI and Alert Framework - Configuration

Display Alert Framework Alerts in CCMS
Alert Framework (ALM) and PI

Using the Alert Framework PI can generate Alerts for specific
Sender / Receiver / Interface combinations (Alert Rules).
Different contact groups can be alerted based on Alert
Categories. Alert Rules are assigned to Alert Categories.
The Alert Framework is a standard NetWeaver functionality.
Alerts can be delivered using several channels, like Email, SMS,
Pager (SAPConnect).
As a prerequisite End-to-End Monitoring (Process Monitoring
Infrastructure PMI) must be configured
Until
NW 04 SP 13 including, from SP 14 on the Alert generation does

not depend on PMI anymore
Activate Required ICF Services

Take care that the ITS
Plugin, the ALM related ICF
Services, and required ICF
Services are activated.
Start Report
RSXMB_ACTIVATE_ICF_SER
VICES in TC SE38. Refer to
SAP Note: 736312.
End-to-End Monitoring Configuration

In the Runtime Workbench
select Configuration. For
generating alerts set the
monitoring level to at least
medium and save the entries.
In the End-to-End Monitoring
section press button Further
Settings, set the job
frequency, and activate the
monitoring.
Verify that a background job
with a cryptic name is
created in TC SM37. The job
executes the Abap Report
SPI_PS_ASSEMBLE_DSP.
Report SXMSALERT_PROCESS_DATA_GET
The Report SXMSALERT_
PROCESS_DATA_GET reads
the Alerts from the
assembled PMI data and
reports them using the Alert
Framework.
Schedule the Report as a
periodic background job in
TC SM36.
Align the job period with the
End-to-End Monitoring job
period.
Alert Categories I
Alert Categories are
container for some kind of
alerts. Additional information
like alert texts and
subsequent activities as well
as recipient lists are
maintained per Alert
Category.
In the Runtime Workbench in
section Alert Configuration
press the button Create Alert
Category.
On the following screen
maintain an Alert Category.
Alert Categories II
Container Elements for various Message Header information are
available for PI Alerts. These Container Elements are filled at
runtime with Message specific information and are used within
the Alerts short and long text, e.g.
Container
Element SXMS_MSG_GUID returns the Message ID

Container Element SXMS_FROM_INTERFACE returns the Sender
Interface
Subsequent Activities for PI Alerts by default contain links for

the resp. message to the
Message
Monitoring
End-to-End Monitoring
Recipients could be identified

as
Fixed Users
via User Roles
via Self-Subscription based on User Roles
Alert Rules
Alert Rules define the error
situation which raises a
specific alert. One Alert
Category can contain one or
many Alert Rules.
In the Runtime Workbench in
section Alert Configuration
select a Alert Category.
Define an Alert Rule and add
it to the Alert Category.
Alert Subscription and Alert Inbox
PI and Alert Framework - Configuration

Display Alert Framework Alerts in CCMS
Extend the PI-ALM Background Job

Extend the Background
Job SXMSALERT_
PROCESS_DATA_GET
In TC SM37 change the
Job SXMSALERT_
PROCESS_DATA_GET
and add the ABAP
report SXMSALERT_
ACTIVE_ALERTS to the
Jobs Step List.
See also SAP Note:
824039.
Extend the PI Monitor

Extend the PI Monitor.
In TC RZ20 activate the
Maintenance functions
and select the PI Monitor.
On the following screen
add a rule based monitor
to the PI Monitor.
Specify CCMS_GET_
MTE_BY_CLASS as rule,
ExchangeInfrastructure_
Systems as R3System,
SXI_RWBAlerts as
MTEClass.
Demo
Demo

PI Performance Measurement
CCMS Performance Alert
TRex Message Search
PI Performance Analysis
By default only a limited set of performance data is stored
For collecting more detailed data in the Integration Engine
Increase
the MEASUREMENT_LEVEL
Store the Performance Header in a separate table
Two background jobs must be scheduled to aggregate and
reorganize the performance data
PMI data could be used for Performance Analysis, too

Backgound
jobs must be scheduled to read the Performance Data

from PMI and aggregate it into the performance database
Aggregated and Detailed Performance Data can be accessed via

the Runtime Workbench
Configure Integration Engine

The Integration Engine
Configuration Parameter
MEASUREMENT_LEVEL and
MEASUREMENT_PERSIST
determine the Integration
Engines Performance
Measurement behaviour.
In TC SXMB_ADM change
the specific configuration.
Job Scheduling
SAP_XMB_PERF_AGGREGATE (SXMS_PF_AGGREGATE)
This job reads the persisted runtime data from the persistence layer and
aggregates it on an hourly basis.
SAP_XMB_PERF_REORG (SXMS_PF_REORG)
This job deletes the runtime data once the time interval defined by the
configuration parameter DAYS_TO_KEEP_DATA has been exceeded.
SAP_XMB_EXTRACT_PMI_DATA (SXMS_PMI_EXTRACT_PMI_DATA)
This job extracts runtime data from PMI. The job is optional. If you want
to display performance data from PMI in the Runtime Workbench, you
must schedule this job on your monitoring server
SAP_XMB_GET_PMI_DATA (SXMS_PF_GET_PMIDATA)
This job transfers the runtime data that has been extracted on the
monitoring server to the Integration Server and can display the data in
the performance monitoring of the Runtime Workbench. The job is
optional, see above.
Runtime Workbench - Performance

Enhanced performance statistics
Measurement of throughput and latency (processing time)
Selection and aggregation of performance data by:
a. XI component
(Integration Server,
Adapter Engine)
b. Time range
c. Message attributes:
Sender, receiver,
message type
Demo
Demo
TRex Message Search
Motivation
If the processing time for a specific interface exceeds predefined
thresholds, an alert should be raised.
Detect performance bottlenecks within your Integration Server
Based on message performance data gathered on the Integration
Server
For more details refer to SAP Note: 730193
Create a CCMS Alert Monitor Node

For a specific Sender /
Receiver / Interface
combination define
Processing Alert Thresholds.
Maintain table
ALXMBPFALERT in TC SM30
and enter the required values.
CCMS Alert Monitor

As a consequence a new
monitor node is created in
the Exchange
Infrastructure Alert
Monitor.
Demo
Demo
TRex Message Search
Use TRex Search Engine for Message Selection

All Messages from both the Integration Server and the Adapter
Engine are transfered to TRex for indexing.
Full Text Search on Payload
Fast Results for Message Search
Embedded in Runtime Workbench
Temporally delayed because Messages need to be synchronized
with TRex
From SP 14 on
PI TRex Architecture
TREX
ABAP
Client
Name
Server
Java
Client
HTTP
XML
Preprocessor
Queue
Server
Gateway
Index
RFC
Server
Web
Server
TCP/IP
Server
Text Mining
Engine
Text Search
Engine
Attribute
Engine
Index
Index
Index
Configuration Integration Engine I

Create a RFC Destination
pointing to the TRexs
Servers registered Server
Program.
In TC SXMB_ADM
Integration Engine
Configuration Edit
Specific Configuration
and enter the RFC
Destination created
before for the parameter
Monitoring
TREX_RFC_
DESTINATION.
Configuration Integration Engine II

Activate Indexing for the
Integration Engine.
In TC SXMS_ADMI_IND
adapt the indexing
parameters and activate
Indexing by pressing the
button Indexing.
Deploy PI TRex Application

Deploy the aii_trex.sda
using the SDM.
The sda is available via
SAP Note: 867381
Configuration Adapter Engine I

Configure the TRex
Service.
In the Visual
Administrator select
Cluster Server
Services TRex Service
and enter the resp. values
for nameserver.address
and
nameserver.backuplist.
Configuration Adapter Engine II

Change Authorization for
PIs TRex Application.
In the Visual Administrator
select Cluster Server
Services Security
Provider. Select the
component
sap.com/com.sap.aii.trex
and add the group SAP_
XI_ADMINISTRATOR_J2EE
for the Security Role
admin.
Configuration Adapter Engine III

Activate Indexing for the
Adapter Engine.
Access the URL
http://<host>:<port>/Trex/M
onitor and switch to the
Admin Page. Adapt the
Indexing Parameter to your
needs and activate the
Indexing.
Message Search using TRex

To enable Message Search
via TRex in the Runtime
Workbench, a new
parameter must be created
in the Exchange Profile.
In the Exchange Profile
create the Parameter
com.sap.aii.rwb.trex.
messagesearch with value
true in section Runtime
Workbench.
Message Search Using TRex
Demo
Demo
Summary
You have seen how the CCMS Alert Monitoring and the Alert
Framework can support you seamlessly operate your Process
Integration.
You are able to do a PI Performance Analysis and configure
Performance CCMS Alerts for specific interfaces.
You can utilize TRex for Message Search.
Further Information
Public Web:
www.sap.com
SAP Developer Network: www.sdn.sap.com Exchange Infrastructure
Forum
SAP Customer Services Network: www.sap.com/services/
NetWeaver Developers Guide: www.sdn.sap.com/sdn/developersguide.sdn
Related SAP Education Training Opportunities

http://www.sap.com/education/
Related Workshops/Lectures at SAP TechEd 2005

BP103, End-to-End Process Integration in SAP NetWeaver, Lecture
BPI300, Troubleshooting the J2EE-Based Adapter Engine, Lecture
LCM200, Administration and Support of SAP NetWeaver-Based Solutions,
Lecture
LCM265, SAP NetWeaver Administrator The Latest Tool for Monitoring
and Administration, Hands-on
Questions?
Q&A
Feedback
Please complete your session evaluation.
Be courteous deposit your trash,
and do not take the handouts for the following session.
Thank You !
Copyright 2005 SAP AG. All Rights Reserved
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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,
Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
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.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver 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 in several other countries all over the world. 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.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited
to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use
of these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use
of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party
Web pages.

PI Monitoring 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

PI Monitoring PDF

Uploaded by

Copyright:

Available Formats

Session ID: BPI208

Process Integration Monitoring

Prasad illapani, SAP Labs, LLC

As a result of this workshop, you will

SAP AG 2005, SAP TechEd 05 / BPI208 / 3

of your Landscape Components

The following Monitoring Tools are available for the Exchange

SAP AG 2005, SAP TechEd 05 / BPI208 / 4

Process Integration and CCMS

XI All-in One Server

Business Process Engine

SAP AG 2005, SAP TechEd 05 / BPI208 / 7

XI 3.0 Components in SAP Web AS 6.40

SAP AG 2005, SAP TechEd 05 / BPI208 / 9

CEN Central Monitoring System

To register a remote system,

SAP AG 2005, SAP TechEd 05 / BPI208 / 10

J2EE Specific CCMS Configuration

SAP AG 2005, SAP TechEd 05 / BPI208 / 12

Register CCMS Agent

SAP AG 2005, SAP TechEd 05 / BPI208 / 13

Verify CCMSR Agent Registration and Status

Verify that the Agents Status

SAP AG 2005, SAP TechEd 05 / BPI208 / 14

J2EE Monitoring Template

SAP AG 2005, SAP TechEd 05 / BPI208 / 15

Activation of CCMS Monitoring

Activate CCMS Monitoring by

Change the value for Parameter

SAP AG 2005, SAP TechEd 05 / BPI208 / 17

CCMS System Group Maintenance with TC RZ21

SAP AG 2005, SAP TechEd 05 / BPI208 / 18

Activation of qRFC - Prerequisites

SAP AG 2005, SAP TechEd 05 / BPI208 / 19

SAP AG 2005, SAP TechEd 05 / BPI208 / 20

SAP AG 2005, SAP TechEd 05 / BPI208 / 21

GRMG (Generic Request and Message Generator) Framework

(An example of GRMG scenario)

SAP AG 2005, SAP TechEd 05 / BPI208 / 23

Activation of heartbeat monitoring- Prerequisites

SAP AG 2005, SAP TechEd 05 / BPI208 / 24

GRMG Configuration file upload - Prerequisites

SAP AG 2005, SAP TechEd 05 / BPI208 / 25

Customizing GRMG Scenarios

SAP AG 2005, SAP TechEd 05 / BPI208 / 26

Adjusting Frequency for individual Scenarios

SAP AG 2005, SAP TechEd 05 / BPI208 / 27

SAP AG 2005, SAP TechEd 05 / BPI208 / 28

SAP AG 2005, SAP TechEd 05 / BPI208 / 29

Process Integration and CCMS

PI and Alert Framework - Configuration

Alert Framework (ALM) and PI

NW 04 SP 13 including, from SP 14 on the Alert generation does

SAP AG 2005, SAP TechEd 05 / BPI208 / 32

Activate Required ICF Services

SAP AG 2005, SAP TechEd 05 / BPI208 / 33

End-to-End Monitoring Configuration

SAP AG 2005, SAP TechEd 05 / BPI208 / 34

SAP AG 2005, SAP TechEd 05 / BPI208 / 35

SAP AG 2005, SAP TechEd 05 / BPI208 / 36

Element SXMS_MSG_GUID returns the Message ID

Subsequent Activities for PI Alerts by default contain links for

Recipients could be identified