Booking a Single Flight

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.