JDE E1 Orchestrator
Related pages:
JDE E1 Orchestrator Technical Notes
Description
This is the component for working with Oracle JDE Edwards EnterpriseOne Orchestrator service on elastic.io platform.
Purpose
The component provides ability to connect to Oracle JDE Edwards EnterpriseOne Orchestrator service (JDE E1) and execute orchestrations.
How works. API version
The component is based on REST API for JD Edwards EnterpriseOne AIS Server version 3.0.
Requirements
Environment variables
Name | Mandatory | Description | Values |
---|---|---|---|
NODE_TLS_REJECT_UNAUTHORIZED |
false | For ignoring server https certificate | 0 |
Please Note: From the platform version 20.51 we deprecated the component
LOG_LEVEL
environment variable. Now you can control logging level per each step of the flow.
Credentials
This component use JD Edwards EnterpriseOne authentication for mobile enterprise applications. It involves:
JDE E1 Domain
Username
Password
Device Name
. The original security model put in place for mobile applications still applies, even for non-mobile clients. TheDevice Name
(orDevice ID
) is an arbitrary string.
Triggers
This component has no trigger functions. This means it will not be accessible to select as a first component during the integration flow design.
Actions
Execute an Orchestration
Execute the orchestration with the specified parameters on JDE E1 server and return orchestration results.
Input fields description
- Orchestration name - a dropdown list where you should choose an orchestration which you want to execute.
Metadata description
Orchestration input formats are defined within the orchestration, and they are all unique. Use the Orchestrator Studio to create or modify orchestrations.
Limitations
- All JDE
Date
types represented in GUI as aString