Workarounds and Limitations: Known issues in Jazz Reporting Service 7.0.2

The following known problems are related to this release.

Workarounds

The following problems in this release have workarounds:


Workarounds

Restoring LQE databases from backup gives an error for text indexes that do not exist


First occurrence
7.0.2

Problem
While restoring an LQE database from a backup, the following error occurs:
“server\conf\lqe\datasets\history\historyText’ does not exist”
It is because shapes\textIndex and history\textIndex subfolders are not available anymore in the LQE backup folder.

Note: The creation of the default\textIndex subfolder is optional. In the LQE Advanced Properties page, if the Create Index for Full Text Search option is selected, then the default\textIndex subfolder is created.

Workaround
To resolve the error, contact IBM Support for a test fix for LQE. Installation of the test fix will resolve the error.

Related Information
Work item 521100

Back to top


The links_am data source is added in a failed state to LDX when the ELM 7.0.1 environment is renamed


First occurrence

7.0.2

Problem
After you rename the Engineering Lifecycle Management 7.0.1 environment, the links_am data source is added to LDX in a failed state. Therefore, the links_am data source cannot be reindexed.
 
Workaround
To enable reindexing of the links_am sources, complete the following steps:
  1. From the LDX data sources page (http://<server>:<port>/ldx/web/admin/data-sources), remove the links_am data sources.
  2. Go to the EWM Administration page (http://<server>:<port>/ccm/admin) to create the OAuth consumer key.
  3. To create the OAuth consumer key, complete the steps in the “Creating an inbound consumer key for LQE or LDX on each lifecycle management application” section of the Adding data sources from a different JTS topic. The functional user is lqe_user.
  4. Go to the LDX data sources page (http://<host_name>:<port>/ldx/web/admin/data-sources).
  5. To add the data source, click Add Data Sources. The Add Data Sources wizard opens.
  6. In the Select Data Source step of the wizard, complete the following substeps:
    • In the Data Source field, click https://<server>:<port>/<am_context_root>/oslc/workitems/trs2 for the Architecture Management application.
    • (Optional) In the Label field, you can enter links_am to identify the data source for Architecture Management.
    • In the Authentication field, click Specify OAuth authentication details for this data source.
    • Click Next.
  7. In the Specify Authentications Details step of the wizard, complete the following substeps:
    • In the OAuth consumer key and OAuth secret key fields, enter the consumer key and secret key that you created in step 3.
    • In the three URL fields, enter the details for Architecture Management.
      The URLs must be similar to the following examples, where <am_context_root> is the context root for the Architecture Management application.
      https://<server>:<port>/<am_context_root>/oauth-request-token
      https://<server>:<port>/<am_context_root>/oauth-authorize
      https://<server>:<port>/<am_context_root>/oauth-access-token
    • Click Next.
  8. In the Configure Data Source step of the wizard, enter the required details, and then click Finish.
Related Information
Work item 519497

Back to top


The clmhelp.war file and the updateSite.zip for release 7.0.2 are unavailable for download

First occurrence
7.0.1

Problem
The clmhelp.war file and the updateSite.zip file for release 7.0.2 are unavailable for download due to technical issues.

Workaround
You can install the KCCI.zip file on your intranet server to view the help locally. Click here to download the ELM702_KCCI_contents.zip file.

For information about installing the KCCI.zip file, see the Installing help on an intranet server topic.
 
Related information
Work Item 59952

Back to top


DCC shows old product names on the Resource Group Configuration page


First occurrence

7.0

Problem
When you upgrade the Data Collection Component to version 7.0, on the Resource Group Configuration page, you might see old product names or versions such as Rational DOORS Next Generation.

Workaround

Complete these steps:
  1. Restart the Data Collection Component server while the ELM applications are running.
  2. Click the Load Jobs button.
  3. The correct product names, such as IBM Engineering Requirements Management DOORS Next, are displayed.
Related information
Work Item 486500

Back to top


Workarounds: RM types are displayed as URLs in (LQE) Requirements trend report


First occurrence

7.0

Problem
If you are writing a requirements trend report for a LQE data source, the RM types might display as URLs instead of type names.
The problem is that there is a configuration missing which prevents the job that updates the type names from running. This problem might be seen in previous versions of this product.

Workaround
Complete these steps:
  1. When you upgrade to the 7.0 release, run the LQE setup again for the history jobs to create that configuration.  To run the setup, open https://<server>:<port>/lqe/setup/history.
  2. If the setup is successful, you will see a “status: “OK”  message on the page.
  3. Run the metric jobs to trigger additional updates. It may take a couple of runs for the information to be completely updated.
Your reports should now show the correct type names.

Related information
Work Item 491432

Back to top


Logging information not available for changes made to reports, schedules, report managers, and data sources


First occurrence

6.0.6.1

Problem
Report Builder does not log the following tasks:
  • Creating, deleting, and updating reports
  • Creating and deleting schedules
  • Adding and deleting report managers
  • Adding, deleting, or updating data sources
This issue is resolved when you apply the following interim fixes but the log4j.properties file does not get updated when you upgrade JRS by replacing the rs.war files.
  • 7.0.1 interim fix 002 and later
  • 7.0 interim fix 005 and later
  • 6.0.6.1 interim fix 012 and later
  • 6.0.6 interim fix 018 and later
Workaround
Add the following content to the Jazz_Install_Dir/server/conf/rs/log4j.properties file if you upgrade JRS by replacing the rs.war files:

log4j.additivity.R=false

# Logger to analyze creation/deletion/updation of report/schedule/endpoints/report managers
log4j.logger.AUDIT=DEBUG, AUDIT
log4j.additivity.AUDIT=false
log4j.appender.AUDIT=org.apache.log4j.RollingFileAppender
log4j.appender.AUDIT.File=logs/rs_audit.log
log4j.appender.AUDIT.MaxFileSize=10MB
log4j.appender.AUDIT.MaxBackupIndex=10
log4j.appender.AUDIT.layout=org.apache.log4j.PatternLayout
log4j.appender.AUDIT.layout.ConversionPattern=%d{ISO8601} – %m%n

 

Note: Report Builder does not log tasks that involve draft reports.


Related information
Work Item 510387

Back to top


Timeout limits must be increased before metamodel refresh


First occurrence

6.0.6.1

Problem
For servers with many project areas, the Report Builder metamodel fails to refresh, because the “sparqlShapeTypes” type queries time out.

Workaround
Increase the timeout limits to provide enough time for all the metadata to refresh.

Increase all the following timeout values to 1200 seconds. If the problem still persists, set them all to a higher value, such as 1800 seconds.
  • The lqe.read.timeout value in the conf/rs/app_runtime.properties file
  • The socketTimeout value in the conf/rs/app_runtime.properties file
Note: Add + 1 to the query timeout value to set the socket timeout value. For instance, if the query timeout value is set to 1200, the socket timeout value must be 1201.
  • The query timeout value in LQE
  • The timeout value for any proxy server
Related information
https://www.ibm.com/support/knowledgecenter/en/SSYMRC_7.0.2/com.ibm.team.jp.jrs.doc/topics/c_set_query_socket_timeout.html

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 License Key Center (formerly known as 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 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 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 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 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 (now known as ELM):
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 (now known as ELM) 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


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