Workflow to Create and Add an Oracle Logistics Adapter Connection to an Integration
You follow a very simple workflow to create a connection with an adapter and include the connection in an integration in Oracle Integration.
| Step | Description | More Information |
|---|---|---|
|
1 |
Create the adapter connections for the applications you want to integrate. The connections can be reused in multiple integrations and are typically created by the administrator. Oracle Logistics Adapter connections must use the TransmissionService for version 6.4.2 or greater. |
|
|
2 |
Create the integration. When you do this, you add trigger and invoke connections to the integration. |
Create Integrations and Add the Oracle Logistics Adapter Connection to an Integration |
|
3 |
Map data between the trigger connection data structure and the invoke connection data structure. Note: Data in Oracle Logistics Cloud generally resides in a domain. This can be a single domain for an entire implementation or multiple domains segregated by business unit, customer, or other criteria. Oracle Logistics Cloud domains may not correlate to the upstream system, so the domain must be specified in the mapper in the inbound direction to Oracle Logistics Cloud. For example, element ORDER123 in Supply Chain Cloud can map into Oracle Logistics Cloud as element MY_DOMAIN.ORDER123. |
Map Data in Using Integrations in Oracle Integration Generation 2 |
|
4 |
(Optional) Create lookups that map the different values used by those applications to identify the same type of object (such as units of measure or country codes). |
Manage Lookups in Using Integrations in Oracle Integration Generation 2 |
|
5 |
Activate the integration. |
Manage Integrations in Using Integrations in Oracle Integration Generation 2 |
|
6 |
Monitor the integration on the dashboard. |
Monitor Integrations in Using Integrations in Oracle Integration Generation 2 |
|
7 |
Track payload fields in messages during runtime. |
Assign Business Identifiers for Tracking Fields in Messages and Manage Business Identifiers for Tracking Fields in Messages in Using Integrations in Oracle Integration Generation 2 |
|
8 |
Manage errors at the integration level, connection level, or specific integration instance level. |
Manage Errors in Using Integrations in Oracle Integration Generation 2 |