Creating orchestrations in JD Edwards is a straightforward way to automate tasks and integrate external systems with your EnterpriseOne environment—without writing extensive custom code. This post walks you through how to get started in Orchestrator Studio.

What Is an Orchestration?

An orchestration is a defined workflow in JD Edwards Orchestrator that automates a sequence of actions. Each orchestration is made up of components like:

• Inputs: Data from external sources like sensors, APIs, or user forms
• Service Requests: Actions performed in EnterpriseOne (e.g., calling an application or business function)
• Rules and Cross-References: Logic and mapping to shape the data
• Outputs: The result, typically a response or update in another system

Step-by-Step: Creating Your First Orchestration

1. Launch Orchestrator Studio
   Accessible via a web browser, Orchestrator Studio is your interface for designing and managing orchestrations.
2. Define the Orchestration Name and Description
   Give it a clear title that indicates its function. This becomes the REST endpoint for external access.
3. Add Inputs
   These define the data your orchestration will receive. For example, an orchestration processing IoT sensor data may take inputs like temperature, device ID, or timestamp.
4. Create the Logic
   Build your orchestration using reusable components:

• Add Service Requests to call JDE applications or functions
• Use Rules for decision-making (e.g., if/else logic)
• Add Cross-References to map external values to internal codes

5. Configure Transformations
   Map your inputs to the required format for each step in the orchestration. This ensures smooth data flow across all components.
6. Test and Validate
   Orchestrator Studio allows you to test orchestrations before deploying. Use the test interface to simulate inputs and verify outputs.
7. Save and Deploy
   Once tested, your orchestration can be published to the AIS Server and made available for scheduled or event-driven execution.

Tips for Success

• Start small and build incrementally
• Name components clearly to support maintenance
• Use version control to track changes over time

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.