WSP Install Guide v2014

(1)

Wonderware

Wonderware System

Platform Installation

Guide

(2)

All rights reserved. No part of this documentation shall be reproduced, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of Invensys Systems, Inc. No copyright or patent liability is assumed with respect to the use of the information contained herein. Although every precaution has been taken in the

preparation of this documentation, the publisher and the author assume no responsibility for errors or omissions. Neither is any liability assumed for damages resulting from the use of the information contained herein.

The information in this documentation is subject to change without notice and does not represent a commitment on the part of Invensys Systems, Inc. The software described in this documentation is furnished under a license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of these agreements.

Invensys Systems, Inc.

26561 Rancho Parkway South Lake Forest, CA 92630 U.S.A. (949) 727-3200

http://www.wonderware.com

For comments or suggestions about the product documentation, send an e-mail message to [email protected].

All terms mentioned in this documentation that are known to be trademarks or service marks have been appropriately capitalized. Invensys Systems, Inc. cannot attest to the accuracy of this information. Use of a term in this documentation should not be regarded as affecting the validity of any trademark or service mark.

Alarm Logger, ActiveFactory, ArchestrA, Avantis, DBDump, DBLoad, DT Analyst, Factelligence, FactoryFocus, FactoryOffice, FactorySuite, FactorySuite A2_{, InBatch, InControl, IndustrialRAD,}

IndustrialSQL Server, InTouch, MaintenanceSuite, MuniSuite, QI Analyst, SCADAlarm, SCADASuite, SuiteLink, SuiteVoyager, WindowMaker, WindowViewer, Wonderware, Wonderware Factelligence, and Wonderware Logger are trademarks of Invensys plc, its subsidiaries and affiliates. All other brands may be trademarks of their respective owners.

(3)

3

Chapter 1 Wonderware System Platform Installation...9

Preparing for Wonderware System Platform Installation ... 9

Wonderware System Platform Prerequisites ... 9

About SQL Server Requirements ... 11

Selecting a Type of Installation ... 11

About Product-Based Installation ... 11

About Role-Based Installation ... 11

ArchestrA User Account ... 12

About ArchestrA User Account Privileges ... 13

Changing the ArchestrA User Account ... 13

Installing the Wonderware System Platform ... 14

Configuring Products ... 24

Modifying an ArchestrA User Account ... 26

Modifying an Installation ... 26

Repairing an Installation ... 28

Uninstalling a Wonderware System Platform Component ... 29

Upgrading a Wonderware System Platform Component ... 30

Installing a Product License ... 30

Chapter 2 Application Server Requirements and

Prerequisites ... 31

(4)

4 Contents

SQL Server Rights Requirements ... 33

Working with SQL Server Versions ... 33

Issues with Legacy Common Components ... 35

Chapter 3 Application Server Upgrade ... 37

Basic Upgrade Sequence ... 39

Upgrading a Galaxy Repository Node ... 40

Upgrading an IDE-only Node ... 41

Migrating the Galaxy Database ... 41

Upgrading Run-Time Nodes ... 42

Upgrading Redundant Pairs ... 43

Upgrade Considerations for Multi-Galaxy Communication ... 47

Chapter 4 InTouch HMI Requirements and

Prerequisites ... 49

Wonderware Product Licensing ... 49

Installing FS Gateway and Modifying FS Gateway Installations ... 51

FS Gateway Installation Scenarios ... 52

Uninstalling FS Gateway and Modifying FS Gateway Installations ... 55

Chapter 5 Historian Server Requirements and

Recommendations... 57

Server Requirements ... 58

High Availability Support ... 60

Requirements for Historian Management Tools ... 61

Remote IDAS Requirements ... 61

Security Considerations for a Remote IDAS ... 62

Disk Sizing and Data Storage ... 63

General Hardware Recommendations for Storage ... 63

Planning for Disk Space Requirements ... 63

Disk Requirements for Database Files ... 64

Disk Space Requirements for Historical Data Files ... 65

Storage and Network Transmission Sizes for Tags ... 66

Disk Space Estimation ... 67

Bandwidth Estimation for Streaming Data ... 68

Bandwidth Estimation for Store-and-Forward Data ... 69

(5)

Contents5

Performance Considerations ... 71

Server Loading ... 72

IDAS Performance ... 73

Tiered Historians ... 73

Storage Subsystem Performance ... 74

Networking Recommendations ... 74

Client Access ... 76

Licensing ... 76

Historian_Tagcount Feature Line ... 78

Historian_ServerOS Feature Line ... 79

Historian_RemoteIDASCount Feature Line ... 79

Historian_ModifyHistoryData Feature Line ... 80

Historian_HistoryDuration Feature Line ... 81

Historian_ReplicationServer Feature Line ... 82

Support for Non-English Operating Systems ... 82

Integration with Other Wonderware Products ... 83

System Sizing Examples ... 84

Process Historian Sizing Examples ... 84

Server 1 (Non-Tiered): 2.4 GHz Single Processor Quad-Core CPU ... 84

Server 2 (Non-Tiered): Four Dual-Core 2.7 GHz CPUs ... 86

Server 3 (Non-Tiered): Four Dual-Core 3.4 GHz CPUs ... 88

Server 4 (Tier-2): Eight Dual-Core 2.67 GHz CPUs (Hyper Threaded) ... 90

SCADA (Tiered) Historian Sizing Examples ... 91

Topology 1: Centralized Tiered Historian Topology on a Slow/Intermittent Network ... 91

Topology 2: Centralized Tiered Historian Topology for a Single Physical Location ... 94

Topology 3: Simple Tiered Historian Topology for a Modem Configuration ... 96

Chapter 6 Historian Server Installation and

Configuration ... 99

Microsoft SQL Server Installation ... 100

Wonderware Historian Installation Features ... 101

About the Wonderware Historian Installation ... 102

Configuring Databases and Data File Locations ... 103

Testing the Installation ... 107

Antivirus Software ... 108

(6)

6 Contents

Modifying the Wonderware Historian Installation ... 109

Uninstalling the Wonderware Historian ... 109

Upgrading from a Previous Version ... 109

About Database Migration ... 110

Upgrading the Wonderware Historian Version ... 110

Migration of History Data Stored in SQL Server ... 111

Chapter 7 Historian Client Requirements ... 113

Wonderware Historian Client Components ... 114

Desktop Applications ... 114

Microsoft Office Add-Ins ... 114

ActiveX and .NET Controls ... 115

