December 5, 2016
The foundation of the Collaborative Lifecycle Management solution
Jazz Foundation 6.0.1
Jazz Foundation 6.0.1 New & Noteworthy
Jazz Foundation is an integral part of the Rational solution for Collaborative Lifecycle Management (CLM). For new and noteworthy information about the CLM applications, see these pages:
- Change and Configuration Management 6.0.1
- Quality Management 6.0.1
- Requirements Management 6.0.1
- Jazz Reporting Service 6.0.1
- Rational Engineering Lifecycle Manager 6.0.1
For a list of changes to the installation and upgrade process, see CLM 6.0.1 Installation and Upgrade Notes.
To activate the configuration management capabilities that were added in CLM 6.0, Rational DOORS Next Generation and Rational Quality Manager require a no-cost activation key. For more information, see Enabling configuration management in CLM 6.0.1 applications.
New in previous versions of Jazz Foundation
For details about new features and functionality in previous releases, see these pages:
- Jazz Foundation New & Noteworthy 6.0
- Jazz Foundation New & Noteworthy 5.0.2
- Jazz Foundation New & Noteworthy 5.0.1
- Jazz Foundation New & Noteworthy 5.0
- Jazz Foundation New & Noteworthy 4.0.7
New in Jazz Foundation 6.0.1
- Global Configuration Management
- Jazz Foundation Services online migration
- Separate table spaces for database indexes on IBM DB2 and Oracle
- SAML support for web clients through the Jazz Authorization Server
- WebSphere Liberty replaces Apache Tomcat
- New authentication type in Rational Team Concert clients - Integrated Windows
Global Configuration ManagementOne-step creation of a baseline hierarchy
The Create Baseline operation on a stream creates a baseline hierarchy from the stream hierarchy in a single step. Likewise, Commit Baseline creates a baseline hierarchy from a baseline staging stream hierarchy.
Create streams for selected baselines in the context of the global stream
The Create Streams operation creates streams for the selected baselines and any global configurations required to complete the stream hierarchy.
Automation of milestone baseline creation
You can now stage a new baseline hierarchy from an existing one, which is useful when rebaselining because of a project area configuration change (for example, an updated requirements baseline).
Custom attributes using Manage Project Properties
Privileged users can define custom properties—global configuration attributes, links, and data types—for a project area through the Manage Project Properties page. Project properties are a convenient way to differentiate configurations. The details pane of the configuration tree view has sections for displaying and editing custom attribute and link values.
New system attributes: Branch and tags
Users can add branch and tag attributes to global configurations. The global configuration picker features filtering by tags.
Component skew icon
The configuration tree view automatically shows an icon alerting users if skew exists. Component skew occurs if multiple configurations of a component are in the same configuration hierarchy.
Persistence of recent configurations
The Recent Configurations list is persisted across sessions on the Global Configurations banner menu. Also, the list displays only configurations rather than configurations and components, so finding a configuration is easier.
Jazz Foundation Services online migration
You can migrate Jazz Foundation Services resources from one server to another while the old server is running. For details, see the Jazz Foundation Services online migration documentation.
Separate table spaces for database indexes on IBM DB2 and Oracle
Administrators now have more control over table space organization on IBM DB2 and Oracle. By setting options before creating database tables, administrators can configure Jazz-based products to use a different table space for indexes and for LOBs. For more information, see Manually configuring a DB2 database and Manually configuring an Oracle database.
SAML support for web clients through the Jazz Authorization Server
When you use Jazz Security Architecture single sign-on, you can configure your Jazz Authorization Server to use a Security Assertion Markup Language (SAML) identity provider. For more information, see Managing users on Jazz Authorization Server.
WebSphere Liberty replaces Apache Tomcat
The Apache Tomcat application server is no longer being bundled with Jazz products. It has been replaced by IBM WebSphere Liberty, a lightweight, high-performance Java EE server. When you upgrade from a previous release that used Apache Tomcat, select the WebSphere Liberty option when you install the 6.0.1 release, and select the Migrate from Apache Tomcat to IBM WebSphere® Liberty profile option in the Interactive upgrade guide. The upgrade scripts automatically migrate the old Tomcat configuration to the Liberty configuration in the new installation. Some manual adjustments might be required; see the upgrade documentation for details.
Apahce Tomcat is still supported, so if you cannot switch to WebSphere Liberty, you can download and install your own copy of Tomcat. Instructions for continuing to use Tomcat are provided in both the Interactive installation guide and the Interactive upgrade guide.
Note: If you previously used the Tomcat user registry (where user names and passwords are stored in the tomcat-users.xml file), and you perform the upgrade to use WebSphere Liberty, the user accounts are converted to the WebSphere Liberty basic user registry, where user names and passwords are also stored in an XML configuration file. For security reasons, passwords cannot be migrated because they are encrypted in the Tomcat user registry in a way that does not allow decryption. Therefore, new passwords are generated for each user, and are stored in a file named passwords.txt in the server folder of the new installation (where the upgrade scripts were run from). The system administrator must use that file to determine the new password for all users, inform them of their password, and encourage them to change the password when they log in to the new installation for the first time.
New authentication type in Rational Team Concert clients - Integrated Windows
Rational Team Concert clients (rich client, repotools, VS.NET, and others) now support Integrated Windows Authentication.
This type of authentication is only available on Microsoft Windows operating systems and only if the client machine is a member of a domain. A user's userId and password in
Change and Configuration Management (CCM) must be the same as the credentials used to log into the workstation.
In this case, Integrated Windows Authentication will reuse the credentials the user provided when logging into the workstation to authenticate with CCM.
For more information see Connecting to repositories and project areas, Repository tools command-line reference, Connecting to repositories and project areas in Advanced mode and Connecting to repositories for Microsoft Visual Studio IDE.