r7 - 2016-01-08 - 07:05:39 - IanWarkYou are here: TWiki >  Deployment Web > DeploymentPlanningAndDesign > DeploymentLicensingCLM

Licensing in the Rational solution for Collaborative Lifecycle Management (CLM)

Authors: RosaNaranjo
Build basis: Rational solution for Collaborative Lifecycle Management 2012 , CLM 4.0.x

The Rational solution for Collaborative Lifecycle Management comprises Jazz Team Server (JTS), Rational Team Concert (RTC), Rational Quality Manager (RQM), and Rational Requirements Composer (RRC).

What's New

New in Licensing for 4.0.5:

In the 4.0.5 release, the default time-out values for licenses changed:

Floating licenses: The default time-out value changed from 7200 seconds (120 minutes) to 3600 seconds (60 minutes). Token licenses: The default time-out value changed from 7200000 ms (120 minutes) to 3600000 ms (60 minutes).

In 4.0.5, the minimum time-out values for licenses are as follows:

Floating licenses: The minimum time-out value changed from 7200 seconds (120 minutes) to 3600 seconds (60 minutes). Token licenses: The minimum time-out value remains at 3600000 ms (60 minutes). This value has been the same since the 4.0.3 release.

For information about how to change the time-out values for licenses, see the documentation:

Floating licenses: See step 4 in Installing and managing floating client access license keys. Token licenses: See the note in step 4 in Setting up the Rational Common Licensing token service keys.

In the 4.0.5 release, the reset frequency for the time-out of token licenses changed. Before this release, the time-out value was reset only after the license expired. Now, most actions reset the time-out value of the license to the value of the time-out. This change makes the resetting of the time-out for token licenses the same as for floating licenses. This change causes the lmgrd.log file on the Rational License Key Server to increase in size faster than it used to, because each reset of the license causes entries to be written to the lmgrd.log file. That file is in the common directory. For example, on Windows systems, the file is typically in C:\Program Files (x86)\IBM\RationalRLKS\common\lmgrd.log.

New in Licensing for 4.0.1:

New licenses help make the Rational solution for Collaborative Lifecycle Management more affordable for smaller teams, and make it easier to license all lifecycle capabilities without having to figure out the number of licenses you need for individual products.

  • CLM Practitioner -- Offers the use of any one of the CLM products at a given time.
  • CLM Practitioner for Workgroups -- A great option for smaller teams and departments for multi-role access for team members that are responsible for multiple tasks in different departments.
  • RRC Business Analyst for Workgroups and RQM Quality Professional for Workgroups -- Complements the existing Rational Team Concert for Workgroups.

New in Licensing for CLM 2012:

  • addition of read-access to Design Management [Beta] capabilities to the following client license types: Contributor (RTC, RQM, RRC), Developer (RTC), Quality Professional (RQM), and Analyst (RRC).
  • ability to connect to multiple floating license servers due to the High Availability and Clustering feature of CLM 2012. See item 93167
  • License Compatibility with version 3.0.x applications. The version 4.0 licenses work with version 3.0.x applications but version 3.0 licenses do not work with version 4.0 applications. This compatibility allows for a topology where not all applications have to be upgraded to version 4.0 at the same time. You can upgrade JTS and one of the applications and continue to work with the other applications at the version 3.0.x level.
  • A new starter pack bundle of 10 licenses of RTC Developer for Workgroups is available. The Starter Pack provides 24x7 IBM support providing an easy upgrade when teams need more than community support for their first 10 seats. There is a limit of 1 Starter Pack (10 seats) per Jazz license server group. The Starter Pack only installs on RTC version 4.0 license servers.

What are the client license types (roles) in CLM 2012?

The definitions below have been updated to include information regarding read-access to Design Management [Beta] capabilities.

RTC

Before we get into these in details, itís important to note that starting with RTC version 3.0, a user who does not have a license assigned still has read-only access to view project work items, BIRT reports, and dashboards unless prohibited by the project administrator.

Stakeholder

The Stakeholder license is designed to support extended users such as customers, support personnel or extended community members who want to modify work items, and observe project progress. A user with an assigned Stakeholder license has read and write access to Change Management, and read access to Reports (with the ability to author BIRT reports), and Planning capabilities, unless otherwise restricted by role-based process permissions.

Contributor

The Contributor license is designed for professional team members actively participating in the project. A user with an assigned Contributor license has full read and write access to Change Management, report customization, and planning. The Contributor license also provides read access to Software Configuration Management (SCM), Automation (Build System), Requirements Management, Test Management and Design Management [Beta] capabilities unless otherwise restricted by role-based process permissions. The Contributor license capabilities are the same across the CLM products.

Developer

The Developer license is designed for professional developers actively participating in the project. A user with an assigned Developer license has full read and write access to Change Management, report customization, planning, SCM, and Automation (Build System) capabilities unless otherwise restricted by role-based process permissions. The Developer license also provides read access to Design Management [Beta] capabilities unless otherwise restricted by role-based process permissions.

Developer for IBM Enterprise Platforms

The Developer for IBM Enterprise Platforms license is designed for professional developers actively participating in the project. In addition to the capabilities provided by the Developer license, this license adds advanced building with dependency management, build impact analysis, promotion support (z/OS), deployment support (z/OS, IBM i, UNIX, and Linux) and advanced context aware search. It is designed for development teams targeting System z and Power Systems platforms.

