These properties vary according to the database vendor requirements for JDBC driver implementations. You must set the appropriate properties on every data source that you configure. These settings are for a DB2® data source that is connecting to an application server that is running on AIX®, HP-UX, Linux®, Solaris, or Windows® systems.
Starting with version 9 of DB2, Linux, HP-UX, and Solaris systems require a 64-bit kernel. In addition, the width of the default instance bit is now determined by the operating system, which is different than with previous versions of DB2. With these changes in operating system requirements, the -w option, which would have provided the ability to specify the bit width of the instance, was removed for the db2icrt, db2ilist and db2iupdt commands.
These changes on Linux, HP-UX, and Solaris systems preclude the ability to create or maintain a 32-bit instance of the application server with version 9 of DB2 on UNIX® platforms. On 64-bit UNIX systems that have a 32-bit instance created for version 8 of DB2, migrate the 32-bit instance for version 8 of DB2 to a 64-bit instance for version 8 of DB2 before you migrate the instance to version 9 of DB2.
gotchaThis provider is a one-phase commit JCC provider for DB2 that uses the IBM Data Server Driver for JDBC and SQLJ. The IBM Data Server Driver for JDBC and SQLJ is the next generation of the DB2 Universal JDBC driver. Data sources you create under this provider support only 1-phase commit processing, unless you use the type 2 JDBC driver with the application server for z/OS®. If you run the application server on z/OS with the type 2 driver, the driver uses RRS and supports 2-phase commit processing.
com.ibm.db2.jcc.DB2ConnectionPoolDataSource
db2jcc_license_cisuz.jar does not ship with the application server. Place this file in the same directory as the db2jcc4.jar file, so that DB2_JCC_DRIVER_PATH points to both files.
${DB2_JCC_DRIVER_PATH}/db2jcc4.jar ${UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cu.jar ${DB2_JCC_DRIVER_PATH}/db2jcc_license_cisuz.jar ${PUREQUERY_PATH}/pdq.jar ${PUREQUERY_PATH}/pdqmgmt.jar
${DB2_JCC_DRIVER_NATIVEPATH}If driverType is set to 2, the DB2_JCC_DRIVER_NATIVEPATH variable should be set to the directory in your DB2 client installation that contains the native driver libraries. If driverType is set to 4, the native path is not used.
com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper
You can use useTransactionRedirect for both driverType 2 and driverType 4 data sources. To configure the property, use either the wsadmin scripting tool or the administrative console page, Java EE resource provider or connection factory custom properties collection. Assign the property the value of true.
The DB2 Using IBM JCC Driver (XA) is a two-phase commit JCC provider for DB2 that uses the IBM Data Server Driver for JDBC and SQLJ. The IBM Data Server Driver is the next generation of the DB2 Universal JDBC driver. Data sources that you create under this provider support the use of XA to perform two-phase commit processing.
com.ibm.db2.jcc.DB2XADataSource
db2jcc_license_cisuz.jar does not ship with the application server. Place this file in the same directory as the db2jcc4.jar file, so that DB2_JCC_DRIVER_PATH points to both files.
${DB2_JCC_DRIVER_PATH}/db2jcc4.jar ${UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cu.jar ${DB2_JCC_DRIVER_PATH}/db2jcc_license_cisuz.jar ${PUREQUERY_PATH}/pdq.jar ${PUREQUERY_PATH}/pdqmgmt.jar
${DB2_JCC_DRIVER_NATIVEPATH}If driverType is set to 2, the DB2_JCC_DRIVER_NATIVEPATH variable should be set to the directory in your DB2 client installation which contains the native driver libraries. If driverType is set to 4, the native path is not used.
com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper
You can use useTransactionRedirect for both driverType 2 and driverType 4 data sources. To configure the property, use either the wsadmin scripting tool or the administrative console page, Java EE resource provider or connection factory custom properties collection. Assign the property the value of true.
The DB2 Universal JDBC Driver is an architecture-neutral JDBC driver for distributed and local DB2 access. Because the Universal Driver architecture is independent of any particular JDBC driver connectivity or target platform, it allows both Java connectivity (Type 4) or Java Native Interface (JNI) based connectivity (Type 2) in a single driver instance to DB2.
com.ibm.db2.jcc.DB2ConnectionPoolDataSource
db2jcc_license_cisuz.jar does not ship with the application server. Place this file in the same directory as the db2jcc.jar file, so that the DB2UNIVERSAL_JDBC_DRIVER_PATH points to both.
${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.jar ${UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cu.jar ${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cisuz.jar
com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper
You can use useTransactionRedirect for both driverType 2 and driverType 4 data sources. To configure the property, use either the wsadmin scripting tool or the administrative console page Java EE resource provider or connection factory custom properties collection. Assign the property the value of true.
The DB2 Universal JDBC Driver provider (XA) is an architecture-neutral JDBC provider for distributed and local DB2 access. The IBM Data Server Driver for JDBC and SQLJ is the next generation of the DB2 Universal JDBC driver.Whether you use this provider for Java connectivity or Java Native Interface (JNI) based connectivity depends on the version of DB2 you are running. Version 6.0 and later of the application server requires DB2 8.1 Fix Pack 6. This version of DB2 only supports XA connectivity over the Java Native Interface (JNI) based connectivity (Type 2) driver. In order to use XA connectivity with the Type 4 driver, DB2 8.1 Fix Pack 7 or higher is required.
com.ibm.db2.jcc.DB2XADataSource
You must use the right license .jar file to access a specific database backend.
${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc.jar ${UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cu.jar ${DB2UNIVERSAL_JDBC_DRIVER_PATH}/db2jcc_license_cisuz.jar ${DB2UNIVERSAL_JDBC_DRIVER_NATIVEPATH}
com.ibm.websphere.rsadapter.DB2UniversalDataStoreHelper
You can use useTransactionRedirect for both driverType 2 and driverType 4 data sources. To configure the property, use either the wsadmin scripting tool or the administrative console page Java EE resource provider or connection factory custom properties collection. Assign the property the value of true.