Note: Before you install this server patch file, 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.

Procedure to install the server patch:

1. Stop the CLM server.


2. Verify whether the following directory exists: server_installation_directory/server/patch.
• If the directory exists, back up and remove its contents.
• If the directory does not exist, create it.


3. Copy the server patch file into the /server/patch directory.


4. Start the server.


5. Run "repotools-<app> -clean" for each application that is installed.

Note: For a distributed CLM deployment, complete the same steps on each server.
Also, the "-clean" parameter is the OSGI framework command which runs repotools with the default argument "help". The output is captured in the reptools-<app>_help.log which resides in the <JazzInstallDir>/server/ directory where reptools-<app>.bat resides.

Procedure to uninstall the server patch:

1. Stop the CLM server.


2. Back up and remove the contents of the following directory: <server_installation_directory>/server/patch


3. Start the CLM server.


4. Run "repotools-<app> -clean" for each application that is installed.

Note: For a distributed CLM deployment, complete the same steps on each server.

To clear the application cache on WebSphere Application Server:

Remove the contents from these directories under the profile root, except for the noted help directory: temp, tranlog, 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 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: work/Catalina/localhost/clmhelp.

To validate that the server patch was successfully installed or uninstalled:

1. After the server starts, open a CLM application.
2. Click Help > About the Server.
3. In the Build Information section, review the interim fix information to confirm that it is either installed (listed) or uninstalled (not listed).

Procedure to install the client update site:

1. Extract the update site file to the computer where the client is installed.


2. In the Rational Team Concert client, click Help > Install New Software.


3. In the Install window, click Add.


4. In the Add Repository window, click Local and navigate to the extracted update site file.
   Note: The update site root directory contains a site.xml file.


5. Select the patches to install.


6. If you agree to the terms, accept the license agreement and click Install.


7. After the installation is complete, restart the Rational Team Concert client.

Note: To update the feature patch, you can install the new version directly over the old patch. You do not have to uninstall the old patch.

Procedure to uninstall the client update site:

1. In the Rational Team Concert client, click Help > About Rational Team Concert > Installation Details.


2. Select the patches to uninstall and click Uninstall.


3. After the uninstall process is complete, restart the Rational Team Concert client.

WARNING:

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 will break 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 4, click Archive and select the p2 repository .zip file and install the Rational Team Concert feature. This step will remove the patched plug-ins and replace 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.

Procedure to install the Visual Studio client update:

1. Close all the running Visual Studio client(s).


2. Extract the patch zip file to the computer where the RTC Visual Studio client is installed.


3. In the IBM Installation Manger, click File > Preferences > Repositories > Add Repository and provide the path to the folder extracted in the second step.


4. Click Ok to close Preferences window.


5. Make sure that the check box File > Preferences > Files for Rollback > "Save files for rollback" is checked.


6. Now click on Update in the Installation Manager.


7. Select IBM Rational Team Concert Client for Microsoft Visual Studio IDE package group and click Next.


8. Select the RTC version that needs to be updated and click Next.


9. If you agree to the terms, accept the license agreement and click Install.


10. Select the Visual Studio version(s) and click Next.


11. Click on Update


12. Click Finish to complete update.


13. After the installation is complete, start the Rational Team Concert Visual Studio client.

To update the feature patch, you can install the new version directly over the old patch if the Visual Studio IDE version is 2010 or 2012. You do not have to uninstall the old patch.

Procedure to roll back to the previous client version:

1. Close all the running Visual Studio client(s).


2. In the IBM Installation Manager, click Roll Back.


3. Select the IBM Rational Team Concert Client for Microsoft Visual Studio IDE package group and click Next.


4. Select the patch to roll back to.


5. Click on Roll Back.


6. Click Finish.

WARNING:

The 6.0 patch can be installed only on top of 6.0 GA release.

To remove a patch, only Roll Back should be used in the Installation Manager.

Uninstalling the patch will completely remove the GA release along with the patch(s) installed on top of it.

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)

1. Open a command window and navigate to the WebSphere profile bin directory (e.g. <WAS_HOME>/<AppServer>/profiles/<Profile>/bin).
2. 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. C:/iFixPatch/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. /opt/IBM/iFixPatch/clm_update.py>
     <path to war files to be updated e.g. /iFixPatch>

NOTE: This will update all applications with war files from the iFixPatch directory specified.

Option 2: Using the WebSphere Application Server Admin Console

1. 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.
2. Update the rs_war file: Select the rs_war check box and click Update.
3. Select "Replace the entire application," browse to the new rs.war file in the location that you extracted it to, and click Next.
4. Follow the Fast Path installation, and accept all of the default values.
5. After the update is complete, save the configuration changes when you are prompted to.
6. 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)

