Atina JDE EnterpriseOne - Partner connector
Partner connectors developed by our Tech Partners and published on the Boomi Platform provide seamless integration solutions for customers. Customers initiate support for these connectors through the Boomi Support Portal, which routes tickets to the respective partner. The partner or their designated third party is responsible for ongoing support, including troubleshooting, bug fixes, and resolving related issues.
Oracle JD Edwards EnterpriseOne (JDE) is an enterprise resource planning (ERP) suite that manages financial, manufacturing, supply chain, and human capital processes for midsize and large organizations. The Atina JDE EnterpriseOne connector connects Boomi Integration to Oracle JD Edwards EnterpriseOne, enabling you to invoke Business Functions (BSFNs), call web services, submit Universal Batch Engine (UBE) jobs, and process real-time events without developing custom JDE integration code.
The connector does not communicate directly with JD Edwards EnterpriseOne. Instead, it connects through the Atina microservice, a separately licensed component that implements the JD Edwards communication protocol and forwards requests to your JDE environment. This architecture keeps all JDE connectivity and protocol logic outside the runtime, allowing multiple runtimes to share the same microservice instance.
Unlike traditional JD Edwards connectors, the Atina architecture isolates all Oracle JD Edwards EnterpriseOne native libraries, communication protocols, and session management inside the Atina microservice. As a result, no Oracle JD Edwards EnterpriseOne client installation or native libraries are required on the Boomi runtime. This simplifies deployment, reduces maintenance, minimizes upgrade dependencies, centralizes connectivity management, and allows multiple runtimes to securely share the same JDE integration layer. Upgrading the connector or the Atina microservice can be performed independently, reducing operational risk and simplifying long-term maintenance.
With the Atina JDE EnterpriseOne connector, you can:
- Authenticate to Oracle JD Edwards EnterpriseOne using a user, password, environment, and role, or reuse an existing session token.
- Invoke any Business Function (BSFN) or web service (WS) available in your JDE environment, with request and response profiles generated automatically from JDE metadata.
- Open, commit, and roll back BSFN transactions across multiple operations.
- Submit Universal Batch Engine (UBE) reports for background processing and retrieve their execution status.
- Poll for real-time event transactions generated by Oracle JD Edwards EnterpriseOne.
Connector configuration
To configure the Atina JDE EnterpriseOne connector for communication with Oracle JD Edwards EnterpriseOne, create and configure the following components:
-
Atina JDE EnterpriseOne connection. Defines how Boomi connects to the Atina microservice. It stores the microservice endpoint together with the Oracle JD Edwards EnterpriseOne authentication settings, including the user, password, environment, and role.
-
Atina JDE EnterpriseOne operation. Defines the action that the connector performs. You can select one of the following actions: Authenticate, Logout, Transaction, Invoke BSFN, Invoke Web Services (WS), Submit UBE, Get UBE Job Status, or Poll Events. For actions that invoke a specific Business Function or Web Service, the operation also references the imported request and response profiles generated from Oracle JD Edwards EnterpriseOne metadata.
Separating the configuration into connections and operations allows both components to be reused across multiple integration processes. A single connection can be shared by many operations, and a single operation can be reused wherever the same Oracle JD Edwards EnterpriseOne object is invoked.
After you create the connection and operation components, add them to a Boomi Integration process. The connector uses these components to exchange data between Boomi Integration and Oracle JD Edwards EnterpriseOne through the Atina microservice.
Supported editions
The Atina JDE EnterpriseOne connector is compatible with Oracle JD Edwards EnterpriseOne environments supported by the Atina microservice. The connector has been validated with Oracle JD Edwards EnterpriseOne Tools Release 8.98 Update 4 and later.
For Invoke WS operations, Atina recommends using a recent Oracle JD Edwards EnterpriseOne Tools Release. Earlier releases may have limitations in their Web Services implementation that can affect the availability or behavior of certain services. Because the connector communicates exclusively with the Atina microservice over gRPC, compatibility with a specific Oracle JD Edwards EnterpriseOne release depends on the version of the Atina microservice.
One of the key advantages of this architecture is that Oracle JD Edwards EnterpriseOne compatibility updates are delivered through the Atina microservice. In most cases, supporting new JD Edwards EnterpriseOne releases or Tools Releases requires updating only the Atina microservice, without requiring changes to the Boomi connector itself.
Prerequisites
Before configuring the Atina JDE EnterpriseOne connector, ensure that the following prerequisites are met:
-
Deploy and configure the Atina microservice. The connector requires access to an Atina microservice instance deployed in your network. Ensure that the service is running and reachable from the Boomi runtime. Transport Layer Security (TLS) is optional but recommended for production environments.
-
Have valid Oracle JD Edwards EnterpriseOne credentials. You must have a valid user, password, environment, and role to authenticate with Oracle JD Edwards EnterpriseOne.
-
Verify Oracle JD Edwards EnterpriseOne permissions. The authenticated user must have permission to invoke the Business Functions, Web Services, Universal Batch Engine (UBE) reports, and real-time events required by your integration process.
-
No Oracle JD Edwards EnterpriseOne client installation is required on the Boomi runtime. All Oracle JD Edwards EnterpriseOne native libraries, communication protocols, and session management are hosted by the Atina microservice.
Supported objects
The objects that an Atina JDE EnterpriseOne operation supports depend on the action you select. Actions that call a specific JD Edwards EnterpriseOne artifact browse the object catalog dynamically from your JD Edwards EnterpriseOne environment; the remaining actions use a fixed, small set of object types:
| Action | Object type source | Object types |
|---|---|---|
| Authenticate | Fixed | USER, TOKEN |
| Logout | Fixed | LOGOUT |
| Transaction | Fixed | START, COMMIT, ROLLBACK |
| Invoke BSFN | Dynamic, browsed from JD Edwards EnterpriseOne | Any cataloged Business Function, for example AddressBookMasterMBF |
| Invoke WS | Dynamic, browsed from JD Edwards EnterpriseOne | Any cataloged BSSV web service, for example oracle.e1.bssv.JP010000.AddressBookManager.getAddressBook |
| Submit UBE | Manual entry | MANUAL, with the UBE version you type in the UBE Name field, for example R01010Z-ZJDE0001 |
| Get UBE Job Status | Fixed | Get Job Status |
| Poll Events | Fixed | Capture Event Transactions |
For dynamic actions, click Import Objects at design time to browse the catalog that the Atina microservice returns from your JD Edwards EnterpriseOne environment and generate a typed profile for the object you select.
Tracked properties
This connector has no predefined tracked properties. Refer to the topic Adding tracked fields to a connector operation to learn how to add a custom tracked field.
