This section explains the process of creating web service consumer activity for RESTful Web Service.
Steps to create Web Service Consumer activity for RESTful Web Service
On the create Web Service Consumer page, select the REST radio button.
In the URL textbox, enter the URL of the Web Service that you want to invoke.
You need to pass the request in the URL. You can also define the values of the parameters in the Parameter table. |
To populate the Parameter table automatically from a URL, click the Extract Param from URL button. You can also populate the Parameter table along with their default values by giving the query parameters in the URL itself.
You can dynamically override a complete URL or any parameter of the URL with the value of any variable. To do this you need define the variable name in the URL field. For Example, to override a complete URL you can define the URL as $$REST_URL_Var$$. |
To encrypt the password using Vault, first create a vault and then use it to mask the password. It can either be used in the URL, or in the Parameter table. Write the aliasName and the key, which contains the confidential information (in this case- password) in the following format:
With Vault, the URL format will be:
Instead of extracting parameters from the URL, you can also use Vault when you provide parameters directly in the table. |
Select the style of the parameters from the Style drop-down list. It could be Query or Header.
If you want to pass parameters as a part of HTTP request then, you need to select Header in the Style drop-down list. |
Select a security policy from the Security Policy drop-down list.
|
When you use either Put or Post method, then following two additional options are displayed.
Post query string is used to pass the query paramters in RESTful Request. To send the query parameters with Put or Post method, enable the Post Query String option and define the parameters in the Parameter table. Enable Multipart is used to the post the file to the RESTful Webservice. To send a file follow the below steps:
Media type for Response varies for different web service. It can be application/json or application/xml. Change Content Type of Multipart and Disposition OrderTo change the Content-type of multipart and disposition order, you need to set the following variables in the process flow: For Content Type: Service.{EntityName}.attachmentMediaType For Disposition Type: Service.{EntityName}.ReOrderContentDisposition = true here the EntityName is the web services consumer activity name, for example: Service.WeatherReport.attachmentMediaType=application/xml To send one or multiple payloads along with the file, Define the Context Variable Service.<Consumer Entity Name>.multipartParams in the Process Flow.
Once defined, you can pass the payloads (in key-value pairs), separated by comma, as the value to this Context Variable. Given below is the example of two payloads in key-value pair. param1=value1,param2=value2
|
Expand Advanced Properties to view the advance property of the RESTful web service consumer activity.
If you do not want your RESTful web service consumer activity to wait indefinitely for a response from a web service provider then, enter a timeout value in the Read Timeout (in seconds) text box. The default value is 0 which means your RESTful web service consumer activity will wait indefinitely for a response.