Cloud Application Integration (On-Premises) : Service Development : Working with webMethods Messaging Triggers : About Join Time-Outs
About Join Time-Outs
 
Join Time-Outs for All (AND) Join Conditions
Join Time-Outs for Only One (XOR) Join Conditions
Setting a Join Time-Out
When you create a join condition using an All (AND) join or an Only one (XOR), you need to specify a join time-out. A join time-out specifies how long Integration Server waits for the other documents in the join condition. Integration Server uses the join time-out period to avoid deadlock situations (such as waiting for a document that never arrives) and to avoid duplicate service invocation.
How the join time-out affects document processing by the webMethods messaging trigger is different for each join type.
*For an All (AND) join, the join time-out determines how long Integration Server waits to receive an instance of each publishable document type in the condition.
*For an Only one (XOR) join, the join time-out determines how long Integration Server discards instances of publishable document types in the condition after it receives an instance document of one of the publishable document types.
*An Any (OR) join condition does not need a join time-out. Integration Server treats an Any (OR) join condition like a webMethods messaging trigger with multiple simple conditions that all use the same trigger service.
Join Time-Outs for All (AND) Join Conditions
Join Time-Outs for Only One (XOR) Join Conditions
Setting a Join Time-Out
Copyright © 2015- 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback