|
Url
|
External service address. |
|
Username
|
Login or username to access the service. |
|
Password
|
Password associated with the username. |
|
Connected gateway
|
Select zero, one or several gateways to receive the response from the http server. |
|
SoapFault strategy
|
If an error occurs during processing, the response to a SOAP message is a SOAP fault element in the body of the message, and the fault is returned to the sender of the SOAP message.
Standard Soap protocol suggests that they should be sent with a 500 HTTP error code, but some systems still send it with a HTTP 200 ok return code.
Choose here how you want to handle your Soap Fault messages:
1) You can treat them as normal messages and therefore, no special rules applies. If they arrive with a HTTP 500 error code, you should add 500 in the list of valid return code. Otherwise, they will end up in error, as normal messages.
2) You can always treat them as Error. Even if we receive them via a valid HTTP response code, the message will be put in error.
3) You can always treat them as Successful messages. Even if we receive them via a invalid HTTP return code, the message will be put in success and possibly transferred to a connected gateway.
|
|
Valid HTTP return code
|
Comma separated list of expected return Http code. If the return code is not in the list, the message is set in error. The default is '200,201,202,204,205'. |
|
Success expression
|
The success expression is a regex. If the response doesn't match the success expression, the message is flagged with 'error' status. |
|
Response filename
|
You can specify a filename that will be associated with the server response. Default is 'attachment'. |
|
User Metadata Transfer Strategy
|
The strategy that will be used to transfer the user metadata to the response message created in the connected gateways. |
|
Retry strategy
|
Allows you to determine what to do if call to remote server fails. If 'No retry' is chosen, the message will be put immediately in error. Other values allow to make some retries before setting the message in error.
- No retry
-
Keep trying for 3 minutes
- Will retries after 10sec, 40sec, 1, and 2 minutes.
-
Keep trying for 15 minutes
- Will retries after 2, 4, 7, 10 and 15 minutes.
-
Keep trying for 1 hour
- Will retries after 2, 4, 8, 15, 30 and 60 minutes.
-
Keep trying for 3 hours
- Will do 6 retries in the first hour, then every hour.
-
Keep trying for 8 hours
- Will do 6 retries in the first hour, then every hour.
-
Keep trying for 1 day
- Will do 4 retries in the first hour, then every hour.
-
Keep trying for 3 days
- Will do 5 retries in the first 2 hours, then every 3 hours.
-
Keep trying for 5 days, once a day
- Will do One retry every day for 5 days at the same time as the first try.
-
Keep trying for 7 days
- Will do 5 retries in the first hour, then every 3 hours for 3 days, then every 6 hours.
|
|
Filename
|
Filename of the outgoing message [with extension if applicable]. If empty, we will apply the default settings. |
|
Http Method
|
You can specify the http method to call. The default is POST. |
|
Timeout
|
Timeout for connection in milliseconds. Must be between 10000 and 240000. |
|
Http headers
|
You can add specific http header. This accepts metadata. |
|
SOAPAction http header
|
Value of the SOAPAction http header. |
|
SOAP Attachments
|
Allows to specify one or more soap attachments, based on SOAP with Attachments (SwA) using MIME. Name will be sent as 'ContentId' of the mime part of the attachment and Value must contain the name of the metadata containing the String or byte array body of the attachment. |
|
Trust level
|
The trust level defines the level of security used in the SSL handshake. Relax = No certificate verification, Standard = trusting certificates in environment certificates as well as known CA's, Paranoiac = only trusts certificates defined in the environmnent certificates. Mutual = requires 2-way authentication. |
|
Authentication method
|
You can select from FORM, BASIC, DIGEST, CERT or ANY. CERT is 2-way SSL authentication. ANY is BASIC, DIGEST or NTLM depending on the server response. |
|
Preemptive authentication
|
Allows to send authentication information with the first http request (to avoid making a second request). Only for BASIC or DIGEST authentication. |
|
Login url
|
If authentication method is FORM. |
|
Authentication form fields
|
When using FORM authentication, you can add specific authentication form fields to the authentication call. This accepts metadata. |
|
2-way auth. certificate
|
If CERT authentication is used (2-way SSL authentication), this allows to select the key pair to use from the environment certificate. |
|
Soap headers
|
You can add specific soap header. This accepts metadata. |
|
Soap version
|
Defined the standard version of the remote SOAP service. |
|
Ws-Security profile
|
Ws-Security profile defines the type of security required to call the SOAP service. |
|
Ws-Security Username
|
Ws-Security username is used in the username/token digest profile. |
|
Ws-Security token
|
Ws-Security token is used in the username/token digest profile. |
|
Ws-Security signing key
|
Ws-Security username is used in the X.509 signing profiles. |
|
Ws-Security encryption certificate
|
Ws-Security username is used in the X.509 encryption profiles. |