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.
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.