Known issues
Review the issues with workarounds and limitations for this release
Workarounds
The following issues in this release have workarounds:
Defect ID | Description |
474873 |
After an upgrade, data might not load in some RELM (now known as Engineering Insights) views. First occurrence: 6.0.6.1 Problem: After you upgrade Rational® Engineering Lifecycle Manager, data might not load in views that were created in an earlier version of the product. Workaround: If this problem occurs, re-create the view by using the artifacts from the palette. |
498728 |
For third-party applications, the preview of the artifacts is not getting displayed in the views. First occurrence: 7.0 Problem: For third-party applications, when you hover over the artifacts in the containers of a view, you are unable to see the preview of the artifacts. Workaround:
|
474873 |
After an upgrade, data might not load in some RELM (now known as Engineering Insights) views. First occurrence: 6.0.6.1 Problem: After you upgrade Rational Engineering Lifecycle Manager, data might not load in views that were created in an earlier version of the product. Workaround: If this problem occurs, re-create the view by using the artifacts from the palette. |
498728 |
For third-party applications, the preview of the artifacts is not getting displayed in the views. First occurrence: 7.0 Problem: For third-party applications, when you hover over the artifacts in the containers of a view, you are unable to see the preview of the artifacts. Workaround:
|
499616 |
Full-text search indexes must be rebuilt when you upgrade to 6.0.6.1 or later. First occurrence: 6.0.6.1 Problem: In the 6.0.6.1 release, the Apache Lucene full-text search engine was upgraded to a more recent version. This upgrade requires all existing full-text search indexes that were created in 6.0.6 or earlier to be rebuilt. Full-text search indexes must be rebuilt for both the ELM servers and the Engineering Workflow ManagementConcert® Client for Eclipse IDE. Workaround: Typically, when you upgrade an installation by using the upgrade scripts, the full-text search indexes from the earlier installation are copied to the new installation. However, the upgrade scripts in 6.0.6.1 and later do not copy previous indexes from version 6.0.6 or earlier (including interim fixes). Instead, the new server automatically rebuilds the indexes in the background after you start it. Results of full-text searches might be incomplete until the reindexing operation is finished; the progress of the reindex is periodically written to the server log file. Alternatively, instead of allowing the server to rebuild full-text search indexes online. You can rebuild them manually by running the repo tools app rebuildTextIndices command after the upgrade is complete. But before you start the server, where app is one of am, ccm, or qm Reindexing might be a lengthy process and can take many hours for a large database. In the web client, a system alert in the banner states that reindexing is in progress. If you follow a manual upgrade procedure instead of running the upgrade scripts, you must verify that the full-text indexes are not copied from the old installation to the new installation. If the new installation is configured to use the same full-text index location as the old installation (the value of the com.ibm.team.fulltext.indexLocation property in the old and new teamserver.properties file is the same absolute path name), you must either run the repotools app -rebuildTextIndices command before you start the server, or delete the contents of the folder at that location before you start the server. You might want to preserve the old contents if you decide to abandon the upgrade and roll back to the previous release. If an application is clustered, the offline reindexing procedure (by using repotools) or the
online procedure (ensuring that the full-text index folder is empty before starting the server) must
be installed on each node in the cluster. The Engineering
Workflow Management
Client for Eclipse maintains a local full-text search index
for the team Artifact History view. When you upgrade the Engineering Workflow Management Client
for Eclipse to version 6.0.6.1 or later; the full-text search index is automatically deleted. This
means the artifact history is cleared and will accumulate artifacts again after the upgrade. For ELM
servers, complete one of these steps:
|
425428 |
If the view data source is Lifecycle Query Engine by using Configurations, queries that result in many artifacts might fail First occurrence: 6.0.1 Problem: If you use WebSphere® Application Server 8.5.5.6 or 8.0.0.11 with Java™ run time 6.1.8.4 (Java 6, R1, SR8, FP4), the jrs.log file on the Jazz® Reporting Service (JRS) server might contain the following error: java.lang.OutOfMemoryError: Direct buffer memory. Use appropriate '<size>' via -XX:MaxDirectMemorySize=<size>. This error is triggered by using a defect in Java runtime version 6.1.8.4. Use the previous WebSphere Application Server fix pack level, or upgrade to WebSphere Application Server fix pack 7. Workaround: Upgrade your WebSphere Application Server
8.5.5 to fix pack 7, or revert your WebSphere
Application Server 8.0 to fix pack 10 if you must use WebSphere Application Server 8.5.5.6 or 8.0.0.11, edit the JVM arguments by using the WebSphere Application Server Integrated Solutions Console as follows:
|
425430 |
If you use the default settings, Design Management and Asset Management data are not visible in the views of Rational Engineering Lifecycle Manager (now known as Engineering Insights) First occurrence: 6.0.1 Problem: If you use the default settings, artifacts from applications that don't support the Access Control 2.0 specification are not visible in views. For example, Design Management 6.0.1, Asset Manager 7.5.2.3, and earlier versions, do not support the Access Control 2.0 specification. Workaround: Configure the data source permission for these applications in the Lifecycle Query
Engine (LQE):
|
465351 |
Parameter changes in custom artifact elements are not reflected in views. First occurrence: 6.0.6 Problem: If you change a parameter in a custom artifact element, the change is not shown in views that contain that custom artifact element. Workaround: Complete these steps:
|
511221 |
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. |
425425 |
The removal of back links might affect queries and views that were created before version 6.0 First occurrence: 6.0 Problem: Before version 6.0, lifecycle management applications such as Rational DOORS® Next Generation, Engineering Workflow Management, and Rational Quality Manager included both forward and back links in the tracked resource set (TRS) feeds. The forward and back links were indexed in the Lifecycle Query Engine (LQE), and queried by Rational Engineering Lifecycle Manager. Starting in version 6.0, if you enable configuration management for your lifecycle management applications. And if you enable your project area for configuration management, the back links in your application are not included in the TRS feed, and are not indexed in LQE. Links are effectively one way. For example, in previous versions, two triples were included in the LQE index for a single conceptual link relationship:<requirement A> oslc_rm:validatedBy <test case B>and <test case B> oslc_qm:validatesRequirement <requirement A>. In version 6.0, only <test case B> oslc_qm:validatesRequirement <requirement A> is included in the LQE index; which of the two directions is considered forward depends on each link type
For example, if your existing query from a previous application version was Requirement
oslc_rm:validatedBy? testCase, in version 6.0 it should be as follows:?testCase oslc_qm: validates
Requirement?Requirement. This syntax also works with previous versions of lifecycle management
applications that store both link directions. In the transition phase, or for third-party
applications that store only the oslc_rm: validated. By link, use the following property
path:?testCase(oslc_qm:validatesRequirement|^oslc_rm:validatedBy)?requirement
Note: Your
queries might run slower, and you might find duplicate results that require further
adjustment.
Complete below steps:
|
425505 |
Upgrading Rational Engineering Lifecycle Manager token licenses from a version 5 to version 6 release requires extra steps. First occurrence: 6.0 Problem: Rational Engineering
Lifecycle Manager (now known as Engineering Insights) version 5 token licenses cannot be upgraded to
version 6 the same way as other licenses. For example, you follow this procedure to upgrade Rational Engineering Lifecycle Manager floating licenses and
authorized user licenses from version 5 to 6: Upgrading Rational Engineering Lifecycle Manager floating and authorized user licenses
All users that had version 5 licenses are now assigned version 6 licenses. No further action is
required. For token licenses, you must complete a procedure that involves the following
steps.Upgrading Rational Engineering Lifecycle Manager
token licenses (high-level workflow)
Workaround: To upgrade Rational Engineering Lifecycle
Manager token licenses from 5.0 to 6.0, complete these steps:
Note: If you use an application such as IBM
Lotus®
Symphony® or Microsoft Excel to edit the file, extra characters can be added that cause the import process
to fail.
In this case, you replace all occurrences of com.ibm.team.relm.user.token.20150420_1111 with com.ibm.team.relm.user.token and save the file. Importing the users does not cause any changes except for assigning the licenses. The users who had version 5 licenses should now have version 6 licenses assigned to them. |
425419 |
Views might not show artifacts when the Lifecycle Query Engine that is configured as the Report Builder data source is registered with a separate Jazz Team Server. First occurrence: 6.0 Problem: SPARQL queries defined for Rational Engineering Lifecycle Manager views are run by the Lifecycle Query Engine (LQE), which is configured as the data source in Report Builder. When Report Builder and LQE are running on separate Jazz Team Servers, and authentication is not established yet, queries from Rational Engineering Lifecycle Manager fail, and the view containers show errors. Workaround: Complete these steps:
|
425508 |
When you upgrade from version 5.0.2 or earlier, a Lifecycle Query Engine error indicates a problem with the product definition tool First occurrence: 6.0 Problem: When you upgrade Rational Engineering Lifecycle Manager (now known as Engineering Insights) from version 5.0.2 or earlier to a version 6 release, a Lifecycle Query Engine (LQE) error indicates a problem with the product definition tool. The error occurs because the product definition tool is no longer available in Rational Engineering Lifecycle Manager version 6.0 and later. The product configuration tree capabilities are now available in the Global Configuration Management application. This error does not affect any product function in the new version, but LQE tries to acquire indexes periodically, and logs the errors. Workaround 1: To avoid the error, complete one of these workarounds. If you do not intend to visualize product definition artifacts in your views, delete the product definition data source:
Workaround 2: If you still use product definition artifacts that were indexed in Rational Engineering Lifecycle Manager 5.0.2, pause the indexing of product definition tool data:
|
484440 |
Updating the CE4IoTConnector base URL requires a restart of the IOTP application First occurrence: 6.0.6 Problem: Starting in the V6.0.6 release, the CE Connector for IoT base URL updates automatically. This happens after you complete the RELM setup. There is a known problem where the base URL for the connector is updated in the teamserver.properties file of the IOTP application, however the connector starts with the old URL. Workaround: After completing the JTS setup, you must restart the IOTP application at most one time to pick up the updated base URL. |
496132 |
In the Sort tab, attributes from other project areas are displayed First occurrence: 7.0 Problem: When you select the scope (such as Project Areas) at the view level, then this scope is applicable when you sort the artifacts. However, when you select the scope at the container level, then this scope does not get immediately applied when you sort the artifacts. Workaround:
Result: Now, the selected scope is applied to the sort function for the container |
Limitations
The following issues in this release do not have workarounds.
ID | Description |
---|---|
471850 |
In view, you cannot show links between Rational DOORS Next Generation and IoT artifacts First occurrence: 6.0.6. Problem: You cannot create links between Rational DOORS Next Generation (now known as IBM Engineering Requirements Management DOORS Next) and Internet of Things (IoT) artifacts by using the Continuous Engineering (CE) Connector for IoT. However, when you create views to show the relationships between these artifacts, the links are not displayed. |
460677 |
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. |
425426 |
Matrix reports can no longer be generated in CSV format. First occurrence: 6.0 Problem: In Rational Engineering Lifecycle Manager 5.0.2, on the Queries page, you click Generate Matrix to create a matrix report in CSV format. In version 6.0 and later, this capability is no longer available because the Queries menu now opens Report Builder, which does not support matrix reports in those versions. |