Move FTA from one TWS master to another

Answer

Here are the recommended steps to take to switch an FTA from one master domain manager (development) to another (production):

NOTE: This assumes that you have installed the FTA on the Windows 2008 workstation with your "production" username, directory structure, and port number convention. This eliminates the need for you to uninstall and reinstall TWS with the username you use for the production environment. Once TWS is installed for a certain username on a Windows system, that name cannot be "changed"...this is a Windows restriction, not a TWS issue.

When ready to switch the FTA from dev master to prod master:

1. Stop all TWS processes on the FTA, including netman and tokensrv. (conman unlink, stop, shut, then shutdown from the twshome directory)

2. Delete the FTA's CPU definition from the development master.

(NOTE: The development master will still "know" about the FTA until the next time the Final schedule runs. It is important to do the "unlink" (from step 1 above) so the development master doesn't continue to attempt to link with that FTA during the time before Final runs on it.)

Also, delete the ...\TWA\TWS\pobox\FTANAME.msg file from the development master's pobox directory.

It is also recommended to stop and restart all the TWS processes on the development master after the FTA being moved has linked successfully with the production master. This is to refresh the netman process on the development master to clear any cached information about the FTA.

3. Ensure that the FTA's CPU definition exists in the production master's CPU definitions. (NOTE: This definition will take effect when the Final schedule runs.)

IMPORTANT: The settings for "CPUNAME" and "TCPADDR" in the CPU definition in the production master's database must match the settings for "thiscpu" and "nm port" respectively in the FTA's "...\TWA\TWS\localopts file. Change the FTA's localopts file to the port number you use for your production systems...and ensure the CPU name is the same between the master and localopts file.

4. Remove the following files from the FTA: (NOTE: This clears out any "cached" information that the FTA will have regarding the "old" master (development) server).

- Symphony
- Sinfonia
- Jobtable
- *.msg files (you can within the ...\TWA\TWS directory for *.msg and then remove the files). If you get a message that one of the msg files (example, mailbox.msg) cannot be deleted, reboot the system.

NOTE: Change the "master=" option in the "...\TWA\TWS\mozart\globalopts" file to reflect the new production master's name. This is not "read" by any TWS process, but can be changed just to keep it accurate for future reference. It is an easy way to know what master the FTA belongs to if it is kept accurate.

5. Allow Final to run on the production master without starting the TWS processes on the FTA. After Final runs, the production master's netman process will be "looking" for the FTA. As soon as you start the netman process on the FTA, it should link with the production master.

6. Issue the conman link and start commands from either the master or the FTA after starting netman on the FTA. (Again, if autolink is "on" in the CPU definition, it should automatically link).