![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Migrating 5.2 to 7.0 Topic Summary: Created On: 31-Mar-2004 13:00 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi,
I am currently working with v5.2 database and thinking about migrating to v7.0. Has anyone come across any problems with this? or is it a straight-forward process? Thanks, Arlene |
|
![]() |
|
![]() |
|
The answer to your question depends on what you define as straightforward and what DXL's you currently use.
To migrate your database, all you need to do is: 1. Stop the v5.2 database server 2. Install v6.0 database server, pointed at the v5.2 data 3. Start a v6.0 client, enter the Administrator password when prompted. 4. Stop the v6.0 database server 5. Install v7.0SP1 database server, pointed at the (now) v6.0 data 6. Start a v7.0SP1 client, enter the Administrator password You are now migrated. There is some discussion about whether or not you need to run a script called "module_migrator" between v6 and v7 (available through the Telelogic web site). According to Telelogic support, you don't need to do that. According to user experience, you may get better performance in v7 if you do run the script. My experience is that it doesn't hurt to run the script, but it takes a long time to run. All the script does is open every module and save it. If you don't run the script, the first time you open in v7 it will take longer (until you save it). The other issue you will face is related to OLE objects. If you have any custom DXLs that manipulate OLE objects, they will need to be changed. The upgrade from v5 to v6 changed the way OLE objects are implemented in DOORS. In v6 and later, the OLE objects are part of the RichText. Therefore, there are DXL functions available to get text with or without the OLE. The scripts that some people used to remove rich text markup (to clear out unknown markup) now remove graphics. I hope this helps, Brian Azelborn |
|
![]() |
|
![]() |
|
Ensure that you have the latest version of 7 SP1, i.e build 70214, it fixes some important bits!
------------------------- Graham Stradling, Alcatel-Lucent. |
|
![]() |
|
![]() |
|
Arlene,
I made the jump from 5.2 to 7.0 SP1 Build 70214 two months ago. I did not have any problems other than a few DXLs needing to be fixed. I did run the module migrator script to complete the migration to DOORs v6 and was told by support that it was necessary. Make sure you have a backup of your data folder just incase something does go south. Adam |
|
![]() |
|
![]() |
|
We migrated to 7.0 just less than a month ago. We followed the same path as above and experienced no real problems.
Today I got an email from one group of users listing their problems with DOORS 7. Any comments/suggestions on what to tell them? I will say this is the first time I've heard of any of this except for issue 2. 1) Unable to Export SRD's to MS-Word - Un-recoverable errors start appearing about 1/3 of the way through the export process. 2) OLE Objects - There are several issues regarding OLE objects including sizing problems, viewing and editing problems. 3) Views - Exclusive write access to views. I created an ICD_Document view but when I published it, it becomes locked and others cannot modify it. Is this the correct behavior? 4) System Slow-Down - There appears to be a system slow-down occurring in Doors. Is this related to an increase in users, an increase in functionality in Doors 7, or an intranet throughput issue? Thanks Wayne ------------------------- Wayne Sanders-Unrein Honeywell Aero Electronics Olathe, KS, USA |
|
![]() |
|
![]() |
|
Hi Arlene,
I've performed 4 seperate migrations from DOORS 5.2 to DOORS 7SP1. W.r.t. the issues listed by Wayne Sanders-Unrein in his posting. 1) This could be due to the "doors.dot" file not being replaced when a DOORS 7 client is installed on a PC that already has a DOORS 5.2 client. I've experienced mixed results with this, on most occasions it gets the DOORS 7 installation replaces the old file. However, if your company has been in the habit of altering MSWord properties associated with where template and start-up files should be located, the DOORS 7 installation may not be able replace the original. 2) I agree with this - DOORS 7 has some OLE sizing commands under the Module Tools>Support Tools menu item. I've had mixed and "clunky" results with using these. 3) DOORS 7 has introduced the concept of Public and Private Views. The access rights of views are maintained when you migrate, but as soon as you save over an existing view, the view will default to being a Public view and will be owned by the person who saved the view. This can catch users out as they were previously used to being able to modify and save over views that previously may have had inherited rights. 4) Can't say that I've noticed anything major here, although I havn't performed a migration without using the migrator script that was recommended when migrating from v5.2 to v6.0 (Brian Azelborn mentions this in his post above). Something that I have experienced is problems with RTF control words. DOORS version 6 was the start of DOORS becoming more compliant with the Rich Text Format (RTF) standard which is owned by Microsoft. I have seen cases where the font and paragraph settings of text appear quite differantly when migrated from version 5.2 to version 6 and these carry over to version 7. In some cases, the previously hidden text markup characters that version 5.x used now appear in the text or they appear when you export to MSWord. I've reported this to Telelogic (no response as of yet). The pattern seems to be that these RTF problems are confined to modules where the origin of objects was from an export from MSWord to DOORS. ------------------------- 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 |
|
![]() |
|
![]() |
|
Paul
Here is a little more info on our situation. As far as item 1. Telelogic has accepted it as a bug and opened a case: 2040553. They have two files that duplicate the problem. As of yesterday I now have 3. 2. "Clunky" is nice way to put it. 3. After I explained it to them, they seem to have accepted this one. For item 4. Only one group of users is complaining about performance. They say they see 30 to 40 second open times on documents where I see 6 to 7. Still looking at this one. (I did use the migrator script going from 5.2 to 6.) ------------------------- Wayne Sanders-Unrein Honeywell Aero Electronics Olathe, KS, USA |
|
![]() |
|
![]() |
|
Wayne,
We are in the process of upgrading to 7.0 ... 5.2 is so slow, can take up to 1 min to open a module. We are hoping for a performance improvement with 7.0 - How large is your client base? How many projects are in your database and how many concurrent users do you have on any one point in time? We are win2000 platform, have over 500 projects active in the database, a client base of 3000, with 52 concurrent users on at a time. How long did it take you to copy your database? Last copy I ran took over 10hours! What method did you use to do the copy? Thanks, Maryanne Sprint -KC |
|
![]() |
|
![]() |
|
Not sure this is the place to discuss all this. Email me at wayne.sanders-unrein@honeywell.com and I'll try to answer your questions.
------------------------- Wayne Sanders-Unrein Honeywell Aero Electronics Olathe, KS, USA |
|
![]() |
Telelogic DOORS
» General Discussion
»
Migrating 5.2 to 7.0
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.