KiranChikkanna 270005HX17 Visits (2965)
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:
Licensing in High avai
There are 2 types of HA/Clustering available with CLM 4.0:
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]
License Compatibility with 3.0.x appl
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:
AcdntlPoet 2700019V2G Visits (1498)
Did you hear? Fariz Saracevic, Lifecycle Scenario Architect, announced on his blog Tuesday that the ALM Community is launching an Office Hours program. these office hours are intended to help connect you, our clients, with the right Subject Matter Experts (SMEs) to help answer questions, provide feedback, or even learn about deeper ALM related topics. Check out his blog here for more details, or just use the information below to join the ALM community and begin working directly with your peers and the ALM SMEs! To get notified about ALM Community Office Hours, become an ALM community member, and/or pass this information to your peers:. If you have IBM developerWorks ID, click "Join this Group" button from ALM community home page. If you do not have IBM developerWorks ID, register with IBM developerWorks/join ALM community with easy three steps: 1. Go to the IBM developerWorks registration page 2. Complete registration form and , click on the 3. Go to the ALM community home page and click "Join this Group" button.
Check out his blog here for more details, or just use the information below to join the ALM community and begin working directly with your peers and the ALM SMEs!
To get notified about ALM Community Office Hours, become an ALM community member, and/or pass this information to your peers:.
If you have IBM developerWorks ID, click "Join this Group" button from ALM community home page. If you do not have IBM developerWorks ID, register with IBM developerWorks/join ALM community with easy three steps: 1. Go to the IBM developerWorks registration page 2. Complete registration form and , click on the 3. Go to the ALM community home page and click "Join this Group" button.
If you do not have IBM developerWorks ID, register with IBM developerWorks/join ALM community with easy three steps:
1. Go to the IBM developerWorks registration page
2. Complete registration form and , click on the
3. Go to the ALM community home page and click "Join this Group" button.
AcdntlPoet 2700019V2G Visits (1964)
Beginning September 24, 2012, you can now search, subscribe to and track the progress of Rational Focal Point, Rational Rhapsody, Rational DOORS, and DOORS Web Access defects using the open APAR records published to the web. This is all part of the roll out for publishing of Open APARs to the Web for the products noted: As a client, you will be able to see Open APAR content published to the Web (if you are entitled to use the product -- see below) References for even more information:
As a client, you will be able to see Open APAR content published to the Web (if you are entitled to use the product -- see below)
References for even more information:
AcdntlPoet 2700019V2G Visits (1508)
The numbers are in for the top reused content in August! This list is based on data showing the top content reused by our Support Engineers to help solve PMRs over the month of August. We're sure you'll find some great information to either help solve issues you're currently struggling with, or even avoid them altogether!
Have you found a technote that helped you solve an issue without having to open a PMR? Let us know by rating and leaving feedback on that content using the "Rate this page" stars on the top right of the content or the box of the same name at the bottom of each technote! Your feedback is highly valuable to us as we work to improve the quality of solutions and help you sole issues more effectively and efficiently.
Jazz team server has a detailed reporting mechanism for the floating license usage and these reports can be very helpful in managing the available floating licenses effectively. The reports give a picture of license consumption in a given time frame. This not only helps you to manage your licenses but also provides a big picture about your license requirements for a project.
There are two ways to collect data about the license usage on a license server:
* Historic usage snapshots - Data that tracks how many of each CAL were used concurrently over time.
* Full license usage log - Exactly which users used which CALs and for how long.
Historic usage snapshots
By default, the license server will collect basic license usage data and store the data as historic snapshots. The data collected is only how many of each Client Access License, CAL were used, and by which server. That data is used to generate the graphs provided by the admin web UI.
You can see the admin web UI graphs by going to this URL, http
Load the admin web UI of the license server, usually http
Three ways of monitoring the license usage on the web UI:
1. Click the server tab and in the licensing pane, Click reports.
2. On the floating license usage page, select a license type from the menu.
3. Optional : Enter values in the start date and end date fields.
4. Click on the "Reports" link in the "Floating License Usage" section of the left navigation area.
The page to obtain the floating license usage looks like this:
In below given scenario:
We are running the reports for the IBM Rational Quality Manager – Quality Professional – Token licenses from September 1st to September 10th.
Further the details about the license denial's if any also would be present in the logs.
In below provided image, It is clear that the consumption of the tokens is high from 09/09/2012 to 09/12/2012.
You can also get access to the raw data through the generic reporting UI by doing the following:
View the report UI in the web by going to http
Full license usage log
To use the full license log, you must first enable it through the admin web UI. You can do it through the following steps:
After the license log has been enabled a file will be generated for each license action that happens on the server. Here is an extract of a sample log:
The meaning of each column is: