# How to set up JD Edwards Orchestrator (step by step) > Source: https://netray.co/erp-help/jde-orchestrator-setup-guide > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind how-to ## System jd-edwards ## Erp JD Edwards EnterpriseOne ## Module Orchestrator Studio / EnterpriseOne Orchestrator ## Query how to set up JD Edwards Orchestrator ## Alternate Queries - JDE Orchestrator Studio tutorial - create orchestration JD Edwards step by step - JDE orchestrator form request vs service request - EnterpriseOne Orchestrator REST API setup ## Applies To JD Edwards EnterpriseOne 9.2 with Application Interface Services (AIS) server, Orchestrator Studio ## Steps ### Build a working orchestration **Items:** Confirm 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. Log into Orchestrator Studio (typically at http://:/jderest/orchestrator or the configured URL) with a valid EnterpriseOne user. Create 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. Record the request's input and output parameters carefully - these become the contract the orchestration and eventually the REST caller will use. Create 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. Add 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. Test inside Orchestrator Studio using its built-in test panel before exposing it externally - this validates parameter mapping without needing a REST client yet. Once it passes, call it externally via the AIS REST endpoint (POST to /jderest/orchestrator/) with a valid AIS token or basic auth, and verify the JSON response matches expectations. Secure 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. ## Sections ### Form Request vs Service Request **Body:** 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 **Body:** 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 **Body:** 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. **Code:** POST http://:/jderest/orchestrator/MyOrchestration Content-Type: application/json Authorization: Bearer { "MyOrchestration": { "orchestrationName": "MyOrchestration", "Form_01": { "BusinessUnit": { "value": "30" } } } } ## 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. ## Ai Angle 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. ## Faq ### Do I need custom development to build an orchestration? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms JD Edwards Orchestrator setup, Orchestrator Studio tutorial, JDE AIS server REST, form request vs service request JDE, EnterpriseOne orchestration REST API, JDE orchestrator example, Application Interface Services JDE, how to build JDE orchestration --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json