Wonderware System Platform

Installation Guide
© 2017 Schneider Electric Software, LLC.
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 Schneider Electric Software, LLC. No liability is assumed with
respect to the use of the information contained herein.
Although precaution has been taken in the preparation of this documentation, Schneider
Electric Software, LLC assumes no responsibility for errors or omissions. The information in
this documentation is subject to change without notice and does not represent a commitment
on the part of Schneider Electric Software, LLC. The software described in this
documentation is furnished under a license agreement. This software may be used or copied
only in accordance with the terms of such license agreement.
ArchestrA, Avantis, DYNSIM, eDNA, EYESIM, Foxboro, Foxboro Evo, I/A Series, InBatch,
InduSoft, InStep, IntelaTrac, InTouch, PIPEPHASE, PRiSM, PRO/II, PROVISION, ROMeo,
Schneider Electric, SIM4ME, SimCentral, SimSci, Skelta, SmartGlance, Spiral Software,
VISUAL FLARE, WindowMaker, WindowViewer, and Wonderware are trademarks of
Schneider Electric SE, its subsidiaries, and affiliated companies. An extensive listing of
Schneider Electric Software, LLC trademarks can be found at: http://software.schneider-
electric.com/legal/trademarks/. All other brands may be trademarks of their respective
owners.
Schneider Electric Software, LLC
26561 Rancho Parkway South
Lake Forest, CA 92630 U.S.A.
(949) 727-3200
http://software.schneider-electric.com/
Publication date: 11/9/2017
Contact Us
Contact Schneider Electric Software Technical Support
Avantis Technical Support
Listing of regional and local country contacts: http://software.schneider-
electric.com/support/avantis/
Technical support: http://softwaresupport.schneider-electric.com/
For Avantis.PRO, Avantis Approvals, Avantis.DSS, and Condition Manager:
 Email: [email protected]
 Phone (8:30 a.m. to 5:00 p.m. Monday to Friday, Eastern Time):
o Toll-Free U.S. and Canada: 1-888-262-7111
o Toll-Free EMEA: 1-800-4670-6466
o Direct dial: 1-905-632-0635
For Avantis.XA:
 Email: [email protected]
 Phone (8:30 a.m. to 5:00 p.m. Monday to Friday, Eastern Time):
o Toll-Free U.S. and Canada: 1-800-991-8000
o Toll-Free EMEA: 1-800-4670-6466
o Direct dial: 1-905-632-4122
SimSci Technical Support
Listing of regional and local country contacts: http://software.schneider-
electric.com/support/simsci/
Technical support: http://softwaresupport.schneider-electric.com/
 Email U.S. and Canada: [email protected]
 Phone (USA 8:00 a.m. to 5:00 p.m. Central Time)
o Toll-Free U.S. and Canada: 1-800-746-7241
Skelta Technical Support
 Email: [email protected]
 Phone:
o U.S.: 1-678-306-4110 Option 3
o India: 91-80-4060-2600 Option 3
Wonderware Technical Support
Listing of regional and local country contacts: https://www.wonderware.com/contact/contact-
support/
Technical support: http://softwaresupport.schneider-electric.com/
 Priority email for Customer FIRST Members: [email protected]
 Email for customers without a support agreement: [email protected]
 Phone
o Toll-Free North America and Latin America: 1-800-966-3371
o Direct dial: 1-949-639-8500
InStep Technical Support
Contact page: http://www.instepsoftware.com/contact-us
Technical support: https://support.instepsoftware.com/
 Email: [email protected]
 Phone (USA 8:00 a.m. to 5:00 p.m. Central Time)
o 1-312-894-7870
Schneider Electric – Smart Water Software Technical Support
 Help desk email: [email protected]
 Help desk telephone hotline: +45 88 30 20 77 (09:00 to 16:00 Monday to Thursday,
Friday 09:00 to 15:00, Central European Time)
Contact Schneider Electric Software Learning Services
Contact Software Learning Services for assistance regarding classes, schedule, offerings,
frequently asked questions, tuition, policies, and more.
 Email: [email protected]
 Toll-Free U.S. and Canada: 1-866-998-7246
 Direct: 1-949-639-8508
 Fax: 1-949-639-1847
 Wonderware System Platform Installation Guide

Contents
Chapter 1 Wonderware System Platform Installation ....................................................... 9
Preparing for Wonderware System Platform Installation ............................................................... 9
License Installation and Activation ........................................................................................ 9
Operating System Minimum Requirements ......................................................................... 11
System Sizing Guidelines .................................................................................................. 12
Supported and Recommended Node Hardware Types ........................................................ 13
Required Installation Order of Additional Wonderware Products ........................................... 14
Common Components ....................................................................................................... 14
Windows Network Configuration......................................................................................... 15
Wonderware System Platform Prerequisites ....................................................................... 15
About SQL Server Requirements.................................................................................. 18
Selecting a Type of Installation........................................................................................... 18
About Product-Based Installation .................................................................................. 18
About Role-B ased Installation ...................................................................................... 20
ArchestrA User Account..................................................................................................... 23
About ArchestrA Us er Account Privileges ...................................................................... 24
Installing the Wonderware System Platform .............................................................................. 24
Configuring Wonderware System Platform Components ............................................................ 34
Configuring the Schneider Electric License Server Location ................................................. 34
Configuring Databases and Dat a File Locations .................................................................. 35
System Restart after Configuration ..................................................................................... 41
Modifying an Installation .......................................................................................................... 41
Repairing an Installation .......................................................................................................... 43
Uninstalling Wonderware System Platform ............................................................................... 43
Uninstalling Wonderware System Platform Uninstall a Wonderware System Platform
Component ...................................................................................................................... 43
Uninstall All Components ................................................................................................... 44
Upgrading Wonderware System Platform ................................................................................. 45

Chapter 2 Security and Permissions.................................................................................. 49

Modifying an ArchestrA User Account ...................................................................................... 49
SQL Server Rights Requirements ............................................................................................ 49
Setting the SQL Server Security Mode ..................................................................................... 50
Restoring Required SQL Server Accounts ................................................................................ 52
Setting the FIPS Security Policy Option .................................................................................... 52

Chapter 3 Configuring SQL Server .................................................................................... 53

SQL Server Requirements ....................................................................................................... 53
Working with SQL Server Versions........................................................................................... 54
SQL Server not found on node: small configuration ............................................................. 55

5
Wonderware System Platform Installation Guide Contents

SQL Server not found on node: medium and larger configurations ........................................ 55
Compatible version of SQL Server already installed ............................................................ 55
New version of SQL Server already installed ....................................................................... 55
Incompatible version of SQL Server already installed .......................................................... 55
Using a Non-Default Port for SQL Server.................................................................................. 56
Setting a Windows Firewall Exception for the SQL Server Port ............................................. 57

Chapter 4 Application Server Upgrade .............................................................................. 59

About Upgrading Application Server ......................................................................................... 59
Basic Upgrade S equence ........................................................................................................ 61
Upgrading a Galaxy Repository Node ....................................................................................... 62
Upgrading an IDE-only Node ................................................................................................... 62
Migrating the Galaxy Database ................................................................................................ 63
Upgrading Run-Time Nodes .................................................................................................... 63
Upgrading Redundant Pairs ..................................................................................................... 64
Upgrade Considerations for Multi-Galaxy Communication.......................................................... 68
Issues with Legacy Common Components ............................................................................... 69

Chapter 5 InTouch HMI Requirements and Prerequisites .............................................. 71

Installing OI Gateway and Upgrading from FS Gateway ............................................................. 71
Compatibility with Existing FS Gateway Applications ........................................................... 72

Chapter 6 Historian Server Requirements and Recommendations .............................. 75

Server Requirements .............................................................................................................. 75
High A vailability Support .................................................................................................... 77
Requirements for Historian Management Tools ......................................................................... 78
Remote IDAS Requirements .................................................................................................... 78
Security Considerations for a Remote IDAS ........................................................................ 78
Disk Sizing and Data Storage .................................................................................................. 79
General Hardware Recommendations for Storage ............................................................... 80
Planning for Disk Space Requirements ............................................................................... 80
Disk Requirements for Database Files ................................................................................ 80
Disk Space Requirements for Historical Data Files .............................................................. 81
Storage and Net work Transmission Sizes for Tags .............................................................. 81
Disk Space Estimation ....................................................................................................... 83
Bandwidth Estimation for Streaming Data ........................................................................... 83
Bandwidth Estimation for Store-and-Forward Data .............................................................. 84
Time Estimation for Store-and-Forward Data....................................................................... 85
About Data Compression and the Buffer Age Limit .............................................................. 85
Performance Considerations .................................................................................................... 85
Server Loading.................................................................................................................. 86
IDAS Performance ............................................................................................................ 87
Tiered Historians ............................................................................................................... 87
Storage Subsystem Performance ....................................................................................... 88
Networking Rec ommendations ................................................................................................ 88
Client Access.......................................................................................................................... 89
Support for Non-English Operating Systems ............................................................................. 90

6
Contents Wonderware System Platform Installation Guide

Integration with Other Wonderware Products ............................................................................ 90

System Sizing Examples ......................................................................................................... 90
Process Historian Sizing Examples .................................................................................... 91
Server 1 (Non-Tiered): 2.4 GHz Single Processor Quad-Core CPU ................................ 91
Server 2 (Non-Tiered): Four Dual-Core 2.7 GHz CP Us .................................................. 92
Server 3 (Non-Tiered): Four Dual-Core 3.4 GHz CP Us .................................................. 94
Server 4 (Tier-2): Eight Dual-Core 2.67 GHz CPUs (Hyper Threaded) ............................ 96
SCADA (Tiered) Historian Sizing Examples ........................................................................ 97
Topology 1: Centralized Tiered Historian Topology on a Slow/Int ermittent Network .......... 97
Topology 2: Centralized Tiered Historian Topology for a Single Physical Location ........... 99
Topology 3: Simple Tiered Historian Topology for a Modem Configuration .................... 101

Chapter 7 Historian Server Installation and Configuration ........................................... 103

Preparing for the Wonderware Historian Installation ................................................................ 103
Microsoft SQL Server Installation ........................................................................................... 104
Wonderware Historian Installation Features ............................................................................ 105
About the Wonderware Historian Installation ........................................................................... 105
Testing the Installation........................................................................................................... 106
Antivirus Software ................................................................................................................. 106
Wonderware Historian Menu Shortcuts................................................................................... 107
Repairing the Wonderware Historian ...................................................................................... 107
Modifying the Wonderware Historian Installation ..................................................................... 107
Uninstalling the Wonderware Historian ................................................................................... 107
Upgrading from a Previous Version ........................................................................................ 107
About Database Migration................................................................................................ 108
Upgrading the Wonderware Historian Version ................................................................... 108
Migration of History Data Stored in SQL Server ................................................................. 109

Chapter 8 Historian Client Requirements........................................................................ 111

About Wonderware Historian Client ........................................................................................ 111
Wonderware Historian Client Components.............................................................................. 111
Desktop Applications ....................................................................................................... 111
Microsoft Office Add-Ins................................................................................................... 112
ActiveX and .NE T Cont rols .............................................................................................. 112
Requirements and Recommendations .................................................................................... 112
Support for Operating System Language Versions .................................................................. 112

Chapter 9 Historian Client Installation and Configuration............................................. 113

About the Wonderware Historian Client Installation ................................................................. 113
Using Wonderware Historian Client Soft ware with Roaming P rofiles ......................................... 114
Repairing the Wonderware Historian Client Installation ............................................................ 114
Uninstalling Wonderware Historian Client ............................................................................... 114
Upgrading from a Previous Version ........................................................................................ 114

Appendix A Using Silent Installation ................................................................................ 117

7
Wonderware System Platform Installation Guide Contents

Starting Silent Installation ...................................................................................................... 117

Using Response Files ........................................................................................................... 118
Response File Samples ......................................................................................................... 119
Role-Based Res ponse Files ............................................................................................. 119
Product-Based Response Files ........................................................................................ 120
Configuring the License Server .............................................................................................. 122

Appendix B Single Product Installation............................................................................ 123

Guidelines for Creating a Compact Installation Source ............................................................ 123
Upgrading from a Previous Version .................................................................................. 124
Preparation for Installing a Single Product .............................................................................. 124
Optional Folder for Historian ............................................................................................ 126
Creating the Installation Source and Installing the Selected Component ................................... 126

Index ....................................................................................................................................... 129

8
 Wonderware System Platform Installation Guide

C HAPTER 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.

In This Chapter
Preparing for Wonderware System Platform Installation .................................................................... 9
Installing the Wonderware System Platform .................................................................................... 24
Configuring Wonderware System Platform Components .................................................................. 34
Modifying an Installation ................................................................................................................ 41
Repairing an Installation ................................................................................................................ 43
Uninstalling Wonderware System Platform ..................................................................................... 43
Upgrading Wonderware System Platform ....................................................................................... 45

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. See Selecting a Type of Installation on page 18 for additional information.

License Installation and Activation

A valid product license is required to enable product functionality. The Schneider Electric
License Server and Schneider Electric License Manager are automatically selected when you
select Application Server or Wonderware InTouch, or any role (if you select role-based
installation (see "About Role-Based Installation" on page 20)) that includes the Application
Server Galaxy Repository. In some cases, such as when you install a Runtime Client, the
Galaxy Repository is installed "silently" (without any notice it is being installed).
While the Application Server Galaxy Repository is selected for installation, you cannot
deselect the Schneider Electric licensing components. The License Server and License
Manager are installed on the Galaxy Repository node by default.
Note: If you are using a workgroup, the Schneider Electric License Manager and License
Server must be installed on the same node.
You will need to configure the License Server and activate your product licenses before using
the products you install. For detailed information about product licensing and activation, refer
to the Schneider Electric Licensing Guide (SELicenseManagerGuide.pdf). You can access it
from:
 The Wonderware System Platform Installation DVD, under Install Files\CD-
Licensing\SELicenseManager.

9
Wonderware System Platform Installation Guide Wonderware System Platform Installation

 The Schneider Electric License Manager node, under the Schneider Electric start
