OpenLink Drivers for JDBC Installation & Configuration

OpenLink Drivers for JDBC™ Installation & Configuration

Windows 95/98/NT/2000 Based Local Client-Server Environment
Windows 95/98/NT/2000 Based Client-Server Environment
Windows 95/98/NT/2000 Based Application-Server Environment
Linux or UNIX Based Local Client-Server Environment
Linux or UNIX Based Client-Server Environment
Linux or UNIX Based Application-Server Environment
Pure Java Local Client-Server Environment
Pure Java Client-Server Environment
Pure Java Application-Server Environment
Mixed Operating System Environments

OpenLink Database Connectivity Middleware Configuration

OpenLink Drivers for JDBC Utilization

OpenLink Type 1 Drivers for JDBC™
OpenLink Type 2 Drivers for JDBC™
OpenLink Type 3 Drivers for JDBC™

Connecting To Remote ODBC DSNs
Connecting To Remote UDBC DSNs
Connecting To Databases Using DSN-Less Connections
Connecting To Remote Databases On Separate Server Machine (OpenLink 3-Tier Architecture)
Connecting To Remote Databases On Separate Server Machine Using Database Vendor's Networking (Mixed 3-Tier Architecture)

OpenLink Demonstration Programs

JDBC Compliant Applet Demos

JDBCDemo
ScrollDemo
ScrollDemo2
RowSetDemo

JDBC Compliant Application Demos

Running Demos on Windows 95/98/NT/2000
Running Demos on Linux or UNIX

Important Mutli-User JDBC Solution Development & Utilization Issues

Sensitivity To Changes In Underlying Database
Concurrency Control

Introduction

The OpenLink Drivers for JDBC™ enable the development, deployment, and utilization of database independent Java Applications, Applets, Servlets, and Bean Components (collectively called JDBC Clients) that conform to the JDBC 1.0.2, JDBC 1.1.x, or JDBC 2.0.x specifications from JavaSoft.

JDBC clients are built by importing the "java.sql.*" collection of classes known as the JDBC Driver Manager interface. The JDBC Driver Manager uses JDBC URLs to link JDBC clients with JDBC Drivers. It is important to note that JDBC URLs are JDBC Driver specific. Detailed information regarding JDBC is available from: http://java.sun.com/products/jdbc/index.html

Downloading Driver Software

The OpenLink Drivers for JDBC are packaged either as a bundle alongside the other OpenLink data access drivers (ODBC, UDBC, and OLE-DB) that make up the OpenLink Universal Data Access Driver Suite or as a separate release archive which contains only the OpenLink Megathin Drivers for JDBC, a 100% pure Java Driver for JDBC.

When you download the drivers as part of the data access driver suite bundle three driver types for JDBC are available to you:

OpenLink Driver for JDBC Type 1 (JDBC-ODBC Bridge)
OpenLink Driver for JDBC Type 2 (JDBC-Native Bridge)
OpenLink Driver for JDBC Type 3 (Network enabled all Java Driver)

When you download the OpenLink Megathin Drivers for JDBC you only get a very thin 100% Pure Java Type 3 Driver for JDBC known as the OpenLink Megathin Driver for JDBC.

OpenLink Web Download Wizard Interaction

If you aren't installing these Drivers from a CD you would have to visit the OpenLink Web Site's download page to obtain these Drivers.

The screen shots that follow depict the OpenLink download wizard interaction that is required in order to download either the JDBC Driver bundle or the standalone Megathin Drivers.

Download Wizard Interaction for obtaining OpenLink Drivers for JDBC Bundle

Select a Client Operating System from the "Select Client Operating System" listbox and then select a database engine that you will be connecting to via your Driver for JDBC using the "Select Database" listbox.
Pick one or more server components matching the server operating system that will host the OpenLink Server components required by the Drivers for JDBC. Then click on the "Download Selected Software" button.
Download all the software components presented in the "Software Download" page.

Download Wizard Interaction for obtaining OpenLink Megathin Drivers for JDBC

Select a Java Virtual Machine version from the "Select Client Operating System" listbox and then select a database engine that you will be connecting to via your Driver for JDBC using the "Select Database" listbox.
Pick one or more server components matching the server operating system that will host the OpenLink Server components required by the Drivers for JDBC. Then click on the "Download Selected Software" button.
Download all the software components presented in the "Software Download" page.

OpenLink Drivers for JDBC Installation & Configuration

Once you have downloaded your OpenLink drivers for JDBC using the instructions provided above, the next step in the process is the actual configuration of these drivers for use within your operating environment.

Java is operating system independent by virtue of its core philosophy, but JDBC Drivers may or may not be operating system independent as this is JDBC Driver format and implementation specific. The sections that follow walk your through the OpenLink Driver for JDBC installation and configuration process.

Windows 95/98/NT/2000 Based Local Client-Server Environment

In this scenario your Windows machine is acting as the host machine for both your OpenLink client and server components, implying that you are going to install your OpenLink Client and Server components for JDBC on the same machine.

Installation Process

Download appropriate driver software installation archive using the instructions provided in the section that covers interaction with the OpenLink Software Download Wizard
As Windows 95/98/NT/200 is playing the dual role of both Client and Server machine for your OpenLink components, you would have downloaded a ZIP archive that contains both the OpenLink Client & Server components for this platform. Extract the contents of this ZIP archive to a temporary installation folder and then run the "Setup.exe" program
The archive you have downloaded will contain the entire suite of Data Access Drivers for this platform. If you do not require the OpenLink ODBC or OLE-DB Drivers simply uncheck these components using the installers component list dialog when presented during the install process
The installer will automatically determine what version of the Java Virtual Machine is installed on your machine and then automatically checks which OpenLink Drivers for JDBC java classes should be checked for installation by default. You can override this settings during the installation process so as to match your specific requirements should they differ from those derived by the installer.
The installer will also add the OpenLink Driver for JDBC class files that you have selected in step 3 to the CLASSPATH environment variable on your system
Reboot your system

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:

OpenLink Driver for JDBC Type	Verification Command
Generic Driver for JDBC 1.0.2	java openlink.jdbc.Driver
Generic Driver for JDBC 1.1.x	java openlink.jdbc.Driver
Generic Driver for JDBC 1.2.x or 2.x	java openlink.jdbc2.Driver
Megathin Driver for JDBC 1.1.x	java openlink.megathin.Driver
Megathin Driver for JDBC 1.2.x or 2.x	java openlink.megathin2.Driver

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/

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.

An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink JDBC server components called the OpenLink JDBC agents. You do this by starting a DOS command Window and then move into the "bin" sub-directory of your OpenLink installation directory (default is "c:\program files\openLink"). Then run the following commands:

jdbc_sv -? - this will verify the default JDBC Agent
jodbc_sv -? - This will verify the JDBC-ODBC Agent
judbc_sv -? - This will verify the JDBC-UDBC Agent
An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink Database server components called the OpenLink Database agents. You do this by moving into the "bin" sub-directory of your OpenLink installation's base installation directory. Then run one of the following commands (depending on what database(s) you will be connecting to via JDBC):

ora8_sv -? :this will verify the Oracle Database Agent
pro83a_sv -? :this will verify the Progress Database Agent
syb10_sv -? : this will verify the Sybase Database Agent
inf7_sv -? : this will verify the Informix Database Agent
ing7_sv -? : this will verify the Ingres II Database Agent
db2_sv -? : this will verify the IBM DB2 Database Agent

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

Windows 95/98/NT/2000 Based Client-Server (2-Tier Configuration) Environment

In this scenario one or more Windows machines act as the host machine for your OpenLink client components, while a separate Windows server machine hosts your OpenLink server components. This Windows server machine also hosts the database engine that you will be connecting to via JDBC, this machine is typically referred to as your Database Server machine.

Client Components Installation

Download appropriate driver software using the instructions provided in the section that covers interaction with the OpenLink Software Download Wizard on to your designated client machine
As Windows 95/98/NT/200 is playing the single role of Client machine for your OpenLink Drivers for JDBC, you would have downloaded a ZIP archive that contains only the OpenLink Client components. Extract the contents of this ZIP archive to a temporary installation folder and then run the "Setup.exe" program
The archive you have downloaded will contain the entire suite of Data Access Drivers for this platform. If you do not require the OpenLink ODBC or OLE-DB Drivers simply uncheck these components using the installers component list dialog when presented during the install process
The installer will automatically determine what version of the Java Virtual Machine is installed on your machine and then automatically checks which OpenLink Drivers for JDBC java classes should be checked for installation by default. You can override this settings during the installation process so as to match your specific requirements should they differ from those derived by the installer
The installer will also add the OpenLink Driver for JDBC class files that you have selected in step 3 to the CLASSPATH environment variable on your system
Reboot your system

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:

OpenLink Driver for JDBC Type	Verification Command
Generic Driver for JDBC 1.0.2	java openlink.jdbc.Driver
Generic Driver for JDBC 1.1.x	java openlink.jdbc.Driver
Generic Driver for JDBC 1.2.x or 2.x	java openlink.jdbc2.Driver
Megathin Driver for JDBC 1.1.x	java openlink.megathin.Driver
Megathin Driver for JDBC 1.2.x or 2.x	java openlink.megathin2.Driver

Server Components Installation

Download appropriate server components software using the instructions provided in the section that covers interaction with the OpenLink Software Download Wizard on to your designated server machine
As Windows 95/98/NT/200 is playing the single role of Server machine for your OpenLink Drivers for JDBC, you would have downloaded a ZIP archive that contains only the OpenLink Server components. Extract the contents of this ZIP archive to a temporary installation folder and then run the "Setup.exe" program
The archive you have downloaded will contain both OpenLink client and Server components for this platform. Since you are setting up a Server machine simply uncheck the OpenLink Client components (ODBC, JDBC, OLE-DB) using the installers component list dialog when presented during the install process, this ensures that you only install OpenLink Server components on your Server machine(s)
If you are an existing OpenLink user please ensure that you do not have an OpenLink Request Broker process running (check your services control panel item), if there is a Request Broker process running please shut it down at this point
Run the "setup.exe" program
Start the OpenLink Request Broker, you this by either going into your "Services" control panel (for Windows NT) or to the "OpenLink Data Access Drivers" Windows Start Menu, and then click on the "Broker Startup" menu item
Verify your OpenLink Driver for JDBC server components installation by starting a Web Browser session from either your OpenLink Client or Server machine and then enter one of the following URLs:

