April 23, 2019
IBM Rational Team Concert
Task tracking · Source control · Agile planning
Rational Team Concert 6.0.4
Rational Team Concert 6.0.4 New & Noteworthy
Rational Team Concert is an integral part of the Rational solution for Collaborative Lifecycle Management (CLM). For new and noteworthy information about other applications, see these pages:
- Jazz Foundation (Jazz Team Server) and Global Configuration Management 6.0.4
- Quality Management 6.0.4
- Requirements Management 6.0.4
- Jazz Reporting Service 6.0.4
- Rational Engineering Lifecycle Manager 6.0.4
- Design Management 6.0.4
For a list of changes to the installation and upgrade process, see the CLM and IoT CE 6.0.4 Installation and Upgrade Notes.
New in Rational Team Concert 6.0.4
For a complete list of new and noteworthy items in this release, see the New & Noteworthy Details.
For a summary of items in this release, see the following highlights:
Support for Rational Team Concert clustering
To support horizontal scaling and high availability, Rational Team Concert can now be clustered. Multiple backend nodes that run Change and Configuration Management (CCM) servers can be provisioned as nodes of a cluster. Client traffic to these nodes is load-balanced by a front-end proxy, or load balancer, such as HAProxy. A clustered application maintains high efficiency by making nodes communicate via MQTT Broker, such as IBM MessageSight. For details, see Change and Configuration Management cluster environment.
Operation History view available for streams and workspaces
You can now view the operation history for a stream or workspace. From within the Operation History view, you can also roll back the contents of an entire workspace or stream to a previous point in time.
New check-in advisors are available
The following new server-side preconditions are available for source control check-in operations, and you can set them in either the Eclipse client or web client:
- Restrict File Size: This precondition prevents users from checking in files that exceed a specified size limit.
- Restrict Check-in of Resources with the Same Name: This precondition prevents users from checking in a resource if another resource in the same location has the same name, even when the capitalization differs. Because Windows systems ignore capitalization and Linux systems do not, this precondition can help avoid conflicts in projects where developers use both platforms.
- Restrict Check-in Based on Specified MIME Types and Encodings: This precondition prevents users from checking in files if the MIME type or encoding are not permitted for the project area. Currently, you can only set this precondition by using the Eclipse client. An extension point for check-in operations is also available so that you can write your own preconditions.
- Restrict Change Set Size: This precondition ensures that the number of changes in each change set does not exceed the value that you specify.
Set the validity status on links between SCM files and other CLM artifacts
You can now set the validity status on links between SCM-controlled files in Rational Team Concert and other Collaborative Lifecycle Management (CLM) artifacts, such as requirements in Rational DOORS Next Generation, test scripts in Rational Quality Manager, or other SCM-controlled files, to provide full traceability from user requirements to implementation to test results. For details, see Linking Rational Team Concert source control files to CLM artifacts.
Display links in containers and show the history of valid links
You can now find the links between SCM-controlled files and other artifacts for all files in a stream, snapshot, or baseline. Each stream, snapshot, and baseline has a File Links tab, which displays the files within that object that have links associated with them. The display includes the validity of the links so that you can address any discrepancies. You can navigate the links and change the validity status from this view.
The validity status can now show the history of links with a valid status between two artifacts. This feature enables you to discover when the relationship was considered valid when you decide whether the status of the link has changed.
Support for Microsoft Visual Studio 2017
You can now install the Rational Team Concert integration into the Microsoft Visual Studio 2017 IDE. Unlike previous versions, Microsoft Visual Studio 2017 allows multiple instances of the IDE (such as Professional and Enterprise) to co-exist. IBM Installation Manager detects the instances of Microsoft Visual Studio 2017 on the system and lets you install the Rational Team Concert integration into all of them.
SAFe template improvements
This release includes improvements to the SAFe 4.0 Process (Program) and SAFe 4.0 Process (Portfolio) templates. For details, see SAFe template improvements.
Improved storage model for Enterprise Extensions artifacts
In this release, Rational Team Concert Enterprise Extensions has completed the migration to a new internal storage model for artifacts. Previously, these artifacts were stored differently and triggered the creation of Jena indexes, used for queries, that were stored in the server file system. Now all the queries are performed against the CCM relational database, and Jena is not used.
After server startup, Enterprise Extensions runs migration tasks to complete the conversion.
Quick Planner Next (technical preview)
Quick Planner Next is available as a technical preview in this release. For details, see Quick Planner Next (technical preview).
New in previous versions of Rational Team Concert
For details about new features and functionality in previous releases, see these pages: