Workarounds and Limitations: Known issues in Jazz Reporting Service 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

Registration with Jazz Team Server fails on Oracle when the context root identifier is too long


First occurrence
6.0.6

Problem
When you register Lifecycle Query Engine (LQE) with Jazz Team Server, the setup fails on Oracle if the LQE context root identifier is longer than 5 characters.

Workaround
Ensure that the LQE context root is 5 characters or less.

Back to top


Certificate-based authentication fails when you use a smart card

First occurrence
6.0.5

Problem
In a smart card or client certificate authentication environment, Report Builder prompts for a user name and password for data service URLs. Report Builder cannot detect that the environment is secured with a smart card or client certificate, so it expects HTTP basic authorization credentials for data service URLs.

For example, this issue occurs in the following scenario with Microsoft Excel:
  1. Create and save a report in Report Builder that uses CLM applications with smart card or client certificate authentication.
  2. Run the report and export it to Microsoft Excel with live data.
  3. Open the Excel spreadsheet and click Make Results Dynamic. You are prompted to select which user certificate to use for authentication. Select a certificate.
  4. When the certificate validation is successful, Report Builder prompts you for your user name and password.
To resolve this specific scenario, complete the following steps:
  1. Re-export the Microsoft Excel spreadsheet.
  2. Open it and set the basicAuthenticationEnabled=false parameter in the Query URL field on the Run Query sheet. Save the Microsoft Excel document.
  3. Click Make Results Dynamic. You are prompted for a user certificate, after which you should see live data instead of the user name and password prompt.

Workaround
  1. Upgrade to Report Builder version 6.0.6 iFix003 or later.
  2. Add the https.client_cert.enabled=true property to <JTS_installation_directory>/server/conf/rs/app.properties.
  3. Start Report Builder. Newly exported reports should not have this issue.

Related information
Work Item 462179

Back to top


Draft reports cannot be edited


First occurrence

6.0.5

Problem
If you build and edit a report and do not save it, the report is auto-saved in a draft state with a generated title and timestamp, but you cannot edit the draft later.

Workaround
Complete these steps:
  1. Duplicate the draft report.
  2. Save the duplicate report with a new name.
  3. Delete the draft report.
  4. You can then edit the new report.
Related information
Work Item 465504

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 or 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.
Related information
IBM Rational License Key Center
Interactive Upgrade Guide
Oracle release note: Restrict JARs signed with weak algorithms and keys

Back to top


Links in an exported Word document cause authentication errors

First occurrence
6.0.4

Problem
If you export a Report Builder report that contains hyperlinks to Microsoft Word, clicking a hyperlink in the exported Word document might fail and cause the following error after you complete the login for CLM:
Invalid path to authentication servlet.

Workaround
Complete the steps in the following article to add a registry key entry for Word, which enables you to successfully log in to CLM after clicking the hyperlink in the Word document:
Error message when clicking hyperlink in Office: “Cannot locate the Internet server or proxy server”

Related information
Work Item 414080

Back to top


Limitations

Lifecycle Query Engine (LQE) requires Java 1.8


First occurrence
6.0.6

Problem
LQE requires a Java 1.8 runtime environment and will not work with Java 1.7.

Workaround
Install a Java 1.8 runtime environment.

Related information
See instructions for WebSphere Application Server and WebSphere Liberty.

Back to top


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


Ready-to-use reports might have untranslated columns when exported to another format


First occurrence

6.0.4

Problem
When you export a ready-to-use report to another format (for example Microsoft Word or PDF) in a non-English locale, the report might include extra non-translated columns. These reports often contain extra variables that are not displayed in Report Builder. When the report is exported, these hidden query variables are displayed as additional columns in the report and are not translated.

This problem does not affect ready-to-copy reports.

Related information
Work Item 414604

Back to top


Report Builder database backup cannot be disabled


First occurrence
6.0.1

Problem
Every six hours, the Report Builder database is backed up so that you can restore the data if an error occurs. You cannot disable the backup process.

Related information
Work Item 452514

Back to top


Feedback
Was this information helpful? Yes No 0 people rated this as helpful.