Setting Up Point-to-Point Connections 

Purpose

The Integration Server provides a variety of services that are required in cross-system processes, for example, routing and executing mappings. In those cases where such services are not required, communicating by using the Integration Server unnecessarily slows down message exchange. This is usually the case for new applications where both the sender and receiver use message interfaces to communicate. In such cases, mappings are often not required because the outbound and inbound messages use the same message type.

The process below explains how client and server proxies, which were generated by means of message interfaces from the Integration Repository, can communicate with each other directly by using the Web service runtime. This has the following advantages:

●      Performance is improved by bypassing the Integration Server.

●      If the services of the Integration Server are required at a later date, it is possible to switch from the Web service runtime to the XI runtime, without having to change the program code (see also: Runtime Configuration).

Prerequisites

●      Your scenario uses a synchronous outbound and inbound message interface from the Integration Repository. Both message interfaces use the same message type for the request, response, or fault message. You have already created the corresponding client and server proxies in the application systems.

●      No mapping is required (this includes value mappings).

●      No receiver determination is required, in other words, the receiver is static. It is also possible to set the receiver dynamically yourself (by using the GET_LOGICAL_PORT_FROM_RECEIVER method, see Receiver Pre-Identification).

●      No monitoring functions are required (only the following are available: trace for the Internet Communication Manager (ICM), Internet Communication Framework (ICF) and transaction SM59 for the HTTP connection).

Process Flow

...

       1.      Create the corresponding Web service for the server proxy.

                            a.      Display your server proxy in the Object Navigator (transaction SE80).

                            b.      From the context menu, choose Create ® Enterprise Service / Web Service ®Web Service. (The wizard is only active for synchronous server proxies). Follow the wizard’s instructions and specify the names and the descriptions for the Web service.

                            c.      Check as necessary if the navigation tree of the Object Navigator is displaying the name of the Web service, and whether the Web service has been successfully deployed.

                            d.      Log on to the target client of the receiver system and release the Web service.

       2.      Log on to the source client of the sender system (client side).

       3.      Create a corresponding HTTP destination by calling transaction SM59.

       4.      Enter the following data on the Technical Settings tab page:

                            a.      Enter the path of the Web service that you released as the Path Prefix. Example: /sap/bc/srt/xip/sap/<Web service name>.

                            b.      Specify a Target Machine (including the port, if applicable).

       5.      Enter the logon data on the Logon/Security tab page and save your entries.

       6.      In the same client, call transaction LPCONFIG and create a logical port for the client proxy.

                            a.      On the Runtime tab page, choose Web Service Infrastructure.

                            b.      Assign the http destination to the logical port.

                            c.      Activate the logical port.

Result

You can now send messages directly to the logical port and the server proxy by using the client proxy call in the source client of the sender system (see also: Sending a Message).