WebSphere Adapter for Oracle E-Business Suite
The event processing mechanism for Oracle E-Business Suite is used with WebSphere® Adapter for JDBC to process inbound events from the Oracle database. The Adapter for JDBC processes outbound requests to create, update or retrieve data in the Oracle database.
The Oracle E-Business Suite is built around and works with the Oracle database. Oracle E-Business Suite has its own event processing mechanism, the Business Event System (BES). This system enables raising events in the Oracle database and then using subscriptions that consume the events and perform an action, which is based on your preset configuration. Actions can include populating a table or an Oracle AQ queue with information from the event, or running some SQL or Java™ code.
When an event is raised, the Business Event System searches for subscriptions that use that event type, and it processes the actions defined in those subscriptions. The Oracle user has flexibility in defining what actions can be taken. For example, an event could be designed to trigger based on updates to a Customer object in the Oracle database. Then a subscription that targets a customer change event would be notified and would take an action. The action could be to populate the key values for the changed object into an event table for consumption by another component.
WebSphere Adapter for JDBC is used to handle interfacing with database artifacts. It enables direct SQL table calls and interaction with database stored procedures and APIs. This solution uses the built-in event processing support inherent in the Oracle E-Business Suite to process events that can be consumed by the Adapter for JDBC. This solution also uses the Adapter for JDBC to populate information in the Oracle database and to call procedures to process data into the Oracle system.
In the sample application for inbound event processing, the Adapter for JDBC is used to poll an event table created in the Oracle application's database. The adapter uses the event information from the event table, such as the object key and type, to retrieve business object information from the Oracle base tables. For information on the architecture of the Adapter for JDBC, refer to WebSphere Adapters: Adapter for JDBC User Guide.
Oracle's internal Business Event System allows you to recognize when a business object is changed and to populate that information to the event table. See the sample application for specific details on use of the Business Event System. For more information on the Business Event System, refer to your documentation for Oracle Applications, specifically the Workflow Administrator's Guide.
For outbound request processing, the Adapter for JDBC is used to populate object information to the interface tables in the Oracle application. The interface tables are standard tables used to enable inbound information to be processed into the Oracle base tables. Oracle supports this process to help prevent undesirable content changes that could occur from direct updates to the base tables.
The Adapter for JDBC populates the interface tables, then it is used to call a stored procedure that invokes a standard function call included in the Oracle application. The Oracle database processes the data in the interface tables and populates it to the base tables.
To retrieve data from the Oracle application, a Retrieve operation using the Adapter for JDBC can be performed against the base tables, because no data is being modified in the tables.
In addition, the Adapter for JDBC can be used to directly call Oracle's built-in database application programming interfaces (APIs). However, the JDBC driver limits parameters to simple, or non-record, data types when an API is called directly from the Adapter for JDBC. Because the majority of the Oracle APIs use record parameters, these APIs can be wrapped inside of stored procedures, which can then be called by the Adapter for JDBC.
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)