Requirements and Recommendations ... 115

Support for Operating System Language Versions ... 115

Chapter 8 Historian Client Installation and

Configuration ... 117

About the Wonderware Historian Client Installation ... 117

Using Wonderware Historian Client Software with Roaming Profiles ... 118

Repairing the Wonderware Historian Client Installation ... 118

Uninstalling Wonderware Historian Client ... 119

Chapter 9 Information Server Requirements and

Recommendations... 121

Web Server Requirements and Recommendations ... 122

Operating System Requirements ... 123

Software Requirements ... 123

Using a Domain Controller with Wonderware Information Server ... 124

Using an Existing Domain Controller ... 125

Using Wonderware Information Server without a Domain Controller ... 125

Guidelines for Installing Microsoft Operating Systems ... 125

Guidelines for Installing Microsoft Windows 7 ... 125

Guidelines for Installing Microsoft Windows Server 2008 R2 ... 126

(7)

Contents7

Guidelines for Installing IIS and ASP.NET ... 130

Guidelines for Installing IIS and ASP.NET on Windows 7 .... 130

Guidelines for Installing IIS and ASP.NET on Windows Server 2008 R2 ... 131

Guidelines for Installing IIS and ASP.NET on Windows Server 2012 ... 133

Guidelines for Installing Microsoft Reporting Services ... 136

Guidelines for Configuring SQL Server 2008 Reporting Services ... 136

Installing Language Packs for Multilingual Systems ... 138

Chapter 10 Information Server Installation and

Configuration ... 139

Installable Features ... 140

Installation Pre-Requisites ... 141

About the Wonderware Information Server Installation ... 141

About Wonderware Information Server Configuration ... 142

Windows Firewall Exceptions ... 143

Using Windows Authentication with Microsoft SQL Server 2008, SQL Server 2008 R2, or SQL Server 2012 .... 143

Configuring a Wonderware Information Server that Uses a Remote SQL Server ... 143

Configuring the Wonderware Information Server ... 144

Starting the Configurator Utility ... 144

Configuring the Core Wonderware Information Server ... 146

Configuring ActiveFactory Reporting ... 148

Configuring Microsoft Excel Application Components ... 150

Defining a New Historian Data Source ... 151

Configuring ArchestrA Reporting ... 152

Defining a New Alarm Data Source ... 154

Configuring Sample Content ... 155

Configuring the Information Model ... 155

Importing Model Content ... 158

Editing Connection Details for an Information Model Data Source ... 159

Installing the ArchestrA Web Exporter ... 160

Installing the Win-XML Exporter ... 160

Modifying Wonderware Information Server ... 160

Repairing Wonderware Information Server ... 161

(8)

8 Contents

Upgrading the Server from Wonderware Information Server 5.0 or 5.0 Patch 01 ... 163

Installing the Product License ... 163

Appendix A Using Silent Installation... 165

Starting Silent Installation ... 165

Using Response Files ... 166

Response File Samples ... 167

Role-Based Response Files ... 168

Product-Based Response Files ... 169

Installing License Manager ... 169

Appendix B Single Product Installation ... 171

Guidelines for Creating a Compact Installation Source ... 172

Preparation for Installing a Single Product ... 172

Optional Folder for Historian ... 175

Creating the Installation Source and Installing the Selected Component ... 175

(9)

9

Chapter 1 Wonderware System Platform

Installation

You can use the Wonderware® System Platform installation program to install the entire suite of products or any of the components.

Preparing for Wonderware System Platform

Installation

Before you begin the installation program, you need to prepare your system, and you should plan your installation according to the two installation types available to you—product-based and role-based.

Note: You should not install the Galaxy Repository on a computer that

is used as a domain controller or an Active Directory server.

Wonderware System Platform Prerequisites

The Wonderware System Platform installation program analyzes the software installed on your computer and lists any software that is required but not currently installed, and any installed sofware that is incompatible.

Important: At the start of the installation, the prerequisites check is

(10)

10  Chapter 1 Wonderware System Platform Installation

The following prerequisites, if not already present on your system, will be installed by the Wonderware System Platform installation

program:

•

Windows Installer 4.5

•

Microsoft .NET® Framework 4.5.1

•

SQL Server 2012 SP2 Express

SQL Server 2012 SP2 Express will be installed only if the following conditions are met:

•

No version of SQL Server is installed on the system.

•

You select InTouch Development and Runtime during the Wonderware System Platform installation, with or without selecting Application Server Galaxy Repository. When you select InTouch Development and Runtime, a Galaxy Repository will be installed.

•

You select Application Server Galaxy Repository during the Wonderware System Platform installation, with or without selecting InTouch Development and Runtime.

While installing Wonderware System Platform, if the logged-on user (the installer) is not a SQL Server administrator, the Config SQL

dialog box appears and requests SQL Server administrator

credentials. Enter valid SQL Server administrator credentials when requested.

For more information about SQL Server installation, see "About SQL Server Requirements" on page 11.

The Wonderware System Platform installation installs both

system-specific and product-specific prerequisites. It also checks for incompatible software that will prevent installation from proceeding. You do not have to exit from the Wonderware System Platform installation procedure to install the prerequisite software. You will, however, need to exit and perform any uninstall operations that are indicated before continuing with installation.

(11)

Preparing for Wonderware System Platform Installation11

Missing prerequisites are listed with the status "not met" and

highlighted in yellow. Pre-existing software that is incompatible with components being installed is listed with the status "incompatible" and highlighted in red.

For information on prerequisites and software requirements for the specific products, see the Wonderware System Platform Readme, the Readme files of the specific products located in your documentation directory, or the specific product information chapter in this

installation guide.

About SQL Server Requirements

The exception to the prerequisites installation workflow is the SQL Server requirement for installing the Historian Server.

If you select the Historian Server for installation, and if the supported version of SQL Server is not already installed, you must exit the installation program, install the supported SQL Server version, then resume the installation.

We recommend that you install and configure the supported SQL Server version before you begin the Wonderware System Platform installation program.

For more information about SQL Server prerequisites, see "SQL Server Requirements" on page 31.

Selecting a Type of Installation

The Wonderware System Platform installation program offers you a choice of two types of installation— product-based or role-based.

(12)

About Product-Based Installation

Product-based installation provides a combination of features not specific to a node. This would be the preferred installation type for a stand-alone product installation.

If you are familiar with Wonderware products and their associated components, you can opt for a product-based installation, and then choose the components that you need.

