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 these 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 process integration scenario

The process integration scenario is in the ES Repository under the name CheckFlightSeatAvailability (in the software component version SAP Basis 7.30, namespace http://sap.com/xi/XI/Demo/Agency). Navigate forward to find all the objects used by the process integration scenario (interface objects, mapping objects).

The airline provides a Web service for exchanging messages. You can find the Web service definition in the SAP system. Call transaction Object Navigator (SE80) and select the package SAI_DEMO_AIRLINE. You find the Web service definition under Enterprise Services Service Provider. The name of the Web service is SXIDAL_FLIGHTSEATAVAIL_CHECK .

Note Note

The Web service is a development object that is included in the shipment.

End of the note.

Design Time

Concept	Description
Process integration scenario with multiple component views	Multiple component views are defined for the process 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 service interface and the Web service.
Process 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 for the application component Airline. 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.
Web service definition	The Web service definition contained in the SAP system is based on the inbound service interface FlightSeatAvailabilityQuery_In (software component version SAP Basis 7.30, namespace http://sap.com/xi/XI/Demo/Airline).

Concept

Description

Process integration scenario with multiple component views

Multiple component views are defined for the process 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 service interface and the Web service.

Process 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 for the application component Airline.

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.

Web service definition

The Web service definition contained in the SAP system is based on the inbound service interface FlightSeatAvailabilityQuery_In (software component version SAP Basis 7.30, namespace http://sap.com/xi/XI/Demo/Airline).

Configuration Time

Concept	Description
Communication component with party	In the SAP standard configuration, the Web service for determining flight seat availability is implemented as the business component of a party.
Receiver agreement and Communication Channels	Since the airline expects a Web service call, the receiver agreement is assigned a communication channel with the adapter type WS.
Activating a Web service More information: SOA Manager	The Web service is implemented and shipped by SAP, but you must activate it in the SAP system. To do this, use the SOA Manager.

Concept

Description

Communication component with party

In the SAP standard configuration, the Web service for determining flight seat availability is implemented as the business component of a party.

Receiver agreement and

Communication Channels

Since the airline expects a Web service call, the receiver agreement is assigned a communication channel with the adapter type WS.

Activating a Web service

More information: SOA Manager

The Web service is implemented and shipped by SAP, but you must activate it in the SAP system. To do this, use the SOA Manager.

Runtime

Concept	Description
Communication on the basis of Web service runtime (Communication Channel with Adapter Type WS)	The airline implements the flight availability check as a Web service that is connected with the Integration Server using a communication channel with adapter type WS.