The web service (SOAP) transport definition panel allows you to specify the URL to which the HTTP SOAP web services request will be sent along with any optional credentials that will be needed when interacting with the web service. It also allows you to specify common runtime behavior shared by many transports such as:
- Connection and Transaction timeouts
- Store and Forward
- Mapping Logs.
To define a web service, follow these steps:
- Using the Workbench access a node and navigate to
the transport panel and click the New
button to bring up a transport definition
panel.
- In the Name parameter, type a
unique name for the transport.
A web services transport name can be up to 64 characters in length and can include letters, numbers, and the underscore character. You will not be able to type invalid characters. For example, spaces are not allowed. You will not be able to insert a space in the name. - Use the Type down-arrow, and then
select WS_SOAP.
The Transport window changes to accommodate the definition of a WS_SOAP transport.
Parameters tab
| Parameter | Description |
|---|---|
| URL | Required. A URL to validate. This URL value can be a WSDL address or the actual web service address (for example, the location URL of the WSDL). If the URL contains a hostname, you must make sure the node is configured to use a DNS server. For more information, see Setting the DNS server for host name resolution. The URL value is only used to validate that you are able to connect to the Web service URL. This URL is not used when executing a web service call from a trigger/transport map. |
| User | Optional. This is the credential that the Transaction Server will use to access the web service. |
| Password | Optional. This is the password associated with the user credential. |
| The next 4 fields contained within the SSL section of the transport definition panel are used to specify keystore information that is used when establishing a secure HTTP connection with a web server. The fields are optional however all fields are required to be specified if used. | |
| Keystore | Specify the location of the keystore file in the staging directory that contains the client certificate to be used if requested by the server. The store should be in java key store (JKS) format. You can use the file chooser button to bring up a dialog to select the file from the staging directory. The location is specified relative to the root of the staging directory. |
| Keystore Password | Specify the password used to access the keystore |
| Truststore | Specify the location of the truststore file in the staging directory that contains trusted Certificate Authority (CA) certificates. The store should be in JKS format. You can use the file chooser button to select the file from the staging directory. |
| Truststore Password | Specify the password used to access the truststore. |