If your deployed network distributed application is non-redundant, some of the supporting
tasks documented in this chapter might be irrelevant or unnecessary.

For example, there would be no need to set up a temporary system, with the secondary
server as the primary server, or to disable and then restore redundancy.

To upgrade a non-redundant network application, use the following steps as a guideline,
keeping the noted exceptions in mind:



Prepare for the upgrade. See “Step 1 – Upgrade Preparation” on page 105. Ignore
the subsection about ensuring that the most recent application files are on the primary
server computer.



Back up the deployed application. See “Step 2 – Back up the deployed
application” on page 107. Ignore the tip about ensuring that the most recent
application files are on the primary server computer.



Upgrade the engineering workstation. See “Step 5 – Upgrade software
components on Workstation #1” on page 116. Ignore the last subsection, about
specifying Server #2 as the Network Directory location.



Migrate the deployed application. See “Step 6 – Migrate the FactoryTalk View SE
application” on page 118.



Upgrade the application server. See “Step 10 – Upgrade software components on
Server #1” on page 123. For the non-redundant case, assume that the application
server computer hosts the FactoryTalk Network Directory, an HMI server, and an
RSLinx Enterprise data server.

FTViewSEInstallENU.book Page 104 Wednesday, July 16, 2014 10:53 AM

Advertising

Popular Brands

Popular manuals