Understanding Scheduler

The Orchestrator Studio provides a user interface, which is called the Scheduler user interface, where you can view the notification and orchestration jobs along with the attached schedules. Using the Scheduler user interface, you can view all the jobs and perform tasks, such as starting and stopping individual or multiple jobs. The Scheduler user interface eliminates the need to use third-party applications to start and stop jobs. The Scheduler user interface enables you to designate a job that should be automatically started whenever the AIS server is started. This enables the scheduled jobs to be automatically started when the AIS server is restarted.

You must have been granted proper UDO security to work with the notification and orchestration jobs on the Scheduler user interface.

The Scheduler user interface provides information about the orchestration jobs that are running and the ones that need to be started.

The scheduler runs as a process on the Application Interface Services (AIS) server. You can view only those schedules on the AIS server that you are currently logged-in to. For information on designating the AIS server as a scheduler, see "Configuring AIS Server Manager Settings" in the JD Edwards EnterpriseOne Application Interface Services Server Reference Guide.

Note: When a Scheduler server points to a JAS server that supports an environment, which is also supported on another Scheduler server pointing to another JAS server, two instances of the same job could exist. This is because the job is running for a specific environment and that environment is supported in two different scheduler configurations. This is applicable when the scheduler is not resilient.