Argent Scheduler
The Argent Scheduler consists of a service and a client GUI. In most cases the service and client GUI are installed on the same machine.
You can also install just the client GUI of the Argent Scheduler on the desktops of users who need to schedule jobs regularly.
A frequently asked question is,
“If I install the client GUI on the desktops of three different users, will they see each other’s jobs?”
The short answer is yes, and the long answer is it depends.
Every client GUI connecting to the same service is sharing the same database holding the Job Classes, Alerts, Macros, Calendars, etc. So, in a default installation (no changes in configuration) all client GUIs can see all jobs in the shared database.
But you can set security in the Job Classes and you can tie a Job Class to a specific W200x user group, thus giving you control of which users see which jobs.
Of course, you can also have completely separate installations of the Argent Scheduler services. In this case there are distinct and independent databases, and any client GUIs connecting to one service will only see the jobs for that service. You might want to go this route if you have multiple departments submitting jobs unrelated to each other.
Remember: the Argent Scheduler simply submits jobs to one or more Argent Queue Engines. It does not “run” these jobs – jobs are run by the Argent Queue Engines. The Argent Scheduler connects to the Argent Queue Engines, and when the time comes for the jobs to run the Argent Scheduler submits the jobs to the appropriate Argent Queue Engines. The Argent Scheduler’s role is to keep track of schedule and ensure jobs run when and where they should.
See Also: Argent Queue Engine