Checking Flight Seat Availability (Web Service-to-Web-Service

This section describes how to configure the Checking Flight Seat Availability process integration scenario in the Web Service-to-Web Service Communication variant. In this variant, you configure the Agency (client 105) as Web Service consumer and the airline Singapore Airlines (SQ) (client 107) as Web service provider. The communication is done directly from the agency to the Singapore Airline system without message transfer in the Integration Server.

This demo example is implemented as the process integration scenario CheckFlightSeatAvailability. The process integration scenario is located in the Enterprise Services Repository, in the software component SAP BASIS, software component version SAP BASIS 7.40, in the namespace http://sap.com/xi/XI/Demo/Agency.

For the business description of the process integration scenario, see ‎5.1.1.

In this variant, the airline Singapore Airlines offers a Web service for the communication and the agency consumes this Web service in a direct Web Service call.

The Web service definition is delivered with the demo examples.

To display the Web service definition, call transaction Object Navigator (SE80) in the SAP system. Select the package SAI_DEMO_AIRLINE and open the node Enterprise Services  Service Provider. The name of the Web service is SXIDAL_FLIGHTSEATAVAIL_CHECK.

To enable the Web service configuration, assign the role

SAP_BC_WEBSERVICE_ADMIN to the user XIDEMO in client 107, see chapter ‎4.1.3.

In order to configure the Flight Availability Check (Web Service-to-Web Service

Communication) variant, you have to activate the Web service in the SAP system. As you already activated the Web Service in the variant Proxy-to-Web Service it can also be used in the Web Service-to-Web Service variant. If you have not executed the

CheckFlightSeatAvailability variant Proxy-to-Web Service you have to execute chapter ‎7.2.1 now. Otherwise use the WSDL and endpoint-URL from chapter ‎7.2.1 in the Web Service-to- Web Service variant as well.

7.3.1 Activating the WS Cache Notification for the

Agency

To activate the automatic configuration transfer for the Web Service Configuration in the agency client you have to switch on the WS configuration using the WS Adapter and set user and password for the cache notification in the business system in the directory.

1. In the integration directory open the business system <SID>_105 via double click. 2. Switch to change mode ( ).

3. In the tab Logon Data set the flag for Support Communication using the WS Adapter. As user set a user with the role SAP_XI_ID_SERV_USER_MAIN (for example PIDIRUSER) with the corresponding password in client 105.

With this setting the WS consumer configuration will be done automatically in the agency client 105.

7.3.2 Configuration in Integration Directory

Settings in the Model Configurator

To accomplish the following configuration steps in the Integration Directory, proceed as described in detail in section ‎5.1.2. To configure the process integration scenario

CheckFlightSeatAvailability in the Web Service-to-Web Service Communication variant, use the settings as listed in the table below.

All configuration objects for this variant are saved in the same configuration scenario as used for the Proxy-to-Proxy variant

(XIDemo_CheckFlightSeatAvailability).

Settings for the Process Integration Scenario CheckFlightSeatAvailability (Proxy-to- Web Service Communication)

Configuration Step Settings Selecting the Process

Integration Scenario (Component View) and Creating the Scenario

Open the scenario XIDemo_CheckFlightSeatAvailability and call the model configurator (as described under ‎6.1.1).

Select the component view Web_Service_2_Web_Service.

If you have not configured the Check Flight Seat Availability process integration scenario in another variant before, you first have to start the model configurator and create the configuration scenario XIDemo_CheckFlightSeatAvailability before you can proceed with the next configuration steps. For a detailed description of the procedure, see 5.1.2 under Selecting the Process integration scenario (Component View). Assigning

Communication Components

For the Agency application component

 Assign the business system component <SID>_105 (entry under Business System Components)

 Assign the party XIDemo_Agency and component CheckFlightSeatAvailability (entries under Business Components for External Communication)

For the Airline application component

 Assign the party XIDemo_SingaporeAirlines and component ProvideFlightSeatAvailability (entries under Assign Business Components for B2B Communication)

Configuring the Connection

For the receiver relation you have to specify a receiver communication channel (receiver communication component ProvideFlightSeatAvailability).

In this variant you specify the receiver communication channel by creating a new channel on the basis of a communication channel template from the Enterprise Services Repository. To do this, proceed as follows:

1. In the tab Connections from the Communication component Assignment choose the dropdown menu for the push button New ( ).

2. In the dropdown menu select Create Communication Channel with Template.

A wizard for creating a communication channel on the basis of a communication channel template is started.

3. Choose Continue.

4. In the Select Template step, select the XIDemoChannel_WS communication channel template (software component version SAP BASIS 7.40, namespace

http://sap.com/xi/XI/Demo/Agency). 5. Choose Continue.

6. In the Create New Communication Channel step, confirm all entries by clicking Finish.

7. Click Close to close the Create New Communication Channel dialog box.

The system creates a communication channel with the name XIDemoChannel_WS.

8. Set the flag for Direct Connection. Generating the

Configuration Objects

Manual Editing To determine the outbound processing of the message, you have to specify the receiver communication channel XIDemoChannel_WS. In the channel you have to change the following settings:

 In the field WSDL access URL, enter the WSDL URL you have found out before (see ‎7.2.1). (e.g.

http://ls0045.wdf.sap.corp:50005/sap/bc/srt/wsdl/srvc_<numb er>/wsdl11/allinone/ws_policy/document?sap-client=107  In the field Authentication Method for WSDL access, select

Basic Authentication over HTTP, set the user XIDEMO_WS with the password you set in chapter 4.1.4.

 In the Technical Transport Settings in field Target Host select the Service Information using the Input Help.

 The inputs in fields Service Name/Port and URL Access Path should be entered automatically when you select the Target Host.

 Save the channel.

In the direct connection you have to configure the User Authentication. Open the Direct connection | <SID>_105 |

FlightSeatAvailabilityQuery_Out | XIDemo_SingaporeAirlines. Under Adapter-Specific Attributes set the user name and password.

 In the field User Name enter user XIDEMO_WS.

 In the field User Password enter the password set in chapter ‎4.1.4.

 Save the direct connection.

Final Steps Save the scenario XIDemo_CheckFlightSeatAvailability.

Activate the scenario XIDemo_CheckFlightSeatAvailability and all objects that it uses (follow the procedure as described in section

‎

5.1.2.

7.3.3 Executing and Testing

There is an application in the SAP system of the Integration Server (client 105) that you can use to test the process integration scenario (for both configurations).

The execution of this variant of the process integration scenario is not different from that of the Proxy-to-Proxy, Proxy-to-RFC and Proxy-to-Web Service variant (see ‎5.1.3).

This time, however, you use the flights SQ 0988, SQ 0997, SQ 9999 and N.N. 9999. If you get the error ‘No sender agreement found for , <SID>_105,

XIDemo_SingaporeAirlines, ProvideFlightSeatAvailability, http://sap.com/xi/XI/Demo/Agency, FlightSeatAvailabilityQuery_Out’ check out the chapter Error Message: No sender agreement found for , <SID>_105… in the Troubleshooting Chapter 9 at the end of this document.

Be aware that for this kind of communication – WS – WS direct communication – no messages can be found in the PI monitoring (PI Monitoring Home,

SXMB_MONI, Solution Manager).