For example if you need to install InTouch® with the default options, then select a product-based installation.

Important: The Product-Based installation includes an option to

install the InTouch Access Anywhere Secure Gateway. This option can only be installed by itself on a computer with no other System Platform components present.

About Role-Based Installation

Role-based installation provides a combination of features specific to a node. This is preferred in ArchestrA types of installation.

If you are uncertain about the specific products or components you need, but you know what role your computer will play, you can opt for a role-based installation.

For example, if your computer is a run-time node or a development node, you can select those roles in the role-based installation program. The Wonderware System Platform installation program will install all components required for the roles that you have selected.

It is recommended that you define the node you are installing and select the appropriate role before starting the installation program. During the installation, you can click a role to see its description, as described in "Installing the Wonderware System Platform" on page 14. The following roles are available for selection:

•

Runtime Client: Install only the necessary components required

to run a visualization client, Historian client, and ArchestrA object server run-time components.

•

Development Workstation: Install the components required for

an engineering development workstation with only the required components to allow the node to connect to an existing

development server. InTouch and Wonderware System Platform applications can be developed and tested.

•

System Platform Development Server: Install the components

required to host the development server, and develop and test InTouch and Wonderware System Platform applications.

(13)

Preparing for Wonderware System Platform Installation13

•

Historian Client Node: Install the components required to

connect to an existing Historian Server and analyze the data.

•

Information Portal: Install the necessary components for

aggregating and presenting plant production and performance data on the internet or company intranet with the capability to access live plant process data, integrated data trending and analysis, production and performance reporting, and integration to existing IT infrastructure and web portals.

•

All-in-One Node: All products are installed on a single node.

•

Custom: Allows you to customize the components that are

installed.

•

InTouch Access Anywhere Secure Gateway Node: Install the

components to access Wonderware InTouch applications hosted on Terminal Servers by using HTML5 compatible web browsers. You must install this component on a computer with no other System Platform components installed.

ArchestrA User Account

The ArchestrA user account is a user name and password combination that enables inter-node communication between all computers in an ArchestrA environment. You must specify the same user account each time you install Wonderware System Platform components on

computers that communicate with each other.

WARNING! The ArchestrA user account is a Windows operating system account located on the local computer or on a domain. Do not delete this account with operating system account management tools. If you do, ArchestrA-enabled software may stop functioning properly.

If no other ArchestrA-enabled software is installed on the computer, you are prompted to create a new ArchestrA user account or specify an existing user account during the Wonderware System Platform installation. If you select an existing user account, it should meet the following requirements:

•

User account with a permanent password that does not expire.

•

User account in which the password cannot be changed.

•

User account that is a member of the local Administrators group.

Note: The Application Server installation will add the necessary SQL

Server privileges for SQL Server. For more information, see "SQL Server Rights Requirements" on page 33.

(14)

About ArchestrA User Account Privileges

During the Wonderware System Platform installation, you can choose to have the system automatically create a new local administrator account. This new account cannot be used to interactively log on to the computer.

During installation, if you select a pre-existing user who is already a local administrator (domain or local), the already-existing interactive log on privileges are not changed.

Changing the ArchestrA User Account

After you install a Wonderware System Platform component, you can use the ArchestrA Change Network Account utility to change or recreate the ArchestrA user account. This utility is located in the Common folder. You must have Administrator privileges on the computer to make changes with the Change Network Account utility. For more information, see the Change Network Account utility documentation.

Note: If you recreate the user account using the Change Network

Account utility, the Microsoft Windows security component on the computer can take several minutes to update this information on the ArchestrA Galaxy node. Until that occurs, the ArchestrA component may not function properly. Restarting the Galaxy node updates this information immediately.

Installing the Wonderware System Platform

You can select a product-based or a role-based installation for your computer.

To install the Wonderware System Platform

1 Insert the DVD into your DVD-ROM drive. The installation program automatically runs.

(15)

Installing the Wonderware System Platform15

If your network or company security policy does not permit autorun, browse the root directory of the DVD and run setup.exe.

The installation program checks whether or not the minimum system requirements are met. This includes checking that the Microsoft .NET 4.5.1 framework is installed.

For more information on specific system requirements, see the Wonderware System Platform Readme.

•

If the requirements are met, the installation proceeds to verify the general installation prerequisites.

•

If the .NET framework is not installed, the installation program will install it now. A system reboot is required after installing .NET.

Note: In most cases, the installation program will reboot the system

and then resume automatically. However, if you are installing from a network share location or mapped drive, you may have to restart setup.exe.

The following procedure applies if setup does not resume automatically after rebooting. This will occur if user login credentials are needed for access to the network location.

a Click OK when prompted to reboot the system.

b Log back into the network location that contains setup.exe after the system reboots.

c Start setup.exe.

2 Install system-specific prerequisites. The installation now checks that the general installation prequisites are met.

(16)

If your computer does not meet the initial system prerequisites,

the Prerequisites dialog box appears indicating the missing ones.

•

Select the Show All Prerequisites check box to view all prerequisites.

•

Double-click any item to see more information about that item.

•

Click Install Prerequisites. The program installs the general system prerequisites.

•

Click Next. The select installation type dialog box appears.

(17)

4 Select whether you want a product-based or a computer role-based installation, and then click Next. The select components dialog box appears.

•

For information about product-based installation, see "About Product-Based Installation" on page 11.

•

For information about role-based installation, see "About Role-Based Installation" on page 12.

Note: The select components dialog box varies depending on whether

you have selected a product-based or a role-based installation.

If you select the Product Based Selection option, then the product based installation dialog box appears.

(18)

If you select the Wonderware System Platform Computer Roles

option, the role based installation dialog box appears.

You can select multiple products or roles. All the selected components will be installed together.

5 Select the check boxes to indicate which products or roles you want to install, and then click Next. The verify selection dialog box appears.

(19)

Important: The InTouch 16-Pen Trend Wizard supplementary

component is no longer installed by default. Regardless of whether you select a product or role-based installation, you must select the

Customize Installation option to install 16-Pen Trend Wizard.

Complete the following installation steps to install InTouch HMI supplementary components and make other changes:

a Select Customize Installation.

b Click Next.The customize installation dialog box appears.

c Scroll the list of Wonderware System Platform products to be installed to the InTouch Supplementary Components section.

d Select InTouch 16 PenTrend from the list.

•

You can make other product and component selections.

•

You can click Browse on the customize installation dialog box to change the program installation destination folder.

e Click Next to continue the remainder of the installation procedure.

