The Scheduler Resilience feature in JD Edwards is primarily used to run notifications and orchestrations at designated intervals, which can run as a process on one or multiple AIS Servers. The Scheduler Resilience feature is able to tolerate failures, restart with little to no human intervention, and load balance if it or another scheduler is falling behind.
You may be wondering why we can’t use the standard JD Edwards scheduler to execute these sorts of jobs. The primary reason is because the standard scheduler in JDE doesn’t have a tolerance built into it. Meaning if the JDE scheduler fails, it needs human intervention to get up and running again. It also doesn’t contain any load balancing capabilities. With the Scheduler Resilience feature on the AIS Server, we can store the scheduled job properties for the notifications and orchestrations in a database. This means if a server fails, the scheduler running on the other AIS Server can continue to operate.