Architecture

The WebSphere(R) Adapter for JDBC is a resource adapter that provides bidirectional connectivity between J2EE(TM) applications and enterprise information systems (EISs). For such applications, the exchange of data, which is in the form of business objects, happens at the database level.

The adapter for JDBC communicates with an EIS which is a database provider. Updates to a database might need to be applied to another enterprise information system, and changes to data in an EIS might need to be applied to a database. The resource adapter can integrate with any application built on a database having a JDBC driver that supports the JDBC 2.0 or later specification. Examples include IBM(R) DB2(R), Oracle, Microsoft(TM) SQLServer, Sybase, and Informix databases.

To support integration, the resource adapter processes requests received from any EIS and processes events generated as a result of database updates. The adapter transmits these events to various predefined endpoints in the application server. Endpoints are J2EE applications or other client consumers of the event. Data updates that are made to tables in a database can be automatically propagated to other applications connected to the application server, such as Siebel, PeopleSoft, and Oracle applications, through event notifications posted in an event store. The adapter updates the database tables using SQL queries or stored procedures, as specified in the business objects.

The Adapter for JDBC supports integration of databases accessible through the JDBC application programming interface (API) by providing inbound and outbound support under the Java(TM) 2 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, or retrieveall. 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.

Under inbound operations, as data is changed in the application tables in the database, appropriate events are inserted into an event store, along with relevant information such as key values. To capture the changed data, triggers are placed on the respective tables, or other methods are used, 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. 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. Only after-image support is provided for inbound operations.

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

This image is described in the surrounding text.

Processing within the JDBC adapter


Terms of use |

Last updated: Thu Mar 23 13:24:29 2006

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