SAP NetWeaver Process Integration - Demo Example Configuration

Transcription

1 SAP NetWeaver 7.40 f SAP NetWeaver Process Integration - Demo Example Configuration 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 Community Network (SDN) titled SAP NetWeaver Process Integration 7.4 Demo Examples Configuration.

3 1 Preface Introduction Overview Prerequisites Overview of the Configuration Procedure Estimating Configuration Duration Notes on Tools and Transactions Notes on Upgrade from SAP NetWeaver PI 7.* to SAP NetWeaver General Configuration Steps Providing the Necessary Users and Authorizations Authorizations for Configuration Steps in the SAP System Authorizations for Configuring the IDoc Variant Authorizations for Configuring the Web Service Variants Authorizations for Configuring the Message Exchange in the IDoc and RFC Variant Authorizations for Configuring the message exchange in the WS Variant Deactivate the advanced Authorization check in application clients Setting Up the System Landscape System Landscape Setting Up the Logical Systems Assigning the Logical Systems to Clients Client Copy Execute the CTC template to configure the clients Checking the System Landscape in the System Landscape Directory Technical System Landscape Business System Description Check Configuration of the Local Integration Engine Configuring the Role of the Business Systems Registering Queues Defining Communication Components, Communication Channels and Receiver Rules (Integration Directory) Creating Communication Parties for B2B Communication Defining Communication Components Defining the Integration Process Component Editing the Communication Channels Defining Receiver Rules Further Steps for Configuring the Demo Examples Activating the BSP Application Generating the Flight Data Configuring Process Integration Scenarios for Proxy-to- Proxy Communication Checking Flight Seat Availability (Proxy-to-Proxy Communication)

4 5.1.1 Business Description (Brief) Configuration in Integration Directory Executing and Testing Booking a Single Flight (Proxy-to-Proxy Communication) Business Description (Brief) Configuration in Integration Directory Executing and Testing Booking Connecting Flights (Proxy-to-Proxy Communication) Business Description (Brief) Preliminary Steps Configuration in Integration Directory Executing and Testing Configuring Process integration scenarios for Proxy-to- RFC/IDoc Communication Checking Flight Seat Availability (Proxy-to-RFC Communication) Configuration in Integration Directory Executing and Testing Booking a Single Flight (Proxy-to-IDoc Communication) Special Settings for IDoc Communication in the SAP System Configuration in Integration Directory Executing and Testing Booking a Single Flight (Proxy-to-IDoc AAE Communication) Special Settings for IDoc Communication in the SAP System Configuration in Integration Directory Executing and Testing Booking Connecting Flights (Proxy-to-Proxy/IDoc Communication) Special Settings for IDoc Communication in the SAP System Configuration in Integration Directory Executing and Testing Booking Connecting Flights (Proxy-to-Proxy/IDoc AAE Communication) Special Settings for IDoc Communication in the SAP System Configuration in Integration Directory Executing and Testing Configuring Process Integration Scenarios for B2B-like Communication Preliminary Steps Checking Flight Seat Availability (Proxy-to-Web-Service Communication) Activating Web Service Configuration in Integration Directory Executing and Testing Checking Flight Seat Availability (Web Service-to-Web-Service Direct Communication) Activating the WS Cache Notification for the Agency Configuration in Integration Directory Executing and Testing March 2012

5 7.4 Booking a Single Flight (Proxy-to-Web-Service Communication) Activating Web Service Configuration in Integration Directory Activating Consumer Proxy for Asynchronous Response Executing and Testing Configuring Process Integration Scenarios for Communication with File/FTP Adapter Distributing Booking Order Data (Proxy-to-File System) Business Description (Brief) Preliminary Steps Distributing Booking Order Data (Proxy-to-File System for XML File) Distributing Booking Order Data (Proxy-to-File System for CSV File) Executing and Testing Appendix Monitoring Monitoring in Runtime Workbench Monitoring in PI Configuration and Monitoring Home Monitoring in Integration Server (SXMB_MONI) Monitoring in Solution Manager Notes on Troubleshooting

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 all the configuration steps that are necessary to execute the SAP NetWeaver Process Integration demo examples (former: SAP Exchange Infrastructure demo examples (SAP PI demo examples)) on the basis of SAP NetWeaver This document is updated on a regular basis in SAP Developer Network (SDN) at SAP NetWeaver Process Integration Demo Examples of Configuration. Intended Audience Make sure you have the latest version of this document by checking SDN before you begin the configuration. 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 demo examples. 6 March 2012

7 2 Introduction The SAP NetWeaver Process Integration demo examples (referred to simply as demo examples) are part of SAP NetWeaver Process Integration (PI). The demo examples demonstrate the basic communication scenarios and guide you step-by-step through the technical concepts and tools. The demo examples comprise a set of simple process integration scenarios. These process integration scenarios are shipped as part of SAP NetWeaver Process Integration. For a detailed description of the individual process integration scenarios, see Demo Examples. You must configure the demo examples before you can execute them. This guide describes the configuration steps for all the available demo examples. We recommend that you use the standard configuration described in this documentation. Since the demo examples are only intended to demonstrate SAP NetWeaver PI and are not scenarios for productive use, SAP only provides support for the standard configuration. See also the note under SAP recommends that you configure the demo examples in exactly the sequence that is given by the structure of this document. This is because the structure of this document is adapted to the needs of those learners who require an initial step-by-step introduction to the concepts of SAP NetWeaver PI (the most simple process integration scenarios are looked at first, before progressing to the more complex process integration scenarios and sophisticated communication variants). Additionally, if you configure the demo examples in exactly the sequence that is given by the structure of this document, you can rely on these step-by-step guidelines in every detail. Nevertheless, it is possible to configure the demo examples in another sequence, as required. The few steps you have to consider in particular in this case are noted in the text, but are not described in detail. 2012

8 3 Overview 3.1 Prerequisites List of required steps Step Documentation 1. You have installed SAP NetWeaver 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 You have imported the content for the Enterprise Services Repository corresponding to the latest support package/patch. 3. You have configured SAP NetWeaver You have configured the System Landscape Directory (SLD). 5. You have activated the necessary ICF services (Internet Communication Framework) to enable you to execute the BSP application (see 4.6). 6. You have installed SAP Solution Manager 7.1 Importing ESR Content The demo examples are located in the Enterprise Services Repository in the software component SAP BASIS, software component version SAP BASIS 7.40, in the namespaces and Configuration of SAP NetWeaver Process Integration Configuring, Working with and Administering System Landscape Directory SAP Note You can find the corresponding guides on SAP Service Marketplace SAP Enhancement Package 1 for SAP Solution Manager 7.0 Note that you set up the demo examples in your development or test system, but not in your productive system. 3.2 Overview of the Configuration Procedure This section contains an overview of the configuration of the demo examples. For a detailed description of the individual configuration steps for each process integration scenario and each individual communication variant, see the respective chapter. The configuration of the demo examples consists of the following: 8 March 2012

9 General configuration steps The general configuration steps form the basis for the configuration of the individual process integration scenarios. Configuration of the individual process integration scenarios and each individual communication variant General Configuration Steps Providing the Necessary Users and Authorizations To be able to call the transactions in the SAP system of the Integration Server that are required for configuration, you must have the relevant authorizations. Furthermore, to configure receiver communication channels you require particular system users so that you can call the relevant functions in the target application. For more information, see 4.1. Setting Up the System Landscape The demo examples (process integration scenarios) are defined in the Enterprise Services Repository independently of a specific system landscape. During configuration, you configure the process integration scenarios for a particular system landscape. The SAP standard configuration is based on a system landscape comprising a travel agency system and two airline systems. This system landscape is simple enough to be easily understood yet complex enough to illustrate the most important concepts of process integration. To set up this system landscape with a minimum of effort, we recommend that you simulate the different business systems by using different clients of one SAP system. Note that all the configuration steps specified in this guide are based on the implementation of this system landscape. To generate the clients for the different business systems, you use client copy. For more information, see Describing the System Landscape in the System Landscape Directory To be able to access the metadata for the business systems in the later configuration steps, you must describe the system landscape in the System Landscape Directory. During configuration of the individual process integration scenarios in the Integration Directory, you define how messages are to be exchanged between the business systems involved (and executable integration processes, if applicable). For more information, see 4.3. Configuring the Business Systems as the Local Integration Engine You must configure the involved business systems (clients) of the system landscape as the local Integration Engine and define the connection to the central Integration Server. For more information, see 4.4. Defining Communication Components, Communication Channels and Receiver Rules To be able to address business systems as the sender or receiver of messages, you must define them as communication components (business system communication components) in the Integration Directory. 2012

10 If you want to use an integration process as the sender or receiver of messages at runtime, you must also define the integration process as a communication component (integration process component). The demo examples include two process integration scenarios that use an integration process (MultipleFlightBooking). The configuration instructions for these process integration scenarios include instructions for defining a communication component for an integration process. To define the outbound processing of messages (from the Integration Server to a receiver business system), you must assign a communication channel to the corresponding communication component. The communication channel contains the technical information that is used for outbound processing of the message. The adapter type of the communication channel depends on the type of the receiver adapter. The SAP standard configuration uses communication channels with the adapter type XI (for communication using the proxy runtime), RFC (for communication using the RFC adapter), WS (for Web service communication) and IDoc (for communication using the IDoc adapter or IDoc AAE adapter (IDoc Advanced Adapter Engine Java IDoc Adapter)). You define receiver rules to define the logical routing. Receiver rules are defined generically and can be reused in the different receiver determinations of the individual scenarios. For more information, see 4.5. Activating the BSP Application and Generating the Flight Data A BSP (Business Server Pages) application is available in the SAP system for executing the demo examples once configuration is complete. You must activate this BSP application. To be able to access flight data during execution of the demo examples, you first have to generate it. You can use a data generation program to do this. For more information, see 4.6. Configuring Process Integration Scenarios for Specific Communication Options The process integration scenarios for the demo examples and all the corresponding objects (such as interface objects and mapping objects) are shipped with SAP NetWeaver PI. A process integration scenario contains the business logic for a particular cross-system process. This includes interfaces for message exchange, mappings for message transformation, and executable integration processes. The process integration scenarios are defined independently from the system landscape in which they are executed. During configuration of the demo examples, you map the relevant process integration scenarios to the specific system landscape that you set up and described in the general configuration steps. One or more component views are defined for each process integration scenario, reflecting the different communication options that can be configured (for example, Proxy-to-Proxy, Proxy-to-IDoc, Proxy-to-IDoc AAE communication). During configuration of a process integration scenario, you define the following: The adapter-specific settings Some communication options (for example, Proxy-to-IDoc communication) require settings that are specific for the respective adapter (in this example, the IDoc adapter). These settings have to be defined before you can begin with the configuration of the process integration scenario in the Integration Directory. The senders and receivers of messages 10 March 2012

11 These can be executable integration processes or business systems. To use the business systems of the underlying system landscape as senders and receivers of messages, you access the defined business system components. The receiver interfaces (and mappings, if used) of messages The details for inbound and outbound message processing for particular sender/receiver pairs To specify the details for inbound and outbound message processing, you use the defined communication channels. To define the relevant objects in the Integration Directory, use the model configurator. This tool enables you to automate most of the configuration steps for a process integration scenario. The following table lists the available process integration scenarios and the respective communication options that can be configured on the basis of this document: Available Process integration scenarios and Supported Communication Options Process integration scenario CheckFlightSeatAvailability SingleFlightBooking MultipleFlightBooking DistributeBookingOrderInformation Communication Option (Chapter) Proxy-to-Proxy (see 5.1) Proxy-to-RFC (see 6.1) Proxy-to-Web Service (see 7.2) Web Service-to-Web Service (see 7.3) Proxy-to-Proxy (see 5.2) Proxy-to-IDoc (see 6.2) Proxy-to-IDoc AAE variant with Java IDoc adapter (see 6.3) Proxy-to-Web Service (see 7.4) Proxy-to-Proxy including an integration process (see 5.3) Proxy-to-Proxy/IDoc including an integration process (see 6.4) Proxy-to-Proxy/IDoc AAE including an integration process (see 6.5) Proxy-to-File System (see 8.1) 3.3 Estimating Configuration Duration The time estimates below indicate approximately how long it will take you to configure the demo examples: General Configuration Steps Configuration Step Setting Up Users/Authorizations Setting Up the System Landscape (Client Copy) Duration Estimate 30 minutes 15 (+30) minutes for each client The user activities for entering the necessary information take approximately 15 minutes for each client. Note that once these activities have been completed, the client copy itself then takes approximately 30 minutes (for each client). Note also that you can only execute one client copy in a system at one time. Take this into account and schedule the later configuration steps accordingly. 2012

12 Configuring the Business Systems as the Local Integration Engine Describing the System Landscape in the System Landscape Directory Defining the business system components and the communication channels Generating the flight data and activating the BSP application 15 minutes (total time for all three application clients) 1 hour 30 minutes 20 minutes (total) Configuring Process Integration Scenarios for Specific Communication Options Process Integration Scenario (Variant) CheckFlightSeatAvailability (Proxy-to-Proxy) CheckFlightSeatAvailability (Proxy-to-RFC) CheckFlightSeatAvailability (Proxy-to-Web Service) CheckFlightSeatAvailability (Web Service-to- Web Service) SingleFlightBooking (Proxy-to-Proxy) SingleFlightBooking (Proxy-to-IDoc) Alternative: SingleFlightBooking (Proxy-to-IDoc AAE) variant with Java IDoc adapter SingleFlightBooking (Proxy-to-Web Service) MultipleFlightBooking (Proxy-to-Proxy) MultipleFlightBooking (Proxy-to-Proxy/IDoc) MultipleFlightBooking (Proxy-to-Proxy/IDocAAE) DistributeBookingOrderInformation (Proxy-to-File System) Estimate of Configuration Duration 30 minutes 30 minutes 30 minutes 30 minutes 30 minutes 2 hours and 30 minutes 2 hours (special settings for Idoc communication in SAP system) + 30 minutes (configuration in Integration Directory) 2 hours and 30 minutes 2 hours (special settings for IDoc communication in SAP system) + 30 minutes (configuration in Integration Directory) 40 minutes 45 minutes 1 hour 15 minutes (special settings for IDoc communication in SAP system) + 45 minutes (configuration in Integration Directory) 1 hour 15 minutes (special settings for IDoc communication in SAP system) + 45 minutes (configuration in Integration Directory) 1 hour 40 minutes (preparatory tasks) + 20 minutes (configuration in Integration Directory) The times given above are approximate and are intended as a guide to help you with planning. 3.4 Notes on Tools and Transactions You use different tools to execute the individual configuration steps. Transactions in the SAP system of the Integration Server To log on to the SAP system and call the transactions required for the demo example configuration, you have to create a user XIDEMO with the following roles: SAP_XI_DEMOAPP, SAP_XI_ADMINISTRATOR, SAP_XI_CONFIGURATOR and SAP_XI_MONITOR. 12 March 2012

13 For the IDoc and Web Services Configuration you also have to assign the roles SAP_BC_SRV_EDI_ADMIN, SAP_BC_WEBSERVICE_ADMIN. If the initial configuration is done and the demo examples are used to run after SP implementation or system changes, to test the usability, a user XIDEMO_EXE with only the roles SAP_XI_DEMOAPP_EXECUTE and SAP_XI_MONITOR may be created to execute this tests. For more information, see chapters 4.1.1, and Note that you can call the transactions in the SAP system in the user menu or in the SAP menu. To call the user menu, choose User menu ( ) in the pushbutton bar. To call the SAP menu, choose SAP menu ( pushbutton bar. System Landscape Directory Integration Builder (user interface of Integration Directory) You use the Integration Builder to configure the demo examples. ) in the You call the System Landscape Directory and the Integration Builder on the initial screen of SAP NetWeaver Process Integration. To call the initial screen, choose Process Integration Start Integration Builder in the user menu. For more information about calling the relevant tools and transactions, see the descriptions of the respective configuration steps. 3.5 Notes on Upgrade from SAP NetWeaver PI 7.* to SAP NetWeaver 7.40 If you have already configured the demo examples based on SAP NetWeaver PI 7.1 and are upgrading to SAP NetWeaver 7.40, note the following: Deactivate the advanced Authorization check in the application clients In 7.30 a new advanced authorization check for proxy applications was introduced that will cause the existing demo examples to fail. To deactivate this check please execute the following steps: 1. Login to the client of the travel agency (client 105). 2. Call transaction SXMB_ADM Integration Engine Configuration Specific Configuration 3. Add the parameter AUTHORITY_ON_MSG_TYPE from category RUNTIME with the value Save the entry. 5. Do the same in Clients 106 and 107. Checking Activation of BSP Applications Check that the BSP (Business Server Pages) application is still activated after the upgrade (see 4.6.1) 2012

14 Activate the following SICF nodes if not already activated: /sap/public/bc/icons /sap/public/bsp/sap/system /sap/public/bsp/sap/public/bc /sap/public/bsp/sap/htmlb /sap/public/bc/ur /sap/bc/bsp/sap/system /sap/bc/bsp/sap/public/bc If using the Web service scenarios, also check the activation of the SICF nodes mentioned in chapter 7.1. Deleting the old IDoc Metadata From the Cache With transaction IDX2, delete the IDoc metadata for FLIGHTBOOKING_CREATEANDRESP01 and FLIGHTBOOKING_SENDRESPONSE01 (Delete button). Configuring the Process Integration Scenarios The demo process integration scenarios that are shipped with SAP NetWeaver 7.1 respectively are not different (from a business perspective) from those shipped with SAP NetWeaver In productive scenarios you can generally assume that, after a release upgrade, process integration scenarios will be different from a business perspective from the previous version. This is not the case with the demo examples. Moreover, the configuration objects previously created are still valid after the upgrade (configuration objects are independent of the underlying SAP NetWeaver release), the one exception being communication channels with adapter type IDoc, see below). This means that, for the most part, you can still run the demo examples after an upgrade. You have the following options: 1. You reconfigure the demo examples in the Integration Directory. In this case, you create a separate configuration scenario for each process integration scenario that you want to configure in the Integration Directory and use the model configurator. No new configuration objects are created during generation, but the objects that were created during configuration based on an earlier release of SAP NetWeaver are reused. Therefore, you do not need to edit the generated objects manually. 2. You do not reconfigure the process integration scenarios, but execute the demo examples using the configuration settings made before the upgrade. In this case, you must be aware that the process integration scenario information displayed in the configuration scenario in part no longer corresponds with the SAP NetWeaver release (example: release names of the application components). In both cases, check the communication channels with adapter type IDoc. The SAP Release attribute must be 731 (not 700, 640, 710 or 711). Correct 14 March 2012

15 this, if necessary, and activate the communication channel again (see Editing the Communication Channels with Adapter Type IDoc). Configuring the New Process Integration Scenarios There are new scenarios available for SAP NetWeaver CheckFlightSeatAvailability - Webservice -to-webservice (New in SAP NetWeaver 7.30) SingleFlightBooking - Proxy-to-IDoc variant using Java IDoc adapter (New in SAP NetWeaver 7.30) MultipleFlightBooking Proxy-to-IDoc variant using Java IDoc adapter (New in SAP NetWeaver 7.30) To get them running, you have to configure the scenarios as described in chapters 7.3, 6.3 and General Configuration Steps 4.1 Providing the Necessary Users and Authorizations Authorizations for Configuration Steps in the SAP System To log on to the SAP system to configure the demo examples, you have to create a user XIDEMO with the following roles in the client (001) used for the client copy: SAP_XI_ADMINISTRATOR SAP_XI_CONFIGURATOR SAP_XI_MONITOR To run the demo examples after initial configuration, you may create a user XIDEMO_EXE with the following roles in the client (001) used for the client copy: SAP_XI_DEMOAPP_EXECUTE SAP_XI_CONFIGURATOR SAP_XI_MONITOR These roles are sufficient to regenerate the flight data, check and change the Directory configuration, call the demo example application and start the scenarios and to monitor the message exchange. A user with these roles may be used to test SAP NetWeaver PI after SP implementation or system change Authorizations for Configuring the IDoc Variant To configure the SingleFlightBooking (Proxy-to-IDoc communication or alternative Proxy-to- IDoc AAE ) and MultipleFlightBooking (Proxy-to-Proxy/IDoc communication or alternative Proy-to-Proxy/IDoc AAE) variant, you must make specific ALE settings in the SAP system (see 6.2.1, 0 and 6.5). To call the transactions necessary to do this, you must add the following role to the user XIDEMO in the Client 107: SAP_BC_SRV_EDI_ADMIN 2012