(20)

7 If you have selected an InTouch HMI installation, the language selection dialog box appears. Click the language for your InTouch HMI installation.

If you select InTouch features, you need to select a language for the InTouch installation. The localized InTouch versions are supported only in the paired operating system. For example, the German version of the InTouch HMI is only supported on the German operating system.

(21)

9 Click I have read and accept the terms of the license

agreement(s), and then click Agree. The ArchestrAUser Account

dialog box appears.

10 Specify an ArchestrA user account. You can create a new

ArchestrA user account if no other ArchestrA-enabled software is installed on the computer, or specify an existing user account.

If you create a new account, do the following:

a Click the Create Local Account check box if not already selected. By default, the Domain/Local Machine box displays your computer name.

b Type your user name and password.

Important: For security reasons, the ArchestrA user account by

default, as configured in the operating system user rights management, is not permitted to log on to the Galaxy locally or through Remote Desktop Services.

If you select an existing user account, do the following:

a Clear the Create Local Account check box. When you clear the check box, the Domain/Local Machine text box displays the default domain name. Specify a different domain/local machine name if necessary.

b Type the user name and password for the existing account. The account must meet the following requirements:

•

The account must have a permanent password that does not expire.

(22)

•

The account must be a member of the local Administrators group.

c Click Next to complete the User Account setup. The ArchestrA user account is a user name and password combination that enables inter-node communication between all computers in an ArchestrA environment. You must specify the same user account on every node when you install the Wonderware System Platform components for the first time on computers that communicate with each other.

Wherever an ArchestrA user account is required, the Wonderware System Platform Installation dialog box appears and you need to provide a valid user name and password.

WARNING! The ArchestrA user account is a Windows operating system account located on the local computer or on a domain. Do not delete this account with operating system account management tools. If you do, ArchestrA-enabled software may stop functioning properly.

11 Install the product-specific prerequisites.

A list of prerequisites specific to the components you have selected appears after you complete the User Account setup.

•

Select the Show All Prerequisites check box to view all prerequisites.

•

Double-click any item to see more information about that item.

•

If any prerequisite is not met, click Install Prerequisites. The program installs the product-specific prerequisites.

(23)

•

When all prerequisites are installed, click Next.

12 Review your installation.

The final installation confirmation dialog box appears after the program finishes installing the product-specific prerequisites.

(24)

14 After the installation is over, the complete installation dialog box appears. If the installed products do not need configuration, click

Finish, else click Configure.For more information on configuring

products, see "Configuring Products" on page 18.

You must restart the system to complete the installation.

15 Click Reboot Now or Reboot Later.

Configuring Products

Some products require post-installation configuration for initial setup. You need to configure your products using the Configurator dialog box after you have installed them. The Configurator dialog box lists all product components that you have installed. You can configure the locations for the product database and the data files.

You must have sysadmin permissions to configure products using the Configurator.

(25)

To configure products

1 In the complete installation dialog box, click Configure.The

Configurator dialog box appears. The following example shows

configuration for the Historian Server.

1 On the left pane, select the component and configure the details on the right pane.

2 Click Configure.After the installation is complete, the system may prompt you to restart. You can restart now or later.

Note: The installed programs may not function properly until you

(26)

Modifying an ArchestrA User Account

After you install the Wonderware System Platform, you can use the ArchestrA Change Network Account utility to change or recreate the ArchestrA user account. This utility is located in the Common folder after you install the Wonderware System Platform products. You must have Administrator privileges on the computer to make changes with the Change Network Account utility. For more information, see the Change Network Account utility on-line help.

Note: If you recreate the user account using the Change Network

Account utility, the Microsoft Windows security component on the computer can take several minutes to update this information on the ArchestrA Galaxy Repository node. Until that occurs, the ArchestrA component may not function properly. Restarting the Galaxy Repository node updates this information immediately.

Modifying an Installation

You can change the Wonderware System Platform components installed on your computer. You can add new components or remove the existing ones. You can modify any component of Wonderware System Platform.

You must have the installation DVD inserted in the DVD-ROM drive before you can modify a program.

Note: When you apply a patch, the product version number

increments in Windows Add or Remove Programs (Uninstall or

Change a Program in Windows 7 and Windows 2008). If you install a

new feature from the original media, the product version will revert to the original installation version. You must re-apply the patch each time you install a new feature.

To modify an installation

1 Click the Add or Remove Programs option in Windows Control

Panel. (In Windows Server 2008 R2, this is called Uninstall or

Change a Program.) The list of software installed on your

computer appears.

2 Select any Wonderware System Platform component, and then click the Uninstall/Change button. The Modify, Repair or Remove

(27)

Modifying an Installation27

Note: The name of the Uninstall/Changebutton varies depending on the Windows operating system installed on your computer.

3 Click the Modify option, and then click Next. The list of Wonderware System Platform components appears.

4 Select or clear the components that you want to add or remove, and then click Next. The verify change dialog box appears.

(28)

6 Click Finish.

Repairing an Installation

You can repair the installation of any component of the Wonderware System Platform. You can repair missing or corrupt files, registry keys or shortcuts. You can also reset the registry key to the default value.

Note: You must insert the installer DVD in the DVD-ROM drive before

you can repair a program.

To repair an installation

1 Click the Add or Remove Programs option in Windows Control

computer appears.

2 Select the Wonderware System Platform component that you want to repair, and then click the Uninstall/Change button. The Modify

Repair or Remove Installation dialog box appears.

Note: The name of the Uninstall/Change button varies depending on the Windows operating system installed on your computer.

3 Click the Repair option, and then click Next. The Confirm Repair

dialog box appears.

(29)

Uninstalling a Wonderware System Platform Component29

Uninstalling a Wonderware System Platform

Component

You can uninstall any component of the Wonderware System Platform that is installed on your computer.

To uninstall the Wonderware System Platform component 1 Click the Add or Remove Programs option in Windows Control

computer appears.

2 Select the Wonderware System Platform component that you want to uninstall, and then click the Uninstall/Change button. The

Modify Repair or Remove Installation dialog box appears.

Note: The name of the Uninstall/Change button varies depending on the Windows operating system installed on your computer.

3 Click the Remove option, and then click Next. The confirmation dialog box appears.

4 Click Uninstall. The component is uninstalled and the complete uninstallation dialog box appears.

(30)

Upgrading a Wonderware System Platform

Component

You can upgrade any component of the Wonderware System Platform if you have an older version of the software installed in your system.

