SAP NetWeaver SAP NetWeaver Process Integration Simple Use Cases for Advanced Adapter Engine Extended (AEX)

Transcription

1 SAP NetWeaver 7.40 SAP NetWeaver Process Integration Simple Use Cases for Advanced Adapter Engine Extended (AEX) Document Version 1.0 October 2013

2 SAP AG Dietmar-Hopp-Allee Walldorf Germany T +49/18 05/ F +49/18 05/ Copyright 2013 SAP AG. All rights reserved. MaxDB is a trademark of MySQL AB, Sweden. 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. 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. 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, Informix, i5/os, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. 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 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. 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. Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAP s Support Services and may not be modified or altered in any way. Documentation in SAP Developer Network (SDN) You can find this documentation in SAP Developer Network (SDN) titled SAP NetWeaver Simple Use Cases for Advanced Adapter Engine Extended.

3 1 Preface Introduction and Prerequisites Introduction Prerequisites General Prerequisites Providing the necessary User and Authorizations Special Prerequisites for Configuring Variants 10 and Special Prerequisites for Configuring Variant Setting Up the File Directories Creating the Technical and Business Systems in the System Landscape Directory of the Advanced Adapter Engine Extended Defining Business System Components in the Integration Directory in the Advanced Adapter Engine Extended Special Prerequisites for Configuring Performance Monitoring Parameter Special Prerequisites for Configuring Variants Design Objects Used Variant 1: One Sender and One Receiver using the Advanced Adapter Engine Extended Design Objects Used Configuring the Process Integration Scenario Executing the Use Case Virus-Scanning for Messages: Variant 2: One Sender and Two Receivers using the Advanced Adapter Engine Extended with Duplicate Message Handling Design Objects Used Configuring the Process Integration Scenario Executing the Use Case Mass consistency check of the alert rules Execution and Verification Variant 3: One Sender and Two Receivers using Advanced Adapter Engine Extended with Routing Condition Design Objects Used Configuring the Process Integration Scenario Executing the Use Case Copy configuration scenario with content Variant 4: One Sender and Multiple Receivers using Advanced Adapter Engine Extended with Dynamic Receiver Determination Prerequisite - Creating Value Mapping Group Design Objects Used Configuring the Process Integration Scenario Executing the Use Case Variant5: One Sender and Two Receivers using Advanced Adapter Engine Extended With Message Mapping Design Objects Used Configuring the Process Integration Scenario March

4 7.3 Executing the Use Case Variant 6: One Sender and Two Receivers using Advanced Adapter Engine Extended With XSLT Mapping Design Objects Used Modifying Configuration Scenario Executing the Use Case Variant 7: One Sender and Two Receivers using Advanced Adapter Engine Extended - with XML-Validation Design Objects Used Configuring the Process Integration Scenario Execution Variant 8: One Sender and One Receiver using Advanced Adapter Engine Extended - using Exactly Once In Order Design Objects Used Configuring the Process Integration Scenario Execution Variant 9: One Sender and One Receiver - Proxy-to-Proxy Communication using the Advanced Adapter Engine Design Objects Used Configuring the Process Integration Scenario Execution Variant 10: One Sender and One Receiver - Proxy-to- Proxy Communication using the Advanced Adapter Engine and Principle Propagation Prerequisites Activating Principle Propagation Trust Relationship Settings Create Destination in the AEX system Design Objects Used Configuring the Process Integration Scenario Execution Variant 11: One Sender and One Receiver synchronous Proxy-to-Proxy Communication using the Advanced Adapter Engine Design Objects Used Configuring the Process Integration Scenario Execution Variant 12: One Sender and One Receiver synchronous Proxy-to-Proxy Communication using the Advanced Adapter Engine and Principle Propagation Prerequisites Activating Principle Propagation Trust Relationship Settings Create Destination in the AEX Design Objects Used Configuring the Process Integration Scenario Execution March 2012

5 15 Variant 13: One Sender and One Receiver - Proxy-to- Proxy Communication using the Advanced Adapter Engine whereas Receiver send back an Acknowledgment Configuring the Process Integration Scenario Execution Variant 14: One Sender and One Receiver - Proxy-to- Proxy Communication using the Advanced Adapter Engine using Packaging Packaging Configuring the Process Integration Scenario Execution Variant 15: One Sender and One Receiver using Advanced Adapter Engine Extended with Parameterized Mapping Design Objects Used Configuring the Process Integration Scenario Execution Execution with Channel Scheduling Variant 16: One Sender and Two Receivers using Advanced Adapter Engine Extended with Message Order at Runtime Design Objects Used Configuring the scenario in Integration Directory Execution Variant 17: One Sender and One Receiver using Advanced Adapter Engine Extended With Mapping and encrypted persistent storage (PCI-compliant) Design Objects Used Configuring the Scenario in Integration Directory Executing the Use Case Appendix Setting up the system for payload encryption Creating the Keystore and generating the encryption key Global configuration of the MessagingSystem for persistence layer encryption Monitoring Tools PI Component Monitor for NWA Monitoring in Solution Manager PI Communication Channel Monitor Enhancement for NWA Configuration for data collection in Performance Monitor March

6 1 Preface Constraints The texts, references, and graphics contained in this manual have been compiled with utmost care; nevertheless, it is impossible to guarantee that they are fully without error. SAP cannot assume any responsibility for the correctness or completeness of the following documentation; the user alone is responsible for verifying the information contained therein. SAP will only assume liability for damage arising from the use of this documentation irrespective of the pertinent legal basis in the case of intentional or active negligence, under no other circumstances will a warranty be made. Definition This manual describes simple application cases for the Extended adapter engine for process integration and all the configuration steps that are necessary to execute the application cases on the basis of SAP NetWeaver. Intended Audience This manual is intended to be used by both technology and application consultants. Structure The structure of this document follows the sequence of steps required to configure and run the use cases. Additional Documentation List of related documentation Documentation SAP NetWeaver Library documentation: Demo Examples Purpose Introduction to demo examples and description of the process integration scenarios SAP NetWeaver Documentation Simple Use Cases Configuration of SAP NetWeaver Process Integration Introduction to Simple Use Cases and description of the simple use case scenarios for Process Integration Configuring usage type Advanced Adapter Engine Extended This document is updated on a regular basis in SAP Developer Network (SDN) and is available as SAP NetWeaver Simple Use Cases for Advanced Adapter Engine Extended. 2 Introduction and Prerequisites 2.1 Introduction Use cases are based on simple examples that enable you to learn the main features of Advanced Adapter Engine Extended. These instructions will enable you to understand, configure, and execute simple scenarios (that are based on fundamental communication patterns), as well as check that the scenarios are executed correctly. The prerequisite for this document is that you have a general understanding of SAP NetWeaver Process Integration. The following use case variants for the Advanced Adapter Engine Extended are available at present: Variant Variants 1, 8, 9, 10, 11, 12, Description Represents message exchange between one sender and one receiver on the Advanced Adapter Engine Extended 6 March 2012

7 13, 14, 15, and 17: (AAEX). The message processing is done locally on the Advanced Adapter Engine Extended. Variant 8 is executed using EOIO protocol. Variants 9 to 14 are using PROXY clients to send and receive the messages, Variants 11 and 12 are executed synchronously. Variant 13 is using acknowledgments. Variant 14 is using packaging. Variants 10 and 12 are using principal propagation. Variant 15 is using parameterized mapping. In Variant 17 the message payload is stored encrypted on the database. The payload can be seen unencrypted in Message Monitoring. Variant 2 and 4: One sender and two receivers Variant 3: One sender and two receivers with routing condition (see 5) Variant 5 and 6: One sender and two receivers with mapping Variant 7: One sender and two receivers with XML- Validation (see 9 8) Variant 16: One sender and two receivers with Sender EOIO and Mapping Order At Runtime for one Receiver (see 20) You can aim to learn about the following with the use cases: Represents message exchange between one sender and two receivers. The message processing is done locally on the Advanced Adapter Engine Extended. Represents message exchange between one sender and two receivers. The receivers are determined on the fly using mapping via Extended Receiver Determination. Represents message exchange between one sender and two receivers in which the way the message is forwarded to the receivers is determined by routing conditions The message processing is done locally on the Advanced Adapter Engine Extended. Represents message exchange between one sender and two receivers. A mapping is executed when the message is forwarded to one of the two receivers. The message processing and mapping are done locally on the Advanced Adapter Engine Extended. Variant 5 uses Message Mapping. Variant 6 uses Mapping based on XSL (Extensible Stylesheet Language) transformation program. Represents message exchange between one sender and two receivers. A mapping is executed when the message is forwarded to one of the two receivers. The payload is validated using XML-Validation in inbound processing of the adapter engine. The message processing, mapping and XML validation are done locally on the Advanced Adapter Engine Extended. Represents message exchange between one sender and two receivers. Sender has EOIO setting to handle EOIO message for multiple receivers. At one of receiver, Mapping Order At Runtime setting is done to check retrieved messages follow the order of definition as per the agreement. The message processing and mapping are done locally on the Advanced Adapter Engine Extended. Working with the Enterprise Services Builder Enterprise Services Repository: Understanding existing design objects Working with the Integration Builder Integration Directory: Configuring simple scenarios and understanding created configuration objects Working with the runtime: Executing the use cases and checking the results by using monitoring March

8 SAP provides the required design objects and files for these learning targets. This document contains a complete set of instructions that enable you to configure and execute the use cases without any additional special prerequisites. SAP NetWeaver Process Integration (Advanced Adapter Engine Extended) must be installed and configured, and be error free. In this respect, note the information under Within the scenarios file directories on the host of the SAP system on which the Advanced Adapter Engine Extended and the Integration Server is installed serve as the senders and receivers of messages. The use cases rely on file directories (and therefore the file/ftp adapter) to keep the technical prerequisites as simple as possible. In variants 1 to 6 the messages are sent directly from the sender adapter to the receiver adapter without using the ABAP IS runtime to show the possibility of using the Advanced Adapter Engine Extended. In variant 6 the messages are processed in sequence. In variants 7 and 8 the messages are sent from Advanced Adapter Engine Extended to the ABAP Integration Server. In variant 8 the messages are processed in sequence. This document assumes that you will configure the variants in succession, in the order specified. While it is technically possible to configure the variants in a different order, doing so would mean that the order of the step-by-step instructions in this document would no longer be correct. If you need to configure and execute the use cases as quickly as possible, skip the chapters concerning the design objects used and start instead with configuration. You can then return to the skipped chapters at a later stage for a better understanding of the various concepts. 2.2 Prerequisites General Prerequisites To configure and execute the use cases, SAP NetWeaver with usage type Process Integration and Advanced Adapter Engine Extended must be correctly installed and configured. The following table lists the prerequisites and the relevant guides: List of required steps Step 1. You have installed the Advanced Adapter Engine Extended and SAP NetWeaver Software Component version for SAP_BASIS in Sender Proxy System Documentation Master Guide SAP NetWeaver Installation Guide SAP Web AS ABAP and Java You can find the corresponding guides on SAP Service Marketplace in the Implementation Documentation Center for SAP NetWeaver 7.4 To execute variants 9 15, Sender Proxy system should have 731 version for SAP_BASIS Software Component. You can also use Application System client (e.g. 105) of a PI Dual Stack system as Sender Proxy System. 8 March 2012

9 3. You have imported the content for the Enterprise Services Repository corresponding to the latest support package/patch into the PI and the Advanced Adapter Engine Extended System. 4. You have configured the Advanced Adapter Engine Extended and SAP NetWeaver Process Integration. 5. You have configured the System Landscape Directory (SLD) for the PI and the Advanced Adapter Engine Extended System. SAP Note The simple use cases are located in the Enterprise Services Repository in the software component SAP BASIS, software component version SAP BASIS 7.40, in the namespaces m/patterns. Configuration of SAP NetWeaver Process Integration Configuring, Working with and Administering System Landscape Directory Note that you set up the use cases in your development or test system, but not in your productive system Providing the necessary User and Authorizations To log on to the SAP system to configure the simple use cases, you have to create a user XIDEMO with the following roles in the integration server client (001) and in the Advanced Adapter Engine Extended: SAP_XI_ADMINISTRATOR SAP_XI_CONFIGURATOR SAP_XI_MONITOR SAP_XI_DEMOAPP In order to receive alert mail notification the following role has to be assigned to the user also: SAP_XI_ALERT_CONSUMER Special Prerequisites for Configuring Variants 10 and 12 In Variants 10 and 12, principal propagation will be used during message processing. For this kind of data exchange trust relationship settings have to be done. These tasks need to be carried out by a system administrator because global system configuration is affected. Ask the system administrator to do the setup if you have not the rights. Maybe parts of the steps are already done! Activating Principle Propagation Trust Relationship Settings 1. Logon to the sending system (<SID>_105) 2. Call transaction STRUSTSSO2 3. Select System-PSE 4. Double_Click in the field Own-Certificate Owner 5. In the Certificate Frame press the button Export Certificate March

10 6. Logon to AEX NWA http(s)://<host>:<port>/nwa 7. Switch to tab Configuration 8. Press link Certificates and Keys 9. Select Keystore-View TicketKeystore 10. In the Details Tab create entry for <SID>_105 and upload certificate. 11. Now Maintain ACL Security Provider. 12. Go Back to the Configuration tab. Press link Trusted Systems. 13. Press button Add trusted system 14. Add <SID>, client and assign certificate to upload (certificate from <SID>_105). 15. Note the client information shown below the SID of the AEX. 16. Go Back to the Configuration tab. 17. Press link Certificates and Keys 18. Select Keystore-View TicketKeystore and select entry SAPLogonTicketKeypaircert 19. Export entry. 20. Logon to receiving system (again <SID>_105) 21. Call transaction STRUSTSSO2 22. Select System-PSE 23. Upload the certificate (which was exported at the AEX) and press button Add to Certificate List. 24. Then press button Add to ACL and enter AEX <SID> for System ID and the client number from step 15 for client. 25. Save your settings Special Prerequisites for Configuring Variant 17 In Variant 17 data will be encrypted before being persisted in the database. For this kind of encryption, the J2EE Engine needs to be configured upfront. Concretely, a secure keystore with a certain name needs to be created and a suitable key needs to be placed in that keystore. Furthermore the AEX needs to be configured to use that particular key for the process of encrypting message payloads. These tasks need to be carried out by a system administrator because global system configuration is affected. The documentation of these configuration steps is available in the appendix chapter Setting Up the File Directories The variants are based on a very simple system landscape that comprises various different file systems (on the host of the SAP system on which the Advanced Adapter Engine Extended and for variants 7 and 8 on the host where the PI Integration Server is installed). When the use cases are executed, files are moved between file directories. Therefore, to be able to configure the use cases, the file directories must have been created and described in the System Landscape Directory. Only then can you access the directories during configuration in the Integration Directory. Perform the steps below to create the required directories on the host of the SAP system on which the Advanced Adapter Engine Extended is installed. 1. Open the file directory of the SAP system, on which the Advanced Adapter Engine Extended is installed. For Example using Windows Explorer on Windows Systems. 2. Create a directory in which you can save files temporarily and create sub directories XiPatterns_AAEX and XiPatternsO_AAEX in it. 10 March 2012

11 A work directory already exists on many computers that can be used for this purpose and under which you can create the required directories. 3. Create four further sub directories in the sub directory XiPatterns_AAEX. Suggested names: XiPattern1, XiPattern2, XiPattern1_PCI, XiPattern2_PCI, XiPattern3, and XiPattern Create three further sub directories in the sub directory XiPatternsO_AAEX. Suggested names: XiPattern4, XiPattern5. You must have authorization to access this directory to be able to test the process integration scenario. Bear this in mind when you define the directory, and, if applicable, contact your system administrator. 5. Copy the following three files to directory XiPattern1 ZXiPatternSenderFile1.xml ZXiPatternSenderFile2.xml ZXIPatternSenderFile3.xml ZXIPatternSenderFileParamMap.xml ZXiPatternSenderFileMapOrderRuntime.xml 6. Copy the following file to directory XiPattern4 XiPatternSenderFilesEOIO.zip (This file contains 1000 xml files for the EOIO scenario, they will be unpacked when executing the scenario.) 7. Copy following file to directory XiPattern10 ZXIPatternSenderFile1.xml 8. Copy the following files to directory XiPattern1_PCI: ZXiPatternSenderFile2.xml These files are provided by SAP in a ZIP file. The ZIP file for 7.40 containing also the EOIO test files is available in SAP Developer Network (SDN) and can be found using the direct link SAP NetWeaver Process Integration 7.4 Test Files for Simple Use Cases Creating the Technical and Business Systems in the System Landscape Directory of the Advanced Adapter Engine Extended Perform the following steps to create the required technical and business systems in the System Landscape Directory (SLD) for the Advanced Adapter Engine Extended: 1. To call the System Landscape Directory for the Advanced Adapter Engine Extended System, open the Advanced Adapter Engine Extended Start Page using the URL: http(s)://<aaex-host>:<aaex-port>/dir. 2. Start the SLD. To do so, on the Advanced Adapter Engine Extended start page, choose System Landscape Directory. 3. Log on using the XIDEMO user you created in On the initial screen of the SLD, choose Technical Systems. 5. Create a new technical system. To do so, choose New Technical System. 6. Select the type Standalone by choosing the appropriate radio button. 7. Choose Next. 8. On the Technical System Wizard - System Details screen, enter the following information about the technical system: March

