Workaround: Upgrading Rational Engineering Lifecyle Manager token licenses from 5.0 to 6.0 requires extra steps

Rational Engineering Lifecycle Manager 5.0 token licenses cannot be upgraded to version 6.0 the same way as other licenses.
Author: Peter Farrell
Last updated: 9 June 2015

Problem

Rational Engineering Lifecycle Manager 5.0 token licenses cannot be upgraded to version 6.0 the same way as other licenses. For example, you follow this procedure to upgrade Rational Engineering Lifecycle Manager floating licenses and authorized user licenses from version 5.0 to 6.0.

1. Import the 6.0 versions of the client access licenses (CALs) from the License Management page that is listed in this location: jts/admin > Server page.
2. Delete the version 5.0 licenses.
3. Go to jts/admin > Users > Client Access License Management and select the Rational Engineering Lifecycle Manager user license. All users that had 5.0 licenses are now assigned 6.0 licenses. No further action is required.

For token licenses, you must complete a procedure that involves the following steps.

Upgrading Rational Engineering Lifecycle Manager token licenses (high-level workflow):

1. Generate a list of licenses that are available in the 5.0 product.
2. Generate a list of users and their licenses.
3. Import the 6.0 token license and delete the old 5.0 licenses.
4. Generate the list of licenses again.
5. Edit the file of users and licenses to change the 5.0 token license entry to the 6.0 version.
6. Import the edited file to apply the 6.0 token licenses to all users who had 5.0 token licenses.

Workaround

To upgrade Rational Engineering Lifecycle Manager token licenses from 5.0 to 6.0, complete these steps:

1. Log in to the Jazz Team Server that is associated with Rational Engineering Lifecycle Manager. The user that you log in as must have Admin permissions to the Jazz Team Server and write permissions to the JazzTeamServer/server directory.
2. Change to the JazzTeamServer/server directory. The default location is as follows:
   • Windows: C:Program FilesIBMJazzTeamServerserver
   • Linux: /opt/IBM/JazzTeamServer/server
3. Run the following command:
   • Windows: repotools-jts.bat -listLicenses adminUserID=<Your_admin_user_ID> adminPassword=<your_admin_password>
   • Linux: repotools-jts.sh -listLicenses adminUserID=<Your_admin_user_ID> adminPassword=<your_admin_password>
4. To preserve the output from 5.0, rename the output log file from repotools-jts_listLicenses.log to repotools-jts_listLicenses_5.0.log.
5. To generate a users.csv file that has a list of users and the licenses that are assigned to them, run the following command:
   • Windows: repotools-jts.bat -exportUsers adminUserID=<Your_admin_user_ID> adminPassword=<your_admin_password>
   • Linux: repotools-jts.sh -exportUsers adminUserID=<Your_admin_user_ID> adminPassword=<your_admin_password>
6. Go to Jazz Team Server and import the Rational Engineering Lifecycle Manager 6.0 user token license.
7. Delete the Rational Engineering Lifecycle Manager 5.0 user token license. Ignore the warning about the license being assigned to users and about losing information.
8. Run the following command again:
   • Windows: repotools-jts.bat -listLicenses adminUserID=<Your_admin_user_ID>adminPassword=<your_admin_password>       
   • Linux: repotools-jts.sh -listLicenses adminUserID=<Your_admin_user_ID>adminPassword=<your_admin_password>
9. Open the repotools-jts_listLicenses.log file that was generated in step 8 and look for the Rational Engineering Lifecycle Manager user token license entry. Compare the value in this file to the value that was in the repotools-jts_listLicenses_5.0.log file.
10. In a plain text editor, open the users.csv file that was generated in step 5.
    Note: If you use an application such as IBM Lotus Symphony or Microsoft Excel to edit the file, extra characters can be added that cause the import process to fail.
11. Use the find-and-replace function to change the 5.0 license value to the new 6.0 license value. For example, the 5.0 license might look like this:

    com.ibm.team.relm.user.token.20150420_1111

    The 6.0 license might look like this:

    com.ibm.team.relm.user.token

    In this case, you replace all occurrences of com.ibm.team.relm.user.token.20150420_1111 with com.ibm.team.relm.user.token and save the file.
12. To import the users and assign the new 6.0 license, run the following command:
    
    • Windows: repotools-jts.bat -importUsers adminUserID=<Your_admin_user_ID> adminPassword=<your_admin_password>
    • Linux: repotools-jts.sh -importUsers adminUserID=<Your_admin_user_ID> adminPassword=<your_admin_password>
    Note: Importing the users does not cause any changes except for assigning the licenses. The users who had 5.0 licenses should now have 6.0 licenses assigned to them.
13. Check the repotools-jts_importUsers.log file for errors. If errors exist, resolve the issues and rerun the importUsers command.
14. Log in to jts/admin, go to the Users > Client Access License Management page, and select the Rational Engineering Lifecycle Manager token license. The users that had 5.0 licenses should now be listed under the 6.0 license.

Users now have the 6.0 token license assigned, and can proceed to work with the product.

Related information

• Work Item 353640