Migrating the adapter to an upgrade installation of CLM

When you upgrade Rational® solution for Collaborative Lifecycle Management, you must migrate the Git adapter to the new location of the Jazz™ Team Server.

Before you begin

Upgrade CLM, see Upgrading the Rational solution for CLM.

About this task

You must migrate the Git adapter to the location where you installed the upgraded Jazz Team Server. The steps are different if JTS runs on Apache Tomcat or a WebSphere® Application Server.

Procedure

  1. Back up the Git adapter database.
  2. Install the Git adapter to the location where you installed the Jazz Team Server when you upgraded CLM. For example, if you upgraded to CLM 4.0.3 and the previous installation location was /opt/IBM/JazzTeamServer, then /opt/IBM/JazzTeamServer403 is the new location.

    For the steps to install the Git adapter, see Installing from IBM Installation Manager.

Migrate the Git adapter to the upgrade installation of CLM where JTS runs on a WebSphere Application Server. Skip to the next section if your Jazz Team Server runs on Apache Tomcat.

  1. Uninstall the adapter web application by using the console:
    1. Open the Admin console.
    2. Click Applications > Application Types > WebSphere enterprise applications.
    3. Select the check box next to gitAdapter; click Uninstall.
    4. Verify that the gitAdapter_war application was uninstalled correctly and click Save directly to the master configuration.
  2. Replace the teamserver.properties file.
    1. Go to the originalJazzInstallDir/server/conf/gitAdapter directory where you installed the previous version of the Git adapter.
    2. Copy the teamserver.properties file to the newJazzInstallDir/server/conf/gitAdapter directory where you installed the latest version of the Git adapter.
  3. Check how the indices folder is referenced in the teamserver.properties file. Look for the com.ibm.team.jfs.index.root.directory, which is the key in the teamserver.properties file for the location of the index. Choose one of the following approaches:
    • If the indices folder is specified with an absolute path and is in a location that can persist after you complete your Git adapter migration to the new location, back up your indices folder. Make sure that the indices folder is stable and cannot be deleted if an application is uninstalled.
    • If your indices folder is referenced with a relative path and is in the location where you installed the previous version of the Git adapter, replace the indices folder in the location where you installed the latest version of the Git adapter. For example, replace the indices folder in newJazzInstallDir/server/conf/gitAdapter, with the indices folder from the location where you installed the previous version of the Git adapter.
  4. Merge any customization changes that you made to the log4j.properties file from the location where you installed the previous version of the Git adapter with the log4j.properties file in the location where you installed the latest version of the Git adapter.
  5. Install and start the adapter web application.
    1. Click Applications > New application > New Enterprise Application.
    2. Under Full path, enter the path to the gitAdapter.war web application file.

      Choose the newJazzInstallDir/server/webapps/gitAdapter.war directory for the upgrade installation of CLM.

    3. Click Next then select Fast Path - Prompt only when additional information is required.
    4. Click Next to accept the default options until you reach the Map context roots for web modules page.
    5. In the Map context roots for web modules, set Context root to /gitAdapter and click Next.
    6. Click Finish.
    7. Verify that the gitAdapter_war application was installed correctly and click Save directly to the master configuration. The Preparing for the application installation page opens again. Click Applications > Application Types > WebSphere enterprise applications to see your application in the list of installed applications.
    8. Select the check box next to gitAdapter_war; click Start. A green arrow indicates that the application started.

Migrate the Git adapter to the upgrade installation of CLM where JTS runs on Apache Tomcat. Skip to the next section if the JTS does not run on Apache Tomcat.

  1. Stop the Apache Tomcat application server.
  2. If you are using the included Derby database, go to the JTS directory of the upgrade installation of CLM where you installed the latest version of the Git adapter and delete the Derby repositoryDB directory.

    newJazzInstallDir\server\conf\jts\derby\repositoryDB

  3. If you are using the included Derby database, go to the directory where you installed the previous version of the Git adapter and copy the Derby database to the same JTS directory of the upgrade installation of CLM.

    newJazzInstallDir\server\conf\jts\derby\repositoryDB

  4. Replace the teamserver.properties file.
    1. Go to the originalJazzInstallDir/server/conf/gitAdapter directory where you installed the previous version of the Git adapter.
    2. Copy the teamserver.properties file to the newJazzInstallDir/server/conf/gitAdapter directory where you installed the latest version of the Git adapter.
  5. Check how the indices folder is referenced in the teamserver.properties file. Choose one of the following approaches:
    • If the indices folder is specified with an absolute path, for example, com.ibm.team.jfs.index.root.directory and is in a location that can persist after you complete your Git adapter migration to the new location, back up your indices folder. Make sure that the indices folder is stable and cannot be deleted if an application is uninstalled.
    • If your indices folder is referenced with a relative path and is in the location where you installed the previous version of the Git adapter, replace the indices folder in the location where you installed the latest version of the Git adapter. For example, replace the indices folder in newJazzInstallDir/server/conf/gitAdapter, with the indices folder from the location where you installed the previous version of the Git adapter.
  6. Merge any customization changes that you made to the log4j.properties file from the location where you installed the previous version of the Git adapter with the log4j.properties file in the location where you installed the latest version of the Git adapter.
  7. Start the Apache Tomcat application server.

Start the Git adapter.

  1. Point your browser to https://fully qualified hostname:port/gitAdapter. Log in to the adapter server. Verify that the Git adapter administration page opens.

Results

The Git adapter is migrated to the location where you installed the Jazz Team Server when you upgraded CLM.

What to do next

Continue to use the adapter, see Using the Git adapter.

Feedback