Prasad illapani

SAP Labs
What You Need t o Know
About SAP Net Weaver
Ex c hange I nf r ast r uc t ur e
(XI ) Message Pr oc essi ng,
Moni t or i ng, and
Tr oubl eshoot i ng
SAP AG 2006, 2
What Wel l Cover
Processing XML messages in XI 3.0 overview
Message monitoring in the Integration Server
Message monitoring in the Runtime Workbench (RWB)
Alerts and TREX Engine message search
Message troubleshooting
Live demo
Message monitoring and troubleshooting tips
Wrap-up
SAP AG 2006, 3
XI Message Pr oc essi ng Over vi ew
Application
System A
SOAP-XML
Integration Server
Application
System B
SOAP-XML
XI connects various application systems via XML messaging
XI uses an SAP-specific implementation of the SOAP protocol
Messages received at the Integration Server are processed
through a defined series of steps called Pipeline Services
When a message is received at the Integration Server, the
message is examined and all valid configurations (as maintained
in the Integration Directory) for that message are executed
SAP AG 2006, 4
Message Moni t or i ng i n XI 3.0
Messages can be monitored in XI 3.0 in two
different ways:
1. Integration Server using transaction: SXMB_MONI via
SAPGUI
All the inbound and outbound XML messages with various
statuses can be monitored
2. Runtime Workbench (RWB) via browser
Messages can be monitored at the Integration Server level and also
at the Adapter Engine level
Messages can also be monitored via the payload base search using
the TREX Engine Indexing functionality
The RWB provides other monitoring features, such as Component
Monitoring, End-to-End Monitoring, Performance Monitoring, and
alerts via the Alert Framework, etc.
SAP AG 2006, 5
What Wel l Cover
Processing XML messages in XI 3.0 overview
Message monitoring in the Integration Server
Message monitoring in the Runtime Workbench (RWB)
Alerts and TREX Engine message search
Message troubleshooting
Live demo
Message monitoring and troubleshooting tips
Wrap-up
SAP AG 2006, 6
Message Moni t or i ng i n I nt egr at i on Ser ver
Two selection screens
(standard/advanced)
Selection on:
Status Group
Status
Execution From
Execution To
Party/Scheme/Agency/Service
(S/R)
Interface Name/Namespace
(S/R)
Pipeline
Technical Inbound Channel
Outbound Status
Error
Client
Integration Server using transaction:
SXMB_MONI via SAPGUI
All the Inbound and Outbound XML
Messages with various statuses can be
monitored
SAP AG 2006, 7
XML Message Li st
Flexible ALV Views
Legend
SAP AG 2006, 8
Di spl ay Message Cont ent s
Compare
versions
S
t
e
p
s

i
n

P
i
p
e
l
i
n
e
Display and download of the content
SAP AG 2006, 9
What Wel l Cover
Processing XML messages in XI 3.0 overview
Message monitoring in the Integration Server
Message monitoring in the Runtime Workbench (RWB)
Alerts and TREX Engine message search
Message troubleshooting
Live demo
Message monitoring and troubleshooting tips
Wrap-up
SAP AG 2006, 10
Message Moni t or i ng vi a t he RWB
Runtime Workbench
Messages can be
monitored at the
Integration Server
level and also at the
Adapter Engine level
Messages can also be
monitored via the
Payload base search
using the TREX Engine
Indexing functionality
RWB provides other
monitoring features,
such as Component
Monitoring, End-to-
End Monitoring,
Performance
Monitoring, and Alerts
Central Monitoring
Runtime
Workbench
(RWB)
S
y
s
t
e
m

L
a
n
d
s
c
a
p
e
D
i
r
e
c
t
o
r
y
Message
Monitoring
Performance
Analysis
Component
Monitoring
CCMS
Alerting
Framework
PMI
Message
Alerting
Integration Server
(SAP Web AS 6.40)
Business
Process Engine
Integration Engine
Adapter Engine
SAP
Application
SAP Web AS 6.40,
using XI proxies
(decentral)
Adapter
Engine
J2SE
Adapter
Engine
SAP AG 2006, 11
XI 3.0 RWB Message Moni t or i ng
Message Monitoring
Harmonization of different message monitors
Integration Engine
Adapter Framework (J2EE)
All message monitoring centrally accessible
through the RWB
Monitoring locally available as well
At least for Partner Connectivity Kit
SAP AG 2006, 12
Message Moni t or i ng Message Det ai l s
To see the detailed information
about a message, select the radio
button for the message and
choose Details
To view the individual versions
of the message (as in transaction
SXI_MONITOR), choose
Message Content
You can also view referencing
and referenced messages
SAP AG 2006, 13
What Wel l Cover
Processing XML messages in XI 3.0 overview
Message monitoring in the Integration Server
Message monitoring in the Runtime Workbench (RWB)
Alerts and TREX Engine message search
Message troubleshooting
Live demo
Message monitoring and troubleshooting tips
Wrap-up
SAP AG 2006, 14
Al er t Conf i gur at i on
Alert Categories are
containers for some kinds of
alerts. Additional
information, such as alert
texts and subsequent
activities, as well as recipient
lists, are maintained for each
Alert Category.
In the Runtime Workbench in
section Alert Configuration,
press the button Create
Alert Category.
On the following screen,
maintain an Alert Category.
SAP AG 2006, 15
Al er t Cat egor i es
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. For example:
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 respective message to:
Message Monitoring
End-to-End Monitoring
Recipients can be identified
As Fixed Users
Via User Roles
Via Self-Subscription based on User Roles
SAP AG 2006, 16
Al er t Rul es
Alert Rules define the error
situation that raises a
specific alert. One Alert
Category can contain one or
many Alert Rules.
In the Runtime Workbench in
the Alert Configuration
section, select an Alert
Category.
Define an Alert Rule and add
it to the Alert Category.
SAP AG 2006, 17
Al er t Subsc r i pt i on and Al er t I nbox
SAP AG 2006, 18
TREX Engi ne f or Message Sear c h i n XI 3.0
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
Temporarily delayed because Messages need to be synchronized
with TREX
From SAP NetWeaver 04 SPS 15
SAP AG 2006, 19
PI TREX Ar c hi t ec t ur e
TREX
Index Server
Text Search
Engine
Text Mining
Engine
Attribute
Engine
Index Index Index
Preprocessor
Web
Server
ABAP
Client
Java
Client
RFC
Server
Gateway
Queue
Server
Name
Server
transactionP/IP
HTTP
XML
SAP AG 2006, 20
Conf i gur at i on I nt egr at i on Engi ne
Create an RFC
Destination pointing to
the TREX Servers
registered Server
Program
In transaction
SXMB_ADM Integration
Engine Configuration
Edit Specific
Configuration, enter the
RFC Destination created
before for the parameter
Monitoring TREX_RFC_
DESTINATION
SAP AG 2006, 21
Conf i gur at i on I nt egr at i on Engi ne (c ont .)
Activate Indexing for the
Integration Engine
In transaction
SXMS_ADMI_IND adapt
the indexing parameters
and activate Indexing by
pressing the button
Indexing
SAP AG 2006, 22
Depl oy PI TREX Appl i c at i on
Deploy the aii_trex.sda
using the SDM.
The SDA is available via
SAP Note 867381
SAP AG 2006, 23
Conf i gur at i on Adapt er Engi ne (AE)
Configure the TREX
Service
In the Visual
Administrator, select
Cluster Server
Services TREX Service
and enter the respective
values for
nameserver.address and
nameserver.backuplist
SAP AG 2006, 24
Conf i gur at i on Adapt er Engi ne (c ont .)
Change Authorization for
PIs TREX Application
In the Visual Administrator,
select Cluster Server
Services Security
Provider. Select the
sap.com/com.sap.aii.trex
component and add the
SAP_XI_ADMINISTRATOR_
J2EE group for the
Security Role admin.
SAP AG 2006, 25
Conf i gur at i on Adapt er Engi ne (c ont .)
Activate Indexing for the
Adapter Engine
Access the URL
http://<host>:<port>/TREX/
Monitor and switch to the
Admin Page. Adapt the
Indexing Parameter to your
needs and activate the
Indexing.
SAP AG 2006, 26
Message Sear c h Usi ng 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
SAP AG 2006, 27
Message Sear c h Usi ng TREX (c ont .)
SAP AG 2006, 28
What Wel l Cover
Processing XML messages in XI 3.0 overview
Monitoring messages in the Integration Server
Monitoring messages in the Runtime Workbench (RWB)
Alerts and TREX Engine message search
Message troubleshooting
Live demo
Message monitoring and troubleshooting tips
Wrap-up
SAP AG 2006, 29
Message Tr oubl eshoot i ng i n XI 3.0
Problems with message processing
Within the Integration Engine pipeline
Connectivity from/to the Integration Server
Within the Adapter Engine (messaging layer)
SAP AG 2006, 30
Typi c al J our ney of a Message i n I nt egr at i on Ser ver
Internet Communication Manager (ICM)
Internet Communication Framework (ICF)
Rec. Det.
Int. Det. Mapping
Tech.
Routing
Call
Adapter
SAP Web AS Java stack
JRFC
HTTP HTTP
Adapter Engine
or proxy
Adapter Engine
or proxy
SAP Web AS ABAP stack
SAP AG 2006, 31
Logi c al Rout i ng
Logical routing does not find a receiver
A seemingly error-free XML message cannot be processed
Processing ends after logical routing. No receiver could be found.
Error code NO_RECEIVER_CASE_BE or NO_RECEIVER_CASE_ASYNC
Inspect receiver determination area in SXI_CACHE
If necessary, adjust the routing information in the Integration Directory
If the message is asynchronous, it can be restarted manually, and manual
changes in the SOAP header are permitted
Common causes of error are discrepancies between the configuration
and the SOAP header of the incoming message
Sender service does not match (case-sensitive!)
Sender interface name or namespace does not match (case-sensitive!)
Condition for content-based routing has not been met
Double-check message content
Double-check condition (XPath expression or context object)
SAP AG 2006, 32
Logi c al Rout i ng (c ont .)
Logical routing finds more than one receiver (synchronous)
This is not permitted for synchronous XML messages
Integration Directory content may need to be adjusted
It is the responsibility of the configuration person to make sure that the
routing rules are such that exactly one receiver will be found
Synchronous messages cannot be restarted manually from XI
Error code TOO_MANY_RECEIVERS_CASE_BE
Common causes of error
In the Integration Directory there are several complex routing rules that
are content-based. Since every routing rule is evaluated during runtime,
two or more rules may be true at runtime for a specific message.
.
SAP AG 2006, 33
Tec hni c al Rout i ng
Technical routing not executed or executed with errors
Message processing ends after technical routing
The XML message could not be sent to the target system
Processing stops once the target system has been called
Analyze the contents of the Outbound binding header and check connectivity
parameters (as described in next slides)
Analyze the Error header
Note: An error such as outbound binding not found usually indicates that the
receiver agreement could not be found. Check the Integration Directory.
SAP AG 2006, 34
Tec hni c al Rout i ng: Message Not Ar r i vi ng i n Tar get
Examine the outbound binding header
after the technical routing pipeline step
Ensure that the target system is
accessible using the same connectivity
parameters displayed in the outbound
binding
Adjust connectivity settings in target
system, or adjust communication
channel/receiver agreement as
appropriate
SAP AG 2006, 35
Out bound Bi ndi ng I nf or mat i on
Information on the sender and
receiver service/interface/NS
Header mapping results
Communication channel data:
Adapter type
Connectivity information
SAP AG 2006, 36
Mappi ng Er r or s
Mapping not executed or contains errors
Processing of an XML message ends after mapping
Mapping was not executed or was executed with errors
Solution
Examine error header
JCO_COMMUNICATION_FAILURE indicates a problem in the RFC
connection between the Integration Engine and the mapping runtime
in J2EE
Check the RFC destination AI_RUNTIME_JCOSERVER
Check the receiving end of the RFC connection in the J2EE Engine
(AI_RUNTIME_XR3)
Check the application sap.com/com.sap.xi.services in the J2EE Engine
NO_MAPPINGPROGRAM_FOUND indicates a problem in locating the
mapping program (e.g., the mapping program has been deleted)
EXCEPTION_DURING_EXECUTE: Check the code of the mapping
program (ABAP, Java, XSLT)
SAP AG 2006, 37
Mappi ng Er r or s (c ont .)
Many semantic mapping errors go undetected
i.e., the payload after the mapping is not what it is supposed
to be
This may trigger an error at a further point
In a future pipeline step (e.g., BPM scenarios)
In an adapter (e.g., IDoc adapter checks payload format)
In the target application (e.g., transaction cannot be posted)
In another XI system (in the case of XI-to-XI communication)
Typically the mapping will have to be adjusted at the
semantic level
Therefore, it is important to test mappings thoroughly
This is a development task
SAP AG 2006, 38
Queue Regi st r at i on
Are the queues registered?
Call transaction SMQR in the
corresponding client (Integration
Server or application client)
If in doubt, register the queues.
To do this, use transaction
SXMB_ADM and go to the function
Manage Queues.
Pay particular attention to
externally registered queues with
the prefixes XBQ*, XBT*, XB*, or X*
Check the Queue Status
In transaction SMQR check the
status of the scheduler and the
status of the individual queues
SAP AG 2006, 39
Pr obl ems w i t h t he Queues
Messages stuck in status Scheduled for outbound processing
message scheduled (commit follows)
Indicates there is a problem with the underlying queue
Scroll to the right and click on the queue name to navigate to SMQ2
SAP AG 2006, 40
Resol vi ng Pr obl ems w i t h Queues
Examine Status Text for first entry
Resolve issue with the first entry
Restart or cancel message from SXMB_MONI
Reset queue status if applicable
Execute LUW at the queue level for emergency cases only
Never delete LUW at the queue level
Activate scheduler
SAP AG 2006, 41
Adapt er Pr obl ems
Problem with the messaging layer of the J2EE adapter engine
Problem with the individual adapters running on top of the J2EE
adapter engine
Problem with message processing for adapters contained in the
ABAP stack (plain HTTP, IDoc)
Sender adapter: The message can be seen in the adapter monitor
(via the Runtime Workbench) but does not appear in SXMB_MONI
Receiver adapter: The message in SXMB_MONI is in status
processed successfully but cannot be seen in the
target system
SAP AG 2006, 42
Pr obl em w i t h Messages w i t hi n t he AE
Check the message monitor for the adapter engine
Via the RWB
Directly via http://<host>:<port>/mdt
For the given message, select details
For more information, select audit protocol
If the information is still not sufficient, check the appropriate log file in
the J2EE log viewer
SAP AG 2006, 43
I Doc Adapt er : Connec t i vi t y Pr obl ems
IDoc connectivity relies on tRFC. Check tRFC monitor (SM58).
Connection from XI Integration Server to IDoc senders and receivers
should be maintained
For metadata callback to IDoc senders
For posting the message into IDoc receivers
Ensure that the ALE-specific connectivity is in place
RFC destination is assigned target port and client (IDX1)
RFC destination is maintained correctly (SM59)
If IDoc metadata still cannot be loaded into the Integration Server,
this must be solved on a case-by-case basis
Possible reason: IDoc type or segment has not been released
SAP AG 2006, 44
I S - I Doc Rec ei ver : I Doc Does Not Reac h Tar get Syst em
Examine RFC destination from outbound binding as previously
described
Obtain transaction ID (TID) from Runtime header and monitor in
transaction SM58
The TID can also be obtained from the IDoc adapter monitor (IDX5)
SAP AG 2006, 45
I Doc Conver si on Cont ai ns Er r or s
Problem with the conversion between the ALE logical system name
and the XI business system name
This information is maintained in the SLD
In association with the Business System (for third-party systems)
In association with the Technical System client (for Web AS-ABAP)
Entry must be maintained in uppercase
Mandatory for any Business System that will act as IDoc sender/receiver
In some cases the header mapping functionality in the receiver
agreement can be used to overwrite sender/receiver service in the
SOAP header, or some fields of the IDoc control record (see IDoc unit
in adapters course)
<SAP:Stack>Unable to convert the sender service XXXX to an ALE
logical system</SAP:Stack>
SAP AG 2006, 46
What Wel l Cover
Processing XML messages in XI 3.0 overview
Monitoring messages in the Integration Server
Monitoring messages in the Runtime Workbench (RWB)
Alerts and TREX Engine message search
Message troubleshooting
Live demo
Message monitoring and troubleshooting tips
Wrap-up
SAP AG 2006, 47
Li ve Demo
Message Monitoring and
Troubleshooting in XI 3.0
SAP AG 2006, 48
What Wel l Cover
Processing XML messages in XI 3.0 overview
Message monitoring in the Integration Server
Message monitoring in the Runtime Workbench (RWB)
Alerts and TREX Engine message search
Message troubleshooting
Live demo
Message monitoring and troubleshooting tips
Wrap-up
SAP AG 2006, 49
Message Moni t or i ng and Tr oubl eshoot i ng Ti ps
Identify the root cause of the error when a message fails
Errors can happen at any step in the pipeline services
Check the Logs/Traces in the monitoring transaction
Identify where the error is occurring in the pipeline step
Use the RWB to display the error at the Adapter Engine level
Configure alerts to differentiate between system errors and
process alerts
Route alerts via email or SMS to appropriate person based on
the type of alert
Ti p
SAP AG 2006, 50
What Wel l Cover
Processing XML messages in XI 3.0 overview
Message monitoring in the Integration Server
Message monitoring in the Runtime Workbench (RWB)
Alerts and TREX Engine message search
Message troubleshooting
Live demo
Message monitoring and troubleshooting tips
Wrap-up
SAP AG 2006, 51
Summar y
Monitor XML messages via transaction SXMB_MONI
The Runtime Workbench is a tool for monitoring the XI (and all of
its components, processes, and messages) centrally through a
Java-based interface
The Runtime Workbench unifies many of the monitoring
architectures available in SAP solutions into a single, coherent,
Web-based interface
The Runtime Workbench offers a central view of all components
and processes such as Message Monitoring, Component
Monitoring, and End-to-End Message Monitoring
Performance measurement across distributed XI landscape is
available via the RWB
Smooth Integration with Basis Monitoring solutions:
CCMS
PMI
Alert Framework
Unified User Interface (UI)
SAP AG 2006, 52
Resour c es
http://help.sap.com
SAP NetWeaver Process Integration SAP Exchange Infrastructure
Runtime Central Monitoring
SAP Guides
SAP Exchange Infrastructure 3.0 SR1 Configuration Guide
SAP NetWeaver XI 3.0 Troubleshooting Guide
How-to Guides
How to Monitor Integration Processes (ccBPM)
How to Monitor Exchange Infrastructure 3.0
SAP AG 2006, 53
For mor e i nf or mat i on: Ac c ess t he SAP Devel oper Net w or k
w w w .sdn.sap.c om
The central hub for the SAP technology
community
Everyone can connect, contribute and
collaborate- consultants, administrators and
developers
Focus around SAP NetWeaver and SAP xApps
High quality of technical resources
Articles, how-to guides, weblogs,
collaborative areas, discussion forums and
downloads, toolkits and code-samples
A collaboration platform, not a one-way
street
SAP experts from customers, partners and
SAP
SDN is powered by SAP NetWeaver
Built on the SAP Enterprise Portal
Featuring collaboration capabilities of SAP
Knowledge Management
SAP AG 2006, 54
7 Key Poi nt s t o Tak e Home
Leverage the available message monitoring options in XI 3.0
Explore the different monitoring features in the RWB
Utilize the Alert Framework tool for routing error messages
Analyze the different errors and identify the sources of the errors
Use TREX Engine for message search based on payload data
Follow the best practice that suits your system landscape
Discuss your problems at the SDN Web site: http://sdn.sap.com
under XI forum, and get quick answers from SAP experts and
other forum members
SAP AG 2006, 55
Your Tur n!
How to contact me:
Prasad illapani
prasad.illapani@sap.com
Questions?