Show TOC

Process documentationConfiguring a Process Integration Scenario Locate this document in the navigation structure

 

You must configure the scenario before you can execute it.

This section contains an overview of the necessary configuration steps.

For detailed instructions of how to configure this integration scenario (for the SAP standard configuration), see the separate configuration guide(see General Configuration Steps).

Prerequisites

Before you configure this process integration scenario, you must execute general configuration steps (for example, set up the System Landscape Directory, generate the appropriate flight data). For details, see General Configuration Steps.

Configuration Steps

You must activate the Web service SXIDAL_FLIGHTSEATAVAIL_CHECK (short description: XI Demo: Check Flight Availability) before you begin configuration in the Integration Directory. To do this, call transaction SOA Manager (SOAMANAGER) in the SAP system of the airline that provides the Web service.

You can use the model configurator for the whole configuration procedure. Note the following:

  • Select the process integration scenario CheckFlightSeatAvailability (component view ABAP_Proxy_2_Web_Service) from the ES Repository.

  • Assign communication components: Assign the corresponding business system components of the travel agency and the business component of the airline that provides the Web service to the application components of the process integration scenario.

  • Create a communication channel with adapter type WS for the airline that receives the flight availability query and specify the necessary attributes. Create the communication channel based on the communication channel template XIDemoChannel_WS from the ES Repository (software component version SAP BASIS 7.10, namespace http://sap.com/xi/XI/Demo/Agency).

  • Use the model configurator to generate receiver determinations, interface determinations, and receiver agreements.

  • Define the corresponding conditions for the receiver determination so that messages are forwarded to the correct airline. Use the context object AirlineID.

Once you have finished, do not forget to activate all change lists containing changes that you made during configuration.