Interim fix CLM_602_iFix002.zip This interim fix is only valid for the Rational solution for Collaborative Lifecycle Management (CLM) 6.0.2 release. The Rational solution for CLM 6.0.3 is the next release that will include all these fixes. If you plan to upgrade, upgrade to version 6.0.3 or later. CONTENTS OF THIS INTERIM FIX 1. This readme file: readme.txt 2. Server patch file: CLM_server_patch_6.0.2.0-CALM602M-I20160603-1042.zip (see the SERVER PATCH INSTRUCTIONS section) 3. Jazz Reporting Service (Report Builder) patch file: rs.war (see the JAZZ REPORTING SERVICE INSTRUCTIONS section) 4. Lifecycle Query Engine patch file: lqe.war (see the LIFECYCLE QUERY ENGINE AND LINK INDEX PROVIDER INSTRUCTIONS section) 5. Link Index Provider patch file: ldx.war (see the LIFECYCLE QUERY ENGINE AND LINK INDEX PROVIDER INSTRUCTIONS section) 6. Rational Team Concert Client for Eclipse update site: UpdateSiteFor_6.0.2.0-CALM602M-I20160603-1042.zip (see the RATIONAL TEAM CONCERT CLIENT FOR ECLIPSE UPDATE SITE INSTRUCTIONS section) 7. Rational Team Concert Client for Microsoft Visual Studio readme file: readme-vsclient.txt 8. Rational Team Concert Client for Microsoft Visual Studio patch file: rtc_vsclient_I6.0.2_iFix002.zip (see the RATIONAL TEAM CONCERT CLIENT FOR MICROSOFT VISUAL STUDIO INSTRUCTIONS section) 9. Oracle Outside In Technology fix: OutsideIn_8-5-2_Patch_CPU_April2016.zip (see the UPDATING ORACLE OUTSIDE IN TECHNOLOGY FOR RDNG section) 10. WebSphere Application Server script file: clm_update.py (see the LIFECYCLE QUERY ENGINE AND LINK INDEX PROVIDER INSTRUCTIONS and JAZZ REPORTING SERVICE INSTRUCTIONS sections) In addition to the fixes listed in this readme file, the interim fix might also contain fixes for security issues. For details, see the IBM Product Security Incident Response Blog: https://www.ibm.com/connections/blogs/PSIRT/tags/psirtrational CONTENTS OF THIS FILE 1. SERVER PATCH INSTRUCTIONS 2. JAZZ REPORTING SERVICE (REPORT BUILDER) INSTRUCTIONS 3. DATA COLLECTION COMPONENT INSTRUCTIONS 4. LIFECYCLE QUERY ENGINE AND LINK INDEX PROVIDER INSTRUCTIONS 5. RATIONAL TEAM CONCERT CLIENT FOR ECLIPSE UPDATE SITE INSTRUCTIONS 6. RATIONAL TEAM CONCERT CLIENT FOR MICROSOFT VISUAL STUDIO INSTRUCTIONS 7. ADDITIONAL FIXES INSTRUCTIONS 8. APAR FIXES 9. CLIENT APAR FIXES 10. UPDATING ORACLE OUTSIDE IN TECHNOLOGY FOR RDNG 11. KNOWN ISSUES 1. SERVER PATCH INSTRUCTIONS Note: -The CLM server patch file, CLM_server_patch_6.0.2.0-CALM602M-I20160603-1042.zip, might contain fixes for either a subset or all of these applications: Jazz Team Server, Rational Team Concert, Rational Quality Manager, Rational DOORS Next Generation, Data Collection Component, Rational Engineering Lifecycle Manager, CLM Server Monitoring. For the list of APARs that were fixed, listed by application, see the APAR FIXES section. -Before you install the server patch file, CLM_server_patch_6.0.2.0-CALM602M-I20160603-1042.zip, verify that no other test fixes or hot fixes are installed. If other fixes are installed, contact IBM Software Support. -For a CLM deployment on a single server, complete the following steps once. For a distributed CLM deployment, complete the same steps on each server. To install the server patch: a. Stop the CLM server. b. Verify whether the following directory exists: /server/patch. -If the directory exists, back up and then remove its contents. -If the directory does not exist, create it. c. Copy the server patch file, CLM_server_patch_6.0.2.0-CALM602M-I20160603-1042.zip, into the /server/patch directory. d. Clear the application server cache. For instructions on clearing the cache, consult the application server's detailed documentation. For instructions on what to remove, see the "To clear the application cache on WebSphere Application Server", "To clear the application cache on WebSphere Liberty Server" and "To clear the application cache on Apache Tomcat" sections in this file. e. Start the CLM server. f. Run repotools- -clean for each application that is installed to clear the repotools cache. Note: This will also display the help output. For instance: - repotools-jts -clean - repotools-ccm -clean - repotools-qm -clean - repotools-rm -clean g. To ensure that the Data Collection Component mapping files are correctly updated, please follow the instructions in the DATA COLLECTION COMPONENT INSTRUCTIONS section below Note: For a distributed CLM deployment, complete the same steps on each server, including the DCC server, if the DCC component exists on a separate machine. To uninstall the server patch: a. Stop the CLM server. b. Back up and then remove the contents of the following directory: /server/patch c. Clear the application server cache. For instructions on clearing the cache, consult the application server's detailed documentation. For instructions on what to remove, see the "To clear the application cache on WebSphere Application Server", "To clear the application cache on WebSphere Liberty Server" and "To clear the application cache on Apache Tomcat" sections in this file. d. Start the CLM server. e. Run repotools- -clean for each application that is installed. Note: This will also display the help output. For instance: - repotools-jts -clean - repotools-ccm -clean - repotools-qm -clean - repotools-rm -clean To clear the application cache on WebSphere Application Server: Remove the contents from these directories under the profile root(e.g. //profiles/), except for the noted help directory: temp, wstemp, workspace. Note: Do not remove this directory, which is required for the CLM local help: temp/{jts_node}/{jts_server}/clmhelp_war. To clear the application cache on WebSphere Liberty Server: We have not identified the need to clear any cache in WebSphere Liberty Server To clear the application cache on Apache Tomcat: Remove the contents from these directories under the tomcat root, except for the noted help directory: temp, work. Note: Do not remove this directory, which is required for the CLM local help: /server/tomcat/work/Catalina/localhost/clmhelp. To validate that the server patch was successfully installed or uninstalled: a. After the server starts, open a CLM application. b. Click Help > About the Server. c. In the Build Information section, review the interim fix information to confirm that it is either installed (listed) or uninstalled (not listed). 2. JAZZ REPORTING SERVICE (REPORT BUILDER) INSTRUCTIONS To install the patch with Jazz Reporting Service (Report Builder) deployed on WebSphere Application Server: Option 1: Using the WebSphere Application Server scripting tool (wsadmin) a. Open a command window and navigate to the WebSphere profile bin directory (e.g. //profiles//bin). b. Execute the following command, ensuring that the WebSphere Application Server is running: Windows: wsadmin -language jython -user -password -f /server/was/clm_update.py> Linux: ./wsadmin.sh -language jython -user -password -f /server/was/clm_update.py> NOTE: This will update all applications with war files from the iFixPatch directory specified Option 2: Using the WebSphere Application Server Admin Console a. In the WebSphere Application Server Admin Console, stop the Jazz Reporting Service: Click Applications > Application Types > WebSphere enterprise applications, select the rs_war check box, and click Stop. b. Update the rs_war file: Select the rs_war check box and click Update. c. Select "Replace the entire application," browse to the new rs.war file in the location that you extracted it to, and click Next. d. Follow the Fast Path installation, and accept all of the default values. e. After the update is complete, save the configuration changes when you are prompted to. f. Start the Jazz Reporting Service: Select the rs_war check box and click Start. To uninstall the patch with Jazz Reporting Service (Report Builder) deployed on WebSphere Application Server: Option 1: Using the WebSphere Application Server scripting tool (wsadmin) a. Locate the rs.war file in the original Jazz Reporting Service installation. If there are other war files in this directory, copy the war files that you want to update to a new temporary folder (the clm_update.py script updates all applications with war files in the directory specified). a. Open a command window and navigate to the WebSphere profile bin directory (e.g. //profiles//bin). b. Execute the following command, ensuring that the WebSphere Application Server is running: Windows: wsadmin -language jython -user -password -f /server/was/clm_update.py> /server/webapps> Linux: ./wsadmin.sh -language jython -user -password -f /server/was/clm_update.py> /server/webapps> Option 2: Using the WebSphere Application Server Admin Console a. Locate the rs.war file in the original Jazz Reporting Service installation. b. In the WebSphere Application Server Admin Console, stop the Jazz Reporting Service: Click Applications > Application Types > WebSphere enterprise applications, select the rs_war check box, and click Stop. c. Update the rs_war file: Select the rs_war check box and click Update. d. Select "Replace the entire application," browse to the rs.war file in the original installation location, and click Next. e. Follow the Fast Path installation, and accept all of the default values. f. After the update is complete, save the configuration changes when you are prompted to. g. Start the Jazz Reporting Service: Select the rs_war check box and click Start. To install the patch with Jazz Reporting Service (Report Builder) deployed on WebSphere Liberty Server: a. Rename the new rs.war file as rs.war.zip. b. Stop the WebSphere Liberty Server for the Jazz Reporting Service. c. Back up the following file in case you need to revert the patch: \server\liberty\servers\clm\apps\rs.war.zip d. Delete the following files: \server\liberty\servers\clm\apps\rs.war.zip \server\liberty\clmServerTemplate\apps\rs.war.zip e. Delete the following directories: \server\liberty\servers\clm\apps\rs.war \server\liberty\clmServerTemplate\apps\rs.war f. Place the new rs.war.zip file in the following directories: \server\liberty\servers\clm\apps \server\liberty\clmServerTemplate\apps g. Unzip the new rs.war.zip file into the following directories: \server\liberty\servers\clm\apps\rs.war \server\liberty\clmServerTemplate\apps\rs.war h. Start the server. To uninstall the patch with Jazz Reporting Service (Report Builder) deployed on WebSphere Liberty Server: a. Stop the WebSphere Liberty Server for the Jazz Reporting Service. b. Restore the original rs.war.zip file that was backed up during the installation to the following directories: \server\liberty\servers\clm\apps \server\liberty\clmServerTemplate\apps c. Delete the following directories: \server\liberty\servers\clm\apps\rs.war \server\liberty\clmServerTemplate\apps\rs.war d. Unzip the original rs.war.zip file into the following directories: \server\liberty\servers\clm\apps\rs.war \server\liberty\clmServerTemplate\apps\rs.war e. Start the server. To install the patch with Jazz Reporting Service (Report Builder) deployed on Apache Tomcat: a. Stop the Apache Tomcat server for the Jazz Reporting Service. b. Back up the following file in case you need to revert the patch: \server\tomcat\webapps\rs.war c. Delete the following file: \server\tomcat\webapps\rs.war d. Delete the following directories: \server\tomcat\webapps\rs \server\tomcat\work\Catalina\localhost\rs e. Place the new rs.war file in the \server\tomcat\webapps directory. f. Start the server. To uninstall the patch with Jazz Reporting Service (Report Builder) deployed on Apache Tomcat server: a. Stop the Apache Tomcat server for the Jazz Reporting Service. b. Restore the original rs.war file that was backed up during the installation to the following directory: \server\tomcat\webapps\ c. Delete the following directories: \server\tomcat\webapps\rs \server\tomcat\work\Catalina\localhost\rs d. Start the server. To verify that the patch was successfully installed: a. After the server starts, open the Jazz Reporting Service home page. b. Click the question mark icon near the upper right. c. Select About Jazz Reporting Service. d. Check that the build ID in the dialog box is JRS_6.0.2-I20160602-2043 3. DATA COLLECTION COMPONENT INSTRUCTIONS To ensure that the Data Collection Component mapping files are correctly updated, after performing step 1 above to install the server patch, either: a. Restart the DCC server. b. Go to https://:9443/dcc/web c. Click on "Load Jobs" OR a. Open the \server\conf\dcc\teamserver.properties file. b. Locate the com.ibm.rational.datacollection.initialized parameter, change its value to false, and save/close the file. For example: com.ibm.rational.datacollection.initialized=false c. Restart the DCC server. 4. LIFECYCLE QUERY ENGINE AND LINK INDEX PROVIDER INSTRUCTIONS If this is a new installation, a backup is not needed. Otherwise, be sure you have a backup before you install this interim fix. There has been no change to LQE metadata or index structure since V6.0, so there is no need to migrate your data. For details, see "Backing up and restoring Lifecycle Query Engine": http://www.ibm.com/support/knowledgecenter/SSYMRC_6.0.0/com.ibm.team.jp.lqe2.doc/topics/t_lqe_backup.html. To install the patch with Lifecycle Query Engine or Link Index Provider deployed on a WebSphere Application Server: Option 1: Using the WebSphere Application Server scripting tool (wsadmin) a. Open a command window and navigate to the WebSphere profile bin directory (e.g. //profiles//bin). b. Execute the following command, ensuring that the WebSphere Application Server is running: Windows: wsadmin -language jython -user -password -f /server/was/clm_update.py> Linux: ./wsadmin.sh -language jython -user -password -f /server/was/clm_update.py> NOTE: This will update all applications with war files from the iFixPatch directory specified Option 2: Using the WebSphere Application Server Admin Console a. Extract the lqe.war or ldx.war file to your local computer or on the Lifecycle Query Engine or Link Index Provider server. b. In the WebSphere Application Server Admin Console, stop the Lifecycle Query Engine or Link Index Provider application: Click Applications > Application Types > WebSphere enterprise applications, select the lqe_war or ldx_war check box, and click Stop. c. Update the lqe_war or ldx_war file: Select the lqe_war or ldx_war check box and click Update. d. Select "Replace the entire application," browse to the new lqe.war or ldx.war file in the location that you extracted it to, and click Next. e. Follow the Fast Path installation, and accept all of the default values. f. After the update is complete, save the configuration changes when you are prompted to. g. Start the Lifecycle Query Engine or Link Index Provider application: Select the lqe_war or ldx_war check box and click Start. To uninstall the patch with Lifecycle Query Engine or Link Index Provider deployed on a WebSphere Application Server: Option 1: Using the WebSphere Application Server scripting tool (wsadmin) a. Locate the lqe.war or ldx.war file in the original Jazz Reporting Service installation. If there are other war files in this directory, copy the war files that you want to update to a new temporary folder (the clm_update.py script updates all applications with war files in the directory specified). a. Open a command window and navigate to the WebSphere profile bin directory (e.g. //profiles//bin). b. Execute the following command, ensuring that the WebSphere Application Server is running: Windows: wsadmin -language jython -user -password -f /server/was/clm_update.py> /server/webapps> Linux: ./wsadmin.sh -language jython -user -password -f /server/was/clm_update.py> /server/webapps> Option 2: Using the WebSphere Application Server Admin Console a. Locate the lqe.war or ldx.war file in the original Lifecycle Query Engine or Link Index Provider installation. b. In the WebSphere Application Server Admin Console, stop the Lifecycle Query Engine or Link Index Provider application: Click Applications > Application Types > WebSphere enterprise applications, select the lqe_war or ldx_war check box, and click Stop. c. Update the lqe_war or ldx_war file: Select the lqe_war or ldx_war check box and click Update. d. Select "Replace the entire application," browse to the lqe.war or ldx.war file in the original installation location, and click Next. e. Follow the Fast Path installation, and accept all of the default values. f. After the update is complete, save the configuration changes when you are prompted to. g. Start the Lifecycle Query Engine or Link Index Provider application: Select the lqe_war or ldx_war check box and click Start. To install the patch with Lifecycle Query Engine or Link Index Provider deployed on WebSphere Liberty Server: a. Rename the new lqe.war or ldx.war file as lqe.war.zip or ldx.war.zip. b. Stop the WebSphere Liberty Server for the Lifecycle Query Engine or Link Index Provider. c. Back up the following file in case you need to revert the patch: \server\liberty\servers\clm\apps\lqe.war.zip or \server\liberty\servers\clm\apps\ldx.war.zip d. Delete the following files: \server\liberty\servers\clm\apps\lqe.war.zip \server\liberty\clmServerTemplate\apps\lqe.war.zip or \server\liberty\servers\clm\apps\ldx.war.zip \server\liberty\clmServerTemplate\apps\ldx.war.zip e. Delete the following directories: \server\liberty\servers\clm\apps\lqe.war \server\liberty\clmServerTemplate\apps\lqe.war or \server\liberty\servers\clm\apps\ldx.war \server\liberty\clmServerTemplate\apps\ldx.war f. Place the new lqe.war.zip or ldx.war.zip file in the following directories: \server\liberty\servers\clm\apps \server\liberty\clmServerTemplate\apps or \server\liberty\servers\clm\apps \server\liberty\clmServerTemplate\apps g. Unzip the new lqe.war.zip or ldx.war.zip file into the following directories: \server\liberty\servers\clm\apps\lqe.war \server\liberty\clmServerTemplate\apps\lqe.war or \server\liberty\servers\clm\apps\ldx.war \server\liberty\clmServerTemplate\apps\ldx.war h. Start the server. To uninstall the patch with Lifecycle Query Engine or Link Index Provider deployed on WebSphere Liberty Server: a. Stop the WebSphere Liberty Server for the Lifecycle Query Engine or Link Index Provider. b. Restore the original lqe.war.zip or ldx.war.zip file that was backed up during the installation to the following directories: \server\liberty\servers\clm\apps \server\liberty\clmServerTemplate\apps or \server\liberty\servers\clm\apps \server\liberty\clmServerTemplate\apps c. Delete the following directories: \server\liberty\servers\clm\apps\lqe.war \server\liberty\clmServerTemplate\apps\lqe.war or \server\liberty\servers\clm\apps\ldx.war \server\liberty\clmServerTemplate\apps\ldx.war d. Unzip the original rs.war.zip file into the following directories: \server\liberty\servers\clm\apps\lqe.war \server\liberty\clmServerTemplate\apps\lqe.war or \server\liberty\servers\clm\apps\ldx.war \server\liberty\clmServerTemplate\apps\ldx.war e. Start the server. To install the patch when the Lifecycle Query Engine or Link Index Provider is deployed on Apache Tomcat: a. Stop the Apache Tomcat server for the Lifecycle Query Engine or Link Index Provider application. b. Back up the following file in case you need to revert the patch: \server\tomcat\webapps\lqe.war or \server\tomcat\webapps\ldx.war c. Delete the following file: \server\tomcat\webapps\lqe.war or \server\tomcat\webapps\ldx.war d. Delete the following directories: \server\tomcat\webapps\lqe or \server\tomcat\webapps\ldx \server\tomcat\work\Catalina\\lqe or \server\tomcat\work\Catalina\\ldx e. Place the new lqe.war or ldx.war file in the \server\tomcat\webapps directory or the \server\tomcat\webapps directory, respectively. f. Start the server. To uninstall the patch with Lifecycle Query Engine or Link Index Provider deployed on an Apache Tomcat server: a. Stop the Apache Tomcat server for the Lifecycle Query Engine or Link Index Provider application. b. Restore the original lqe.war or ldx.war file that was backed up during the installation to the following directory: \server\tomcat\webapps\ or \server\tomcat\webapps\ c. Delete the following directories: \server\tomcat\webapps\lqe or \server\tomcat\webapps\ldx \server\tomcat\work\Catalina\localhost\lqe or \server\tomcat\work\Catalina\localhost\ldx d. Start the server. To verify that the patch was successfully installed: a. After the server starts, open the Lifecycle Query Engine or Link Index Provider home page. b. Verify that the build ID in the upper right matches LQE_6.0.2-I20160527-2100. After installing the patch: a. The Lifecycle Query Engine or Link Index Provider automatically detects whether it is necessary to migrate data from an existing instance. If data migration is necessary, a Start Migration button is displayed on the main Lifecycle Query Engine or Link Index Provider page: https:///lqe/web/admin or https:///ldx/web/admin. If the button is displayed, click Start Migration. b. Reindex the data sources as required. 5. RATIONAL TEAM CONCERT CLIENT FOR ECLIPSE UPDATE SITE INSTRUCTIONS To install the client update site: a. Extract the update site file to the computer where the client is installed. b. In the Rational Team Concert client, click Help > Install New Software. c. In the Install window, click Add. d. In the Add Repository window, click Local and navigate to the extracted update site file. The update site root directory contains a site.xml file. e. Select the patches to install. f. If you agree to the terms, accept the license agreement and click Install. g. After the installation is complete, restart the Rational Team Concert client. To update the feature patch, you can install the new version directly over an old patch. You do not have to uninstall the old patch. To uninstall the client update site: a. In the Rational Team Concert client, click Help > About Rational Team Concert > Installation Details. b. Select the patches to uninstall and click Uninstall. c. After the uninstall process is complete, restart the Rational Team Concert client. WARNING: -The update site does not work with Rational Team Concert Client for Eclipse 3.6 that was installed by using IBM Installation Manager. Alternatively, you can use the Rational Team Concert Client for Eclipse 3.6 .zip installation, or you can use IBM Installation Manager to install the Rational Team Concert Client for Eclipse 4.2. -If you run the uninstall process on a Rational Team Concert client that was installed by using a .zip file, the feature patch will be removed along with the original feature. Removing the patch breaks the functionality of the affected feature. For a client that was installed by using a .zip file, reinstall the features by downloading the Rational Team Concert p2 repository from Jazz.net, and use the same installation steps with the following exception. For step d, click Archive and select the p2 repository .zip file and install the Rational Team Concert feature. This step removes the patched plug-ins and replaces the missing features with the original versions of the feature from the p2 repository. -If you run the uninstall process on a Rational Team Concert client that was installed by using the p2 repository, to remove the patch, you must uninstall the entire Rational Team Concert p2 feature and then reinstall the entire Rational Team Concert feature through the p2 repository. 6. RATIONAL TEAM CONCERT CLIENT FOR MICROSOFT VISUAL STUDIO INSTRUCTIONS For details of the fixes included in this iFix refer to the bundled readme file readme-vsclient.txt. To install the Rational Team Concert Client for Microsoft Visual Studio update: a. Close all running instances of Rational Team Concert Client for Microsoft Visual Studio. b. Extract the patch .zip file to the computer where the Rational Team Concert Client for Microsoft Visual Studio client is installed. c. In IBM Installation Manger, click File > Preferences > Repositories > Add Repository and provide the path to the extracted folder from step b. d. To close the Preferences window, click OK. e. Click File > Preferences > Files for Rollback and ensure that the "Save files for rollback" check box is selected. f. In IBM Installation Manager, click Update. g. Select the IBM Rational Team Concert Client for Microsoft Visual Studio IDE package group and click Next. h. Select the Rational Team Concert version to update and click Next. i. If you agree to the terms, accept the license agreement and click Install. j. Select the versions of Microsoft Visual Studio to support and click Next. k. Click Update. l. To complete the update, click Finish. m. After the installation is complete, start the Rational Team Concert Client for Microsoft Visual Studio. To update the feature patch, you can install the new version directly over an old patch. You do not have to uninstall the old patch. To roll back to the previous client version: a. Close all running instances of Rational Team Concert Client for Microsoft Visual Studio. b. In IBM Installation Manager, click Roll Back. c. Select the IBM Rational Team Concert Client for Microsoft Visual Studio IDE package group and click Next. d. Select the patch to roll back to. e. Click Roll Back. f. Click Finish. WARNING: -The 6.0.2 patch can only be installed on top of the official 6.0.2 release. -To remove a patch, only use the Roll Back feature in IBM Installation Manager. -Uninstalling the patch completely removes the entire release, as well as any patches that are installed on top of it. 7. ADDITIONAL FIXES INSTRUCTIONS No patch non-compliant work items found. 8. APAR FIXES This interim fix contains fixes for the following APARs: [APAR ID] [Maintenance Item Summary] [Maintenance Item URL] +-- Product Data Collection Component Fixed in release 6.0.3: [APAR PI61751] [DCC should support SQL Server connection URLs that use an instanceName instead of port] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/388728] [APAR PI61751] [When link archival is enabled, deleted timesheet entries do not get soft deleted in the data warehouse] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/388230] [APAR PI61751] [DB2z JDBC Driver had been renamed from db2jcc.jar to db2jcc4.jar] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/392406] +-- Product Rational Team Concert Server Fixed in release 6.0.3: [APAR PI53450] [[Code Review] Clicking on a file does not show the content when there are merges (387017)] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/389219] [APAR PI59457] [Make build ETL tolerate item not found errors] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/391509] [APAR PI59688] [Source code gets truncated in web UI] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/391275] [APAR PI59705] [Deleted files cannot be marked as viewed (and thus the "Require Approver to Review all Files" precondition cannot be met)] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/387335] [APAR PI60018] [Dependency Build: accept should be scoped components aware] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/392815] [APAR PI60167] [Promotion error message does not indicate module itself if it is not in the right state when doing work item promotion (387484)] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/389183] [APAR PI60330] [MY STUFF shows html code only] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/392030] [APAR PI61516] [Can no longer export queries to CSV in pt_BR] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/392056] +-- Product Rational Quality Manager Fixed in release 6.0.3: [APAR PI59554] [Cannot permanently delete test case results with status in progress.] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/151421] [APAR PI59597] [Test Artifact review information (Approved dates) are modified (incorrect dates)] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/150137] [APAR PI59630] [Archiving Completed Approval Groups throws SQLException in Upgraded Server] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/150258] [APAR PI59794] [Event history is missing after migration from prior to 6.0] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/150136] [APAR PI60646] [Approval auto-transition functionality issue] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/150290] [APAR PI61255] [QM: Keyword reference is included in the Test Script XML even after deletion] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/151148] [APAR PI61751] [Error while creating a link from DM to QM project - Exception in qm.log] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/150573] +-- Product Rational Team Concert Client Fixed in release 6.0.3: [APAR PI53450] [[Code Review] Clicking on a file does not show the content when there are merges (387017)] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/389219] [APAR PI59457] [Make build ETL tolerate item not found errors] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/391509] [APAR PI59688] [[Backport to 6.0.2] Source code gets truncated in web UI] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/391275] [APAR PI59705] [Deleted files cannot be marked as viewed (and thus the "Require Approver to Review all Files" precondition cannot be met)] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/387335] [APAR PI60018] [Dependency Build: accept should be scoped components aware] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/392815] [APAR PI60167] [Promotion error message does not indicate module itself if it is not in the right state when doing work item promotion (387484)] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/389183] [APAR PI60330] [MY STUFF shows html code only] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/392030] [APAR PI61516] [Can no longer export queries to CSV in pt_BR] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/392056] +-- Product Jazz Foundation Server Fixed in release 6.0.3: [APAR PI61618] [GUI becomes blank while trying to accept a delivery from another stream. [ 6.0.2]] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/389799] [APAR PI62300] [DROP PRIMARY KEY does not drop INDEX any longer] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/391300] [APAR PI62331] [Primary keys are dropped and recreated when running repotools -onlineMigrateEstimate] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/391301] [APAR PI62336] [ResourceGoneException when running repotools-jts -updateLPASampleTemplates] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/392414] [APAR PI63097] [Expose Token License Group Counters so they can be loaded in the data warehouse] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/392480] [APAR PI61751] [Change the sequence of generate data warehouse upgrade scripts to avoid grant errors] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/392481] +-- Product Jazz Reporting Service Fixed in release 6.0.3: [APAR PI61304] [Result columns are not being processed as expected] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/392134] [APAR PI61751] [Duplicate calls to rs/report ?action=queryBuilderOutput when using report builder viewlets on RTC dashboard] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/389094] [APAR PI61751] [JRS-Watson Analytics integration doesn't work on jazz.net] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/388228] [APAR PI61751] [Preview of historical trend report shows no data for weeks, months, years setting with large amounts of data] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/389364] [APAR PI61751] [Report Builder has formatting issues when no CCM is registered (JRS running in "standalone" mode).] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/388227] [APAR PI61751] [Work Item count is too low] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/388229] [APAR PI61793] [LQE Data source is adding extra spaces in requirement types] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/389861] [APAR PI62363] [Date scale calculation lost when using Count values of a single attribute with no dimensions] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/391503] [APAR PI62454] [Test Categories are not available as attributes for Test Scripts] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/389893] [APAR PI63459] [Advanced SQL report: returns 15 results, when paging from first 10 to next 10 get no results] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/388226] [APAR PI61751] [Add a calculated column then add a regular column - adds two columns expectantly] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/390652] [APAR PI61751] [Invalid data in XLS exported report (empty columns cause shifting)] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/390692] [APAR PI61751] [SQLSyntaxErrorException error encountered when adding a Work Item custom attribute to the Format Results section when building a report] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/391378] [APAR PI61751] [Selecting a request category doesn't include the project id in the SQL] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/391266] +-- Product Rational DOORS Next Generation Fixed in release 6.0.3: [APAR PI58513] [Strikethrough styling is not applied when tags are not directly surrounding text] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/106550] [APAR PI59165] [ReqIF Exports the original folder name of a renamed folder] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/105581] [APAR PI60101] [JazzUser cannot generate customized report] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/106559] [APAR PI60425] [OSLC queries that involve manifested views are slow] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/106020] [APAR PI60920] [Reviews need to be more resilient to concurrent user interactions] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/106141] [APAR PI60978] [Revision history of a core artifact does not show baseline thumbnails] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/105999] [APAR PI61258] [Migration from 5.x to 6.x incorrectly categorizes artifact and review comment numbering data] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/106640] [APAR PI61260] [Migration from 5.x to 6.x incorrectly creates versioned review comments] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/106585] [APAR PI61345] [Discrepancies with the "Created On" and "Created By" attributes in the Overview section of the artifact's history] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/106144] [APAR PI61751] [CommentNumber Triple has been incorrectly removed] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/105429] [APAR PI61751] [Detect unmigrated module baselines before attempting migration from 5.x to 6.x] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/106205] [APAR PI61751] [For views, advanced rules for link drill-down (tree view) can become corrupted in some situations] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/105816] [APAR PI61751] [In grid view, showing links as tree view does not show the links after saving the view and coming back to it later.] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/105893] [APAR PI61751] [View Filter Logic is corrupted for some attribute types during update from 6.0.1 to 6.0.2RC1] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/105583] [APAR PI61751] [upgrade - upgrading an archived project and then restoring it causes rm/web to get stuck at 'loading'] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/106619] [APAR PI62387] [Upgrade failed with NotFoundException in addTables script] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/106434] +-- Product Jazz Foundation Client Fixed in release 6.0.3: [APAR PI61618] [GUI becomes blank while trying to accept a delivery from another stream. [ 6.0.2]] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/389799] [APAR PI62300] [DROP PRIMARY KEY does not drop INDEX any longer] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/391300] 9. CLIENT APAR FIXES This client update site contains fixes for the following defects: [APAR ID] [Maintenance Item Summary] [Maintenance Item URL] +-- RTC Client Fixes Fixed in release 6.0.3: [APAR PI53561] [scm doesn't distinguish different conflicts with files with the same path] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/387289] [APAR PI56189] [The Require-Work-Item-to-Match-Query precondition is not inherited properly by child project areas] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/391291] [APAR PI56307] [Need to improve error message when loading project with invalid name] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/388868] [APAR PI58508] [Issue with Auto-Resolve when 'children with the same name' conflict is resolved] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/391406] [APAR PI59771] [Incorrect error message when auto-merging in unloaded components] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/391298] [APAR PI61844] [Delete temporary buildmaps should not timeout after 8 minutes] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/390308] [APAR PI63032] [Local conflict results from conflicting link addition] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/392151] 10. UPDATING ORACLE OUTSIDE IN TECHNOLOGY FOR RDNG These steps need to be done only once. The Outside In files changed in iFix002. If you have already deployed these files as part of installing iFix002 or later, you do not have to do these steps again. Follow the instructions detailed in the README.txt file contained within the OutsideIn_8-5-2_Patch_CPU_April2016.zip file. 11. KNOWN ISSUES None