Show TOC

Procedure documentationConsuming A Stateful Web Service Locate this document in the navigation structure

 

The interface patterns stateless (XI 3.0 compatible), stateless, stateful, and TU&C/C assign the type of communication to be performed for each service interface. Stateful communication means that the messaging runtime supports the saving of a status at the provider once the messaging runtime has completed the message exchange successfully.

This interface pattern is only needed for a few special technical scenarios. It does not guarantee a common update of data at the receiver.

You cannot use this interface pattern for enhanced communication using the Integration Server. Only synchronous stateful communication is supported.

Prerequisites

Calling a Synchronous Service from an Application

Proceed as follows:

  1. Instantiate the proxy class.

        DATA: lv_<client proxy name> TYPE REF TO <client proxy name>.

        CREATE OBJECT lv_<client proxy name>

            EXPORTING

              LOGICAL_PORT_NAME =

    The logical port must be specified if no standard port has been agreed upon.

  2. Fill in the query data structure.

        DATA: lv_<request data> TYPE <request data>.

              lv_<response data> TYPE <response data>.

  3. Call the service.

        CALL METHOD lv_<client proxy name>-><name of method / operation>

            EXPORTING

               INPUT = lv_<request data>

            IMPORTING

               OUTPUT = lv_<response data>

  4. Edit the received data.

        LOOP AT lv_<response data>

            <process the data>

        ENDLOOP.

The runtime supports protocols for more specialised services. For more information, see Protocols.