The WebSphere for
z/OS configuration needs to have WebSphere and POSIX environment variables
set so that the DB2 home directory and the db2sqljjdbc.properties file can
be located. Click on Environment > Manage WebSphere Variables. Select the
node level view and click Apply.
There are two variables of interest.
- DB2390_JDBC_DRIVER_PATH This variable will be present but have
no assigned value. Update this value to the directory in which the DB2 code
resides. For example: /usr/lpp/db2/db2710
- DB2SQLJPROPERTIES This variable will not be present. Add this value
to indicate the location and name of DB2 JDBCSQLJ properties file which you
created for this node. For example: /shared/zWebSphere/V5/misc/p5nc_wscjudy_db2sqljjdbc.properties
Note: These variables are set at the node level and thus are applicable
to all servers in the node residing on this system. They can be set at the
server level instead of or in addition to setting them at the node level.
Note: The
DB2390_JDBC_DRIVER_PATH variable could actually be set at the cell level and
removed from the node level definitions if all nodes in the cell will use
the same DB2 home directory.
Note: The DB2SQLJPROPERTIES should not
be set at the cell level, as it contains the specific DB2 subsystem to which
the JDBC driver will use.
Note: The /shared/zWebSphere/V5/misc/ directory
is a commonly accessible directory for all systems in the sysplex. The name
of the file indicates which cell (for example, p5) and node (for example,
nc) that it is intended to be used. It is certainly possible to use a non-shared
directory that is system specific (for example, /etc/zWebSphere/V5/misc/...)
Note: After
these updates have been made and saved, it is necessary to restart the server
to have the server use the //STEPLIB DD updates from Step 1, if required,
and to have the POSIX runtime environment variables refreshed with the changes
made in this step. This restart can be delayed, but it must be done before
the data source created in the last step can be used.