WebSphere Adapter for Oracle E-Business Suite

Inbound processing sample application

This sample uses the Oracle Business Event System to send inbound customer data from Oracle E-Business Suite to an event table where the Adapter for JDBC can read it. The Adapter for JDBC retrieves and processes the business object from the Oracle database. The content included for this sample is described in this section.

This sample shows the processing of inbound customer data from Oracle E-Business Suite. The Oracle built-in Business Event System raises the event and populates the necessary values to the Adapter for JDBC event table.

A custom concurrent program searches for updates to the Customer table and raises events if any new or modified customers are found. You can configure the concurrent program to run at set intervals or be manually invoked, or be invoked through a stored procedure. For this sample, the Concurrent program is configured for set intervals. To save time while the sample steps are performed, the concurrent program is invoked manually. Once the data reaches the event table, the Adapter for JDBC polls the table for the object_key, object_name, and object_function. Then it processes the business object from the Oracle database application.

Figure 1. Inbound event processing
This image is described in the surrounding text.

For the Business Event System, an event is defined for updates to the Customer table. When changes are saved, the event is raised, and the Oracle Event Manager searches for subscriptions for that event type. The sample uses a custom subscription that recognizes the change to the customer data. The event is passed to the subscription, which processes the data based on the action defined in the subscription. The event information populates the Adapter for JDBC's event table. The adapter queries that table and uses the event information to perform a Retrieve operation from the business object's base tables.

The content for this sample includes the stored procedures necessary to set up the action and the event tables.

Note: Although it is possible to use a trigger on the customer table to handle the population of the event table, this is not recommended by Oracle.
Related tasks
Sample 2: Receiving inbound data from the EIS

Terms of use |

Last updated: Mon 30 Oct 2006 03:46:26

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)