16 Make sure the profile is generated correctly, check this in transaction PFCG Authorizations for Configuring the Web Service Variants To configure the Proxy-to-WS and WS-to-WS communication variants, you must make specific WS settings in the SAP system (see 7.1, and 7.4.1). To call the transactions necessary to do this, you must add the following roles to the user XIDEMO in the Client 107: SAP_BC_WEBSERVICE_ADMIN SAP_BC_WEBSERVICE_CONFIGURATOR Authorizations for Configuring the Message Exchange in the IDoc and RFC Variant To configure the Flight Availability Check (Proxy-to-RFC Communication) variant and the IDoc variants for the single and multiple flight booking, you require a system user that is assigned the role SAP_XI_DEMOAPP_APPL in client 107 (see 4.5.4). Create the user XIDEMO_APPL with the role SAP_XI_DEMOAPP_APPL in client Authorizations for Configuring the message exchange in the WS Variant To configure the Proxy-to-WS and WS-to-WS Communication variants you require a system user that is assigned the roles SAP_XI_APPL_SERV_USER and SAP_BC_WEBSERVICE_SERVICE_USER. Please create the user XIDEMO_WS with the roles SAP_XI_APPL_SERV_USER and SAP_BC_WEBSERVICE_SERVICE_USER in the Integration Server client 001 and in the United Airline/Singapore Airline client Deactivate the advanced Authorization check in application clients In 7.30 a new advanced authorization check for proxy applications is introduced that will not be used for the demo example proxy applications. To deactivate this check please execute the following steps: 1. Login to the client of the travel agency (client 105). 2. Call transaction SXMB_ADM Integration Engine Configuration Specific Configuration 3. Add the parameter AUTHORITY_ON_MSG_TYPE from category RUNTIME with the value Save the entry. Do the same in airline clients 106 and Setting Up the System Landscape This section contains all the configuration steps for setting up the system landscape System Landscape The figure below shows the system landscape that is used for the configuration of the demo examples: 16 March 2012

17 Airline LH SAP NW 7.31 Airline AA SAP NW 7.31 Airline UA External Partner SAP NW 7.31 Airline SQ External Partner SAP NW 7.31 Integration Server SAP NW 7.31 Travel Agency SAP NW 7.31 System Landscape for the Demo Examples The system landscape consists of one Integration Server and four different application systems (one system for the travel agency, and one system for each of the airlines Lufthansa (LH), American Airlines (AA), United Airlines (UA), and Singapore Airlines (SQ) respectively). The application systems of the travel agency and of the airlines LH and AA are implemented by business systems ( internal systems). In the SAP standard configuration, you set up an additional client for each of the three business systems on the SAP system of the Integration Server (see table below). The airlines UA and SQ play the role of an external partner and therefore the application system of the airlines UA and SQ are represented by a business component (assigned to a communication party). Technically, the application systems of the airlines UA and SQ are also implemented by a separate client of the SAP system of the Integration Server. To keep the effort of setting up the system landscape low, the same client is used for all three airlines AA, UA and SQ. Nevertheless, this technical feature is not visible when you carry out the configuration steps in the Integration Directory. Representation of Systems by Different Clients Use the following clients for the required systems: Role Communication Party Implementing System (Client) Travel agency - <SID> (105) Airline Lufthansa - <SID> (106) Airline American Airlines - <SID> (107) Airline United Airlines XIDemo_UnitedAirlines <SID> (107) Airline Singapore Airlines XIDemo_SingaporeAirlines <SID> (107) Note that you are not permitted to implement and run additional productive applications on the SAP system of the Integration Server. The main reason for this is that connecting a productive application to the Integration Server in this 2012

18 way makes it impossible to upgrade the application or the Integration Server separately. This guideline does not apply to the demo examples. The reasoning behind this exception is as follows: - The demo examples are not a productive application and are only for use in development or test systems. - The demo examples are part of SAP NetWeaver Process Integration and, therefore, do not have their own release cycle. Setting up separate business systems would significantly increase the technical requirements for the demo examples. To keep the examples simple and easy to use, you are therefore permitted to use additional clients on the SAP system of the Integration Server for the demo examples. Supported Communication Variants and Involved Clients The following table lists the clients that are involved in the different process integration scenarios/communication variants (according to the standard configuration described in this document). Clients Involved in the different Communication Variants Process Integration Scenario Communication Variant Clients Involved CheckFlightSeatAvailability Proxy-to-Proxy (see 5.1) 105, 106 Proxy-to-RFC (see 6.1) 105, 107 Proxy-to-Web Service (see 7.2) 105, 107 Web Service-to-Web Service (see 7.3) 105, 107 SingleFlightBooking Proxy-to-Proxy (see 5.2) 105, 106 Proxy-to-IDoc (see 6.2) 105, 107 Alternative: Proxy-to-IDoc AAE variant with Java IDoc adapter (see 6.3) 105, 107 Proxy-to-Web Service (see 7.4) 105, 107 MultipleFlightBooking Proxy-to-Proxy (see 5.3) 105, 106, 107 Proxy-to-Proxy/IDoc (see 6.4) 105, 106, 107 Alternative: Proxy-to-Proxy/IDoc AAE variant with Java IDoc adapter (see 6.5) 105, 106, 107 DistributeBookingOrderInformation Proxy-to-File System (see 8.1) 105 (and file system) The individual variants are largely decoupled from each other. When you configure the different variants of one process integration scenario one after the other, you simply add the communication options. For example, if you have configured the Proxy-to-Proxy and Proxy-to-RFC variants of the CheckFlightSeatAvailability process integration scenario, you can run the flight seat availability check for both airlines Lufthansa (106) and American Airlines (107). However, if you only have configured the Proxy-to-Proxy variant, the flight availability check for airline American Airlines will cause an error. 18 March 2012

19 4.... SAP NetWeaver 7.40 Demo Examples Configuration The client for the Integration Server is set up during installation of SAP NetWeaver Process Integration. In this configuration guide, the client 001 is assigned to the Integration Server. You must set up additional clients for the business systems of the travel agency and the two airlines. These clients are referred to as application clients below. Generation of Different Clients You generate the application clients from the SAP reference client (001) (Integration Server) using client copy. To do this, execute the following steps in the SAP system of the Integration Server: 1. Set up the logical systems (for travel agency and airlines) 2. Assign client and logical system 3. Client Copy The three-figure ID of the SAP system on which the Integration Server is installed is referred to below as <SID> Setting Up the Logical Systems To be able to configure a business system as a sender or receiver of IDocs, you must assign a logical system to it. You must specify (ALE) logical systems for the configuration of the variant SingleFlightBooking (Proxy-to-IDoc Communication). However, you also require the logical systems for the client copy (step 4.2.4). It is not possible to add or change the logical systems later. Therefore, you should execute the following steps even if you are not currently planning to set up the IDoc demo example. Define a logical system for each business system. 1. Choose the transaction Display IMG (transaction code SALE). 2. Choose Basic Settings Logical Systems Define Logical System. Ignore the message: Caution: The table is cross-client. 3. In the Log.System column, specify the logical systems for all three clients. Adhere to the naming convention <SID>CLNT<Client>. 4. In the Name column, enter a name for each logical system. Use a meaningful name. Make the following entries in the Log.System and Name columns: Log.System <SID>CLNT001 <SID>CLNT105 <SID>CLNT106 <SID>CLNT107 Name Integration Server Travel Agency Airline LH Airline AA, UA and SQ 5. Save your entries ( ). 2012

20 4.2.3 Assigning the Logical Systems to Clients Since the business systems in the SAP standard configuration are implemented using different clients, you must assign a logical system to each client In the SAP menu, choose Tools Administration Administration Client Administration Client Maintenance (SCC4). 2. Choose Display Change ( ). Field Ignore the message: Caution: The table is cross-client. 3. Choose New Entries. 4. In the New Entries: Details of Added Entries dialog box, enter the following information for client 105: Entry Client 105 Description (Field to the left of Client field) Logical System Travel Agency <SID>CLNT105 Select the entry in the dropdown list box. Client 5. Save your entries ( ). 6. Choose Back ( ). 7. Add an entry for each of the other clients. In the New Entries: Details of Added Entries dialog box, enter the following information: Description (field to the right of the Client field) Logical System 001 INTEGRATION_SERVER <SID>CLNT Travel Agency <SID>CLNT Airline LH <SID>CLNT Airline AA, UA and SQ <SID>CLNT Client Copy You use the steps below to enter additional attributes for the specified clients and execute the client copy. Execute the following steps separately for each of the clients 105, 106, and Log on in client 105. Use the user SAP* and the password PASS. Make sure the parameter login/no_automatic_user_sapstar is set to 0 to enable the logon of user SAP*. For more information, see SAP Note Deactivating the Automatic SAP* User. 2. In the SAP menu, choose Tools Administration Administration Client Administration Client Copy Local Copy (SCCL). 3. In the Select Profile field, select SAP_UCSV. 20 March 2012

