Demo Examples

PDF download from SAP Help Portal:

http://help.sap.com/saphelp_nw73ehp1/helpdata/en/48/c7a31cda5e31ebe10000000a42189b/content.htm

Created on May 25, 2015

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note

This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP SE 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. SAP and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC Page 1 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Table of content
1 Demo Examples
1.1 Purposes and Concepts
1.2 Business Overview
1.3 Technical Overview
1.4 General Configuration Steps
1.5 Checking Flight Availability
1.5.1 Business Description (CheckFlightSeatAvailability)
1.5.2 Checking Flight Seat Availability (Proxy-to-Proxy)
1.5.2.1 Concepts
1.5.2.2 Configuring a Process Integration Scenario
1.5.2.3 Executing a Process Integration Scenario
1.5.2.3.1 Monitoring Messages
1.5.3 Checking Flight Seat Availability (Proxy-to-RFC)
1.5.3.1 Concepts
1.5.3.2 Configuring a Process Integration Scenario
1.5.3.3 Executing a Process Integration Scenario
1.5.4 Checking Flight Seat Availability (Proxy-to-Web Service)
1.5.4.1 Concepts
1.5.4.2 Configuring a Process Integration Scenario
1.5.4.3 Executing a Process Integration Scenario
1.5.5 Checking Flight Seat Availability (Web Service-to-Web-Service Direct Communication)
1.5.5.1 Concepts
1.5.5.2 Configuring a Process Integration Scenario
1.5.5.3 Executing a Process Integration Scenario
1.6 Booking a Single Flight
1.6.1 Business Description (SingleFlightBooking)
1.6.2 Booking a Single Flight (Proxy-to-Proxy)
1.6.2.1 Concepts
1.6.2.2 Configuring a Process Integration Scenario
1.6.2.3 Executing a Process Integration Scenario
1.6.3 Booking a Single Flight (Proxy-to-IDoc)
1.6.3.1 Concepts
1.6.3.2 Configuring a Process Integration Scenario
1.6.3.3 Executing a Process Integration Scenario
1.6.4 Booking a Single Flight (Proxy-to-IDoc AAE Communication)
1.6.4.1 Concepts
1.6.4.2 Configuring a Process Integration Scenario
1.6.5 Booking a Single Flight (Proxy-to-Web-Service Communication)
1.6.5.1 Concepts
1.6.5.2 Configuring a Process Integration Scenario
1.7 Booking Connecting Flights
1.7.1 Business Description (MultipleFlightBooking)
1.7.2 Booking Connecting Flights (Proxy-to-Proxy(IDoc)
1.7.2.1 Concepts
1.7.2.2 Configuring a Process Integration Scenario
1.7.2.3 Executing a Process Integration Scenario
1.7.3 Booking Connecting Flights (Proxy-to-Proxy/IDoc AAE Communication)
1.7.3.1 Concepts
1.7.3.2 Configuring a Process Integration Scenario
1.8 Distributing Booking Order Data
1.8.1 Business Description (DistributeBookingOrderInformation)
1.8.2 Distributing Booking Order Data (Proxy-to-File System)
1.8.2.1 Concepts
1.8.2.2 Configuring a Process Integration Scenario
1.8.2.3 Executing a Process Integration Scenario

PUBLIC Page 2 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1 Demo Examples

Use
The demo examples demonstrate the basic communication scenarios of Process Integration (PI) and guide you step-by-step through the technical concepts and
tools.
You use the demo examples to do the following:
Learn the technical concepts of Process Integration
The basic concepts are addressed in the simple demo examples.
Test the underlying functions of Process Integration.
Using the demo examples you can simply check whether SAP NetWeaver was correctly configured for the usage type Process Integration and if it is
operational.

Caution
The demo examples are designed to be used as teaching and test examples for SAP NetWeaver Process Integration. They are not intended for
productive operation.

Recommendation
The demo examples are very useful if you want to learn about the concepts of Process Integration and how they fit together all in just one example.

Features
The features of the demo examples include several complete Process Integration scenarios and comprise the following parts:
Design objects in the Enterprise Services Repository
The design objects are defined and shipped by SAP.
Configuration objects in the Integration Directory
You must create the configuration objects yourself. SAP provides comprehensive recommendations to help you.
Example Applications
SAP has implemented example applications for the communication parties involved. These example applications also contain user interfaces. You use
these to execute the demo examples.
Configuration guide
Detailed configuration instructions for the standard configuration recommended by SAP are available for the demo examples. These describe all the steps
required to configure the demo examples in detail. A basic knowledge of Process Integration is sufficient to be able to make the relevant configuration
settings.
More information: General Configuration Steps
Documentation
Besides the detailed configuration instructions, additional documentation is also available. This also describes how to use the individual demo examples and
explains the technical concepts addressed.
Documentation Structure
The documentation consists of a general cross-process-integration-scenario section and separate sections for the individual process integration scenarios.
The general cross-scenario section contains the following information:
Purposes and Concepts
Contains an overview of the ways that you can use the demo examples and the concepts that they impart. For each concept there is a reference to a demo
scenario that enables you to illustrate the concept.
Business Overview
A description of the business application case of the demo examples.
Technical Overview
An overview of the demo examples from a technical perspective. It contains information on the objects that are shipped with the demo examples and how to
use them.
General Configuration Steps
An overview of the most important cross-scenario configuration steps with references to the detailed descriptions in the configuration guide for the demo
examples.
In the scenario-specific sections you will find the following information for each process integration scenario.
A short business description of Process Integration scenario
The configuration variants of the Process Integration scenario (referred to simply as "variants") that are currently supported
The sections on the variants contain the following:
A description of the concepts addressed by the Process Integration scenario
A short overview of the configuration process flow
Information about the execution of the Process Integration scenario (in the respective variant)
The application case for the demo examples is the communication between a travel agency and airlines with regard to flight bookings. At the moment four Process
Integration scenarios are available. The table below lists the Process Integration scenarios and their variants:

Process Integration Scenarios Variants Note

Checking flight seat availability ( ABAP proxy runtime to ABAP proxy runtime Synchronous Communication
CheckFlightSeatAvailability ) ABAP proxy runtime to RFC runtime
ABAP Proxy Runtime to Web-Service
Web Service to Web Service (Direct Connection)

Booking a single flight ( SingleFlightBooking ) ABAP proxy runtime to ABAP proxy runtime Asynchronous Communication
ABAP proxy runtime to IDoc runtime using the IDoc (IE)

PUBLIC Page 3 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 adapter
ABAP proxy to IDoc runtime using the IDoc (AAE) adapter
ABAP proxy to Web service

Booking connecting flights ( MultipleFlightBooking ) ABAP proxy runtime to ABAP proxy/IDoc runtime using Asynchronous communication with an executable
the IDoc (IE) adapter integration process
ABAP proxy runtime to ABAP proxy/IDoc runtime using
the IDoc (AAE) adapter

Distributing booking order data ( ABAP Proxy Runtime to File System Asynchronous communication with a file system as
DistributeBookingOrderInformation ) receiver

1.1 Purposes and Concepts

Use
For a quick introduction to the demo examples, this section contains the following:
A list of the basic purposes of the demo examples and the relevant parts
A list of the most important concepts of Process Integration and the example process integration scenarios and variants that illustrate these concepts
Purpose
The following table provides an overview of the basic purposes of the demo examples and the relevant parts.

Area of Use Relevant Part of the Demo Examples

Understanding the basic structure of design objects (objects of the Enterprise The design objects required for the demo examples are defined by SAP and shipped.
Services Repository ) These objects are located in the Enterprise Services Repository in the software
Understanding the relationship between different object types in the Enterprise component SAP BASIS , software component version SAP BASIS 7.30 in the
Services Repository namespaces http://sap.com/xi/XI/Demo/Agency and http://sap.com/xi/XI/Demo/Airline
Using example solutions for object design in the Enterprise Services Repository .
Working with the Enterprise Services Builder (user interface of the Enterprise
Services Repository)

Understanding and using the basic steps for setting up the system landscape You make the configuration settings yourself in your system landscape. A detailed
Learning how to configure process integration content in the Integration Directory configuration guide is available for this purpose (see: General Configuration Steps ).
Understanding and making adapter configuration settings using examples
Working with the Integration Builder (user interface of the Integration Directory)

Executing process integration scenarios The shipment contains the user interfaces for executing process integration scenarios.
Monitoring the processing of XML messages at runtime
Testing the basic functions and installation of SAP NetWeaver Process Integration

See also:
For more information, see Technical Overview .
Concepts
The following table summarizes the important concepts that you can illustrate by using the demo examples. Each concept is implemented in a process integration
scenario.

Concept Implemented in Process Integration Scenario/Variant

Using process integration scenarios - general All process integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)

Process integration scenario with a synchronous connection Checking Flight Seat Availability (Proxy-to-Proxy)

Process integration scenario with an asynchronous connection Booking a Single Flight (Proxy-to-Proxy)

Process integration scenario with an executable integration process Booking Connecting Flights (Proxy-to-Proxy)

Process integration scenario with an application component of type Template Distributing Booking Order Data (Proxy-to-File System)

Process integration scenario with multiple component views Checking Flight Availability

Using an executable integration process Booking Connecting Flights (Proxy-to-Proxy)

Concept Implemented in Process Integration Scenario/Variant

Synchronous service interfaces Checking Flight Seat Availability (Proxy-to-Proxy)

Asynchronous service interfaces Booking a Single Flight (Proxy-to-Proxy)

Abstract service interfaces for an executable integration process Booking Connecting Flights (Proxy-to-Proxy)

Abstract service interface for an external business partner Distributing Booking Order Data (Proxy-to-File System)

Message types All process integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)

Fault message types in synchronous service interfaces Checking Flight Seat Availability (Proxy-to-Proxy)

Fault message types in asynchronous service interfaces Booking a Single Flight (Proxy-to-Proxy)

Data types All process integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)

External definitions Distributing Booking Order Data (Proxy-to-File System)

Context objects Booking a Single Flight (Proxy-to-Proxy)

Imported objects: RFCs Checking Flight Seat Availability (Proxy-to-RFC)

PUBLIC Page 4 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Imported objects: IDocs Booking a Single Flight (Proxy-to-IDoc)

Concept Implemented in Process Integration Scenario/Variant

Operation mappings in synchronous communication Checking Flight Seat Availability (Proxy-to-RFC)

Booking Connecting Flights (Proxy-to-Proxy)

Operation mappings in asynchronous communication Booking a Single Flight (Proxy-to-Proxy)

Operation mappings used by the integration process Booking Connecting Flights (Proxy-to-Proxy)

Message mapping Booking a Single Flight (Proxy-to-Proxy)

Multi-mappings Booking Connecting Flights (Proxy-to-Proxy)

Message mapping for mapping data structures with multiple hierarchy levels to a data Distributing Booking Order Data (Proxy-to-File System)
structure with one hierarchy level

Hierarchy levels to a data structure with one hierarchy level

Message mapping with a user-defined function

Message mapping with fixed-value mapping

Concept Implemented in Process Integration Scenario/Variant

Communication channel templates for a file system Distributing Booking Order Data (Proxy-to-File System)

Concept Implemented in Process Integration Scenario/Variant

Synchronous outbound proxy and synchronous inbound proxy (ABAP) Checking Flight Seat Availability (Proxy-to-Proxy)

Asynchronous outbound proxy and asynchronous inbound proxy (ABAP) Booking a Single Flight (Proxy-to-Proxy)

Defining a Web service based on a service interface Checking Flight Seat Availability (Proxy-to-Web Service)

Concept Implemented in Process Integration Scenario/Variant

Using configuration scenarios All process integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)

Configuration with process integration scenario as template (model configurator) All process integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)

Business system component for an SAP system All process integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)

Business system service for a file system Distributing Booking Order Data (Proxy-to-File System)

Integration process component Booking Connecting Flights (Proxy-to-Proxy)

Receiver determination All process integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)

Routing condition with context object Booking a Single Flight (Proxy-to-Proxy)

Interface determination All process integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)

Receiver agreement All process integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)

Receiver communication channel for adapter type XI Booking a Single Flight (Proxy-to-Proxy)
Distributing Booking Order Data (Proxy-to-File System)

Receiver communication channel for adapter type RFC Checking Flight Seat Availability (Proxy-to-RFC)

Receiver communication channel for adapter type IDoc Booking a Single Flight (Proxy-to-IDoc)

