Interim fix CLM_602_iFix001a.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.

Note: 6.0.2 iFix001a replaces 6.0.2 iFix001 that was published on May 11. If you have previously deployed iFix001 you only need to re-deploy the Jazz Reporting Service patch file included with iFix001a.

CONTENTS OF THIS INTERIM FIX

1. This readme file: readme.txt 
2. Server patch file: CLM_server_patch_6.0.2.0-CALM602M-I20160503-2309.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. 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. ADDITIONAL FIXES INSTRUCTIONS
6. APAR FIXES 
7. CLIENT APAR FIXES
8. KNOWN ISSUES


1. SERVER PATCH INSTRUCTIONS

Note: 
-The CLM server patch file, CLM_server_patch_6.0.2.0-CALM602M-I20160503-2309.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-I20160503-2309.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_installation_directory>/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-I20160503-2309.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-<app> -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_installation_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-<app> -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. <WAS_HOME>/<AppServer>/profiles/<Profile>), 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 install>/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. <WAS_HOME>/<AppServer>/profiles/<Profile>/bin).
b. Execute the following command, ensuring that the WebSphere Application Server is running:
Windows:                                                             
  wsadmin -language jython -user <username> -password <password>           
    -f <path to clm_update.py e.g. <server_installation_directory>/server/was/clm_update.py>                       
    <path to war files to be updated e.g. C:/iFixPatch>                                                                                         
Linux:                                                           
  ./wsadmin.sh -language jython -user <username> -password <password>     
    -f <path to clm_update.py e.g. <server_installation_directory>/server/was/clm_update.py>                                                 
    <path to war files e.g. /opt/IBM/iFixPatch>

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. <WAS_HOME>/<AppServer>/profiles/<Profile>/bin).
b. Execute the following command, ensuring that the WebSphere Application Server is running:
Windows:                                                            
  wsadmin -language jython -user <username> -password <password>          
    -f <path to clm_update.py e.g. <server_installation_directory>/server/was/clm_update.py>                      
    <path to war files to be updated e.g. <server_installation_directory>/server/webapps>                                                                                        
Linux:                                                          
  ./wsadmin.sh -language jython -user <username> -password <password>    
    -f <path to clm_update.py e.g. <server_installation_directory>/server/was/clm_update.py>                                                
    <path to war files e.g. <server_installation_directory>/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:
	<JRS_installation_directory>\server\liberty\servers\clm\apps\rs.war.zip
d. Delete the following files:
	<JRS_installation_directory>\server\liberty\servers\clm\apps\rs.war.zip
	<JRS_installation_directory>\server\liberty\clmServerTemplate\apps\rs.war.zip
e. Delete the following directories:
	<JRS_installation_directory>\server\liberty\servers\clm\apps\rs.war
	<JRS_installation_directory>\server\liberty\clmServerTemplate\apps\rs.war
f. Place the new rs.war.zip file in the following directories:
	<JRS_installation_directory>\server\liberty\servers\clm\apps
	<JRS_installation_directory>\server\liberty\clmServerTemplate\apps
g. Unzip the new rs.war.zip file into the following directories:
	<JRS_installation_directory>\server\liberty\servers\clm\apps\rs.war
	<JRS_installation_directory>\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:
	<JRS_installation_directory>\server\liberty\servers\clm\apps
	<JRS_installation_directory>\server\liberty\clmServerTemplate\apps
c. Delete the following directories:
	<JRS_installation_directory>\server\liberty\servers\clm\apps\rs.war
	<JRS_installation_directory>\server\liberty\clmServerTemplate\apps\rs.war
d. Unzip the original rs.war.zip file into the following directories:
	<JRS_installation_directory>\server\liberty\servers\clm\apps\rs.war
	<JRS_installation_directory>\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:
	<JRS_installation_directory>\server\tomcat\webapps\rs.war
c. Delete the following file:
	<JRS_installation_directory>\server\tomcat\webapps\rs.war
d. Delete the following directories:
	<JRS_installation_directory>\server\tomcat\webapps\rs
	<JRS_installation_directory>\server\tomcat\work\Catalina\localhost\rs
e. Place the new rs.war file in the <JRS_installation_directory>\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:
	<JRS_installation_directory>\server\tomcat\webapps\
c. Delete the following directories:
	<JRS_installation_directory>\server\tomcat\webapps\rs
	<JRS_installation_directory>\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-I20160511-1314



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://<server name>:9443/dcc/web
c. Click on "Load Jobs"

OR

a. Open the <DCC_Install_Directory>\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. <WAS_HOME>/<AppServer>/profiles/<Profile>/bin).
b. Execute the following command, ensuring that the WebSphere Application Server is running:
Windows:                                                             
  wsadmin -language jython -user <username> -password <password>           
    -f <path to clm_update.py e.g. <server_installation_directory>/server/was/clm_update.py>                       
    <path to war files to be updated e.g. C:/iFixPatch>                                                                                         
Linux:                                                           
  ./wsadmin.sh -language jython -user <username> -password <password>     
    -f <path to clm_update.py e.g. <server_installation_directory>/server/was/clm_update.py>                                                 
    <path to war files e.g. /opt/IBM/iFixPatch>

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. <WAS_HOME>/<AppServer>/profiles/<Profile>/bin).
b. Execute the following command, ensuring that the WebSphere Application Server is running:
Windows:                                                            
  wsadmin -language jython -user <username> -password <password>          
    -f <path to clm_update.py e.g. <server_installation_directory>/server/was/clm_update.py>                      
    <path to war files to be updated e.g. <server_installation_directory>/server/webapps>                                                                                        
