Driver properties

Configure these properties on the Driver tab:

Database Driver Type Select the connection library type used for this cache. Your choices for library type are:

JDBC – for connections using a Java Database Connectivity driver.
CTLIB_110 – for Sybase Open Client Client-Library connections.
ODBC – for connections using an open database connectivity driver.
OCI_7 – for connections using OCI 7.x.
OCI_8 – for connections using OCI 8.x.
OCI_9 – for connections using OCI 9.x.
OCI_9U – for connections using OCI 9.x.

Connection Library 1PC Enter the class name or library name used to support single-phase commit transactions.

For UNIX platforms, use one of the connection libraries listed in Table 4-1.

**Table 4-1: UNIX platform connection libraries**
Type	Connection library name
JDBC	The Java class name for the driver class. For example, if you are using a Sybase ASA or Adaptive Server Enterprise database, set one of these values: com.sybase.jdbc2.jdbc.SybConnectionPoolDataSource To access the connection cache with JNDI, you must use this driver and this syntax for the server name: NetworkProtocol=Tds:Server=<db_host_name>:Port=<db_listener_port> com.sybase.jdbc2.jdbc.SybDriver When you use this driver, use this syntax for the server name: jdbc:sybase:Tds:<db_host_name>:<db_port> The Oracle connectivity driver requires oracle.jdbc.pool.OracleConnectionPoolDataSource. For EJB CMP entity beans, EAServer supplys JDBC wrapper drivers that can improve performance through the use of deferred updates and stored procedures. For more information, see “Using CMP JDBC wrapper drivers” in the EAServer Performance and Tuning Guide.
Client Library 12.5	libjct_r.so for Solaris, AIX, Digital UNIX, and Linux. libjct_r.sl for HP-UX. You must use the version in the EAServer lib subdirectory, which has been optimized for EAServer threading.
ODBC	libodbc.so (installed in $JAGUAR/intersolv/lib) for Solaris and AIX. libodbc.so (installed in /var/opt/DAU100/connect/lib) for Digital UNIX. libodbc.sl (installed in $JAGUAR/intersolv/lib) for HP-UX.
OCI 7.x	libclntsh.so for Solaris, AIX, Digital UNIX, and Linux. libclntsh.sl for HP-UX.
OCI 8.x
OCI 9.x

Library location must be in library path On Solaris, Digital UNIX, and Linux, the location of the connection library must be in your LD_LIBRARY_PATH for ODBC, Client-Library, or OCI caches, and in CLASSPATH for JDBC caches.

On AIX, the file must be in your LIBPATH for ODBC, Client-Library, or OCI caches, and in CLASSPATH for JDBC caches.

On HP-UX, the file must be in your SHLIB_PATH for ODBC, Client-Library, or OCI caches, and in CLASSPATH for JDBC caches.

For Windows platforms, use one of the connection libraries listed in Table 4-2.

**Table 4-2: Windows platform connection libraries**
Type	Connection library name
JDBC	The Java class name for the driver class. For example, if you are using a Sybase ASA or Adaptive Server Enterprise database, set one of these values: com.sybase.jdbc2.jdbc.SybConnectionPoolDataSource To access the connection cache with JNDI, you must use this driver and this syntax for the server name: NetworkProtocol=Tds:Server=<db_host_name>:Port=<db_listener_port> com.sybase.jdbc2.jdbc.SybDriver When you use this driver, use this syntax for the server name: jdbc:sybase:Tds:<db_host_name>:<db_port> The Oracle connectivity driver requires oracle.jdbc.pool.OracleConnectionPoolDataSource
Client Library 12.5	libjct.dll – you must use the version in the EAServer dll subdirectory, which has been optimized for EAServer threading.
ODBC	odbc32.dll
OCI 7.x	ociw32.dll
OCI 8.x	oci.dll
OCI 9.x	oci.dll

Library location must be in PATH or CLASSPATH The location of the connection library must be in your PATH environment variable for ODBC, Client-Library, or OCI caches, and in CLASSPATH for JDBC caches.

Connection Library XA Enter the class name or library name used to support two-phase commit transactions, and the name of the XA resource library.

**Table 4-3: Connection libraries and XA resource libraries for Solaris**
Database driver	Connection library	XA resource library
JDBC	Same as the JDBC connection library described in Table 4-1	com.sybase.jdbc2.jdbc.SybXADataSource
Sybase Client Library 11.0	libjct_r.so	libjxa.so
Oracle OCI 7.x	libclntsh.so	libclntsh.so
Oracle OCI 8.x	libclntsh.so	libclntsh.so
Oracle OCI 9.x	libclntsh.so	libclntsh.so

**Table 4-4: Connection libraries and XA resource libraries for Windows**
Database driver	Connection library	XA resource library
JDBC	Same as the JDBC connection library described in Table 4-2	com.sybase.jdbc2.jdbc.SybXADataSource
Sybase Client Library 11.0	libjct.dll	libjxa.dll
Oracle OCI 7.x	ociw32.dll	xa73.dll
Oracle OCI 8.x	oci.dll	oraclient8.dll
Oracle OCI 9.x	oci.dll	oraclient9.dll

By default, EAServer uses the XA libraries listed in Table 4-3 and Table 4-4 to obtain an XA resource that is exported from the database connection libraries.

The resource manager determines the connection type based on the configuration and state of the transaction. In most cases, you should not need to modify the resource manager properties. However, to use a shared library or DLL other than the default, you must edit the database property file. For example, for XA resource connections using Oracle OCI 8.x, where 8.x is 8.1.5 or lower, set this property value in the OCI_8.props file:

com.sybase.jaguar.resourcemanager.xalib = xa80.dll

Table 4-5 lists the resource manager database property files for the C/C++ connection caches, which are located in the EAServer Repository/ResourceManager directory.

**Table 4-5: Database property files**
Database driver	Database property file
Sybase Client Library 11.0	CTLIB_110.props
Oracle OCI 7.x	OCI_7.props
Oracle OCI 8.x	OCI_8.props
Oracle OCI 9.x	OCI_9.props

To use a shared library or DLL other than the default for a single connection cache, edit the connection cache properties file, <cache_name>.props, located in the EAServer Repository/ConnCache directory, and specify the shared library or DLL name:

com.sybase.jaguar.conncache.xadllname = library_name

If you execute a transaction without an XA resource configured for a database, the EAServer connection manager returns CS_FAIL.

If a configured XA resource is not running or cannot be connected to, EAServer cannot initialize. To solve this problem, perform one of these tasks:

Start the XA resource.
Make the XA resource available to EAServer.
Start the JagRepair server and delete the XA resource. See “Using the JagRepair server” for information about JagRepair.

Use HA Connection When using Client Library 11.0 to connect to an Adaptive Server Enterprise database, this enables the high availability failover feature.

To use this feature, you also need to modify the client connection information and pass CS_HAFAILOVER when calling ct_config or ct_con_props—see “Open Client Client-Library” for more information.