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.
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:
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.
(Note that you also need to restart the server if the driver has changed.)
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 Server Installation manual.