InfoCenter Home >
3: Migration overview >
3.3: Migrating APIs and specifications >
3.3.9: Migrating to supported transaction support

3.3.9: Migrating to supported transaction support

Version 3.0x of the product ran with a 1.1 level of JDK. Version 3.0x included packages written by IBM to provide transaction support features usually provided by JDK 1.2. Now that Version 3.5 runs with JDK 1.2, applications should no longer import the proprietary IBM packages, but instead import the open Java 1.2 packages that provide the required functionality.

  1. In Java source files, find the import statement:
    import com.ibm.db2.jdbc.app.jta.javax.transaction.*
  2. Change the import statement to:
    import javax.transaction.*
  3. Recompile the Java files using JDK 1.2.

Other transaction considerations for Version 3.5:

  • One database connection cannot be used across multiple user transactions. If an application component obtains a connection to a database, then begins a transaction, the connection is closed automatically when the transaction ends. The connection must be obtained again before beginning another transaction.
  • The timeout units for transaction inactivity are in milliseconds.
  • If multiple datasource connections are involved in the same transactions, then JTA must be enabled on those datasources. JTA must be enabled for two-phase commit actions.
Go to previous article: Deprecated connection manager APIs Go to next article: Migrating to supported XML configuration

 

 
Go to previous article: Deprecated connection manager APIs Go to next article: Migrating to supported XML configuration