/SAPSRM/XML_TEST_REPORT_OUT - Program SPROX_SERVICE_INTERFACE_TEST_I

rdisp/max_wprun_time - Maximum work process run time   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Purpose

This report is used to call a service consumer or event provider with a given request payload and display the resulting response payload.

Integration

Prerequisites

Features

To test a consumer proxy or event provider, the generated proxy class is used. However, contrary to the test of this class with the test environment of the class builder, XML data is used to represent input and output.

Execution is done by the following steps:

• The request is mapped to ABAP structures and classes

• The consumer proxy or event provider class is called

• The ABAP data is mapped to the XML request at proxy runtime

• The XML request is sent to the service provider or event consumer

• The XML response from the service is received (consumer proxy only)

• The XML response is mapped to ABAP structures and classes (if available)

• The resulting ABAP structures and classes are mapped to XML to display the response The responsein the test environment displays only the data understood by the consumer. If there is no response,the data is ignored and the response tab does not contain any data. To close this gap, an additionaltab contains the original response. Under this tab, the XML response that acts as input for the mappingto the ABAP data is displayed. However, even this may not be equal to the data sent over the network.The data sent over the network can have different formats, for example, attachments and compressed files.If you need the data sent over the network, use HTTP trace, for example. Nevertheless, the data shown as original response should contain what was received from the service.

• Use Runtime
  By default, the consumer proxy or event provider is called using the runtime in the same way as when you use the proxy class from any ABAP program.

• Local Interface Call (only available for service consumers)
  Using the F4 help, you can selecta service provider available in the local system. Instead of the runtime, the implementation of theservice provider in the local system is called directly. Contrary to the runtime, no configuration is required for the local interface call.

• Extended XML handling
  By selecting this checkbox, you can activate extended XML handling in the consumer proxy.

For more information regarding the test environment, see here.

Selection

Standard Variants

Output

Activities

Example

ABAP Short Reference   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.


Length: 2978 Date: 20120523 Time: 223933     triton ( 117 ms )