Download Release
April 23, 2019

Jazz Foundation

The foundation of the Collaborative Lifecycle Management solution

Jazz Foundation 3.0.1

Product Release / Trial | June 14, 2011
This is not the most recent version. We recommend Jazz Foundation . 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 Release Notes

Jazz Foundation 3.0.1 Release Notes

The following notes provide information on the contents of the Jazz Foundation 3.0.1 (June 14, 2011) release including details on issues of which users and consumers of Jazz Foundation should be aware.

Resolved APARs

The following APARs are fixed in this release:



Work Item

PM32064 Unable to add more than 10 floating developer CAL's on Derby 148690
PM32672 Validation errors when migrating Derby to DB2 in RTC 3.0 140989
PM34398 shortcuts for starting and stopping server not working on windows 7 when installed as admin using default install location 139997

Security Fixes

The Jazz Foundation 3.0.1 release includes important security fixes. It is recommended that all 3.0 customers upgrade to this release to obtain these important fixes.

Adoption Items

For application authors upgrading to Jazz Foundation 3.0.1, the list of adoption items can be found here. All adoptions are required unless otherwise indicated.

Other Notes

Client Access Licenses (CALs)

The early access 'Foundation User' client access license key included with the Jazz Foundation 3.0.1 - Jazz Team Server will expire on August 14, 2011. 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. If the expiration date above has passed, this should indicate that there is a newer milestone or service release available containing a CAL with an updated expiration. If you encounter this situation, please visit the Jazz Foundation downloads page and check the list of milestones and releases to identify a more appropriate download.

CRJAZ1846E Error Attempting to Assign Multiple Client Access Licenses (CALs) to a User from CCM or QM Application

When editing users from the Rational Team Concert (RTC) 3.0.1 or Rational Quality Manager (RQM) 3.0.1 admin web UI, the save operation may fail with the following error:

An error occurred while trying to assign the Client Access License keys to the user. Click "show details" to view the details of the license assignment error. Follow the instructions to fix the problem, and click "Save" to try again.ID CRJAZ1846E

Error Detail: The user configured to perform the request [ILicenseRestService] on the JTS is not authorized. There may not be a functional user configured for the oauth consumer, or the functional user that is configured does not have sufficient privileges to perform the requested operation. Connection Error: nullID CRJAZ1832E

This problem is known to affect license assignment and resource allocation changes involving users with multiple license assignments. The problem is isolated to non-distributed deployments, where RTC 3.0.1 or RQM 3.0.1 are deployed to the same application container as the Jazz Team Server (JTS) 3.0.1.

You can workaround this issue using one of the following 3 methods:

  1. Use the Jazz Team Server admin web UI (instead of the application admin web UI) to perform the operation
  2. Use the RTC Eclipse Client to perform the operation
  3. RTC and RQM can be configured to avoid this problem by setting the following Java system property and restarting the application server:^(?:(?!ILicenseRestService).)*$
Note that option 3 may adversely impact system performance as this disables a performance optimization. This issue is tracked in 167290: Cannot assign multiple CALs to a user in CCM or QM when server dispatch is enabled (affects single server only) [workaround exists]

Upgrade Script Parameters Should Use Quotes around Paths Containing Spaces

If you are performing a product upgrade using an upgrade script, you can provide command arguments by filling out the appropriate parameter file or by specifying the arguments on the command line. In both cases, you need to enclose paths that contain spaces within quotes. Failure to do so will result in a failed upgrade and you will need to re-run the upgrade script step after fixing the path. The parameter files for the upgrades are located in the server\upgrade directory. To locate the parameter files, from the command line, navigate to the 3.0.1_Install_Directory\server\upgrade directory and run the following command: locale.bat -showParamFileName

All paths specified in these files should enclose paths that contain spaces with quotation marks.

Alternatively, if you are specifying arguments on the command line to an upgrade script in the server\upgrade directory, all paths that contain spaces must be enclosed with quotation marks.

The exact error that occurs for failing to do this can vary depending on which parameter is improperly specified. The error will typically indicate that the command cannot find the specified path along with the path it is looking for. To fix the problem, enclose the problem parameter in quotes and re-run the upgrade script from the failed step.

This issue is most likely to impact Windows users because the default install path (C:\Program Files\IBM\JazzTeamServer) must be enclosed in quotation marks ("C:\Program Files\IBM\JazzTeamServer").

This issue is tracked in 167860: upgrade.bat fails, doesn't tolerate spaces in NEW_TOMCAT_HOME

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.

Lifecycle Project Administration Members Page Fails Silently for Unprivileged Users

If a user who does not have permission to modify project members attempts to save changes on the Lifecycle Project Administration members page, the operation will fail silently.

You can verify that the changes you make were applied by checking the members UI after you have saved your changes. If the changes you made are reflected in the UI, then the save operation was successful. If your changes are not shown in the updated UI, you may be having this problem. Verify that you have the repository roles and project area roles that are necessary to perform the operations that you are attempting.

This issue is tracked by 139795: Members page doesn't report error if user doesn't have permission to add member

Lifecycle Project Administration Members Page Doesn't Ask for Confirmation Before Navigating Away

