Understanding Schedules

A schedule defines how often the system executes a notification. You can define a schedule using minutes, hours, days, or a Cron string, such as every Tuesday at 2:00 pm. The schedule is then attached to a notification to determine how often it runs. You can attach the same schedule to multiple notifications, but a single notification can only be associated with one schedule.

As a notification designer you can assign your notifications to existing schedules by picking a schedule from the drop-down list. You may also have privileges to create new schedules, in which case the New Schedule button will be active for you. Schedules are managed as UDOs, so you can publish and share your schedules for others to use, and you can use schedules that others have published.

The task of starting, stopping, and managing the scheduler itself is a system administrator task. The scheduler runs as a process on the Application Interface Services (AIS) server.

Note: The AIS server instance where the scheduler is started cannot be clustered. The scheduler should only be started on one instance.

Starting with Tool 9.2.4, you can use the Scheduler user interface page to manage the scheduled jobs. You can start and stop jobs using the Scheduler user interface. See Working with Scheduler for more information.

The scheduler is managed using a set of REST APIs, which are documented with all other JD Edwards REST APIs:

JD Edwards EnterpriseOne Tools REST API for the Application Interface Services Server Guide