Workarounds and Limitations: Known issues in Jazz Foundation 6.0.6

The following known problems are related to this release.

Workarounds

The following problems in this release have workarounds:

Limitations

The following problems in this release do not currently have workarounds:


Workarounds

Application menu is empty in the Add Association dialog box


First occurrence
6.0.6

Problem
When you add an association to a project area, the Application menu in the Add Association dialog box might be empty. Typically, this issue occurs if you have several hundred project areas and use Mozilla Firefox as a web browser.

Workaround
Complete one of the following workarounds:
  • Add the association by using another supported web browser.
     
  • In Mozilla Firefox, close the dialog box and re-open it. It might take several attempts to populate the Application menu. Note: With hundreds of project areas, the dialog box can take 10 or more seconds to load.
Related information
Work Item 458116

Back to top


Licensing errors might occur if you upgrade the Java environment or upgrade applications to version 6.0.5 or later


First occurrence

6.0.5

Problem
If you upgrade your version of Java to a fix pack that was built after April 2017, or you upgrade an application to version 6.0.5 and later and are using WebSphere Liberty, licensing errors might occur. The errors occur because earlier licenses were signed with the MD5 algorithm, which is now blocked by newer versions of Java.

For example, the License Key Management page for Jazz Team Server might display the following error in the Description field: CRJAZ1236I A development time license is being used. Similarly, the jts.log file might display the following error: CRJAZ0965I The file was not a valid server or client access license activation key.

The latest license files no longer contain the MD5 algorithm because IBM and Oracle Java introduced restrictions on JAR files that are signed with weak algorithms and keys.

Workaround
The licenses in the IBM Rational License Key Center were updated to use a different signature algorithm.

After you upgrade your server to version 6.0.5 or later, obtain the updated licenses from the IBM Rational License Key Center to replace your current licenses. If you previously used floating, token, or authorized user single install licenses, install their updated versions. Your existing user license assignments are kept during the installation of the updated licenses.

Important: If you are not upgrading all applications at the same time, you must apply an interim fix to the applications at earlier versions before you upgrade Jazz Team Server. The following interim fixes contain the compatible version of Java:
  • 6.0.4 interim fix 007 and later
  • 6.0.3 interim fix 010 and later
  • 6.0.2 interim fix 015 and later
  • No version of 5.0.2 contains a compatible Java version. For 5.0.2, complete the steps in the IBM Support flash article.
If you cannot apply the interim fix before the upgrade, upgrade Jazz Team Server and then complete the steps in the IBM Support flash article. If you do not apply the interim fix or complete the steps in the article, the internal licenses do not load on Jazz Team Server and the applications might experience issues.

To update your current license files, follow the instructions in the Interactive Upgrade Guide or complete the following steps based on the type of license:

For term (floating or authorized user) or token licenses:

Note: For token licenses, you are only required to download the jazztokens.zip file. You do not have to download the license.dat file because it does not contain changes.
  1. Log in to Jazz Team Server, go to jts/admin > Server > License Key Management and note all the licenses on the server.
  2. In IBM Rational License Key Center, under License Management, click Return Keys.
  3. Click the product link that you want to return the license keys for, and then click Return.
  4. After the license is returned, click Get Keys.
  5. Click the product link to generate licenses for.
  6. When prompted, provide the required information and click Generate.
  7. Download the  file that contains the new licenses.
  8. Log in to Jazz Team Server, go to Server > License Key Management and reimport the new license files.
  9. To add a license, click Add, accept the license agreement if you agree to its terms, and then complete the steps in the wizard.
For non-term floating and authorized user licenses:
  1. Log in to Jazz Team Server, go to jts/admin > Server > License Key Management and note all the licenses on the server.
  2. In IBM Rational License Key Center, go to View keys by host or View keys by user.
  3. Enter the information about the host or the user.
  4. Select the product to generate the license for.
  5. Click View Licenses for Selected Product Lines.
  6. Select the license and click View Details.
  7. Click Download Keys.
  8. Log in to Jazz Team Server, go to Server > License Key Management and reimport the new license files.
  9. To add a license, click Add, accept the license agreement if you agree to its terms, and then complete the steps in the wizard.
Note: If you imported trial licenses before the newer versions of Java were adopted, you might still receive errors in the jts.log file even after you import the updated licenses. For example, you might receive this error: CRJAZ0965I The file was not a valid server or client access license activation key. You can ignore these errors.

Related information
IBM Rational License Key Center
Interactive Upgrade Guide
Oracle release note: Restrict JARs signed with weak algorithms and keys

Back to top


Global Configuration Management custom attributes and links are editable by default after upgrading from a pre-6.0.4 release


First occurrence
6.0.4

Problem
In Global Configuration Management version 6.0.1, 6.0.2, and 6.0.3, custom attributes and links of baselines are read-only in the web client. If you upgrade from one of these releases to version 6.0.4 or later, the attributes and links are editable by default after the upgrade.

Workaround
If you prefer custom attributes and links of baselines to remain read-only after the upgrade, go to Manage Project Properties and clear the Allow editing on baselines check box for each item.

Related information
Work Item 370782

Back to top


Team areas are not useful in Global Configuration Management


First occurrence
6.0.4

Problem
Global Configuration Management does not currently support team areas in a useful way. You can define team areas, but cannot associate them with global components to achieve team-dependent roles or privileges for them.

Workaround
Starting in version 6.0.3, global configuration hierarchies can contain global configurations from other project areas, so you can differentiate roles and privileges for users and components by project area.
Starting in version 6.0.6.1, Global Configuration Management supports team areas. For details, see Customizing access to components and configurations by using team areas in IBM Knowledge Center.

Related information
Work Item 404131
Work Item 382235
Limitation: Global Configuration Management does not support team areas [6.0, 6.0.1, 6.0.2, 6.0.3]
Global Configuration Management: Components and configurations now support team areas for managing group permissions

Back to top


Limitations

Java 7.1 SR4 FP10 is not supported


First occurrence
6.0.5

Problem
Collaborative Lifecycle Management (CLM) applications that run on WebSphere Application Server Liberty (16.0.0.4 and 17.0.0.2) and that are configured with JRE 7.1 SR4 FP10 might crash. By default, versions 6.0.5 and later include a Java version that is stable.

Related information
Work Item 439584

Back to top


Java 8 SR5 Fix Pack 5 through Fix Pack 10 is not supported as the runtime for CE/CLM applications on a Windows platform


First occurrence

6.0.5

Problem
Continuous Engineering (CE) and Collaborative Lifecycle Management (CLM) applications on a Windows platform that run on Java 8 SR5 Fix Pack 5 through Fix Pack 10 encounter null pointer exceptions and might not be usable. Use Java 8 SR5 Fix Pack 11 (8.0.5.11) or later as the runtime.

Related information
Work Item 455371
Work Item 452307
APAR IJ04429

Back to top


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Feedback
Was this information helpful? Yes No 0 people rated this as helpful.