Viewse In003 - en e
Viewse In003 - en e
Original Instructions
Connectivity............................................................................................................................................................................................................................................................................ 10
Installation package..............................................................................................................................................................................................................................................................10
System requirements.............................................................................................................................................................................................................................. 11
Pre-installation configuration................................................................................................................................................................................................................15
Steps.........................................................................................................................................................................................................................................................................................18
Deploy applications................................................................................................................................................................................................................................27
FactoryTalk tools................................................................................................................................................................................................................................................................... 47
Uninstalling IIS.......................................................................................................................................................................................................................................................................53
Command-line parameters..................................................................................................................................................................................................................................................54
Examples................................................................................................................................................................................................................................................................................. 57
Legal Notices......................................................................................................................................................................................................................................... 59
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.
These labels may also be on or inside the equipment to provide specific precautions.
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).
Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this publication are not in alignment with the movement toward
inclusive language in technology. We are proactively collaborating with industry peers to find alternatives to such terms and making changes to our products and content.
Please excuse the use of such terms in our content while we implement these changes.
Preface
You can also search for technical notes, application tips, solutions to common problems, and the latest patches from Rockwell Automation Knowledgebase https://
rockwellautomation.custhelp.com.
If you cannot find the answer, contact Rockwell Automation Customer Support, using any of these methods:
Support staff are available Monday to Friday from 8:00 to 17:00 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:
If you are running a FactoryTalk View SE network distributed application, also note:
Which computers are running clients (FactoryTalk View SE Client or FactoryTalk View Studio).
FactoryTalk View provides monitoring and control solutions designed to span stand-alone machine-level applications up through supervisory-level HMI applications across
a network.
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.
FactoryTalk View Studio is the design-time environment for FactoryTalk View that provides the editors and tools you need to develop and test network distributed, network
station, and local station human-machine interface (HMI) applications. It contains editors for creating complete applications, and contains client and server software for
testing the applications you create.
• 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.
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).
• For Site Edition applications, the FactoryTalk ViewPoint Server runs on a desktop or server computer.
• For Machine Edition applications, a PanelView™ Plus operator terminal functions as the server.
FactoryTalk Directory
The FactoryTalk Directory centralizes access to system resources and names for all FactoryTalk products and components participating in an automated control system.
The FactoryTalk Network Directory manages resources for FactoryTalk View SE network applications, and the FactoryTalk Local Directory manages resources for
FactoryTalk View SE local applications.
To distribute device-based and tag-based alarms in a FactoryTalk View SE application, you can set up FactoryTalk Alarms and Events servers in the application.
FactoryTalk Security
FactoryTalk Security centralizes user authentication and authorization at the FactoryTalk Directory.
FactoryTalk Diagnostics
FactoryTalk Diagnostics collects and provides access to activity, status, warning, and error messages generated throughout a FactoryTalk system.
FactoryTalk Activation
FactoryTalk Activation services provide a secure, software-based system for activating Rockwell Software products and managing software activation files.
Connectivity
How you plan to obtain data for an application will determine which communications software you install.
You can use FactoryTalk Linx, RSLinx Classic, or other software and devices that support OPC (OLE for Process Control) communications.
FactoryTalk Linx
FactoryTalk Linx is a communication server built around FactoryTalk technology to assist in developing and running your FactoryTalk View SE applications.
For communications with Allen-Bradley local and remote devices, particularly with Studio 5000 controllers, FactoryTalk Linx is the recommended data communications
software for FactoryTalk View applications.
FactoryTalk Linx allows you to create redundant controller shortcuts and to perform online tasks such as uploading and downloading Studio 5000 Logix Designer files.
Installation package
The Setup wizard offers the following options for FactoryTalk View SE applications:
• 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 Setup wizard offers the following options for FactoryTalk View ME applications:
System requirements
This chapter introduces computer and Microsoft Windows support information for a FactoryTalk View SE system, including:
If a network application requires multiple HMI servers, data servers, or alarm servers, to distribute the load, it is recommended that you install the necessary software and
run the servers on multiple host computers.
For information about setting up redundant FactoryTalk View SE servers, see FactoryTalk View Site Edition User’s Guide.
The following is a sample specification of computer hardware to run FactoryTalk View SE applications aligned with the hardware used in product development testing.
Recommended specifications for application servers are not as flexible, because server computers are more likely to host critical components and to handle more of the
processing load in a FactoryTalk View SE application.
FactoryTalk View SE is tested on operating systems installed from original Microsoft media only. FactoryTalk View SE runs on the following Windows operating systems:
* For more information, see Rockwell Automation Knowledgebase Document ID: IN4493 - Windows 10 Support for the FactoryTalk Suite of Rockwell Software
products.
A client can be any of FactoryTalk View SE Client, FactoryTalk View Studio, the FactoryTalk View SE Administration Console, a FactoryTalk Historian SE connector, a
FactoryTalk Transaction Manager connector, or another FactoryTalk View SE Server.
More than 10 client connections, the recommended operating systems (with the appropriate number of Client Access Licenses installed)
• Windows 11
• Windows 10
NOTE: Do not run the primary and secondary servers in a redundant server pair on the computers that have different operating systems. For
example, do not run the primary server on a Windows Server 2019 computer and the secondary server on a Windows Server 2022 computer.
Workgroups can be used only in applications that include 20 or fewer computers. Do not use Windows Workgroups with more than 20 computers, a Windows domain is
recommended in that case.
For more information about setting up domains and workgroups, see the document, FactoryTalk View SE Distributed System Design Considerations, attached to
Knowledgebase Document ID: IN3416 - FactoryTalk View SE Distributed System Design Considerations.
• A domain controller makes it possible to administer the network and user accounts from a central location. FactoryTalk Security, which manages centralized
security services, supports Windows-linked accounts that are managed and authenticated by the Windows operating system, but have separate permissions for
accessing the automation system.
• Name resolution is required for the computers to communicate with each other on the network.
• All computers participating in a single FactoryTalk system must be members of the same Windows domain.
• Do not locate the domain controller on the same computer as any FactoryTalk software. Microsoft recommends against third party software being installed on a
domain controller.
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.
• 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 security for applications
in a Windows workgroup, it is recommended that you use the FactoryTalk Directory user accounts. This simplifies account management, by centralizing security
services at the FactoryTalk Directory.
Time synchronization
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
configured on all application computers.
For more information about synchronizing application computer clocks to an authoritative time server, see FactoryTalk View SE Design Considerations, attached to
Knowledgebase Document ID: IN3416 - FactoryTalk View SE Distributed System Design Considerations.
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 Knowledgebase Document ID: BF20782 - FactoryTalk View SE: Inability to
access FactoryTalk Network Directory after renaming computer (for FactoryTalk View SE network applications), or QA3873 - Renaming a PC with ME/SE Local
Security (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:
NOTE: Windows updates should be disabled in all production computers. Updates can cause unexpected behaviors, including shutting down running
applications and automatically restarting the computer.
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 FactoryTalk View SE applications, it is recommended that you use managed switches across the control system network and that you manually configure the same link
speed and duplex setting for all network connections into the managed switches.
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 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.
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.
If installed on a computer with FactoryTalk View SE software components, the Internet Explorer ESC can interfere with the ability of FactoryTalk View SE Clients to connect
to application servers.
To avoid unexpected behavior, it is recommended that you remove the ESC from computers running FactoryTalk View SE.
To remove ESC:
1. On the Windows taskbar, select the Server Manager icon.
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.
4. In the Internet Explorer Enhanced Security Configuration dialog box, select Off to turn off IE Enhanced Security for Administrators and for Users, and then click
OK.
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, and then select System and Security > System.
2. Under Related settings on the left, select Advanced system settings.
3. On the Advanced tab of the System Properties dialog box, under Performance, click Settings.
4. In the Performance Options dialog box, click the Data Execution Prevention tab.
5. Select Turn on DEP for essential Windows programs and services only, and then click OK.
3. In the Component Services tool, expand Component Services, open the Computers folder, right-click My Computer, and then select Properties.
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.
To learn about upgrading an existing version of FactoryTalk View SE, see Upgrade an operating FactoryTalk View SE application on page 32.
To learn about modifying or uninstalling the FactoryTalk View software, see Modify or uninstall FactoryTalk View on page 22.
Steps
FactoryTalk View supports the Setup wizard installation and command-line installation.
Command-line installation
In the command-line installation, you type a specified command line with multiple parameters. During the installation process, instead of prompting you for installation
and configuration information interactively, the process follows the parameters specified in the command lines and completes the installation silently. For more
information, see Use command-line installation on page 54.
The Setup wizard offers the following options for FactoryTalk View SE applications:
• 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 Setup screen, the following table shows the mandatory, recommended and optional software components to install.
Studio Enterprise Studio Enterprise Site Edition Server FactoryTalk Historian Connectivity* (2)
Site Edition Client* (1) FactoryTalk ViewPoint SE FactoryTalk Updater Agent* (3)
FactoryTalk Services Platform FactoryTalk ViewPoint ME
FactoryTalk Activation Manager
Site Edition Station Site Edition Server Studio Enterprise FactoryTalk Historian Connectivity
Site Edition Client FactoryTalk ViewPoint SE FactoryTalk Updater Agent
FactoryTalk Services Platform
FactoryTalk Activation Manager
FactoryTalk Alarms and Events
FactoryTalk Linx
Stand-alone FactoryTalk Directory Server FactoryTalk Services Platform FactoryTalk Updater Agent
FactoryTalk Activation Manager
1. Site Edition Client is not mandatory if you do not plan to install FactoryTalk ViewPoint SE.
2. For more information about FactoryTalk Historian Connectivity, see About FactoryTalk Historian Connectivity on page 19.
3. For more information about FactoryTalk Updater Agent, see Common upgrade procedures on page 49.
To trend data points from the FactoryTalk Historian SE server, FactoryTalk Historian ME model, or OSIsoft® PI Server™, FactoryTalk Historian Connectivity must be installed
as a minimum required component with Site Edition Client or Studio Enterprise.
Tip: You cannot install FactoryTalk Historian Connectivity on top of FactoryTalk Historian SE.
Before you start using the trending objects with your FactoryTalk Historian SE server, do the following:
• Add the FactoryTalk Historian SE server to the same FactoryTalk Directory as FactoryTalk View SE computers.
• Create a mapping or trust for security between FactoryTalk View SE and FactoryTalk Historian SE.
For detailed instructions, see FactoryTalk View SE TrendX and TrendPro in FactoryTalk Historian SE Installation and Configuration Guide.
IMPORTANT: If you install Studio Enterprise, Site Edition Server, or FactoryTalk ViewPoint SE on a computer with no FactoryTalk View
component installed, the installation enables HTTPS by default. You can select Customize to disable HTTPS.
For secure communication, HTTPS protocol is recommended. If HTTPS is enabled, you must configure a TLS certificate after installation. If you do
not configure the certificate, there will be unexpected errors when operating FactoryTalk View SE components. For details, see Configure a TLS
certificate on page 21.
With HTTPS enabled, port 443 is used by default. However, if port 443 is already in use by other web applications (such as Node.js web server), this
will cause a port conflict. To avoid the port conflict, after the installation, change the port number used by FactoryTalk View SE in:
◦ Site binding in Internet Information Services (IIS) Manager
◦ FactoryTalk View SE's HTTPS protocol properties in FactoryTalk Administration Console
If you want to install a FactoryTalk View SE component on a computer installed with any FactoryTalk View SE component, the installation will keep
the original settings.
FactoryTalk Batch View HMI controls are installed with Site Edition Client and Studio Enterprise by default.
Tip:
You will have to log on as an administrator on the computer.
Tip:
You will have to log on as an administrator on the computer.
Certificates from your organization's internal Certificate Authority (CA) and a commercial CA are supported. If you want to use a commercial certificate, you need to obtain
it by sending a request to a CA. Once you have a certificate, install it on all HMI server and FactoryTalk View Studio computers.
The steps may vary on different operating systems. Follow the on-screen instructions that apply to the operating system you are using. This instruction uses Windows 10
as an example.
Tip: The Setup wizard detects and installs IIS automatically if IIS is not available on the computer.
After installing the certificate, make sure the TLS certificate is selected for the HTTPS site binding.
where
ComputerName is the name of the computer hosting the installation package.
4. Press Enter.
For more information about installation parameters, see Command-line parameters on page 54.
• From the installation package, double-click Setup.exe, select one product and click Uninstall.
• From Programs and Features of Windows Control Panel, right-click the installed FactoryTalk View product and select Uninstall.
• From the Command Prompt window, type a command with the following syntax:
Setup.exe [/Q | /QS] /Uninstall /Product=product_name
Components, such as FactoryTalk Activation Manager, that are shared with other products will not be uninstalled. For more information about command-line
parameter, see Command-line parameters on page 54.
• Floating concurrent activations are checked out of an activation server located on the network, and require a continuous network connection.
• Borrowed concurrent activations are time-expiring activations checked out of an activation server on the network, and do not require a continuous network
connection.
For standard installations of the product software, FactoryTalk View SE does not support node-locked activations.
• 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.
Tip: As of FactoryTalk View SE version 13, activation is no longer required to implement web clients in a system. FactoryTalk ViewPoint is included as a built-in
feature with no additional cost. FactoryTalk ViewPoint is also included with FactoryTalk View SE version 11 and 12 with a patch installed.
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 Redundancy Server (network distributed applications), unlimited displays FTVSERED.MAX
FactoryTalk View SE Client (network distributed applications), read and write RSVSECLI.RW
FactoryTalk View SE Station (network station and local station applications), unlimited RSVSE.MAX
displays
FactoryTalk View SE Station Lite (network station and local station applications), 25 displays RSVSE.25
• 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 or a Remote Desktop Services session. However, within that single Terminal Services or Remote
Desktop Services session, the client activation key is sharable.
Tip: Starting from FactoryTalk View SE version 11.0 and ThinManager version 11.0, a single FactoryTalk View SE Client license is required per
ThinManager-managed terminal. This allows you to deliver an unlimited number of sessions (either for ThinManager MultiSession or Failover) and
consume only that one SE Client license per ThinManager-managed terminal.
• Local applications use a single key (RSVSE.*) to activate both the FactoryTalk View SE Client and the FactoryTalk View SE Server at runtime. These components
running together are also known as FactoryTalk View SE Station. To run multiple station client instances on the same server computer, make sure to launch the
clients first and then the server. Otherwise, two activation keys may be required.
• If you want to switch from a station application to a network distributed application, use the original station key to activate the remote display client in the
network distributed application.
The type of license obtained by the client decides whether a FactoryTalk View SE Client runs in read-write or 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.
Deploy applications
After you finish developing and testing a FactoryTalk View Site Edition application, you can deploy it to run in a live setting, such as the plant floor.
This chapter shows the steps of deploying network distributed applications, network station applications, and local station applications. Most steps are common for the
three types of applications. Those that are unique to a certain application are marked with a note.
Tip:
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.
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. On the Create a Backup tab, select your application and follow the wizard to back up the application.
3. Copy the .apb file to the production computer.
If you are restoring an application on a computer that contains a copy of the original application, use FactoryTalk View SE Application Manager to delete or rename the
original application, before you begin the restore operation.
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. In the Restore an Archive tab, specify the restore options and follow the wizard.
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, see the product documentation for the OPC server.
If you are restoring redundant data servers, then the device paths must be confirmed and reapplied for both the primary and the secondary server.
If you are deploying a network distributed application, you must set up the HMI server properties separately for each server in the system. You can do this on the computer
running the HMI server or from a remote computer.
For a network distributed application, 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.
NOTE: This topic only applies to when you deploy network distributed applications.
On 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
NOTE: This topic only applies to when you deploy network distributed applications.
On 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.
To automatically save the project online edits to both active and standby servers, in FactoryTalk View Studio, from the menu, select Tools > Options. On the Settings tab,
make sure the Save edits to both active and standby HMI servers option is selected. To keep the HMI memory tag values the same on both active and standby servers,
on the same tab, select the Auto synchronize HMI memory tag values to both active and standby HMI servers option.
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 runtime, the current value of HMI memory tags, and retentive tags.
NOTE:
Make sure to verify the current HMI server name and status before the replication.
Tip: To show the status of the HMI servers, FactoryTalk Alarm and Event servers, and data servers at runtime, add one of the following to the
application:
◦ A Server Status display under the Library folder.
◦ A redundancy function, such as PrimaryServerStatus and SecondaryServerStatus.
3. In the HMI Server Properties dialog box, in the Redundancy tab, click Replicate Active to Standby.
When using a network station or local station application, the FactoryTalk View SE Client must run on the same computer as the HMI server.
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.
Tip: It is not necessary to start the HMI server if you want to use the FactoryTalk View SE Client Wizard.
By default, auto logout is enabled for 10 minutes, which means the current logged-on user will be automatically logged out if there is no mouse or keyboard activity in 10
minutes. You can cancel this option on the FactoryTalk View SE Client Wizard's Advanced settings > Security and debugging tab.
• 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 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.
• Prevent switching to other applications. To do this, in the FactoryTalk View SE Client wizard, select the check box, Disable switch to other applications. For
details, click Help in the FactoryTalk View SE Client wizard.
• Restrict access to the desktop, using the DeskLock tool.
To open Desklock, on the desktop select Start > Rockwell Software > DeskLock.
For details about using DeskLock, click Help within the tool.
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.
• Restrict access to system files via the Windows file explorer when saving the trace data or captured image of TrendPro and XY Plot.
To do this, use the CustomFileExplorer VBA property by setting it to True. When saving the trace data or captured image, the custom file explorer opens instead
of the Windows file explorer.
You can run the client configuration from the desktop, or from any other location on the client computer.
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 server location on page 20.
Import and export HMI tags. Tag Import and Export Wizard
For details about these editors or more administrative operations, see FactoryTalk View SE Help.
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, select
Start > Rockwell Software, right-click Legacy Tag Database Conversion and select Run as administrator. For details about using the utility, click Help.
Depending on the design, content, and complexity of your control system, you might have to perform additional tasks to support the upgrade, especially if you are
upgrading FactoryTalk View SE in a production environment.
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.
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.
In this example, Workstation #1 is the name of the engineering workstation. Assume that:
• 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.
• Windows administrative rights are required to install FactoryTalk View and supporting software.
• FactoryTalk administrative rights are required to log on to the FactoryTalk Network Directory, back up and restore FactoryTalk View SE applications, etc.
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. On the Create a Backup tab, select your application and follow the wizard to back up the application.
Tip: If you host the FactoryTalk Network Directory, HMI server, and data server on the same computer, select Studio Enterprise, and skip to Step 7:
Upgrade the engineering workstation on page 34.
4. Follow the instructions to finish the installation. For more information, see Install FactoryTalk View on page 18.
5. After installation, install any necessary product updates. For more information, see Install product updates on page 49.
3. On the Setup page, select Studio Enterprise and click Install now.
4. If you have FactoryTalk Historian Management Tools installed, you need to manually uninstall the Management Tools Suite and the System Management Tools
before installing FactoryTalk Historian Connectivity. For more information, see Knowledgebase Document ID: QA25767 - FactoryTalk View SE v8.00 (CPR 9 SR 7):
The "FactoryTalk Historian Connectivity" option.
5. Follow the instructions to finish the installation. For more information, see Install FactoryTalk View on page 18.
6. After installation, install any necessary product updates. For more information, see Install product updates on page 49.
3. On the Setup page, select Site Edition Client and click Install now.
4. Follow the instructions to finish the installation. For more information, see Install FactoryTalk View on page 18.
5. After installation, install any necessary product updates. For more information, see Install product updates on page 49.
Example
The following illustration shows an example of a FactoryTalk View SE network distributed application with redundant servers.
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.
• Windows administrative rights are required to install FactoryTalk View and supporting software.
• FactoryTalk administrative rights are required to log on to the FactoryTalk Network Directory, back up and restore FactoryTalk View SE applications, etc.
Ensure that the latest application files are on the primary server
During the upgrade, the application and HMI project 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 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.
Use the FactoryTalk View SE 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: 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 FactoryTalk View SE Application Manager Help.
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 Description
1 First, set up Server #2 as the Network Directory and primary HMI and data server (without
redundancy). Then, upgrade the software on Server #2.
2 Next, upgrade the software components on Workstation #1, and then migrate the restored
application.
3 Finally, upgrade the software components on some runtime clients only, and then test the
partial upgrade.
NOTE: To avoid introducing incompatible software component versions into a deployed production system, be sure to restore the HMI project and
application files before upgrading any software.
To set up a temporary system so that you can test a partial upgrade, perform the tasks below.
• Disable HMI and data server redundancy in the original application on page 40
• Copy the archive file to Server #2 on page 40
• Specify Server #2 as the Network Directory location on page 40
• Restore the application on Server #2 as the primary server on page 40
• Specify Server #2 as the Network Directory location for Workstation #1 on page 40
• Disable redundancy on Server #2 on page 41
• Disable alarm and event history logging on page 41
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.
3. In the FactoryTalk Directory Server Configuration dialog box, select This computer and click OK.
Tip:
To change the Network Directory location, you have to log on as an administrator on the new Network Directory computer (local or remote).
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 Restore an Archive tab, specify the restore scope as Restore application, with FactoryTalk Directory and the Primary Host as Server #2.
3. Follow the wizard to restore the application.
Tip:
To change the Network Directory location, you have to log on as an administrator on the new Network Directory computer (local or remote).
If your system has controller device-based alarms, follow the steps below to disable the history logging.
1. In the Explorer window, right-click the FactoryTalk Linx Data server and select Properties.
2. In the Alarms and Events tab, clear the Enable history check box and click OK.
4. Follow the instructions to finish the installation. For more information, see Install FactoryTalk View on page 18.
5. After installation, install any necessary product updates. For more information, see Install product updates on page 49.
Tip:
To change the Network Directory location, you have to log on as an administrator on the new Network Directory computer (local or remote).
Start Server #2
If Server #2 is not already started, start the server and wait for the server to finish starting.
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.
Tip:
To change the Network Directory location, you have to log on as an administrator on the new Network Directory computer (local or remote).
4. Follow the instructions to finish the installation. For more information, see Install FactoryTalk View on page 18.
5. After installation, install any necessary product updates. For more information, see Install product updates on page 49.
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.
If your system has controller device-based alarms, follow the steps below to enable the history logging.
1. In the Explorer window, right-click the FactoryTalk Linx Data server and select Properties.
2. In the Alarms and Events tab, select the Enable history check box, select the database and click OK.
• 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.
To run the tools, select Start > Rockwell Software and then select the tool in the list of apps. The steps may vary depending on your operating system.
• Application Documenter
Used to view the contents of the application’s components and the tags used in these components.
• DeskLock
Used to prevent users of FactoryTalk View SE Client and FactoryTalk View ME from gaining access to the Windows desktop and system keys.
• FactoryTalk View Alarm Migration Tool
Used to migrates legacy HMI alarms to FactoryTalk Alarms and Events tag-based alarms.
• FactoryTalk View File Viewer
Used to view and save log files such as SE datalog files, ME datalog files, ME alarm log files and dBASE file.
• FactoryTalk View SE Application Manager
Formerly known as Distributed Application Manager, used to manage all types of SE applications (network distributed, network station, and local station).
• FactoryTalk View SE Cache File Management Tool
Used to manage the temporary files of HMI Server components.
• FactoryTalk View SE Website Setup Tool
Used to enable the HTTPS protocol over the default website and create a custom website on an HMI server computer.
• HMI Server Backup and Restore
Used to back up FactoryTalk View SE HMI servers while they are running. Use this utility when backing up or restoring a stand-alone system, or when deploying a
distributed system from one set of computers to another.
• Legacy Tag Database Conversion Utility
Used to convert legacy tag database (before View 6.0) to a new format to work with Microsoft SQL database.
• SE Administration Console
Used to administer FactoryTalk View SE applications after they are deployed. Use the sub-set of editors available in the Administration Console to make minor
changes to an application without installing FactoryTalk View Studio.
Tip:
SE Administration Console will close automatically after being open for two hours.
• SE Service Manager
Used to stop or start the FactoryTalk View HMI service manually on the computer.
• Tag Import and Export Wizard
Used to import or export the FactoryTalk View SE Server’s tag database.
FactoryTalk tools
Use the following tools for FactoryTalk or FactoryTalk Alarms and Events:
• Diagnostics Viewer
Used to view the contents of FactoryTalk Diagnostics logs, to help with troubleshooting the system.
Rockwell Automation Knowledgebase provides the updates through the Patch Tables of Contents (TOCs). 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.
Use the FactoryTalk Updater tool to assist with the update. For instructions, see Update from the product on page 49.
You can also manually search Rockwell Automation Knowledgebase and locate the latest updates. For instructions, see Update from Rockwell Automation Knowledgebase
on page 49.
Tip: To receive notifications of new versions and patch roll-ups, the tool requires access to the Download Center web service. Verify that the firewall
does not block access to this URL: https://api.rockwellautomation.com/es-be-pcdc-vpcprod/
This appendix servers as a reference to help you troubleshoot issues and verify IIS settings.
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.
The following example shows the installation for Windows Server 2019.
8. Click to expand Management Tools and then expand IIS 6 Management Compatibility.
9. Under IIS 6 Management Compatibility, select IIS 6 Metabase Compatibility.
The following example shows the installation for Windows Server 2019.
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.
11. At the end of the wizard, click Install to install the Web Server role.
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.
Use RSViewWebManager to recreate the virtual directories. The default location is:
The unattended installation is an automated installation method that reduces user interaction. It is typically used for large-scale rollouts when it might be too slow and
costly to have administrators or technicians interactively install FactoryTalk View on individual computers.
For more information about parameters, type Setup.exe /? or see Command-line parameters on page 54.
Command-line parameters
Use command-line parameters to perform an unattended or silent installation of the software.
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
/Q Silent Install, install runs in a quiet mode without any user interface.
This parameter is recommended when deploying the software installation using an IT tool
or script, and don’t expect any error or restart messages. When using this parameter, 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 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, the installation will stop and display 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 displayed to confirm the restart. Installation resumes automatically
from the point of interruption after restart.
This parameter is required if /Q is not specified.
Parameter Description
/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 either
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 displayed during the install process.
The value must be the 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.
/DirectoryServer="value" Specifies the FactoryTalk network directory if you are using a distributed system.
This parameter is optional. If it is not specified, the software will use its current computer as
the FactoryTalk Directory server.
Parameter Description
The value must be the host name of the FactoryTalk Directory server.
/SystemStatusPortal="value" Specifies that the installation includes the FactoryTalk System Status Portal.
This parameter is optional.
The value must be one of the following:
• Yes
The FactoryTalk System Status Portal will be installed.
• No
The FactoryTalk System Status Portal will not be installed.
/IISCommPort Specifies the IIS server communication port for HTTPS. The default port for HTTPS is 443.
If the HTTPS port was previously configured using FactoryTalk Services Platform, like port
4356, then the existing HTTPS port setting is retained.
This parameter is optional.
/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.
For FactoryTalk Services Platform commands to back up and restore directory, system, and applications, see FactoryTalk Security System Configuration Guide.
The following table identifies the error codes that can be returned by an installation.
ERROR_BAD_CONFIGURATION 1610 The configuration data for this product is corrupt. Contact
your support personnel.
ERROR_SUCCESS_REBOOT_INITIATED 1641 The installer has initiated a restart. After restart, the
installation will continue.
ERROR_REBOOT_PENDING 3012 Restart pending. Restart the computer for the installation to
continue.
ERROR_SUCCESS_NOT_APPLICABLE 3013 The installation cannot proceed because the products are
already installed.
Examples
The following examples show how to use the commands for the installation.
means:
means:
means:
• FactoryTalk View Studio Enterprise will be installed with customized FactoryTalk Directory server. ServerName is host name of the customized FactoryTalk
Directory server.
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.
means:
• FactoryTalk View will use the recording file FactoryTalk View Studio Enterprise.rec to complete the installation.
Example 6: Uninstall
Setup.exe /Q /Uninstall /Product="Studio Enterprise"
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.
Legal Notices
Rockwell Automation publishes legal notices, such as privacy policies, license agreements, trademark disclosures, and other terms and conditions on the Legal Notices
page of the Rockwell Automation website.
You can view a full list of all open source software used in this product and their corresponding licenses by opening the oss_license.txt file located in your product's
OPENSOURCE folder on your hard drive. This file is divided into these sections:
• Components
Includes the name of the open source component, its version number, and the type of license.
• Copyright Text
Includes the name of the open source component, its version number, and the copyright declaration.
• Licenses
Includes the name of the license, the list of open source components citing the license, and the terms of the license.
You may obtain Corresponding Source code for open source packages included in this product from their respective project web site(s). Alternatively, you may obtain
complete Corresponding Source code by contacting Rockwell Automation via the Contact form on the Rockwell Automation website: http://www.rockwellautomation.com/
global/about-us/contact/contact.page. Please include "Open Source" as part of the request text.
Component Copyright
Technical Support Center Find help with how-to videos, FAQs, chat, user forums, and rok.auto/support
product notification updates.
Local Technical Support Phone Numbers Locate the telephone number for your country. rok.auto/phonesupport
Product Compatibility and Download Center (PCDC) Get help determining how products interact, check features rok.auto/pcdc
and capabilities, and find associated firmware.
Documentation feedback
Your comments help us serve your documentation needs better. If you have any suggestions on how to improve our content, complete the form at rok.auto/docfeedback.
Rockwell Automation maintains current product environmental information on its website at rok.auto/pec.