Workarounds and Limitations: Known issues in IBM Rational Engineering Lifecycle Manager 6.0.3

The following known problems are related to this release.

Workarounds

The following problems in this release have workarounds:

Limitations

The following problems in this release do not currently have workarounds:


Workarounds

In views with hidden containers, you must save and refresh the view before the artifacts in new containers load


First occurrence
6.0.3

Problem
In views, you can create links between multiple containers by using the Show Links To wizard or the Link Settings dialog box.

Consider an example that shows links between containers C-1, C-2, and C-3:
  • You can hide container C-2 to show direct links between C-1 and C-3.
  • However, container C-2 does not load properly when you try again to create links between C-1 and C-2.
  • If the C-2 container is hidden, and you want to link C-1 to a new requirements container, the new container doesn’t load.

Workaround
Complete these steps:

1. Save the view.
2. Click the Reload icon to refresh the view.

Related information
Work Item 403550

Back to top


Links between containers might not load if you select Show Linked Nodes Only


First occurrence

6.0.3

Problem
In views, you can create links between containers by using either the Show Links To wizard or the Link Settings dialog box. When you right-click the link between the containers and select Show Linked Nodes Only, the container might not load.

Workaround
If you click Show Linked Nodes Only, save and refresh the view to see the artifacts in the container:

1. Save the view.
2. Click the Reload icon to refresh the view.

Related information
Work Item 396550 

Back to top


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

Back to top


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

Back to top


Limitations

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

Back to top


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