Download 6.0.6 Release
June 15, 2018
Try
Buy

Collaborative Lifecycle Management

Design, test, analyze, develop, deliver ... integrated by design

Collaborative Lifecycle Management 6.0

Product Release / Trial | June 26, 2015
This is not the most recent version. We recommend Collaborative Lifecycle Management 6.0.6 . This is made available for archival purposes and may contain bugs and/or security vulnerabilities. If you do download this version, it is being provided AS IS, without warranties of any kind, including the implied warranties of merchantability and fitness for a particular purpose. We strongly advise you review the support pages for this version and update the product or take actions recommended therein. Security bulletins contain instructions for the security vulnerability addressed therein, and may require upgrading to a newer version. Link to security vulnerability blog: IBM PSIRT blog.

Rational solution for Collaborative Lifecycle Management New & Noteworthy

Collaborative Lifecycle Management 6.0 New & Noteworthy

For new and noteworthy information about the Rational solution for Collaborative Lifecycle Management (CLM), see these pages:

New in previous versions of the Rational solution for Collaborative Lifecycle Management

For details about new features and functionality in previous releases, see these pages:

New in the Rational solution for Collaborative Lifecycle Management 6.0

Global Configuration Management

The global configuration management capabilities assemble and manage configurations that span project areas across CLM applications. For details about the current release of Global Configuration Management, see the Jazz Foundation (Jazz Team Server) 6.0 New & Noteworthy information.

Configuration management information and activation

To learn how to use the latest configuration management and global configuration management capabilities, see these resources:

Jazz Reporting Service

Jazz Reporting Service contains the following applications:

  • Data Collection Component replaces the default CLM data collection tasks (Java ETLs). This application must be installed and configured to keep data in the data warehouse current.
  • Report Builder provides useful out-of-the box reports for software lifecycle management and is integrated with CLM dashboards through the widget catalog.
  • Lifecycle Query Engine indexes data from across lifecycle tools that support the tracked resource set (TRS) specification.

For details about the current release of Jazz Reporting Service, see the Jazz Reporting Service 6.0 New & Noteworthy information.

Licensing

Rational License Key Server lmgrd.log file output is different in 6.0

Changes to Rational Common Licensing Client 8.1.4.7 Interim Fix 001, which is built in to Jazz Team Server, affect the output of the Rational License Key Server lmgrd.log file for token licenses.

In releases prior to version 6.0, token licenses that were checked out of the Rational License Key Server had entries in the lmgrd.log file that looked similar to this:

