Configuration Examples

You can review a few configuration examples to learn more about event delivery with batching.

• You can deliver each event as a JMS message within a transaction through the DeliveryMDB, which is configured to handle the messages for the ‘DELIVERY’ activation string.

  

• You can deliver, for example, 100 events which are of same event type (created out of the same integration flow) as, for example, 100 JMS messages together within a transaction through the DeliveryMDB which is configured to handle messages for activation string 'DELIVERY'.

  

• You can deliver, for example, 100 events in the order of their creation which are of same event type (created out of the same integration flow) as, for example, 100 JMS messages together within a transaction through the DeliveryMDB, which is configured to handle messages for the 'DELIVERY' activation string.
  The order of the messages is guaranteed only up to the JMS queue. It is recommended to use only one consumer to maintain the order from the JMS queue.

  

• You can deliver, for example, 100 events which are of same event type (created out of the same integration flow) as one JMS message (see Note below) within a transaction through the DeliveryMDB which is configured to handle messages for the DELIVERY activation string.
  All the event XML documents are added to an XML document to form one batch XML. The message payload will observe the Batch* variations of the event schemas returned.

  

• Deliver each event as a JMS message within a transaction through the DeliveryMDB. The DeliveryMDB is configured to handle messages for an activation string which is equivalent to that of the value in the event XML for the property Destination Name which is given in the field Destination Prop.
  • If no value is found in the event XML for the property given in the field Destination Prop, then the value in the Destination Static field is used as activation string.
  • The event delivery fails if no DeliveryMDB instance is handling the activation string obtained from the event XML.

  

• Deliver each event as one JMS message within a transaction through the DeliveryMDB, which is configured to handle messages for the activation string 'DELIVERY'. Each JMS message is expected to have four header properties, such as application, transactionStage, operator, and staticPriority for which the values are identified from the fields of same name in the event XML.
  • If no value is found (empty value or the event XML does not have such a field), then the property has no value.
  • If multiple values are found because the event field is a multiple value field then the property values are set with ‘/’ as the delimiter. Example: accountOfficers=56/34/75