Designer 10.15 | webMethods Service Development Help | Properties | JMS Trigger Properties | Universal Messaging and webMethods Broker Properties
 
Universal Messaging and webMethods Broker Properties
In the Properties view, under Universal Messaging and webMethods Broker, you can configure properties specific to Universal Messaging or webMethods Broker when Universal Messaging or Broker is used as the JMS provider for the trigger.
Note:webMethods Broker is deprecated.
Property
Description
Max prefetch size
When the JMS provider is Universal Messaging, specifies the maximum number of messages retrieved from Universal Messaging in each polling request. Only concurrent, non-transacted JMS triggers can prefetch messages from Universal Messaging. You must specify a value greater than 1.
When the JMS provider is webMethods Broker, specifies the maximum number of messages that the webMethods Broker API for JMS will retrieve and cache per request for this trigger. Using prefetch cache can speed up the retrieval of messages from webMethods Broker. If you specify a value of -1 for this setting, Integration Server uses the value specified on the watt.server.jms.trigger.maxPrefetchSize parameter for this setting.
Because messages will be placed in Integration Server memory, you may want to decrease this setting if this trigger receives very large messages. Otherwise, memory issues can occur. This setting applies only if this trigger connects to Universal Messaging or webMethods Broker .
The default is 10 messages.