12 Technical System Identification: Enter a name according to the following naming convention: <SID>_FileSystem. In this case, <SID> is the system ID of the Advanced Adapter Engine Extended. System Host Name: Enter the host name of the Advanced Adapter Engine Extended, for example pwdf Choose Finish. 10. Now create seven new business systems. To create the first business system, on the SLD start page, choose Business Systems. 11. Choose New Business System Select the type Standalone by selecting the appropriate radio button. 13. Choose Next. 14. Select the technical system of the Advanced Adapter Engine Extended system that you defined previously (dropdown list box in field System). 15. Choose Next. 16. Enter the name <SID>_AAEX_FileSystem_XiPattern1. <SID> is the system ID of the Advanced Adapter Engine Extended System. 17. Choose Next. 18. Specify the Advanced Adapter Engine Extended System as Integration Server (field Related Integration Server). 19. Choose Finish. 20. Following the same procedure, create business systems with the following names: <SID>_AAEX_FileSystem_XiPattern2 <SID>_AAEX_FileSystem_XiPattern3 <SID>_AAEX_FileSystem_XiPattern4 <SID>_AAEX_FileSystem_XiPattern5 <SID>_AAEX_FileSystem_XiPattern10 <SID>_AAEX_FileSystem_XiPattern11 <SID>_AAEX_FileSystem_XiPattern12 <SID>_AAEX_FileSystem_XiPattern1_PCI <SID>_AAEX_FileSystem_XiPattern2_PCI Create one more technical system for the Logical system of the ABAP (ERP R/3 backend) proxy server for variants To do so, Login to the R/3 system. 2. Go to transaction /nrz Enter following details of the PI AEX system for RFC Connection to SLD. Gateway Host: Enter the host name of PI system, for example pwdf2638. Gateway Service: Enter the service of the PI System, for example sapgw10. (You can get this information from Administration -> Settings within SLD. 4. Click Start SLD Data Collection Now (F5). 5. Click Yes on confirmation pop-up. 6. Message for successful data collection will be displayed as RFC call successful. Exit the transaction. 7. Go to SLD of the Advanced Adapter Engine Extended System. To do so, on the Advanced Adapter Engine Extended start page, choose System Landscape Directory. 8. On the initial screen of the SLD, choose Technical Systems. 9. Entry as <SID> on <server> will be available as AS ABAP type in the list of Technical Systems. 12 March 2012

13 10. Now create one new business system using this Technical System. To create the business system, on the SLD start page, choose Business Systems. 11. Choose New Business System. 12. Select the type AS ABAP by selecting the appropriate radio button. 13. Choose Next. 14. Select the technical system for the R/3 Logical System that you just defined (dropdown list box in field System). 15. Select the client for the R/3 Logical System (e.g. 105) 16. Choose Next. 17. Enter the name <SID>_105. <SID> is the system ID of the R/3 server. 18. Choose Next. 19. Choose Next. 20. Specify the Advanced Adapter Engine Extended System as Integration Server (field Related Integration Server). 21. Choose Finish Defining Business System Components in the Integration Directory in the Advanced Adapter Engine Extended In the following steps you define communication components for the business systems you just created in the Advanced Adapter Engine Extended. You need to create communication components to be able to address the business systems as senders/receivers of messages when you configure the process integration scenario in the Integration Directory. To prepare the configuration of the process integration scenario, you must do the following: Define the involved business systems as communication components (business system components) in the Integration Directory Only then can you address the business systems as senders or receivers of messages. Define communication channels for outbound message processing (for all relevant receiver business systems) You define communication components in the Integration Directory of the Advanced Adapter Engine Extended. Therefore, to execute the activities described below, call the Integration Builder (user interface of Integration Directory). 1. To call the Integration Directory for the Advanced Adapter Engine Extended System, open the Advanced Adapter Engine Extended Start Page using the URL: http(s)://<aaex-host>:<aaex-port>/dir. 2. On the Advanced Adapter Engine Extended Start Page, choose the hyperlink Integration Builder (under Integration Directory). 3. Log on using the XIDEMO user you created in The system opens the Integration Builder. You use the steps below to define a communication component (business system component) in the Integration Directory for each business system. 1. Clear the SLD cache. To do this, select Environment Clear SLD Data Cache in the menu of the Integration Builder. 2. In the Integration Builder navigation area, on the Objects tab page, position the cursor on the Communication Components Without Party node. 3. To call the wizard for assigning business systems, choose Assign Business System in the context menu. 4. On the next screen, choose Continue. March

14 The business system components are not assigned to a party. 5. On the next screen, select the following business systems by using the corresponding checkboxes: <SID>_AAEX_FileSystem_XiPattern1 <SID>_AAEX_FileSystem_XiPattern2 <SID>_AAEX_FileSystem_XiPattern3 <SID>_AAEX_FileSystem_XiPattern4 <SID>_AAEX_FileSystem_XiPattern5 <SID>_AAEX_FileSystem_XiPattern10 <SID>_AAEX_FileSystem_XiPattern11 <SID>_AAEX_FileSystem_XiPattern12 <SID>_105 <SID>_AAEX_FileSystem_XiPattern1_PCI <SID>_AAEX_FileSystem_XiPattern2_PCI 6. Make sure that the checkbox Create Communication Channels for Following Adapters is deselected. The relevant communication channels are created when the process integration scenario is configured. 7. Choose Finish. The system displays the communication components in the Integration Builder navigation area, on the Objects tab page, under Communication Components Without Party Business System. Perform the following steps to activate the communication components. 1. In the navigation area, choose the Change Lists tab page. 2. Choose Open Standard Change List. 3. Check that the five communication components you just created are contained in the change list. 4. Position the cursor on the Standard Change List node and choose Activate ( ) in the context menu Special Prerequisites for Configuring Performance Monitoring Parameter Collecting data about the performance of message processing on the Advanced Adapter Engine is deactivated by default and requires activation in Net Weaver Administrator. These tasks need to be carried out by a system administrator because global system configuration is affected. The documentation of these configuration steps is available in the appendix chapter Special Prerequisites for Configuring Variants 02 In Variant 02 an Alerting Solution provides local alert handling within multiple registered alert queues to enable multipurpose alert consumers. This is achieved by providing new configuration object Alert Rule in PI directory. A support user configures alert rules using NWA Alerting Configuration or Integration Directory. According to configuration of the alert rules, it is triggered when an error occurs during the message sending (in this case due to Duplicate message) and alert notification is sent to the users involved in the alert configuration. 14 March 2012

15 General Requirements 1. NWA alerting settings check (AEX system): Start NWA using where the host and port are the http host and port. Login if necessary. Navigate to Configuration -> Infrastructure Click link Java System Properties Select Services tab. Search for XPI Service: AF Core. In the Extended Details area bellow in the Properties tab all properties of this service are displayed. The following properties values have to be as described below: alerting.isactive ->true alerting.target -> 1 If the properties values are different require from the system administrator to set them as it is described above. Then, the system has to be restarted AEX must be configured to send s. To check this, go to NWA -> Configuration -> Infrastructure -> Java System Properties. Search for Java Mail Client under tab Services. Check if property mail.smtp.host is set to mail.sap.corp. If the properties values are different require from the system administrator to set them as it is described above. Settings for Consuming Alerts By setting an alert rule to use a local alert consumer and scheduling a dedicated background job you can configure a simple notification mechanism. Using this mechanism the system would generate notifications upon message alert events, and would send these notifications via to users who should receive them. The following steps should be executed on the AEX system. Prerequisites The SAP_XI_ALERT_CONSUMER and NWA_SUPERADMIN roles are needed to schedule the job for sending s and consuming the alerts which will be sent via the . Make sure the alert rules for which you need to configure notification meet all of the following requirements: The alert consumer and all other rule parameters are configured as needed. The alert rule is enabled and activated. Procedure 1. Open a browser and go to to access SAP NetWeaver Administrator. 2. Choose Operations->Job->Java Scheduler->Job Definitions and make sure the AlertConsumerJob job is present. 3. Choose the Tasks tab and then choose the Add button. Create a new task. 4. Select the AlertConsumerJob job and enter: Name - you can monitor your job in Jobs tab, so you need a distinct name to recognize it Description March

16 5. Retention period for the task - specifies the days, for which job logs are persisted in database. The default is 23; 0 does not keep job logs; -1 keeps the logs forever. You better use a positive integer value, to be able to view the logs in case of a failing job 6. On the Set Properties step enter the following information: 7. In the MailTo field, enter the addresses (separated with comma) of all users that should receive notifications. 8. In the MailFrom field, enter the address of the use that should appear as sender in the notifications. 9. In the AlertToMailLimit field, enter the number of individual message details that would be included in the notification. The default value is 0. You can use 20 for example. 10. In the Consumer field, enter the name of the local alert consumer specified for the alert rule. 11. Set the task execution time (better a bigger one 1 or 2 hours with time repetition 10 or 15 minutes). 12. Choose Finish to save the task. 2.3 Design Objects Used This section explains all the design objects that are used for describing the variants. The subsequent description of each variant will refer to the description in this section; the relevant design objects will only be listed briefly in each case. Process Integration Scenario/Component View A process integration scenario describes the process flow and represents the points in the process flow at which messages are exchanged between application components (in this case, the application components Sender and Receiver). Component View File2File_NoMapping represents the variant with message exchange between Advanced Adapter Engine Extended and the PI System, whereas the Component View File2File_NoMapping_InOrder represents the variant with message exchange in EOIO. The variants only running locally in the Advanced Adapter Engine Extended are not based on component views because they are using the integrated configuration. Interface Objects Interface objects describe the communication mode and the data structure for exchanging messages. Interface objects comprise service interfaces, message types, and data types, which you can open by means of forward navigation, starting with the Service Interfaces. Mapping Objects If the interfaces at the sender and receiver are different, a mapping is required. Communication Channel Templates You use communication channel templates to define details, which were defined when the process integration scenario was defined, for the inbound or outbound processing of the message. You can then use the communication channel template to create the corresponding communication channel when configuring in the Integration Directory. You then need to specify all the details, which are only known at configuration time, in the communication channel. The specific design objects will be listed in the specific variants below. 3 Variant 1: One Sender and One Receiver using the Advanced Adapter Engine 16 March 2012

17 Extended This variant enables you to configure and execute the simplest kind of message exchange: One sender (file directory XiPattern1) sends a message to one receiver (file directory XiPattern2). Hereby, the message is exchanged between sender and receiver adapter by using one Advanced Adapter Engine Extended. No mapping is executed between the outbound and inbound interface in this variant. 3.1 Design Objects Used This section explains all the design objects that are used for describing this variant. There is a step-by-step description of how to access each object. SAP recommends that you follow these steps directly in the system. The subsequent description of each variant will refer to the detailed step-by-step description in this section; the relevant design objects will only be listed briefly in each case. You use the component view File2File_NoMapping in process integration scenario XiPatternOneStepScenario to configure this variant. The following graphic shows the component view: The following describes all the objects that describe the message exchange in this variant in turn. Starting with the process integration scenario (component view), you can open all the objects that the component view uses. 1. To call the Enterprise Services Builder (user interface of the Enterprise Services Repository) for the Advanced Adapter Engine Extended System, open the Advanced Adapter Engine Extended Start Page using the URL: http(s)://<aaex-host>:<aaex- Port>/dir.. 2. On the Process Integration Tools page, choose Enterprise Services Builder under Enterprise Services Repository. 3. In the navigation area, open the software component SAP BASIS, software component version SAP BASIS 7.40, and namespace 4. Open the node Process Integration Scenarios. 5. Open process integration scenario XiPatternOneStepScenario by double-clicking. The process integration scenario editor is opened. March

18 Process Integration Scenario/Component View A process integration scenario describes the process flow and represents the points in the process flow at which messages are exchanged between application components (in this case, the application components Sender and Receiver). Specific communication variants are represented by different component views. Component View File2File_NoMapping represents the three variants without a mapping. Component View File2File_WithMapping represents the variant that includes a mapping. Ensure that component view File2File_NoMapping is displayed in the graphical editor. If it is not displayed, choose the component view in the preview area on the left by double-clicking. The component view comprises two actions Send Message 1 and Receive Message 1, which are linked by an asynchronous communication step (angled arrow). Interface Objects Interface objects describe the communication mode and the data structure for exchanging messages. Interface objects comprise service interfaces, message types, and data types, which you can open by means of forward navigation, starting in the component view. 1. To open the interface objects used, double-click the connecting arrow in the component view. The connection editor is displayed. The service interfaces for the sender and receiver are displayed on the Assign Interfaces tab page: in the case of the sender, it is the outbound interface XiPatternInterface1 and in the case of the receiver, it is the same inbound interface XiPatternInterface1. Since the interface is the same for both the sender and receiver, no mapping is required. 2. To open the service interface XiPatternInterface1, double-click the interface name. 3. In the Service Interface editor you can see that it is an abstract interface. The interface is abstract because the interface description is not implemented in the relevant software component. 4. To open the message type, double-click the name of the message type XiPatternMessage1 (in the service interface editor under Messages). In the Message Type editor, you can display the data structure of the message. The data structure is defined by the data type XiPatternDataType1. Information about a person is structured by different elements in the data structure of the exchanged message. Details such as the maximum character length are displayed in the Details column. Mapping Objects If the interfaces at the sender and receiver are different, a mapping is required. Navigate to the connection editor and choose the Assign Mapping tab page. You can see that a mapping has not been assigned for the connection between the two (identical) service interfaces. Communication Channel Templates You use communication channel templates to define details, which were defined when the process integration scenario was defined, for the inbound or outbound processing of the message. You can then use the communication channel template to create the corresponding communication channel when configuring in the Integration Directory. You then need to specify all the details, which are only known at configuration time, in the communication channel. 1. In the connection editor, choose the Assign Communication Channel Template tab page. One communication channel is specified for both the sender and receiver: (XiPatternChannel_FileSender for the sender, XiPatternChannel_FileReceiver for the receiver. 2. To open a communication channel template (for example, for the sender), double-click the name. Further details are displayed in the Display Communication Channel Template editor. 18 March 2012

19 3. Close all objects and the process integration scenario. Summary of Design Objects Used The design objects used are summarized once more in the following table. Design Objects Used For a general description of the various object types, see SAP Help Portal at: Enterprise Services Repository Object Type (Name) Process Integration Scenario (XiPatternOneStepScenario) Service Interface (XiPatternInterface1) Message Type (XiPattermMessage1) Data Type (XiPatternDataType1) Communication Channel Templates for Sender and Receiver (XiPatternChannel_FileSender, XiPatternChannel_FileReceiver) Description Describes the process flow and indicates the points at which messages are exchanged between the different components. The component view File2File_NoMapping in particular describes all variants in which no mapping is executed (interfaces at the sender and receiver are identical). Specifies the communication mode (asynchronous) and references the message type used. Describes the message sent at runtime and references the data type used. Describes the data structure of the message Specifies the sender (and receiver) adapter configuration details, which are defined at design time. Communication channel templates enable a communication channel to be preconfigured at design time. 3.2 Configuring the Process Integration Scenario In configuration, you translate the process described by the process integration scenario (component view) to an actual system landscape. You have already described the system landscape in the SLD. The communication components you defined earlier enable you to address the involved business systems as senders/receivers of messages in the Integration Directory. You use the model configurator for the whole configuration procedure. This tool enables you to use a process integration scenario from the Enterprise Services Repository as a configuration template and to add further information (which is not known until configuration time). You perform the following configuration steps in the Integration Directory of the Advanced Adapter Engine Extended. For this scenario, the integrated configuration object is used for configuration. For more information, see Defining the Integrated Configuration. Calling the Integration Directory First, call the Integration Directory. To call the Integration Directory for the Advanced Adapter Engine Extended System, open the Advanced Adapter Engine Extended Start Page using the URL: http(s)://<aaex-host>:<aaex-port>/dir. March

20 Selecting the Process Integration Scenario Perform the following steps to select the process integration scenario that you want to configure from the Enterprise Services Repository. Also, enter the name of the configuration scenario (in the Integration Directory) in which you want to group the configuration objects. 1. To call the model configurator, choose Tools Apply Model from ES Repository in the Integration Builder menu bar. This calls a wizard, which you use to select a model (in this case, a process integration scenario) and create a configuration scenario in the Integration Directory. 2. Make sure that the model type Process Integration Scenario is selected (radio button under Type of ES Repository Model). 3. Choose the input help (for the Name field) ( ) This calls an input help, which displays all process integration scenarios from the Enterprise Services Repository in a list. 4. Select the process integration scenario XiPatternOneStepScenario (software component version SAP BASIS 7.40, namespace from the Enterprise Services Repository and choose Apply. 5. Choose Continue. 6. Enter the name of the configuration scenario as: XiPatternOneStepScenario_AAEX. 7. Choose Finish and then Close. The system calls the model configurator. Selecting the Component View Check whether the component view File2File_NoMapping is displayed. If it is not, choose the menu option Select Component View ( ). On the subsequent screen, select the component view (in the preview area) by double-clicking. Assigning Communication Components You perform the following steps to assign communication components to the application components of the process integration scenario. You use the business system components that you created before (see 2.2.7). 1. In the graphical editor, click on the lane representing the Sender application component. This calls the Assign Business System Component dialog box for the Sender application component (below the graphical representation of the process integration scenario). 2. To assign a communication component click in the input field in the Communication Component column and call the input help ( ). 3. In the subsequent screen, select the communication component <SID>_AAEX_FileSystem_XiPattern1 and then choose Apply. 4. Choose Next Role ( ) to navigate to the configuration dialog for the application component Receiver. 5. Assign the communication component <SID>_AAEX_FileSystem_XiPattern2 to the application component Receiver. Follow the same procedure as when assigning the communication component to the application component Sender. 6. Choose Assign. Configuring the Connection You perform the following steps to configure the connection of the process integration scenario. You activate the relevant sender-receiver relation (between the sender and receiver component) and assign both the sender and receiver a (sender or receiver) communication channel. You create the communication channel on the basis of the communication channel templates that the process integration scenario already contains. 1. In the graphical editor, click on the connection between the lanes representing the two application components. 20 March 2012

21 2. This calls the Configure Connection dialog box for the connection between the actions (below the graphical representation of the process integration scenario). 3. On the Configure Connections screen, choose the tab page Connections from Component Assignment. The communication components that you assigned in the previous configuration step are displayed. The remaining tab pages contain further information about the process integration scenario, for example, the communication channel templates that are defined for the process integration scenario in the Enterprise Services Repository. 4. Assign the sender a communication channel. To do so, place the cursor in the field Communication Channel for the Sender Component, in the push button bar choose Create Communication Channel With Template ( ). In the subsequent wizard you can create a communication channel based on a communication channel template. 5. Choose Continue. The default communication channel template on the subsequent screen is that which was assigned to the sender application component in the process integration scenario (name XiPatternChannel_FileSender, software component version SAP BASIS 7.40, namespace 6. Choose Continue. The default name for the communication channel on the next screen is XiPatternChannel_FileSender. 7. Confirm your selection by choosing Finish. 8. Following the same procedure (see step 4-7), assign the application component of the receiver a communication channel (XiPatternChannel_FileReceiver) based on the default communication channel template (name XiPatternChannel_FileReceiver, software component version SAP BASIS 7.40, namespace Generating the Configuration Objects In the following steps, you generate the relevant configuration objects based on the settings made in previous steps. 1. If not already selected, select the flag for Configuration for Advanced Adapter Engine. 2. Choose the push button Create Configuration Objects ( ). 3. Under General, select the radio button Generation. 4. Choose Start. The integrated configuration objects are generated based on the settings you made. Once generation is complete, the generation log is opened. The generation log displays the results of generation. The generation log enables you to analyze any errors that occurred during generation. 5. Close the generation log. 6. Close the model configurator. Choose Apply. 7. Save the configuration scenario. Manual Editing In the following steps, you edit the generated configuration objects manually and enhance the configuration settings made during generation. In this variant, you must edit the communication channels after generation. 1. In the editor Display Configuration Scenario (for the open scenario XiPatternOneStepScenario_AAEX), on the tab page Objects, open the communication channel ( ) XiPatternChannel_FileSender by double-clicking. 2. Under File Access Parameter in the Source Directory field, enter the path in the file directory that you defined previously (see 2.2.4). In the case of the sender March

22 communication channel, enter the whole path for the file directory XiPattern1. Example: C:/<selected path>/xipatterns/xipattern1 3. Save the communication channel. 4. Activate it by using the menu Communication Channel Activate. 5. To check if the channel works you can directly jump to the channel monitoring using the menu path Communication Channel Channel Monitoring 6. The PI Communication Channel Monitoring page will open up where you can do a self test for the channel. To do this click on the button Ping Channel. 7. The status page for the channel will show up with detailed information of the executed self test. 8. Following the same procedure, edit the communication channel XiPatternChannel_FileReceiver (communication component <SID>_AAEX_FileSystem_XiPattern2). Enter the path for the file directory XiPattern2. 9. Save the communication channel and activate it. 10. Open the Channel Monitoring and check the status of the channel. Activating the Change List 1. To do this, select the Change Lists tab page in the Integration Directory navigation area. 2. Choose Open Standard Change List. 3. Position the cursor on the Standard Change List node and choose Activate ( ) in the context menu. 3.3 Executing the Use Case You perform the following steps to check that the use case is executed without errors. 1. On the host of the Advanced Adapter Engine Extended, open the file directory XiPattern1. 2. Rename the file ZXiPatternSenderFile1.xml as XiPatternSenderFile1.xml. The File/FTP adapter is designed in a way that a file with exactly this name is recognized and moved from the source directory XiPattern1 to the target directory XiPattern2 every 60 seconds. If the configuration was executed without errors, the file will be moved from the source directory within 60 seconds after it is renamed. 3. Open the directory XiPattern2 and check that the file has arrived. 4. Open the file and check whether the content has changed (compare with the original file ZXiPatternSenderFile1.xml). The file must not have been changed when this variant is executed. Furthermore, you can check the processing in the message in monitoring. To do this, proceed as follows: 1. Start the Monitoring by choosing Configuration and Monitoring Home on the Advanced Adapter Engine Extended start page. 2. Choose Message Overview. 3. Select Database. 4. Use appropriate filter criteria to restrict the number of XML messages displayed (for example, the processing period). 5. Choose Go. The system displays the selected messages in a table. You want to locate the messages that were sent during execution. 6. Select the message to be displayed by selecting the appropriate radio button and then choose Open Message. 22 March 2012

23 A new window will appear. The tab Payloads displays the message contents for the various versions of the message during processing. Close the window. 7. Click on the button Open Settings Dialog. The Settings Pane will appear. Under the tab Column Selection -> Hidden Columns select the columns - Message Size(byte), Duration(ms) and Server Node then click on the button Add Item. As a result the columns would be transferred to the section Displayed Columns. Click on OK. 8. The table - Message List will have the above 3 columns added in the end. Verify populated values. The same are present as attributes with corresponding values under the tab Message details. The added 3 columns will be saved for your user. Verify by logging off from the system and logging in back go to SOA -> Message Monitor -> Database tab -> the message list table will have the columns shown. Check Performance Monitoring of the message in NWA/PIMON Performance Monitoring is often required to gauge the performance of the Adapter Engine by measuring the bytes processed over a given time period. It would be a useful piece of information for the Administrators to get an idea about time spent by messages in various stages of its lifecycle. Performance Monitoring for message exchange can be done for parameters as 1) Message put in to the queue 2) Message retrieved from the queue and 3) 'Call Sap Adapter' module. 4) Any other custom module. To start Performance monitoring proceed as follows: 1. Start the Monitoring by choosing Configuration and Monitoring Home on PI Tools Home Page 2. Choose Monitoring -> Adapter Engine 3. Click on link Performance Monitor. New Screen opens up titled PI Performance Monitoring: Overview 4. Click on button Advanced Selection and Filter for Receiver Channel XiPatternChannel_FileReceiver in Outbound Channel Field 5. Entries with respect to above filter criteria are displayed in an hourly interval aggregation. Table will display following details of Message flow in the aggregation intervals a. Message Size (Bytes) b. Average Processing Time (Milliseconds) c. Total Processing Time (Milliseconds) 6. Select one entry of the Table. Message Scenario table with further details (directory objects involved in message flow) along with Average Message Size and Total Message size value will be displayed. An entry within this table is automatically selected. 7. Further another table titled Message Processing Details is displayed for above entry. This table has two tabs. a. Module Information tab - Information about time taken (Minimum Time, Maximum Time and Average Time) by different modules to process the message. Check existence of following modules i. Module:CallSapAdapter ii. MS:Message_Put_In_Queue iii. MS: Message_Remove_From_Queue iv. Optional other custom module if Channel processing this message has custom adapter module March

24 b. Message Information tab - Information about size of message. Value in this is same as per first table. 8. Use appropriate filter criteria (for example, the processing period) and check for more message and their performance parameters. 9. A field Aggregation Interval is available to provide the time that db will write out collected performance data to disk, and therefore allow it to be visualized on UI. Aggregation Interval varies as per selection of Time Interval. Check for following combination of Time Interval and their corresponding Aggregation Interval a. Last 12 Hours 15 Minutes and 1 Hour b. Today 15 Minutes, 1 Hour and 1 Day c. Yesterday 1 Hour and 1 Day d. Last Seven Days 1 Hour and 1 Day e. This Week 15 Minutes, 1 Hour and 1 Day f. Last Week 1 Hour and 1 Day g. This Month 15 Minutes, 1 Hour and 1 Day h. This Year 15 Minutes, 1 Hour and 1 Day i. User-Defined Selection - 15 Minutes, 1 Hour and 1 Day along with an option to Select Start Date/Time and End Date/Time 10. Open Performance Monitoring in NWA via http(s)://<host>:<port>/nwa -> SOA -> Monitoring -> PI Performance Monitoring 11. Repeat Steps 3 9 and Compare UI and displayed data. It should be same 3.4 Virus-Scanning for Messages: The Virus Scan Interface that is part of SAP NetWeaver allows you to include external virus scanners in an SAP system and to scan files or documents processed by SAP applications for viruses. In order to test the Virus Scanning of Messages on the JAVA side we consume the above simple scenario & enhance it. In the message payload, the virus is attached [treated as malicious by the Virus Scanner not a real virus]. Prerequisites: To test this scenario a virus scanner needs to be configured first 1. To configure the Virus Scan Interface in the Java environment, NWA is needed to define the required settings for scanner groups (NWA Configuration Security Virus Scan Provider), the virus scan adapter and scan profiles. The configuration of the Virus Scan Provider service is stored in the Configuration Manager of the JEE Engine. New PI Virus Scan Profile Profile Name pi_messaging Profile Description Process Integration Messaging Reference Profile <Default Profile> 2. Logon to SAP NetWeaver Administrator and go to Configuration Infrastructure Java System Properties.Search for service XPI Adapter: XI and specify the following Java system properties (see table). Service Property Possible Values XPI Adapter: XI xiadapter.virusscan.active 0 - inactive (default) 1 - active XPI Adapter: XI xiadapter.virusscan.profile pi_messaging (default) 24 March 2012

25 XPI Adapter: XI xiadapter.virusscan.mode 1 - attachments (default) 2 - attachments + main payload XPI Adapter: XI xiadapter.virusscan.content_type 1 - binary (default) 2 - all content types Modifying the Configuration: In this scenario we check the Virus scanning of the Messages - Specific to the Scenario [Virus scanning can be enabled Globally or Specific to scenario]. Scenario Specific virus scanning can be achieved at both Inbound and Outbound Processing. 1. In the Integration Directory main menu, open the integrated configuration object <SID>_AAEX_FileSystem_XiPattern1 / XiPatternInterface1 / 2. Switch to change mode ( ). 3. In tab Inbound Processing Tab, Go to the Virus Scan field and for the scenario specific, choose the option Virus scan by Adapter for scanning the infected message.(you can also try the Virus scan configuration at the Outbound Processing Tab). 4. Save the integrated configuration. Activating the Change List 1. To do this, select the Change Lists tab in the Integration Directory navigation area. 2. Choose Open Standard Change List. Position the cursor on the Standard Change List node and choose Activate ( context menu. )) in the Execution: The scenario will be executed with following different ways 1. Sending virus within main payload. 2. Sending virus within the attachment. 3. Sending infected payload without activating virus scanner. 4. Sending message after deleting virus from the main payload and attachment and then retest Sending virus within main payload 1. In order to test the virus scanner send the infected payload as given below. X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H* For sending, place above content in a file and name the file as XiPatternSenderFile.xml and place it at sender location. 2. In the sender channel, change the name of sender file. Save and activate. 3. Start the Communication channels consumed in the scenario. On starting these channels the virus scanner will scan the infected messages and throw the error at the sender channel. Sending virus within attachment You can also try the virus scanner functionality with the attachment of another file with the main payload and try to send the message as described in the execution step. 1. Open the sender channel in edit model. 2. Under source tab Click on the Additional file(s). 3. Under File List, enter a name of your choice for each additional file. 4. Now add four different fields and its value. March

26 Name Additional_File.namePart Additional_File.optional Additional_File.type Additional_File.encoding Value ".xml"="_test.xml" NO BIN UTF-8 For more information, see Specifying Additional Files in the Sender File Adapter. 5. The file XiPatternSenderFile_test.xml is the file attached with the main payload. For creation of attachment file, place the content(eicar string) given below in a file and name it as XiPatternSenderFile_test.xml and place the file at sender location. X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H* 6. Save and activate. 7. Now start the channels to see scanning of the infected file. 8. After message flow on sender, you will see error thrown on sensing the virus: Sending infected payload without activating virus scanner 1. Open the integrated configuration object <SID>_AAEX_FileSystem_XiPattern1 / XiPatternInterface1 / 2. Switch to change mode ( ). 3. In tab Inbound Processing Tab, Go to the Virus Scan field and for the scenario specific, choose the option No Virus scan.(you can also try the Virus scan configuration at the Outbound Processing Tab) save and activate. 4. Start the channel and check whether the infected file is getting scanned or not on setting the No virus scan in The Integrated Configuration. The channels should be successfully executing without detecting virus in the file. Sending message after deleting virus from the main payload and attachment and then retest 1. Edit sender communication channel and place file XiPatternSenderFile1.xml in the File name field and unmark the additional file option. 2. Start the communication channels consumed in the scenario. Now check whether the message is processed successfully. The channel should be successfully processed the message. 4 Variant 2: One Sender and Two Receivers using the Advanced Adapter Engine Extended with Duplicate Message Handling This variant extends variant 1 by adding an additional receiver. The message is sent from the sender to two receivers using the Advanced Adapter Engine Extended, without a mapping being executed at runtime. One sender (file directory XiPattern1) sends a message to two receivers (file directory XiPattern2 and XiPattern3). The message is exchanged between sender and receiver adapter using the Advanced Adapter Engine Extended. No mapping is executed between the outbound and inbound interface in this variant. 26 March 2012

