Jazz Jazz Community Blog Countdown to Rational Team Concert 3.0: Part III – Packaging and Licensing

Today we are announcing that Rational Team Concert 3.0 will be generally available on November 23, 2010. Visit the Rational Team Concert project page to learn more and get the highlights of what’s new!

In addition to the enhancements in the main product functions, there have been significant changes to the licensing and deployment models based on both feedback and lessons learned as the family of Jazz products expands.*

Platforms

We’ve simplified the packaging and platform support so that in 3.0 there is only one product that supports all our platforms. Instead of the model in 2.X with separate products and servers for these platforms, they have been merged. A new Team Concert Developer for IBM Enterprise Platforms contains advanced features focused on the needs of System z and IBM i development teams, I introduced some of them in the Part II Source Control enhancement blog.

This means that the server can run on ANY supported platform, and you can purchase users licenses for the function or capabilities that your team needs.

The Jazz Team Server

Adrian explained the design goals of the split between products, applications, and the Jazz Team Server a couple of months ago. The 3.0 release of Rational Team Concert is the first of our products with this new architecture. In addition to improved navigation and flexible deployment, these enhancements offer several advantages for administrators and enterprise customers:

  • Under the covers, the Jazz Team Server is basically a hub for integrating common data. In a set of applications, it allows users, licenses, and personal dashboards to be shared.
  • As an administrator, the first thing you’ll notice is that there are now two applications running on your server: the CCM (Change and Configuration Management) and the JTS (Jazz Team Server).
  • As an administrator of several instances of Team Concert 2.X, during the upgrade to 3.0 you can optionally choose to share the same JTS and benefit from increased license re-use and lower administration costs for managing users, repository permissions, and licenses.
  • As we make new applications available, you will be able to install licenses into the same JTS, and share users and licenses across the applications. This will be very useful as we release upgraded versions of RQM and RRC as part of our CLM initiative. It’s also useful in the setup of distributed source control as explained in Part II: Source Control enhancements.

Licensing

We’ve made three important licensing changes based on your feedback:

  • You can now install as many servers as you have user licenses.
    Benefits: This means that you can deploy client access licenses across as many or as few servers as you need. The most common advantages are to support disaster recovery installations, maintain separate test or training configurations, and enable teams who need many servers for physical security isolation.
  • Added a new user license called “Rational Team Concert Stakeholder”.
    Benefits: An entry priced license for users who don’t have to use the planning capabilities but instead simply want to use work items and dashboards to collaborate with a team. A typical user role for Stakeholder licenses might be users of your software who need to report defects or view project status.
  • Added a new user license called “Rational Team Concert Developer for Workgroups”.
    Benefits: An entry-priced Developer license that is limited to fifty Authorized Users per server.** “Developer for Workgroups” is identical to “Developer” except it does not support the new Distributed Source Control feature and it only supports Authorized User licenses. “Developer for Workgroups” can be combined with any other 3.x license on the same server. This allows teams to grow beyond fifty developers without having to trade-in their existing “Developer for Workgroups” licenses.

Fixed Term Licenses

We’ve also added support for fixed term licenses, available at an affordable annual renewal rate. If you have a temporary need for more licenses to add to your team, now you can easily do so.

Conclusion

Stay tuned for the new downloads page which will have a lot more details about the different licenses and official list of supported platforms.

Jean-Michel Lemieux
Chief Architect for Rational Team Concert

* Our lawyers would like me to remind you that these are not finalized plans or commitments…just work in progress and plans are subject to change without notice. See the Terms of Use.

** If you manage them with a shared license server, then you are only permitted to have a total of 50 Developer for Workgroups licenses installed across the set of servers using the same shared license server.

1 Star2 Stars3 Stars4 Stars5 Stars (4 votes, average: 4.75 out of 5)
Loading...
9 Comments
  1. David Davies November 9, 2010 @ 5:58 pm

    Sounds like lots of good improvements to the licensing. Will there be a converter to move our old 2.x licenses to the new models????

  2. Jean-Michel Lemieux November 11, 2010 @ 7:34 am

    Hi David, what occurs during upgrade is that your license assignments remain the same (eg, which user is assigned to which license) and then you should install the 3.0 license packs and then continue working. The licenses for 2.X aren’t compatible with 3.0, but the upgrade process is quite simple since the assignments remain valid.

  3. Rolf Nelson November 12, 2010 @ 12:57 pm

    Hi David, just to add to the above. Any RTC 2.x customer under active maintenance will receive entitlement to their corresponding RTC 3.0 user license. This entitlement will happen in Passport Advantage when RTC 3.0 is released. So for example if you had 10 RTC Developer Express licenses in RTC 2.x they will get mapped to an entitlement for 10 RTC 3.0 Developer for Workgroups licenses.

  4. Mike Kinney November 15, 2010 @ 1:48 pm

    What Eclipse clients will be supported? Will Ganymede still be supported?

  5. Jean-Michel Lemieux November 15, 2010 @ 9:07 pm

    Hi Mike, with RTC 3.0 the supported Eclipse client versions has moved up from 3.4 to supporting both 3.5 (Galileo) and 3.6 (Helios).

  6. siba guha November 18, 2010 @ 1:35 am

    Hi, what happens to Standard/Enterprise server license that is required in RTC 2.x ?

  7. Mike Johnson November 18, 2010 @ 1:52 pm

    Related to licensing — I seem to remember from 2.0 that users who did not have a license still had read-only access to the repo (not sure if it was work items and/or dashboards…?) If this is correct, does this still hold true for 3.0?

  8. Rolf Nelson November 19, 2010 @ 3:05 pm

    Hi Mike J, Yes. In RTC 3.0 a user can still read any work item, dashboard or BIRT report without a license as long as they have permissions and access granted to the project. You need a license to modify a work item but you can assign floating licenses to a broad array of people who may only need to submit a new defect now and then.

  9. Amante Gomez December 2, 2010 @ 2:19 am

    We will surely wait for the development of your plans as well as the quick license system

You must be logged in to post a comment.