From Client Machine: http://<server name or IP address>:8000

From Server Machine: http://localhost: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.

An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink JDBC server components called the OpenLink JDBC agents. You do this by starting a DOS command Window and then move into the "bin" sub-directory of your OpenLink installation directory (default is "c:\program files\openLink"). Then run the following commands:

jdbc_sv -? - this will verify the default JDBC Agent
jodbc_sv -? - This will verify the JDBC-ODBC Agent
judbc_sv -? - This will verify the JDBC-UDBC Agent
An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink Database server components called the OpenLink Database agents. You do this by moving into the "bin" sub-directory of your OpenLink installation's base installation directory. Then run one of the following commands (depending on what database(s) you will be connecting to via JDBC):

ora8_sv -? :this will verify the Oracle Database Agent
pro83a_sv -? :this will verify the Progress Database Agent
syb10_sv -? : this will verify the Sybase Database Agent
inf7_sv -? : this will verify the Informix Database Agent
ing7_sv -? : this will verify the Ingres II Database Agent
db2_sv -? : this will verify the IBM DB2 Database Agent

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

Windows 95/98/NT/2000 Based Application-Server (3-Tier Configuration) Environment

In this scenario your OpenLink Client and Server components for JDBC are installed on an Application Server, as this is where your JDBC based application will be hosted and developed (if you are building a JDBC based 3-Tier solution). Thus, the installation process is broken down into two parts, Application Server, and Database Server components installation. You will not need to install any software on the client machines being used by your JDBC solutions end-users.

Application Server Components Installation

Download appropriate server components software using the instructions provided in the section that covers interaction with the OpenLink Software Download Wizard on to your designated server machine
As this machine needs to host both Client and Server components (by virtue of this machine playing the role of Application Server), you would have downloaded a ZIP archive that contains both the OpenLink Client & Server components for this platform. Extract the contents of this ZIP archive to a temporary installation folder and then run the "Setup.exe" program
The archive you have downloaded will contain the entire suite of Data Access Drivers for this platform. If you do not require the OpenLink ODBC or OLE-DB Drivers simply uncheck these components using the installers component list dialog when presented during the install process.
If you choose to use OpenLink's Database Independent Networking to connect to remote database engines hosted on one or more dedicated Database Server machine, then ensure that an OpenLink Database Agent checkbox for each Database Engine type is checked from the component list presented by the installer. If on the other hand you choose to use Database Specific Networking provided by your database vendor(s) when connecting to your remote Database Engine(s) hosted on your dedicated Database Server machines, then simply leave all the OpenLink Database Agent checkboxes unchecked.

SQL*Net, Open Client, Progress Client. I-Connect, Ingres Net, and Netlib are database specific networking products for Oracle, Sybase, Progress, Informix, Ingres, and Microsoft SQL Server respectively.
The installer will automatically determine what version of the Java Virtual Machine is installed on your machine and then automatically checks which OpenLink Drivers for JDBC java classes should be checked for installation by default. You can override this settings during the installation process so as to match your specific requirements should they differ from those derived by the installer
The installer will also add the OpenLink Driver for JDBC class files that you have selected in step 3 to the CLASSPATH environment variable on your system
Reboot your system

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:

OpenLink Driver for JDBC Type	Verification Command
Generic Driver for JDBC 1.0.2	java openlink.jdbc.Driver
Generic Driver for JDBC 1.1.x	java openlink.jdbc.Driver
Generic Driver for JDBC 1.2.x or 2.x	java openlink.jdbc2.Driver
Megathin Driver for JDBC 1.1.x	java openlink.megathin.Driver
Megathin Driver for JDBC 1.2.x or 2.x	java openlink.megathin2.Driver

Verify your OpenLink Driver for JDBC server components installation by starting a Web Browser session from either your OpenLink Client or Server machine and then enter one of the following URLs:

From Client Machine: http://<server name or IP address>:8000

From Server Machine: http://localhost: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.

An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink JDBC server components called the OpenLink JDBC agents. You do this by starting a DOS command Window and then move into the "bin" sub-directory of your OpenLink installation directory (default is "c:\program files\openLink"). Then run the following commands:

jdbc_sv -? - this will verify the default JDBC Agent
jodbc_sv -? - This will verify the JDBC-ODBC Agent
judbc_sv -? - This will verify the JDBC-UDBC Agent
If you are going to be connecting to your remote database servers using database specific networking provided by one or more database vendors then you need to perform an additional check to ensure that your database agent have been installed properly. You do this by starting a DOS command Window and then move into the "bin" sub-directory of your OpenLink installation directory (default is "c:\program files\openLink"). Then run one of the following commands (depending on what database(s) you will be connecting to via JDBC):

ora8_sv -? :this will verify the Oracle Database Agent
pro83a_sv -? :this will verify the Progress Database Agent
sql6_sv -? :this will verify the Microsoft SQL Server Database Agent
syb10_sv -? : this will verify the Sybase Database Agent
db2_sv -? : this will verify the IBM DB2 Database Agent

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

Database Server Components Installation

This step is only required if your are connecting your Application Server components installed in the prior section to a remote database engine hosted on a dedicated Database Server machine using OpenLink's Database Independent Networking.

Download appropriate server components software using the instructions provided in the section that covers interaction with the OpenLink Software Download Wizard on to your designated server machine
As Windows 95/98/NT/2000 is playing the single role of a dedicated Database Server machine for your OpenLink Application Server components for JDBC, you would have downloaded a ZIP archive that contains only the OpenLink Server components. Extract the contents of this ZIP archive to a temporary installation folder and then run the "Setup.exe" program
The archive you have downloaded will contain both OpenLink client and Server components for this platform. Since you are setting up a Server machine simply uncheck the OpenLink Client components (ODBC, JDBC, OLE-DB) using the installers component list dialog when presented during the install process, this ensures that you only install OpenLink Server components on your Server machine(s)
Ensure that an OpenLink Database Agent checkbox for each Database Engine type is checked from the component list presented by the installer. Uncheck all JDBC component related checkboxes unless you anticipate using this dedicated Database Server as an Application Server at a later date.
If you are an existing OpenLink user please ensure that you do not have an OpenLink Request Broker process running (check your services control panel item), if there is a Request Broker process running please shut it down at this point
Run the "setup.exe" program
Start the OpenLink Request Broker, you do this by either going into your "Services" control panel (for Windows NT) or to the "OpenLink Data Access Drivers" Windows Start Menu, and then click on the "Broker Startup" menu item
Verify your OpenLink Database server components installation by starting a Web Browser session from either your OpenLink Client, Application or Server machine and then enter one of the following URLs:

From Client or Application Server Machine: http://<server name or IP address>:8000

From Database Server Machine: http://localhost: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.

An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink Database server components called the OpenLink Database agents. You do this by starting a DOS command Window and then move into the "bin" sub-directory of your OpenLink installation directory (default is "c:\program files\openLink"). Then run one of the following commands (depending on what database(s) you will be connecting to via JDBC):

ora8_sv -? :this will verify the Oracle Database Agent
pro83a_sv -? :this will verify the Progress Database Agent
sql6_sv -? :this will verify the Microsoft SQL Server Database Agent
syb10_sv -? : this will verify the Sybase Database Agent
db2_sv -? : this will verify the IBM DB2 Database Agent

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

Linux or UNIX Based Local Client-Server Configuration

In this scenario your Linux or UNIX machine is acting as the host machine for both your OpenLink client and server components, implying that you are going to install your OpenLink Client and Server components for JDBC on the same machine.

Installation Process

Download appropriate driver software installation archive using the instructions provided in the section that covers interaction with the OpenLink Software Download Wizard. Ensure that you hatched a checkbox for each Database Engine type that you will be connecting to via JDBC.
Move the Request Broker and Database Agent archives into a temporary installation folder on your Linux or UNIX machine then run the following commands from the command line prompt:

Linux:
rpm -ivh openlink-3.2-2.rpm
rpm -ivh openlink-agents-3.2-2.i386-glibc2.rpm (for glibc2 based Linux Environments)
or
rpm -ivh openlink-agents-3.2-2.i386-libc5.rpm (for libc5 based Linux Environments)

Linux (if your Linux system does not have the RPM facility) and UNIX:

sh install.sh
Follow the instructions presented by the installer for configuring your OpenLink Database Agents, if you installed via a Linux RPM archive, post RPM installation you will need to run the "oplcfg" located in the "openlink/bin" sub-directory of your OpenLink base installation directory
The installer creates an OpenLink environment setup script named "openlink.sh" in the openlink installation's base installation directory. This files contains the following entries which you can modify so as to match the OpenLink Drivers for JDBC to the appropriate Java environment on your machine:

#CLASSPATH=$CLASSPATH:/dbs/openlink/v32/openlink/jdk1.0.2/opljdbc.zip
CLASSPATH=$CLASSPATH:/dbs/openlink/v32/openlink/jdk1.1.x/opljdbc.jar
#CLASSPATH=$CLASSPATH:/dbs/openlink/v32/openlink/jdk1.2.x/opljdbc2.zip
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:

OpenLink Driver for JDBC Type	Verification Command
Generic Driver for JDBC 1.0.2	java openlink.jdbc.Driver
Generic Driver for JDBC 1.1.x	java openlink.jdbc.Driver
Generic Driver for JDBC 1.2.x or 2.x	java openlink.jdbc2.Driver
Megathin Driver for JDBC 1.1.x	java openlink.megathin.Driver
Megathin Driver for JDBC 1.2.x or 2.x	java openlink.megathin2.Driver

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.

An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink JDBC server components called the OpenLink JDBC agents. You do this by starting a DOS command Window and then move into the "bin" sub-directory of your OpenLink installation directory (default is /opt/openlink for Linux and /usr/openlink for UNIX). Then run the following commands:

