Atina JDE EnterpriseOne — Partner operation

An Atina JDE EnterpriseOne operation defines the action that the connector performs. Each operation component represents a single connector action and contains the configuration required to execute that action. For actions that invoke a specific Oracle JD Edwards EnterpriseOne Business Function or Web Service, the operation also references the imported request and response profiles for that object.

Create a separate operation component for each action required by your integration. Operations can be reused across multiple Boomi Integration processes.

All Atina JDE EnterpriseOne operations are executed using the Execute action and exchange data in JSON format. Each execution processes a single input document and returns a single output document.

The connector supports the following actions:

Authenticate
Logout
Transaction
Invoke BSFN
Invoke WS
Submit UBE
Get UBE Job Status
Poll Events

Authenticate tab

The Authenticate action opens an Oracle JD Edwards EnterpriseOne session and returns a session token that can be reused by subsequent connector operations. It supports the following authentication methods:

Most integration processes do not need to use the Authenticate action. By default, connector operations run using the Oracle JD Edwards EnterpriseOne credentials configured in the connection. Use Authenticate only when a process must execute subsequent operations under a different Oracle JD Edwards EnterpriseOne user. For example, workflows that retrieve purchase orders pending approval or approve purchase orders typically require the credentials of the specific approver rather than the generic integration account.

Authenticates using an Oracle JD Edwards EnterpriseOne user, password, environment, and role.
Use the Import wizard to define the object you are integrating based on the action you specified. Click Import Operation and follow the wizard to successfully configure an operation and automatically generate the response XML or JSON profile that can include all required base and custom fields.

Input: JDE_User, JDE_Password, JDE_Environment, JDE_Role
Output: JDE_Token, JDE_AB_No, Session_Id

Authenticates using an existing Atina session token instead of Oracle JD Edwards EnterpriseOne credentials.

Use the Import wizard to define the object you are integrating based on the action you specified. Click Import Operation, and follow the wizard to successfully configure an operation and automatically generate the response XML or JSON profile that can include all required base and custom fields.

Input: JDE_Token
Output: JDE_Token, JDE_AB_No, Session_Id

Logout tab

The Logout action closes an Oracle JD Edwards EnterpriseOne session identified by the supplied session token. Use the Logout action only to close sessions created by the Authenticate action. Sessions established automatically by the connector using the connection credentials are managed by the Atina microservice and do not require an explicit logout.

Logout

Input: JDE_Token
Output: JDE_Token and JDE_AB_No (returned as 0)

Transaction tab

The Transaction action manages Oracle JD Edwards EnterpriseOne Business Function transaction boundaries. It supports the following operations: Start Transaction, Commit Transaction and Rollback Transaction. Use the Transaction ID returned by START as input to subsequent Invoke BSFN operations that participate in the same transaction and then pass the same Transaction ID to either COMMIT or ROLLBACK to complete the transaction.

The Transaction action always uses the Oracle JD Edwards EnterpriseOne native Business Function interface. It does not support Web Services and always requires a connection configured with JDE WS Connection with False.

Start Transaction

Opens a new transaction and returns a Transaction ID that identifies the transaction context.
Use the Import wizard to define the object you are integrating based on the action you specified. Click Import Operation and follow the wizard to successfully configure an operation and automatically generate the response XML or JSON profile that can include all required base and custom fields.

Commit Transaction

Commits the transaction identified by the supplied Transaction ID. Use the Import wizard to define the object you are integrating based on the action you specified. Click Import Operation and follow the wizard to successfully configure an operation and automatically generate the response XML or JSON profile that can include all required base and custom fields.

Rollback Transaction

Rolls back the transaction identified by the supplied Transaction ID. Use the Import wizard to define the object you are integrating based on the action you specified. Click Import Operation and follow the wizard to successfully configure an operation and automatically generate the response XML or JSON profile that can include all required base and custom fields.

Invoke BSFN tab

The Invoke BSFN action executes an Oracle JD Edwards EnterpriseOne Business Function (BSFN) and returns its output values. Click Import Objects to browse the Business Function catalog exposed by the Atina microservice. Select a Business Function to automatically generate its request and response profiles from Oracle JD Edwards EnterpriseOne metadata.
The generated profiles include all Business Function input and output parameters together with the connector’s standard fields, such as JDE Token and Correlation ID. If the Business Function is executed within an active transaction, the request profile also includes Transaction ID.
Each Invoke BSFN operation is associated with a single Business Function. To invoke different Business Functions, create a separate operation for each one.
The generated profiles reflect the parameter definitions exposed by Oracle JD Edwards EnterpriseOne, allowing Boomi Integration to map Business Function inputs and outputs without manually defining the request structure.

Invoke WS tab

The Invoke WS action executes an Oracle JD Edwards EnterpriseOne Business Service (BSSV) and returns its response. This action requires a connection configured with JDE WS Connection = True.
Click Import Objects to browse the Business Service catalog exposed by the Atina microservice. Select a Business Service operation to automatically generate its request and response profiles from Oracle JD Edwards EnterpriseOne metadata. The generated profiles include all Business Service request and response fields together with the connector’s standard fields, such as JDE Token and Correlation ID. Each Invoke WS operation is associated with a single Business Service operation. To invoke different Business Service operations, create a separate operation for each one. The generated profiles reflect the request and response structures exposed by Oracle JD Edwards EnterpriseOne, allowing Boomi Integration to map Business Service inputs and outputs without manually defining the message structure. The generated profiles reflect the parameter definitions exposed by Oracle JD Edwards EnterpriseOne, allowing Boomi Integration to map Business Function inputs and outputs without manually defining the request structure.

Submit UBE tab

The Submit UBE action submits an Oracle JD Edwards EnterpriseOne Universal Batch Engine (UBE) report for background execution. Specify the UBE report and version in the UBE Name field using the format -, for example R01010Z-ZJDE0001. Click Import Objects to generate the request and response profiles for the selected UBE version.
Each Submit UBE operation is associated with a single UBE report version. To execute different UBE reports or versions, create a separate operation for each one.
At runtime, you can override the configured UBE by supplying the UBE_Name field in the input document. When provided, this value takes precedence over the value configured in the operation.
On successful submission, the action returns the Oracle JD Edwards EnterpriseOne job number assigned to the submitted UBE. This job number can be used later with the Get UBE Job Status action to monitor the execution.
Importing the UBE generates typed request and response profiles from Oracle JD Edwards EnterpriseOne metadata, allowing Boomi Integration to map report parameters without manually defining the document structure.

Get UBE Job Status tab

The Get UBE Job Status action retrieves the execution status of a previously submitted Oracle JD Edwards EnterpriseOne Universal Batch Engine (UBE) report. Click Import Objects to generate the request and response profiles for this action. The request includes the job identification fields required by Oracle JD Edwards EnterpriseOne. These values are typically obtained from the output of the Submit UBE action. The response returns information about the job, including its queue, execution status, and completion details. This action is typically used after Submit UBE to monitor the progress of a background job until it completes.

Poll Events tab

The Poll Events action retrieves real-time event transactions from the Oracle JD Edwards EnterpriseOne event tables. This action is typically used in event-driven Boomi Integration processes that react to Oracle JD Edwards EnterpriseOne business events, such as synchronizing downstream systems when a sales order, customer, or item is created or updated.
Click Import Objects to generate the request and response profiles for this action.
The response returns the list of event transactions available since the previous poll, including the event payload for each transaction. The Atina microservice tracks the polling state and returns only new event transactions that have not been delivered by previous polling requests.