You can configure DB2 Web Query to run with z/OS or OS/390 and WebSphere Application Server version 1.2
You must modify the WebSphere Application Server configuration file was.conf to include the class path to the DB2 Web Query jar files, and to include the DB2 Web Query parameters. You must then modify the DB2 Web Query configuration parameters to reflect your current DB2 Web Query installation.
Note: As new versions of DB2 Web Query are released, you must make sure that the jar file for the current version is in the class path.
To modify the Application Server configuration file:
1. In your WebSphere Application Server installation directory, locate and open the file named was.conf.
2. In was.conf, locate the ncf.jvm.classpath parameter.
3. To the end of this parameter, add the class path to the DB2 Web Query jar files, db2webquery.jar and db2wqtv10.jar. This is the location where you installed db2webquery.jar and db2wqtv10.jar on your application server.
Note: You must begin the class path information with the character ":" to separate it from the preceding parameter information. Also, do not insert any spaces or line breaks when you add the class path to the ncf.jvm.classpath parameter.
4. In was.conf, locate the session.enable parameter and set it to session.enable=true.
Session tracking is enabled.
5. In was.conf, locate the session.invalidationtime parameter and set it to session.invalidationtime=1800000, or to the session invalidation time you prefer.
Note: The session.invalidationtime parameter sets the number of milliseconds that a session is allowed to go unused before it is no longer considered valid. You can set this parameter to be longer or shorter than the recommended time of 1800000 milliseconds (30 minutes) if you prefer.
6. In was.conf, define the DB Connection Pool in WebSphere Application Server.
The following are the defaults for the DB connection pool parameters:
IBMConnMgr.Pool=DB2WebQuery
IBMConnMgr.Pool.DB2WebQuery.useServerIdentity=false
IBMConnMgr.Pool.DB2WebQuery.poolType=JDBC
IBMConnMgr.Pool.DB2WebQuery.reapTime=1800
IBMConnMgr.Pool.DB2WebQuery.connectionTimeOut=0
IBMConnMgr.Pool.DB2WebQuery.maxIdleTime=900
IBMConnMgr.Pool.DB2WebQuery.minConnections=2
IBMConnMgr.Pool.DB2WebQuery.maxConnections=2000
IBMConnMgr.Pool.DB2WebQuery.maxAge=-1
7. Scroll to the end of was.conf, and add the following DB2 Web Query information and parameters:
# IBM DB2 Web Query (1.2)
# Copyright (c) 2000 IBM, Inc. All Rights Reserved.
# Copyright (c) 2000 Rocket Software, Inc. All Rights Reserved.
#____________________________________________________________
#_______[ BEGIN IBM DB2 Web Query ]_____________________
servlet.DB2WebQuery.code=com.ibm.db2.WebQueryTool.WebQuery
servlet.DB2WebQuery.initArgs=webRoot=/DB2WebQuery,appRoot=/servlet/ DB2WebQuery, installRoot=,wqUserId=, wqUserPass=, daysSaved=, hostName=, emailHost=, queryTimeout=, queryRowLimit=, dbConnectionPool=
#_______[ END IBM DB2 Web Query ]______________________
Note: When you add the DB2 Web Query parameters, do not use spaces or line breaks. Separate all parameters with a comma. All lines that begin with the character "#" are comments, included for informational purposes only, and can be omitted.
8. In the parameters that you added, locate the line that begins:
"servlets.DB2WebQuery.initArgs="
9. Modify the parameters in this line to reflect your current installation. These parameters and their definitions are listed in the Parameter List.
Note: When you modify parameters, do not include spaces or line breaks. Separate all parameters with a comma.
10. Save was.conf.
11. To enable the changes, run updateproperties on the server, and restart the web and application servers.
The DB2 Web Query servlets are now registered, and configuration is complete.