IBM Data Server DB2 - Manual (Page 155)

Chapter 4. Deploying applications with DB2 141
sqlj.zip and sqlj4.zip:
These file contain classes that are required to prepare SQLJ applications for
execution under the IBM Data Server Driver for JDBC and SQLJ. DB2
includes sqlj.zip in the CLASSPATH during the installation process. This file
is for applications that use JDBC 3.0 and earlier functions. You have to
manually include sqlj4.zip in the CLASSPATH to use JDBC 4.0 and earlier
functions. Do not include both.
On DB2 server products that can perform Connect gateway functionality, IBM
Data Server Driver for JDBC and SQLJ license files are installed and placed
in the sqllib/java directory for the Linux or UNIX systems and the sqllib\java
directory for the Windows systems. The license files are not required for
connections to the DB2 database for Linux, UNIX, and Windows (LUW) using
IBM Data Server Driver for JDBC and SQLJ Version 3.50 or later.
IBM Data Server Driver for JDBC and SQLJ native libraries are also installed
to support Type 2 connectivity. These are placed in the sqllib/lib directory for
Linux and UNIX systems, or the sqllib\bin directory for Windows systems.
Table 4-2 shows the library file names for different platforms.
Table 4-2 Library file names for different platforms
Database server configuration setup
To allow successful application connection to a DB2 database with IBM Data
Server Driver for JDBC and SQLJ, check these settings in the database server:
Remote client connectivity:
In general, the DB2 database should be already configured to allow remote
access.
Follow this procedure to configure the database for remote client access:
a. Check if TCP/IP is already enabled using the following command:
db2set -all
Check if DB2COMM=TCPIP is presented in the output. If it is not already
present, set the environment variable DB2COMM to TCPIP:
db2set DB2COMM=TCPIP
Platform File name
AIX, HP-UX, Linux, and Solaris libdb2jcct2.so
Windows db2jcct2.dll