If there are unsaved changes on the Lifecycle Project Administration members page and the user decides to drill into a project area editor or otherwise navigate away from the page, they are not prompted to confirm the navigation before they leave the page and their unsaved changes are lost.

This issue affects any action that triggers a navigation away from the members page. This is most commonly seen when a user decides to drill into a project area editor from the details view of a member record.

This issue is tracked by 167098: Members are removed if add roles is clicked before save - No Navigate-Away confirmation from Lifecycle Project Members page

The Lifecycle Project Administration Setup Wizard Step Doesn't Allow the User to Advance to the Final Step in Some Cases

In some cases, when proceeding through the Jazz Team Server setup wizard, the Lifecycle Project Administration step will not allow the user to advance to the final step. When the user clicks the next button, they are quickly redirected back to the LPA step.

This problem has only been observed after the Jazz Team Server setup wizard has been completed once successfully in the past. When this problem happens, it does not adversely affect the finalization process for the Lifecycle Project Administration application. The user can reload the page and proceed with the setup wizard without any adverse effects.

This issue is tracked by 167379: Setup Wizard looping from Summary back to LPA Finalize Setup

The Lifecycle Project Administration UI Redirects Infinitely With Certain Configurations

If the Lifecycle Project Administration application is configured with a capital letter in the hostname of its public URL, the UI will redirect infinitely.

The Lifecycle Project Administration application attempts to make sure the user is accessing the UI using the public URL, and it redirects the user if the request URL doesn't match the public URL. This leads to an infinite redirect when the public URL contains a capital letter since the browser always converts requests to use a lower-case hostname. In order to fix this problem, change the public URL in /conf/admin/ so the hostname is entirely lower-case and restart the Lifecycle Project Administration application.

This issue is tracked by 167977: Unable to access LPA due to server redirects

Problem with Unexpanded Variables in XDC Configuration Files

If you are running the Jazz Team Server, or any of the CLM applications, with a private URL that differs from the configured public URL, and if you are additionally using the product together with Rational Insight, you may have problems downloading the configuration files required to make the Cognos Data Manager ETL jobs work. These files are downloaded from the "Reports" section of the Admin Web UI. In the error case, the XDC file will contain some variables (e.g. for the server URL) which are not properly expanded.

To workaround this issue, load the XDC files using the Rational XML Data Configuration tool shipped with Rational Insight and manually specify the correct public URL for the servers (replacing the placeholder variable). This only needs to be done once, after downloading the XDC file and before creating the ODBC data source.

This issue is tracked by 165754: XDC file downloads not populating with changes made on Jazz admin reports Data Collection page.

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

Configure Data Warehouse Setup Wizard Page does Not Allow the Use of Certificates for Authentication

The data warehouse relies on the existence of a "data collection user", who is used to run all of the data collection jobs. Due to technical limitations, the current implementation requires that this user be able to log in using a password, and as such, does not support certificate authentication. As a result, reporting functionality in general which relies on the data warehouse (such as out-of-the-box BIRT reporting for RQM and RTC, and custom reporting using RRDI) will not function in these environments.

A partial workaround is to use the RTC data mart, a legacy implementation, instead of the data warehouse. To do this, skip the creation of the data warehouse during the server setup. Instead, in the Admin Web UI for RTC, select "Reports", and select "Data Mart" instead of "Data Warehouse". Reporting functionality for RTC will remain similar to that in RTC 3.0 and previous versions. The out-of-the-box BIRT reports will function, but custom reporting with RRDI will not be supported. This workaround applies to RTC only; there is no comparable workaround for RQM.

This issue is tracked by 160897: Configure Data Warehouse setup wizard page does not allow the use of certificates

Unable to Display Floating License Usage Report for Tokens using Internet Explorer 8

When attempting to run the license usage report for tokens using IE 8, the section for inputting the data range disappears when selecting the tokens report type. At present, the only workaround is to use an alternate browser such as Firefox 3.6 to view this report.

This issue is tracked by 167723: Floating license usage report for tokens does not work in IE 8 (workaround exists)

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 3.0.1

You may experience a problem viewing a remote requirements viewlet after upgrading RRC from 2.x to 3.0.1 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 3.0.1
  • Before upgrading the RM application to 3.0.1 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 3.0.1. (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.

Observed Memory Leaks When Using Internet Explorer 8

When the Web UI for RRC, RQM, RTC, or the Jazz Team Server is accessed using the Internet Explorer 8 browser in scenarios that involve a number of application transitions (e.g. with the "JKE Banking" sample), we have observed that the system memory used by iexplore.exe grows with every transition. Eventually the performance will be affected and the system may run out of memory. This seems to be a know issue in Internet Explorer 8 related to garbage collection of DOM nodes and JavaScript objects used by Web applications that are not completely freed when pages are unloaded.

Since memory leaks persist between opened tabs in a browser, only closing and reopening the browser will release the trapped memory. However, the problem will reappear over time. The issue does not manifest itself on other supported browsers, including Mozilla Firefox 3.6. While Internet Explorer 9 is not an officially supported browser for this release, we have not observed the problem in question when using it in testing.