To use custom data tokens in the DS, create a custom database and table, add the credentials to access that custom database to the DS options, and reference that custom database using tokens.
Here is an example of how to do the aforementioned process. This example will show how to create a custom data source to be used to map PCT real-time migrations. Follow these guidelines, altering them slightly, to create a custom data source to do anything that is wanted.
Here are the step-by-step instructions on how to create a custom database that maps the source computer to the destination computer when doing PCT real-time migrations:
1. Open the SQL Server Enterprise Manager.
2. Connect to the SQL Server and create a database called eXpress_Custom.
3. Expand the eXpress_Custom database and create a new table with the following columns:
4. The data type for both columns must be char, and the length should be the number of characters in the longest computer name in the environment. (Windows XP* will allow computer names of up to 64 characters.)
5. Set the Source_Computer_Name as the primary key for this table.
6. Save the new table as PCT_RTM_Map.
7. Open the DS Console.
8. Go to Tools > Options > Custom Data Sources.
9. Add a Database Source with the following information:
a. Alias: Custom
b. Server: <Your SQL Server Name>
c. Database: eXpress_Custom
d. If you are trying to connect to remote SQL server do the following:
To connect to remote SQL server(mentioned in custom data sources tab in tools option) from DS console there two options, by using windows authentication or using SQL server authentication.
1. Windows authentication:
a. The check box Use integrated authentication should be checked in database source dialog in custom data source tab.
b. The user running the axengine should be domain user and have access to database on remote SQL server.
2. SQL server authentication:
a. The check box Use integrated authentication should be unchecked in database source dialog in custom data source tab.
b. The SQL server user credential should be provided in database source dialog in custom data source tab.
10. Create a new job called PCT_RTM.
11. In the PCT_RTM job, add a Run Script task.
Enter the following for the script. This is case-sensitive, so it would be best to cut and paste. Remember to change ServerName to match the name of your server.
\\ServerName\express\PCT\PCTWiz.exe -rt:network=%#Custom*"select Destination_Computer_Name from PCT_Distribution_Map where Source_Computer_Name = '%COMPNAME%'"% -p:\\ServerName\express\PCT\EN\default.pbt -q
Note: Users may want to add additional switches such as -user: or -usermap: to make the migration more specific. This example uses the default.pbt template file that is included with the PCT install but the switch can be changed to point to any template file.
Now, open the PCT_RTM_Map table that was just created and populate it with the names of the destination and source computers to migrate to and from, respectively. Then run the PCT_RTM job on the source computer and it will perform the real-time migration to the destination computer that is setup in the PCT_RTM_Map table.
Imported Document Id