CLASSPATH is the location of the jConnect runtime classes and/or jar files for JDK 1.4.x or later. This section describes what you need in your CLASSPATH depending on which versions of JDK and jConnect you are using.
To use jConnect 6.05 with JDK versions 1.4.x and later, add the following path to the CLASSPATH environment variable:
On UNIX or Linux:
$JDBC_HOME/classes/jconn3.jar
On Windows:
%JDBC_HOME%\classes\jconn3.jar
To run the samples or the TDS-tunnelling servlet, add the following to the CLASSPATH environment variable:
On UNIX or Linux:
$JDBC_HOME/classes/jconn3.jar:$JDBC_HOME/classes
On Windows:
%JDBC_HOME%\classes\jconn3.jar;%JDBC_HOME%\classes
Sybase requires that you run JDK 1.4.2 or later with
jConnect 6.05.
In addition, the CLASSPATH should include the location of any application classes you have defined.
If you use Netscape, some restrictions may apply to the way you set your CLASSPATH environment variable.
The Java VM security manager will not allow a version of jConnect installed in your local file system to create a connection to a server, even if the server is your local system. This can create a problem if you use Netscape to run an applet that uses jConnect.
When Netscape needs to load jConnect to create a connection to a server, it looks for a CLASSPATH defined in its environment to find the jConnect classes. If it finds a CLASSPATH that you have defined to point to your local jConnect installation, it loads jConnect directly from the local file system—rather than from the server—and tries to create a connection. This generates a security error and the connection fails.
In summary, if you are using Netscape to run jConnect applets, do not set the CLASSPATH to the local jConnect directory.
