Design a job with infinite loop
Posted: Fri Jan 18, 2013 1:41 pm
Hi,
I have a requirement where i have to design a sequence job which will keep on running and it will look for trigger file.
Trigger file will be created by another master job,which has source as MQ. This job will also keep on running and as soon as message land up to the MQ it will create trigger file.Design will be look like this:-
It will have more then 100 distinct sequences which will be always running and waiting for trigger file.Once trigger file created that particular sub sequence should start.My worry is may these infinite running jobs will eat more CPU resources and phantom process.Is it a good approach to design a flow like this.Need experts advice.
I have a requirement where i have to design a sequence job which will keep on running and it will look for trigger file.
Trigger file will be created by another master job,which has source as MQ. This job will also keep on running and as soon as message land up to the MQ it will create trigger file.Design will be look like this:-
Code: Select all
Master Seq (infinte loop)---> SubSeq1 ------> seq
(infinte loop wait for trigger)
----> SubSeq2 --------> seq
----> SubSeq3.......100 ---------> seq
It will have more then 100 distinct sequences which will be always running and waiting for trigger file.Once trigger file created that particular sub sequence should start.My worry is may these infinite running jobs will eat more CPU resources and phantom process.Is it a good approach to design a flow like this.Need experts advice.