directory (after installation is complete).
Schneider Electric Licensing
The Schneider Electric License Server acquires, stores, and serves licenses for all installed
Schneider Electric software, including all Wonderware System Platform products. The
Schneider Electric License Server and Manager work together to provide centralized
management of all your product licenses.
For products and roles that do not install the License Server on the same node, you will have
to provide the location (node name) of the License Server.
The basic product installation and license activation workflow is:
1. Install Wonderware System Products, along with the Schneider Electric License Server
and License Manager. See Installing the Wonderware System Platform on page 24.
2. Configure the Schneider Electric License Server (and Historian, if installed). See
Configuring the Schneider Electric License Server Location (see "Configuring the
Schneider Electric License Server Location" on page 34).
3. Start the Schneider Electric License Manager. The License Manager is browser-based,
and is located in the Schneider Electric folder (Start > Schneider Electric > Schneider
Electric License Manager). The License Manager uses the following URL:
http://localhost/SELicenseManager
Note: If you are running the License Manager from a remote node (not the License
Server/Galaxy Repository node), substitute the node name for localhost.

10
Wonderware System Platform Installation Wonderware System Platform Installation Guide

4. If a License Server is displayed, you can simply click on it to select it. If there are no
License Servers displayed, click the Add Server button, and then enter the computer
name of the License Server, or select the computer name from the drop down.
5. Select and activate your product license(s) from your license file before starting the
application(s). See the Schneider Electric License Manager Guide for detailed
information.

6. Start your application(s).

Note: Changes to licensing, such as switching license servers or activating a new license,
should not be done for a product that is already running. Depending on the product, it may
take up to 30 minutes to acquire a new or changed license. To immediately acquire a license,
restart the affected product. However, product interdependencies may require you to restart
the node to force the immediate acquisition of the license.

Operating System Minimum Requirements

The following table lists the minimum operating system version for Wonderware System
Platform products. See the Schneider Electric GCS Technology Matrix for the complete list of
supported Windows operating systems.
Minimum Required Operating System Version

Product Client OS (x86 and x64) Server OS (x64 only)

Wonderware Application Server

Windows 8.1 Professional
Windows Server 2012
Wonderware InTouch Windows 10 Version 1607

11
Wonderware System Platform Installation Guide Wonderware System Platform Installation

Wonderware Historian
Schneider Electric Licensing
Wonderware InTouch Access Server OS is required
Anywhere

Note: Windows 10 versions prior to version 1607 (Anniversary Update; OS build 14393) do
not support Wonderware System Platform 2017.

System Sizing Guidelines

The following table provides guidelines for hardware configurations suitable for Wonderware
System Platform 2017 UPDATE 1, based on the size of the application. These guidelines are
subject to the limitations of your Windows operating system, and if applicable, to the SQL
Server edition (Express, Standard, or Enterprise). See the Schneider Electric GCS
Technology Matrix for supported versions of Windows operating systems and SQL Server.
 The Intel Itanium 2 processor is not supported.
 A minimum display resolution of 1280 x 1024 is recommended for engineering tools such
as the Integrated Development Environment (IDE).
 A Windows Server operating system is required for large installations with more than
50,000 I/O per node.
 SQL Server Express is not supported for installations with more than 25,000 I/O per node
(small installations only).
 Pagefile.sys, the Windows paging file (also called the swap file or virtual memory file),
must be enabled. The Windows default setting is enabled.

CPU HD Screen Network

Application Level RAM
Cores Space Resolution Speed

Server Nodes: for Historian Server, GR node, IDE, AppEngine host

Minimum 2 2 GB 100 GB 1024 x 768 100 Mbps

Sm all Application
(1 - 25K I/O per Node)
Recommended 4 4 GB 200 GB 1920 x 1080 1 Gbps

Medium Application Minimum 4 8 GB 200 GB 1024 x 768 1 Gbps

(25k - 50k I/O per
Node) Recommended 8 12 GB 500 GB 1920 x 1080 1 Gbps

Minimum 8 16 GB 500 GB 1024 x 768 1 Gbps

Large Application
(> 50k I/O per Node) Recommended 16 24 GB 1000 GB 1920 x 1080 Dual 1 Gbps

Thin Client Node

RDP clients, ITAA Minimum 1 512 MB N/A 800 x 600 100 Mbps
browsers, mobile
devices Recommended 2 2 GB N/A 1280 x 1024 100 Mbps

Client Node

WindowViewer, Minimum 2 1 GB 100 GB 1024 x 768 100 Mbps

ViewApp, Historian
Client, Remote IDE Recommended 4 4 GB 200 GB 1920 x 1080 1 Gbps

12
Wonderware System Platform Installation Wonderware System Platform Installation Guide

CPU HD Screen Network

Application Level RAM
Cores Space Resolution Speed

Thin Client-Server Node

Basic RDS - Minimum 4 8 GB 200 GB 1024 x 768 1 Gbps

Basic RDS -
RDS, ITAA Server 8 12 GB 500 GB 1920 x 1080 1 Gbps
Recommended
Supports up to five
remote sessions Large RDS - Minimum 8 16 GB 500 GB 1024 x 768 1 Gbps

Large RDS -
16 24 GB 1000 GB 1920 x 1080 Dual 1 Gbps
Recommended

All-In-One Node

All products on a single Minimum 4 8 GB 200 GB 1280 x 1024 100 Mbps

node
1,000 I/O maximum Recommended 6 12 GB 500 GB 1920 x 1080 1 Gbps

Server node type applies to Historian Server, Galaxy Repository node, and nodes hosting AppEngines.
In redundant environments, increase CPU and RAM to maintain a maximum of 40% typical resource utilization.

Supported and Recommended Node Hardware Types

Product Server Thin Client- Client Thin Client All-In-One

Node Server Node Node

Wonderware Application Server

Galaxy Repository Preferred Supported Supported No Supported

Application Engine Preferred Supported Supported No Supported
IDE Preferred Supported Supported RDP Supported

ViewApp Runtime Supported Supported Preferred ITAA/RDP Supported

Wonderware InTouch Standalone
Window Maker (No Modern Apps) Supported Supported Preferred RDP Supported
Window Maker (with Modern Apps) Preferred Supported Supported RDP Supported

WindowViewer / InTouch ViewApp (runtime Supported Supported Preferred ITAA/RDP Supported

only)
Wonderware InTouch for System Platform

Window Maker (with Managed Apps) Preferred Supported Supported RDP Supported

WindowViewer / InTouch ViewApp (runtime Supported Supported Preferred ITAA/RDP Supported

only)
InTouch Access Anywhere

InTouch Access Anywhere Server Supported Preferred No No Supported

InTouch Access Anywhere Client (HTML5 Browser Browser Browser Browser Browser
Browser)
InTouch Access Anywhere Secure Gateway Supported No No No No

13
Wonderware System Platform Installation Guide Wonderware System Platform Installation

Product Server Thin Client- Client Thin Client All-In-One

Node Server Node Node

Historian

Historian Server Preferred Supported Supported No Supported

Historian InSight Client Browser Browser Browser Browser Browser

Historian Client (Active Factory) Supported Supported Preferred RDP Supported

Support Components

OI Gatew ay Preferred Supported Supported No Supported

Schneider Electric Licensing - Server Preferred Supported Supported No Supported

Schneider Electric Licensing - Manager Preferred Supported Supported No Supported

Schneider Electric Licensing - Manager Browser Browser Browser Browser Browser

Client

Required Installation Order of Additional Wonderware Products

Due to license compatibility limitations, some Wonderware products released prior to System
Platform Version 2017 must be installed before you install System Platform. These are:
 Alarm Adviser 2014 R2 SP1 and prior versions
 Intelligence 2014 R3 and prior versions
 Recipe Manager Plus 2014 R3 and prior versions
If any of these products will be installed on the same system as System Platform Version
2017, install these products first. Then, install System Platform.

Common Components
Wonderware System Platform 2017 includes several shared modules that are needed for the
products to operate. You will see the following common components listed under Programs
and Features in the Windows Control Panel after installation is complete:
 ArchestrA Data Store 2.1.1
 ArchestrA Service Bus Framework V5
 ArchestrA Service Bus Framework 4.1.0
 Schneider Electric Licensing
 Schneider Electric Licensing (x86)
 Schneider Electric License Server
 Wonderware Operations Integration – Core G-2.1
 Wonderware Operations Integration – Supervisory Gateway (G-2.1 Series)

14
Wonderware System Platform Installation Wonderware System Platform Installation Guide

OI Gateway is present only if InTouch was installed, or if OI Gateway is selected as part

of a custom installation. OI Gateway replaces FS Gateway that was supplied with
previous releases. If you are upgrading from a prior version of InTouch, or if FS Gateway
was previously installed as a standalone product, FS Gateway is deleted and replaced by
OI Gateway. See Installing OI Gateway and Modifying FS Gateway Installations (see
"Installing OI Gateway and Upgrading from FS Gateway " on page 71) for additional
information.

Windows Network Configuration

If you are installing Wonderware System Platform products on more than one node, we
recommend that you use domain based networking. Domain based (client-server) networks
provide better user account security and management than workgroup based (peer to peer)
networks.
Note: Do not install the Galaxy Repository on a computer that is used as a domain controller
or an Active Directory server.
Operations that rely on inter-node communications may not function correctly in a workgroup
based Application Server installation. Examples of this type operation include connecting to a
remote IDE, or viewing the status of a remote platform.
If you must use workgroup based networking, you can avoid communications issues by
enabling "everyone permissions" for anonymous users. To enable these permissions, go to:
Local Security Policy > Local Policies > Security Options > Network Access:
Let everyone permissions apply to anonymous.

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 software that is incompatible.
 Microsoft .NET® Framework 3.5 SP1: Before starting installation, check that the .NET
3.5 SP1 Framework is installed. If .NET 3.5 SP1 is not installed, install it before
proceeding. This is required for certain SQL Server functionality, even if you are not
installing a product or role that directly uses SQL Server.
To check which versions of .NET are installed:
a. On the Start menu, choose Run.
b. In the Open box, enter regedit.exe. You must have administrative credentials to run
regedit.exe.
c. In the Registry Editor, open the following subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP.
d. The installed versions of .NET will be listed.
If you need to install .NET 3.5 SP1, go to: https://www.microsoft.com/en-
us/download/details.aspx?id=25150
The following prerequisites are installed by the Wonderware System Platform installation
program, if not already present on the system:
 Windows Installer 4.5

15
Wonderware System Platform Installation Guide Wonderware System Platform Installation

 Microsoft .NET® Framework 4.5.2: In addition to .NET 3.5 SP1, .NET 4.5.2 is also
required. .NET 4.5.2 is automatically installed if a version of .NET equal to, or higher than,
4.5.2 is not found.
 SQL Server: SQL Server is required for products or roles that you select for installation
that include GR node or Historian Server. If SQL Server is not present, you are given the
option to install SQL Server 2014 SP2 Express with Tools as part of the Wonderware
System Platform installation. However, SQL Server Express supports only small
installations with less than 25,000 I/O per node.

For medium and large installations, a copy of SQL Server 2016 SP1 Standard Edition is
supplied with Wonderware System Platform. You must install it or another supported
version of SQL Server separately, before you install Wonderware System Platform. See
the Schneider Electric Global Support (GCS) Technology Matrix for a list of supported
SQL Server versions.
If you do not want to install SQL Server, and you have product or role selections that
include the GR node by default, you can select the Customize Installation checkbox and
deselect the Galaxy_Repository. However, this will limit any database-related product
functionality, such as the Application Server IDE, that uses the Galaxy Repository.
See SQL Server Requirements on page 53 for more information about the limitations of
using SQL Server Express instead of a standard or enterprise edition.
The following tables summarize which Wonderware System Platform products and roles
require SQL Server.

SQL
Wonderware System Platform Product Selections Required

Wonderware Application Server Yes

16
Wonderware System Platform Installation Wonderware System Platform Installation Guide

SQL
Wonderware System Platform Product Selections Required

Application Server Runtime No

Application Server Development No

Application Server Galaxy Repository Yes

Wonderware InTouc h Yes

InTouch Development and Runtime Yes

InTouch Runtime Only No

InTouch Access Anywhere and InTouch Runtime No

InTouch Access Anywhere Secure Gat eway No

Historian Yes

Historian Client No

Licensing No

SQL
Wonderware System Platform Role Selections Required

Runtime Client No

Remote System Platform Development Client No

System Platform Development Server Yes

 Without GR node (c ustom installation) No
Historian Server Node Yes

Historian Client Node No

InTouch Access Anywhere Secure Gat eway Node No

All-In-One-Node Yes
 Without GR node and Historian Server (custom installation) No

Note: Wonderware System Platform allows you to install an InTouch development system
without a GR node. However, InTouch Modern Applications will not work without the GR
node.

17
Wonderware System Platform Installation Guide Wonderware System Platform Installation

While installing Wonderware System Platform, if the logged-on user (the installer) is not a
SQL Server administrator, the aaConfig SQL dialog box appears and requests SQL Server
administrator credentials. Enter valid SQL Server administrator credentials when requested.
For more information about setting user privileges with the aaConfig SQL utility, see Setting
the SQL Server Security Mode on page 50. For more information about SQL Server
installation, see About SQL Server Requirements on page 18.
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, (for example, if InTouch Access Anywhere was previously installed). You do
not have to exit from the Wonderware System Platform installation procedure to install the
prerequisite software, with the exception of standard or enterprise versions of SQL Server.
You will need to exit and perform any uninstall operations that are indicated before continuing
with installation.
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
Wonderware System Platform products. In most cases, SQL Server is required when you
install:
 Wonderware Application Server
 Wonderware Historian
 Wonderware InTouch (when used with modern applications)
If a 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.
Note: If you are installing a small system (less than 25000 I/O), you can use SQL Server
Express instead of a standard version of SQL Server. You can elect to install SQL Server
Express as part of the Wonderware System Platform installation process; you do not have to
install it separately.
For more information about SQL Server prerequisites, see SQL Server Requirements on
page 53.

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.

About Product-Based Installation

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

18
Wonderware System Platform Installation Wonderware System Platform Installation Guide

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. The following product selection options are available:
Important: Product-Based installation includes an option to install the InTouch Access
Anywhere Secure Gateway. This option can only be installed on a computer running a
supported version of the Windows Server operating system (minimum: Windows Server
2012). No other System Platform components can be installed with it.

Software Components (included by default when

Product product is selected)

Wonderware Application Server ArchestrA Data Store

Bootstrap
Integrated Development Environment (IDE )
Galaxy Repository
 Plus documentation and licensing components
Wonderware InTouch ArchestrA Data Store
Bootstrap
Integrated Development Environment (IDE )
Galaxy Repository
InTouch Development and Runtime
InTouch Alarm Logger and Purge Archive Components
InTouch Demo A pps
InTouch Recipe Manager
InTouch SQL Access
Symbol Factory
 Plus documentation and licensing components
InTouch Acce ss Anywhere and ArchestrA Data Store
InTouch Runtime
InTouch Access Anywhere Server
Bootstrap
InTouch Runtime
InTouch Alarm Logger and Purge Archive Components
InTouch Recipe Manager
InTouch SQL Access
Symbol Factory
 Plus documentation and licensing components
InTouch Acce ss Anywhere InTouch Access Anywhere Secure Gat eway
Secure Gateway
Note: Must be installed as a standalone product.

19
Wonderware System Platform Installation Guide Wonderware System Platform Installation

Software Components (included by default when

Product product is selected)

Hi storian Historian Server

IDAS (InTouch Data Acquisition Service)
Active E vent remote system client
Configuration Tools
Historian Extensions for OData and SSRS
 Plus documentation
Hi storian Client Historian Client with Trend/ Query Clients
 Plus documentation

About Role-Based Installation

Role-based installation provides a combination of features specific to a node. 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 24.
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.
 Remote System Development Workstation: Install the components required for a
remote engineering development workstation with only the required components to allow
the node to connect to an existing development server; GR is not installed by default. It
allows development and testing of InTouch and Wonderware System Platform
applications.
 System Platform Development Server: Install the components required to host the
development server, and develop and test InTouch and Wonderware System Platform
applications.
 Historian Server Node: Install the necessary components to store historical data in an
ArchestrA environment.
 Historian Client Node: Install the components required to connect to an existing
Historian Server and analyze the data.
 All-in-One Node: All products are installed on a single node.
 Custom: Allows you to customize the components that are installed.

20
Wonderware System Platform Installation Wonderware System Platform Installation Guide

 InTouch Access Anywhere Secure Gateway Node: Install the components to access
Wonderware InTouch applications hosted on Terminal Servers by using HTML5
compatible web browsers. This component cannot be installed on a computer that has
other System Platform components installed.

Role Component

Runtime Client ArchestrA Data Store

Bootstrap
InTouch Runtime
InTouch Alarm Logger and Purge Archive Components
InTouch Recipe Manager
InTouch SQL Access
Symbol Factory
Historian Client with Trend/ Query Clients
 Plus documentation and licensing components
Remote System Development ArchestrA Data Store
Workstation
Bootstrap
Integrated Development Environment (IDE )
InTouch Development and Runtime
InTouch Alarm Logger and Purge Archive Components
InTouch Demo A pps
InTouch Recipe Manager
InTouch SQL Access
Symbol Factory
Historian Client with Trend/ Query Clients
 Plus documentation and licensing components

21
Wonderware System Platform Installation Guide Wonderware System Platform Installation

Role Component

System Platform Development ArchestrA Data Store

Server
Bootstrap
Integrated Development Environment (IDE )
Galaxy Repository
InTouch Development and Runtime
InTouch Alarm Logger and Purge Archive Components
InTouch Demo A pps
InTouch Recipe Manager
InTouch SQL Access
Symbol Factory
Historian Client with Trend/ Query Clients
 Plus documentation and licensing components
Hi storian Server Node Bootstrap
Historian Server
IDAS (InTouch Data Acquisition Service)
Active E vent remote system client
Wonderware Historian InSight
Configuration Tools
Historian Extensions for OData and SSRS
 Plus documentation and licensing components
Hi storian Client Node ArchestrA Data Store
Bootstrap
Historian Client with Trend/ Query Clients
 Plus documentation and licensing components
InTouch Acce ss Anywhere InTouch Access Anywhere Secure Gat eway
Secure Gateway Node
Note: Must be installed as a standalone product.

22
Wonderware System Platform Installation Wonderware System Platform Installation Guide

Role Component

All-In-One Node ArchestrA Data Store

Includes all Application Bootstrap
Server, InTouch, Historian,
Integrated Development Environment (IDE )
Historian Client, and
Licensing components Galaxy Repository
InTouch Development and Runtime
InTouch Alarm Logger and Purge Archive Components
InTouch Demo A pps
InTouch Recipe Manager
InTouch SQL Access
InTouch 16 PenTrend
Symbol Factory
Historian Server
IDAS (InTouch Data Acquisition Service)
Active E vent remote system client
Wonderware Historian InSight
Configuration Tools
Historian Extensions for OData and SSRS
Historian Client with Trend/ Query Clients
 Plus documentation and licensing components
Custom [No components selected by default]

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 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 will 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.
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 use an existing user account, it should meet
the following requirements:
 User account with a permanent password that does not expire.

23
Wonderware System Platform Installation Guide Wonderware System Platform Installation

 User account in which the password cannot be changed.

 User account that is a member of the local Administrators group.
Important: To enhance security, the ArchestrA User Account is not permitted to log on to the
Galaxy locally or through Remote Desktop Services by default. This is configured in the
operating system user rights management.

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.
If you select a pre-existing user account during installation that is already a local administrator
(domain or local), the existing interactive log on privileges are not changed.
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 49.
See Modifying an ArchestrA User Account on page 49 if you need to change or recreate the
ArchestrA User Account.

Installing the Wonderware System Platform

You can select a product-based or a role-based installation for your computer.
Note: Prerequisites are installed as part of product installation and not in a separate
workflow.
To install the Wonderware System Platform
1. Insert the DVD into your DVD-ROM drive. Depending on your computer's security
settings, Windows User Access Control may ask for permission to run the installation
program. Allow it to run, and the startup screen appears. If your network or company
security policy does not permit autorun, browse the root directory of the DVD and run
setup.exe.
 If the operating system is not supported, you blocked from continuing. See Operating
System Minimum Requirements (see "Operating System Minimum Requirements" on
page 11) for additional information.
 If the operating system is supported, basic installation requirements are checked.
.NET 4.5.2 is installed if it or a later version is not already present.
Note: You may be prompted to reboot after the .NET framework is installed.

24
Wonderware System Platform Installation Wonderware System Platform Installation Guide

2. After some automatic configuration occurs, the select installation mode dialog box
appears.

3. Select whether you want a product-based or a computer role-based installation, and then
click Next. The select options dialog box appears. Its appearance will vary, depending on
whether you chose product-based or role-based installation.
 For information about product-based installation, see About Product-Based Installation
on page 18.
 For information about role-based installation, see About Role-Based Installation on
page 20.

25
Wonderware System Platform Installation Guide Wonderware System Platform Installation

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

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. If you are installing InTouch Access Anywhere Secure Gateway, it must be
installed by itself, without any other System Platform components.

26
Wonderware System Platform Installation Wonderware System Platform Installation Guide

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

5. To proceed with your selections without making any changes, click Next. To change your
configuration, select the Customize Installation check box before clicking Next.
Important: You must select the Customize Installation option to install the InTouch 16-
Pen Trend Wizard supplementary component.
6. Complete the following installation steps to install InTouch HMI supplementary
components and make other changes:
a. Select Customize Installation.

27
Wonderware System Platform Installation Guide Wonderware System Platform Installation

b. Click Next. The customize installation dialog box appears.

c. Scroll through 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.

28
Wonderware System Platform Installation Wonderware System Platform Installation Guide

7. If you have selected an InTouch HMI features, the language selection dialog box
appears. Select the language for your InTouch HMI installation. The InTouch language
versions are supported only for the matching operating system language. For example,
the German version of the InTouch HMI is only supported on the German operating
system.

8. Click Next. The End User License Agreement dialog box appears.

29
Wonderware System Platform Installation Guide Wonderware System Platform Installation

9. Review the license(s). Click I have read and accept the terms of the license
agreement(s), and then click Agree.
10. If the products or roles you selected require it, the ArchestrA User Account dialog box
appears.
Note: If an Archestra User Account is NOT required (for example, if you are only installing
Historian Client), you will be prompted to click Install. If this is the case, skip to step 12.

11. Specify an ArchestrA User Account. You can specify an existing user account, or create a
new ArchestrA User Account if no other ArchestrA-enabled software is installed on the
computer.
 To select an existing user account:
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.
– The account must have a password that cannot be changed.
– The account must be a member of the local Administrators group.
c. Click Next to complete the User Account setup.

 To create a new account:

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

30
Wonderware System Platform Installation Wonderware System Platform Installation Guide

e. Type your user name and password.

12. If the products or roles you selected require Microsoft SQL Server, and a supported
version of SQL Server is not already installed, you will be prompted to select either
automatic installation of SQL Server Express, or to exit and manually install a full version
of SQL Server.

Caution: If you select SQL Server Express, Wonderware System Platform will
automatically grant you (the logged in user) SQL sysadmin privileges. This level of access
is required to proceed with SQL Server Express installation. You will retain sysadmin
privileges even after installation. If you need to remove sysadmin privileges from the
logged in account, be sure to create a sysadmin account first.
 Click Yes to use SQL Server Express. SQL Server Express is adequate for systems
with less than 25000 IO. It will be installed automatically along with the other
prerequisites and the selected Wonderware System Platform components.
 Click No to skip SQL Server Express installation. Then, click Exit and manually install
SQL Server. Wonderware System Platform for medium and large installations
includes a separate DVD with a full version of SQL Server 2016 SP1 Standard.
However, you can install any supported version of SQL Server. See the Schneider
Electric Global Support (GCS) Technology Matrix for a list of supported SQL Server
versions.
When you have finished SQL Server installation, restart Wonderware System Platform
installation.

31
Wonderware System Platform Installation Guide Wonderware System Platform Installation

13. A list of missing prerequisite components (if any) and the Wonderware System Platform
products to be installed are displayed.

Note: Any prerequisites required for the products selected for installation will be listed
above the list of products and components. The prerequisites will be installed first, and
the product and components will be installed immediately after installation of the
prerequisites has finished. If you elected to install SQL Server Express, it will be installed
along with any other prerequisites.

32
Wonderware System Platform Installation Wonderware System Platform Installation Guide

14. Click Install to proceed. The progress bar appears.

15. After the installation is over, the complete installation dialog box appears.

 Select View Readme for important information about Wonderware System Platform
2017 UPDATE 1, including hardware and software requirements, new features, and
known and resolved issues.
 Select Configure to continue. See Configuration (see "Configuring Wonderware
System Platform Components" on page 34) for the final steps to complete installation .

33
Wonderware System Platform Installation Guide Wonderware System Platform Installation

Configuring Wonderware System Platform Components

Both Schneider Electric Licensing and the Wonderware Historian Server 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 require post-installation configuration. You can configure the
locations for the product database and the data files.
You must have sysadmin permissions to configure products using the Configurator.
To start the Configurator
 Click Configure on the final installation dialog box. The Configurator dialog box appears.
The product feature tree expands by default.

The status of each item in the Configurator is displayed when the Configuration opens and
as items are configured. The status indicators are:
o Error - Indicates that an error occurred during configuration.
o Not Configured - Indicates that the feature is installed, but not configured.
o Warning - Indicates that configuration is complete, but with warnings.
o Configured - Indicates that configuration completed successfully.
o Not Installed - Indicates that the feature is not installed.

Configuring the Schneider Electric License Server Location

Detailed information about configuring the Schneider Electric License Server is contained in
the Schneider Electric Licensing Guide. This guide can be accessed from the Schneider
Electric License Manager (see License Installation and Activation (see "License Installation
and Activation" on page 9) for additional information). The basic steps to configure the
location of the Schneider Electric License Server are:
1. In the left pane, select Schneider Electric Server.
 Primary Server Name: if the License Server is not installed on the local node, enter
the License Server name, or select a server name from the drop down list of
previously-configured License Servers (if any).
 Server Port: default is 55555

34
Wonderware System Platform Installation Wonderware System Platform Installation Guide

 Backup: If you have configured a backup server (secondary server), select the
checkbox to enable backup. Then, enter the secondary server name.

2. Click the Configure button.

3. Configure any other products that are listed in the left pane.
4. Click the Close button to exit from the Configurator.

Configuring Databases and Data File Locations

You can use the Configurator to configure Wonderware Historian settings.
Note: Before running the Configurator, be sure SQL Server is installed and running. Also, be
sure you have SQL Server administrator rights.
You can start the Configurator at any time from the Windows Start menu on the Historian
computer.
To configure the databases and data file folders
1. Start Configurator from the Start menu.

35
Wonderware System Platform Installation Guide Wonderware System Platform Installation

2. In the left pane, click Server. Then configure the databases as follows.

a. Under Database Information, specify the SQL Instances and database path.
– SQL Instance
Name the SQL Instance associated with this historian.
– Database Path
Unless you have specific requirements, keep the default SQL Server database
path. This is the path where the configuration database is deployed. Click the
ellipsis button to specify a different directory in which to install the historian
database files.
b. Under Existing Database Conflict, read any notices.
If the database is created for the first time, then this option is not available. When
reconfiguration is done, then the Drop and Create New Database option is available.
If you select this check box, then the existing database is dropped and a new
database is created. If this check box is cleared, then the database is not dropped, but
configured for changes, if any.
c. Under Alarms & Events Storage, configure how you want to store alarm and events.

36
Wonderware System Platform Installation Wonderware System Platform Installation Guide

Important: If you want to change this setting later after the Historian is running, you
must first shut down and disable the historian using the Management Console. Then,
after making the change, you can restart and enable the historian.
– High-speed (default/recommended)
The high speed setting for storing alarms and events in history blocks provides
several advantages. You can manage the data using simple operations such as
moving, copying, or deleting folders, instead of using database management
software.With this storage method, you no longer need to purge to sustain
storage.This method offers significantly higher storage rates. Also, the capacity for
alarm and event storage is only limited by disk space, not by insertion rate.
If you select this option, you will not be able to query alarm and event history from
SQL queries, but alarm and event data stored in history blocks can be retrieved
via the Open Data Protocol (OData), the ArchestrA AlarmClient control 2014 R2 or
later, or the Historian SDK 2014 R2 or later.
For more information on retrieving alarm and event history via OData, see the
Wonderware Historian Retrieval Guide.
– Traditional
The traditional setting stores alarms and events in the A2ALMDB SQL Server
database. This works well for smaller applications. Alarm and event data stored in
the A2ALMDB database can be retrieved using SQL queries. You can also use
SQL Server tools, such as Reporting Services, to query alarm and event history.
d. Under Network, accept the default ports or change these settings. The ports you
specify are added to the exclusions list of Windows Firewall.
– Historian TCP port is used for replication data.
If you are configuring a tiered historian server, specify the port number for tag
replication between the tier-1 and tier-2 servers. You must use the same port for
all the tier-1 and tier-2 systems working together in the tiered configuration.
– InSight/REST TCP port is used for data queries via InSight or the Historian REST
API to the Historian Server.
Type the number for the port used by InSight and REST interface queries.
– Search port is used for data searches. This field is for reference only.
e. Under Security, Check the box if you want to allow remote access of this server's
System Management Console (SMC).

37
Wonderware System Platform Installation Guide Wonderware System Platform Installation

3. In the left pane, click Security. Configure the security options as follows.

a. Under Historian Users, review the existing users and roles for this server. Make
adjustments to the list as needed:
– To create a new user account, click Create Users and then specify account
details.
– To add existing user accounts to this list, click Add Users and then select the
account criteria to use.
– If you don't need this account anymore, mark the Delete Account check box.
b. Under SQL Logins, do one of the following to ensure your SQL Server logins are
secure:
– If you want to keep using a default account listed, type a new password.
– If you don't need this account, mark the Delete Account check box.

38
Wonderware System Platform Installation Wonderware System Platform Installation Guide

Note: Secure Development Lifecycle (SDL) guidelines recommend against using

automatically created users like aaUser and aaAdminUser with well-known or publicly
documented passwords.

When you migrate from an older version of Wonderware Historian Server, this area is
populated with all preexisting SQL Server accounts and gives you the option to
change account password and to delete unused accounts to ensure strong security for
your system.
4. In the left pane, click Search. Then configure the search options as follows.

Under Search Configuration, specify file locations.

o Data Path
Accept the default path, or click the ellipsis button to specify a different directory for
the historian history blocks.
Make sure that you have plenty of space on this drive most of your plant data will be
stored here. (The SQL Server database files typically take less disk space.)
o Log Path
Accept the default path, or click the ellipsis button to specify a different directory for
the log files.

39
Wonderware System Platform Installation Guide Wonderware System Platform Installation

o Mark the Reindex Search Documents check box to create a new index of all existing
tags.
5. In the left pane, click Reporting. Then mark the appropriate check boxes to configure
OData extensions for SQL Reporting Studio or Visual Studio Report Designer on your
system.

6. In the Configuration Messages area, read messages regarding prerequisite checks,

current configuration state, and configuration activities that are logged.
7. Click Configure. The Processing SQL Script dialog box appears. You can see the
historian database configuration scripts running. Multiple scripts run during the
configuration.
8. After the system finishes running the SQL scripts, the Historian node and Historian Server
node are shown with a green status indicator if the database is successfully configured.
9. Click All Messages to see all the configuration messages.

40
Wonderware System Platform Installation Wonderware System Platform Installation Guide

System Restart after Configuration

When you have configured all the listed components, click Close. The system will prompt you
to restart. You can restart now or later.

Note: The installed programs may not function properly until you restart the system.
After the system restarts, and before you start using Wonderware System Platform, make
sure that you have activated your product licenses. See License Installation and Activation
(see "License Installation and Activation" on page 9).

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.
To modify an installation
1. Select the Modify option from the Wonderware System Platform Modify, Repair or
Remove Installation dialog box. You can open the dialog by doing either of the following:
 Run Setup.exe from the Wonderware System Platform installation DVD.
 Navigate to Uninstall or Change a Program in the Windows Control Panel. Then,
select any Wonderware System Platform component and then click the
Uninstall/Change button.

41
Wonderware System Platform Installation Guide Wonderware System Platform Installation

Note: The name of the Uninstall/Change option may vary depending on which
Windows operating system is installed on your computer.

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

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

42
Wonderware System Platform Installation Wonderware System Platform Installation Guide

4. Click Modify. The selected components are added or removed and the complete
modification dialog box appears.
5. Click Finish.
Note: The system may not prompt you to restart the system after Modify is successful.
However, if you have added a new product or feature, a system restart is recommended.

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 Uninstall or Change a Program option in Windows Control Panel. The list of
software installed on your 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.
4. Click Repair. The complete repair dialog box appears.
5. Click Finish.

Uninstalling Wonderware System Platform

Uninstall a Wonderware System Platform Component
You can uninstall any component of the Wonderware System Platform that is installed on
your computer.
To uninstall a Wonderware System Platform component
1. Click the Uninstall or Change a Program option in Windows Control Panel. The list of
software installed on your computer appears.

43
Wonderware System Platform Installation Guide Wonderware System Platform Installation

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.

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.
5. Click Finish.

Uninstall All Components

To uninstall Wonderware System Platform (remove all components)
Begin by opening the Windows Control Panel, and select Programs and Features. Uninstall
components by selecting the component, and then click Uninstall. You must uninstall
components in the following order:
Note: Ignore components that are listed below if they have not been installed on your system.
1. Wonderware Application Server 2017 UPDATE 1
2. Wonderware InTouch 2017 UPDATE 1
3. Wonderware Historian 2017 UPDATE 1
4. Wonderware Historian Client 2017 UPDATE 1
5. Wonderware Operations Integration – Core G-2.1
6. Wonderware Operations Integration – Supervisory Gateway (G-2.1 Series)
7. ArchestrA Service Bus Framework V5

44
Wonderware System Platform Installation Wonderware System Platform Installation Guide

8. ArchestrA Service Bus Framework V4.1.0

9. Schneider Electric Licensing (x86)
10. Schneider Electric Licensing
11. Schneider Electric License Server
12. Schneider Electric License Manager
13. ArchestrA Data Store 2.1.1

Upgrading Wonderware System Platform

You can upgrade to Wonderware System Platform 2017 Update 1 from Wonderware System
Platform 2014 R2 SP1 (with or without Patch 01 or Patch 02), or from Wonderware System
Platform 2017. Only components that were previously installed can be upgraded. You cannot
choose to add components that were not already installed, and you cannot deselect
components. That is, if a newer version of a component is included on the installation DVD,
the previously installed component is automatically upgraded.
If you are upgrading from Wonderware System Platform 2014R2 SP1, you will be changing to
the new licensing system. See License Installation and Activation (see "License Installation
and Activation" on page 9) for additional information.
Note: If you plan to upgrade Wonderware System Platform on a computer that has InTouch
Access Anywhere Server or InTouch Access Anywhere Gateway installed, you must first
uninstall the InTouch Access Anywhere Server or Gateway. Then, upgrade Wonderware
System Platform and finally reinstall InTouch Access Anywhere.
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
startup screen appears, and then the upgrade feature dialog box appears.

Products that will be upgraded are listed in the startup screen. Schneider Electric
licensing will be displayed for upgrade if any of the following products are installed:
o Alarm Adviser
o Intelligence
o Recipe Manager Plus
Note: You can only upgrade the products that are already installed, and you will not be
able to install additional products during the upgrade process.
2. Click OK and wait as configuration completes. If there are any recommended steps that
should be performed before continuing, they will be displayed.

45
Wonderware System Platform Installation Guide Wonderware System Platform Installation

3. Follow the instructions given and click Next. A list of all Wonderware System Platform
components appears. The installed components that need to be upgraded are selected
and disabled. You cannot clear these check boxes or select more components during the
upgrade.

4. Click Next. The upgrade dialog box appears.

5. Click Upgrade to proceed with the upgrade.

6. Restart the computer when prompted to apply the upgrade.
46
Wonderware System Platform Installation Wonderware System Platform Installation Guide

If you are upgrading from a prior version of Wonderware Application Server, and a galaxy is
deployed, the Galaxy Patcher will start as soon as you connect to the galaxy from the
Application Server IDE. Undeployed galaxies are not patched until you connect to them.
Important: Galaxy patching may take several minutes. Do not shut down the node while the
patching operation is in progress.
If you have upgraded from Wonderware System Platform 2014R2 SP1, a new icon for the
Wonderware Application Manager is installed on the desktop, Use the Application Manager to
select and run deployed InTouch OMI ViewApps.

47
 Wonderware System Platform Installation Guide

C HAPTER 2
Security and Permissions
In This Chapter
Modifying an ArchestrA User Account ............................................................................................ 49
SQL Server Rights Requirements .................................................................................................. 49
Setting the SQL Server Security Mode ........................................................................................... 50
Restoring Required SQL Server Accounts ...................................................................................... 52
Setting the FIPS Security Policy Option .......................................................................................... 52

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 ArchestrA User Account on page 23 and
the Change Network Account utility on-line help.
Important: When you change or recreate the ArchestrA User Account, a system restart is
required. Close all applications and click OK to proceed.

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.

SQL Server Rights Requirements

When you install a Galaxy Repository (as part of an Application Server or InTouch
installation), the installation process creates the following items to support Galaxy
communications, system security, and connection to SQL Server:
 An operating system user group (aaAdministrators)
 An ArchestrA User Account
 A Galaxy owner user account (aaGalaxyOwner)
 A SQL Server logon

49
Wonderware System Platform Installation Guide Security and Permissions

The ArchestrA User Account is an operating system administrator and, as a member of the
aaAdministrators group, has the SQL sysadmin fixed server role. This account must be
defined for Galaxy operations. See ArchestrA User Account on page 23 for additional
information.
Caution: aaGalaxyOwner and ASBService are reserved OS user names. aaAdministrators
and ASBSolution are reserved OS group names. Do not create users or groups with these
names.
The automated process that creates the aaAdministrators group, ArchestrA User Account,
and aaGalaxyOwner user account also provides the rights required for operations within the
GR. The aaAdministrators group, ArchestrA User Account, and aaGalaxyOwner user account
must all be present and enabled for Galaxy operations.
Note: The aaGalaxyOwner account is the owner (dbo) of all Galaxy databases in your
system. It does not have a system login, and does not have the OS admin privileges that the
ArchestrA User Account has.
 If you accidentally delete the aaAdministrators group or the ArchestrA User Account from
the Windows operating system, you can run either the Change Network Account utility
or the aaConfig SQL utility to restore it.
Both of these programs are located in the Wonderware folder, under All Programs.
 If you accidentally delete the aaGalaxyOwner account from the Windows operating
system, you must run the aaConfig SQL utility to restore it.
 If you accidentally delete the aaAdministrators group, ArchestrA User Account, or
aaGalaxyOwner from the SQL Server security logons, you must run the aaConfig SQL
utility to restore it.

Setting the SQL Server Security Mode

If you are a SQL administrator, you can use the aaConfig SQL utility to set user privileges
within SQL Server for accessing and using Galaxy databases (the Galaxy Repository). The
aaConfig SQL utility is included with Wonderware Application Server. User privileges are
determined by the security mode. Two security modes are available:
WARNING! The aaConfig SQL utility automatically restarts the computer to ensure
syste m stability. If you press OK, you will not be able to cancel the restart.
 Legacy Mode. This is the default setting. Authenticated users have the sysadmin
privilege and are not restricted from any SQL Server activity, including creating,
modifying, and deleting any SQL Server database.
Select this mode to ensure that users can perform all Galaxy operations. If users will
frequently be restoring Galaxies created with previous versions of Application Server, this
may be the preferred setting.
 Enhanced Security Mode. This mode removes the sysadmin privilege from Application
Server users, and retains only the minimum privileges needed for normal operations.
Select this mode for compliance with corporate or other IT security requirements or
guidelines.

50
Security and Permissions Wonderware System Platform Installation Guide

If you select Enhanced Security Mode, you may be prompted to provide SQL sysadmin
user credentials when restoring a Galaxy that was created with an older version of
Application Server. You do not need sysadmin credentials to restore Galaxies created
with the current version of Application Server.
Enhanced Security Mode removes the SQL sysadmin privilege from various ArchestrA
users and groups, including:
o NTAUTHORITY\SYSTEM
o aaAdminstrators (local security group that contains the ArchestrA Network User)
o <NodeName>\ASBService (used for cross-Galaxy communications, and for browsing
ArchestrA components)

To change the SQL security mode with aaConfig SQL

1. Select the authentication type (Windows or SQL Server).
2. Provide SQL sysadmin logon credentials (User Name and Password).
3. Select the SQL Server security mode. The system will restart automatically.
4. If you have selected Enhanced Security Mode: After the system restarts, ensure that the
BUILTIN\Administrators group does not have the sysadmin role.
Note: The system performs a check prior to changing to Enhanced Security Mode. This is
to ensure that at least one account will exist with the SQL sysadmin privilege after the
change. If the system check determines that no accounts with the SQL sysadmin privilege
will remain after changing modes, an error message will be displayed and security will
remain in Legacy Mode.

51
Wonderware System Platform Installation Guide Security and Permissions

Restoring Required SQL Server Accounts

If you delete the aaAdministrators group, ArchestrA User Account, or the aaGalaxyOwner
account, restore them by running aaConfigSQL. You do not have to do anything else to
restore the missing group or account. The missing group or account is created automatically
when you run the utility. Running the utility does force a system restart, however, even if you
retain the same security configuration.

Setting the FIPS Security Policy Option

Application Server does not support the FIPS (Federal Information Processing Standards)
security policy option in Microsoft Windows.The Federal Information Processing Standards
are United States Government standards that provide a benchmark for implementing
cryptographic software. If your system has FIPS enabled, you should disable it. The security
setting for FIPS is listed under Security Settings> Local Policies> Security Options> System
cryptography, or as part of Group Policy.

52
 Wonderware System Platform Installation Guide

C HAPTER 3
Configuring SQL Server
In This Chapter
SQL Server Requirements............................................................................................................. 53
Working with SQL Server Versions ................................................................................................ 54
Using a Non-Default Port for SQL Server ....................................................................................... 56

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 a product or role that includes either Historian Server or an
ArchestrA Galaxy Repository, you can choose to allow Wonderware System Platform to
automatically install SQL Server 2014 Express SP2 with Tools as it installs other
prerequisites.
Note: SQL Server Express is limited for use with small installations only (25,000 I/O per node
or less). 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 49, 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 a product or role that requires the Galaxy Repository, and SQL Server is not
installed on the computer, the installation program will install SQL Server 2014 Express
with Tools SP2.
 You cannot install and use a GR 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 SQL Server Configuration Manager.

53
Wonderware System Platform Installation Guide Configuring SQL Server

2. In the tree pane, click SQL Server Services.

3. If any services are displayed in the results pane, verify that each service under is in the
Running state.
If a service is Stopped, 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 each protocol is Enabled:
 Shared Memory
 Named Pipes
 TCP/IP
If Disabled appears, right-click on the protocol name and enable it.
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 each client protocol is Enabled:
 Shared Memory
 Named Pipes
 TCP/IP
If Disabled appears, right-click on the protocol name and enable it.
8. If you had to enable any services:
a. Start Task Manager.
b. Go to the Services tab.
c. Restart MSSQLServer/<InstanceName>.

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

54
Configuring SQL Server Wonderware System Platform Installation Guide

Note: Nodes are defined as follows: Small = up to 25,000 I/O per node; Medium = 25,000 to
50,000 I/O per node; Large = 50,000 to 400,000 I/O per node.

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 2014 Express with Tools SP2 is installed as part of the installation
process. This version of SQL Server is suited for small configurations, and is best for a single-
node system. You can use any of the following versions of SQL Server Express for small
installations:
 SQL Server 2012 Express SSME (SP2)
 SQL Server 2014 Express SSME (no service pack, SP1, and SP2 (default))
 SQL Server 2016 Express SSME (no service pack, SP1)
See the Wonderware System Platform Readme for additional information.

SQL Server not found on node: medium and larger configurations

For medium and larger systems, the following versions of SQL Server are supported:
 SQL Server 2012 Standard or Enterprise edition (SP2)
 SQL Server 2014 Standard or Enterprise edition (no service pack, SP1, SP2)
 SQL Server 2016 Standard or Enterprise edition (no service pack, SP1)
See the Wonderware System Platform Readme for additional information.
For more information about the comparative capabilities of SQL Server 2016 and earlier
versions, see the following URL:
https://msdn.microsoft.com/en-us/library/mt590198(v=sql.1).aspx
https://msdn.microsoft.com/en-us/library/mt590198(v=sql.1).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 Express 2014 SP2 is not 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 2017 UPDATE 1 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 2017 UPDATE 1 products, installation will stop and a warning
will be displayed stating the SQL Server version is not compatible. You must upgrade to a
supported version of SQL Server before you can resume installation.

55
Wonderware System Platform Installation Guide Configuring SQL Server

Using a Non-Default Port for SQL Server

The default port for SQL Server is 1433. If you want to use a different port number, use SQL
Server Configuration Manager to set the port number.
If you are using the SQLData object to store and retrieve data, you will need to enter the non-
default SQL Server port number as you enter other database connection information. See the
SQLData Object help file, available through the ArchestrA IDE, for additional information.
To change to a non-default SQL Server port number
1. If you are upgrading from a prior version of Wonderware System Platform, upgrade all
nodes. See Basic Upgrade Sequence on page 61 for more information. If this is a new
installation, continue to step 2.
2. Launch SQL Server Configuration Manager.
3. Select SQL Server Network Configuration, then select Protocols for MSSQLSERVER.
4. In the list of protocol names to the right, select and open TCP/IP Properties.

5. In the TCP/IP Addresses tab, scroll down to IPAll.

6. Change the TCP Port number from 1433 to the desired number.
7. Click OK or Apply to commit the changes.
8. Reboot the GR node.

56
Configuring SQL Server Wonderware System Platform Installation Guide

Setting a Windows Firewall Exception for the SQL Server Port

You will need to set a Windows Firewall exception for a non-default SQL Server port number
if you are using a remote node. Without access through the firewall, remote nodes will be
unable to connect to the database.
To allow access through the Windows Firewall
1. Open Allow an app through Windows Firewall.
2. Select SQLServer from the list of applications. Double click to open the Edit a Port
window.
3. Change the port number to match the port number listed in SQL Server Configuration
Manager.
4. Click Network types... and select Domain.

57
 Wonderware System Platform Installation Guide

C HAPTER 4
Application Server Upgrade
Direct upgrade to Wonderware System Platform 2017 UPDATE 1 is supported from:
 Wonderware System Platform 2014 R2 SP1 (with or without Patch 01 or Patch 02
applied).
 Wonderware System Platform 2017.

In This Chapter
About Upgrading Application Server............................................................................................... 59
Basic Upgrade S equence .............................................................................................................. 61
Upgrading a Galaxy Repository Node ............................................................................................ 62
Upgrading an IDE-only Node ......................................................................................................... 62
Migrating the Galaxy Database ...................................................................................................... 63
Upgrading Run-Time Nodes .......................................................................................................... 63
Upgrading Redundant Pairs .......................................................................................................... 64
Upgrade Considerations for Multi-Galaxy Communication ............................................................... 68
Issues with Legacy Common Components ..................................................................................... 69

About Upgrading Application Server

Important: Direct upgrade to Application Server 2017 UPDATE 1 is supported from
Application Server 2014 R2 SP1 (with or without Patch 01 or 02) and Wonderware System
Platform 2017. Your system must meet the minimum system requirements, including
operating system and SQL Server version.
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, with the
following upgrade exceptions:
o Windows 8 to Windows 8.1
o Windows 8.1 to Windows 10
o Windows Server 2012 to Windows Server 2012 R2
Other than the above exceptions, Wonderware System Platform products must be
uninstalled prior to upgrading the operating system.
 You can upgrade SQL Server after Application Server is installed. Refer to Microsoft’s
SQL Server resources for guidelines and procedures.

59
Wonderware System Platform Installation Guide Application Server Upgrade

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.
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 deployed WinPlatform object is removed from
run time and upgraded to version 2017 UPDATE 1.
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 can choose to
continue with the upgrade or to cancel. If you continue, the components are removed and
upgraded to version 2017 UPDATE 1.
Upgraded IDE/Client nodes cannot connect to a non-upgraded GR node. The GR node is
undeployed before it is upgraded to Application Server 2017 UPDATE 1.
 IDE, GR, and Bootstrap
A warning message is displayed if you attempt to upgrade a computer with a deployed
WinPlatform or if a client application is connected to the GR node. You can choose to
continue with the upgrade or to cancel. If you continue, all components are removed and
upgraded to version 2017 UPDATE 1.
 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.
Note: No system objects are removed on non-GR nodes when migrating from earlier versions
of Application Server.
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.

60
Application Server Upgrade Wonderware System Platform Installation Guide

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 107.

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 62.
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 62.
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 63.
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 Run-Time Nodes on page 63.
 Upgrade redundant pairs one at a time. For more information, see Upgrading
Redundant Pairs on page 64.
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.

61
Wonderware System Platform Installation Guide Application Server Upgrade

Important: After you have upgraded the GR node to Application Server 2017 UPDATE 1,
you will not be able to deploy or undeploy from the GR node to non-upgraded remote nodes.
Also, an IDE node that has been upgraded to 2017 UPDATE 1 will not be able to connect to a
GR node that has not been upgraded.

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 2017 UPDATE 1 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.
5. Click Next. The Prerequisites dialog box appears. You can select the Show All
check box to view all prerequisites.
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: An IDE node that has been upgraded to Application Server 2017 UPDATE 1 will
not be able to connect to a GR node that has not been upgraded. Conversely, an IDE node
that has not been upgraded cannot connect to a GR node that has been upgraded.
To upgrade an IDE-only node
1. On the IDE node, run Setup.exe from the DVD. An information box appears that lists the
products installed on the node.
2. Click OK. The Select Features dialog box appears. Any previously-installed features
appear dimmed.
3. Click Next. The Ready to Upgrade dialog box appears.

62
Application Server Upgrade Wonderware System Platform Installation Guide

4. Click Upgrade. The node will be upgraded to Wonderware System Platform 2017
UPDATE 1, then click Finish.
5. When prompted, click Restart Now to complete the upgrade.

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.
2. Connect to the Galaxy database to migrate. You are prompted to migrate it.
3. Follow the prompts to complete the migration.
Migration errors
Migration of a very large Galaxy may fail, with various (and sometimes misleading) warnings
and errors displayed in the Logger. This is due to the Galaxy database transaction log
expanding over its maximum allocated size.
Before making the changes described here, use the Event Viewer to check if the transaction
log is full. If you confirm that the transaction log has exceeded its maximum file size
restriction, remove the restriction as follows:
1. In SQL Server Management Studio, right click the Galaxy database, then click
Properties on the shortcut menu.
2. In the Database Properties dialog, select the Files page.
3. Locate Log ... in the File Type column.
4. Click the ellipsis (...) button in the Autogrowth column on the same line.
5. In the Change Autogrowth for Base_Application_Server_log dialog, click the
Unrestricted File Growth radio button under the Maximum File Size parameter, then
click OK.
6. After the Galaxy migration is finished, repeat steps 1 through 5 to reinstate the file size
limit on the transaction log.

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 2017 UPDATE 1,
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 2017 UPDATE 1.

63
Wonderware System Platform Installation Guide Application Server Upgrade

Upgrading to Application Server 2017 UPDATE 1 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. On the run-time node, run Setup.exe from the DVD. An information box appears that lists
the products installed on the node.
2. Click OK. The Select Features dialog box appears. Any previously-installed features
appear dimmed.
3. Click Next. The Ready to Upgrade dialog box appears.
4. Click Upgrade. The node will be upgraded to Wonderware System Platform 2017
UPDATE 1, then click Finish.
5. When prompted, click Restart Now to complete the upgrade.

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.

64
Application Server Upgrade Wonderware System Platform Installation Guide

Node A Node B Node C

GR Primary AppEngine (E1) Backup AppEngine (E1b)
Platform 0 (P0) Platform 1 (P1) Platform 2 (P2)

Resulting Resulting Resulting

Step Action State Action State Action State

(Initial state) Deployed. E1 Deployed E1b

– Active. Deployed –
Standby.

1 Upload run- Changes

time made at run-
changes time now
stored in the
database.

2 Upgrade; P0 and its

shut down engines
P0 and its remain
engines deployed but
when are shut
prompted. down.

3 Reboot Software is
when now at v2
prompted and P0
engines are
running off-
scan.

4 Open IDE Galaxy

and migrate database
database now at v2.
IDE shows
P0, P1 and
P2 in SUP
state.

5 Optional: InTouch
Open and ViewApps
migrate now at v2.
InTouch
ViewApps

65
Wonderware System Platform Installation Guide Application Server Upgrade

Node A Node B Node C

GR Primary AppEngine (E1) Backup AppEngine (E1b)
Platform 0 (P0) Platform 1 (P1) Platform 2 (P2)

Resulting Resulting Resulting

Step Action State Action State Action State

6 Cascade All objects

deploy P0 on P0 are
deployed.
The SUP
state is
cleared for
P0 objects.

7 Upgrade; P2, its

shut down hosted
P2 and its engines and
engines objects
when remain
prompted. deployed but
are shut
down.
8 Reboot when E1b is
prompted. patched to
v2 and is
running off-
scan.

9 E1 becomes Cascade E1b

undeploy ed. Deploy P2 becomes
active, and
Note: Note: This its objects
Objects action results are running
under E1 in a brief on-scan.
show as downtime for
deployed, objects on Note: E1b
since the E1 and E1b does NOT
objects are as E1 start from
deployed on becomes the check-
redundant undeploy ed pointed state
partner (a few of non-
AppEngine seconds to a upgraded
E1b. few minut es, E1.
depending
on number of
objects).

66
Application Server Upgrade Wonderware System Platform Installation Guide

Node A Node B Node C

GR Primary AppEngine (E1) Backup AppEngine (E1b)
Platform 0 (P0) Platform 1 (P1) Platform 2 (P2)

Resulting Resulting Resulting

Step Action State Action State Action State

10 Upgrade; P1, its

shut down hosted
P1 and its engines and
engines objects
when remain
prompted. deployed but
are shut
down.

11 Reboot E1 is
when patched to
prompted v2 and is
running off-
scan.

12 Cascade E1 is No down-
deploy P1 deployed as time for
part of P1 objects on
deployment. E1b as E1b
continues to
E1 starts as
run as
standby and
active.
fully syncs
with active
engine.

N/A Final state Deployed. E1 Deployed E1b

– Standby. Deployed –
Active.

After you have upgraded to Wonderware System Platform 2017 UPDATE 1, you can enable
CPU load balancing to improve the performance of redundant AppEngines during failover.
See the Wonderware Application Server User’Guide, Working with Redundancy, for
additional information.
The following table describes the behaviors associated with specific upgrade actions and
states.

Action or State Behavior

Cascade deploy a Platform If the upgraded plat form hosts a backup redundant engine with
after upgrade a part ner 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.

67
Wonderware System Platform Installation Guide Application Server Upgrade

Action or State Behavior

Deploy a redundant engine The deploy operation is always a Cascade Deploy.

with a partner in the SUP
state.
Multi-selection for a cascade The cascade deploy operation skips the redundant engine in
deployment includes a SUP state and logs a message.
redundant engine with a
partner in S UP state
Select a backup redundant The backup redundant engine extracts the hosted objects from
partner engine for deployment the primary redundant engine and deploys them along with the
backup redundant engine.
The hosted objects are under the primary redundant engine on
a part ner 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.

Partner engine is deployed but Redundant engine deployment fails.

not reachable or not ready to
sync.
Partner engine has older The partner engine is detected and rec ognized as having an
software version. older soft ware version. It is automatically stopped and
unregistered.
Primary engine transitions into Active – Partner not Upgraded
redundancy status.
Primary and backup partners cannot sync, 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.

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 2017 UPDATE 1. 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.
68
Application Server Upgrade Wonderware System Platform Installation Guide

Do the following to rename a Galaxy for use in a multi-Galaxy environment. For more
information about creating and backing up galaxies, see "Getting Started with the IDE," and
"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 2017 UPDATE 1.
Your Galaxy can now be configured for use in a multi-Galaxy environment.

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.

69
 Wonderware System Platform Installation Guide

C HAPTER 5
InTouch HMI Requirements and
Prerequisites
You need to meet the requirements and prerequisites for Wonderware products.

In This Chapter
Installing OI Gateway and Upgrading from FS Gateway ................................................................. 71

Installing OI Gateway and Upgrading from FS Gateway

Operations Integration Gateway (OI Gateway) is automatically installed as an InTouch
component when InTouch is selected for installation. OI Gateway replaces Factory Suite (FS)
Gateway, which was supplied with prior versions of Wonderware System Platform. Like FS
Gateway, OI Gateway acts as a communications protocol converter, provides OPC
connectivity and also supports OPC UA connectivity. Default configurations for both OPC and
OPC UA are included.
See the Wonderware Operations Integration Gateway Help for information about connecting
to OPC and OPC UA servers, as well as for information about linking clients and data
sources that communicate using different protocols.
In addition to installing OI Gateway as part of installing InTouch, you can install OI Gateway
as a stand-alone application. There are three common installation scenarios:

"Clean" System without OI Older version of OI Gateway FS Gateway is installed

Gateway or FS Gateway is installed

71
Wonderware System Platform Installation Guide InTouch HMI Requirements and Prerequisites

"Clean" System without OI Older version of OI Gateway FS Gateway is installed

Gateway or FS Gateway is installed
OI Gateway is installed as part 1. The WSP installation 1. The WSP installation
of InTouch installation. program upgrades the program removes FS
existing OI Gateway Gateway, but saves the
version to the new version existing FS Gateway
and exits. configuration.
2. Restart the WSP 2017 Two instances of OI
UPDA TE 1 installation Gateway are installed. The
program after OI Gateway existing FS Gateway is
has been upgraded. This replaced by the second OI
installs the remaining WSP Gateway instance, whic h
components, including uses the existing FS
InTouch. Gateway application
name.
2. After the upgrade to WSP
2017 UP DA TE 1 is
complete, activat e the
instance that has replaced
FS Gateway.
There is no change in
behavior for InTouch us ers
that use the pre-existing
OPC access name.
See Compatibility with
Existing FS Gateway
Applications (see
"Compatibility wit h Existing
FS Gateway Applications"
on page 72).

Compatibility with Existing FS Gateway Applications

If you are upgrading from InTouch 2014 R2 SP1 where FSGateway has been installed, OI
Gateway will continue to maintain the FSGateway application name in the Access Name
definition. The application name is preserved to enhance compatibility with existing
applications.

72
InTouch HMI Requirements and Prerequisites Wonderware System Platform Installation Guide

 If you are upgrading from InTouch 2014 R2 SP1, FS Gateway will appear in the SMC
(System Management Console) under DAManager.

 After upgrading to InTouch 2017 UPDATE 1 from InTouch 2014 R2 SP1, two new
Gateway servers are installed. The first OI Gateway is installed under Operations
Integration Supervisory Servers as OI.GATEWAY.n. A second instance replaces the
existing FS Gateway instance, but preserves the existing configuration and name, even
though FS Gateway has been deleted and the new OI Gateway has been installed in its
place. Since the new gateway instance is in a deactivated state, you must activate it
(select the instance, right-click, and select "Activate Server").

73
Wonderware System Platform Installation Guide InTouch HMI Requirements and Prerequisites

Note that the component names are changed from "FSGateway" to "Gateway." This does
not affect references or change the behavior of the gateway.

74
 Wonderware System Platform Installation Guide

C HAPTER 6
Historian Server Requirements and
Recommendations
For your Wonderware Historian to achieve maximum performance, make sure your hardware
and software meets the following requirements. Because the Wonderware Historian is a high-
performance relational database, it is also important to size your system to handle the level of
data that you expect to store.
The Wonderware Historian is tightly integrated with Microsoft products, and a working
knowledge of both Microsoft SQL Server and Microsoft Windows operating systems is
required. For more information on Microsoft SQL Server or Windows operating systems, see
your Microsoft documentation.

In This Chapter
Server Requirements .................................................................................................................... 75
Requirements for Historian Management Tools .............................................................................. 78
Remote IDAS Requirements.......................................................................................................... 78
Disk Sizing and Data Storage ........................................................................................................ 79
Performance Considerations ......................................................................................................... 85
Networking Rec ommendations ...................................................................................................... 88
Client Access ............................................................................................................................... 89
Support for Non-English Operating Systems................................................................................... 90
Integration with Other Wonderware Products .................................................................................. 90
System Sizing Examples ............................................................................................................... 90

Server Requirements
The minimum hardware and software requirements for the Wonderware Historian are based
on the tag count and the anticipated data throughput rate. These requirements are divided
into four levels, which are outlined in this section.
The recommended memory configuration for SQL Server (32-bit) is to clamp memory
consumption to 50 percent of the amount of physical memory installed on the server or 512
MB, whichever is larger. For SQL Server Standard and Enterprise editions (32-bit), the
recommended physical memory configuration is 1 GB. The recommended Windows virtual
memory setting is twice the amount of physical RAM installed on the server. For installation
requirements for SQL Server versions, see the Microsoft documentation.

75
Wonderware System Platform Installation Guide Historian Server Requirements and Recommendations

You need to ensure that the memory that SQL Server reserves for the Wonderware Historian
is adequate for the expected load. Based on your particular environment, you may need to
adjust the SQL Server MemToLeave allocation. For more information on MemToLeave, see
the Microsoft documentation.
You can install the Wonderware Historian on operating systems that have the User Account
Control (UAC) turned on.
If you are running the Wonderware Historian on a virtual server, the historian must have an
adequate CPU, adequate network memory, and disk I/O resources at all times. Overloading
the virtual server leads to unpredictable behavior. See System Sizing Guidelines (see
"System Sizing Guidelines" on page 12) for general hardware requirements.
Operating Systems
Any supported operating system. See the Schneider Electric Global Customer Support (GCS)
Technology Matrix.
Microsoft SQL Server
For supported Microsoft SQL Server versions, see the Schneider Electric Global Customer
Support (GCS) Technology Matrix.
Disk Space
 300 MB of free disk space to install the Wonderware Historian
 Appropriate space for history block storage. For more information, see Disk Sizing and
Data Storage on page 79.
Level 1 Server - Hardware
A Level 1 server can handle a load of about 5,000 tags. For example, 2,600 analogs, 2,200
discretes, 300 strings, and 20 non-I/O Server (manual) tags.
When replicating to Wonderware Online, each Level 1 server can support up to 15,000 tags
and 5,000 values per second.
The requirements are:
 Processor:
o Minimum: P4 3.2 GHz CPU
o Recommended: dual-core CPU
 RAM:
o Minimum: 2 GB
o Recommended: 4 GB
 100 Mbps network interface card (NIC)
Level 2 Server - Hardware
A Level 2 server can handle a load of about 100,000 tags, with 50% analog, 45% discrete,
and 5% string tags. The requirements are:
 Processor:
o Minimum: P4 3.0 GHz dual CPU
o Recommended: quad-core CPU

76
Historian Server Requirements and Recommendations Wonderware System Platform Installation Guide

 RAM:
o Minimum: 4 GB
o Recommended: 8 GB
 1 Gbps network interface card (NIC)
Level 3 Server - Hardware
A Level 3 server can handle a load of 150,000 tags, with 50% analog, 45% discrete, and 5%
string tags. The requirements are:
 Processor:
o Minimum: P4 2.7 GHz Xeon quad CPU
o Recommended: dual processor, quad-core CPUs
 RAM:
o Minimum: 6 GB
o Recommended: 12 GB
 1 Gbps network interface card
Level 4 Server - Hardware
A Level 4 server can handle a load of 2,000,000 tags, with 50% analog, 45% discrete, and
5% string tags. The requirements are:
 Processor:
o Recommended: two quad-core CPUs
 RAM:
o Minimum: 24 GB
o Recommended: 48GB
 1 Gbps network interface card
A performance report for different historian systems is provided in System Sizing Examples
on page 90.

High Availability Support

The Wonderware Historian provides built-in support for Stratus ft3500 fault-tolerant servers.
Other high availability features include:
 Tiering - using the "replication" functionality with a small "local" Historian on site that
replicates to two "tier 2" Historians.
 Virtualization - using HyperV or VMware high availability options with Historian running on
a virtual machine. For more information, see the Wonderware System Platform in a
Virtualized Environment Implementation Guide.
 Redundancy - the Application Server can send data to two Historians at once and
maintains independent store-and-forward channels to each.

77
Wonderware System Platform Installation Guide Historian Server Requirements and Recommendations

Requirements for Historian Management Tools

The management tools include the Wonderware Historian System Management Console and
the Wonderware Historian Database Export/Import Utility. If you are installing the tools on a
remote computer, the following requirements apply:
 Any supported operating system. See the Schneider Electric Global Customer Support
(GCS) Technology Matrix.
 Microsoft Management Console 2.0
 MDAC 2.7
 Any supported browser. See the Schneider Electric Global Customer Support (GCS)
Technology Matrix.
 20 MB of free disk space
Note: The Historian Data Importer is installed as part of the server installation.

Remote IDAS Requirements

A remote IDAS runs on all supported operating systems: domain member, stand-alone
workstation, or server.
To determine the CPU and memory needed for a remote IDAS, use the same guidelines of
the Wonderware Historian computer. For more information, see Server Requirements on
page 75.
The IDAS computer does not necessarily have to be as powerful as the server computer,
because it will not be performing all of the same functions (for example, processing SQL
Server transactions), but it should be powerful enough to handle the tag load that you expect.
The amount of free disk space required depends on whether or not you will have store-and-
forward enabled for the IDAS. If store-and-forward is enabled, you need to make sure that the
disk space on the remote IDAS computer is sufficient to store cached data if the network
connection to the historian fails. Estimate the disk space requirements for a remote IDAS as
that of the historian. For more information, see Disk Space Requirements for Historical Data
Files on page 81.
A remote IDAS configured for store-and-forward has more stringent requirements on memory
to ensure that the IDAS local storage engine has sufficient resources to run properly. In
general, estimate memory requirements for a remote IDAS configured for store-and-forward
the same as you would for a historian having the corresponding tag count.

Security Considerations for a Remote IDAS

If you set up a remote IDAS, you need to configure security settings that allow access
permissions between the remote IDAS and the Wonderware Historian. For example, the
historian needs to access the remote computer to start and stop the IDAS. Also, the remote
IDAS needs to access the historian computer to send data. These are administrative tasks,
which require administrative permissions.

78
Historian Server Requirements and Recommendations Wonderware System Platform Installation Guide

When you install the historian, you must specify an administrative user account under which
all of the historian services run. Make sure that this same user account is added to the
Administrators security group on the remote IDAS computer. The existence of the same
administrative user account on both the computers, allows the historian to access the remote
IDAS, and vice versa.
Note: A remote IDAS only requires the same administrative account to exist on the local
computer and the historian. It is not required for you to log on to the remote IDAS computer
using the administrator account.
If you change the Windows login using the System Management Console, after installing the
historian, make sure that the user account change is reflected on the remote IDAS computer.
If you are running the historian in a domain environment (recommended), you can create the
administrative user account on the domain controller and add the account to the
Administrators group on the historian computer and the remote IDAS computer. Do not create
a local user on any computer with the same name and/or password as the administrative user
account.
If you are running a remote IDAS in a workgroup environment, there is no centralized
management and authentication of user accounts (no domain controller). Create the same
administrative user account on each individual computer running a historian component. For
example, if you have a computer running the historian and plan to install remote IDASs on
two other computers, create the user account (that is, matching user names and passwords)
on all three computers.
For information on workgroups, domains, creating user accounts, and adding accounts to the
Administrators security group, see your Microsoft operating system documentation.

Disk Sizing and Data Storage

A number of storage-related questions must be answered when setting up the Wonderware
Historian. They include:
 How important is the data? Is it acceptable that four weeks of data is stored online and is
then over-written?
 How important is the configuration and event data? This type of information is stored in
the Microsoft SQL Server database.
 How often is data in the Microsoft SQL Server database changing?
 Is anyone in the organization going to require operating data that is older than a month?
Older than a year?
 How much is the SQL Server component of the historian expected to be used (for
example, for the event system)?
 How long can the system be off-line because of a component failure?
 What happens if the system stops storing data?
 What happens if stored data is lost because of a hard drive failure?
 Can the server equipment be taken off-line to perform repairs?
Ask yourself questions like these to help you determine disk space requirements and how
you should plan to protect your data.

79
Wonderware System Platform Installation Guide Historian Server Requirements and Recommendations

A performance report for different historian systems is provided in System Sizing Examples
on page 90.

General Hardware Recommendations for Storage

The following are the general recommendations for the hardware used for storage:
 SCSI drives configured using hardware RAID is optimum. The disk space required is a
function of data rate and the desired history duration.
 NTFS is the only officially supported file system for a production environment.

Planning for Disk Space Requirements

There are a number of factors to consider when estimating the amount of disk space required
to run the Wonderware Historian:
 Disk space required to install the required software components and files needed to run
the historian.
 Disk space required to store the historian database files.
 Disk space required to store the historian data files.
 If a remote IDAS is used, the disk space required on the local IDAS computer to store
cached data if the network connection to the historian fails.
 We recommend that you keep sufficient free disk space (around 20%) so that you can run
a disk defragmenting utility without negatively affecting the historian performance.
A performance report for different historian systems is provided in System Sizing Examples
on page 90.

Disk Requirements for Database Files

The Wonderware Historian installation program adds the Runtime and Holding databases to
the Microsoft SQL Server by default. If you choose to store events to SQL Server, the
A2ALMDB database is created.
Note: Historical plant data is not stored in the database files. This type of data is stored in
special files called history blocks.
 The Runtime database stores all historian configuration data and classic event data. The
information in the Runtime database is stored to disk as a database file named
RuntimeDat_116_<server_name>.mdf. Its associated log file is
RuntimeLog_116_<server_name>.ldf.
The configuration data in the database file remains relatively static and usually never
causes the file size to go above 20 MB. However, if you set up classic events, records of
event detections and the results of any data summaries or snapshots increase the size of
the Runtime database file because the tables are filling up. Also, entries are created in the
log file for event-related transactions. If the database files are set to auto-size, the
Runtime database file expands to accommodate event-related data until the hard drive is
full.
Note: In a 2,000,000 tag system, 2.5 GB of space should be preallocated for data files when
modification tracking is not used. When modification tracking is used, 20 GB should be
preallocated.

80
Historian Server Requirements and Recommendations Wonderware System Platform Installation Guide

 The Holding database temporarily stores tag definitions being imported from InTouch®
HMI software. The information in the Holding database is stored to a database file named
HoldingDat_116_<server_name>.mdf. Its associated log file is
HoldingLog_116_<server_name>.ldf.
 The A2ALMDB database stores alarm and event data. The information in the A2ALMDB
database is stored to a database file named A2LMDat_115_<server_name>.mdf. Its
associated log file is A2ALMDB_LOG.ldf.
The Runtime and Holding databases are set to automatically expand at a 10% rate (the
default).
You cannot change these defaults during the installation. The databases can be resized later
using Microsoft SQL Server utilities. For more information on sizing databases, see your
Microsoft SQL Server documentation for guidelines.
Note: If you are upgrading a previous version of the Wonderware Historian, the installation
program needs space to save a copy of the old Runtime database while it creates the new
one. To upgrade, the database space required is twice the size of the old database, plus the
database size for the new install.

Disk Space Requirements for Historical Data Files

The Wonderware Historian stores historical plant data to hard disk in special files called
history blocks. When you install the historian, you are required to specify a storage location
(directory) in which these files will be dynamically created and subsequently filled. You must
have at least 200 MB of free disk space for these files to install the historian.
After the historian is up and running, when the free space on the drive containing the storage
directory drops below a minimum threshold, the oldest data is overwritten. It is very important
that you allocate enough disk space to store your plant data for the desired length of time.
The amount of data that can be stored to disk before running out of space is dependent upon
the number of tag values that are stored and how often they are stored. That is, the more
tags you have, the fewer values you can store per tag before you need to archive off the
oldest data. Likewise, the higher the specified storage rate per tag, the faster the system runs
out of space.
Important: You must have sufficient disk space in the circular storage area to hold at least
two full history blocks, plus the space specified for the minimum threshold for the circular
storage area. Use the System Management Console to view or change the minimum
threshold value.
A performance report for different historian systems is provided in System Sizing Examples
on page 90.

Storage and Network Transmission Sizes for Tags

The following table lists the storage and network transmission sizes for various tag types.

Storage Engine - Network

Storage Engine - Storage Transmi ssi on Item Size
Tag Type Item Size (Bytes) (Byte s)

Analog - Integer 8 34

81
Wonderware System Platform Installation Guide Historian Server Requirements and Recommendations

Storage Engine - Network

Storage Engine - Storage Transmi ssi on Item Size
Tag Type Item Size (Bytes) (Byte s)

Analog - Floating Point 8 34

Analog - Double 12 38

Discrete 5 31

String 5+A vgStringLength (5+A vgStringLength)+26

Analog Summary 37 63

Discrete State Summary 40 66

Analog State Summary 28 * NumberOfStates (28*NumberOfStates)+26

String State Summary (28+A vgStringLength) * ((28+A vgSt ringLength) *

NumberOfStates NumberOfStates)+26

Alarm 325 6061

Acknowledgement 325 6066

E vent 300 5048

The storage size is used for estimating the space required for storage.
The network transmission size is used for calculating the network bandwidth required
between HCAL and the historian.
If you enable compression on the AppEngine from which events are originating, then the
network size is reduced by approximately 80%.
For alarms and events, the network transmission size assumes that the average name length
for each of the alarm properties is 20 characters.
The following table provides some sizing examples.

Storage Engine - Network

Storage Engine - Storage Transmi ssi on Item Size
Tag Type Item Size (Bytes) (Byte s)

String Tags (32 byte string) 5+32 = 37 (5+32)+26 = 63

State Summary for Analog (for 28*10 = 280 71*10 = 710

10 states)
State Summary for Discrete 20*2 = 40 68*2 = 136
(for 2 states)
State Summary for String (10 (1+32)*10 = 330 (69+32)*10 = 1010
states and 32 byte string)

82
Historian Server Requirements and Recommendations Wonderware System Platform Installation Guide

Note: Current space calculations are different than the calculations used by the classic
storage system.

Disk Space Estimation

This section provides guidance on how to determine the appropriate history block duration. A
history block duration can range from 1 hour to 24 hours, with a default of 24 hours.
For retrieval performance, it is better to have longer block durations. However, if the incoming
data rate is too high during a 24-hour period, the Original.dat file in which data collects may
grow so large that issues occur for history block management and other aspects of the
storage subsystem.
We recommend that you tune the history block duration so that the size of the Original.dat file
does not exceed 8 GB per history block.
You can estimate how many bytes this data rate generates in one hour by using the following
formula:
N kbps = (N / 8) bytes per second = (450 * N) bytes per hour
Where N is the transmission item size for the type of data that you are storing. For information
on calculating this number, see Storage and Network Transmission Sizes for Tags on page
81.
If you multiply this by the history block duration, you can get an estimate of the biggest data
file containing streamed and forwarded data, Original.dat.
If that estimate is larger than 8 GB, keep reducing the history block duration until the estimate
is under the 8 GB limit.

Bandwidth Estimation for Streaming Data

The network bandwidth required can be estimated by adding the data transmission rate for all
data types and the network overhead. Network overhead is approximately 4% of the total
transmission rate, assuming the data rate is above 1000 points/sec. The estimated bandwidth
would be the minimum bandwidth required for replication with reliable network (always
connected). However, if there are network disconnections/reconnections, using only the
minimum required bandwidth would make the "catch-up" process take a long time if possible.
It is recommended that you add a 30% safe margin to the estimated bandwidth to ensure that
the forwarding process can complete quickly if an unexpected network outage occurs.
The formula for estimated bandwidth is as follows:
BandwidthStreaming = 1.04 * 8 *  Each Tag Ty pe (Data Rate * Transmission Item Size)
BandwidthRecommendedStreaming = 1.3 * BandwidthStreaming
For example, with the following replication configuration:
1. Simple Replication - 798 4-byte analog tags changing every second.
2. Simple Replication - 815 discrete tags changing every second.
3. Simple Replication - 187 string tags (20 bytes string) every second.
4. 1 Minute Analog Summary - 800 tags
5. 1 Hour Analog Summary - 800 tags

83
Wonderware System Platform Installation Guide Historian Server Requirements and Recommendations

6. 1 Minute State Summary (Analog, 10 states) - 800 tags

7. 1 Hour State Summary (Analog, 10 states) - 800 tags
The average number of bytes transmitted every second for each of the above replication
types is as follows. For a table of transmission sizes, see Storage and Network Transmission
Sizes for Tags on page 81.
1. 798 * 34 = 27132 Bytes
2. 815 * 31 = 25265 Bytes
3. 187 * 52 = 9724 Bytes
4. 800 * 96 / 60 = 1280 Bytes
5. 800 * 96 / 3600 = 21 Bytes
6. 800 * 710 / 60 = 9467 Bytes
7. 800 * 710 / 3600 = 157.8 Bytes
BandwidthStreaming = 1.04 * 8 * (27132 + 25265 + 9724 + 1280 + 21 + 9467 + 158) = 608 Kbps
BandwidthRecommendedStreaming = 1.3 * 608 Kbps = 790 Kbps

Bandwidth Estimation for Store-and-Forward Data

If there is a network disconnection, HCAL sends data to local storage and later forwards the
data to the historian. After the forwarding process starts, HCAL will try to send as much as
data as possible with a large packet. The forwarding bandwidth is the bandwidth required to
stream the store-and-forward data.
The store-and-forward storage size is the same as for local historian storage. The following
table lists the average sizes used for bandwidth estimation used in this example.

Storage Item Size

Tag Type (Byte s)

Discrete Tags 5

Analog Tags (4 byte data) 8

String Tags (32 byte string) 37

Analog Summary (4 byte analog) 37

State Summary for Analog (for 10 states) 28 * 10 = 280

State Summary for Discrete (for 2 states) 20 * 2 = 40

State Summary for String (10 states and 32 byte string) (1 + 32) * 10 = 330

The forwarding bandwidths are calculated using the following formulas:

BandwidthForwa rding = 1.04 * 8 *  Each Tag Ty pe (Data Rate * Storage Item Size)
BandwidthRecommendedFor wardin g = 1.3 * BandwidthFor wardi ng

84
Historian Server Requirements and Recomm endations Wonderware System Platform Installation Guide

For this example, if all are stored in the local storage engine and forwarded later, the number
of bytes required for every second is as follows:
1. 798 * 8 = 6384 Bytes
2. 815 * 5 = 4075 Bytes
3. 187 * 25 = 4675 Bytes
4. 800 * 37 / 60 = 493 Bytes
5. 800 * 37 / 3600 = 8 Bytes
6. 800 * 280 / 60 = 3733 Bytes
7. 800 * 280 / 3600 = 62 Bytes
BandwidthForwa rding = 1.04 * 8 * (6384 + 4075 + 4675 + 493 + 8 + 3733 + 62) = 162 Kbps
BandwidthRecommendedFor wardin g = 1.3 * 162 Kbps = 211 Kbps

Time Estimation for Store-and-Forward Data

The actual time taken to forward store-and-forward snapshots depends on the amount of data
accumulated and the bandwidth limit. HCAL typically waits for about 30 second to attempt
forwarding process after reconnection. It may need to wait for a longer time if the historian is
busy.
To simplify the calculation, the following is assumed:
 HCAL can start forwarding immediately without interruption
 The bandwidth is 30% above the data rate before disconnection
The time taken to forward is as follows:
TimeForwarding = TimeInStoref orward * RatioFor wardi ngDataSize / 0.3
Where RatioForwardingDataSi ze = Forwarding data Size / Streaming data size
For example, the date rate is 1 Mbps and the bandwidth is 1.3 Mbps. Assume you have
simple replication for analog tags and store-and-forward data has been accumulating for 1
hour.
RatioForwar dingDataSi ze = 8 / 34 = 0.235
TimeForwarding = 60 (minutes) * 0.235 / 0.3 = 47 minutes

About Data Compression and the Buffer Age Limit

Bandwidth usage is reduced by about 80% if compression is enabled. This assumes that the
data rate is high enough to keep the buffer (64K) filled to have better compression ratio. For
analog tags, the data rate is roughly 2000 values/second.
When the data rate is low, enabling compression may not be effective. To fill the buffer with
low data rate, you can select the Wait to send incomplete packets option (BufferAgeLimit
attribute) for the AppEngine configuration. This attribute is not applicable to replication.

Performance Considerations
For a complete Wonderware Historian system, the following components put a demand on
memory.

85
Wonderware System Platform Installation Guide Historian Server Requirements and Recommendations

 Internal historian subsystems, such as the Configuration Manager, data acquisition, and
data storage
 The associated Microsoft SQL Server
 The operating system
 Client access (data retrieval), which includes caching
When determining the amount of memory to purchase, remember that adding more memory
is the cheapest and easiest thing that you can do to improve performance. Increasing the
amount of memory reduces the amount the server has to use virtual memory, thus lowering
the load on the storage subsystem. Even if you have a large amount of memory, additional
memory is used as additional disk cache, speeding up disk access and therefore file service.
Also, processes needed by the server become faster because they are memory-resident.
A major factor in system performance is the amount of plant data you anticipate storing in the
system, including considerations about how often that data is stored and retrieved. In general,
the more you store, the more often you store it, and the more you retrieve it, the slower the
system. The major storage factors affecting the performance of the system are:
 Effective analog flow rate (analog updates per second).
 Period of online data storage required.
 Effective discrete variable flow rate.
 Number of concurrent end users required.
 Complexity of end user queries.
 Number and size of string tags, as well as the effective flow rate of string values.
 Number and duration of string tag retrieval queries, as well as the frequency at which
these queries are executed.
A performance report for different historian systems is provided in System Sizing Examples
on page 90.

Server Loading
When a user connects to the Wonderware Historian with a client, configuration information is
immediately requested from the historian. This information includes the tags that the server
stores, their descriptions, engineering units, and other tag data. SQL Server reads this
information from the database (stored on disk) and places it in memory.
As the user selects time periods to trend, the historian reads data from files located on the
disk and prepares the results of the client's data request to be transmitted back to the client.
The ability of the server to quickly handle subsequent requests for data from the same client
and others is dependent on the server's ability to keep as much information in memory
without having to again access data from the disk.
As a higher load is placed for memory, a higher load is placed on the disk I/O system as the
server has to use disk caching and read from the data files.
The following table summarizes the loading for various systems.

86
Historian Server Requirements and Recommendations Wonderware System Platform Installation Guide

System Load Description

Acquisition and Base load of the historian. This load exists as long as the system is running.
storage However, this load is not affected by client activity.
Retrieval Variable loading caused by data ret rieval from client applications. When the
client initially connects, the data requested is configuration data, which is
stored in SQL Server. The historian requests data from SQL Server,
causing its loading to increase. As the client requests historical data, the
disk time increases as information from the data files is transferred to
memory. This continues as the client requests additional data. If the client
application requests data that has already been transferred to memory,
there is no associated disk activity and trans fer of data to memory.

The server must be able to adequately handle the variation on loading caused by the client
applications. To accomplish this, make sure that your hardware is sized so that it can handle
the base load created by the acquisition and storage systems and that there are adequate
resources still available for the retrieval system.

IDAS Performance
An IDAS can acquire an unlimited number of real-time data values, from an unlimited number
of I/O Servers, each with an unlimited number of topics. However, IDASs are subject to the
following limitations.
 The maximum sustained data throughput for any single IDAS is 30,000 items per second
for real-time data. For late or old data, the maximum throughput is 9,000 items per
second. The total combined throughput (real-time data plus late or old data) cannot
exceed 30,000 items per second. For higher-volume applications, you can set up multiple
IDASs to serve a single storage subsystem.
 The size of any data value is limited to 64,000 bytes.
 The maximum number of tags supported by any single IDAS is 30,000.

Tiered Historians
If you are installing a tiered historian, tier-1 nodes use the same basic configuration for the
number and types of tags and data collection rates.
The tier 1 configuration should be "delta" data collected and stored:
 12,000 analog tags every 2 seconds
 2,900 discrete tags every 2 seconds
 100 32-character string tags every 30 seconds
For the analog and discrete tags, the averages and value state aggregates are:
 6000 tags with an hourly calculation performed at the top of each hour
 6000 tags with 1-minute calculations performed at the top of each minute
plus
 1500 tags replicated (not aggregated) in tier 2
 1500 tags stored only in tier 1 (no aggregates or replication)
87
Wonderware System Platform Installation Guide Historian Server Requirements and Recommendations

Storage Subsystem Performance

The storage subsystem can support a continuous data acquisition rate of 150,000 updates
per second. The storage sub-system also supports a burst rate of 300,000 updates per
second up to 1 second.
The classic storage subsystem can support a continuous real-time data acquisition rate of
30,000 updates per second and a burst rate of 60,000 updates per second up to 1 second.
The storage subsystem processes all real-time data as a high-priority task that is never
interrupted. However, data received from "manual" methods (such as UPDATE/INSERT
commands, CSV file imports, or store-and-forward) is handled by a low priority task. If the
system is generally busy, then it may take some time for the manual data to be posted.

Networking Recommendations
The Wonderware Historian is a highly configurable package that can be set up in many
different ways depending on your needs.
The historian can use any protocol currently supported by Microsoft SQL Server 2012. You
can use the default Microsoft SQL Server 2012 protocol (named pipes) with TCP/IP. TCP/IP
is required if SuiteLink™ is used.
Do not use the historian computer as a domain controller.
It is highly recommended that you run the historian on a dedicated computer. For example,
running the historian on a mail server or an Internet server may impact performance.

88
Historian Server Requirements and Recommendations Wonderware System Platform Installation Guide

Generally, it is recommended that you split the process and IS networks to ensure that the
process network does not become overloaded. The following illustration shows one possible
network architecture where the historian is the link between the process network and the
business LAN/WAN

For this architecture, install two network cards on a server computer and configure them to
segment the IS network from the process network.
Note: All tags to be stored in historian are on "advise" all the time. This may cause heavy
load conditions on the process network. Before you install the historian, investigate the
possible load impact of installing the historian on your network.

Client Access
All clients should connect to the Wonderware Historian using the default Microsoft SQL
Server connection. Usually, this means using the name of the computer on which the
historian is running as the server name when logging on.
To change the default network protocol used by Microsoft SQL Server to something other
than named pipes, configure the client network access using the SQL Server Client Network
Utility. For more information, see your Microsoft SQL Server documentation.

89
Wonderware System Platform Installation Guide Historian Server Requirements and Recommendations

Support for Non-English Operating Systems

The English version of Wonderware Historian, the Wonderware Historian Database
Export/Import Utility, and the Historian Data Importer run on localized versions of all the
supporting operating systems for the following languages. Set the regional settings before
you install SQL Server. The corresponding version of Microsoft SQL Server for the required
language must be used.
 German
 French
 Japanese
 Simplified Chinese
The following entities are not supported in double-byte languages:
 Domain names, user names, and passwords (including SQL Server login names and
passwords).
 Names of I/O Server host machines, I/O Server application names, topic names, and item
names.
 Any text associated with licensing.

Integration with Other Wonderware Products

The Wonderware Historian is Wonderware's open relational database for plant and process
data. Many of the features of the historian allow it to be used with many of Wonderware's
other products.
The historian can store data from any application that supports SuiteLink™. Examples of
Wonderware applications that can send data to the historian are Wonderware Application
Server, I/O Servers, and InTouch® WindowViewer™.
Any client application that can retrieve information using SQL can retrieve data from
Wonderware Historian. For example, some Wonderware products that can retrieve data by
means of SQL queries are the InTouch HMI, Historian Client applications and controls,
Manufacturing Execution Module, and InBatch™ products. The historian further extends SQL
to improve the ability to handle time series data.
Also, Wonderware Historian I/O Server (aahIOSvrSvc.exe) is an interface for clients to
access current data values a historian by means of the SuiteLink protocol. The Wonderware
Historian I/O Server can update items with current values for given topics, providing "real-
time" I/O Server functionality.
Finally, you can use InTouch to configure the historian by importing tag definitions and I/O
Server definitions from the InTouch Tagname.x file into the Runtime database.

System Sizing Examples

To help you determine how to size your system, performance reports are provided for
different Wonderware Historian configurations.
Important: The information presented here is a guideline only. The actual results in your
environment may vary.

90
Historian Server Requirements and Recommendations Wonderware System Platform Installation Guide

Process Historian Sizing Examples

Performance reports are provided for various levels of a Historian.

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

Wonderware Historian Specifications
 DELL OptiPlex 755 with 2.4 GHz single processor quad-core CPU
 4 GB RAM
 512 MB Virtual Memory
 1 Gbps NIC
 Microsoft SQL Server 2008 SP3 Standard Edition
 SQL memory clamped @ 512 MB
 12-hour history block duration
Tag Information
Tag count (total) = 5,187
Analog tags = 2,607
Discrete tags = 2,285
String tags = 295
Manual tags = 17
Update rate of +/- 5,000 updates/second
Remote IDAS
None.
Event Information
 3 snapshot events, each having:
o 1 analog snapshot
o 1 discrete snapshot
o 1 string snapshot
 2 summary events, each having:
o 1 AVG calculation (1 tag every 8 hours)
o 1 MAX calculation (1 tag every 8 hours)
o 1 MIN calculation (1 tag every 8 hours)
o 1 SUM calculation (1 tag every 8 hours)
 1 SQL insert every 4 hours
 2 SQL multi-point updates every hour

91
Wonderware System Platform Installation Guide Historian Server Requirements and Recommendations

Query Load
For the following seven queries, each are occurring at different times in the hour:
 1 query (trend):
o live mode - 1 second update
o 1-hour duration
o 10 tags (7 analogs, 3 discretes)
 1 query: 1-hour range / hour (1 tag)
 4 queries: 15-minute range / hour (1 tag)
 1 query: 24-hour report every 24 hours (25 to 30 tags)
Performance Results
Category Value

A verage CP U load (%) 1.896

Wonderware Historian memory (Privat e Bytes) 714

consumption (MB)

Number of online history blocks 18

Uncompressed hard drive disk space per history block 1002

(MB)

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

Wonderware Historian Specifications
 DELL Precision WorkStation T5400 with four dual-core Intel Xeon 2.7 GHz CPUs
 4 GB RAM
 3072 MB Virtual Memory
 1 Gbps NIC
 Microsoft SQL Server 2008 SP3 Standard Edition
 SQL memory clamped @ 1024 MB
 4-hour history block duration
Tag Information
Tag count (total) = 63,000
Analog tags = 39,359
Discrete tags = 19,734
String tags = 295
Manual tags = 5,057

92
Historian Server Requirements and Recommendations Wonderware System Platform Installation Guide

Update rate of +/- 30,000 updates/second

Remote IDAS
One remote IDAS:
 P4 1.7 GHz
 1 GB RAM
 34,000 tags via the remote IDAS and the rest via the local IDAS
Note: Because this configuration was used for performance and stress testing, the remote
IDAS tag count is more than the recommended 30,000 maximum.

Event Information
 3 snapshot events, each having:
o 1 analog snapshot
o 1 discrete snapshot
o 1 string snapshot
 2 summary events, each having:
o 1 AVG calculation (1 tag every 8 hours)
o 1 MAX calculation (1 tag every 8 hours)
o 1 MIN calculation (1 tag every 8 hours)
o 1 SUM calculation (1 tag every 8 hours)
 1 SQL insert every 4 hours
 2 SQL multi-point updates every hour
Query Load
For the following seven queries, each are occurring at different times in the hour:
 1 query (trend):
o live mode - 1 second update
o 1- hour duration
o 10 tags (7 analogs, 3 discretes)
 1 query: 1-hour range / hour (1 tag)
 4 queries: 15-minute range / hour (1 tag)
 1 query: 24-hour report every 24 hours (25 to 30 tags)
Performance Results
Category Value

A verage CP U load (%) 5.38

93
Wonderware System Platform Installation Guide Historian Server Requirements and Recommendations

Category Value

Wonderware Historian memory (Privat e Bytes) 1174

consumption (MB)

Number of online history blocks 20

Uncompressed hard drive disk space per history block 4.12

(GB)

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

Wonderware Historian Specifications
 DELL PowerEdge 6800 with four dual-core Intel Xeon 3.4 GHz CPUs
 16 GB RAM
 4096 MB Virtual Memory
 1 Gbps NIC
 Microsoft SQL Server 2008 SP3 Standard Edition
 SQL memory clamped @ 3967 MB
 2-hour history block duration
Tag Information
Tag count (total) = 133,941
Analog tags = 73,600
Discrete tags = 53,560
String tags = 6920
Update rate of +/- 50,000 updates/second
MDAS
In the total tag count, 4009 tags originated from Wonderware Application Server.
Remote IDAS
Two remote IDASs:
 Remote IDAS 1: P4 1.9 GHz, 1 GB RAM
 Remote IDAS 2: P4 2.5 GHz, 512 MB RAM
44,370 tags via the remote IDAS 1
45,584 tags via the remote IDAS 2
44,383 tags via the local IDAS
Note: Because this configuration was used for performance and stress testing, the remote
IDAS tag counts are more than the recommended 30,000 maximum.

94
Historian Server Requirements and Recommendations Wonderware System Platform Installation Guide

Event Information
 3 snapshot events, each having:
o 1 analog snapshot
o 1 discrete snapshot
o 1 string snapshot
 2 summary events, each having:
o 1 AVG calculation (1 tag every 8 hours)
o 1 MAX calculation (1 tag every 8 hours)
o 1 MIN calculation (1 tag every 8 hours)
o 1 SUM calculation (1 tag every 8 hours)
 1 SQL insert every 4 hours
 2 SQL multi-point updates:
o 1 every 15 minutes
o 1 every 30 minutes
Query Load
For the following seven queries, each are occurring at different times in the hour:
 1 query (trend):
o live mode - 1 second update
o 15-minute duration
o 15 tags (10 analogs, 5 discretes)
 1 query: 1-hour range / hour (1 tag)
 4 queries: 15-minute range / hour (1 tag)
 1 query: 24-hour report every 24 hours (25 to 30 tags)
Performance Results
Category Value

A verage CP U load (%) 10

Wonderware Historian memory (Privat e Bytes) 360

consumption (MB)

Number of online history blocks 10

Uncompressed hard drive disk space per history block 1.81

(average GB)

95
Wonderware System Platform Installation Guide Historian Server Requirements and Recommendations

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

Wonderware Historian Specifications
 DELL PowerEdge T610 with Eight Dual-Core 2.67 GHz CPUs (Hyper Threaded)
 48 GB RAM
 48 GB Virtual Memory
 1 Gbps NIC
 Windows Server 2012 Data Center Edition
 Microsoft SQL Server 2012 SP1 Standard and Enterprise
 SQL memory clamped @ 4096 MB
 1-hour history block duration
Tag Information
Tag count (total) = 2,000,000
Analog tags = 1,000,000
Discrete tags = 900,000
String tags = 100,000
Update rate of +/- 150,000 updates/second
Query Load
The following query is occurring at different times in the hour:
 1 query (trend):
o live mode - 1 second update
o 15-minute duration
o 500 tags (250 analogs, 225 discretes, 25 strings)
Performance Results
Category Value

A verage CP U load (%) 26.444

Wonderware Historian memory (Privat e Bytes) 11,124

consumption (MB)

Number of online history blocks 246

Uncompressed hard drive disk space per history block 10.00

(average GB)

96
Historian Server Requirements and Recommendations Wonderware System Platform Installation Guide

SCADA (Tiered) Historian Sizing Examples

Performance reports are provided for various levels of a multiple Historian SCADA
configuration.

Topology 1: Centralized Tiered Historian Topology on a Slow/Intermittent

Network
This topology consists of ten tier-1 historians performing simple and summary replication of
the same tags independently to two tier-2 historians. This topology is targeted to reflect the
requirements of geographically distributed SCADA applications operat ing on slow and
intermittent networks.

The 400 Kbps data transfer limit reflects a typical data transfer speed between remote
locations over the Internet. The data transfer from each tier-1 historian to a tier-2 historian is
assumed to be through a dedicated 400 Kbps connection; multiple tier-1 historians do not
share the same 400 Kbps connection. It is assumed that the 400 Kbps is a bandwidth that
can be fully used.
Tier 2 Historian Specifications
 DELL PowerEdge 6800 with four dual-core Intel Xeon 3.4 GHz CPUs
 16 GB RAM with enabled PAE or 4 GB RAM
 Disk I/O subsystem of a 100MB/s throughput, 6 ms access time.
 100/1000 Base-T network card
 400 Kbps network connection (actual usable bandwidth)
Tier 1 Historian Specifications
 DELL Precision WorkStation T5400 with dual processor quad-core Intel Xeon 2.7 GHz
CPUs
 4 GB RAM
 Disk I/O subsystem of a 60MB/s throughput, 16 ms access time.

97
Wonderware System Platform Installation Guide Historian Server Requirements and Recommendations

 100/1000 Base-T network card

Loading Information
Assume that the total tag count on the tier-1 historian is 15,000.
The tier-1 historian receives 15,000 tags from I/O Servers of the following types and data
rates:
 12,000 4-byte analog delta tags changing every 2 seconds: (10,000 always fitting the real-
time window and 2,000 falling outside of the real-time window being 50 minutes late).
 2,800 1-byte discrete delta tags changing every 2 seconds
 200 variable-length string delta tags of 32-character length changing every 30-seconds
The tier-2 historian stores the following:
 6,000 tags with hourly analog summary calculations performed at the top of each hour
(using 6,000 4-byte analog tags as tier-1 tags)
 Another 6,000 tags with 1-minute analog summary calculations performed at the top of
each minute (using 6,000 4-byte analog tags as tier-1 tags)
 1,500 tags replicated (as simple replication) to tier-2 (using 1,400 1-byte discrete tags and
100 variable-length string delta tags as tier-1 tags)
 Another 1,500 tags only stored on tier-1 (using 1,400 1-byte discrete tags and 100
variable-length string delta tags as tier-1 tags)
Performance Results for the Tier-2 Historian
Category Value

A verage CP U load (%) (with no queries executing) 1%

Wonderware Historian memory (Virtual Bytes) consumption 3.05 GB

(GB)

Number of online history blocks 312

Uncompressed hard drive disk space per history block 888 MB

(average MB)

Latency Results
Category Value

Fastload (1 day fastload) 10.33 hours

Simple replication 4 seconds

Summary replication 4.6 seconds

Latency is the difference in time between when the value is received by the tier-1 historian
and when it is received by the tier-2 historian.

98
Historian Server Requirements and Recommendations Wonderware System Platform Installation Guide

Topology 2: Centralized Tiered Historian Topology for a Single Physical

Location
A 100 Mbps data transfer limit reflects a typical data transfer speed within one location, but
distributed over several buildings. In this case the 100 Mbps bandwidth is a physical
characteristic of the connection. It is assumed that up to 33% of that physical bandwidth c an
be used.

Tier-2 Historian Tier-2 Historian

100-Base T

Tier-1 Historians
(standard configurations)

Tier 2 Historian Specifications

 DELL PowerEdge 6800 with four dual-core Intel Xeon 3.4 GHz CPUs
 16 GB RAM with enabled PAE or 4 GB RAM
 Disk I/O subsystem of a 100MB/s throughput, 6 ms access time.
 100/1000 Base-T network card
 100 Kbps network connection (actual usable bandwidth)
Tier 1 Historian Specifications
 DELL Precision WorkStation T5400 with dual processor quad-core Intel Xeon 2.7 GHz
CPUs
 4 GB RAM
 Disk I/O subsystem of a 60MB/s throughput, 16 ms access time.
 100/1000Base-T network card
Loading Information
Assume that the total tag count on the tier-1 historian is 15,000.
The tier-1 historian receives 15,000 tags from I/O Servers of the following types and data
rates:
 12,000 4-byte analog delta tags changing every 2 seconds: (10,000 always fitting the real-
time window and 2,000 falling outside of the real-time window being 50 minutes late).
99
Wonderware System Platform Installation Guide Historian Server Requirements and Recommendations

 2,800 1-byte discrete delta tags changing every 2 seconds

 200 variable-length string delta tags of 32-character length changing every 30-seconds
The tier-2 historian stores the following:
 6,000 tags with hourly analog summary calculations performed at the top of each hour
(using 6,000 4-byte analog tags as tier-1 tags)
 Another 6,000 tags with 1-minute analog summary calculations performed at the top of
each minute (using 6,000 4-byte analog tags as tier-1 tags)
 1,500 tags replicated (as simple replication) to tier-2 (using 1,400 1-byte discrete tags and
100 variable-length string delta tags as tier-1 tags)
 Another 1,500 tags only stored on tier-1 (using 1,400 1-byte discrete tags and 100
variable-length string delta tags as tier-1 tags)
Performance Results for the Tier-2 Historian
Category Value

A verage CP U load (%) (with no queries executing) 1.55%

Wonderware Historian memory (Virtual Bytes) consumption 3.3 GB

(GB)

Number of online history blocks 312

Uncompressed hard drive disk space per history block 888 MB

(average MB)

Latency Results
Category Value

Fastload (1 day fastload) 9.92 hours

Simple replication 1.65 seconds

Summary replication 1.51 seconds

Latency is the difference in time between when the value is received by the tier-1 historian
and when it is received by the tier-2 historian.

100
Historian Server Requirements and Recommendations Wonderware System Platform Installation Guide

Topology 3: Simple Tiered Historian Topology for a Modem Configuration

In a modem configuration, the network bandwidth between the tier-1 and the tier-2 historians
is limited by 56 Kbps. Because the tag count and the replication data rate of the tier-1
historian should be very limited, it would be sufficient to consider only one tier-1 historian
performing simple replication to one tier-2 historian over a modem network.

Tier 2 Historian Specifications

 DELL Precision WorkStation T5400 with dual processor quad-core Intel Xeon 2.7 GHz
CPUs
 4 GB RAM
 Disk I/O subsystem of a 60MB/s throughput, 16 ms access time.
 100/1000Base-T network card
 56K modem
Tier 1 Historian Specifications
 OptiPlex 755 with single processor quad-core CPU 2.4 GHz
 4 GB RAM
 Disk I/O subsystem of a 60MB/s throughput, 16 ms access time.
 100/1000Base-T network card
 56K modem

101
Wonderware System Platform Installation Guide Historian Server Requirements and Recommendations

Loading Information
In the tier-1 historian modem configuration, the tier-1 historian receives 3,000 tags from I/O
Servers of the following types with average update rate 300 items per second:
 1,500 4-byte analog delta tags (1,400 always fitting the real-time window and 100 falling
outside of the real-time window being 50 minutes late)
 1,350 1-byte discrete delta tags
 150 variable-length string delta tags of 32 bytes each
Performance Results for the Tier-2 Historian
Category Value

A verage CP U load (%) (with no queries executing) 1%

Wonderware Historian memory (Virtual Bytes) consumption 1.86 GB

(GB)

Number of online history blocks 30

Uncompressed hard drive disk space per history block 43 MB

(average GB)

Latency Results
Category Value

Fastload (1 day fastload) n/a

Simple replication 5 seconds

Summary replication n/a

Latency is the difference in time between when the value is received by the tier-1 historian
and when it is received by the tier-2 historian.

102
 Wonderware System Platform Installation Guide

C HAPTER 7
Historian Server Installation and
Configuration
In This Chapter
Preparing for the Wonderware Historian Installation ...................................................................... 103
Microsoft SQL Server Installation ................................................................................................. 104
Wonderware Historian Installation Features .................................................................................. 105
About the Wonderware Historian Installation ................................................................................. 105
Testing the Installation ................................................................................................................ 106
Antivirus Software....................................................................................................................... 106
Wonderware Historian Menu Shortcuts ........................................................................................ 107
Repairing the Wonderware Historian ............................................................................................ 107
Modifying the Wonderware Historian Installation ........................................................................... 107
Uninstalling the Wonderware Historian ......................................................................................... 107
Upgrading from a Previous Version.............................................................................................. 107

Preparing for the Wonderware Historian Installation

A complete Wonderware Historian system consists of the following software components:
 Microsoft SQL Server
 Historian program files, database files, and history data files
 System Management Console, the configuration and control tool
 One or more local or remote IDASs (at least one must be defined)
 Wonderware Historian documentation.
You should have a definite plan for implementing the historian in your plant environment
before you start the installation process. This plan should include the type of network
architecture for the historian system, the amount of disk space required for data storage, and
the amount of space required for the historian database files and log files.
Also, any administrative security accounts that you specify for either the Microsoft SQL
Server or the historian should be accounts that do not change often, if ever. In particular, do
not change an administrative password during any part of the installation process.

103
Wonderware System Platform Installation Guide Historian Server Installation and Configuration

You must have administrative rights on the local computer to install the historian. The account
with which you log on to the computer must also be a sysadmin for the SQL Server or you
must be able to provide a sysadmin account for the SQL Server when prompted for it during
the installation. For SQL Server 2008, computer administrators are not automatically added
as SQL Server sysadmins by default.
The installation program detects any previous versions of the historian and notifies you of
your migration options.

Microsoft SQL Server Installation

You need to install and run the required version of Microsoft SQL Server before installing the
Wonderware Historian.
Configure the following Microsoft SQL Server options before installing the historian. If you
already have Microsoft SQL Server installed, you can run the Microsoft SQL Server setup
program to change these options. Microsoft SQL Server options should only be configured by
a qualified Windows or SQL Server administrator. For more information, see your Microsoft
SQL Server documentation.
 Microsoft Client Utilities must be installed.
 The historian must run with the Microsoft SQL Server default instance name (that is, the
computer name).
 During the Database Engine Configuration step of the SQL Server installation, make sure
to add the ArchestrA User Account and/or the local Administrators group as authorized
users.
 Remote Microsoft SQL Servers are not supported by the historian.
 For networking support, use named pipes and any other support required at your site.
However, you must select at least named pipes and TCP/IP sockets (the defaults). It is
highly recommended that you do not modify the default configuration for named pipes and
TCP/IP sockets.
 As you select the path to the data files, you must consider that the historian Runtime
database will grow, especially if you are going to use the event subsystem (including
summaries) or storing data in the ManualAnalog, ManualDiscrete, or ManualString tables.
 The Microsoft SQL Server services should be installed using the local system account.
The account you specify should be an account that does not change often, if ever.
 For obvious security reasons, you should not use a blank password for Microsoft SQL
Server.
 Both case-sensitive and case-insensitive SQL Servers are supported. However, you
should avoid mixing case-sensitive collations in tiered historian topologies.
 The SQL Server e-mail functionality requires a Windows domain user account. You can
change the service account after SQL Server is installed. However, it is highly
recommended that you use an account for which the password does not change often.
For more information on SQL Server e-mail, see your Microsoft SQL Server
documentation.

104
Historian Server Installation and Configuration Wonderware System Platform Installation Guide

Wonderware Historian Installation Features

The Wonderware Historian installation program allows you to install some of the features of
the system separately. The following table describes the various historian features that can
be installed. The online help is installed with all the features.
For information on hardware and software requirements for installing any of these features,
see the Wonderware Historian Readme file..

Feature Description

Wonderware This option installs or re-installs the historian, configuration tools and
Historian selected subcomponents.

IDAS An IDAS, which can be used remotely. The IDAS is always installed if you
select to install a complete historian.
Configuration Tools The server management tools include Wonderware Historian Configuration
Editor and Wonderware Historian Management Console. Both of these
applications are MMC snap-ins that are contained in the System
Management Console. These tools are always installed on the same
computer as the historian and can also be installed on a different computer
on the network. The Wonderware Historian Database Export/Import Utility
is also an installed configuration tool.

ActiveE vent ActiveE vent is an ActiveX cont rol that allows you to notify the historian
classic event system when an event has occurred in another application,
such as InTouch HMI software.
InSight Client Wonderware Historian InSight is a browser client included with
Wonderware Historian. It is the on-premises version of Wonderware Online
InSight, and provides instant access to production and performance dat a.
Historian This option installs historian extensions for OData and SQL Server
Extensions Reporting Services (SSRS ).

About the Wonderware Historian Installation

The Wonderware Historian installation is performed in two phases. In the first phase, the
installation program performs the following operations:
 Deploys the common components, such as SuiteLink and the License Viewer, unless they
are already installed and validated.
 Locates the required version of a running Microsoft SQL Server on the local computer.
 Logs on to the installed Microsoft SQL Server using the account of the person who is
currently logged on. This account must be an administrative account on the local
computer.
 Checks for required disk space based on the features that you select.
 Creates the historian directories on the hard disk, installs program files for the selected
features, and registers components. For more information, see Wonderware Historian
Installation Features on page 105.
105
Wonderware System Platform Installation Guide Historian Server Installation and Configuration

 Populates the historian program or startup group with icons.

The Database Configuration Utility automatically runs after the historian program file
installation is complete. This utility:
 Creates and/or configures the required databases.
 Creates the directory for the history data files (history blocks).
To install the Wonderware Historian for use in a tiered historian environment, install the
Wonderware Historian on the individual computers, then implement them as described in the
"Managing and Configuring Replication" chapter of the Wonderware Historian Administration
Guide.
Use the Wonderware System Platform installation program to install the entire system or any
of the features. It is assumed that you are familiar with the installation options. The installation
program does not log any errors that may occur.
You must have administrative rights on the local computer to install the historian. The account
with which you log on to the computer must also be a sysadmin for the SQL Server or you
must be able to provide a sysadmin account for the SQL Server when prompted for it during
the installation. For SQL Server 2008, computer administrators are not automatically added
as SQL Server sysadmins by default.
Important: Do not install Wonderware Historian on a computer named INSQL, because this
conflicts with the name of the Wonderware Historian OLE DB provider and the installation
eventually fails.
For detailed instructions on installing, see Wonderware System Platform Installation on page
9.
After the installation completes, configure the server using the instructions in Configuring
Databases and Data File Locations on page 35.
Refer to the Wonderware System Platform Readme before using the historian.

Testing the Installation

Test the Wonderware Historian installation to make sure that everything is installed correctly
and is working properly.
To test the installation
1. Start the historian.
2. Start the storage system and check that the system is receiving data from the system
tags.
After the historian is installed, no additional configuration is required to run client tools against
the server using named pipes. However, you may want to change the system or server
configuration using the System Management Console.

Antivirus Software
After installing the Wonderware Historian, configure your antivirus software to prevent archive
files from being scanned. Also, antivirus software should not scan files in certain folders. For
a list of folder exclusions, see the Wonderware System Platform Readme file.

106
Historian Server Installation and Configuration Wonderware System Platform Installation Guide

Wonderware Historian Menu Shortcuts

The following Start menu shortcuts are created in the Start\All
Programs\Wonderware\Wonderware Historian folder.
 Administration
 Configuration Export and Import
 Data Import
 InSight
In addition, the shortcut to the System Management Console appears in the Start\All
Programs\Wonderware folder.
Note: If you performed a complete historian installation, the System Management Console is
configured so that the local SQL Server is already registered. However, if you only installed
the client tools, the console is empty.

Repairing the Wonderware Historian

For a repair, the installation program automatically detects if you have an existing copy of the
Wonderware Historian on your computer and then reinstalls missing or corrupt program files,
registry keys, and shortcuts.
For detailed repair instructions, see Repairing an Installation on page 43.
To repair a database, use the Database Configurator. For more information, see Configuring
Databases and Data File Locations on page 35.

Modifying the Wonderware Historian Installation

You can modify the Wonderware Historian features that are already installed.
For detailed modification instructions, see Modifying an Installation on page 41.
To modify the disk directories for the database files and/or the history data files (history
blocks), use the Database Configurator. For more information, see Configuring Databases
and Data File Locations on page 35.

Uninstalling the Wonderware Historian

The uninstall program allows you to remove all the historian program files. The Runtime,
Holding, and A2ALMDB databases and the history blocks are not deleted.
During the uninstall, you have the option to delete the configuration files (idatacfg_*.dat)
created by IDAS and the Configuration Service.
For detailed uninstall instructions, see Uninstalling Wonderware System Platform on page 43.

Upgrading from a Previous Version

You can upgrade to Wonderware Historian 2017 from Wonderware Historian 2014 R2
(version 11.6.12100) SP1 (and applicable patches). No other versions are supported for
direct upgrades.

107
Wonderware System Platform Installation Guide Historian Server Installation and Configuration

You should upgrade the Historian Server before upgrading Wonderware Historian remote
IDAS nodes. Remote IDAS nodes that are not upgraded to 2017 will remain fully functional.
However, it is strongly recommended that you upgrade them to 2017 to incorporate minor
improvements and simplify further upgrades and maintenance.
If you have been using replication, when upgrading historian nodes, upgrade the tier-2
historian node first and then the tier-1 historian node.

About Database Migration

The data in an existing Runtime database can be migrated to a new Runtime database. The
old Runtime database is not deleted. Keep the old database until the Wonderware Historian
migration is validated.
Important: Back up the Runtime database before performing the migration.
There is no migration for the content of the Holding database, because this database is used
only to temporarily hold data when importing an InTouch data dictionary.
Any configuration data associated with obsolete system tags is not migrated.
For the event subsystem, all SQL-based detectors and actions are migrated to the OLE DB
syntax. If you have any custom SQL-based detectors or actions, you need to rewrite them
using the OLE DB syntax.
History data that is stored in SQL Server tables (not history blocks) can be migrated after the
general upgrade has been performed.
The scripts are created when you first run the database setup utility so that you can run them
at any time. The file path is:
\ProgramData\ArchestrA\Historian\Install\Scripts

Upgrading the Wonderware Historian Version

Refer to Upgrading from a Previous Version on page 107 to see which versions can be
directly upgraded to Wonderware Historian 2017.
The existing Runtime and A2ALMDB databases are automatically migrated to during the
installation, preserving all existing settings and tag configuration.
History blocks created using a previous version of Wonderware Historian do not require any
migration and can be copied to and used with Wonderware Historian 2017 as long as the
tags they contain are present in the Runtime database.
To upgrade Wonderware Historian
1. Back up the Runtime database.
2. Shut down and disable the Wonderware Historian using the Management Console. Any
remote IDAS nodes will go into store-and-forward mode.
3. Run the Wonderware System Platform installation program to perform the upgrade. For
more information, see Upgrading Wonderware System Platform on page 45.
4. The installation program detects the previous version of the Runtime database and
prompts you to keep the existing database or recreate the new database.

108
Historian Server Installation and Configuration Wonderware System Platform Installation Guide

5. If you re-create the database, existing Runtime database will not be re-named but will be
overwritten with a new Runtime database. If you do not re-create the database, the
existing database will remain intact.
6. Finish the installation of Wonderware Historian.
7. Restart the computer.
8. Start the Historian. The Historian will start acquiring and storing the store-and-forward
data from the existing remote IDASs.
9. After the Historian Server node is upgraded, you can upgrade any remote IDAS nodes.

Migration of History Data Stored in SQL Server

The normal SQL Server tables in the Runtime database contain configuration data and
certain types of history data. History data that is stored in the normal SQL Server tables
includes:
 Data in the AnalogManualHistory, DiscreteManualHistory, and StringHistory tables.
 Classic event and summary data, which is stored in the EventHistory, SummaryHistory,
SummaryData, AnalogSnapshot, DiscreteSnapshot, and StringSnapshot tables.
These tables can contain hundreds of thousands of rows, if not millions of rows. Depending of
the amount of data to be migrated, migrating this data can take a few minutes to many hours,
and in some cases, days.
Important: You MUST perform the database migration before the server goes back into
production, because the history table content will be truncated. Be sure that you have disk
space equivalent to two times the size of the Runtime database on the drive to which the
history data will be migrated; otherwise, the migration may fail. Back up the Runtime
database with the migrated configuration data before migrating the history data.

109
 Wonderware System Platform Installation Guide

C HAPTER 8
Historian Client Requirements
In This Chapter
About Wonderware Historian Client.............................................................................................. 111
Wonderware Historian Client Components ................................................................................... 111
Requirements and Recommendations .......................................................................................... 112
Support for Operating System Language Versions ........................................................................ 112

About Wonderware Historian Client

You can use the Wonderware Historian Client software to address specific data
representation and analysis requirements. The Wonderware Historian Client software
maximizes the value of the data present in the Wonderware Historian and helps you
organize, explore, analyze, present, and distribute process data in a variety of formats.
With the Wonderware Historian Client software, you can:
 Explore data graphically to find important information
 Analyze data
 Develop and execute ad hoc queries against any data stored in the Wonderware Historian
database
 Visualize the current process state

Wonderware Historian Client Components

The Wonderware Historian Client software comprises of tools that eliminate the need to be
familiar with the SQL and provides intuitive point-and-click interfaces to access, analyze, and
graph both current and historically acquired time-series data.

Desktop Applications
The Wonderware Historian Client software includes the following stand-alone applications:
Wonderware Historian Client Trend
 Allows plotting of historical and recent data over time
 Allows you to compare data over different time periods
Wonderware Historian Client Query
 Allows you to query the Wonderware Historian database
 Provides complex, built-in queries
 Eliminates the need to be familiar with the database structure or SQL

111
Wonderware System Platform Installation Guide Historian Client Requirements

Microsoft Office Add-Ins

The Wonderware Historian Client software includes the following add-ins for Microsoft Excel
and Microsoft Word. The add-ins support only 32-bit versions of these applications.
Wonderware Historian Client Workbook
 Allows display and analysis of historical and recent data from a Wonderware Historian
database using the Excel spreadsheet format
Wonderware Historian Client Report
 Allows advanced reporting of historical and recent data from a Wonderware Historian
database using the Word document format

ActiveX and .NET Controls

The aaHistClientTrend and aaHistClientQuery controls provide essential functionality of
Wonderware Historian Client Trend and Wonderware Historian Client Query. You can use
these controls in container applications, such as InTouch® HMI software, Visual Studio
(Visual Basic .NET or C#), and Internet Explorer. You can also use Wonderware Historian
Client "building block" controls (such as aaHistClientTagPicker,
aaHistClientTimeRangePicker, and so on) in your custom applications.

Requirements and Recommendations

You must log on to the computer as an administrator to install the Wonderware Historian
Client software. Be sure that you read the hardware and software requirements in the
Wonderware System Platform Readme before starting the installation.

Support for Operating System Language Versions

The English version of the Wonderware Historian Client software runs on the following
operating system language versions:
 English
 French
 German
 Japanese
 Simplified Chinese
Note: The SQL Server locale language must be the same as the operating system locale
language.

112
 Wonderware System Platform Installation Guide

C HAPTER 9
Historian Client Installation and
Configuration
The Wonderware System Platform installation program allows you to install the Wonderware
Historian Client software. The Wonderware System Platform installation program copies the
files from the setup DVD to the target computer.
For more information on the components installed, see Wonderware Historian Client
Components on page 111.

In This Chapter
About the Wonderware Historian Client Installation ....................................................................... 113
Using Wonderware Historian Client Soft ware with Roaming P rofiles .............................................. 114
Repairing the Wonderware Historian Client Installation .................................................................. 114
Uninstalling Wonderware Historian Client ..................................................................................... 114
Upgrading from a Previous Version.............................................................................................. 114

About the Wonderware Historian Client Installation

Before installing the Wonderware Historian Client software, log on to the computer as an
administrator. Before copying the software files, the Wonderware System Platform installation
program checks for the basic system prerequisites.
You can individually select or deselect features of Historian Client for installation. These are:
 Trend/Query Clients: This feature lets you view and analyze data and trends.
 Microsoft Office (32-bit) Add-ins: This feature installs Historian Client add-ins for Microsoft
Word and Excel. You must have a 32-bit version of these programs installed.
 PDF Documents
The Wonderware System Platform installation program checks if a Microsoft Excel process is
running. If Excel is running, a message appears informing you that an Excel process and the
aaHistClientReportingService.exe service are running.
To continue with the installation, you need to manually stop the services and click Retry.
Click Close if you want to stop the installation.
Note: In some cases, depending upon the operating system and the prerequisite, you may
have to restart the system after the prerequisites are installed. In such cases, the setup
automatically continues after the restart.
For instructions on installing the Wonderware Historian Client software files, see Installing the
Wonderware System Platform on page 24.

113
Wonderware System Platform Installation Guide Historian Client Installation and Configuration

After the Wonderware Historian Client software is installed on the computer, you must install
the Language Packs manually.

Using Wonderware Historian Client Software with Roaming

Profiles
If your network environment uses roaming user profiles, you must change a registry key so
that changes to any Wonderware Historian Client software options are saved in the user
profiles.
To save software options in the roaming user's profile, add a DWORD key named
"EnableRoaming" to the user's HKEY_CURRENT_USER\Software\ArchestrA
\ActiveFactory registry folder and change its value to 1.

Repairing the Wonderware Historian Client Installation

You can use the Wonderware System Platform installation program to repair corrupt files of
the installed features. For more information, see Repairing an Installation on page 43.
Note: You can also use the standard Windows Add/Remove Programs feature from the
Control Panel to repair the Wonderware Historian Client software installation.

Uninstalling Wonderware Historian Client

You can use the Wonderware System Platform installation program to remove Wonderware
Historian Client software that exists on your computer. For more information, see Uninstalling
Wonderware System Platform on page 43.
Note: You can also use the standard Windows Add/Remove Programs feature from the
Control Panel to remove the Wonderware Historian Client software installation.

Upgrading from a Previous Version

You can upgrade to Wonderware Historian 2017 Update 1 from Wonderware Historian 2014
R2 (version 11.6.12100) SP1 (and applicable patches).
You should upgrade the Historian Server before upgrading Wonderware Historian remote
IDAS nodes. Remote IDAS nodes that are not upgraded to 2017 will remain fully functional.
However, it is strongly recommended that you upgrade them to 2017 to incorporate minor
improvements and simplify further upgrades and maintenance.
If you have been using replication, when upgrading historian nodes, upgrade the tier-2
historian node first and then the tier-1 historian node.
Upgrading From a Version Earlier Than Wonderware Historian 2014 R2
You must make some changes manually if you need to upgrade from a version of
Wonderware Historian prior to version 2014 R2. When you run the Configurator, it generates
SQL scripts that you can use for manually migrating older releases.
To upgrade from an earlier version of Historian (before v.2017 R2)
1. Install Wonderware Historian 2017 and run Configurator.
2. From the System Management Console, shutdown and disable Historian.

114
Historian Client Installation and Configuration Wonderware System Platform Installation Guide

3. Locate SQL scripts that you'll need for intermediate migration in this folder:
C:\ProgramData\ArchestrA\Historian\Install\Scripts
4. From SQL Server Management Studio:
a. Drop the Runtime database.
b. Restore a backup of the Runtime from your previous version of Historian.
5. Disable any triggers or constraints that would prevent schema changes. This prepares
your database for changes.
6. Run the scripts you need to update Historian 2017.
If you are upgrading from a much older version, you may have to run scripts to
incrementally upgrade versions.Run the scripts in the order they appear (when sorted
alphanumerically).
7. Restore any changes (triggers and other constraints) that you made to settings in step #5.
8. Shut down the old server's remote IDAS.
9. From the new server, force an update to the remote IDAS configuration.

115
 Wonderware System Platform Installation Guide

A PPENDIX A
Using Silent Installation
Wonderware System Platform supports silent (command line) installation. This feature
enables you to install Wonderware System Platform products without user interaction.
Important: If prerequisite software is required for the Wonderware System Platform
products you are installing, all prerequisites must be installed before starting silent
installation.
Prerequisite software includes .NET Framework and SQL Server. Details about prerequisite
software is provided in Wonderware System Platform Prerequisites on page 15. See SQL
Server Requirements on page 53 for additional information about supported versions of SQL
Server.
Setup.exe is run from the command line and accepts as an argument the name and path of a
response file containing pre-scripted responses to Wonderware System Platform installation
prompts.
Important: Use silent installation only to install a new system or upgrade an existing one.
Modifying a previously installed system, that is, adding or removing components at the same
release level, is not supported through silent installation. However, you can add components
as part of an upgrade to a higher release level. Removing components during an upgrade is
NOT supported.

In This Appendix
Starting Silent Installation ............................................................................................................ 117
Using Response Files ................................................................................................................. 118
Response File Samples .............................................................................................................. 119
Configuring the License Server .................................................................................................... 122

Starting Silent Installation

To run silent installation, open a command prompt using Run as administrator. The basic
syntax of the silent installation command consists of the full path to the setup.exe file
(typically the DVD drive designation on your local computer), the command line switch for
silent installation, and the full path to the response file.
Silent installation syntax:
<DVD>:\setup.exe /silent "<path\response-file-name>"
Note that the full filespec of the response file (filename plus location of file) must be included.
For example:
D:\setup.exe /silent "C:\docs\WSPInstall\response.txt"

117
Wonderware System Platform Installation Guide Using Silent Installation

The /silent switch completely disables the graphical user interface of Setup.exe. There is no
input from or feedback to the end user. However, the installation will output progress to a log
file. The log is usually found here:
C:\Program Files (x86)\Common Files\ArchestrA\Install\
{<FolderName>}\ILog<timestamp>.log
Silent installation with minimal GUI syntax:
D:\setup.exe /MINGUI <path\response-file-name>

Running setup with the /MINGUI switch will cause setup to install without any input from the
end user, but it will display the progress of the installation on screen.
Silent installation command-line help:
D:\setup.exe /?
Running setup with the /? switch will display the silent installation command-line help.

Using Response Files

Response files are plain text files. They specify which Wonderware System Platform
products, and even which features of a product that Setup.exe will install. For example, one
response file could be used to install the components for a run-time environment. A different
response file might be used to install the components for a development server.
Response files can install more than one product at a time, enabling you to install all the
necessary products for a given role.
Because the user will get little feedback on error conditions, it is necessary for the user to
perform the following checks before installing via command line:
1. Ensure that the operating system is a supported version with all of the correct service
packs.
2. Ensure that the SQL Server is a supported version.
3. Ensure that the user running the install has administrator rights.
Any issues that would stop a normal GUI-based installation, such as the presence of
incompatible software, will also prevent successful completion of a command-line installation.
Note: If the GUI installer would install any necessary prerequisites, the command line installer
will also install these items.
If another WSP product was previously installed, already creating the ArchestrA Network
User, subsequent installations will not create another ArchestrA Network User. The original
ArchestrA Network User will be retained.
For example, under those conditions, Setup.exe will ignore the following lines in the response
file:
AdminUserForm.SUserName=ArchestrAUser
AdminUserForm.SPassword=<password>
AdminUserForm.SCreateLocal=true
A good approach for testing is to first run the setup.exe in GUI mode on a typical computer
and confirm that no incompatibities exist that would stop the installation, then cancel and run
by command line.
Note: If the GUI-based installation requires a system reboot after the installation is complete,
installing by command line will also require a system reboot.

118
Using Silent Installation Wonderware System Platform Installation Guide

Response File Samples

The response file samples are provided as .txt files on the installation DVD within the
following directory path:
\InstallFiles\ResponseFiles\Samples\
These samples can be used as templates to initiate the installation of certain products or
features during the silent install process.
To use the response file samples as templates
1. In Notepad or a similar text editor, open the appropriate response .txt file from the
installation DVD. Refer to the Role-Based Response Files on page 119 or the Product-
Based Response Files on page 120 sections to determine the correct .txt file to use.
2. Edit the response file as necessary.
a. Edit the UserName, Password and CreateLocal (true or false) responses. The
templates contain sample responses on these lines. Delete the sample responses,
located to the right of the equal sign (=), and replace with your own response.
b. If you install Historian components, provide the SQL Server user name and password.
3. Save the file to a directory on your local computer. Note the path and full name of the file.
4. From the command line, type the install command and provide the path and filename of
the response file you want to use.
Example: D:\setup.exe /silent c:\Documents\DevNode.txt.
In this example, the setup.exe file is in the root directory of the DVD, and the development
node response file is on the local C: drive in the specified directory.
5. Press Enter to start the specified installation.

Role-Based Response Files

The following response files install Wonderware System Platform products to perform the
functions of specific roles.

Response File Description

Historian Client Node.txt Installs the components required to connect to an existing Historian
Server, analyze the dat a, and provide ArchestrA object server run-
time components. Components include:
 Bootstrap
 Historian Client
Historian Server Node.txt Installs the components required to host a Historian server, analyze
the data with a Historian Client, and provide ArchestrA object
server run-time components. Components include:
 Bootstrap
 Historian Server with IDAS, configuration tools and extensions
 Historian InSight
 InTouch Alarm DB Logger

119
Wonderware System Platform Installation Guide Using Silent Installation

Response File Description

Remote System Platform Installs the components required to connect to an existing

Development Client.txt development server in order to develop and test InTouch and
Wonderware System Platform applications. Components include:
 Bootstrap
 Application Server IDE
 Galaxy Repository
 InTouch Runtime and Development
 InTouch Demo A pplications
 Documentation set for A pplication Server and InTouch
 Recipe Manager
 Historian Client
Runtime Client.txt Installs the components required to run InTouc h HMI, the Historian
client, and ArchestrA object server run time. Components include:
 Bootstrap
 InTouch Runtime
 InTouch Alarm DB Logger
 Recipe Manager
 Historian Client
System Platform Installs the components required to host the development server, in
Development Server.txt order to develop and test InTouch and Wonderware System
Platform applications. Components include:
 Bootstrap
 Application Server IDE
 Galaxy Repository
 InTouch Development and Runtime
 InTouch Alarm DB Logger
 Intouch Demo Applic ations
 Recipe Manager
 Historian Client

Product-Based Response Files

The following response files install the selected product or products of Wonderware System
Platform.

120
Using Silent Installation Wonderware System Platform Installation Guide

Response File Description

All.txt Installs every product of the Wonderware System Platform, except

InTouch Access Anywhere Secure Gat eway. The Secure Gateway
must be installed as a standalone product.
Application Server Installs the development components for Wonderware Application
Development.txt Server, including:
 ArchestrA Data Store
 Bootstrap
 Application Server IDE
Application Server Galaxy Installs the components required to run Wonderware Application
Repository.txt Server as a Galaxy Repository, including:
 ArchestrA Data Store
 Bootstrap
 Application Server IDE
 Galaxy Repository
Application Server Installs the run-time components for Wonderware Application
Runtime.txt Server, including:
 ArchestrA Data Store
 Bootstrap
Historian.txt Installs the components to run the Wonderware Historian, including:
 Historian Server with IDAS, configuration tools and extensions
 Historian InSight
 InTouch Alarm DB Logger
Historian Client.txt Installs the components required to run the Wonderware Historian
Client, including:
 Historian Client
InTouch Access Anywhere Installs the components to run InTouch and InTouch Access
and InTouch Runtime.txt Anywhere, including:
 ArchestrA Data Store
 Bootstrap
 InTouch Access Anywhere (lets you access InTouch
applications remotely through a web browser)
 InTouch Runtime
 Recipe Manager
InTouch Access Anywhere Installs the InTouch Access Anywhere Sec ure Gateway.
Secure Gateway.txt
 InTouch Any where Secure Gateway (for use in a DMZ to
provide remote access to InTouch applications )
Wonderware Application Installs all of the components for Wonderware Application Server,
Server.txt including:

121
Wonderware System Platform Installation Guide Using Silent Installation

Response File Description

 ArchestrA Data Store

 Bootstrap
 Application Server IDE
 Galaxy Repository
Wonderware InTouc h.txt Installs the components to run InTouch, including:
 ArchestrA Data Store
 Bootstrap
 Application Server IDE
 Galaxy Repository
 InTouch Development and Runtime
 Alarm DB Logger
 InTouch Demo A pplications

Configuring the License Server

You can configure licensing through the silent install process by using a response .txt file. To
configure the License Server, add the following entry to your .txt response file:
<configurator>
Schneider Electric Licensing.LicAPI2.NewServerName=SE_LICENSE_SERVER_NAME
Schneider Electric Licensing.LicAPI2.NewPortNumber=55555
</configurator>
Replace "SE_LICENSER_SERVER_NAME" with the name of your License Server. If you
need change the port number, replace the default entry "55555" with the new port number.

122
 Wonderware System Platform Installation Guide

A PPENDIX B
Single Product Installation
You can create an alternative installation media source if you are installing only Historian,
Historian Client, or the Application Server runtime, and you want to reduce network usage.
This alternative installation source will be much smaller than the full set of installation files,
and thus will be easier to send to remote locations. This is of particular value if your network
connection to the remote site is slow or unreliable, and any of the following, or similar
circumstances, apply:
 You have multiple nodes at a remote site on which you want to install only Historian,
Historian Client, or the Application Server runtime.
 A firewall at the remote site restricts most off-site access, and having a local copy of the
installation files is easier to manage than having to modify the firewall.
 Installing from a WAN-based share is impossible due to the speed or reliability of the
network connection.
With this procedure, you will:
1. Create a new installation source that contains a subset of the installation files contained
on the Wonderware System Platform installation DVD.
2. Install Historian, Historian Client, or the Application Server runtime from this subset of
files.
Copying the files, rather than installing from a remote location, eliminates the possibility of a
time-out during installation.

In This Appendix
Guidelines for Creating a Compact Installation Source .................................................................. 123
Preparation for Installing a Single Product .................................................................................... 124
Creating the Installation Source and Installing the Selected Component ......................................... 126

Guidelines for Creating a Compact Installation Source

Important: This process can only be used for installing Historian, Historian Client, or the
Application Server runtime. Other product configurations are not supported.
The workflow for creating the compact installation source is:
1. Copy the entire contents of the Wonderware System Platform installation DVD.
2. Delete language and product components that are not needed.
3. Copy the directory containing the remaining components to either:
 To the node where you will install the product.
 To a CD or DVD to be used as the installation disk.

123
Wonderware System Platform Installation Guide Single Product Installation

When you run the installation program, components that were deleted will show as disabled
(grayed-out) and unavailable for selection.

Upgrading from a Previous Version

Do not delete folders for products that are already installed. The upgrade process will not
complete if you do not upgrade all products previously installed on the node. For example, if
both Historian and Historian Client are installed on the node, you must upgrade both.

Preparation for Installing a Single Product

To install Historian, Historian Client, Application Server, or InTouch, you can choose not to
install or copy unnecessary files.
 The root directory contains a total of 11.5 MB. Two files in the root directory are absolutely
required: Autorun.inf (1 KB) and Setup.exe (1.7 MB). The remaining files are documents:
the Wonderware Installation Guide (3 MB), the Wonderware System Platform Virtual
Implementation Guide (3.5 MB), the Wonderware System Platform Getting Started Guide
(3.2 MB), and the Wonderware System Platform Readme (260 KB).
 The entire InstallITK folder (7 MB) is required.
 The following table shows which subfolders in the InstallFiles folder are required for
Historian, Historian Client, the Application Server runtime, and the NGX Visualization
runtime. You can delete folders that are not required for the product you are installing.
The size of the resulting set of folders is approximate and is provided for reference.
 There are about 16 files in the InstallFiles folder root, with a total size of about 6 MB.
Three of these are document files, which total about 5 MB. These files are not required for
installation (21_CFR_Part11_Deployment_Guide.pdf, ReadMe.html,
WSP_Install_Guide.chm).
The following table lists folders that can be deleted and that must be retained for each of the
product installations.
indicates that a folder can be deleted.
indicates that a folder must be retained.

InTouch
InstallFiles Folder Folder Size Hi storian Application (Run time only
(Component) (approx) Hi storian Client Server or run time and
development)

CD-ADS 6 MB

CD-ApplicationServer 1.5 GB

CD-ASBFramework 61 MB

CD-Gateway 50 MB

CD-Historian 491 MB

CD-HistorianClient 53 MB

CD-Intouch 671 MB Optional [select

124
Single Product Installation Wonderware System Platform Installation Guide

InTouch
InstallFiles Folder Folder Size Hi storian Application (Run time only
(Component) (approx) Hi storian Client Server or run time and
development)
language]

CD-IntouchFrench 721 MB Optional [select

language]
CD-IntouchGerman 592 MB Optional [select
language]
CD-Intouch Japanese 604 MB Optional [select
language]
CD-Intouch S Chinese 592 MB Optional [select
language]
CD-Language Assistant 102 MB Optional Optional

CD-LicAPI 56 MB

CD-Licensing 62 MB

CD-NGVisualization 171 MB

CD-OIEngine 62 MB

CD-OIGA TEWAY 16 MB

CD-Server 47 MB

External 3 MB

Redist 1.2 GB

The Redist folder contains SQL Server Express in subfolder SQL2014EXPRSP2. If you are installing Historian Client or the
Application Server runtime, or if you installing Historian and the target system already has a supported version of SQL
Server, you can remove the SQL Server Express subfolder. See SQL Server Requirements on page 53 for information about
supported versions of SQL Server.

 DOTNE T 67 MB Optional Optional Optional Optional

Note: If .NET version 4.5.1 or higher is already installed on the target system, you can remove the DOTNET folder from
Redist.

 MDAC 5 MB

 MSI4.5 6 MB

 PreReqInstaller 0 MB

 Safenet 8 MB

 SQL2014E XP RSP2 1.1 GB

 VC10SP 1 18 MB

125
Wonderware System Platform Installation Guide Single Product Installation

InTouch
InstallFiles Folder Folder Size Hi storian Application (Run time only
(Component) (approx) Hi storian Client Server or run time and
development)

 VC90SP 1 4 MB

 VC2012U4 13 MB

 VC2013U4 13 MB

ResponseFiles 0 MB

Support 0.2 MB

UpgradeSupport 38 MB

Note: The Redist folder contains SQL Server Express in folder SQL2014EXPRSP2. If you
the products you are installing do not need SQL Server, or if the target system already has a
supported version of SQL Server, you can remove the SQL Server Express subfolder. See
SQL Server Requirements on page 53 for information about supported versions of SQL
Server.

Optional Folder for Historian

The CD-InTouch folder contains a database purge utility that Historian uses (this utility is not
called when block-based event history is utilized). Without this folder, Historian cannot purge
the A2ALMDB alarm database and an error will be generated (this does not occur with block-
based history). If you are installing Historian Client only, this utility is not called and the folder
can be deleted without any issues.
Note: If you are installing Historian and the CD-Intouch has been deleted, you will not be able
to purge the A2ALMDB alarm database and an error will be generated (does not apply if you
are using block-based history). However, the installation will complete successfully.

Creating the Installation Source and Installing the Selected

Component
To create an installation source
1. Copy the entire contents of the Wonderware System Platform installation DVD to a local
folder on your computer or to a network share location.
This location will be used to prepare for the installation or upgrade of the product you are
installing.
Important: You must copy the entire DVD. The root directory from the DVD and all files in
it must be in place and completely intact.
2. Navigate to the location where you copied the DVD. Delete the files, components and
language folders that you do not need.

126
Single Product Installation Wonderware System Platform Installation Guide

Now you are ready to install or upgrade the product(s) using either of the methods
described below.
To install or upgrade a single product
Direct installation from the copy location (install locally or on a different network node):
1. Remove the original Wonderware installation DVD from the drive.
Important: When you run setup.exe, it checks for the Wonderware DVD. If the
Wonderware DVD is available, it will be used instead of the copy location.
2. Navigate to the copy location.
3. Make sure you have deleted the folders you do not need.
4. Run setup.exe. Components that were deleted will be grayed-out and unavailable for
installation.
5. If this is a new installation (not an upgrade), select the target location when you are
prompted.
Installation from a CD or DVD:
1. Create a CD or DVD from the copy location after deleting the folders you do not need.
2. Run setup.exe from the CD/DVD on each node. Components that were deleted will be
grayed-out and unavailable for installation.

127
 Wonderware System Platform Installation Guide

Index
configuring products • 32
1
16 Pen Trend • 23 D
database
A configuring • 33
A2ALMDB database • 75 disk space requirements • 75
aaAdministrators group • 47 disk sizing • 74
aaConfigSQL • 48 disk space
aaGalaxyOwner user account • 47 history blocks • 76
acquistion planning • 75
loading • 81
ActiveEvent • 98
ActiveX and .NET Controls • 104
E
Enhanced Security Mode • 48
aaHistClientQuery • 104
event data
aaHistClientTrend • 104
migrating from older versions • 102
Antivirus Software • 100
Application Server
hardware requirements • 56 F
fault-tolerant servers • 73
user account requirements • 22
ArchestrA user account
requirements for use with Application G
Server • 22 Galaxy database, migrating • 58
ASBService • 51 Galaxy Repository
ASBSolution • 51 upgrading • 57
upgrading with the Bootstrap • 55
B upgrading with the Bootstrap and IDE •
Bootstrap 55
upgrading • 55
building block controls H
aaHistClientTagPicker • 104 hardware recommendations
aaHistClientTimeRangePicker • 104 storage • 75
Historian Client • 103
C Historian Database Export/Import Utility
Change Network Account utlity • 47 requirements • 73
common components • 64, 99 history blocks
configuration utility • 33 disk space requirements • 76

129
Wonderware System Platform Installation Guide Index

history data Microsoft Client Utilities • 98

disk space requirements • 76 Microsoft SQL Server
migrating from older versions • 101 installation • 98
Holding database
disk space • 75 N
named pipes • 98
I network cards • 82
network protocol • 83
IDASs
networking • 82
installing • 98 NTFS • 75
performance • 81
requirements • 74 O
security • 74 operating system
IDE • 58
non-English • 84
upgrading • 58
upgrading • 56
upgrading with the Bootstrap and
Galaxy Repository • 55
InBatch • 84 P
installation • 98 performance • 80
about • 105 examples • 84
modifying • 39 IDASs • 81
repairing • 41 physical memory • 71
port
silent • 109
SQL Server • 53
SQL Server • 98
port, non-default
Wonderware Historian • 97
SQL Server • 53
Wonderware System Platform • 23 process network • 82
InTouch products
Window Viewer • 84 configuring • 32
protocols • 83
L recommendations • 82
LAN • 82
legacy mode • 48 R
legacy software • 64
RAID • 75
License Viewer • 99
repair • 106
licensing • 67
loading Wonderware Historian • 100
Wonderware Historian • 81 Wonderware Historian Client • 106
requirements • 56, 71, 104
disk space • 75
M
Historian Database Export/Import Utility
Management Console • 98
• 73
Manufacturing Execution Module • 84
memory requirements • 71, 80 IDASs • 74

130
Index Wonderware System Platform Installation Guide

System Management Console • 73 installing • 98

Wonderware Historian • 71 requirements • 73
reserved names
system • 51 T
response files • 110 TCP/IP • 82, 98
retrieval tiered historian
loading • 81 sizing • 90
roaming profiles • 106
Runtime database
disk space • 75
U
uninstall
migration • 101
Wonderware Historian Client • 106
Wonderware System Platform
S component • 41
SCSI • 75 upgrade
security
basic steps • 56
modes • 48
Galaxy Repository • 57
remote IDASs • 74
IDE • 58
silent installation • 109
software requirements • 56 operating system • 56
IDASs • 74 redundant pairs • 59
System Management Console • 73 run-time nodes • 59
Wonderware Historian • 71 SQL Server • 56
SPCPro • 23, 84
SQL Server V
incompatible version installed • 53 virtual memory • 71
SQL Server • 53, 56, 98
SQL Server language • 104 W
SQL Server, not found • 52 WAN • 82
SQL Server, untested version installed Wonderware Historian
• 53 components • 98
versions • 52 installation • 99
storage loading • 81
disk sizing • 74 memory requirements • 71, 80
hardware recommendations • 75 repair • 106
loading • 81 requirements • 71
SuiteLink • 82
upgrading • 106
summary data
Wonderware Historian Client Components
migrating from older versions • 102
components • 103
system
Query • 103
sizing • 84
System Management Console Report • 103
Trend • 103
131
Wonderware System Platform Installation Guide Index

Workbook • 103
Wonderware System Platform • 23

132