Download SR1 Release

Jazz Foundation

The foundation of IBM Engineering Lifecycle Management

Jazz Foundation 6.0.3

Product Release / Trial | December 5, 2016
This is not the most recent version. We recommend Jazz Foundation 7.0.2 SR1. This is made available for archival purposes and may contain bugs and/or security vulnerabilities. If you do download this version, it is being provided AS IS, without warranties of any kind, including the implied warranties of merchantability and fitness for a particular purpose. We strongly advise you review the support pages for this version and update the product or take actions recommended therein. Security bulletins contain instructions for the security vulnerability addressed therein, and may require upgrading to a newer version. Link to security vulnerability blog: IBM PSIRT blog.

Jazz Foundation 6.0.3 New & Noteworthy

Jazz Foundation 6.0.3 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:

For a list of changes to the installation and upgrade process, see CLM and IoT CE 6.0.3 Installation and Upgrade Notes.

New in Jazz Foundation 6.0.3

All interactive guides are available from one page

In version 6.0.3, a single landing page is available where you can access all the interactive guides for installing, upgrading, and setting up Collaborative Lifecycle Management (CLM) applications. This release also includes a removal guide that you can use to uninstall software packages. For details, see Interactive installation, upgrade, and setup guides.

New model for deploying Help locally

In previous releases, you could download a .zip file that included the IBM Documentation framework and the full set of Rational solution for Collaborative Lifecycle Management (CLM) Help. In 6.0.3, the Knowledge Center framework is included with the Jazz Team Server and is installed as a .zip file in the jazz-team-server-install-dir/kcci_install directory. Extract the contents of the .zip file. Then download a .zip file that includes the CLM Help content, and extract that .zip file into the kcci_install directory. For details, see Installing help on your computer.

Labels for project area permissions have changed

Labels for these project area permission groups have changed to be more consistent with other CLM applications: Dashboards, Global Configuration Management, Process, and Reports. This change affects only the labels you see; it does not affect how permissions are assigned to users.

CLM Server Monitoring was removed

CLM Server Monitoring, a performance monitoring utility included in versions 5.0.2 and later, was removed in 6.0.3. Version 6.0.3 includes a new, lightweight monitoring utility that uses industry-standard MBeans and that can be consumed by other application monitoring services. For more information about server performance and monitoring, see Plan Item 396673, Work Item 392897, and the Deployment wiki article about Known Expensive Scenarios.

Monitoring performance and resource-intensive scenarios

The CLM solution now provides application-level and scenario-level data for operational monitoring tools, which are published as Java Management Extension (JMX) MBeans.

Application performance and usage metrics

To help monitor the overall health of a production system, application metrics are now available in the form of MBeans. These MBeans can be integrated into most enterprise-monitoring tools and can help analyze trends and report on operational data. To publish the MBeans, you must enable them from the Advanced Property section of the application administration page. For details about MBeans, see the CLM Monitoring Managed Beans Reference on the Deployment wiki.

Resource-intensive scenarios and verbose logging

The application administration page contains a new Serviceability section. This section lists scenarios for the application that can use a large number of system resources, which can degrade server performance and negatively affect the user experience. Administrators can turn verbose logging for these scenarios on and off. Verbose logging enables a debugging mode for a subset of Java classes associated with specific scenarios so that administrators can determine whether the scenarios are affecting system performance. For details about these scenarios and options for managing them, see the Deployment wiki: Known Expensive Scenarios.

Global Configuration Management

Update a stream from a baseline

You can now update a stream to use the same configurations as a baseline.

This operation simplifies changing a hierarchy of configurations to use more recent baselines, or rolling back to previous baselines.

For example, you can update a global stream used by your team to match a global baseline produced by another team. As your team develops a product variant, you can update your stream with baselines produced by the platform team, to use more recent versions of common components.

When you choose this action:

  • Streams and their location in the hierarchy do not change, unless they are removed.
  • Baselines are replaced to mirror the baseline hierarchy that you update from.

To use this feature, right-click a global stream and click Update; then, select a baseline.

Update example

Confirm update stream

See Work Item 388777.

Enhancements to the Add Configuration dialog box

  1. You can now add global configurations from other project areas managed by the same GCM application using the Project Area list.
  2. Use the new All project areas option to search for global configurations across project areas that you have access to.
  3. You can select several global configurations from the same page of the results to add more than one at once.
  4. The last application that you select in the Add Configuration dialog box is displayed the next time that you open the dialog box.
Add configuration enhancements

See Work Item 343851, Work Item 388218, and Work Item 340989.

Archive nested global configurations

Archive nested global configurations by using the new option in the Confirm Archive window. Global configurations that are used by other active configurations are automatically excluded. This feature provides more automation for archiving global configurations that you no longer use.

Confirm archive

The Unarchive button on archived configurations has been relabeled Restore.

Image of restore

See Work Item 396085.

Preview for creating and staging baselines

When you create or stage a baseline, you now see a preview of the configurations to be created. Configurations that do not have unique names are identified so that you can pick a non-conflicting name.

Preview of create baselinne

See Work Item 390570.

Show a configuration as the root

To focus on a section in a configuration hierarchy, use the new Show as Root operation on child nodes to open the configuration tree with the selected configuration as the root.

Save as root

See Work Item 370833.

Other interface improvements and constraints

Name uniqueness

Name uniqueness rules are enforced for new artifacts and when renaming an existing artifact. However, existing name collisions are not changed.

  • Component names must be unique within a project area.
  • Configuration names must be unique within a component.

See Work Item 384122.

Component skew indicator is more obvious and informational

The component skew indicator for a configuration hierarchy has been improved as follows:

  • The indicator is much more visible—a bar at the top of the tree.
  • It tells the user directly what the issue is (no more reliance on a tool tip)
  • It defines component skew and indicates what to do about it
  • It indicates the number of skewed components

Component skew detection

See Work Item 390521 and Work Item 390267.

Baseline creation no longer navigates away

The Create Baseline operation no longer navigates away to the baseline, but instead remains in the stream hierarchy where the request was initiated so you can do further work on the stream. A message provides a link to the baseline.

See Work Item 370914.

Simplified process for creating a stream from a baseline

In 6.0.2, configuration leads could create a stream from a baseline that was in the middle of a baseline hierarchy; however, the new stream was not added to the hierarchy because it was not modifiable. The 6.0.3 release simplifies this scenario. Now, configuration leads can create a stream from a baseline only if the root of a hierarchy is modifiable (a stream).

Create stream when root is stream

See Work Item 370924.

Project area shown in details view of configuration

Since you can add global configurations from other project areas, the details show where the configuration is from (which determines the governing permissions and project properties).

Project area shown in details

See Work Item 391454.

New in previous versions of Jazz Foundation

For details about new features and functionality in previous releases, see these pages: