![]() |
Telelogic System Architect (steve huntington) | ![]() |
Topic Title: Migrating to SA V11 Topic Summary: Steps needed to migrate to SA V11 Created On: 22-Apr-2008 14:17 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi,
Planning to test migration process from SA V10.7 to SA V11 on a test server. We already have old copies of databases + catalog database on test server (not LM). But plan to move current/latest databases + catalog database over to test server. Has any one already done this? 1. Were there any problems copying the catalog database over to test server? Did you use database copy/backup/restore or catalog--> copy? 2. Could you use the old license file or did you need a new temporary license file? Or did you use 2 temporary versions. one for SA V10.7 an one for SA V11? 3. What files did you have to manually remove after the un-install? 4. Did you encounter any hiccups? Any informations or step by step process details would be appreciated (by all). Thanks. Arif Hussain |
|
![]() |
|
![]() |
|
Done it.
1. No problems in copying the catalog database over to test server, as long as you have you have not modified the standard roles. In that case use Catalog Manager to export the roles accross. 2. The same license file works for both SA V10.7 and SA V11 3. Saving/protecting files No need to do anything with Sa2001.ini. The usrprop.txt and usrmatrx.xml were in the database, so no need to worry. The autoexec.sty can be in the database or a global one, so need to worry. That just leaves the macros/reports/termplate directories in SA and Reports/Stylesheets/Templates directories in SA/Publisher, which ordinary users would/should not change. As long as the administrator keeps his setting in a safe place, there should be no problems. 4. No hiccups, even the SA SOA add-on installed with any problem. We did have to manually attach the macros to see the added menu. Did not notice any improvement in the SVG area. |
|
![]() |
|
![]() |
|
Has anyone successfully migrated to V11, where DOORSlink is involved. I had an data loss incident with DOORS 8.3. This may have been the fault of the inexperienced users driving the utility. I would prefer to gain confidence that it was probably user error.
|
|
![]() |
|
![]() |
|
We have hit serious problems with the client side installation.
A new user cannot see the SQLServer database until an administrator has explicitly accessed an encyclopaedia from that client under their network user id. Basically the user cannot find the encyclopaedias until one has been opened for them. We cannot work out where the SA2001.ini file is being built from when a new user logs in and it always defaults to the vanilla format. No doubt there is something very simple that we are failing to do but we are unable to work out what. Edited: 22-Jul-2008 at 17:22 by Peter Crabb-Wyke |
|
![]() |
|
![]() |
|
The first problem was not quite as described but it was very easy in testing to end up with a user who couldn't connect for themselves. This may have been down to deleting the user account from the PC and retesting with the same id.
Telelogic have pointed us to where the ini file is built, I couldn't find this when I checked the documentation. (my administrator training was on version 7) |
|
![]() |
|
![]() |
|
Since at least SA V10.7 the SA2001.ini file for each user has been store in a hidden file at this path:
C:\Documents and Settings\ ------------------------- Theodore A. Menard |
|
![]() |
|
![]() |
|
We have found the ini files, they are created automatically when the user first logs in. The problem was discovering where the values were derived from. I have yet to find another user with time to spare to log into our test machine and create a new profile and see if Telelogics recommendations will work.
|
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.