IBM(R) DB2(R) Web Query Tool for Multiplatforms, Version 1 Release 3 Fix Pack 5 IBM DB2 Web Query Tool for Workgroups, Version 1 Release 3 Fix Pack 5 README CONTENTS 1.0 ABOUT THIS README FILE 1.1 Evaluation Program 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 5.0.2 on Multiplatforms to work with IBM DB2 Web Query 3.2 Configuring IBM WebSphere Application Server Version 5 on z/OS to work with IBM DB2 Web Query 3.3 To install DB2 Web Query Tool version 1.3 Fix Pack 5 when working with WebSphere Application Server Version 4.0.3 on Multiplatforms and iSeries 3.4 To install DB2 Web Query Tool version 1.3 Fix Pack 5 when working with WebSphere Application Server Version 4.0.3 on z/OS 3.5 To upgrade to DB2 Web Query Tool version 1.3 Fix Pack 5 when working with WebSphere Application Server Version 3.5.6 4.0 CONFIGURATION INSTRUCTIONS 5.0 RESTRICTIONS 6.0 CORRECTIONS TO DOCUMENTATION 7.0 HOW TO GET HELP 8.0 NOTICES 8.1 Use of Evaluation Program 8.2 Notices of other companies 8.3 TRADEMARKS AND SERVICE MARKS ________________________________________________________________________________ 1.0 ABOUT THIS README FILE Welcome to IBM DB2 Web Query, Version 1 Release 3 Fix Pack 5, 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.3.132 and DB2 for Z/OS at PDO0410. 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. In this README file, the following naming convention applies: IBM DB2 Web Query Tool for Multiplatforms and IBM DB2 Web Query Tool for Workgroups are abbreviated to DB2 Web Query. 1.1 Evaluation Program 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 - APAR PQ83340 - Timestamp display error. Timestamps ending in zeros are now formatted properly - APAR PQ81799 - Corrected permissions functionality for catalog objects. - APAR PQ79570 - When accessing data that is not stored in DB2 for /OS or OS 390, the SQL0204N "SYSIBM.SYSSYNONYMS" is an undefined name. SQLSTATE=42704 error is no longer experienced. - APAR PQ80056- the Troubleshooting section of the User's Guide has been updated to indicate how to work with DBCS characters in DB2 Web query. - Duplicate Connections are no longer allowed. - Charts can now be resized in DB2 Web Query. - Colors can now be assigned properly to charts on Chart options screen. - Temporary result sets can now be compared properly. 1.3 ENHANCEMENTS - The DB2 Web Query navigation tree can be traversed with the keyboard - By default, when DB2 Web Query runs an SQL SELECT statement that queries a table, FOR READ ONLY WITH UR is specified for SELECT statements that are run on a DB2 target database and do not already contain a "with ur" clause. This feature can be disabled. 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 |V3.5.6 Advanced, V4.0.5 Advanced, | |or V5.0.2 Advanced Edition ----------------------------------------------------------------------------------- Windows NT or |IBM DB2 Web Query Tool |IBM WebSphere Application Server Windows 2000 |for Multiplatforms |V3.5.6 Advanced, V4.0.5 Advanced, | |or V5.0.2 Advanced Edition ----------------------------------------------------------------------------------- OS/400 Version |IBM DB2 Web Query |IBM WebSphere Application Server 4.4 or later |Tool for iSeries |V3.5.6 Advanced, V4.0.5 Advanced, | |or V5.0.2 Advanced Edition ----------------------------------------------------------------------------------- z/OS, OS/390 |IBM DB2 Web Query | IBM WebSphere Application Server Operating System, |Tool for z/OS |V3.5.6 Advanced, V4.0.5 Advanced, Version 2 Release | |or V5 service level W502009 release 5 or higher with | |03 or higher Advanced edition UNIX System Services| | installed on MVS | | ----------------------------------------------------------------------------------- It is recommended that you keep up-to-date as updates to WebSphere V3.5, 4.0 and V5.0 become available. Note: IBM WebSphere Application Server is recommended (versions 3.5.6 Advanced, 4.0.3, and 5.0.3 Advanced Edition are supported). However, DB2 Web Query Tool is compatible with any application server that supports JSDK 1.3 and above, J2EE and JDBC 1.0. 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. Functional Dependency: If you use WebSphere Application Server on z/OS or OS/390, Version 4.0 is required in order to use the SOAP functions. Database: IBM DB2 Version 6.x 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. IBM DB2 Web Query has been tested and validated with all DB2 V 6.x and above. 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 5.0.2 on Multiplatforms to work with IBM DB2 Web Query 1. Start the WebSphere Application Server V 5.0.2 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.5 -Dclient.encoding.override=UTF-8 Where C:\IBM\CWQ1.3.5 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.5.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. 3.2 Configuring IBM WebSphere Application Server Version 5 on z/OS to work with IBM DB2 Web Query 1. Start the WebSphere Application Server Advanced edition (V5 service level W502009 release 03 or higher). Ensure that all setup has hold action be performed before CWQ install is attempted. 2. Open the WebSphere Application Server Administrative Console. 3. 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. In the Additional Properties table on the Configuration screen, click the Process Definition link. 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 4. 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 5. 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. 6. 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. 7. 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) 8. 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.5.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. 9. Select Application -> Enterprise Applications in the left pane and ensure that cwqEA appears listed as an application. 10. Save the configuration by clicking Save on the menu bar at the top of the screen. 11. Select the cwqEA application and change the WAR Classloader Policy from Module to Application. 12. Save the configuration by clicking Save on the menu bar at the top of the screen. 13. Stop then restart the application server. 14. 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. 15. 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 16. 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. 17. Click Update. The Configuration Utility closes. You can now login to DB2 Web Query. 3.3 To install DB2 Web Query Tool version 1.3 Fix Pack 5 when working with WebSphere Application Server Version 4.0.3 on Multiplatforms and iSeries: 1. Navigate to the installRoot directory on the machine where DB2 Web Query is installed. 2. Edit the wqenvset.bat file. In wqenvset.bat, change the following variable values as appropriate for your environment: - wqt_wasRoot - The directory where WebSphere Application server has been installed. - wqt_installRoot - The directory where Web Query is installed. - wqt_nodeName - The name of the WebSphere node to configure. This variable is case sensitive. - wqt_rootURI - the prefix of the URL to use to access DB2 Web Query. 3. Run wqinstall.bat. 4. Open the WebSphere Administrative Console. There will now be a DB2 Tools Server under Nodes -->Nodename --> Application Servers. Tip: If the DB2 Tools Server is not visible, close the IBM WebSphere Application Server console and start it up again. 5. Set up a new data source. a. Create a table called manager in any database with DB2 Web Query as the owner. Use the following syntax: CREATE TABLE WQ.manager ( cwqName VARCHAR (40) NOT NULL, PRIMARY KEY (cwqName) ) b. From the WebSphere Administrative console, select: Console-->New -->Data Source. The Data Source Properties window opens. c. In the Name field, type: cwqManagerDB. d. In the JNDI Name field, type: jdbc/cwqManagerDB e. In the JDBC Provider field, type: Sample DB Driver. f. On the Custom Properties panel, click the Add button. g. In the Name column, type: ″databaseName″ h. In the Value column, type the name of the database in which you created the table wq.manager. i. On the Custom Properties panel, click the Add button again. j. In the Name column, type: ″user″ k. In the Value column, type your user ID. l. On the Custom Properties panel, click the Add button again. m. In the Name column, type: ″password″ n. In the Value column, type your password. o. Click OK. 6. In the IBM WebSphere Application Server Administrative Console navigation tree, navigate to the JDBC Providers section: Resources -->JDBC Providers 7. On the JDBC Providers page, specify the implementation class name appropriate to your installation. For example: COM.ibm.db2.jdbc.app.DB2driver 8. Navigate to the data source that you just created and click it. It will appear under: Resources -->JDBC Providers --> Sample DB Driver --> Data Sources in the Navigation tree. 9. Click the Connection Pooling tab. 10. Check the Disable AutoConnection Cleanup checkbox. 11. Click Apply. 12. Right-click Enterprise Applications on the Administrative Console. A pop-up menu appears. 13. From the pop-up menu, select: Install Enterprise Application. The Application Installation Wizard opens. 14. Click the Browse button that is next to Install Application (*.ear). The Browse window opens. 15. Navigate to the CWQ\conf directory and select cwq.ear. Click Open. The path to cwq.ear is added to the Path field. 16. Click Next. The Mapping User Roles Screen opens. 17. Click Next. The Mapping EJB RunAs Roles to Users Screen opens. 18. Click Next. The Binding Enterprise Beans to JNDI Names Screen opens. 19. Click Next. The Mapping EJB References to Enterprise Beans Screen opens. 20. Click Next. The Mapping Resource References to Resources Screen opens. 21. Click Select Resource. A pop-up window opens. 22. Select cwqDBManager and click OK. 23. Click Next. The Specifying the Default Data source for EJB Modules Screen opens. 24. Click Next. The Specifying Data Sources for Individual CMP Beans Screen opens. 25. Click Next. The Selecting Virtual Host for Web Modules Screen opens. 26. Click Next. The Selecting Application Servers Screen opens. 27. In the Module column, click cwqManager EJB. 28. Click Select Server. A pop-up window opens. 29. Select the DB2 Tools Server. Click OK. 30. In the Module column, click cwqWA. 31. Click Select Server. A pop-up window opens. 32. Select the DB2 Tools Server. Click OK. 33. Click Next. The Completing the Application Installation Wizard opens. 34. Click Finish. A message appears asking you if you want to regenerate the code now. Click No. (The deployment may take a couple of minutes). When the deployment is complete, a cwqEA folder will appear under Enterprise Applications on the WebSphere Application server Administrative Console. 35. Right click the DB2 Tools Server. A pop-up menu opens. 36. On the WebSphere Administrative Console navigation tree (in the left pane of the window), click the DB2 Tools Server branch. 37. On the right pane of the WebSphere Administrative Console, click the Custom tab. The Custom page opens. 38. In the table on the Custom page, ensure that Automatic Generation of Plugin is set to true. 39. Right click the DB2 Tools Server. A pop-up menu appears. Select Start. 40. Open the DB2 Web Query Configuration Utility by accessing the following URL: http://server/DB2Tools/WebQuery/Configure The initial user id is: cwq. The initial password is: cwq 41. In the Configuration Utility, specify the DB2 Web Query initial parameters. For more information on initial parameters, see the “Parameter list” on page 8. Note: 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 3.4 To Install DB2 Web Query Tool version 1.3 Fix Pack 5 when working with WebSphere Application Server Version 4.0.3 on z/OS 1. Ensure that WebSphere Application Server Version 4.0.3 is installed and functioning properly. a) Install WebSphere Application Server 4.0.3 for z/OS b) Install WebSphere Service Level 95 and all associated updates for related systems. c) Start WebSphere and associated services. d) Verify that the IVP is operational. To check that the IVP is operational, access the following URL: http:///webapp/examples/ 2. Stop all WebSphere Web servers. To stop the servers, issue the following cancel commands for the J2EE and HTTPd servers from SDSF: /c bboasr2.bboasr2a /c httpd1 3. Create a table called manager in any database with DB2 Web Query as the owner. Use the following syntax: CREATE TABLE WQ.manager ( cwqName VARCHAR (40) NOT NULL, PRIMARY KEY (cwqName) ) Note: This table must be accessible from the system on which DB2 Web Query is running. If you are working on z/OS or os/390, you must also create a unique or primary index for wq.manager using the following syntax: CREATE UNIQUE INDEX wq.manageridx ON wq.manager ( cwqname asc ) 4. Decompress the DB2 Web Query files into the DB2 Web Query installRoot. To determine the appropriate archive to decompress, see section 2.2, SOFTWARE REQUIREMENTS. 5. Ensure that you have read and write permission to the DB2 Web Query installRoot directory so that configuration and log files can be created and written. 6. Update the HTTPd configuration. To update the HTTPd configuration, add the following directory to httpd.conf: Service /DB2Tools/* /usr/lpp/WebSphere/WebServerPlugIn/bin/was400plugin.so:service_exit Ensure that the path to was400plugin.so is correct. 7. Add the following lines to the jvm.properties file: client.encoding.override=UTF-8 com.ibm.db2.cwq.installRoot= Note: The default location is for the jvm.properties file is: /WebSphere390/CB390/controlinfo/envfile/SVSCPLEX/BBOASR2A/jvm.properties 8. In the webcontainer.conf file, locate the following line: session.invalidatetime= Update its value to your desired timeout. This value is in milliseconds. The default value is 180000 (3 minutes). The recommended value is 3600000 (1 hour) and it may be changed to fit your requirements. NOTE: The default location for this file is: /WebSphere390/CB390/controlinfo/envfile/SVSCPLEX/BBOASR2A/webcontainer.conf 9. Install and start the WebSphere Application Server for z/OS and os/390 Administration client. 10. From the WebSphere Application Server for z/OS and os/390 Administration client, connect to WebSphere. 11. In WebSphere Application Server for z/OS and os/390 Administration client, create a new conversation. To create a new conversation using the WebSphere Administration client for z/OS: a) From WebSphere Application Server for z/OS and os/390 Administration client, connect or login to the z/OS or os/390 machine where DB2 Web Query is installed. b) Click the Conversation Node on the left side of the screen. c) Right click the Conversation node in the left side of the screen. From the pop-up menu, select Add. d) Type a name for the conversation that is appropriate for your environment in the Name field. e) Click Save. 12. Identify data locations (subsystems) that you want to access using DB2 Web Query. 13. Create a new data source for each data location that you want to access using DB2 Web Query. Make note of the name of the new data sources. These data source names will be used during the DB2 Web Query configuration as the data source name. Data sources are needed in order for DB2 Web Query to connect to any DB2 data location, including the DB2 Web Query manager table. 14. In WebSphere Application Server for z/OS and os/390 Administration client, install the DB2 Web Query J2EE Application. To install the DB2 Web Query J2EE Application: a) In the WebSphere Application Server for z/OS and os/390 Administration client, expand the navigation tree in the left pane to J2EEApplications: Conversations//Sysplexes//J2EEServers/ b) Right click the defined server and select: Install J2EE application c) Specify the cwq-1.3.4_390.ear file and click OK. The Reference and Resource Resolution window opens NOTE: cwq-1.3.4_390.ear must be located on the machine from which you are running the WebSphere Application Server for z/OS and os/390 Administration client. The default location for this file is the /Conf directory on the machine where DB2 Web Query is installed. 15. In the Reference and Resource Resolution window, expand the following directories in the navigation tree in the left pane of the window: cwqEA/cwqManagerEJB/CwqManager click the J2EE Resource tab and select the data source where the DB2 Web Query Manager table is located. 16. In the navigation tree in the left pane of the Reference and Resource Resolution window expand the following directories: cwqEA/cwqWA_WebApp.jar/cwqWA_WebApp 17. Click the EJB tab. The EJB page opens. 18. On the EJB page, click the Set Default JNDI Path & Name button. 19. Click the Reference tab. The Reference page opens. 20. From the Reference page, select (ejb-link)CwqManager from the JNDI Name drop-down list. 21. Click OK to finish installing the DB2 Web Query Enterprise Application. 22. Activate the Conversation. a) Right click: Conversations/cwqEA A pop-up menu appears. From the pop-up menu, select Validate. b) Right click: Conversations/cwqEA A pop-up menu appears. From the pop-up menu, select Commit. c) Right click: Conversations/cwqEA A pop-up menu appears. From the pop-up menu, select Complete --> All Tasks. d) Right click: Conversations/cwqEA A pop-up menu appears. From the pop-up menu, select Activate. The cwqEA Conversation is active. A lock symbol with a lightening bolt appears. This may take some time. 23. Start the WebSphere Web servers. To start the WebSphere Web servers, issue the start command for the J2EE and HTTPd servers To start the J2EE and HTTPd servers using TSO SDSF, issue the following commands: /s bboasr2.bboasr2a /s httpd1 24. Access the DB2 Web Query Configuration Utility by going to the following URL: http:///DB2Tools/WebQuery/Configure 25. From the Configuration utility, set the configuration parameters. For more information on the DB2 Web Query Configuration parameters, see the "Parameter List" in Chapter 2 of the DB2 Web Query User's guide. NOTE: You must add a database driver entry for each database location that was installed in the WebSphere Application Server for z/OS and os/390 Administration client. You can select from the list of default database drivers or you can create a custom database driver by checking the Custom check box and filling in the Name and Connection Pool fields. You must Click the Update button after each database driver that you add. NOTE: Ensure that the wqUserId 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 26. Start DB2 Web Query. Using a Web browser open the following URL: http:///DB2Tools/WebQuery The DB2 Web Query login screen opens. 3.5 To install DB2 Web Query Tool version 1.3 Fix Pack 5 when working with WebSphere Application Server Version 3.5.6 1. Stop the WebSphere Administrative Console and the Administration client service if they are started. 2. Navigate to the following file and open it: WebSphere\AppServer\bin\admin.config 3. Find com.ibm.ejs.sm.adminserver.classpath in admin.config. Insert the following directly after the equals sign that is to the right of com.ibm.ejs.sm.adminserver.classpath: installroot/servlet/xercesImpl.jar;installroot/servlet/ xml-apis.jar;installroot/servlet/xalan.jar; Note: There will already be content to the right of the equals sign. The above must be placed directly after the equals sign, before any existing content. If you are working in Windows, the path to the install root must use the following syntax: drive letter\:/directories For further illustration, see the example below. For example in Windows: e\:/IBM/CWQ/servlet/xercesImpl.jar;e\:/IBM/CWQ/servlet/ xml-apis.jar;e\:/IBM/CWQ/servlet/xalan.jar; 4. Restart the administration client and Administrative Console. 5. Create a table called manager in any database with DB2 Web Query as the owner. Use the following syntax: CREATE TABLE WQ.manager ( cwqName VARCHAR (40) NOT NULL, PRIMARY KEY (cwqName) ) Note: This table must be accessible from the system on which DB2 Web Query is running. If you are working on z/OS or OS/390, you must also create a unique or primary index for wq.manager using the following syntax: CREATE UNIQUE INDEX wq.manageridx ON wq.manager ( cwqname asc ) 6. Navigate to the installRoot on the machine that is running DB2 web Query. For example: CWQ\conf\multiplatform\win\was35x 7. Edit the wqenvset.bat file. In wqenvset.bat, change the following variable values as appropriate for your environment: - wqt_wasRoot - The directory where WebSphere Application server has been installed. - wqt_installRoot - The directory where Web Query is installed. - wqt_nodeName - The name of the WebSphere node that needs to be configured. This variable is case sensitive. - wqt_rootURI - the prefix of the URL that will be used to access DB2 Web Query. 8. Run wqinstall.bat. 9. Run wqstart.bat. 10. Open the WebSphere Administrative Console. There will now be a ″DB2 Tools Server″ under Nodes. Note: If the ″DB2 ToolsServer″ is not visible, close the console and start it again. 11. Expand DB2 Tools Server under the Node Name. 12. Click ejbContainer on Administration Console navigation tree. 13. Click the DataSource tab. 14. In the Userid box, type the user ID that is used to access the WQ.manager table that you created in the first step. 15. In the Password box, type the password that is used to access the WQ.manager table that you created in the first step. 16. Click Apply. 17. Click jdbc/cwqManagerDB on Administration Console navigation tree. Ensure the driver that it is attached to is a valid DB2 Driver - if it is not, create a new driver and attach jdbc/cwqManagerDB to it (the steps to create a new driver are below). It should also be attached to the database that WQ.manager is under. To create a new JDBC driver: a. Select Console --> Tasks --> Create Data Source b. Use the WebSphere graphical User Interface to create and install a new JDBC driver. c. Name your newly created JDBC driver. d. From the Class Name drop-down list, select a class name or type a class name in the Class Name field. (Typically COM.ibm.db2.jdbc.app.DB2Driver for DB2 on Windows. This one is not in the list). Class names are case sensitive. e. Select Node. f. Specify the location of the DB2 driver’s file (typically db2java.zip even though it may ask for a .jar file) g. Type a data source name in the Data Source Name field. h. Type the name of the database where the WQ.manager table is located, in the Database Name field. i. Click Finish. 18. Open the DB2 Web Query Configuration Utility by accessing the following URL: http://server/DB2Tools/WebQuery/Configure The initial user id is: cwq. The initial password is: cwq 19. On the Configuration screen, change the initialContextfactory parameter to: com.ibm.ejs.ns.jndi.CNInitialContextFactory 20. In the Configuration Utility, specify the DB2 Web Query initial parameters. For more information on initial parameters, see the “Parameter list” on page 8. Note: 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 21. Click Update. The Configuration Utility closes. You can now login to DB2 Web Query. 4.0 CONFIGURATION 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 5 is equivalent to DB2 Web Query Tool Version 1 Release 3 Fix Pack 5. 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: - 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 website. 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 Lunux, 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. - WebQuery Tool must not be installed in a folder with double byte characters in the name. - SOAP functionality is supported on WebSphere Application Server 4.0.3 and higher only. SOAP functionality is not supported on WebSphere Application Server 3.5.6. 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 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_FP5-mp-win.zip | +-----------------------+----------------------+--------------------------------+ | Windows or UNIX | iSeries |cwq-1.3_FP5-mp-iseries.zip | +-----------------------+----------------------+--------------------------------+ | Windows or UNIX | z/OS |cwq-1.3_FP5-mp-zos.tar | +-----------------------+----------------------+--------------------------------+ | Windows or UNIX | UNIX |cwq-1.3_FP5-mp-unix.tar | +-----------------------+----------------------+--------------------------------+ | iSeries | Windows |cwq-1.3_FP5-iseries-win.zip | +-----------------------+----------------------+--------------------------------+ | iSeries | iSeries |cwq-1.3_FP5-iseries-iseries.zip | +-----------------------+----------------------+--------------------------------+ | iSeries | z/OS |cwq-1.3_FP5-iseries-zos.tar | +-----------------------+----------------------+--------------------------------+ | iSeries | UNIX |cwq-1.3_FP5-iseries-unix.tar | +-----------------------+----------------------+--------------------------------+ | z/OS | Windows |cwq-1.3_FP5-zos-win.zip | +-----------------------+----------------------+--------------------------------+ | z/OS | iSeries |cwq-1.3_FP5-zos-iseries.zip | +-----------------------+----------------------+--------------------------------+ | z/OS | z/OS |cwq-1.3_FP5-zos-zos.tar | +-----------------------+----------------------+--------------------------------+ | z/OS | UNIX |cwq-1.3_FP5-zos-unix.tar | +-----------------------+----------------------+--------------------------------+ | DB2 Web Query for Workgroups Archives | +-----------------------+----------------------+--------------------------------+ | Platform on which DB2 | Platform on which | Archive | | Resides | you are installing | | | | DB2 Web Query | | +-----------------------+----------------------+--------------------------------+ | Windows or UNIX | Windows |cwq-1.3_FP5-wse-win.zip | +-----------------------+----------------------+--------------------------------+ | Windows or UNIX | UNIX |cwq-1.3_FP5-wse-unix.tar | +-----------------------+----------------------+--------------------------------+ 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 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 application 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 program 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 Notices of other companies 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 iSeries z/OS zSeries 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 IBM Corporation 2001, 2004. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.