WebSphere Adapter for JDBC
When an appplication component needs to invoke an operation on the enterprise information system (EIS), for example to retrieve data, the Adapter for JDBC acts as the connector between the application component and the EIS. The adapter provides certain outbound operations. The standard outbound operations can process either after-image or delta style business objects. The adapter also supports both local and XA transactions for outbound operations.
The adapter supports two business object styles that relate to the amount and purpose of information conveyed by the business object: after-image and delta. An after-image is the state of a business object after all changes have been made to it. A delta is a business object used in an update operation that contains only key values and the data to be changed.
Outbound operations without after-image or delta support::
For details on how the adapter processes business objects for each of the supported outbound operations, see the "Outbound operations" section.
The Adapter for JDBC supports both local and XA transactions. In the adapter, a transaction is an isolated interaction with the back-end database, or enterprise information system (EIS). A transaction can consist of multiple operations on the database that are performed as an atomic unit. These operations are not affected by simultaneously occurring operations from other client applications of the database.
The adapter supports XA transactions for IBM DB2 and Oracle databases only.
Use the properties XADataSourceName and XADatabaseName with XA transactions. See the "Managed (J2C) connection factory properties" in the "Reference" section for details about these properties.
Sample values for two XA transaction properties are provided below:
IBM DB2
XADataSourceName for Type 2 Driver (db2java.zip): COM.ibm.db2.jdbc.DB2XADataSource
XADataSourceName for Type 4 Driver (db2jcc.jar): com.ibm.db2.jcc.DB2XADataSource
XADatabaseName : <dbname>
where dbname is the name of the database.
Oracle
XADataSourceName: oracle.jdbc.xa.client.OracleXADataSource
If the DataSourceJNDIName property is defined as a local or XA transaction data source, then the adapter uses this property for obtaining the inbound or outbound connection to the database. The DataSourceJNDIName represents the DataSource created within WebSphere® Process Server or WebSphere Enterprise Service Bus. This name could represent an XA or Connection Pool data source.
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)