Defining a Web Service Consumer (REST)

Defining this object identifies the active service made available by a provider using the REST protocol, and allows you to configure settings on how the service is to be consumed.

1. Under the Settings section, enter the URL. This indicates the actual location of the service.
   If you are connecting to a secure (HTTPS) URL you may need to import the certificate for the URL you are connecting to the Clarify Keystore prior to connecting.

   Note: You can also type a Substitution Variable - a place holder for all or part of the url path. The actual url will be supplied at runtime by a Business Process.". An example of partial replacement may be just replacing

   https://api.bestbuy.com/v1/products/${productId}.json

   where

   $productId}

   gets substituted with an actual product id at runtime.
2. Select the HTTP Method. This indicates the type of REST operation (GET, POST, PUT, DELETE) to perform when accessing a URL.
3. Use the Timeout field to determine exactly when a connection attempt to an external Web Service provider will be terminated if a response is not received.
4. Use the Retry Count field to determine the number of times the Web Service consumer will attempt to reconnect.
5. Use the Retry Delay field to determine the amount of time between each retry attempt.
6. Determine payload behavior by using the Transfer Type field. Two options are available.
   1. Chunked: The payload will be divided into smaller units and sent one at a time.
   2. Content-Length: The entire payload will be sent.
7. Enter the name of the Alias into the Vault Entry Alias field to have this object to use a vault entry. See Secure Authorization of Web Service Requests using a Clarify Server Vault for more details.
8. Under the Default Request HTTP Headers section, click the Add button to provide and define any HTTP Headers you plan to use with the REST consumer. This optional table allows you to send additional headers to the remote server when the REST consumer is executed. The values specified in the HTTP headers are the default values sent out, however, these values can be modified when the REST Consumer is used by the Business Process at runtime.
   Note: These new REST interfaces are also available in the Web Service Consumer editor so you can change these values after the Web Service Consumer is created.