Download appropriate driver software installation archive using the instructions provided in the section that covers interaction with the OpenLink Software Download Wizard. You would have selected "Java Virtual Machine" as your client operating system when interacting with the OpenLink download Wizard and then have the files "megathin.jar" or "megathin2.jar" presented in the download results page depending on the version of the Java Virtual Machine selected

Place the "megathin.jar" or "megathin2.jar" file into directory of your choice then add the directory and reference to the JAR file to your CLASSPATH environment variable. See example below:

Windows 95/98/NT/2000

Presuming you place the "megathin.jar" file in the "\program files\openlink\jdk11" on your Windows machine, you would add the following line to your "autoexec.bat" if you are running Windows 95/98:

set CLASSPATH=%CLASSPATH%;"c:\program files\openlink\jdk11\megathin.jar":. 

If you are using NT or Windows 2000 " then you need to open the "System Environment" properties of the "System" Control Panel applet and then add the same entry to the "System Variables" section if you want the driver to be accessible to all users, if not place the entry in the "User Variables" section.

Reboot your machine

Verify your OpenLink Driver for JDBC client components installation by running one of the following commands (depending on your choice of driver for JDBC) from a DOS Window's command prompt:

If you receive output indicating the relevant OpenLink component branding then this indicates that the drivers have been installed correctly and are ready for use with you Java environment, anything else indicates something is wrong. Typically this would be a mismatch between the Java Virtual machine (your default Java environment) and the OpenLink Driver for JDBC classes. Correcting your PATH or CLASSPATH environment variable entries will typically resolve these problems.

Verify your OpenLink Driver for JDBC server components installation by starting a Web Browser session and then entering the following URL:

http://localhost:8000 or http://<hostname of current machine>:8000

If you are presented with the Home Page of the OpenLink Admin Assistant then this confirms that your OpenLink Server environment is also correctly setup.

Verify your OpenLink Database server components. Do this by changing into the "bin" sub-directory of the OpenLink base directory. Then run an agent with the --help parameter. For example:

ora80_sv --help  (this will verify the Oracle Database Agent)
pro83a_sv --help (this will verify the Progress Database Agent)
syb10_sv --help  (this will verify the Sybase Database Agent)
inf73_sv --help  (this will verify the Informix Database Agent)
ingii_sv --help  (this will verify the Ingres II Database Agent)
db2_sv --help    (this will verify the IBM DB2 Database Agent)

See the detailed section about OpenLink Database Agents for additional information.

Presuming you place the "megathin.jar" file in the "/opt/openlink/jdk11" on your Linux or UNIX machine, you would need to modify the following line in the file "openlink.sh" so that they match what is listed below:

CLASSPATH=$CLASSPATH:/opt/openlink/jdk1.1.x/megathin.jar

Run the script "openlink.sh" (you may also want to add a reference to this in your ".profile" file) by executing the following command from your Linux or UNIX command line prompt:

. openlink.sh

Verify your OpenLink Driver for JDBC client components installation by running one of the following commands (depending on your choice of driver for JDBC) from a DOS Window's command prompt:

If you receive output indicating the relevant OpenLink component branding then this indicates that the drivers have been installed correctly and are ready for use with you Java environment, anything else indicates something is wrong. Typically this would be a mismatch between the Java Virtual machine (your default Java environment) and the OpenLink Driver for JDBC classes. Correcting your PATH or CLASSPATH environment variable entries will typically resolve these problems.