Concept

Description

Integration scenario with one synchronous connection

The integration scenario comprises one synchronous communication step between the travel agency and the airline.

Synchronous message interfaces

The integration scenario uses a synchronous message interface for each sender and receiver. Each message 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 types

The message types used by the travel agency are structurally identical to the message 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 (see ABAP proxy objects)

There is an executable client proxy in the SAP system (ABAP object class) for the outbound message interface of the travel agency.

There is an executable server proxy in the SAP system (ABAP object interface with an implementing ABAP object class) for the inbound message interface of the airline.

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 CheckFlightSeatAvailability is used as a template for configuration. You use the integration scenario configurator to enter the required configuration data from the integration scenario step-by-step. The integration scenario configurator generates all the relevant configuration objects (receiver determinations, interface determinations, collaboration agreements).

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

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 (SAP NetWeaver 7.0). 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 phases).