Download 7.0.2SR1 Release

Jazz Foundation

The foundation of IBM Engineering Lifecycle Management

Jazz Foundation

Product Release / Trial | November 2, 2012
This is not the most recent version. We recommend Jazz Foundation 7.0.2 7.0.2SR1. 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 Release Notes

Jazz Foundation Release Notes

The following notes provide information on the contents of the Jazz Foundation release (Nov 02, 2012).

Resolved APARs

The following APARs are fixed in this release:

APAR Summary Work Item
PM63335 NPE occurs when catching exception on email send 236369

A complete list of defects and enhancements resolved in can be found here

Other Notes

Upgrading from 3.0.1,, or

The upgrade from 3.0.1,, or to is a straightforward set of steps that extracts configuration information from, but does not alter the 3.0.1,, or installation. Refer to the Upgrade Instructions in the Info Center to guide you through the upgrade process.

Client Access Licenses (CALs)

The early access 'Foundation User' client access license key included with the Jazz Foundation - Jazz Team Server will expire in the future. Jazz Foundation is provided as early access technology and, as such, users and consumers are expected to move aggressively to the most recent milestones and releases in order to take advantage of the latest fixes and enhancements and to ensure that feedback is timely. A newer milestone or service release is available containing a CAL with an updated expiration. Please visit the Jazz Foundation downloads page and check the list of milestones and releases to identify a more appropriate download.

Use a New Command Prompt for each Application Upgrade

If you are performing an upgrade with an upgrade script, you should always use a new command prompt window to avoid environment variable conflicts.

If you are running repotools commands or running multiple upgrades from a single command prompt, it is possible that the environment variables from a previous command will interfere with the upgrade script. Specifically, we have seen problems when issuing a 2.x repotools command to export data followed by a 3.0.1 upgrade script command. The problem is due to the fact that the 2.x repotools command does not reset all of the environment variables. In this case, the upgrade script will ultimately fail with the error:

"CRJAZ1834E Error provisioning the server."

In general, it is good practice to use a new command prompt for each upgrade even if you are not running 2.x repotools commands first.

Upgrade Script Workaround for Distributed Deployment when Systems have Different Architecture (32bit vs 64bit)

Several commands used by the upgrade script invoke other commands that do not function properly when invoked on a system with a different architecture. For example, if your setup includes CCM on a 32-bit system with a shared JTS on a 64-bit system, you will hit errors during the upgrade execution. The errors occur when the upgrade script on the application system attempts to execute a repotools command remotely on a JTS system of differing architecture.

Diagnosing the problem:

On Windows, the following error message will occur during step 0 (updateConfigurationFiles) or step 3 (importApplicationData) of the upgrade:

CRJAZ2107E The Jazz Team Server compatibility check failed with a machine type mismatch error. The machine type of the application system and the target Jazz Team Server system must be the same, either both 32-bit or both 64-bit. If this is not the case, follow the instructions in the InfoCenter for a distributed deployment where drive-mapping is not possible.

There is currently no CLM error message for non-Windows platforms and we do not have the full list of OS error messages for every supported platform. The error should indicate a machine type mismatch with the java command.

To workaround the problem. Following the instructions below for the application version you are upgrading:

JTS 3.0:
  • No workaround is required since no remote JTS command is issued.
RM 2.X:
  • No workaround is required since the RM upgrade is run from the JTS system.
CCM 3.0:
  • Step 0: Validate that the JTS has already been upgraded to 3.0.1. Run the upgrade script with the -ignoreJTSVersionCheck flag.
CCM 2.x:
  • Start script execution on the CCM system.
  • Step 0: Validate that the JTS has already been upgraded to 3.0.1. Run the upgrade script with the -ignoreJTSVersionCheck flag.
  • Step 3: Stop the script execution here. Run Step 3 manually from the JTS machine. This will require you to move files between the JTS and CCM systems or mount a drive to the CCM system from the JTS system.
  • Resume script execution at step 4 on the CCM system.
QM 2.x:
  • Start script execution on the QM system.
  • Step 0: Validate that the JTS has already been upgraded to 3.0.1. Run the upgrade script with the -ignoreJTSVersionCheck flag.
  • Step 3: Stop the script execution here. Run Step 3 manually from the JTS machine. This will require you to move files between the JTS and QM systems or mount a drive to the QM system from the JTS system.
  • Resume script execution at step 4 on the QM system.

Issue with Data Collector User Not Being Assigned Data Collector CAL

When configuring the Jazz Team Server to work with an external LDAP user registry, in some cases, the Data Collection User may not be properly assigned a license when completing the server setup wizard. The result is that some of the data collection jobs will fail when run with permission-related exceptions.

To work around this issue, as an administrator, go to the user editor for the data collection user (e.g. "dw_user"), and verify that the "Data Collector" license is checked, and that the "JazzAdmins" repository permission is assigned to the user. If not, make these changes and save the user editor. The data collection jobs should then proceed normally.

This issue is tracked by 165703: Data Collector user not given Data Collector CAL

Error During Initial Login to RRC Deployed in a Distributed Environment when Using Internet Explorer 8

If you have deployed RRC in a distributed topology (where the RRC application and JTS are in separate application containers), users may experience a problem during initial login to the RRC application when using IE8. In particular, the login will fail with the error "Invalid path to authentication servlet.: /".

To workaround this problem, the user will need to refresh the browser and repeat the login attempt. On the the second attempt, the user should be presented with a "collaborate with server..." prompt allowing the user to communicate with the JTS and proceed past the login sequence. Alternatively, the problem can be avoided by using an alternate browser such as IE7 or Firefox 3.6.

Recovering from CRJAZ1512E: "the theming storage area has the wrong OAuth key associated with it."

If you experience any of the following behaviors, it is an indication that the OAuth key associated with the theme storage area in the Jazz Team Server is incorrect:

  • If there is an active theme, the changes will not appear in the web ui.
  • When accessing the theme admin page, the list of themes will not show up.
  • The error log will have an error stating that "the theming storage area has the wrong OAuth key associated with it."

One known scenario where this can occur is when running through the server setup wizard when an expired CAL is assigned. To fix the issue, an Administrator must bring the server down and use the repotools tool to correct the OAuth key associated with the theming storage area. The following is the complete list of steps to identify and resolve the issue:

  1. Get the correct OAuth key.
    • Login to Jazz as an Admin.
    • Navigate to the Communication/Consumers (Inbound)
    • In the section Authorized Keys, find the net.jazz.ajax.theme entry, and copy the Consumer Key for later reuse
  2. Shutdown the server
  3. Verify you have a bad OAuth key
    • Run the command: -listStorageAreaKeys*
    • Find the entry for 'net.jazz.ajax.theme' and compare it to the value copied above.
  4. Fix the OAuth key by running the command -setStorageAreaKeys list=net.jazz.ajax.theme,<correct consumer key>
  5. Restart the jazz server

Unable to view a remote Requirements viewlet on a dashboard after upgrading RRC from 2.x to

You may experience a problem viewing a remote requirements viewlet after upgrading RRC from 2.x to if all of the following are true:

  • You have two or more CCM 3.0 applications associated with a single 3.0 Jazz Team Server
  • You first upgraded the JTS and one of the CCM 3.0 applications to version
  • Before upgrading the RM application to you added a remote RRC viewlet to one of the CCM 3.0 application's project or team area dashboards
  • You then upgrade the RM application from 2.x to (at this point the remote RRC viewlet will be broken)

To correct the issue, go to the following URL and click on "Update":


This will fix the viewlets on all dashboards associated with the Jazz Team Server.