JDBC client deployment

You must install a Java Runtime Environment (JRE) to use JDBC. Version 1.6.0 or later is recommended.

In addition to a JRE, each JDBC client requires a SQL Anywhere JDBC driver or jConnect.

To deploy the SQL Anywhere JDBC 4.0 driver, you must deploy the following files:

sajdbc4.jar This must be in the application's classpath. This file is located in the SQL Anywhere installation java folder.
The JDBC driver support files.

To deploy the SQL Anywhere JDBC 3.0 driver, you must deploy the following files:

sajdbc.jar This must be in the application's classpath. This file is located in the SQL Anywhere installation java folder.
The JDBC driver support files.

To deploy the jConnect JDBC driver, you must deploy the following files:

The jConnect driver files. For a version of the jConnect software and the jConnect documentation, see http://www.sybase.com/products/allproductsa-z/softwaredeveloperkit/jconnect.
When you use a TDS client (either Open Client or jConnect based), you have the option of sending the connection password in clear text or in encrypted form. The latter is done by performing a TDS encrypted password handshake. The handshake involves using private/public key encryption. The support for generating the RSA private/public key pair and for decrypting the encrypted password is included in a special library. The library file must be locatable by the SQL Anywhere server in its system path. For Windows, this file is called dbrsakp12.dll. There are both 64-bit and 32-bit versions of the DLL. On Linux and Unix environments, the file is a shared library called libdbrsakp12.so. On Mac OS X, the file is a shared library called libdbrsakp12.dylib. The file is not necessary if you do not use this feature.