TestDirector (TD) Project Data Migration

1, do backup work
A, after installing TD will be in the installation letter:/program Files/common files/mercury interactive/domsinfo directory, There is an Access database Doms.mdb for system information that is created by TD and is encrypted and holds all of the TD's configuration information. This directory contains doms.mdb files (user information and engineering lists), connection strings (connection strings), parameters (parameters), Global style sheets (global stylesheet), the database Template (Empty_db.mdb) (some temporary data)
B, Td_dir contains a list of automatic tests, attachments, settings, and styles for each project. By default in the C:/td_dir/default directory, open this directory can see the TD's engineering files, we need to back up the project files.

2, install a new TestDirector8.0 server, and then log on to site Administrator to create the same domain and project as the TD system being migrated.

3. Copy the files in the migrated Td_dir directory to the Td_dir directory where they are migrated and enter each project under the Td_dir directory.

4, in the Td_dir/default directory into each project, modify the Dbid.ini file in the server's address database Server=default (the advantage of setting default is that if you need to transplant later, You no longer need to modify this INI configuration file.)
The contents of the document are as follows:
[General]
Database_type=mssql//indicates that the project database type is SQL Server
created_date=11/07/07 01:06:31//Database creation time
CREATED_BY=TD//Database for TD creation
Aliasname=zb_test//Project name
Names of project databases in database name=zb_td_zb_test_db//sqlserver2000
Database Server=local//machine name of the server where the databases reside
Domain Name=default//Project Location
Sendallqualified=n
Has_vcs_db=n

5, the/program files/common files/mercury interactive/domsinfo Directory In addition to the Doms.mdb file cover the new server under the directory text

Pieces, as to why except Doms.mdb file, in the following file will have instructions.

6, after the above modifications, the migration of data has been successful, restart the machine, TD server can access the migrated database.

F&q:
A: Why not use the original doms.mdb to copy to the same directory as the new server.
A: I in the practice process, directly copied over, log on to TD Server prompts: "Server properties wasn ' t initialized successfully"
There are many solutions on the web that are used to meet the same problem, but none of them are available, so I took a rather cumbersome approach to building my own library locally and then using the original

The

comes with attachments, styles, files, and so on. This solves the problem of server properties wasn ' t initialized successfully.