21 4. In the Source Client fields, select the client of the Integration Server as the source client (client 001 in this configuration guide). 5. In the menu bar, choose Client Copy Start Immediately. 6. Once the client copy is complete, execute the client copy for clients 106 and 107 one after the other. Note that the user activities for entering the necessary information take approximately 15 minutes for each client. Once you have completed these activities, you must then allow approximately 30 minutes for the actual client copy (for each client). Take this into account and schedule the later configuration steps accordingly. Note that other users cannot work in the system at the same time Execute the CTC template to configure the clients To correctly configure the created clients for SAP NetWeaver PI and WS usage, a CTC template is available which executes the following configuration steps: 1. Describing the system landscape in the System Landscape Directory 2. Configuring the role of the business systems 3. Registering RFC queues 4. Executing WS configuration To execute the CTC template, you have to use the configuration wizard: 1. Open SAP NetWeaver Administrator (http(s)://server:port/nwa) and choose Configuration Management Scenarios. Call the Configuration Wizard. Log on with user J2EE_ADMIN. 2. Select All Configuration Tasks. 3. Search for the template PI Demo Client. 4. Choose Start. 5. As ABAP Administrator enter user DDIC with the correct password. 6. As J2EE Administrator enter user J2EE_ADMIN with the correct password. 7. Set the Master Password you have used during initial NW configuration. 8. Set the client 105 for configuration 9. Choose Next to start the configuration. 10. Execute the template ones again for client 106 and Checking the System Landscape in the System Landscape Directory This section contains all the configuration objects that should be automatically created in the System Landscape Directory. The description of the system landscape consists of: 2012 The technical system landscape

22 The business system landscape You access this data in the System Landscape Directory when executing the further configuration steps in the Integration Directory To call the System Landscape Directory, choose Process Integration Start Integration Builder in the user menu. 2. On the initial screen of SAP NetWeaver Process Integration, choose the hyperlink System Landscape Directory. 3. Log on using your user and password Technical System Landscape Since the involved business systems are each simulated by a different client of the same SAP system, you only need one technical system (the system of the Integration Server). The system of the Integration Server registers itself as a technical system in the System Landscape Directory automatically during installation of SAP NetWeaver Process Integration (according to the Installation Guide). You should check the application clients to this technical system On the initial screen of the System Landscape Directory, choose Technical Systems. The system displays all the technical systems in a table. The technical system of the Integration Server has the following name: <SID> on <Server Name>. If you have called the system <SID>, the name of the server (<Server Name>) is displayed in the corresponding status field in the status bar of the SAP window (for the system <SID>) (for example, PWDF1234). 2. Open the technical system <SID> on <Server Name>. To do this, click the corresponding entry. The system details are displayed. 3. Check if the clients 105, 106 and 107 are already automatically registered. This should be the case after you executed the steps described in the preceding section Business System Description The business system description comprises the following: Client A business system for the Integration Server The business system for the Integration Server is defined in the System Landscape Directory during installation of SAP NetWeaver (see Installation Guide). Business systems for the clients of the travel agency and airlines (application clients) The business systems for the application clients should be automatically created during execution of the CTC template Configure PI Demo Client (as described in section 4.2.5). To check the business systems, on the initial screen of the System Landscape Directory, choose Business Systems. The system displays all the business systems in a table. The business systems of the application systems should have the following names: Business System Name 105 (Travel Agency) <SID>_ March 2012

23 106 (Airline Lufthansa) <SID>_ (Airline American Airlines, United Airlines and Singapore Airlines) <SID>_ Check Configuration of the Local Integration Engine Configuring the Role of the Business Systems Each business system has a local Integration Engine, which controls the message exchange with other systems. The CTC template executed as described in section has configured the application clients as local Integration Engine and defined the connection to the central Integration Server (client 001). Execute the following steps separately for each application client (105, 106, and 107) to check the configuration. 1. In the respective application client, choose Process Integration Administration Integration Engine Administration (SXMB_ADM) in the user menu. 2. Choose Integration Engine Configuration. 3. The role of the business system should be Application System. 4. In the Corresponding Integ. Server field, a HTTP destination to address the central Integration Server should be set. (dest://<http Destination>) Registering Queues To enable asynchronous message processing within the application clients, the qrfc queues have to be registers at the QIN Scheduler in all PROXY clients. The registration is done during CTC template execution (as described in section 4.2.5). 4.5 Defining Communication Components, Communication Channels and Receiver Rules (Integration Directory) To prepare the configuration of the process integration scenarios, you must do the following: For B2B communication only: Define the involved communication parties. Define the involved business systems as communication components (business system component) in the Integration Directory Only then can you address the business systems as senders or receivers of messages. All variants use business system components and therefore these business system components are created now as part of the general configuration steps. Define communication channels for outbound message processing (for all relevant receiver business systems) You must define a communication channel for all communication types that you want to use (Proxy-to-Proxy and Proxy-to-IDoc) and for all potential receiver systems. Define receiver rules for receiver determinations 2012

24 You define receiver rules to use them in receiver determinations in case multiple receivers of a message are addressed (agency several airlines; airline agency or integration process). You define communication components, communication channels and receiver rules in the Integration Directory. Therefore, to execute the activities described below, call the Integration Builder (Integration Directory). 1. To call the Integration Builder (Integration Directory), choose Process Integration Start Integration Builder in the user menu. 2. On the initial screen, choose the hyperlink Integration Builder (under Integration Directory). 3. Log on using your user and password. The system opens the Integration Builder Creating Communication Parties for B2B Communication In the SAP standard configuration of the following variants, the senders and receivers of messages are addressed as communication components of communication parties. Because of this, you have to create the following objects: One communication party for the travel agency Two communication parties for the airlines United Airlines and Singapore Airlines To do so, perform the following steps in the Integration Builder. 1. In the navigation area, choose the Objects tab page. 2. Position the cursor on the node Party. 3. In the context menu choose New. 4. In the dialog Create Object enter XIDemo_Agency in the Name field. 5. Enter XI demo agency in the Description field. 6. Choose Create. The object editor for the party is opened. 7. In the object editor choose Save ( ). 8. Create two other parties with the names XIDemo_UnitedAirlines (description: XI demo United Airlines) and XIDemo_SingaporeAirlines (description: XI demo Singapore Airlines). 9. Activate the change list that contains the parties (tab Change Lists) Defining Communication Components You use the steps below to define a communication component (business system component) in the Integration Directory for each business system. You can also create communication channels for the involved business systems automatically In the Integration Builder navigation area, on the Objects tab page, position the cursor on the Communication component node. 2. To call the wizard for assigning business systems, choose Assign Business System in the context menu. 3. Choose Continue. 24 March 2012

25 4. On the next screen, choose Continue. 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>_105 <SID>_106 <SID>_ Make sure that the Create Communication Channels Automatically checkbox is selected. In this case, the receiver communication channels for the selected business systems are created automatically. 7. Choose Finish. The system displays the communication components in the Integration Builder navigation area, on the Objects tab page, under Communication Component Business System. The communication channels that are generated automatically are assigned to the selected communication components and displayed in the Integration Builder navigation area under Communication Channel. Communication channels with adapter type XI have the name *I<SID>_<Client>IGeneratedReceiverChannel_XI. Communication channels with adapter type IDoc have the name *I<SID>_<Client>IGeneratedReceiverChannel_IDoc. Communication channels with adapter type RFC have the name *I<SID>_<Client>IGeneratedReceiverChannel_RFC. You need receiver communication channels with adapter type XI, IDoc, and RFC for the standard configuration. To be able to use the communication channels, you have to edit them manually. For the Web Services Variants you have to create business components and assign them to the created parties. 1. In the Integration Builder navigation area, on the Objects tab page, position the cursor on the Business Component node. 2. In the Context menu choose New. 3. As Party select XIDemo_Agency and as Communication Component set CheckFlightSeatAvailability. 4. Choose Create. 5. In the Edit Communication Component Screen press Save. 6. Create the business component SendSingleFlightBooking to Party XIDemo_Agency, business component ProvideFlightSeatAvailability to party XIDemo_UnitedAirlines, business component ProvideFlightSeatAvailability to party XIDemo_SingaporeAirlines and Business Component BookSingleFlightAndConfirm to Party XIDemo_UnitedAirlines following the same procedure Defining the Integration Process Component The executable integration process MultipleFlightBookingCoordination (with a separate application component) is integrated in the process integration scenario MultipleFlightBooking. To be able to address the integration process as a sender or receiver of messages, you must create a communication component for the integration process in the Integration Directory In the Integration Builder, select the Objects tab page. 2012

26 2. Expand the Communication Component node. 3. Position the cursor on the Integration Process node and choose New in the context menu. The system calls the wizard for creating an integration process component. 4. Choose Continue. 5. The next screen displays all integration processes from the Enterprise Services Repository in a list. Select the integration process MultipleFlightBookingCoordination (software component version SAP Basis 7.40, namespace 6. Choose Continue. 7. On the next screen, enter the following in the Name field: MultipleFlightBookingCoordinator 8. Choose Finish Editing the Communication Channels Generating the communication channels automatically ( 4.5.2) creates receiver communication channels with adapter type XI, IDoc, RFC, WS and HTTP. You require the following communication channels for the standard configuration: Each of the three application systems of the travel agency, airline LH and airline AA is used at least once as a proxy receiver. Therefore, you must define a receiver communication channel with adapter type XI for each business system component (<SID>_105, <SID>_106, and <SID>_107). In the process integration scenario Flight Availability Check (Proxy-to-RFC Communication), the application system of the airline American Airlines is used as an RFC receiver. Therefore, you must define a receiver communication channel with adapter type RFC for the business system component <SID>_107. In the process integration scenarios Single Flight Booking (Proxy-to-IDoc Communication) and Multiple Flight Booking (Proxy-to-Proxy/IDoc Communication), the application system of the airline American Airlines is used as an IDoc receiver. Therefore, you must define a receiver communication channel with adapter type IDoc for the business system component <SID>_107. To ensure an error-free configuration, you must edit these (automatically created) communication channels manually. For the standard configuration of the variants CheckFlightSeatAvailability (Proxy-to-Web Service), SingleFlightBooking (Proxy-to-Web Service), SingleFlightBooking (Web Service-to-Web Service) and DistributeBookingOrderInformation (Proxy-to-File System) you require channels with adapter type WS and File, respectively. These communication channels are created on the basis of communication channel templates (see 7.2.2, and 8.1.2, respectively). Editing the Communication Channels with Adapter Type XI To ensure that the outbound message processing (in the direction of a proxy receiver) can be executed without errors, you must edit the automatically generated communication channels GeneratedReceiverChannel_XI manually as follows: 26 March 2012

27 You must execute the following steps for all three communication channels GeneratedReceiverChannel_XI for the communication components <SID>_105, <SID>_106, and <SID>_107. Execute the following steps separately for each communication channel. 1. In the Integration Builder navigation area, under Communication Channel, position the cursor on the communication channel. In the context menu, choose Open ( ). 2. The system opens the communication channel in the Integration Builder work area. 3. Switch to change mode. To do this, choose Switch between display and edit mode ( ). 4. Enter the following values for the communication channel attributes. The table contains the correct entries for all fields in the communication channel. Note that some fields will be completed by the system when communication channels are created automatically. The Specify Manually column indicates which fields remain to be completed. Entries for Communication Channels Specify Manually Attribute Transport Protocol Message Protocol Addressing Type Target Host Value HTTP 1.0 XI 3.0 URL Address Name of the server of the target host (for example, pwdf0005) X Service Number Number of the HTTP port Path Authentication Data Specify Attribute Manually x Authentication Type x User Name x User Password x Logon Language x Client To find out the number of the HTTP port (service number), see the ICM Monitor of the relevant Integration Server (call transaction SMICM and then Goto Services). Select the Service Name/Port for the Protocol HTTP. /sap/xi/engine?type=entry Value Use Logon Data for SAP System Create a copy of PIAPPLUSER in all three clients 105, 106 and 107 and use this user here Use the password set for the user EN 105 (for channel in communication component <SID>_105) 106 (for channel in communication component <SID>_106) 2012

28 107 (for channel in communication component <SID>_107) 5. Save the communication channel ( ). Sender agreements are not necessary for adapter type XI and XI 3.0 protocol. Therefore, no sender communication channels are necessary. Editing the Communication Channels with Adapter Type IDoc Prerequisite: Defining R/3 Connection to the Application System of the Airline American Airlines You must perform the following steps in the SAP system of the Integration Server (001). Only then can the settings in the communication channels with adapter type IDoc be used. 1. In the integration server client, call the transaction Display and Maintain RFC Destinations. To do this, choose Process Integration Environment RFC Destinations (Display and Maintenance) (SM59) in the user menu. 2. Select the ABAP connections node. 3. In the pushbutton bar, choose Create. 4. In the RFC destination field, enter the following name for the RFC destination for the Integration Server: <SID>_ In the Connection type field, in the dropdown list box, select 3 - Connection to R/3 System. 6. In the Description frame, in the Description 1 field, enter the following: Connection to American Airlines. 7. Choose Enter ( ). 8. On the Technical settings tab page, enter the following information: In the Target host field, enter localhost. In the System Number field, specify the system number of the SAP system (for example, 73). To find the system number, choose Properties in the logon dialog box (SAP Logon). The system number is displayed in the System Number field. 9. On the Logon/Security tab page, enter the logon data for the target system. In the Logon frame, enter the following information: In the Client field, specify the client of the application system for American Airlines: 107. In the User field, specify the user XIDEMO_APPL you created in Only then can the system (client) of the airline American Airlines receive and process IDocs. In the Password field, enter a password for this user. 10. Save the RFC destination (choose the Save pushbutton). 11. To test the RFC destination, choose Test connection in the pushbutton bar. 28 March 2012

29 12. Choose Back ( ). Editing the Communication Channels To configure the variant SingleFlightBooking (Proxy-to IDoc Communication) and MultipleFlightBooking (Proxy-to-Proxy/IDoc Communication), you must edit the receiver communication channel GeneratedReceiverChannel_IDoc (with adapter type IDoc) in communication component <SID>_107. Perform the following steps in the Integration Directory. If you only want to configure the variants for Proxy-to-Proxy communication, you can omit the following steps. 1. In the Integration Builder navigation area, under Communication Channel, position the cursor on the communication channel *I<SID>_107IGeneratedReceiverChannel_IDoc. In the context menu, choose Open ( ). 2. The system opens the communication channel in the Integration Builder work area. 3. Switch to change mode ( ). 4. In the RFC Destination field, specify the RFC destination for client 107: <SID>_ In the SAP Release field, enter Deselect Apply Control Record Values from Payload. 7. Save the communication channel ( ). Sender agreements are not necessary for adapter type IDoc and XI 3.0 protocol. Therefore, no sender communication channels are necessary. The communication channel must be defined as follows: Entries for the Communication Channel Specify Manually x x Attribute Transport Protocol Message Protocol Adapter Engine RFC Destination Segment Version Value IDoc IDoc Integration Server <SID>_107 x Interface Version Port SAP Release SAP Release 4.0 or higher SAP<SID> 731 Editing the Communication Channel with Adapter Type RFC To configure the Flight Availability Check (Proxy-to-RFC-Communication) variant, you must configure the receiver RFC adapter. For this purpose, edit the receiver communication channel GeneratedReceiverChannel_RFC (with adapter type RFC) in the <SID>_107 communication component, as described below. 2012

30 For more information about configuring the receiver RFC adapter, see Configuring the Receiver RFC Adapter If you only want to configure the variants for Proxy-to-Proxy communication, you can omit the following steps In the Integration Builder navigation area, under Communication Channel, position the cursor on the communication channel *I<SID>_107IGeneratedReceiverChannel_RFC. In the context menu, choose Open ( ). 2. The system opens the communication channel in the Integration Builder work area. 3. Switch to change mode ( ). 4. Enter the following values for the communication channel attributes: Entries for the Communication Channel Specify Manually Attribute Transport Protocol Message Protocol Adapter Engine Adapter Status RFC Client Parameter Specify Manually Attribute Load balancing Application server System number Authentication mode Value RFC RFC (RFC-XML) Central Adapter Engine Active Value Checkbox deactivated <Host name of the SAP system> <System number> Use logon data to SAP system x Logon user Enter the user XIDEMO_APPL you created in x x x Logon password Logon language Logon client The authorizations assigned to this role are required to read the RFC metadata in the receiver system. <Password for the user specified> EN 107 Maximum connections 1 Advanced mode Checkbox deactivated RFC Metadata Repository The Use Alternative RFC Metadata Repository checkbox must be deactivated. Activating Communication Component and Communication Channels You must activate the communication components and communication channels. 30 March 2012

31 When the communication channels are generated automatically, communication channels with adapter type HTTP and WS are also generated for the selected business systems. These communication channels are not required for the configuration of the demo examples, but they are saved in the user s standard change list. Since these communication channels are not fully specified, you cannot activate them along with the other channels (adapter type XI, IDoc, and RFC). The same applies to the communication channels GeneratedReceiverChannel_IDoc and GeneratedReceiverChannel_RFC for the communication components <SID>_105 and <SID>_106. These are also not required for the further configuration steps. Therefore, you must delete the communication channels that are not required before activating In the Integration Builder navigation area, select the Change Lists tab page. 2. If you have created more than one change list, expand the change lists and check which one the communication channels are assigned to. 3. Delete all communication channels that are not required separately. To delete an object in a change list, select Delete ( the object. ) in the context menu for 4. Position the cursor in the change lists with the communication channels and choose Activate in the context menu Defining Receiver Rules Create receiver rules for the airlines used in the different scenarios. The first rule only contains the airline LH used in the scenarios CheckFlightSeatAvailability and SingleFlightBooking scenarios (proxy-to-proxy variants). Execute the following steps: 1. In the Integration Builder menu choose Object New ( ). 2. Under Configuration Objects select Receiver Rule. 3. Make the following entries: Name: XIDemoAirlineID_LH Description: Receiver Rule for AirlineID LH 4. Choose Create. 5. Select the input help ( ) in the column Condition. The condition editor is displayed. 6. In the condition editor, select the input help ( ) in the column Left Operand. 7. Select the context object AirlineID. 8. Choose Apply. 9. Choose OK. 10. In the condition editor for the Right Operand enter LH. 2012

32 11. Choose OK. 12. Select the communication component <SID>_106 and save the receiver rule. To be able to run the scenarios in all possible variants, it is necessary to create another receiver rule for the two airlines AA and LH and one for all three airlines. To do this, perform the following steps: 1. In the Integration Builder navigation area, on the Objects tab, position the cursor on the receiver rule XIDemoAirlineID_LH just created. 2. Choose Copy Object in the context menu. 3. Enter the name XIDemoAirlineID_LH_AA. 4. Choose Copy. 5. Select change mode. 6. Change the description to Receiver Rule for AirlineID LH and AA. 7. Add the condition AirlineID = AA for communication component <SID>_107 as described above and save the receiver rule. 8. Copy the receiver rule XIDemoAirlineID_LH_AA to a new rule with the name XIDemoAirlineID_all and description Receiver Rule for all AirlineIDs using the same procedure. Add the condition AirlineID = UA for communication party XIDemo_UnitedAirlines with communication component ProvideFlightSeatAvailability and save the receiver rule. 9. Copy the receiver rule XIDemoAirlineID_LH_AA to a new rule with the name XIDemoAirlineID_all_Book and description Receiver Rule for all AirlineIDs in Booking Scenario using the same procedure. Add the condition AirlineID = UA for communication party XIDemo_UnitedAirlines with communication component BookSingleFlightAndConfirm and save the receiver rule. Create another rule for the OrderTypes used in the demo example scenarios. Execute the steps described above to create a receiver rule with the following settings: Name: XIDemoOrderType Description: Receiver Rule for OrderType Define condition OrderType = Multiple for communication component MultipleFlightBookingCoordinator. Define condition OrderType = Single for communication component <SID>_105. Activate the created receiver rules. 4.6 Further Steps for Configuring the Demo Examples Activating the BSP Application A BSP (Business Server Pages) application is available to enable you to execute the demo examples. You use this application to make the necessary entries and display the results. To be able to execute the demo examples after configuration, you must activate the BSP application. For more information about the necessary ICF (Internet Communication Framework) services, see SAP Note Log on to the SAP system in the Integration Server client (001) 32 March 2012

33 2. Call the transaction Maintain Service. To do this, choose Tools Administration Administration Network HTTP Service Hierarchy Maintenance (SICF) in the SAP menu. 3. In the Virt.Hosts / Services column, expand the following nodes: default host sap bc bsp sap. Select the entry sxidemo_agcy_ui. Entry in gray font: Service is not activated. Entry in black font: Service is activated. A service can only be activated if all nodes above it are activated. 4. In the context menu, choose Activate Service. 5. To open the service, double-click it. 6. Switch to change mode. To do this, choose Change ( ). 7. In the Logon Data frame, make the following entries: In the Client field, specify the client of the travel agency: 105. The user and password entries are not mandatory. To protect your system you should leave these fields empty. In this case a logon popup will ask for user and password during execution of the BSP application. 8. Choose Input ( ). The system automatically creates a transport request for your change. A dialog box appears, in which you confirm this transport request Generating the Flight Data To be able to access flight data during execution of the demo examples, you first have to generate it. A data generation program is available to enable you to generate data for flights with different airlines on different days. The data for a flight is made up of static data (for example, airline, flight date, flight number) and dynamic data (seat availability in the three flight classes). The dynamic data is dependent on the business system (client). Therefore, you must generate the data separately in all three clients. The data generation process generates flight data for flights in a time interval from 40 weeks before until 40 weeks after the date of data generation. It also generates flights for the first day of every month for the year following the date of data generation for each airline and flight number. This simplifies the execution of the demo examples: When you select the first day of the month as the flight date, it is guaranteed that a flight is available for each airline and connection number. Generate the data in all three clients on the same day. This guarantees that the (static) flight data (that is, the set of flights offered) is identical in all three clients. The data generation does not generate any booking data. To represent the distribution of the data management tasks between the travel agency and the airlines as realistically as possible, the data generation program generates the following results: 2012

34 6.... SAP NetWeaver 7.40 Demo Examples Configuration If data generation is carried out in the client of the travel agency, the maximum number of seats is set to zero for all flights. If data generation is carried out in an airline client, the maximum number of seats is set greater than zero for airline(s) represented by this client and set to zero for the other airline(s). This guarantees that you can only ever book the appropriate flights (for the respective client). Execute the following steps separately in each application client (105, 106, and 107). 1. Log on to the SAP system in the respective client. 2. In the user menu, choose Process Integration Demo Examples Settings: Generate Flight Data (SXIDEMO3). 3. In the Specify the airlines for this system frame, specify the role of the respective application client. Specifying Airlines for Individual Application Clients Client you are Logged on Activities 105 Select the No radio button. 106 Select the Yes radio button and specify the airline ID LH in the Airline field. You can leave the to field empty. 107 Select the Yes radio button and choose Multiple Selection ( ). In the screen Multiple Selection for Airline (tab Select Single values) set the values AA, UA and SQ and choose Multiple Selection. On screen Multiple Selection for Airline choose Copy ( ). 4. In the Select data range frame, specify the range of the generated data set. Select the Optimized Flight Data radio button. We strongly recommend that you select the Optimized Flight Data radio button. In this case, a manageable number of flight connections is generated (for LH 0400, LH 0401, AA 0017, AA 0064, UA 0941, UA 3504, SQ 988, SQ 997). Only select the Complete Flight Data option if you want to use the generated flight data for other demo examples that require access to a more extensive data set. In this case, flight data is generated for other airlines that do not belong to the system landscape of the demo examples. However, note that in this case you must adjust the configuration of the demo examples to the more extensive data set (for example, by adjusting the routing conditions). The configuration steps below are based on the data set generated using the Optimized Flight Data option. 5. Choose Execute ( ). 34 March 2012

35 5 Configuring Process Integration Scenarios for Proxy-to-Proxy Communication 5.1 Checking Flight Seat Availability (Proxy-to-Proxy Communication) This section describes how to configure the Checking Flight Seat Availability process integration scenario in the Proxy-to-Proxy Communication variant. In this variant, you configure both business systems of travel agency (client 105) and airline Lufthansa (LH) (client 106) as receiver of proxies. This demo example is implemented as the process integration scenario CheckFlightSeatAvailability. The process integration scenario is located in the Enterprise Services Repository, in the software component SAP BASIS, software component version SAP BASIS 7.40, in the namespace Business Description (Brief) A travel agency uses the synchronous process integration scenario CheckFlightSeatAvailability to check the seat availability of a flight with an airline. The maximum number of seats and the number of available seats in the three flight classes (economy, business, and first class) are specified for the flight. You use this process integration scenario to check the current seat availability before booking Configuration in Integration Directory Start Integration Builder (Integration Directory) You perform the following configuration steps in the Integration Directory. Therefore, to execute the activities described below, call the Integration Builder. 1. In the user menu (in the SAP system of the Integration Server), choose Process Integration Start Integration Builder. 2. On the initial screen, choose the hyperlink Integration Builder (under Integration Directory). 3. Log on using your user and password. The system opens the Integration Builder. 2012

36 The central tool is the model configurator. For more information about the model configurator, see Configuring Process Integration Scenarios. Selecting the Process Integration Scenario (Component View) You use the steps below to do the following: Select the process integration scenario and the component view from the Enterprise Services Repository Create the scenario in the Integration Directory to group all the relevant 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 (checkbox under Type of ES Repository Model). 3. Choose the input help (for the Name field) ( ) and select Process Integration scenario in the dropdown listbox. 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 CheckFlightSeatAvailability (software component version SAP Basis 7.40, namespace and choose Apply. 5. In the wizard, choose Continue. 6. On the next screen, you edit the predefined name of the scenario. Change the name to XIDemo_CheckFlightSeatAvailability. 7. Choose Finish. The system creates the configuration scenario. 8. Choose Close. The system calls the model configurator. The process integration scenario CheckFlightSeatAvailability is displayed in a graphical editor. 9. Select the push button Select Component View ( ). A new screen appears where the available Component Views for the process integration scenario are displayed. 10. In the preview area, select the component view ABAP_Proxy_2_ABAP_Proxy and choose Apply. Assigning Communication Components You use the steps below to assign communication components to the application components of the process integration scenario. 1. In the graphical editor, click on the lane representing the Agency application component. This calls the Assign Business System Communication Components dialog box for the Agency application component (below the graphical representation of the process integration scenario). 36 March 2012

37 2. In the tab Business System Communication Components for A2A, click in the input field in the Communication Component column and call the input help ( ). The system displays all communication components of type Business System. 3. Select the communication component <SID>_105 and choose Apply. 4. In the Assign Business System Communication Components dialog box, click the navigation arrow ( ) to switch to the application component Airline. 5. In the tab Business System Communication Components for A2A, click in the input field in the Communication Component column and choose the input help ( the pushbutton bar. 6. On the Choose Communication Component screen, select the communication component <SID>_ Choose Apply. Configuring the Connection You use the steps below to configure the connection of the process integration scenario. 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 Check Flight Seat Availability and Determine Flight Seat Availability (below the graphical representation of the process integration scenario). 3. In the Connections from Component Assignment tab, check that the sender/receiver relation is activated (select checkbox). 4. To specify a receiver communication channel for the relation between sender communication component <SID>_105 and receiver communication component <SID>_106, click in the input field in the Communication Channel column. 5. Call the input help ( ). ) in If there are not yet any configuration objects in the system, the system displays all communication channels that are assigned to the communication component <SID>_106. If receiver agreements already exist for the inbound interface of the connection, the system only displays the communication channel assigned to this receiver agreement. 6. Select the communication channel GeneratedReceiverChannel_XI and choose Apply. Generating the Configuration Objects You use the steps below to generate the relevant configuration objects. 1. Choose the push button Create Configuration Objects ( ). 2. Under General, select the Generation radio button. 3. Under Scope of Generation, select the checkboxes Receiver Determination, Interface Determination, and Sender/Receiver Agreement. 4. Under Change List for Generated Objects, select the Create New radio button. This means that the changes resulting from the generation are saved in a separate change list with the name of the scenario. 2012

38 5. Choose Start. The scenario itself is saved in the standard change list. The objects are generated. The generation log is called. The generation log contains an overview of all information relating to the generation and indicates if any manual editing is necessary for the generated objects. Manual Editing You use the steps below to execute the necessary manual editing for the generated configuration objects. To define exactly how a message is to be forwarded from the travel agency to the airline, you must add a routing condition to the receiver determination. 1. In the generation log, expand the Connections area. 2. Navigate to the receiver determination <SID>_105 FlightSeatAvailabilityQuery_Out. The yellow traffic light symbol signifies that manual editing may be necessary for this object. 3. To open the receiver determination, click the key <SID>_105 FlightSeatAvailabilityQuery_Out. The system opens the receiver determination. 4. To switch to change mode, choose the function Switch Between Display and Edit Modes ( ) in the pushbutton bar of the Display Receiver Determination editor. In the Configured Receivers area, insert the condition for forwarding messages to the receiver communication component. 5. Delete the line containing the service <SID>_106 and insert a new line using the Insert Receiver Rule entry. 6. In the new line, click in the input field in the Rule column and call the input help ( ). 7. Select the Rule XIDemoAirlineID_LH. 8. Save the receiver determination ( ). Final Steps Execute the following steps: 1. Close the generation log. You can save the generation log as a file. 2. Close the model configurator. The system displays the message Do you want to keep the changes? Confirm with Apply. 3. Save the scenario XIDemo_CheckFlightSeatAvailability. 4. Activate the scenario XIDemo_CheckFlightSeatAvailability and all objects that it uses. 38 March 2012

39 Note that there are two change lists: - Standard change list (containing the scenario XIDemo_CheckFlightSeatAvailability) - Change list XIDemo_CheckFlightSeatAvailability (containing all objects of the scenario) You must activate both change lists Executing and Testing There is an application in the SAP system of the Integration Server (client 105) that you can use to test the configuration of the process integration scenario. To start the application, login to the SAP system (client 105). In the user menu, choose Process Integration Demo Examples Travel Agency: Execute Demo Examples (SXIDEMO). On the start page of the application, choose the scenario Check Flight Seat Availability. You can select a restricted number of flights (see also 4.6.2) and the flight date. SAP recommends that you use the default setting (the first day of next month). To run the process integration scenario, choose Check Availability. The system displays a dialog containing the results of the availability check (see table). Possible Input and Expected Results Input (Airline and Flight ID) Lufthansa 0400 Lufthansa 0401 Lufthansa 9999 N.N Expected Result System displays the maximum number of seats and the number of available seats in the three flight classes (economy, business, and first class). You can compare this result with the flight seat availability data in the SAP system (client) of the airline. System displays XI application error: Flight does not exist System displays XI system error: No receiver could be determined Synchronous XML messages are not stored permanently in the database. Because of this, if the application was executed without errors, the corresponding XML messages are not displayed in the Monitoring. This is due to the fact that Logging for Synchronous Messages is deactivated by default. To display synchronous XML messages in monitoring, activate Logging. For more information, see Logging and Tracing. See also chapter 9 under XML Messages Not Found on the Integration Server. You can also choose flights for the airlines American Airlines (AA) and United Airlines (UA). Nevertheless, a flight seat availability check is only possible, if you have configured the corresponding variants of the process integration scenario (receiver AA is configured in the Proxy-to-RFC Communication variant (see 6.1), receiver UA is configured in the Proxy-to-Web Service Communication variant (see 7.2), receiver SQ is configured in the Web Service-to-Web Service Communication variant (see 7.3). If these variants are not configured, a system error (No receiver could be determined) is generated when you choose one of these flights. 2012

40 For more information about how to start the application, how to check that the process integration scenario has been executed correctly and how to monitor the XI message exchange, see Executing the Process Integration Scenario and the chapter Monitoring at the end of the document. 5.2 Booking a Single Flight (Proxy-to-Proxy Communication) This section describes how to configure the Booking a Single Flight process integration scenario in the Proxy-to-Proxy Communication variant. In this variant, you configure both business systems of travel agency (client 105) and airline Lufthansa (LH) (client 106) as receiver of proxies. This demo example is implemented as the process integration scenario SingleFlightBooking. The process integration scenario is located in the Enterprise Services Repository, in the software component SAP BASIS, software component version SAP BASIS 7.40, in the namespace Business Description (Brief) A travel agency uses the asynchronous SingleFlightBooking process integration scenario to book a flight with an airline. The booking refers to exactly one flight for exactly one passenger. The airline sends a response stating whether the booking was successful or not. 40 March 2012

41 5.2.2 Configuration in Integration Directory Settings in the Model Configurator To accomplish the following configuration steps in the Integration Directory, proceed as described in detail in section To configure the process integration scenario SingleFlightBooking in the Proxy-to-Proxy Communication variant, use the settings as listed in the table below. Settings for the Process Integration Scenario SingleFlightBooking (Proxy-to-Proxy Communication) Configuration Step Selecting the Process Integration Scenario (Component View) and Creating the Scenario Assigning Communication Components Configuring the Connections Generating the Configuration Objects Manual Editing Settings In the model configurator select the process integration scenario SingleFlightBooking (software component version SAP Basis 7.40, namespace Change the predefined name of the scenario to XIDemo_SingleFlightBooking. Select the component view ABAP_Proxy_2_ABAP_Proxy. For the Agency application component assign the communication component <SID>_105. For the Airline application component assign the communication component <SID>_106. Note that two connections have to be configured in this scenario. Always select the receiver communication channel GeneratedReceiverChannel_XI (assigned to the respective receiver communication component). Same as described under To define exactly how a message is to be forwarded from the travel agency to the airline, you must add a routing condition to the receiver determination <SID>_105 BookingOrderRequest_Out. You can navigate to this receiver determination in the generation log of the model configurator (by selecting the connection between the actions Send Single Flight Booking Order and Book Single Flight And Confirm). Delete the line containing the service <SID>_106 and insert a new line using the Insert Receiver Rule entry. In the new line, select the receiver rule XIDemoAirlineID_LH. In case you have already configured the process integration scenario MultipleFlightBooking in the Proxyto-Proxy variant before, you have to define whether the message from the airline systems is forwarded to the integration process (process integration scenario MultipleFlightBooking) or to the travel agency system (process integration scenario SingleFlightBooking). To do this, you must add conditions to the receiver determination <SID>_106 FlightBookingOrderConfirmation_Out as described in under Manual Editing). 2012

42 Final Steps Save the scenario XIDemo_SingleFlightBooking. Activate the scenario XIDemo_SingleFlightBooking and all objects that it uses (follow the procedure as described in section 5.1.2) Executing and Testing There is an application in the SAP system of the Integration Server (client 105) that you can use to test the configuration of the process integration scenario. To start the application, login to the SAP system (client 105). In the user menu, choose Process Integration Demo Examples Travel Agency: Execute Demo Examples. On the start page of the application, choose the scenario Book Single Flight. You can select a restricted number of flights (see also 4.6.2), the flight date, the flight class and you can select the name and date of birth of the passenger. SAP recommends that you use the default setting for the flight date (the first day of next month). To run the process integration scenario, choose Create Booking Order. The system displays a dialog containing the order status. You can check if the booking was successful by choosing Refresh. Note that you can check the flight seat availability of both airlines before and after you have executed the process integration scenario. Possible Input and Expected Results Input (Airline and Flight ID) Lufthansa 0400 Lufthansa 0401 Lufthansa 9999 N.N Expected Result If seats are available, flight booking is successful (green traffic light icon is displayed in Order Status field). If no seats are available or you chose a date on which the flight is not scheduled, flight booking is not successful (red traffic light icon is displayed in Order Status field). Flight booking is not successful because flight does not exist (red traffic light icon is displayed in Order Status field). No answer arrives as there is no such airline configured. Status of booking order stays on Awaiting confirmation (amber traffic light icon is displayed in Order Status field). In the PI Monitoring you can see the error No receiver could be determined in the PI Message. Make a note of the order number in case you want to check the order status again later (choose Query Booking Status on the start page of the application). For more information about how to start the application, how to check that the process integration scenario has been executed correctly and how to monitor the XI message exchange, see Executing the Process Integration Scenario and the chapter Monitoring at the end of the document. 5.3 Booking Connecting Flights (Proxy-to-Proxy Communication) This section describes how to configure the Booking Connecting Flights process integration scenario in the Proxy-to-Proxy Communication variant. In this variant, you configure the 42 March 2012

43 business systems of the travel agency (client 105) and both airlines Lufthansa (LH) (client 106) and American Airlines (AA) (client 107) as receiver of proxies. This demo example is implemented as the process integration scenario MultipleFlightBooking. The process integration scenario is located in the Enterprise Services Repository, in the software component SAP BASIS, software component version SAP BASIS 7.40, in the namespace Business Description (Brief) A travel agency uses the asynchronous process integration scenario MultipleFlightBooking to book a flight and a connecting flight (for a passenger). The travel agency requests flight bookings for both legs of the trip (flight and connecting flight) with the respective airlines. The two legs of the trip can be with different airlines. The booking of a flight and a connecting flight is only successful if both individual flights are booked successfully. Therefore, it is necessary to coordinate the results of both flight bookings. This is done by an application between the travel agency and airline applications. Technically speaking, this coordinating application is an executable integration process. 2012

44 5.3.2 Preliminary Steps Activating Workflow Customizing To get the Business Process Engine (BPE) working correctly, the initial configuration has to be executed successfully. Check and if necessary execute the configuration. Start transaction SWF_XI_CUSTOMIZING in the Integration Server client. Check and if necessary execute all workflow customizing steps (Definition and Runtime Environment) Configuration in Integration Directory Settings in the Model Configurator To accomplish the following configuration steps in the Integration Directory, proceed as described in detail in section To configure the process integration scenario MultipleFlightBooking in the Proxy-to-Proxy Communication variant, use the settings as listed in the table below. 44 March 2012

45 Settings for the Process Integration Scenario MultipleFlightBooking (Proxy-to-Proxy Communication) Configuration Step Selecting the Process Integration Scenario (Component View) and Creating the Scenario Assigning Communication Components Settings In the model configurator select the process integration scenario MultipleFlightBooking (software component version SAP Basis 7.40, namespace Change the predefined name of the scenario to XIDemo_MultipleFlightBooking. Select the component view ABAP_Proxy_2_ABAP_Proxy. For the Agency application component assign the communication component <SID>_105. For the Coordinator application component assign the communication component (integration process component) MultipleFlightBookingCoordinator. Configuring the Connection Generating the Configuration Objects To select the communication component, choose the input help on the Communication Component Assignment tab page. The input help icon ( ) is to the right of the Party and Communication Component input fields. For the Airline application component assign the communication components <SID>_106 and <SID>_107. For each sender/receiver relation with a business system as receiver, select the receiver communication channel GeneratedReceiverChannel_XI (assigned to the respective receiver communication component). For each sender/receiver relation with an integration process as receiver, no receiver communication channel is necessary. Same as described under

46 Manual Editing To define exactly how a message is to be forwarded from the executable integration process to the two airlines, you must add routing conditions to the following two receiver determinations. MultipleFlightBookingCoordinator FlightBookingOrderCancelationRequest_Abstract MultipleFlightBookingCoordinator FlightBookingOrderRequest_Abstract Delete the local rule containing the service <SID>_106 and <SID>_107 and insert a new line using the Insert Receiver Rule entry. In the new line, select the receiver rule XIDemoAirlineID_LH_AA. If you have already configured the process integration scenario SingleFlightBooking in the Proxy-to-Proxy variant (see 5.2) before, you have to define whether the message from the airline systems is forwarded to the executable integration process (process integration scenario MultipleFlightBooking) or to the travel agency system (process integration scenario SingleFlightBooking). To do this, you must add conditions to the following receiver determination: <SID>_106 FlightBookingOrderConfirmation_Out Final Steps The airline use the same outbound interface for both variants SingleFlightBooking and MultipleFlightBooking. This differentiation is necessary in routing to enable both scenarios to be used simultaneously. The forwarding of the message depends on whether you are booking a single flight or a flight and a connecting flight. This is defined by the booking type (OrderType). If OrderType=Single, the booking is for a single flight. If OrderType=Multiple, the booking is for a flight and a connecting flight. Select Operation-specific. Delete the local rule containing the service <SID>_105 and MultipleFlightBookingCoordinator and insert a new line using the Insert Receiver Rule entry. In the new line, select the receiver rule XIDemoOrderType. Save the scenario XIDemo_MultipleFlightBooking. Activate the scenario XIDemo_MultipleFlightBooking and all objects that it uses (follow the procedure as described in section Executing and Testing There is an application in the SAP system of the Integration Server (client 105) that you can use to test the configuration of the process integration scenario. To start the application, login to the SAP system (client 105). In the user menu, choose Process Integration Demo Examples Travel Agency: Execute Demo Examples. On the start page of the application, choose the scenario Book Flight and Connecting Flight. Select one of the available flight combinations, the flight date, the flight class and specify the name and date of birth of the passenger. SAP recommends that you use the default setting 46 March 2012

47 for the flight date (the first day of next month). For each flight you can select a restricted number of flights (see also 4.6.2), To run the process integration scenario, choose Create Booking Order. The system displays a dialog containing the order status. You can check if the booking was successful by choosing Refresh. Note that you can check the flight seat availability of both airlines before and after you have executed the process integration scenario. Possible Input and Expected Results Input (Airline and Flight ID) Combination of Lufthansa 0400 and American Airlines 0017 Combination of Lufthansa 0400 and American Airlines 9999 Combination of Lufthansa 9999 and American Airlines 0017 Combination of Lufthansa 9999 and American Airlines 9999 Expected Result If seats are available for both flights, overall flight booking is successful ( green traffic light icon is displayed in Order Status field). Overall flight booking is not successful because one flight (with the number 9999) does not exist (red traffic light icon is displayed in Order Status field). For this flight a seat is booked but later cancelled. Overall flight booking is not successful because both flights do not exist. For both flights there will be no bookings created (red traffic light icon is displayed in Order Status field). Make a note of the order number in case you want to check the order status again later (choose Query Booking Status on the start page of the application). For more information about how to start the application, how to check that the process integration scenario has been executed correctly and how to monitor the XI message exchange, see Executing the Process Integration Scenario and the chapter Monitoring at the end of the document. 6 Configuring Process integration scenarios for Proxy-to-RFC/IDoc Communication 6.1 Checking Flight Seat Availability (Proxy-to-RFC Communication) This section describes how to configure the Checking Flight Seat Availability process integration scenario in the Proxy-to-RFC Communication variant. In this variant you configure the business system of airline American Airlines (AA) (client 107) as receiver of RFCs. This demo example is implemented as the process integration scenario CheckFlightSeatAvailability. The process integration scenario is located in the Enterprise Services Repository, in the software component SAP BASIS, software component version SAP BASIS 7.40, in the namespace For the business description of the process integration scenario, see

48 11. SAP NetWeaver 7.40 Demo Examples Configuration Configuration in Integration Directory All configuration objects for this variant are saved in the same configuration scenario as used for the Proxy-to-Proxy variant (XIDemo_CheckFlightSeatAvailability). Settings in the Model Configurator To accomplish the following configuration steps in the Integration Directory, proceed as described in detail in section To configure the process integration scenario CheckFlightSeatAvailability in the Proxy-to-RFC-Communication variant, use the settings as listed in the table below. Settings for the Process Integration Scenario CheckFlightSeatAvailability (Proxy-to- RFC-Communication) Configuration Step Selecting the Process Integration Scenario (Component View) and Creating the Scenario Settings Perform the following steps: a) Open the scenario XIDemo_CheckFlightSeatAvailability. b) Switch to change mode ( ). c) In the header area of the object editor, choose Model Configurator ( ). d) Select the push button Select Component View ( ). A new screen appears where the available Component Views for the process integration scenario are displayed. e) In the preview area, select the component view ABAP_Proxy_2_RFC and choose Apply. Assigning Communication Components If you have not configured the Check Flight Seat Availability process integration scenario in the Proxy-to- Proxy Communication variant before, you first have to start the model configurator and create the configuration scenario XIDemo_CheckFlightSeatAvailability before you can proceed with the next configuration steps. For a detailed description of the procedure, see under Selecting the Process integration scenario (Component View). For the Agency application component assign the communication component <SID>_105. For the Airline application component assign the communication component <SID>_ March 2012

49 Configuring the Connection For the sender/receiver relation, select the receiver communication channel GeneratedReceiverChannel_RFC (assigned to receiver communication component <SID>_107). Generating the Configuration Objects No sender agreement with a sender channel is required for this variant since an RFC is only expected on the receiver side. Same as described under Manual Editing In the receiver determination <SID>_105 FlightSeatAvailabilityQuery_Out delete the line containing the service <SID>_107 and change the receiver rule to XIDemoAirlineID_LH_AA to be able to address now both airlines LH and AA. Final Steps Save the scenario XIDemo_CheckFlightSeatAvailability. Activate the scenario XIDemo_CheckFlightSeatAvailability and all objects that it uses (follow the procedure as described in section ) Executing and Testing There is an application in the SAP system of the Integration Server (client 105) that you can use to test the process integration scenario (for both configurations). The execution of this variant of the process integration scenario is not different from that of the Proxy-to-Proxy variant (see 5.1.3). This time, however, you use the flights AA 0017, AA 0064, AA 9999 and N.N For more information about how to start the application, how to check that the process integration scenario has been executed correctly and how to monitor the XI message exchange, see Executing the Process Integration Scenario and the chapter Monitoring at the end of the document. 6.2 Booking a Single Flight (Proxy-to-IDoc Communication) This section describes how to configure the Booking a Single Flight process integration scenario in the Proxy-to-IDoc Communication variant. In this variant, you configure the business system of airline American Airlines (AA) (client 107) as a receiver of IDocs. If you are interested in the alternative using the variant with Java IDoc Adapter please go directly to 6.3. Booking a Single Flight (Proxy-to-IDoc AAE Communication) instead of configuring this variant with the ABAP IDoc adapter. Also keep in mind when you are use the alternative variant you have to use 6.5 for the Booking Connecting Flights (Proxy-to- Proxy/IDoc AAE Communication). This demo example is implemented as the process integration scenario SingleFlightBooking. The process integration scenario is located in the Enterprise Services Repository, in the software component SAP BASIS, 2012

50 software component version SAP BASIS 7.40, in the namespace For the business description of the process integration scenario, see Special Settings for IDoc Communication in the SAP System You must make the following additional settings in the SAP system for the SingleFlightBooking (Proxy-to-IDoc Communication) variant. To call the transactions required for the configuration steps below, add the following role to user XIDEMO: SAP_BC_SRV_EDI_ADMIN. Specifying RFC Destinations To enable the business system of the airline American Airlines (business system <SID>_107) to communicate with the Integration Server by using IDocs, you must do the following: Specify an R/3 connection to the Integration Server (client 001) in the client of the airline American Airlines (107) Enter the required information as an RFC destination. ABAP Connection to the Integration Server 1. In client 107, call the transaction Display and Maintain RFC Destinations. To do this, choose Process Integration Environment RFC Destinations (Display and Maintenance) (SM59) in the user menu. 2. Select the ABAP connections node. 3. In the pushbutton bar, choose Create. 4. In the RFC destination field, enter the following name for the RFC destination for the Integration Server: <SID>_ In the Connection type field, in the dropdown list box, select 3 - Connection to ABAP System. 6. In the Description frame, in the Description 1 field, enter the following: Connection to Integration Server. 7. Choose Enter ( ). 8. On the Technical settings tab page, enter the following information: In the Target host field, enter localhost. In the System Number field, specify the system number of the SAP system (for example, 73). To find the system number, choose Properties in the logon dialog box (SAP Logon). The system number is displayed in the System Number field. 9. On the Logon/Security tab page, enter the logon data for the target system. In the Logon frame, enter the following information: In the Client field, specify the client of the Integration Server: 001. In the User field, enter the name of a copy from PIAPPLUSER. In the Password field, enter the password set for this user in client March 2012

51 Save the RFC destination (choose the Save pushbutton). 11. To test the RFC destination, choose Test connection in the pushbutton bar. 12. Choose Back ( ). R/3 Connection to the Application System of the Airline American Airlines See Editing the Communication Channels with Adapter Type IDoc Specifying the IDoc Port To be able to send the IDocs from the application system of American Airlines to the system of the Integration Server, you must specify the port of the Integration Server In client 107, call the transaction WE21. To do this, choose Tools ALE ALE Administration Runtime Settings Port Maintenance (WE21) in the SAP menu. 2. Select the Ports Transactional RFC node and choose Create ( ). 3. In the Ports in IDoc processing dialog box, select the own port name radio button. 4. Enter the following port name: SAP<SID>. 5. Choose Continue ( ). 6. In the Description field, enter Integration Server. 7. In the RFC destination field, specify the RFC destination of the Integration Server: <SID>_ Save your entries ( ). Specifying IDocs To define the involved IDocs, you must execute the following steps. Messages from the Travel Agency to the Airline American Airlines First, define the IDocs for the messages from the travel agency to the airline American Airlines (client 105 client 107). Execute the following steps in client Call the transaction WE20 in client 107. To do this, choose Tools ALE ALE Administration Runtime Settings Partner Profiles (WE20) in the SAP menu. 2. In the Partner no. field, specify the logical system of the travel agency: <SID>CLNT In the Partn.Type field, in the dropdown list box, select LS (for logical system). 4. On the Post processing: permitted agent tab page, specify the user for the IDoc administrator. The IDoc administrator can then execute the IDoc monitoring. In the Type field, specify the user type (for example, organizational unit, normal user). 5. Save your entries ( ). 6. In the Inb. parameters. table, add a new line (Create inbound parameter ( )). 7. In the Partner profiles: Inbound parameters dialog box, in the Message Type field, specify the inbound IDoc. In the dropdown list box, select FLIGHTBOOKING_CREATEANDRESP. 8. On the Inbound options tab page, in the Process code field, select the entry BAPI in the dropdown list box. 9. Save your entries ( ). 10. Choose Back ( ).

52 14. SAP NetWeaver 7.40 Demo Examples Configuration Messages from the Airline American Airlines to the Integration Server Define the IDocs for the messages from the airline American Airlines to the Integration Server (client 107 client 001). Execute the following steps in client 107. Note that the receiver in this send direction is the Integration Server (that is, the IDoc adapter) and not the travel agency. The actual receiver system (the travel agency) is not defined until routing (receiver determination). 1. In the Partner Profiles dialog box, choose Create ( ). 2. In the Partner no. field, specify the logical system of the Integration Server: <SID>CLNT In the Partn.Type field, in the dropdown list box, select LS (for logical system). 4. On the Post processing: permitted agent tab page, specify the user for the IDoc administrator. The IDoc administrator can then execute the IDoc monitoring. In the Type field, specify the user type (for example, organizational unit, normal user). 5. Save your entries ( ). 6. In the Outbound parameters table, add a new line (Create outbound parameter ( )). 7. In the Partner profiles: Outbound parameters dialog box, in the Message Type field, specify the outbound IDoc. In the dropdown list box, select FLIGHTBOOKING_SENDRESPONSE. 8. On the Outbound Options tab page, in the Receiver Port field, select the IDoc port of the Integration Server: SAP<SID>. 9. In the Output Mode frame, choose Transfer IDoc immed. (radio button). 10. In the IDoc Type frame, in the Basic Type field, select the basic type of the outbound IDoc: FLIGHTBOOKING_SENDRESPONSE Save your entries ( ). Specifying the ALE Distribution Model (SALE) Specifying the Sender, Receiver, and Underlying BAPI Execute the following steps in client Call the transaction Display IMG (transaction code SALE). 2. Choose Modeling and Implementing Integration processes Maintain Distribution Model and Distribute Views. 3. Switch to change mode. To do this, choose Switch between display and edit mode ( ). 4. Choose Create model view. 5. In the Short Text field, enter XI IDoc. 6. In the Technical Name field, enter XIDEMO. 7. Choose Continue ( ). 8. The system displays the distribution model as another node under Model views. Select the node XI IDoc. 9. Choose Add BAPI. 10. Call the input help in the Sender/client field. 52 March 2012

53 11. Select the logical system <SID>CLNT107 and choose Copy ( ). 12. In the Receiver/server field, select the logical system <SID>CLNT In the Obj. name/interface field, select the business object FlightBooking (by using the input help). 14. In the Method field, select the BAPI SendResponse (as a method of the business object FlightBooking). 15. Choose Continue ( ). 16. Save the distribution model. Defining the Ports in the IDoc Adapter The IDoc adapter requires metadata to be able to convert the IDocs sent to it into IDoc XML. To establish an RFC connection to the system that contains the metadata, you must execute the following steps. 1. In client 001, call the transaction Port Maintenance in IDoc Adapter (IDX1). To do this, choose Process Integration Configuration Port Maintenance in IDoc Adapter in the user menu. 2. Choose Create ( ). 3. In the Port field, enter SAP<SID>. 4. In the Client field, enter In the Description field, enter Airline American Airlines. 6. In the RFC destination field, specify the RFC destination of the airline American Airlines: <SID>_ Save your entries ( ). The name of the port is generated automatically: SAP<SID>_ Configuration in Integration Directory All configuration objects for this variant are saved in the same configuration scenario as used for the Proxy-to-Proxy variant (XIDemo_SingleFlightBooking). Settings in the Model Configurator To accomplish the following configuration steps in the Integration Directory, proceed as described in detail in section To configure the process integration scenario SingleFlightBooking in the Proxy-to-IDoc Communication variant, use the settings as listed in the table below. 2012

54 Settings for the Process Integration Scenario SingleFlightBooking (Proxy-to-IDoc Communication) Configuration Step Selecting the Process Integration Scenario (Component View) and Creating the Scenario Settings Open the scenario XIDemo_SingleFlightBooking and call the model configurator (as described under 6.1.1). Select the component view ABAP_Proxy_2_Idoc. Assigning Communication Components Configuring the Connection Generating the Configuration Objects Manual Editing Final Steps If you have not configured the Check Flight Seat Availability process integration scenario in the Proxy-to- Proxy Communication variant before, you first have to start the model configurator and create the configuration scenario XIDemo_CheckFlightSeatAvailability before you can proceed with the next configuration steps. For a detailed description of the procedure, see under Selecting the Process integration scenario (Component View). For the Agency application component assign the communication component <SID>_105. For the Airline application component assign the communication component <SID>_107. For the connection between the actions Sending Single Flight Booking Order and Book Single Flight And Confirm (sender/receiver relation: <SID>_105/<SID>_107) select the receiver communication channel GeneratedReceiverChannel_IDoc (assigned to the receiver communication component <SID>_107). For the connection between the actions Book Single Flight And Confirm and Process Order Confirmation (sender/receiver relation: <SID>_107/<SID>_105) select the communication channel GeneratedReceiverChannel_XI (assigned to the receiver communication component <SID>_105). Same as described under In the receiver determination <SID>_105 BookingOrderRequest_Out delete the line containing the service <SID>_107 and change the receiver rule to XIDemoAirlineID_LH_AA to be able to address now both airlines LH and AA. Save the scenario XIDemo_SingleFlightBooking. Activate the scenario XIDemo_SingleFlightBooking and all objects that it uses (follow the procedure as described in section 5.1.2) Executing and Testing There is an application in the SAP system of the Integration Server (client 105) that you can use to test the process integration scenario (for both configurations). The execution of this process integration scenario variant is not different from the Proxy-to- Proxy variant ( 5.2.3). Select the flights AA 0017 or AA 0064 (instead of the Lufthansa flights) to receive a successful flight booking. 54 March 2012

55 For more information about how to start the application, how to check that the process integration scenario has been executed correctly and how to monitor the XI message exchange, Executing the Process Integration Scenario and the chapter Monitoring at the end of the document. 6.3 Booking a Single Flight (Proxy-to-IDoc AAE Communication) The existing IDoc Adapter is developed in ABAP and hence not available as a part of the Advanced Adapter Engine (AAE). To use the concept of IDocs in the AAE the new Java based IDoc Adapter was developed. The Advanced Adapter Engine is an enhancement of the Adapter Engine (AE) which allows end-to-end message processing without invoking the central Integration Engine (IE) of a PI system. Using an IDoc Adapter in an Integrated Scenario you have to choose the Java IDoc Adapter. The Java IDoc Adapter can be used in Integrated Scenarios as well as in typical scenarios. This section describes how to configure the Booking a Single Flight process integration scenario in the Proxy-to-IDoc AAE Communication variant in typical scenario. In this variant, you configure the business system of airline American Airlines (AA) (client 107) as a receiver of IDocs with the new Java IDoc adapter. Be aware that these two variants cannot run in parallel. You have to use either the ABAP IDoc adapter or the one in the AAE. If you configured the variants with the ABAP IDoc adapter first you have to change/delete the existing objects. Which configuration to be adopted is mentioned explicitly in the below chapters This demo example is implemented as the process integration scenario SingleFlightBooking. The process integration scenario is located in the Enterprise Services Repository, in the software component SAP BASIS, software component version SAP BASIS 7.40, in the namespace For the business description of the process integration scenario, see

56 Java IDoc Adapter Receiver Java IDoc Adapter Sender Special Settings for IDoc Communication in the SAP System You must make the following additional settings in the SAP system for the SingleFlightBooking (Proxy-to-IDoc AAE Communication) variant. To call the transactions required for the configuration steps below, add the following role to user XIDEMO: SAP_BC_SRV_EDI_ADMIN. Specifying TCP/IP Destinations To enable the business system of the airline American Airlines (business system <SID>_107) to communicate with the Integration Server by using IDocs AAE, you must do the following: Specify an TCP/IP connection to the Integration Server (f.e. client 001) in the client of the airline American Airlines (107) Enter the required information as an RFC destination. TCP/IP Connection to the Integration Server 1. In client 107, call the transaction Display and Maintain RFC Destinations. To do this, choose Process Integration Environment TCP/IP Destinations (Display and Maintenance) (SM59) in the user menu. 2. Select the TCP/IP connections node. 3. In the pushbutton bar, choose Create. 4. In the TCP/IP destination field, enter the following name for the TCP/IP destination for the Integration Server: <SID>_XIDEMO_JIDOC. 5. In the Connection type field, in the dropdown list box, select T TCP/IP Connection. 56 March 2012

57 6. In the Description frame, in the Description 1 field, enter the following: Connection to Integration Server for Java IDoc adapter. 7. Choose Enter ( ). 8. On the Technical settings tab page, enter the following information: For the Activation Type enable Registered Server Program. In the Program ID field, enter <SID>_XIDEMO_JIDOC. 9. Goto to Tab Unicode and in Communication Type with Target System enable Unicode 10. Save the RFC destination (choose the Save pushbutton). 11. Testing the RFC connection, choose Test connection in the pushbutton bar. This connection test fails because at that time the corresponding Sender Communication Channel for the Java IDoc adapter and Sender Agreement not configured and activated in the Integration Builder. Only when the same Program ID used in the Sender Communication Channel the connection will be worked. Otherwise ERROR: program <SID>_XIDEMO_JIDOC not registered, raises. 12. Choose Back ( ). Specifying the IDoc Port To be able to send the IDocs from the application system of American Airlines to the system of the Integration Server, you must specify the port of the Integration Server In client 107, call the transaction WE21. To do this, choose Tools ALE ALE Administration Runtime Settings Port Maintenance (WE21) in the SAP menu. 2. Select the Ports Transactional RFC node and choose Create ( ). 3. In the Ports in IDoc processing dialog box, select the own port name radio button. 4. Enter the following port name: SAP<SID>. 5. Choose Continue ( ). 6. In the Description field, enter Integration Server. 7. In the RFC destination field, specify the RFC destination of the Integration Server: <SID>_XIDEMO_JIDOC. 8. Save your entries ( ). Specifying IDocs If you had already configured the scenario with the ABAP IDoc adapter before the port already exists. In this case please only change the used RFC destination, execute step 7 and 8 only. To define the involved IDocs, you must execute the following steps. Messages from the Travel Agency to the Airline American Airlines First, define the IDocs for the messages from the travel agency to the airline American Airlines (client 105 client 107). Execute the following steps in client Call the transaction WE20 in client 107. To do this, choose Tools ALE ALE Administration Runtime Settings Partner Profiles (WE20) in the SAP menu. 2. In the Partner no. field, specify the logical system of the travel agency: <SID>CLNT

58 17. SAP NetWeaver 7.40 Demo Examples Configuration 3. In the Partn.Type field, in the dropdown list box, select LS (for logical system). 4. On the Post processing: permitted agent tab page, specify the user for the IDoc administrator. The IDoc administrator can then execute the IDoc monitoring. In the Type field, specify the user type (for example, organizational unit, normal user or your own user). 5. Save your entries ( ). 6. In the Inb. parameters. table, add a new line (Create inbound parameter ( )). 7. In the Partner profiles: Inbound parameters dialog box, in the Message Type field, specify the inbound IDoc. In the dropdown list box, select FLIGHTBOOKING_CREATEANDRESP. 8. On the Inbound options tab page, in the Process code field, select the entry BAPI in the dropdown list box. 9. Save your entries ( ). 10. Choose Back ( ). If you had already configured the scenario with the ABAP IDoc adapter before nothing has to be changed. Messages from the Airline American Airlines to the Integration Server back to the Travel Agency Define the IDocs for the messages from the airline American Airlines to the Integration Server back to the Travel Agency (client 107 client 105) Execute the following steps in client 107. Note that the receiver in this send direction is the Integration Server (that is, the IDoc adapter) and not the travel agency. The actual receiver system (the travel agency) is not defined by the Integration Server until routing (receiver determination). 1. In the Partner Profiles dialog box, choose Create ( ). 2. In the Partner no. field, specify the logical system of the Integration Server: <SID>CLNT In the Partn.Type field, in the dropdown list box, select LS (for logical system). 4. On the Post processing: permitted agent tab page, specify the user for the IDoc administrator. The IDoc administrator can then execute the IDoc monitoring. In the Type field, specify the user type (for example, organizational unit, normal user, or your own user). 5. Save your entries ( ). 6. In the Outbound parameters table, add a new line (Create outbound parameter ( )). 7. In the Partner profiles: Outbound parameters dialog box, in the Message Type field, specify the outbound IDoc. In the dropdown list box, select FLIGHTBOOKING_SENDRESPONSE. 8. On the Outbound Options tab page, in the Receiver Port field, select the IDoc port of the Integration Server: SAP<SID>. 9. In the Output Mode frame, choose Transfer IDoc immed. (radio button). 10. In the IDoc Type frame, in the Basic Type field, select the basic type of the outbound IDoc: FLIGHTBOOKING_SENDRESPONSE March 2012

59 11. Save your entries ( ). If you had already configured the scenario with the ABAP IDoc adapter before nothing has to be changed. Specifying the ALE Distribution Model (SALE) Specifying the Sender, Receiver, and Underlying BAPI Execute the following steps in client Call the transaction Display IMG (transaction code SALE). 2. Choose Modeling and Implementing Integration processes Maintain Distribution Model and Distribute Views. 3. Switch to change mode. To do this, choose Switch between display and edit mode ( ). 4. Choose Create model view. 5. In the Short Text field, enter XI IDoc. 6. In the Technical Name field, enter XIDEMO. 7. Choose Continue ( ). 8. The system displays the distribution model as another node under Model views. Select the node XI IDoc. 9. Choose Add BAPI. 10. Call the input help in the Sender/client field. 11. Select the logical system <SID>CLNT107 and choose Copy ( ). 12. In the Receiver/server field, select the logical system <SID>CLNT In the Obj. name/interface field, select the business object FlightBooking (by using the input help). 14. In the Method field, select the BAPI SendResponse (as a method of the business object FlightBooking). 15. Choose Continue ( ). 16. Save the distribution model. If you had already configured the scenario with the ABAP IDoc adapter before nothing has to be changed Configuration in Integration Directory All configuration objects for this variant are saved in the same configuration scenario as used for the Proxy-to-Proxy variant (XIDemo_SingleFlightBooking). 2012

60 Settings in the Model Configurator To accomplish the following configuration steps in the Integration Directory, proceed as described in detail in section To configure the process integration scenario SingleFlightBooking in the Proxy-to-IDocAAE Communication variant, use the settings as listed in the table below. Settings for the Process Integration Scenario SingleFlightBooking (Proxy-to-IDocAAE Communication) Configuration Step Deleting objects from Proxy-to-IDoc variant Selecting the Process Integration Scenario (Component View) and Creating the Scenario Settings If you have configured the Proxy-to-IDoc communication variant before delete the receiver agreement for the IDoc channel GeneratedReceiverChannel_IDoc before generating the objects. Delete the following receiver agreement: <SID>_105 <SID>_107 FLIGHTBOOKING_CREATEANDRESP.FLIGHTBOOKING_ CREATEANDRESP01 Activate the change list. Open the scenario XIDemo_SingleFlightBooking and call the model configurator (as described under 6.1.1). Select the component view ABAP_Proxy_2_IdocAAE. Assigning Communication Components If you have not configured the Check Flight Seat Availability process integration scenario in the Proxy-to- Proxy Communication variant before, you first have to start the model configurator and create the configuration scenario XIDemo_CheckFlightSeatAvailability before you can proceed with the next configuration steps. For a detailed description of the procedure, see under Selecting the Process integration scenario (Component View). For the Agency application component assign the communication component <SID>_105. For the Airline application component assign the communication component <SID>_ March 2012

61 Configuring the Connection Generating the Configuration Objects For the connection between the actions Sending Single Flight Booking Order and Book Single Flight And Confirm (sender/receiver relation: <SID>_105/<SID>_107) you have to specify a receiver communication channel. In this variant you specify the communication channel by creating a new channel on the basis of a communication channel template from the Enterprise Services Repository. To do this, proceed as follows: 1. In the tab Connections from the Communication component Assignment choose the dropdown menu for the push button New ( ). 2. In the dropdown menu select Create Communication Channel with Template. A wizard for creating a communication channel on the basis of a communication channel template is started. 3. Choose Continue. 4. In the Select Template step, select the XIDemoChannel_IDocAAE_Receiver communication channel template (software component version SAP BASIS 7.40, namespace 5. Choose Continue. 6. In the Create New Communication Channel step, confirm all entries by clicking Finish. 7. Click Close to close the Create New Communication Channel dialog box. The system creates a communication channel with the name XIDemoChannel_IDocAAE_Receiver. For the connection between the actions Book Single Flight And Confirm and ProcessOrderConfirmation (sender/receiver relation: <SID>_107/<SID>_105) you have to specify a sender communication channel. Please repeat the same steps (1-7) and select for the sender component <SID>_107 the XIDemoChannel_IDocAAE_Sender communication channel template (software component version SAP BASIS 7.40, namespace The system creates a communication channel with the name XIDemoChannel_IDocAAE_Sender. For the connection between the actions Book Single Flight And Confirm and Process Order Confirmation (sender/receiver relation: <SID>_107/<SID>_105) select the receiver communication channel GeneratedReceiverChannel_XI (assigned to the receiver communication component <SID>_105). Same as described under

62 Manual Editing In the receiver determination <SID>_105 BookingOrderRequest_Out delete the line containing the service <SID>_107 and change the receiver rule to XIDemoAirlineID_LH_AA to be able to address now both airlines LH and AA. To determine the outbound processing of the message, you have to specify the receiver communication channel XIDemoChannel_IDocAAE_Receiver. You have to change the following settings: In the field SAP Client enter the Client of the Receiver Business System airline American Airlines 107. In the field User Name and Password enter the User for the Receiver Business System (f.e. XIDEMO_APPL). In the field Server Name set the Server name and in the Port Number field the Port of the Receiver Business System airline American Airline. Change to tab Advanced and set Control record in IDoc XML to not Mandatory While configuring the Receiver Channel, there will be the following options in the "Advanced" tab for the Control Header in the IDoc: 1) Control Record in IDoc XML - Mandatory 2) Control Record in IDoc XML not Mandatory If the user selects 1), then it is assumed that the control record will be present in the Idoc XML. If the user selects 2), then control record will be created. For this variant you have to specify the sender communication channel XIDemoChannel_IDocAAE_Sender. You have to change the following settings: In the field SAP Client enter the Client for the Sender Business System airline American Airline 107. The American Airline send a Booking response back to the Travel Agency. In the field User Name and Password enter the User for the Sender Business System (f.e. XIDEMO_APPL) In the field Server Name set the Server name and in the Port Number field the Port of the Sender System airline American Airline. In the field Program ID enter the Program ID which correspond to the relevant RFC destination of Type T in the Sender Business System (f.e. <SID>_XIDEMO_JIDOC, Specifying TCP/IP Destinations) Final Steps Save the scenario XIDemo_SingleFlightBooking. Activate the scenario XIDemo_SingleFlightBooking and all objects that it uses (follow the procedure as described in section 5.1.2). 62 March 2012

