Show TOC

Procedure documentationConsuming A Stateless 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 to each service interface. Stateless communication means that the messaging runtime does not support the saving of a status at the provider once the messaging runtime has completed the message exchange successfully.

Depending on the interface pattern, the service interface editor provides you with different operation patterns and modes. Read the explanations on Interface Patterns and Operations in the section Service Interface in the documentation for the Enterprise Services Repository.

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 = ...

    If no standard port has been agreed, the logical port must be specified.

  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 the purpose of more specialist services.

Calling an Asynchronous Service from an Application

Read the section Programming with Sequences.

Testing the Client Application

You can test how the Web service behaves when it is called by an application. Select the proxy that you have generated and choose Test (F8).

For more information, refer to the section:

Types of Message Transmission.