| Feature | Starter | Standard | Enterprise | |
|---|---|---|---|---|
| Maximum number of developers/contributors | 25/unrestricted | 250/unrestricted | Unrestricted/unrestricted | |
| Supported databases | ||||
| Supported application servers | ||||
| Supported Eclipse clients | ||||
| Agile planning: daily, iteration, release | included | included | included | |
| included | included | included | ||
| included | included | included | ||
| Work item tracking | included | included | included | |
| Customizable process | included | included | included | |
| Subversion integration | included | included | included | |
| Role-based process permissions | included | included | included | |
| Process level access control | included | included | included | |
| LDAP Authentication | included | included | included | |
| Dashboards | limited support2 | included | included | |
| Cross-project dashboards | included | included | included | |
| Cross-repository dashboards | included | included | included | |
| Customizable work item attributes and presentations | included | included | included | |
| Rational Developer for System z integration | included | included | included | |
| ClearCase® Importer | included | included | included | |
| ClearQuest® Importer | included | included | included | |
| Customizable work item workflow | not included | included | included | |
| Plan risk assessment | not included | included | included | |
| Reports | not included | included | included | |
| Role-based process permissions | not included | included | included | |
| ClearCase Synchronizer | not included | included | included | |
| ClearCase Bridge | not included | included | included | |
| ClearQuest Connector | not included | included | included | |
| ClearQuest record and Jazz work item bridge | not included | included | included | |
| LDAP import | not included | included | included | |
| Floating licenses available | not included | included | included | |
| High availability | not included | included | ||
The number and types of Client Access Licenses (CALs) are defined by the Jazz Team Server for System z in your edition of Rational Team Concert for System z.
| Client Access License | Description |
|---|---|
| No Client Access License |
|
| Contributor |
|
| Developer |
Note: Floating Developer Client Access Licenses count against
the server user limit only when a user action occurs that requires
the license key. Unlike permanent Contributor Client Access Licenses,
floating Developer Client Access Licenses are not counted when they
are assigned.
|
| Build System |
|
| ClearCase Connector |
|
| ClearQuest Connector |
|
A floating Client Access License (CAL) enables multiple users to share the same CAL. For example, if two users only occasionally use the Jazz Team Server for System z, such as once or twice a day to update work items, then those users can share a floating CAL instead of purchasing two separate permanent CALs. A single server can administer and monitor CAL purchase counts and usage, and distribute CALs to more than one Jazz Team Server for System z.
A user who is assigned a floating CAL can only use the supported CAL functions if there is an available copy of a CAL. For example, if a server administrator purchases three floating Contributor CALs and assigns them to five users, then only three users can use the CALs at the same time. CAL usage starts when a user performs their first server operation that requires the CAL. A user holds the CAL until 2 hours after their last server operation. If a user acquires a CAL at 9 AM and edits work items until 9:24 AM, then the user holds the CAL until 11:24 AM.
You can simplify floating CAL usage administration and tracking by using a single server to distribute all floating CALs in a multiple Jazz Team Server for System z environment. Select a server that can hold the floating CALs, such as an existing server that runs as a Jazz Team Server for System z and floating CAL server. After installing floating CALs on a server, you can use the Admin Web UI to configure other servers to point to the floating CAL server, then those servers can assign and use the floating CALs.
To determine whether to install a new server to only manage floating CALs or to reuse an existing Jazz Team Server for System z as a CAL server, consider the following: