Preparing the JDBC Environment

In order to use the Adapter for JDBC, you must install the JDBC driver for whichever data source you would like to access, set its CLASSPATH value before server startup, and ensure that the JSCOM3 service is running.

For example, if you want to access a UniData database, you must install a JDBC driver for UniData. You can configure only one generic JDBC adapter per server instance.

Note:
  • If an adapter for a specific data source type is available, you should use that adapter to access that type. The Adapter for JDBC does not support data source types for which a specific adapter already exists. For example, the Adapter for Db2 is available to access Db2 databases, so you should not use the Adapter for JDBC to access Db2.
  • If a specific adapter for a data source type is not currently available, you may use the Adapter for JDBC with a vendor-provided JDBC driver. Note that the adapter conforms to generic JDBC standards. Vendors, on the other hand, may have interpreted or extended those standards for their specific data source requirements. If this introduces an incompatibility, you may experience inconsistent behavior when using the adapter for that vendor's data source type. If this occurs please contact Customer Support Services for assistance. They will work with your enterprise to try and support your data access needs.

Set Up the Environment on Windows and UNIX

    Procedure
  1. Identify the location of the JDBC Driver files by adding them to the environment variable CLASSPATH before server startup.

    For example, to set a UNIX or IBM i location for some JDBC Driver files to /usr/driver_files/mydriver.jar, issue the commands: 

    CLASSPATH=/usr/driver_files/mydriver.jar;$CLASSPATH
export CLASSPATH

    Similarly, on Windows, you would issue the command:

    set CLASSPATH=c:\usr\driver_files\mydriver.jar:%CLASSPATH%

    Note that if you run the server workspace as a Windows service, you must set the CLASSPATH as a system-wide environment variable.

    Similarly, on UNIX, to ensure that the variable is set before server startup, add the CLASSPATH setting in your UNIX profile.

  2. Start (or restart) the server.

    (Note that you also need to restart the server if the driver has changed.)

  3. Verify that the JSCOM3 service is active by issuing the following command in the server workspace 
    edastart -show

    and checking that the special services section displays "JSCOM3 active".

    If the JSCOM3 service is not active, a "fail to start" message will typically also be in the server EDAPRINT log. To resolve the problem, review the JDBC listener requirements in the chapter for your operating system in the ibi™ WebFOCUS® Reporting Server Installation manual.