Contraining bpel processes to single instances

[ruperty]

Hi,

I have a scenario where I am processing a new job and an update job (in same bpel process), from an inbound queue. It is necessary for the new job to finish before the update starts.

So, I think what I want to do is constrain the process to only run one instance of the process at a time. Is it correct that I can do this by setting the "max concurrency limit" in the QoS config (as opposed to the thread count at the bpel SE level)?

Also, if the bpel se is clustered will this concurrency limit apply across the clsuter, that is, there will only be one instance of the process running at any one time?

Regards,
Rupert

[Philip Varghese]

Some javascript/style in this post has been disabled (why?)

Hi,
answers inlined..

ruperty wrote:

Hi,

I have a scenario where I am processing a new job and an update job (in same
bpel process), from an inbound queue. It is necessary for the new job to
finish before the update starts. 

So, I think what I want to do is constrain the process to only run one
instance of the process at a time. Is it correct that I can do this by
setting the "max concurrency limit" in the QoS config (as opposed to the
thread count at the bpel SE level)?
  

Correct, setting the "max concurrency limit" to 1 will enable serial order processing , refer to link http://wiki.open-esb.java.net/Wiki.jsp?page=SerialOrderConfiguration

Also, if the bpel se is clustered will this concurrency limit apply across
the clsuter, that is, there will only be one instance of the process running
at any one time?
  

No, concurrency limit does not apply across cluster instances...

Regards,
Rupert 


-----
Regards,
 
Rupert Young
Principal Architect
ReStart Consulting Ltd
 UK: [phone]
 UK: [phone]
http://www.restartconsulting.com