Linux:                                                          
  ./wsadmin.sh -language jython -user <username> -password <password>    
    -f <path to clm_update.py e.g. <server_installation_directory>/server/was/clm_update.py>                                                
    <path to war files e.g. <server_installation_directory>/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:
	<LQE_installation_directory>\server\liberty\servers\clm\apps\lqe.war.zip 
	or
	<LDX_installation_directory>\server\liberty\servers\clm\apps\ldx.war.zip
d. Delete the following files:
	<LQE_installation_directory>\server\liberty\servers\clm\apps\lqe.war.zip
	<LQE_installation_directory>\server\liberty\clmServerTemplate\apps\lqe.war.zip
	or
	<LDX_installation_directory>\server\liberty\servers\clm\apps\ldx.war.zip
	<LDX_installation_directory>\server\liberty\clmServerTemplate\apps\ldx.war.zip
e. Delete the following directories:
	<LQE_installation_directory>\server\liberty\servers\clm\apps\lqe.war
	<LQE_installation_directory>\server\liberty\clmServerTemplate\apps\lqe.war
	or
	<LDX_installation_directory>\server\liberty\servers\clm\apps\ldx.war
	<LDX_installation_directory>\server\liberty\clmServerTemplate\apps\ldx.war
f. Place the new lqe.war.zip or ldx.war.zip file in the following directories:
	<LQE_installation_directory>\server\liberty\servers\clm\apps
	<LQE_installation_directory>\server\liberty\clmServerTemplate\apps
	or
	<LDX_installation_directory>\server\liberty\servers\clm\apps
	<LDX_installation_directory>\server\liberty\clmServerTemplate\apps
g. Unzip the new lqe.war.zip or ldx.war.zip file into the following directories:
	<LQE_installation_directory>\server\liberty\servers\clm\apps\lqe.war
	<LQE_installation_directory>\server\liberty\clmServerTemplate\apps\lqe.war
	or
	<LDX_installation_directory>\server\liberty\servers\clm\apps\ldx.war
	<LDX_installation_directory>\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:
	<LQE_installation_directory>\server\liberty\servers\clm\apps
	<LQE_installation_directory>\server\liberty\clmServerTemplate\apps
	or
	<LDX_installation_directory>\server\liberty\servers\clm\apps
	<LDX_installation_directory>\server\liberty\clmServerTemplate\apps
c. Delete the following directories:
	<LQE_installation_directory>\server\liberty\servers\clm\apps\lqe.war
	<LQE_installation_directory>\server\liberty\clmServerTemplate\apps\lqe.war
	or
	<LDX_installation_directory>\server\liberty\servers\clm\apps\ldx.war
	<LDX_installation_directory>\server\liberty\clmServerTemplate\apps\ldx.war
d. Unzip the original rs.war.zip file into the following directories:
	<LQE_installation_directory>\server\liberty\servers\clm\apps\lqe.war
	<LQE_installation_directory>\server\liberty\clmServerTemplate\apps\lqe.war
	or
	<LDX_installation_directory>\server\liberty\servers\clm\apps\ldx.war
	<LDX_installation_directory>\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:
	<LQE_installation_directory>\server\tomcat\webapps\lqe.war or <LDX_installation_directory>\server\tomcat\webapps\ldx.war
c. Delete the following file:
	<LQE_installation_directory>\server\tomcat\webapps\lqe.war or <LDX_installation_directory>\server\tomcat\webapps\ldx.war
d. Delete the following directories:
	<LQE_installation_directory>\server\tomcat\webapps\lqe or <LDX_installation_directory>\server\tomcat\webapps\ldx 
	<LQE_installation_directory>\server\tomcat\work\Catalina\<host>\lqe or <LDX_installation_directory>\server\tomcat\work\Catalina\<host>\ldx 
e. Place the new lqe.war or ldx.war file in the <LQE_installation_directory>\server\tomcat\webapps directory or the <LDX_installation_directory>\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:
	<LQE_installation_directory>\server\tomcat\webapps\ or <LDX_installation_directory>\server\tomcat\webapps\
c. Delete the following directories:
	<LQE_installation_directory>\server\tomcat\webapps\lqe or <LDX_installation_directory>\server\tomcat\webapps\ldx
	<LQE_installation_directory>\server\tomcat\work\Catalina\localhost\lqe or <LDX_installation_directory>\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-I20160428-2047.

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://<server:port>/lqe/web/admin or https://<server:port>/ldx/web/admin. If the button is displayed, click Start Migration.
b. Reindex the data sources as required.



5. ADDITIONAL FIXES INSTRUCTIONS

No patch non-compliant work items found.



6. 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]

+-- 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 PI59705] [[Code Review] 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 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]

+-- Product Rational Quality Manager
Fixed in release 6.0.3:
[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 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 PI59705] [[Code Review] 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 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]

+-- Product Jazz Reporting Service
Fixed in release 6.0.3:
[APAR PI61751] [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] [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]

+-- Product Rational DOORS Next Generation
Fixed in release 6.0.3:
[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 PI61751] [CommentNumber Triple has been incorrectly removed] [https://jazz.net/jazz03/resource/itemName/com.ibm.team.workitem.WorkItem/105429]
[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]





7. CLIENT APAR FIXES
This client update site contains fixes for the following defects:
[APAR ID] [Maintenance Item Summary] [Maintenance Item URL]

+-- RTC Client Fixes



8. KNOWN ISSUES
None