16:14:52 (ibmratl) OUT: "TLSTOK" ccm_dev@CLMSERVER  [#u#ccm_dev#u##s#JAZZ(3592e8f1-8f7b-4b5d-a309-b0dfaeb09f4c)#s##p#Change and Configuration Management#p#] (8 licenses)

In version 6.0, this output changed to include not only the application that is in use, but also the client access license (CAL) role type:

16:31:41 (ibmratl) OUT: "TLSTOK" ccm_dev@clmserver2k8  [#u#ccm_dev#u##s#JAZZ(a1f6987c-487b-4ade-882d-c8c0fbe983e7)#s##p#Change and Configuration Management#p##jazzrole#Developer#jazzrole#] (8 licenses)

In both examples, the user has a Developer token license assigned, but in the 6.0 version, you can now see the Developer role in the output of the lmgrd.log file.

The following examples show the differences for a Rational Quality Manager Quality Professional license:

Output before 6.0:

10:06:12 (ibmratl) OUT: "TLSTOK" qm_pro@CLMSERVER  [#u#qm_pro#u##s#JAZZ(9acdb6af-fee8-49b7-b5c8-af39a43aa5cd)#s##p#Quality Management#p#] (10 licenses)

6.0 output:

10:03:23 (ibmratl) OUT: "TLSTOK" qm_pro@clmserver2k8  [#u#qm_pro#u##s#JAZZ(7fa25f53-db66-4c04-8691-a80fb6ffe027)#s##p#Quality Management#p##jazzrole#QualityProfessional#jazzrole#] (10 licenses)

The following examples show the differences for a Rational DOORS Next Generation Analyst license:

Output before 6.0:

10:11:32 (ibmratl) OUT: "TLSTOK" rm_analyst@CLMSERVER  [#u#rm_analyst#u##s#JAZZ(4229b4f2-a946-4d34-ab0e-0db686dd15e9)#s##p#Requirements Management#p#] (9 licenses)

6.0 output:

10:40:02 (ibmratl) OUT: "TLSTOK" rm_analyst@clmserver2k8  [#u#rm_analyst#u##s#JAZZ(4d99b5e4-a201-4ba0-9336-3edaeb1d012a)#s##p#Requirements Management#p##jazzrole#Analyst#jazzrole#] (9 licenses)

In the 6.0 output, you might see unfamiliar combinations of products and licenses because the product in the output is the application that is in use when the license is checked out. For example, you could see the following 6.0 output:

10:49:15 (ibmratl) OUT: "TLSTOK" qm_pro@clmserver2k8  [#u#qm_pro#u##s#JAZZ(ae6d6130-653e-4730-abd3-a26d16a6d0c0)#s##p#Requirements Management#p##jazzrole#QualityProfessional#jazzrole#] (10 licenses)

In this example, a user with a Quality Professional license logged in to Rational DOORS Next Generation. The combination in the output might look odd until you recognize that the product is the application in use, not the product that owns the client access license.  

The following example shows another possible combination:

11:07:35 (ibmratl) OUT: "TLSTOK" ccm_dev@clmserver2k8  [#u#ccm_dev#u##s#JAZZ(b67ba78f-0157-410f-ac68-c6b622438070)#s##p#Quality Management#p##jazzrole#Developer#jazzrole#] (8 licenses)

In this example, a user with a Rational Team Concert Developer license logged in to Rational Quality Manager to look at a test plan. The output shows the application in use is the Quality Management application and the Developer client access license is checked out.

Note: There is no change to the version of the Rational License Key Server that serves the tokens. That product is still at version 8.1.4.

CLM Server Monitoring permanent and term licenses available in 6.0

In version 6.0, permanent and term authorized user licenses are available for CLM Server Monitoring. When you generate a permanent or term authorized user license or floating license for a CLM product from the License Key Center, the license includes the CLM Server Monitoring authorized user license.

For example, when you generate any of the following authorized user licenses or floating licenses, you also receive a copy of the 10 CLM Server Monitoring authorized user licenses:

  • CLM Contributor
  • CLM Practitioner
  • CLM Stakeholder
  • RTC Contributor
  • RTC Developer
  • RTC Developer for IBM Enterprise
  • RTC Stakeholder
  • QM Quality Professional
  • QM Contributor
  • RDNG Analyst
  • RDNG Contributor

Currently CLM Server Monitoring authorized user licenses are not available if you use only token licenses, because the tool that generates token licenses cannot generate authorized user licenses as well as tokens. If you use only token licenses and want to use CLM Server Monitoring after the trial expires, contact IBM Support.

Impact to permanent licenses (for term licenses, see Impact to term licenses)

Previously, when you imported the .zip file for any of the previously stated licenses, you were prompted to provide the number of licenses that you are entitled to. Now, that does not always occur. Sometimes you are prompted; sometimes you are not. You have two options for importing and enabling the number of licenses:

  • Option 1: Import the .zip files and then edit the licenses to add the number of licenses that you are entitled to.
  • Option 2: Extract each license .zip file and then import each license individually. If you use this method, you only have to import the CLM Server Monitoring authorized user license once, even though you receive a copy of the license with each purchased license.

Option 1: Import the combined .zip file

In this option, you generate the licenses from the License Key Center and then import each downloaded .zip file.

  1. Generate all your licenses from the License Key Center.
  2. Log in to jts/admin using the administrator account.
  3. Go to Server > License Key Management.
  4. Go to the Client Access License Types section and click Add.
  5. In the license import wizard, click Browse.
  6. Navigate to the location where you downloaded the .zip files from the License Key Center, select a .zip file, and click OK.
    Note: The CLM Server Monitoring license is displayed and so is the license that you selected to import. Sometimes you can add the number of licenses in this wizard, but not always. This procedure assumes that you are not prompted for the number of licenses. Also note that CLM Server Monitoring has only 10 licenses: that number cannot be changed.
  7. Import the rest of the licenses.
    Note: Even though CLM Server Monitoring is in each of the other license .zip files, it only appears once in the list of licenses being imported during a single session of the license import wizard. If you open the wizard a second time to import other licenses, you see the CLM Server Monitoring license again, but it does not increase the number of licenses available for CLM Server Monitoring.
  8. After you import all the licenses into the wizard, click Next.
  9. If you imported floating licenses, you are prompted to enable the current Jazz Team Server to become a floating license server. Accept the prompt and click Next.
  10. You are prompted to accept the license agreement for each license that you imported. You are only prompted for the CLM Server Monitoring license agreement once. If you agree to the terms of the license agreements, accept them and click Finish.
  11. For a new installation, add the license entitlement for each license that was imported (except for CLM Server Monitoring):
    Note: If you are importing the 6.0 licenses onto a server that was upgraded from a version 5 release to 6.0, you do not have to add the entitlements or assign users, because that is done automatically as part of importing the 6.0 licenses when you upgrade floating and authorized user licenses.
    • If you imported authorized user licenses other than for CLM Server Monitoring, click the Edit button in the Client Access License section of the license management page. Enter the license entitlement for each authorized user license and click OK.
    • If you imported only floating licenses, click the Edit button in the Floating License Server section of the license management page. Enter the license entitlement for each floating license and click OK.
    After you import all the licenses and add the license entitlement, you can assign licenses to users. If you are upgrading from an earlier release, no action is required because the users that had version 5 licenses should now be listed under the 6.0 licenses. To verify that the licenses are assigned correctly, go to the Users > Client Access License Management page, select the 6.0 license and confirm that the correct users are listed.

Option 2: Extract each license .zip file and then import each license individually

  1. Generate all your licenses from the License Key Center.
  2. To separate the files, extract each file individually.
  3. Log in to jts/admin as an administrator.
  4. Go to Server > License Key Management.
  5. Go to the Client Access License Types section and click Add.
  6. In the license import wizard, click Browse and navigate to where you extracted the license files in step 2.
  7. Select a license and import it. During the import process, you are prompted for the license entitlement for each license, except for the CLM Server Monitoring client access license where the value cannot change. If you are upgrading, when you import the 6.0 licenses, the value that was set for the version 5 licenses is populated by default.
    Note: Even though you have multiple copies of the CLM Server Monitoring authorized user Client Access License .zip file, you only need to import it once. Importing it a second time does not add additional licenses to the server.
  8. Import all the licenses.
  9. If you imported any floating licenses, you are prompted to enable the current Jazz Team Server to become a floating license server. Accept the prompt and click Next.
  10. If you agree to the terms of the license agreements for all the imported licenses, accept them and click Finish.
  11. If necessary, assign the licenses to users:
    • For a new installation, go to the Users > Client Access License Management page, select a license, click Assign Client Access Licenses, and select the users to assign the license to.
    • If you are upgrading, you do not need to assign licenses because the users are automatically assigned 6.0 licenses for the licenses that they were assigned in version 5.
Impact to term licenses

Because term licenses are generated differently than permanent licenses, the import process differs. With term licenses, you are not prompted for the number of licenses because you had to provide that number when you generated the license from the License Key Center.

Import term licenses

  1. Generate all your licenses from the License Key Center.
  2. To separate the files, extract each file individually.
  3. Log in to jts/admin using the administrator account.
  4. Go to Server > License Key Management.
  5. Go to the Client Access License Types section and click Add.
  6. In the license import wizard, click Browse.
  7. Navigate to the location where you extracted the files in step 2, select a license, and import it.
    Note:
    Even though you have multiple copies of the CLM Server Monitoring authorized user Client Access License .zip file, you are only entitled to import the license once, which you can assign to 10 users.
  8. Import all the licenses.
  9. If you imported any floating licenses, you are prompted to enable the current Jazz Team Server to become a floating license server. Accept the prompt and click Next.
  10. If you agree to the terms of the license agreements for all the imported licenses, accept them and click Finish.
  11. If necessary, assign the licenses to users:
    • For a new installation, go to the Users > Client Access License Management page, select a license, click Assign Client Access Licenses, and select the users to assign the license to.
    • If you are upgrading, you must manually reassign the license from the version 5 license to the newly imported 6.0 license:
      1. From the User menu, select Client Access License Management.
      2. From the drop-down list, select the 5.0 license that you want to reassign the licenses for.
        Note: If you select a license that has no users, return to the drop-down list and select the other entry for that license. A list of users should now be displayed.
      3. Click the Reassign All link in the upper right of the page.
      4. Select the corresponding license from the list and click OK. No users should be listed.
      5. Go to the drop-down menu and select the 6.0 license. All the users that had the 5.0 license should now be listed under the 6.0 license.
      6. Go back to the Server page and select License Key Management.
      7. Find the 5.0 license that you just reassigned users from and delete it by clicking the red X.
      8. Repeat steps a-g for each license that was upgraded from 5.0 to 6.0.

Token license packaging in 6.0

Because of issues with generating both 5.0 and 6.0 token licenses from the License Key Center (the license generator would time out and no licenses were generated), version 5.0 licenses are no longer generated when you generate 6.0 token licenses. The only exception is for Rational DOORS 9.6 customers, where 5.0 and 6.0 token client access licenses (CALs) are generated for Rational DOORS Next Generation Analyst and Rational DOORS Next Generation Contributor. All other licenses are generated for version 6.0 only. For version 5.0 token licenses, contact IBM Support.