Hi,

My application needs to run "groups" of jobs in sequence, but the all the jobs within
one group need to run in parallel. How do I approach this in JAL?

Thanks
George Coles

Let's say you have 5 "worker" jobs in a group.
For every group create an extra "control" job that launches other jobs in group as below

Dim( pid, number )
Run( "24x7.exe /JOB [job id 1]", "", pid )
Run( "24x7.exe /JOB [job id 2]", "", pid )
Run( "24x7.exe /JOB [job id 3]", "", pid )
Run( "24x7.exe /JOB [job id 4]", "", pid )
Run( "24x7.exe /JOB [job id 5]", "", pid )

This will start all 5 "worker" jobs concurently (parallel)

Now to create a sequential group run (group after group after group) set each "worker" job to create a unique semaphore file on job finish, and set each control file for the "following" group to watch for "previous" group files semaphore files. You can use the built-in Dependencies Editor tool to do this graphically. Make sure every "worker" job is set to run synchronously.

: Hi,

: My application needs to run "groups" of jobs in sequence, but the
: all the jobs within
: one group need to run in parallel. How do I approach this in JAL?

: Thanks
: George Coles

Thanks for the swift reply. I think I understand this,
I just downloaded the manual today. I don't want to complicate things
too much, but in my app each job is actually a windows forms application,
there are 15 copies of the app running, each one running on a different
pc, and it must run interactively, which is a bad constraint. My job control app needs to know when these apps are done, and users should
be able to kill individual jobs in the list, or all jobs if they want. Can I customize
your GUI? I have written an app that does this with sockets and WMI that has
been running for several months, but I dont see why I should maintain this
when products like yours exist.

What are the implications of this in licensing terms?

Thanks in advance,
George

: Let's say you have 5 "worker" jobs in a group.
: For every group create an extra "control" job that launches other
: jobs in group as below

: Dim( pid, number )
: Run( "24x7.exe /JOB [job id 1]", "", pid )
: Run( "24x7.exe /JOB [job id 2]", "", pid )
: Run( "24x7.exe /JOB [job id 3]", "", pid )
: Run( "24x7.exe /JOB [job id 4]", "", pid )
: Run( "24x7.exe /JOB [job id 5]", "", pid )

: This will start all 5 "worker" jobs concurently (parallel)

: Now to create a sequential group run (group after group after group) set each
: "worker" job to create a unique semaphore file on job finish,
: and set each control file for the "following" group to watch for
: "previous" group files semaphore files. You can use the built-in
: Dependencies Editor tool to do this graphically. Make sure every
: "worker" job is set to run synchronously.

You can write a custom Windows application or create a Web-based system using either COM or Java API to present job flow in a form easily understood by end-users (see 24x7 API's manuals for more info)

If you set each "worker" job to run synchronously as I previously suggested you would always know when they are done. If the total number of jobs running is big I also suggest enabling job start/finish event notifications of database type each job. This way you can have all jobs from all PC to log events into a centralized database which you can always read/monitor from any custom application. If you want to control/orchestrate all applications on multiple computers from one place consider running one central 24x7 Scheduler and running 24x7 Remote Agents on other PCs. This way you can run and control jobs remotely.

For every PC with 24x7 software installed you would need a separate installation license as well as a license for your custom application (if any) using 24x7 COM/Java API (client part). If the number of computers where you plan to install 24x7 is 10+ (also count PCs for system administrators who could monitor and manage jobs remotely using 24x7 Remote Control) consider getting a site license. The site license also includes web-base interface (Web-based Management Console) allows using API with a web-server and some other goodies.

: Thanks for the swift reply. I think I understand this,
: I just downloaded the manual today. I don't want to complicate things
: too much, but in my app each job is actually a windows forms application,
: there are 15 copies of the app running, each one running on a different
: pc, and it must run interactively, which is a bad constraint. My job control
: app needs to know when these apps are done, and users should
: be able to kill individual jobs in the list, or all jobs if they want. Can I
: customize
: your GUI? I have written an app that does this with sockets and WMI that has
: been running for several months, but I dont see why I should maintain this
: when products like yours exist.

: What are the implications of this in licensing terms?

: Thanks in advance,
: George

Thank you for all your help.

Best Regards
George Coles

: You can write a custom Windows application or create a Web-based system using
: either COM or Java API to present job flow in a form easily understood by
: end-users (see 24x7 API's manuals for more info)

: If you set each "worker" job to run synchronously as I previously
: suggested you would always know when they are done. If the total number of
: jobs running is big I also suggest enabling job start/finish event
: notifications of database type each job. This way you can have all jobs
: from all PC to log events into a centralized database which you can always
: read/monitor from any custom application. If you want to
: control/orchestrate all applications on multiple computers from one place
: consider running one central 24x7 Scheduler and running 24x7 Remote Agents
: on other PCs. This way you can run and control jobs remotely.

: For every PC with 24x7 software installed you would need a separate
: installation license as well as a license for your custom application (if
: any) using 24x7 COM/Java API (client part). If the number of computers
: where you plan to install 24x7 is 10+ (also count PCs for system
: administrators who could monitor and manage jobs remotely using 24x7
: Remote Control) consider getting a site license. The site license also
: includes web-base interface (Web-based Management Console) allows using
: API with a web-server and some other goodies.