63 6.3.3 Executing and Testing There is an application in the SAP system of the Integration Server (client 105) that you can use to test the process integration scenario (for both configurations). Please check before starting the Travel Agency BSP-Application for SingleFlightBooking in Client 107 in Transaction SM59 the created TCP/IP Destination to the Integration Server. If this connection does not work, no Process Order Confirmation will be send to the Agency. If the connection does not work, please see Notes on Troubleshooting Notes on Troubleshooting 9. The execution of this process integration scenario variant is not different from the Proxy-to- Proxy variant ( 5.2.3). Select the flights AA 0017 or AA 0064 (instead of the Lufthansa flights) to receive a successful flight booking. For more information about how to start the application, how to check that the process integration scenario has been executed correctly and how to monitor the XI message exchange, Executing the Process Integration Scenario and the chapter Monitoring at the end of the document. 6.4 Booking Connecting Flights (Proxy-to-Proxy/IDoc Communication) This section describes how to configure the Booking Connecting Flights process integration scenario in the Proxy-to-Proxy/IDoc Communication variant. In this variant, you configure the business systems of the travel agency (client 105) and the airline Lufthansa (LH) (client 106) as sender and receiver of proxies and the airline American Airlines (AA) (client 107) as sender and receiver of IDocs. If you configured the 6.2. Booking a Single Flight (Proxy-to-IDoc Communication) with the ABAP IDoc Adapter, you can execute this chapter 6.4 Booking Connecting Flights (Proxy-to- Proxy/IDoc Communication). If you configured the 6.3 Booking a Single Flight (Proxy-to-IDoc AAE Communication) with Java IDoc Adapter, please execute the chapter 6.5. Booking Connecting Flights (Proxy-to- Proxy/IDoc AAE Communication). Be aware that these two variants cannot run in parallel. You have to use either the ABAP IDoc adapter or the one in the AAE. If you configured the variants with the ABAP IDoc adapter first you have to change/delete the existing objects. Which configuration to be adopted is mentioned explicitly in the below chapters This demo example is implemented as the process integration scenario MultipleFlightBooking. The process integration scenario is located in the ES Repository, in the software component SAP BASIS, software component version SAP BASIS 7.40, in the namespace For the business description of the integration scenario, see

