Many of you (our CLM and Insight clients) have requested this information and we are now pleased to announce the CLM jazz.net Information Center contains great detailed information about the Reporting Data Dictionaries data model, thanks to great collaborative efforts between our clients, support, development, and information developers! So, today we can announce that we've published the first iteration of these documentation improvements at:
Here's a quick excerpt to really whet your appetite....
And while you're at it, don't miss Seth Packham's blog post covering "More CLM 2012 beta videos: Clustering, installation, scriptable setup, express setup, process editing and more" on the Jazz.net blog!
Sumant Renukarya 270002B42N Visits (560)
One of the queries that I received, while working on IBM Rational Team Concert (RTC) is this:
2. Change the LDAP host in Websphere Application Server (WAS).
AcdntlPoet 2700019V2G Visits (740)
The Rational User Educ
CLM 2012 Deployment Guide: http
AcdntlPoet 2700019V2G Visits (1270)
Change the public URL for Rational Collaborative Lifecycle Management server V4.0.1- This is a demonstration of changing the public URL for a Jazz Team Server in IBM Rational Collaborative Lifecycle Management V4.0.1. This activity affects IBM Rational Team Concert, IBM Rational Quality Manager, and IBM Rational Requirements Composer.
KiranChikkanna 270005HX17 Visits (1994)
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: