Embed Size (px)
Citation preview
Prasad illapaniSAP Labs
What You Need to Know About SAP NetWeaverExchange Infrastructure (XI) Message Processing, Monitoring, and Troubleshooting
© SAP AG 2006, 2
What We’ll 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 Processing — Overview
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 Monitoring in 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 browserMessages 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 usingthe 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 We’ll 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 Monitoring in Integration Server
Two selection screens(standard/advanced)
Selection on:Status GroupStatusExecution FromExecution ToParty/Scheme/Agency/Service (S/R)Interface Name/Namespace (S/R)PipelineTechnical Inbound ChannelOutbound StatusErrorClient
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 List
Flexible ALV Views
Legend
© SAP AG 2006, 8
Display Message Contents
Compare versions
Step
s in
Pip
elin
eDisplay and download of the content
© SAP AG 2006, 9
What We’ll 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 Monitoring via the 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
RuntimeWorkbench(RWB)
Syst
em L
ands
cape
Dire
ctor
y
MessageMonitoring
PerformanceAnalysis
ComponentMonitoring CCMS
Alerting Framework
PMI
MessageAlerting
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)AdapterEngine
J2SEAdapterEngine
© SAP AG 2006, 11
XI 3.0 RWB — Message Monitoring
Message MonitoringHarmonization of different message monitors
Integration EngineAdapter Framework (J2EE)
All message monitoring centrally accessible through the RWBMonitoring locally available as well
At least for Partner Connectivity Kit
© SAP AG 2006, 12
Message Monitoring — Message Details
To see the detailed information about a message, select the radio button for the message and choose DetailsTo view the individual versions of the message (as in transaction SXI_MONITOR), choose Message ContentYou can also view referencing and referenced messages
© SAP AG 2006, 13
What We’ll 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
Alert Configuration
Alert Categories arecontainers for some kinds of alerts. Additionalinformation, such as alert texts and subsequentactivities, as well as recipientlists, are maintained for eachAlert Category.
In the Runtime Workbench in section Alert Configuration,press the button CreateAlert Category. On the following screen,maintain an Alert Category.
© SAP AG 2006, 15
Alert Categories
Container Elements for various Message Header information areavailable for PI Alerts. These Container Elements are filled at runtime with message-specific information and are used withinthe Alert’s short and long text. For example:
Container Element SXMS_MSG_GUID returns theMessage IDContainer Element SXMS_FROM_INTERFACE returns theSender Interface
Subsequent Activities for PI Alerts by default contain links forthe respective message to:
Message MonitoringEnd-to-End Monitoring
Recipients can be identifiedAs Fixed UsersVia User RolesVia Self-Subscription based on User Roles
© SAP AG 2006, 16
Alert Rules
Alert Rules define the errorsituation 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 addit to the Alert Category.
© SAP AG 2006, 17
Alert Subscription and Alert Inbox
© SAP AG 2006, 18
TREX Engine for Message Search in XI 3.0
All Messages from both the Integration Server and the Adapter Engine are transfered to TREX for indexingFull Text Search on PayloadFast Results for Message SearchEmbedded in Runtime WorkbenchTemporarily delayed because Messages need to be synchronizedwith TREXFrom SAP NetWeaver ’04 SPS 15
© SAP AG 2006, 19
PI — TREX Architecture
TREX
Index Server
Text SearchEngine
Text MiningEngine
AttributeEngine
Index Index Index
Preprocessor
Web Server
ABAPClient
JavaClient
RFC Server
Gateway
QueueServer
NameServer
transactionP/IP
HTTPXML
© SAP AG 2006, 20
Configuration Integration Engine
Create an RFC Destination pointing to the TREX Server’sregistered Server Program
In transactionSXMB_ADM Integration Engine ConfigurationEdit Specific Configuration, enter the RFC Destination created before for the parameter Monitoring TREX_RFC_DESTINATION
© SAP AG 2006, 21
Configuration Integration Engine (cont.)
Activate Indexing for theIntegration Engine
In transactionSXMS_ADMI_IND adapt the indexing parameters and activate Indexing by pressing the button Indexing
© SAP AG 2006, 22
Deploy PI TREX Application
Deploy the aii_trex.sdausing the SDM.
The SDA is available via SAP Note 867381
© SAP AG 2006, 23
Configuration Adapter Engine (AE)
Configure the TREXService
In the Visual Administrator, selectCluster ServerServices TREX Service and enter the respective values for nameserver.address and nameserver.backuplist
© SAP AG 2006, 24
Configuration Adapter Engine (cont.)
Change Authorization forPI’s TREX Application
In the Visual Administrator,select Cluster ServerServices Security Provider. Select the sap.com/com.sap.aii.trexcomponent and add the SAP_XI_ADMINISTRATOR_J2EE group for theSecurity Role admin.
© SAP AG 2006, 25
Configuration Adapter Engine (cont.)
Activate Indexing for theAdapter Engine
Access the URL http://<host>:<port>/TREX/Monitor and switch to theAdmin Page. Adapt theIndexing Parameter to yourneeds and activate theIndexing.
© SAP AG 2006, 26
Message Search Using TREX
To enable Message Searchvia TREX in the RuntimeWorkbench, a newparameter must be createdin the Exchange Profile
In the Exchange Profile,create the Parameter com.sap.aii.rwb.trex.messagesearch with valuetrue in section RuntimeWorkbench
© SAP AG 2006, 27
Message Search Using TREX (cont.)
© SAP AG 2006, 28
What We’ll 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 Troubleshooting in XI 3.0
Problems with message processingWithin the Integration Engine pipelineConnectivity from/to the Integration ServerWithin the Adapter Engine (messaging layer)
© SAP AG 2006, 30
Typical Journey of a Message in Integration Server
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 Engineor proxy
Adapter Engineor proxy
SAP Web AS – ABAP stack
© SAP AG 2006, 31
Logical Routing
Logical routing does not find a receiverA seemingly error-free XML message cannot be processedProcessing 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_CACHEIf necessary, adjust the routing information in the Integration DirectoryIf 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
Logical Routing (cont.)
Logical routing finds more than one receiver (synchronous)This is not permitted for synchronous XML messagesIntegration 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 XIError code TOO_MANY_RECEIVERS_CASE_BE
Common causes of errorIn 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
Technical Routing
Technical routing not executed or executed with errorsMessage processing ends after technical routingThe 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
Technical Routing: Message Not Arriving in Target
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
Outbound Binding Information
Information on the sender and receiver service/interface/NS
Header mapping results
Communication channel data:Adapter typeConnectivity information
© SAP AG 2006, 36
Mapping Errors
Mapping not executed or contains errorsProcessing of an XML message ends after mappingMapping was not executed or was executed with errors
SolutionExamine 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_JCOSERVERCheck 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
Mapping Errors (cont.)
Many semantic mapping errors go undetectedi.e., the payload after the mapping is not what it is supposed to be
This may trigger an error at a further pointIn 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 Registration
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 StatusIn transaction SMQR check the status of the scheduler and the status of the individual queues
© SAP AG 2006, 39
Problems with the Queues
Messages stuck in status “Scheduled for outbound processing”message scheduled (commit follows)
Indicates there is a problem with the underlying queueScroll to the right and click on the queue name to navigate to SMQ2
© SAP AG 2006, 40
Resolving Problems with Queues
Examine Status Text for first entry
Resolve issue with the first entryRestart or cancel message from SXMB_MONIReset queue status if applicableExecute LUW at the queue level for emergency cases onlyNever delete LUW at the queue level
Activate scheduler
© SAP AG 2006, 41
Adapter Problems
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
Problem with Messages within the AE
Check the message monitor for the adapter engineVia the RWBDirectly 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
IDoc Adapter: Connectivity Problems
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 sendersFor posting the message into IDoc receivers
Ensure that the ALE-specific connectivity is in placeRFC 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
IS - IDoc Receiver: IDoc Does Not Reach Target System
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
IDoc Conversion Contains Errors
Problem with the conversion between the ALE logical system name and the XI business system name
This information is maintained in the SLDIn 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 uppercaseMandatory 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 We’ll 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
Live Demo
Message Monitoring and Troubleshooting in XI 3.0
© SAP AG 2006, 48
What We’ll 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 Monitoring and Troubleshooting Tips
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
Tip
© SAP AG 2006, 50
What We’ll 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
Summary
Monitor XML messages via transaction SXMB_MONIThe Runtime Workbench is a tool for monitoring the XI (and all of its components, processes, and messages) centrally through a Java-based interfaceThe Runtime Workbench unifies many of the monitoring architectures available in SAP solutions into a single, coherent, Web-based interfaceThe Runtime Workbench offers a central view of all components and processes such as Message Monitoring, Component Monitoring, and End-to-End Message MonitoringPerformance measurement across distributed XI landscape is available via the RWBSmooth Integration with Basis Monitoring solutions:
CCMSPMIAlert Framework
Unified User Interface (UI)
© SAP AG 2006, 52
Resources
http://help.sap.comSAP NetWeaver Process Integration SAP Exchange Infrastructure
Runtime Central Monitoring
SAP GuidesSAP Exchange Infrastructure 3.0 SR1 Configuration Guide SAP NetWeaver XI 3.0 Troubleshooting Guide
How-to GuidesHow to Monitor Integration Processes (ccBPM)How to Monitor Exchange Infrastructure 3.0
© SAP AG 2006, 53
For more information: Access the SAP Developer Network – www.sdn.sap.com
The central hub for the SAP technology community
Everyone can connect, contribute and collaborate- consultants, administrators and developersFocus around SAP NetWeaver and SAP xApps
High quality of technical resourcesArticles, 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 PortalFeaturing collaboration capabilities of SAP Knowledge Management
© SAP AG 2006, 54
7 Key Points to Take 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.comunder XI forum, and get quick answers from SAP experts and other forum members
