Download 6.0.6.1 Release
April 23, 2019

Jazz Foundation

The foundation of the Collaborative Lifecycle Management solution

Jazz Foundation 3.0.1.6 interim fix 8

Product Release / Trial | September 30, 2016
This is not the most recent version. We recommend Jazz Foundation 6.0.6.1 . 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 3.0.1.6 Release Notes

Jazz Foundation 3.0.1.6 interim fix 8 Release Notes

This interim fix is a service release of Jazz Foundation, Version 3.0.1.

The following information describes the important fixes and issues in the release. Be sure to also read the Rational Team Concert Version 3.0.1.6 interim fix 8 Release Notes, the Rational Requirements Composer Version 3.0.1.6 interim fix 8 Release Notes, and the Rational Quality Manager 3.0.1.6 interim fix 8 Release Notes.

Known Issues in 3.0.1.6 interim fix 8

Action required for a remote floating license server after upgrade

After the upgrade of 3.0.1.6 interim fix 8, if you use a floating license server that is not on the same server as the JTS application, apply the steps at Workaround: Action is required for a remote floating license server after an upgrade to version 6.0. The steps for 3.0.1.6 are the same as the steps for 6.0.

JTS Setup for Microsoft SQL Server does not support integrated authentication

JTS Setup fails with the error, "This connection does not support integrated authentication." You will be unable to install CLM in your environment. This issue is tracked by 233472: Need to document that "Integrated Authentication" is not supported.

3.0.1.6 interim fix 8 includes Installation Manager (IM) version 1.5.3.
If you are using the 3.0.1.6 interim fix 8 product launchpad on systems with newer versions of Installation Manager installed, it might be necessary to apply steps from Workaround: IBM Installation Manager installed on machine is incompatible with the version included in Jazz downloads.

Issue with Data Collector User not being assigned Data Collector Client Access License
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 (for example, "dw_user"), and verify that the "Data Collector" license is selected 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.

Use a new command prompt for each application upgrade
If you are performing an upgrade with an upgrade script, 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, the environment variables from a previous command might interfere with the upgrade script. Specifically, problems have been observed 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 ultimately fails with this 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 (32 bit vs. 64 bit)
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 the Change and Configuration Management (CCM) application on a 32-bit system with a shared Jazz Team Server on a 64-bit system, errors occur during the upgrade. The errors occur when the upgrade script on the application system tries to run a repotools command remotely on a Jazz Team Server system of different architecture.

Diagnosing the problem:

On Windows, the following error message is shown 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.

On other platforms, no CLM error message exists. A full list of OS error messages for every supported platform is not available. The error should indicate a machine type mismatch with the Java command.

To work around the problem, follow the instructions below for the application version you are upgrading:

Jazz Team Server 3.0:
  • No workaround is required because no remote Jazz Team Server command is issued.
Requirement Management (RM) application 2.X:
  • No workaround is required because the RM upgrade is run from the Jazz Team Server system.
CCM application 3.0:
  • Step 0: Validate that Jazz Team Server has already been upgraded to 3.0.1. Run the upgrade script with the -ignoreJTSVersionCheck flag.
CCM application 2.x:
  1. Start script execution on the CCM system.
  2. Step 0: Validate that Jazz Team Server has already been upgraded to 3.0.1. Run the upgrade script with the -ignoreJTSVersionCheck flag.
  3. Step 3: Stop the script execution here. Run Step 3 manually from the Jazz Team Server machine. To run step 3 manually, you must move files between the Jazz Team Server and CCM systems or mount a drive to the CCM system from the Jazz Team Server system.
  4. Resume script execution at step 4 on the CCM system.
Quality Management (QM) application 2.x:
  1. Start script execution on the QM system.
  2. Step 0: Validate that Jazz Team Server has already been upgraded to 3.0.1. Run the upgrade script with the -ignoreJTSVersionCheck flag.
  3. Step 3: Stop the script execution here. Run Step 3 manually from the Jazz Team Server machine. To run step 3 manually, you must move files between the Jazz Team Server and QM systems or mount a drive to the QM system from the Jazz Team Server system.
  4. Resume script execution at step 4 on the QM system.

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

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

  • If there is an active theme, the changes are not shown in the web UI.
  • When you access the theme admin page, the list of themes are not shown.
  • The error log contains 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 you are running through the server setup wizard and an expired client access license is assigned. To fix the issue, an administrator must shut down the server and use the repotools tool to correct the OAuth key that is associated with the theming storage area. To identify and resolve the issue, follow these steps:

  1. Get the correct OAuth key.
    1. Login to Jazz as an administrator.
    2. Go to the Communication/Consumers (Inbound) section.
    3. In the Authorized Keys section, find the net.jazz.ajax.theme entry, and copy the consumer key for later reuse.
  2. Shut down the server
  3. Verify that you have a bad OAuth key:
    1. Run this command: repotools-jts.sh -listStorageAreaKeys*
    2. Find the entry for net.jazz.ajax.theme and compare it to the value that you copied earlier.
  4. Fix the OAuth key by running this command: repotools-jts.sh -setStorageAreaKeys list=net.jazz.ajax.theme,<correct consumer key>.
  5. Restart the Jazz server.

Known problems and workarounds

For a list of the known problems and workarounds that are published as jazz.net workaround articles, view the Jazz Foundation V3.0.1.6 workaround articles jazz.net query.