Note: If you plan to upgrade Wonderware System Platform on a

computer that has InTouch Access Anywhere Server installed, you must first uninstall the InTouch Access Anywhere Server. Then, upgrade Wonderware System Platform and finally reinstall InTouch Access Anywhere Server.

To upgrade a Wonderware System Platform component 1 Insert the DVD into your DVD-ROM drive. Run setup.exe to start

the set-up program. The upgrade feature dialog box appears.

Note: You can only upgrade the products that are already installed

and you will not be able to install new products that have an upgrade process. The installed components that need to be upgraded are selected and disabled. You can neither clear these check boxes nor select more components during the upgrade.

2 Click Next. The confirm upgrade dialog box appears.

3 Click Upgrade. The complete upgrade dialog box appears.

4 Click Finish.

Installing a Product License

Use the Invensys License Manager to install licenses. For information about how to use the Invensys License Manager, see the Invensys License Manager Guide and the online help.

To start the Invensys License Manager

•

On the Start menu on the Windows Taskbar, point to Programs,

Invensys, and then select Invensys License Manager. The

Invensys License Manager main window appears. Follow the procedures provided in the License Manager online help.

(31)

31

Chapter 2 Application Server

Requirements and

Prerequisites

SQL Server Requirements

In a typical configuration, you should install Microsoft SQL Server before you install Application Server. It is important to take into consideration the requirements of the different versions of SQL Server. Follow Microsoft installation instructions for your particular edition of SQL Server.

If no version of SQL Server is installed on your system when you install Wonderware System Platform, and you install InTouch Development and Runtime or Application Server Galaxy Repository, SQL Server 2012 SP1 Express will be installed automatically. For information about the versions of SQL Server supported by Application Server and other Wonderware System Platform products, see the Wonderware System Platform Readme.

For more information about specific requirements for SQL Server configuration, see "SQL Server Rights Requirements" on page 33, or see Microsoft documentation available online.

•

A supported version of SQL Server must be installed on the computer designated as the ArchestrA Galaxy Repository (GR) node before you install Application Server. If you select

Wonderware Application Server Galaxy Repository for installation and no SQL Server is installed on the computer, the installation

(32)

32  Chapter 2 Application Server Requirements and Prerequisites

•

You cannot install and use Application Server on a computer that has both Microsoft SQL Server 2000 and Microsoft SQL Server 2008 or later versions installed.

•

The GR locks the SQL Server maximum memory usage to 65% of the computer's physical memory.

•

TCP/IP must be enabled on the computer hosting a SQL Server database. The TCP/IP protocol setting can be verified from the SQL Server Network Configuration under SQL Server

Configuration Manager. Do the following steps to enable TCP/IP.

To enable the TCP/IP protocol for the SQL Server database instance

1 Open the Start menu, point to All Programs, point to Microsoft

SQL Server, point to Configuration Tools, and then click SQL

Server Configuration Manager.

2 In the tree pane, click SQL Server Services.

3 In the results pane, verify that, under the State column, Running

appears next to the name of each service.

If Stopped appears, right-click the name of the service, and click

Start.

4 In the tree pane, click SQL Server Network Configuration to expand it, and then click Protocols for

MSSQLServer/<InstanceName>.

If you specified the default instance during installation, the instance name will be MSSQLSERVER.

5 In the results pane, verify that, under the Status column, Enabled

appears next to the name of the TCP/IP protocol.

If Disabled appears, right-click TCP/IP, and then click Enable.

6 In the tree pane, click SQL Native Client Configuration to expand it, and then click Client Protocols.

7 In the results pane, verify that, under the Status column, Enabled

appears next to the name of the TCP/IP protocol.

If Disabled appears, right-click TCP/IP, and then click Enable.

8 In the tree pane, click SQL Server Services.

9 In the results pane, right-click SQL Server

(33)

SQL Server Requirements33

SQL Server Rights Requirements

SQL Server 2008 and later versions do not automatically create the BUILTIN\Administrators role that was delivered in SQL Server 2005. Because of this change to SQL Server, the Application Server

installation process creates the necessary operating system user group (aaAdministrators), as well as the necessary SQL Server logon. This automated process provides the rights required to allow operations within the GR without the need for blanket BUILTIN\Administrator rights. The aaAdministrators group must be present and enabled. If you accidentally delete the aaAdministrators group from the Windows operating system, you can run either of the two following options to restore it:

•

Click Start, point to All Programs, point to Wonderware, and then click the Change Network Utility.

•

Click Start, point to All Programs, point to Wonderware, and then click the aaConfig SQL Utility.

If you accidentally delete the aaAdministrators group from the SQL Server security logons, you must run the aaConfig SQL Utility to restore it.

Working with SQL Server Versions

The installation workflow will vary, depending on whether or not SQL Server is already installed. The version of SQL Server that is installed can also make a difference in the workflow. If SQL Server is not already installed, the Wonderware System Platform installation program will install SQL Server Express. This is adequate for small configurations, but not for medium and large configurations. For these, install SQL Server before installing Wonderware. The following workflow scenarios are described:

•

SQL Server not found on node: small configuration

•

SQL Server not found on node: medium and larger configurations

•

Compatible version of SQL Server already installed

•

New (untested) version of SQL Server already installed

•

Incompatible version of SQL Server already installed

SQL Server not found on node: small configuration

If you install the Application Server Galaxy Repository and SQL Server is not found on the computer, SQL Server 2012 SP1 Express is installed as part of the installation process. This version of SQL Server is suited for small configurations, up to 5,000 I/O per node, and is best for a single-node system.

(34)

34  Chapter 2 Application Server Requirements and Prerequisites

SQL Server not found on node: medium and larger configurations

For medium and larger systems, the following versions are supported:

•

Recommended version: SQL Server 2012 SP1, Standard or Enterprise edition

•

SQL Server 2014, Standard or Enterprise edition

•

SQL Server 2012 SP2, Standard or Enterprise edition

•

SQL Server 2008 R2, Standard or Enterprise edition

For more information about the comparative capabilities of different SQL Server editions, see "Features Supported by the Different Versions of SQL Server 2012" at the following URL:

http://msdn.microsoft.com/en-us/library/cc645993(v=SQL.110).aspx.

Compatible version of SQL Server already installed

If a compatible version of SQL Server is already installed, Wonderware System Platform installation will continue without interruption (SQL Server 2012 Express will not be installed).

New version of SQL Server already installed

