Guidelines for Configuring Batch Processing
When configuring JMS trigger for batch processing, keep the following in mind:
The trigger service must be coded to handle multiple messages as input. That is, the trigger service must use the
pub.jms.batchTriggerSpec as the service signature.
When receiving a batch of messages,
Integration Server evaluates the local filter in the routing rule against the first message in the batch only.
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 reuse of transacted JMS sessions. If the JMS provider does not support reuse of transacted JMS sessions, set
Max batch processing 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, webMethods Universal Messaging version 9.5 SP1 and higher, and webMethods Nirvana version 7 and higher support the reuse of transacted JMS sessions.
A JMS trigger that contains an All (AND) or Only one (XOR) join cannot use batch processing.
SOAP-JMS triggers cannot process messages in batches.
