Troubleshooting
Problem
Invalid resource URI due to artifact attribute creation or update during user re-authentication can result in artifacts not being displayed in IBM Rational Requirements Composer.
Symptom
Steps to reproduce:
- Go to manage project properties
- Click on either artifact types/artifact attributes/artifact data types
- Click create new
- Before you press save, clear the active logins and browser cookies
- Press save
Actual Result: An error is thrown.
Cause
Invalid resource URI in type system: https://server:port/rm/types?oauth_token=7b91a6c6d0634b19aa1e7d74f9b374…
Due to an issue where an OAuth authentication token can get injected into the rdf:about property for certain RRC types resources, these affected types will become inoperable, and in many cases will disappear from the list of types within the Manage Project Properties section of RRC.
Subsequently, any other types within the type system which also reference the affected type can become inoperable, and any artifacts which reference any of these affected types may also have problems loading attribute data in the browser. In order to prevent OAuth authentication tokens from getting injected into type data, the RRC defects RRC projects unusable with artifact access and artifact type system problems (73081) and Invalid resource URI with oauth token (86820) have been filed and addressed in the RDNG (Rational DOORS Next Generation) 5.0 release.
An additional side-effect of OAuth tokens being injected into type data is that the main types "Storage Area resource" can get overwritten with invalid data. When this happens, the process which handles indexing data within the Types Storage Area will no longer be able to index data properly, and thus any types modified after this point will be removed from the index (even though the modified data will still be written to the database properly) and will not be re-added to the index, thus causing the affected types to become inaccessible by the application. In order to correct the Storage Area resource, a recreate storage area must be performed.
Diagnosing The Problem
Please contact IBM Support so we can assess the situation and provide a diagnostic tool to confirm the diagnostics.
Also follow the steps below to provide information on the "Storage Area resource":
- Log in to https://server:port/rm/rmadmin.
- Through Advanced Properties, set com.ibm.rdm.fronting.server.debug.enabled to true
- Navigate to the Debug Service page
- Enter the URL https://server:port/jts/storage/com.ibm.rdm.types in the URL input box on this page.
- Report the output back to IBM Support.
Resolving The Problem
Depending on the OAuth issue encountered, as described in the Cause field above, the issue can be resolved by running the diagnostic tool on repair mode. Instructions on how to do this are included in the README file of the tool that will be sent by the support engineer to you.
If the issue involves OAuth tokens being injected in the main types of the Storage Area resource", a recreation of storage areas, including online reindex will be required.
Steps:
1. Log in to https://server:port/rm/rmadmin
2. Go to the Storage Areas page.
3. Click the Reconfigure Storage.
An additional step might be required if the above steps don't resolve the problem:
Refresh the types feed cache by accessing https://server:port/rm/types?resourceContext=[projectUrl]&refreshTypeFe…
Related Information
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21683846