If a new version of SQL Server is already installed that has not yet been fully tested with Wonderware System Platform 2014 R2

products, a warning is displayed stating that the installed SQL version has not yet been tested. You can proceed with the installation, but we recommend that you contact Wonderware customer support before proceeding to check if any issues have been found.

Incompatible version of SQL Server already installed

If an older version of SQL Server is already installed that is not supported for use with Wonderware System Platform 2014 R2

products, installation will stop and a warning will be displayed stating the SQL Server version is not compatible. You must exit the

installation process and upgrade to a supported version of SQL Server before you can resume installation.

(35)

Issues with Legacy Common Components35

Issues with Legacy Common Components

Wonderware Application Server uses the latest version of the ArchestrA common components, which are installed to the following folder:

C:\Program Files\Common Files\ArchestrA

On a 64-bit operating system, the common components are installed to the following folder:

C:\Program Files (x86)\Common Files\ArchestrA

Legacy ArchestrA common components are installed to the following folder:

C:\Program Files\FactorySuite\Common

On a 64-bit operating system, legacy common components are installed to the following folder:

C:\Program Files (x86)\FactorySuite\Common

It is possible to install duplicate common components on a computer if you install an ArchestrA product that still uses the legacy common components after you install Application Server. Unexpected behavior can occur if duplicate common components are installed. The system components may not run properly, or may not run at all. Contact technical support for further assistance. You can also reference Tech Note 454, Manual Uninstall of Wonderware Products.

(36)

(37)

37

Chapter 3 Application Server Upgrade

For specific versions of the Application Server that you can upgrade to version 2014 R2, see the Wonderware System Platform Readme file.

Important: Ensure that you have installed the latest patch for your

existing version, wherever possible, before upgrading to the latest version. Also, only systems that meet the minimum system

requirements, including operating system and SQL Server version, can be upgraded.

If you plan to upgrade system components in addition to Application Server, keep the following in mind:

•

After Application Server is installed, operating system migration is not supported.

•

You can upgrade SQL Server after Application Server is installed. Refer to Microsoft’s SQL Server resources for guidelines and procedures.

To upgrade SQL Server after Application Server is installed, we recommend that you undeploy any galaxies deployed on the relevant computer, and that you undeploy all ArchestrA Service Bus (ASB) services. For more information, see the Wonderware Application Server User Guide.

(38)

38  Chapter 3 Application Server Upgrade

You can upgrade the following Application Server components:

•

Bootstrap

You will see a warning message if you attempt to upgrade a computer with a deployed WinPlatform. You have the choice to continue with the upgrade or to cancel. If you continue with the Bootstrap upgrade, the WinPlatform object is removed and upgraded to version 2014 R2.

If an InTouchViewApp instance is deployed for a managed InTouch application, the folder is undeployed and deleted. You are

prompted to stop InTouch WindowViewer from running the managed application.

•

IDE and Bootstrap

You will see a warning message if you attempt to upgrade a computer with a deployed WinPlatform. You have the choice to continue with the upgrade or to cancel. If you continue with the upgrade, the current IDE and Bootstrap are removed and the new versions are installed.

If an installed InTouchViewApp instance is deployed for a managed InTouch application, the folder is undeployed and deleted. You are prompted to stop InTouch WindowViewer from running the managed application.

•

Galaxy Repository (GR) and Bootstrap

You will see a warning message if you attempt to upgrade a computer with a deployed WinPlatform or a client application is connected to the GR node. You have the choice to continue with the upgrade or to cancel. If you continue with the Bootstrap upgrade, the components are removed and upgraded to version 2014 R2. Upgraded IDE/Client nodes cannot connect to a non-upgraded GR node. The GR node is undeployed before it is upgraded to

Application Server 2014 R2.

•

IDE, GR, and Bootstrap

You see a warning message if you attempt to upgrade a computer with a deployed WinPlatform or if a client application is connected to the GR node. You have the choice to continue with the upgrade or to cancel. If you continue with the Bootstrap upgrade, all components are removed and upgraded to version 2014 R2.

•

Run-time node

Upgrading the Bootstrap on any computer removes the running WinPlatform and AppEngine. Both of these system objects are marked as undeployed if they are running on any Galaxy node.

(39)

Basic Upgrade Sequence39

If a remote node is disconnected from the GR node, or if you upgrade the remote node before you upgrade the GR node, the remote Platform is not marked as undeployed. You must undeploy and redeploy the Platform.

The run-time functionality of Application Server continues throughout the upgrade process, except during a run-time node upgrade.

Configuration, however, must be done using components that are at the same version level. For example, you cannot use the Galaxy Browser in the InTouch HMI on a non-upgraded node to view or select attributes from an upgraded Galaxy. You can, though, view or modify run-time data using an InTouch window or the Object Viewer.

Special considerations apply if you are upgrading both the Application Server and the Wonderware Historian. For more information, see "Upgrading from a Previous Version" on page 111.

Basic Upgrade Sequence

Important: Back up the Galaxy before starting an upgrade. Also,

upload any run-time changes for critical objects. You cannot upload any run-time change from non-upgraded nodes after you upgrade the system.

The basic upgrade steps are:

1 Upgrade your hardware and prerequisite software such as the operating system or Microsoft SQL Server to the required versions. For information on hardware and software requirements, see the Wonderware System Platform Readme file.

If you are upgrading the SQL Server database on the GR node, you must undeploy the GR node before starting the SQL Server upgrade.

2 Upgrade the GR node. For more information, see "Upgrading a Galaxy Repository Node" on page 40.

3 Upgrade at least one IDE installation. If you upgrade the GR node, that IDE installation is upgraded. However, if you have any IDE-only nodes, you will have to upgrade them separately. For more information, see "Upgrading an IDE-only Node" on page 41.

4 Use the upgraded IDE to connect to the upgraded GR node and migrate the Galaxy database. For more information, see

"Migrating the Galaxy Database" on page 42.

5 Deploy the GR Platform.

6 Upgrade run-time nodes.

•

Upgrade non-redundant run-time nodes one at a time and redeploy them. For more information, see "Upgrading

(40)

•

Upgrade redundant pairs one at a time. For more information, see "Upgrading Redundant Pairs" on page 44.

If you upgrade a remote Platform node before you migrate the Galaxy database, the remote Platform and hosted objects show the software upgrade pending icon after you migrate and deploy the Galaxy. To resolve this, undeploy and redeploy the remote Platform.

The preferred sequence of upgrade is:

