Tip: Rational Team Concert 2.0 editions and licensing overview (including 184.108.40.206 license changes)
Last Updated: September 29, 2009
Authors: Paul Vanderlei, Kartik Kanakasabesan, Dave Thomson, Bill Higgins
Rational Team Concert is available in four editions, Express-C, Express, Standard, and Enterprise which enable different levels of server infrastructure capabilities and user capabilities. Additionally, Rational Team Concert allows administrators to assign users one or more Client Access Licenses, which enable the user to access particular product capabilities.
Rational Team Concert is available in four different editions:
Express-C: Designed for very small teams or individual practitioners who wish to experiment with Rational Team Concert or to use it for a small project. The Express-C edition is available as a free download from Jazz.net and supports up to 10 users. It includes ten Developer Client Access Licenses, which allow users to use Jazz SCM, Work Items, Build, and other capabilities. Express-C works only with the Derby database (included).
220.127.116.11 Update: Express-C now includes 10 FREE Developer Client Access Licenses and can be used with any of the supported commercial databases. You can purchase additional Contributor licenses.
Express: As teams outgrow the Express-C edition, they can transition to the Express edition. User capabilities are the same as the Express-C edition, but the Express edition supports larger teams, up to 50 users, and allows the customer to use an IBM DB2, Oracle, or SQL Server database to back the Jazz repository. Express edition includes three Developer Client Access Licenses. Express can be used with Derby, but is limited to 10 users in this configuration.
Standard: Allows up to 250 users and provides additional functionality and infrastructure components that are not part of Express or Express-C, including ClearCase and ClearQuest Connectors to interface the server to these systems. It also provides two additional components that are useful for tracking larger teams: Dashboards and Reports. IBM DB2 or Oracle database can be used to back the Jazz repository. The Standard Edition also includes three Developer Client Access Licenses. Standard can be used with Derby, but is limited to 10 users in this configuration.
Enterprise: Similar to Standard with two notable exceptions. It is unrestricted in the number of users the Jazz Team Server will support. It also provides support for use of the Jazz Team Server in a high availability configuration. The Enterprise edition allows installation of a second copy of the server in an idle standby application server failover configuration. Note, this requires WebSphere Application Server and optional high availability database configuration (DB2, Oracle, SQL Server).
Understanding Client Access License Options
Rational Team Concert uses Client Access Licenses to allow users to use certain product capabilities. If a user is not assigned any Client Access Licenses, the user may still view information in the Jazz Repository (for instance bug reports), but the user must be assigned one or more Client Access Licenses to make changes in the Jazz repository.
Rational Team Concert supports two user Client Access License types: Contributor and Developer. These Client Access License types are described below in detail:
A user assigned the Developer Client Access License type has complete access to all the developer capabilities and additional capabilities within Rational Team Concert. The additional capabilities include the ability to:
- Create and manage Project Areas and Team Areas
- Implement Process enforcement models
- Create personal dashboards (Standard and Enterprise editions only)
- Create and manage reports (Standard and Enterprise editions only)
- Synchronize with ClearCase and/or ClearQuest (Standard and Enterprise editions only)
A Contributor Client Access License is intended for non-developer team members who would like to know the status of the projects or modify work items. It allows read-only access to all capabilities, and read-write access to work items. The following Figure illustrates some of the differences between contributor and developer Client Access Licenses. The contributor Client Access License has the capability to view dashboards and reports only with Standard and Enterprise editions.18.104.22.168 Update: The Contributor Client Access License now allows all write operations except for Source Control and Build operations. This means that the Contributor Client Access License can be used to create and manage plans, reports, process customizations, and dashboards. In the diagrams below, think of the Contributor Client Access License as everything in the Developer License except for Source Control and Build.
Client Access License Frequently Asked Questions
Q1: Does the product include any Client Access Licenses?
A1: Express, Standard, and Enterprise editions of Rational Team Concert include three Developer Client Access Licenses. Express-C includes ten Developer Client Access Licenses. A user assigned a Developer Client Access License has access to all capabilities within the installed edition of Rational Team Concert.
Q2: What about people who only need read-only access to the information in the Jazz Repository?
A2: A user without any assigned Client Access License may view information in a Jazz Repository. Only operations that write to the repository require a Client Access License.
Q3: If I need to access two separate Jazz Team Server instances running Rational Team Concert, do I need to have a Client Access License on each instance?
A3: If you need write access to both servers then yes, you need a Client Access License for each. You only need a Client Access License for servers that you need to write to – a Client Access License is not required for read-only access. If you have a long-term assignment change that changes which servers you need write access to, your server administrator can reassign your licenses for you.
Q4: Do I need a Client Access License to administer a Jazz Team Server?
A4: No. A Jazz Team Server administrator does not require a Client Access License. Broadly speaking, operations which modify Jazz Team Server infrastructure settings do not require an assigned Client Access License but operations that modify software development artifacts do require an assigned Client Access License. So for instance, a user would not need an assigned Client Access License to modify Jazz Team Server’s database settings or manage license keys, but the user would require an appropriate Client Access License to create Project Areas or deliver source code to Jazz SCM.
This section uses example scenarios to demonstrate how different types of teams would choose from the various Rational Team Concert editions and make choices about purchasing Client Access License keys. This section of the Tech Note uses example scenarios to demonstrate how different types of teams would choose from the various Rational Team Concert editions and make choices about purchasing Client Access License keys.
Development teams consist of various types of roles and not everyone in a development is a technical stakeholder. Teams may have team members who play roles such as:
- Project Manager
- Team Lead
Different members of the team may different interactions with Rational Team Concert based on their roles:
Deployment Scenario 1: A small team of 10 users
- In this scenario the team consists of 8 developers, 1 development lead and the business owner. In this case the business owner needs to view the progress the team is making on a particular release. The business owner is usually on the road meeting customers and soliciting requirements and in most cases uses the web to interface with the development team. The customer who will be consuming the actual product that the development team produces wants to have some insight into the product. In this scenario the development team chooses to use Express-C and does not have to purchase anything. The customer in this case will not have a Client Access License but will be able to view the information exposed from the web interface.
Deployment Scenario 2: Small to mid-sized team of 50 users
- In this scenario there is a development team of 25 developers. The developers include 1 build engineer, 2 team leads and 1 development manager. Along with these stakeholders in the project, the organization has 10 system engineers in the field that submit bugs and participate in discussions with the development teams and in some cases provide code changes back to the repository based on customer experience. The organization also has 10 major customers that influence the decision around how the product evolves and submit development tasks to the development team. The team also has 2 project managers that provide development tasks and track progress on the work that is being done for the iteration. There also 3 testers in the project who validate the projects code deliverables submit work items in cases where they fail to comply. In this scenario this organization will need 35 Developer Client Access Licenses (25 for the development teams and ten for the system engineers) 12 Contributor Client Access Licenses (10 for the customers and 2 for the project managers) and the testers can use the 3 Developer Client Access Licenses included with the server. Since the total number of Developer and Contributor Client Access licenses is exactly 50, they can use either an Express, Standard, or Enterprise server depending on their functional needs.
Deployment Scenario 3: Several small to mid-sized teams on a single Standard server
- As an extension to Scenario 2 imagine 5 teams of 40 each with similar composition being hosted on a single server. In this case the single server will be a Standard server hosting projects for up to 250 users working in various projects on a single a server. In this case you can have developers work across project areas and deliver changes. In the case of the Standard server you still have the three included Developer Client Access Licenses, so you would need to purchase 197 additional Client Access Licenses, a mixture of Developer and Contributor Client Access Licenses, depending on the composition of the team.
Deployment Scenario 4: One large team hosted on a single server
- Similar to Deployment Scenario 3 in terms of the user volume but in this case it is a single Project Area hosting artifacts from 250 users on a Standard Server. A benefit of this type of implementation is that it allows changes to the process to impact all users working in the same project area. You can still have multiple teams hosted in a single Project Area with multiple team areas and streams for the respective team areas. Since 3 Developer Client Access Licenses are included, you would need to purchase 197 additional Client Access Licenses, a mixture of Developer and Contributor Client Access Licenses, depending on the composition of the team.
Deployment Scenario 5: Large distributed team hosted on a single server, using ClearCase and ClearQuest Connectors
- This is similar to Deployment Scenario 4, with three differences. First, the ClearCase and ClearQuest Connectors are being used to interface the server to these other systems. Second, this team is larger, numbering 1000. Third, given the single server installation, this team will be the Jazz Team Server in a high availability configuration (a second copy running in idle standby). Because of the number of users on one server and the need for high availab ility support, this team will use the Enteprise edition of Rational Team Concert. The only additional requirement over and above Scenario 5, is that all of the users directly accessing ClearCase and ClearQuest must be properly licensed for these systems. You do not need ClearCase and ClearQuest licenses for users that are only using Rational Team Concert, and you do not need Rational Team Concert Client Access Licenses for the users that are only directly accessing ClearCase and ClearQuest. In general, the license says you do need Cient Access Licenses for anyone who is directly or indirectly accessing Rational Team Concert unless the access is read-only, but the license grants an exception in the case of ClearCase and ClearQuest.