Workarounds and Limitations: Known issues in IBM Engineering Lifecycle Optimization – Engineering Insights 7.0
The following known problems are related to this release.
Workarounds
The following problems in this release have workarounds:
- In the Sort tab, attributes from other project areas are displayed
- Text in a node displays outside the container border
- For third party applications, the preview of the artifacts is not getting displayed in the views
- After an upgrade, data might not load in some RELM (now known as Engineering Insights) views
- Full-text search indexes must be rebuilt when you upgrade to 6.0.6.1 or later
- After an upgrade, users might not have the required impact analysis management permissions
- Updating the CE4IoTConnector base URL requires a restart of the IOTP application
- Parameter changes in custom artifact elements are not reflected in views
- Filters cannot be set in the Set Scope and Conditions dialog box when RELM (now known as Engineering Insights) and Report Builder are on different servers
- If you use the default settings, Design Management and Asset Management data are not visible in RELM (now known as Engineering Insights) views
- If the view data source is Lifecycle Query Engine using Configurations, queries that result in a large number of artifacts might fail
- The removal of back links might affect queries and views that were created before version 6.0
- Upgrading Rational Engineering Lifecycle Manager (now known as Engineering Insights) token licenses from a version 5 to version 6 release requires extra steps
- 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
- When you upgrade from version 5.0.2 or earlier, a Lifecycle Query Engine error indicates a problem with the product definition tool
Limitations
The following problems in this release do not currently have workarounds:
- Incomplete data is loaded within the container in the ENI views due to the size limit of the LQE result set
- Known issue in translated versions of ELM 7.0 documentation
- In views, you cannot show links between Rational DOORS Next Generation (now known as IBM Engineering Requirements Management DOORS Next) and IoT artifacts
- After a server rename, artifacts in snapshots of views still have the old server URL
- Java 8 SR5 Fix Pack 5 through Fix Pack 10 is not supported as the runtime for CE/CLM applications on a Windows platform
- Matrix reports can no longer be generated in CSV format
Workarounds
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 Refine 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
Related information
Work Item 496132
Text in a node displays outside the container border
First occurrence
7.0
Problem
Steps to recreate the problem:
- Open an Internet Explorer V11 web browser.
- Log in to IBM Engineering Lifecycle Optimization – Engineering Insights. The URL is https://<server>:<port>/relm/web, where <server> is the fully qualified domain name or localhost and the context root is /relm/web. For example, in the Internet Explorer V11 web browser, type the address:
https://localhost:9443/relm/web - Open an existing view that has node data.
- In the toolbar, click the Zoom to fit button.
- In the toolbar, click on 100% button.
Workaround
Move the mouse pointer over the container node and the text no longer displays outside the container border:
296414
Related information
488231
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 required to be added as a friend in ENI.
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 latest artifacts from the palette.
Related information
Work Item 474469
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 Rational Team Concert 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 repotools-<app> -rebuildTextIndices command after the upgrade is complete, but before you start the server, where <app> is one of am, ccm, or qm. Note that 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 ensure 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 pathname), 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 (using repotools) or the online procedure (ensuring that the full-text index folder is empty before starting the server) must be performed on each node in the cluster.
The Rational Team Concert Client for Eclipse maintains a local full-text search index for the Team Artifact History view. When you upgrade the Rational Team Concert Client for Eclipse to version 6.0.6.1 or later, the full-text search index is automatically deleted, which means the artifact history is cleared and will accumulate artifacts again after the upgrade.
For ELM servers, complete one of these steps:
For online background indexing, no action is required except to ensure that the full-text index folder is empty before you start the server.
For offline indexing, before you start the server, run the appropriate repotools-<app> -rebuildTextIndices command.
After an upgrade, users might not have the required impact analysis management permissions
First occurrence
6.0.6.1
Problem
After you upgrade Rational Engineering Lifecycle Manager, users might not have the required impact analysis management permissions, such as to create, modify, or delete impact analysis diagrams, filters, and profiles.
Workaround
Administrators must assign the required impact analysis management permissions to users. Administrators set these permissions in the Rational Engineering Lifecycle Manager project area administration section, on the Permissions page.
Related information
Work Item 477273
Updating the CE4IoTConnector base URL requires a restart of the IOTP application
First occurrence
6.0.6
Problem
Starting in 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.
Related information
Work Item 481461
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:
- For the custom artifact element parameters that are already used in the view, set the value type to Not Used.
- Delete the settings under Parameter Value.
- Save the view.
- Clear the browser cache and reload the view to pick up the changed parameter details.
Work Item 465072
Filters cannot be set in the Set Scope and Conditions dialog box when RELM (now known as Engineering Insights) and Report Builder are on different servers
First occurrence
6.0.2
Problem
When Rational Engineering Lifecycle Manager and Report Builder are installed on different Jazz Team Servers, you might not be able to set filters in the “Set Scope and Conditions” dialog box when you add artifacts from the palette onto the view canvas. The following message is displayed: The content was blocked because it was not signed by a valid security certificate.
This problem occurs because a security certificate for your Jazz Team Server was not installed on your browser.
Workaround
Follow this link to install the security certificate: Installing a security certificate.
Related information
Work Item 383179
Configuring security certificates
Configuring security certificates for Report Builder servers
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 do not 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 page http://<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 will have access to the resources. To grant all LQE users permission to access the resources, select Everyone.
4. Click OK to save your settings.
Related information
Design Management 6.0.1 support for the OSLC access control specification is tracked in this work item: 46014: [DM] Adopt new Access Control 2.0 specification for TRS
Rational Asset Management 7.5.2.3 support for the OSLC access control specification is tracked in this work item: CQPAR00080035 RAM supports ACP 2.0
If the view data source is Lifecycle Query Engine using Configurations, queries that result in a large number of 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::Please use appropriate ‘<size>’ via -XX:MaxDirectMemorySize=<size>.
This error is triggered by a defect in Java run time 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 using the WebSphere Application Server Integrated Solutions Console as follows:
1. Click the JRS server in Servers > 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.
Related information
IV74043: INCREASE IN THE NUMBER OF SYSTEM.GC() CALLS AFTER APPLYING IV687 43
Work Item 99731
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, Rational Team Concert, 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 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 be affected by the removal of back links. To ensure that existing queries work with data coming from version 6.0 applications, the queries must 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 have 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. Note that some additional computational cost is required 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:validatesRequirement ?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:validatedBy link, use the following property path:
?testCase (oslc_qm:validatesRequirement|^oslc_rm:validatedBy) ?requirement
Note that your queries might run slower, and you might find duplicate results that require further adjustment.
Workaround
Complete these 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.
Related information
Work Item 356471
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: jts/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
- 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>
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>
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>
10. In a plain text editor, open the users.csv file that was generated in step 5.
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.
11. Use the find-and-replace function to change the version 5 license value to the new version 6 license value.
- 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
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 the Users > 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 assigned and can proceed to work with the product.
Related information
Work Item 353640
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 used in the view that reports errors.
2. On the Setup page https://server:port/rs/setup, click Data Sources.
3. Click the data source 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.
Related information
Work Item 343789
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 indices periodically, and logs the errors.
Workaround
To avoid the error, complete one of these workarounds.
Workaround 1
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 Remove 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/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 Pause Indexing icon on the upper-right toolbar.
Related information
Work Item 355905
Product configuration tree moved from Rational Engineering Lifecycle Manager 6.0
Limitations
Incomplete data is loaded within the container in the ENI Views due to the size limit of the LQE result set
First occurrence
7.0
Problem
ENI sends SPARQL queries to LQE and the result-set that is returned is displayed in the container.
The permissible size of the result-set from LQE is the maximum of the two values: Actual result of the SPARQL query or the value of Query Result Set Limit parameter.
Therefore, when the size of the actual result of the SPARQL query is more than the value of the “Query Result Set Limit“, LQE does not return the complete result-set of the SPARQL query.
And, this scenario causes incomplete data in the container within the ENI Views.
Note: The default value of Query Result Set Limit is 3000 records.
Known issue in translated versions of ELM 7.0 documentation
First occurrence
7.0
Problem
- The table of contents for ELM 7.0 documentation on IBM Knowledge Center (KC) might display long navigation titles in place of short titles for content in languages other than English.
- The pre-release header is visible on the translated pages of ELM documentation on IBM KC.
Task 496011
In views, 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.
Related information
Work Item 452491
After a server rename, artifacts in snapshots of views still have the old server URL
First occurrence
6.0.5
Problem
After a server rename, artifacts in snapshots of views still have the old server URL, which means you cannot perform any actions on those artifacts. For example, you can’t open, view the properties, or run an impact analysis on the artifacts.
Related information
Work Item 465728
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
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.
Related information
Work Item 355524
© Copyright IBM Corporation 2020
Yes