jdbc_sv -? - this will verify the default JDBC Agent
jodbc_sv -? - This will verify the JDBC-ODBC Agent
judbc_sv -? - This will verify the JDBC-UDBC Agent
An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink Database server components called the OpenLink Database agents. You do this by moving into the "bin" sub-directory of your OpenLink installation's base installation directory. Then run one of the following commands (depending on what database(s) you will be connecting to via JDBC):

ora8_sv -? :this will verify the Oracle Database Agent
pro83a_sv -? :this will verify the Progress Database Agent
syb10_sv -? : this will verify the Sybase Database Agent
inf7_sv -? : this will verify the Informix Database Agent
ing7_sv -? : this will verify the Ingres II Database Agent
db2_sv -? : this will verify the IBM DB2 Database Agent

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

Linux or UNIX Based Client-Server (2-Tier Configuration) Installation

In this scenario one or more Linux or UNIX machines act as the host machine for your OpenLink client components, while a separate Linux or UNIX server machine hosts your OpenLink server components. This Linux or UNIX server machine also hosts the database engine that you will be connecting to via JDBC, this machine is typically referred to as your Database Server machine.

Client Components Installation

Download appropriate driver software installation archive using the instructions provided in the section that covers interaction with the OpenLink Software Download Wizard
Although Linux or UNIX is only playing role of both Client machine for your OpenLink components, you still need to download a Linux RPM or a UNIX compressed TAR archive containing the OpenLink Request Broker (the download page clearly identifies this archive), this contains both the OpenLink Request Broker and the OpenLink Driver for JDBC components. Move this archive to a temporary installation folder and then run the following installation programs:

Linux:

rpm -ivh openlink-3.2-2.rpm

Linux (if your Linux system does not have the RPM facility) and UNIX:

sh install.sh
The installer creates an OpenLink environment setup script named "openlink.sh" in the openlink installation base installation directory. This files contains the following entry which you can modify so as to match the OpenLink Drivers for JDBC to the appropriate Java environment on your machine:

#CLASSPATH=$CLASSPATH:/dbs/openlink/v32/openlink/jdk1.0.2/opljdbc.zip
CLASSPATH=$CLASSPATH:/dbs/openlink/v32/openlink/jdk1.1.x/opljdbc.jar
#CLASSPATH=$CLASSPATH:/dbs/openlink/v32/openlink/jdk1.2.x/opljdbc2.zip
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:

OpenLink Driver for JDBC Type	Verification Command
Generic Driver for JDBC 1.0.2	java openlink.jdbc.Driver
Generic Driver for JDBC 1.1.x	java openlink.jdbc.Driver
Generic Driver for JDBC 1.2.x or 2.x	java openlink.jdbc2.Driver
Megathin Driver for JDBC 1.1.x	java openlink.megathin.Driver
Megathin Driver for JDBC 1.2.x or 2.x	java openlink.megathin2.Driver

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.

An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink JDBC server components called the OpenLink JDBC agents. You do this by starting a DOS command Window and then move into the "bin" sub-directory of your OpenLink installation directory (default is /opt/openlink for Linux and /usr/openlink for UNIX). Then run the following commands:

jdbc_sv -? - this will verify the default JDBC Agent
jodbc_sv -? - This will verify the JDBC-ODBC Agent
judbc_sv -? - This will verify the JDBC-UDBC Agent
An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink Database server components called the OpenLink Database agents. You do this by moving into the "bin" sub-directory of your OpenLink installation's base installation directory. Then run one of the following commands (depending on what database(s) you will be connecting to via JDBC):

ora8_sv -? :this will verify the Oracle Database Agent
pro83a_sv -? :this will verify the Progress Database Agent
syb10_sv -? : this will verify the Sybase Database Agent
inf7_sv -? : this will verify the Informix Database Agent
ing7_sv -? : this will verify the Ingres II Database Agent
db2_sv -? : this will verify the IBM DB2 Database Agent

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

Database Server Components Installation

Only perform these steps if you are connecting to database engines hosted on your dedicated Database Server using OpenLink's Database Independent Networking:

Download appropriate server components installation archive using the instructions provided in the section that covers interaction with the OpenLink Software Download Wizard. Ensure that you hatched a checkbox for each Database Engine type that you will be connecting to via JDBC.
Move the Request Broker and Database Agent archives into a temporary installation folder on your Database Server machine then run the following commands from the command line prompt:

Linux:
rpm -ivh openlink-3.2-2.rpm
rpm -ivh openlink-agents-3.2-2.i386-glibc2.rpm (for glibc2 based Linux Environments)
or
rpm -ivh openlink-agents-3.2-2.i386-libc5.rpm (for libc5 based Linux Environments)

Linux (if your Linux system does not have the RPM facility) and UNIX:

sh install.sh
Follow the instructions presented by the installer for configuring your OpenLink Database Agents
An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink Database server components called the OpenLink Database agents. You do this by moving into the "bin" sub-directory of your OpenLink installation's base installation directory. Then run one of the following commands (depending on what database(s) you will be connecting to via JDBC):

ora8_sv -? :this will verify the Oracle Database Agent
pro83a_sv -? :this will verify the Progress Database Agent
syb10_sv -? : this will verify the Sybase Database Agent
inf7_sv -? : this will verify the Informix Database Agent
ing7_sv -? : this will verify the Ingres II Database Agent
db2_sv -? : this will verify the IBM DB2 Database Agent

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

Linux or UNIX Based Application-Server (3-Tier Configuration) Installation

In this scenario your OpenLink Client machine plays the role of an Application Server, as this is where your JDBC based application will be hosted and developed (if you are building a 3-Tier JDBC solution). Thus, the installation process is broken down into two parts, Application Server, and Database Server components installation. You will not need to install any software on the machines being used by your JDBC solution's end-users.

Application Server Components Installation

Download appropriate driver software installation archive using the instructions provided in the section that covers interaction with the OpenLink Software Download Wizard. Ensure that you hatched a checkbox for each Database Engine type that you will be connecting to via JDBC.
Although Linux or UNIX is only playing role of Client machine for your OpenLink components, you still need to download Linux RPMs or a UNIX compressed TAR archives containing the OpenLink Request Broker and the Database Agents for each database engine that you will be connecting to via JDBC (the download page clearly identifies these archives).
Move the Request Broker and this archive to a temporary installation folder, if you choose to use OpenLink's Database Independent Networking to connect to remote database engines hosted on one or more dedicated Database Server machines, do not move the Database Agent archives into the temporary installation directory on the Application Server. Run the following installation programs from the temporary installation directory on your Application Server machine:

Linux:

rpm -ivh openlink-3.2-2.rpm

Linux (if your Linux system does not have the RPM facility) and UNIX:

sh install.sh
Linux:

rpm -ivh openlink-3.2-2.rpm

Linux (if your Linux system does not have the RPM facility) and UNIX:

sh install.sh

* Ignore the Database Agent configuration menu when presented to you by the installer. *

If on the other hand you choose to use Database Specific Networking provided by your database vendor(s) when connecting to your remote Database Engine(s) hosted on your dedicated Database Server machines, then then move each Database Agent archive into a temporary installation directory alongside the Request Broker archive and then run the following installation programs:

Linux:
rpm -ivh openlink-3.2-2.rpm
rpm -ivh openlink-agents-3.2-2.i386-glibc2.rpm (for glibc2 based Linux Environments)
or
rpm -ivh openlink-agents-3.2-2.i386-libc5.rpm (for libc5 based Linux Environments)

Linux (if your Linux system does not have the RPM facility) and UNIX:

sh install.sh
The installer creates an OpenLink environment setup script named "openlink.sh" in the openlink installation base installation directory. This files contains the following entry which you can modify so as to match the OpenLink Drivers for JDBC to the appropriate Java environment on your machine:

#CLASSPATH=$CLASSPATH:/dbs/openlink/v32/openlink/jdk1.0.2/opljdbc.zip
CLASSPATH=$CLASSPATH:/dbs/openlink/v32/openlink/jdk1.1.x/opljdbc.jar
#CLASSPATH=$CLASSPATH:/dbs/openlink/v32/openlink/jdk1.2.x/opljdbc2.zip
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:

OpenLink Driver for JDBC Type	Verification Command
Generic Driver for JDBC 1.0.2	java openlink.jdbc.Driver
Generic Driver for JDBC 1.1.x	java openlink.jdbc.Driver
Generic Driver for JDBC 1.2.x or 2.x	java openlink.jdbc2.Driver
Megathin Driver for JDBC 1.1.x	java openlink.megathin.Driver
Megathin Driver for JDBC 1.2.x or 2.x	java openlink.megathin2.Driver

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.

An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink JDBC server components called the OpenLink JDBC agents. You do this by starting a DOS command Window and then move into the "bin" sub-directory of your OpenLink installation directory (default is /opt/openlink for Linux and /usr/openlink for UNIX). Then run the following commands:

jdbc_sv -? - this will verify the default JDBC Agent
jodbc_sv -? - This will verify the JDBC-ODBC Agent
judbc_sv -? - This will verify the JDBC-UDBC Agent
Verify your OpenLink Database server components installation by starting a Web Browser session from either your OpenLink Client, Application or Server machine and then enter one of the following URLs:

From Client Machine: http://<server name or IP address>:8000

From Database Server Machine: http://localhost: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.

An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink Database server components called the OpenLink Database agents. You do this by moving into the "bin" sub-directory of your OpenLink installation directory. Then run the following commands:

ora8_sv -? :this will verify the Oracle Database Agent
pro83a_sv -? :this will verify the Progress Database Agent
syb10_sv -? : this will verify the Sybase Database Agent
inf7_sv -? : this will verify the Informix Database Agent
ing7_sv -? : this will verify the Ingres II Database Agent
db2_sv -? : this will verify the IBM DB2 Database Agent

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

Database Server Components Installation

Only perform these steps if you are connecting to database engines hosted on your dedicated Database Server using OpenLink's Database Independent Networking:

