Integration & DataGlossary

What Is JD Edwards Orchestrator?

Also known as: JDE Orchestrator, Oracle JD Edwards Orchestrator Studio, JDE orchestration

Definition

JD Edwards Orchestrator is Oracle's low-code tool in EnterpriseOne that exposes JDE forms, business functions and database data as REST services through the Application Interface Services (AIS) server, so outside apps, IoT devices and AI agents can call JDE.

JD Edwards Orchestrator Explained

Orchestrator Studio is used to design orchestrations, each a series of steps that call JDE form requests, business function calls (BSFN), database queries and messages. An orchestration is published and invoked through the AIS server over REST using JSON, with the same JDE security as a user signing on.

Beyond single calls, an orchestration can use rules, custom Java, cross references and notifications, and can be triggered by a schedule or by external devices through Internet of Things Orchestrator features. Components are reusable building blocks, and Orchestrator can call other orchestrations and external REST endpoints.

In practice Orchestrator replaces many older integration styles such as direct Business Services (BSSV) and flat file interfaces. Limits include dependence on the AIS server tier, performance when stepping through many form interactions, and the need for tools release levels that support the features used. It works for both Oracle-hosted and on-premises installations.

Why It Matters

It is the supported route for exposing JDE to modern integrations and AI agents without editing code or bypassing security.
Because orchestrations run as a JDE user, role and row security remain enforced.
Form-based steps are slower than direct business functions, so design affects throughput.
JDE customers on older Tools releases may need upgrades before using it.

In Practice

A plant wants a mobile app to check inventory availability. An orchestration takes item number and branch, calls a form request on Item Availability, returns on-hand and committed quantities as JSON, and is published through the AIS server. The mobile app calls it using a service account mapped to a restricted JDE role.

Frequently Asked Questions

What is the AIS server?

The Application Interface Services server is the JDE web tier that receives REST calls, handles authentication and runs orchestrations or form services.

Do I need to code to use Orchestrator?

Mostly no. Orchestrations are designed visually, though custom Java or business functions can be added for special logic.

Is Orchestrator a replacement for BSSV?

For many use cases yes, since it is simpler and REST-based, but existing BSSV interfaces may remain in use.

Related Terms

REST API

A REST API is a web interface that exposes application data as addressable resources over HTTP, using standard verbs such as GET, POST, PUT, PATCH, and DELETE, stateless requests, and conventional status codes, typically exchanging JSON.

Middleware

Middleware is software that sits between applications and handles the communication, transformation, routing, and reliability concerns of moving data between them, so that the applications themselves do not need to know about each other directly.

API (Application Programming Interface)

An API (Application Programming Interface) is a defined contract that lets one software system request data or trigger functions in another, specifying the available operations, the structure of requests and responses, and the rules for authentication and error handling.

iPaaS

iPaaS (Integration Platform as a Service) is a cloud-hosted platform that provides prebuilt connectors, data mapping, orchestration, and monitoring so organizations can build and operate integrations between applications without running their own integration infrastructure.

ERP (Enterprise Resource Planning)

ERP (Enterprise Resource Planning) is integrated business software that runs finance, manufacturing, supply chain, sales, and HR processes on a single shared database, so a transaction entered once updates every dependent function in real time.

Go Deeper

Free Tool

ERP Migration Risk Assessment

Answer 10 questions about your data, team, testing, and budget to get a migration risk score and a prioritized list of mitigations before your project starts.

Oracle JD Edwards to Infor Migration Guide

Plan your Oracle JD Edwards EnterpriseOne migration to Infor CloudSuite or LN. Data mapping, functional comparison, and migration timeline.

Legacy ERP AI Modernization: Wrappers vs Rewrites

Modernize a legacy ERP with AI: when an AI wrapper layer beats a full rewrite, how to scope it, and the failure modes of each approach in manufacturing.

Working with JD Edwards Orchestrator in a live environment? Our engineers do this every day - and our AI agents automate most of it.

Talk to an Expert Browse the Full Glossary

Back to Glossary

Try it here, free

JD Edwards Orchestrator and AIS REST Call Generator

Open full tool

Fill in your AIS host, orchestration name and inputs to get a working Python requests script and curl commands that call a JD Edwards EnterpriseOne 9.2 orchestration.

Fill in

AIS Server base URL

Protocol, host and port of the AIS Server, without /jderest.

Orchestration name

The name exactly as saved in Orchestrator Studio.

Orchestrator API version

Authentication

False = HTTP Basic auth on the orchestrator call. True = request an AIS token first, send it in the jde-AIS-Auth header, then log out.

EnterpriseOne user

