Siebel Connector for Oracle Applications > Overview of Siebel Connector for Oracle Applications > Architecture >
The component architecture and paths for one-way and two-way synchronous data integrations between Siebel Applications and Oracle Applications are represented in Figure 1.
Figure 1. Siebel and Oracle Integration: Inbound and Outbound Process Flow
For outbound data sent from Siebel Applications to Oracle Applications:
- A user action in a Siebel Applet, a Siebel Workflow Event, or a Business Integration Manager batch run invokes an Integration Workflow to execute the data transfer.
- The workflow invokes the EAI Siebel Adapter to query the updated business object through Siebel Object Manager and put the data into an instantiated internal integration object.
- The integration object is passed to the Data Transformation Engine (DTE). The DTE transforms the object content from Siebel Applications representation into an equivalent Oracle Applications representation and puts it into an instantiated external integration object.
- The external integration object is passed to the Database Adapter. The Adapter writes the object data to a buffer table.
- The Oracle Procedural Adapter invokes a PL/SQL script to run a business logic validation.
- The script sends all data other than Order information to the Open Interface Table. It sends Order information to an Oracle Applications API.
- If the data goes to the Open Interface Table, the Oracle Concurrent Program Manager runs a program to import the data into the Application's base tables. If the data goes to an API, the API writes the data directly to the base table.
For inbound data from Oracle Applications to Siebel Applications:
- An alert is raised when a record is changed in Oracle Applications.
- To handle the alert, a SQL script runs to register the unique Id of the changed record in the Notification Table.
- The Oracle Receiver picks up the new table entry and invokes a workflow when it polls the Notification Table for changes.
- The workflow uses the Unique Id, retrieved by the Oracle Receiver, to invoke the Oracle Adapter. The Adapter queries for the actual changed record from the Oracle Application's base table. The query results are put into an instantiated external integration object.
- The integration object is passed to the Data Transformation Engine. The DTE transforms the object content from an Oracle Applications representation into an equivalent Siebel Applications representation and puts it into an instantiated internal integration object.
- The internal integration object is passed to the Siebel Adapter. The Adapter "upserts" (inserts or updates) the data to the Siebel Object Manager and puts it into the Siebel Database.