27 The variant also involves the feature to avoid/control the processing of duplicate messages using the File/FTP Sender Channel. It also provides flexible threshold configuration and channel deactivation (if threshold exceeds) options Field Enable Duplicate Handling Duplicate Message Alert Threshold Disable Channel if threshold exceeded Description To enable the Duplicate Message Handling feature It will process the given number of duplicates and if the duplicate count exceeds, the subsequent message will be ignore and alerts will be created The channel will become inactive status and no more processing is allowed If this feature is enabled, file/ftp sender channel determines if the current file is a duplicate of an already processed file. If it is a duplicate, it will ignore and create an alert based on the configuration. The duplicate file is identified by the combination of the following file properties. Fully qualified path including file name (with extension) Size Last modified time stamp If any of these properties gets changed, the duplicate count also reset and considered as a new file 4.1 Design Objects Used In this variant the same interfaces are used as in variant Configuring the Process Integration Scenario When you configure this variant, you will extend the configuration settings from variant 1. You use the same configuration scenario XiPatternOneStepScenario_AAEX as in variant 1. Opening the Configuration Scenario In this variant, the configuration scenario XiPatternOneStepScenario_AAEX created in variant 1 is extended. The integrated configuration object is used again for configuration of this scenario. For more information, see Defining the Integrated Configuration. Opening the Configuration Scenario Perform the following steps to open the configuration scenario that you created in variant In the Integration Directory, open configuration scenario XiPatternOneStepScenario_AAEX. To do so, in the Integration Directory navigation area, choose the tab page Scenarios and open the configuration scenario XiPatternOneStepScenario_AAEX by double-clicking. March

28 If you followed the configuration sequence suggested in this document, the configuration objects that were generated in variant 1 are displayed in the configuration scenario. 2. Change to Edit Mode. 3. Start the model configurator. To do so, press the button Model Configurator. The model configurator loads the same process integration scenario as in variant 1. Selecting the Component View Check that the component view File2File_NoMapping is selected. If it is not, under Configuration Steps, choose the menu option Select Component View. On the subsequent screen, select the component view (in the preview area) by double-clicking. Assigning Communication Components Additionally, assign the application component Receiver the business system component <SID>_AAEX_FileSystem_XiPattern3. Configuring the Connection The communication channels selected for variant 1 are displayed for the relation from sender communication component <SID>_AAEX_FileSystem_XiPattern1 and receiver component <SID>_AAEX_FileSystem_XiPattern2. If this is not the case, select them again by using the input help. For the relation from the sender component <SID>_AAEX_FileSystem_XiPattern1 and receiver component <SID>_AAEX_FileSystem_XiPattern3, proceed as follows: Assign the communication channel XiPatternChannel_FileSender (communication component <SID>_AAEX_FileSystem_XiPattern1) that you created previously to the sender component. To do so, position the cursor on the input field in the column Communication Channel (in the composite column Sender Business System Components for A2A) and call the input help ( ). Using the communication channel template, create a new communication channel for the receiver communication component <SID>_AAEX_FileSystem_XiPattern3. To do so, proceed as described in variant 1. Generating the Configuration Objects Proceed as described in variant 1. Once you have checked the generation log, close it and save the configuration scenario. Manual Editing Manually edit the new communication channel XiPatternChannel_FileReceiver for communication component <SID>_AAEX_FileSystem_XiPattern3 as in variant 1. Under File Access Parameter in field Source Directory, enter the path for the file directory XiPattern3 (see 2.2.5). Save the channel and execute the Channel Ping as described in the variant 1. Also edit the Sender Communication channel XiPatternChannel_FileSender (communication component <SID>_AAEX_FileSystem_XiPattern1). Go to the Processing tab -> check the check box Enable Duplicate Handling, enter the Duplicate Message Alert threshold as 2 and check the check box Disable channel if threshold is exceeded. Save the channel and execute the Channel Ping as described in the variant 1. Alert Rule creation and configuration 28 March 2012

29 1. In the Integration Builder menu select Objects->New 2. In the Create Object window select Alert Rule node and enter the rule s name. 3. Press Create button. 4. In the Edit Alert Rule view under the Basic tab enter the following parameters Severity: Low Enabled: No Payload in Alert: Disabled Assigned Configuration Objects Business System: <SID>_AAEX_FileSystem_XiPattern1 Business System: <SID>_AAEX_FileSystem_XiPattern2 Business System: <SID>_AAEX_FileSystem_XiPattern3 Integrated Configuration: Integrated Configuration for the scenario 5. Under Extended tab select all checkboxes and choose the consumer from the value help button. You should first enable the Add Consumer option from Edit menu of the alert rule, then select the + button and click on the value help button to select the consumer (if you prefer to use a different than the default consumer, you should enter its name manually). 6. Save and activate the created Alert Rule <User>_Alert_Rule 7. Select the alert rule and copy it to a new alert rule 8. Save and activate the newly created copy of the alert rule Activating the Change List 1. To do this, select the Change Lists tab in the Integration Directory navigation area. 2. Choose Open Standard Change List. 3. Position the cursor on the Standard Change List node and choose Activate ( )) in the context menu. 4.3 Executing the Use Case Mass consistency check of the alert rules First, validate the consistency of the alert rule: 1. Navigate to NWA -> SOA -> Monitoring -> Message Alert Configuration on the AEX system 2. Select all of the rules using the button in the upper-left corner of the table with alert rules 3. Select Check Consistency button to perform the consistency checks 4. In the pop-up select the checkboxes for disabled rules and for overlapping rules 5. Select Run button 6. As s result a new pop-up appears displaying the problematic alert rules check if the created on previous steps alert rules are under groups Disabled Rules and Overlapping Rules, Group X 7. Close the pop-up 8. Delete the copy of the alert rule (in Integration Directory, as it was created there; activate the changelist) 9. Select the original alert rule <User>_Alert_Rule and enable it (choose Edit then Yes from drop-down menu for Enabled ) 10. Save and activate the alert rule using the respective buttons 11. Perform the mass consistency check again 12. Copy Of the alert rule should not be in the list with problematic alert rules and <User>_Alert_Rule should not be under Disabled Rules node March

30 4.3.2 Execution and Verification You perform the following steps to check that the process integration scenario is executed without errors. As for the execution of variant 1, in directory XiPattern1, copy the file ZXiPatternSenderFile1.xml and rename it XiPatternSenderFile1.xml. The file will be moved from the directory within the next 60 seconds. Since this variant has two target directories (receivers), check whether the file has arrived in both directories XiPattern2 and XiPattern3. The file should be available in both directories. The content of the xml file should not change as no mapping is executed. Check the message monitoring as described for variant 1. The message monitoring will display two messages, one for each of the receivers. In this variant, two messages are created from the outbound message (one for each receiver). After the file XiPatternSenderFile1.xml has been processed the first time, to test the feature of Duplicate Message handling, verify the following for the above scenario: Note: The First Message (created from a file) will be always referred as Original Message The Second Message (Created from the same file) will be referred as First Duplicate Message and the current duplicate count is 1 Verification: 1. The file will be processed only 3 times (Original Message + 2 Duplicates) 2. All other messages after starting from the First Duplicate will give a warning message. 3. Channel will be inactive status with errors (after threshold value exceeds the duplicate count) 4. Since Channel is in inactive status, it won t process the further messages 5. Duplicate alerts are sent to alert inbox Note: The same error message will be available in alert inbox also. You can also try different scenarios with different values for handling Duplicate message: 5 Variant 3: One Sender and Two Receivers 30 March 2012

31 using Advanced Adapter Engine Extended with Routing Condition This variant extends variant 2 by adding a routing condition. Depending on the condition, the message is sent to one of the two receivers. 5.1 Design Objects Used In this variant, the same interfaces are used as in variant Configuring the Process Integration Scenario When you configure this variant, you will extend the configuration settings from variant 1 and 2. You use the same configuration scenario XiPatternOneStepScenario_AAEX. Using the Configuration Scenario In this variant, the configuration scenario XiPatternOneStepScenario_AAEX created in variants 1 and 2 is extended. For this scenario, again the integrated configuration object is used for configuration. Changing the Integrated Configuration 5. In the Integration Directory main menu, open the integrated configuration object <SID>_AAEX_FileSystem_XiPattern1 / XiPatternInterface1 / 6. Switch to change mode ( ). 7. In tab Receiver, select the cell for the receiver component <SID>_AAEX_FileSystem_XiPattern2 in the column Condition. 8. Call the condition editor by choosing the input help icon ( ). 9. In the column Left Operand, call the expression editor by choosing the input help icon ( ). 10. In the expression editor, select the XPath radio button. The data structure of the message is displayed. 11. Expand the structure and select the element CountryCode by using the cursor. 12. Choose OK. 13. In the condition editor, choose the operator = in the column Op. 14. In the column Right Operand, enter US. 15. Choose OK. You have specified the routing condition CountryCode = US. At runtime, messages that have the value US entered for the element CountryCode are sent to receiver <SID>_AAEX_FileSystem_XiPattern Following this procedure, create the routing condition CountryCode = DE for the configured receiver <SID>_AAEX_FileSystem_XiPattern Save the integrated configuration. Activating the Change List 3. To do this, select the Change Lists tab in the Integration Directory navigation area. 4. Choose Open Standard Change List. 5. Position the cursor on the Standard Change List node and choose Activate ( )) in the context menu. March

32 5.3 Executing the Use Case You perform the following steps to check that the process integration scenario is executed without errors. In directory XiPattern1, copy the file ZXiPatternSenderFile1.xml and rename the copied file XiPatternSenderFile1.xml. The file will be moved from the directory within the next 60 seconds. Check whether the file has arrived in directory XiPattern2. Open the file and check that the country code US is entered in the personal data. There should be no file in directory XiPattern3. Message monitoring contains one entry for this exchange of messages. You can repeat this procedure for file ZXiPatternSenderFile2.xml. This file should arrive in directory XiPattern3 (contains personal data with the country code DE). 5.4 Copy configuration scenario with content Integration Builder provides a tool to copy objects of a configuration scenario to another business system along with adjustment to new system landscape (system names, channel configuration, collaboration agreements etc) thus greatly saving time. You perform the following configuration steps in the Integration Directory of the Advanced Adapter Engine Extended. Calling the Integration Directory First, call the Integration Directory. To call the Integration Directory for the Advanced Adapter Engine Extended System, open the Advanced Adapter Engine Extended Start Page using the URL: http(s)://<aaex-host>:<aaex-port>/dir. Creating Configuration Scenario with content 1. Open Configuration Scenario XiPatternOneStepScenario_AAEX created and executed in previous section. 2. Go to menu Configuration Scenario -> Refactor. A wizard Refactor Configuration Scenario appears with detailed information about what this tool will do. Click on Continue. 3. Enter XiPatternOneStepScenario_AAEX_Copy as Target Configuration Scenario and click Continue. 4. In the wizard, three business systems used in source configuration scenarios are displayed with an option to select target communication components. It also displays all the objects referencing the selected communication components. 5. Using input help, select target business systems as per below table and click Continue. Current Value <SID>_AAEX_FileSystem_XiPattern1 <SID>_AAEX_FileSystem_XiPattern2 <SID>_AAEX_FileSystem_XiPattern3 Target Value <SID>_AAEX_FileSystem_XiPattern10 <SID>_AAEX_FileSystem_XiPattern11 <SID>_AAEX_FileSystem_XiPattern12 6. The wizard displays a preview of objects being created and reused in the configuration scenario XiPatternOneStepScenario_AAEX_Copy. One Sender and two receiver channels are created alongwith an Integrated Configuration & Configuration Scenario. Click Finish to trigger creation of objects. 7. A summary is displayed for the objects (Channels, Integrated Configuration and Configuration Scenario) created. Click Close. 32 March 2012

33 8. The Target Configuration Scenario is displayed. This new scenario contains exactly same number of objects as per original one. 9. Activate the configuration scenario with all underlying objects (Channels and Integrated Configuration). Manual Editing Manually edit the new communication channel XiPatternChannel_FileSender for communication component <SID>_AAEX_FileSystem_XiPattern10 as in variant 1. Under File Access Parameter in field Source Directory, enter the path for the file directory XiPattern10 (see 2.2.5). Save and Activate the channel. Execution You perform the following steps to check that the newly process integration scenario is executed without errors. In directory XiPattern10, copy the file ZXiPatternSenderFile1.xml and ZXiPatternSenderFile2.xml. Rename the copied files to XiPatternSenderFile1.xml and XiPatternSenderFile2.xml respectively. Both the files will be moved from the directory within the next 60 seconds. Check whether the file arrived in directory XiPattern2 contains personal data with the country code US and in directory XiPattern3 contains personal data with the country code DE. Message monitoring contains two entries for this exchange of messages. Rename the files XiPatternSenderFile1.xml & XiPatternSenderFile2.xml back to ZXiPatternSenderFile1.xml & ZXiPatternSenderFile2.xml respectively to stop continuous flow of messages. 6 Variant 4: One Sender and Multiple Receivers using Advanced Adapter Engine Extended with Dynamic Receiver Determination This variant is an alternative to variant 3 to use a dynamic receiver determination via mapping so that the receiver lists can be updated on the fly without requiring any cache update. Dynamic Receiver Determination provides an option to use mapping lookup program and hence identifies corresponding receiver for message to be sent depending on the pre-defined conditions. Calling the Integration Directory First, call the Integration Directory. To call the Integration Directory for the Advanced Adapter Engine Extended System, open the Advanced Adapter Engine Extended Start Page using the URL: Prerequisite - Creating Value Mapping Group Perform the following steps to check if Value Mapping Group Receiver_US and Receiver_DE already exist: 1. Open Search Help for objects. 2. Enter Group name as Receiver_US and press enter. If Value Mapping Group exist, it will be listed else search for Receiver_DE. 3. Open Value Mapping Group by double click. 4. Check if Value Mapping Group Receiver_US has following entries. Agency Country, Schema Code and Value US Agency Country, Schema Receiver and Value <SID>_AAEX_FileSystem_XiPattern2 March

34 5. Check if Value Mapping Group Receiver_DE has following entries. Agency Country, Schema Code and Value DE Agency Country, Schema Receiver and Value <SID>_AAEX_FileSystem_XiPattern3. 6. Close Value Mapping Groups. Perform the following steps to create two Value Mapping Groups: 1. In the Integration Directory main menu, choose Object New. 2. Under Administration select Value Mapping Group. 3. Enter Group Name as Receiver_US and a description. 4. For first row, enter Agency Country, Schema Code and Value US. 5. Press Add button. Now enter Agency Country, Schema Receiver and Value <SID>_AAEX_FileSystem_XiPattern2. 6. Press Save. 7. Repeat steps 1 to 5 to create one more Value Mapping Group Receiver_DE using following Agency Schema values. Agency Country, Schema Code and Value DE Agency Country, Schema Receiver and Value <SID>_AAEX_FileSystem_XiPattern3 6.2 Design Objects Used In this variant, the sender interface is used as in variant 1. The following describes all the additional objects that describe the message exchange in this variant in turn. Interface Objects 1. The asynchronous service interface XiPatternInterface1 is entered as the inbound interface at the sender. This service interface references the message type XiPatternMessage1. The data structure of the message is defined by the data type XiPatternDataType1. 2. For receiver, standard interface ReceiverDetermination under software component SAP BASIS, software component version SAP BASIS 7.40, and namespace is used. To open the service interface ReceiverDetermination, double-click the interface name. 3. To open the message type, double-click the name of the message type Receivers (in the service interface editor under Messages). 4. In the Message Type editor, you can display the data structure of the message. The data structure is defined by the data type Receivers. Information about a Receiver includes Party (Agency & Schema) and Service which is structured by different elements in the data structure of the exchanged message. Mapping Objects A mapping lookup is required to fetch the receiver lists to be used for routing messages at runtime. Double-click on the operation mapping (XiPatternInterface1ToReceiverDetermination) to open it. The names of the source and target interface, as well as the source and target message are displayed. The message mapping used is displayed under Mapping Program. Double-click to open the message mapping (XiPatternMessage1ToReceivers). In the message mapping, a Value Mapping group is used as lookup program to read receiver as per value of element CountryCode in sender payload. Summary of Design Objects Used The design objects used are summarized once more in the following table. 34 March 2012

35 Design Objects Used For a general description of the various object types, see SAP Help Portal at: Enterprise Services Repository Object Type (Name) Service Interface (XiPatternInterface1) Description Specifies the communication mode (asynchronous) and references the message type used. Service Interface (ReceiverDetermination) Message Type (XiPattermMessage1) Describes the message sent at runtime and references the data type used. Message Type (Receivers) Data Type (XiPatternDataType1) Describes the data structure of the message Message Type (Receivers) Operation mapping (XiPatternInterface1ToReceiverDete rmination) Message Mapping (XiPatternMessage1ToReceivers) Describes the mapping between the source and target interface Describes the mapping between the source and target structure in detail 6.3 Configuring the Process Integration Scenario Using the Configuration Scenario In this variant, the configuration scenario XiPatternOneStepScenario_AAEX created in variants 3 is modified. Editing Integrated Configuration 1. In the Integration Directory main menu, open the integrated configuration object <SID>_AAEX_FileSystem_XiPattern1 / XiPatternInterface1 / 2. Switch to change mode ( ). 3. On tab Receiver, select Extended for Type of Receiver Determination. A new frame to assign Operation Mapping via value help appears. 4. Using value help select operation mapping XiPatternInterface1ToReceiverDetermination of namespace under software component version SAP BASIS Check if already assigned receivers <SID>_AAEX_FileSystem_XiPattern2 and <SID>_AAEX_FileSystem_XiPattern3 should still be available in frame Possible Receivers. 6. Save the integrated configuration. Activating the Change List 1. To do this, select the Change Lists tab in the Integration Directory navigation area. 2. Choose Open Standard Change List. March

36 3. Position the cursor on the Standard Change List node and choose Activate ( )) in the context menu. 6.4 Executing the Use Case You perform the following steps to check that the process integration scenario is executed without errors. In directory XiPattern1, copy the file ZXiPatternSenderFile1.xml and ZXiPatternSenderFile2.xml. Rename the copied files to XiPatternSenderFile1.xml and XiPatternSenderFile2.xml respectively. Both the files will be moved from the directory within the next 60 seconds. Check whether the file arrived in directory XiPattern2 contains personal data with the country code US and in directory XiPattern3 contains personal data with the country code DE. Message monitoring contains two entries for this exchange of messages. 7 Variant5: One Sender and Two Receivers using Advanced Adapter Engine Extended With Message Mapping In this variant the scenario from variant 3 is extended. The message is sent to two receivers. A mapping is executed when the message is forwarded to one of the two receivers. 7.1 Design Objects Used You use the component view File2File_WithMapping in process integration scenario XiPatternOneStepScenario to configure this variant. The following graphic shows the component view: As described under previous section, you can navigate to all design objects used from the component view. The following explains the design objects that play an additional role when using this component view. Interface Objects You can see that the outbound interface entered in the connection editor is the same as the interface in component view File2File_NoMapping. If you navigate further to the message type and data type used, you will see that the data structure on the sender side is the same as in the previous variants (defined by the data type XiPatternDataType1). 36 March 2012

37 However, the asynchronous service interface XiPatternInterface2 is entered as the inbound interface at the receiver. This service interface references the message type XiPatternMessage2. The data structure of the message is defined by the data type XiPatternDataType2. The structure of data type XiPatternDataType2 is different to the structure of data type XiPatternDataType1 (which is used in the component view) in the following ways: In data type XiPatternDataType1, two separate elements are used to specify the person s first and second name, whereas in data type XiPatternDataType2, only one element is used (FullName). In data type XiPatternDataType1, the name of the element that specifies the telephone number is TelephonNumber, whereas in data type XiPatternDataType2, the name is PhoneNumber. Mapping Objects A mapping between the sender and receiver data structures must therefore be executed for the message to be processed. In the connection editor, navigate to the relevant mapping objects by choosing the tab page Assign Mapping. Double-click on the name of the operation mapping (XiPatternInterface1ToInterface2) to open it. The names of the source and target interface, as well as the source and target message are displayed. The message mapping used is displayed under Mapping Program. Doubleclick to open the message mapping (XiPatternMessage1ToMessage2). In the message mapping editor, the tab page Design displays the source and target structures. You have the option of displaying for which elements of the source and target structure mappings are to be executed. To do so, choose Display Dependencies Display All ( ). Summary of Additional Design Objects Used The following table summarizes the additional design objects used. Additional Design Objects Used Object Type (Name) Component View File2File_WithMapping (Process Integration Scenario XiPatternOneStepScenario) Service interface (XiPatternInterface2) Message Type (XiPatternMessage2) Description Describes the process flow and the message exchange if a mapping is to be executed during message processing (the interfaces on the sender and receiver sides are not identical) Describes the interface and data structure of the receiver. The data structure is different to the data structure of the sender. Data Type (XiPatternDataType2) Operation mapping (XiPatternInterface1ToInterface2) Message Mapping (XiPatternMessage1ToMessage2) Describes the mapping between the source and target interface Describes the mapping between the source and target structure in detail March

38 7.2 Configuring the Process Integration Scenario When you configure this variant, you will extend the configuration settings from variant 3. You use the same configuration scenario XiPatternOneStepScenario_AAEX. Using the Configuration Scenario In this variant the configuration scenario XiPatternOneStepScenario_AAEX created in variant 1 and extended in variants 2 and 3 is extended to use a mapping for one of the receivers. Open configuration scenario XiPatternOneStepScenario_AAEX in Edit Mode and call the model configurator from the configuration editor. Selecting an Process Integration Scenario (Component View) Select component view File2File_WithMapping. Any settings previously made in the model configurator will be overwritten. Assigning Communication Component Assign the communication component <SID>_AAEX_FileSystem_XiPattern1 to the application component Sender, and the communication component <SID>_AAEX_FileSystem_XiPattern3 to the application component Receiver. In this variant, only the connection between sender <SID>_AAEX_FileSystem_XiPattern1 and receiver <SID>_AAEX_FileSystem_XiPattern3 is reconfigured. The configuration of the connection between sender <SID>_AAEX_FileSystem_XiPattern1 and receiver <SID>_AAEX_FileSystem_XiPattern2 (defined in the previous variants) remains unchanged. Configuring the Connection When you configure the connection, you select the communication channels that were selection in the previous variants. Generating the Configuration Objects To do so, proceed as described in variant 1. When you have checked the generation log, close it and save the configuration scenario. Manual Editing Open the Integrated configuration object, select the tab Receiver Interfaces and check the settings for communication component <SID>_AAEX_FileSystem_XiPattern3. Delete the line with the receiver interface XiPatternInterface1, the one without the mapping. Save the Integrated Configuration. Activating the Change List 1. To do this, select the Change Lists tab in the Integration Directory navigation area. 2. Choose Open Standard Change List. 3. Position the cursor on the Standard Change List node and choose Activate ( )) in the context menu. 7.3 Executing the Use Case You perform the following steps to check that the process integration scenario is executed without errors. 38 March 2012

39 In directory XiPattern1, copy the file ZXiPatternSenderFile2.xml. Rename the file to XiPatternSenderFile2.xml. The file will be moved from the directory within the next 60 seconds. Check whether a file has arrived in directory XiPattern3. Open the file. The structure will have changed: the first and the second name of the person have been concatenated; the field for the telephone number has a new name. Monitoring contains one entry for this exchange of messages. You can repeat this procedure for file ZXiPatternSenderFile1.xml. This file is expected in directory XiPattern2 (no mapping executed). 8 Variant 6: One Sender and Two Receivers using Advanced Adapter Engine Extended With XSLT Mapping In this variant the scenario from variant 4 is modified. Instead of using a message mapping, mapping via XSL transformation program is executed when the message is forwarded to one of the two receivers. 8.1 Design Objects Used You use the component view File2File_WithMapping in process integration scenario XiPatternOneStepScenario to configure this variant. The following graphic shows the component view: As described under 3.1, you can navigate to all design objects used from the component view. The following explains the design objects that play an additional role when using this component view. Mapping Objects A mapping between the sender and receiver data structures is executed via XSL (Extensible Stylesheet Language) transformation program. You can login to Enterprise Services Repository and open Operation Mapping XiPatternInterface1ToInterface2_XSLT. An imported Archive XiPatternInterface1To2 is used as XSL type Mapping Program. March

