Install and activate Rockwell Software products on the appropriate runtime computers. As part of installing each product, also install FactoryTalk Services Platform.
In addition, on each FactoryTalk Network Directory client computer, specify which computer on the network is hosting the FactoryTalk Network Directory Server. Then follow the steps below.
Step 1 · On a Network Directory computer
Before you begin, shut down all Rockwell Software products running on every computer on the network.
Next, on any computer in the Network Directory, run the FactoryTalk Administration Console and restore the directory you backed up previously. See “Restore a FactoryTalk Directory” on page 187.
If necessary, do the following:
If the computers in your runtime system are on the same physical network as your development computers but are in a different domain, then rename any computers with the same name. A Windows Domain Controller will not allow multiple computers in different domains to have the same name on the same network.
(In the Explorer window, expand the Computers and Groups folder, expand the Computers folder, right-click the computer account icon, and then click Properties on the pop-up menu. Type the new name for the computer, and then click OK.)
If you created Windows-linked user accounts on your development system, recreate all security settings for these accounts in your runtime system.
If you created Windows-linked user groups on your development system, move them to the new domain.
(In the Explorer window, expand the Users and Groups folder, expand the User Groups folder, right-click the user group you want to move to the new domain, and then click Properties on the pop-up menu. In the Properties dialog box, click Change Domain, and then choose the new domain. The new domain must already contain a user group of the same name.) Click OK to save.
Step 2 · On the FactoryTalk View Site Edition Server computer
Restore the HMI project and identify the location of data servers. Open FactoryTalk View Studio (or the View Administration Console), and edit the application. The HMI and data servers will be in error because the are still configured for the development computer. Edit
the properties of the HMI and data servers to reflect their new location. See FactoryTalk View documentation for help.
Step 3 · On the FactoryTalk View Site Edition Client computers
Restore client configuration files (*.cli). The location on the runtime computer is not important, but by default, the client files are located in C:\Documents and Settings\All Users\Documents\RSView Enterprise\SE\Client. See FactoryTalk View documentation for help.
Step 4 · On the RSLinx Classic computer
1. Run the RSLinx Backup Restore Utility to restore the RSLinx Classic configuration.
From the Windows Start menu, point to All Programs > Rockwell Software >
RSLinx > Backup Restore Utility.
2. Update any offline topics in the project to online topics.
3. To see PLC or SLC symbol files when browsing offline, copy the processor project from the development computer to the runtime computer. Then define the new location of the project file in the RSLinx Classic topic for that processor.
Step 5 · On the RSLinx Enterprise server computer
1. Copy the communications configuration file you copied previously back to the same directory location C:\Documents and Settings\All Users\Application
Data\Rockwell\RSLinx Enterprise\RSLinxNG.XML, and then restart your computer.
2. On any computer in the Network Directory, run FactoryTalk Administration Console.
3. Change the name of the computer hosting the RSLinx Enterprise data servers.
Right-click the Data Server icon and then click Properties to open the Data Server Properties dialog box. In the Computer hosting the RSLinx Enterprise Make sure that the folder name and HMI project file name (*.sed) have the same name or the HMI Server will not load properly.
server box, identify the name of the runtime computer where the data server is now located. Repeat this step for each defined data server.
4. Re-map any device shortcuts to their corresponding physical devices listed in the Communication Setup editor. For help, see RSLinx Enterprise online help.
Step 6 · On the Microsoft SQL Server computer
If your FactoryTalk system includes Microsoft SQL Server databases for logging
historical data, including FactoryTalk Alarms and Events logs, restore any data you want to deploy to the new system, and then re-establish a connection between a database definition, held in the directory, and its associated Microsoft SQL Server database.
1. On any computer in the Network Directory, run FactoryTalk Administration Console.
2. From the Explorer window, open System > Connections > Databases.
You must also update the names of the computers hosting the HMI servers and the Tag Alarms and Events servers.
3. Double-click the database definition to open its properties, change the name of the computer hosting the Microsoft SQL Server, and then click OK.
The system checks for database tables and creates them, if they do not exist.
Step 7 · On the FactoryTalk Transaction Manager computer If your FactoryTalk system includes FactoryTalk Transaction Manager:
1. Run Transaction Manager and restore the project you backed up. On the Configuration menu, click Restore.
2. Next change the name of the computer associated with each connector configuration.
For each defined Connector Service, right-click the Configuration name and select Define Connector from the pop-up menu. Change the Host Name from the name of the development computer to the name of the runtime FactoryTalk Transaction Manager computer.
Step 8 · On the FactoryTalk Batch Server computer
If your FactoryTalk system includes FactoryTalk Batch, restore FactoryTalk Batch Server and client files. For help, see FactoryTalk Batch Installation Guide.
Step 9 · On the FactoryTalk Batch client computers
If your FactoryTalk system includes FactoryTalk Batch, restore FactoryTalk Batch client files. For help, see FactoryTalk Batch Installation Guide.