Remote service configuration errors

When Rational® DOORS® (not Rational DOORS Web Access) is started it connects to each remote server configured in the Remote Services window and requests each remote server’s rootservices document. If the remote server is unavailable or the information configured in Rational DOORS is incorrect, Rational DOORS Web Access displays an error message when it tries to access the remote resource.

The details that Rational DOORS Web Access needs to navigate to remote services are stored in this file: /server/festival/config/friendsconfig.rdf.

This file is automatically updated each time a user logs in to Rational DOORS Web Access. If the file is empty, or your remote service is missing, Rational DOORS Web Access cannot connect to the remote resource.

Any easy way to check is to log in to Rational DOORS Web Access, open the file and make sure that the remote servers are present. There should be an entry for each remote server in this format:
<jd:Friend>
<dc:title>some title</dc:title>
<jd:rootServices rdf:resource="a rootservices url"/>
<jfs:oauthDomain rdf:resource="some value"/>
<jfs:oauthConsumerKey>my key</jfs:oauthConsumerKey>
<jfs:oauthConsumerSecret>my secret</jfs:oauthConsumerSecret>
</jd:Friend>
If there is an entry for the remote service, and an error is still displayed, make sure that the oauthDomain attribute is populated and does not contain a blank value. If it contains a blank value, Rational DOORS connected to the remote server but failed to read the rootservices document properly.

This file is specific to Rational DOORS Web Access. Rational DOORS uses a different connection mechanism. It is possible that the Rational DOORS Web Access configuration can be invalid while Rational DOORS is able to access the remote resource.


Feedback