1. 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).
2. Open a command window and navigate to the WebSphere profile bin directory (e.g. <WAS_HOME>/<AppServer>/profiles/<Profile>/bin).
3. 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. C:/iFixPatch/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. /opt/IBM/iFixPatch/clm_update.py>
     <path to war files to be updated e.g. /iFixPatch>

Option 2: Using the WebSphere Application Server Admin Console

To install the patch with Jazz Reporting Service (Report Builder) deployed on Apache Tomcat:

1. Stop the Apache Tomcat server for the Jazz Reporting Service.
2. Back up the following file in case you need to revert the patch:
   • <JRS_installation_directory>\server\tomcat\webapps\rs.war
3. Delete the following file:
   • <JRS_installation_directory>\server\tomcat\webapps\rs.war
4. Delete the following directories:
   • <JRS_installation_directory>\server\tomcat\webapps\rs
   • <JRS_installation_directory>\server\tomcat\work\Catalina\localhost\rs
5. ce the new rs.war file in the <JRS_installation_directory>\server\tomcat\webapps directory.
6. Start the server.

To uninstall the patch with Jazz Reporting Service (Report Builder) deployed on Apache Tomcat server:

1. Stop the Apache Tomcat server for the Jazz Reporting Service.
2. Restore the original rs.war file that was backed up during the installation to the following directory:
   • <JRS_installation_directory>\server\tomcat\webapps\
3. Delete the following directories:
   • <JRS_installation_directory>\server\tomcat\webapps\rs
   • <JRS_installation_directory>\server\tomcat\work\Catalina\localhost\rs
4. Start the server.

To verify that the patch was successfully installed:

1. After the server starts, open the Jazz Reporting Service home page.
2. Click the question mark icon near the upper right.
3. Select About Jazz Reporting Service.
4. Check that the build ID in the dialog box has increased.

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.

To install the patch with Lifecycle Query Engine or Link Index Provider deployed on a WebSphere Application Server:

1. Extract the lqe.war or ldx.war file to your local computer or on the Lifecycle Query Engine or Link Index Provider server.
2. 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.
3. Update the lqe_war or ldx_war file: Select the lqe_war or ldx_war check box and click Update.
4. 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.
5. Follow the Fast Path installation, and accept all of the default values.
6. After the update is complete, save the configuration changes when you are prompted to.
7. 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)

1. 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).
2. Open a command window and navigate to the WebSphere profile bin directory (e.g. <WAS_HOME>/<AppServer>/profiles/<Profile>/bin).
3. 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. C:/iFixPatch/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. /opt/IBM/iFixPatch/clm_update.py>
     <path to war files to be updated e.g. /iFixPatch>

Option 2: Using the WebSphere Application Server Admin Console

1. Locate the lqe.war or ldx.war file in the original Lifecycle Query Engine or Link Index Provider installation.
2. 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.
3. Update the lqe_war or ldx_war file: Select the lqe_war or ldx_war check box and click Update.
4. Select "Replace the entire application," browse to the lqe.war or ldx.war file in the original installation location, and click Next.
5. Follow the Fast Path installation, and accept all of the default values.
6. After the update is complete, save the configuration changes when you are prompted to.
7. 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 when the Lifecycle Query Engine or Link Index Provider is deployed on Apache Tomcat:

1. Stop the Apache Tomcat server for the Lifecycle Query Engine or Link Index Provider application.
2. 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
3. Delete the following file:
   • <LQE_installation_directory>\server\tomcat\webapps\lqe.war or <LDX_installation_directory>\server\tomcat\webapps\ldx.war
4. 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
5. 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.
6. Start the server.

To uninstall the patch with Lifecycle Query Engine or Link Index Provider deployed on an Apache Tomcat server:

1. Stop the Apache Tomcat server for the Lifecycle Query Engine or Link Index Provider application.
2. 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\
3. 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
4. Start the server.

To verify that the patch was successfully installed:

1. After the server starts, open the Lifecycle Query Engine or Link Index Provider home page.
2. Verify that the build ID in the upper right ghas increased.

After installing the patch:

1. 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.
2. Reindex the data sources as required.

Procedure to install the Data Collection Component patch:

1. Back up all the files inside the <DCC_Install_Directory>\server\conf\dcc\mapping directory.


2. Delete all the existing files from this directory.


3. Extract the contents of the com.ibm.rational.rrdi.dcc.mapping_*.zip into this directory.


4. Open the <DCC_Install_Directory>\server\conf\dcc\teamserver.properties file.


5. 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
   
   


6. Restart the DCC server.

Procedure to uninstall the Data Collection Component patch:

1. Restore the files backed up from step 1 in the installation instructions.


2. Restart the DCC server.