IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > JDBC > Overview of IBM WebSphere Adapter for JDBC > Technical overview

Outbound processing

When an application component needs to query the existence of a record in the database or retrieve or modify data in the database, the adapter acts as the connector between the application component and the database. The adapter provides a set of standard outbound operations, which process either after-image or delta style business objects. The adapter also supports both local and XA (distributed) transactions for outbound processing.

The adapter business object model uses two styles of business objects for making updates: after-image and delta. An after-image business object is one that contains the complete state of the business object after all wanted changes have been made to it. A delta business object is one that contains only key values and the data to be changed. Delta business objects are used only in operation that update business objects.

Supported operations

The table below lists the outbound operations that are supported for each type of business object and indicates whether each supports after-image or delta style processing.

Outbound operations supported by type of business objects

Business objects supported	Operation	After-image support	Delta support
Tables Views Synonyms Nicknames	Create	Yes	No
Update	Yes	No
UpdateAll	Yes	No
Delete	Yes	No
DeleteAll	Yes	No
Retrieve	Not applicable	Not applicable
RetrieveAll	Not applicable	Not applicable
ApplyChanges	Yes	Yes
Exists	Not applicable	Not applicable
	Upsert	Yes	No
Stored procedures Batch SQL	Execute	Not applicable	Not applicable
Queries	RetrieveAll	Not applicable	Not applicable
Wrappers	Create	Yes	No
Update	Yes	No
Delete	Yes	No
Retrieve	Yes	No

Transaction management

The adapter supports both local and XA (distributed) transactions for outbound processing. In the adapter, a transaction is an isolated interaction with the database. A transaction can consist of multiple operations on the database performed as an atomic unit. These operations are not affected by simultaneously occurring operations from other users of the database.

The adapter supports transactions only if the database server supports transactions. The types of transactions supported are local and XA transactions:

• A local transaction is one in which a component defines the start and end of the transaction with a single database. It uses a one-phase commit protocol. The transaction is managed and performed by the database.

• An XA transaction is one in which the transaction can span multiple heterogeneous databases. It uses a global, or two-phase commit, protocol. The transaction manager coordinates the transaction.

XA transactions

The adapter supports XA transactions for outbound processing. Choose one of the following methods to configure the adapter for XA transactions:

• Specify a JNDI data source that supports XA transactions using the XA DataSource JNDI name (XADataSourceJNDIName) property.

• Specify an XA data source using the XA DataSource name (XADataSourceName) property.

The XA DataSource JNDI name property represents a data source created within IBM BPM or WebSphere Enterprise Service Bus.

If you define a JNDI data source that supports XA transactions on the server, and specify that data source when you configure the adapter, the adapter participates in XA transactions. Optionally, if you use an XA data source, the adapter participates in XA transactions.

For information about how to configure XA transaction, see Setting deployment properties and generating the service.

• Outbound operations
  Application components use operations to perform actions such as retrieving from a database. The adapter provides certain outbound operations. Details are provided on how the adapter processes business objects for each of the supported operations.
• User-defined query criteria for operations
  IBM WebSphere Adapter for JDBC supports user-defined criteria on table business objects for the RetrieveAll, UpdateAll, DeleteAll, and Exists operations. You can use this user-defined criteria to retrieve, update, delete multiple records in one operation, and check the existence of multiple records or one record in a single operation.
• Matching records using child business object attributes
  IBM WebSphere Adapter for JDBC supports matching records using the child business object attributes on RetrieveAll, DeleteAll, Exists, and UpdateAll operations.

Technical overview

Related tasks:

Setting deployment properties and generating the service

Performing the migration

Create the project

Setting deployment properties and generating the service

Related reference:

Managed connection factory properties

Solutions to common problems

Migration considerations