Administration and configuration problems

This topic describes some of the problems you may encounter when installing, administering or configuring Rational® solution for systems and software engineering.

Configuring Rational DOORS as a tracked resource set (TRS) provider

When configuring Rational DOORS® as a TRS provider you will select Tools > Configure TRS. Occasionally this causes error CRCRD7213W: Unable to update the Tracked Resource Set configuration.

To resolve this error, update any requirement and then select to configure TRS again.

Error when Configuring TRS in DOORS

When configuring the DOORS TRS provider, the following error may display when Configure TRS is selected from the Tools menu:
CRCRD7213W: Unable to update the Tracked Resource Set configuration.
This is more common when you are using a new installation of DOORS V9.5.0 or earlier with saved data from a previous installation.

To resolve the error update any requirement and attempt to configure TRS again.

Upgrading DOORS Next Generation

When you configure or upgrade the Requirements Management (RM) server, problems can occur with OAuth consumer keys that make the server unusable. Buttons in setup wizard might be disabled, or the following error might occur in the server/logs/rdm.log file: CRJZS0033E Invalid consumer key. If this occurs, see the technote Troubleshooting issues with OAuth consumer keys.

Rhapsody DM configuration different from other Jazz applications

Unlike other Jazz™ Applications, inbound consumers of Rhapsody® DM must be defined in https://servername:port/jts/admin. Do not use https://servername:port/dm/admin.

When an inbound request is made externally to Rhapsody DM, the provisional key must be approved in https://servername:port/jts/admin.

Restarting Jazz Team Server does not restart Rhapsody DM

In an environment where Jazz Team Server, Rhapsody DM and Rational Engineering Lifecycle Manager are all installed into a single JTS (using the default Tomcat and Derby on a Windows 2008 server), restarting the Jazz Team Server does not always restart the Rhapsody DM server.

You may encounter this in the following situations:
  • You cannot access the Rhapsody DM site: https://hostname:9444/dm/web
  • The https://hostname:9444/dm/admin site indicates Rhapsody DM has not been registered with a Jazz Team Server.
  • The Lifecycle Query Engine indicates that Rhapsody DM is not a TRS provider: https://hostname:9444/lqe/web/admin/data-sources

Ensure that Rhapsody DM is properly configured by going to the Jazz Team Server > Configuration > Registered Applications page: https://hostname:9444/jts/admin. There should be a Design Management entry.

Confirm that Rhapsody DM has been started by going to the https://hostname:9444/jts/admin site and going to the Application Administration section and searching for Design Management. If the Design Management section says it is undefined or it does not appear at all, restart the Jazz Team Server.

Model artifacts fail to load after a Rational Rhapsody model is imported into Rhapsody DM

If you import a Rhapsody model into Rhapsody DM you might see an error message when you attempt to open the model artifact. The Rhapsody Systems Domains project area might be missing a Documentation Domains or Configuration Management Systems Domains dependency.

  • Associate the Documentation Domain to the Project area if it is an actively managed project.
  • Associate the [System Defined] Domains in Configuration Management for an externally managed project.
    Adding a dependency to a project
    Adding the System Domain dependency
    Adding the System Domain dependency

Logging out results in a WebSphere Application Server error message

If you are running WebSphere® Application Server and you log out of Rational Engineering Lifecycle Manager, you may get the error message SESN0008EA: user authenticated as anonymous has attempted to access a session owned by user..."..

Enable the fix on WebSphere Application Server (V8.0.0.3 or later) by adding a custom session manager property. Click Application servers > server1 > Session management > Custom properties and add the InvalidateOnUnauthorizedSessionRequestException = true custom property.

Alternatively, if you close the browser window rather than explicitly logging out, the session eventually times out on its own.


Feedback