Concept

Description

Integration scenario with two asynchronous connections

The integration scenario comprises two asynchronous communication steps between the travel agency and the airline.

Asynchronous message interfaces

The integration scenario uses asynchronous message 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.

Interface mapping

The integration scenario uses interface mappings to do the following:

·        To map the travel agency booking order to an airline booking order (interface 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 (interface mapping FBOConfirmation_Airline2Agency)

Asynchronous outbound proxy and synchronous inbound proxy (see ABAP proxy objects)

There are executable client proxies in the SAP system (ABAP object classes) for the outbound message interfaces.

There are executable server proxies in the SAP system (ABAP object interfaces with implementing ABAP object classes) for the inbound message interfaces.

Concept

Description

Using configuration scenarios in the Integration Directory

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

Integration scenario configurator

The integration scenario SingleFlightBooking is used as a template for configuration. The integration scenario 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.

Service

A service 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 interface mapping used.

·        Two interface determinations define the inbound interface and the interface 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.

Concept

Description

Communication using the proxy runtime

The SAP systems of the travel agency and the airlines are based (in the standard configuration) on SAP Web AS 7.00. 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 phases).