Known issues

Edit online

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:
  1. A third-party application whose artifacts are displayed in ENI must have the Delegated Preview Service enabled.
  2. The third-party applications must be added as a friend to either JTS or ENI. If it is added as a friend in JTS, it is not necessary to add at ENI.
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:
  1. A third-party application whose artifacts are displayed in ENI must have the Delegated Preview Service enabled.
  2. The third-party applications must be added as a friend to either JTS or ENI. If it is added as a friend in JTS, it is not necessary to add as a friend at ENI.
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:
  1. For online background indexing, no action is required except to ensure that the full-text index folder is empty before you start the server.
  2. For offline indexing, before you start the server, run the appropriate repotools-<app> -rebuildTextIndices command.
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:
  1. Click the JRS server inServers > Server Types > > WebSphere application servers.
  2. Under Server Infrastructure, click Java and Process Management > Process Definition
  3. Go to Additional Properties > Java virtual machine.
  4. In the Generic JVM arguments field, remove this argument: -XX:MaxDirectMemorySize=1G.5. Save the changes, and restart the server
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):
  1. Go to the LQE administration Permissions pagehttp://<host_name>:<port>/lqe/web/admin/permissions
  2. On the Permissions page, under Data Groups, select Design Management or the application that you want to configure.
  3. In the Groups section, click Add groups, and select the groups that have access to the resources. To grant all LQE users permission to access the resources, select Everyone.
  4. Click OK to save your settings.
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:
  1. For the custom artifact element parameters that are already used in the view, set the value type to Not Used.
  2. Delete the settings under Parameter Value.
  3. Save the view.
  4. Clear the browser cache and reload the view to pick up the changed parameter details.
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 project areas that are not using configuration management, back links are still created, and Rational Engineering Lifecycle Manager queries work as before.
  • If existing SPARQL queries in Rational Engineering Lifecycle Manager (including queries that are embedded in views and in artifact element definitions) use back links with an LQE index for artifacts in version 6.0 lifecycle management applications, the results of the queries might get affected on the removal of back links. To ensure that the existing queries should work with data fetched from version 6.0 applications, the queries needs to be modified for the portions that depend on back links.
  • When you create new queries that apply only to version 6.0 lifecycle management applications, query for the forward link in the forward direction.
  • If you have a mix of version 6.0 and older lifecycle management applications or third-party applications that are not yet adopted the OSLC link simplification, use the path expression a|^b in queries, where a is the forward link predicate, b is the back link predicate, and^is the inverse operator. This way, the query can redundantly but sufficiently match the forward and back links. Some additional computational cost is necessary for this redundant matching.
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:
  1. Check which version of the lifecycle management tools produced the artifacts in the LQE index
  2. Identify where back link predicates are used in views and artifact element queries.
  3. Make the changes suggested in the problem description above.
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
  1. Import the version 6 client access licenses (CALs) from the license Management page that is listed in this location: ts/admin > Server page
  2. Delete the version 5 licenses.
  3. Go to jts/admin > Users > Client Access license Management and select the Rational Engineering Lifecycle Manager user license.
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)
  1. Generate a list of licenses that are available in the version 5 product.
  2. Generate a list of users and their licenses.
  3. Import the version 6 token license and delete the old version 5 licenses.
  4. Generate the list of licenses again.
  5. Edit the file of users and licenses to change the version 5 token license entry to the version 6 entry.
  6. Import the edited file to apply the version 6 token licenses to all users who had version 5 token licenses.
