FT Views Einst Allen U
FT Views Einst Allen U
Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required to be carried out by
suitably trained personnel in accordance with applicable code of practice. If this equipment is used in a manner not specified by the manufacturer,
the protection provided by the equipment may be impaired.
In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this
equipment.
The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated
with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and
diagrams.
No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this
manual.
Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited.
Throughout this manual, when necessary, we use notes to make you aware of safety considerations.
WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to
personal injury or death, property damage, or economic loss.
ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic
loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence
Important: Identifies information that is critical for successful application and understanding of the product.
SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be
present.
BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous
temperatures.
ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to potential Arc Flash. Arc
Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory requirements for safe work
practices and for Personal Protective Equipment (PPE).
Allen-Bradley, Rockwell Software, Rockwell Automation, and TechConnect are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Table of contents
Chapter 1
Chapter 2
Hardware, operating system, What can I install and run on one server? ..................................................................... 23
Review hardware requirements ....................................................................................... 23
and domain information
Review operating system requirements .......................................................................... 24
Operating system recommendations for application servers ............................. 25
Set up the Windows domain or workgroup ................................................................. 26
Domain controller requirements ............................................................................ 27
About synchronizing time on application computers ........................................ 27
Windows workgroup requirements........................................................................ 28
Set up computers with names to be used in production............................................. 28
Chapter 3
Chapter 4
Chapter 5
Chapter 6
Chapter 7
Chapter 8
Chapter 9
Upgrade operating network Find out about features in the new product version ................................................... 86
Upgrade a non-redundant network distributed application ..................................... 86
distributed applications
Example ........................................................................................................................ 87
Part 1: Prepare for the upgrade ........................................................................................ 87
Step 1: Prepare for the upgrade ............................................................................... 87
Log on with administrative rights ................................................................... 87
Record the names and passwords of administrative users .......................... 88
Perform set-up tasks on application computers ........................................... 88
Rockwell Automation Publication VIEWSE-IN003P-EN-E -February 2018 5
Table of contents
Appendix A
Appendix B
Appendix C
Appendix D
Appendix E
Troubleshoot KEPServer Set DCOM configuration for KEPServer Enterprise ............................................... 119
Enterprise
Index
What’s in this Installation This manual describes the FactoryTalk View product and system, the tasks to be
performed on a system before installation, the detailed installation steps, how to
Guide? use FactoryTalk Activation to license the installed product, tasks for deploying
applications, and how to upgrade an existing system.
The contents of this Installation Guide appear in the order you would use during
installation on new or existing systems:
About the FactoryTalk View In addition to FactoryTalk View Installation Guide, the FactoryTalk View
documentation documentation set includes:
Release Notes. Read the Release Notes before you begin installing or
working with FactoryTalk View and supporting software.
The Release Notes are available from the FactoryTalk View installation
package, the Setup Wizard, or the Help menu in FactoryTalk View Studio.
Help. Procedures and reference information are available from the Help
menu in FactoryTalk View Studio, and from editors and dialog boxes used
to develop FactoryTalk View SE applications.
What’s in this manual The Installation Guide is available in PDF format from the FactoryTalk View
installation package, from the Help menu in FactoryTalk View Studio, and from
the Rockwell Automation Literature Library.
Tip: In the Literature Library, to find the current version of the Installation Guide and
the User’s Guide, search for publication numbers containing the string VIEWSE.
Each chapter includes a task check list, which you can use to create customized
procedures suited to the needs of your application.
Open FactoryTalk View manuals You can open the FactoryTalk View Site Edition User’s Guide and Installation
Guide in FactoryTalk View Studio. From the Help menu, select Online Books,
and then select the manual.
Tip: Adobe Reader may be required to view the manuals. For information about using
Adobe Reader, see the product documentation.
Other documents
Document Description
FactoryTalk Alarms and Events System Configuration Guide, publication Describes the tasks to install, configure, and use FactoryTalk Alarms and Events services as part of a
FTAE-RM-001 FactoryTalk-enabled automation system.
FT Security System Configuration Guide, publication FTSEC-QS001 Walk through of configuring FactoryTalk Security, creating accounts and setting permissions.
Contact Rockwell If you cannot find the answer to your question in the documentation or on the
Internet, contact Rockwell Automation Technical Support, using any of these
Automation Technical methods:
Support
Telephone: 1-440-646-3434
Online: http://support.rockwellautomation.com
Support staff are available Monday to Friday from 8:00 a.m. to 5:00 p.m. local
time (North America only), except on statutory holidays.
When you call, it is recommended that you be at your computer and ready to
provide the following information:
The product’s Serial Number and Product Key, which are printed on the
Activation Certificate enclosed with the product software installation
package.
The FactoryTalk View product version number.
FactoryTalk Services Platform version number.
The connectivity (FactoryTalk Linx or RSLinx Classic) version number.
The type of hardware you are using.
The names of other Rockwell Automation products installed on the
computer.
The exact wording of any messages shown on the computer.
A description of what happened and what you were doing when the
problem occurred.
A description of how you tried to solve the problem.
You can view the Rockwell Automation End-User License Agreement ("EULA")
by opening the License.rtf file located in your product's install folder on your hard
drive.
Trademark Notices
Other Trademarks
Access, ActiveX, Internet Explorer, Microsoft, SQL Server, Surface, Visual Basic,
Visual C++, Windows, and Windows Server are either registered trademarks or
trademarks of Microsoft Corporation in the United States and other countries.
Intel, Intel Atom, Intel Core, and Intel Xeon are either registered trademarks or
trademarks of the Intel Corporation in United States and other countries.
All other trademarks are the property of their respective holders and are hereby
acknowledged.
Warranty
This product is warranted in accordance with the product license. The product’s
performance may be affected by system configuration, the application being
performed, operator control, maintenance, and other related factors. Rockwell
Automation is not responsible for these intervening factors. The instructions in
this document do not cover all the details or variations in the equipment,
procedure, or process described, nor do they provide directions for meeting every
possible contingency during installation, operation, or maintenance. This
product’s implementation may vary among users.
This document is current as of the time of release of the product; however, the
accompanying software may have changed since the release. Rockwell Automation,
Inc. reserves the right to change any information contained in this document or
the software at any time without prior notice. It is your responsibility to obtain the
most current information available from Rockwell when installing or using this
product.
Environmental compliance
FactoryTalk View, including FactoryTalk View Site Edition (SE) and FactoryTalk
View Machine Edition (ME), are human-machine interface (HMI) software
products designed with a common look, feel, and navigation to help speed HMI
application development and training time.
What is FactoryTalk View FactoryTalk View SE is an integrated software package for developing and
running HMI applications that can involve multiple users, clients, and servers,
SE? distributed over a network.
FactoryTalk View SE provides all the tools you need to create powerful,
dependable process monitoring and supervisory control applications.
A FactoryTalk View SE System is more than the HMI Server and Clients. It also
includes FactoryTalk Services Platform and Data Communication products such
as FactoryTalk Linx and RSLinx Classic.
About the architecture of your A network distributed FactoryTalk View SE system consists of several
components as shown below.
FactoryTalk View system
FactoryTalk View Studio FactoryTalk View Studio Enterprise is the configuration software for developing
Enterprise and testing FactoryTalk View SE network distributed, network station, local
station, and FactoryTalk View ME applications.
FactoryTalk View Studio contains editors for creating complete applications, and
includes client and server software for testing the applications you create. Use the
editors to create applications that are as simple or as complex as you need.
FactoryTalk View SE Server FactoryTalk View SE Server, also called the HMI server, stores HMI project
components (for example, graphic displays) and supplies them to clients. The
16 Rockwell Automation Publication VIEWSE-IN003P-EN-E -February 2018
FactoryTalk View basics Chapter 1
server also contains a database of tags, and performs alarm detection and historical
data logging.
The FactoryTalk View SE Server has no user interface. Once installed, it runs as a
set of headless Windows services that supply information to clients as they request
it.
FactoryTalk View SE Client FactoryTalk View SE Client is software for viewing and interacting with
FactoryTalk View SE local station, network station, and network distributed
applications at run time.
Use the FactoryTalk View SE Client Wizard to create client configuration files
that can be deployed to client host computers. For details, see the FactoryTalk
View SE Help.
FactoryTalk View SE Station FactoryTalk View SE Station is a supervisory HMI software package for enterprise
solutions. SE Station is a single-computer HMI that can be operated in either a
Local or a Network FactoryTalk Directory. There are key differences between
View SE Distributed and View SE Station:
View SE Distributed can share HMI screens and data with multiple clients.
View SE Station does not allow sharing of HMI screens or data to other
View SE Stations.
A local station system can include several HMI computers, each with its own
FactoryTalk Directory server and data server connection to the controllers.
FactoryTalk ViewPoint FactoryTalk ViewPoint is an add-on to FactoryTalk View that provides for a fully
scalable, fully animated, read-and-write view of existing Site Edition (SE) and
Machine Edition (ME) web applications from a web browser.
A web application consists of graphic displays selected from the FactoryTalk View
application, converted for viewing in a web browser, and then published to a
FactoryTalk ViewPoint Server (also called the web server).
Stand-alone FactoryTalk Linx FactoryTalk Linx is a FactoryTalk Live Data server and can be enabled as a
Server FactoryTalk Alarms and Events server. Your applications use FactoryTalk Linx to
communicate with devices such as controllers and I/O scanners. This enables you
to see values, such as sensor readings and other controller data from your plant
floor devices, on your desktop computer or dedicated PanelView Plus terminal.
Stand-alone FactoryTalk FactoryTalk Directory provides a central lookup service for a FactoryTalk system
so all definitions do not have to exist in a single physical project file. References
Directory Server
saved by FactoryTalk Directory are used by FactoryTalk-enabled products and
FactoryTalk services to locate definitions when they are needed. It allows clients to
locate key configuration information such as system organization, server locations,
and policy information. FactoryTalk Directory provides a common address or
phone book of factory resources that are shared among FactoryTalk-enabled
applications in a distributed system.
FactoryTalk Services FactoryTalk Services Platform provides a set of common services (such as
diagnostic messages, health monitoring services, and access to real-time data) for
Platform all the FactoryTalk products and applications used in a control system.
To open the Administration Console, select Start > All Programs > Rockwell
Software > FactoryTalk Administration Console.
FactoryTalk Directory
The FactoryTalk Directory centralizes access to system resources and names for all
FactoryTalk products and components participating in an automated control
system.
FactoryTalk Alarms and Events, which installs behind the scenes during
FactoryTalk View SE installation, provides system-wide alarm monitoring and
control centralized at the FactoryTalk Directory.
FactoryTalk Security
FactoryTalk Diagnostics
FactoryTalk Activation
Connectivity How you plan to obtain data for an application will determine which
communications software you install.
You can use the FactoryTalk Linx or RSLinx Classic software shipped with
FactoryTalk View SE, or use other software and devices that support OPC ( OLE
for Process Control) communications.
Tip: FactoryTalk Linx is automatically installed for FactoryTalk View applications. You
may also choose to include RSLinx Classic during the installation procedure.
FactoryTalk Linx
However, FactoryTalk Linx does not allow you to create alias topic shortcuts, or to
perform online tasks such as uploading and downloading RSLogix 5000 files. If
you need these capabilities, you may use RSLinx Classic as your data
communications server instead.
RSLinx Classic
For example, install and use RSLinx Classic to serve data through DH+ (Data
Highway +) networks, to support complex bridging and routing, and to support
unsolicited messaging from a controller to RSLinx.
RSLinx Classic also allows you to create alias topic shortcuts, and to perform
online tasks such as uploading and downloading RSLogix 5000 files.
Installation package The FactoryTalk View installation package provides all the software you need to
develop and run local applications confined to a single computer, or distributed
control systems that involve several computers, connected over a network.
Studio Enterprise
Site Edition Server
Site Edition Client
Site Edition Station
FactoryTalk ViewPoint SE
Stand-alone FactoryTalk Linx Server
Stand-alone FactoryTalk Directory Server
Three other applications can also be installed from this Setup Wizard for
FactoryTalk View ME applications:
What can I install and run In a network application, it is possible for a single server computer that meets the
on one server? listed hardware requirements to host all of the following components:
However, running more than one HMI server on a single computer is not
recommended. If you plan to deploy a network distributed application that uses
more than two servers (or two pairs of redundant servers) and 20 clients, it is
recommended that you contact your local Rockwell Automation Sales office for
architectural assistance. For information about setting up redundant FactoryTalk
View SE Servers, see Chapter 14, Setting up FactoryTalk system availability, in the
FactoryTalk View User's Guide VIEWSE-UM006.
Review hardware The computer hardware you choose to install and operate your FactoryTalk View
SE System should be adequately sized for the demands of each component. These
requirements specifications are based on the hardware that the FactoryTalk View product and
its supported operating systems require.
and more RAM than operator or engineering workstations. The greater the
demand, the more powerful a system you need.
You should also specify a hard drive that has enough disk space to provide virtual
memory that is at least twice the size of the physical RAM.
Note: Do not run FactoryTalk Alarms and Events servers (Rockwell Automation Device Server or
Tag Alarm and Event Server) on the computers that meet only minimum server
requirements.
Review operating system The choices you make will depend in part on whether the computer is to host an
requirements application client or server. You might choose to run operator or engineering
workstations in a Windows Server operating system, but that is not required.
Windows 10 Enterprise*
Windows 10 Professional*
Windows 10 IoT Enterprise 2016 Long Term Servicing Branch (LTSB)
Embedded**
Windows 8.1 Enterprise
Windows 8.1 Professional
Operating system For computers hosting application servers (HMI servers, data servers, or Tag
Alarm and Event Servers), operating system requirements depend on whether the
recommendations for
server will support more or fewer than 10 client connections.
application servers
A client can be any of FactoryTalk View SE Client, FactoryTalk View Studio, the
FactoryTalk View SE Administration Console, a FactoryTalk Transaction
Manager connector, or another FactoryTalk View SE Server.
Set up the Windows domain The number of computers participating in a FactoryTalk View SE network
application determines whether the computers can belong to a Windows domain
or workgroup or a workgroup.
For more information about setting up domains and workgroups, see the
document, FactoryTalk View SE Distributed System Design Considerations,
attached to Rockwell Automation Knowledgebase Answer ID 32549 .
Domain controller For network applications consisting of more than 10 computers, the use of a
requirements domain controller is recommended.
For more information about Windows operating systems and Service Pack
compatibility, see Rockwell Automation Knowledgebase Answer ID 20450 .
Note: Do not install FactoryTalk Directory, FactoryTalk View SE Server, or any other application
software on the same computer as the Windows domain controller. This configuration is
not supported.
About synchronizing time on In a networked system, to ensure that time stamps on alarms, historical data, and
diagnostics are accurate, it is highly recommended that time synchronization be
application computers
configured on all application computers.
Windows workgroup For network applications consisting of 10 or fewer computers, you can run
FactoryTalk View SE in a Windows workgroup network environment.
requirements
Name resolution is required for the computers to communicate with each
other on the network.
Workgroups do not use a domain controller, so central network
administration is not available. This means that security and network
communications (for example, name resolution) must be handled at each
individual computer in the workgroup.
Each workstation in a workgroup must have the same user accounts, with
the same user names and passwords on each machine, for all machines
participating in a client-server environment.
All users in a workgroup should have Administrative rights assigned to
them.
FactoryTalk Directory provides centralized security services without
requiring a Windows Server and domain controller. When setting up
centralized security in a FactoryTalk Network Directory for Windows
Workgroups, do not use Windows-linked accounts. Instead, create user
accounts that are managed and authenticated by FactoryTalk Security.
Set up computers with When you install the FactoryTalk Services Platform with FactoryTalk View SE,
names to be used in the program creates a FactoryTalk account for the current computer, under the
Local and Network FactoryTalk Directories.
production
As a result, if you rename the computer after installing FactoryTalk View SE or
when you deploy an application, the FactoryTalk Directory will not recognize the
new name.
To avoid this problem, it is recommended that you give the application client and
server host computers the names they will use in a production setting, before you
install the FactoryTalk View SE software.
Tip: If you must rename a computer and you encounter problems, for assistance, see
Rockwell Automation Answer ID 35169 (for FactoryTalk View SE network
applications), or Answer ID 38775 (for FactoryTalk View SE local and ME
applications).
Pre-installation configuration
This chapter guides you through the steps for preparing your computer for
installation of the FactoryTalk View SE product and supporting software.
Use the following checklist for preparing the computer for installation:
Disable automatic Windows When you install Microsoft Service Pack releases and other Windows operating
updates system updates, you introduce new software that could affect the operation of
FactoryTalk View SE components on the computer.
Note: Windows updates should be disabled in all production computers. Updates can cause
unexpected behaviors, including shutting down running applications and automatic
computer restarting.
3. In the Important Updates drop down, select Never check for updates.
4. Select the check box Give me recommended updates the same way I
receive important updates.
5. Clear the check box Allow all users to install updates on this computer.
For more information about Windows operating systems and Service Pack
compatibility, see Rockwell Automation Knowledgebase Answer ID 20450 .
Manually configure NICs The Network Interface Card (NIC) is the hardware in a computer that lets it
connect to other devices on the network. A switch manages traffic on the Ethernet
and switch ports network. Some switches allow ports (physical connections) to be configured
individually.
The link speed and duplex settings for network connections can be
auto-negotiated (the device determines the best way to communicate), or
manually configured (settings are hard coded).
Many NICs also offer a power-saving feature that turns off the network card if it is
not being used. This setting sometimes interferes with the ability of the computer
to receive data, causing errors such as wireframes, stale data, and other failures. To
prevent these errors, disable power saving for your computer’s network interface
cards. For details, see Disable power saving for the NIC on page 31.
It is also recommended that you manually configure the managed switch ports,
using the same settings. To learn how to configure switch ports, see the product
documentation provided with the switches you are using.
For an overview of best practices for connecting devices over a network, see the
Ethernet Design Considerations Reference Manual document in the Rockwell
Automation Literature Library. (Search for publication ENET-RM002.)
Note: If you are using unmanaged switches, the NIC settings must remain auto-negotiated.
Connecting an auto-negotiated device to a manually configured device can result in
network communication errors and is not recommended.
Set up the NIC link speed and Follow the steps below. The steps may vary slightly for some of the Windows
operating systems.
duplex
1. Open Windows Control Panel, and then click Network and Internet.
3. From the list of Tasks on the left, select Change adapter settings (or
Manage network connections).
6. In the Properties dialog box for the device, click the Advanced tab.
7. From the list of properties for the device, select Link Speed & Duplex (or
Speed & Duplex).
8. From the Value list, select the highest possible value for the connection, and
then click OK.
Disable power saving for the Follow the steps below. The steps may vary slightly for some of the Windows
operating systems.
NIC
1. Open Windows Control Panel, and then click Network and Internet.
3. From the list of Tasks on the left, select Change adapter settings (or
Manage network connections).
6. In the Properties dialog box for the device, click the Power Management
tab.
7. Clear the Allow the computer to turn off this device to save power check
box, and then click OK.
Disable or uninstall FactoryTalk View SE is compatible only with the built-in Windows firewall and
should not be used with third-party firewalls because this can cause unexpected
third-party firewalls results.
Before installing FactoryTalk View SE, disable or uninstall all third-party firewalls
on the computer. For details, see the documentation supplied with your firewall
product.
Remove Enhanced Security Internet Explorer Enhanced Security Configuration (ESC) is a group of default
security settings for Windows Server 2008 and Windows Server 2012 that
Configuration protects servers by limiting the ways users can browse Internet and Intranet Web
sites on the computer.
To avoid unexpected behavior, it is recommended that you remove the ESC from
computers running FactoryTalk View SE.
2. In the Server Manager Dashboard window, on the left side, click Local
Server.
3. On the right side of the Local Server window, under Properties, locate IE
Enhanced Security Configuration and click On.
Set up Data Execution Data Execution Prevention (DEP) is a Microsoft Windows security feature that is
built into the operating system starting with Windows XP and Windows Server
Prevention 2003. DEP is intended to protect programs and services from viruses and other
security threats.
The DEP settings determine which programs and services are covered by DEP
protection. On computers running FactoryTalk View SE components, it is
recommended that DEP be turned on for essential Windows programs and
services only.
To turn on DEP:
1. Open Windows Control Panel, select Control Panel Home > System and
Maintenance.
2. Click System.
3. From the list of tasks on the left, select Advanced system settings.
7. Select the option, Turn on DEP for essential Windows programs and
services only, and then click OK.
Remove unnecessary DCOM If multiple DCOM protocols are installed and configured on the computer,
performance of communications in a FactoryTalk View SE system can be
networking protocols adversely impacted. To ensure that DCOM communications function correctly,
and do not affect the performance of the system, remove all protocols other than
TCP/IP.
2. In the Run dialog box, type dcomcnfg, and then click OK.
4. Click the Default Protocols tab. If the DCOM Protocols list shows
protocols in addition to TCP/IP, remove those unnecessary protocols. For
example, remove the protocol Connection-oriented SPX.
The FactoryTalk View installation package provides all the software you need to
develop and run distributed systems involving multiple computers on a network,
or local applications confined to a single computer using FactoryTalk View SE.
This chapter uses FactoryTalk View Studio Enterprise to illustrate the installation
steps, because it includes all mandatory and optional installation choices included
with the other selections on the welcome screen.
To learn about upgrading an existing version of FactoryTalk View SE, see Upgrade
an operating FactoryTalk View SE application on page 85.
Steps FactoryTalk View supports two installation methods: Setup wizard installation
and command-line installation.
This chapter uses the Setup wizard installation method to illustrate the steps. The
overall installation process includes:
In a distributed system, you can also install Site Edition clients through the web
browser. For instructions, see Install SE clients in a distributed system on page 47.
Command-line installation
installation Ensure that the user installing the software has administrative rights in
Windows.
If installing FactoryTalk View Studio Enterprise, locate the serial number
because you will be prompted for it after the installation. Serial numbers are
generally on the original packaging of the installation media.
Schedule downtime for the system if you are upgrading operating
applications or replacing computers during the installation.
Decide which components to The FactoryTalk View SE Setup wizard offers several options for installing the
install FactoryTalk View Site Edition software. You can select:
Studio Enterprise
Site Edition Server
Site Edition Client
Site Edition Station
FactoryTalk ViewPoint SE
Stand-alone FactoryTalk Linx Server
Stand-alone FactoryTalk Directory Server
The option you choose depends on the type of FactoryTalk View SE application
or software component you plan to run on the computer and on the design of your
control system.
For each selection on the Welcome Screen, the following table shows the
mandatory, recommended and optional software components to install.
1
: Site Edition Client is not mandatory if you do not plan to install FactoryTalk ViewPoint SE.
2
: For more information, see About FactoryTalk Historian Connectivity on page 37.
About FactoryTalk Historian FactoryTalk Historian Connectivity allows the trending objects to retrieve data
from a Historian SE Server or FactoryTalk Historian ME Module. It makes
Connectivity
updates to FactoryTalk Administration Console and FactoryTalk View SE Studio
to display an Historian icon for FactoryTalk Historian SE when registered. You
can use it to create new FactoryTalk Historian SE points from trending objects,
and select existing Historian points from Historian SE or Historian ME.
Before you start using the trending objects with your FactoryTalk Historian SE
server, do the following:
Step 2: Launch Setup wizard To launch the Setup wizard and select the product to install:
3. On the Welcome page, select the product to install, and select another
language that will be displayed during the installation process if needed.
Step 3: Customize product For each FactoryTalk View product, there may be three different options
components displayed:
Step 4: Review and accept End user license agreements (EULA) spell out your rights and responsibilities.
license agreements Depending on the applications being installed, it is possible that there may be
more than one license agreement on this page.
Some software products may be delivered or made available only after you agree to
the terms and conditions of each of the license agreements.
3. After you review all license agreements, click Accept All to agree with the
terms of all the listed license agreements and start the installation process.
Step 5: Start the After installing prerequisites, the Setup wizard automatically installs all the
Rockwell Software applications selected previously. Installation is automatic and
installation does not require any input from the user.
During the installation, the Progress page displays the installation percentage
complete. Status notification messages at the bottom of the page identify which
files are being installed.
Step 6: Complete the When the installation of selected products completes, the Setup wizard first
searches for activation keys required the installed products. If no available
installation activation keys are found, the activation page is displayed. You can specify whether
to activate the products now or later.
3. Click Restart now to restart your computer now. Click Restart later to
restart later.
Step 7: Post-installation After you install FactoryTalk View, there may be several final setup steps that
procedures must be completed:
Specify the Network Directory After installing FactoryTalk software, specify one of the computers on the
server location network as the Network Directory server, and then point the other computers on
the network to that computer. This allows all of the computers on the network to
share FactoryTalk Network Directory services and resources.
1. On the computer that you want to use as the Network Directory Server,
from Windows Start menu, select All Programs > Rockwell Software >
FactoryTalk Tools > Specify FactoryTalk Directory Location.
1. On one client computer, from Windows Start menu, select All Programs
> Rockwell Software > FactoryTalk Tools > Specify FactoryTalk
Directory Location.
4. Type the name of the Network Directory server computer, or click the
Browse button to find and select the computer, and then click OK.
6. Repeat steps 1 to 5 on the remaining client and server computers that will
participate in the deployed network distributed application.
Install SE clients in a In a distributed system, after installing the server computer with the Client Install
Portal feature, you can install SE clients through the web browser.
distributed system
To install the SE client application:
3. Press Enter. Internet Explorer displays a page from the server that allows
you to install the FactoryTalk View Site Edition Client application.
Tip: If Internet Explorer displays an error message that it cannot connect to the install
web page, try adding the FactoryTalk View Site Edition website (URL above) to
your local intranet site list.
To do this, in Internet Explorer, click Tools > Internet Options > Security tab >
Local intranet > Sites > Advanced, and add the website to the list. For more
information about the local intranet, refer to Windows Help and Support.
4. Microsoft .NET Framework 4.0 or higher is required before you can install
FactoryTalk View Client. If it is not installed, FactoryTalk View installs
.NET Framework 4.6 by default. Click Install .NET Framework 4.6 on
this computer to install it. The option is not shown if it is already installed.
Modify or uninstall To modify components of FactoryTalk View, from the installation package,
FactoryTalk View double-click Setup.exe, select one product and click Modify.
About FactoryTalk FactoryTalk Activation Manager provides a secure, software-based system for
activating Rockwell Software products and managing software activation files.
Activation Manager
With FactoryTalk Activation Manager, there is no need for a physical master disk
or any physical media; instead, activation files are generated and distributed
electronically.
Tip: To learn about the types of activation that other Rockwell Automation products
can use, see the product documentation or contact your local Rockwell Automation
Sales office.
What happens if If the FactoryTalk View components you have installed cannot be activated, for
example, because the activation server is unavailable or because borrowed
FactoryTalk View is not activations have expired, the software will continue to run for up to seven days.
activated?
The seven-day grace period allows time to correct the problem with acquiring
activations without disrupting critical applications. If activation is restored within
seven days, normal operations will resume.
If activation is not restored, the grace period will expire. After the grace period
expires, if you restart FactoryTalk View SE and activation remains unavailable, the
software will run for two hours in demo mode.
You can create or load up to five HMI servers locally in FactoryTalk View
Studio.
You can run a local station FactoryTalk View application for up to two
hours.
Remote clients cannot connect to a FactoryTalk View server.
Starting from FactoryTalk View version 10.00, some limitations are eliminated.
You can create or load over five graphic displays per HMI server now. You can also
fully use the Symbol Factory library without restriction.
Set up client computers to Floating concurrent activations are assigned automatically to clients that need
them, and returned automatically to the activation server pool when FactoryTalk
obtain floating activations View SE stops running on the client, or when the client computer shuts down.
Client computers must be set up to obtain floating activations from the activation
server.
If you prefer to use borrowed activations for clients, skip to Borrow activations for
development computers on page 51.
After you set up the activation server (or servers), you can specify which server
each client computer will obtain activations from.
Once a client is connected to a server, all you have to do is to run the FactoryTalk
View software (for example, the FactoryTalk View SE Client), and the server will
issue available activations automatically.
Ensure that network To ensure that critical software components in a network application using
floating activations can always obtain the necessary activations, even if the
application components network is disrupted, set up a FactoryTalk Activation server on every computer
stay activated where the FactoryTalk View SE software is running. This includes all clients and
Borrow activations for If it is not convenient for a development computer to remain connected to the
network where the activation server resides, you can connect to the activation
development computers server temporarily, borrow a concurrent activation for a limited amount of time,
and then disconnect. When the time-limited activation expires, its associated
software is no longer activated, and the activation automatically becomes available
again from the server's activation pool.
Only the FactoryTalk View Studio activation keys can be borrowed. While
developing Network applications disconnected from the network, the
FactoryTalk View Studio activation key is shared by any test clients and HMI
servers in your application, allowing all necessary components to run for
development purposes.
Note: To use borrowed activations, you must upgrade to FactoryTalk Activation Manager version
3.30 or later (included on any FactoryTalk CPR 9 SR 4 product’s installation package) on all
server and client computers where the borrowed activations will be used.
Activation keys for The activation files you download from the Rockwell Software Activation
Website contain the activation keys you purchased, in encrypted form. The
FactoryTalk View software activation key is the software that activates FactoryTalk View SE components.
components
Following is a list of activation keys used by the FactoryTalk View SE and ME
products. For information about the keys required to activate other Rockwell
Automation products in your application, see the product documentation.
FactoryTalk View SE Station (network station and local station applications), 250 displays RSVSE.250
FactoryTalk View SE Station (network station and local station applications), 100 displays RSVSE.100
FactoryTalk View SE Station (network station and local station applications), 25 displays RSVSE.25
FactoryTalk View SE Station (network station and local station applications), 15 displays RSVSE.15
Sharing keys among multiple Multiple FactoryTalk View SE software components can function using one
activation key in the following cases:
software components
Multiple instances of FactoryTalk View Studio or the FactoryTalk View
SE Client running on the same computer can use a single key
(RSV.STUDIO or RSVSECLI), as long as the components are not running
in a Terminal Services session.
In the network application of FactoryTalk View SE versions earlier than
6.10, for development and testing purposes, one FactoryTalk View Studio
key activates a FactoryTalk View SE Client and SE Server on the same
computer. Remote clients and servers require component-specific
activations.
Note: In version 6.10 or higher, one FactoryTalk View Studio key can no longer activate the local
server or client to run in test run mode.
Read-write versus view-only In a network application, FactoryTalk View SE Clients can use two types of
activation:
activations
Read-write keys (RSVSECLI.RW) allow full read-write privileges.
View-only keys (RSVSECLI.RO) allow view-only privileges.
If the activation server can only provide view-only licenses, and a read-write
client obtains one of these licenses, then the activation overrides the client’s
configuration, and the client runs in view-only mode.
If the activation server can only provide read-write licenses, and a view-only
client obtains one of these licenses, then the client’s configuration overrides
the activation, and the client runs in view-only mode.
Do not rely on available activation keys to determine whether the
FactoryTalk View SE Client runs in read-write or view-only mode. Instead,
to ensure that a client always runs in view-only mode, choose the view-only
option when setting up the client’s configuration file. For details, click Help
in the FactoryTalk View SE Client wizard.
After developing and testing a FactoryTalk View Site Edition network distributed
application, you can deploy it to run in a live setting, such as the plant floor.
Deploying a network distributed application often involves installing FactoryTalk
View SE software components on multiple client and server computers.
For details about installing the software, see Install FactoryTalk View on page 35.
For details about the structure and content of network distributed applications,
see Chapter 6, Working with network distributed applications in the FactoryTalk
View Site Edition User’s Guide.
Overview of tasks The checklist in this section summarizes the basic tasks involved in deploying a
FactoryTalk View SE network distributed application. Each task is described in
detail in the rest of this chapter. Add or remove steps as necessary to create a
customized procedure that reflects the design and content of your FactoryTalk
View application. For example, your application might include additional
communications or database servers.
Step 1: Back up the network Before backing up an application, record the user names and passwords of
distributed application administrative users set up for the application, in case you need this information
after restoring the application.
Use the Distributed Application Manager tool to back up the application. The
backup archive has an .APB extension, and includes all FactoryTalk Directory
data, such as accounts, passwords, policies and security settings. It also includes all
Note: RSLinx Classic configuration files are not included when you back up a FactoryTalk View SE
application. You need to back up the RSLinx Classic configuration files manually. For
instructions, see Back up RSLinx Classic configurations on page 56.
1. On the HMI server, select Start > All Programs > Rockwell Software >
FactoryTalk View > Tools > Distributed Application Manager.
Tip: The logged on user must have the Backup and restore directory contents
permission. For more information, see FactoryTalk Security Help or check with your
System Administrator.
2. In the Create a Backup tab, select your application and follow the wizard to
back up the application. For more instructions, see Distributed Application
Manager Help.
Back up RSLinx Classic RSLinx Classic configuration files are not included when you back up an
configurations application. You have to back up, move, and restore the files manually.
Tip: You can also restore RSLinx Classic configuration files from the Wizard Completed
window of the RSLinx Classic software setup program.
3. Select a folder for the backup file, type a file name, and then click Save.
About FactoryTalk Directory The following illustration shows what a FactoryTalk View SE network distributed
application looks like when opened in FactoryTalk View Studio.
System information
For example, FactoryTalk user and computer accounts set up for each application
are stored in the System folder.
Note: FactoryTalk Linx device paths are also saved with System information, and might not be
correct for the computer where the application will be restored. For information about
checking device paths after restoring an application. see Verify FactoryTalk Linx shortcuts
on page 99.
Step 2: Restore the network Before restoring the network distributed application, all client and server
computers in the application must point to the same FactoryTalk Directory
distributed application server.
Use the Distributed Application Manager tool to restore the application. You
can restore the application to an existing or a new FactoryTalk Directory. You can
choose to restore the HMI project files only, the application only, the application
with FactoryTalk Directory, or the application with FactoryTalk Directory and
security identifier.
After restoring the application, restore the RSLinx Classic configures as need. See
Restore RSLinx Classic configurations on page 58.
To restore an application:
1. On the HMI server, select Start > All Programs > Rockwell Software >
FactoryTalk View > Tools > Distributed Application Manager.
Tip: The logged on user must have the Backup and restore directory contents
permission. For more information, see FactoryTalk Security Help or check with your
System Administrator.
3. Follow the wizard to restore the application. The following example shows
an overview of the tool when restoring an archive. For more instructions,
see Distributed Application Manager Help.
Restore RSLinx Classic RSLinx Classic configuration files are not included when you back up an
configurations application. You have to back up, move, and restore the files manually.
Tip: You can also restore RSLinx Classic configuration files from the Wizard Completed
window of the RSLinx Classic software setup program.
1. Copy the backup file (with .rsx extension) from the development computer
and paste it into a location on the data server production computer.
4. Find and select the backup file, and then click Open.
Step 3: Renew data server After restoring RSLinx data servers in the application, renew or verify the topics,
shortcuts, and device paths associated with each data server, as needed.
shortcuts, topics, and
device paths If you are restoring redundant data servers, then the device paths must be
confirmed and reapplied for both the primary and the secondary server.
2. In the Explorer window, expand the data server (FactoryTalk Linx), and
then double-click Communications Setup.
4. Save the configuration, and then close the Communications Setup editor.
1. On the data server computer, select Start > All Programs > Rockwell
Software > RSLinx > RSLinx Classic.
3. In the Topic List, select each configured topic and confirm that the
corresponding data source updates correctly.
Step 4: Set up additional After restoring the application, you can open the HMI server properties dialog
box in FactoryTalk View Studio to verify the HMI server settings and set up the
HMI server properties following HMI server properties, as needed.
You must set up the HMI server properties separately, for each server in the
FactoryTalk View SE network distributed application you are deploying. You can
do this on the computer running the HMI server, or from a remote computer.
For details about setting up HMI server properties, see Chapter 6, Working with
network distributed applications in the FactoryTalk View Site Edition User’s Guide.
For details about setting up redundant HMI servers, see Chapter 14, Setting up
FactoryTalk system availability in the FactoryTalk View Site Edition User’s Guide.
Specify the startup type In the General tab, you can specify that the HMI server will load when the first
client attempts to connect to it (On demand) or when the host computer starts
up (Load and run startup components when operating system initializes). The
second option is recommended for production HMI servers, and required for an
HMI server that is part of a redundant pair.
Set up redundancy In the Redundancy tab, select Provide redundancy using a secondary server,
specify the name the computer that will host the secondary server, and select a
switchover option.
After you apply the settings, FactoryTalk View SE automatically copies HMI
project information from the primary server to the secondary server.
Specify startup components In the Components tab, select the application components that will start
automatically when the HMI server starts, and select the macro that will run when
the server shuts down. You can also start or stop components manually.
If the HMI server is redundant, you can also start and stop components for the
primary and the secondary server, and select On active and On standby macros.
Synchronize redundant HMI At run time, you can make changes to the HMI project components in an
application while it is running. For example, you can add, modify or delete graphic
servers and projects
displays and other components, and have those changes to take effect at connected
clients. To automatically save the project online edits to both active and standby
servers:
1. In FactoryTalk View Studio, from the menu, select Tools > Options.
2. In the Settings tab, make sure the Save edits to both active and standby
HMI servers option is selected.
If you do not set up the option, manually replicate the changes from the active
server to standby server. The replicate operation copies the current active server’s
configuration files, including settings in the Components tab, to the standby
server.
For example, if an On Active and a Shutdown macro are selected for the Active
server, the settings will be replicated to the Standby server. This means that the
same macros specified for the Active server will run when the Standby server
becomes active or shuts down. Information that is not included in the replicate
operation includes datalog files generated at run time, the current value of HMI
memory tags, retentive tags, and the HMI tag alarm suppressed list.
Note: Make sure to verify the current HMI server name and status before the replication.
2. In the Server Status dialog box, verify that the current HMI server status is
Active and the other is Standby.
3. In the HMI server Properties dialog box, in the Redundancy tab, click
Replicate Active to Standby.
Step 5: Set up the The FactoryTalk View SE Client provides a complete and secure run-time
environment for an SE application. For example, operators can use the client to:
FactoryTalk View SE Clients
Load, view, and interact with graphic displays from any HMI server in the
application.
Monitor and control alarms (HMI tag alarms and FactoryTalk Alarms and
Events).
View and interact with trends.
Adjust set points.
Start and stop server components.
If you have already set up FactoryTalk View SE Client files for a network
distributed application, you can copy the files to the production computers.
Otherwise, you can create new client files.
Create a FactoryTalk View SE The FactoryTalk View SE Client configuration file specifies the name of the
application the client will connect to, the components that start when the
Client file
connection is made, and how the client will behave at run time. The file is with a
.cli extension.
Tip: It is not necessary to start the HMI server if you want to use the FactoryTalk View SE
Client Wizard.
1. From Windows Start menu, All Programs > Rockwell Software >
FactoryTalk View > FactoryTalk View Site Edition Client.
Copy existing FactoryTalk View When setting up the FactoryTalk View SE Clients for a network distributed
application, you can copy existing client files from the development computer to
SE Client files
the client production computers.
You can run the client configuration from the desktop, or from any other location
on the client computer.
Lock operators into the To lock operators into the FactoryTalk View SE Client at run time, for example,
to prevent access to other programs on the computer, try one or more of the
run-time environment
following methods:
Limit the ability to manipulate graphic displays, by removing the title bar
or minimize and maximize buttons from selected displays.
To do this, in the Display Settings dialog box, clear the check boxes Title
Bar, Minimize Button, and Maximize Button. For details, see Chapter 16,
Creating graphic displays in the FactoryTalk View Site Edition User’s Guide.
Limit the ability to manipulate the client window, by removing the title
bar or minimize and maximize buttons from the client.
To do this, in the FactoryTalk View SE Client wizard, clear the check boxes,
Show title bar, and Show system menu and close button. For details, click
Help in the FactoryTalk View SE Client wizard.
Note: Do not enable DeskLock until you read the help for the tool and understand how it works.
Otherwise, you could end up locking yourself out of the desktop.
Step 6: Run the FactoryTalk Once the network distributed application is fully deployed, test it by running the
FactoryTalk View SE Clients.
View SE Clients
To start the FactoryTalk View SE Client, or to change users while the client is
running, the user logging on must have the necessary security permissions. If the
user does not have the necessary permissions, the FactoryTalk View SE Client
login dialog box opens, to let another user log on.
Note: To connect a FactoryTalk View SE Client to a network distributed application, all client and
server computers in the application must point at the same FactoryTalk Network Directory
server. For details, see Specify the Network Directory location on application computers on
page 69.
For tips to help you get communications working between clients and servers, see
the FactoryTalk View Site Edition Help.
2. In the FactoryTalk View SE Client Wizard dialog box, select the client
configuration file from the list of most recently used files and click Run. To
search for and select another file, click the browse button.
For information about adding shortcuts to the Startup folder, see the Windows
Help
After you finish developing and testing a FactoryTalk View Site Edition network
station application, you can deploy it to run in a live setting, such as the plant
floor. Deploying a network station application involves installing all FactoryTalk
View SE software components on the application’s host computer.
For details about installing the software, see Install FactoryTalk View on page 35.
For details about the structure and content of network station applications, see
Chapter 7, Working with network station applications in the FactoryTalk View Site
Edition User’s Guide.
Overview of tasks The checklist in this section summarizes the basic tasks involved in deploying a
FactoryTalk View SE network station application. Use the checklist to guide you
through the tasks you need to perform. Each task is described in detail in the rest
of this chapter.
Step 1: Move the network There are two steps involved in moving a network station application: on the
station application development computer, back up the application; then, on the production
You can perform both of these steps in the Application Manager tool. For details
about options in the Application Manager, click Help in the tool.
Note: Before backing up an application, record the user names and passwords of administrative
users set up for the application, in case you need this information after restoring the
application.
1. From Windows Start menu, select Start > All Programs > Rockwell
Software > FactoryTalk View > Tools > Application Manager.
Tip: To back up a network station application, the logged on user must have
FactoryTalk administrative rights. If you receive a prompt to log on, check with
your System Administrator.
3. Select the back up operation, and then follow the instructions in the
Application Manager to complete the operation.
1. On the production computer, from Windows Start menu, select Start> All
Programs > Rockwell Software > FactoryTalk View > Tools >
Application Manager.
Tip: To restore a network station application, the logged on user must have FactoryTalk
administrative rights. If you receive a prompt to log on, check with your System
Administrator.
3. Select the restore operation, and then follow the instructions in the
Application Manager to complete the operation.
Step 2: Specify the Network If you have not done so already, use the FactoryTalk Directory Server Location
Utility to specify the location of the FactoryTalk Network Directory server.
Directory location
Performing this task might require more than one set of FactoryTalk security
credentials:
To use the FactoryTalk Directory Server Location Utility, you must have
administrative rights on the local computer.
To specify a remote location for the Network Directory, you must have
administrative rights on the remote computer.
1. On the client or server computer, select Start > All Programs > Rockwell
Software > FactoryTalk Tools > Specify FactoryTalk Directory
Location.
2. Click the Browse button beside the field, Computer hosting directory
server.
4. Type the name of the Network Directory server computer, or click the
Browse button to find and select the computer, and then click OK.
Step 3: Move the After specifying the FactoryTalk Network Directory location on application
computers, ensure that the required communications software (FactoryTalk Linx,
application’s data server RSLinx Classic, or other OPC software) is installed on computers that will run
files data servers.
Then, if necessary for the data servers you are deploying, move configuration files
to the production computers, and then specify the new host computer names.
Tip: For information about moving setup files for OPC data servers other than RSLinx
Classic, see the product documentation for the OPC server
Restore RSLinx Classic RSLinx Classic configuration files are not included when you back up an
application. You have to back up, move, and restore the files manually.
configurations
If RSLinx Classic is installed on the development and production computers, you
can use the RSLinx Classic Backup/Restore tool to back up and restore
configuration files.
Tip: You can also restore RSLinx Classic configuration files from the Wizard Completed
window of the RSLinx Classic software setup program.
1. Copy the backup file (with .rsx extension) from the development computer
and paste it into a location on the data server production computer.
4. Find and select the backup file, and then click Open.
Step 4: Specify data server After moving data server configuration files to production computers, open the
restored network station application, and in the Properties dialog box for each
host computer names data server, specify the name of the server’s host computer.
Then, renew RSLinx shortcuts, topics, and device paths, as needed. For details, see
Step 5: Renew data server shortcuts, topics, and device paths on page 71.
For information about setting up other data server properties, click Help in the
server’s Properties dialog box, or see the product documentation.
Tip: The first time you open an application after relocating a data server, if the server
does not load, you should still be able to open the Properties dialog box and
change the host computer name. After the computer name is updated, the server
should load as expected.
1. From Windows Start menu, select Start > All Programs > Rockwell
Software > FactoryTalk Administration Console.
2. In the Select FactoryTalk Directory dialog box, select Network, and then
click OK.
4. In the General tab, in the field, Computer hosting the FactoryTalk Linx
server, type the name of the production computer, or click Browse to find
and select the computer, and then click OK. Acknowledge the warning if
needed by clicking OK.
3. In the General tab, in the field, Computer that will run the OPC server,
type the name of the production computer, or click Browse to find and
select the computer, and then click OK.
Step 5: Renew data server After restoring the application, renew or verify the topics, shortcuts, and device
paths associated with each data server, as needed.
shortcuts, topics, and
device paths If you are restoring redundant data servers, then the device paths must be
confirmed and reapplied for both the primary and the secondary server.
2. In the Explorer window, expand the data server (FactoryTalk Linx), and
then double-click Communications Setup.
4. Save the configuration, and then close the Communications Setup editor.
3. In the Topic List, select each configured topic and confirm that the
corresponding data source updates correctly.
Step 6: Specify when HMI In FactoryTalk View Studio, open the Properties dialog box for the HMI server in
the application, to view the location of the HMI project files, the current number
server components start or of displays in the application, and the maximum number of displays allowed.
stop
You can add a description for the HMI server and, in the Components tab, select
components that will start when the HMI server starts running.
Tip: In a local station application, the HMI server and the application have the same
name. The name cannot be modified in the HMI server's Properties dialog box.
1. Click Start > All Programs > Rockwell Software, and then click
FactoryTalk View Studio.
2. Select View Site Edition (Network Station), and then click Continue.
3. Click the Existing tab, select the network station application’s name, and
then click Open.
4. In the Explorer window, right-click the HMI server’s name, and then click
Properties.
How HMI server components Use the HMI Server Properties dialog box to specify which components in a local
station application will start automatically, when the HMI server starts running.
start and stop
In a network station or local station application, the HMI server loads and the
specified components start running when the FactoryTalk View SE Client
connects to the application. When the client stops running, the HMI server is
unloaded, and the specified shutdown macro is run.
You can also start or stop the HMI server components manually. To do this, in the
Components tab, click Run Startup Components and Stop All Running
Components, respectively.
1. In the HMI Server Properties dialog box, click the Components tab.
2. To specify startup components, select the component check boxes, and then
select the components you want to start automatically, when the HMI
server starts running.
Step 7: Set up the The FactoryTalk View SE Client provides a complete and secure run-time
environment for an SE application. For example, operators can use the client to:
FactoryTalk View SE Client
Load, view, and interact with multiple graphic displays from the HMI
server.
Manage alarm information.
View trends.
Adjust set points.
Start and stop server components.
If you have already set up a FactoryTalk View SE Client file for the application,
you can copy the file to the production computer. Otherwise, you can create a new
client file.
Create a FactoryTalk View SE The FactoryTalk View SE Client configuration file specifies the name of the
application the client will connect to, the components that start when the
Client file
connection is made, and how the client will behave at run time. The file is with a
.cli extension.
Tip: It is not necessary to start the HMI server if you want to use the FactoryTalk View SE
Client Wizard.
1. From Windows Start menu, All Programs > Rockwell Software >
FactoryTalk View > FactoryTalk View Site Edition Client.
Lock operators into the To lock operators into the FactoryTalk View SE Client at run time, for example,
to prevent access to other programs on the computer, try one or more of the
run-time environment
following methods:
Limit the ability to manipulate graphic displays, by removing the title bar
or minimize and maximize buttons from selected displays.
To do this, in the Display Settings dialog box, clear the check boxes Title
Bar, Minimize Button, and Maximize Button. For details, see Chapter 16,
Creating graphic displays in the FactoryTalk View Site Edition User’s Guide.
Limit the ability to manipulate the client window, by removing the title
bar or minimize and maximize buttons from the client.
To do this, in the FactoryTalk View SE Client wizard, clear the check boxes,
Show title bar, and Show system menu and close button. For details, click
Help in the FactoryTalk View SE Client wizard.
Note: Do not enable DeskLock until you read the help for the tool and understand how it works.
Otherwise, you could end up locking yourself out of the desktop.
Step 8: Run the FactoryTalk Once the application is deployed, test it by running the FactoryTalk View
SE Client.
View SE Client
To start the FactoryTalk View SE Client, or to change users while the client is
74 Rockwell Automation Publication VIEWSE-IN003P-EN-E -February 2018
Deploy network station applications Chapter 7
running, the user logging on must have the necessary security permissions. If the
user does not have the necessary permissions, the FactoryTalk View SE Client
login dialog box opens, to let another user log on.
2. In the FactoryTalk View SE Client Wizard dialog box, select the client
configuration file from the list of most recently used files and click Run. To
search for and select another file, click the browse button.
For information about adding shortcuts to the Startup folder, see the Windows
Help
Administer deployed To make minor changes to an application after it is deployed, use either
FactoryTalk View Studio or the FactoryTalk View SE Administration Console.
applications The SE Administration Console contains the following subset of editors.
1. Select Start > All Programs > Rockwell Software > FactoryTalk View >
FactoryTalk View Studio.
Rockwell Automation Publication VIEWSE-IN003P-EN-E -February 2018 75
Chapter 7 Deploy network station applications
2. Select View Site Edition (Network Station), and then click Continue.
3. In the Existing tab, select the restored application’s name, and then click
Open.
After you finish developing and testing a FactoryTalk View Site Edition local
station application, you can deploy it to run in a live setting, such as the plant
floor. Deploying a local station application involves installing all FactoryTalk View
SE software components on the application’s host computer.
For details about installing the software, see Install FactoryTalk View on page 35.
For details about the structure and content of local station applications, see
Chapter 8, Working with local station applications in the FactoryTalk View Site
Edition User’s Guide.
Overview of tasks The checklist in this section summarizes the basic tasks involved in deploying a
FactoryTalk View SE local station application. Use the checklist to guide you
through the tasks you need to perform. Each task is described in detail in the rest
of this chapter.
Step 1: Move the local There are two steps involved in moving a local station application: on the
station application development computer, back up the application; then, on the production
computer, restore the application archive.
You can perform both of these steps in the Application Manager tool. For details
about options in the Application Manager, click Help in the tool.
Note: Before backing up an application, record the user names and passwords of administrative
users set up for the application, in case you need this information after restoring the
application.
1. On the desktop, click Start > All Programs > Rockwell Software >
FactoryTalk View > Tools > Application Manager.
2. In the Application Manager, select Site Edition (Local Station), and then
click Next.
Tip: The logged on user must have FactoryTalk administrative rights. If you receive a
prompt to log on, check with your System Administrator.
3. Select the back up operation, and then follow the instructions in the
Application Manager to complete the operation.
If you are restoring a local station application on a computer that contains a copy
of the original application, restart the computer, then use the Application
Manager to delete (or rename) the original application, before you begin the
restore operation.
1. On the production computer, click Start > All Programs > Rockwell
Software > FactoryTalk View > Tools > Application Manager.
Tip: To restore a local station application, the logged on user must have FactoryTalk
administrative rights. If you receive a prompt to log on, check with your System
Administrator.
3. Select the restore operation, and then follow the instructions in the
Application Manager to complete the operation.
About restoring System In FactoryTalk View Studio, in a local station application, the top-level System
folder contains FactoryTalk Security information, including user accounts set up
information with the
for all applications using the same FactoryTalk Local Directory (also called the
application Local Directory).
In the Application Manager tool, after specifying the archive to restore, select the
option, Restore the FactoryTalk View SE (local station) application and
FactoryTalk Local Directory.
To complete the operation, the user logged on to the Application Manager must
have FactoryTalk administrative rights at the Local Directory being restored.
Step 2: Move data servers A FactoryTalk View SE local station application can contain one FactoryTalk
Linx data server, which must be located on the same computer as the application.
and change their properties
In addition, the local station application can contain one or more OPC data
servers (RSLinx Classic, or some other OPC server), which can be located on
remote computers.
Tip: For information about moving setup files for OPC data servers other than RSLinx
Classic, see the product documentation for the OPC server.
After installing FactoryTalk Linx, RSLinx Classic, or some other OPC server
software on the production computer, if necessary, you can move the data server’s
setup files to the computer.
Restore RSLinx Classic RSLinx Classic configuration files are not included when you back up an
application. You have to back up, move, and restore the files manually.
configurations
If RSLinx Classic is installed on the development and production computers, you
can use the RSLinx Classic Backup/Restore tool to back up and restore
configuration files.
Tip: You can also restore RSLinx Classic configuration files from the Wizard Completed
window of the RSLinx Classic software setup program.
1. Copy the backup file (with .rsx extension) from the development computer
and paste it into a location on the data server production computer.
4. Find and select the backup file, and then click Open.
Step 3: Specify OPC data After moving RSLinx Classic configuration files to production computers, open
the restored local station application, and in the Properties dialog box for each
server host computer data server, specify the name of the server’s host computer.
names
Tip: Unlike RSLinx Classic data servers, you do not have to change the computer names
of FactoryTalk Linx data servers. The FactoryTalk Linx data server in a local station
application must be located on the same computer as the application, and is
always named localhost.
For information about setting up other data server properties, click Help in the
server’s Properties dialog box, or see the product documentation.
Tip: The first time you open an application after relocating a data server, if the server
does not load, you should still be able to open the Properties dialog box and
change the host computer name. After the computer name is updated, the server
should load as expected.
3. In the General tab, in the Computer that will run the OPC server field,
type the name of the production computer, or click Browse to find and
select the computer, and then click OK.
Step 4: Specify when HMI In FactoryTalk View Studio , open the Properties dialog box for the HMI server
in the application, to view the location of the HMI project files, the current
server components start or number of displays in the application, and the maximum number of displays
stop allowed.
You can add a description for the HMI server and, in the Components tab, select
components that will start when the HMI server starts running.
Tip: In a local station application, the HMI server and the application have the same
name. The name cannot be modified in the HMI server's Properties dialog box.
1. From Windows Start menu, select Start > All Programs > Rockwell
Software > FactoryTalk View Studio.
2. Select View Site Edition (Network Station), and then click Continue.
3. Click the Existing tab, select the network station application’s name, and
then click Open.
4. In the Explorer window, right-click the HMI server’s name, and then click
Properties.
How HMI server components Use the HMI Server Properties dialog box to specify which components in a local
station application will start automatically, when the HMI server starts running.
start and stop
In a network station or local station application, the HMI server loads and the
specified components start running when the FactoryTalk View SE Client
connects to the application. When the client stops running, the HMI server is
unloaded, and the specified shutdown macro is run.
You can also start or stop the HMI server components manually. To do this, in the
Components tab, click Run Startup Components and Stop All Running
Components, respectively.
1. In the HMI Server Properties dialog box, click the Components tab.
2. To specify startup components, select the component check boxes, and then
select the components you want to start automatically, when the HMI
server starts running.
Step 5: Set up the The FactoryTalk View SE Client provides a complete and secure run-time
environment for an SE application. For example, operators can use the client to:
FactoryTalk View SE Client
Load, view, and interact with multiple graphic displays from the HMI
server.
Manage alarm information.
View trends.
Adjust set points.
Start and stop server components.
If you have already set up a FactoryTalk View SE Client file for the application,
you can copy the file to the production computer. Otherwise, you can create a new
client file.
Create a FactoryTalk View SE The FactoryTalk View SE Client configuration file specifies the name of the
application the client will connect to, the components that start when the
Client file
connection is made, and how the client will behave at run time. The file is with a
.cli extension.
Tip: It is not necessary to start the HMI server if you want to use the FactoryTalk View SE
Client Wizard.
1. From Windows Start menu, All Programs > Rockwell Software >
FactoryTalk View > FactoryTalk View Site Edition Client.
Lock operators into the To lock operators into the FactoryTalk View SE Client at run time, for example,
to prevent access to other programs on the computer, try one or more of the
run-time environment
following methods:
Limit the ability to manipulate graphic displays, by removing the title bar
or minimize and maximize buttons from selected displays.
To do this, in the Display Settings dialog box, clear the check boxes Title
Bar, Minimize Button, and Maximize Button. For details, see Chapter 16,
Creating graphic displays in the FactoryTalk View Site Edition User’s Guide.
Limit the ability to manipulate the client window, by removing the title
bar or minimize and maximize buttons from the client.
To do this, in the FactoryTalk View SE Client wizard, clear the check boxes,
Show title bar, and Show system menu and close button. For details, click
Help in the FactoryTalk View SE Client wizard.
Note: Do not enable DeskLock until you read the help for the tool and understand how it works.
Otherwise, you could end up locking yourself out of the desktop.
Step 6: Run the FactoryTalk Once the application is deployed, test it by running the FactoryTalk View
SE Client.
View SE Client
To run an SE Client using the .cli file:
2. In the FactoryTalk View SE Client Wizard dialog box, select the client
configuration file from the list of most recently used files and click Run. To
search for and select another file, click the browse button.
For information about adding shortcuts to the Startup folder, see the Windows
Help
Administer deployed To make minor changes to an application after it is deployed, use either
FactoryTalk View Studio or the FactoryTalk View SE Administration Console.
applications The SE Administration Console contains the following subset of editors.
1. Click Start > All Programs > Rockwell Software > FactoryTalk View >
FactoryTalk View Studio.
2. Select View Site Edition (Local Station), and then click Continue.
3. In the Existing tab, select the restored application’s name, and then click
Open.
After installing the new software version, you should be able to open a
FactoryTalk View SE \application in FactoryTalk View Studio, and then run the
application in a FactoryTalk View SE Client without any further intervention.
Tip: Applications developed on versions 6.0 and earlier may need to be converted using
the Legacy Tag Database Conversion utility. To start the utility, from Windows
Start menu, select All Programs > Rockwell Software > FactoryTalk View >
Tools, right-click Legacy Tag Database Conversion and select Run as
administrator. For details about using the utility, click Help.
As there are many possible variations for this type of application, parts of the
documented process might not apply directly to the application you are upgrading.
If you have questions about architectural elements not covered in this chapter, for
example, your application is more or less complex than the example provided,
contact your local Rockwell Automation Sales office for assistance.
Note: Before installing FactoryTalk View applications or any supporting software, review
Hardware, operating system, and domain information on page 23, and ensure that you
have performed the tasks that are appropriate to the role and configuration of each
application host computer.
You can also look for answers in other Rockwell Automation product
documentation, and on the Rockwell Automation Web site. See Open
FactoryTalk View manuals on page 10.
Tip: RSView Enterprise is the former name of the FactoryTalk View family of software
products. If you are upgrading from a version of RSView, the information in this
chapter still applies, even though it refers to FactoryTalk View as the previous
product version.
Find out about features in After upgrading all the software components in your deployed application, to find
out about features in the new product version, see the product Release Notes.
the new product version
You can find Release Notes from:
Upgrade a non-redundant Use the following checklist as a guideline for upgrading your application. Details
network distributed about each step are provided in this chapter.
The FactoryTalk Directory server, HMI server, and data server are hosted
on different computers.
The Tag Alarm and Event server and HMI server are hosted on the same
computer.
Part 1: Prepare for the Use the following multi-step checklist as a guideline when you prepare for the
upgrade. For details, see procedures that follow.
upgrade
Have the FactoryTalk View installation package on hand
Step 1: Prepare for the upgrade
Log on with administrative rights on page 87
Record the names and passwords of administrative users on page 88
Perform set-up tasks on application computers on page 88
Log on with administrative rights To perform certain tasks, the user performing the upgrade must have
administrative rights in Windows and at the FactoryTalk Network Directory.
To open the utility, you must log on as a FactoryTalk administrator on the local
computer. To specify a remote Network Directory location, you must also have
administrative rights on the remote computer.
Record the names and passwords of Before backing up the deployed application, ensure that you have recorded the
administrative users user names and passwords of users that belong to the FactoryTalk administrators
group.
Perform set-up tasks on application Before upgrading FactoryTalk View SE, review the chapter Hardware, operating
computers system, and domain information on page 23. It contains information about tasks
you can perform on application computers, to ensure that FactoryTalk View SE
runs smoothly after it is installed. It also contains information about hardware and
software requirements, and application limits.
Step 2: Back up the deployed Before backing up the deployed application, ensure that the most recent
application data is available for the upgrade at the FactoryTalk Network
application
Directory.
Use the Distributed Application Manager tool to back up the application. The
backup archive has an .APB extension, and includes all FactoryTalk Directory
data, such as accounts, passwords, policies and security settings. It also includes all
application contents like application configurations, HMI servers, data servers,
and tag Alarm and Event servers.
Tip: RSLinx Classic configuration files are not included when you back up a FactoryTalk
View SE application. You need to back up the RSLinx Classic configuration files
before upgrading. For instructions, see Back up and restore RSLinx Classic
configurations on page 58.
1. On the HMI server, select Start > All Programs > Rockwell Software >
FactoryTalk View > Tools > Distributed Application Manager.
Tip: The logged on user must have the Backup and restore directory contents
permission. For more information, see FactoryTalk Security Help or check with your
System Administrator.
2. In the Create a Backup tab, select your application and follow the wizard to
back up the application. For more instructions, see Distributed Application
Manager Help.
Step 4: Upgrade the FactoryTalk 1. On the FactoryTalk Directory computer, close all open Windows
programs.
Directory server
2. Double-click Setup.exe within the installation package.
Tip: If you host the FactoryTalk Network Directory, HMI server, and data server on the
same computer, select Studio Enterprise.
4. Follow the instructions to finish the installation. For more information, see
Install FactoryTalk View on page 35.
Tip: If you host the FactoryTalk Network Directory, HMI server, and data server on the
same computer, skip to Step 7: Upgrade the engineering workstation on page 90.
Step 5: Upgrade the HMI server 1. On the HMI server computer, close all open Windows programs.
3. On the Welcome page, select Site Edition Server and click Next.
5. Follow the instructions to finish the installation. For more information, see
Install FactoryTalk View on page 35.
Step 6: Upgrade the data server 1. On the FactoryTalk Linx data server computer, close all open Windows
programs.
4. Follow the instructions to finish the installation. For more information, see
Install FactoryTalk View on page 35.
Step 7: Upgrade the 1. On the engineering workstation computer, close all open Windows
programs.
engineering workstation
2. Double-click Setup.exe within the installation package.
5. Follow the instructions to finish the installation. For more information, see
Install FactoryTalk View on page 35.
Step 8: Migrate the application Use the following checklist as a guideline when you migrate the FactoryTalk View
SE application:
1. On Workstation #1, select Start > All Programs > Rockwell Software >
FactoryTalk View > FactoryTalk View Studio.
2. Select View Site Edition (Network Distributed) and then click Continue.
5. Wait until the HMI server and all project components in the application
are loaded, and then leave the application open in FactoryTalk View Studio.
Verify FactoryTalk Linx shortcuts To confirm that data communications are set up correctly in the migrated
application, verify that FactoryTalk Linx shortcuts point at the correct devices.
1. In FactoryTalk View Studio, expand the data server FactoryTalk Linx, and
then double-click Communications Setup.
Test the migrated application To test the migrated application, run the application on Workstation #1.
Step 9: Upgrade all run-time If you already have the Client Install Portal feature installed on the HMI server,
you can upgrade the clients through a web browser. For detailed instructions, see
clients
Install SE clients in a distributed system on page 47. Otherwise, you can use the
installation package. Follow the instructions below.
1. On the client computers, close all software programs that are currently
running.
3. On the Welcome page, select Site Edition Client and click Next.
4. Follow the instructions to finish the installation. For more information, see
Install FactoryTalk View on page 35.
Step 10: Test the migrated To test the migrated FactoryTalk View SE application, perform these tasks:
application Run the migrated application on upgraded clients on page 92
Verify that the system is functioning as expected on page 92
Run the migrated application on On each of the upgraded run-time client computers, run the existing FactoryTalk
upgraded clients View SE Client configuration file (.cli).
Verify that the system is functioning After the application starts running on the upgraded client computers, verify that
as expected display navigation, object animation, communications, alarming (if configured),
and other applications features are functioning as expected.
Upgrade a redundant Upgrading a redundant system can be done in parts, allowing you to keep your
system running without redundancy temporarily while you upgrade. During an
network distributed upgrade, a temporary system can help you with verification and validation.
application
Use the following multi-step checklist as a guideline for upgrading your redundant
system. Details about each step are provided in this chapter.
In this example, Server #1 is the name of the primary server computer, Server #2
is the name of the secondary server computer, and Workstation #1 is the name of
the engineering workstation. Assume that:
The FactoryTalk Directory server, primary data server, primary HMI server,
and primary Tag Alarm and Event server are located on Server #1.
The secondary data server, secondary HMI server, and secondary Tag Alarm
and Event server are located on Server #2.
Part 1: Prepare for the Use the following multi-step checklist as a guideline when you prepare for the
upgrade. For details, see the procedures that follow.
upgrade
Have the FactoryTalk View installation package on hand
Step 1: Prepare for the upgrade
Log on with administrative rights on page 93
Record the names and passwords of administrative users on page 94
Perform set-up tasks on application computers on page 94
Ensure that the latest application files are on the primary server on page 94
Log on with administrative rights To perform certain tasks, the user performing the upgrade must have
administrative rights in Windows and at the FactoryTalk Network Directory.
To open the utility, you must log on as a FactoryTalk administrator on the local
computer. To specify a remote Network Directory location, you must also have
administrative rights on the remote computer.
Record the names and passwords of Before backing up the deployed application, ensure that you have recorded the
administrative users user names and passwords of users that belong to the FactoryTalk administrators
group.
Perform set-up tasks on application Before upgrading FactoryTalk View SE, review the chapter Hardware, operating
computers system, and domain information on page 23. It contains information about tasks
you can perform on application computers, to ensure that FactoryTalk View SE
runs smoothly after it is installed. It also contains information about hardware and
software requirements, and application limits.
Ensure that the latest application During the upgrade described in this chapter, the application and HMI project
files are on the primary server files backed up on the primary server are restored on the secondary server, and
then migrated in FactoryTalk View Studio on the upgraded engineering
workstation.
To ensure that you migrate and re-deploy the most recent application, ensure that
the application and HMI project files you back up initially, on the primary server,
are the most recent application files.
Step 2: Back up the application Before backing up the deployed application, ensure that the most recent
application data is available for the upgrade on Server #1.
on Server #1
Use the Distributed Application Manager tool to back up the application. The
backup archive has an .APB extension, and includes all FactoryTalk Directory
data, such as accounts, passwords, policies and security settings. It also includes all
application contents like application configurations, HMI servers, data servers,
and tag Alarm and Event servers.
Tip: RSLinx Classic configuration files are not included when you back up a FactoryTalk
View SE application. You need to back up the RSLinx Classic configuration files
before upgrading. For instructions, see Back up and restore RSLinx Classic
configurations on page 58.
1. On Server #1, select Start > All Programs > Rockwell Software >
FactoryTalk View > Tools > Distributed Application Manager.
Tip: The logged on user must have the Backup and restore directory contents
permission. For more information, see FactoryTalk Security Help or check with your
System Administrator.
2. In the Create a Backup tab, select your application and specify the Host
Machine as Server #1.
3. Follow the wizard to back up the application on Server #1. For more
instructions, see Distributed Application Manager Help.
Part 2: Set up a temporary During this part, a temporary system is set up to test a partial upgrade that
involves Server # 2, Workstation #1, and selected run-time clients. For the test,
system and perform a Server #2 is set up to function as the primary server.
partial upgrade
Tip: It is recommended that you upgrade the software on some application clients,
confirm that the upgraded application is running as expected, and then upgrade
the software on the remaining clients. The number of clients to upgrade initially is
left to your discretion.
Step 3: Set up a temporary As part of the process, the original HMI project and application files that were
backed up on Server #1 are restored on Server #2. The restored application will
upgrade system
be migrated later, after Workstation #1 is upgraded.
To set up a temporary system so that you can test a partial upgrade, perform the
tasks below. For details, see the procedures that follow.
Disable HMI and data server redundancy in the original application on page
96
Copy the archive file to Server #2 on page 96
Specify Server #2 as the Network Directory location on page 96
Restore the application on Server #2 as the primary server on page 97
Specify Server #2 as the Network Directory location for Workstation #1 on
page 97
Disable redundancy on Server #2 on page 97
Disable alarm and event history logging on page 98
Disable HMI and data server To ensure that Server #2 can be detached from the application for upgrading,
redundancy in the original open the application in FactoryTalk View Studio, and disable redundancy for the
application HMI server and data server.
2. In the Explorer window, right-click the HMI server and select Properties.
3. In the Redundancy tab, clear the check box Provide redundancy using a
secondary server, and click OK.
4. In the Explorer window, right-click the data server FactoryTalk Linx and
select Properties.
5. In the Redundancy tab, clear the check box Provide redundancy using a
secondary server, and click OK.
Copy the archive file to Server #2 Move the archive file (*.apb) created on Server #1 to Server #2.
Specify Server #2 as the Network 1. On Server #2, select Start > All Programs > Rockwell Software >
Directory location FactoryTalk Tools > Specify FactoryTalk Directory Location.
Tip: To use the utility, you have to log on as an administrator on the local computer.
2. Click the Browse button beside the field Computer hosting directory
server.
Tip: To change the Network Directory location, you have to log on as an administrator
on the new Network Directory computer (local or remote).
Restore the application on Server #2 1. On Server #2, select Start > All Programs > Rockwell Software >
as the primary server FactoryTalk View > Tools > Distributed Application Manager.
Tip: The logged on user must have the Backup and restore directory contents
permission. For more information, see FactoryTalk Security Help or check with your
System Administrator.
3. Follow the wizard to restore the application. For more instructions, see
Distributed Application Manager Help.
Specify Server #2 as the Network 1. On Workstation #1, select Start > All Programs > Rockwell Software >
Directory location for Workstation #1 FactoryTalk Tools > Specify FactoryTalk Directory Location.
Tip: To use the utility, you have to log on as an administrator on the local computer.
2. Click the Browse button besides the field Computer hosting directory
server.
Tip: To change the Network Directory location, you have to log on as an administrator
on the new Network Directory computer (local or remote).
Disable redundancy on Server #2 1. On Workstation #1, open the restored application in FactoryTalk View
Studio.
2. In the Explorer window, right-click the HMI server and select Properties.
3. In the Redundancy tab, clear the check box Provide redundancy using a
secondary server, and click OK.
4. In the Explorer window, right-click the data server FactoryTalk Linx and
select Properties.
5. In the Redundancy tab, clear the check box Provide redundancy using a
secondary server, and click OK.
Disable alarm and event history After you restore the application, the alarm and event history logging is also
logging enabled on Server #2. It is recommended that you disable the history logging.
Follow the steps below.
2. In the Explorer window, right-click the Tag Alarm and Event server and
select Properties.
3. In the Priorities and History tab, clear the Enable history check box and
click OK.
Step 4: Upgrade Server #2 To upgrade the software components, install FactoryTalk View SE and any
necessary products updates on Server #2.
3. On the Welcome page, select Site Edition Server and click Next.
4. Follow the instructions to finish the installation. For more information, see
Install FactoryTalk View on page 35.
Step 5: Upgrade Workstation #1 To upgrade the software components, install FactoryTalk View Studio and any
necessary products updates on Workstation #1.
4. Follow the instructions to finish the installation. For more information, see
Install FactoryTalk View on page 35.
Step 6: Migrate the application To migrate the FactoryTalk View SE application that was restored on Server #2,
perform these tasks:
1. On Workstation #1, select Start > All Programs > Rockwell Software >
FactoryTalk View > FactoryTalk View Studio.
2. Select View Site Edition (Network Distributed) and then click Continue.
5. Wait until the HMI server and all project components in the application
are loaded, and then leave the application open in FactoryTalk View Studio.
Verify FactoryTalk Linx shortcuts To confirm that data communications are set up correctly in the migrated
application, verify that FactoryTalk Linx shortcuts point at the correct devices.
1. In FactoryTalk View Studio, expand the data server FactoryTalk Linx, and
then double-click Communications Setup.
Test the migrated application To test the migrated application, run the application on Workstation #1.
Step 7: Upgrade selected To upgrade the software components, install FactoryTalk View SE Client and any
necessary products updates on the selected run-time clients. Perform these tasks
run-time clients
on each client computer. For details, see the procedures that follow.
you can upgrade the clients through a web browser. For detailed instructions, see
Install SE clients in a distributed system on page 47. Otherwise, you can use the
installation package. Follow the instructions below.
1. On the client computers, close all software programs that are currently
running.
3. On the Welcome page, select Site Edition Client and click Next.
4. Follow the instructions to finish the installation. For more information, see
Install FactoryTalk View on page 35.
Specify Server #2 as the Network After upgrading the software on the client computer, specify Server #2 as the
Directory location on client Network Directory location.
computers
To specify Server #2 as the Network Directory:
1. On each of the client computers, select Start > All Programs > Rockwell
Software > FactoryTalk Tools > Specify FactoryTalk Directory
Location.
Tip: To use the utility, you have to log on as an administrator on the local computer.
2. Click the Browse button besides the field Computer hosting directory
server.
Tip: To change the Network Directory location, you have to log on as an administrator
on the new Network Directory computer (local or remote).
Step 8: Test the migrated To test the migrated application before upgrading remaining application
computers, perform these tasks:
application
Start Server #2 and wait for it to finish starting on page 101
Run the migrated application on upgraded clients on page 101
Verify that the system is functioning as expected on page 101
Start Server #2 and wait for it to If Server #2 is not already started, start the server and wait for the server to finish
finish starting starting.
1. On Server #2, select Start > All Programs > Rockwell Software >
FactoryTalk Tools > Diagnostics Viewer.
Tip: To find a message faster in the Diagnostics Viewer, on the View menu, click
Options. Then, in the Filter tab, create a Message filter with one or more
keywords from the message.
Run the migrated application on On each of the upgraded run-time client computers, run the existing FactoryTalk
upgraded clients View SE Client configuration file (.cli).
Verify that the system is functioning After the application starts running on the upgraded client computers, verify that
as expected display navigation, object animation, communications, alarming (if configured),
and other applications features are functioning as expected.
Part 3: Upgrade remaining This part involves upgrading the remaining run-time clients and Server # 1, and
restoring the redundancy. After upgrading, Server #2 becomes the primary server
clients and restore and Server #1 becomes secondary.
redundancy
Step 9: Upgrade remaining After testing the partially upgraded system, on the remaining client computers,
install FactoryTalk View SE Client and point at Server #2 as the Network
client computers
Directory. Perform these tasks:
1. On the client computers, close all software programs that are currently
running.
3. On the Welcome page, select Site Edition Client and click Next.
4. Follow the instructions to finish the installation. For more information, see
Install FactoryTalk View on page 35.
Specify Server #2 as the Network After upgrading the software on the client computer, specify Server #2 as the
Directory location on client Network Directory location.
computers
To specify Server #2 as the Network Directory:
1. On each of the client computers, select Start > All Programs > Rockwell
Software > FactoryTalk Tools > Specify FactoryTalk Directory
Location.
Tip: To use the utility, you have to log on as an administrator on the local computer.
2. Click the Browse button besides the field Computer hosting directory
server.
Tip: To change the Network Directory location, you have to log on as an administrator
on the new Network Directory computer (local or remote).
Step 10: Upgrade Server #1 To upgrade FactoryTalk View SE and supporting software on Server #1, install
FactoryTalk View SE Server and set up Server #1 to point at Server #2. Perform
these tasks:
3. On the Welcome page, select Site Edition Server and click Next.
4. Follow the instructions to finish the installation. For more information, see
Install FactoryTalk View on page 35.
Specify Server #2 as the Network 1. On Server #1, select Start > All Programs > Rockwell Software >
Directory for Server #1 FactoryTalk Tools > Specify FactoryTalk Directory Location.
Tip: To use the utility, you have to log on as an administrator on the local computer.
2. Click the Browse button beside the field Computer hosting directory
server.
Tip: To change the Network Directory location, you have to log on as an administrator
on the new Network Directory computer (local or remote). In this case, the new
location is remote.
Step 11: Restore redundancy Before finishing the upgrade, you need to enable the redundancy and check the
server status. If the status is not right, restart Server #1 and Server #2. Perform
and finish upgrading
the following tasks:
3. In the Redundancy tab, select the check box Provide redundancy using a
secondary server.
4. Under the Secondary Server area, type Server #1 and click OK.
5. In the Explorer window, right-click the data server FactoryTalk Linx and
select Properties.
6. In the Redundancy tab, select the check box Provide redundancy using a
secondary server.
7. Under the Computer running secondary server field, type Server #1 and
click OK.
8. From the menu, select Tools > Options. In the Settings tab, make sure the
Save edits to both active and standby HMI servers option is selected.
Enable alarm and event history If the alarm and event history logging is already disabled on Server #2, follow the
logging steps below to enable the history logging.
2. In the Explorer window, right-click the Tag Alarm and Event server and
select Properties.
3. In the Priorities and History tab, select the Enable history check box,
select the database and click OK.
Confirm the status of primary and On Workstation #1, in FactoryTalk View Studio, right-click the HMI server and
secondary servers then select Server Status.
Server #2 and Active status are displayed in the fields Primary server and
Primary status respectively.
Server #1 and Standby status are displayed in the fields Secondary server
and Secondary status respectively.
Tip: To switch the Active server to Server #1, click Switchover.
Start all run-time clients To ensure that the entire, upgraded application is functioning as expected, run the
existing FactoryTalk View SE Client configuration file on each run-time client
computer.
FactoryTalk View tools To run the following set of tools, select Start > All Programs > Rockwell
Software > FactoryTalk View > Tools, and then click the tool you want to run.
SE HMI Tag Alarm Log Setup is software for setting up HMI tag alarm
logging.
SE HMI Tag Alarm Log Viewer is software for viewing the contents of
HMI tag alarm log files.
SE Service Manager is a tool that allows you to stop or start the
FactoryTalk View HMI Service manually on the computer.
Tag Import and Export Wizard is software for importing or exporting the
FactoryTalk View SE Server’s tag database.
FactoryTalk tools To run the following tool, select Start > All Programs > Rockwell Software >
FactoryTalk Alarms and Events, and then click the tool you want to run.
To run the following set of tools, select Start > All Programs > Rockwell
Software > FactoryTalk Tools, and then click the tool you want to run.
This section contains notes, common procedures and information from the
Rockwell Automation Knowledgebase that you may find helpful during
installation of FactoryTalk View products.
Install product updates After installing FactoryTalk View SE, you should locate and install patches for the
software products on your system. To locate patches, search the Rockwell
Automation Knowledgebase for Patch TOCs (Tables of Contents). The TOCs
contain lists of all available patches for your software. Go to
http://rockwellautomation.custhelp.com and select the Search Knowledgebase
tab.
A Patch TOC describes updates released for a particular product and version, and
provides instructions for downloading and installing the updates on computers
where the software is installed.
2. On the Rockwell Automation Support Center page, click the down arrow
on the Search Knowledgebase tab and select By Product.
3. Scroll down to Software and click on FactoryTalk View SE. In the Search
box, type Patch TOC and click Search.
In the search results, look for Patch TOCs related to all the products you
installed. If necessary, conduct additional searches for other newly-installed
applications, including:
SE Client
SE Server
SE Station
Studio Enterprise
FactoryTalk Services Platform
FactoryTalk Alarms and Events
FactoryTalk Linx
RSLinx Classic
This appendix servers as a reference to help you troubleshoot issues and verify IIS
settings.
Manually install IIS The steps may vary because of different versions and configurations. Follow the
on-screen instructions that apply to the operating systems you are using. If
necessary, install IIS from your Microsoft Windows operating system installation
package.
4. Expand the Web Management Tools folders, and then expand the IIS 6
Management Compatibility folder.
5. Select the IIS Metabase and IIS 6 configuration compatibility check box.
6. Expand the World Wide Web Services folder and then expand the
Application Development Features folder.
7. Select the ASP check box. The ISAPI Extensions check box should then be
selected automatically.
8. Under the World Wide Web Services folder, expand the Common
HTTP Features folder.
9. Under World Wide Web Services folder, expand the Security folder.
Tip: If IIS is installed correctly, you should be able to open the HMI server status page
on localhost first, then from another computer. To test this, open Internet Explorer,
in the address field, type http://localhost/rsviewse, or
http://computername/rsviewse then press Enter.
2. (Windows Server 2008 R2) In the Server Manager window, under Roles
Summary, click Add Roles.
3. Use the Add Roles Wizard (or Add Roles and Features Wizard) to add the
Web Server (IIS) role.
4. To install the Web Server, some additional Windows features might need to
be installed. In each case, click Add Required Features.
The following example shows the installation for Windows Server 2008 R2.
The following example shows the installation for Windows Server 2008 R2.
10. Click Next, and then accept the default selections at each remaining step of
the wizard by clicking Next until all of the steps are complete.
Rockwell Automation Publication VIEWSE-IN003P-EN-E -February 2018 111
Appendix C Install Microsoft IIS
11. At the end of the wizard, click Install to install the Web Server role.
About uninstalling IIS If for some reasons, you need to uninstall and then reinstall IIS, after reinstalling,
you need to recreate the virtual directories in IIS.
You can typically use this installation method for unattended installation.
Perform command-line The command-line installation requires the administrator permission. The steps
may vary slightly depending on your operating system.
installation
To perform command-line installation:
Command-line parameters The following table identifies the installation command-line parameters.
Command-line parameters are case-insensitive. However, if a specified value
includes a space, be sure to enclose the value in quotation marks (for example,
"value with spaces").
Parameter Description
/? Shows the usage options for installation parameters.
Parameter Description
/Q Silent Install. Install runs in a quiet mode without any user interface.
This parameter is recommended if you are deploying the software installation using an IT tool or script, and don’t
expect to see any error or restart messages. When using this parameter, your IT tool or script should check the
error codes, and respond as needed. For example, if the installation returns error code 1641, then the IT tool or
script should restart the computer and relaunch the installation after restart.
This parameter is required if /QS or /Record is not specified.
/QS Unattended Install. Install runs in a quiet simple mode and shows progress through the UI. It does not accept any
input, but still shows error or restart messages.
When using this parameter, you will not have to check the error codes, and the installation will stop and show a
prompt if there are error or restart messages. For example, if an immediate restart is required to complete the
install, a restart message will be shown for you to confirm the restart. Installation resumes automatically from
the point of interruption after restart.
This parameter is required if /Q or /Record is not specified.
/IAcceptAllLicenseTerms Acknowledges acceptance of the license terms and agreement to continue the installation.
This parameter is required.
/AutoRestart Automatically restarts the computer after the installation is complete. Used when a restart is required to
complete the installation.
This parameter is optional. If this parameter is not used, silent install (/Q) will return error code 1641 or 3010 if a
restart is required, and unattended install (/QS) will result in a confirmation prompt that must be agreed to
before the installation is completed.
/SetupLanguage="value" Specifies which language will be shown during install process.
The value must be one of the following:
ENU
CHS
DEU
ESP
FRA
ITA
JPN
KOR
PTB
This parameter is optional. If this parameter is not used, the default language is the current user or operating
system user interface language.
/Record Records the installation options chosen to a recording file.
This parameter is optional.
/Playback Plays back a recording file to specify the installation options.
This parameter is optional.
Parameter Description
/Product="value" Specifies which product will be installed.
The value must be the one of following:
Studio Enterprise
Site Edition Server
Site Edition Client
Site Edition Station
FactoryTalk ViewPoint SE
Stand-alone FactoryTalk Linx Server
Stand-alone FactoryTalk Directory Server
This parameter is required.
/Uninstall Uninstalls components that are already installed with the product specified.
This parameter is optional.
/ProductLanguage="value" Specifies the language version of the software being installed.
The value must be one of the following:
ENU
CHS
DEU
FRA
JPN
This parameter is optional. If this parameter is not used, the default language is the same as the setup language.
If the software does not support multiple languages, this parameter is not available.
/SerialNumber="value" Specifies the serial number of the software being installed. This is used to activate the software during
installation.
This parameter is optional. If it is not specified the software must be activated manually after installation if
activation is required.
Some software does not require activation. If activation is not required, this parameter is not available.
/ProductKey="value" Specifies the product key used to get activation keys during installation.
This parameter is optional. If it is not specified, the software must be activated manually after installation if
activation is required.
Some software does not require activation. If activation is not required, this parameter is not available.
/Version="value" Specifies the version of the software to activate which corresponds to the product version associated with the
SerialNumber and ProductKey.
This parameter is optional. If it is not specified, the installer will use the most recent product version available.
Some software does not require activation. If activation is not required, this parameter is not available.
Error codes
The following table identifies the error codes that can be returned by an
installation.
Examples The following examples show how to use the commands for the installation.
means:
means:
Setup.exe /Record
means
FactoryTalk View will open the Setup wizard and record your selections
during the installation.
When complete, FactoryTalk View will save the recording file to your
desktop.
Setup.exe /Q /IAcceptAllLicenseTerms
/Playback="C:\Users\Public\FactoryTalk View Studio
Enterprise.rec"
means:
FactoryTalk View will use the recording file FactoryTalk View Studio
Enterprise.rec to complete the installation.
Example 5: Uninstall
means:
FactoryTalk View Studio Enterprise and the components that are installed
with FactoryTalk View Studio Enterprise will be uninstalled.
Components, such as FactoryTalk Activation Manager, that are shared with
other products will not be uninstalled.
If you are using KEPServer Enterprise as an OPC server with FactoryTalk View
version 9.00.00 or later and using an HMI tag to connect to a third-party device,
you will not be able to access the tag value. The cause is that the security
enhancements in FactoryTalk View version 9.00.00 or later affect the
communications with third-party devices. To access the tag value, additional
Distributed Component Object Model (DCOM) configuration is required for
KEPServer Enterprise on the computers.
If you are using a direct reference tag through the KEPServer Enterprise OPC
server, you can access the tag value successfully.
Set DCOM configuration for In the following steps, KEPServer Enterprise 5.19 is used as an example. The steps
also apply to earlier versions of KEPServer Enterprise.
KEPServer Enterprise
To set DCOM configuration for KEPServer Enterprise
Tip: You can open Component Services from Control Panel > Administrative Tools,
or use the search box on the Windows Start menu or the taskbar. For more
information about how to open Component Services, see Windows Help.
2. From the console tree, select Component Services > Computers > My
Computer > DCOM Config.
a. Click Add.
c. Click OK.
c. Click OK.
8. On the Security tab, in the Access Permissions area, select Customize and
click Edit. The Access Permission dialog box opens.
10. Allow Local Access permission and Remote Access permission for LOCAL
SERVICE. For detailed instruction, see step 7.
F
D FactoryTalk Alarms and Events
Data Execution Prevention (DEP) hardware requirements 23
setting up 33 FactoryTalk Diagnostics Viewer 100
data servers FactoryTalk Directory 17
backing up and restoring RSLinx Classic 59 FactoryTalk Directory Configuration Wizard 106
moving files 69, 79 FactoryTalk Linx
renewing shortcuts, topics, and device paths 59, 99 backing up and restoring device paths 68
troubleshooting loading 80 FactoryTalk Services Platform 19
DCOM protocols FactoryTalk Help 86
removing unnecessary 33 FactoryTalk tools and utilities 106
deploying local applications 67, 77 FactoryTalk View SE Alternate Website Setup 105
backing up 68, 77 FactoryTalk View SE Cache Management Tool 105
backing up the Local Directory 78 FactoryTalk View SE Client 17
creating new client files 64 copying client files 65
moving RSLinx Classic files 59 creating new client files 64
restoring 68, 77 file locations 65, 66, 83
restoring the Local Directory 78 setting up security 65
starting or stopping HMI servers 80 starting 66, 83
updating data server names 70 starting when Windows starts 83
deploying network applications 55 using .cli file 66, 83
backing up 55 FactoryTalk View SE Server 17
changing HMI server properties 60 FactoryTalk View Site Edition 15
copying client files 65 documentation set ix 9
creating new client files 64 installing 35
restoring 58 release notes 9
synchronizing HMI servers with projects 63 upgrading 85
updating data server names 70 FactoryTalk View Studio 16
DeskLock 65, 105 file locations
device paths SE Client files 65, 66, 83
126 Rockwell Automation Publication VIEWSE-IN003P-EN-E -February 2018
Index
M
H moving files
hardware requirements 23 data servers 69, 70, 79, 80
FactoryTalk Alarms and Events 23
HMI Server Backup and Restore utility 105
HMI servers 17, 73
N
setting up properties 60 naming
starting or stopping 60, 73 computers 28, 70, 80
synchronizing with projects 63 data server computers 70, 80
troubleshooting computer names 28
network applications
I run-time clients 64
Import RSSecurity Configuration 106 security 65
incompatible firewalls 31 troubleshooting 66
installing Network Directory
choosing components 36 specifying location 45, 96
FactoryTalk View SE 35 network interface cards (NIC)
product updates 107 disabling power saving 31
troubleshooting 85 duplex 30
upgrading 85 troubleshooting 30
Internet Explorer network switches
removing enhanced security configuration 31 troubleshooting 30
Internet Information Services (IIS) networks
configuring 109 removing unnecessary DCOM protocols 33
uninstalling 112
Internet technical support 10
O
OLE for Process Control (OPC)
K renaming data servers 80
keys using for communications 20
FactoryTalk Activation 51 online Help
sharing for FactoryTalk Activation 52 FactoryTalk Services Platform 86
Rockwell Automation Publication VIEWSE-IN003P-EN-E -February 2018 127
Index
T U
Tag Import and Export Wizard 105 Unattended installation 35, 113
technical support 10 Uninstall FactoryTalk View 105
testing unmanaged switches
upgraded applications 100 auto-negotiation 29, 30
third-party firewalls using 29, 30
incompatible 31 upgrading 49, 85
time about activation keys 50, 51, 52
synchronizing on computers 27 backing up and restoring 94
using scheduled downtime for upgrades 95 disabling redundancy 96
tools and utilities 106 from RSView Enterprise to FactoryTalk View 86
Alarm Log Setup 105 grace period 49
Alarm Log Viewer 105 installing product updates 107
Application Documenter 105 non-redundant applications 86
Application Manager 68, 105 planning 93
DeskLock 65, 105 read-write keys 52
Diagnostics Viewer 106 run-time clients 99, 101
FactoryTalk 106 servers 97, 98, 101, 102
FactoryTalk Directory Configuration Wizard 106 sharing activation keys 52
FactoryTalk View SE Alternate Website Setup 105 testing applications 100
FactoryTalk View SE Cache Management Tool 105 troubleshooting 49, 51, 96
HMI Server Backup and Restore 105 upgrading for borrowed activation files 51
Import RSSecurity Configuration 106 using scheduled downtime 95
Log On to FactoryTalk 106 view-only keys 52
Rockwell Software Data Client 106 workstations 98, 99, 101
RSSecurity Emulator Install 106
SE HMI Tag Alarm Log Setup 105
SE HMI Tag Alarm Log Viewer 105
V
SE Service Manager 105 virtual directories
Specify FactoryTalk Directory Location 45, 96, 106 recreating in IIS 112
Tag Import and Export Wizard 105
Uninstall FactoryTalk View 105
W
Windows Firewall Configuration Utility 106
topics Windows
renewing after backup and restore 59, 99 compatibility 27
troubleshooting file locations 66, 83
applications 66 firewall 31
clients 66 service packs 27
data servers 80 starting SE Client with Windows 83
FactoryTalk Activation 49 Windows Firewall Configuration Utility 106
network applications 66 workgroups
network interface cards (NIC) 30 design considerations 26
network switches 30 setting up 26
redundancy 60, 63 system requirements 27
workstations
upgrading 98, 99, 101
Rockwell Automation Publication VIEWSE-IN003P-EN-E -February 2018 129
Index
In addition, we offer multiple support programs for installation, configuration, and troubleshooting. For more information, contact your local
distributor or Rockwell Automation representative, or visit http://www.rockwellautomation.com/services/online-phone .
Installation assistance
If you experience a problem within the first 24 hours of installation, review the information that is contained in this manual. You can contact
Customer Support for initial help in getting your product up and running.
United States Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to
your distributor to complete the return process.
Outside United States Please contact your local Rockwell Automation representative for the return procedure.
Documentation feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this document, complete the
feedback form, publication RA-DU002.
Supersedes Publication VIEWSE-IN003O-EN-E Copyright © 2018 Rockwell Automation Technologies, Inc. All Rights Reserved. Printed in the U.S.A.