Interim fix CLM_603_iFix002.zip This interim fix is only valid for the Rational solution for Collaborative Lifecycle Management (CLM) 6.0.3 release. The Rational solution for CLM 6.0.4 is the next release that will include all these fixes. If you plan to upgrade, upgrade to version 6.0.4 or later. CONTENTS OF THIS INTERIM FIX 1. This readme file: readme.txt 2. Server patch file: CLM_server_patch_6.0.3.0-CALM603M-I20170131-0057.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. Data Collection Component patch file: com.ibm.rational.datacollection.wrapper_1.0.0.v20160805_1809.jar (see the DATA COLLECTION COMPONENT INSTRUCTIONS section) 5. Lifecycle Query Engine patch file: lqe.war (see the LIFECYCLE QUERY ENGINE AND LINK INDEX PROVIDER INSTRUCTIONS section) 6. Link Index Provider patch file: ldx.war (see the LIFECYCLE QUERY ENGINE AND LINK INDEX PROVIDER INSTRUCTIONS section) 7. Rational Team Concert Client for Eclipse update site: UpdateSiteFor_6.0.3.0-CALM603M-I20170131-0057.zip (see the RATIONAL TEAM CONCERT CLIENT FOR ECLIPSE UPDATE SITE INSTRUCTIONS section) 8. Rational Team Concert Client for Microsoft Visual Studio readme file: readme-vsclient.txt 9. Rational Team Concert Client for Microsoft Visual Studio patch file: rtc_vsclient_I6.0.3_iFix002.zip (see the RATIONAL TEAM CONCERT CLIENT FOR MICROSOFT VISUAL STUDIO INSTRUCTIONS section) 10. Oracle Outside In Technology fix: DNG603_OutsideIn_8-5-3_Patch_CPU_January2017.zip (see the UPDATING ORACLE OUTSIDE IN TECHNOLOGY FOR RDNG section) 11. 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/blogs/psirt/ 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.3.0-CALM603M-I20170131-0057.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.3.0-CALM603M-I20170131-0057.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.3.0-CALM603M-I20170131-0057.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 and class 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. For UNIX platforms, run the following script: /bin/clearClassCache.sh For Windows platforms, run the following script: \bin\clearClassCache.bat 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.3-I20170127-1022 3. DATA COLLECTION COMPONENT INSTRUCTIONS Note: The wrapping jar file last changed in iFix001. If you have already deployed this file as part of installing iFix001 or later, you do not have to do these steps again. Installing the wrapping jar file allows DCC ETL jobs to be scheduled from the Insight server. However, It should be noted that installing this on AIX is not supported because Insight does not support AIX. To install the wrapping jar patch with Data Collection Component: 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. Back up com.ibm.rational.datacollection.wrapper_*.jar inside \server\conf\dcc\wrapper\lib directory. d. Delete the existing com.ibm.rational.datacollection.wrapper_*.jar file from this directory. e. Paste the new DCC wrapper jar into this directory. f. 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.3-I20170126-0819. 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.3 patch can only be installed on top of the official 6.0.3 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 +-- Product Rational Team Concert Server Fixed in release 6.0.4: [APAR PI61751] [Backport SCM debug tracing to 6.0.3] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/408258] This defect requires additional steps to apply: The patch effects all rich clients. While the Eclipse client supports patching, the CLI and VS client, which is also used by the customer, is shipped differently. ---- +-- Product Rational Team Concert Client Fixed in release 6.0.4: [APAR PI61751] [Backport SCM debug tracing to 6.0.3] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/408258] This defect requires additional steps to apply: The patch effects all rich clients. While the Eclipse client supports patching, the CLI and VS client, which is also used by the customer, is shipped differently. ---- +-- Product Rational Team Concert Common Fixed in release 6.0.4: [APAR PI61751] [Backport SCM debug tracing to 6.0.3] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/408258] This defect requires additional steps to apply: The patch effects all rich clients. While the Eclipse client supports patching, the CLI and VS client, which is also used by the customer, is shipped differently. ---- 8. APAR FIXES This interim fix contains fixes for the following APARs: [APAR ID] [Maintenance Item Summary] [Maintenance Item URL] +-- Product Rational Engineering Lifecycle Manager Fixed in release 6.0.4: [APAR PI73388] [JAWS fails to read error messages for show link wizard and Artifact panel] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/407223] [APAR PI73388] [Switching configurations will loose unsaved changes] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/407220] [APAR PI73388] [Test case is getting displayed in the incorrect global configuration] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/407209] [APAR PI73388] [User's views not showing up after conversion to case insensitive user ids] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/407224] [APAR PI73388] [When I enabled Global Configuration Management, Component is no longer shown in the palette] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/407221] +-- Product Data Collection Component Fixed in release 6.0.4: [APAR PI71853] ["_94.load is not a function" when attempting to save schedule] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/405278] [APAR PI72867] [Requirement type name in the dimension file has the wrong format] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/407045] +-- Product Rational Team Concert Server Fixed in release 6.0.4: [APAR PI61751] [zOS.integration failing during computing change impacts] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406233] [APAR PI68102] [[6.0.3] Fetch Outplaced Children On Demand makes top entry's progress information incorrect until expanded.] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/408869] [APAR PI69263] [[6.0.3 iFix] Plan view filter fails to work on plan views with work items which have an empty summary field] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406203] [APAR PI70489] [Work items in a plan cannot be sorted by a custom attribute of type iteration] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406965] [APAR PI70846] [[603] Plan elements only show "Related" links for one endpoint] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406200] [APAR PI70973] [Handle build definition deletion during buildmap maintenance] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/405030] [APAR PI71059] [Cleanup duplicate build maps] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/405022] [APAR PI71915] [successfully built files in previous failed build are flagged for rebuild when do not compute flag is set] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/405846] [APAR PI72024] [Previews of image attachments have problems (web UI)] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/407061] +-- Product Lifecycle Query Engine Fixed in release 6.0.2: [APAR PI73388] [LQE skipped resource retrying may significantly slow indexing times] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/408339] Fixed in release 6.0.4: [APAR PI75116] [Add http://jazz.net/ns/lqe#Vocabulary triple to vocabularies updated via upgradeHandlers] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/409927] [APAR PI73388] [Customize the blocksize to retrieve the selection/selects data from a relational database (particularly for Oracle 11)] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/410197] +-- Product Rational Quality Manager Fixed in release 6.0.4: [APAR PI73388] [Missing execution records in LQE after reindexing trs2 feed] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/158183] [APAR PI73388] [Purging an ExecutionResult removes the ExecutionElementResults (steps) from being referenced but does not delete them] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/158365] [APAR PI73731] [Requirement Validity requests do not consider different application URLs such as /rm, /dm] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/159155] [APAR PI74023] [Multiple (Duplicate) validate by links are generated after enabling Global Configuration] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/159709] [APAR PI74556] [Upgrade to Liberty 16.0.0.3 results in numerous print related errors in QM] [https://jazz.net/jazz02/resource/itemName/com.ibm.team.workitem.WorkItem/159446] +-- Product Rational Team Concert Client Fixed in release 6.0.4: [APAR PI61751] [zOS.integration failing during computing change impacts] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406233] [APAR PI68102] [Fetch Outplaced Children On Demand makes top entry's progress information incorrect until expanded.] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/408869] [APAR PI69263] [Plan view filter fails to work on plan views with work items which have an empty summary field] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406203] [APAR PI70489] [Work items in a plan cannot be sorted by a custom attribute of type iteration] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406965] [APAR PI70846] [Plan elements only show "Related" links for one endpoint] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406200] [APAR PI70973] [Handle build definition deletion during buildmap maintenance] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/405030] [APAR PI71059] [Cleanup duplicate build maps] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/405022] [APAR PI71915] [successfully built files in previous failed build are flagged for rebuild when do not compute flag is set] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/405846] [APAR PI72024] [Previews of image attachments have problems (web UI)] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/407061] +-- Product Jazz Foundation Server Fixed in release 6.0.4: [APAR PI73388] [Error messages in jts logs after JTS setup.] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/407140] [APAR PI73388] [Filters do not work in configuration picker] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406787] [APAR PI73388] [Oracle Data Warehouse Upgrade generates bad scripts] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406737] [APAR PI73388] [repotools repair command for "multi currents" (repairMultipleVersionsMarkedAsCurrent) fails on Oracle] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406799] +-- Product Rational Team Concert Common Fixed in release 6.0.4: [APAR PI61751] [zOS.integration failing during computing change impacts] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406233] [APAR PI68102] [Fetch Outplaced Children On Demand makes top entry's progress information incorrect until expanded.] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/408869] [APAR PI69263] [Plan view filter fails to work on plan views with work items which have an empty summary field] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406203] [APAR PI70489] [Work items in a plan cannot be sorted by a custom attribute of type iteration] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406965] [APAR PI70846] [Plan elements only show "Related" links for one endpoint] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406200] [APAR PI70973] [Handle build definition deletion during buildmap maintenance] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/405030] [APAR PI71059] [Cleanup duplicate build maps] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/405022] [APAR PI71915] [successfully built files in previous failed build are flagged for rebuild when do not compute flag is set] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/405846] [APAR PI72024] [Previews of image attachments have problems (web UI)] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/407061] +-- Product Jazz Reporting Service Fixed in release 6.0.4: [APAR PI71685] [MS SQL server does not support the DOUBLE data type] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/407226] [APAR PI71877] [CQPAR00198729: Missing traceability links for Requirements] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406338] [APAR PI72605] [SQL generator does not respect Oracle 30 character limit on column name alias] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406722] [APAR PI73254] [Report Builder is ignoring the issoftdeleted flag for the RM link types] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406938] [APAR PI73388] [Connect to Data sources creates invalid LQE data source] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/404839] [APAR PI73388] [Duplicated reports cannot have their graph configured] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/405043] [APAR PI73388] [Report results parsing can cause Report Builder to hang] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/408802] +-- Product Rational DOORS Next Generation Fixed in release 6.0.4: [APAR PI70712] [Default ootb graphic artifact document style reports are not available] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111223] [APAR PI71470] [Incorrect link type when creating DM links] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111785] [APAR PI71971] [Deleting a large module causes CPU to spike and OOME] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111780] [APAR PI72519] [Addition/Removal of existing artifacts to/from modules becomes slow after adding/removing a lot of artifacts] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111848] [APAR PI72586] [Investigate poor performing SPARQL query from module analyzer] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111256] [APAR PI72777] [View cannot be switched/unselected if you change views in bad timing] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111430] [APAR PI73248] [Unable to open Stream editor from Manage Configurations page using IE] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111923] [APAR PI73388] [Address reporting performance issues in 6.0.3] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111616] [APAR PI73388] [Can't import types from another component] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111215] [APAR PI73388] [Changing view while filter settings are open, destroys the UI] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111216] [APAR PI73388] [Debug Service RM Response Format is unusable] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/112138] [APAR PI73388] [Enabling ISR Debug breaks Artifact operations] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111339] [APAR PI73388] [Excessive memory usage in the Module Analysis tool] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/112140] [APAR PI73388] [Imported type system not reportable in JRS] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111230] [APAR PI73388] [Inadequate TRS performance under load (high CPU usage and memory consumption, high latency of the feed, potentially out of sync with repository)] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111907] [APAR PI73388] [LQE-based JRS Report not showing data after RM refactoring across projects] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/110953] [APAR PI73388] [Module Analysis does not properly scope initial module binding query to project and configuration] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111795] [APAR PI73388] [Module Merge - Structural module changes are all dependent so user must always deliver the first changes] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111308] [APAR PI73388] [Module analyzer should branch versions when appropraite] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111214] [APAR PI73388] [ReqIf import should handle workflow data cleanly] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111228] [APAR PI73388] [Requirements picker keeps on prompting for login, even after successful login in Visual Studio Client] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111225] [APAR PI73388] [The Link Constraint Add Rule dialog is showing incorrect target artifact data] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111221] [APAR PI73388] [dashboard - requirements view dashboard widget does not apply the specified view] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111535] [APAR PI73388] [refactor - module 'created by' date unexpected when refactored to a new component] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111222] [APAR PI73424] [Improve performance for large baseline compare query] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111932] [APAR PI73885] [When exporting a module to CSV or XLSX, the links appear as NULL if they point to an artifact inside another module and that artifact does not exist in the default stream] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/111779] [APAR PI74931] [OSLC Service might leave invalid vvc mapping when updating module artifacts] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/112070] +-- Product Jazz Foundation Client Fixed in release 6.0.4: [APAR PI73388] [Error messages in jts logs after JTS setup.] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/407140] [APAR PI73388] [Filters do not work in configuration picker] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406787] [APAR PI73388] [Oracle Data Warehouse Upgrade generates bad scripts] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406737] [APAR PI73388] [repotools repair command for "multi currents" (repairMultipleVersionsMarkedAsCurrent) fails on Oracle] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/406799] 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.4: [APAR PI69593] [Manual Proxy settings are getting used instead of Native Proxy settings in Eclipse client 6.x] [https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/405631] 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 DNG603_OutsideIn_8-5-3_Patch_CPU_January2017.zip file. 11. KNOWN ISSUES None