The short version of the question is; with APM 12.9, have any customers come up with a creative way to sequentially run Data Import jobs; where one job runs the very second a different job finishes?

With 11.3.4, I had a batch file that called two different importer jobs. With the way 11.3.4 worked, the Data Importer EXE would not “exit” until it completed running the first job. So the second line (second job) would not get called until the first job finished running. I had a Windows Scheduled Task setup to call the batch file.

With 12.9, I created a batch file that calls the two jobs via the Import Processor command. But, with the Import Processor EXE, it exits as soon as it is “submits” the job; meaning the second line in the batch file (the second job) gets submitted before the first job runs/finishes.

Using the Schedule function of the Data Importer 12.9 does not satisfy the need, as the time it takes the first job to run varies.

For the purposes of this question assume the process to create the data files is automated. There is no place in the process for human manipulation or adjustment.

Anyone have any feedback for Ryan?

Thanks

Data Importer - sequential jobs

This question is Not Answered.(Mark as assumed answered)

Ryan Guise Feb 17, 2015 2:03 PM

The short version of the question is; with APM 12.9, have any customers come up with a creative way to sequentially run Data Import jobs; where one job runs the very second a different job finishes?

With 11.3.4, I had a batch file that called two different importer jobs. With the way 11.3.4 worked, the Data Importer EXE would not “exit” until it completed running the first job. So the second line (second job) would not get called until the first job finished running. I had a Windows Scheduled Task setup to call the batch file.

With 12.9, I created a batch file that calls the two jobs via the Import Processor command. But, with the Import Processor EXE, it exits as soon as it is “submits” the job; meaning the second line in the batch file (the second job) gets submitted before the first job runs/finishes.

Using the Schedule function of the Data Importer 12.9 does not satisfy the need, as the time it takes the first job to run varies.

For the purposes of this question assume the process to create the data files is automated. There is no place in the process for human manipulation or adjustment.

Using the ImportProcessor command, and some clever scripting, you can actually retrieve the jobid that was submitted, and then loop, querying for the status of that job id (via the import processor), and when it comes back as complete, move on to the next job.  Have a look at this set of documentation.  (How to Submit a Data Import Using the Command Line - CA Service Management - 14.1 - CA Wiki).  Yes, its on 14.1, but should work on 12.9 as well.

Rick