webMethods 10.2 | Service Development Help | Working with webMethods Messaging Triggers | About Join Time-Outs | Join Time-Outs for Only One (XOR) Join Conditions
 
Join Time-Outs for Only One (XOR) Join Conditions
A join time-out for an Only one (XOR) join condition specifies how long Integration Server discards instances of the other documents in the condition. When Integration Server pulls the document from the webMethods messaging trigger queue, it determines which condition the document satisfies. If that condition is an Only one (XOR) condition, the Integration Server executes the service specified in the condition. When it pulls the document from the webMethods messaging trigger queue, Integration Server starts the time-out period. For the duration of the time-out period, Integration Server discards any documents of the type specified in the join condition. Integration Server discards only those documents with same activation ID as the first document.
When the time-out period elapses, the next document in the webMethods messaging trigger queue that satisfies the Only one (XOR) condition causes the trigger service to execute and the time-out period to start again. Integration Server executes the service even if the document has the same activation ID as an earlier document that satisfied the join condition. Integration Server generates a journal log message when the time-out period elapses for an Only one (XOR) condition.

Copyright © 2017-2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release