40 You have the option of displaying mapping program to know which elements of the source and target structure mappings are to be executed. To do so, double click on xsl file within Imported Archive object. In data type XiPatternDataType1, two separate elements are used to specify the person s first and second name, whereas in data type XiPatternDataType2, only one element is used (FullName). In data type XiPatternDataType1, the name of the element that specifies the telephone number is TelephonNumber, whereas in data type XiPatternDataType2, the name is PhoneNumber. The transformation program adds one more element ext-welcome with value Welcome to Process Integration. XSLT Mapping with custom Java Class works! for receiver. Summary of Additional Design Objects Used The following table summarizes the additional design objects used Additional Design Objects Used Object Type (Name) Operation mapping (XiPatternInterface1ToInterface2_XSLT) Imported Archive (XiPatternInterface1To) Description Describes the mapping via XSLT transformation between the source and target interface Imported object having XSL transformation program 8.2 Modifying Configuration Scenario Configuration scenario XiPatternOneStepScenario_AAEX will be modified here to use above XSL based transformation mapping. Editing Integrated Configuration Open the Integrated configuration object, select the tab Receiver Interfaces and select communication component <SID>_AAEX_FileSystem_XiPattern3. In lower frame Receiver Interface, modify used Operation Mapping via value help to select XiPatternInterface1ToInterface2_XSLT of Namespace Save the Integrated Configuration. Activating the Change List 1. To do this, select the Change Lists tab in the Integration Directory navigation area. 2. Choose Open Standard Change List. 3. Position the cursor on the Standard Change List node and choose Activate ( )) in the context menu. 8.3 Executing the Use Case In directory XiPattern1, copy the file ZXiPatternSenderFile2.xml. Rename the file to XiPatternSenderFile2.xml. The file will be moved from the directory within the next 60 seconds. Check whether a file has arrived in directory XiPattern3. Open the file. The structure will have changed: the first and the second name of the person have been concatenated; the field for the telephone number has a new name and an additional field ext-welcome with value Welcome to Process Integration. XSLT Mapping with custom Java Class works! is available Monitoring contains one entry for this exchange of messages. Click on message Id link of receiver message. Now go to tab Message Log. You will find information as Executing request mapping " This confirms that XSLT mapping created in Enterprise Services Repository is used. 40 March 2012

41 You can repeat this procedure for file ZXiPatternSenderFile1.xml. This file is expected in directory XiPattern2 (no mapping executed). 9 Variant 7: One Sender and Two Receivers using Advanced Adapter Engine Extended - with XML-Validation This variant extends variant 4 by switching on the XML-Validation to check the schema of the file to be sent. The message is sent from the sender to two receivers using the Advanced Adapter Engine Extended if the schema is correct, the file will not be picked up if the structure does not fit. 9.1 Design Objects Used In this variant the same interfaces are used as in variant Configuring the Process Integration Scenario When you configure this variant, you will extend the configuration settings from variant 4. You use the same configuration scenario XiPatternOneStepScenario_AAEX. Opening the Configuration Scenario In this variant the configuration scenario XiPatternOneStepScenario_AAEX created in variant 1 and extended in variants 2 to 4 is extended to use XML-Validation to check the structure of the message. For this scenario, again the integrated configuration object is used for configuration. Changing the Integrated Configuration 1. In the Integration Directory main menu, open the integrated configuration object <SID>_AAEX_FileSystem_XiPattern1 / XiPatternInterface1 / 2. Switch to change mode ( ). 3. In tab Inbound Processing for Schema Validation select the radio button Validation by Adapter. 4. Save the Integrated configuration. Activating the Change List 1. To do this, select the Change Lists tab in the Integration Directory navigation area. 2. Choose Open Standard Change List. 3. Position the cursor on the Standard Change List node and choose Activate ( )) in the context menu. 9.3 Execution You perform the following steps to check that the process integration scenario is executed without errors. Execution without Validation Error For the execution in directory XiPattern1, rename the file ZXiPatternSenderFile1.xml to XiPatternSenderFile1.xml. The file will be moved from the directory within the next 60 seconds. Check in directory XiPattern2 whether the file has arrived. March

42 Furthermore, you can check the processing in the message in monitoring. To do this, proceed as follows: 1. Start the Monitoring by choosing Configuration and Monitoring Home on the Process Integration start page. 2. Choose Message Overview. 3. Select Database. 4. Use appropriate filter criteria to restrict the number of XML messages displayed (for example, the processing period). 5. Choose Go. The system displays the selected messages in a table. You want to locate the messages that were sent during execution. 6. Select the message to be displayed by selecting the appropriate radio button and then choose Open Message. The tab Payloads displays the message contents for the various versions of the message during processing. Message monitoring displays one message. Execution with Validation Error For the execution with wrong XML schema in directory XiPattern1, rename the file ZXiPatternSenderFile3.xml to XiPatternSenderFile3.xml. The file will not be moved from the directory within the next 60 seconds. No file should arrive in directory XiPattern2. The message-processing will not process the message because the message has the wrong XML-schema. If you check the XML file ZXiPatternSenderFile3.xml, you will see a tag with the name , this tag does not exist in the message type XiPatternMessage1 used in the outbound interface XiPatternInterface1. You cannot see the error in message monitoring because the adapter engine does not create a message out of the file because of the wrong structure. You can only see the error in channel monitoring. To do this, proceed as follows: 1. Start the Monitoring by choosing Configuration and Monitoring Home on the Process Integration start page. 2. Select Adapter Engine Communication Channel Monitoring. 3. Use the Link Advanced to get additional selection fields. 4. Set XiPatternChannel_FileSender as channel name and <SID>_AAEX_FileSystem_XiPattern1 as communication component to get only the channel used for this variant. 5. Choose Go. The system displays the channel used for picking up the files from the sender directory. You will see that the channel is in error state because the XML-Validation found an error in the structure of the payload. To end the processing, delete the file XiPatternSenderFile3.xml from the directory. 10 Variant 8: One Sender and One Receiver using Advanced Adapter Engine Extended - using Exactly Once In Order This variant enables you to configure and execute the simplest kind of message exchange: one sender on the Advanced Adapter Engine Extended (file directory XiPatterns4) sends a series of messages to one receiver on the Advanced Adapter Engine Extended (file directory XiPatterns5). No mapping is executed between the outbound and inbound interface in this variant. The messages are delivered in some particular order. Concretely, the file adapter allows either the last-modified timestamp or the filename to be used to order the input files in its directory. 42 March 2012

43 10.1 Design Objects Used You use the component view File2File_NoMapping_InOrder in process integration scenario XiPatternOneStepScenario to configure this variant. The following graphic shows the component view: As described under 3.1, you can navigate to all design objects used from the component view. The following explains the design objects that play a role when using this component view. Interface Objects In this variant, the data structures at both the sender and receiver side are the same and no mapping is required, the service interfaces XiPatternInterface1O is used for sender and receiver Summary of Design Objects Used The following table summarizes the design objects used. Design Objects Used Object Type (Name) Component View File2File_NoMapping_InOrder (Process Integration Scenario XiPatternOneStepScenario) Service interface (XiPatternInterface1O) Message Type (XiPatternMessage1) Data Type (XiPatternDataType1) Description Describes the process flow and the message exchange for this variant. Describes the interface and data structure of the sender and receiver. The data structure is the same for sender and receiver Configuring the Process Integration Scenario To configure this variant, a new configuration scenario is created. March

