title: Best practice/design pattern to control spring batch job execution/scheduling
body: <p>We have few job which are dependent on each other where job 2 cannot start until job 1 completes like wise job 4 cannot start until job 3 completes. Is there any best practice to follow this? All this jobs have some kind of polling to either file system or db, so I am thinking of using spring integration to send job launch events but my confusion is, should I package all them together and have one parent spring integration application context which can control the job execution  or not?</p>
  
  <p>Open to best practice as this we might add 3-4 more jobs later in the project. Also in future we might implement some kind of dashboard to show the status of each job and why it didnt started etc.</p>