Pinned topic DOORS 9.x and RDS
bit of background - we are trying to upgrade to DOORS 9.latest and also attempting to utilise RDS - here is what we have installed:
Rational DOORS_Server_9-2-0-3 on Linux
Rational RDS_Server_5-1-0 Linux Tivoli
OS Redhat Linux 5.2
What did we do then - started the database, logged in as DOORS Administrator and set it to use the RDS in corporate mode and logged off. Then we tested and used it with some users from the corporate AD and tested some of our use cases etc / the usability / functionality. So far so good.
The problem we have - How do you login as DOORS Administrator again? Have no user in our corporate AD we are allowed to use as such - as you can imagine. There is no user to map - or is there? Should we create one?
What we did then - RTFM - ok, nothing there - Place PMR with IBM - 2 days later and we have some emails but no solution - yet - I thought I place this here to see whether anybody encountered and solved the same problem.
Thanks in advance
SystemAdmin 110000D4XK346 Posts
Miky1234 2700011EE71 Post
_KevConroy_ 270001WEWJ1 PostACCEPTED ANSWER
Re: DOORS 9.x and RDS2010-08-13T09:54:27Z in response to Miky1234As Miky1234 says, "Administrator" always works, as it's the fail-safe user account and password incase RDS breaks! It will work no matter what you do. You need it to start and stop the doorsd service anyhow...
The OP did better than I did - I enabled RDS and now the access rights are all broken. The old groups and old users, even though the names exist in RDS Tivoli, do not have the access rights they used to have. Even when the users do get in, they can't edit the views they had set up before.
I'm now going to remigrate and export the user list and group XMLs and try and import those to RDS, but I'm not sure its going to help..
sekrbo 270006AEE05 PostsACCEPTED ANSWER
Re: DOORS 9.x and RDS2013-10-02T09:36:45Z in response to SystemAdmin
The Administrator account is always there, whether or not you use RDS. However, the question is, did you set up DOORS to use system user name as well? In that case you should first have associated the Administrator account in DOORS with a system user, and then it should be fine. If this is the problem then support will be able to help you setting this back to using "regular" log in again. If it's not the case you could always try starting DOORS with the parameter -user (-u) and -password (-P)...