Environment (token mode)

Role (token mode)

Device name

Orchestration inputs (JSON)

Use the input names defined on the orchestration.

Generated code

Free, optional. Reopen it on any device.

Download:

Python (requests)

# Call JD Edwards orchestration JDE_ORCH_AddSalesOrder through AIS (v3)
# pip install requests
import json
import os

import requests

AIS = 'https://ais.example.com:9300/jderest'
ORCH = 'JDE_ORCH_AddSalesOrder'
USER = 'INTEGUSER'
PASSWORD = os.environ.get('JDE_PASSWORD', '')  # never hard-code the password
ENV = 'JDV920'
ROLE = '*ALL'
DEVICE = 'integration-host-01'
USE_TOKEN = False
VERIFY = True  # or the path to your internal CA bundle, e.g. '/etc/ssl/certs/corp-ca.pem'

inputs = json.loads(r'''{"Customer": "4242", "Branch": "30"}''')

session = requests.Session()
session.headers.update({'Content-Type': 'application/json', 'Accept': 'application/json'})
token = None
auth = None

if USE_TOKEN:
    # (1) POST /jderest/v2/tokenrequest, token is returned in userInfo.token
    login = session.post(
        AIS + '/v2/tokenrequest',
        json={'username': USER, 'password': PASSWORD, 'environment': ENV,
              'role': ROLE, 'deviceName': DEVICE},
        timeout=60, verify=VERIFY)
    login.raise_for_status()
    token = login.json()['userInfo']['token']
    session.headers.update({'jde-AIS-Auth': token, 'jde-AIS-Auth-Device': DEVICE})
else:
    # Basic auth: AIS uses its configured default environment and role
    auth = (USER, PASSWORD)

try:
    # (2) POST /jderest/v3/orchestrator/{name} with the orchestration inputs
    resp = session.post(AIS + '/v3/orchestrator/' + ORCH,
                        json=inputs, auth=auth, timeout=120, verify=VERIFY)
    resp.raise_for_status()
    print(json.dumps(resp.json(), indent=2))
finally:
    if token:
        # (3) POST /jderest/v2/tokenrequest/logout ends the AIS session
        session.post(AIS + '/v2/tokenrequest/logout', json={'token': token},
                     timeout=30, verify=VERIFY)

Same call with curl (Basic auth)

curl -s -X POST 'https://ais.example.com:9300/jderest/v3/orchestrator/JDE_ORCH_AddSalesOrder' \
  -u 'INTEGUSER:YOUR_PASSWORD' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -d '{"Customer": "4242", "Branch": "30"}'

curl with an AIS token

TOKEN=$(curl -s -X POST 'https://ais.example.com:9300/jderest/v2/tokenrequest' \
  -H 'Content-Type: application/json' \
  -d '{"username":"INTEGUSER","password":"YOUR_PASSWORD","environment":"JDV920","role":"*ALL","deviceName":"integration-host-01"}' \
  | jq -r '.userInfo.token')

curl -s -X POST 'https://ais.example.com:9300/jderest/v3/orchestrator/JDE_ORCH_AddSalesOrder' \
  -H 'Content-Type: application/json' \
  -H "jde-AIS-Auth: $TOKEN" \
  -H 'jde-AIS-Auth-Device: integration-host-01' \
  -d '{"Customer": "4242", "Branch": "30"}'

curl -s -X POST 'https://ais.example.com:9300/jderest/v2/tokenrequest/logout' \
  -H 'Content-Type: application/json' \
  -d "{\"token\":\"$TOKEN\"}"

Paths follow the Oracle JD Edwards EnterpriseOne 9.2 AIS REST API reference: POST /jderest/v2/tokenrequest (token in userInfo.token), POST /jderest/v3/orchestrator/{orchestration} (token header jde-AIS-Auth), POST /jderest/v2/tokenrequest/logout with a token body field. Check that your Tools release supports v3 and Basic auth on the orchestrator endpoint, and that the user is authorised to the orchestration in Security Workbench.

Get your AIS integration reviewed

Send us the orchestration and your target client (Python, Power Automate, MES) and we will check auth, error handling and session cleanup against your Tools release.

Optional. The tool and every export work without this. No spam.

ArchRay builder

Design the on-prem AI stack for JD Edwards EnterpriseOne: model, GPUs, RAG pipeline, guardrails

See memory, speed and cost as you swap parts, then export the diagram. Free, in your browser.

Open the builder

New to JD Edwards EnterpriseOne? Start with the JD Edwards EnterpriseOne guide and toolkit, or plan with Training Path Builder, Upgrade Path Planner, ERP Table and Field Explorer.