Concepts (SAP Library - Enabling Application-to-Application Processes)

Concepts

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.10, 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.10, 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.10. 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 (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.

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.
Defining Receiver Determinations	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 processing.
Communication based on the adapter runtime ( IDoc-Adapter)	One of the two connected travel agencies communicates with the Integration Server using IDocs.