Download appropriate server components installation archive using the instructions provided in the section that covers interaction with the OpenLink Software Download Wizard. Ensure that you hatched a checkbox for each Database Engine type that you will be connecting to via JDBC.
Move the Request Broker and Database Agent archives into a temporary installation folder on your Database Server machine then run the following commands from the command line prompt:

Linux:
rpm -ivh openlink-3.2-2.rpm
rpm -ivh openlink-agents-3.2-2.i386-glibc2.rpm (for glibc2 based Linux Environments)
or
rpm -ivh openlink-agents-3.2-2.i386-libc5.rpm (for libc5 based Linux Environments)

Linux (if your Linux system does not have the RPM facility) and UNIX:

sh install.sh
Follow the instructions presented by the installer for configuring your OpenLink Database Agents
The installer creates an OpenLink environment setup script named "openlink.sh" in the openlink installation's base installation directory.
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 Database server components installation by starting a Web Browser session from either your OpenLink Client, Application or Server machine and then enter one of the following URLs:

From Client or Application Server Machine: http://<server name or IP address>:8000

From Database Server Machine: http://localhost: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.

An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink Database server components called the OpenLink Database agents. You do this by moving into the "bin" sub-directory of your OpenLink installation directory. Then run the following commands:

ora8_sv -? :this will verify the Oracle Database Agent
pro83a_sv -? :this will verify the Progress Database Agent
syb10_sv -? : this will verify the Sybase Database Agent
inf7_sv -? : this will verify the Informix Database Agent
ing7_sv -? : this will verify the Ingres II Database Agent
db2_sv -? : this will verify the IBM DB2 Database Agent

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

Java Based Local Client-Server

In this scenario the Java Virtual Machine is acting as the host of your OpenLink client component for JDBC (a 100% Pure Java Driver for JDBC). The operating system hosting your Java Virtual Machine, also hosts the OpenLink Server server components for JDBC. Thus, you are going to install your OpenLink Client and Server components for JDBC on the same machine.

Client Components Installation Process

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 you 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.

Linux or UNIX

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

Server Components Installation

Windows 95/98/NT/200

As Windows 95/98/NT/200 is playing the dual role of both Client and Server machine for your OpenLink components, you would have downloaded a ZIP archive that contains both the OpenLink Client & Server components for this platform. Extract the contents of this ZIP archive to a temporary installation folder and then run the "Setup.exe" program
The archive you have downloaded will contain the entire suite of Data Access Drivers for this platform. If you do not require the OpenLink ODBC or OLE-DB Drivers simply uncheck these components using the installers component list dialog when presented during the install process.
Reboot your system

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:

OpenLink Driver for JDBC Type	Verification Command
Megathin Driver for JDBC 1.1.x	java openlink.megathin.Driver
Megathin Driver for JDBC 1.2.x or 2.x	java openlink.megathin2.Driver

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

http://localhost: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.

An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink JDBC server components called the OpenLink JDBC agents. You do this by starting a DOS command Window and then move into the "bin" sub-directory of your OpenLink installation directory (default is "c:\program files\openLink"). Then run the following commands:

jdbc_sv -? - this will verify the default JDBC Agent
jodbc_sv -? - This will verify the JDBC-ODBC Agent
judbc_sv -? - This will verify the JDBC-UDBC Agent
Verify the existence and state of the OpenLink Database server components called the OpenLink Database agents. You do this by moving into the "bin" sub-directory of your OpenLink installation's base installation directory. Then run the following commands:

ora8_sv -? :this will verify the Oracle Database Agent
pro83a_sv -? :this will verify the Progress Database Agent
syb10_sv -? : this will verify the Sybase Database Agent
inf7_sv -? : this will verify the Informix Database Agent
ing7_sv -? : this will verify the Ingres II Database Agent
db2_sv -? : this will verify the IBM DB2 Database Agent

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

Linux or UNIX Server Components Installation

Download appropriate driver software installation archive using the instructions provided in the section that covers interaction with the OpenLink Software Download Wizard. Ensure that you hatched a checkbox for each Database Engine type that you will be connecting to via JDBC.
Move the Request Broker and Database Agent archives into a temporary installation folder on your Linux or UNIX machine then run the following commands from the command line prompt:

Linux:
rpm -ivh openlink-3.2-2.rpm
rpm -ivh openlink-agents-3.2-2.i386-glibc2.rpm (for glibc2 based Linux Environments)
or
rpm -ivh openlink-agents-3.2-2.i386-libc5.rpm (for libc5 based Linux Environments)

Linux (if your Linux system does not have the RPM facility) and UNIX:

sh install.sh
Follow the instructions presented by the installer for configuring your OpenLink Database Agents, if you installed via a Linux RPM archive, post RPM installation you will need to run the "oplcfg" located in the "openlink/bin" sub-directory of your OpenLink base installation directory
The installer creates an OpenLink environment setup script named "openlink.sh" in the openlink installation's base installation directory. This files contains the following entries which you can modify so as to match the OpenLink Drivers for JDBC to the appropriate Java environment on your machine:

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

Note: This step is only required because the Linux and UNIX installer archives automatically install all the OpenLink Driver types for JDBC, and also perform the default CLASSPATH entry configuration.
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 Linux or UNIX command prompt:

OpenLink Driver for JDBC Type	Verification Command
Megathin Driver for JDBC 1.1.x	java openlink.megathin.Driver
Megathin Driver for JDBC 1.2.x or 2.x	java openlink.megathin2.Driver

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.

An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink JDBC server components called the OpenLink JDBC agents. You do this by starting a DOS command Window and then move into the "bin" sub-directory of your OpenLink installation directory (default is /opt/openlink for Linux and /usr/openlink for UNIX). Then run the following commands:

jdbc_sv -? - this will verify the default JDBC Agent
jodbc_sv -? - This will verify the JDBC-ODBC Agent
judbc_sv -? - This will verify the JDBC-UDBC Agent
An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink Database server components called the OpenLink Database agents. You do this by moving into the "bin" sub-directory of your OpenLink installation's base installation directory. Then run the following commands:

ora8_sv -? :this will verify the Oracle Database Agent
pro83a_sv -? :this will verify the Progress Database Agent
syb10_sv -? : this will verify the Sybase Database Agent
inf7_sv -? : this will verify the Informix Database Agent
ing7_sv -? : this will verify the Ingres II Database Agent
db2_sv -? : this will verify the IBM DB2 Database Agent

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

Java Based Client-Server (2-Tier) Installation

In this scenario the Java Virtual Machine and OpenLink Drivers for JDBC reside on separate to OpenLink Server server components for JDBC and Database Connectivity. Thus, you are going to install your OpenLink Client and Server components for JDBC on separate machines, one acting as the Client and the other the Server. The Server also hosts the actual database engine that you will be connecting to via JDBC.

Windows 95/98/NT/2000 Client Components Installation Process

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 you 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:

OpenLink Driver for JDBC Type	Verification Command
Megathin Driver for JDBC 1.1.x	java openlink.megathin.Driver
Megathin Driver for JDBC 1.2.x or 2.x	java openlink.megathin2.Driver

Linux or UNIX Client Components Installation

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 "openlinks.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 Linux or UNIX command prompt:

OpenLink Driver for JDBC Type	Verification Command
Megathin Driver for JDBC 1.1.x	java openlink.megathin.Driver
Megathin Driver for JDBC 1.2.x or 2.x	java openlink.megathin2.Driver

Server Components Installation

Only perform these steps if you are connecting to database engines hosted on your dedicated Database Server using OpenLink's Database Independent Networking:

Windows 95/98/NT/200

As a separate Windows 95/98/NT/200 is playing the role of Server machine, you would have downloaded a ZIP archive that contains both the OpenLink Client & Server components for this platform. Extract the contents of this ZIP archive to a temporary installation folder on the Windows Server machine and then run the "Setup.exe" program
The archive you have downloaded will contain the entire suite of Data Access Drivers for this platform. If you do not require the OpenLink ODBC or OLE-DB Drivers simply uncheck these components using the installers component list dialog when presented during the install process.
Reboot your system
Verify your OpenLink Driver for JDBC server components installation by starting a Web Browser session and then entering the following URL:

http://localhost: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.

An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink JDBC server components called the OpenLink JDBC agents. You do this by starting a DOS command Window and then move into the "bin" sub-directory of your OpenLink installation directory (default is "c:\program files\openLink"). Then run the following commands:

jdbc_sv -? - this will verify the default JDBC Agent
jodbc_sv -? - This will verify the JDBC-ODBC Agent
judbc_sv -? - This will verify the JDBC-UDBC Agent
Verify the existence and state of the OpenLink Database server components called the OpenLink Database agents. You do this by moving into the "bin" sub-directory of your OpenLink installation directory. Then run the following commands:

ora8_sv -? :this will verify the Oracle Database Agent
pro83a_sv -? :this will verify the Progress Database Agent
syb10_sv -? : this will verify the Sybase Database Agent
inf7_sv -? : this will verify the Informix Database Agent
ing7_sv -? : this will verify the Ingres II Database Agent
db2_sv -? : this will verify the IBM DB2 Database Agent

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

Linux or UNIX Server Components Installation

Download appropriate driver software installation archive using the instructions provided in the section that covers interaction with the OpenLink Software Download Wizard. Ensure that you hatched a checkbox for each Database Engine type that you will be connecting to via JDBC.
Move the Request Broker and Database Agent archives into a temporary installation folder on your Linux or UNIX machine then run the following commands from the command line prompt:

Linux:
rpm -ivh openlink-3.2-2.rpm
rpm -ivh openlink-agents-3.2-2.i386-glibc2.rpm (for glibc2 based Linux Environments)
or
rpm -ivh openlink-agents-3.2-2.i386-libc5.rpm (for libc5 based Linux Environments)

Linux (if your Linux system does not have the RPM facility) and UNIX:

sh install.sh
Follow the instructions presented by the installer for configuring your OpenLink Database Agents, if you installed via a Linux RPM archive, post RPM installation you will need to run the "oplcfg" located in the "openlink/bin" sub-directory of your OpenLink base installation directory
The installer creates an OpenLink environment setup script named "openlink.sh" in the openlink installation's base installation directory. This files contains the following entries which you can modify so as to match the OpenLink Drivers for JDBC to the appropriate Java environment on your machine:

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

Note: This step is only required because the Linux and UNIX installer archives automatically install all the OpenLink Driver types for JDBC, and also perform the default CLASSPATH entry configuration.
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 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.

An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink JDBC server components called the OpenLink JDBC agents. You do this by starting a DOS command Window and then move into the "bin" sub-directory of your OpenLink installation directory (default is /opt/openlink for Linux and /usr/openlink for UNIX). Then run the following commands:

jdbc_sv -? - this will verify the default JDBC Agent
jodbc_sv -? - This will verify the JDBC-ODBC Agent
judbc_sv -? - This will verify the JDBC-UDBC Agent
Verify your OpenLink Database server components, you do this by moving into the "bin" sub-directory of your OpenLink installation's base installation directory. Then run one of the following commands (depending on what database(s) you will be connecting to via JDBC):

ora8_sv -? :this will verify the Oracle Database Agent
pro83a_sv -? :this will verify the Progress Database Agent
syb10_sv -? : this will verify the Sybase Database Agent
inf7_sv -? : this will verify the Informix Database Agent
ing7_sv -? : this will verify the Ingres II Database Agent
db2_sv -? : this will verify the IBM DB2 Database Agent

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

Java Based Application-Server (3-Tier) Installation

In this scenario the Java Virtual Machine and OpenLink Drivers for JDBC and the OpenLink Server server components for JDBC reside on the same machine which is known as the Application Server. The OpenLink Database Server components reside on a separate Database Server machine (if required) which hosts the database that you will be connecting to via JDBC.
Windows 95/98/NT/2000 Client Components Installation Process.

Windows 95/98/NT/2000 Application Server Components Installation

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 you 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:

OpenLink Driver for JDBC Type	Verification Command
Megathin Driver for JDBC 1.1.x	java openlink.megathin.Driver
Megathin Driver for JDBC 1.2.x or 2.x	java openlink.megathin2.Driver

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.

An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink JDBC server components called the OpenLink JDBC agents. You do this by starting a DOS command Window and then move into the "bin" sub-directory of your OpenLink installation directory (default is /opt/openlink for Linux and /usr/openlink for UNIX). Then run the following commands:

jdbc_sv -? - this will verify the default JDBC Agent
jodbc_sv -? - This will verify the JDBC-ODBC Agent
judbc_sv -? - This will verify the JDBC-UDBC Agent
Verify your OpenLink Database server components, you do this by moving into the "bin" sub-directory of your OpenLink installation's base installation directory. Then run one of the following commands (depending on what database(s) you will be connecting to via JDBC):

ora8_sv -? :this will verify the Oracle Database Agent
pro83a_sv -? :this will verify the Progress Database Agent
syb10_sv -? : this will verify the Sybase Database Agent
inf7_sv -? : this will verify the Informix Database Agent
ing7_sv -? : this will verify the Ingres II Database Agent
db2_sv -? : this will verify the IBM DB2 Database Agent

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

Linux or UNIX Application Server Components Installation

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 "openlinks.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:

OpenLink Driver for JDBC Type	Verification Command
Megathin Driver for JDBC 1.1.x	java openlink.megathin.Driver
Megathin Driver for JDBC 1.2.x or 2.x	java openlink.megathin2.Driver

Database Server Components Installation

Only perform these steps if you are connecting to database engines hosted on your dedicated Database Server using OpenLink's Database Independent Networking:

Windows 95/98/NT/200

As a separate Windows 95/98/NT/200 is playing the role of Server machine, you would have downloaded a ZIP archive that contains both the OpenLink Client & Server components for this platform. Extract the contents of this ZIP archive to a temporary installation folder on the Windows Server machine and then run the "Setup.exe" program
The archive you have downloaded will contain the entire suite of Data Access Drivers for this platform. If you do not require the OpenLink ODBC or OLE-DB Drivers simply uncheck these components using the installers component list dialog when presented during the install process.
Reboot your system
Verify your OpenLink Driver for JDBC server components installation by starting a Web Browser session and then entering the following URL:

http://localhost: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.

An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink JDBC server components called the OpenLink JDBC agents. You do this by starting a DOS command Window and then move into the "bin" sub-directory of your OpenLink installation directory (default is "c:\program files\openLink"). Then run the following commands:

jdbc_sv -? - this will verify the default JDBC Agent
jodbc_sv -? - This will verify the JDBC-ODBC Agent
judbc_sv -? - This will verify the JDBC-UDBC Agent
Verify the existence and state of the OpenLink Database server components called the OpenLink Database agents. You do this by moving into the "bin" sub-directory of your OpenLink installation directory. Then run the following commands:

ora8_sv -? :this will verify the Oracle Database Agent
pro83a_sv -? :this will verify the Progress Database Agent
syb10_sv -? : this will verify the Sybase Database Agent
inf7_sv -? : this will verify the Informix Database Agent
ing7_sv -? : this will verify the Ingres II Database Agent
db2_sv -? : this will verify the IBM DB2 Database Agent

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

Linux or UNIX Server

Download appropriate driver software installation archive using the instructions provided in the section that covers interaction with the OpenLink Software Download Wizard. Ensure that you hatched a checkbox for each Database Engine type that you will be connecting to via JDBC.
Move the Request Broker and Database Agent archives into a temporary installation folder on your Linux or UNIX machine then run the following commands from the command line prompt:

Linux:
rpm -ivh openlink-3.2-2.rpm
rpm -ivh openlink-agents-3.2-2.i386-glibc2.rpm (for glibc2 based Linux Environments)
or
rpm -ivh openlink-agents-3.2-2.i386-libc5.rpm (for libc5 based Linux Environments)

Linux (if your Linux system does not have the RPM facility) and UNIX:

sh install.sh
Follow the instructions presented by the installer for configuring your OpenLink Database Agents, if you installed via a Linux RPM archive, post RPM installation you will need to run the "oplcfg" located in the "openlink/bin" sub-directory of your OpenLink base installation directory
The installer creates an OpenLink environment setup script named "openlink.sh" in the openlink installation's base installation directory. This files contains the following entries which you can modify so as to match the OpenLink Drivers for JDBC to the appropriate Java environment on your machine:

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

Note: This step is only required because the Linux and UNIX installer archives automatically install all the OpenLink Driver types for JDBC, and also perform the default CLASSPATH entry configuration.
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 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.

An additional but non compulsory check that you may perform is to actually verify the existence and state of the OpenLink JDBC server components called the OpenLink JDBC agents. You do this by starting a DOS command Window and then move into the "bin" sub-directory of your OpenLink installation directory (default is /opt/openlink for Linux and /usr/openlink for UNIX). Then run the following commands:

jdbc_sv -? - this will verify the default JDBC Agent
jodbc_sv -? - This will verify the JDBC-ODBC Agent
judbc_sv -? - This will verify the JDBC-UDBC Agent
Verify your OpenLink Database server components, you do this by moving into the "bin" sub-directory of your OpenLink installation's base installation directory. Then run one of the following commands (depending on what database(s) you will be connecting to via JDBC):

ora8_sv -? :this will verify the Oracle Database Agent
pro83a_sv -? :this will verify the Progress Database Agent
syb10_sv -? : this will verify the Sybase Database Agent
inf7_sv -? : this will verify the Informix Database Agent
ing7_sv -? : this will verify the Ingres II Database Agent
db2_sv -? : this will verify the IBM DB2 Database Agent

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

Mixed Environment Installations

It is important to note that the client and server operating systems hosting your OpenLink Software do not have to be the same. The Installation instructions have only taken this approach in order to simplify understanding of the installation process. A Linux or UNIX machine can act as a client to a Windows machine and vice versa, all you have to do is follow the steps for installing either the client or server components on the appropriate platform.

OpenLink Server Components Configuration

The OpenLink JDBC agent and OpenLink Database agents form the OpenLink server components, In the prior section you would have installed these components on the appropriate server machine.

Following installation you have to configure these server components in order to enable connectivity between your backend database(s) and your OpenLink Driver for JDBC. Both of these components are exposed to your OpenLink Driver for JDBC via the OpenLink Request Broker.

JDBC Agents

These server components are available in two formats, one based on the OpenLink Generic ODBC technology and the Other based on OpenLink Generic UDBC technology.

The ODBC based agents are identified as "JODBC" agents to the OpenLink Driver for JDBC and packaged as "jodbc_sv.exe" and "jodbc_sv" on Windows and Linux/UNIX platforms respectively. The JODBC agent provides you with the flexibility of either connecting to backend databases via existing ODBC DSNs or directly (DSN-Less connections), this facility also has the added benefit of not restricting the use of your Type 3 OpenLink Driver for JDBC to OpenLink ODBC DSNs. This is how OpenLink provides remote JDBC-ODBC Bridging with out compromising the platform independence or Java Purity required of a Type 3 JDBC Driver.

The UDBC based agents are identified as "JUDBC" agents to the OpenLink Driver for JDBC and packaged as "judbc_sv.exe" and "judbc_sv" on Windows and Linux/UNIX platforms respectively. The JUDBC agent provides you with the flexibility of either connecting to backend databases via existing UDBC DSNs or directly (DSN-Less connections). This is how OpenLink provides remote JDBC-Native Interface Bridging with out compromising the platform independence or Java Purity required of a Type 3 JDBC Driver, the OpenLink UDBC layer acts as a Generic Native Database Interface, it does not have any interaction with an ODBC Driver Manager or ODBC DSNs.

Database Agents

