IBM(R) DB2(R) Web Query Tool for Multiplatforms, Version 1 Release 3 Fix Pack 6 README CONTENTS 1.0 ABOUT THIS README FILE 1.1 Evaluation code 1.2 Corrected known problems 1.3 Enhancements 2.0 PREREQUISITES 2.1 Hardware Requirements 2.2 Software Requirements 3.0 INSTALLATION INSTRUCTIONS 3.1 Configuring IBM WebSphere Application Server Version 6.0 on Multiplatforms to work with IBM DB2 Web Query 3.2 Configuring IBM WebSphere Application Server Version 5.0.2 or 5.1 on Multiplatforms to work with IBM DB2 Web Query 3.3 Configuring IBM WebSphere Application Server Version 5 or Version 6 on z/OS to work with IBM DB2 Web Query 4.0 CUSTOMIZATION INSTRUCTIONS 5.0 RESTRICTIONS 6.0 CORRECTIONS TO DOCUMENTATION 7.0 HOW TO GET HELP 8.0 NOTICES 8.1 Use of evaluation code 8.2 Other Notices 8.3 TRADEMARKS AND SERVICE MARKS 1.0 ABOUT THIS README FILE Welcome to IBM DB2 Web Query, Version 1 Release 3 Fix Pack 6, README file. This README file contains information about installing IBM DB2 Web Query Tool. IBM DB2 Web Query has been tested and validated with all supported releases of DB2 Universal Database(TM) through Version 8.1.8 and DB2 for z/OS at PUT0506. Subsequent releases might require additional maintenance. DB2 Web Query Tool supports the following languages on the Windows and Unix operating systems: English, Czech, Japanese, Russian, Simplified Chinese, and Traditional Chinese. 1.1 Evaluation code If you are using evaluation program, the evaluation program enables you to try this product for a period of 60 days. After 60-days, you must purchase a license to continue to use the product. When you purchase the product, the license is enforced based upon the platform to which you are connecting IBM DB2 Web Query. Read NOTICES Section 6.1, Use of Evaluation Program, and the License Agreement provided with your evaluation copy of the program. 1.2 CORRECTED KNOWN PROBLEMS - PK01817 - DB2 Web Query Tool is not clearing connections when quitting - PK01094 - Non-US English user interface is garbled for Help system 1.3 ENHANCEMENTS - PK04029 - Add support for WebSphere V 6 - added support for WebSphere V 5.1 2.0 PREREQUISITES 2.1 Hardware requirements Hardware requirements are those needed to run the software that is described in 2.2 Software Requirements. DB2 Web Query has the following hardware requirements: - Approximately 64 MB of free disk space on any supported platform - Additional space for user data - A minimum of 64 MB memory - Memory to fulfill WebSphere and DB2 minimum requirements 2.2 Software requirements In order to work with IBM DB2 Web Query Tool, you need to have a Web server, a Web Application server (such as IBM WebSphere Application Server), JDBC and DB2 installed on your system. You also need to be able to connect to a DB2 database. When you are using DB2 Web Query Tool, you are working in a browser. Information that you send to DB2 Web Query Tool first goes through your Web Server. Your Web Server passes the information to your Web Application Server (IBM WebSphere Application Server). Your Web Application Server passes the information to DB2 through JDBC. The following table indicates the operating systems, DB2 Web Query Tool products, and the WebSphere products that you can choose for your business. Operating systems, DB2 Web Query Tool products, and the WebSphere products that are supported by DB2 Web Query v 1.3: Operating System | IBM DB2 Web Query | IBM WebSphere Product | Tool Product | =================================================================================== UNIX and Linux |IBM DB2 Web Query Tool |IBM WebSphere Application Server |Tool for Multiplatforms |V5.0.2, 5.1, and 6.0 ----------------------------------------------------------------------------------- Windows 2000 |IBM DB2 Web Query Tool |IBM WebSphere Application Server Windows XP |for Multiplatforms |V5.0.2, 5.1, and 6.0 ----------------------------------------------------------------------------------- z/OS, OS/390 |IBM DB2 Web Query |IBM WebSphere Application Server Operating System, |Tool for z/OS |V5 service level W502009 release Version 2 Release | |03 or higher IBM WebSphere Application 5 or higher with | |Server V 5.1, and IBM WebSphere UNIX System Services| |Application Server V 6.0 installed on MVS | | ----------------------------------------------------------------------------------- It is recommended that you keep up-to-date as updates to WebSphere V5.0, 5.1, or 6.0 become available. DB2 Web Query tool does not support any WebSphere Express Editions. When using WebSphere Application Server, the WebSphere sample applications must be installed. For information on installing the sample applications, see the WebSphere Application Server documentation. Database: IBM DB2 Web Query has been tested and validated with IBM DB2 Version 7.1 and above and V 8.1 Fix Pack 8 and above with a JDBC Type-2 Driver, with the applicable updates to enable JDBC. DB2 Web Query will also work with Informix Dynamic Server 9.3. Note: JDBC Drivers other than those for DB2 can be used to view but not edit database data. Web Browser: To use DB2 Web Query, you must use a Web Browser that supports Java 1.1.x and has cookies and Java script enabled. Microsoft Internet Explorer version 5.5, with Fix Pack 2 is installed and higher is supported. Netscape Version 6.2 and higher is supported. Tip: Ensure that the current fix levels are applied for the JDBC driver, JDK, HTTPD, and IBM WebSphere. 3.0 INSTALLATION INSTRUCTIONS Install the selected updates using either PKZIP for zip file format or GUNZIP for tar file format. 3.1 Configuring IBM WebSphere Application Server Version 6.0 on Multiplatforms to work with IBM DB2 Web Query 1. Start the WebSphere Application Server V 6.0 2. Open the WebSphere Application Server Administrative Console 3. Set the DB2 Web Query Install Root within the Administrative Console: a. Under Servers -> Application servers -> ServerName expand Java and Process Management. Where ServerName is the name of your server. b. Select Process Definition. c. From the Additional Properties box, select Java Virtual Machine d. In the Generic JVM arguments field, type: -Dcom.ibm.db2.cwq.installRoot=C:\IBM\CWQ1.3.6 -Dclient.encoding.override=UTF-8 Where C:\IBM\CWQ1.3.6 is the installRoot directory. These lines should be typed on one line separated by spaces with no carriage returns. Note: The variables, such as installRoot, in this section are case sensitive. e. Set the maximum heap size to 256. f. Click Apply. g. Click OK then save the configuration. 4. Create a JDBC Provider within the Administrative Console: a. Select: Resources -> JDBC Providers -> Sample DB Driver and from the Additional Properties box, select Data Sources (Version 4). Information : If the Sample DB driver has not already been created, you can create it as follows: i. From the JDBC Providers screen, press the New button. ii. Select DB2 as the database type. iii. Select DB2 Legacy CLI-based Type 2 JDBC Driver. iv. Select Connection pool data source as the implementation type. v. Click Next. vi. Click Apply. b. Click Data sources (version 4). c. Click New. The Configuration tab opens. d. Fill in the fields on the Configuration tab: i. In the Name field, type: cwqManagerDB ii. In the JNDI Name field, type: jdbc/cwqManagerDB iii. In the Database field, specify a database. iv. In the Userid field, type a userID to be used to connect to the specified database. v. In the Password field, type a password to be used to connect to the specified database. vi. Click Apply. vii. Click OK then save the configuration. d. Using your preferred query tool, connect to the cwqManagerDB database that you specified in step 5c (using the userID and Password that you specified in step 5c) and run the following create statement: CREATE TABLE WQ.MANAGER (CWQNAME VARCHAR(40) NOT NULL, PRIMARY KEY(CWQNAME)) 5. Provide the values for all the "WebSphere Variables" being used by the JDBC provider that you use. For example: in the case of "DB2 JDBC Provider" a value for the WebSphere Variable $DB2_JDBC_DRIVER_PATH must be provided. In this case the value is the location of db2java.zip. By default the location of db2java.zip is: C:\Program Files\IBM\SQLLIB\java To specify this value, save the selected JDBC provider to the master configuration and navigate on the WebSphere admin console to: Environment -> WebSphere Variables and click DB2_JDBC_DRIVER_PATH and type the location of the db2java.zip in the Value field. Click OK. 6. Create a "DB2 JDBC" shared library within the Administrative Console: a. In the Administrative console go to: Environment -> Shared Libraries b. Click New. The Configuration tab opens. c. On the Configuration tab, type: "DB2 JDBC" in the Name field. d. On the Configuration tab, type: the classpath of the JDBC driver in the Classpath field. For example, a typical path on Windows is: C:\Program Files\IBM\SQLLIB\java\db2java.zip e. Click Apply. f. Click OK then save the configuration. Information: To work with an Informix database, create a similar entry for the Informix JDBC driver. 7. Use WebSphere Application Server V6.0, install the DB2 Web Query application from the cwq-1.3.6.ear file. a. Select Applications --> Install New application. b. Select the Local Path radio button. c. In the Local Path type the fully defined file name where the DB2 Web Query .ear file is stored on your local machine, or use the browse button to navigate to it. d. Click Continue. The Generate Default Bindings box opens. e. Click Next. Click Continue until the Provide options to perform the installation page opens. f. Click the Map Resource references to resources link. g. On the Map Resource references to resources page, select: jdbc/cwqManagerDB Check to select the module: cwqManagerEJB Click Apply, then click Next. h. In the Application Installation wizard, go to the Summary page and click Finish. The Application Installation wizard closes and the following message is displayed: Application cwqEA installed successfully. i. Click the Save to Master Configuration link to save the configuration and click the Save button on the page that opens. j. In the WebSphere Administrative console, select: Applications -> Enterprise Applications -> cwqEA. The Application Properties panel opens. k. From the Additional Properties box, select Libraries from the Additional Properties box. Check to make sure the DB2 JDBC entry that you created in step 6 is listed. If it is not listed, add it by clicking the Add button and selecting the DB2 JDBC Library Name on the Configuration screen that follows. l. Click Apply. m. Click OK then save the configuration. n. Select the cwqEA application and change the WAR Classloader Policy from Module to Application. Save your changes. o. Start the Enterprise Application cwqEA. To start the Enterprise application, Navigate to Applications -- > Enterprise Applications and select the Enterprise Application cwqEA then click Start. p. Stop WebSphere Application Server and re-start it. 8. Open the DB2 Web Query Configuration Utility by accessing the following URL: http://server:port/DB2Tools/WebQuery/Configure Where server is the name of your Web server and port is the WebSphere Application server port. Information: The default WebSphere Application Server port is 9080. The initial user id is: cwq. The initial password is: cwq 9. In the DB2 Web Query Configuration Utility, specify the DB2 Web Query initial parameters. For more information on initial parameters, see “Parameter list” in the DB2 Web Query User’s Guide. Requirement: Ensure that the user ID that you specify for the wqUserId parameter has select authority on the following tables at each location to which DB2 Web Query connects: SYSIBM.SYSTABLES SYSIBM.SYSTABAUTH SYSIBM.SYSADMAUTH SYSIBM.SYSDBAUTH WQ.STORE_TABLE WQ.INDEX_TABLE WQ.SMTP 10. Click Update. Click Login to login to DB2 Web Query and complete the configuration necessary to work with DB2 Web Query. For more information on configuring DB2 Web Query, see Creating the DB2 Web Query Tool Catalog in the DB2 Web Query user's guide. 3.2 Configuring IBM WebSphere Application Server Version 5.0.2 or 5.1 on Multiplatforms to work with IBM DB2 Web Query 1. Start the WebSphere Application Server V 5.0.2 or 5.1 2. Open the WebSphere Application Server Administrative Console 3. Set the DB2 Web Query Install Root within the Administrative Console: a. Select: Servers -> Application Servers -> serverName Where serverName is the name of the name of your server. b. From the Additional Properties box, select Process Definition c. From the Additional Properties box, select Java Virtual Machine d. In the Generic JVM arguments field, type: -Dcom.ibm.db2.cwq.installRoot=C:\IBM\CWQ1.3.6 -Dclient.encoding.override=UTF-8 Where C:\IBM\CWQ1.3.6 is the installRoot directory. These lines should be typed on one line separated by spaces with no carriage returns. Note: The variables, such as installRoot, in this section are case sensitive. e. Set the maximum heap size to 256. f. Click Apply. g. Click OK then save the configuration. 4. Create a JDBC Provider within the Administrative Console: a. Select: Resources -> JDBC Providers -> Sample DB Driver and from the Additional Properties box, select Data Sources (Version 4). Information : If the Sample DB driver has not already been created, you can create it as follows: i. From the JDBC Providers screen, press the New button. ii. Select DB2 JDBC Provider and click OK. iii. Optional Change the name field to: Sample DB Driver iv. Click Apply. v. Click OK then save the configuration. b. Click New. The Configuration tab opens. c. Fill in the fields on the Configuration tab: i. In the Name field, type: cwqManagerDB ii. In the JNDI Name field, type: jdbc/cwqManagerDB iii. In the Database field, specify a database. iv. In the Userid field, type a userID to be used to connect to the specified database. v. In the Password field, type a password to be used to connect to the specified database. vi. Click Apply. vii. Click OK then save the configuration. viii. Optional: Test the connection to Data Source (Version 4). Select: Resources -> JDBC Providers -> Sample DB Driver and from the Additional Properties box select: Data Sources (Version 4). Then select the cwqManagerDB data source and click the Test Connection button. d. Using your preferred query tool, connect to the cwqManagerDB database that you specified in step 5c (using the userID and Password that you specified in step 5c) and run the following create statement: CREATE TABLE WQ.MANAGER (CWQNAME VARCHAR(40) NOT NULL, PRIMARY KEY(CWQNAME)) 5. Provide the values for all the "WebSphere Variables" being used by the JDBC provider that you use. For example: in the case of "DB2 JDBC Provider" a value for the WebSphere Variable $DB2_JDBC_DRIVER_PATH must be provided. In this case the value is the location of db2java.zip. By default the location of db2java.zip is: C:\Program Files\IBM\SQLLIB\java To specify this value, save the selected JDBC provider to the master configuration and navigate on the WebSphere admin console to: Environment -> Manage WebSphere Variables and click DB2_JDBC_DRIVER_PATH and type the location of the db2java.zip in the Value field. 6. Create a "DB2 JDBC" shared library within the Administrative Console: a. In the Administrative console go to: Environment -> Shared Libraries b. Click New. The Configuration tab opens. c. On the Configuration tab, type: "DB2 JDBC" in the Name field. d. On the Configuration tab, type: the classpath of the JDBC driver in the Classpath field. For example, a typical path on Windows is: C:\Program Files\IBM\SQLLIB\java\db2java.zip e. Click Apply. f. Click OK then save the configuration. Information: To work with an Informix database, create a similar entry for the Informix JDBC driver. 7. Use WebSphere Application Server V5.0.2, install the DB2 Web Query application from the cwq-1.3.6.ear file. a. Select Applications --> Install New application. b. Select the Local Path radio button. c. In the Local Path type the fully defined file name where the DB2 Web Query .ear file is stored on your local machine, or use the browse button to navigate to it. d. Click Next. The Generate Default Bindings box opens. e. Click Next. The Provide options to perform the installation page opens. f. Click the Map Resource references to resources link. g. On the Map Resource references to resources page, select: jdbc/cwqManagerDB Check to select the module: cwqManagerEJB Click Apply. h. In the Application Installation wizard, go to the Summary page and click Finish. The Application Installation wizard closes and the following message is displayed: Application cwqEA installed successfully. i. Click the Save to Master Configuration link to save the configuration and click the Save button on the page that opens. j. In the WebSphere Administrative console, select: Applications -> Enterprise Applications -> cwqEA. The Application Properties panel opens. k. From the Additional Properties box, select Libraries from the Additional Properties box. Check to make sure the DB2 JDBC entry that you created in step 6 is listed. If it is not listed, add it by clicking the Add button and selecting the DB2 JDBC Library Name on the Configuration screen that follows. l. Click Apply. m. Click OK then save the configuration. n. Select the cwqEA application and change the WAR Classloader Policy from Module to Application. Save your changes. o. Stop then restart the application server: serverName. p. Start the Enterprise Application cwqEA. To start the Enterprise application, Navigate to Applications -- > Enterprise Applications and select the Enterprise Application cwqEA then click Start. 8. Open the DB2 Web Query Configuration Utility by accessing the following URL: http://server:port/DB2Tools/WebQuery/Configure Where server is the name of your Web server and port is the WebSphere Application server port. Information: The default WebSphere Application Server port is 9080. The initial user id is: cwq. The initial password is: cwq 9. In the DB2 Web Query Configuration Utility, specify the DB2 Web Query initial parameters. For more information on initial parameters, see “Parameter list” in the DB2 Web Query User’s Guide. Requirement: Ensure that the user ID that you specify for the wqUserId parameter has select authority on the following tables at each location to which DB2 Web Query connects: SYSIBM.SYSTABLES SYSIBM.SYSTABAUTH SYSIBM.SYSADMAUTH SYSIBM.SYSDBAUTH WQ.STORE_TABLE WQ.INDEX_TABLE WQ.SMTP 10. Click Update. The Configuration Utility closes. You can now login to DB2 Web Query and complete the configuration necessary to work with DB2 Web Query. For more information on configuring DB2 Web Query, see Creating the DB2 Web Query Tool Catalog in the DB2 Web Query user's guide. 3.3 Configuring IBM WebSphere Application Server Version 5 or Version 6 on z/OS to work with IBM DB2 Web Query When working on Z/OS with USS, the directory where DB2 Web Query is installed and its subdirectories must be owned by and writable by the ID that is running WebSphere. These steps should be done as soon as the Web Query tool is un-tarred. If you go back after you have started Web Query and change the ownership of these files, it may be necessary to stop and re-start WebSphere, in order for WebSphere to have the change. 1. Ensure that all setup has hold actions are performed before the DB2 Web Query install is attempted. 2. When working on Z/OS with USS, ensure that the directory where DB2 Web Query is installed and its subdirectories are owned by, and writable by the ID that is running WebSphere. This must be done before the Web Query application is installed into WebSphere. 3. Start the WebSphere Application Server. 4. Open the WebSphere Application Server Administrative Console. 5. Configure your application servers. a. Expand the Servers item in the left pane. b. Under the Servers item, click the Application Servers link. The Application Servers screen is displayed in the right pane. c. On the Application Servers screen, click the serverName link. Where serverName is the name of your server. d. When working wth WebSphere Applicaton Server V 5: In the Additional Properties table on the Configuration screen, click the Process Definition link. The process definition screen is displayed. When working with WebSpere Application Server V6: Under Server Infrastructure section, expand the Java and Process Management tree by clicking the plus sign. Click Process Definition. The process definition screen is displayed. e. On the Process Definition screen, click the Servant link. f. In the Additional Properties table on the Configuration screen, click the Java Virtual Machine link. The Java Virtual Machine screen displays. g. In the Additional Properties table on the Configuration screen, click the Custom Properties link. The Custom Properties screen displays. h. Click New to create the following entries in the Custom Properties table: * First entry: - Name: com.ibm.db2.cwq.installRoot - Value: installRoot directory (the path to the location where DB2 Web Query is installed. - Description: CWQ Install Directory * Second entry: - Name: client.encoding.override - Value: UTF-8 - Description: CWQ Encoding override 6. Configure JDBC providers. Install the DB2 Universal JDBC Driver Provider as the JDBC Provider within the Administrative Console: a. Select: Resources -> JDBC Providers the JDBC Providers page opens. b. Click the link corresponding to the DB2 Universal JDBC Driver Provider in the table on the JDBC Providers screen. The configure tab of the DB2 Universal JDBC Provider page opens. Information: If a DB2 Universal JDBC Driver Provider has not already been created, you can create it as follows: i. Press the New button. ii. Select DB2 Universal JDBC Driver Provider and click OK. c. Ensure that the following files are in the classpath for the JDBC provider: db2jcc.jar db2jcc_javax.jar db2jcc_license_cu.jar db2jcc_license_cisuz.jar sqlj.zip d. Ensure that the native lib path contains the db2 jcc jdbc driver lib directory. The default for this directory is: .../usr/lpp/db2/db2810/jcc/lib .../usr/lpp/db2/db2810/lib 7. Create the cwqManagerDB. a. In the Additional Properties table, click DataSources (Version 4). b. Click New. The Configuration tab opens. c. Fill in the fields on the Configuration tab: i. In the Name field, type: cwqManagerDB ii. In the JNDI Name field, type: jdbc/cwqManagerDB iii. In the Database field, specify a location or database alias. iv. In the Userid field, type a userID to be used to connect to the specified location or database alias. v. In the Password field, type a password to be used to connect to the specified location and database alias. d. In the Additional Properties table, click Custom Properties and define all of the required custom properties for the data source including: * driverType: The JDBC connectivity-type of a data source. If you want to use type 4 driver, set the value to 4. If you want to use type 2 driver, set the value to 2. On the WebSphere z/OS, driver, Type 2 uses RRS and supports 2-phase commit processing. * serverName: The TCP/IP address or host name for the DRDA server. * portNumber: The TCP/IP port number where the DRDA server resides. 8. Configure a JDBC (Version 4) data source for each database to which you want to connect using DB2 Web Query. You can name your data sources any name that fits with your organization. The recommended JNDI naming convention is: jdbc/ where is the location name of the database. Requirement: Data sources that are used to connect to a database must have the auto connection cleanup option disabled. This option is set on the Connection pool tab. To create a data source you must: a. Define all of the required custom properties for the data source including: * driverType: The JDBC connectivity-type of a data source. If you want to use type 4 driver, set the value to 4. If you want to use type 2 driver, set the value to 2. On the WebSphere z/OS, driver, Type 2 uses RRS and supports 2-phase commit processing. * serverName: The TCP/IP address or host name for the DRDA server. * portNumber: The TCP/IP port number where the DRDA server resides. b. Test each data source after configuration to ensure that it functions properly. If the connection test is not successful, consult the WebSphere documentation on instructions, hold actions, and paths to jar and native lib files. 9. Configure the DB2 Web Query EJB database. Using your preferred query tool, connect to the cwqManagerDB location or database alias that you specified in step 5c (using the userID and Password that you specified in step 5c) and run the following create statement: CREATE TABLE WQ.MANAGER (CWQNAME VARCHAR(40) NOT NULL, PRIMARY KEY(CWQNAME)) If the cwqManagerDB is a on z/OS or OS/390 system you must also run the following to make the table usable: CREATE UNIQUE INDEX wq.manageridx ON wq.manager(cwqname asc) 10. Deploy DB2 Web Query a. From the left pane, expand the Applications item. b. Click the Install New Application link. The Preparing for the application installation page opens. c. From the left pane, under the Applications item, click Install new application. Specify the path to the .ear file that you want to install under Server Path. Select cwq-1.3_FP6_390.ear. The Provide options to perform the installation page is displayed. d. On the Provide options to perform the installation page: * Check the Distribute Application check box. * Check the Create MBeans for Resources check box. * In the Application Name field, type cwqEA. e. Click the Next until the Map resource references to resources page opens. f. On the the Map resource references to resources page: i. Select jdbc/cwqManagerDB from the drop down box ii. Check the module cwqManagerEJBcheckbox. iii. Click Apply. iv. Click Next. jbdc/cwqManagerDB appears in the JNDI Name column. g. Click the Summary link. The Summary of Install Options page opens. h. On the Summary of Install Options page, click Finish to deploy DB2 Web Query. 11. Select Application -> Enterprise Applications in the left pane and ensure that cwqEA appears listed as an application. 12. Save the configuration by clicking Save on the menu bar at the top of the screen. 13. Select the cwqEA application and change the WAR Classloader Policy from Module to Application. 14. Save the configuration by clicking Save on the menu bar at the top of the screen. 15. Stop then restart the application server. 16. Ensure that the cwqEA application has been started by selecting Enterprise Applications and then checking the box next to cwqEA. If the start button is available, then the application is not started. You can start it by clicking Start. 17. Open the DB2 Web Query Configuration Utility by accessing the following URL: http://server:port/DB2Tools/WebQuery/Configure Where server is the name of your Web server and port is the WebSphere Application Server port. Information: The default WebSphere Application Server port is 9080. The initial user id is: cwq. The initial password is: cwq 18. In the DB2 Web Query Configuration Utility, specify the DB2 Web Query initial parameters. For more information on initial parameters, see “Parameter list” In the DB2 Web Query User’s guide. Requirement: Ensure that the user ID that you specify for the wqUserId parameter has select authority on the following tables at each location to which DB2 Web Query connects: SYSIBM.SYSTABLES SYSIBM.SYSTABAUTH SYSIBM.SYSADMAUTH SYSIBM.SYSDBAUTH WQ.STORE_TABLE WQ.INDEX_TABLE WQ.SMTP a. Ensure that the entry for managerDatasource is set to jdbc/cwqManagerDB b. Ensure that dbDriver# statements are created for each data source that you created in step 6 to which DB2 Web Query will connect. c. Ensure that the connection pool field is set to the JNDI name of the data source as defined in step 6. 19. Click Update. The Configuration Utility closes. You can now login to DB2 Web Query. 4.0 CUSTOMIZATION INSTRUCTIONS For complete instructions on how to customize and use DB2 Web Query, refer to DB2 Web Query Tool for Multiplatforms User's Guide. If you received your copy of DB2 Web Query electronically, locate the User's Guide here: http://www.ibm.com/software/data/db2imstools/library.html If you are installing this image from a CD-ROM, the documentation is located in /doc directory. The User's Guide on the Web can contain updates to the publication on CD-ROM. Modification level is equivalent to Fix Pack level, e.g. DB2 Web Query Tool Version 1 Release 3 Modification 6 is equivalent to DB2 Web Query Tool Version 1 Release 3 Fix Pack 6. Please check this Web page periodically for newer fix packs: http://www.ibm.com/software/data/db2imstools/support/fixpaks.html 5.0 RESTRICTIONS The following are the current restrictions to DB2 Web Query: - IBM DB2 Web Query does not support Java 2 security. - DB2, when running on some platforms, supports long owner names for tables, however, DB2 Web Query Tool restricts the length of the owner name for queries, result sets, XSL transforms, and charts to 8 characters when saving them as DB2 Web Query tool objects. - Support for 64 bit IBM DB2 UDB servers: IBM DB2 UDB 64 bit databases are supported only through 32 bit DB2 clients which are available for download from the IBM DB2 Support Web site. For more details on the supported client versions for various DB2 UDB server configurations refer to the "Supported and non-supported client and server configuration scenarios for DB2 Universal Database Versions 7 and 8" section of the "DB2 Client Server Compatibility and Migration Considerations" document from IBM DB2. - When using the DB2 UDB V7 client, inconsistent results may occur when connecting to DB2 UDB V8 server. To connect to DB2 UDB V8 you must upgrade your DB2 UDB client to DB2 UDB V8. - When using a DB2 UDB V7 (on Linux, Unix, or Windows) Client for the WebSphere Application Server to connect to a DB2 V8 for z/OS server the following DB2 Web Query features may not function: - Right clicking table from the navigation tree and selecting Query may result in an SQL statement with long column names (greater than 18 characters) truncated to 18 characters. You will need to key in the complete names or upgrade to a DB2 UDB V8 (for Linux, Unix, or Windows) client. - SQL statements of greater than 32 Kb of text may result in a "[IBM][CLI Driver][DB2] SQL0101N The statement is too long or too complex. SQLSTATE=54001" In order to use SQL statements longer than 32 Kb, you must upgrade to a DB2 UDB V8 (for Linux, Unix, or Windows) client. - When using the CREATE LIKE function with a V7 client connecting to a V8 z/OS server an "invalid string or buffer length" error can occur when using longnames. - When using the DB2 Table Editor functionality through DB2 Web Query, if you are using Microsoft Internet Explorer Version 6, you must have the Java 2 SDK V 1.4.1 or higher installed. - When using the DB2 Table Editor functionality through DB2 Web Query, if you are working with DB2 sample tables that contain primary keys, you need to upgrade to DB2 Table Editor 4.3 Fix Pack 3 or higher. - DB2 Web Query Tool must not be installed in a folder with double byte characters in the name. - SOAP functionality is not supported on non-J2EE compliant servers. - In some cases an Error 500 is produced when the HTTP session has expired. In this event, your connection(s) to the databases have been closed. To restart your session the main Web Query URL must be entered again. - DB2 Synonyms appear as Alias objects when connecting to DB2 Universal Database on Multiplatforms. - Web Services are restricted when running on z/OS using WebSphere 3.5 - When working with DB2 Table Editor V 4.3 Fix Pack 6 or higher, the following line must be added to cwq.conf: db2TableEditorClass=com.rocketsoftware.juser.DB2FormsApplet.class Once this line has been added, you must stop and re-start WebSphere in order for the change to take effect. 6 .0 CORRECTIONS TO DOCUMENTATION To obtain the latest refresh of DB2 Web Query Tool publications refer to: http://www.ibm.com/software/data/db2imstools/library.html - In the DB2 Web Query User's Guide, Table 3 in Chapter two should read as follows: Table 3. IBM DB2 Web Query Tool Distribution files +-----------------------+----------------------+--------------------------------+ | Platform on which DB2 | Platform on which | Archive | | Resides | you are installing | | | | DB2 Web Query | | +-----------------------+----------------------+--------------------------------+ | Windows or UNIX | Windows |cwq-1.3_FP6-mp-win.zip | +-----------------------+----------------------+--------------------------------+ | Windows or UNIX | z/OS |cwq-1.3_FP6-mp-zos.tar | +-----------------------+----------------------+--------------------------------+ | Windows or UNIX | UNIX |cwq-1.3_FP6-mp-unix.tar | +-----------------------+----------------------+--------------------------------+ | z/OS | Windows |cwq-1.3_FP6-zos-win.zip | +-----------------------+----------------------+--------------------------------+ | z/OS | z/OS |cwq-1.3_FP6-zos-zos.tar | +-----------------------+----------------------+--------------------------------+ | z/OS | UNIX |cwq-1.3_FP6-zos-unix.tar | +-----------------------+----------------------+--------------------------------+ - In the DB2 Web Query User's Guide, the Setting up DB2 Web Query Tool for e-mail access section should include the following: Tips on configuring your e-mail infrastructure to work with DB2 Web Query's e-mail functionality Most companies have strict controls on delivery of email. This makes it likely that, in order for the email feature of DB2 Web Query to work, site modifications will need to made by the local mail administrator in order to redirect mail to the hosts that are running DB2 Web Query. The domain name space address defaults to hostx.domain.com. SMTP relays see this as a distinct domain, and will attempt to search the domain name space for a mail pointer record. Because it is highly impractical to set up zone records for every host, the local mail relays must have explicit rules defined at the MTA level that map these domains to an IP address. The method of doing so will vary from mail system to mail system. For example, a site that uses Microsoft Exchange server might define a routing group in Microsoft Exchange that points to the DB2 Web Query host. Also, the mail relay contains pointer records that map the domain name to an IP address. This implies that the host running Web Query, must have a static IP address. In order for the software to send mail it must have access to an SMTP relay. 7.0 HOW TO GET HELP For a complete and up-to-date source of DB2 Web Query Tool information, including information on issues discovered after this readme was published, go to the following website: DB2 Web Query Tool Online Support: http://www.ibm.com/software/data/db2imstools/support.html If you are not able to find your answer searching the listed URL, call 1-800-IBM-SERV to speak to an IBM representative for assistance. 8.0 NOTICES This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10594-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this publication to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is as your own risk. Licensees of this program who want to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation J74/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM Internationa This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10594-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any ther country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this publication to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is as your own risk. Licensees of this program who want to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation J74/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the a pplication programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. 8.1 Use of evaluation code If you are using an evaluation copy of the program, the following terms apply: This program contains a disabling device that will prevent it from being used upon expiration of this license. You will not tamper with this disabling device or program. You should take precautions to avoid any loss of data that might result when the program can no longer be used. See the License Agreement for a complete explanation of the terms that apply. 8.2 Other Notices Xerces and Xalon Licenses: Apache Xerces The Apache Software License, Version 1.1 Copyright (c) 1999-2000 The Apache Software Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear. 4. The names "Xerces" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org. 5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation. THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ==================================================================== This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, International Business Machines, Inc., http://www.ibm.com. For more information on the Apache Software Foundation, please see . Apache Xalan The Apache Software License, Version 1.1 Copyright (c) 1999 The Apache Software Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear. 4. The names "Xalan" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org. 5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation. THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. ==================================================================== This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation and was originally based on software copyright (c) 1999, Lotus Development Corporation., http://www.lotus.com. For more information on the Apache Software Foundation, please see . 8.3 Trademarks and service marks. The following terms are trademarks or service marks of the IBM Corporation in the United States or other countries or both: DB2 IBM z/OS zSeries Informix Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. In the United States or other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others. (C) Copyright Rocket Software, Inc., 2001.2005. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.