![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Archiving/Restorinig modules Topic Summary: Archiving/Restorinig modules Created On: 28-Sep-2004 16:27 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hello,
I have 3 modules (two formal and one link module) on server 1 that I want to move to server 2. The 2 formal modules are linked via the link module. There is one linkset in the link module between those two formal modules... After archiving and restoring the modules, the links are not in place on server 2. Should they be? I thought you could trade modules this way and have all of your links, too...The link module on server 2 does not have any linksets...I created the linkset b/w the two modules, but that doesn't help unless I want to re-create those links manually... Is it not possible to restore the links as I thought? Thanks, Patrick |
|
![]() |
|
![]() |
|
No. Module archives do NOT preserve any links.
You'll have to run capture.dxl to store the information about the links in the source module, then archive the modules, then restore them, then link-by-attribute to reestablish the links. - Louie Edited: 28-Sep-2004 at 19:23 by Louie Landale |
|
![]() |
|
![]() |
|
Alternatively, you could define a partition of the project containg these modules (including the link module and the relevant linksets). Give full access to the modules in the partition.
Then export the partition...this will render the modules in the partition as read-only. To get full access to the modules back, select the exported partition and hit the recover button. Now, when you import the partition on the other server, all the modules will have the links present, and full access will be available. Since the partition has been "recovered", you won't be able to "synchronise" or "rejoin" the partition, but this method is effective for quickly getting a copy of a set of modules in a project, with links. Antonio. Edited: 29-Sep-2004 at 13:04 by Antonio Norkus |
|
![]() |
|
![]() |
|
Would it not make sense to be able to simply archive the link module and restore that on your new DB?
|
|
![]() |
|
![]() |
|
When restoring an archive of a link module, the linksets are missing. When you archive a link module, all you are archiving is its name. You may as well create a new link module on the other database, for all the good the archive is giving you.
In any case, if you archive a link module, there is no guarantee that the source and target for a link is going to be present when it is restored...this guarantee is provided by project archives and project partitions...at least for links within the project. Edited: 29-Sep-2004 at 17:27 by Antonio Norkus |
|
![]() |
|
![]() |
|
Links themselves are stored in the source Formal module. The link module just houses the link-sets (as "Objects"). But when you archive the module you don't get the links (sadly).
Antonio's partition solution is a good one. IIRC there are a couple other partition commands you need to do in order to remove the partition from both the home and away database. One problem is if the away database has a link module with the same name as the one you are sending (in the same folder). For example, if by policy you put your "Requirement Links" in a link module named "Links Reqs", then you've got a partition problem, since you'll end up with two link modules. If you had some sort of "MoveLinkSet.dxl" script you could restore it, then move the links from the partition link module to the permanant one. Archiving a LinkModule not only preserves its name but also presevers its extra attributes, if you use link-attributes (which are real sticky) in your project. - Louie |
|
![]() |
|
![]() |
|
did you know that, if you change the access rights to a link module to read-only and then try to create a link using a linkset in the link module, the link isn't created. If using drag'n'drop linking, no error is reported. If using the create links dialog, an error is reported that the linkset can't be accessed.
If a link isn't stored in the link module, why does linking require write access to the link module?? I'm beginning to think that links are actually stored in the link module, though the UI and published DXL gives the illusion that it is stored in the source module. |
|
![]() |
|
![]() |
|
True, you need (IIRC) RM access to the link module. Also, the link module is actually opened for either Edit or Share WHILE you are creating the link (we've had access conflicts to prove it).
I guess they do that to control which formal modules are allowed to create links "in" which link module: Joe isn't allowed to create any Test-Links. It also may be a residual artifact of the fact that you DO need to modify the Link Module when you create your first link: the link-set object is created. - Louie |
|
![]() |
|
![]() |
|
Hi, Louie,
Where is capture.dxl? THanks! Catherine |
|
![]() |
|
![]() |
|
Here's a crude version. Notice it creates real-ugly attribute names and does NOT erase the old ones, so if you run the script twice you get duplicate entries in the attributes. You'll need to manually delete all the attributes before running the script. You'll also need to modify the script to capture outgoing links, as this one only captures incoming.
- Louie |
|
![]() |
|
![]() |
|
THanks a lot, Louie!
Catherine |
|
![]() |
|
![]() |
|
I also noticed that in the DXL Library (I'm running DOORS 7.0), there's a script called "Example to create a Text Attribute that can be used for Link-by-attribute". It looks like Louie's script will create attributes for each module that is linked to, versus running this script multiple times for each target module.
Thanks for your help, Louie and Antonio. -Patrick |
|
![]() |
Telelogic DOORS
» General Discussion
»
Archiving/Restorinig modules
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.