 |
Return to the article. To verify the DB2 client installation, complete the following tasks:
- Check the DB2 release level.
Start the DB2 command window by selecting Start>Programs>IBM DB2>Command Window. Enter the following command: D:\>db2level
It should generate output similar to the following:
DB21085I Instance "DB2"uses DB2 code release "SQL07021"with level identifier "03020105"
and informational tokens "DB2 v7.1.0.43","n010504" and "WR21254a" |
An internal release level of 7.1.0.43 should be indicated.
Note: All the numbers should either match or be at a higher level than the ones displayed. If not, double check the db2level after installing the fixpaks.
- Close the DB2 command window.
- Configure the DB2 client
After the DB2 client installation, you need to configure the server so that WebSphere is able to use the DB2 client to access a remote DB2 database: Stop unused Windows services
To conserve system memory, you can choose to start only those DB2-related Windows services that are used by most WebSphere applications. The startup type for the service can be set to automatic, manual, or disabled. Table 5, below, lists the services settings as they are after installation, as well as the settings we recommend.
Table 5. DB2 Services settings
| Service name | Startup mode after installation | Startup mode recommended setting | | DB2 JDBC Applet Server | Automatic | Automatic | | DB2 Applet Server Control Center | Manual | Manual | | DB2 Security Server | Automatic | Manual |
To change the startup of one of these DB2 Windows services, use the Windows 2000 Services control panel. Update the JDBC level
IBM WebSphere Application Server V4.0 requires JDBC 2.0, whereas the default installation of IBM DB2 V7.2.1 uses JDBC 1.2. To update the DB2 JDBC level, complete the following steps:
- Stop the DB2 JDBC Applet Server Windows service as follows:
Open a Services window by selecting Start>Settings>Control Panel>Administrative Tools>Services.Then look for the "DB2 JDBC Applet Server" and stop it.
Or use the D:\>net stop "DB2 JDBC Applet Server" command.
- In a command window, change to the D:\SQLLIB\java12 directory where you installed DB2 and enter the following command:
D:\SQLLIB\java12 \ >usejdbc2.bat.
Note: If the output of usejdbc2 indicates that any of the files failed to copy successfully, then the JDBC2 update failed. If this occurs, stop all DB2 services and then repeat the above steps. If you see any "access denied" or "process cannot access..." errors and the JDBC Applet Server is indeed not running, then another (non-DB2) process has locked the db2java.zip file for some reason.
- Start the DB2 JDBC Applet Server Windows service as follows:
Open a Services window by selecting Start>Settings>Control Panel>Administrative Tools>Services. Then look for the "DB2 JDBC Applet Server" and start it. Or use the D:\>net start "DB2 JDBC Applet Server" command.
- Check the contents of the D:\SQLLIB\java12\inuse file. If JDBC 2.0 is being used, the file will contain:
JDBC 2.0
Return to the article. | |