Workaround: To upgrade Rational Engineering Lifecycle Manager token licenses from 5.0 to 6.0, complete these steps:
  1. Log in to the Jazz Team Server that is associated with Rational Engineering Lifecycle Manager. The user that you log in as must have Admin permissions to the Jazz Team Server and write permissions to the JazzTeamServer/server directory.
  2. Change to the JazzTeamServer/server directory. The default location is as follows:
    • Windows: C:Program FilesIBMJazzTeamServerserver
    • Linux®: /opt/IBM®/JazzTeamServer/server
  3. Run the following command:
    • repotools-jts.bat -listLicenses adminUserID=<Your_admin_user_ID> adminPassword=<your_admin_password>Windows:
    • repotools-jts.sh -listLicenses adminUserID=<Your_admin_user_ID> adminPassword=<your_admin_password>Linux:
  4. To preserve the output from version 5, rename the output log file from repotools-jts_listLicenses.log to repotools-jts_listLicenses_5.0.log.
  5. To generate a users.csv file that has a list of users and the licenses that are assigned to them, run the following command:
    • Windows: repotools-jts.bat -exportUsers adminUserID=<Your_admin_user_ID> adminPassword=<your_admin_password>
    • Linux: repotools-jts.sh -exportUsers adminUserID=<Your_admin_user_ID> adminPassword=<your_admin_password>
  6. Go to Jazz Team Server and import the Rational Engineering Lifecycle Manager version 6 user token license.
  7. Delete the Rational Engineering Lifecycle Manager version 5 user token license. Ignore the warning about the license being assigned to users and about losing information.
  8. Run the following command again:
    • Windows: repotools-jts.bat -listLicenses adminUserID=<Your_admin_user_ID>adminPassword=<your_admin_password>
    • Linux: repotools-jts.sh -listLicenses adminUserID=<Your_admin_user_ID>adminPassword=<your_admin_password>
  9. Open the repotools-jts_listLicenses.log file that was generated in step 8 and look for the Rational Engineering Lifecycle Manager user token license entry. Compare the value in this file to the value that was in the repotools-jts_listLicenses_5.0.log file.
  10. In a plain text editor, open the users.csv file that was generated in step 5.
  11. Use the find-and-replace function to change the version 5 license value to the new version 6 license value.
  12. To import the users and assign the new version 6 license, run the following command:
    • Windows: repotools-jts.bat -importUsers adminUserID=<Your_admin_user_ID> adminPassword=<your_admin_password>
    • Linux: repotools-jts.sh -importUsers adminUserID=<Your_admin_user_ID> adminPassword=<your_admin_password>
  13. Check the repotools-jts_importUsers.log file for errors. If errors exist, resolve the issues and rerun the importUsers command.
  14. Log in to jts/admin, go to theUsers > Client Access license Management page, and select the Rational Engineering Lifecycle Manager token license. The users that had version 5 licenses should now be listed under the version 6 license. Users now have the version 6 token license that is assigned and can proceed to work with the product
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.
  • For example, the version 5 license might look like this: com.ibm.team.relm.user.token.20150420_1111
  • The 6.0 license might look like this: com.ibm.team.relm.user.token

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:
  1. Open the Report Builder that defines the data source that is used in the view that reports errors.
  2. On the set up page https://server:port/rs/setup, click data sources.
  3. Click the data source that is used in the view that fails.
  4. Click Test Connection.
  5. If authentication is required, log in with the correct credentials, and click OK.
  6. Return to the Rational Engineering Lifecycle Manager view, and reload the page.opacity
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:

  1. Go to the LQE administration page: https://lqe_server_url:port/lqe/web/admin/home
  2. In the data sources section, click Manage data sources.
  3. Click the name of the product definition data source in the list.
  4. Click the Removed icon on the upper-right toolbar.
  5. Click Remove in the dialog box.
  6. Click OK to confirm that you remove the 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:

  1. Go to the LQE administration page: https://lqe_server_url:port/lqe/web/admin/home2
  2. In the data sources section, click Manage data sources.
  3. Click the name of the product definition data source in the list.
  4. Click the Pause Indexing icon on the upper-right toolbar.
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:

  1. To select the scope at the container level, right-click a node, and then click Refine Container Content > Edit Scope.
  2. From the list of project areas, select the project areas to which you want to reduce the scope, and then click OK.
  3. In the Refined Container Content window, go to the Sort tab.
  4. Select the attribute by which the artifacts are to be sorted, and then click OK.

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.