Trigger Processing Mode

May 25, 2011

—

in Broker, IntegrationServer, webMethods Administration

Hey Guys,Today I am going to post a doubt to discuss. I have faced this question a number of time and i don’t find me giving a very satisfactory answer.

Question is :-

What is the difference/similarities between IS Trigger processing

If mode is set to serial
Or if mode is set to Concurrent but with Maximum Thread set to 1.

Something which i found out is if we have concurrent with max thread as 1, then this will indicate to Broker that it can hand out documents to multiple IS instances at the same time without any document order maintained.Please post your thoughts in comment section.

Happy Learning 🙂

Comments

4 responses to “Trigger Processing Mode”

Mangat

May 31, 2011

Comments from shashank patel – He explained difference with situation.

Situation: Clustered environment with 2 ISs and a trigger on both IS. This Cluster will have a client on Broker.

If a trigger is set to Serial – then, only 1 document is processed at a time. Either of IS can pull document from Client queue to its Trigger queue. But, never both.

If a trigger is set to Concurrent – and max Threads =1 ; Then, both ISs can pull 1 document each at the same time from Client Queue towards their respective Trigger queues.

Reply
1. Sandeep Potdar
  
  October 23, 2015
  
  I concur. We’ve observed this difference at a customer both Shashank & I worked together at.
  
  Reply
Sandeep

October 25, 2015

I think on the backend implementation “serial” corresponds to a Queue whereas “concurrent” corresponds to a Topic, for the trigger client queues created.

Reply
1. MANGAT RAI
  
  October 28, 2015
  
  you can say that broadly. but underlying it is complex. you can have a concurrent trigger on queue and serial on topic.
  
  Reply