Software AG Products 10.7 | Service Development Help | Properties | JMS Trigger Properties | Message Processing Properties
 
Message Processing Properties
In the Properties view, under Message processing, you enable or disable a JMS trigger, set the transaction type, specify the acknowledgement mode, expiration, and execution user credentials.
Property
Description
Processing mode
Specifies how Integration Server processes messages received by the JMS trigger. You can specify serial or concurrent message processing.
Select...
To...
Serial
Specify that Integration Server should process messages received by the trigger one after the other.
Concurrent
Specify that Integration Server should process multiple messages for this trigger at one time.
Max execution threads
Specify the maximum number of messages that Integration Server can process concurrently. Integration Server uses one thread to process each message. The default is 1 server thread.
Max batch messages
Specify the maximum number of messages that the trigger service can receive at one time. If you do not want the trigger to perform batch processing, leave this property set to 1. The default is 1.
Note:
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, and Universal Messaging version 9.5 SP1and higher, and webMethods Nirvana version 7 and higher support the reuse of transacted JMS sessions.
Note:Designer does not display this property for a SOAP-JMS trigger because SOAP-JMS triggers cannot process batches of messages
Connection count
Specifies the number of connections this trigger makes to the JMS provider. Multiple connections can improve trigger throughput, but keep in mind that each connection requires a dedicated Integration Server thread, regardless of the current throughput. The default is 1.
Note:
If you specify a connection count greater than one, the alias associated with this trigger must be configured to create a new connection for each trigger. For more information about JMS connection aliases, refer to webMethods Integration Server Administrator’s Guide.