44 Selecting the Process Integration Scenario Perform the following steps to select the process integration scenario that you want to configure from the Enterprise Services Repository. Also, enter the name of the configuration scenario (in the Integration Directory) in which you want to group the configuration objects. 1. To call the model configurator, choose Tools Apply Model from ES Repository in the Integration Builder menu bar. This calls a wizard, which you use to select a model (in this case, a process integration scenario) and create a configuration scenario in the Integration Directory. 2. Make sure that the model type Process Integration Scenario is selected (radio button under Type of ES Repository Model). 3. Choose the input help (for the Name field) ( ) This calls an input help, which displays all process integration scenarios from the Enterprise Services Repository in a list. 4. Select the process integration scenario XiPatternOneStepScenario (software component version SAP BASIS 7.40, namespace from the Enterprise Services Repository and choose Apply. 5. Choose Continue. 6. Enter the name of the configuration scenario as: XiPatternOneStepScenario_AAEX_EOIO. 7. Choose Finish and then Close. The system calls the model configurator. Selecting the Component View Check whether the component view File2File_NoMapping_InOrder is displayed. If it is not, choose the menu option Select Component View ( ). On the subsequent screen, select the component view (in the preview area) by double-clicking. Assigning Communication Components You perform the following steps to assign communication components to the application components of the process integration scenario. You use the business system components that you created before (see 2.2.7). 1. In the graphical editor, click on the lane representing the Sender application component. This calls the Assign Business System Component dialog box for the Sender application component (below the graphical representation of the process integration scenario). 2. To assign a communication component click in the input field in the Communication Component column and call the input help ( ). 3. In the subsequent screen, select the communication component <SID>_AAEX_FileSystem_XiPattern4 and then choose Apply. 4. Choose Next Role ( ) to navigate to the configuration dialog for the application component Receiver. 5. Assign the communication component <SID>_AAEX_FileSystem_XiPattern5 to the application component Receiver. Follow the same procedure as when assigning the communication component to the application component Sender. 6. Choose Assign. Configuring the Connection You perform the following steps to configure the connection of the process integration scenario. You activate the relevant sender-receiver relation (between the sender and receiver component) and assign both the sender and receiver a (sender or receiver) communication channel. You create the communication channel on the basis of the communication channel templates that the process integration scenario already contains. 44 March 2012

45 1. In the graphical editor, click on the connection between the lanes representing the two application components. 2. This calls the Configure Connection dialog box for the connection between the actions (below the graphical representation of the process integration scenario). 3. On the Configure Connections screen, choose the tab page Connections from Component Assignment. The communication components that you assigned in the previous configuration step are displayed. The remaining tab pages contain further information about the process integration scenario, for example, the communication channel templates that are defined for the process integration scenario in the Enterprise Services Repository. 4. Assign the sender a communication channel. To do so, place the cursor in the field Communication Channel for the Sender Component, in the push button bar choose Create Communication Channel With Template ( ). In the subsequent wizard you can create a communication channel based on a communication channel template. 5. Choose Continue. The default communication channel template on the subsequent screen is that which was assigned to the sender application component in the process integration scenario (name XiPatternChannel_FileSenderO, software component version SAP BASIS 7.40, namespace 6. Choose Continue. The default name for the communication channel on the next screen is XiPatternChannel_FileSenderO. 7. Confirm your selection by choosing Finish. 8. Following the same procedure (see step 4-7), assign the application component of the receiver a communication channel (XiPatternChannel_FileReceiverO) based on the default communication channel template (name XiPatternChannel_FileReceiverO, software component version SAP BASIS 7.40, namespace Generating the Configuration Objects In the following steps, you generate the relevant configuration objects based on the settings made in previous steps. 1. If not already selected, select the flag for Configuration for Advanced Adapter Engine. 2. Choose the push button Create Configuration Objects ( ). 3. Under General, select the radio button Generation. 4. Choose Start. The integrated configuration objects are generated based on the settings you made. Once generation is complete, the generation log is opened. The generation log displays the results of generation. The generation log enables you to analyze any errors that occurred during generation. 5. Close the generation log. 6. Close the model configurator. Choose Apply. 7. Save the configuration scenario. Manual Editing In the following steps, you edit the generated configuration objects manually and enhance the configuration settings made during generation. In this variant, you must edit the communication channels after generation. March

46 1. In the editor Display Configuration Scenario (for the open scenario XiPatternOneStepScenario_AAEX_EOIO), on the tab page Objects open the communication channel ( ) XiPatternChannel_FileSenderO by double-clicking. 2. Under File Access Parameter in the Source Directory field, enter the path in the file directory that you defined previously (see 2.2.4). In the case of the sender communication channel, enter the whole path for the file directory XiPattern4. Example: C:/<selected path>/xipatterns/xipattern4 3. Save the communication channel. 4. To check if the channel works you can directly jump to the channel monitoring using the menu path Communication Channel Channel Monitoring 5. The PI Communication Channel Monitoring page will open up where you can do a selftest for the channel. To do this click on the button Ping Channel. 6. The status page for the channel will show up with detailed information of the executed self-test. 7. Following the same procedure, edit the communication channel XiPatternChannel_FileReceiverO (communication component <SID>_AAEX_FileSystem_XiPattern5). Enter the path for the file directory XiPattern5. 8. Save the communication channel. 9. Open the Channel Monitoring and check the status of the channel. Activating the Change List 1. To do this, select the Change Lists tab page in the Integration Directory navigation area. 2. Choose Open Standard Change List. 3. Position the cursor on the Standard Change List node and choose Activate ( ) in the context menu Execution You perform the following steps to check that the process integration scenario is executed without errors. 1. Stop the channel <SID>_AAEX_FileSystem_XiPattern4 XiPatternChannel_FileSender in the Configuration and Monitoring Home Adapter Engine Communication Channel Monitoring to make sure no processing runs during the time the files are placed into the source folder. 2. On the host of the Advanced Adapter Engine Extended open the file directory XiPatternsO_AAEX/XiPatterns5. If the output file XiPatternReceiverFile.txt is already present, delete this file. The execution of this test will create this file if it is not present and append a series of output files to this file. 3. Open the file directory XiPatternsO_AAEX/XiPatterns4 4. Unpack file XiPatternSenderFilesEOIO.zip in the current directory. This will place a series of input files XiPatternSenderFile00001.xml,, XiPatternSenderFile01000.xml. The File/FTP adapter is configured so that the files are picked in the order sorted by the file names and moved from the source directory XiPatterns4 to the target directory XiPatterns5 and the files are concatenated into a single file XiPatternReceiverFile.txt. 5. Start the channel <SID>_AAEX_FileSystem_XiPattern4 XiPatternChannel_FileSender in the Configuration and Monitoring Home Adapter Engine Communication Channel Monitoring to start processing the files. 6. Open the directory XiPatternsO_AAEX/XiPatterns5 and check that the files have been transferred. 7. Open the XML file XiPatternReceiverFileAll.xml which includes the output file and check whether the content is in the correct order. 46 March 2012

47 The content must be in the correct order with the incremental ID value and the entire content must be present. 8. Furthermore, you can check the processing of the messages in the message monitoring as in Variant Variant 9: One Sender and One Receiver - Proxy-to-Proxy Communication using the Advanced Adapter Engine In this variant, the message is processed via the ABAP proxy runtime; the message is forwarded using the Adapter Engine instead of the Integration Server. Following the standard configuration suggested below one application system is used both as sender and receiver of messages Design Objects Used You use the component view Proxy2Proxy_NoMapping in process integration scenario XiPatternOneStepScenario to configure this variant. The following graphic shows the component view: As described under 3.1, you can navigate to all design objects used from the component view. The following explains the design objects that play a role when using this component view. Interface Objects In this variant, the data structures at both the sender and receiver side are the same and no mapping is required. Nevertheless, two different service interfaces are used: outbound interface XiPatternInterface2_Out for the sender and inbound interface XiPatternInterface2_In for the receiver. This is due to the fact that the sender and receivers systems are SAP systems that communicate with each other by the ABAP proxy runtime. This communication type requires an outbound proxy and an inbound proxy (both generated resp. derived from the outbound resp. inbound interface). March

48 Summary of Design Objects Used The following table summarizes the additional design objects used. Design Objects Used Object Type (Name) Component View Proxy2Proxy_NoMapping (Process Integration Scenario XiPatternOneStepScenario) Service interface (XiPatternInterface2_Out) Service Interface (XiPatternInterface2_In) Message Type (XiPatternMessage2) Description Describes the process flow and the message exchange for this variant. Describes the interface and data structure of the receiver. The data structure is the same for sender and receiver. The fault message type is used to handle application-specific errors that occur on the inbound side and that are reported back to the sender. Fault Message Type (XiPatternFaultMessage) Data Type (XiPatternDataType2) 11.2 Configuring the Process Integration Scenario Create the connection to the XI Adapter in the Advanced Adapter Engine To connect the sending client to the Java XI Adapter you have to create a HTTP Destination to the Adapter Engine. Do the following in the application client 105: 1. Call transaction SM Create a HTTP Destination to an external system (Type G). As name set JAVA_XI_ADAPTER_AEX, as description use Connection to Java XI Adapter in Adapter Engine. As target host set the host name of the adapter engine, as service set (Service No.) the HTTP Port and as path set /XISOAPAdapter/MessageServlet?ximessage=true. Note: Ensure that you have maintained the proper URL of the Advanced Adapter Engine of PI system in SM59 of the sender application. You may get the warning Query string not allowed when saving the destination, just press enter to confirm the warning message. 3. Under Logon and Security select Basic Authentication and set the user PIAPPLUSER (or a copy of the PIAPPLUSER) with the corresponding password. This user and password will be checked against the Advanced Adapter Engine Extended system, where the message is sent to. 4. Save the destination and execute Connection Test. Response Code HTTP 200 means successful connection. Activating the connection to the Java XI Adapter To enable the sending application system to send a message to the Java XI Adapter instead of the Integration Server you have to create a filter for the sending interface and have to set the URL to the Adapter Engine in the sending application client. Execute the following steps in the sending client 105: 1. Call transaction SXMSIF. 48 March 2012

49 2. Create a new entry for Sender/Receiver ID with the name JAVA_XI_ADAPTER_AEX. As description set Call the Java XI Adapter in PI Demo Examples, as communication Component set <SID>_105, as interface name and namespace set XiPatternInterface2_Out and 3. Save the entry. 4. Call transaction SXMB_ADM, select Integration Engine Configuration. 5. Select the button Change Configuration. Switch to Change Mode and create a new entry with the following settings: Category: RUNTIME Parameter: IS_URL Subparameter: select the Sender/Receiver ID JAVA_XI_ADAPTER_AEX Value: dest://java_xi_adapter_aex 6. Save the entry. Calling the Integration Directory You perform the following configuration steps in the Integration Directory. For this scenario, the integrated configuration object is used for configuration. For more information, see Defining the Integrated Configuration. First, call the Integration Directory. On the Process Integration initial screen, choose Integration Directory. To configure this variant, a new configuration scenario is created. Selecting the Process Integration Scenario Perform the following steps to select the process integration scenario that you want to configure from the Enterprise Services Repository. Also, enter the name of the configuration scenario (in the Integration Directory) in which you want to group the configuration objects. 1. To call the model configurator, choose Tools Apply Model from ES Repository in the Integration Builder menu bar. This calls a wizard, which you use to select a model (in this case, a process integration scenario) and create a configuration scenario in the Integration Directory. 2. Make sure that the model type Process Integration Scenario is selected (radio button under Type of ES Repository Model). 3. Choose the input help (for the Name field) ( ) This calls an input help, which displays all process integration scenarios from the Enterprise Services Repository in a list. 4. Select the process integration scenario XiPatternOneStepScenario (software component version SAP BASIS 7.40, namespace from the Enterprise Services Repository and choose Apply. 5. Choose Continue. 6. Enter the name of the configuration scenario as: XiPatternOneStepScenario_Proxy2Proxy_AAE. 7. Choose Finish and then Close. The system calls the model configurator. March

50 Selecting the Component View Check whether the component view Proxy2Proxy_NoMapping is displayed. If it is not, choose the menu option Select Component View ( ). On the subsequent screen, select the component view (in the preview area) by double-clicking. Assigning Communication Components You perform the following steps to assign communication components to the application components of the process integration scenario. You use the business system components that you created before (see 2.2.6). 1. In the graphical editor, click on the lane representing the Sender application component. This calls the Assign Business System Component dialog box for the Sender application component (below the graphical representation of the process integration scenario). 2. To assign a communication component click in the input field in the Communication Component column and call the input help ( ). 3. In the subsequent screen, select the communication component <SID>_105 and then choose Apply. 4. Choose Next Role ( ) to navigate to the configuration dialog for the application component Receiver. 5. Assign the same communication component <SID>_105 to the application component Receiver. Follow the same procedure as when assigning the communication component to the application component Sender. 6. Choose Assign. Configuring the Connection You perform the following steps to configure the connection of the process integration scenario. You activate the relevant sender-receiver relation (between the sender and receiver component) and assign both the sender and receiver a (sender or receiver) communication channel. You create the communication channel on the basis of the communication channel templates that the process integration scenario already contains. 1. In the graphical editor, click on the connection between the lanes representing the two application components. 2. This calls the Configure Connection dialog box for the connection between the actions (below the graphical representation of the process integration scenario). 3. On the Configure Connections screen, choose the tab page Connections from Component Assignment. The communication components that you assigned in the previous configuration step are displayed. The remaining tab pages contain further information about the process integration scenario, for example, the communication channel templates that are defined for the process integration scenario in the Enterprise Services Repository. 4. Assign the sender a communication channel. To do so, place the cursor in the field Communication Channel for the Sender Component, in the push button bar choose Create Communication Channel With Template ( ). In the subsequent wizard you can create a communication channel based on a communication channel template. 5. Choose Continue. The default communication channel template on the subsequent screen is that which was assigned to the sender application component in the process integration scenario (name XiPatternChannel_XiSender, software component version SAP BASIS 7.40, namespace 6. Choose Continue. 50 March 2012

51 The default name for the communication channel on the next screen is XiPatternChannel_XiSender. 7. Confirm your selection by choosing Finish. 8. Following the same procedure (see step 4-7), assign the application component of the receiver a communication channel (XiPatternChannel_XiReceiver) based on the default communication channel template (name XiPatternChannel_XiReceiver, software component version SAP BASIS 7.40, namespace Generating the Configuration Objects In the following steps, you generate the relevant configuration objects based on the settings made in previous steps. 1. If not already selected, select the flag for Configuration for Advanced Adapter Engine. 2. Choose the push button Create Configuration Objects ( ). 3. Under General, select the radio button Generation. 4. Choose Start. The integrated configuration objects are generated based on the settings you made. Once generation is complete, the generation log is opened. The generation log displays the results of generation. The generation log enables you to analyze any errors that occurred during generation. 5. Close the generation log. 6. Close the model configurator. Choose Apply. 7. Save the configuration scenario. Manual Editing In the following steps, you edit the generated configuration objects manually and enhance the configuration settings made during generation. In this variant, you must edit the receiver communication channel after generation. 1. In the editor Display Configuration Scenario (for the open scenario XiPatternOneStepScenario_Proxy2Proxy_AAE), on the tab page Objects open the communication channel ( ) XiPatternChannel_XiReceiver by double-clicking. 2. As target URL set the entry path for the application client 105: http(s)://server:httpport/sap/xi/engine?type=entry. As Authentication Data, enter client 105 and the user PIAPPLUSER (or a copy of the PIAPPLUSER) with its password in client 105. Note: 1. in case https then you should specify the host and the whole qualified domain name 2. If receiver server is lower than NW7.10 please consider that the URL should contain the http(s) port. Check the transaction SMICM and use the corresponding http(s) port instead of the URL which is used start the integration directory. 3. Save the communication channel. Activating the Change List 1. To do this, select the Change Lists tab page in the Integration Directory navigation area. 2. Choose Open Standard Change List. 3. Position the cursor on the Standard Change List node and choose Activate ( ) in the context menu Execution You perform the following steps to check that the process integration scenario is executed without errors. March

52 To run the process integration scenario, you can use a transaction that is available in the SAP PI system, however this transaction should run in the of the business client but not on the client where the Integration Server is available. 1. Logon to the SAP system of the business system, client Choose transaction SXIPATT1. 3. Enter values for the fields Name, Country, and Tel. 4. Choose Send. 5. To check whether the data are transferred correctly from the sender to the receiver, switch to the receiver view (pushbutton Receiver View). When the message was sent without errors, the data are displayed that you entered in the sender view. If you switch fast enough from sender to receiver view after having chosen Send, you can see the former data. Choose Refresh to check if the message was already processed and the data is updated accordingly. The message should be visible in the monitoring in client 105 and in the PI monitoring for the adapter engine, but not in Integration Server. 6. You may double check in Audit Log of the NWA (NetWeaver Administrator) of the PI, where the Central Adapter Engine is running as well. 7. As a fine verification, you may start NWA using http(s)://<host>:<port>/nwa 8. Navigate to SOA / Monitoring and click on the Message Monitoring Tab. 9. Execute on the overview page the search for messages. Select from the Message Status Overview the row with the corresponding sender and/or receiver. For this single row, it will be displayed how many messages are transmitted and the count of the message in error, scheduled, success, and canceled. Moreover, in the second block of the Message Status Overview, more detailed information for each selected row exists. For messages which are not transmitted successfully you can resend or cancel them. In the Status Values Tab, there exists a column named Number. This count of messages with specific status has got a link to the Database message monitoring. For each row in the Message Status Overview, there could up-to four entries (error, scheduled, success, and canceled.) If you hit the link on the count, there will be a jump into Database Monitoring. The advantage of this link is that the so called Message Header Data (Sender Party, Receiver Party, Interface, Sender Component, Receiver Component, and Interface Namespace) will be considered and filled automatically. Alternatively, you may directly monitor the messages from the Database Tab as mentioned in variant 1 (chapter 3.3) and drill-down in the Message List and Message Details provided. All Message Header Data can be set/changed using the F4 Help, where you are able to see and change different values and descriptions of the Message Header Data beside the message status. 12 Variant 10: One Sender and One Receiver - Proxy-to-Proxy Communication using the Advanced Adapter Engine and Principle Propagation In this variant, the message is processed via the ABAP proxy runtime; the message is forwarded using the Adapter Engine instead of the Integration Server. Following the standard configuration suggested below one application system is used both as sender and receiver of messages. 52 March 2012

53 12.1 Prerequisites Activating Principle Propagation Trust Relationship Settings To use principal propagation you need to do some global configuration settings which are described in the prerequisite chapter Create Destination in the AEX system 1. Switch back to AEX NWA http(s)://<host>:<port>/nwa 2. Go to tab Configuration and click on Destinations. 3. Create HTTP Destination : <SID>_105_PP 4. Set URL to of <SID>_105>>:<port>/sap/xi/engine?type=entry 5. Maintain SID, client and language. 6. Select Ignore SLL Server Certificate 7. Press next and choose Assertion Ticket for Authentication. 8. Save Changes. 9. Execute Ping. Result should be Ping not successful! Received HTTP response Design Objects Used You use the component view Proxy2Proxy_PP_NoMapping in process integration scenario XiPatternOneStepScenario to configure this variant. The following graphic shows the component view: As described under 3.1, you can navigate to all design objects used from the component view. The following explains the design objects that play a role when using this component view. Interface Objects In this variant, the data structures at both the sender and receiver side are the same and no mapping is required. Nevertheless, two different service interfaces are used: outbound interface XiPatternInterface9_Out for the sender and inbound interface XiPatternInterface9_In for the receiver. This is due to the fact that the sender and receivers systems are SAP systems that communicate with each other by the ABAP proxy runtime. March

54 This communication type requires an outbound proxy and an inbound proxy (both generated resp. derived from the outbound resp. inbound interface). Summary of Design Objects Used The following table summarizes the additional design objects used. Design Objects Used Object Type (Name) Component View Proxy2Proxy_PP_NoMapping (Process Integration Scenario XiPatternOneStepScenario) Service interface (XiPatternInterface9_Out) Service Interface (XiPatternInterface9_In) Message Type (XiPatternMessage9) Description Describes the process flow and the message exchange for this variant. Describes the interface and data structure of the receiver. The data structure is the same for sender and receiver. The fault message type is used to handle application-specific errors that occur on the inbound side and that are reported back to the sender. Fault Message Type (XiPatternFaultMessage) Data Type (XiPatternDataType9) 12.3 Configuring the Process Integration Scenario Create the connection to the XI Adapter of the AEX system To connect the sending client to the Java XI Adapter you have to create a HTTP Destination to the Adapter Engine. Do the following in the application client 105: 1. Call transaction SM Create a HTTP Destination to an external system (Type G). As name set JAVA_XI_ADAPTER_AEX_<SID>_PP, as description use Connection to Java XI Adapter in Adapter Engine. As target host set the host name of the adapter engine, as service set (Service No.) the HTTP(S) Port and as path set /XISOAPAdapter/MessageServlet?ximessage=true. Note: Ensure that you have maintained the proper URL of the Advanced Adapter Engine of PI system in SM59 of the sender application. You may get the warning Query string not allowed when saving the destination, just press enter to confirm the warning message. 3. Under Logon and Security select Basic Authentication and set the user PIAPPLUSER (or a copy of the PIAPPLUSER) with the corresponding password. This user and password will be checked against the Advanced Adapter Engine Extended system, where the message is sent to. 4. Save the destination and execute Connection Test. Response Code HTTP 200 means successful connection. Activating the connection to the Java XI Adapter To enable the sending application system to send a message to the Java XI Adapter instead of the Integration Server you have to create a filter for the sending interface and have to set 54 March 2012

55 the URL to the Adapter Engine in the sending application client. Execute the following steps in the sending client 105: 1. Call transaction SXMSIF. 2. Create a new entry for Sender/Receiver ID with the name JAVA_XI_ADAPTER_AEX_PP_IF9. As description set Call the Java XI Adapter in PI PP Async Demo Examples, as communication Component set <SID>_105, as interface name and namespace set XiPatternInterface9_Out and 3. Save the entry. 4. Call transaction SXMB_ADM, select Integration Engine Configuration. 5. Select the button Change Configuration. Switch to Change Mode and create a new entry with the following settings: Category: RUNTIME Parameter: IS_URL Subparameter: select the Sender/Receiver ID JAVA_XI_ADAPTER_AEX_PP_IF9 Value: dest://java_xi_adapter_aex_<sid>_pp 6. Save the entry. Calling the Integration Directory You perform the following configuration steps in the Integration Directory. For this scenario, the integrated configuration object is used for configuration. For more information, see Defining the Integrated Configuration. First, call the Integration Directory. On the Process Integration initial screen, choose Integration Directory. To configure this variant, a new configuration scenario is created. Selecting the Process Integration Scenario Perform the following steps to select the process integration scenario that you want to configure from the Enterprise Services Repository. Also, enter the name of the configuration scenario (in the Integration Directory) in which you want to group the configuration objects. 1. To call the model configurator, choose Tools Apply Model from ES Repository in the Integration Builder menu bar. This calls a wizard, which you use to select a model (in this case, a process integration scenario) and create a configuration scenario in the Integration Directory. 2. Make sure that the model type Process Integration Scenario is selected (radio button under Type of ES Repository Model). 3. Choose the input help (for the Name field) ( ) This calls an input help, which displays all process integration scenarios from the Enterprise Services Repository in a list. 4. Select the process integration scenario XiPatternOneStepScenario (software component version SAP BASIS 7.40, namespace from the Enterprise Services Repository and choose Apply. 5. Choose Continue. 6. Enter the name of the configuration scenario as: XiPatternOneStepScenario_Proxy2Proxy_PP_AAE. 7. Choose Finish and then Close. The system calls the model configurator. March

56 Selecting the Component View Check whether the component view Proxy2Proxy_PP_NoMapping is displayed. If it is not, choose the menu option Select Component View ( ). On the subsequent screen, select the component view (in the preview area) by double-clicking. Assigning Communication Components You perform the following steps to assign communication components to the application components of the process integration scenario. You use the business system components that you created before (see 2.2.5). 1. In the graphical editor, click on the lane representing the Sender application component. This calls the Assign Business System Component dialog box for the Sender application component (below the graphical representation of the process integration scenario). 2. To assign a communication component click in the input field in the Communication Component column and call the input help ( ). 3. In the subsequent screen, select the communication component <SID>_105 and then choose Apply. 4. Choose Next Role ( ) to navigate to the configuration dialog for the application component Receiver. 5. Assign the same communication component <SID>_105 to the application component Receiver. Follow the same procedure as when assigning the communication component to the application component Sender. 6. Choose Assign. Configuring the Connection You perform the following steps to configure the connection of the process integration scenario. You activate the relevant sender-receiver relation (between the sender and receiver component) and assign both the sender and receiver a (sender or receiver) communication channel. You create the communication channel on the basis of the communication channel templates that the process integration scenario already contains. 1. In the graphical editor, click on the connection between the lanes representing the two application components. 2. This calls the Configure Connection dialog box for the connection between the actions (below the graphical representation of the process integration scenario). 3. On the Configure Connections screen, choose the tab page Connections from Component Assignment. The communication components that you assigned in the previous configuration step are displayed. The remaining tab pages contain further information about the process integration scenario, for example, the communication channel templates that are defined for the process integration scenario in the Enterprise Services Repository. 4. Assign the sender a communication channel. To do so, place the cursor in the field Communication Channel for the Sender Component, in the push button bar choose Create Communication Channel With Template ( ). In the subsequent wizard you can create a communication channel based on a communication channel template. 5. Choose Continue. The default communication channel template on the subsequent screen is that which was assigned to the sender application component in the process integration scenario (name XiPatternChannel_XiSender, software component version SAP BASIS 7.40, namespace 6. Choose Continue. 56 March 2012

57 Enter the name for the communication channel on the next screen as XiPatternChannel_XiSender_PP. 7. Confirm your selection by choosing Finish. 8. Following the same procedure (see step 4-7), assign the application component of the receiver a communication channel (XiPatternChannel_XiReceiver_PP) based on the default communication channel template (name XiPatternChannel_XiReceiver, software component version SAP BASIS 7.40, namespace Generating the Configuration Objects In the following steps, you generate the relevant configuration objects based on the settings made in previous steps. 1. If not already selected, select the flag for Configuration for Advanced Adapter Engine. 2. Choose the push button Create Configuration Objects ( ). 3. Under General, select the radio button Generation. 4. Choose Start. The integrated configuration objects are generated based on the settings you made. Once generation is complete, the generation log is opened. The generation log displays the results of generation. The generation log enables you to analyze any errors that occurred during generation. 5. Close the generation log. 6. Close the model configurator. Choose Apply. 7. Save the configuration scenario. Manual Editing In the following steps, you edit the generated configuration objects manually and enhance the configuration settings made during generation. In this variant, you must edit the receiver communication channel after generation. 1. In the editor Display Configuration Scenario (for the open scenario XiPatternOneStepScenario_Proxy2Proxy_PP_AEX), on the tab page Objects open the communication channel ( ) XiPatternChannel_XiReceiver_PP by double-clicking. 2. As target URL set the entry path for the application client 105: http(s)://server:httpport/sap/xi/engine?type=entry. As Authentication Data, enter client 105 and the user PIAPPLUSER (or a copy of the PIAPPLUSER) with its password in client 105. Note: 1. in case https then you should specify the host and the whole qualified domain name 2. If receiver server is lower than NW7.10 please consider that the URL should contain the http(s) port. Check the transaction SMICM and use the corresponding http(s) port instead of the URL which is used start the integration directory. 3. Save the communication channel. Activating the Change List 1. To do this, select the Change Lists tab page in the Integration Directory navigation area. 2. Choose Open Standard Change List. 3. Position the cursor on the Standard Change List node and choose Activate ( ) in the context menu Check Setup Before starting with the principal propagation configuration, the scenario is tested without principal propagation. This ensures that the default case work. If the default case does not work, principal propagation also won t work. 1. Execute transaction SXIPATT1 (client 105). March

58 2. Check only the checkbox PP. 3. Choose Send. 4. Execute transaction SXMB_MONI 5. Filter messages by Sender-Interface XiPatternInterface9_Out. 6. Message must be processed successfully. 7. Now filter for corresponding message, which is received by the client. Filter messages by Receiver-Interface XiPatternInterface9_In. 8. Message must be processed successfully. Activating Principle Propagation Integration Directory 1. Launch Integration Directory 2. Select the Integrated Configuration XiPatternOneStepScenario_Proxy2Proxy_PP_AAE 3. Check the checkbox Principle Propagation on Inbound Processing and Outbound Processing tab. 4. In the channel XiPatternChannel_XIReceiver_PP select Addressing Typ HTTP Destination and in the field HTTP Destination add the destination <SID>_105_PP. 5. Activate the changes. 6. Move to the Channel Monitor and stop and start the channel. Modify Destination in the ABAP client 1. Call transaction sm Select destination JAVA_XI_ADAPTER_AEX_<SID>_PP. 3. On tab Logon & Security select Do Not Use a User and select Send Logon Ticket without Ref. to Target System. 4. Save the settings. Activating Principle Propagation Sender System 1. Logon to the sending system (<SID>_105) 2. Call transaction SXMB_ADM 3. Execute Configure Principle Propagation 4. Configure Interfaces (Interface Conf. for Transfer of User IDs) 5. Add the interface XiPatternInterface9_Out with namespace and the user you are using. Principle Configuration settings will enforce SAPLogonTicket usage of destination JAVA_XI_ADAPTER_AEX_<SID>_PP Execution You perform the following steps to check that the process integration scenario is executed without errors. To run the process integration scenario, you can use a transaction that is available in the SAP PI system, however this transaction should run in the of the business client but not on the client where the Integration Server is available i.e Logon to the SAP system of the business system, client Choose transaction SXIPATT1. 3. Enter values for the fields Name, Country, and Tel. 4. Select only the checkbox PP. 58 March 2012

59 5. Choose Send. 6. For verification start NWA using 7. Navigate to SOA / Monitoring / Message Monitoring and click on the Database Tab. 8. Search for the message and check, if it was processed successfully. 9. Check the Message Log, whether the message was entering the SOAP Adapter with your ABAP user. 10. Logon to the ABAP System: <SID>_ Call transaction SXMB_MONI. 12. Find the message you send. March

60 13. Check the details of the message. If your user is used in the tag <SAP:User> in the RunTime part of the SOAP Header in the Inbound Message of Sender and Receiver, Principal Propagation works correctly. 13 Variant 11: One Sender and One Receiver synchronous Proxy-to-Proxy Communication using the Advanced Adapter Engine In this variant, the message is processed via the ABAP proxy runtime; the message is forwarded using the Advanced Adapter Engine Extended. Following the standard configuration suggested below one application system is used both as sender and receiver of messages. 60 March 2012

61 13.1 Design Objects Used You use the component view Proxy2Proxy_sync_NoMapping in process integration scenario XiPatternOneStepScenario to configure this variant. The following graphic shows the component view: As described under 3.1, you can navigate to all design objects used from the component view. The following explains the design objects that play a role when using this component view. Interface Objects In this variant, the data structures at both the sender and receiver side are the same and no mapping is required. Nevertheless, two different service interfaces are used: outbound interface XiPatternInterface2_Out_sync for the sender and inbound interface XiPatternInterface2_In_sync for the receiver. This is due to the fact that the sender and receivers systems are SAP systems that communicate with each other by the ABAP proxy runtime. This communication type requires an already generated and delivered outbound proxy and an inbound proxy in the application clients. Summary of Design Objects Used The following table summarizes the additional design objects used. Design Objects Used Object Type (Name) Component View Proxy2Proxy_sync_NoMapping (Process Integration Scenario XiPatternOneStepScenario) Service interface (XiPatternInterface2_Out_sync) Service Interface (XiPatternInterface2_In_sync) Message Type (XiPatternMessage2) Description Describes the process flow and the message exchange for this variant. Describes the interface and data structure of the receiver. The data structure is the same for sender and receiver. The fault message type is used to handle application-specific errors that occur on the inbound side and that are reported back to the sender. Message Type (XiPatternMessage2Response) March

62 Fault Message Type (XiPatternFaultMessage) Data Type (XiPatternDataType2) Data Type (XiPatternDataType2Response) 13.2 Configuring the Process Integration Scenario Create the connection to the XI Adapter in the Advanced Adapter Engine To connect the sending client to the Java XI Adapter you have to create a HTTP Destination to the Adapter Engine. Do the following in the application client 105: 1. Call transaction SM Create a HTTP Destination to an external system (Type G). As name set JAVA_XI_ADAPTER_AAE_SYNC, as description use Synchronous Connection to Java XI Adapter in Adapter Engine. As target host set the host name of the adapter engine, as service set (Service No.) the HTTP(S) Port and as path set /XISOAPAdapter/MessageServlet?ximessage=true. Note: Ensure that you have maintained the proper URL of the Advanced Adapter Engine of AEX system in SM59 of the sender application. You may get the warning Query string not allowed when saving the destination, just press enter to confirm the warning message. 5. Under Logon and Security select Basic Authentication and set the user PIAPPLUSER (or a copy of the PIAPPLUSER) with the corresponding password. This user and password will be checked against the Advanced Adapter Engine Extended system, where the message is sent to. 6. Save the destination and execute Connection Test. Response Code HTTP 200 means successful connection. Activating the connection to the Java XI Adapter To enable the sending application system to send a message to the Java XI Adapter instead of the Integration Server you have to create a filter for the synchronous sending interface and have to set the URL to the Adapter Engine in the sending application client. Execute the following steps in the sending client 105: 1. Call transaction SXMSIF. 2. Create a new entry for Sender/Receiver ID with the name JAVA_XI_ADAPTER_SYNC. As description set Call the Java XI Adapter synchronously in PI Demo Examples, as communication Component (Service) set <SID>_105, as interface name and namespace set XiPatternInterface2_Out_sync and 3. Save the entry. 4. Call transaction SXMB_ADM, select Integration Engine Configuration. 5. Select the button Change Configuration. Switch to Change Mode and create a new entry with the following settings: Category: RUNTIME Parameter: IS_URL 62 March 2012

63 Subparameter: select the Sender/Receiver ID JAVA_XI_ADAPTER_SYNC Value: dest://java_xi_adapter_aae_sync 6. Save the entry. Calling the Integration Directory You perform the following configuration steps in the Integration Directory. For this scenario, the integrated configuration object is used for configuration. For more information, see Defining the Integrated Configuration. First, call the Integration Directory. On the Process Integration initial screen, choose Integration Directory. To configure this variant, a new configuration scenario is created. Selecting the Process Integration Scenario Perform the following steps to select the process integration scenario that you want to configure from the Enterprise Services Repository. Also, enter the name of the configuration scenario (in the Integration Directory) in which you want to group the configuration objects. 1. To call the model configurator, choose Tools Apply Model from ES Repository in the Integration Builder menu bar. This calls a wizard, which you use to select a model (in this case, a process integration scenario) and create a configuration scenario in the Integration Directory. 2. Make sure that the model type Process Integration Scenario is selected (radio button under Type of ES Repository Model). 3. Choose the input help (for the Name field) ( ) This calls an input help, which displays all process integration scenarios from the Enterprise Services Repository in a list. 4. Select the process integration scenario XiPatternOneStepScenario (software component version SAP BASIS 7.40, namespace from the Enterprise Services Repository and choose Apply. 5. Choose Continue. 6. Enter the name of the configuration scenario as: XiPatternOneStepScenario_Proxy2Proxy_SYNC_AAE. 7. Choose Finish and then Close. The system calls the model configurator. Selecting the Component View Check whether the component view Proxy2Proxy_sync_NoMapping is displayed. If it is not, choose the menu option Select Component View ( ). On the subsequent screen, select the component view (in the preview area) by double-clicking. Assigning Communication Components You perform the following steps to assign communication components to the application components of the process integration scenario. You use the business system components that you created before (see 2.2.6). 1. In the graphical editor, click on the lane representing the Sender application component. This calls the Assign Business System Component dialog box for the Sender application component (below the graphical representation of the process integration scenario). 2. To assign a communication component click in the input field in the Communication Component column and call the input help ( ). March

64 3. In the subsequent screen, select the communication component <SID>_105 and then choose Apply. 4. Choose Next Role ( ) to navigate to the configuration dialog for the application component Receiver. 5. Assign the same communication component <SID>_105 to the application component Receiver. Follow the same procedure as when assigning the communication component to the application component Sender. 6. Choose Assign. Configuring the Connection You perform the following steps to configure the connection of the process integration scenario. You activate the relevant sender-receiver relation (between the sender and receiver component) and assign both the sender and receiver a (sender or receiver) communication channel. You create the communication channel on the basis of the communication channel templates that the process integration scenario already contains. 1. In the graphical editor, click on the connection between the lanes representing the two application components. 2. This calls the Configure Connection dialog box for the connection between the actions (below the graphical representation of the process integration scenario). 3. On the Configure Connections screen, choose the tab page Connections from Component Assignment. The communication components that you assigned in the previous configuration step are displayed. The remaining tab pages contain further information about the process integration scenario, for example, the communication channel templates that are defined for the process integration scenario in the Enterprise Services Repository. 4. Assign the sender a communication channel. To do so, place the cursor in field Communication Channel for Sender Component and call input help ( ). 5. In the subsequent screen, select the communication channel XiPatternChannel_XiSender of communication component <SID>_105 and then choose Apply. 6. Following the same procedure (see step 4-5), assign the receiver communication channel XiPatternChannel_XiReceiver of <SID>_105. Generating the Configuration Objects In the following steps, you generate the relevant configuration objects based on the settings made in previous steps. 1. If not already selected, select the flag for Configuration for Advanced Adapter Engine. 2. Choose the push button Create Configuration Objects ( ). 3. Under General, select the radio button Generation. 4. Choose Start. The integrated configuration objects are generated based on the settings you made. Once generation is complete, the generation log is opened. The generation log displays the results of generation. The generation log enables you to analyze any errors that occurred during generation. 5. Close the generation log. 6. Close the model configurator. Choose Apply. 7. Save the configuration scenario. 64 March 2012

65 Manual Editing In the following steps, you edit the generated configuration objects manually and enhance the configuration settings made during generation. In this variant, you must edit the receiver communication channel after generation. 1. In the editor Display Configuration Scenario (for the open scenario XiPatternOneStepScenario_Proxy2Proxy _SYNC_AAE), on the tab page Objects open the communication channel ( ) XiPatternChannel_XiReceiver by double-clicking. 2. As target URL set the entry path for the application client 105: http(s)://server:httpport/sap/xi/engine?type=entry. As Authentication Data, enter client 105 and the user PIAPPLUSER (or a copy of the PIAPPLUSER) with its password in client 105. Note: 1. in case https then you should specify the host and the whole qualified domain name 2. If receiver server is lower than NW7.10 please consider that the URL should contain the http(s) port. Check the transaction SMICM and use the corresponding http(s) port instead of the URL which is used start the integration directory. 3. Save the communication channel. Activating the Change List 1. To do this, select the Change Lists tab page in the Integration Directory navigation area. 2. Choose Open Standard Change List. 3. Position the cursor on the Standard Change List node and choose Activate ( ) in the context menu 13.3 Execution Activate logging for synchronous messages A successfully processed synchronous message is only visible in the monitoring if the logging of synchronous messages is enabled, this is valid for the sender and receiver client as well as for the Advanced Adapter Engine. To activate the logging of synchronous messages in the sender and receiver client execute the following steps in client 105: 1. Call transaction SXMB_ADM and select Integration Engine Configuration. 2. Use the button Change Configuration to get the list of PI configuration parameters. 3. Set the parameter RUNTIME/ LOGGING_SYNC to 1. If the parameter does not exist yet, create it with this value. Default value is 0, which means that the successful synchronous messages are not persisted. To activate the logging of synchronous messages in the Advanced Adapter Engine Extended execute the following steps in the AEX system: 1. Call the NWA (NetWeaver Administrator) in the AEX system: http(s)://<server>:<port>/nwa and select Configuration --> Infrastructure Java System Properties. To execute this step you will need the role Administrator or ask the system administrator to adjust the parameter. 2. Select the Services tab and search for service XPI Adapter: XI. 3. In Extended Details search for the parameter xiadapter.logger.conf. 4. Using the button Modify you can change the parameter to AM=2. With this setting all synchronous messages are logged with business content. Default value is Empty which means that no messages are persisted. 5. Save the changes. March

66 Execution of the scenario You perform the following steps to check that the process integration scenario is executed without errors. To run the process integration scenario, you can use a transaction that is available in the SAP PI system, however this transaction should run in the business client but not on the client where the Integration Server is available i.e Logon to the SAP system of the business system, client Choose transaction SXIPATT1. 3. Enter values for the fields Name, Country, and Tel. 4. Set the flag for Synchronous Messaging. 5. Choose Send. 6. To check whether the data are transferred correctly from the sender to the receiver, switch to the receiver view (pushbutton Receiver View). When the message was sent without errors, the data are displayed that you entered in the sender view. A successfully processed synchronous message will only be visible if you activated the logging as described above. 7. Also check the processing of the message in the NWA (NetWeaver Administrator) of the AEX system. A successfully processed synchronous message will only be visible in AEX if you activated the logging as described above. 8. To start the monitoring in NWA use the link http(s)://<host>:<port>/pimon 9. Click on Message Monitor. 10. On the overview page select a time range and execute the search for messages. 11. From the Message Status Overview select the row with the corresponding sender and/or receiver. You will see how many messages are transmitted and the count of the message in error, scheduled, success, and canceled. In the second block of the Message Status Overview more detailed information for the selected row is displayed. 12. Additionally in the Status Values Tab, there exists a column named Number. This count of messages with specific status has got a link to the Database message monitoring. For one row in Message Status Overview there could up-to four entries (error, scheduled, success, and canceled.) If you hit the link on the count, there will be a jump into Database Monitoring. The advantage of this link is that the so called Message Header Data (Sender Party, Receiver Party, Interface, Sender Component, Receiver Component, Interface Namespace) will be considered and filled automatically. 14 Variant 12: One Sender and One Receiver synchronous Proxy-to-Proxy Communication using the Advanced Adapter Engine and Principle Propagation In this variant, the message is processed via the ABAP proxy runtime; the message is forwarded using the Adapter Engine instead of the Integration Server. Following the standard configuration suggested below one application system is used both as sender and receiver of messages. 66 March 2012

67 14.1 Prerequisites Activating Principle Propagation Trust Relationship Settings To use principal propagation you need to do some global configuration settings which are described in the prerequisite chapter Create Destination in the AEX If the HTTP Destination already exists, skip these steps. 1. Switch back to AEX NWA 2. Go to tab Configuration and click on Destinations. 3. Create HTTP Destination : <SID>_105_PP 4. Set URL to http(s)://<host of <SID>_105>>:<port>/sap/xi/engine?type=entry 5. Maintain SID, client and language. 6. Select Ignore SLL Server Certificate 7. Press next and choose Assertion Ticket for Authentication. 8. Save Changes. 9. Execute Ping. Result should be Ping not successful! Received HTTP response Design Objects Used You use the component view Proxy2Proxy_PP_sync_NoMapping in process integration scenario XiPatternOneStepScenario to configure this variant. The following graphic shows the component view: As described under 3.1, you can navigate to all design objects used from the component view. The following explains the design objects that play a role when using this component view. Interface Objects In this variant, the data structures at both the sender and receiver side are the same and no mapping is required. Nevertheless, two different service interfaces are used: outbound interface XiPatternInterface9_Out_sync for the sender and inbound interface XiPatternInterface9_In_sync for the receiver. This is due to the fact that the sender and March

68 receivers systems are SAP systems that communicate with each other by the ABAP proxy runtime. This communication type requires an outbound proxy and an inbound proxy (both generated resp. derived from the outbound resp. inbound interface). Summary of Design Objects Used The following table summarizes the additional design objects used. Design Objects Used Object Type (Name) Component View Proxy2Proxy_PP_NoMapping (Process Integration Scenario XiPatternOneStepScenario) Service interface (XiPatternInterface9_Out_sync) Service Interface (XiPatternInterface9_In_sync) Message Type (XiPatternMessage9) Description Describes the process flow and the message exchange for this variant. Describes the interface and data structure of the receiver. The data structure is the same for sender and receiver. The fault message type is used to handle application-specific errors that occur on the inbound side and that are reported back to the sender. Fault Message Type (XiPatternFaultMessage) Data Type (XiPatternDataType9) 14.3 Configuring the Process Integration Scenario Create the connection to the XI Adapter in the Advanced Adapter Engine To connect the sending client to the Java XI Adapter you have to create a HTTP Destination to the Adapter Engine. Do the following in the application client 105: Maybe the destination already exists because of the asynchronous PP configuration. If this is the case, execute only step 3 and skip the rest. 1. Call transaction SM Create a HTTP Destination to an external system (Type G). As name set JAVA_XI_ADAPTER_AEX_<SID>_PP, as description use Connection to Java XI Adapter in Adapter Engine. As target host set the host name of the adapter engine, as service set (Service No.) the HTTP(S) Port and as path set /XISOAPAdapter/MessageServlet?ximessage=true. Note: Ensure that you have maintained the proper URL of the Advanced Adapter Engine of PI system in SM59 of the sender application. You may get the warning Query string not allowed when saving the destination, just press enter to confirm the warning message. 3. Under Logon and Security select Basic Authentication and set the user PIAPPLUSER (or a copy of the PIAPPLUSER) with the corresponding password. This user and password will be checked against the Advanced Adapter Engine Extended system, where the message is sent to. 68 March 2012

69 4. Save the destination and execute Connection Test. Response Code HTTP 200 means successful connection. Activating the connection to the Java XI Adapter To enable the sending application system to send a message to the Java XI Adapter instead of the Integration Server you have to create a filter for the sending interface and have to set the URL to the Adapter Engine in the sending application client. Execute the following steps in the sending client 105: 1. Call transaction SXMSIF. 2. Create a new entry for Sender/Receiver ID with the name JAVA_XI_ADAPTER_AEX_PP_IF9_SYN. As description set Call the Java XI Adapter in PI PP Sync Demo Examples, as communication Component set <SID>_105, as interface name and namespace set XiPatternInterface9_Out_sync and 3. Save the entry. 4. Call transaction SXMB_ADM, select Integration Engine Configuration. 5. Select the button Change Configuration. Switch to Change Mode and create a new entry with the following settings: Category: RUNTIME Parameter: IS_URL Subparameter: select the Sender/Receiver ID JAVA_XI_ADAPTER_AEX_PP_IF9_SYN Value: dest://java_xi_adapter_aex_<sid>_pp 6. Save the entry. Calling the Integration Directory You perform the following configuration steps in the Integration Directory. For this scenario, the integrated configuration object is used for configuration. For more information, see Defining the Integrated Configuration. First, call the Integration Directory. On the Process Integration initial screen, choose Integration Directory. To configure this variant, a new configuration scenario is created. Selecting the Process Integration Scenario Perform the following steps to select the process integration scenario that you want to configure from the Enterprise Services Repository. Also, enter the name of the configuration scenario (in the Integration Directory) in which you want to group the configuration objects. 1. To call the model configurator, choose Tools Apply Model from ES Repository in the Integration Builder menu bar. This calls a wizard, which you use to select a model (in this case, a process integration scenario) and create a configuration scenario in the Integration Directory. 2. Make sure that the model type Process Integration Scenario is selected (radio button under Type of ES Repository Model). 3. Choose the input help (for the Name field) ( ) This calls an input help, which displays all process integration scenarios from the Enterprise Services Repository in a list. 4. Select the process integration scenario XiPatternOneStepScenario (software component version SAP BASIS 7.40, namespace from the Enterprise Services Repository and choose Apply. March

70 5. Choose Continue. 6. Enter the name of the configuration scenario as: XiPatternOneStepScenario_Proxy2Proxy_PP_SYNC_AAE. 7. Choose Finish and then Close. The system calls the model configurator. Selecting the Component View Check whether the component view Proxy2Proxy_PP_sync_NoMapping is displayed. If it is not, choose the menu option Select Component View ( ). On the subsequent screen, select the component view (in the preview area) by double-clicking. Assigning Communication Components You perform the following steps to assign communication components to the application components of the process integration scenario. You use the business system components that you created before (see 2.2.6). 1. In the graphical editor, click on the lane representing the Sender application component. This calls the Assign Business System Component dialog box for the Sender application component (below the graphical representation of the process integration scenario). 2. To assign a communication component click in the input field in the Communication Component column and call the input help ( ). 3. In the subsequent screen, select the communication component <SID>_105 and then choose Apply. 4. Choose Next Role ( ) to navigate to the configuration dialog for the application component Receiver. 5. Assign the same communication component <SID>_105 to the application component Receiver. Follow the same procedure as when assigning the communication component to the application component Sender. 6. Choose Assign. Configuring the Connection You perform the following steps to configure the connection of the process integration scenario. You activate the relevant sender-receiver relation (between the sender and receiver component) and assign both the sender and receiver a (sender or receiver) communication channel. You create the communication channel on the basis of the communication channel templates that the process integration scenario already contains. 1. In the graphical editor, click on the connection between the lanes representing the two application components. 2. This calls the Configure Connection dialog box for the connection between the actions (below the graphical representation of the process integration scenario). 3. On the Configure Connections screen, choose the tab page Connections from Component Assignment. The communication components that you assigned in the previous configuration step are displayed. The remaining tab pages contain further information about the process integration scenario, for example, the communication channel templates that are defined for the process integration scenario in the Enterprise Services Repository. 4. Assign the sender a communication channel. To do so, place the cursor in communication Channel field for Sender Component and call input help ( ). 70 March 2012

71 5. In the subsequent screen, select the communication channel XiPatternChannel_XiSender_PP of communication component <SID>_105 and then choose Apply. 8. Following the same procedure (see step 4-5), assign the receiver communication channel XiPatternChannel_XiReceiver_PP of communication component <SID>_105. Generating the Configuration Objects In the following steps, you generate the relevant configuration objects based on the settings made in previous steps. 1. If not already selected, select the flag for Configuration for Advanced Adapter Engine. 2. Choose the push button Create Configuration Objects ( ). 3. Under General, select the radio button Generation. 4. Choose Start. The integrated configuration objects are generated based on the settings you made. Once generation is complete, the generation log is opened. The generation log displays the results of generation. The generation log enables you to analyze any errors that occurred during generation. 5. Close the generation log. 6. Close the model configurator. Choose Apply. 7. Save the configuration scenario. Manual Editing In the following steps, you edit the generated configuration objects manually and enhance the configuration settings made during generation. In this variant, you must edit the receiver communication channel after generation. 1. In the editor Display Configuration Scenario (for the open scenario XiPatternOneStepScenario_Proxy2Proxy_PP_SYNC_AAE), on the tab page Objects open the communication channel ( ) XiPatternChannel_XiReceiver_PP by doubleclicking. 2. As target URL set the entry path for the application client 105: http(s)://server:httpport/sap/xi/engine?type=entry. As Authentication Data, enter client 105 and the user PIAPPLUSER (or a copy of the PIAPPLUSER) with its password in client 105. Note: 1. in case https then you should specify the host and the whole qualified domain name 2. If receiver server is lower than NW7.10 please consider that the URL should contain the http(s) port. Check the transaction SMICM and use the corresponding http(s) port instead of the URL which is used start the integration directory. 3. Save the communication channel. Activating the Change List 1. To do this, select the Change Lists tab page in the Integration Directory navigation area. 2. Choose Open Standard Change List. 3. Position the cursor on the Standard Change List node and choose Activate ( ) in the context menu Check Setup Before starting with the principal propagation configuration, the scenario is tested without principal propagation. This ensures, that the default case work. If the default case does not work, principal propagation also won t work. 1. Execute transaction SXIPATT1 (client 105). 2. Check only the Synchronous PP checkbox. March

72 3. Choose Send. 4. Execute transaction SXMB_MONI. 5. Filter messages by Sender-Interface XiPatternInterface9_Out_sync. 6. Message must be processed successfully. 7. Now filter for corresponding message, which is received by the client. Filter messages by Receiver-Interface XiPatternInterface9_In_sync. 8. Message must be processed successfully. Activating Principle Propagation Integration Directory 1. Launch Integration Directory 2. Select the Integrated Configuration XiPatternOneStepScenario_Proxy2Proxy_PP_SYNC_AAE 3. Check the checkbox Principle Propagation on Inbound Processing and Outbound Processing tab. 4. In the channel XiPatternChannel_XIReceiver select Addressing Typ HTTP Destination and in the field HTTP Destination add the destination <SID>_105_PP. 5. Activate the changes. 6. Move to the Channel Monitor and stop and start the channel. Modify Destination in the ABAP client 1. Call transaction sm Select destination JAVA_XI_ADAPTER_AEX_<SID>_PP. 3. On tab Logon & Security select Do Not Use a User and select Send Logon Ticket without Ref. to Target System. 4. Save the settings. Activating Principle Propagation Sender System 1. Logon to the sending system (<SID>_105) 2. Call transaction SXMB_ADM 3. Execute Configure Principle Propagation 4. Configure Interfaces (Interface Conf. for Transfer of User IDs) 5. Add the interface XiPatternInterface9_Out_sync with namespace and the user you are using. Principle Configuration settings will enforce SAPLogonTicket usage of destination JAVA_XI_ADAPTER_AEX_<SID>_PP Execution You perform the following steps to check that the process integration scenario is executed without errors. To run the process integration scenario, you can use a transaction that is available in the SAP PI system, however this transaction should run in the of the business client but not on the client where the Integration Server is available i.e Logon to the SAP system of the business system, client Choose transaction SXIPATT1. 3. Enter values for the fields Name, Country, and Tel. 4. Select only the checkbox Synchronous PP. 5. Choose Send. 6. For verification start NWA using http(s)://<host>:<port>/nwa 72 March 2012

73 7. Navigate to SOA / Monitoring / Message Monitoring and click on the Database Tab. 8. Search for the message and check, if it was processed successfully. 9. Check the Message Log, whether the message was Entering the SOAP Adapter with your ABAP user. 10. Logon to the ABAP System: <SID>_ Call transaction sxmb_moni 12. Find the message you send. 13. Check the details of the message. March

74 If your user is used in the tag <SAP:User> in the RunTime part of the SOAP Header in the Inbound Message of Sender and Receiver, Pricipal Propagation works correctly. 15 Variant 13: One Sender and One Receiver - Proxy-to-Proxy Communication using the Advanced Adapter Engine whereas Receiver send back an Acknowledgment Similar to the One Sender and One Receiver - Proxy-to-Proxy Communication using the Advanced Adapter Engine, in this variant, the message is processed via the ABAP proxy runtime; the message is forwarded using the Adapter Engine instead of the Integration Server. Moreover, the Receiver Component sends back an Acknowledgment to the Sender Component. Following the standard configuration suggested below one application system is used both as sender and receiver of messages. Enabling acknowledgment is only possible if the sender component requests for this. Therefore, in all cases ensure that the sender component especially the application used is able to send the acknowledgment request beside the application data. The program SXIPATT1 fulfills this prerequisite in form of a check box called System Ack and Appl. Ack. Enabling this Acknowledgment requires the following steps listed below and guides how you should maintain the corresponding setting. Enabling the functionality of acknowledgment, you may use the previous configuration of the One Sender and One Receiver - Proxy-to-Proxy scenario. Additionally, you should full fill some more setting mentioned in the description below especially, the paragraphs beginning with the Additional setting for the Acknowledgment Configuring the Process Integration Scenario Create the connection to the XI Adapter in the Advanced Adapter Engine To connect the sending client to the Java XI Adapter you have to create a HTTP Destination to the Adapter Engine. Do the following in the application client 105: 1. Call transaction SM Create a HTTP Destination to an external server (Type G). As name set JAVA_XI_ADAPTER_AAE, as description use Connection to Java XI Adapter in Adapter Engine Extended. As target host, set the host name of the adapter engine, as service set (Service No.) the HTTP Port and as path set /XISOAPAdapter/MessageServlet?ximessage=true. Note: Ensure that you have maintained the proper URL of the Advanced Adapter Engine of PI system in SM59 of the sender application. You may get the warning Query string not allowed when saving the destination, just press enter to confirm the warning message. 3. Under Logon and Security select Basic Authentication and set the user PIAPPLUSER (or a copy of the PIAPPLUSER) with the corresponding password. This user and password will be checked against the Advanced Adapter Engine Extended system, where the message is sent to. 4. Save and Test Connection 5. Additional setting for the Acknowledgment Call transaction SM March 2012

75 6. Create HTTP Connections to an external Server (Type G). This connection is relevant to the Acknowledgment(s) expected. As name set JAVA_XI_ADAPTER_ACK, as description use Connection to Java XI Adapter in Adapter Engine Extended. As target host, set the host name of the adapter engine, as service set (Service No.) the HTTP Port and as path set /MessagingSystem/receive/AFW/XI 7. Save and Test Connection Activating the connection to the Java XI Adapter To enable the sending application system to send a message to the Java XI Adapter instead of the Integration Server you have to create a filter for the sending interface and have to set the URL to the Adapter Engine in the sending application client. Execute the following steps in the sending client 105: 1. Call transaction SXMSIF. 2. Create a new entry for Sender/Receiver ID with the name JAVA_XI_ADAPTER. As description set Call the Java XI Adapter in PI Demo Examples, as communication Component set <SID>_105, as interface name and namespace set XiPatternInterface2_Out and 3. Save the entry. 4. Call transaction SXMB_ADM, select Integration Engine Configuration. 5. Select the button Change Configuration. Switch to Change Mode and create a new entry with the following settings: Category: RUNTIME Parameter: IS_URL Subparameter: select the Sender/Receiver ID JAVA_XI_ADAPTER Value: dest://java_xi_adapter_aae Note that this scenario cannot run in parallel with variant 6, if you set the RUNTIME/IS_URL parameter in SXMB_ADM all messages for this interface will be sent to the destination maintained here. 6. Save the entry Additional setting for the Acknowledgment 7. Call transaction SXMSIF. 8. Create a new entry for Sender/Receiver ID with the name JAVA_XI_ADAPTER_ACK. As description set Call the Java XI Adapter in PI Demo Examples, as communication Component set <SID>_105, as interface name and namespace set XiPatternInterface2_In and Note: Do NOT use the "Acknowledgement" radio button in Message Category. Specify the inbound interface instead of the outbound interface. 9. Save the entry. 10. Call transaction SXMB_ADM, select Integration Engine Configuration. 11. Select the button Change Configuration. Switch to Change Mode and create a new entry with the following settings: Category: RUNTIME Parameter: IS_URL Subparameter: select the Sender/Receiver ID JAVA_XI_ADAPTER_ACK Value: dest://java_xi_adapter_aae_ack 12. Save the entry. March

76 When you configure this variant, you will extend the configuration settings from variant One Sender and One Receiver - Proxy-to-Proxy scenario. You use the same configuration scenario XiPatternOneStepScenario_Proxy2Proxy_AAE. Using the Configuration Scenario In this variant, the configuration scenario XiPatternOneStepScenario_Proxy2Proxy_AAE created in variants 9 is extended. For this scenario, again the integrated configuration object is used for configuration. Additional setting for the Acknowledgment 1. Enabling of Acknowledgment request Go to the Integration Builder and open the corresponding scenario i.e. XiPatternOneStepScenario_Proxy2Proxy_AAE and open Sender Communication Channel i.e. XiPatternChannel_XISender. Ensure that in the Module tab under the Module Configuration, the parameter generatesysack is set to true. This parameter activates the default system acknowledgment which is per default true in higher releases. Go to the Parameter tab and chose the Acknowledgment Handling tab, and maintain the Http destination (from NWA), for example XI_Proxy2Proxy_via_AEX. 2. Save the communication 3. Activate the Change List. Important Notes: 1. Ensure that you have maintained the proper URL of the Advanced Adapter Engine of PI system in SM59 of the sender application. Because of former Simple Use Case variant the URL of Integration Engine is maintained instead of the Adapter Engine. 2. Ensure that you have maintained in communication channel the proper Target URL of the receiver in integration builder. Creating HTTP Destination in NWA of AEX Additional setting for the Acknowledgment 1. Launch the SAP NetWeaver Administration (alias: nwa) via URL http(s)://<host>:<port>/nwa in the address bar of the AEX where the adapter engine is involved. Go to SOA and Configuration and under the Infrastructure link click on the Destination. Create the http destination following the wizard.... Enter the following information in the corresponding fields: Hosting System: Local Java System A4Y - Involved AEX system, field is automatically filled. Destination Name: XI_Proxy2Proxy_via_AEX - see step 3 of Integration Directory, the destination name should be sync Destination Type: HTTP Click Next URL : http(s)://server:port/sap/xi/engine?type=entry System Id: SID Client: Client 105 Language: EN - Server and SAP business system data mentioned belongs to the involved proxy server/system Click Next Select From Logon Data List <Basic Authentication>, and enter user id and password. Note: The credentials maintained for the http destination should be available in the ABAP Client server as well. 76 March 2012

77 2. You can use the Ping Destination function to test the connection Execution Execution of the test scenario is similar to the execution of the One Sender and One Receiver - Proxy-to Proxy Communication using the Advanced Adapter Engine Extended (AEX). You perform the following steps to check that the process integration scenario is executed without errors. To run the process integration scenario, you can use a transaction that is available in the SAP PI system, however this transaction should run in one of the business client but not on the client where the Integration Server is available i.e Logon to the SAP system of the business system, client Choose transaction SXIPATT1. 3. Enter values for the fields Name, Country, and Tel. 4. Unselect the radio buttons of the Appl. Ack and Sys. Ack to test. 5. Post each Acknowledgment options choose Send. 6. Ensure the message is send via the Receiver View 7. Repeat the execution of the transaction SXIPATT1 with the following input - With selected Appl. Ack only - With selected Sys. Ack only - With selected Sys and Appl. Ack If you switch fast enough from sender to receiver view after having chosen Send, you can see the former data. Choose Refresh to check if the message was already processed and the data is updated accordingly. The message should be visible in the monitoring in client 105 and in the PI monitoring for the adapter engine, but not in Integration Server. Verification: 1. The test case should have a positive acknowledgments result. Positive acknowledgments ensures the following: System acknowledgments used by the runtime environment to confirm that an asynchronous message has reached the receiver. Application acknowledgments used to confirm that the asynchronous message has been successfully processed at the receiver. 2. Depending on the Ack option selected you can find corresponding entries in the transactionsxmb_moni of the sender/receiver proxy system of each processed message. Note: Transaction sxmb_moni - Monitor for Processed XML Messages from Client 105 Initial run of the SXIPATT1 without Ack request (unselected radio buttons of the Appl. and Sys. Ack), you will observe entries in sxmb_moni: Sender and Receiver is Client 105; Sender Namespace and Sender Interface is and XiPatternInterface2_Out respectively in one row. The Pipeline is here Sender. Receiver Namespace and Receiver Interface is and XiPatternInterface2_In respectively in one row. The Pipeline is here RECEIVER. Run of the SXIPATT1 with selected Appl. Ack only You should observe similar two entries in the sxmb_moni as before. One is the Pipline SENDER and the second is Pipeline RECEIVER. On the initial screen of the sxmb_moni there should be an icon of successful acknowledgment: for No errors in acknowledgment March

78 Run of the SXIPATT1 With selected Sys. Ack only You should observe similar to the Appl Ack two entries in the sxmb_moni. One is the Pipline RECEIVER and the second is Pipeline SENDER. On the initial screen of the sxmb_moni you there will be the same icon for a successful acknowledgment. Run of the SXIPATT1 With selected Sys and Appl. Ack Similarly to the run with single or double Ack, you will observe in this case two entries in sxmb_moni with successful icon as well. However, with double click on the Ack row of sxmb_moni, you should be able to see two Acknowledgments request Message IDs from Sender Client 105 and a single Acknowledgment Message ID coming back from Receiver Client 105. Alternatively, you can verify the result is in the NWA (SAP NetWeaver Administrator) of the AEX system. 1. Start NWA using http(s)://<host>:<port>/nwa 2. Navigate to SOA / Monitoring and click on the Message Status Monitoring Tab. 3. Navigate finding the proxy Client 105. For each sent and received message there will be an individual entry from and to the corresponding proxy Client and used interfaces. Here exist XiPatternInterface2_Out and XiPatternInterface2_In for Sender and Receiver interfaces respectively. - For messages sent without Ack then the number of messages sent and received are proportional - Depending on the Ack option selected you should have more number of messages sent from the Sender component to receiver. - Numbers of Acknowledgment processed are counted independently in NWA. The Interface and Namespace of Acknowledgment are called Acknowledgment and respectively. Message Status Overview aggregates the statistics according the Sender Interface; hence, there should be three of these: - Acknowledgment - XiPatternInterface2_In - XiPatternInterface2_Out 16 Variant 14: One Sender and One Receiver - Proxy-to-Proxy Communication using the Advanced Adapter Engine using Packaging 16.1 Packaging For the sake of improvement on performance, packaging has been introduced. This improvement works in such away by avoiding multiple HTTP calls to the same destination. Instead of that, group of asynchronous messages (EO) messages can be combined as a new multi-message and sent as a single HTTP call. This variant is similar to the One Sender and One Receiver - Proxy-to-Proxy Communication using the Advanced Adapter Engine. The message is processed via the ABAP proxy runtime; the message is forwarded to the Adapter Engine of AEX instead of the Integration Server available in SAP PI systems. 78 March 2012

79 For testing this functionality, you may use the previous configuration of the One Sender and One Receiver - Proxy-to-Proxy scenario completely as it is. Beside this there is only one place where you should enable the packaging functionality and that is the receiver communication channel of the receiver component in the Integration Directory. Note: If the corresponding scenario is already available according the description provided for One Sender and One Receiver - Proxy-to-Proxy scenario using the Advanced Adapter Engine, you can proceed directly with steps for enabling the packaging functionality only. This is described in the chapter of 1.1 especially the section Additional setting for the Packaging of this guide under the chapter Creating the Communication Channels for Sender and Receiver. In case not, configure the scenario as per description provided for One Sender and One Receiver - Proxy-to-Proxy scenario using the Advanced Adapter Engine. For Execution and Verification of the Packaging functionality, follow the subsequent sections. The demo program SXIPATT1 fulfills this prerequisite to send a multiple (identical) messages. The important field is called Msg. Count sending a multiple messages. Here you may enter a number of messages to be sent post activation of the packaging in the receiver communication channel Configuring the Process Integration Scenario Create the connection to the XI Adapter in the Advanced Adapter Engine To connect the sending client to the Java XI Adapter you have to create a HTTP Destination to the Adapter Engine. Do the following in the application client 105: 1. Call transaction SM Create a HTTP Destination to an external server (Type G). As name set JAVA_XI_ADAPTER_AAE, as description use Connection to Java XI Adapter in Adapter Engine Extended. As target host, set the host name of the adapter engine, as service set (Service No.) the HTTP Port and as path set /XISOAPAdapter/MessageServlet?ximessage=true. Note: Ensure that you have maintained the proper URL of the Advanced Adapter Engine of PI system in SM59 of the sender application. You may get the warning Query string not allowed when saving the destination, just press enter to confirm the warning message. 3. Under Logon and Security select Basic Authentication and set the user PIAPPLUSER (or a copy of the PIAPPLUSER) with the corresponding password. This user and password will be checked against the Advanced Adapter Engine Extended system, where the message is sent to. 4. Save and Test Connection Activating the connection to the Java XI Adapter To enable the sending application system to send a message to the Java XI Adapter instead of the Integration Server you have to create a filter for the sending interface and have to set the URL to the Adapter Engine in the sending application client. Execute the following steps in the sending client 105: 1. Call transaction SXMSIF. 2. Create a new entry for Sender/Receiver ID with the name JAVA_XI_ADAPTER. As description set Call the Java XI Adapter in PI Demo Examples, as March

80 communication Component set <SID>_105, as interface name and namespace set XiPatternInterface2_Out and 3. Save the entry. 4. Call transaction SXMB_ADM, select Integration Engine Configuration. 5. Select the button Change Configuration. Switch to Change Mode and create a new entry with the following settings: Category: RUNTIME Parameter: IS_URL Subparameter: select the Sender/Receiver ID JAVA_XI_ADAPTER Value: dest://java_xi_adapter_aae Note that this scenario cannot run in parallel with variant 6, if you set the RUNTIME/IS_URL parameter in SXMB_ADM all messages for this interface will be sent to the destination maintained here. 6. Save the entry Calling the Integration Directory You perform the following configuration steps in the Integration Directory. For this scenario, the integrated configuration object is used for configuration. The model configurator is not used in this case. For more information, see Defining the Integrated Configuration. First, call the Integration Directory. On the Process Integration initial screen, choose Integration Directory. When you configure this variant, you will extend the configuration settings from variant One Sender and One Receiver - Proxy-to-Proxy scenario. You use the same configuration scenario XiPatternOneStepScenario_Proxy2Proxy_AAE. Using the Configuration Scenario In this variant, the configuration scenario XiPatternOneStepScenario_Proxy2Proxy_AAE created in variants 9 is extended. For this scenario, again the integrated configuration object is used for configuration. Additional setting for the Packaging 1. Maintain the following parameters to activate the packaging in the block XI Packaging Parameter Unit Description Select Check box (value=true) Wait Time Number Package Size none Seconds Integer Number MB Select the check box enabling the packaging functionality Maintain the maximum wait time until the queue is processed when the maximum number of messages has not yet been reached Maximum number of messages per package Maximum total size of all messages in package Note: 80 March 2012

81 1. In case of https, then you should specify the host and the whole qualified domain name 2. If receiver server is lower than NW7.10 please consider that the URL should contain the http(s) port. Check the transaction SMICM and use the corresponding http(s) port instead of the URL which is used start the integration directory. 2. Save the communication channel. 3. Activate the change list. Important Notes: 1. Ensure that you have maintained the proper URL of the Advanced Adapter Engine of PI system in SM59 of the sender application. Because of former Simple Use Case variant the URL of Integration Engine is maintained instead of the Adapter Engine. 2. Ensure that you have maintained in communication channel the proper Target URL of the receiver in integration builder Execution Execution of the test scenario is similar to the execution of the One Sender and One Receiver - Proxy-to Proxy Communication using the Advanced Adapter Engine Extended (AEX). You perform the following steps to check that the process integration scenario is executed without errors. To run the process integration scenario, you can use a transaction that is available in the SAP PI system, however this transaction should run in one of the business client but not on the client where the Integration Server is available i.e Logon to the SAP system of the business system, client Choose transaction SXIPATT1. 3. Enter values for the fields Name, Country, and Tel. 4. Leave all radio buttons (Synchronous, Sys.Ack, Appl.Ack, sensitive data and EOIO) unselect. 5. Fill the number of messages you want to send in the field name called MsgCount. This number should be more than the threshold you maintained in the XI Packaging block of the receiver communication channel. For example if you the threshould number is three then send 4 messages or more. 6. Send the message via the corresponding tab of the transaction SXIPATT1 7. Ensure the message is send via the Receiver View or in SXMB_MONI If you switch fast enough from sender to receiver view after having chosen Send, you can see the former data. Choose Refresh to check if the message was already processed and the data is updated accordingly. The message should be visible in the monitoring in client 105 and in the PI monitoring for the adapter engine, but not in Integration Server. Verification: The test case should have a positive packaging result. Result observation from Sender/Receiver proxies: 1. The messages should be sent successfully. 2. Depending on the number of the messages sent, you can find corresponding entries in the transaction SXMB_MONI of the sender/receiver proxy system of each processed message. Note: Transaction SXMB_MONI - Monitor for Processed XML Messages from Client 105 March

82 - You should observe n message entries of the Sender Client 105. Sender Namespace and Sender Interface is and XiPatternInterface2_Out respectively for each message. The Pipeline is here Sender. - You should observe n message entries of the Receiver Client 105. Receiver Namespace and Receiver Interface is and XiPatternInterface2_In respectively for each message. The Pipeline is here RECEIVER. - As the sender and receiver system is client 105 then there should be n x 2 entries for the sent and received messages in the sxmb_moni for just executed messages. Result observation from NWA (SAP NetWeaver Administrator) of the AEX system. 1. Start NWA using http(s)://<host>:<port>/nwa 2. Navigate to SOA / Monitoring and select the Link message Monitoring. 3. Select the Database tab and use the advanced mode restricting your monitoring target. 4. Enter the time frame first then select the check box Message Header Data and enter the Sender/Receiver component name. 5. You should be able to see n messages in the Message List block for sent and received Messages (n rows). 6. Select (mark) one of the messages from the Message List and go to the Message Detail block, here you should be able to see at least 4 tabs,namely Message Detail, Message Log, Message Content and Further Links. 7. Select Message Content tab and select further PayLoad from Message tree. You should be able to view the message send. 8. Select the Message Log from the Message Detail tab. (Expand the Tray Option to maximum). Ensure that there is successful entries (Status=information) are written beside other process information. Time Information Description. Information.. Information XI Packaging (Bulk Mode) Option: true Information Delivered this Message to the Message Collector. It will be processed later. Information MSG_FORMING_BULK Information XISOAP Bulk Processing: Creating a Multi- Message for Packaging Information XISOAP Bulk Processing: Retrieved from the bulk for processing Information XISOAP Bulk Processing: This message will be added to the Multi-Message Information XISOAP Bulk Processing: Successfully Created the Multi-Message. Number of child Messages : 1 Information Message was successfully transmitted to endpoint <local> using connection SOAP_http://sap.com/xi/XI/System Information Message status set to DLVD 82 March 2012

83 Result observation from MDT (Message Display Tool) of the AEX system. 1. Start MDT using http(s)://<host>:<port>/mdt 2. Select Message from <Database> 3. Enter restriction criteria such as Sender/Receiver Components and time ranges. 4. Navigate to SOA / Monitoring and select the Link message Monitoring. 5. Execute Start tab. 6. You should be able to see n messages in the Message List block for sent and received Messages (n rows). Note: the Message List is configurable. 7. Select (mark) one of the messages by selecting the check box in the left column and select the tab Details. There will be a new window generated and you should be able to see at least 3 tabs,namely Message Data, Message Content and Audit Log. 8. Select the Audit Log scroll the page if necessary. You should see the same information shown in the table before. Note that the messages sent are asynchronous. 17 Variant 15: One Sender and One Receiver using Advanced Adapter Engine Extended with Parameterized Mapping This variant enables you to configure and execute message exchange with Parameterized Mapping: One sender (file directory XiPattern1) sends a message to one receiver (file directory XiPattern2). Hereby, the message is exchanged between sender and receiver adapter by using one Advanced Adapter Engine Extended. A mapping is executed when the message is forwarded to the receiver. Here Mapping used is Parameterized Mapping. Parameterized Mapping provides an option to pass configured parameters while executing a mapping. The Parameter needs to be defined while defining Mapping in repository. The Actual values can be provided in directory while configuring the Mapping for scenarios Design Objects Used You use the component view File2File_WithParameterizedMapping in process integration scenario XiPatternOneStepScenario to configure this variant. The following graphic shows the component view: March

84 As described under 3.1, you can navigate to all design objects used from the component view. The following explains the design objects that play a role when using this component view. Interface Objects You can see that the outbound interface entered in the connection editor is different. If you navigate further to the message type and data type used, you will see that the data structure on the sender side is different than the previous variants (defined by the data type XiPatternDataType4). However, the asynchronous service interface XiPatternInterface5 is entered as the inbound interface at the receiver. This service interface references the message type XiPatternMessage5. The data structure of the message is defined by the data type XiPatternDataType5. The structure of data type XiPatternDataType5 is different to the structure of data type XiPatternDataType4 (which is used in the component view) in the following ways: In data type XiPatternDataType4, two separate elements are used to specify the person s first and last name, whereas in data type XiPatternDataType5, only one element is used (Name) having Title (from Parameter defined in Message Mapping XiPatternMessage4ToMessage5) prefixed and concatenated with FirstName and LastName. In data type XiPatternDataType4, the name of the element that specifies the telephone number is MobileNumber, whereas in data type XiPatternDataType5, it is ContactNumber having CountryCode (from Parameter defined in Message Mapping XiPatternMessage4ToMessage5) prefixed and concatenated with MobileNumber. Mapping Objects A mapping between the sender and receiver data structures must therefore be executed for the message to be processed. In the connection editor, navigate to the relevant mapping objects by choosing the tab page Assign Mapping. Double-click on the name of the operation mapping (XiPatternInterface4ToInterface5) to open it. The names of the source and target interface, as well as the source and target message are displayed. The message mapping used is displayed under Mapping Program. Parameters are defined here which are mapped to parameters of message mapping. Doubleclick to open the message mapping (XiPatternMessage4ToMessage5). 84 March 2012

85 In the message mapping editor, the tab page Design displays the source and target structures. You have the option of displaying for which elements of the source and target structure mappings are to be executed. To do so, choose Display Dependencies Display All ( ). Also you can view Fields CountryCode & Title defined as parameter on Signature tab of Message Mapping XiPatternMessage4ToMessage5. Summary of Design Objects Used The following table summarizes the design objects used. Design Objects Used Object Type (Name) Component View File2File_WithParametrizedMapping (Process Integration Scenario XiPatternOneStepScenario) Service interface (XiPatternInterface4) Service interface (XiPatternInterface5) Description Describes the process flow and the message exchange if a mapping is to be executed during message processing (the interfaces on the sender and receiver sides are not identical) Describes the interface and data structure of the receiver. The data structure is different to the data structure of the sender. Message Type (XiPatternMessage4) Message Type (XiPatternMessage5) Data Type (XiPatternDataType4) Data Type (XiPatternDataType5) Operation mapping (XiPatternInterface4ToInterface5) Message Mapping (XiPatternMessage4ToMessage5) Describes the mapping between the source and target interface Describes the mapping between the source and target structure in detail 17.2 Configuring the Process Integration Scenario To configure this variant, a new configuration scenario is created. Selecting the Process Integration Scenario Perform the following steps to select the process integration scenario that you want to configure from the Enterprise Services Repository. Also, enter the name of the configuration scenario (in the Integration Directory) in which you want to group the configuration objects. 1. To call the model configurator, choose Tools Apply Model from ES Repository in the Integration Builder menu bar. This calls a wizard, which you use to select a model (in this case, a process integration scenario) and create a configuration scenario in the Integration Directory. 2. Make sure that the model type Process Integration Scenario is selected (radio button under Type of ES Repository Model). 3. Choose the input help (for the Name field) ( ) March

86 This calls an input help, which displays all process integration scenarios from the Enterprise Services Repository in a list. 4. Select the process integration scenario XiPatternOneStepScenario (software component version SAP BASIS 7.40, namespace from the Enterprise Services Repository and choose Apply. 5. Choose Continue. 6. Enter the name of the configuration scenario as: XiPatternOneStepScenario_AAEX_Param_Mapping. 7. Choose Finish and then Close. The system calls the model configurator. Selecting the Component View Check whether the component view File2File_WithParameterizedMapping is displayed. If it is not, choose the menu option Select Component View ( ). On the subsequent screen, select the component view (in the preview area) by double-clicking. Assigning Communication Components You perform the following steps to assign communication components to the application components of the process integration scenario. You use the business system components that you created before (see 2.2.7). 1. In the graphical editor, click on the lane representing the Sender application component. This calls the Assign Business System Component dialog box for the Sender application component (below the graphical representation of the process integration scenario). 2. To assign a communication component click in the input field in the Communication Component column and call the input help ( ). 3. In the subsequent screen, select the communication component <SID>_AAEX_FileSystem_XiPattern1 and then choose Apply. 4. Choose Next Role ( ) to navigate to the configuration dialog for the application component Receiver. 5. Assign the communication component <SID>_AAEX_FileSystem_XiPattern2 to the application component Receiver. Follow the same procedure as when assigning the communication component to the application component Sender. 6. Choose Assign. Configuring the Connection You perform the following steps to configure the connection of the process integration scenario. You activate the relevant sender-receiver relation (between the sender and receiver component) and assign both the sender and receiver a (sender or receiver) communication channel. You create the communication channel on the basis of the communication channel templates that the process integration scenario already contains. 1. In the graphical editor, click on the connection between the lanes representing the two application components. 2. This calls the Configure Connection dialog box for the connection between the actions (below the graphical representation of the process integration scenario). 3. On the Configure Connections screen, choose the tab page Connections from Component Assignment. The communication components that you assigned in the previous configuration step are displayed. The remaining tab pages contain further information about the process integration scenario, for example, the communication channel templates that are defined for the process integration scenario in the Enterprise Services Repository. 86 March 2012

87 4. Assign the sender a communication channel. To do so, place the cursor in the field Communication Channel for the Sender Component, in the push button bar choose Create Communication Channel With Template ( ). In the subsequent wizard you can create a communication channel based on a communication channel template. 5. Choose Continue. The default communication channel template on the subsequent screen is that which was assigned to the sender application component in the process integration scenario (name XiPatternChannel_FileSender, software component version SAP BASIS 7.40, namespace 6. Choose Continue. Rename the communication channel on the next screen to XiPatternChannel_FileSender_ParamMap. 7. Confirm your selection by choosing Finish. 8. Following the same procedure (see step 4-7), assign the application component of the receiver a communication channel based on the default communication channel template (name XiPatternChannel_FileReceiver, software component version SAP BASIS 7.40, namespace Rename the Receiver Communication Channel to XiPatternChannel_FileReceiver_ParamMap. Generating the Configuration Objects In the following steps, you generate the relevant configuration objects based on the settings made in previous steps. 1. If not already selected, select the flag for Configuration for Advanced Adapter Engine. 2. Choose the push button Create Configuration Objects ( ). 3. Under General, select the radio button Generation. 4. Choose Start. The integrated configuration objects are generated based on the settings you made. Once generation is complete, the generation log is opened. The generation log displays the results of generation. The generation log enables you to analyze any errors that occurred during generation. 5. Close the generation log. 6. Close the model configurator. Choose Apply. 7. Save the configuration scenario. Manual Editing In the following steps, you edit the generated configuration objects manually and enhance the configuration settings made during generation. In this variant, you must edit the communication channels after generation. 1. In the editor Display Configuration Scenario (for the open scenario XiPatternOneStepScenario_AAEX_Param_Mapping), on the tab page Objects open the communication channel ( ) XiPatternChannel_FileSender_ParamMap by doubleclicking. 2. Under File Access Parameter in the Source Directory field, enter the path in the file directory that you defined previously (see 2.2.4). In the case of the sender communication channel, enter the whole path for the file directory XiPattern4. Example: C:/<selected path>/xipatterns/xipattern1 3. Enter File Name as XiPatternSenderFileParamMap.xml 4. Save the communication channel. 5. To check if the channel works you can directly jump to the channel monitoring using the menu path Communication Channel Channel Monitoring March

88 Channel Monitoring will show last activated state of the Channel. In case Channel is being created, you need to activate it before it can be seen in Channel Monitoring via direct jump from Directory. 6. The PI Communication Channel Monitoring page will open up where you can do a self test for the channel. To do this click on the button Ping Channel. 7. The status page for the channel will show up with detailed information of the executed self test. 8. Follwing step 1-2, edition to file for Receiver Channel XiPatternChannel_FileReceiver_ParamMap is needed. Enter File name as XiPatternReceiverFileParamMap.xml. 9. Save the communication channe. 10. Open the Channel Monitoring and check the status of the channel. 11. Open Integrated Configuration and go to Tab Receiver Interface. Enter Values for Parameter Title and CountryCode. Save Integrated Configuration. Activating the Change List 1. To do this, select the Change Lists tab page in the Integration Directory navigation area. 2. Choose Open Standard Change List. 3. Position the cursor on the Standard Change List node and choose Activate ( ) in the context menu Execution You perform the following steps to check that the process integration scenario is executed without errors. In directory XiPattern1, Rename the file ZXiPatternSenderFileParamMap.xml to XiPatternSenderFileParamMap.xml. The file will be moved from the directory within the next 60 seconds. Check whether a file has arrived in directory XiPattern2. Open the file. The structure will have changed: the first and the second name of the person have been concatenated and prefixed with Title; the field for the MobileNumber has a new name ContactNumber prefixed with CountryCode. The value of Field Title and CountryCode in received message is as per defined in Integrated Configuration tab Receiver Interface. Monitoring contains one entry for this exchange of messages. Rename the file XiPatternSenderFileParamMap.xml back to ZXiPatternSenderFileParamMap.xml to stop continuous flow of messages. Furthermore, you can check the processing of the messages in the message monitoring as in Variant Execution with Channel Scheduling Channel scheduling functionality can be used to group channels and maintain times when these channels shall be available. Availability means if a channel is part of channel schedule, then it will automatically be up and running within times as per configuration of schedule. Outside Channel schedule time, the channel will be in status stopped. With PI 7.40, Introduction of a new view/tab in Communication Channel Monitor is done where scheduling information would be visualized in a calendar view. Name of the tab "Schedule Allow to select a single channel or a set of channels and display their scheduling details in one view If a channel is scheduled and schedule is Active, tab Availability Times will have information about duration when channel will be up and running 88 March 2012

89 Creating a Schedule Creation of Schedule can be done in Communication Channel Monitoring 1. Go to PI Start Page via http(s)://<host>:<port>/dir. 2. Click on link Configuration and Monitoring Home. 3. Click on the tab Monitoring and then on sub-tab Adapter Engine. 4. And then Click on link Communication Channel Monitor. 5. In new window, Click on Tab Availability Planning. 6. Create a Schedule of Type Once. Click on Button New and Select Once from drop down values 7. In Description field enter name of Schedule ParamMap_Once. If another schedule exists with the same name, delete it first before creation. 8. Select Start Date as <CurrentDate>, Start Time as <nexthour>, End Date as <CurrentDate> and End Time as <nexthour + 1> 9. Click on Communication Channels tab within Schedule creation to add channels to the schedule. 10. Enter XiPatternChannel_FileSender_ParamMap in Communication Channel field and press Use Filter. Result will be only Channel XiPatternChannel_FileSender_ParamMap being displayed in table Scheduled Channels. 11. Select checkbox Active and then click on Save. You will get a confirmation message for the same. 12. Now Create another Schedule of type Daily. Click on Button New and Select Daily from drop down values 13. In Description field enter name of Schedule ParamMap_Daily. If another schedule exists with the same name, delete it first before creation. 14. Select Start Date as <CurrentDate>, Start Time as <nexthour>, End Date as <CurrentDate>, End Time as <nexthour + 1> and End By as <CurrentDate + 2> so as to make this schedule as recurring for 3 days (<CurentDate> till <CurrentDate + 2>). 15. Click on Communication Channels tab within Schedule creation to add channels to the schedule. 16. Enter XiPatternChannel_FileReceiver_ParamMap in Communication Channel field and press Use Filter. Result will be only Channel XiPatternChannel_FileReceiver_ParamMap being displayed in table Scheduled Channels. 17. Select checkbox Active and Save. You will get a confirmation message for the same. Execution of a Schedule You perform the following steps to check that View of Channel Schedule in Channel Monitoring and Channel Schedule functionality is executed without errors. 1. Open Channel Monitoring for both channels XiPatternChannel_FileSender_ParamMap and XiPatternChannel_FileReceiver_ParamMap in two different browser windows. 2. Check if Control Data of both the above channels is Automatic. If not, click on Automatic Control to change control data of channels to Automatic. 3. The moment control data of above channels is Automatic, channel will be in status Stopped. This happens as per settings of created Channel Schedule ParamMap_Once and ParamMap_Daily. 4. Perform below step 5 - step15 within Channel Monitoring browser for both channels. 5. A newly introduced tab called Channel Availability can be seen in main table of channel. 6. Click on Tab Channel Availability 7. All the buttons Start, Stop, Automatic Control, External Control, Mass Change and Ping Channel will be disabled in this view. 8. Two frames are available. One displays Monthly and another Weekly Schedule for the selected Channel. March

90 9. Monthly Schedule by default will display information for the current month. There are buttons to check Schedule Information for previous and next months as well. It will contain 1 block for each day of the month. 10. Weekly Schedule by default will display information for current week starting Sunday. It will have 1 block for each day with 1 row for each hour of the day starting from 12:00 AM and ending with 11:00 PM. 11. The block for schedule of current date will be available in orange background color, green color for future schedule (in case of recurring) and will not be displayed for recurring schedule in past. 12. To display Schedule information for other weeks of the month, click on a block of day from Monthly Schedule. Weekly schedule information will change to week containing the selected day. 13. Created Schedule ParamMap_Once or ParamMap_Daily can be seen as one block as per configured date and time. The schedule block has information about Schedule Validity, Schedule Name and Schedule Type. The format of information is <Schedule Start Time> :<Schedule Name> (<Schedule Time Period>) <Schedule End Time> (<Schedule Type>). 14. Click on Channels Tab to return back to Channels display. 15. Now in Channel details table, another newly introduced tab called Schedule can be seen. 16. Click on tab Schedule. 17. The new view is similar to view of Channel Availability tab as above except that basic Channel table is still visible. Repeat above step 7 to step Check if current time is still non-availability time of schedule. Wait until current time is reached to available time of schedule. 19. Channel XiPatternChannel_FileSender_ParamMap and XiPatternChannel_FileReceiver_ParamMap will start automatically once current time is equal to schedule available time. The same can be checked by reaching tab Administration Information on Channel details table. Information regarding Time Stamp, Action (Started/Stopped) and Person Responsible (Schedule <ScheduleName> will be available. 20. In directory XiPattern1, Rename the file ZXiPatternSenderFileParamMap.xml to XiPatternSenderFileParamMap.xml. The file will be moved from the directory within the next 60 seconds. 21. Check whether a file has arrived in directory XiPattern2. Open the latest arrived file. The structure will have changed: the first and the second name of the person have been concatenated and prefixed with Title; the field for the MobileNumber has a new name ContactNumber prefixed with CountryCode. The value of Field Title and CountryCode in received message is as per defined in Integrated Configuration tab Receiver Interface. 22. Rename the file XiPatternSenderFileParamMap.xml back to ZXiPatternSenderFileParamMap.xml to stop continuous flow of messages. 23. For next 1 hour (Schedule available time), both the channels will be in started status. Once Schedule available time is over, Channels will again be stopped as per action performed by underlying Schedule (ParamMap_Once and ParamMap_Daily). 24. Since schedule ParamMap_Daily is a recurring schedule, check again on <currentdate +1> and <CurrentDate + 2>. The channel XiPatternChannel_FileReceiver_ParamMap will be started during its schedule available time. Start channel XiPatternChannel_FileSender_ParamMap manually and rename file in sender directory to check flow of message for the scenario. 25. Rename the file XiPatternSenderFileParamMap.xml back to ZXiPatternSenderFileParamMap.xml to stop continuous flow of messages. 90 March 2012

91 18 Variant 16: One Sender and Two Receivers using Advanced Adapter Engine Extended with Message Order at Runtime This variant enables you to configure and execute message exchange with Message Order at Runtime: One sender (file directory XiPattern1) sends a message to two receivers (file directory XiPattern2 and XiPattern2). Hereby, the message is exchanged between sender and receiver adapter by using one Advanced Adapter Engine Extended. The order in which messages are retrieved in Receiver File Directory is defined by the order in the Receiver Interfaces panel of Integrated Configuration within Integration Directory. In this variant, configuration of Sender Channel with EOIO (Exactly Once In Order) setting is done and an additional receiver channel is added so as to handle multiple receivers for EOIO messages. Hence two messages will be sent out for respective receivers. Message Order at Runtime settings provide an option to define an order for received messages to follow. The checkbox for the same is available within Receiver Interface tab of Integrated Configuration while configuring the scenarios in Directory Design Objects Used As described under 3.1, you can navigate to all design objects used in this variant in ESR. The following explains the design objects that play a role while configuring this variant. Interface Objects In this case outbound interface and inbound interfaces are different. If you navigate further to the message type and data type used, you will see that the data structure on the sender side is different than the previous variants (defined by the data type XiPatternDataType6). However, the asynchronous service interface XiPatternInterface7 and XiPatternInterface8 is entered as the inbound interface at the receiver. This service interface references the message types XiPatternMessage7 and XiPatternMessage8 respectively. The data structure of the message is defined by the data types XiPatternDataType7 and XiPatternDataType8 respectively. The structure of data types XiPatternDataType7 and XiPatternDataType8 is more of subsets of structure of data type XiPatternDataType6 defined in the following ways: In data type XiPatternDataType6, two separate elements are used to specify the person s first and last name, whereas in data type XiPatternDataType7, only one element is used (FullName) which is concatenation of FirstName and LastName. In data type XiPatternDataType6, two separate elements are used to specify the person s Address (AddressLine1 and AddressLine2), whereas in data type XiPatternDataType8, only one element FullAddress is used which is concatenation of AddressLine1 and AddressLine2. Mapping Objects A mapping between the sender and receiver data structures must therefore be executed for the message to be processed. In ESR, navigate to the relevant mapping objects. Double-click on name of the operation mapping (XiPatternInterface6ToInterface7and8) to open it. The names of the source and target interface, as well as the source and target message are displayed. The message mapping used is displayed under Mapping Program. Double-click to open the message mapping (XiPatternMessage6ToMessage7and8). In the message mapping editor, the tab page Design displays the source and target structures. March

92 You have the option of displaying for which elements of the source and target structure mappings are to be executed. To do so, choose Display Dependencies Display All ( ). Summary of Design Objects Used The following table summarizes the design objects used. Design Objects Used Object Type (Name) Service interface (XiPatternInterface6) Service interface (XiPatternInterface7) Service interface (XiPatternInterface8) Description Describes the interface and data structure of the sender and receiver. The data structure of receiver is different to the data structure of the sender. Message Type (XiPatternMessage6) Message Type (XiPatternMessage7) Message Type (XiPatternMessage8) Data Type (XiPatternDataType6) Data Type (XiPatternDataType7) Describes the data structure of the sender message Describes the data structure of the receiver message Data Type (XiPatternDataType8) Operation mapping (XiPatternInterface6ToInterface7and8) Message Mapping (XiPatternMessage6ToMessage7and8) Communication Channel Templates for Sender and Receiver (XiPatternChannel_FileSenderO_MultiRe ceiver, XiPatternChannel_FileReceiverO_MapR untime) Describes the mapping between the source and target interface Describes the mapping between the source and target structure in detail. Mapping with Message split is done here. Specifies the sender (and receiver) adapter configuration details, which are defined at design time. Communication channel templates enable a communication channel to be preconfigured at design time Configuring the scenario in Integration Directory You perform the following configuration steps in the Integration Directory of the Advanced Adapter Engine Extended. For this scenario, the integrated configuration object is used for configuration. For more information, see Defining the Integrated Configuration. Calling the Integration Directory First, call the Integration Directory. To call the Integration Directory for the Advanced Adapter Engine Extended System, open the Advanced Adapter Engine Extended Start Page using the URL: http(s)://<aex-host>:<aex-port>/dir and click on link Integration Builder. 92 March 2012

93 Creating a Configuration Scenario Perform the following steps to create a configuration scenario to group the configuration objects. 1. In the Integration Directory main menu, choose Object New. 2. Under Administration select Configuration Scenario. 3. Enter the name XiPatternOneStepScenario_AEX_MessageOrderRuntime. 4. Choose Create. 5. Save the configuration scenario. Creating the Communication Channels for Sender and Receiver Perform the following steps to create the communication channels. 1. In the Integration Directory main menu, choose Object New. 2. Under Collaboration Profile select Communication Channel. 3. Call the input help ( ) for the Communication Component. 4. Select the communication component <SID>_AAEX_FileSystem_XiPattern1 and choose Apply. 5. In field Communication Channel enter XiPatternChannel_FileSenderO_MapOrderRuntime. 6. Under Add to Scenario select XiPatternOneStepScenario_AEX_ MessageOrderRuntime (input help). 7. Choose Create. 8. The newly created communication channel is opened. 9. In the menu of the communication channel object editor select Communication Channel Apply Template. 10. Select the template XiPatternChannel_FileSenderO_MultiReceiver. 11. Choose Apply. 12. Under File Access Parameter in the Source Directory field, enter the path in the file directory that you defined under In the case of the sender communication channel, enter the whole path for the file directory XiPattern1. Example: C:/<selected path>/xipatterns_aaex/xipattern1 13. In the field Adapter Engine select the central adapter engine. 14. Save the communication channel. 15. Following the same procedure, create communication channel XiPatternChannel_ FileReceiver_MapOrderRuntime (communication component <SID>_AAEX_FileSystem_XiPattern2) using the template XiPatternChannel_FileReceiverO_MapRuntime. Enter the path in file directory that you defined under In the case of the receiver communication channel, enter whole path for file directory Example: C:/<selected path>/xipatterns_aaex/xipattern2 16. Save the communication channel. 17. Following above, create one more communication channel XiPatternChannel_ FileReceiver_MapOrderRuntime (communication component <SID>_AAEX_FileSystem_XiPattern3) using the template XiPatternChannel_FileReceiver. This channel will be used for EOIO with Multiple receivers. Enter the path in file directory that you defined under In the case of the receiver communication channel, enter whole path for file directory March

94 Example: C:/<selected path>/xipatterns_aaex/xipattern3 18. Enter File name as XiPatternReceiverFileEOIO.xml 19. Save the communication channel. 20. Save the scenario. 21. Activate the change list. Creating the Integrated Configuration 1. In the Integration Directory main menu, choose Object New. 2. Under Collaboration Agreement select Integrated Configuration. 3. Call the input help ( ) in the field Communication Component. 4. Select the communication component <SID>_AAEX_FileSystem_XiPattern1 and choose Apply. 5. In the fields Interface and Namespace enter XiPatternInterface6 and respectively. The input help may not show the interface and namespace. Create the entry manually or choose Category Any in the F4 Help. 6. Under Add to Scenario select XiPatternOneStepScenario_AEX_ MessageOrderRuntime (input help). 7. Choose Create. 8. In tab Inbound Processing select the communication channel XiPatternChannel_FileSenderO_MapOrderRuntime. For the software component version of sender interface select SAP BASIS In the tab Receiver select the communication component <SID>_AAEX_FileSystem_XiPattern Add one more receiver <SID>_AAEX_FileSystem_XiPattern3 using option Insert Receiver. 11. In tab Receiver Interfaces first select Receiver <SID>_AAEX_FileSystem_XiPattern2. For name and namespace enter XiPatternInterface6 and respectively. In Software Component Version set SAP BASIS The input help may not show the interface and namespace. Create the entry manually. 12. Insert one more condition using option Add button. Now use F4 help to select Operation Mapping XiPatternInterface6ToInterface7and8. This will automatically add two more receiver interface XiPatternInterface7 and XiPatternInterface8 with their namespaces and software Component Version. 13. Select checkbox Maintain Order at Runtime for received messages to follow the above defined order. 14. Now Select Receiver <SID>_AAEX_FileSystem_XiPattern3. For name and namespace enter XiPatternInterface6 and respectively. In Software Component Version set SAP BASIS The input help may not show the interface and namespace. Create the entry manually. 94 March 2012

95 1. In the tab Outbound Processing select the communication channel XiPatternChannel_ FileReceiver_MapOrderRuntime of respective Components <SID>_AAEX_FileSystem_XiPattern2 and <SID>_AAEX_FileSystem_XiPattern3. 2. Save the integrated configuration. 3. Save the Configuration Scenario. Activating the Change List 1. To do this, select the Change Lists tab in the Integration Directory navigation area. 2. Choose Open Standard Change List. 3. Position the cursor on the Standard Change List node and choose Activate ( )) in the context menu Execution You perform the following steps to check that the process integration scenario is executed without errors. In directory XiPattern1 rename the file ZXiPatternSenderFileMapOrderRuntime.xml to XiPatternSenderFileMapOrderRuntime.xml. The file will be moved from the directory within the next 60 seconds. 1. Check whether 3 files have arrived in directory XiPattern2. Check the file name XiPatternReceiverFileMapOrderRuntime<NUMBER> having counter information. Compare the counter information for all the files. The counter of received files should be in the order as per Interfaces order in Receiver Interface tab of Integrated Configuration in Directory. This works as per new setting Mapping Order At Runtime. The structure of first file will be same as per the sent file but structure of other two files will have changed as per definition in Message Mapping. 2. Check whether a file has arrived in directory XiPattern3. Open the file. The structure of this file will be same as per the sent file. 3. Also check the processing of message in NWA (NetWeaver Administrator) or PI Monitoring of AEX system 4. To start Monitoring use the link http(s)://<host>:<port>/pimon 5. Click on Message Monitor. 6. On the overview page go to Database tab and click on link Advanced 7. Select Time period as Last Hour, click on Message Header Data checkbox and enter Sender Component as <SID>_AAEX_FileSystem_XiPattern1 and execute search for messages. 8. Messages fulfilling the criteria will be displayed. Click on button Open Settings Dialog to add EOIO columns to be displayed. 9. Add columns Quality of Service, Sequence ID and Serialization Context from Hidden Columns to Displayed Columns. Press Apply and Ok 10. Now the messages displayed will have information about Quality of Service, Sequence ID and Serialization Context as well Messages are displayed in total. Out of these, 3 will have Queue Name EOIOMOR as per entered in Sender channel XiPatternChannel_FileSender_MapOrderRuntime. These 3 are as per EOIO from sender <SID>_AAEX_FileSystem_XiPattern1 with multiple receivers <SID>_AAEX_FileSystem_XiPattern2 and <SID>_AAEX_FileSystem_XiPattern3. Receiver <SID>_AAEX_FileSystem_XiPattern2 has two conditions and hence 2 messages. Serialization Context column has information about receiver component to verify above. 12. Also one condition of receiver <SID>_AAEX_FileSystem_XiPattern2 is using an operation mapping for further split hence we have remaining 2 messages 13. Rename the file XiPatternSenderFileMapOrderRuntime.xml back to ZXiPatternSenderFileMapOrderRuntime.xml to stop continuous flow of messages. March

96 Furthermore, you can change order of condition on Receiver Interface tab of Integrated Configuration and check retrieved timestamp for received files. 19 Variant 17: One Sender and One Receiver using Advanced Adapter Engine Extended With Mapping and encrypted persistent storage (PCI-compliant) In this variant a new scenario will be created. The message is sent to one receiver. A mapping is executed when the message is forwarded to the receiver. Additionally, the message payload is encrypted before it is stored on database to fulfill the requirements of the PCI standard. The process of encrypting and decrypting data is transparent to the user and message monitoring tools, as it only affects the data which is written/read from database. For this kind of data encryption, the system needs to be configured upfront (see prerequisite chapter 2.2.2). Make sure that this configuration has been made by an administrator before proceeding Design Objects Used You use the component view File2File_WithMapping_PCI in process integration scenario XiPatternOneStepScenario to configure this variant. The following graphic shows the component view: As described under 3.1, you can navigate to all design objects used from the component view. The following explains the design objects that play an additional role when using this component view. Interface objects Special versions of the XiPatternInterfaces are used for this variant. These versions use the same message type and data type like the other interfaces, also the used mapping is performing the same transformation as in variant 4. However, in contrast to the other interfaces, for the versions used in this variant the Sensitive Data flag is set, which is the relevant configuration option for the payload to be encrypted at runtime. Please refer to variant 4 for the description of the message type used by the interface and what the mapping will do. The interfaces used by this variant are: 96 March 2012

97 - XiPatternInterface1_PCI for the sender and - XiPatternInterface2_PCI for the receiver. Mapping Objects As the same message types are used as in variant 4, a mapping is needed in this variant as well. In the connection editor, navigate to the relevant mapping objects by choosing the tab page Assign Mapping. Double-click on the name of the operation mapping (XiPatternInterface1_PCIToInterface2_PCI) to open it. The names of the source and target interface, as well as the source and target message are displayed. The message mapping used is displayed under Mapping Program. Double-click to open the message mapping (XiPatternMessage1ToMessage2). In the message mapping editor, the tab page Design displays the source and target structures. You have the option of displaying for which elements of the source and target structure mappings are to be executed. To do so, choose Display Dependencies Display All ( ). Summary of Additional Design Objects Used The following table summarizes the additional design objects used. Additional Design Objects Used Object Type (Name) Component View File2File_WithMapping_PCI (Process Integration Scenario XiPatternOneStepScenario) Service interface (XiPatternInterface1_PCI, XiPatternInterface2_PCI) Description Describes the process flow and the message exchange if a mapping is to be executed during message processing (the interfaces on the sender and receiver sides are not identical) and message payload will be encrypted at runtime. Describes the interface and data structure of the receiver. The data structure is different to the data structure of the sender. Message Type (XiPatternMessage2) Data Type (XiPatternDataType2) Operation mapping (XiPatternInterface_PCI1ToInterface2_P CI) Message Mapping (XiPatternMessage1ToMessage2) Describes the mapping between the source and target interface Describes the mapping between the source and target structure in detail 19.2 Configuring the Scenario in Integration Directory When you configure this variant, you will create a new configuration scenario. March

98 Using the Configuration Scenario Choose the process integration scenario XiPatternOneStepScenario in the model configurator and use the name XiPatternOneStepScenario_AAEX_PCI for the configuration scenario. Please refer to chapter 3.2 for the description how to start and use the model configurator. Selecting an Process Integration Scenario (Component View) Check whether the component view File2File_WithMapping_PCI is displayed. If it is not, choose the menu option Select Component View ( ). On the subsequent screen, select the component view (in the preview area) by double-clicking. Assigning Communication Component Assign the communication component <SID>_AAEX_FileSystem_XiPattern1_PCI to the application component Sender, and the communication component <SID>_AAEX_FileSystem_XiPattern2_PCI to the application component Receiver. (refer to chapter 3.2 for the description how to assign the components). Configuring the Connection When you configure the connection, you use the Channel Templates for creating the sender and receiver channel. You change the default names for the communication channels and use the name XiPatternChannel_FileSender_PCI for the sender and XiPatternChannel_FileReceiver_PCI for the receiver. (refer to chapter 3.2 for the description how to configure the connection using the channel templates). Generating the Configuration Objects To do so, proceed as described in chapter 3.2. When you have checked the generation log, close it and save the configuration scenario. Manual Editing In the following steps, you edit the generated configuration objects manually and enhance the configuration settings made during generation. In this variant, you must edit the communication channels and the Integrated Configuration after generation First you need to edit the communication channels, which were generated with the Channel Templates. Therefore you navigate to channels and configure the whole path for file directory XiPattern1_PCI as Source Directory field for the sender channel XiPatternChannel_FileSender_PCI and the path for file directory XiPattern2_PCI for the receiver channel XiPatternChannel_FileReceiver_PCI, as described in chapter 3.2 section Manual editing Now you need to edit the generated Integrated Configuration configuration object. You will configure an additional persistence step, so that messages of this scenario will be persisted before and after the mapping step. As the interface of a message is changed during the mapping, this will result in a persistent message version for both the sender interface (before mapping) and the receiver interface (after mapping). This way you can verify that the payload of both versions was encrypted (because both the sender- and the receiver interface are relevant for encryption as they both got the Sensitive Data flag set). To configure the additional persistence step, you need to perform the following steps: 1. In the editor Display Configuration Scenario (for the currently edited scenario XiPatternOneStepScenario_AAEX_PCI), on the tab Objects, open the Integrated Configuration by double-clicking it. 2. Navigate to the Advanced Settings tab of the Integrated Configuration. 3. Find the Staging section and choose Use scenario-specific configuration. 4. In the DropDown list for step Mapping, choose the value Store(3). The following screenshot shows that setting: 98 March 2012

99 Activating the Change List 4. To do this, select the Change Lists tab in the Integration Directory navigation area. 5. Choose Open Standard Change List. 6. Position the cursor on the Standard Change List node and choose Activate ( )) in the context menu Executing the Use Case You perform the following steps to check that the process integration scenario is executed without errors. In directory XiPattern1_PCI, copy the file ZXiPatternSenderFile2.xml. Rename the file to XiPatternSenderFile2.xml. The file will be moved from the directory within the next 60 seconds. Check whether a file has arrived in directory XiPattern2_PCI. Open the file. The structure will have changed: the first and the second name of the person have been concatenated; the field for the telephone number has a new name. Furthermore, you can check the processing of the messages in the message monitoring as in Variant 1. Monitoring contains one entry for this exchange of messages (with two versions as persistence before and after the mapping was configured). Try to open the message payload from the monitoring. As described, the encryption/decryption of the payload happens transparent, so that the payload should be visible as with a normal message. Try to open both versions of the message and view the payload. Now, you can verify in the Persistence-Layer Encryption Monitor that all versions of the message were encrypted with the key you ve configured. Therefore, navigate to http(s)://<host>:<port>/nwa and follow the link to SOA -> Monitoring -> Persistence-Layer Encryption Monitor In the Monitoring, It will show a summary of all the key names which were used to encrypt messages. In this case the Key used to encrypt the message is TestingKey which you can see under Encryption Keys Table. March

100 Additionally you can also check the processed messages in the Messages table. In the list of messages for the key you ve used, you need to be able to find the message id of the message which was created for your scenario. To verify, that the payload is indeed encrypted on database, you can rename the key which was used to encrypt the message. Therefore, navigate to the Keystore PI_KEY_STORE as described in the appendix. Find the relevant key in the Keystore and rename it using the Rename button. This optional verification needs administrator rights as the encryption key has to be changed. Please ask the system administrator to execute them or to provide you the necessary authorization. Renaming the key means that key for decrypting the message is not available. When the key is not available, the message payload cannot be decrypted so that it should not be possible to see it in the message monitoring. When you now open the message again and try to view the payload, you should get an error message that the key to decrypt the message isn t available. Now rename the key to its original name, and open up the message again. Now you should be able to view the payload again. 100 March 2012

101 20 Appendix 20.1 Setting up the system for payload encryption Before the payload of messages can be encrypted, the system needs to be configured initially. This includes the creation of a dedicated Keystore, the generation and storage of an encryption key in that Keystore and the setup of message payload encryption in the messaging system Creating the Keystore and generating the encryption key As a prerequisite for the persistence layer encryption, a dedicated Keystore has to be available and it needs to contain a key which can be used for encryption. To check, whether or not the Keystore is available, you need to access Certificates and Keys in the Netweaver Administrator (NWA), under tab Configuration / Security, as depicted in the following screenshot: In the tab Key Storage of that tool, all available Keystores ( Views ) are listed. Please check, if a view with the name PI_KEY_STORE is already existing. If this view is already existing, please proceed with the Key creation. If there is no view with that name yet, you need to create it. Therefore, click on the button Add View in the Key Storage Views section: A popup dialog will appear. Enter PI_KEY_STORE as View Name, and click Create : March

102 This will create a new Keystore, which is now listed in the Key Storage list. Now you need to create a Key, which can be used for encryption. Therefore, select the Keystore PI_KEY_STORE in the Key Storage list and click on Create in the Details section of the Keystore at the bottom: A popup dialog to create the new entry will appear. Enter some alias name for the key, for example: TestingKey as Entry Name, then click on the Next button: 102 March 2012

103 On the next page, enter the mandatory values ( countryname and an arbitrary description for commonname ), then confirm the creation by clicking the Finish button: When the creation was successful, you now should be able to see the newly created entry in the View Entries tab, consisting of an entry for the Private Key: If the Keystore PI_KEY_STORE is existing, and it contains a valid Key, the prerequisites for the persistence layer encryption are met and you can proceed to the next step Global configuration of the MessagingSystem for March

104 persistence layer encryption After the Keystore is available and an encryption key was created, the persistence layer encryption needs to be enabled and configured in the MessagingSystem. Therefore, go to the Netweaver Administrator (NWA) and open the Java System Properties view under Configuration / Infrastructure / Java System Properties, as depicted in the following screenshot: In the Java System Properties configuration UI, go to tab Services, find the Service XPI Service: Messaging System and select it. Now go to the Extended Details section and find the relevant properties by filtering for persistencelayer. This query should show the 3 properties which are relevant for the persistence layer encryption configuration. The viewname property must not be changed. To enable the persistence layer encryption, select property messaging.security.persistencelayerencryption.enabled, press the Modify button and enter the value true. Then you need to provide the key alias which should be used to find the encryption key. This is the EntryName, which you used while creating the Key in Step 1. Select property messaging.security.persistencelayerencryption.currentkeyalias and press Modify. Now enter the name of the Key and confirm. Afterwards don t forget to save your changes. The following screenshot summarizes the configuration of the MessagingSystem properties: 104 March 2012

105 After you ve saved your changes, you can verify that the settings were accepted by checking the status page for the persistence layer encryption of the MessagingSystem by accessing the following link: http(s)://<host>:<port>/messagingsystem In the navigation pane on the left hand side, click on Persistence-Layer Encryption Monitor. On the opening page, you can verify the current values used by the MessagingSystem. Check there, that your configurations were applied correctly. After the configuration of Step 1 and 2 are done, the system is ready to encrypt messages Monitoring Tools PI Component Monitor for NWA The PI Component Monitor displays the availability and operational status details of the various SAP PI or AEX components. Specially, this is necessary for the AEX installation as in this installation, there is no RWB (Runtime workbench) available. It allows users to do a Self-Test (Tab: Repeat Self-Test) and check availability (Tab: Repeat-Ping) as well. The PI Component Monitor in NWA (SAP NetWeaver Administrator) includes components listed in the table below if the point of access is <All Component Types> for Component Type and <All> for Component Name. Within these maximum selection criteria, the following components should be displayed for SAP PI and AEX. # Component Types Comment SAP PI Component Type = <All Component Types> AND Component Name=<All> 1 Central Adapter Engine Yes Yes 2 Mapping Runtime of central adapter engine Yes Yes 3 Integration Directory Yes Yes 4 Enterprise Service Repository Yes Yes 5 Integration Engine Yes ** AEX March