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 - Consumer |
Execute ACL | Specifies the ACL that governs which user groups on your server can use this web service endpoint alias. Select an ACL from the drop-down list. By default, only members of groups governed by the Internal ACL can use this alias. |
Field | Description |
JNDI properties | Select this option if you want to connect to the JMS provider using a connection factory. Provide the following information: ![]() ![]() Note: You have to specify a connection factory only if the WSDL document used to create the consumer web service descriptor does not specify a connection factory or you want to overwrite the connection factory. |
JMC connection alias | Select this option if you want to connect to the JMS provider using a JMS connection alias. Provide the following information: ![]() |
Field | Description |
Username | The user name to include with the UsernameToken. |
Password | The password to include with the UsernameToken (must be plain text). |
Retype password | Re-type the above password. |
Keystore alias | Alias to the keystore that contains the private key used to: ![]() ![]() ![]() Note: To verify messages from this consumer, the web services provider must have a copy of the corresponding public key. |
Key alias | Alias to the private key used to sign or include X.509 authentication token for outbound SOAP messages or decrypt inbound SOAP responses. 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. |