Calling SOAP web service with profile in Response

Please import the following profile and set it to active. This profile serves us as a local web service: Profile-Profile_as_web_service_dynamic_response.pak. See also section Profile as SOAP web service (dynamic response) .

Calling the web service


Now import the following profile. We use this profile to call the local web service in a Response : Profile-Calling_web_service_with_response_route.pak

Please open the example profile and navigate to phase 3.

Here we create a target structure based on the WSDL file of the web service.


images/download/thumbnails/159865944/814-version-1-modificationdate-1700622895198-api-v2.png


(1) Click here and select the menu item "Create structure from WS-SOAP request". Another dialogue appears.


images/download/attachments/159865944/1903-version-2-modificationdate-1718088416913-api-v2.png


(2) Enter the value "https://localhost:443/dw/Request/addition_web_service?wsdl". That is our local web service.

(3) After you click here, (4) will be filled.

(4) The list of web service methods (only one here).

(5) Creates a fitting target structure, see the following screenshot. Enter the fixed values "1" and "2" in fields "intA" and "intB".


images/download/attachments/159865944/809-version-1-modificationdate-1700622895203-api-v2.png


Now navigate to phase 5 and select the XMLNoTemplateUnit and enter value "Add" for the "Root node name" parameter. You can ignore all other parameters.


images/download/attachments/159865944/810-version-1-modificationdate-1700622895187-api-v2.png


Now switch to phase 6 and add a Response "HTTP". The content settings must be as follows.


images/download/attachments/159865944/827-version-1-modificationdate-1700622895191-api-v2.png

Following the HTTP settings.


images/download/attachments/159865944/1902-version-2-modificationdate-1718011329312-api-v2.png


(6) Must be set.

(7) The URL of the web service. That is our local web service.

(8) The response of the web service can (but does not have to) be analysed in a subsequent profile. See details in section Response "HTTP". Note: The response has the encoding UTF-8.

(9) Some web services require additional values that are expected in the HTTP header, such as eBay (application ID, etc.). These can be set here.

Setting HTTP request headers


See (9).