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 Informix® data sources.
The Informix JDBC Driver is a Type 4 JDBC driver that provides JDBC access to the Informix database.
com.informix.jdbcx.IfxConnectionPoolDataSource
Requires
the following JDBC driver files: ifxjdbc.jar
ifxjdbcx.jar
Requires the following DataStoreHelper class:com.ibm.websphere.rsadapter.InformixDataStoreHelper
Requires
a valid authentication alias.The name of the Informix instance on the server. Example: ol_myserver.
The port on which the instances listen. Example: 1526.
Either the IP address or the host name of the machine that is running the Informix database to which you want to connect. Example: myserver.mydomain.com.
To support IPv6: On AIX and Solaris, IBM Informix Dynamic Server 10.00 with fix pack 1 supports the IPv6 standard. To enable IPv6 on your WebSphere Application Server connection with one of these Informix releases, input your full IPv6 host name for the ifxIFXHOST property.
The name of the database from which the data source obtains connections. Example: Sample.
Although not required, this property enables you to set the number of seconds that Informix software waits for a lock. By default, Informix code throws an exception if it cannot immediately acquire a lock. Example: 2.
The Informix JDBC Driver (XA) is a Type 4 JDBC driver that provides XA-compliant JDBC access to the Informix database.
com.informix.jdbcx.IfxXADataSource
Requires
the following JDBC driver files: ifxjdbc.jar
ifxjdbcx.jar
To use SQLJ: This provider also requires driver file ifxsqlj.jar if you plan to use SQLJ for queries.
com.ibm.websphere.rsadapter.InformixDataStoreHelper
Requires a valid authentication alias.
The name of the Informix instance on the server. Example: ol_myserver.
The port on which the instances listen. Example: 1526.
Either the IP address or the host name of the machine that is running the Informix database to which you want to connect. Example: myserver.mydomain.com.
To support IPv6: On AIX and Solaris, IBM Informix Dynamic Server 10.00 with fix pack 1 supports the IPv6 standard. To enable IPv6 on your WebSphere Application Server connection with one of these Informix releases, input your full IPv6 host name for the ifxIFXHOST property.
The name of the database from which the data source obtains connections. Example: Sample.
Turn on this property when multiple users access the same database. Activating the property enforces tight coupling of XA transactions within the same global transaction ID, and requires the transactions to share lock space.
These parameters help prevent transaction management errors from occurring in the case of multiple client requests.
Turn on the ifxIFX_XASPEC property by assigning it the value of Y or y; either character works because the setting is not case-specific. Turn the property off by assigning it the value of N or n. WebSphere Application Server ignores all other values. Your setting for the property overrides the Informix database system setting.
Although not required, this property enables you to set the number of seconds that Informix software waits for a lock. By default, Informix code throws an exception if it cannot immediately acquire a lock. Example: 2.
The Informix IBM JCC Driver is a one-phase commit provider for Informix that uses the IBM Data Server Driver for JDBC and SQLJ. The IBM Data Server Driver is JDBC 4.0 compliant and is the next generation of the Universal JCC driver.
This provider is configurable in version 7.0 and later nodes.
com.ibm.db2.jcc.DB2ConnectionPoolDataSource
db2jcc4.jar
db2jcc_license_cu.jar
db2jcc_license_cisuz.jar
as well as the following DataStoreHelper
class:com.ibm.websphere.rsadapter.InformixJccDataStoreHelper
This provider requires a valid authentication alias.
The Informix IBM JCC Driver (XA) is a two-phase commit provider for Informix that uses the IBM Data Server Driver for JDBC and SQLJ. The IBM Data Server Driver is JDBC 4.0 compliant and is the next generation of the Universal JCC driver.
This provider is configurable in version 7.0 and later nodes.
com.ibm.db2.jcc.DB2XADataSource
db2jcc4.jar
db2jcc_license_cu.jar
db2jcc_license_cisuz.jar
as well as the following DataStoreHelper
class:com.ibm.websphere.rsadapter.InformixJccDataStoreHelper
This provider requires a valid authentication alias.
java.sql.SQLException: Already in transaction.
at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:398)
at com.informix.jdbc.IfxSqli.a(IfxSqli.java:3247)
at com.informix.jdbc.IfxSqli.E(IfxSqli.java:3556)
at com.informix.jdbc.IfxSqli.dispatchMsg(IfxSqli.java:2382)
at com.informix.jdbcx.IfxXASqli.receiveMessage(IfxXASqli.java:120)
at com.informix.jdbc.IfxSqli.X(IfxSqli.java:7926)
at com.informix.jdbc.IfxSqli.a(IfxSqli.java:854)
at com.informix.jdbc.IfxSqli.executeCommand(IfxSqli.java:749)
at com.informix.jdbc.IfxResultSet.b(IfxResultSet.java:293)
at com.informix.jdbc.IfxStatement.c(IfxStatement.java:1269)
at com.informix.jdbc.IfxStatement.b(IfxStatement.java:423)
at com.informix.jdbc.IfxStatement.executeUpdate(IfxStatement.java:277)
at com.informix.jdbc.IfxSqliConnect.setTransactionIsolation(IfxSqliConnect.java:2565)
gotchaThe Informix JDBC Driver is a Type 4 JDBC driver that is JDBC 3.0 compliant and provides access to the Informix database.
com.ibm.db2.jcc.DB2ConnectionPoolDataSource
db2jcc.jar
db2jcc_license_cu.jar
db2jcc_license_cisuz.jar
as well as the following DataStoreHelper
class:com.ibm.websphere.rsadapter.InformixJccDataStoreHelper
This provider requires a valid authentication alias.
The Informix Using JDBC Driver (XA) is a Type 4 JDBC driver that is JDBC 3.0 compliant and provides XA-compliant JDBC access to the Informix database.
com.ibm.db2.jcc.DB2XADataSource
db2jcc.jar
db2jcc_license_cu.jar
db2jcc_license_cisuz.jar
as well as the following DataStoreHelper
class:com.ibm.websphere.rsadapter.InformixJccDataStoreHelper
This provider requires a valid authentication alias.
java.sql.SQLException: Already in transaction.
at com.informix.util.IfxErrMsg.getSQLException(IfxErrMsg.java:398)
at com.informix.jdbc.IfxSqli.a(IfxSqli.java:3247)
at com.informix.jdbc.IfxSqli.E(IfxSqli.java:3556)
at com.informix.jdbc.IfxSqli.dispatchMsg(IfxSqli.java:2382)
at com.informix.jdbcx.IfxXASqli.receiveMessage(IfxXASqli.java:120)
at com.informix.jdbc.IfxSqli.X(IfxSqli.java:7926)
at com.informix.jdbc.IfxSqli.a(IfxSqli.java:854)
at com.informix.jdbc.IfxSqli.executeCommand(IfxSqli.java:749)
at com.informix.jdbc.IfxResultSet.b(IfxResultSet.java:293)
at com.informix.jdbc.IfxStatement.c(IfxStatement.java:1269)
at com.informix.jdbc.IfxStatement.b(IfxStatement.java:423)
at com.informix.jdbc.IfxStatement.executeUpdate(IfxStatement.java:277)
at com.informix.jdbc.IfxSqliConnect.setTransactionIsolation(IfxSqliConnect.java:2565)
gotcha