Field | Description |
Alias | Name of the JMS provider web service endpoint alias. The alias name cannot include the following special characters: # ©\ & @ ^ ! % * : $ . / \ \ ` ; , ~ + = ) ( | } { ] [ > < " |
Description | A description for the endpoint alias. |
Type | Specifies the type - Provider |
Field | Description |
Delivery mode | The message delivery mode for the request message. This is the delivery mode that web service clients must specify in the JMS message that serves as the request message for the web service. You can select one of the following modes: PERSISTENT. Specifies that the request message should be persistent. The message is not lost if the JMS provider fails. NON_PERSISTENT. Specifies that the request message is not persistent. The message might be lost if JMS provider fails. |
Time to live | The number of milliseconds that can elapse before the request message expires on the JMS provider. If you specify a value 0, it indicates that the message does not expire. |
Priority | Specifies the message priority. The JMS standard defines priority levels from 0 to 9, with 0 as the lowest priority and 9 as the highest. |
Reply to name | Name or lookup name of the destination to which the web service sends a response (reply) message. Specify a name if the JMS connection alias used by the SOAP-JMS trigger connects to the webMethods Broker natively. Specify a lookup name if the JMS connection alias uses JNDI to retrieve a connection factory that is then used to connect to the JMS provider. |
Reply to type | Type of destination to which the web service sends the response (reply) message. Specify the destination type if the following are true: The web service descriptor to which the endpoint alias is assigned use the In-Out message exchange pattern. The JMS connection alias specified by the SOAP-JMS trigger connects to the webMethods Broker natively. On the webMethods Broker, a queue and topic can have the same name. You must specify Reply To Type to indicate to which destination the reply will be sent. Select one of the following destination types: Queue. Specifies that the web service sends the response message to a particular queue. Topic. Specifies that the web service sends the response message to a particular topic. |
Field | Description |
Include connection factory name | When selected, includes the connection factory name in the JMS URI. |
Include JNDI parameters | When selected, includes the JNDI parameters in the JMS URI. |
Field | Description |
Keystore alias | Alias of the keystore containing the private key used to decrypt the inbound SOAP request or sign the outbound SOAP response. Note: The provider must have already given the consumer the corresponding public key. |
Key alias | Alias of the private key used to decrypt the request or sign the response. The key must be in the keystore specified in Keystore alias. |
Truststore alias | The alias for the truststore that contains the list of CA certificates that API Gateway uses to validate the trust relationship. |
Timestamp precision | Specifies whether the timestamp is precise to the second or millisecond. If you set the precision to milliseconds, API Gateway uses the timestamp format yyyy-MM-dd'T'HH:mm:ss:SSS'Z'. If you set the precision to seconds, API Gateway uses the timestamp format yyyy-MM-dd'T'HH:mm:ss'Z'. If you do not select a precision value, API Gateway uses the value specified for the watt.server.ws.security.timestampPrecisionInMilliseconds parameter. |
Timestamp time to live (seconds) | Specifies the time-to-live value for the outbound message in seconds. API Gateway uses the time-to-live value to set the expiry time in the Timestamp element of outbound messages. The Timestamp Time to Live value must be an integer greater than 0. If you do not specify a Timestamp time to live value, API Gateway uses the value specified for the watt.server.ws.security.timestampTimeToLive parameter. Note: The Timestamp time to live value should be greater than the Time to live value specified under JMS transport properties. |
Timestamp maximum skew (seconds) | Specifies the maximum number of seconds that the web services client and host clocks can differ and still allow timestamp expiry validation to succeed. Specify a positive integer or zero. API Gateway uses the timestamp maximum skew value only when you implement WS-Security via a WS-Policy. API Gateway validates the inbound SOAP message only when the creation timestamp of the message is less than the sum of the timestamp maximum skew value and the current system clock time. If you do not specify a timestamp maximum skew value, API Gateway uses the value specified for the watt.server.ws.security.timestampMaximumSkew parameter. |