Workarounds and Limitations: Known issues in Jazz Reporting Service 6.0.6.1

Report export to Microsoft Excel with more than 5000 records might be truncated

First occurrence
6.0.6.1

Problem
A Report Builder report exported to Microsoft Excel exports a maximum of 5000 records by default. If you have a larger set of records, the report might be truncated.

Workaround
You can modify this on the server to change the default behavior.

Complete these steps:

1. On your system, open the JRS_install_dir\server\conf\rs\app.properties file in a text editor.
2. Add the query.results.excel.limit property and set a value with the new limit. For example to limit the query to 6000 records, set query.results.excel.limit=6000.
3. Save your changes and restart the server.

Related information
Work Item 467464
 

Report formatting is not displayed correctly if the source for a calculated column contains an apostrophe

First occurrence
6.0.6.1

Problem
If you create a report that includes a calculated column, and the source value for that column contains an apostrophe (such as Won’t Fix), when you run the report, the formatting is not displayed correctly and you receive an XML error.

Workaround
Complete these steps:

1. On the Report Builder home page, click either My Reports or All Reports.
2. Search for the report with the issue.
3. Open the Action menu for that report and click Edit.
4. Click Format Results.
5. If the Graph view is selected, click Table view.
6. Remove the row with the calculated value that contains an apostrophe.
7. Re-create the row that you deleted in step 6 by clicking  Calculated value .
8. Select Count number of artifacts by URL > Limit > Resolution > is > Won’t Fix (or whichever value contained the apostrophe).
9. Save the report.

Related information
Work Item 476868

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.

Workarounds: Scheduled report with filters exported to Excel has no data

First occurrence
6.0.6

Problem
The “QueryResults” sheet is empty in an Excel sheet generated from a report schedule. This issue happens with reports that are using an LQE configuration-aware data source.The problem occurs because the schedule does not capture the configuration selected by the user to run the report and schedule it.

Workaround
Delete the schedule and create a new schedule after upgrading to the iFix containing fix for PH05830.

Related information
Work Item 470637

 

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

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.

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

Links in an exported Word document cause authentication error

s
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

Reports on custom artifact types which differ in name only by a space do not work

First occurrence
6.0.6.1

Problem
Existing reports that use data from custom artifact types whose names differ only by a space do not work.
Recreate any reports affected by this problem. Avoid creating custom attributes whose name differs by a whitespace, for example “CustomAttribute” and “Custom Attribute.”

Related information
Work Item 470818

 

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

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

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