triggerName | String Fully qualified name for the JMS new trigger. Names use any combination of letters, and/or the underscore character. Make sure to specify the name of the folder and subfolder in which you want to save the JMS trigger.
| |||||
package | String Name of the package in which you want to save the trigger. | |||||
aliasName | String Name of the JMS connection alias that you want this JMS trigger to use to receive messages from the JMS provider. The JMS connection alias must already exist at the time this service executes. Although a JMS connection alias does not need to be enabled at the time you create the JMS trigger, the JMS connection alias must be enabled for the JMS trigger to execute at run time. A transacted JMS connection alias cannot be assigned to a JMS trigger if a cluster policy is applied to the connection factory used by the JMS connection alias. | |||||
jmsTriggerType | String Type of JMS trigger. Specify: Standard to create a standard JMS trigger. This is the default. SOAPJMS to create a SOAP-JMS trigger. | |||||
properties | Document Optional. Properties that you want to assign to the JMS trigger. | |||||
Key | Description | |||||
enabled | String Flag indicating whether the new JMS trigger is enabled or disabled. Set to: true to create the JMS trigger in an enabled state. false to create the JMS trigger in a disabled state. This is the default. | |||||
joinTimeout | String Optional. Number of milliseconds Integration Server waits for additional messages to fulfill the join. Integration Server starts the join time-out period when it receives the first message that satisfies the join. Set joinTimeout to -1 to indicate that the join condition never expires. The default is one day (86400000 milliseconds). You need to specify a joinTimeout only when the joinType is AND or XOR. You do not need to specify a join time-out for an OR join.
| |||||
joinType | String Specifies the join type for this standard JMS trigger. The join type indicates whether Integration Server needs to receive messages from all, any, or only one of destinations to execute the trigger service. You only need to set joinType if the JMS trigger receives messages from multiple destinations.
| |||||
Set to: N/A to indicate that this JMS trigger does not have a join. That is, the JMS trigger receives messages from one Destination only. AND to invoke the trigger service when the standard JMS trigger receives a message from every destination within the join time-out period. The messages must have the same activation. For more information about activation IDs, see Using webMethods Integration Server to Build a Client for JMS. OR to invoke the trigger service when the standard JMS trigger receives a message from any of the specified destinations.
XOR to invoke the trigger service when it receives a message from any of the specified destinations. For the duration of the join time-out period, the Integration Server discards any messages with the same activation that the trigger receives from the specified destinations. | ||||||
maxRetryAttempts | String Optional. Maximum number of times Integration Server should re-execute the trigger service when the trigger service ends because of a transient error that causes an ISRuntimeException. The default is 0 attempts (indicating the trigger service does not retry)
| |||||
retryInterval | String Optional. Length of time Integration Server waits between retry attempts. The default is 10 seconds.
| |||||
onTransientError | String Flag indicating how Integration Server handles transient errors for the JMS trigger. For a non-transacted JMS trigger, indicates how Integration Server handles a retry failure for a JMS trigger. A retry failure occurs when Integration Server reaches the maximum number of retry attempts and the trigger service still fails because of an ISRuntimeException. For a transacted JMS trigger, indicates how Integration Server handles a transient error that occurs during service execution, resulting in the entire transaction being rolled back. | |||||
Specify one of the following: Throw Exception/ Recover Only This is the default. For a non-transacted JMS trigger, indicate that Integration Server throws a service exception when the last allowed retry attempt ends because of an ISRuntimeException. For a transacted JMS trigger, indicate that Integration Server recovers the message back to the JMS provider. Integration Server receives the message again almost immediately. Suspend and Retry Later/ Suspend and Recover For a non-transacted JMS trigger, indicate that Integration Server suspends the trigger when the last allowed retry attempt ends because of an ISRuntimeException. Integration Server retries the trigger service at a later time when the resources needed by the trigger service become available. For a transacted JMS trigger, indicate that Integration Server suspends the JMS trigger and then recovers the message back to the JMS provider. Integration Server executes the trigger service at a later time when the resources needed by the trigger service become available. Selecting Suspend and Retry Later/ Suspend and Recover also instructs Integration Server to suspend the trigger when a transient error occurs during trigger preprocessing. For more information about transient error handling during trigger preprocessing, see webMethods Service Development Help. | ||||||
resumeTaskSvcName | String Optional. Fully qualified name of the service that Integration Server executes when one of the following occurs: The trigger service ends because of a retry failure and onTransientError is set to Suspend and Retry Later/Suspend and Recover. The trigger service is part of a transacted JMS trigger and onTransientError property is set to Suspend and Retry Later/Suspend and Recover. The document resolver service used for exactly-once processing (dupResolverSvcName) ends because of a run-time exception and the watt.server.trigger.preprocess.suspendAndRetryOnError is set to true. | |||||
isConcurrent | String Flag indicating whether the JMS trigger uses a concurrent processing mode or a serial processing mode. Set to: true to specify a concurrent processing mode. Integration Server processes multiple messages for this trigger at one time. false to specify a serial processing mode. Integration Server processes messages received by this trigger one after the other. This is the default. | |||||
suspendOnError | String Flag indicating whether Integration Server suspends the JMS trigger when an exception occurs during trigger service execution. Set to: true to suspend the trigger when a trigger service ends with a fatal error. false to not suspend the JMS trigger when a trigger service ends with a fatal error. This is the default. | |||||
maxExecutionThreads | String Optional. Maximum number of messages that Integration Server can process concurrently on each connection for this trigger. maxExecutionThreads must be greater than or equal to connectionCount. The default is 1.
| |||||
maxBatchSize | String Optional. Maximum number of messages that the trigger service can receive at one time. If you do not want the trigger to perform batch processing, leave this property set to 1. The default is 1. A transacted JMS trigger can be used for batch processing if the JMS connection alias used by the trigger connects to a JMS provider that supports the reuse of transacted JMS sessions. If the JMS provider does not support the reuse of transacted JMS sessions, set maxBatchSize to 1. Consult the documentation for your JMS provider to determine whether or not the JMS provider supports the reuse of transacted JMS sessions. Note that webMethods Broker version 8.2 and higher and webMethods Universal Messaging version 9.5 support the reuse of transacted JMS sessions.
| |||||
dupDetection | String Flag indicating whether exactly-once processing is enabled for the JMS trigger. Set to: true to specify that exactly-once processing is provided for messages received by this trigger. false to specify that exactly-once processing is not provided for messages received by this trigger. This is the default. | |||||
dupHistory | String Flag indicating whether a document history database will be maintained and used to determine whether a message is a duplicate. Set to: true to indicate that Integration Server uses a document history database as part of exactly-once processing. false to indicate that Integration Server does not use a document history database as part of exactly-once processing. This is the default. | |||||
dupHistoryTTL | String Optional Number of milliseconds that the document history database maintains an entry for a document processed by this trigger. The default is 2 hours (7200000 milliseconds). | |||||
dupResolverSvcName | String Optional. Specifies the service that you created to determine whether message's status is New, Duplicate, or In Doubt. | |||||
prefetchSize | String Optional. Specifies the maximum number of messages Integration Server attempts to retrieve for this JMS trigger when it requests more messages from the webMethods Broker. The default is 10.
| |||||
acknowledgeMode | String Indicates how the JMS trigger acknowledges messages it receives to the JMS provider.
Set to: CLIENT_ACKNOWLEDGE to acknowledge or recover the message only after the JMS trigger processes the message completely. This is the default. AUTO_ACKNOWLEDGE to automatically acknowledge the message when it is received by the JMS trigger. The Integration Server will acknowledge the message before the trigger completes processing. The JMS provider cannot redeliver the message if Integration Server becomes unavailable before message processing completes. DUPS_OK_ACKNOWLEDGE to lazily acknowledge the delivery of messages. This may result in the delivery of duplicate messages. | |||||
executeUser | String Optional. Name of the user account whose credentials Integration Server uses to execute a service associated with the JMS trigger. You can specify a locally defined user account or a user account defined in a central or external directory. The default is Administrator. | |||||
connectionCount | String Optional. Specifies the number of connections a concurrent JMS trigger can use to retrieve messages from the JMS provider. connectionCount must be less than or equal to maxExecutionThreads. The default is 1.
| |||||
destinations | Document List Destinations from which the JMS trigger receives messages.
| |||||
Key | Description | |||||
destination | String Name or lookup name of the Destination from which you want the JMS trigger to receive messages. Specify the lookup name of the Destination object when the JMS connection alias uses JNDI to retrieve administered objects. Specify the provider-specific name of the Destination when the JMS connection alias uses the native webMethods API to connect directly to the webMethods Broker. | |||||
destinationType | String Optional. Type of destination from which the JMS trigger receives messages. Set to: Queue to specify that the destination is a queue. This is the default. Topic to specify that the destination is a topic. | |||||
messageSelector | String Optional. Filter used to receive a subset of messages from the specified destination. A message selector allows a client to filter the messages it wants to receive by use of a SQL92 string expression in the message header. That expression is applied to properties in the message header (not to the message body content) containing the value to be filtered. | |||||
durableSubscriber Name | String Optional. Name of the durable subscriber that you want to create for this JMS trigger on the JMS provider. A durable subscriber creates a durable subscription on the JMS provider. A durable subscription allows the subscriber to receive all the messages published on a topic, including those published while the subscriber is inactive.
| |||||
durableSubscriber NoLocal | String Optional. Flag indicating whether the JMS trigger ignores messages sent by the same Integration Server on which the JMS trigger resides. Set to: true to indicate that the JMS trigger ignores messages sent by the same Integration Server on which the JMS trigger resides. false to indicate that the JMS trigger receives and processes messages sent by the same Integration Server on which the JMS trigger resides. This is the default.
| |||||
routingRules | Document List Optional. Routing rules for messages received by this standard JMS trigger.
| |||||
Key | Description | |||||
ruleName | String Name for the routing rule. | |||||
serviceName | String Fully qualified name of the service Integration Server invokes when it receives a message from one of the specified destinations. | |||||
filter | String Optional. Filter that you want Integration Server to apply to messages the JMS trigger receives. A filter specifies criteria for the contents of the message body. Integration Server applies a local filter to message after the JMS trigger receives the message from the JMS provider. | |||||
|