How to set up JD Edwards Orchestrator (step by step)
how to set up JD Edwards Orchestrator
Also searched as
- JDE Orchestrator Studio tutorial
- create orchestration JD Edwards step by step
- JDE orchestrator form request vs service request
- EnterpriseOne Orchestrator REST API setup
Short answer
An EnterpriseOne orchestration chains one or more requests (form requests that drive an interactive application, or service requests that call a BSFN, business service, or SQL) plus optional rules and notifications, then exposes the whole thing as a callable REST endpoint via the AIS (Application Interface Services) server. The setup work happens in Orchestrator Studio, not the Fat Client.
Applies to: JD Edwards EnterpriseOne 9.2 with Application Interface Services (AIS) server, Orchestrator Studio
Build a working orchestration
- 1Confirm your AIS server is installed and running, and note its base URL - Orchestrator Studio and all runtime calls go through AIS, not directly to the enterprise server.
- 2Log into Orchestrator Studio (typically at http://<aisserver>:<port>/jderest/orchestrator or the configured URL) with a valid EnterpriseOne user.
- 3Create the underlying request first: a Form Request if you are driving an existing interactive application's fields and grid, or a Service Request if you are calling a BSFN, business service, table-based CRUD operation, or a connector.
- 4Record the request's input and output parameters carefully - these become the contract the orchestration and eventually the REST caller will use.
- 5Create a new Orchestration, add your request(s) as steps, and map orchestration-level inputs to each step's inputs, and each step's outputs forward as needed.
- 6Add rules if you need conditional branching (e.g. only call step 2 if step 1's output meets a condition) or notifications for email/alert steps.
- 7Test inside Orchestrator Studio using its built-in test panel before exposing it externally - this validates parameter mapping without needing a REST client yet.
- 8Once it passes, call it externally via the AIS REST endpoint (POST to /jderest/orchestrator/<orchestration name>) with a valid AIS token or basic auth, and verify the JSON response matches expectations.
- 9Secure it properly: use a dedicated service account with least-privilege security rather than a personal login, and review row/column security since orchestrations respect the calling user's EnterpriseOne security.
Form Request vs Service Request
A Form Request automates an actual interactive application - it drives the same forms, grids, and buttons a user would click, which makes it good for reusing complex UI validation and business logic you do not want to reimplement, but it is slower and more brittle to application layout changes.
A Service Request calls a BSFN, a published business service, a table-based CRUD action, or a connector directly, without going through UI screens - faster and more stable for straightforward data operations, but you lose any validation logic that lives only in form-level event rules rather than the underlying business function.
The role of AIS
Application Interface Services is the middle-tier component that exposes EnterpriseOne functionality as REST/JSON. Orchestrator Studio itself is a web app served by AIS, and every orchestration you build ultimately runs as an AIS REST call, whether triggered from Studio's test panel, a mobile app, an external system, or a scheduled job.
Because of this, AIS server health, its connection to the enterprise server, and its own security configuration (token server, JAS/AIS user setup) are prerequisites that must be right before any orchestration work will succeed - an orchestration failing to run is often an AIS connectivity issue, not a logic error in the orchestration itself.
Common real-world uses
Exposing a sales order status lookup to a customer portal, validating and creating a purchase order from a scanned mobile form, triggering a UBE submission from an external scheduling tool, or building lightweight approval notifications tied to a workflow condition.
Orchestrations are also the standard integration point for connecting EnterpriseOne to low-code platforms, RPA tools, or custom web/mobile front ends without writing new custom BSFNs for every integration need.
POST http://<aisserver>:<port>/jderest/orchestrator/MyOrchestration
Content-Type: application/json
Authorization: Bearer <token>
{
"MyOrchestration": {
"orchestrationName": "MyOrchestration",
"Form_01": { "BusinessUnit": { "value": "30" } }
}
}Common pitfalls
- !Building the orchestration before fully defining and testing the underlying request - parameter mapping errors are much harder to debug once both layers are combined.
- !Using a personal login as the service account for external callers, which mixes up security auditing and breaks when that person's password changes or account is disabled.
- !Assuming an orchestration bypasses EnterpriseOne security - it does not; the calling user's row, column, and application security still applies.
- !Choosing a Form Request purely out of habit when a Service Request would be faster and more stable for a simple data operation with no UI-only validation.
- !Not testing in Orchestrator Studio's own test panel first, going straight to an external REST client and conflating orchestration bugs with client-side integration bugs.
How an ERP-grounded AI assistant handles this
ERPray can help draft the JSON payload and parameter mapping for a new orchestration from a plain description of what it should do, and can answer questions about an existing orchestration's inputs/outputs by reading its definition directly rather than someone reverse-engineering it from Orchestrator Studio's UI. Actually building and testing the orchestration remains a normal EnterpriseOne configuration task done by a developer or admin.
Frequently asked questions
Do I need custom development to build an orchestration?
No - orchestrations are built through configuration in Orchestrator Studio using existing applications, business functions, or business services. Custom development is only needed if the underlying BSFN or business service you want to call does not already exist.
Can an orchestration call another orchestration?
Yes, orchestrations can be nested as steps within other orchestrations, which is a common way to build reusable building blocks for larger integration flows.
What authentication does the REST endpoint use?
AIS supports token-based authentication (recommended, via the AIS token server) and basic authentication against a valid EnterpriseOne user, subject to whatever your AIS server security configuration allows.
Why does my orchestration work in Studio's test panel but fail from an external caller?
Usually a difference in authentication, the JSON payload structure, or the security context of the account used externally versus the account logged into Studio. Compare the exact request body and the calling user's EnterpriseOne security between the two.
Related
How to set data selection and processing options in JD Edwards
Data selection controls which rows a UBE's underlying business view reads (a filter, stored per version in F9210/F9211), while processing options control how the program behaves once it has that data (a settings template stored per version in F983051/F983052). They are configured from the same Version Detail screen but are separate, unrelated mechanisms that new users routinely confuse.
Error fixJD Edwards business function (BSFN) errors: how to diagnose them
A BSFN error in EnterpriseOne means either the compiled function was not found for the current package build, or the function ran and threw an internal exception (often a null business view row, an unhandled C runtime error, or a failed table I/O). The fix path is different for each, so the first step is always determining which one you are facing from jde.log.
Error fixJDE UBE failed (status E): how to read jde.log and jdedebug.log
A UBE (batch report/program) that ends with status E in Work With Submitted Jobs tells you almost nothing on its own. The real error is in jde.log on the enterprise server, in the job's own PDF/log subdirectory (jdedebug.log if you turned on debug), and in the work directory for that job number under PrintQueue or the OS temp path.
Error fixJD Edwards: record is being used by another user (record reservation)
EnterpriseOne places a soft record reservation lock when a user opens a record for edit, tracked in the F00165 table, and releases it when the user saves, cancels, or the session ends cleanly. A stuck lock almost always means a session died abnormally (browser crash, network drop, kiosk timeout) without triggering the release, and it must be cleared by an admin, not by the original user retrying.
Error fixJDE package build failed: how to find the real cause
A package build (Full or Update) that ends in a failed or errored status on the deployment server does not explain itself in the Package Build Workbench screen. The real diagnostic detail is in the package's own log subdirectory on the deployment server, which holds a build log, a table conversion log, and per-object compile logs that pinpoint the actual failure.
How-toJD Edwards table conversion: how it works and how to run one
Table conversion (TC) is the EnterpriseOne mechanism that updates a table's physical structure and converts its existing data whenever a table's definition changes in Object Librarian, most commonly running automatically as part of a package build. Simple field additions or size changes convert automatically; more complex changes such as splitting a field or transforming values need a custom conversion routine attached to the table object.
AI for ERPAI for JD Edwards EnterpriseOne, Built on Orchestrator and AIS
Add AI to JD Edwards E1 9.2 using Orchestrator, AIS, and BSSV rather than screen-scraping. Ground a private LLM on F4211, F4111, and F0411 data.
AI for ERPAI for JD Edwards World on IBM i, without a EnterpriseOne migration
Add AI to JD Edwards World on IBM i without replatforming: read the physical files safely, ground an LLM on your data, and keep control on the box you already run.
Stuck on JD Edwards EnterpriseOne?
Talk to engineers who work inside JD Edwards EnterpriseOne every week, and who build private AI that answers these questions from your own ERP data.