I did set up a spring Batch job, it runs fine on a single JVM. But I need it to be deployed on to a clustered environemnt. I am using spring task scheduler to schedule the job.
Two suggestions:
Both of these approaches will ensure your task is getting picked up just once.
The first approach requires the (tedious) Quartz DB setup but then you can connect your unclustered Websphere webapps directly.
The second approach doesn't require persistent store and via the Apache Camel wrapper makes the setup a breeze.
I have finally got it working with EJB persistent timers launching the spring batch job. The transaction type for those EJB timers have defined as Bean Transaction, so it is not container managed. The Websphere scheduler takes care of the clustering with EJB timers. So the spring batch job gets kicked off on only one server at a time.
SpringBatch does not support any means of clustered executions. If you want your tasks to be clustered you should check products for it, I can suggest you to have look at hazelcast.