Workflow to Create and Add an Oracle E-Business Suite 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.

This table lists the workflow steps for both adapter tasks and overall integration tasks, and provides links to instructions for each step.

Task	Description	More Information
Prerequisites	Before using the Oracle E-Business Suite Adapter, you must perform setup tasks to ensure the appropriate user privileges and required features are in place and the Oracle E-Business Suite Adapter is ready for creating integrations in Oracle Integration.	Set Up and Enable the Oracle E-Business Suite Adapter for Integrations
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.	Create an Oracle E-Business Suite Connection
2	Create the integration. When you do this, you add the Oracle E-Business Suite Adapter as a trigger (source) or an invoke (target) connection to the integration.	Create Integrations in Using Integrations in Oracle Integration Generation 2, Add the Oracle E-Business Suite Adapter as a Trigger Connection, and Add the Oracle E-Business Suite Adapter as an Invoke Connection
3	Map data between the trigger connection data structure and the invoke connection data structure.	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 gender codes 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 If an XML Gateway message is used in an integration, you must perform post activation steps to ensure the integration works properly. See: Post Activation Manual Steps for XML Gateway Messages as a Trigger
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 and Troubleshoot the Oracle E-Business Suite Adapter and Related Error Messages while testing the connection and creating the integration with the Oracle E-Business Suite Adapter at design time.

To better understand how to use the Oracle E-Business Suite Adapter in an integration, see:

• Implement Common Patterns Using the Oracle E-Business Suite Adapter

• Oracle E-Business Suite Adapter Samples

  • An Example of Using a Business Event as a Trigger (Source) in an Integration

  • An Example of Using an XML Gateway Message as a Trigger (Source) in an Integration

  • An Example of Using a PL/SQL REST Service as an Invoke (Target) Connection in an Integration

  • An Example of Using an Open Interface REST Service as an Invoke (Target) Connection in an Integration

  • Examples of Using a Java REST Service as an Invoke (Target) Connection in an Integration

Additionally, refer to the following documents for more information about the Oracle E-Business Suite Adapter:

• Oracle E-Business Suite Adapter in Oracle Integration Frequently Asked Questions (FAQ), My Oracle Support Knowledge Document 2110687.1

• Oracle E-Business Suite Adapter Issues in Known Issues for Oracle Integration Generation 2

• What's New for Oracle Integration Generation 2