Overview
Client-mode REST API connector for the JD Edwards EnterpriseOne AIS Server: token login and validation plus Orchestrator calls and data service queries.BASE_ADDRESS defaults to https://YOUR_AIS_SERVER:PORT. Topics use erp/jd-edwards/<object>/<verb>.
Authentication
AIS token. JdeLogin sends HTTP Basic (Authorization: {value.json.authorization}, i.e. “Basic base64(user:password)”) with optional jde-AIS-Auth-Environment / -Role / -Device headers and returns userInfo.token. All other events send that token as jde-AIS-Auth: {value.json.ais_token}. Tools 9.2.4+ for header authentication.Notes
- The AIS Server is customer-hosted (on-premises or OCI); replace BASE_ADDRESS with your AIS URL. Orchestrations are built by the customer in Orchestrator Studio, so the orchestration name and its inputs are site-specific.
- If the token was requested with jde-AIS-Auth-Device, every later call must send the same device; add the header in a fork if you use it.
- Call JdeLogout when done; AIS sessions also hold an HTML Server session until timeout.
Basic Syntax
Sources
- https://docs.oracle.com/en/applications/jd-edwards/cross-product/9.2/rest-api/index.html
- https://docs.oracle.com/en/applications/jd-edwards/cross-product/9.2/rest-api/Authentication.html
- https://docs.oracle.com/en/applications/jd-edwards/cross-product/9.2/rest-api/api-orchestrator-service.html
- https://docs.oracle.com/en/applications/jd-edwards/cross-product/9.2/rest-api/op-v3-orchestrator-jde-login-post.html
- https://docs.oracle.com/en/applications/jd-edwards/cross-product/9.2/rest-api/op-v3-orchestrator-orchestration-post.html
- https://docs.oracle.com/en/applications/jd-edwards/cross-product/9.2/rest-api/op-v2-dataservice-post.html

