Integration Server 10.11 | Publish-Subscribe Developer’s Guide | Understanding Join Conditions | Join Types
 
Join Types
The join type that you specify for a join condition determines whether Integration Server needs to receive all, any, or only one of the documents to execute the trigger service. The following table describes the join types that you can specify for a condition.
Join Type
Description
All (AND)
Integration Server invokes the associated trigger service when the server receives an instance of each specified publishable document type within the join time-out period. The instance documents must have the same activation ID. This is the default join type.
For example, suppose that a join condition specifies document types documentA and documentB and documentC. Instances of all the document types must be received to satisfy the join condition. Additionally, all documents must have the same activation ID and must be received before the specified join time-out elapses.
Any (OR)
Integration Server invokes the associated trigger service when it receives an instance of any one of the specified publishable document types.
For example, suppose that the join condition specifies document types documentA or documentB or documentC. Only one of these documents is required to satisfy the join condition. Integration Server invokes the associated trigger service every time it receives a document of type documentA, documentB, or documentC. The activation ID does not matter. No time-out is necessary.
Only one (XOR)
Integration Server invokes the associated trigger service when it receives an instance of any of the specified document types. For the duration of the join time-out period, Integration Server discards (blocks) any instances of the specified publishable document types with the same activation ID.
For example, suppose that the join condition specifies document types documentA or documentB or documentC. Only one of these documents is required to satisfy the join condition. It does not matter which one. Integration Server invokes the associated trigger service after it receives an instance of one of the specified document types. Integration Server continues to discard instances of any qualified document types with the same activation ID until the specified join time-out elapses.
Tip:
You can create an Only one (XOR) join condition that specifies only one publishable document type. For example, you can create a condition that specified documentA and documentA. This condition indicates that Integration Server should process one and only one documentA with a particular activation ID during the join time-out period. Integration Server discards any other documentA documents with the same activation ID as the first one received.