OpenLink Database Agents are the OpenLink data access server components that actually provide database connectivity services to your OpenLink Driver for JDBC. An Database Agent exists for each database engine supported by OpenLink, the supported database list currently includes: Oracle, DB2, Informix, Sybase, Ingres, Progress, Microsoft SQL Server, OpenLink Virtuoso, Solid, PostgresSQL, and other ODBC based databases. Please follow the instructions provided in the OpenLink Database Agents configuration guide prior to attempting to use your OpenLink Drivers for JDBC (if you haven't already done so as part of the installation process).

OpenLink Drivers for JDBC™ Utilization

OpenLink Drivers for JDBC are available in three different JDBC Driver formats.

JDBC Type 1 - Driver for JDBC is implemented as a bridge to ODBC Drivers, thereby implementing the JDBC Driver classes through native methods, this is due to the fact that ODBC is a 'C' language based data access application programming interface. Thus, this driver format is inherently part Java and part Native, implying that it is inherently platform specific rather than independent.
JDBC Type 2 - Driver for JDBC is implemented as a bridge to Native Database Call Level Interfaces, thereby implementing the JDBC Driver classes through native methods, this is due to the fact that Native Database Call Interfaces are either C/C++ language based data access application programming interfaces. Thus, this driver format is inherently part Java and part Native, implying that it is inherently platform specific rather than independent
JDBC Type 3 - Driver for JDBC is implemented in Java sitting atop a database independent networking layer bridge also implemented in Java. Thus, the entire driver is Pure Java and thereby operating system independent.

JDBC Applets, Applications, Bean Components, and Servlets communicate with JDBC drivers through JDBC Uniform Resource Locators (URLs). Theses URLs are service request and binding formats implemented slightly differently for each OpenLink Driver for JDBC format. The general JDBC URL format is:

jdbc:<jdbc-subprotocol>:[jdbc implementation specific URL attributes]

The "sub-protocol" component of the URL above identifies each JDBC implementation and typically identifies the JDBC driver vendor, the actual URL attributes are vendor specific. Each OpenLink Driver for JDBC type has a different JDBC URL format, the sections that follow depict and provides examples of these formats.

OpenLink Driver for JDBC Type 1

URL Format

This driver format connects you to ODBC Data Source Names (DSNs) via JDBC. The URL format is as follows:

jdbc:openlink://ODBC[/DSN][/UID][/PWD][/READONLY]

URL Attributes

/DSN - ODBC Data Source Name
/UID - Username
/PWD - Password
/READONLY - Determines session mode, read-write or read-only.

Example:

If you were attempting to connect to an ODBC DSN on your machine named "Customers Database" in read-only mode then you would enter the following JDBC URL:

jdbc:openlink://ODBC/DSN=Customer Database/UID=test/PWD=test/READONLY=Y

Note: In the case of OpenLink ODBC DSNs you do not have to provide values for the /UID and /PWD attributes since these can be controlled and configured on the database or application server using the OpenLink Session Rules Book.

OpenLink Driver for JDBC Type 2

URL Format

This driver format connects you to UDBC Data Source Names (DSNs) via JDBC. The URL format is as follows:

jdbc:openlink://UDBC[/DSN][/UID][/PWD][/READONLY]

URL Attributes

/DSN - UDBC Data Source Name
/UID - Username
/PWD - Password
/READONLY - Determines session mode, read-write or read-only.

Example:

If you were attempting to connect to an UDBC DSN on your machine named "Customers Database" in read-only mode then you would enter the following JDBC URL:

jdbc:openlink://UDBC/DSN=Customer Database/UID=test/PWD=test/READONLY=Y

OpenLink Driver for JDBC Type 3

URL Format

This driver format connects you to remote database using remote ODBC or UDBC DSNs. It also supports direct DSN-Less connections to remote databases. The URL format is as follows:

jdbc:openlink://<Hostname>:[portnumber] [/DSN] [/UID] [/PWD] [/READONLY] [/FBS] [/JDBCAGENT] [/HOST] [/SVT] [/DATABASE] [/OPTIONS] [/DRIVER]

URL Attributes

Hostname - Network Alias or IP address of server machine running an OpenLink Request Broker instance

Port Number - Port number that identifies location of OpenLink JDBC Agent Service, the default value is 5000

/DSN - ODBC Data Source Name

/UID - Username

/PWD - Password

/READONLY - Determines session mode, read-write or read-only

/FBS - Sets number of JDBC resultset rows that get packed into a single network packet

/JDBCAGENT - Determines JDBC Agent type used rather than default (JDBC Agents exist for ODBC and UDBC)

/HOST - Locates the Network Alias (or IP address) of a server machine that is running an Openlink Request Broker instance. Note that this machine can be different from the <Hostname> value (e.g., in a application server architecture)

/SVT - Determines OpenLink Database Agent type (Oracle, Informix, Sybase, Progress, Ingres, SQL Sever, Sybase etc.)

/DATABASE - Actual database name within a particular database environment

/OPTIONS - Values used to connect to OpenLink Database Agents to remote database servers using database vendors networking

/DRIVER - Used when making a DSN-Less connection to remote ODBC Driver

Examples:

Connecting To Remote ODBC DSN

If you were attempting to connect to a remote ODBC DSN named "Customers Database", hosted on a database server machine with the network alias "pluto", with an OpenLink JDBC server listening at port 5001 (rather than default of 5000), and you wanted this session to be in read-only mode then you would enter the following JDBC URL:

jdbc:openlink://pluto:5001/DSN=Customer Database/UID=test/PWD=test/READONLY=YES/JDBCAGENT=jodbc/FBS=55

Note:

In the case of OpenLink ODBC DSNs you do not have to provide values for the /UID and /PWD attributes since these can be controlled and configured on the database or application server using the OpenLink Session Rules Book
If "pluto" is a Windows 95/98/NT/2000 machine then the "/JDBCAGENT" attribute defaults to "jodbc" when left out of the JDBC URL. Likewise if "pluto" is a Linux or UNIX machine the "/JDBCAGENT" attribute defaults to "judbc"
"/FBS" ensures that each iteration of a JDBC Resultset fetch loop returns 55 records or less until all records have been retrieved from a remote database server

Connecting To Remote UDBC DSN

If you were attempting to connect to a remote UDBC DSN named "Customers Database", hosted on a database server machine with the network alias "pluto", with an OpenLink JDBC server listening at port 5001 (rather than default of 5000), and you wanted this session to be in read-only mode then you would enter the following JDBC URL:

jdbc:openlink://pluto:5001/DSN=Customer Database/UID=test/PWD=test/READONLY=Y/JDBCAGENT=judbc/FBS=55

Note:

In the case of OpenLink UDBC DSNs you do not have to provide values for the /UID and /PWD attributes since these can be controlled and configured on the database or application server using the OpenLink Session Rules Book
If "pluto" is a Linux or UNIX machine then the "/JDBCAGENT" attribute defaults to "judbc" when left out of the JDBC URL. Likewise if "pluto" is a Windows 95/98/NT/2000 machine the "/JDBCAGENT" attribute defaults to "jodbc"
"/FBS" ensures that each iteration of a JDBC Resultset fetch loop returns 55 records or less until all records have been retrieved from a remote database server

Connecting To Databases Using DSN-Less Connections

You do not have to create ODBC or UDBC DSNs in order to use your OpenLink Drivers for JDBC when using the type 3 format. Instead you can specify the OpenLink Database Type and Database Name attributes as part of your JDBC URL. (See full list of attributes in section below.)

To connect to a remote Microsoft SQL Server database without going via an ODBC DSN you would construct the following URL:

jdbc:openlink://saturn:5001/HOST=localhost/SVT=SQLServer 6/DATABASE=pubs/UID=sa/PWD=/FBS=55/READONLY=Y

Notes:

In the case of OpenLink ODBC DSNs you do not have to provide values for the /UID and /PWD attributes since these can be controlled and configured on the database or application server using the OpenLink Session Rules Book
As "saturn" is a Windows 95/98/NT/2000 machine the "/JDBCAGENT" attribute defaults to "jodbc"
This feature applies to both OpenLink JDBC Agent types: JODBC Agent and JUDBC Agent

Connecting To Database via ODBC Driver Without A DSN (DSN-Less Connection)

This JDBC URL format is currently only supported by the OpenLink JDBC Agent for ODBC DSNs (JODBC Agent). DSN-Less connections require you to determine the ODBC connect string attributes for the ODBC Driver that you are using. For OpenLink ODBC Drivers these values are:

/DRIVER - Registered Driver Name as listed in ODBC Driver manager

/UID - Valid Database Username

/PWD - Valid Password for Username

/READONLY - Determines session mode, read-write or read-only.

/SERVERTYPE - Database Agent Type

/HOST - Machine hosting the Database Agent serving an OpenLink ODBC Driver

/FETCHBUFFERSIZE - Number of resulset records fetched during each ODBC fetch loop

/DATABASE - Actual database name within database server environment

/NoLoginBox - Disables OpenLink ODBC Drivers attempt to present dialog when ODBC Driver determines an incomplete ODBC connect string (collection of ODBC attributes passed at connect time), good examples being missing or blank Username and Password attributes.

If you were connecting a remote Oracle database on a machine called "pluto" and you wanted this session to be read-only, your URL formal would be as follows:

jdbc:openlink://pluto/DRIVER={OpenLink Generic 32 Bit Driver}/Database=ORCL/UID=test/PWD=test/
ReadOnly=Yes/FBS=55/ServerType=Oracle 8/Host=pluto

Connecting To Remote Databases On Separate Server Machine (OpenLink 3-Tier Architecture)

You may choose to install your OpenLink Drivers for JDBC on an Application Server and then install your OpenLink Data Access Server components (Request Broker and Database Agents) on your dedicated database server machine. In such a scenario you will be connecting to your remote database engine using OpenLink Database Independent as opposed to your Database vendor's database specific networking middleware.

If you were connecting from your Application Server called "pluto" to a dedicated Database Server machine named "ora_server", hosting an Oracle database identified as "ORCL" you would construct the following JDBC URL:

jdbc:openlink://pluto/SVT=Oracle 6/
UID=test/PWD=test/HOST=ora_server

Notes:

This feature applies to both OpenLink JDBC Agent types: JODBC Agent and JUDBC Agent
You could also have used the "/DSN" attribute to point to an ODBC or UDBC DSN which has been configured to connect to the Database Server machine, this simply reduces the size of your JDBC URL, but imposes the use of DSNs upon you.

Connecting To Remote Databases On Separate Server Machine Using Database Vendors Networking (Mixed 3-Tier Architecture)

Organizational standards or individual preference may present you with a scenario in which you have two server machines in use, one acting as an Application Server hosting your OpenLink Drivers for JDBC and OpenLink Data Access Server components (Request Broker & Database Agents), and the other acting as a dedicated Database Server. You may not have the necessary authority to install the OpenLink Data Access Server components on the Database Server, or you simply prefer to use your database vendors networking software which is already configured on your Application Server. This scenario can be described as a "Mixed 3-Tier" architecture, this is because you are going to use your OpenLink Database Agents atop database vendor provided networking rather than connecting to an OpenLink Database Agent using OpenLink Database independent networking.

If you were connecting to a remote Oracle database somewhere on your network from our application server called "pluto" using an ODBC DSN called "Customers" you would construct the following JDBC URL assuming a Net8 or SQL*Net "tnsname" or server alias called "ora_pluto":

jdbc:openlink://pluto/SVT=Oracle 8/
UID=test/PWD=test/OPTIONS=ora_pluto

Notes:

The "/OPTIONS" JDBC URL attribute provides the entry or bind point for connecting OpenLink Database agents to Database vendors networking products. This applies to all supported OpenLink databases, see the OpenLink Database Agents configuration guide for additional information relating to the database specific formats of values passed to the "/OPTIONS" JDBC URL attribute
This feature applies to both OpenLink JDBC Agent types: JODBC Agent and JUDBC Agent
You could also have used the "/DSN" attribute to point to an ODBC or UDBC DSN which has been configured to connect to the Database Server machine, this simply reduces the size of your JDBC URL, but imposes the use of DSNs upon you.

OpenLink Demonstration Programs

To assist you further during your utilization or evaluation of OpenLink's Drivers for JDBC a number of demonstration JDBC compliant Applets and Applications are bundled with your OpenLink Driver for JDBC installation, these programs are provided in both binary and source code format for your free use. The sections that follow guide you through the process of using these programs

JDBC Compliant Applet Demos

Three JDBC applet samples are bundled with your OpenLink Driver for JDBC installation, each one of these demonstrating practical use of JDBC applets and highlighting OpenLink specific functionality. Each of these demos reside in the "samples\jdbc\jdk[10 or 11 or 12]" sub-directory below the directory into which you installed your OpenLink software. Each applet is accessible from the OpenLink Admin Assistant (an OpenLink agent that provides HTTP services like any Web Server does). The programs are:

JDBCDemo - demonstrates basic JDBC functionality via an Applet
ScrollDemo - demonstrates JDBC functionality via an Applet. It also demonstrates the additional Resultset navigation functionality provided by OpenLink's Scrollable Resultset & RowSet Extensions for JDBC on a Record by Record Basis.
ScrollDemo2 - demonstrates JDBC functionality via an Applet. It also demonstrates the additional Resultset navigation functionality provided by JDBC 2.0
RowSetDemo - demonstrates JDBC functionality via an Applet. It also demonstrates the additional Resultset navigation functionality provided by OpenLink's Scrollable Resultset & RowSet Extensions for JDBC on a RowSet by RowSet Basis.

JDBCDemo

This applet demonstrates basic JDBC functionality via an Applet.

Utilization Steps:

Start the OpenLink Request Broker (click here for instructions on how to do this under Windows and here on how to do this on Linux or UNIX machines)
Start up your Web Browser
Enter one of the following URLs into your browser depending on the location of your OpenLink Request Broker:
Local To you:
http://localhost:8000

Remote Server:
http://<hostname or IP address of remote server>:8000

Note: Port "8000" presumes that you provide this value when prompted during your OpenLink Sever components installation.
Follow the Admin Assistant's Menu tree to the location of the "Sample Applications->JDBC Applet Demos" menu item. The graphic below depicts this process.
Click on the hyperlink that reads "Applet demonstration with OpenLink Software JDBC Driver"
Use the Applet's File->Set Connection URL menu item set a URL pointing to an ODBC or UDBC DSN. If uncertain follows the instructions laid out in the section covering OpenLink JDBC URL formats which shows you how to construct Type 1, 2, and 3 URL formats for your OpenLink Drivers for JDBC. This applet will run with non OpenLink Drivers for JDBC but you will need to obtain URL construction information from the relevant driver vendor.

The line below depicts the URL construction dialog presented:

jdbc:openlink://localhost/DSN=WebJDBCDemo
Enter a valid SQL statement for the backend database that you are connecting to via JDBC and then click on the "Query" button. The screen shot below depicts this process:
Basic JDBC 1.1 functionality provides Forward-Only as opposed to Bi-Directional record Scrolling, this is why the basic JDBC applet on has a "Next" button. When you click on the "Next" button you are moved to the next record in your JDBC resultset, unfortunately you have to hit the "Query" button again and re-start the Forward-Only resultset navigation if you need to see the First or Prior resultset records from your current position. The examples that follow show how OpenLink and the new release of JDBC (version 2.0) address the Bi-Directional Scrolling Limitation demonstrated by this Applet.

ScrollDemo

This program demonstrates JDBC functionality via an Applet. It also demonstrates the additional Resultset navigation functionality provided by OpenLink's Scrollable Resultset & RowSet Extensions for JDBC on a Record by Record Basis.

Utilization Steps:

Start the OpenLink Request Broker (click here for instructions on how to do this under Windows and here on how to do this on Linux or UNIX machines)
Start up your Web Browser
Enter one of the following URLs into your browser depending on the location of your OpenLink Request Broker:
Local To you:
http://localhost:8000

Remote Server:
http://<hostname or IP address of remote server>:8000

Note: Port "8000" presumes that you provide this value when prompted during your OpenLink Sever components installation.
Follow the Admin Assistant's Menu tree to the location of the "JDBC Applet Demos" menu item. The graphic below depicts this process.
Click on the hyperlink that reads "Applet demonstration with OpenLink Software JDBC Scrollable Cursor extensions"
Use the Applet's File->Set Connection URL menu item set a URL pointing to an ODBC or UDBC DSN. If uncertain follows the instructions laid out in the section covering OpenLink JDBC URL formats which shows you how to construct Type 1, 2, and 3 URL formats for your OpenLink Drivers for JDBC.

The line below depicts the URL construction dialog presented:

jdbc:openlink://localhost/DSN=WebScrollDemo
Enter a valid SQL statement for the backend database that you are connecting to via JDBC and then click on the "Query" button. The screen shot below depicts this process:
JDBC 1.1 functionality provides Forward-Only as opposed to Bi-Directional Resultset Scrolling, OpenLink's Scrollable Resultset Extensions for JDBC enable Bi-Directional Resultset Scrolling. This is why this applet has an additional set of Resultset Navigation buttons: "First","Next", "Prior","Last", "Lock", "Unlock", "Add", "Update", "Get Bookmark", "Set Bookmark", "and Go To" . The existence of Bi-directional Scrollable Resultsets (or Cursors) is often presumed by end-users and developers alike, its importance rarely understood prior to embarking upon JDBC application development or product selection, the unfortunate consequence being complex application re-writes or implementation of sub par JDBC solutions. Each of the button in the applet demo is explained below so as to understand the magnitude of this issue:

First - takes you to first record in the Resultset

Next - takes you to the next record in the Resultset from your current position

Prior - takes you to the previous record in the Resultset from your current position

Last - takes you to the last record in the Resultset

Lock - locks the current record

Unlock - unlocks the current record

Add - add a new record to database

Update - change current record

Delete - remove current record from database

Get Bookmark - mark current record position for future revisit

Set Bookmark - revisit previous marked position in current ResultSet

Go To - go directly to a specific record number within the current ResultSet

Refresh - Reopen current resultset

ScrollDemo2

This applet demonstrates JDBC functionality via an Applet. It also demonstrates the additional Resultset navigation functionality provided by JDBC 2.0

This Applet require a browser that is Java Virtual Machine version 1.2.x or 2.x compliant. If you do not have such a Browser, you can simply run the JDBC Application version of this program.

Utilization Steps:

Start the OpenLink Request Broker (click here for instructions on how to do this under Windows and here on how to do this on Linux or UNIX machines)
Start up your Web Browser
Enter one of the following URLs into your browser depending on the location of your OpenLink Request Broker:
Local To you:
http://localhost:8000/

Remote Server:
http://<hostname or IP address of remote server>:8000

Note: Port "8000" presumes that you provide this value when prompted during your OpenLink Sever components installation.
Follow the Admin Assistant's Menu tree to the location of the "Sample Applications->JDBC Applet Demos" menu item. The graphic below depicts this process.
Click on the hyperlink that reads "Applet demonstration with OpenLink Software JDBC 2.0 Scrollable Cursors"
Use the Applet's File->Set Connection URL menu item set register your Driver for JDBC 2.0 and then enter a URL pointing to an ODBC or UDBC DSN. If uncertain follow the instructions laid out in the section covering OpenLink JDBC URL formats which shows you how to construct Type 1, 2, and 3 URL formats for your OpenLink Drivers for JDBC. This applet will run with non OpenLink Drivers for JDBC but you will need to obtain Driver registration and JDBC URL construction information from the relevant Driver vendor.

The screen shot below depicts the URL construction dialog presented:
Enter a valid SQL statement for the backend database that you are connecting to via JDBC and then click on the "Query" button.
JDBC 1.1 functionality provides Forward-Only as opposed to Bi-Directional Resultset Scrolling, JDBC 2.0 on the other hand supports Bi-Directional Resultset Scrolling. As a result this applet has an additional set of Resultset Navigation buttons: "First","Next", "Previous","Last", "Insert", "Update", "Absolute", "Relative". Unfortunately JDBC 2.0 does not provide Bookmarking or Row Level concurrency control hence the exclusion of the "Lock", "UnLock", "Go To", "Set Bookmark", "Get Bookmark" navigation buttons provided in the "ScrollDemo" applet. To use this functionality in a JDBC 2.0 environment you simply make use of the OpenLink Scrollable ResultSet & RowSet Extensions.

Each navigation button is described below so as to shed more light on the Scrollable ResultSet functionality provided by JDBC 2.0.

First - takes you to first record in the Resultset

Next - takes you to the next record in the Resultset from your current position

Previous - takes you to the previous record in the Resultset from your current position

Last - takes you to the last record in the Resultset

Add - add a new record to database

Update - change current record

Delete - remove current record from database

Relative - moves N number of records forward from the current record where N represents a value entered into the field beside the "Relative" button. IF the field contains a negative number then it indicates a backwards move.

Absolute - go directly to record number N within the current ResultSet where N represents a value entered into the field beside the "Relative" button, the actual direction of Resultset navigation depends on the actual location of the record in question

Refresh - Reopen current resultset

RowSetDemo

This applet demonstrates JDBC functionality via an Applet. It also demonstrates the additional Resultset navigation functionality provided by OpenLink's Scrollable Resultset & RowSet Extensions for JDBC on a RowSet by RowSet Basis.

Utilization Steps:

Start the OpenLink Request Broker (click here for instructions on how to do this under Windows and here on how to do this on Linux or UNIX machines)
Start up your Web Browser
Enter one of the following URLs into your browser depending on the location of your OpenLink Request Broker:
Local To you:
http://localhost:8000

Remote Server:
http://<hostname or IP address of remote server>:8000

Note: Port "8000" presumes that you provide this value when prompted during your OpenLink Sever components installation.
Follow the Admin Assistant's Menu tree to the location of the "Sample Applications->JDBC Applet Demos" menu item. The graphic below depicts this process.
Click on the hyperlink that reads "Applet demonstration with OpenLink Software JDBC Scrollable Cursor RowSet Extensions"
Use the Applet's File->Set Connection URL menu item set a URL pointing to an ODBC or UDBC DSN. If uncertain follows the instructions laid out in the section covering OpenLink JDBC URL formats which shows you how to construct Type 1, 2, and 3 URL formats for your OpenLink Drivers for JDBC. This applet will run with non OpenLink Drivers for JDBC but you will need to obtain URL construction information from the relevant driver vendor.

The screen shot below depicts the URL construction dialog presented:
Enter a valid SQL statement for the backend database that you are connecting to via JDBC and then click on the "Query" button. The screen shot below depicts this process:
JDBC 1.1 functionality provides Forward-Only as opposed to Bi-Directional Resultset Scrolling, JDBC 2.0 provides Scrollable Resultsets but does not provide Bookmarking or Attached RowSets (transient RowSets located in the same process space as the ResultSet). OpenLink's Scrollable Resultset Extensions for JDBC address these issues irrespective of JDBC version. As a result this applet has an additional set of Resultset Navigation buttons when compared to the basic JDBC 2.0 Applet in the prior section, the buttons are: "First","Next", "Prior","Last", "Lock", "Unlock", "Add", "Update", "Get Bookmark", "Set Bookmark", "and Go To" . The existence of transient RowSets due to Bi-directional Scrollable Resultsets (or Cursors) in JDBC 2.0 is more than likely presumed to exist by end-users and developers alike, it is important that you take note of this before embarking upon JDBC 2.0 application development or product selection. Each of the buttons in the Applet demo is explained below so as to assist in the understanding of these matters:

First - takes you to first RowSet in the Resultset

Next - takes you to the next RowSet in the Resultset from your current position

Prior - takes you to the previous RowSet in the Resultset from your current position

Last - takes you to the last RowSet in the Resultset

Lock - locks the current RowSet

Unlock - unlocks the current RowSet

Add - add a new record to database

Update - change current record with the current RowSet of

Delete - remove current record from within the current RowSet from the database

Get Bookmark - mark current RowSet within Resultset for future revisit

Set Bookmark - revisit previous marked RowSet position in current ResultSet

Go To - go directly to a specific record number within the current ResultSet

Refresh - Reopen current resultset

JDBC compliant Application Demos

All the JDBC compliant Applet demos described in the previous sections have also been implemented as JDBC compliant Applications Demos, you can run these programs in a number of ways depending on operating system hosting your Java Virtual Machine.

Windows 95/98/NT/200

Click on your Windows Start Menu Button
Select the "OpenLink Data Access Drivers" Start Menu Group
Locate the "JDBC Samples" Menu Item
Choose from the list of JDBC Applications presented

Linux or UNIX

Move into your OpenLink base installation directory
The move to the following directory listing output maps out the location of the various JDBC Application demos by Java Virtual Machine version:

JDBC/jdk1.0.2/Applications:
JDBCDemo RowSetDemo ScrollDemo

JDBC/jdk1.0.2/Applications/JDBCDemo:
DialogConnection.class JDBCDemo.class
DialogConnection.java JDBCDemo.java

JDBC/jdk1.0.2/Applications/RowSetDemo:
DataTextField.class DialogConnection.java readme.txt
DataTextField.java RowSetDemo.class
DialogConnection.class RowSetDemo.java

JDBC/jdk1.0.2/Applications/ScrollDemo:
DialogConnection.class ScrollDemo.class readme.txt
DialogConnection.java ScrollDemo.java

JDBC/jdk1.1.x/Applications:
JDBCDemo RowSetDemo ScrollDemo

JDBC/jdk1.1.x/Applications/JDBCDemo:
DialogConnection.class JDBCDemo.class
DialogConnection.java JDBCDemo.java

JDBC/jdk1.1.x/Applications/RowSetDemo:
DataTextField.class DialogConnection.java readme.txt
DataTextField.java RowSetDemo.class
DialogConnection.class RowSetDemo.java

JDBC/jdk1.1.x/Applications/ScrollDemo:
DialogConnection.class ScrollDemo.class readme.txt
DialogConnection.java ScrollDemo.java

JDBC/jdk1.2.x/Applications:
JDBCDemo RowSetDemo ScrollDemo ScrollDemo2

JDBC/jdk1.2.x/Applications/JDBCDemo:
DialogConnection.class JDBCDemo.class
DialogConnection.java JDBCDemo.java

JDBC/jdk1.2.x/Applications/RowSetDemo:
DataTextField.class DialogConnection.java readme.txt
DataTextField.java RowSetDemo.class
DialogConnection.class RowSetDemo.java

JDBC/jdk1.2.x/Applications/ScrollDemo:
DialogConnection.class ScrollDemo.class readme.txt
DialogConnection.java ScrollDemo.java

JDBC/jdk1.2.x/Applications/ScrollDemo2:
DialogConnection.class ScrollDemo2.class
DialogConnection.java ScrollDemo2.java
Move into the appropriate directory and then execute the following command:

java <classname>

where "<classname>" represents the JDBC class file hosting your JDBC application demo. For instance if you wanted to run the "RowSetDemo" JDBC application you would type the following:

java RowSetDemo

Important Multi-User JDBC Solution Development & Utilization Issues

Sensitivity To Changes In Underlying Database

It is extremely important to application developers and end-users alike to understand the degree to which the Resultsets presented to them by a JDBC solution are actually sensitive to underlying changes in the source database. JDBC 1.1 not only fails to provide you with Bi-directional Resultset Scrolling, it also presents what is basically a snapshot of the data in your database at the time a JDBC query is executed. This has the effect of increasing Multi-User JDBC solution development complexity or limiting the functionality and usability of JDBC by end-users.

Sensitive to changes in underlying database takes many forms, this includes: Static, KeySet, Dynamic, and Mixed modes of sensitivity.

Static - same as basic JDBC, records scrolling occurs over a database snapshot and is insensitive to underlying change by other users

KeySet - JDBC resultset records scroll over a set of record identifiers uniquely identifying records in the underlying database, this type of scrolling is sensitive to changes is those records with identifiers at the time of query execution. This form of scrolling is insensitive to record record additions or deletions.

Dynamic - JDBC resultset records scroll over a set of record identifiers uniquely identifying records in the underlying database, these unique identifiers are recreated before each RowSet traversal (collection of resultset records used as scrolling marker or sliding window or Cursor), rather than once at query execution time. This type of scrolling is sensitive to all changes in the underlying database but may introduce a performance penalties depending on the size of RowSets and available network bandwidth.

Mixed - JDBC resultset records scroll over a set of record identifiers uniquely identifying records in the underlying database, these unique identifiers are created to a limited size (known as the KeySet Size) at query execution time, only when RowSet traversal goes beyond the existing set of unique row identifiers is another collection of unique identifiers assembled. This type of scrolling is sensitive to all changes in the underlying database, but insensitive to Additions or Deletions affecting records in the current RowSet scrolling across a current KeySet, once KeySet boundaries are crossed Insertions or Deletions are recognized. This mode of sensitivity provides increased performance and the expense of reduced sensitivity.

Concurrency Control

In addition to being sensitive to changes in the underlying database, Multi-User applications need to be able to protect users and application processes from the effects of one another when the same record or collection of records are being manipulated at the same time. The process by which these issue are addressed is known as Concurrency Control.

Concurrency control occurs in one of two ways, Optimistic or Pessimistic control.

Optimistic Concurrency Control - presumes that probability and frequency of multiple users and processes instigating changes to the same database records is low. As result when an end-user or process attempts to change records it first of all determines if the record values at the point of change are still the same as what they were at the time of retrieval. If they are unchanged at the point of change then the change occurs otherwise the change process is rejected and then re-attempted. Although this reduces concurrent user latency, it does have the knock on effect of reducing data integrity if changes rejections aren't managed carefully.

Pessimistic Concurrency Control - presumes that the probability and frequency of multiple user processing and instigating changes to the same records is high. As a result an end-user or process attempts to changes records it first of all secures Exclusive Locks on the records in question, performs the changes, and then releases the locks. Although this increases and preserves data integrity it does introduce concurrent use latency , which is perceived as performance degradation by the end-user or application developer.

OpenLink's Scrollable ResultSet and RowSet extensions for JDBC all the Multi-User JDBC solution issues raised in this section, our bundled and live online demonstrations enable you to evaluate this for yourself and ultimately make a knowledgeable JDBC Driver product and vendor selection.