Sun Microsystems JDBC/ODBC Adapter manual Transaction Support Levels

Chapter 3	Section 3.2
Setting Properties of the JDBC/ODBC eWay	Configuring the eWay Connectivity Map Properties

In 5.1.2, five new records are to be inserted into a table. If one of the records fails to insert (such as when a duplicate key exists), the other four records will not be inserted. This is the behavior of the LocalTransaction.

In order to achieve the same result as in 5.1.0 versions, you can choose the method below:

AIn the Connectivity Map, delete the link to the database external application, then reconnect the link and select NoTransaction.

BFill in the NoTransaction property for the database external system under the Environment.

CRebuild the Project.

The following charts identifies what transaction support levels changed between

5.0.5and 5.1.2, and 5.1.0 and 5.1.2, respectively. Note that there are no changes when migrating from ICAN version 5.0.5 and Java CAPS 5.1.2.

Figure 8 Transaction Support Levels

ICAN Version 5.0.5	Java CAPS 5.1.2
Outbound Informix eWay	Outbound Informix eWay
(LocalTransaction)	(LocalTransaction)

Outbound Informix XA	Outbound Informix XA
eWay	eWay
(XATransaction)	(XATransaction)

Java CAPS 5.1.0	Java CAPS 5.1.2
Outbound Informix eWay	Outbound Informix non-
	Transaction eWay
(LocalTransaction)
	(NoTransaction)

Outbound Informix XA	Outbound Informix XA
eWay	eWay
(XATransaction)	(XATransaction)

Under the scenario noted above, if you want 5.1.2 behavior for a LocalTransaction, then set your eWay connection to be Outbound JDBC/ODBC non-Transactional eWay (NoTransaction).

JDBC/ODBC eWay Adapter User’s Guide 28 Sun Microsystems, Inc.