Rational Solution for Collaborative LifeCycle Management 2012(CLM 2012) was released in June 2012.
In this post, I have tried to capture the changes in CLM 2012 from a licensing perspective. I have outlined the licensing requirements for the clustering requirements and covered the implementation changes in the Jazz token licensing for CLM 2012. Also, there is a small section answering the most frequent questions asked in the context of deployment of CLM 2012 licenses under “FAQ section”. So watch out for those tips!
Ok, lets get started now. To begin with let me broadly list the changes which have been brought in CLM 2012 from the licensing perspective.
What's 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 & Clustering feature of CLM 2012.
License Compatibility with 3.0.x applications. The 4.0 licenses work with 3.0.x applications but 3.0 licenses do not work with 4.0 applications.
This compatibility allows for a topology where not all applications have to be upgraded to v4.0 at the same time. You can upgrade JTS and one of the applications and continue to work with the other applications at the 3.0.x level.
A new starter pack bundle of 10 licenses of RTC Developer for Work groups 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 4.0 license servers.
Licensing in High availability/Clustering for Rational's Collaborative Life cycle Management products
There are 2 types of HA/Clustering available with CLM 4.0:
CLM High Availability / Clustering on WAS
WAS based High Availability
Prerequisite: Will require licensed WAS-ND (which will not be bundled with CLM v4, which is not provided by Rational License Team). Requires Freely available key file from support to activate capability.
Server rename is only for a limited set of scenarios. It requires careful planning, and should generally be used only as a last resort when other approaches are unworkable. You should review the supported scenarios at Supported scenarios to understand if server rename will work for your deployment.
Prerequisite: Requires a freely available key file from support to activate capability
Both the setups do not require extra CAL ( Client Access Licenses ) for the applications hosted on the JTS, Since there will be only one repository. Both the setups do not require the extra server licenses as well ( JTS ). They need the WAS and freely available key file from support to activate capability, which is not a license file and customers need to contact the product support in order to obtain the same.
Design Management Licensing
Design Management is a collaborative web-based tool that enables a broad set of stakeholders to contribute to and influence the design of products, software, and systems. Rational Software Architect Design Manager ([Beta] and Rational Rhapsody Design Manager [Beta] use the Design Management (DM) application, which includes the Design Management capability.
Important: The integration with Design Management is considered beta functionality and is for evaluation purposes only.
There are no extra licenses available as of now for the Design Management tools. As of now the following client license types: Contributor (RTC, RQM, RRC), Developer (RTC), Quality Professional (RQM), and Analyst (RRC) have been provided with only the Read-access capabilities to Design Management [Beta]
There are no trial extensions for the licenses of Design Management tools as of now.
License Compatibility with 3.0.x applications/Support rolling upgrade capability (N-1) for CLM
The 4.0 licenses work with 3.0.x applications but 3.0 licenses do not work with 4.0 applications. This compatibility allows for a topology where not all applications have to be upgraded to v4.0 at the same time.
You can upgrade JTS and one of the applications and continue to work with the other applications at the 3.0.x level. You can upgrade Jazz Team Server and support both RTC 3.0.1 and RTC 3.Next clients. You can upgrade one CLM application at a time (rather than having to do all at once). Allows RTC, RQM, RRC to upgrade incrementally. 4.0 CALs would require the JTS version to be at 4.0. However 3.0 CALs can be imported into JTS 4.0 without any problem.
When Jazz Tokens are used as licenses instead of CAL's and when the version of CLM is upgraded to 4.0, we have incompatibility issues with the Jazz Tokens.
In order to resolve the reported error apply the steps below: