Preparing the i Access Environment (JDBC)

The Adapter for i Access (SUFFIX=SQLIIA) is available for configuration in ODBC and JDBC modes on Windows. Only JDBC mode is available on UNIX/Linux environments. This chapter describes the preliminary setup that must be done to use the Adapter in JDBC mode, obtaining the applicable jar file, and making it accessible to the WebFOCUS Reporting Server.

Set Up the JDBC Environment on Windows and UNIX

    Procedure
  1. The JDBC IBM i jar file is named jt400.jar. A copy is shipped on every IBM i machine in the /QIBM/ProdData/os400/jt400/lib directory. You can also download the file from the internet, if direct access to copying this file is not available. This file must be transferred in binary mode to the machine where you want to configure the Adapter for i Access. The file may be placed in any readable directory.
  2. Assuming the jt400.jar file was placed in the /usr/driver_file directory, set the CLASSPATH environment variable to include the full path name of the jar file. The step for this may be done in one of several ways, depending on your platform.

    On Windows:

    • As a system-level environment variable, set before server startup.
    • As a variable in the EDACONF bin\edaenv.cfg file.
    • As a file on the class path property of the JSCOM listener.

    On non-Windows:

    • As an export environment variable, set before server startup.
    • As a variable in the EDACONF bin\edaenv.cfg file.
    • As a file on the class path property of the JSCOM listener.
    Note: Using the edaenv.cfg file does not resolve embedded variables, so a line such as the following would be invalid: 
    CLASSPATH=/usr/driver_files/myjt400.jar;$CLASSPATH

    The fully expanded actual value needs to be used.

    For example, on Windows: 

    CLASSPATH=c:\usr\driver_files\jt400.jar;c:\mydirectory\myjar.jar

    For example, on non-Windows: 

    CLASSPATH=/usr/driver_files/jt400.jar:/usr/mydirectory/myjar.jar
export CLASSPATH

  3. If using variables, restart or start the WebFOCUS Reporting Server. If added as a file on the class path property of the JSCOM listener, the JSCOM process is restarted as part of the process.

    The new jar should be noted in the edaprint file.

  4. Open the WebFOCUS Reporting Server browser interface and proceed to the Get Data page to start the configuration step.