How-to Guide SAP NetWeaver 04

How To Monitor Integration Processes (ccBPM)

Version 1.00 July 2005 Applicable Releases: SAP NetWeaver 04 Support Package Stack 10

 Copyright 2005 SAP AG. All rights reserved. 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. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. These materials are provided as is 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 not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. 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. SAP NetWeaver How-to Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting. Any software coding and/or code lines / strings (Code) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

Table of Contents 1 2 3 Scenario .......................................................................................................................1 Introduction..................................................................................................................1 The Step By Step Solution...........................................................................................2 3.1 Description of the Business Process ....................................................................2 3.2 How to find the correlation ID of a message .......................................................2 3.3 How to check for correct mappings in ccBPM....................................................7 3.4 How-to analyze an integration process in the XI runtime cache .......................11 3.5 How to analyze an integration process in the runtime cache.............................12 4 Appendix....................................................................................................................13

1 Scenario
When an integration process is executed, the system creates corresponding work items, just like during the execution of an SAP Business Workflow. You can use the transactions for monitoring the Business Process Engine to display the generated work items in the Workflow log as well as display detailed information about the status of a specific process or its individual steps. This How-To Guide will explain this very detailed procedure. It is sometimes very difficult to monitor individual work items because you do not know how work items relate to each other. For this purpose, process monitoring is available in XI message monitoring. In process monitoring you can select just integration-processrelated messages and group them in the integration process. This How-To Guide explains what information about processes is available and how you can access it.

2 Introduction
SAP NetWeaver Exchange Infrastructure (SAP NetWeaver XI) has the transaction Integration Engine Monitoring (SXMB_MONI) for persisted XI messages. The Monitor for Processed XML Messages menu option offers you two different views on processed XML messages: Default (default setting): This view displays all messages that meet the chosen selection criteria. Process: This view only displays messages that were processed using the Business Process Engine. The displayed messages are grouped according to the process instances involved. Business Process Engine monitoring contains the following: Graphical overview of the process Detailed list with process-related work items Correlation identifier (if applicable) Mapping (if applicable) This information is explain in section 3.

-1-

3 The Step By Step Solution

Chapter 3.1 describes the business process that was used for the example. Chapter 3.2 describes how to find the correlation ID of a message. Chapter 3.3 describes how to find the messages after a mapping in the process engine. Chapter 3.4 describes how to check if the integration process was transferred successfully from the Integration Directory to the XI runtime. Chapter 3.5 describes how to find the definition and runtime version of a process.

3.1

Description of the Business Process

1. The example collects purchase order messages that have the same purchase order number. When a message with buyer information for the same purchase order number arrives, all messages are mapped to a single message and sent to the receiver.

3.2

How to find the correlation ID of a message

If two messages are related, it is useful to know where to find the correlation ID.
1. On the Integration Server, call transaction: SXMB_MONI,(Integration Engine Monitoring).

-2-

2. Choose Monitor for Processed XML Messages.

3. Choose Process to display all messages assigned to an integration process. Note: Select a timeframe for the messages. Execute the selection.

4. Double-click PE in the Technical Outbound Channel column in message monitoring.

-3-

5. Note: In an error situation when you cannot navigate from message level to the process engine, you can use the Event Queue Browser. Either you find the relevant process with this or you may use transaction SXMB_MONI_BPE. For more information, see the online documentation: Administration of Integration Processes and Monitoring the Business Process Engine.

6. Choose List with Technical Details.

-4-

7. Choose the icon Show Container for the relevant receive step (Task: Start Message)

8. Choose _CORRELATIONS

-5-

9. A table js displayed in the lower part of the window. The number of rows in the table corresponds to the number of open correlations. Check the content of the correlations by double-clicking on the relevant rows.

10. The correlation content is displayed.

-6-

3.3

How to check for correct mappings in ccBPM

Message mappings can also be executed in a transformation step in the process engine. This section explains how to find the message before and after this mapping step.
1. Select the relevant process and follow the procedure described in steps 2 to 6 above.

2. Choose the icon Show Container for the relevant receive step (Task: Mapping)

-7-

3. The subsequent pop-up displays a set of parameters for the mapping step. The values for the parameters MESSAGES_IN and MESSAGES_OUT (<n Entries>) represent the number of abstract message interfaces involved in the interface mapping.

4. Choose MESSAGES_IN to display the data entering the mapping. Row MESSAGES_OUT displays the result of the mapping step.

-8-

5. A table is displayed at the bottom of the pop-up. Each row in the table represents one abstract message interface used in the message mapping definition. To check the instances, choose the relevant rows. Open the context menu by rightclicking.

6. Choose Nested table MESSAGES

-9-

7. In this example, three instances of the abstract message interface were used in the mapping. Double-click the relevant row to check the message content.

8. The message is displayed in transaction SXMB_MONI. Doubleclick on the relevant row to show the content of the message.

9. Double-click the relevant row to show the content of container used in the mapping step.

- 10 -

3.4

How-to analyze an integration process in the XI runtime cache

If your integration process is not working properly, check that the latest version has been transferred to the runtime cache successfully.

1. Integration Repository and Integration Directory data transferred to the Runtime can be displayed in transaction: SXI_CACHE. Double-click Integration Processes on the right-hand side and search for the name of your integration process. Check that your process has the return code 0 (OK). Return code 99 indicates an error.

.
2. If your process is not in the cache, check the Integration Directory. Start the Integration Directory. Check that your process has been activated. Choose Environment Cache Notifications. Check the entries for the relevant cache instance, user, and date. 3. Check the notification status green is okay, red indicates an error situation.

- 11 -

4. To trigger a new cache update when an error has occurred, select the relevant notifications and choose Resend.

Note: If process changes from the Integration Repository do not reach the runtime, you must check that the process is activated in the Integration Repository and in the Integration Direction.

3.5

How to analyze an integration process in the runtime cache

For details on the integration process it is very helpful to know the corresponding workflow task. This can be found in the runtime cache. With this number you are able to find the version and further details about the process definition on the process engine runtime.

1. Integration Repository and Integration Directory data transferred to the runtime can be displayed in transaction: SXI_CACHE. Double-click Integration Processes and search for the name of your integration process. The number of the process is displayed in the Task column, for example: WS96600027 Select the process and choose the sunglasses icon to call transaction SWF_XI_PBUILDER.

- 12 -

2. Alternatively, call transaction SWF_XI_PBUILDER and enter the process number. Press the Enter key. The active version is then shown. Ensure that it is the one you activated in the Integration Repository. You can check for earlier versions, too. Note: If a process that is currently being executed has a longer duration and is still active, the changes will be effective after this process has finished or a new process has been triggered.

4 Appendix
See SAP Note 807640 for information about troubleshooting integration processes. For more information about dos and donts for BPM, see the online documentation at: http://help.sap.com Documentation SAP NetWeaver SAP NetWeaver04 Process Integration Integration Processes (ccBPM) Checklist: Making Correct Use of an Integration Process

- 13 -

www.sap.com/netweaver