1 Upgrade the GR node.

2 Upgrade the IDE node.

3 Migrate the Galaxy database.

4 Upgrade the remote Platforms.

Important: After you have upgraded the GR node to Application

Server 2014 R2, you will not be able to deploy or undeploy from the GR node to non-upgraded remote nodes. Also, the upgraded GR node will not be able to connect to an IDE node that has not been upgraded to 2014 R2.

Note: As long as the operating system and SQL requirements are met,

upgrade is supported. During software installation, operating system upgrade is not supported.

Upgrading a Galaxy Repository Node

When you upgrade a GR node, the database schema is migrated from the existing schema to the Application Server 2014 R2 schema. Existing data from the GR is also migrated to the new schema.

You must upgrade all Application Server components (IDE, Bootstrap, and GR) to the same version that are installed on the GR node. When you upgrade the GR node, the local Platform and all hosted objects are undeployed.

To upgrade the GR node

1 Run Setup.exe from the DVD. The Welcome dialog box appears.

2 Click Next. Review the recommended steps before you upgrade and take appropriate action, if needed.

3 Click Next. Review the status of objects deployed in the system and take appropriate action, if needed.

4 Click Next. The Select Features dialog box appears. Any previously-installed features appear dimmed.

(41)

Upgrading an IDE-only Node41

6 Click the prerequisite whose status is "Not Met", and then click

Install Prerequisites. The general system prerequisites are

installed.

7 Click Next. Follow the prompts to complete the upgrade.

Upgrading an IDE-only Node

If you have IDE-only installations on nodes other than the GR node, you need to upgrade them separately.

Important: A GR node that has been upgraded to Application Server

version 2014 R2 cannot connect to an IDE node that has not also been upgraded. Conversely, an IDE node that has been upgraded cannot connect to a GR node that has not been upgraded.

To upgrade an IDE-only node

1 On the IDE node, run Setup.exe from the DVD. The Welcome

dialog box appears.

3 Click Next. The Prerequisites dialog box appears. You can select

the Show All check box to view all prerequisites.

4 Click the prerequisite whose status is Not Met, and then click

Install Prerequisites. The general system prerequisites are

installed.

Migrating the Galaxy Database

To migrate the database:

•

The IDE you use to migrate the database must be the current version.

•

The GR node must already be upgraded to the current version. Make sure that all connections to the Galaxy database are closed before migrating the database.

After you migrate the Galaxy, deployed objects on a non-upgraded node are marked with pending software upgrade status.

To migrate the Galaxy database 1 Start the IDE.

(42)

3 Follow the prompts to complete the migration.

Upgrading Run-Time Nodes

After you upgrade the GR and IDE, all run-time nodes continue to run. This enables you to upgrade the run-time nodes individually when it is convenient.

Important: After you have upgraded the GR node to Application

Server 2014 R2, and you have migrated the galaxy, you will not be able to deploy or undeploy from the GR node to remote nodes. Also, an upgraded IDE node will not be able to connect to a GR node that has not been upgraded to 2014 R2.

Upgrading to Application Server 2014 R2 on a run-time node will remove any deployed Platforms on that node.

After you upgrade and then deploy a run-time node, it continues to function with other run-time nodes as long as the other nodes are the current version or from the previous version.

The run-time node does not function while you are upgrading it. You cannot roll back the upgrade.

After you upgrade the run-time node and all hosted objects, you need to redeploy the WinPlatform and all hosted objects to the node.

The GR node migration fails if the GR node is used as a run-time node for another GR.

To upgrade a run-time node

1 Run Setup.exe from the DVD. The Welcome dialog box appears.

2 Click Next. Accept the license agreement.

3 Click Next. Review the status of objects deployed in the system and take appropriate action, if needed.

(43)

Upgrading Redundant Pairs43

Upgrading Redundant Pairs

You can reduce plant down time by upgrading the two partner nodes in a redundant pair, one at a time.

Platforms hosting redundant pairs may be deployed even when a partner platform is not the same software version as the Galaxy Repository (GR) platform, or is in the Software Upgrade Pending (SUP) state.

When upgrading a redundant pair, we recommend upgrading the standby partner first. This way, only one failover of the redundant engines is needed, thus minimizing the period of time in which process data is not collected. After upgrading the first node, upgrade the second as soon as possible. When only one node is upgraded, backup and failover are not available. Both nodes must be at the same software version to enable redundancy.

The following table illustrates the workflow for upgrading a Galaxy Repository and one redundant pair, consisting of different nodes, from software version 1 (v1) to version 2 (v2). Action items are shaded. In this example, the redundant pair is comprised of Node B and Node C, as a redundant Application Engine is hosted by the platform on each node. Use the Platform Manager to determine which platform (P1 or P2) is hosting the active Application Engine. See the Platform Manager User’s Guide for additional information.

To upgrade a redundant pair

Follow the actions listed in the table to upgrade a GR node and redundant pair. These instructions assume an initial state where the primary engine (E1) is active. At the conclusion of this procedure, all three nodes are upgraded and the backup engine (E1b) is active.

Node A

GR Platform 0 (P0)

Node B

Primary AppEngine (E1) Platform 1 (P1)

Node C

Backup AppEngine (E1b) Platform 2 (P2)

Step Action Resulting State Action Resulting State Action Resulting State

(Initial state) Deployed. E1 Deployed – Active. E1b Deployed – Standby. 1 Upload run-time changes Changes made at run-time now stored in the database.

(44)

44  Chapter 3 Application Server Upgrade 2 Upgrade (with AppServer deployed but shut down) All objects on P0 become undeployed. 3 Reboot (when prompted) Software is now at v2. 4 Open IDE and migrate database Galaxy database now at v2. IDE shows P1 and P2 in SUP state. 5 Optional: Open and migrate InTouch ViewApps InTouch ViewApps now at v2. 6 Cascade deploy P0 All objects on P0 are deployed. 7 Upgrade (with AppServer deployed but shut down) P2 and its hosted engines and objects become undeployed. Node A GR Platform 0 (P0) Node B

Node C

(45)

Upgrading Redundant Pairs45 8 E1 becomes undeployed. E1 shows as undeployed, but objects under E1 show as deployed. Cascade Deploy P2 Note: This action results in a brief downtime for objects on E1 and E1b as E1 becomes undeployed (a few seconds to a few minutes, depending on number of objects). E1b becomes active, hosted objects are now running under v2. Note: E1b does NOT start from the check- pointed state of non- upgraded E1 9 Upgrade (with AppServer deployed but shut down) P1 becomes undeployed. 10 Cascade Deploy P1 E1 is deployed as part of P1 deployment. E1 starts as standby and fully syncs with active engine. No downtime for objects on E1b as E1b continues to run as active. (Final state) Deployed. E1 Deployed – Standby. E1b Deployed – Active. Node A GR Platform 0 (P0) Node B

