Not all processes need to run in real time. Some require regular polling, batch processing, or time-based updates. That’s where scheduling in JD Edwards Orchestrator becomes a valuable tool.

Whether you need to check a Watchlist every hour, send alerts at the end of the day, or trigger batch updates overnight, Orchestrator’s built-in scheduler allows you to automate these tasks without manual intervention.

How Scheduling Works in Orchestrator

Scheduling is handled within Orchestrator Studio, where users can define how often an orchestration should run. Each schedule is created as a User Defined Object (UDO) and can be associated with one or more orchestrations.

You can schedule orchestrations to run:

• At regular intervals (e.g., every 15 minutes)
• Daily at specific times (e.g., 3:00 AM)
• Using Cron expressions for more complex timing rules (e.g., Mondays at 8:00 AM and Fridays at 5:00 PM)

Once created, the schedule is deployed to the AIS Server, where the Orchestrator Scheduler process runs it at the defined times.

Use Cases for Scheduled Orchestrations

• Polling External Systems: Check an external API every hour for new data to import into JD Edwards.
• Batch Alerts: Review Watchlists daily and send email notifications to users if thresholds are exceeded.
• Routine Maintenance Checks: Run orchestrations to validate system health or check for stale data on a nightly basis.
• Data Syncs: Perform scheduled exports or imports of transactional data between JDE and other systems.

Setup Considerations

To create and run schedules, users must have the proper UDO security settings. After defining a schedule:

1. Attach it to the orchestration(s) you want to run.
2. Confirm that the Scheduler process is started and running on the AIS Server.
3. Optionally, use REST API services to start, stop, or manage schedules programmatically.

It’s important to note that attaching a schedule alone does not activate it—the scheduler must be running and properly configured by an administrator.

Best Practices

• Use Descriptive Names for schedules so it’s clear what they do.
• Reuse schedules when possible—multiple orchestrations can share the same schedule.
• Monitor execution history to make sure orchestrations are running as expected.
• Avoid excessive frequency—especially if the orchestration is resource-intensive.

Final Thoughts

Scheduled orchestrations are a practical way to automate recurring tasks in JD Edwards. When real-time triggering isn’t necessary, a well-designed schedule can help reduce manual effort, improve consistency, and support time-sensitive business processes around the clock.

Learn More

To further your knowledge and networking, view the resources available on the JD Edwards Orchestrator Strategic Content Center, join a JD Edwards Community Group, and register for an upcoming JD Edwards in-person or online event.