64 6.4.1 Special Settings for IDoc Communication in the SAP System Before running the MultipleFlightBooking (Proxy-to-Proxy/IDoc Communication) you must first execute the configuration steps of the SingleFlightBooking (Proxy-to-IDoc Communication) variant because these configurations are also used in the MultipleFlightBooking (Proxy-to- Proxy/IDoc Communication). Additionally execute the following settings. Specifying IDocs To define the involved IDocs, you must execute the following steps. Messages from the Travel Agency to the Airline American Airlines First, add the Cancel IDoc from the travel agency to the airline American Airlines (client 105 client 107). Execute the following steps in client Call the transaction WE20 in client 107. To do this, choose Tools ALE ALE Administration Runtime Settings Partner Profiles (WE20) in the SAP menu. 2. In the Inbound parameters table of Partner <SID>CLNT105 add a new line (Create inbound parameter). 3. In the Partner Profiles: Inbound Parameters dialog box, in the Message Type field, specify the inbound IDoc. In the dropdown list box, select FLIGHTBOOKING_CANCEL. 4. On the Inbound Options tab page, in the Process Code field, select the entry BAPI in the dropdown list box. 5. Save your entries. 6. Choose Back Configuration in Integration Directory All configuration objects for this variant are saved in the same configuration scenario as used for the Proxy-to-Proxy variant (XIDemo_MultipleFlightBooking). For the Proxy-to-Proxy/IDoc variant the same objects are used as for the Proxy-to-Proxy variant, because of that both scenarios cannot run in parallel. If you already have configured the Proxy-to-Proxy variant the objects (interface determination, receiver agreements) will be changed during configuration of the Proxy-to-Proxy/IDoc variant. Settings in the Model Configurator To accomplish the following configuration steps in the Integration Directory, proceed as described in detail in section To configure the process integration scenario MultipleFlightBooking in the Proxy-to-Proxy/IDoc Communication variant, use the settings as listed in the table below. Settings for the Process Integration Scenario MultipleFlightBooking (Proxy-to-Proxy Communication) Configuration Steps Deleting objects from Proxy-to-Proxy variant Settings If you have configured the Proxy-to-Proxy communication variant before delete the interface determinations for the Proxy interfaces to airline system <SID>_107 before generating the objects. Delete the following interface determinations: MultipleFlightBookingCoordinator 64 March 2012