Node C

(46)

The following table describes the behaviors associated with specific upgrade actions and states.

Action or State Behavior

Cascade deploy a

Platform after upgrade If the upgraded platform hosts a backup redundant engine with a partner in the SUP state, then during the deploy operation, it will extract the hosted objects from the partner and deploy them along with the backup redundant engine. Deploy a redundant

engine with a partner in the SUP state.

The deploy operation is always a Cascade Deploy.

Multi-selection for a cascade deployment includes a redundant engine with a partner in SUP state

The cascade deploy operation skips the redundant engine in SUP state and logs a message.

Select a backup redundant partner engine for deployment

The backup redundant engine extracts the hosted objects from the primary redundant engine and deploys them along with the backup redundant engine

The hosted objects are under the primary redundant engine on a partner platform which is in SUP state. The hosted objects will be forced to deploy with the newer software version during the deployment of the backup redundant engine.

A dialog displays with the option to continue deployment or to cancel.

(47)

Upgrade Considerations for Multi-Galaxy Communication47

Upgrade Considerations for Multi-Galaxy

Communication

Setting up a multiple Galaxy environment requires a unique name for each Galaxy in the environment. This may require you to rename one or more Galaxies if you plan to include galaxies with the same name in your multi-Galaxy communication environment. We recommend performing all necessary renaming prior to upgrading to Wonderware System Platform 2014 R2. This will prepare your Galaxies for use in a multi-Galaxy environment without disrupting the upgrade workflow.

Important: It is very important that you follow the Galaxy name

change procedure provided in the following steps and in the

Wonderware Application Server User Guide. You must create a new

Galaxy with a new, unique name, from a backup .cab file rather than creating a Galaxy and performing a restore of the backup .cab file.

Partner engine is deployed but not reachable or not ready to synch.

Redundant engine deployment fails.

Partner engine has older software version.

The partner engine is detected and recognized as having an older software version. It is automatically stopped and unregistered.

Primary engine transitions into Active –

Partner not Upgraded redundancy

status.

Primary and backup partners cannot synch, but references to a redundant engine with this status—or with Active or

Active – Standby not Available

redundancy statuses—will resolve. Application Objects can be deployed to a redundant partner with Active – Partner

Not Upgraded redundancy status.

You will not be able to deploy the partner engine until you have upgraded it.

(48)

Do the following to rename a Galaxy for use in a multi-Galaxy environment. For more information about creating and backing up galaxies, see Chapter 1 "Getting Started with the IDE," and Chapter 14 "Managing Galaxies," in the Wonderware Application Server User Guide.

1 Select a Galaxy with a duplicate name, undeploy it and back it up to create a .cab file.

2 Use the .cab file as a "template" by placing it in \Program Files\ArchestrA\Framework\Bin\BackupGalaxies.

3 Create a new Galaxy with a new name, based on the backup .cab file. The name must be unique, not in use anywhere else in the multi-Galaxy environment.

4 Repeat the preceding steps for each Galaxy to be renamed with a unique name.

5 Redeploy each newly created Galaxy.

6 Delete the original Galaxy from the GR node.

7 Upgrade to Wonderware Application Server 2014 R2. Your Galaxy can now be configured for use in a multi-Galaxy environment.

(49)

49

Chapter 4 InTouch HMI Requirements

and Prerequisites

You need to meet the requirements and prerequisites for Wonderware products.

Wonderware Product Licensing

NOTICE: LIMITATIONS TO THE WONDERWARE LICENSING FOR INTOUCH 11.1 AND APPLICATION SERVER 4.1.

PROPER USE OF LICENSED PRODUCTS MUST BE STRICTLY FOLLOWED TO ENSURE A FULLY FUNCTIONING

PRODUCTION SYSTEM. READ THIS ENTIRE NOTICE.

If you are licensed for a Wonderware System Platform or the

Wonderware Application Server, you can use all the functionality in these products up to the limits in your license files.

If you are licensed for only InTouch 2014 R2 development and run time, you are licensed to use:

•

All InTouch product software capabilities

•

InTouch tags up to the licensed limit

•

ArchestrA graphics

•

ArchestrA IDE

Important: You are not licensed to use or deploy in production any

(50)

50  Chapter 4 InTouch HMI Requirements and Prerequisites

However, you can use the additional functionality in the Wonderware Application Server in a Demo mode as you learn about its capabilities and consider the advantages of upgrading to a full Wonderware System Platform license.

Wonderware provides you with most or all of the product software in a demonstration, or “Demo,” mode. Demo mode lets you learn about and experience the full breadth of the Wonderware product line,

technology, and capabilities without requiring a legal license file to run the software.

You can use the License Information utility to see whether the current local or remote I/O counts exceed the maximum specified by your Wonderware license. To start the ArchestrA License Manager from any Wonderware product, on the Help menu, click About, and then click View License.

In addition, carefully read the License Certificate documentation, which describes the licensed products you received. The License Certificate is included with your Licensing CD.

Important: Attempting to deploy unlicensed functionality to a

production environment is illegal and results in problems when

upgrading to a future version. Deploying unlicensed functionality is not supported by Wonderware.

For further explanation of licensing compliance, see Appendix B of the InTouch Data Management Guide installed with the software. Or, contact your local Wonderware Distributor or Wonderware Technical Support.

(51)

Installing FS Gateway and Modifying FS Gateway Installations51

Installing FS Gateway and Modifying FS

Gateway Installations

FactorySuite Gateway (FS Gateway) automatically installs with Wonderware System Platform with InTouch HMI as an InTouch HMI component. FS Gateway functions as a data access server (DAServer) and provides OPC connectivity access and configuration.

FS Gateway can also be installed and upgraded as a stand-alone application. In some installation scenarios, FS Gateway will not appear in the Windows Add or Remove Programs list (Uninstall or Change Programs in Windows 7 and Windows Server 2008 R2 operating systems). This does not prevent you from uninstalling or upgrading FS Gateway.

The following describes the installation and modification behavior of FS Gateway as part of a Wonderware System Platform with InTouch HMI installation and as a stand-alone installation.