Developer for Workgroups

The Developer for Workgroups license is similar to the Developer license except that it does not include support for distributed Software Configuration Management (i.e sharing source code changes across multiple RTC repositories), no support for High Availability/Clustering configurations and is limited to 50 authorized users per server or server group. It is designed for departmental teams and budgets. Organizations can grow beyond 50 developers by adding Developer or Developer for IBM Enterprise Platform licenses, though the distributed SCM restriction will remain for all licenses on that server or server group.

Developer for Workgroups Starter Pack

This starter pack includes a single bundle of 10 Developer for Workgroups licenses. Only one Starter Pack license (10 users) can be installed per licensed server or server group. It provides an upgrade option for customers who want to move from community support to 24x7 support. You can still add up to 50 RTC Developer for Workgroups licenses to the Starter Pack for a total of 60 users. The Starter Pack can only be installed on RTC 4.0 license servers.

RQM

Quality Professional

The Quality Professional license is designed for quality professionals actively participating in the project. A user that has been assigned a Quality Professional Client Access License has full read and write access to Change Management, report customization, planning, test management, and some Requirements Management functions. The Quality Professional license allows you to create requirements and requirement collections while using the Quality Management application, but the following operations require a RRC Analyst license: * Creating custom requirement types in the Requirements Management application * Creating and editing project and artifact templates for requirements * Creating and editing most graphical requirements artifacts such as screen flows, user interface sketches, and use case diagrams.

This license also provides read access to Software Configuration Management, Automation (Build System) and Design Management [Beta] capabilities unless otherwise restricted by role-based process permissions.

Contributor

The Contributor license is designed for professional team members actively participating in the project. A user that has been assigned a Contributor license has full read and write access to Change Management, report customization, and planning. The Contributor license also provides read access to Software Configuration Management, Automation (Build System), Requirements Management, Test Management and Design Management [Beta] capabilities unless otherwise restricted by role-based process permissions. The Contributor license capabilities are the same across the CLM products.

RRC

Analyst

The Analyst license is designed for analysts actively participating in the project. A user that has been assigned an Analyst Client Access License has read and write access to Requirements Management, Change Management, report customization and planning. This license also provides read access to Software Configuration Management, Test Management, Automation (Build System) and Design Management [Beta] capabilities unless otherwise restricted by role-based process permissions.

Contributor

The Contributor license is designed for professional team members actively participating in the project. A user that has been assigned a Contributor license has full read and write access to Change Management, report customization, and planning. The Contributor license also provides read access to Software Configuration Management, Automation (Build System), Requirements Management, Test Management and Design Management [Beta] capabilities unless otherwise restricted by role-based process permissions. The Contributor license capabilities are the same across the CLM products.

Options for purchasing CLM licenses

For information about options for purchasing CLM licenses, see CLM 2011 Licensing Guide for this information.

10 Free for RTC Developers! Rational Team Concert (only) is free for up to ten developers, starting with RTC 3.0, with community support only. The license activation kits are available for download on the Rational Team Concert 4.0 download pages. These are Authorized User Single Install only.

What additional software is licensed with CLM 2012?

Each valid client license includes a license to run one instance of DB2 Workgroup or Enterprise Edition (excludes z/OS) and one instance of WebSphere Application Server in support of CLM 2012. A valid client license for CLM 2012 includes entitlement for the following:

  • WebSphere Application Server v8.0.0.3 x86-64
  • WebSphere Application Server OEM Edition for z/OS v7.0 Fixpack 23
  • WebSphere eXtreme Scale 7.1.1.1 iFix 1
  • DB2 Enterprise Server Edition v9.7

FAQ

Is there a timeout period for floating licenses?
Yes, there is a 2 hour period of inactivity that will release a floating license. If the user logs out, the license goes back to the pool immediately.

Do the 10 free RTC Developer licenses include distributed SCM capability?
No, they do not. You must purchase additional Developer licenses to enable this functionality and disable the 10 free licenses.

Does using the Eclipse client and web client at the same time consume 2 licenses?
A single user with both an Eclipse client and web session would only use a single floating license.

For more information

Visit the version 4.0 infocenter for the following topics:

Managing Licenses
Understanding Licenses, permissions and access control
Adding and modifying roles and permissions

Conclusion

CLM 2012 includes some enhancements to the licensing feature. Like everything else that we do, we look forward to hearing feedback from you on these improvements. Have a go and let us know what you think.

Related topics: Deployment Planning and Design

Additional contributors: RolfNelson, MichaelAfshar

Questions and comments:

  • We should update the FAQ to clarify Q3 about consuming 2 licenses. We should explain that logging in from different client machines, logging in with a token license, logging in with Web/Web or Eclipse/Eclipse also only consume a single license. -- IanWark - 2016-01-08 - 02:05

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r7 < r6 < r5 < r4 < r3 | More topic actions
Deployment.DeploymentLicensingCLM moved from Deployment.DeploymentLicensingCLM2012 on 2014-02-25 - 16:04 by RosaNaranjo -
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
Ideas, requests, problems regarding the Deployment wiki? Create a new task in the RTC Deployment wiki project