65 Selecting the Process Integration Scenario (Component View) and Creating the Configuration Scenario Assigning Communication Components Configuring the Connection Generating the Configuration FlightBookingOrderRequest_Abstract <SID>_107 MultipleFlightBookingCoordinator FlightBookingOrderCancelationRequest_Abstract <SID>_107 Activate the change list. Open the scenario XIDemo_MultipleFlightBooking and call the Process Integration Scenario Configurator (as described under 6.1.1). Select the component view ABAP_Proxy_2_ABAP_IDoc. If you have not configured the Booking Connecting Flights process integration scenario in the Proxy-to-Proxy Communication variant before, you first have to start the process integration scenario configurator and create the configuration scenario XIDemo_MultipleFlightBooking before you can proceed with the next configuration steps. For a detailed description of the procedure, see under Selecting the Process Integration Scenario (Component View). For the Agency application component assign the component <SID>_105. For the Coordinator application component assign the component process component) MultipleFlightBookingCoordinator. (integration To select the component, choose the input help on the Component Assignment tab page. The input help icon is to the right of the Party and Component input fields. For the Airline application component assign the components <SID>_106 and <SID>_107. For the first connection between the actions Split Multiple Booking Order (BPM) and Book Single Flight And Confirm select the receiver communication channel GeneratedReceiverChannel_XI for receiver component <SID>_106. Delete the flag for <SID>_107 as this is the connection for the Proxy interface. For the second connection between the actions Split Multiple Booking Order (BPM) and Book Single Flight And Confirm select the receiver communication channel GeneratedReceiverChannel_IDoc for the receiver component <SID>_107. Delete the flag for <SID>_106 as this is the connection for the IDoc interface. For the first connection between the actions Book Single Flight And Confirm and Merge Single Confirmations (BPM) delete the flag for <SID>_107 as this is the connection for the Proxy interface. For the second connection between the actions Book Single Flight And Confirm and Merge Single Confirmations (BPM) delete the flag for <SID>_106 as this is the connection for the IDoc interface. For the connection between the actions Merge Single Confirmations (BPM) and Process Order Confirmation select the communication channel GeneratedReceiverChannel_XI (assigned to the receiver component <SID>_105). For the first connection between the actions Send Single Cancellation (BPM) and Cancel Single Flight Booking select the receiver communication channel GeneratedReceiverChannel_XI for receiver component <SID>_106. Delete the flag for <SID>_107 as this is the connection for the Proxy interface. For the second connection between the actions Send Single Cancelation (BPM) and Cancel Single Flight Booking select the receiver communication channel GeneratedReceiverChannel_IDoc for the receiver component <SID>_107. Delete the flag for <SID>_106 as this is the connection for the IDoc interface. For each sender/receiver relation with an integration process as receiver, no receiver communication channel is necessary. Generate the objects as described under

66 Objects Manual Editing Assign Header Mapping Final Steps If you had already configured the Proxy-to-Proxy communication variant before the routing conditions for the sending communication component MultipleFlightBookingCoordinator to airline systems <SID>_106 and <SID>_107 should already be assigned to the receiver determinations. To make sure the SingleFlightBooking in the Proxy-to-IDoc variant and the MultipleFlightBooking in the Proxy-to-Proxy/IDoc variant can run in parallel you have to define whether the message from the American Airline (AA) system is forwarded to the executable integration process (process integration scenario MultipleFlightBooking) or to the travel agency system (process integration scenario SingleFlightBooking). To do this, you must add conditions to the following receiver determination: <SID>_107 FLIGHTBOOKING_SENDRESPONSE* The airline uses the same outbound interface for both variants SingleFlightBooking and MultipleFlightBooking. The forwarding of the message depends on whether you are booking a single flight or a flight and a connecting flight. This is defined by the tag FBOTYPE. If FBOTYPE=S, the booking is for a single flight. If FBOTYPE=M, the booking is for a flight and a connecting flight. Add the following routing conditions to the receiver determination. Use the XPath expression in the condition editor: (/FLIGHTBOOKING_SENDRESPONSE01/IDOC /E1BPSBOSRE/E1BPSBOAGN/FBOTYPE = M) for receiver MultipleFlightBookingCoordinator (/FLIGHTBOOKING_SENDRESPONSE01/IDOC /E1BPSBOSRE/E1BPSBOAGN/FBOTYPE = S) for receiver <SID>_105 If you have not configured the Proxy-to-Proxy communication variant before you also have to add the routing conditions for the sending communication component MultipleFlightBookingCoordinator to airline systems <SID>_106 and <SID>_107 and for the sending airline Lufthansa system <SID>_106 as described under Change the following receiver determinations accordingly: MultipleFlightBookingCoordinator FlightBookingOrderCancelationRequest_Abstract MultipleFlightBookingCoordinator FlightBookingOrderRequest_Abstract <SID>_106 FlightBookingOrderConfirmation_Out To make the IDoc scenario running, you have to assign header mappings to the receiver agreements for the integration process sending IDocs to be able to get the logical system of the sender. Open the following two receiver agreements and set <SID>_105 as sender communication component: MultipleFlightBookingCoordinator <SID>_107 FLIGHTBOOKING_CANCEL.FLIGHTBOOKING_CANCEL01 MultipleFlightBookingCoordinator <SID>_107 FLIGHTBOOKING_CREATEANDRESP.FLIGHTBOOKING_CREATEANDRE SP01 Save the receiver agreements. Save the scenario XIDemo_MultipleFlightBooking. Activate the scenario XIDemo_MultipleFlightBooking and all objects that it uses (follow 66 March 2012

67 the procedure as described in section ) Executing and Testing There is an application in the SAP system of the Integration Server (client 105) that you can use to test the configuration of the integration scenario (for both configurations). The execution of this process integration scenario variant is not different from the Proxy-to- Proxy variant (section 5.3.4). Select the combination Lufthansa 0400 and American Airlines 0017 to receive a successful flight booking. Also perform section Monitoring in Integration Process Monitor for monitoring of involved Integration process component MultipleFlightBookingCoordination 6.5 Booking Connecting Flights (Proxy-to-Proxy/IDoc AAE Communication) This section describes how to configure the Booking Connecting Flights process integration scenario in the Proxy-to-Proxy/IDoc Communication variant. In this variant, you configure the business systems of the travel agency (client 105) and the airline Lufthansa (LH) (client 106) as sender and receiver of proxies and the airline American Airlines (AA) (client 107) as sender and receiver of IDocs. This demo example is implemented as the process integration scenario MultipleFlightBooking. The process integration scenario is located in the ES Repository, in the software component SAP BASIS, software component version SAP BASIS 7.40, in the namespace For the business description of the integration scenario, see Java IDoc Adapter Sender

68 6.5.1 Special Settings for IDoc Communication in the SAP System Before running the MultipleFlightBooking (Proxy-to-Proxy/IDoc AAE Communication) you must first execute the configuration steps of the SingleFlightBooking (Proxy-to-IDoc AAE Communication) variant because these configurations are also used in the MultipleFlightBooking (Proxy-to-Proxy/IDoc AAE Communication). Additionally execute the following settings. Specifying IDocs To define the involved IDocs, you must execute the following steps. 68 March 2012

69 Messages from the Travel Agency to the Airline American Airlines First, add the Cancel IDoc from the travel agency to the airline American Airlines (client 105 client 107). Execute the following steps in client Call the transaction WE20 in client 107. To do this, choose Tools ALE ALE Administration Runtime Settings Partner Profiles (WE20) in the SAP menu. 2. In the Inbound parameters table of Partner <SID>CLNT105 add a new line (Create inbound parameter). 3. In the Partner Profiles: Inbound Parameters dialog box, in the Message Type field, specify the inbound IDoc. In the dropdown list box, select FLIGHTBOOKING_CANCEL. 4. On the Inbound Options tab page, in the Process Code field, select the entry BAPI in the dropdown list box. 5. Save your entries. 6. Choose Back. If you had already configured the scenario with the ABAP IDoc adapter before nothing has to be changed Configuration in Integration Directory All configuration objects for this variant are saved in the same configuration scenario as used for the Proxy-to-Proxy variant (XIDemo_MultipleFlightBooking). For the Proxy-to-Proxy/IDoc AAE variant the same objects are used as for the Proxy-to-Proxy variant, because of that both scenarios cannot run in parallel. If you already have configured the Proxy-to-Proxy variant the objects (interface determination, receiver agreements) will be changed during configuration of the Proxy-to-Proxy/IDoc AAE variant. Settings in the Model Configurator To accomplish the following configuration steps in the Integration Directory, proceed as described in detail in section To configure the process integration scenario MultipleFlightBooking in the Proxy-to-Proxy/IDoc AAE Communication variant, use the settings as listed in the table below. Settings for the Process Integration Scenario MultipleFlightBooking (Proxy-to- Proxy/IDoc AAE Communication) Configuration Steps Deleting objects from Proxy-to-Proxy variant Deleting Settings If you have configured the Proxy-to-Proxy communication variant before delete the interface determinations for the Proxy interfaces to airline system <SID>_107 before generating the objects. Delete the following interface determinations: MultipleFlightBookingCoordinator FlightBookingOrderRequest_Abstract <SID>_107 MultipleFlightBookingCoordinator FlightBookingOrderCancelationRequest_Abstract <SID>_107 Activate the change list. If you have configured the Proxy-to-Proxy/IDoc communication variant before delete 2012

70 objects from Proxy-to- Proxy/IDoc variant Selecting the Process Integration Scenario (Component View) and Creating the Configuration Scenario Assigning Communication Components Configuring the Connection the receiver agreement for the IDoc channel GeneratedReceiverChannel_IDoc before generating the objects. Delete the following receiver agreements: MultipleFlightBookingCoordinator <SID>_107 FLIGHTBOOKING_CREATEANDRESP.FLIGHTBOOKING_CREATEANDRES P01 MultipleFlightBookingCoordinator <SID>_107 FLIGHTBOOKING_CANCEL.FLIGHTBOOKING_CANCEL01 Activate the change list. Open the scenario XIDemo_MultipleFlightBooking and call the Process Integration Scenario Configurator (as described under 6.1.1). Select the component view ABAP_Proxy_2 ABAP_IDocAAE. If you have not configured the Booking Connecting Flights process integration scenario in the Proxy-to-Proxy Communication variant before, you first have to start the process integration scenario configurator and create the configuration scenario XIDemo_MultipleFlightBooking before you can proceed with the next configuration steps. For a detailed description of the procedure, see under Selecting the Process Integration Scenario (Component View). For the Agency application component assign the component <SID>_105. For the Coordinator application component assign the component (integration process component) MultipleFlightBookingCoordinator. To select the component, choose the input help on the Component Assignment tab page. The input help icon is to the right of the Party and Component input fields. For the Airline application component assign the components <SID>_106 and <SID>_107. For the first connection between the actions Split Multiple Booking Order (BPM) and Book Single Flight And Confirm select the receiver communication channel GeneratedReceiverChannel_XI for receiver component <SID>_106. Delete the flag for <SID>_107 as this is the connection for the Proxy interface. For the second connection between the actions Split Multiple Booking Order (BPM) and Book Single Flight And Confirm select the receiver communication channel XIDemoChannel_IDocAAE_Receiver for receiver component <SID>_107. Delete the flag for <SID>_106 as this is the connection for the IDoc interface. For the first connection between the actions Book Single Flight And Confirm and Merge Single Confirmations (BPM) delete the flag for <SID>_107 as this is the connection for the Proxy interface. For the second connection between the actions Book Single Flight And Confirm and Merge Single Confirmations (BPM) delete the flag for <SID>_106 as this is the connection for the IDoc interface. For the sender component <SID>_107 we need a sender Java IDoc Adapter select the sender communication channel XIDemoChannel_IdocAAE_Sender. For the connection between the actions Merge Single Confirmations (BPM) and Process Order Confirmation select the communication channel GeneratedReceiverChannel_XI (assigned to the receiver component <SID>_105). For the first connection between the actions Send Single Cancellation (BPM) and Cancel Single Flight Booking select the receiver communication channel GeneratedReceiverChannel_XI for receiver component <SID>_106. Delete the flag for <SID>_107 as this is the connection for the Proxy interface. For the second connection between the actions Send Single Cancelation (BPM) and Cancel Single Flight Booking select the receiver communication channel 70 March 2012

71 Generating the Configuration Objects Manual Editing Assign Header Mapping XIDemoChannel_IDocAAE_Receiver for receiver component <SID>_107. Delete the flag for <SID>_106 as this is the connection for the IDoc interface. For each sender/receiver relation with an integration process as receiver, no receiver communication channel is necessary. Generate the objects as described under If you had already configured the Proxy-to-Proxy communication variant before the routing conditions for the sending communication component MultipleFlightBookingCoordinator to airline systems <SID>_106 and <SID>_107 should already be assigned to the receiver determinations. To make sure the SingleFlightBooking in the Proxy-to-IDoc AAE variant and the MultipleFlightBooking in the Proxy-to-Proxy/IDoc AAE variant can run in parallel you have to define whether the message from the American Airline (AA) system is forwarded to the executable integration process (process integration scenario MultipleFlightBooking) or to the travel agency system (process integration scenario SingleFlightBooking). To do this, you must add conditions to the following receiver determination: <SID>_107 FLIGHTBOOKING_SENDRESPONSE* The airline uses the same outbound interface for both variants SingleFlightBooking and MultipleFlightBooking. The forwarding of the message depends on whether you are booking a single flight or a flight and a connecting flight. This is defined by the tag FBOTYPE. If FBOTYPE=S, the booking is for a single flight. If FBOTYPE=M, the booking is for a flight and a connecting flight. Add the following routing conditions to the receiver determination. Use the XPath expression in the condition editor: (/FLIGHTBOOKING_SENDRESPONSE01/IDOC /E1BPSBOSRE/E1BPSBOAGN/FBOTYPE = M) for receiver MultipleFlightBookingCoordinator (/FLIGHTBOOKING_SENDRESPONSE01/IDOC /E1BPSBOSRE/E1BPSBOAGN/FBOTYPE = S) for receiver <SID>_105 If you have not configured the Proxy-to-Proxy communication variant before you also have to add the routing conditions for the sending communication component MultipleFlightBookingCoordinator to airline systems <SID>_106 and <SID>_107 and for the sending airline Lufthansa system <SID>_106 as described under Change the following receiver determinations accordingly: MultipleFlightBookingCoordinator FlightBookingOrderCancelationRequest_Abstract MultipleFlightBookingCoordinator FlightBookingOrderRequest_Abstract <SID>_106 FlightBookingOrderConfirmation_Out To make the IDoc scenario running, you have to assign header mappings to the receiver agreements for the integration process sending IDocs to be able to get the logical system of the sender. Open the following two receiver agreements and set <SID>_105 as sender communication component: MultipleFlightBookingCoordinator <SID>_

72 Final Steps FLIGHTBOOKING_CANCEL.FLIGHTBOOKING_CANCEL01 MultipleFlightBookingCoordinator <SID>_107 FLIGHTBOOKING_CREATEANDRESP.FLIGHTBOOKING_CREATEANDRE SP01 Save the receiver agreements. Save the scenario XIDemo_MultipleFlightBooking. Activate the scenario XIDemo_MultipleFlightBooking and all objects that it uses (follow the procedure as described in section ) Executing and Testing There is an application in the SAP system of the Integration Server (client 105) that you can use to test the configuration of the integration scenario (for both configurations). The execution of this process integration scenario variant is not different from the Proxy-to- Proxy variant (section 5.3.4). Select the combination Lufthansa 0400 and American Airlines 0017 to receive a successful flight booking. Also perform section Monitoring in Integration Process Monitor for monitoring of involved Integration process component MultipleFlightBookingCoordination 7 Configuring Process Integration Scenarios for B2B-like Communication 7.1 Preliminary Steps Activating the SOA Manager To be able to start the Web service configuration, you have to activate the Web Dynpro application. /sap/bc/webdynpro/sap/appl_soap_management /sap/public/bc/ur /sap/public/bc/icons /sap/public/bc/icons_rtl /sap/public/bc/webicons /sap/public/bc/pictograms /sap/public/bc/webdynpro/* (activate all subnodes) /sap/public/myssocntl /sap/bc/srt/* (activate all subnodes) /sap/xi/wsdl_url See also SAP notes , and Log on to the SAP system in client Call transaction Maintain Service. To do this, choose Tools Administration Administration Network HTTP Service Hierarchy Maintenance (SICF) in the SAP menu. 72 March 2012

73 3. In the Virt.Hosts / Services column, expand the following nodes: default host sap bc webdynpro sap. Select the entry appl_soap_management. Entry in gray font: Service is not activated. Entry in black font: Service is activated. 4. In the context menu, choose Activate Service. 5. Activate the services described above using the same procedure. 7.2 Checking Flight Seat Availability (Proxy-to-Web- Service Communication) This section describes how to configure the Checking Flight Seat Availability process integration scenario in the Proxy-to-Web Service Communication variant. In this variant, you configure the airline United Airlines (UA) (client 107) as Web service provider. This demo example is implemented as the process integration scenario CheckFlightSeatAvailability. The process integration scenario is located in the Enterprise Services Repository, in the software component SAP BASIS, software component version SAP BASIS 7.40, in the namespace For the business description of the process integration scenario, see In this variant, the airline United Airlines offers a Web service for the communication with the Integration Server. The Web service definition is delivered with the demo examples. To display the Web service definition, call transaction Object Navigator (SE80) in the SAP system. Select the package SAI_DEMO_AIRLINE and open the node Enterprise Services Service Provider. The name of the Web service is SXIDAL_FLIGHTSEATAVAIL_CHECK To enable the Web service configuration, assign the role SAP_BC_WEBSERVICE_ADMIN to the user XIDEMO in client 107, see chapter In order to configure the Flight Availability Check (Proxy-to-Web Service Communication) variant, you have to activate the Web service in the SAP system Activating Web Service You must make the following additional settings in the SAP system (client 107): 1. Call transaction SOAMANAGER (SOA Manager) Service Administration Single Service Configuration. 2. Search by Service, the search pattern SXIDAL_FLIGHTSEATAVAIL_CHECK in field Both Names, select Go. 3. Select the Web service definition SXIDAL_FLIGHTSEATAVAIL_CHECK. 4. Select Apply Selection.

74 5. In the tab Configurations select Create Endpoint. 6. As Service Name set SXIDAL_FLIGHTSEATAVAIL_CHECKService, as Description use Provide Flight Seat Availability. In field New Binding set SXIDAL_FLIGHTSEATAVAIL_CHECKSoapBinding and choose Apply Settings. 7. The Web Service Configuration of Service Definition: SXIDAL_FLIGHTSEATAVAIL_CHECK opens. 8. In tab Provider Security select Transport Channel authentication User ID/Password. 9. Choose Save 10. To specify the receiver communication channel for the airline, you need to know the Web service address. For this follow the link Open WSDL document for selected binding in tab Overview of the service definition you just created. The WSDL definition of the Web service is displayed. You have to use the WSDL URL later in the channel configuration. WSDL URL looks like: http(s)://<server>:<port/sap/bc/srt/wsdl/srvc_<number>/wsdl 11/allinone/ws_policy/document?sap-client= Store the WSDL URL into a temporary storage (for example, a notepad file) for later use Configuration in Integration Directory Settings in the Model Configurator To accomplish the following configuration steps in the Integration Directory, proceed as described in detail in section To configure the process integration scenario CheckFlightSeatAvailability in the Proxy-to-Web Service Communication variant, use the settings as listed in the table below. All configuration objects for this variant are saved in the same configuration scenario as used for the Proxy-to-Proxy variant (XIDemo_CheckFlightSeatAvailability). Settings for the Process Integration Scenario CheckFlightSeatAvailability (Proxy-to- Web Service Communication) Configuration Step Settings 74 March 2012

75 Selecting the Process Integration Scenario (Component View) and Creating the Scenario Open the scenario XIDemo_CheckFlightSeatAvailability and call the model configurator (as described under 6.1.1). Select the component view ABAP_Proxy_2_Web_Service. Assigning Communication Components Configuring the Connection If you have not configured the Check Flight Seat Availability process integration scenario in the Proxy-to- Proxy Communication variant before, you first have to start the model configurator and create the configuration scenario XIDemo_CheckFlightSeatAvailability before you can proceed with the next configuration steps. For a detailed description of the procedure, see under Selecting the Process integration scenario (Component View). For the Agency application component Assign the business system component <SID>_105 (entry under Business System Components) Assign the party XIDemo_Agency and component CheckFlightSeatAvailability (entries under Business Components for External Communication) For the Airline application component Assign the party XIDemo_UnitedAirlines and component ProvideFlightSeatAvailability (entries under Assign Business Components for B2B Communication) For the sender/receiver relation you have to specify a receiver communication channel (receiver communication component ProvideFlightSeatAvailability). In this variant you specify the communication channel by creating a new channel on the basis of a communication channel template from the Enterprise Services Repository. To do this, proceed as follows: 1. In the tab Connections from the Communication component Assignment choose the dropdown menu for the push button New ( ). 2. In the dropdown menu select Create Communication Channel with Template. A wizard for creating a communication channel on the basis of a communication channel template is started. 3. Choose Continue. 4. In the Select Template step, select the XIDemoChannel_WS communication channel template (software component version SAP BASIS 7.40, namespace 5. Choose Continue. 6. In the Create New Communication Channel step, confirm all entries by clicking Finish. 7. Click Close to close the Create New Communication Channel dialog box. The system creates a communication channel with the name XIDemoChannel_WS. 2012

76 Generating the Configuration Objects Manual Editing Final Steps Same as described under To define exactly how a message is to be forwarded from the travel agency to the airline you must change the routing condition in the receiver determination <SID>_105 FlightSeatAvailabilityQuery_Out. Delete the line containing party XIDemo_UnitedAirline and communication component ProvideFlightSeatAvailability and change the receiver rule to XIDemoAirlineID_all to be able to address now the airlines LH, AA and UA. For a detailed description on how to make these settings with the generation log, see To determine the outbound processing of the message, you have to specify the receiver communication channel XIDemoChannel_WS. In the channel you have to change the following settings: In the field WSDL access URL, enter the WSDL URL you have found out before (see 7.2.1). (e.g. ber>/wsdl11/allinone/ws_policy/document?sap-client=107 In the field Authentication Method for WSDL access, select Basic Authentication over HTTP, set the user XIDEMO_WS with the password you set in chapter In the Technical Transport Settings in field Target Host select the Service Information using the Input Help. The inputs in fields Service Name/Port and URL Access Path should be entered automatically when you select the Target Host. Save the channel. In the receiver agreement you have to configure the User Authentication. Open the receiver agreement <SID>_105 XIDemo_UnitedAirlines ProvideFlightSeatAvailability FlightSeatAvailabilityQuery_In. Under Adapter-Specific Attributes set the user name and password. In the field User Name enter user XIDEMO_WS. In the field User Password enter the password set in chapter Save the agreement. Save the scenario XIDemo_CheckFlightSeatAvailability. Activate the scenario XIDemo_CheckFlightSeatAvailability and all objects that it uses (follow the procedure as described in section Executing and Testing There is an application in the SAP system of the Integration Server (client 105) that you can use to test the process integration scenario (for both configurations). The execution of this variant of the process integration scenario is not different from that of the Proxy-to-Proxy and Proxy-to-RFC variant (see 5.1.3). This time, however, you use the flights UA 0941, UA 3504, UA 9999 and N.N March 2012

77 7.3 Checking Flight Seat Availability (Web Service-to- Web-Service Direct Communication) This section describes how to configure the Checking Flight Seat Availability process integration scenario in the Web Service-to-Web Service Communication variant. In this variant, you configure the Agency (client 105) as Web Service consumer and the airline Singapore Airlines (SQ) (client 107) as Web service provider. The communication is done directly from the agency to the Singapore Airline system without message transfer in the Integration Server. This demo example is implemented as the process integration scenario CheckFlightSeatAvailability. The process integration scenario is located in the Enterprise Services Repository, in the software component SAP BASIS, software component version SAP BASIS 7.40, in the namespace For the business description of the process integration scenario, see In this variant, the airline Singapore Airlines offers a Web service for the communication and the agency consumes this Web service in a direct Web Service call. The Web service definition is delivered with the demo examples. To display the Web service definition, call transaction Object Navigator (SE80) in the SAP system. Select the package SAI_DEMO_AIRLINE and open the node Enterprise Services Service Provider. The name of the Web service is SXIDAL_FLIGHTSEATAVAIL_CHECK. To enable the Web service configuration, assign the role SAP_BC_WEBSERVICE_ADMIN to the user XIDEMO in client 107, see chapter In order to configure the Flight Availability Check (Web Service-to-Web Service Communication) variant, you have to activate the Web service in the SAP system. As you already activated the Web Service in the variant Proxy-to-Web Service it can also be used in the Web Service-to-Web Service variant. If you have not executed the CheckFlightSeatAvailability variant Proxy-to-Web Service you have to execute chapter now. Otherwise use the WSDL and endpoint-url from chapter in the Web Service-to- Web Service variant as well Activating the WS Cache Notification for the Agency To activate the automatic configuration transfer for the Web Service Configuration in the agency client you have to switch on the WS configuration using the WS Adapter and set user and password for the cache notification in the business system in the directory. 1. In the integration directory open the business system <SID>_105 via double click. 2. Switch to change mode ( ). 3. In the tab Logon Data set the flag for Support Communication using the WS Adapter. As user set a user with the role SAP_XI_ID_SERV_USER_MAIN (for example PIDIRUSER) with the corresponding password in client Save the business system <SID>_105 and activate the change list. 2012

78 With this setting the WS consumer configuration will be done automatically in the agency client Configuration in Integration Directory Settings in the Model Configurator To accomplish the following configuration steps in the Integration Directory, proceed as described in detail in section To configure the process integration scenario CheckFlightSeatAvailability in the Web Service-to-Web Service Communication variant, use the settings as listed in the table below. All configuration objects for this variant are saved in the same configuration scenario as used for the Proxy-to-Proxy variant (XIDemo_CheckFlightSeatAvailability). Settings for the Process Integration Scenario CheckFlightSeatAvailability (Proxy-to- Web Service Communication) Configuration Step Selecting the Process Integration Scenario (Component View) and Creating the Scenario Settings Open the scenario XIDemo_CheckFlightSeatAvailability and call the model configurator (as described under 6.1.1). Select the component view Web_Service_2_Web_Service. Assigning Communication Components If you have not configured the Check Flight Seat Availability process integration scenario in another variant before, you first have to start the model configurator and create the configuration scenario XIDemo_CheckFlightSeatAvailability before you can proceed with the next configuration steps. For a detailed description of the procedure, see under Selecting the Process integration scenario (Component View). For the Agency application component Assign the business system component <SID>_105 (entry under Business System Components) Assign the party XIDemo_Agency and component CheckFlightSeatAvailability (entries under Business Components for External Communication) For the Airline application component Assign the party XIDemo_SingaporeAirlines and component ProvideFlightSeatAvailability (entries under Assign Business Components for B2B Communication) 78 March 2012

79 Configuring the Connection Generating the Configuration Objects For the receiver relation you have to specify a receiver communication channel (receiver communication component ProvideFlightSeatAvailability). In this variant you specify the receiver communication channel by creating a new channel on the basis of a communication channel template from the Enterprise Services Repository. To do this, proceed as follows: 1. In the tab Connections from the Communication component Assignment choose the dropdown menu for the push button New ( ). 2. In the dropdown menu select Create Communication Channel with Template. A wizard for creating a communication channel on the basis of a communication channel template is started. 3. Choose Continue. 4. In the Select Template step, select the XIDemoChannel_WS communication channel template (software component version SAP BASIS 7.40, namespace 5. Choose Continue. 6. In the Create New Communication Channel step, confirm all entries by clicking Finish. 7. Click Close to close the Create New Communication Channel dialog box. The system creates a communication channel with the name XIDemoChannel_WS. 8. Set the flag for Direct Connection. Same as described under

80 Manual Editing Final Steps To determine the outbound processing of the message, you have to specify the receiver communication channel XIDemoChannel_WS. In the channel you have to change the following settings: In the field WSDL access URL, enter the WSDL URL you have found out before (see 7.2.1). (e.g. er>/wsdl11/allinone/ws_policy/document?sap-client=107 In the field Authentication Method for WSDL access, select Basic Authentication over HTTP, set the user XIDEMO_WS with the password you set in chapter In the Technical Transport Settings in field Target Host select the Service Information using the Input Help. The inputs in fields Service Name/Port and URL Access Path should be entered automatically when you select the Target Host. Save the channel. In the direct connection you have to configure the User Authentication. Open the Direct connection <SID>_105 FlightSeatAvailabilityQuery_Out XIDemo_SingaporeAirlines. Under Adapter-Specific Attributes set the user name and password. In the field User Name enter user XIDEMO_WS. In the field User Password enter the password set in chapter Save the direct connection. Save the scenario XIDemo_CheckFlightSeatAvailability. Activate the scenario XIDemo_CheckFlightSeatAvailability and all objects that it uses (follow the procedure as described in section Executing and Testing There is an application in the SAP system of the Integration Server (client 105) that you can use to test the process integration scenario (for both configurations). The execution of this variant of the process integration scenario is not different from that of the Proxy-to-Proxy, Proxy-to-RFC and Proxy-to-Web Service variant (see 5.1.3). This time, however, you use the flights SQ 0988, SQ 0997, SQ 9999 and N.N If you get the error No sender agreement found for, <SID>_105, XIDemo_SingaporeAirlines, ProvideFlightSeatAvailability, FlightSeatAvailabilityQuery_Out check out the chapter Error Message: No sender agreement found for, <SID>_105 in the Troubleshooting Chapter 9 at the end of this document. Be aware that for this kind of communication WS WS direct communication no messages can be found in the PI monitoring (PI Monitoring Home, SXMB_MONI, Solution Manager). 7.4 Booking a Single Flight (Proxy-to-Web-Service 80 March 2012

81 Communication) This section describes how to configure the Booking a Single Flight process integration scenario in the Proxy-to-Web Service Communication variant. In this variant, you configure the airline United Airlines (UA) (client 107) as Web service provider. This demo example is implemented as the process integration scenario SingleFlightBooking. The process integration scenario is located in the Enterprise Services Repository, in the software component SAP BASIS, software component version SAP BASIS 7.40, in the namespace For the business description of the process integration scenario, see In this variant, the airline United Airlines offers a Web service for the communication with the Integration Server. The Web service definition is delivered with the demo examples. To display the Web service definition, call transaction Object Navigator (SE80) in the SAP system. Select the package SAI_DEMO_AIRLINE and open the node Enterprise Services Service Provider. The name of the Web service is SXIDAL_FBO_REQUEST To enable the Web service configuration, assign the role SAP_BC_WEBSERVICE_ADMIN to the user XIDEMO in client 107. To configure the Booking a Single Flight (Proxy-to-Web Service Communication) variant, you have to activate the Web service in the SAP system (see 7.4.1) Activating Web Service Apply the following additional settings in the SAP system (client 107): 1. Call transaction SOAMANAGER and choose Service Administration Single Service Configuration. 2. Search by Services and the search pattern SXIDAL_FBO_REQUEST in field Both Names, choose Go. 3. Select the Web service definition SXIDAL_FBO_REQUEST. 4. Choose Apply Selection. 5. In the tab Configurations choose Create Service. 6. As Service Name set SXIDAL_FBO_REQUESTService, as Description use Book Single Flight. In field New Binding set SXIDAL_FBO_REQUESTSoapBinding and press Apply Settings. 7. The Web service configuration of Service definition: SXIDAL_FBO_REQUEST opens. 8. In tab Provider Security select Transport Channel Authentication User ID/Password. 9. Choose Save 10. To specify the receiver communication channel for the airline, you need to know the Web service address. For this select the link Open WSDL document for selected binding in tab Overview of the service definition you just created.

82 The WSDL definition of the Web service is displayed. You have to use the WSDL URL later in the channel configuration. WSDL URL looks like: http(s)://<server>:<port>/sap/bc/srt/wsdl/srvc_<number>/wsd l11/allinone/ws_policy/document?sap-client= Store the WSDL address into a temporary storage (for example, a notepad file) for later use Configuration in Integration Directory Settings in the Model Configurator To accomplish the following configuration steps in the Integration Directory, proceed as described in detail in section To configure the process integration scenario SingleFlightBooking in the Proxy-to-Web Service Communication variant, use the settings as listed in the table below. All configuration objects for this variant are saved in the same configuration scenario as used for the Proxy-to-Proxy variant (XIDemo_SingleFlightBooking). Settings for the Process Integration Scenario SingleFlightBooking (Proxy-to-Web Service Communication) Configuration Step Selecting the Process Integration Scenario (Component View) and Creating the Scenario Settings Open the scenario XIDemo_SingleFlightBooking and call the model configurator (as described under 6.1.1). Select the component view ABAP_Proxy_2_Web_Service. Assigning Communication Components If you have not configured the Single Flight Booking process integration scenario in the Proxy-to-Proxy Communication variant before, you first have to start the model configurator and create the configuration scenario XIDemo_SingleFlightBooking before you can proceed with the next configuration steps. For a detailed description of the procedure, see under Selecting the Process integration scenario (Component View). For the Agency application component Assign the business system component <SID>_105 (entry under Business System Components) Assign the party XIDemo_Agency and component SendSingleFlightBooking (entries under Business Components for External Communication) For the Airline application component Assign the party XIDemo_UnitedAirlines and component BookSingleFlightAndConfirm (entries under Assign Business Components for B2B Communication) 82 March 2012

83 Configuring the Connection Generating the Configuration Objects For the connection between the actions Sending Single Flight Booking Order and Book Single Flight And Confirm (sender/receiver relation: <SID>_105/ XIDemo_UnitedAirlines ) you have to specify a receiver communication channel (receiver communication component BookSingleFlightAndConfirm). In this variant you specify the communication channel by creating a new channel on the basis of a communication channel template from the Enterprise Services Repository. To do this, proceed as follows: 1. In tab Connections from the Communication component Assignment choose the dropdown menu for the push button New ( ). 2. In the dropdown menu select Create Communication Channel with Template. A wizard for creating a communication channel on the basis of a communication channel template is started. 3. Choose Continue. 4. In the Select Template step, select the XIDemoChannel_WS communication channel template (software component version SAP BASIS 7.40, namespace 5. Choose Continue. 6. In the Create New Communication Channel step, confirm all entries by clicking Finish. 7. Click Close to close the Create New Communication Channel dialog box. The system creates a communication channel with the name XIDemoChannel_WS. For the connection between the actions Book Single Flight And Confirm and Process Order Confirmation (sender/receiver relation: < XIDemo_UnitedAirlines /<SID>_105) you have to specify the receiver communication channel GeneratedReceiverChannel_XI for component <SID>_105. For the connection between the actions Book Single Flight And Confirm and Process Order Confirmation (sender/receiver relation: < XIDemo_UnitedAirlines /<SID>_105) you also have to specify a sender communication channel (sender communication component BookSingleFlightAndConfirm). In this variant you specify the sender communication channel by creating a new channel on the basis of a communication channel template from the Enterprise Services Repository. To do this, proceed as described above and create the channel XIDemoChannel_WS_Sender using the Template XIDemoChannel_WS_Sender from software component version SAP BASIS 7.40, namespace Same as described under

84 Manual Editing Manual Editing To define exactly how a message is to be forwarded from the travel agency to the airline, you have to change the routing condition in the receiver determination <SID>_105 BookingOrderRequest_Out. Delete the line containing party XIDemo_UnitedAirline and communication component BookSingleFlightAndConfirm and change the receiver rule to XIDemoAirlineID_all_Book to be able to address now all airlines LH, AA and UA. For a detailed description on how to make these settings with the generation log, see To determine the outbound processing of the message, you have to specify the receiver communication channel XIDemoChannel_WS. In the channel you have to change the following settings: In the field WSDL, access URL enter the URL you have found out before (see 7.4.1). (e.g. /sap/bc/srt/wsdl/srvc_<number>/wsdl11/allinone/ws_policy/do cument?sap-client=107 In the field Authentication Method for WSDL access select Basic Authentication over HTTP, set the user XIDEMO_WS with the password you set in chapter In the Technical Transport Settings in field Target Host select the Service Information using the Input Help. The inputs in fields Service Name/Port and URL Access Path should be entered automatically when you select the Target Host. In the receiver agreement you have to configure the user authentication. Open the receiver agreement <SID>_105 XIDemo_UnitedAirlines BookSingleFlightAndConfirm FlightBookingOrderRequest_In. Under Adapter-Specifc Attributes enter user name and password. In the field User Name enter user XIDEMO_WS. In the field User Password enter the password set in chapter To determine the response processing of the message, you have to specify the sender communication channel XIDemoChannel_WS_Sender. In the channel you have to change the following settings: In the field Target Host enter the host name of the Integration Server (e.g. ld8118). In the field Service Name/Port enter the HTTP port number of the Integration Server (e.g ). In the field Target Client enter the client of the Integration Server (e.g. 001) 84 March 2012

85 Final Steps Close the generation Log. Close the model generator and choose Apply when asked for saving the changes. Save the scenario XIDemo_SingleFlightBooking. Activate the scenario XIDemo_SingleFlightBooking and all objects that it uses (follow the procedure as described in section To configure the WS consumer you need to know the Web service address of the sender agreement in the Integration Server. For this open the sender agreement XIDemo_UnitedAirlines BookSingleFlightAndConfirm FlightBookingOrderConfirmation_Out and open the WSDL using the menu Sender Agreement Display WSDL. The WSDL definition of the sender agreement is displayed. You have to use the WSDL URL later in the consumer Proxy configuration. WSDL URL looks like: http(s)://<server>:<port>/sap/bc/srt/wsdl /ifns_http177sap2com7xi7xi7demo7airline1o H7OO0/ifnm_flightbookingorderconfirmation 5outG82200O/swcv_<number>/chn_<number>/ag r_<number>/wsdl11/document/allinone/ws_po licy?sap-client=001 Store the WSDL address in a temporary storage (for example, a notepad file) for later use Activating Consumer Proxy for Asynchronous Response You must make the following additional settings in the SAP system (client 107): 1. Call transaction SOAMANAGER (SOA Manager) and choose Service Administration Single Service Configuration. 2. Search by Consumer Proxy and the search pattern FlightBookingOrderConfirmation_Out, press Go. 3. Select the Web service definition CO_SXIDAL_FBO_CONFIRM 4. Choose Apply Selection. 5. In tab Configurations, choose Create Logical Port. 6. In field Logical Port Name, enter SXIDAL_FBO_CONFIRM, as Description use Send Confirmation. 7. In URL for WSDL Access, enter the WSDL URL you got form the sender agreement, set user XIDEMO_WS with password set under and press Apply Settings. 8. The Web service Configuration of Proxy Definition: CO_SXIDAL_FBO_CONFIRM opens. 9. Under UserId and Password set XIDEMO_WS with the corresponding password. 10. Choose Save 2012

86 7.4.4 Executing and Testing There is an application in the SAP system of the Integration Server (client 105) that you can use to test the process integration scenario (for both configurations). The execution of this variant of the process integration scenario is not different from that of the Proxy-to-Proxy and Proxy-to-IDoc variant (see 5.1.3). For this variant, however, use the flights UA 0941, UA 3504, UA 9999 and N.N Configuring Process Integration Scenarios for Communication with File/FTP Adapter 8.1 Distributing Booking Order Data (Proxy-to-File System) This section describes how to configure the Distribute Booking Order Data process integration scenario in the Proxy-to-File System Communication variant. This demo example is implemented as the process integration scenario DistributeBookingOrderInformation. The process integration scenario is located in the Enterprise Services Repository, in the software component SAP BASIS, software component version SAP BASIS 7.40, in the namespace You configure two file stores as the receivers of the messages for this purpose. The received messages are stored in XML format in the one file store, and in CSV (Comma Separated Values) format in the other file store. In the Enterprise Services Repository, two component views are defined in the DistributeBookingOrderInformation process integration scenario for this purpose: Component view ABAP_Proxy_2_File_XML describes how data about flight booking orders is received in XML format. Component view ABAP_Proxy_2_File_CSV describes how data about flight booking orders is received in CSV format. Using the instructions below, configure both component views in turn. At runtime, the data about flight booking orders sent from the travel agency to the file system is written to one file in XML format and another file in CSV format simultaneously (message splitting) Business Description (Brief) A travel agency uses the asynchronous process integration scenario DistributeBookingOrderInformation to send data about flight booking orders to subscribed receivers (publish and subscribe). A possible receiver is a travel agency file system. The travel agency performs statistical evaluations of its flight booking orders using a spreadsheet program (for example, Microsoft Excel). 86 March 2012

87 8.1.2 Preliminary Steps Before you can begin configuring the process integration scenario, you must first perform the following steps for the configuration of the Distributing Booking Order Data (Proxy-to-File System) variant ( 8.1.2). Create a file directory on the Integration Server System Landscape Directory: Define a technical system for the file directory System Landscape Directory: Define a second business system for the file directory Integration Directory: Define the business system components for the file system Creating a File Directory You require a file directory on the Integration Server host where you can save the documents received. In an actual customer installation, the two file stores are probably replaced by two directories. SAP recommends that you instead only use one physical directory so you can compare the XML and CSV files with each other easier. For this purpose, create the XIDemo directory at the appropriate position in the file directory of the host. A work directory already exists on many computers that can be used for this purpose and under which you can create the XIDemo directory. 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. 2012

88 System Landscape Directory: Define a Technical System for the File Directory To define a technical system for the target directory in the System Landscape Directory, proceed as follows. 1. Log on to the System Landscape Directory (see 4.3). 2. Choose Technical Systems. 3. Choose New Technical System. 4. Select the Standalone radio button. 5. Choose Next. The file system is not an application system; therefore, select this option. 6. Enter the following: Field Technical System Identification: <SID>_FileSystem Field System Host Name: <Host Name of Integration Server> (for example, pwdf00001). You can determine the host name from the list of technical systems in the System Landscape Directory (Technical System Browser dialog). The naming convention for technical systems of type Web AS ABAP is: <SID> on <Host- Name>. To determine the host name of the Integration Server, search for the technical systems with the system ID (<SID>) of the Integration Server. 7. Choose Finish. System Landscape Directory: Define Two Business Systems for the File Directory In the Distributing Booking Order Data (Proxy-to-File System) variant ( 8.1.2), the data can be received in two ways on the database: in XML format and in Comma Separated Value (CSV) format. In the following steps you define: A business system for the file system to receive the data in XML format A business system for the file system to receive the data in CSV format 1. On the initial screen of the System Landscape Directory, choose Business Systems. 2. Choose New Business System. 3. Choose Next. 4. Select the system type Standalone with the corresponding radio button. 5. Choose Next. 6. Enter the technical system that you defined previously. In the dropdown list box for the System field, select the name of the technical system. The name of the technical system is <SID>_FileSystem on <Host Name of Integration Server>. You do not need to specify the logical system. 7. Enter the following name for the business system: <SID>_FileSystem_XML. 8. Choose Next. 88 March 2012

89 9. Specify the assigned Integration Server. Select the entry: <SID> on <Server Name>. 10. Choose Finish. 11. Following the same procedure, define a business system with the name <SID>_FileSystem_CSV. Integration Directory: Define the Business System Components for the File System To define communication components in the Integration Directory for the business systems created before, proceed as follows: In the menu in the Integration Builder, select Environment Clear SLD Data Cache. 2. Select the Objects tab page. 3. Expand the Communication Component node. 4. Position the cursor on the Business System node and choose Assign Business System in the context menu. The system calls the wizard for creating a business system component. 5. In the business system wizard, choose Continue. 6. In the Assign Partner step, choose Continue. 7. In the Select Business Systems step, select the business systems <SID>_FileSystem_XML and <SID>_FileSystem_CSV by using the check boxes. 8. Deselect the Create Communication Channels Automatically check box. 9. Choose Finish. 10. Activate the change list containing the communication components <SID>_FileSystem_XML and <SID>_FileSystem_CSV Distributing Booking Order Data (Proxy-to-File System for XML File) This section describes how to configure the process integration scenario DistributeBookingOrderInformation to receive files in XML format. Settings in the Model configurator To accomplish the following configuration steps in the Integration Directory, proceed as described in detail in section To configure the process integration scenario DistributeBookingOrderInformation in the Proxy-to-File System for XML File Communication variant, use the settings as listed in the table below. Settings for the Process Integration Scenario DistributeBookingOrderInformation (Proxy-to-File System for XML File) Configuration Step Selecting the Process Integration Scenario (Component View) and Creating the Scenario Settings In the model configurator select the process integration scenario DistributeBookingOrderInformation (software component version SAP Basis 7.40, namespace Change the predefined name of the scenario to XIDemo_DistributeBookingOrderInformation. Select the component view ABAP_Proxy_2_XML. 2012

90 19. SAP NetWeaver 7.40 Demo Examples Configuration Assigning Communication Components Configuring the Connection For the Agency application component assign the communication component <SID>_105. For the application component of the file system assign the communication component <SID>_FileSystem_XML. To configure the connection between the actions Send Booking Order Information and Receive Booking Order Information, you have to specify a receiver communication channel for the relation between sender communication component <SID>_105 (proxy) and receiver communication component <SID>_FileSystem_XML. In this variant you specify the communication channel by creating a new channel on the basis of a communication channel template from the Enterprise Services Repository. Select the communication channel template XIDemoChannel_FileXML (software component version SAP BASIS 7.40, namespace The system creates a communication channel with the name XIDemoChannel_FileXML. The detailed procedure how to create a communication channel on the basis of a communication channel template is described under Settings in the Model Configurator Configuring the Connection. Generating the Configuration Objects Manual Editing Final Steps Same as described under Define the communication channel XIDemoChannel_FileXML (see below). Close the generation log, close the model configurator and then save the scenario XI_Demo_DistributeBookingOrderInformation. Specifying the Communication Channel You specify the XIDemoChannel_FileXML communication channel, open the communication channel by navigating to the receiver agreement in the generation log of the model configurator (Connections area). In the generation log open to the receiver agreement <SID>_105 <SID>_FileSystem_XML BookingOrderDataInformation_Ext. In the Receiver Communication Channel field, click the XIDemoChannel_FileXML entry. The XIDemoChannel_FileXML communication channel is opened. Edit the communication channel. Make the following entries: Settings fort the Receiver Communication Channel Field Adapter Engine Entry Central Adapter Engine 90 March 2012

91 Target Directory Enter the directory defined in In UNIX systems, it is possible that the default relative path in the communication channel already points to your directory. However, in Windows systems you must always specify an absolute path. For a detailed description on how to accomplish these settings with the generation log, see Distributing Booking Order Data (Proxy-to-File System for CSV File) This section describes how to configure the process integration scenario DistributeBookingOrderInformation to receive files in CSV format. Settings in the Model Configurator To accomplish the following configuration steps in the Integration Directory, proceed as described in detail in section To configure the process integration scenario DistributeBookingOrderInformation in the Proxy-to-File System for CSV File Communication variant, use the settings as listed in the table below. Settings for the Process Integration Scenario DistributeBookingOrderInformation (Proxy-to-File System for CSV File) Configuration Step Selecting the Process Integration Scenario (Component View) and Creating the Scenario Assigning Communication Components Configuring the Connection Generating the Configuration Objects Manual Editing Settings Open the scenario XIDemo_DistributeBookingOrderInformation and call the model configurator (as described under 5.1.3). Select the component view ABAP_Proxy_2_File_CSV. For the Agency application component assign the communication component <SID>_105. For the application component of the file system assign the communication component <SID>_FileSystem_CSV. To configure the connection between the actions Send Booking Order Information and Receive Booking Order Information, you have to specify a receiver communication channel for the relation between sender communication component <SID>_105 (proxy) and receiver communication component <SID>_FileSystem_CSV. Proceed as described under Note that you have to select the XIDemoChannel_FileCSV communication channel template (software component version SAP BASIS 7.40, namespace Use this template to then create the XIDemoChannel_FileCSV communication channel. Same as described under During manual editing, make the same additional entries in the XIDemoChannel_FileCSV communication channel as in the XIDemoChannel_FileXML communication channel. 2012

92 Final Steps Save the scenario XIDemo_DistributeBookingOrderInformation. Activate the scenario XIDemo_DistributeBookingOrderInformation and all objects that it uses (follow the procedure as described in section 5.1.2) Executing and Testing Note that you save the configurations of both component views (ABAP_Proxy_2_File_XML and ABAP_Proxy_2_File_CSV) in scenario XIDemo_DistributeBookingOrderInformation. Do not create new change list. Instead, use the change list XIDemo_DistributeBookingOrderInformation which was created in the Distributing Booking Order Data (Proxy-to-File System for XML File) variant (8.1.3). Otherwise the model configurator will generate an error because the receiver determination that is already changed in the change list from the former variant cannot be updated. Alternatively, you can activate the change list from the Distributing Booking Order Data (Proxy-to-File System for XML File) variant first and then configure the Distributing Booking Order Data (Proxy-to-File System for CSV File) variant. There is an application in the SAP system of the Integration Server (client 105) that you can use to test the process integration scenario. For more information about how to start the application, how to check that the process integration scenario has been executed correctly and how to monitor the XI message exchange, see Executing the Process Integration Scenario and the chapter Monitoring at the end of the document. Log on to the SAP system (client 105). In the user menu, choose Process Integration Demo Examples Travel Agency: Send Booking Order Data (SXIDEMO4). You have the option of restricting the number of booking orders to be sent; available criteria are the order key, the order date, or the order status (the selection criteria are linked by a logical AND). After the process integration scenario is executed successfully, you can check the file directory (that you specified as the target directory during communication channel configuration) and display the CSV and XML files that were created. 9 Appendix 9.1 Monitoring Message Exchange can be monitored using different monitoring tools: locally in the PI Configuration and Monitoring Home, in the Runtime Workbench, in the transaction SXMB_MONI in the integration server and centrally using the Solution Manager system. 92 March 2012

93 9.1.1 Monitoring in Runtime Workbench The message exchange can be monitored in the Runtime Workbench. To start the Runtime Workbench monitoring proceed as follows: 1. Start the Monitoring by choosing Runtime Workbench on the PI start page. (transaction SXMB_IFR) 2. Choose Message Monitoring. 3. Select Integration Engine <SID> as the component and then choose Display. 4. Use appropriate filter criteria to restrict the number of XML messages displayed (for example, the processing period). 5. Choose Start. 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 Details. The tab page Message Contents displays the message contents including all message versions for the various phases of message processing Monitoring in PI Configuration and Monitoring Home The message exchange can be monitored in the local PI Monitoring Home. To start the monitoring proceed as follows: 1. Start the Monitoring by choosing Configuration and Monitoring Home on the PI start page. (transaction SXMB_IFR) 2. Choose Message Overview. 3. Select the Integration Engine as component. 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 Monitoring in Integration Server (SXMB_MONI) The messages in the integration server can not only be monitored in the PI Monitoring but as well in the SAP system of the Integration Server. To do this, proceed as follows: 1. In the Integration Server client, start Exchange Infrastructure Integration Engine: Monitoring (transaction SXMB_MONI) 2. Select Monitor for Processed XML Messages and use the appropriate search criteria to restrict the number of XML messages displayed (for example time/date) 3. Choose Start 2012

94 The system displays the selected messages in a table. For more details select the line of the message and choose Display The system displays the message in detail. To display the payload before and after the mapping step you have to activate logging in the Integration server (RUNTIME parameter LOGGING in SXMB_ADM Integration Server Configuration). IN this case, every step in the message processing will be persisted and you can check the payload for each of the steps. To compare the payload before mapping with the payload after mapping use the following procedure in the details screen of a message in transaction SXMB_MONI. 1. On the left side in the tree select Inbound Message Payloads Main Document and choose Display contents in window 1. The Inbound message payload is displayed. 2. Do the same procedure with Receiver Determination --> Payloads --> Main Document and choose Display contents in window 2. The Outbound message payload is displayed Monitoring in Solution Manager The messages can also be monitored centrally in the Solution Manager System. To do this, proceed as follows: 1. Log into the connected SAP Solution Manager System and call the Solution Manager Workcenters using transaction SOLMAN_WORKCENTER. 2. Change to Tab Technical Monitors and follow the link to PI Monitoring. 3. Select the PI Domain you want to monitor (for example B4X). 4. Launch the Message Monitor either embedded or in a new window using the button Message Monitor Monitoring in Integration Process Monitor For MultiFlightBooking, we have Integration Process. Hence additional monitoring can be done for the same via Integration Process Monitor within BPE Monitoring. To do this, 1. Open http(s)://<host>:<post>/pimon -> Monitoring -> Business Process Engine - > Integration Process Monitor. New screen titled PI Monitoring: Integration Processes opens. 2. Two tabs are available. Go to Tab List of Integration Processes. All the Integration Processes for relevant Party and Business Component will be listed in a table. List will also have details on Total Instances, Instances Started, Instances Completed, Instances with Errors and Instances Canceled for each Integration Process. 3. Search for Integration Process by filtering on Component Name MultipleFlightBookingCoordination and select relevant entry. 4. This display further detail like SWCV, Namespace, Integration Process Name, Message Statistics, Message IDs and Message Package Statistics. 5. Compare this Message ID with the Message ID for execution of this scenario. It should be the same. 6. There is Process Instance ID available for this Process which is linked to details of Process Instance Monitor. Clicking on the same open Process Instance Details as a new Tab in Integration Process UI. 7. Process Instance Details tab has further information like Step ID, Execution Duration, Basic Details (Configuration Objects Summary), History (Message Flow 94 March 2012

95 and its status), Container Information (Interface and Interface Namespace), Active Correlation Instance and Buffered Messages. 8. Now click on Tab List of Process Instances. Filter again for on Component Name MultipleFlightBookingCoordination and select relevant entry. 9. Details for each Process Instance ID are displayed in another frame below. It contains information like Status, Part, Component, Workflow Template, Receiver Message ID with Time Stamp, Sent Message ID with Time Stamp and Active Correlation Instances (if any). 10. Clicking on Process Instance ID takes again to tab Process Instance Details. 9.2 Notes on Troubleshooting To execute the demo examples correctly, both SAP NetWeaver Process Integration and the demo examples must be configured correctly. If errors occur when executing the demo examples, this is often due to a configuration error. This section describes some common problems and how to find and correct the errors. User.. is not authorized to use message type In 7.30 a new advanced authorization check for proxy applications is introduced that will not be used for the demo example proxy applications. To deactivate this check please execute the following steps: 1. Login to the client of the travel agency (client 105). 2. Call transaction SXMB_ADM Integration Engine Configuration Specific Configuration 3. Add the parameter AUTHORITY_ON_MSG_TYPE from category RUNTIME with the value Save the entry. 5. Do the same in airline clients 106 and 107. Missing Context Objects in Routing Conditions Problem: When editing the routing conditions in the receiver determinations, the context objects specified in this document are not available. Possible Cause: This problem is often due to an error in the configuration of the business systems in the System Landscape Directory. Procedure: Check in the System Landscape Directory that the technical system defined in 4.3.1and the business systems defined in contain the product SAP NetWeaver For a detailed description of the procedure, see 4.3. To make the changes visible, you must then delete the cache for SLD data in the Integration Builder - Integration Directory. To do this, choose Environment Clear SLD Data Cache. Demo Application (BSP Application) Does Not Start Problem: You cannot start the demo application (BSP application) for the travel agency. (The message HTTP Forbidden appears in the browser.) 2012

96 Possible Cause: This problem is often due to an error in the configuration of the BSP application. Procedure: Check that the ICF service (that the BSP application belongs to) is configured correctly. For more information, see section Check that the service is activated (shown black in the tree). Error Message: Proxy calls not permitted in client of Integration Server Problem: When executing one of the demo scenarios in the BSP application, you get an XI System Error with the detailed information that proxy calls are not permitted in the client of the Integration Server. Possible Cause: The demo examples must be executed in the client of the travel agency (105). The error message means either that the client 105 is configured as the Integration Server or the Web application is executed in the client of the Integration Server (001). Procedure: 1. First, check that the business system of the travel agency <SID>_105 is configured in the System Landscape Directory with the role of an application system (see section 4.3.2). 2. Check that that ICF service (that the Web application belongs to) is configured correctly. (For more information, see section ) Check in particular that the service is activated and that client 105 is entered in the logon data. 3. If another Web application (System Landscape Directory, PI Monitoring, SOA Manager) is already running in client 001, the Web application may be executed in client 001, even though the configuration is correct. In this case, we recommend the following troubleshooting steps (alternatively): Close the other Web applications and restart the demo application. Add?sap-client=105 to the URL of the demo application manually and choose Enter. (Example: http(s)://host:port/sap(bd1lbizjptawmq==)/bc/bsp/sap/sxi demo_agcy_ui/main.htm?sap-client=105) Error Message: No receiver could be determined Problem: When executing one of the demo scenarios in the BSP application, you get an XI System Error with the detailed information that no receiver could be determined. Possible Cause: The demo examples must be executed in the client of the travel agency (105). The error message means that either the scenario is not configured correctly or the application is executed in another client than 105. Procedure: 1. First, check the sender business system for the erroneous message in monitoring (SXMB_MONI, Configuration and Monitoring Home or Solution Manager). 2. If the sender business system is <SID>_105, the application is executed in the correct client. In this case, the configuration of the scenario seams to be wrong. Re-check the configuration in the Integration Directory and check that the cache refresh was executed successfully. This can be checked in the cache notification table in the directory using the menu Environment Cache Notifications. 3. If one of the business systems <SID>_106 or <SID>_107 can be seen as sender of the message, than the demo application is called in the wrong client. This may happen after you execute a browser based application (for example SOAMANAGER in client 107). In this case, we recommend the following troubleshooting steps (alternatively): Close the other Web applications and restart the demo application. Add?sap-client=105 to the URL of the demo application manually and choose Enter. (Example: 96 March 2012

97 http(s)://host:port/sap(bd1lbizjptawmq==)/bc/bsp/sap/sxi demo_agcy_ui/main.htm?sap-client=105) Error Message: No sender agreement found for, <SID>_105, XIDemo_SingaporeAirlines, ProvideFlightSeatAvailability, FlightSeatAvailabilityQuery_Out Problem: When executing the demo scenario CheckFlightSeatAvailability for Airline Singapore Airlines (SQ) in the BSP application, you get an XI System Error with the detailed information that no sender agreement could be found for the sender <SID>_105, to the receiver party XIDemo_SingaporeAirlines and service ProvideFlightSeatAvailability. Possible Cause: The demo example application checks in the cache of the agency (client 105) if a direct connection is available to party XIDemo_SingaporeAirlines and communication Component ProvideFlightSeatAvailability. If this connection is not available with exactly these names the error is displayed. This may happen if the cache refresh for this business system does not work correctly or if the names you used for party and communication component are different from the ones used in the config guide. Procedure: 1. First, in Integration Directory check if the cache refresh for business system <SID>_105 was executed successfully. In the menu Goto Environment Cache Status Overview, as Cache Instances choose <SID>_105. Check that there are no errors for this instance. (The user maintained in the business system logon data must have the necessary authorization and the communication using WS adapter must be activated see chapter 7.3.1) 2. If the cache refresh was executed successfully check the connection in the cache. In client 105 call transaction SXI_CACHE, doubleclick on Direct connection and search for the connection <SID>_105, XIDemo_SingaporeAirlines, ProvideFlightSeatAvailability. 3. The connection parameters need to have the exact names used in the config guide: To-Party: XIDemo_SingaporeAirlines To-Service: ProvideFlightSeatAvailability Make sure you have no spelling errors, also check lower and upper case letters! XML Messages Not Found on the Integration Server Problem: The demo application was executed without errors, but no corresponding XML messages are displayed in the Monitor for Processed XML Messages (transaction SXMB_MONI) on the Integration Server (client 001). Synchronous or Asynchronous Communication Possible Cause: The messages have not been sent by the sender system. Procedure: Switch to the Monitor for Processed XML Messages in the sender system (for example, SID (105) for the travel agency) and analyze the status of the message in the sender system (see also point 5 below). Synchronous Communication (Only Relevant for Scenario CheckFlightSeatAvailability) Problem: Synchronous XML messages are only stored permanently in the data base if an error occurs. If the application was executed without errors, the corresponding XML messages are not displayed in the Monitoring. This is due to the fact that Logging for Synchronous Messages is deactivated by default. Procedure: Activate logging for synchronous messages. To activate logging for synchronous messages, choose Integration Engine - Administration (transaction SXMB_ADM) Integration Engine Configuration. Choose Configuration and switch to change mode. Select the parameter LOGGING_SYNC (in category RUNTIME) and choose the value 1 (from the input help). 2012

98 XML Messages Not Sent Problem: XML messages are displayed as not sent in PI monitoring. Possible cause: This problem is often caused by the queue being blocked by a message with errors or the queue not being activated. Procedure: 1. In the Monitor for Processed XML Messages, navigate to the queue for the message (Queue ID column). If the queue contains a message with errors, you must correct or remove it (contact the owner of the message, if necessary) before the other messages can be processed. 2. Check that the queue is activated. (A common configuration error is activating queues on the Integration Server only and not in the connected business systems). TCP/IP Connection not works for the alternative variant SingleFlightBooking/MultipleFlightBooking with Java IDoc Adapter Problem 1: The Connection Test in the Transaction SM59 for the created TCP/IP connection failed with ERROR: program <SID>_XIDEMO_JIDOC not registered Possible cause: The used Program ID in the TCP/IP Connection is not equal to the Program ID in the Sender Java IDoc adapter. Procedure: Please compare the Program ID if both are equal. Problem 2: The Communication Channel in the Communication Channel Monitoring in the Configuration and Monitoring Home failed with any ERROR: Possible cause: For each manual configurated Sender Java IDoc Adapter a Resource Adapter for the connection will be created by runtime. Sometimes this Resource Adapter not starting automatically. Procedure: Open the URL: http(s)://<server>:<host>/nwa and go to Operation Management Systems Start & Stop. Open Tab Java EE Applications. Insert into the Filter Field of the Application List the Sender communication Channel XIDemoChannel_IDocAAE_Sender and press return. The status of the communication channel will be displayed. Stop the Application and Start. Note for this you need Administration rights or you have to contact your Administrator. Problem 3: Error in the IDoc Processing the Transaction SM58 Transactional RFC cause ERRORS. Possible cause: 1. The TCP/IP Connection in the airline American Airline is not enabled as an Unicode system. 2. Sometimes after deployments at the system J2EE Applications or Objects will be locked. For this you have to remove in the NWA (NetWeaver Administrator) the locks. This can only be done by the Administrator or if you have administration rights. Procedure: 1. Call TA SM59 in airline Americane Airline Client 107 and check in Tab Unicode if the radio button Unicode checked. 2. Please go to the NWA http(s)://<server>:<host>/nwa in the Search Field write locks then you directly come to the view for the locks. Pess locks and all locked Objects will be displayed. Search here for some with Transaction or JavaIdocAdapter marked them and press button Unlock. After that, go back to TA SM58 in the Client 107 and Execute the LUWs. 98 March 2012

99 Problem 4: Communication channel for the Java IDoc Receiver or Java IDoc Sender are not working and signed red in the Communication Channel monitoring. Possible cause: Internal Errors for the Communication Channel (f.e. com.sap.aii.af.idoc.exception.idocadapterexception:com.sap.aii.af.idoc.ejb.exception.idoce JBException: Java Resource Adapter xi/idoc/ra_/u2z_107/xidemochannel_idocaae_sender1 could not be started) Procedure: Check the value for the Server Name in the Communication Channel configuration in the Directory. Please insert into the field the full qualified Server name. (f.e. ldciu2z.wdf.sap.corp instead of the shortform ldciu2z. Start & Stop the channel in the Communication Channel monitoring after you are activate the relevant channel in the Directory in your configuration scenario again. When the channel again not working please check Problem