EAServer 5.5 supports jConnect™ for JDBC™ 6.0. Hence, you need to reconfigure the JDBC connection caches by modifying the instances of jdbc2 to jdbc3. The following lists the affected instances.
JDBC level 1 connection pool drivers (CR #399593) The Sybase jConnect level 1 driver class property should be com.sybase.jdbc3.jdbc.SybDriver.
JDBC level 2 connection pool drivers (CR #399593) The Sybase jConnect level 2 driver connection pool driver property should be com.sybase.jdbc3.jdbc.SybConnectionPoolDataSource.
Table 4-1: UNIX platform connection libraries (CR #399593) If you are using a Sybase ASA or Adaptive Server Enterprise database, the values for the JDBC driver class properties should be:
com.sybase.jdbc3.jdbc.SybConnectionPoolDataSource
com.sybase.jdbc3.jdbc.SybDriver
Table 4-2: Windows platform connection libraries (CR #399593) If you are using a Sybase ASA or Adaptive Server Enterprise database, the values for the JDBC driver class properties should be:
com.sybase.jdbc3.jdbc.SybConnectionPoolDataSource
com.sybase.jdbc3.jdbc.SybDriver
Table 4-3: Connection libraries and XA resource libraries for Solaris (CR #399593) The XA resource library for JDBC database driver should be com.sybase.jdbc3.jdbc.SybXADataSource.
Table 4-4: Connection libraries and XA resource libraries for Windows (CR #399593) The XA resource library for JDBC database driver should be com.sybase.jdbc3.jdbc.SybXADataSource.
Configuring an XA resource (CR #399593) The value for the Driver property (DLL or Class Name) to configure the connection cache should be com.sybase.jdbc3.jdbc.SybXADataSource.
EAServer 5.5 does not include Merant DataDirect Connect Open Database Connectivity (ODBC) driver. Instead, it now comes with an ODBC driver manger, unixODBC on UNIX. Hence, the ODBC connection library path for Sun Solaris, IBM AIX, and HP-UX in table 4-1 is, as follows:
libodbc.so (installed in $JAGUAR/unixodbc/bin) for Solaris and AIX
libodbc.sl (installed in $JAGUAR/unixodbc/bin) for HP-UX
