Concepts
This variant is technically an enhancement of the variant Checking Flight Seat Availability (with Proxy).
The variant Checking Flight Seat Availability (with RFC) addresses most of the technical concepts that are addressed in the variant Checking Flight Seat Availability (with Proxy). See Concepts.
This variant 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 integration scenario
The integration scenario is in the Integration Repository under the name CheckFlightSeatAvailability (in the software component version SAP Basis 7.00, namespace http://sap.com/xi/XI/Demo/Agency). Navigate forward to find all the objects used by the integration scenario (interface objects, mapping objects).
The airline that is integrated into the process by the RFC adapter uses RFCs to exchange messages.
The corresponding proxy for the message interface used by the travel agency is in the SAP system in ABAP proxy generation under the software component version SAP Basis 7.00: the outbound interface FlightSeatAvailabilityQuery_Out in namespace http://sap.com/xi/XI/Demo/Agency.
Design Time
Concept |
Description |
Integration scenario with multiple component views |
Multiple component views are defined for the integration scenario CheckFlightSeatAvailability. The component view ABAP_Proxy_2_RFC contains the definition of the connection that is based on the message exchange between the message interface and the RFC interface. |
The RFC interface used is implemented in the SAP system. The description of the RFC interface is imported to the Integration Repository and is located in the software component version SAP Basis 6.40 under Imported Objects. This means that the RFC interface is also available in the Integration Repository and can be referenced by other design objects (for example, mapping objects). |
|
Message mapping with RFC |
The interface mapping used in the integration scenario maps the message interface to the RFC interface and the other way around. The interface mapping contains three message mappings, which map the request message, response message, and fault message to the RFC. |
Configuration Time
Concept |
Description |
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 the receiver airline American Airlines expects the RFC format, the corresponding receiver agreement is assigned a communication channel with the adapter type RFC. |
Runtime
Concept |
Description |
Communication based on the adapter runtime (RFC adapter) |
The SAP systems of the travel agency and an airline 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. You connect the system of the other airline to the Integration Server by using RFCs. In the SAP standard configuration this system is also based on SAP Web AS (SAP NetWeaver 7.0). |