![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: How to move projects to new server Topic Summary: Created On: 19-Jul-2005 14:09 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
We are putting in place a Citrix based DOORS system and need to move projects from their existing site servers to it.
The DOORS documentation says it is best to use partitions, as archives loose access rights, CPS and links. I believe the process is - Setup the partition on old - Export the partition from old - Import the partition on new - Return the partition from new, ensuring Keep the imported data is ticked This should, I think, makes it look like the data was not from another database. Has anybody got advice/guidance on this? |
|
![]() |
|
![]() |
|
You definately don't want the project in two locations. Partioning used to be a nightmare and I doubt the user access rights move over since they are user-ID based and not user name based. I assume you intend to re-host one of your projects and then remove it from the old location.
I would copy the entire database over to the new location, then remove the Users and the Projects that you don't want. Also remove the Users and the Project from the old location. The hard part is the Users and the hard part of that is knowing which users are [1] exclusively associated with the to-be-moved project, and [2] which users are associated with this and some other to-stay-behind project. - Louie |
|
![]() |
|
![]() |
|
We cannot copy the whole database as we have 4 DOORS servers that are being consolidated into one.
|
|
![]() |
|
![]() |
|
Then you've got a big problem. User access rights are disaster when transfering stuff between databases. I'd hire someone to write a pair of Sister DXL [1] one dumps the user names and access rights of everything in the project to a text file [2] one reads the text file and applies the access rights. These should work so long as the target database has all the same user NAMES as the source databases. This suggests you'll need another pair of DXL [1] one dumps the user info to a file [2] read the user text file and create users with that name, system name and attributes etc.
Good luck. - Louie |
|
![]() |
|
![]() |
|
Hi Richard
Apart from the problems raised by Louie - if you have any DXL Layout or DXL Attribute scripts that have used the unique Item ID's allocated by the DB to identify specific modules, these will not work in the target DB as it will have allocated new unique Item ID's. If the Analysis Wizard has been used to create trace columns configured to use specific Link and\or specific Formal modules, it will use unique Item ID's that only have relevance to the current DB and will not work in any other DB. There is a tedious solution to this but rather than bore you with the details here, please send me an email if this is something you will need to counter. ------------------------- Paul Miller Specification Practices Specialist, EuroCyber, Melbourne, Australia. Mobile: +61 (0)418 135 103 Web Site: http://www.eurocyber.biz E-mail: miller@eurocyber.biz">pmiller@eurocyber.biz Edited: 12-Sep-2005 at 23:45 by Paul Miller |
|
![]() |
|
![]() |
|
Richard,
You mentioned you were consolidating 4 DOORS servers into one. This should not stop you copying each DOORS server database to a seperate folder on the single server and setting up different port addresses for each database. Unless of course you wish to consolidate the databases? I agree with Louie and have previously copied the entire database to the new server and deleted what we don't need. Martin ------------------------- - Martin Edited: 21-Sep-2005 at 15:35 by Martin Hunter |
|
![]() |
|
![]() |
|
If the disparate servers are using different LDAP dbs, then you could do an LDAP merge rather then the scripting that Louie suggests? Then bring each db as a partition as you suggest.
------------------------- Graham Stradling, Alcatel-Lucent. |
|
![]() |
Telelogic DOORS
» Administration
»
How to move projects to new server
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.