Workarounds and Limitations: Known issues in IBM Rational Engineering Lifecycle Manager 6.0.6
The following known problems are related to this release.
Workarounds
The following problems in this release have workarounds:
- Updating the CE4IoTConnector base URL requires a restart of the IOTP application
- Device artifacts cannot be created from the CCM or RM applications
- Parameter changes in custom artifact elements are not reflected in views
- Licensing errors might occur if you upgrade the Java environment or upgrade applications to version 6.0.5 or later
- Data warehouse settings are not preserved in the teamserver.properties file after an upgrade
- When Rational Engineering Lifecycle Manager is installed through IBM Installation Manager, you can’t change the context root value for RELM
- Filters cannot be set in the Set Scope and Conditions dialog box when RELM and Report Builder are on different servers
- If you use the default settings, Design Management and Asset Management data are not visible in Rational Engineering Lifecycle Manager views
- If the view data source is Lifecycle Query Engine using Configurations, queries that result in a large number of artifacts might fail
- View widgets are not displayed on the dashboard
- Upgrading Rational Engineering Lifecyle Manager 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 migrate existing queries to Report Builder 6.0 or later, the URIs in the query results show plain text instead of hyperlinks
- When you upgrade from version 5.0.2 or earlier, a Lifecycle Query Engine error indicates a problem with the product definition tool
- The removal of back links might affect queries and views that were created before version 6.0
Limitations
The following problems in this release do not currently have workarounds:
- In views, you can’t show links between Rational DOORS Next Generation and IoT artifacts
- Links and associations to IoT artifacts cannot be added from the RM, CCM, or QM applications
- After a server rename, artifacts in snapshots of views still have the old server URL
- Java 7.1 SR4 FP10 is not supported
- Java 8 SR5 Fix Pack 5 through Fix Pack 10 is not supported as the runtime for CE/CLM applications on a Windows platform
- Impact analysis is inaccessible after a server rename
- Matrix reports can no longer be generated in CSV format
Workarounds
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
Device artifacts cannot be created from the CCM or RM applications
First occurrence
6.0.6
Problem
If you use the CE Connector for IoT, you can link IBM Watson IoT Platform device artifacts with work items and requirements. However, if you try to create device artifacts from the Change and Configuration Management (CCM) or Requirements Management (RM) applications, the operation fails.
Workaround
Create the device artifact by using the IBM Watson IoT Platform:
1. Log on to the IBM Watson IoT Platform.
2. Go to an organization.
3. Create a resource of the type Device.
Related information
Work Item 459622
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
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.
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.
- Log in to Jazz Team Server, go to jts/admin > Server > License Key Management and note all the licenses on the server.
- In IBM Rational License Key Center, under License Management, click Return Keys.
- Click the product link that you want to return the license keys for, and then click Return.
- After the license is returned, click Get Keys.
- Click the product link to generate licenses for.
- When prompted, provide the required information and click Generate.
- Download the file that contains the new licenses.
- Log in to Jazz Team Server, go to Server > License Key Management and reimport the new license files.
- To add a license, click Add, accept the license agreement if you agree to its terms, and then complete the steps in the wizard.
- Log in to Jazz Team Server, go to jts/admin > Server > License Key Management and note all the licenses on the server.
- In IBM Rational License Key Center, go to View keys by host or View keys by user.
- Enter the information about the host or the user.
- Select the product to generate the license for.
- Click View Licenses for Selected Product Lines.
- Select the license and click View Details.
- Click Download Keys.
- Log in to Jazz Team Server, go to Server > License Key Management and reimport the new license files.
- To add a license, click Add, accept the license agreement if you agree to its terms, and then complete the steps in the wizard.
Related information
IBM Rational License Key Center
Interactive Upgrade Guide
Oracle release note: Restrict JARs signed with weak algorithms and keys
Data warehouse settings are not preserved in the teamserver.properties file after an upgrade
First occurrence
6.0.4
Problem
When you upgrade Rational Engineering Lifecycle Manager, the data warehouse settings are not preserved in the teamserver.properties file.
Workaround
Copy the data warehouse settings from your existing version of Rational Engineering Lifecycle Manager to the teamserver.properties file in the new installation.
Related information
Work Item 458690
When Rational Engineering Lifecycle Manager is installed through IBM Installation Manager, you can’t change the context root value for RELM
First occurrence
6.0.3
Problem
When you install Rational Engineering Lifecycle Manager through IBM Installation Manager, you can’t change the context root value of RELM. To edit the default value, you must change it manually.
Workaround
If you do not want to use the default context root value for RELM, complete these steps to change it manually. In this procedure, <new_relm_context> represents the new context root value for RELM.
1. Install RELM with the default context root value: relm
2. Go to the <CLM_install_dir>/server directory.
3. Rename the repotools-relm.batch file to repotools-<new_relm_context>.batch.
4. Go to the <CLM_install_dir>/server/upgrade directory.
5. Rename the relm folder to <new_relm_context>.
6. Edit the CLM server template entries by completing the following steps:
a. Go to the <CLM_install_dir>/server/liberty/clmServerTemplate/conf directory.
b. Open the application.xml file and search for the following entry:
<application type=”war” id=”relm” name=”relm” location=”${server.config.dir}/apps/relm.war”></application>
c. Edit the entry as shown and save the file.
<application type=”war” id=”relm” name=”<new_relm_context>” location=”${server.config.dir}/apps/<new_relm_context>.war”></application>
d. Go to the <CLM_install_dir>/server/liberty/clmServerTemplate/apps directory.
e. Rename the relm.war.zip file to <new_relm_context>.war.zip.
7. Edit the RELM configuration entries by completing the following steps:
a. Go to the <CLM_install_dir>/server/conf/relm directory and edit the teamserver.properties file.
• Change the value of the com.ibm.team.repository.db.jdbc.location key to conf/<new_relm_context>/derby/repositoryDB.
• Change the value of the com.ibm.team.fulltext.indexLocation key to conf/<new_relm_context>/indices/workitemindex.
b. Go to the <CLM_install_dir>/server/conf/relm/provision_profiles directory and edit the following files:
• In the profile.ini file, change the value of the url key to file: <new_relm_context>/sites/update-site.
• In the relm_profile.ini file, change the value of the url key to file: <new_relm_context>/sites/ com.ibm.relm.updatesite.
• In the relm-repotools-profile.ini file, change the value of the url key to file: <new_relm_context>/sites/ relm-repotools-updatesite.
8. Go to the <CLM_install_dir>/server/conf directory.
9. Rename the relm folder to <new_relm_context>.
10. Start the CLM server.
11. Run the express or custom setup.
RELM is ready to use with the new context.
Related information
Work Item 477200
Filters cannot be set in the Set Scope and Conditions dialog box when RELM 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 Rational Engineering Lifecycle Manager views
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 the 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
View widgets are not displayed on the dashboard
First occurrence
6.0.1
Problem
Rational Engineering Lifecycle Manager view widgets are not displayed on dashboards on a remote Jazz Team Server, because of a security option that is set to avoid clickjacking. View widgets work only if the view content is on the same system as the dashboard. This problem occurs in two situations:
- When Rational Engineering Lifecycle Manager is registered with a Jazz Team Server that runs on a different web server from the dashboard (JTS1 in the following instructions)
- When the view widget is in a dashboard on a remote Jazz Team Server (JTS2 in the following instructions)
Complete these steps:
On JTS1, configure the JTS2 URL as value of the Application X-Frame-Options property. This means that JTS2 can render JTS1 resources in a frame or an iframe, and access these resources.
1. Go to the JTS1 administration page https://jts1_server_url:port/jts/admin.
2. Click the Server menu.
3. In the Configuration section, click Advanced Properties.
4. Set the Application X-Frame-Options property value to ALLOW-FROM https://jts2_server_url:port, and click Save in the upper right of the page. The default value is SAMEORIGIN.
Because the Google Chrome browser does not support the ALLOW-FROM value, use any other browser to set the X-Frame-Options property to ALLOW-FROM to embed Rational Engineering Lifecycle Manager resources into a frame. After saving your configuration, you can access the site by using the Chrome browser.
5. Go to the dashboard, and click the Log in link in the Rational Engineering Lifecycle Manager view widget. Enter your user name and password, and log in.
6. Close the login window by clicking Close on the title bar.
7. Refresh the view widget by clicking Refresh in the widget menu. (Do not click Log in again.)
Related information
Work Item 373420
RFC 7034 – HTTP Header Field X-Frame-Options
Clickjacking – OWASP
Upgrading Rational Engineering Lifecyle Manager token licenses from a version 5 to version 6 release requires extra steps
First occurrence
6.0
Problem
Rational Engineering Lifecycle Manager 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 migrate existing queries to Report Builder 6.0 or later, the URIs in the query results show plain text instead of hyperlinks
First occurrence
6.0
Problem
If you migrate your Rational Engineering Lifecycle Manager queries to Report Builder 6.0 from version 5.0.2 or earlier, the URI values in the query results are in text format. In version 5.0.2, the URIs in query results are hyperlinks.
Workaround
Complete these steps:
1. Open Report Builder, and edit the report produced by the Rational Engineering Lifecycle Manager 5.0.2 query that was imported to the Report Builder.
a. Go to Format results > Advanced.
b. Add or modify the label variable <ui_variable_name>_title (for example, ?resource_title for ?resource) for the URI that should be a hyperlink.
c. Click Validate query.
d. Expand the Columns section, and change the type of the URI variable to URI (Uniform Resource Identifier).
2. Save and run the report.
Related information
Work Item 352279
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 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
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
Limitations
In views, you can’t show links between Rational DOORS Next Generation and IoT artifacts
First occurrence
6.0.6
Problem
You can create links between Rational DOORS Next Generation 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
Links and associations to IoT artifacts cannot be added from the RM, CCM, or QM applications
First occurrence
6.0.6
Problem
In the Requirements Management (RM), Change and Configuration Management (CCM), and Quality Management (QM) applications, you cannot add links or associations to IoT artifacts. If you want to deploy the CE Connector for IoT, contact IBM Software Support.
Related information
Work Item 460011
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 7.1 SR4 FP10 is not supported
First occurrence
6.0.5
Problem
Internet of Things Continuous Engineering applications that run on WebSphere Application Server Liberty (16.0.0.4 and 17.0.0.2) and that are configured with JRE 7.1 SR4 FP10 might crash. By default, versions 6.0.5 and later include a Java version that is stable.
Related information
Work Item 439584
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
Impact analysis is inaccessible after a server rename
First occurrence
6.0
Problem
After a Rational Engineering Lifecycle Manager server rename, you cannot work with impact analysis diagrams, filters, or profiles.
Related information
Work Item 454851
Work Item 455085
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 2019
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means.
Learn more here.
Yes