WebSphere Adapter for JDBC

Technical overview of the Adapter for JDBC

The Adapter for JDBC supports integration of databases that are accessible through the JDBC application programming interface (API) by providing inbound and outbound processing under the Java™ 2 Platform, Enterprise Edition (J2EE) Connector Architecture (JCA).

Under outbound operations, a business object is passed to the adapter as a request that is processed according to the operation specified in the business object, either create, retrieve, update, delete, retrieveall, or execute. Requests are received from different EIS applications that need to have the updates applied to the database being managed by the adapter. Processing of these requests results in the creation, retrieval, update or deletion of rows in the corresponding database tables.

Inbound operations can either use standard event processing with an event store or can use custom event processing.

During standard event processing, as data is changed in the application tables in the database, appropriate events are inserted into an event table called an event store, along with relevant information, such as key values. To capture the changed data, you can place triggers on the respective tables, or use other methods, such as Oracle Change Data Capture, which is provided for Oracle databases. The Adapter for JDBC polls the event store and retrieves a batch of events. The events can be filtered based on business object type and/or timestamp. These events are processed, and each event is used to construct a JDBC business graph. The business graph is then dispatched to the endpoints that have a subscription for the specific business object.

During custom event processing, you can enter a query as either a standard SQL statement, a stored procedure or a stored function. Any of these actions returns a resultset that has the data for the following database columns in order: The adapter constructs a JDBC business graph of each event and delivers it to the endpoints that have a subscription for the specific business object. The adapter also supports custom update and delete queries for custom event processing. The custom update and delete queries are run after each event is processed. The queries take the event_id as an input parameter. The update query ensures that the same record does not get picked up for processing during subsequent poll cycles.

The figure titled "Processing within the JDBC adapter" shows inbound and outbound operations.

Figure 1. Processing within the Adapter for JDBCThis image is described in the surrounding text.

Terms of use |

Last updated: Tue 12 Dec 2006 03:32:39

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