Receiver communication channel for adapter type File Distributing Booking Order Data (Proxy-to-File System)

Receiver communication channel for adapter type WS Checking Flight Seat Availability (Proxy-to-Web Service)

Concept Implemented in Process Integration Scenario/Variant

Sending messages All process integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)

Messages with multiple receivers Distributing Booking Order Data (Proxy-to-File System)

Monitoring message exchange All process integration scenarios, for example Booking a Single Flight (Proxy-to-Proxy)

Executing an integration process Booking Connecting Flights (Proxy-to-Proxy)

Communication using proxy runtime Booking a Single Flight (Proxy-to-Proxy)

Communication based on the adapter runtime (RFC adapter) Checking Flight Seat Availability (Proxy-to-RFC)

Communication based on the adapter runtime (IDoc adapter (IE)) Booking a Single Flight (Proxy-to-IDoc)

Communication based on the adapter runtime (IDoc adapter (AAE)) Booking a Single Flight (Proxy-to-IDoc AAE Communication)
Booking Connecting Flights (Proxy-to-Proxy/IDoc AAE Communicatio

Communication based on the adapter runtime (file/FTP adapter) Distributing Booking Order Data (Proxy-to-File System)

Communication based on the Web service runtime (WS adapter) Checking Flight Seat Availability (Proxy-to-Web Service)

Direct communication of Web service provider and Web service consumer Checking Flight Seat Availability (Web Service-to-Web-Service Direct Communication

1.2 Business Overview

Use
This section gives a brief description of the business application case for the demo examples. Note that the business application case is only for demonstration

PUBLIC Page 5 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 purposes and that the focus of the demo examples is to explain the technical concepts of Process Integration.
The demo examples use the following communication parties:
A travel agency that sells flight tickets for various airlines
Several airlines that sell their flight tickets through the travel agency
The communication between the travel agency and the airlines is electronic and uses Process Integration.
The demo examples currently consist of the following process integration scenarios:
Checking seat availability for a flight
Booking a single flight
Booking a flight with a connecting flight
Distributing booking order data
The demo examples are implemented by SAP and are included in the shipment.

Caution
The example applications are designed as teaching examples and are not intended for productive operation.

Notes on Selecting Demo Examples

The following conflict arises when selecting the business application case for the demo examples.
Real business processes often require specific application knowledge and usually require extensive changes to system settings. Therefore, their suitability
for educational purposes is somewhat limited.
Simplified everyday processes are better suited for educational purposes since they are easier to understand and require little prior preparation. The
disadvantage, however, is that they are not realistic in all aspects.
Since the educational aspect is the main concern in the demo examples, the application case Booking a Flight is chosen.
Booking a flight is something that most people have personal experience of, and is easy to explain. Moreover, the flight data model has been used successfully in
many SAP technology courses and is therefore fairly well-known.
The disadvantage of this application case is that not all of the details correspond with the use of the usage type Process Integration in reality.
SAP demo examples are based on the assumption that a travel agency books directly with various airlines. In reality, bookings are made using a central
booking system.
In reality, flight bookings are time-critical and are not executed asynchronously.
The communication between travel agencies and airlines is a typical application case for business-to-business integration (B2B). The demo examples (to
date) only describe the application-to-application integration (A2A) case.
The demo examples are intended as simple examples to explain the technical concepts. They should be considered as such and do not correspond to reality in
every detail.

Note
The communication models used in the demo examples are, however, a realistic representation of real business scenarios. A cross-component material
booking does include a synchronous material availability query and an asynchronous material booking with asynchronous confirmation.

1.3 Technical Overview

Use
This section describes the demo examples shipped by SAP from a technical perspective. It focuses on explaining the technical concepts of Process Integration
in the context of the demo examples.
Example Applications for Travel Agency and Airline
The demo examples comprise two example applications: A travel agency application and an airline application. Both applications are available in every SAP
system that is based on SAP NetWeaver 2007.

Note
Applications that use Process Integration to communicate are usually part of different products and run on different SAP systems.
From a logical perspective, the travel agency and airline applications can therefore be considered as separate applications. However, from a technical
perspective, both applications are shipped together. This makes it possible to access and use the demo examples on all SAP systems.
To emphasize the separation from the logical perspective, the respective program objects have been created as independently from one another as possible
and belong to different packages in the SAP system.

The travel agency application has a user interface (as a Business Server Page application), which you use to execute the demo examples.
The airline application has a user interface, which you use to access current data in the flight database tables.

Caution
The example applications are designed as teaching examples and are not intended for productive operation.

Design Objects in the Enterprise Services Repository

The design objects that are required to integrate the travel agency and airline applications are defined by SAP and are part of the shipment. Examples of such
objects are process integration scenarios, an integration process, service interfaces, messages, and data types, as well as operation and message mappings.
These objects are located in the Enterprise Services Repository in the software component SAP BASIS , software component version SAP BASIS 7.30 in the
namespaces http://sap.com/xi/XI/Demo/Agency and http://sap.com/xi/XI/Demo/Airline .

PUBLIC Page 6 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Note
The Enterprise Services Repository reflects the logical separation of the travel agency application and the airline application described above. All the design
objects that belong to the travel agency application are in the namespace http://sap.com/xi/XI/Demo/Agency , and those that belong to the airline application
are in the namespace http://sap.com/xi/XI/Demo/Airline .
Cross-component design objects (such as process integration scenarios, integration processes, and mapping objects) cannot always be assigned uniquely to
one of the communication parties. The demo examples are based on the assumption that the airline application provides certain services, which only form a
complete process integration scenario together with the travel agency application. Therefore, all cross-system design objects are defined in the travel agency
namespace.

The available design objects form the basis for executing the demo examples. The design objects also illustrate the following:
How the content of the Enterprise Services Repository is structured
How the various object types in the Enterprise Services Repository are structured and used
The interdependencies between the design objects in the Enterprise Services Repository

Caution
The design objects in the demo examples are designed as teaching examples and are not intended for productive operation.

Configuration Objects in the Integration Directory

The configuration objects required to integrate the travel agency and airline applications are not shipped by SAP and you must define them yourself in the
Integration Directory.
Some of the settings (business system services and communication channels) are cross-process-integration-scenario settings.
For information about the standard SAP configuration, see the detailed instructions for the configuration steps for the demo examples, which are provided in a
separate document (see General Configuration Steps ).
You must configure the demo examples in the Integration Directory before you can execute them. The design objects also illustrate the following:
How the design objects in the Enterprise Services Repository are related to the configuration objects in the Integration Directory
How content is structured in the Integration Directory
How the various configuration object types in the Integration Repository are structured and used
The dependencies between the configuration objects in the Integration Directory
How message processing is controlled by the configuration objects at runtime
Runtime
You can use the runtime of Process Integration to execute the demo examples for test purposes. This enables you to do the following:
Use a simple example to check whether you have configured the usage type Process Integration correctly and whether it is functioning correctly
Use monitoring to monitor messages at runtime and track the steps that are processed

1.4 General Configuration Steps

Use
You must make certain settings before you can execute the demo examples. There are general cross-scenario settings and scenario-specific settings.
This section gives you an overview of all the general cross-scenario settings.

Note
For a detailed introduction to the configuration of the demo examples, see the document SAP Enhancement Package 1 for SAP NetWeaver PI 7.3 - Demo
Examples Configuration available in SAP Developer Network (SDN) at http://scn.sap.com/docs/DOC-27364 .

There is an overview of the scenario-specific settings for the individual process integration scenarios in the description of the process integration scenarios. For a
detailed description of the scenario-specific settings, see the above guide.

Note
It is assumed that the installation and technical configuration of SAP NetWeaver Process Integration has been completed correctly.

Defining a System Landscape - SAP Standard Configuration

To use the demo examples, you need application systems for the travel agency and the airlines. These must be SAP systems based on SAP NetWeaver 7.3.
SAP has provided a standard configuration for the demo examples. This comprises the following application systems:
An application system for the travel agency (called TravelAgency ) that uses the proxy runtime for communication
An application system for the airline Lufthansa (called Airline_LH ) that also uses the proxy runtime for communication
An application system for the airline American Airlines (called Airline_AA ) that either uses the proxy runtime or, if required, the RFC and IDoc runtime
for communication
An application systems for the airlines United Airlines (called Airline_UA ) and Singapore Airlines (called Airline_SQ ) that serve as external partner
and that make Web services available for communication
Technically speaking, these application systems can be different SAP systems, but it is simpler to use several clients of one SAP system.

Caution
We recommend that you use the SAP standard configuration. Since the demo examples are only intended to demonstrate Process Integration and are not
scenarios for productive use, SAP only provides support for the standard configuration.

Note

PUBLIC Page 7 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 The detailed setting instructions in the configuration instructions for the demo examples assume that you are using the standard configuration.

In addition, you need an SAP system with SAP NetWeaver installed. This system contains the Integration Server and the Integration Builder.
The application systems TravelAgency , Airline_LH , Airline_AA , Airline_UA and Airline_SQ communicate using the Integration Server. This is illustrated
in the following graphic:

Figure 1: System Landscape for the Demo Examples

Connecting Application Systems to the Integration Server

To connect the application systems (for the travel agency and the airlines) to the central Integration Server and enable them to communicate, you must make all
the relevant settings. This includes the following settings:
Configuring the local Integration Engines in the application systems
Defining the involved application systems as technical systems and business systems in the System Landscape Directory
Defining the three business systems as business system services in the Integration Directory. You must also generate and define the corresponding
communication channels.
For more detailed information, see the general SAP XI configuration guide.
Application-Specific Settings
You must also make the following settings (specific to the flight booking example) in the application systems.
The demo examples require appropriate data in the flight data tables. You must generate this data in all the involved application systems.
A Business Server Page is available for the travel agency functions. You must activate this in the travel agency system.
For more detailed information (for the SAP standard configuration), see the configuration guide for the demo examples.

1.5 Checking Flight Availability

Use
A travel agency uses the process integration scenario CheckFlightSeatAvailability to check the seat availability for a flight with an airline.
This addresses various technical concepts, depending on the configuration of the process integration scenario. The following variants are supported for this
process integration scenario:
Checking Flight Seat Availability (Proxy-to-Proxy)
The most important characteristics of this variant are: synchronous message exchange, does not use mappings, uses proxy runtime.
Checking Flight Seat Availability (Proxy-to-RFC)
The most important characteristics of this variant are: synchronous message exchange, uses mappings, uses the RFC adapter.
Checking Flight Seat Availability (Proxy-to-Web Service)
The most important characteristics of this variant are: communication using the Web service runtime based on the Web services reliable messaging (WS-
RM) standard.
Checking Flight Seat Availability (Web Service-to-Web-Service Direct Communication)
The most important characteristics of this variant are: direct communication of a Web service consumer and a Web service provider.
For more information about the business uses of the process integration scenario, see Business Description (CheckFlightSeatAvailability) .
For more information about the concepts, configuration, and execution of the process integration scenario, see the descriptions of the variants.

1.5.1 Business Description (CheckFlightSeatAvailability)

Use
PUBLIC Page 8 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Use
A travel agency uses the process integration scenario CheckFlightSeatAvailability to check the seat availability for 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.

Process
The process integration scenario comprises an asynchronous communication step between the travel agency and the airline:
1. The travel agency sends the airline a request for an availability check for a flight. The request contains all the information required to uniquely identify a flight
(airline ID, flight number, flight date). The airline receives the request, executes the availability check, and sends a response to the travel agency. The
response contains the maximum number of seats and the number of available seats in the three flight classes (economy, business, and first class). If the
flight does not exist, the airline sends a fault message to the travel agency.

1.5.2 Checking Flight Seat Availability (Proxy-to-Proxy)

Use
The most important characteristics of this variant of the process integration scenario CheckFlightSeatAvailability are: synchronous message exchange, does not
use mappings, uses proxy runtime.

Note
Using the proxy runtime enables communication to take place by means of generated proxies. Note that this is the main difference between this and the other
variants of the process integration scenario in which communication takes place using the adapter runtime (see Flight Availability Check (with RFC) ).

This section contains the following information:

Concepts
An overview of the technical concepts that are addressed in this process integration scenario.
Configuring a Process Integration Scenario
An overview of the most important configuration steps with references to the detailed descriptions in the configuration instructions for the demo examples.
You have to configure the process integration scenario before you can execute it.
Executing a Process Integration Scenario
Information on how to execute the process integration scenario and how to check the results in the involved systems and in monitoring.

1.8.2.1 Concepts

Use
This section gives an overview of the technical concepts that are addressed in this process integration scenario.
The table below contains the following information for each concept:
A hyperlink to the general description of the concept
A description of how the concept is implemented in the process integration scenario
The process integration scenario is in the ES Repository under the name CheckFlightSeatAvailability (in the software component version SAP Basis 7.30 ,
namespace http://sap.com/xi/XI/Demo/Agency ). Navigate forward to find all the objects used by the process integration scenario (interface objects).
The corresponding proxies for the message interfaces used are in the SAP system in ABAP proxy generation under the software component version SAP Basis
7.30 . For the travel agency, the outbound interface is FlightSeatAvailabilityQuery_Out in the namespace http://sap.com/xi/XI/Demo/Agency . For the airline,
the inbound interface is FlightSeatAvailabilityQuery_In in the namespace http://sap.com/xi/XI/Demo/Airline .
Design Time

Concept Description

Process integration scenario with an asynchronous connection The process integration scenario comprises an asynchronous communication step
between the travel agency and the airline.

Synchronous service interfaces The process integration scenario uses a separate synchronous service interface for the
sender and receiver. Each service interface contains a message type for each request and
response. The structure of the exchanged messages is described by the referenced data
types.

Context object The outbound interface (on the travel agency side) uses the context object AirlineID to
address the field of the same name in the message. You use the context object to
formulate airline-dependent routing conditions.

Fault message type The fault message type FlightNotFound is used to handle the error situation Flight not
found .

Communication without mapping and with different XML namespaces for message The message types used by the travel agency are structurally identical to the message
types types of the same name of the airline. Furthermore, the message types of the travel
agency use the XML namespace of the airline, that is, messages are sent or expected in
the namespace of the airline at runtime. This means that the messages used by the
travel agency are identical to those messages used by the airline. Therefore, mapping is
not necessary.

Synchronous outbound proxy and synchronous inbound proxy There is an executable client proxy in the SAP system (ABAP object class) for the
outbound service interface of the travel agency.

PUBLIC Page 9 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 There is an executable server proxy in the SAP system (ABAP object interface with an
implementing ABAP object class) for the inbound service interface of the airline.

Configuration Time
All descriptions for configuration time are based on the SAP standard configuration.

Concept Description

Using configuration scenarios in the Integration Directory All configuration data for the process integration scenario is grouped into a configuration
scenario in the Integration Directory.

Model configurator The process integration scenario CheckFlightSeatAvailability is used as a template for
configuration. You use the model configurator to enter the required configuration data
from the process integration scenario step-by-step. The model configurator generates all
the relevant configuration objects (receiver determinations, interface determinations,
collaboration agreements).

Communication component A communication component of the type Business System Service is defined in the
Integration Directory for each of the three involved application systems (travel agency
system, airline system for Lufthansa, airline system for American Airlines). This
enables you to address the application systems as the sender of receiver of messages.

Receiver determination , routing condition with context object A receiver determination defines the receiver for the flight availability check request sent
by the travel agency. To ensure that the request is sent to the correct airline system
(Lufthansa or American Airlines), the routing condition is airline-dependent (context
object AirlineID ).

Interface determination Two interface determinations define the inbound interface for the flight availability check
request sent by the travel agency in each of the two airline systems (Lufthansa and
American Airlines). An operation mapping is not assigned.

Receiver agreement and communication channels Receiver agreements are defined in the standard configuration for:
The travel agency (sender) and the airline Lufthansa (receiver)
The travel agency (sender) and the airline American Airlines (receiver)
Each receiver agreement defines the technical details for outbound processing of
the message by means of its assigned communication channel.
Since both receivers (Lufthansa and American Airlines) expect the XI message
format, both receiver agreements are assigned a communication channel with the
adapter type XI .
The sender (travel agency) sends the message in XI message format. Therefore,
a sender agreement to specify inbound processing in more detail is not necessary.

Runtime

Concept Description

Communication using proxy runtime The SAP systems of the travel agency and the airlines are based (in the standard
configuration) on Application Server ABAP. Therefore, you can use ABAP proxies to
connect them to the Integration Server.

Synchronous communication The travel agency and airline communicate with each other synchronously. Once the
request message has been sent (flight availability check request), a response message is
expected from the receiver (airline). Once the request message has been sent, no further
messages can be sent until the response to the request has arrived back at the sender
(travel agency).

Error during synchronous communication If the application error Flight not found occurs at the receiver (airline), it sends a fault
message to the sender (travel agency).

Monitoring messages You use monitoring to display and analyze the messages (for the various processing
More information: Administrative Tasks phases).

1.8.2.2 Configuring a Process Integration Scenario

Use
You must configure the scenario before you can execute it.
This section contains an overview of the necessary configuration steps.
For detailed instructions of how to configure this process integration scenario (for the SAP standard configuration), see the separate configuration guide(see General
Configuration Steps ).

Prerequisites
Before you configure this process integration scenario, you must execute general configuration steps (for example, set up the System Landscape Directory,
generate the appropriate flight data). For details, see General Configuration Steps .

Process
Configuration Steps
You can use the model configurator for the whole configuration procedure. Note the following:

PUBLIC Page 10 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Select the process integration scenario CheckFlightSeatAvailability (component view ABAP_Proxy_2_ABAP_Proxy ) from the ES Repository.
Assign communication components: Assign the corresponding business system components for the travel agency and the two airlines to the application
components of the process integration scenario.
Select a communication channel with the adapter type XI for all connections.
Use the model configurator to generate receiver determinations, interface determinations, and receiver agreements.
Define the corresponding conditions for the receiver determination so that messages are forwarded to the correct airline. Use the context object AirlineID .
Once you have finished, do not forget to activate all change lists containing changes that you made during configuration.

1.8.2.3 Executing a Process Integration Scenario

Use
This section contains information on how to do the following:
Execute the process integration scenario
Check the flight data in the airline system
Check and analyze the messages processed by the Integration Server

Process
Executing the Flight Availability Check
Perform the following actions in the SAP system of the travel agency:
1. In the SAP NetWeaver Process Integration user menu, choose Demo Examples Travel Agency: Execute Demo Examples .
2. Log on to the Business Server Pages (BSP) application, if necessary. Use your user and password for the travel agency system.
3. On the initial screen of the BSP application, choose Check Flight Seat Availability .
Note that the BSP application is only available in English and is always displayed in English, regardless of the logon language.
4. Choose Start .
5. Select the flight for which you want to check the seat availability.
To keep the example simple, only a few flights are available in the SAP standard configuration: flight numbers 0400 and 0401 for Lufthansa, and flight
numbers 0017 and 0064 for American Airlines.
The SAP standard configuration ensures that all flights are available on the first of each month. Therefore, the default setting for the flight date is the first day
of next month. We recommend that you select this flight date.

Note
The dialog also displays some non-existent flights. This makes it possible to trigger error situations. If you select the flight Lufthansa 9999 or
American Airlines 9999 , this triggers the application error that the flight does not exist. If, however, you select the flight N.N. 9999 , this triggers
the system error that the receiver is unknown.

6. Choose Check Availability .

7. The system displays a dialog containing the results of the availability check.
If the availability check was successful, the system displays the maximum number of seats and the number of available seats in the three flight
classes (economy, business, and first class).
If the availability check was not successful, the system displays information on the cause of the error.
Checking the Flight Availability Data in the Airline System
To check that the process integration scenario has been executed correctly, check the flight availability data in the airline system.
Perform the following actions in the SAP system of the respective airline:
1. In the SAP Exchange Infrastructure user menu, choose Demo Examples Airline: Display Flight Data .
2. In the Functions frame, choose Display Availability Data .
3. Choose Execute .
4. Enter the selection criteria for displaying the availability data on the Data Browser screen.
The following fields are suitable for selection criteria: the field CARRID for the airline ID (for example, LH for Lufthansa and AA for American Airlines), the
field CONNID for the flight number (for example, 0400 ), the field FLDATE for the flight date (for example, 01.07.2004 ).
5. The system displays a table containing detailed information about all selected flights.
The availability data is displayed in the following fields: the economy class data is displayed in SEATSMAX_E and SEATSOCC_E , the business class
data in SEATSMAX_B and SEATSOCC_B , and the first class data in SEATSMAX_F and SEATSOCC_F . SEATSMAX_* describes the
maximum number of seats and SEATSOCC_* the number of seats already booked to date.

Caution
Note that the system displays the number of booked seats here, but when you execute the process integration scenario, the system displays the
number of available seats.

Monitoring Messages
You use the monitoring transaction to display the messages that were processed by the Integration Server during execution of the process integration scenario.
You can use the payload of the message to check directly what business data was exchanged during execution of the process integration scenario.
See Monitoring Messages .

1.5.2.3.1 Monitoring Messages

Procedure
Perform the following actions in the Runtime Workbench:

PUBLIC Page 11 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1. To call the Runtime Workbench to monitor the exchanged messages, choose Process Integration Start Integration Builder in the user menu.
You reach the start page of SAP NetWeaver Process Integration.
2. Under Integration Monitoring , choose Runtime Workbench .
The system displays the Runtime Workbench start page.
3. Choose Message Monitoring and select the component that you want to use, in this case the Integration Server.
The component name of the Integration Server begins with IS (normally the first component in the selection list).
4. Choose Display and use suitable filter criteria to limit the number of XML messages to be displayed.

Recommendation
The processing time is a suitable filter criterion (from ... to ...). We also recommend that you restrict the namespace of the sender interface to the value
http://sap.com/xi/XI/Demo* .

5. Choose Use Filter .

The system displays the selected messages in a table. The Status column displays the status of the message.
6. To display the content of a message, select the message in the table and choose Details .
This takes you to a detailed display of the message display tools, which displays the content of the message including all existing message versions for the
various phases of message processing.
The navigation tree displays various information for each message version in a subtree. For example, under Payloads MainDocument
(application/xml) you find the die business application data and under SOAP Header Main the technical information, such as sender and
receiver. To display the information, double click the entry. The system displays the information in the active window.

Note
The monitoring transaction in the SAP system of the Integration Server provides an alternative to message monitoring. To call the monitoring transaction,
choose Process Integration Monitoring Integration Engine: Monitoring in the user menu. Choose Monitor for Processed XML Messages and then
Execute . As in the Runtime Workbench, you have the option of limiting the number of messages to be displayed by using suitable filter criteria and
displaying the content of selected messages.
End-to-end monitoring enables you to track the entire path of the message during its processing.

Caution
You must configure this function separately (see the Demo Examples Configuration Guide ).
1. In the Runtime Workbench, choose End-to-End Monitoring .
The system displays the instance view of this message and highlights the involved components.
2. If you only want to display the involved components, select the Only Display Involved Components checkbox.

1.5.3 Checking Flight Seat Availability (Proxy-to-RFC)

Use
The most important characteristics of this variant of the process integration scenario CheckFlightSeatAvailability are: synchronous message exchange, uses
mappings, uses the RFC adapter.

Note
Using the RFC adapter enables communication between the Integration Server and an SAP system by using an RFC interface. Note that this is the main
difference to the other two process integration scenario variants.

This section contains the following information:

Concepts
An overview of the technical concepts that are addressed in this process integration scenario.
Configuring a Process Integration Scenario
An overview of the most important configuration steps with references to the detailed descriptions in the configuration instructions for the demo examples.
You have to configure the process integration scenario before you can execute it.
Executing a Process Integration Scenario
Information on how to execute the process integration scenario and how to check the results in the involved systems and in monitoring.

1.8.2.1 Concepts

Use
This variant is technically an enhancement of the variant Checking Flight Seat Availability (Proxy-to-Proxy) .
The variant Checking Flight Seat Availability (Proxy-to-RFC) addresses most of the technical concepts that are addressed in the variant Checking Flight Seat
Availability (Proxy-to-Proxy) . See Concepts .
This variant also addresses additional concepts. This section gives you an overview of the additional technical concepts.
The table below contains the following information for each concept:
A hyperlink to the general description of the concept
A description of how the concept is implemented in the process integration scenario
The process integration scenario is in the ES Repository under the name CheckFlightSeatAvailability (in the software component version SAP Basis 7.30 ,
namespace http://sap.com/xi/XI/Demo/Agency ). Navigate forward to find all the objects used by the process integration scenario (interface objects, mapping
objects).

PUBLIC Page 12 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 The airline that is integrated into the process by the RFC adapter uses RFCs to exchange messages.
The corresponding proxy for the service interface used by the travel agency is in the SAP system in ABAP proxy generation under the software component
version SAP Basis 7.30 : the outbound interface FlightSeatAvailabilityQuery_Out in namespace http://sap.com/xi/XI/Demo/Agency .
Design Time

Concept Description

Process integration scenario with multiple component views Multiple component views are defined for the process integration scenario
CheckFlightSeatAvailability . The component view ABAP_Proxy_2_RFC contains
the definition of the connection that is based on the message exchange between the
service interface and the RFC interface.

Imported RFC interfaces The RFC interface used is implemented in the SAP system. The description of the RFC
interface is imported to the ES Repository and is located in the software component
version SAP Basis 6.40 under Imported Objects . This means that the RFC interface
is also available in the ES Repository and can be referenced by other design objects (for
example, mapping objects).

Message mapping with RFC The operation mapping used in the process integration scenario maps the service
interface to the RFC interface and the other way around. The operation mapping contains
three message mappings, which map the request message, response message, and
fault message to the RFC.

Configuration Time

Concept Description

Receiver agreement and communication channels Receiver agreements are defined in the standard configuration for:
The travel agency (sender) and the airline Lufthansa (receiver)
The travel agency (sender) and the airline American Airlines (receiver)
Each receiver agreement defines the technical details for outbound processing of
the message by means of its assigned communication channel.
Since the receiver airline American Airlines expects the RFC format, the
corresponding receiver agreement is assigned a communication channel with the
adapter type RFC .

Runtime

Concept Description

Communication based on the adapter runtime ( RFC adapter ) The SAP systems of the travel agency and an airline are based (in the standard
configuration) on SAP NetWeaver 2007 (AS ABAP). Therefore, you can use ABAP
proxies to connect them to the Integration Server.
You connect the system of the other airline to the Integration Server by using RFCs. In
the SAP standard configuration this system is also based on SAP NetWeaver 2007 (AS
ABAP).

1.8.2.2 Configuring a Process Integration Scenario

Use
You must configure the scenario before you can execute it.
This section contains an overview of the necessary configuration steps.
For detailed instructions of how to configure this process integration scenario (for the SAP standard configuration), see the separate configuration guide(see General
Configuration Steps ).

Prerequisites
Before you configure this process integration scenario, you must execute general configuration steps (for example, set up the System Landscape Directory,
generate the appropriate flight data). For details, see General Configuration Steps .
Configuration Steps
You can use the model configurator for the whole configuration procedure. Note the following:
Select the process integration scenario CheckFlightSeatAvailability (component view ABAP_Proxy_2_RFC ) from the ES Repository.
Assign communication components: Assign the corresponding business system components of the travel agency and the airline that is to work with the
RFC runtime to the application components of the process integration scenario.
Select communication channels with the following adapter types:
Adapter type XI for connections between the travel agency and the receiver.
Adapter type RFC for connections between the airlines and the receiver.
Use the model configurator to generate receiver determinations, interface determinations, and receiver agreements.
If you have configured an airline system for the proxy runtime and now want to use it for the RFC runtime, you must adapt the corresponding interface
determination manually or delete it manually before generation.
Define the corresponding conditions for the receiver determination so that messages are forwarded to the correct airline. Use the context object AirlineID .
Once you have finished, do not forget to activate all change lists containing changes that you made during configuration.
You must also configure the RFC adapter and make all the necessary settings for RFC communication in the SAP system of the airline.

1.8.2.3 Executing a Process Integration Scenario

PUBLIC Page 13 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1.8.2.3 Executing a Process Integration Scenario

Use
The execution of this variant of the process integration scenario is no different from that of the variant described under Checking Flight Seat Availability (Proxy-to-
Proxy) .
See Executing a Process Integration Scenario .

Note
In message monitoring you also have the option of comparing the message before (message format) and after (RFC format) the mapping step.

1.5.4 Checking Flight Seat Availability (Proxy-to-Web Service)

Use
The most important characteristics of this variant of the process integration scenario CheckFlightSeatAvailability are: communication using the Web service
runtime based on the Web services reliable messaging (WS-RM) standard.
This section contains the following information:
Concepts
An overview of the technical concepts that are addressed in this process integration scenario.
Configuring a Process Integration Scenario
An overview of the most important configuration steps with references to the detailed descriptions in the configuration instructions for the demo examples.
You have to configure the process integration scenario before you can execute it.
Executing a Process Integration Scenario
Information on how to execute the process integration scenario and how to check the results in the involved systems and in monitoring.

1.8.2.1 Concepts

Use
This variant is technically an enhancement of the variant Checking Flight Seat Availability (Proxy-to-Proxy) .
The variant Checking Flight Seat Availability (Proxy-to-Web Service) addresses most of the technical concepts that are addressed in the variant Checking Flight
Seat Availability (with Proxy). See Concepts .
This variant also addresses additional concepts. This section gives you an overview of these additional technical concepts.
The table below contains the following information for each concept:
A hyperlink to the general description of the concept
A description of how the concept is implemented in the process integration scenario
The process integration scenario is in the ES Repository under the name CheckFlightSeatAvailability (in the software component version SAP Basis 7.30 ,
namespace http://sap.com/xi/XI/Demo/Agency ). Navigate forward to find all the objects used by the process integration scenario (interface objects, mapping
objects).
The airline provides a Web service for exchanging messages. You can find the Web service definition in the SAP system. Call transaction Object Navigator (
SE80 ) and select the package SAI_DEMO_AIRLINE . You find the Web service definition under Enterprise Services Service Provider. The name of the
Web service is SXIDAL_FLIGHTSEATAVAIL_CHECK .

Note
The Web service is a development object that is included in the shipment.

Design Time

Concept Description

Process integration scenario with multiple component views Multiple component views are defined for the process integration scenario
CheckFlightSeatAvailability . The component view ABAP_Proxy_2_Web_Service
contains the definition of the connection that is based on the message exchange between
the service interface and the Web service.

Process integration scenario with an application component of type Template for The airline providing the Web service has been defined as an External Partner .
communication with an external partner This is represented in the component view by the symbol for the application component
Airline .
The Airline application component is of type Template because messages are
exchanged using a Web service for which you do not necessarily know the technical
details. Of course, the actual realization in the demo example is known. However, this is
not necessarily the case for a travel agency and an airline in a real-life scenario.

Web service definition The Web service definition contained in the SAP system is based on the inbound service
interface FlightSeatAvailabilityQuery_In (software component version SAP Basis
7.30 , namespace http://sap.com/xi/XI/Demo/Airline ).

Configuration Time

PUBLIC Page 14 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Concept Description

Communication component with party In the SAP standard configuration, the Web service for determining flight seat availability
is implemented as the business component of a party.

Receiver agreement and Since the airline expects a Web service call, the receiver agreement is assigned a
Communication Channels communication channel with the adapter type WS .

Activating a Web service The Web service is implemented and shipped by SAP, but you must activate it in the
More information: SOA Manager SAP system. To do this, use the SOA Manager.

Runtime

Concept Description

Communication on the basis of Web service runtime ( Communication Channel with The airline implements the flight availability check as a Web service that is connected
Adapter Type WS ) with the Integration Server using a communication channel with adapter type WS.

1.8.2.2 Configuring a Process Integration Scenario

Use
You must configure the scenario before you can execute it.
This section contains an overview of the necessary configuration steps.
For detailed instructions of how to configure this integration scenario (for the SAP standard configuration), see the separate configuration guide(see General
Configuration Steps ).

Prerequisites
Before you configure this process integration scenario, you must execute general configuration steps (for example, set up the System Landscape Directory,
generate the appropriate flight data). For details, see General Configuration Steps .
Configuration Steps
You must activate the Web service SXIDAL_FLIGHTSEATAVAIL_CHECK (short description: XI Demo: Check Flight Availability ) before you begin
configuration in the Integration Directory. To do this, call transaction SOA Manager ( SOAMANAGER ) in the SAP system of the airline that provides the Web
service.
You can use the model configurator for the whole configuration procedure. Note the following:
Select the process integration scenario CheckFlightSeatAvailability (component view ABAP_Proxy_2_Web_Service ) from the ES Repository.
Assign communication components: Assign the corresponding business system components of the travel agency and the business component of the
airline that provides the Web service to the application components of the process integration scenario.
Create a communication channel with adapter type WS for the airline that receives the flight availability query and specify the necessary attributes. Create
the communication channel based on the communication channel template XIDemoChannel_WS from the ES Repository (software component version
SAP BASIS 7.10 , namespace http://sap.com/xi/XI/Demo/Agency ).
Use the model configurator to generate receiver determinations, interface determinations, and receiver agreements.
Define the corresponding conditions for the receiver determination so that messages are forwarded to the correct airline. Use the context object AirlineID .
Once you have finished, do not forget to activate all change lists containing changes that you made during configuration.

1.8.2.3 Executing a Process Integration Scenario

Use
The execution of this variant of the process integration scenario is no different from that of the variant described under Checking Flight Seat Availability (Proxy-to-
Proxy) .
For more information, see: Executing a Process Integration Scenario

1.5.5 Checking Flight Seat Availability (Web Service-to-Web-

Service Direct Communication)

Use
The most important characteristics of this variant of the process integration scenario CheckFlightSeatAvailability are: Communication using the Web service
runtime based on the Web services reliable messaging (WS-RM) standard. In this variant, Web service provider and consumer communicate directly with each
other without any Integration Server or Advanced Adapter Engine involved.
This section contains the following information:
Concepts
An overview of the technical concepts that are addressed in this process integration scenario.
Configuring a Process Integration Scenario
An overview of the most important configuration steps with references to the detailed descriptions in the configuration instructions for the demo examples.
You have to configure the process integration scenario before you can execute it.
Executing a Process Integration Scenario
Information on how to execute the process integration scenario and how to check the results in the involved systems and in monitoring.

PUBLIC Page 15 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1.8.2.1 Concepts

Use
This variant is technically an enhancement of the variant Checking Flight Seat Availability (Proxy-to-Proxy) .
The variant Checking Flight Seat Availability (Proxy-to-Web Service Direct Communication) addresses concepts related to the direct communication between a
Web service provider and a Web service consumer.
The table below contains the following information for each concept:
A hyperlink to the general description of the concept
A description of how the concept is implemented in the process integration scenario
Configuration Time

Concept Description

Direct connection You can configure direct communication between a Web service consumer and a Web
More information: Configuring Direct Communication service provider in the Integration Directory using the direct connection configuration
object.

WS cache notifications for business systems Configuration settings for direct communication that are maintained centrally in
More information: Configuring Business Systems (with Web Service Communication) Integration Directory, are propagated into the involved business systems based on cache
under 4. Facilitating Distribution of Configuration Data in the Back-End System notifications.

Runtime

Concept Description

Communication on the basis of Web service runtime The airline implements the flight availability check as a Web service that is connected
More information: Configuring the Communication Channel with Adapter Type WS with the Web service consumer (agency) using a communication channel with adapter
type WS.

1.8.2.2 Configuring a Process Integration Scenario

Use
You must configure the scenario before you can execute it.
This section contains an overview of the necessary configuration steps. For detailed instructions of how to configure this integration scenario (for the SAP standard
configuration), see the separate configuration guide.
More information: General Configuration Steps

Prerequisites
Before you configure this process integration scenario, you must execute general configuration steps (for example, set up the System Landscape Directory,
generate the appropriate flight data).
More information: General Configuration Steps

Procedure
This is an overview of the configuration steps:
Activating the Web service SXIDAL_FLIGHTSEATAVAIL_CHECK
More information: Configuring a Process Integration Scenario ( Checking Flight Seat Availability (Proxy-to-Web Service) variant)
Activating the WS cache notification for the agency
To activate the automatic configuration transfer from the Integration Directory to the involved back-end system (agency client) you have to switch on the Web
service configuration using the WS adapter and set user and password for the cache notification in the business system in the Integration Directory.
Assigning communication components and configuring connection: proceed as described for the ( Checking Flight Seat Availability (Proxy-to-Web Service)
variant).
However, when configuring the connection, set the flag for Direct Connection.
Use the model configurator to generate the direct connection.
Manually edit the receiver communication channel (type WS) as described in detail in the configuration guide.

1.8.2.3 Executing a Process Integration Scenario

Procedure
The execution of this variant of the process integration scenario is no different from the Checking Flight Seat Availability (Proxy-to-Proxy) variant.
More information: Executing a Process Integration Scenario

Note
Note that no messages can be monitored for this kind of communication (direct communication).

PUBLIC Page 16 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1.6 Booking a Single Flight

Use
A travel agency uses the 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.
This addresses various technical concepts, depending on the configuration of the process integration scenario. The following variants are supported for this
process integration scenario:
Booking a Single Flight (Proxy-to-Proxy)
The most important characteristics of this variant are: asynchronous message exchange, uses mappings, uses proxy runtime.
Booking a Single Flight (Proxy-to-IDoc)
The most important characteristics of this variant are: asynchronous message exchange, uses mappings, uses proxy runtime and the IDoc adapter (IE).
Booking a Single Flight (Proxy-to-IDoc AAE Communication)
The most important characteristics of this variant are: asynchronous message exchange, uses mappings, uses proxy runtime and the IDoc adapter (AAE).
Booking a Single Flight (Proxy-to-Web-Service Communication)
The most important characteristics of this variant are: communication with a Web service provider using the WS communication channel.
For more information about the business uses of the process integration scenario, see Business Description (SingleFlightBooking) .
For more information about the concepts, configuration, and execution of the process integration scenario, see the descriptions of the variants.

1.6.1 Business Description (SingleFlightBooking)

Use
A travel agency uses the 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.

Process
The process integration scenario comprises two asynchronous communication steps between the travel agency and the airline:
1. The travel agency sends an order for a flight booking to an airline.
The order contains:
Travel agency ID, booking order number, and flight class for the flight to be booked
Information required to uniquely identify the flight (airline ID, flight number, flight date)
Information about the passenger for whom the flight is to be booked (first name, surname, date of birth)
2. The airline receives the flight booking order and executes the flight booking. The airline sends a booking confirmation to the travel agency.
The booking confirmation contains:
Flight booking number of the airline and the airline ID
Travel agency ID, booking order number
Booking status (specifies whether the booking was successful or failed)
If the airline cannot send a response for the flight booking due to technical reasons, an error is triggered in the airline application.
3. The travel agency receives the booking confirmation and updates the booking status in its system.
If the travel agency cannot process the booking confirmation, an error is triggered in the travel agency application.
From a technical perspective, the travel agency always communicates using the ABAP proxy runtime. However, the airline has two communication options:
Communication using the ABAP proxy runtime (compare with the component view ABAP_Proxy_2_ABAP_Proxy in the process integration scenario
SingleFlightBooking )
Communication using the IDoc runtime (compare with the component view ABAP_Proxy_2_IDoc in the process integration scenario SingleFlightBooking
)

1.6.2 Booking a Single Flight (Proxy-to-Proxy)

Use
The most important characteristics of this variant of the process integration scenario SingleFlightBooking are: asynchronous message exchange, uses mappings,
uses proxy runtime.

Process
This section contains the following information:
Concepts
An overview of the technical concepts that are addressed in this process integration scenario.
Configuring a Process Integration Scenario
An overview of the most important configuration steps with references to the detailed descriptions in the configuration instructions for the demo examples.
You have to configure the process integration scenario before you can execute it.
Executing a Process Integration Scenario
Information on how to execute the process integration scenario and how to check the results in the involved systems and in monitoring.

1.8.2.1 Concepts

PUBLIC Page 17 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Use
This section gives an overview of the technical concepts that are addressed in this process integration scenario.
The table below contains the following information for each concept:
A hyperlink to the general description of the concept
A description of how the concept is implemented in the process integration scenario
The process integration scenario is in the ES Repository under the name SingleFlightBooking (in the software component version SAP Basis 7.30 ,
namespace http://sap.com/xi/XI/Demo/Agency ). Navigate forward to find all the objects used by the process integration scenario (interface objects, mapping
objects).
The corresponding proxies for the message interfaces used are in the SAP system in ABAP proxy generation under the software component version SAP Basis
7.30 . For the travel agency, the outbound interface is BookingOrderRequest_Out and the inbound interface is BookingOrderConfirmation_In in the namespace
http://sap.com/xi/XI/Demo/Agency . For the airline, the inbound interface is FlightBookingOrderRequest_In and the outbound interface is
FlightBookingOrderConfirmation_Out in the namespace http://sap.com/xi/XI/Demo/Airline .
Design time

Concept Description

Process Integration Scenario with Two Asynchronous Connections The process integration scenario comprises two asynchronous communication steps
between the travel agency and the airline.

Asynchronous Service Interfaces The process integration scenario uses asynchronous service interfaces for the sender
and receiver.
Each asynchronous outbound interface contains a message type for each output
message. Each asynchronous inbound interface contains a message type for each input
message. The structure of the exchanged messages is described by the referenced data
types.

Context Object The outbound interface (on the travel agency side) uses the context object
AirlineID to address the field of the same name in the message. You use the
context object to formulate airline-dependent routing conditions.
The outbound interface (on the airline side) uses the context object OrderType to
address the field of the same name in the message. You use the context object to
formulate routing conditions dependent on the booking order type.

Fault Message Type Fault message types are used to react to errors during processing. The airline uses the
fault message type ResponseNotPossible and the travel agency uses the fault
message types BookingOrderUpdateNotPossible and
TechnicalProblemsWhileProcessing .

Operation Mapping The process integration scenario uses operation mappings:

To map the travel agency booking order to an airline booking order (operation
mapping BookingOrder_Agency2Airline )
For example, the fields for the first name and last name of the passenger are
merged into a single string.
To map an airline flight booking confirmation to a travel agency flight booking
confirmation (operation mapping FBOConfirmation_Airline2Agency )

Asynchronous Outbound Proxy and Synchronous Inbound Proxy There are executable client proxies in the SAP system (ABAP object classes) for the
outbound service interfaces.
There are executable server proxies in the SAP system (ABAP object interfaces with
implementing ABAP object classes) for the inbound service interfaces.

Configuration Time
All descriptions for configuration time are based on the SAP standard configuration.

Concept Description

Using configuration scenarios in the Integration Directory All configuration data for the process integration scenario is grouped into a configuration
scenario in the Integration Directory.

Model configurator The process integration scenario SingleFlightBooking is used as a template for
configuration. The model configurator guides you through the whole integration scenario
configuration step-by-step. It calculates and generates all the relevant configuration
objects (receiver determinations, interface determinations, collaboration agreements)
automatically.

Communication Component A communication component of the type Business System Service is defined in the
Integration Directory for each of the three involved application systems (travel agency
system, airline system for Lufthansa, airline system for American Airlines). This
enables you to address the application systems as the sender/receiver of messages.

Receiver determination , routing condition with context object A receiver determination defines the receiver for the booking order sent by the
travel agency. To ensure that the booking order is sent to the correct airline
(Lufthansa or American Airlines), the routing condition is airline-dependent
(context object AirlineID ).
There is a receiver determination for each airline system (Lufthansa and
American Airlines), which specifies that the booking confirmation is sent to the
travel agency.

Interface Determination Two interface determinations define the inbound interface for the booking order
sent by the travel agency in each of the two airline systems (Lufthansa and
American Airlines) and the operation mapping used.

PUBLIC Page 18 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Two interface determinations define the inbound interface and the operation
mapping used for the booking confirmation sent by one of the airlines (Lufthansa
or American Airlines) to the travel agency.

Receiver agreement and communication channels Receiver agreements for all existing sender/receiver pairs are defined in the standard
configuration.
Each receiver agreement defines the technical details for outbound processing of the
message by means of its assigned communication channel.
Since all receivers expect the XI message format, all receiver agreements are assigned a
communication channel with the adapter type XI .
All senders send the message in XI message format. Therefore, sender agreements to
specify inbound processing in more detail are not necessary.

Runtime

Concept Description

Communication Using Proxy Runtime The SAP systems of the travel agency and the airlines are based (in the standard
configuration) on SAP Web AS 7.10. Therefore, you can use ABAP proxies to connect
them to the Integration Server.

Asynchronous Communication Both communication steps between the travel agency and the airlines are asynchronous.

Error during asynchronous communication Errors are triggered in error situations. The corresponding fault messages are not sent
back to the sender, but are saved in the system of the application where the error
occurred. To analyze errors, use monitoring.

Monitoring messages You use monitoring to display and analyze the messages (for the various processing
More information: Administrative Tasks phases).

1.8.2.2 Configuring a Process Integration Scenario

Use
You must configure the scenario before you can execute it.
This section contains an overview of the necessary configuration steps.
For detailed instructions of how to configure this process integration scenario (for the SAP standard configuration), see the separate configuration guide(see General
Configuration Steps ).

Prerequisites
Before you configure this process integration scenario, you must execute general configuration steps (for example, set up the System Landscape Directory,
generate the appropriate flight data). For details, see General Configuration Steps .

Process
Configuration Steps
You can use the model configurator for the whole configuration procedure. Note the following:
Select the process integration scenario SingleFlightBooking (component view ABAP_Proxy_2_ABAP_Proxy ) from the ES Repository.
Assign communication components: Assign the corresponding business system components for the travel agency and the two airlines to the application
components of the process integration scenario.
Select a communication channel with the adapter type XI for all connections.
Use the model configurator to generate receiver determinations, interface determinations, and receiver agreements.
Define corresponding conditions for the receiver determination:
The messages from the travel agency must be sent to the correct airline. Use the context object AirlineID .
As long as you do not want to use the process integration scenario MultipleFlightBooking , you do not have to define any conditions for the messages
from the airline.
If you want to use the process integration scenario MultipleFlightBooking , you must define conditions for the messages from the airline. In the
condition OrderType = Single the travel agency is the receiver. Use the context object OrderType .

Once you have finished, do not forget to activate all change lists containing changes that you made during configuration.

1.8.2.3 Executing a Process Integration Scenario

Use
This section contains information on how to do the following:
Execute the process integration scenario
Check the booking data in the airline system
Check and analyze the messages processed by the Integration Server

Features
Executing the Flight Booking

PUBLIC Page 19 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Perform the following actions in the SAP system of the travel agency:
1. In the user menu, choose Process Integration Demo Examples Travel Agency: Execute Demo Examples .
2. Log on to the Business Server Pages (BSP) application, if necessary. Use your user and password for the travel agency system.
Note that the BSP application is only available in English and is always displayed in English, regardless of the logon language.
3. On the initial screen of the BSP application, choose Book Single Flight .
4. Choose Start .
5. Select the flight for which you want to make a booking.
To keep the example simple, only a few flights are available in the SAP standard configuration: flight numbers 0400 and 0401 for Lufthansa, and flight
numbers 0017 and 0064 for American Airlines.
The SAP standard configuration ensures that all flights are available on the first of each month. Therefore, the default setting for the flight date is the first day
of next month. We recommend that you select this flight date.

Note
The dialog also displays some non-existent flights. This makes it possible to trigger error situations. If you select the flights Lufthansa 9999 or
American Airlines 9999 , the booking fails.
If, however, you select the flight N.N. 9999 , this triggers the system error that the receiver is unknown.

6. Select a flight class.

Use the radio buttons. There are three available flight classes: economy, business, and first class.
7. Enter the passenger data.
8. Choose Create Booking Order .
9. The system displays the following information in a dialog:
Booking order information
The system displays the booking order number ( Order Number ), the flight class ( Flight Class ), the date of the booking order ( Order Date ),
and the booking status ( Order Status ). The system generates the booking order number automatically for each new booking order.

Note
Make a note of the booking number, in case you want to check the booking status again later.

Note
Read the notes on the booking status below.

Passenger information
Flight information
The booking number ( Booking Number ) is a number assigned by the airline when a booking is successful. This field is filled if booking is
successful, otherwise it remains empty.
10. Once you have sent the booking order, the system usually displays a yellow traffic light as the booking status. To update the information and check whether
the airline has sent a response in the meantime, choose Refresh .
Notes on the Booking Status
The system expresses the booking status with a traffic light symbol and a text.
For flight bookings, the booking status has the following meaning:
The airline has booked the flight (green light)
The airline was unable to book the flight (red light)
The flight booking order was sent but the airline has not yet sent a response. (yellow light).
For the XI demo example, the booking status has the following meaning:
A green or red light means that the process integration scenario was successful, since both communication steps were completed successfully.
If the system still displays a yellow light after a considerable length of time, then an error may have occurred in the communication. For more
information, use monitoring to analyze the communication.
Checking the Booking Status
You can also check the status of a booking order at a later point in time.
Perform the following actions in the SAP system of the travel agency:
1. In the user menu, choose SAP Exchange Infrastructure Demo Examples Travel Agency: Execute Demo Examples .
2. Log on to the Business Server Pages (BSP) application, if necessary. Use your user and password for the travel agency system.
3. On the initial screen of the BSP application, choose Query Booking Status .
4. Enter the booking order number in the Order Number field.
5. Choose Query Status .
The system displays the following information about the flight booking:
Booking date, flight class, and booking status
For example, Order Status displays whether the booking was executed successfully.
Data on the passenger for whom the flight booking was requested
Data on the flight for which the flight booking was requested
Checking the Flight Bookings in the Airline System
To check that the process integration scenario has been executed correctly, check the booking data in the airline system.
Perform the following actions in the SAP system of the respective airline:
1. In the user menu, choose SAP Exchange Infrastructure Demo Examples Airline: Display Flight Data .
2. In the Functions frame, select the Display Booking Data radio button.
3. Select Execute ( ).
4. Enter the selection criteria for displaying the booking data on the Data Browser screen.
The following fields are suitable for selection criteria: the field CARRID for the airline ID (for example, LH for Lufthansa and AA for American Airlines), the
field CONNID for the flight number (for example, 0400 ), the field FLDATE for the flight date (for example, 01.07.2004 ), the field ORDER_DATE for
the booking date. SAP recommends that you enter today's date for the booking date.
The system displays a table containing detailed information about all flight bookings. This includes the following:
Data on the flight for which the flight booking was requested

PUBLIC Page 20 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Data on the passenger for whom the flight booking was requested
Booking data (booking number, booking date)
Monitoring Messages
You use the monitoring transaction to display the messages that were processed by the Integration Server during execution of the process integration scenario.
You can use the payload of the message to check directly what business data was exchanged during execution of the process integration scenario.
See Monitoring Messages .

1.6.3 Booking a Single Flight (Proxy-to-IDoc)

Use
The most important characteristics of this variant of the process integration scenario SingleFlightBooking are: asynchronous message exchange, uses mappings,
uses proxy runtime and the IDoc adapter.

Note
Using IDoc adapters enables communication based on the adapter runtime. Note that this is a significant difference compared with the process integration
scenario variant described under Booking a Single Flight (Proxy-to-Proxy) . There, communication is based on the proxy runtime.

This section contains the following information:

Concepts
An overview of the technical concepts that are addressed in this process integration scenario.
Configuring a Process Integration Scenario
An overview of the most important configuration steps with references to the detailed descriptions in the configuration instructions for the demo examples.
You have to configure the process integration scenario before you can execute it.
Executing a Process Integration Scenario
Information on how to execute the process integration scenario and how to check the results in the involved systems and in monitoring.

1.8.2.1 Concepts

Use
This variant is technically an enhancement of the variant Single Flight Booking (Proxy-to-Proxy) .
The variant Single Flight Booking (with IDoc) addresses most of the technical concepts that are addressed in the variant Single Flight Booking (with Proxy) .
See Concepts .
This variant also addresses additional concepts. This section gives you an overview of the additional technical concepts.
The table below contains the following information for each concept:
A hyperlink to the general description of the concept
A description of how the concept is implemented in the process integration scenario
The process integration scenario is in the ES Repository under the name SingleFlightBooking (in the software component version SAP Basis 7.30 ,
namespace http://sap.com/xi/XI/Demo/Agency ). Navigate forward to find all the objects used by the process integration scenario (interface objects, mapping
objects).
The airline that is integrated into the process by the IDoc adapter uses IDocs to exchange messages.
The corresponding proxies for the message interfaces used are in the SAP system in ABAP proxy generation under the software component version SAP Basis
7.30 . For the travel agency, the outbound interface is BookingOrderRequest_Out and the inbound interface is BookingOrderConfirmation_In in the namespace
http://sap.com/xi/XI/Demo/Agency .
Design time

Concept Description

Process Integration Scenario with Multiple Component Views Multiple component views are defined for the process integration scenario
SingleFlightBooking . The component view ABAP_Proxy_2_IDoc contains the
definitions of the connections that are based on the message exchange between service
interfaces and IDoc interfaces.

Imported IDoc Interface The IDoc interfaces used are implemented in the SAP system. Descriptions of the IDoc
interfaces are imported to the Enterprise Services Repository and are located in the
software component version SAP Basis 7.30 under Imported Objects . This means
that the IDoc interfaces are also available in the Enterprise Services Repository and can
be referenced by other design objects (for example, mapping objects).

Message mapping with IDocs The mappings used in the process integration scenario map service interfaces to IDoc
interfaces and the other way around.
The IDoc adapter automatically fills the IDoc header. Therefore, it is not necessary to
supply the IDoc header during mapping.

Configuration Time
All descriptions for configuration time are based on the SAP standard configuration.

Concept Description

Using configuration scenarios in the Integration Directory All configuration data for the process integration scenario is grouped into a configuration
scenario in the Integration Directory.
You can execute the whole configuration step-by-step by using the model configurator.

PUBLIC Page 21 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Use the process integration scenario SingleFlightBooking as a template.

Configuration objects with an IDoc interface in the key The receiver determination and the interface determination use IDoc interfaces in the
key.

Receiver agreement and communication channels Receiver agreements for all existing sender/receiver pairs are defined in the standard
configuration.
Each receiver agreement defines the technical details for outbound processing of the
message by means of its assigned communication channel.
Since a receiver expects the IDoc format, the corresponding receiver agreements are
assigned a communication channel with the adapter type IDoc .
Therefore, a sender agreement to specify inbound processing in more detail is not
necessary for senders that send messages in IDoc format.

Runtime

Concept Description

Communication based on the adapter runtime (IDoc adapter) The SAP systems of the travel agency and an airline are based (in the standard
configuration) on AS ABAP. Therefore, you can use ABAP proxies to connect them to the
Integration Server.
You connect the system of the other airline to the Integration Server by using IDocs. In
the SAP standard configuration this system is also based on AS ABAP.

IDoc monitoring with the IDoc adapter The IDoc adapter provides additional message monitoring options.

1.8.2.2 Configuring a Process Integration Scenario

Use
You must configure the scenario before you can execute it.
This section contains an overview of the necessary configuration steps.
For detailed instructions of how to configure this process integration scenario (for the SAP standard configuration), see the separate configuration guide(see General
Configuration Steps ).

Prerequisites
Before you configure this process integration scenario, you must execute general configuration steps (for example, set up the System Landscape Directory,
generate the appropriate flight data). For details, see General Configuration Steps .
Configuration Steps
You can use the model configurator for the whole configuration procedure. Note the following:
Select the process integration scenario SingleFlightBooking (component view ABAP_Proxy_2_IDoc ) from the ES Repository.
Assign communication components: Assign the corresponding business system components of the travel agency and the airline that is to work with the
IDoc runtime to the application components of the process integration scenario.
Select communication channels with the following adapter types:
Adapter type XI for connections between the travel agency and the receiver.
Adapter type IDoc for connections between the airlines and the receiver.
Use the model configurator to generate receiver determinations, interface determinations, and receiver agreements.
If you have configured an airline system for the proxy runtime and now want to use it for the IDoc runtime, you must adapt the corresponding interface
determination manually or delete it manually before generation.
Define corresponding conditions for the receiver determination:
The messages from the travel agency must be sent to the correct airline. Use the context object AirlineID .
As long as you do not want to use the process integration scenario MultipleFlightBooking , you do not have to define any conditions for the messages
from the airline.
If you want to use the process integration scenario MultipleFlightBooking , you must define conditions for the messages from the airline. In the
condition OrderType = Single the travel agency is the receiver. Use the context object OrderType .

Once you have finished, do not forget to activate all change lists containing changes that you made during configuration.
You must also configure the IDoc adapter and make all the necessary settings for IDoc communication in the SAP system of the airline.

1.8.2.3 Executing a Process Integration Scenario

Use
The execution of this variant of the process integration scenario is no different from that of the variant described under Booking Single Flights (Proxy-to-Proxy) .
See Executing a Process Integration Scenario .
The IDoc adapter provides an additional message monitoring option. For more details, see Displaying XML Messages .

1.6.4 Booking a Single Flight (Proxy-to-IDoc AAE

Communication)

Use
PUBLIC Page 22 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Use
The most important characteristics of this variant of the process integration scenario SingleFlightBooking are: asynchronous message exchange, uses mappings,
uses proxy runtime and the IDoc adapter (Advanced Adapter Engine).
Ther IDoc adapter (Advanced Adapter Engine) - also referred to as IDoc adapter (AAE) for short - is part of the Advanced Adapter Engine and allows the setup of
scenarios based on IDoc exchange, even in cases when the Integration Engine is not involved in message processing.

Note
This is in particular important when you use the installation option Advanced Adapter Engine Extended (AEX).

This section contains the following information:

Concepts
An overview of the technical concepts that are addressed in this process integration scenario.
Configuring a Process Integration Scenario
An overview of the most important configuration steps with references to the detailed descriptions in the configuration instructions for the demo examples.
You have to configure the process integration scenario before you can execute it.

1.8.2.1 Concepts

Use
This variant is technically an enhancement of the variant Single Flight Booking (Proxy-to-Proxy). The variant Single Flight Booking (with IDoc (AAE)) addresses
most of the technical concepts that are addressed in the variants Single Flight Booking (with Proxy) and Booking a Single Flight (Proxy-to-IDoc) (using the
"classic" IDoc adapter (IE) that runs on the Integration Engine).
More information:
Concepts (proxy variant)
Concepts (IDoc (Integration Engine) variant)
As one exception to the variants mentioned above, this variant also addresses the IDoc adapter (AAE) as additional concept.
More information: Configuring the IDoc Adapter (Advanced Adapter Engine)
The process integration scenario is in the ES Repository under the name SingleFlightBooking (in the software component version SAP Basis 7.30 ,
namespace http://sap.com/xi/XI/Demo/Agency ). Navigate forward to find all the objects used by the process integration scenario (interface objects, mapping
objects).
The airline that is integrated into the process by the IDoc adapter (AAE) uses IDocs to exchange messages.

1.8.2.2 Configuring a Process Integration Scenario

Procedure
You must configure the scenario before you can execute it.
For detailed instructions of how to configure this process integration scenario (for the SAP standard configuration), see the separate configuration guide.
More information: General Configuration Steps
For the configuration of this variant, you follow a procedure analog to the configuration of the Booking a Single Flight Proxy-to-IDoc (Integration Engine) variant.
More information: Configuring a Process Integration Scenario (Proxy-to-IDoc (Integration Engine) variant)
Note the following information specific to this variant:
For the airline communication component you need to create a sender and a receiver communication channel, both with adapter type IDOC_AAE. Use the
available communication channel templates as described in the configuration guide.
Manually edit the communication channels (adapter type IDOC_AAE) as described in the configuration guide.

1.6.5 Booking a Single Flight (Proxy-to-Web-Service

Communication)

Use
The most important characteristics of this variant of the process integration scenario SingleFlightBooking are: communication with a Web service provider using
the WS communication channel.
This section contains the following information:
Concepts
An overview of the technical concepts that are addressed in this process integration scenario.
Configuring a Process Integration Scenario
An overview of the most important configuration steps with references to the detailed descriptions in the configuration instructions for the demo examples.
You have to configure the process integration scenario before you can execute it.

1.8.2.1 Concepts

Use

PUBLIC Page 23 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 This variant is technically an enhancement of the variant Single Flight Booking (Proxy-to-Proxy) .
It addresses additional concepts that are also covered by the Checking Flight Seat Availability (Proxy-to-Web Service) variant (more information: Concepts ).
The process integration scenario is in the ES Repository under the name SingleFlightBooking (in the software component version SAP Basis 7.30 ,
namespace http://sap.com/xi/XI/Demo/Agency ). Navigate forward to find all the objects used by the process integration scenario (interface objects, mapping
objects).
The airline provides a Web service for exchanging messages. You can find the Web service definition in the SAP system. Call transaction Object Navigator (
SE80 ) and select the package SAI_DEMO_AIRLINE . You find the Web service definition under Enterprise Services Service Provider . The name of
the Web service is SXIDAL_FBO_REQUEST .

Note
The Web service is a development object that is included in the shipment.

1.8.2.2 Configuring a Process Integration Scenario

Procedure
You must activate the Web service SXIDAL_FBO_REQUEST before you begin configuration in the Integration Directory. To do this, call transaction SOA
Manager (SOAMANAGER) in the SAP system of the airline that provides the Web service.
You can use the model configurator for the whole configuration procedure.
Note the following:
For the airline communication component create a receiver communication channel with adapter type WS (to enable the airline to receive the flight
availability query). Create this communication channel based on the communication channel template mentioned in the configuration guide.

Note
The configuration channel template is part of the shipment.

For the agency communication component specify the automatically generated receiver communication channel GeneratedReceiverChannel_XI (to enable
the agency component to act as proxy receiver).
For the airline communication component create a sender communication channel with adapter type WS (to enable the airline to send the flight booking
confirmation to the agency). Create this communication channel based on the communication channel template mentioned in the configuration guide.
Use the model configurator to generate receiver determinations, interface determinations, and receiver agreements.
Manually edit the receiver determinations and the WS communication channels as described in the configuration guide.

1.7 Booking Connecting Flights

Use
A travel agency uses the process integration scenario MultipleFlightBooking to book a flight and a connecting flight (for a passenger).
This addresses various technical concepts, depending on the configuration of the process integration scenario. The following variant is supported for this process
integration scenario:
MultipleFlightBooking (Proxy-to-Proxy/IDoc)
The most important characteristics of this variant are: integration of an executable integration process, asynchronous message exchange, use of mappings,
use of proxy runtime, use of IDocs.
Booking Connecting Flights (Proxy-to-Proxy/IDoc AAE Communicatio
The most important characteristics of this variant are: integration of an executable integration process, asynchronous message exchange, use of mappings,
use of proxy runtime, use of IDocs, connectivity based on the IDoc adapter (Advanced Adapter Engine).
For more information about the business uses of the process integration scenario, see Business Description (MultipleFlightBooking) .
For more information about the concepts, configuration, and execution of the process integration scenario, see the description of the variant.

1.7.1 Business Description (MultipleFlightBooking)

Use
A travel agency uses the 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.
For more information about the process flow of the integration process, see Description of the Example Process .

Process
1. The travel agency sends a booking order for a flight and a connecting flight to the executable integration process.
2. The integration process splits the overall booking into single booking orders (for the individual legs of the trip). The single booking orders are sent to the
respective airlines in parallel.
3. The airline executes the single flight booking. If a seat is available for one leg of the trip, the airline sends a positive confirmation to the integration process. If

PUBLIC Page 24 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 no seats are available for one leg of the trip, the airline sends a negative confirmation to the integration process.
4. The integration process receives single booking confirmations for each leg of the booking order and merges them. If there is a positive booking confirmation
for all legs of the trip, the single confirmations are bundled into an overall booking confirmation. This is sent to the travel agency. If one or more legs of the trip
cannot be booked, a negative overall booking confirmation is sent to the travel agency.
5. The travel agency receives the overall booking confirmation and updates the booking status in its system.
6. If the overall booking order was not successful, the integration process sends cancelations for the booked legs of the trip to the respective airline.
7. The airline cancels the bookings.

1.7.2 Booking Connecting Flights (Proxy-to-Proxy(IDoc)

Use
The most important characteristics of this variant of the process integration scenario MultipleFlightBooking are: Integration of an executable integration process,
asynchronous message exchange, use of mappings, use of proxy runtime, use of IDocs.

Process
This section contains the following information:
Concepts
An overview of the technical concepts that are addressed in this process integration scenario.
Configuring a Process Integration Scenario
An overview of the most important configuration steps with references to the detailed descriptions in the configuration instructions for the demo examples.
You have to configure the process integration scenario before you can execute it.
Executing a Process Integration Scenario
Information on how to execute the process integration scenario and how to check the results in the involved systems and in monitoring.

1.8.2.1 Concepts

Use
The process integration scenario MulitpleFlightBooking is semantically and technically an enhancement of the SingleFlightBooking process integration scenario.
The process integration scenario MultipleFlightBooking addresses most of the technical concepts that are addressed in the process integration scenario
SingleFlightBooking . See Concepts .
This process integration scenario also addresses additional concepts. This section gives you an overview of the additional technical concepts.
The table below contains the following information for each concept:
A hyperlink to the general description of the concept
A description of how the concept is implemented in the process integration scenario
The process integration scenario is in the ES Repository under the name MultipleFlightBooking (in the software component version SAP Basis 7.30 ,
namespace http://sap.com/xi/XI/Demo/Agency ). Navigate forward to find all the objects used by the process integration scenario (interface objects, mapping
objects). The integration process has the name MultipleFlightBookingCoordination (also in the software component version SAP Basis 7.30 , namespace
http://sap.com/xi/XI/Demo/Agency ).
The corresponding proxies for the message interfaces used are in the SAP system in ABAP proxy generation under the software component version SAP Basis
7.30 . For the travel agency, all proxies are in the namespace http://sap.com/xi/XI/Demo/Agency . For the airline, all proxies are in the namespace
http://sap.com/xi/XI/Demo/Airline .
Design time

Concept Description

Process Integration Scenario with Multiple Asynchronous Connections The process integration scenario comprises multiple asynchronous communication
steps between the travel agency, an executable integration process, and the airline:

Process Integration Scenario with an Executable Integration Process The executable integration process coordinates the bookings for both legs of the trip. To
do this, it communicates with the travel agency and airline applications using abstract
service interfaces and uses a correlation and a multi-mapping.
The executable process integration process is integrated into the integration scenario and
is represented there by a separate application component.

Abstract Service Interfaces The interface of the executable integration process is described by abstract service
interfaces.
The abstract service interfaces use the message types defined for the travel agency and
the airlines.

Operation mappings used by the integration process The integration process executes several transformation steps. These are defined by
operation mappings (for example: SplitMutlipleBookingOrder_BPM ).

Multi-mappings The integration process uses multi-mappings.

In the message mapping SplitMutlipleBookingOrder_BPM , two messages (each a
flight booking order for one leg of the trip) are generated from one message (overall
booking order of the travel agency).
In the message mapping MergeOrderConfirmations_BPM , if the booking is
successful, two messages (flight booking confirmations of the airlines) are merged into
one message (overall confirmation for the travel agency).

Configuration Time
All descriptions for configuration time are based on the SAP standard configuration.

PUBLIC Page 25 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Concept Description

Using configuration scenarios in the Integration Directory All configuration data for the process integration scenario is grouped into a configuration
scenario in the Integration Directory.
You can execute the whole configuration step-by-step by using the model configurator.
Use the process integration scenario MultipleFlightBooking as a template.

Communication Component A communication component of type Integration Process is defined in the Integration
Directory for the executable integration process. This enables you to address the
integration process as the sender/receiver of messages.
Communication components of type Business System are also defined for the
application systems involved.

Receiver Determination The receiver determinations used use both business system components and the
integration process components as receiver and sender, respectively.

Receiver agreement and communication channels If the receiver is the executable integration process, neither a receiver agreement nor a
communication channel is necessary.

Runtime

Concept Description

Executing an integration process The executable integration process is processed at runtime. All messages related to a
booking order are received by the process instance and processed further.

Asynchronous Communication In the process integration scenario, multiple asynchronous communication steps
(between the travel agency or the airline and the executable integration process) are
executed.

Monitoring messages You use monitoring to display and analyze messages at different phases of the message
More information: Administrative Tasks processing.

Communication based on the adapter runtime ( IDoc-Adapter ) One of the two connected travel agencies communicates with the Integration Server
using IDocs.

1.8.2.2 Configuring a Process Integration Scenario

Use
You must configure the scenario before you can execute it.
This section contains an overview of the necessary configuration steps.
For detailed instructions of how to configure this process integration scenario (for the SAP standard configuration), see the separate configuration guide(see General
Configuration Steps ).

Prerequisites
Before you configure this process integration scenario, you must execute general configuration steps (for example, set up the System Landscape Directory,
generate the appropriate flight data).
Note that when configuring communication paths to the travel agency using IDocs that you first have to specify those IDocs. For more information, see the separate
configuration guides.
More information: General Configuration Steps

Process
Configuration Steps
You can use the model configurator for the whole configuration procedure.
Note information on this in the separate configuration guides for demo examples in the chapter Booking Connecting Flights (Proxy-to-Proxy/IDoc Communication) .
For a detailed introduction to the configuration of the demo examples, see the SAP Developer Network (SDN) at https://www.sdn.sap.com SOA
Middleware Service Bus-Based Integration . In the Knowledge Center on the Service Bus-Based Integration page choose Getting Started . On the Getting
Started page, choose the SAP NetWeaver Process Integration Demo Examples - Configuration Guide .

1.8.2.3 Executing a Process Integration Scenario

Use
This section contains information on how to do the following:
Execute the process integration scenario
Check the booking data in the airline system
Check and analyze the messages processed by the Integration Server

Features
Executing the Flight Booking with Connecting Flight

PUBLIC Page 26 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Perform the following actions in the SAP system of the travel agency:
1. In the user menu, choose Process Integration Demo Examples Travel Agency: Execute Demo Examples .
2. Log on to the Business Server Pages (BSP) application, if necessary. Use your user and password for the travel agency system.
Note that the BSP application is only available in English and is always displayed in English, regardless of the logon language.
3. On the initial screen of the BSP application, choose Book Flight and Connecting Flight .
4. Choose Start .
5. Select the flight combination for which you want to make a booking.
To keep the example simple, only a few flight combinations are available.
The SAP standard configuration ensures that all flights are available on the first of each month. Therefore, the default setting for the flight date is the first day
of next month. We recommend that you select this flight date.

Note
Use the flight combinations displayed in the dialog to generate the following results: If you use Lufthansa 0400 and American Airlines 0017 ,
it is possible to book both legs of the trip and the overall booking is successful. (Prereqiusite is that both flights are available for the selected date and
that they are not booked out.) If you use Lufthansa 0400 and American Airlines 9999 , or Lufthansa 9999 and American Airlines
0017, it is only possible to book one leg of the trip in both cases. This means that the overall booking is not successful and the legs of the trip that
have been booked are canceled. If you use Lufthansa 9999 and American Airlines 9999 , it is not possible to book either leg of the trip and
the overall booking is therefore not successful.

6. Select a flight class.

Use the radio buttons. There are three available flight classes: economy, business, and first class.
7. Enter the passenger data.
8. Choose Create Booking Order .
9. The system displays the following information in a dialog:
Booking order information
The system displays the booking order number ( Order Number ), the flight class ( Flight Class ), the date of the booking order ( Order Date ),
and the booking status ( Order Status ). The system generates the booking order number automatically for each new booking order.

Note
Make a note of the booking number, in case you want to check the booking status again later.

Note
Read the notes on the booking status below.

Passenger information
Flight information
The booking number ( Booking Number ) is a number assigned by the airline when a booking is successful. This field is filled if booking is
successful, otherwise it remains empty.
10. Once you have sent the booking order, the system usually displays a yellow traffic light as the booking status. To update the information and check whether
a response has been sent in the meantime, choose Refresh .
Notes on the Booking Status
The system expresses the booking status with a traffic light symbol and a text.
For flight bookings, the booking status has the following meaning:
Both legs of the trip were booked successfully (green light)
One or both legs of the trip could not be booked (red light)
The flight booking order was sent but a response has not yet been received (yellow light).
For the XI demo example, the booking status has the following meaning:
A green or red light means that the process integration scenario was successful, since both communication steps were completed successfully.
If the system still displays a yellow light after a considerable length of time, then an error may have occurred in the communication. For more
information, use monitoring to analyze the communication.
Checking the Booking Status
You can also check the status of a booking order at a later point in time.
Perform the following actions in the SAP system of the travel agency:
1. In the user menu, choose Process Integration Demo Examples Travel Agency: Execute Demo Examples .
2. Log on to the Business Server Pages (BSP) application, if necessary. Use your user and password for the travel agency system.
3. On the initial screen of the BSP application, choose Query Booking Status .
4. Enter the booking order number in the Order Number field.
5. Choose Query Status .
The system displays the following information about the flight booking:
Booking date, flight class, and booking status
For example, Order Status displays whether the booking was executed successfully.
Data on the passenger for whom the flight booking was requested
Data on the flight for which the flight booking was requested
Checking the Flight Bookings in the Airline System
To check that the process integration scenario has been executed correctly, check the booking data in the corresponding airline system.
Perform the following actions in the SAP system of the respective airline:
1. In the user menu, choose Process Integration Demo Examples Airline: Display Flight Data .
2. In the Functions frame, select the Display Booking Data radio button.
3. Select Execute ( ).
4. Enter the selection criteria for displaying the booking data on the Data Browser screen.
The following fields are suitable for selection criteria: the field CARRID for the airline ID (for example, LH for Lufthansa and AA for American Airlines), the
field CONNID for the flight number (for example, 0400 ), the field FLDATE for the flight date (for example, 01.07.2004 ), the field ORDER_DATE for

PUBLIC Page 27 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 the booking date. SAP recommends that you enter today's date for the booking date.
The system displays a table containing detailed information about all flight bookings. This includes the following:
Data on the flight for which the flight booking was requested
Data on the passenger for whom the flight booking was requested
Booking data (booking number, booking date)
If the booking of one leg of a trip was successful, there should be a corresponding entry. However, this leg was then canceled (field CANCELLED =
X ).

Monitoring Messages
You use the monitoring transaction to display the messages that were processed by the Integration Server during execution of the process integration scenario.
You can use the payload of the message to check directly what business data was exchanged during execution of the process integration scenario.
See Monitoring Messages .

1.7.3 Booking Connecting Flights (Proxy-to-Proxy/IDoc AAE

Communication)

Use
The most important characteristics of this variant of the process integration scenario MultipleFlightBooking are: Integration of an executable integration process,
asynchronous message exchange, use of mappings, use of proxy runtime, use of IDocs, and connectivity based on the IDoc adapter (Advanced Adapter
Engine) .
This section contains the following information:
Concepts
An overview of the technical concepts that are addressed in this process integration scenario.
Configuring a Process Integration Scenario
An overview of the most important configuration steps with references to the detailed descriptions in the configuration instructions for the demo examples.
You have to configure the process integration scenario before you can execute it.

1.8.2.1 Concepts

Use
This variant addresses most of the technical concepts that are addressed by the variant Booking Connecting Flights (Proxy-to-Proxy/IDoc) .
More information: Concepts (Booking Connecting Flights (Proxy-to-Proxy/IDoc) variant)
As one exception to the variants mentioned above, this variant also addresses the IDoc adapter (AAE) as additional concept.
More information: Configuring the IDoc Adapter (Advanced Adapter Engine)

1.8.2.2 Configuring a Process Integration Scenario

Procedure
You must configure the scenario before you can execute it.
For detailed instructions of how to configure this process integration scenario (for the SAP standard configuration), see the separate configuration guide.
More information: General Configuration Steps
For the configuration of this variant, you follow a procedure analog to the configuration of the Booking Connecting Flights Proxy-to-IProxy/Doc (Integration Engine)
variant.
More information: Configuring a Process Integration Scenario (Proxy-to-Proxy/IDoc (Integration Engine) variant)
Note the following information specific to this variant:
For the airline communication component you need to create a sender and a receiver communication channel, both with adapter type IDOC_AAE. Use the
available communication channel templates as described in the configuration guide.
Manually edit the communication channels (adapter type IDOC_AAE) as described in the configuration guide.

1.8 Distributing Booking Order Data

Use
A travel agency uses the process integration scenario DistributeBookingOrderInformation to send data about flight booking orders to subscribed receivers
(publish and subscribe).
The following configuration variant is currently supported for this process integration scenario:
Distributing Booking Order Data (Proxy-to-File System)
The most important characteristics of this variant of the process integration scenario are: (optional) Messages with multiple receivers, use of external
definitions in the Integration Repository, use of a complex mapping, use of the file/FTP adapter.
For more information about the business uses of the process integration scenario, see Business Description .
For more information about the concepts, configuration, and execution of the process integration scenario, see the description of the variant.

1.8.1 Business Description (DistributeBookingOrderInformation)

PUBLIC Page 28 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 1.8.1 Business Description (DistributeBookingOrderInformation)

Use
A travel agency uses the 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).

Note
You can also configure the process integration scenario with several file systems as receivers.

Process
1. The travel agency sends a message containing information about booking orders.
The message contains a list of booking orders with the following information:
Header data for the booking order
Items contained in the booking
This includes information about the individual flights, the booking numbers of the individual items, and information about the passengers for whom the
individual items are booked.
2. A message containing information about booking data is saved in the file system as a file.
A user can process the file further, for example by using a spreadsheet program, and use it for reporting purposes.

1.8.2 Distributing Booking Order Data (Proxy-to-File System)

Use
The most important characteristics of this variant of the process integration scenario DistributeBookingOrderInformation are: (optional) Messages with multiple
receivers, use of external definitions in the ES Repository, use of a complex mapping, use of the file/FTP adapter.
This section contains the following information:
Concepts
An overview of the technical concepts that are addressed in this process integration scenario.
Configuring a Process Integration Scenario
An overview of the most important configuration steps with references to the detailed descriptions in the configuration instructions for the demo examples.
You have to configure the process integration scenario before you can execute it.
Executing a Process Integration Scenario
Information on how to execute the process integration scenario and how to check the results in the involved systems and in monitoring.

1.8.2.1 Concepts

Use
This section gives an overview of the technical concepts that are addressed in this process integration scenario.
The table below contains the following information for each concept:
A hyperlink to the general description of the concept
A description of how the concept is implemented in the process integration scenario
The process integration scenario is in the ES Repository under the name DistributeBookingOrder Information (in the software component version SAP
Basis 7.30 , namespace http://sap.com/xi/XI/Demo/Agency ). Navigate forward to find all the objects used by the process integration scenario
(interface objects, mapping objects).
The corresponding proxy for the service interface used by the travel agency is in the SAP system in ABAP proxy generation under the software component
version SAP Basis 7.30 : the outbound interface BookingOrderInformation_Out in namespace http://sap.com/xi/XI/Demo/Agency .

Design time

Concept Description

Process Integration Scenario with an Application Component of type Template . The receivers are file systems. These are represented by the application component
AgencyReporting . This is a storage location and not an application (a product).
Therefore, you use an application component of type Template .

Abstract Service Interfaces You define a service interface to represent the file format expected by the file system. This
is an abstract service interface, since the interface is not implemented (unlike in an SAP
system, for example).

External Definitions The file format expected by the file system is described by an XSD file, which was
defined independently of the ES Builder.
This description was imported to the Enterprise Services Repository as an external
definition BookingOrderDataInformation and must not therefore be recreated
manually.
The message type BookingOrderDataInfo defined in the XSD file is referenced in
the service interface BookingOrderDataInformation_Ext .

PUBLIC Page 29 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Message mapping to map data structures with multiple hierarchy levels to a data The Template scenario uses the message mapping
structure with one hierarchy level. BookingOrderDataInfo_Agency2AgencyReporting . This mapping maps a data
structure with multiple hierarchy levels (the message sent by the travel agency) to a data
structure with a single hierarchy level (the message expected by the file system). (For
details, see the test case defined in message mapping.)

Message mapping with a user-defined function The message mapping uses the user-defined function countByTemplate . This
function duplicates field values of the AgencyID and the OrderNumber , if they are
required in multiple item entries.

Message mapping with fixed-value mapping The message mapping uses the function FixValues to map fixed values (flight class:
from codes to meaningful names).

Communication channel template In the communication channel templates XIDemoChannel_FileXML and

XIDemoChannel_FileCSV , the required communication channels are preconfigured.

Configuration Time

Concept Description

Using configuration scenarios in the Integration Directory All configuration data for the process integration scenario is grouped into a configuration
scenario in the Integration Directory.

Communication Component You define a communication component of type Business System Service for the travel
agency system in the Integration Directory.
You define a separate communication component for each file system in the Integration
Directory. These communication components can be either of type Business
Component or Business System .
Communication components enable you to address the application systems as the
sender/receiver of messages.

Receiver Determination A receiver determination defines the receiver of the booking order data. This can be one
or more file systems.
Messages sent by the travel agency are sent to all configured receivers. Therefore, you do
not need to specify any routing conditions.

Interface Determination Interface determinations define the inbound interface and the operation mapping used.

Receiver Agreement and Communication Channels The travel agency sends the message in XI message format. Therefore, a sender
agreement to specify inbound processing in more detail is not necessary.
You define a receiver agreement for each file system. The receiver agreement defines the
technical details for outbound processing of the message by means of its assigned
communication channel.
Since the receivers are file systems, you assign a communication channel with the
adapter type File to the receiver agreement.
You define further details in the communication channel, for example file directory, file
name, and file format (XML format or CSV format (Comma Separated Values)).

When using communication channel templates when assigning communication You create the required communication channels when assigning the receiver
channels (configuration of a connection) communication channels (adapter type File ) for the connection. To do this, use the
communication channel templates XIDemoChannel_FileXML and
XIDemoChannel_FileCSV from the Enterprise Services Repository as templates.

Note
Communication channels can be assigned to a connection during the design of a
process integration scenario. If this is the case, the assigned communication
channel templates are proposed during the configuration of the connection.

Runtime

Concept Description

Messages with multiple receivers If multiple file systems are used, the messages are sent to multiple receivers.
To do this, a message split is performed during message processing.

Communication based on the adapter runtime ( file/FTP adapter ) The SAP system of the travel agency is based (in the standard configuration) on AS
ABAP 7.10. Therefore, you can use ABAP proxies to connect it to the Integration Server.
You connect the file system to the Integration Server using the file/FTP adapter. In the
SAP standard configuration, this file system is localized on the server on which the SAP
system of the travel agency (and the Integration Engine) is also installed.

1.8.2.2 Configuring a Process Integration Scenario

Use
You must configure the scenario before you can execute it.
This section contains an overview of the necessary configuration steps.
For detailed instructions of how to configure this process integration scenario (for the SAP standard configuration), see the separate configuration guide(see General
Configuration Steps ).

Prerequisites

PUBLIC Page 30 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.
 Before you configure this process integration scenario, you must execute general configuration steps (for example, set up the System Landscape Directory,
generate the appropriate flight data). For details, see General Configuration Steps .

Process
Configuration Steps
You can configure the process integration scenario for one file system or for multiple file systems.
If you are interested in the functions of the file/FTP adapter, it is sufficient to configure one file system.
If you are interested in exchanging messages with multiple receivers, you must configure multiple file systems.
Define a suitable communication component in the Integration Directory for each file system. Create a communication channel with the adapter type File for each
of these communication components. In the communication channel, define how the file/FTP adapter is to process an inbound message. for example, file
directory, file name, and file format (XML format or CSV format (Comma Separated Values)).
To configure the message exchange, you need a receiver determination as well as an interface determination and a receiver agreement for each receiver.
For more information, see the configuration guide for the demo examples.
Once you have finished, do not forget to activate all change lists containing changes that you made during configuration.

1.8.2.3 Executing a Process Integration Scenario

Use
This section contains information on how to do the following:
Execute the process integration scenario
Check whether the business process integration scenario has been executed correctly in the file system
Check and analyze the messages processed by the Integration Server

Features
Sending Travel Agency Booking Data
Perform the following actions in the SAP system of the travel agency:
1. In the user menu, choose Process Integration Demo Examples Travel Agency: Sending Data to Booking Orders .
2. On the next screen you have the option of limiting the number of booking orders to be sent.

Note
You can limit the data by using the order key, the order date, or the order status. Note that the selection criteria are linked by a logical AND . In the default
setting, the number of booking orders is not limited, that is, all booking orders that are available in the system are sent.

3. Choose Execute ( ).
The next screen displays information about whether the message was sent successfully and how many booking orders were selected.

Note
If no booking orders meet the selection criteria, no message is sent.

Processing the Booking Data in the File System

1. Open the file directory that you specified as the target directory during communication channel configuration.
2. This should contain the file with the booking data.
If the file format was configured as XML , you can open the file in your Web browser and display the booking data.
If the file format was configured as CSV , you can open the file with a spreadsheet program and process it further there.
Monitoring Messages
You use the monitoring transaction to display the messages that were processed by the Integration Server during execution of the process integration scenario.
You can use the payload of the message to check directly what business data was exchanged during execution of the process integration scenario.
See Monitoring Messages .
In message monitoring you have the option of comparing the message before (data structure with multiple hierarchy levels) and after (data structure with one
hierarchy level) the mapping step.

PUBLIC Page 31 of 31
© 2014 SAP SE or an SAP affiliate company. All rights reserved.