Concepts
This variant is technically an enhancement of the variant Checking Flight Seat Availability (Proxy-to-Proxy).
The variant Checking Flight Seat Availability (Proxy-to-Web Service) 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 in the process by the Web service and the SOAP adapter provides a Web service that enables messages to be exchanged. You can find the Web service definition in the SAP system. Call transaction Object Navigator (SE80) and select the package SAI_DEMO_AIRLINE. The Web service definition is under Enterprise Services ® Web Service Library ® Web Service Definitions (Web service name: SXIDAL_FLIGHTSEATAVAIL_CHECK, short description: XI Demo: Check Flight Availability).
The Web service is a development object that is included in the shipment.
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, namespace http://sap.com/xi/XI/Demo/Agency, outbound interface FlightSeatAvailabilityQuery_Out.
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_Web_Service contains the definition of the connection that is based on the message exchange between the message interface and the Web service. |
Integration scenario with an application component of type Template for communication with an external partner |
The airline providing the Web service has been defined as an External Partner.
This is
represented in the component view by the symbol The Airline application component is of type Template because messages are exchanged using a Web service for which you do not necessarily know the technical details. (Of course, the actual realization in the demo example is known. However, this is not necessarily the case for a travel agency and an airline in a real-life scenario. |
In the communication channel template XIDemoChannel_WebServiceSOAP, the necessary communication channel is preconfigured. |
|
Web service definition |
The Web service definition contained in the SAP system is based on the inbound message interface FlightSeatAvailabilityQuery_In (software component version SAP Basis 7.00, namespace http://sap.com/xi/XI/Demo/Airline). |
Configuration Time
Concept |
Description |
Service with party
|
In the SAP standard configuration, the Web service for determining flight seat availability is implemented as the business service of a party. |
Since the airline expects the SOAP format, the receiver agreement is assigned a communication channel with the adapter type SOAP. |
|
Activating a Web service |
The Web service is implemented and shipped by SAP, but you must activate it in the SAP system. |
Runtime
Concept |
Description |
Communication based on the adapter runtime (SOAP adapter) |
The airline implements the flight availability check as a Web service that is called by the Integration Server using the SOAP adapter. |