Setting up WebSphere Application Server for the version 3 upgrade

This section describes the steps to uninstall your previous web applications and redeploy the new versions when upgrading to version 3 of the Jazz products.

About this task

When setting up WebSphere® for version 3, you must deploy the web applications for the Jazz™ Team Server, for Lifecycle Project Administration, for the version 3 Information Center, and for each application that you have installed. This process is described in Deploying CLM applications on WebSphere Application Server.

If you are upgrading both IBM® Rational® Team Concert and IBM Rational Quality Manager from version 2, you must deploy each to a context root of /jazz, and, as a result to a separate WebSphere instance. For further details about the upgrade process, see Understanding the deployment and upgrade process. For further details about setting up WebSphere Application Server, see Setting up a WebSphere Application Server.

If you created a security certificate for use with the previous release, copy the certificate from the previous release or create a new one. See Configuring security certificates for details.

Procedure

  1. Ensure that you have one of the supported WebSphere Application Sever versions installed: 7.0.0.15+ or 6.1.0.27+.
  2. Login to WebSphere administrative console.
  3. Stop and uninstall the version 2 jazz.war and help.war applications for either Rational Team Concert or Rational Quality Manager, and converter.war and rrc-help.war for Rational Requirements Composer.
  4. Modify the custom properties. For detailed information, see Setting up a WebSphere Application Server.
    1. Modify the JAZZ_HOME property to match the new installation path (<JazzInstallDir>/server/conf) for the Jazz Team Server.
      Note: In a distributed environment, the JAZZ_HOME property of each WebSphere Application Server instance must be updated to point to the configuration directory of the installed application. (<applicationInstalldir>/server/conf).
    2. Modify the Oracle or SQL Server JDBC driver property if needed.
    3. Add the log4j.configuration property with the value set to file:///<3.0.1InstallDir>/server/conf/startup_log4j.properties.

      The settings contained in startup_log4j.properties are used at the early stages in the startup process to pass messages to the WebSphere Application Server SystemOut.log file. After the early stages, each Jazz application will switch to using the application-specific settings from 3.0.1InstallDir/server/conf/<app context>/log4j.properties.

      Note: This property already exists if you are upgrading from Rational Team Concert version 3. Modify the path to match your new installation.
    4. (Optional) Adjust the memory settings, if needed.
  5. Verify that the Generic JVM Arguments do not contain old paths from previous versions of Rational Quality Manager. 
    1. Navigate to the following page in your WAS Admin Console:

      Application servers > myServer > Java and Process Management > Process definition > Java Virtual Machine

    2. Check the text in the Generic JVM Arguments field to see if any old Rational Quality Manager paths are included.

      If there are none, you can continue to Step 6.

    3. If you see arguments with old Rational Quality Manager paths, remove those arguments from the field. Be sure to save the old arguments in a text file as a backup. 
  6. Stop the WebSphere Application Server.
  7. Delete temporary files.

    When uninstalling and reinstalling applications, there may be temporary files and directories that need to be removed. To clean the temporary files, follow these steps:

    1. Go to <WASInstallDir>/profiles/AppSrv01/temp/<machine name>/server1 and delete the <application>_war directory.
    2. Go to <WASInstallDir>/profiles/AppSrv01/temp/wscache and delete the <application>_war directory.
  8. Deploy the 3.0.1 WAR files and map security roles to user or group. As mentioned above, there are multiple WAR files to deploy. For details, see Deploying CLM applications on WebSphere Application Server.
  9. Start the 3.0.1 applications by marking the check box of all deployed war files and clicking Start.

Feedback