Drawbacks of this approach
Limitation from Active Batch Framework
1.BatchJob - This will be responsible to invoke the batch job for first time.For Ex-
This step is using the web service to invoke a batch job.
2. Log step- This will just log the values which will make the execution tracking easier.
3.For Loop Funtionality
This Active batch object allows to iterate over certain number of steps.
This job contains number of sub steps. This job is responsible for -
1.GetBatchJobStatus- This will fetch the job status from the executing job. This job actually depends on logic on how the batch is executing and how we can get the Job status. In this example it was implemented by calling WCF service and this service returns the job status.
2.Log - This is important which allows to log the response of GetBatchJobStatus, which will help in troubleshooting.
3.IfElse-This object will contain the functionality which checks for the response and compare this response with a pre-defined response and depending on the value either waits and continue iterates the loop as in second case in below-
4.Log step- This will just log the values which will make the execution tracking easier.
This job step exits the overall job with appropriate job status (Failure/Success).This should generally be failure as the job could not complete even are 100 iterations of 5 sec(configured) wait time. Depending on functionality this may be implemented in different way.