IBM(R) DB2(R) Web Query Tool for Multiplatforms, Version 1 Release 3 Fix Pack 4 IBM DB2 Web Query Tool for Workgroups, Version 1 Release 3 Fix Pack 4 Interim Fix 20040114 Install Instructions CONTENTS 1.0 Problem Description 2.0 Installation Instructions 2.1 To install DB2 Web Query Tool version 1.3 Fix Pack 4 Interim Fix 20040114 when working with WebSphere Application Server Version 4.0.3 on Multiplatforms and iSeries 2.2 To install DB2 Web Query Tool version 1.3 Fix Pack 4 Interim Fix 20040114 when working with WebSphere Application Server Version 4.0.1 on z/OS 2.3 To upgrade to DB2 Web Query Tool version 1.3 Fix Pack 4 Interim Fix 20040114 when working with WebSphere Application Server Version 3.5.6 3.0 Back out Instructions 3.1 To install DB2 Web Query Tool version 1.3 Fix Pack 4 when working with WebSphere Application Server Version 4.0.3 on Multiplatforms and iSeries 3.2 To install DB2 Web Query Tool version 1.3 Fix Pack 4 when working with WebSphere Application Server Version 4.0.1 on z/OS 3.3 To upgrade to DB2 Web Query Tool version 1.3 Fix Pack 4 when working with WebSphere Application Server Version 3.5.6 ________________________________________________________________________________ 1.0 Problem Description Query Row Limit was not being inforced in all circumstances. Query Row Limit now works properly in all situations. 2.0 Installation Instructions Install the selected updates using either PKZIP for zip file format or GUNZIP for tar file format. 2.1 To install DB2 Web Query Tool version 1.3 Fix Pack 4 Interim Fix 20040114 when working with WebSphere Application Server Version 4.0.3: 1. Navigate to the installRoot directory on the machine where DB2 Web Query is installed. 2. Save cwq.conf as cwq_current.conf. 3. Decompress the DB2 Web Query Tool version 1.3 Fix Pack 4 Interim Fix 20040114 archive into the DB2 Web Query installRoot. 4. Open the WebSphere Administrative Console. Navigate to the DB2 Tools Server under Nodes -->[Nodename] --> Application Servers --> DB2 Tools Server. (DB2 Tools server is the default name, the server, could be named differently in your configuration. Stop the DB2 Tools Server. 5. In the WebSphere Administrative Console, navigate to Enterprise Applications --> cwqEA and remove it. 6. Right-click Enterprise Applications on the Administrative Console. A pop-up menu appears. 7. From the pop-up menu, select: Install Enterprise Application. The Application Installation Wizard opens. 8. Click the Browse button that is next to Install Application (*.ear). The Browse window opens. 9. Navigate to the CWQ\conf directory and select cwq-1.3_FP4_IF1.ear. Click Open. The path to cwq-1.3_FP4_IF1.ear is added to the Path field. 10. Click Next. The Mapping User Roles Screen opens. 11. Click Next. The Mapping EJB RunAs Roles to Users Screen opens. 12. Click Next. The Binding Enterprise Beans to JNDI Names Screen opens. 13. Click Next. The Mapping EJB References to Enterprise Beans Screen opens. 14. Click Next. The Mapping Resource References to Resources Screen opens. 15. Click Select Resource. A pop-up window opens. 16. Select cwqManagerDB and click OK. 17. Click Next. The Specifying the Default Data source for EJB Modules Screen opens. 18. Click Next. The Specifying Data Sources for Individual CMP Beans Screen opens. 19. Click Next. The Selecting Virtual Host for Web Modules Screen opens. 20. Click Next. The Selecting Application Servers Screen opens. 21. In the Module column, click cwqManager EJB. 22. Click Select Server. A pop-up window opens. 23. Select the DB2 Tools Server. Click OK. 24. In the Module column, click cwqWA. 25. Click Select Server. A pop-up window opens. 26. Select the DB2 Tools Server. Click OK. 27. Click Next. The Completing the Application Installation Wizard opens. 28. 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. 29. On the WebSphere Administrative Console navigation tree (in the left pane of the window), click the DB2 Tools Server branch. 30. On the right pane of the WebSphere Administrative Console, click the Custom tab. The Custom page opens. 31. In the table on the Custom page, ensure that Automatic Generation of Plugin is set to true. 32. Navigate to the installRoot directory on the machine where DB2 Web Query is installed. 33. Save cwq_current.conf as cwq.conf. 34. Right click the DB2 Tools Server. A pop-up menu appears. Select Start. 35. Start DB2 Web Query. Using a Web browser open the following URL: http:///DB2Tools/WebQuery The DB2 Web Query login screen opens. 2.2 To Install DB2 Web Query Tool version 1.3 Fix Pack 4 Interim Fix 20040114 when working with WebSphere Application Server Version 4.0.1 on z/OS 1. Stop all WebSphere Web servers. To stop the servers, issue the following commands to stop the J2EE and HTTPd servers from SDSF: /p bboasr2.bboasr2a /p httpd1 2. Navigate to the installRoot directory on the machine where DB2 Web Query is installed. 3. Save cwq.conf as cwq_current.conf. 4. Decompress the DB2 Web Query Tool version 1.3 Fix Pack 4 Interim Fix 20040114 archive into the DB2 Web Query installRoot. 5. Save cwq_current.conf as cwq.conf. 6. 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 7. Start the WebSphere Application Server for z/OS and os/390 Administration client. 8. From the WebSphere Application Server for z/OS and os/390 Administration client, connect to WebSphere. 9. 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_FP4_IF1_390.ear file and click OK. The Reference and Resource Resolution window opens NOTE: cwq-1.3_FP4_IF1_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. 10. 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. 11. 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 12. Click the EJB tab. The EJB page opens. 13. On the EJB page, click the Set Default JNDI Path & Name button. 14. Click the Reference tab. The Reference page opens. 15. From the Reference page, select (ejb-link)CwqManager from the JNDI Name drop-down list. 16. Click OK to finish installing the DB2 Web Query Enterprise Application. 17. 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. 18. Navigate to the installRoot directory on the machine where DB2 Web Query is installed. 19. Start DB2 Web Query. Using a Web browser open the following URL: http:///DB2Tools/WebQuery The DB2 Web Query login screen opens. 2.3 To install DB2 Web Query Tool version 1.3 Fix Pack 4 Interim Fix 20040114 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 installRoot directory on the machine where DB2 Web Query is installed. 3. Save cwq.conf as cwq_current.conf. 4. Decompress the DB2 Web Query Tool version 1.3 Fix Pack 4 Interim Fix 20040114 archive into the DB2 Web Query installRoot. 5. Open the WebSphere Administrative Console. Expand DB2 Tools Server under the Node Name. 6. Restart the DB2 Tools Server using the WebSphere Administrative Console. 7. Start DB2 Web Query. Using a Web browser open the following URL: http:///DB2Tools/WebQuery The DB2 Web Query login screen opens. 3.0 Back out Instructions To back out DB2 Web Query V 1.3 Fix Pack 4, Interim Fix 20040114, install DB2 Web Query V1.3 Fix Pack 4. 3.1 To install DB2 Web Query Tool version 1.3 Fix Pack 4 when working with WebSphere Application Server Version 4.0.3: 1. Navigate to the installRoot directory on the machine where DB2 Web Query is installed. 2. Save cwq.conf as cwq_current.conf. 3. Decompress the DB2 Web Query Tool version 1.3 Fix Pack 4 archive into the DB2 Web Query installRoot. 4. Open the WebSphere Administrative Console. Navigate to the DB2 Tools Server under Nodes -->[Nodename] --> Application Servers --> DB2 Tools Server. (DB2 Tools server is the default name, the server, could be named differently in your configuration. Stop the DB2 Tools Server. 5. In the WebSphere Administrative Console, navigate to Enterprise Applications --> cwqEA and remove it. 6. Right-click Enterprise Applications on the Administrative Console. A pop-up menu appears. 7. From the pop-up menu, select: Install Enterprise Application. The Application Installation Wizard opens. 8. Click the Browse button that is next to Install Application (*.ear). The Browse window opens. 9. Navigate to the CWQ\conf directory and select cwq-1.3.4.ear. Click Open. The path to cwq-1.3.4.ear is added to the Path field. 10. Click Next. The Mapping User Roles Screen opens. 11. Click Next. The Mapping EJB RunAs Roles to Users Screen opens. 12. Click Next. The Binding Enterprise Beans to JNDI Names Screen opens. 13. Click Next. The Mapping EJB References to Enterprise Beans Screen opens. 14. Click Next. The Mapping Resource References to Resources Screen opens. 15. Click Select Resource. A pop-up window opens. 16. Select cwqManagerDB and click OK. 17. Click Next. The Specifying the Default Data source for EJB Modules Screen opens. 18. Click Next. The Specifying Data Sources for Individual CMP Beans Screen opens. 19. Click Next. The Selecting Virtual Host for Web Modules Screen opens. 20. Click Next. The Selecting Application Servers Screen opens. 21. In the Module column, click cwqManager EJB. 22. Click Select Server. A pop-up window opens. 23. Select the DB2 Tools Server. Click OK. 24. In the Module column, click cwqWA. 25. Click Select Server. A pop-up window opens. 26. Select the DB2 Tools Server. Click OK. 27. Click Next. The Completing the Application Installation Wizard opens. 28. 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. 29. On the WebSphere Administrative Console navigation tree (in the left pane of the window), click the DB2 Tools Server branch. 30. On the right pane of the WebSphere Administrative Console, click the Custom tab. The Custom page opens. 31. In the table on the Custom page, ensure that Automatic Generation of Plugin is set to true. 32. Navigate to the installRoot directory on the machine where DB2 Web Query is installed. 33. Save cwq_current.conf as cwq.conf. 34. Right click the DB2 Tools Server. A pop-up menu appears. Select Start. 35. Start DB2 Web Query. Using a Web browser open the following URL: http:///DB2Tools/WebQuery The DB2 Web Query login screen opens. 4.2 To Install DB2 Web Query Tool version 1.3 Fix Pack 4 when working with WebSphere Application Server Version 4.0.1 on z/OS 1. Stop all WebSphere Web servers. To stop the servers, issue the following commands to stop the J2EE and HTTPd servers from SDSF: /p bboasr2.bboasr2a /p httpd1 2. Navigate to the installRoot directory on the machine where DB2 Web Query is installed. 3. Save cwq.conf as cwq_current.conf. 4. Decompress the DB2 Web Query Tool version 1.3 Fix Pack 4 archive into the DB2 Web Query installRoot. 5. Save cwq_current.conf as cwq.conf. 6. 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 7. Start the WebSphere Application Server for z/OS and os/390 Administration client. 8. From the WebSphere Application Server for z/OS and os/390 Administration client, connect to WebSphere. 9. 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. 10. 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. 11. 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 12. Click the EJB tab. The EJB page opens. 13. On the EJB page, click the Set Default JNDI Path & Name button. 14. Click the Reference tab. The Reference page opens. 15. From the Reference page, select (ejb-link)CwqManager from the JNDI Name drop-down list. 16. Click OK to finish installing the DB2 Web Query Enterprise Application. 17. 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. 18. Navigate to the installRoot directory on the machine where DB2 Web Query is installed. 19. Start DB2 Web Query. Using a Web browser open the following URL: http:///DB2Tools/WebQuery The DB2 Web Query login screen opens. 4.3 To install DB2 Web Query Tool version 1.3 Fix Pack 4 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 installRoot directory on the machine where DB2 Web Query is installed. 3. Save cwq.conf as cwq_current.conf. 4. Decompress the DB2 Web Query Tool version 1.3 Fix Pack 4 archive into the DB2 Web Query installRoot. 5. Open the WebSphere Administrative Console. Expand DB2 Tools Server under the Node Name. 6. Restart the DB2 Tools Server using the WebSphere Administrative Console. 7. Start DB2 Web Query. Using a Web browser open the following URL: http:///DB2Tools/WebQuery The DB2 Web Query login screen opens.