Property Name | Description | |
jms.async | Indicates whether this is a synchronous or asynchronous request/reply. This run-time property does not affect a JMS message header field If the web service connector calls an In-Out operation and you want Integration Server to write the request message to the client side queue when the JMS provider is not available, you must pass jms.async= true into transportHeaders. Additionally, to use the client side queue, the Use CSQ property must be set to true for the JMS binder. For information about how to retrieve the response to an asynchronous response, see
Asynchronously Invoking an In-Out
Operation. | |
Value | Description | |
true | Indicates this is an asynchronous request/reply. Integration Server does not wait for a response message before executing the next step in the flow service. If jms.async is true, Integration Server ignore the timeout value passed in to the web service connector. | |
false | Default. Indicates this is a synchronous request/reply. Integration Server waits for a response before executing the next step in the flow service. | |
jms.deliveryMode | Specifies the message delivery mode for the message. Integration Server uses this value to set the JMSDeliveryMode header. Specify one of the following values: | |
Value | Description | |
PERSISTENT | Indicates the request message is persistent. | |
2 | Default. Indicates the request message is persistent. | |
NON_PERSISTENT | Indicates the request message is not persistent. | |
1 | Indicates the request message is not persistent. | |
Note: If the jms.deliveryMode is not one of the above values, Integration Server ignores the name/value pair and uses the default value of 2. | ||
jms.messageType | Specifies the message type for the request message sent by the web service connector. Specify one of the following: BytesMessage TextMessage The message type specified by jms.messageType overwrites the default message type set by the watt.server.soapjms.defaultMessageType configuration parameter. Sending a TextMessage can be useful for debugging purposes because the resulting message will be a human-readable format. The message type of the request message determines the message type of the response message. Note: If the jms.messageType value is not BytesMessage or TextMessage, Integration Server ignores the name/value pair and uses the default value of BytesMessage. | |
jms.timeToLive | Length of time, in milliseconds, that the JMS provider retains the message. A value of 0 means that the message does not expire. The JMS provider uses this value to set the JMSExpiration header in the sent JMS message. Note: If the jms.timeToLive value is not a valid Long, Integration Server ignores the property and uses the default value of 0. | |
jms.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. Integration Server uses this value to set the JMSPriority header. Note: If the jms.priority value is not a value between 0 and 9, Integration Server ignores the property and uses the default value of 4. |