System Platform 2014 R2
Wonderware System Platform 2014 R2 Readme
Last revision: 11/20/2014
This document contains important information about Wonderware® System Platform 2014 R2, which includes the following products:
- Wonderware InTouch HMI 2014 R2 (v11.1)
- Wonderware Application Server 2014 R2 (v4.1)
- Wonderware Historian Server 2014 R2 (v11.6)
- Wonderware Historian Client 2014 R2 (v10.6)
- Wonderware Information Server 2014 R2 (v5.6)
Use the following links to navigate this Readme file:
- About This Release
- System Requirements and Guidelines
- Wonderware Product Compatibility
- Wonderware System Platform Installation
- Wonderware System Platform Upgrade and Migration
- Licensing Information
- Antivirus Information
- Resolved Issues
- Known Issues
Review each of the individual product Readme files for details regarding product-specific known and resolved issues. Insert the Wonderware System Platform installation DVD to access the following readme files.
- Wonderware InTouch HMI Readme
- Wonderware Application Server Readme
- Wonderware Historian Server Readme
- Wonderware Historian Client Readme
- Wonderware Information Server Readme
You can find readme files for previous product releases at Wonderware Developers Network (WDN) Downloads. Log in to WDN with your username and password to access the downloads archive.
Wonderware System Platform 2014 R2 - General Notes
Invensys License Manager
Invensys License Manager provides a unified solution for enterprise management of Invensys product licenses. The Invensys License Manager includes functionality to import, install, and manage licenses on local machines, license servers, and remote machines. With Invensys License Manager, you can associate licenses with individual nodes on the system to assure correct software usage, install and manage licenses on local and remote notes, and check the validity of licenses on your system.
Windows Operating Systems
Wonderware System Platform 2014 R2 component products support Windows 8 and Windows Server 2012 operating systems. The following Windows operating systems are no longer supported:
- Windows XP, all versions
- Windows Vista, all versions
- Windows Server 2003, all versions
- Windows Server 2008, non-R2 versions
SPCPro™ is a Statistical Process Control (SPC) utility formerly available with InTouch HMI. SPCPro is no longer supported by InTouch HMI. We recommend that if you use SPC and SPCPro with InTouch that you migrate your SPC Pro databases to the latest version of QI Analyst. QI Analyst provides support for the latest operating systems and DBMS versions, and provides a migration utility to move your SPCPro database to a QI Analyst database, leaving the existing SPC Pro database intact. Please contact your local Wonderware sales representative for further information.
Important Note: We strongly recommend that you migrate your current SPCPro databases to QI Analyst before installing Wonderware System Platform 2014 R2 with InTouch HMI. As of InTouch 2014, support for SPCPro is no longer included, and InTouch 2014 and newer versions will not open or migrate applications containing SPCPro components.
Wonderware InTouch HMI 2014 R2
ArchestrA Graphic Toolbox in WindowMaker
InTouch WindowMaker incorporates the ArchestrA Graphic Toolbox containing a full complement of ArchestrA symbols and Situational Awareness Library symbols. Adding a symbol to a Modern or managed InTouch application is a simple matter of dragging a symbol from WindowMaker's ArchestrA Graphic Toolbox and dropping it into an InTouch window.
Modern InTouch Applications
Modern InTouch applications give you the capability to easily integrate ArchestrA symbols directly into your applications. All steps to configure ArchestrA symbols for a Modern application are completed from InTouch WindowMaker. Modern applications combine the capability of integrated ArchestrA symbols in managed InTouch applications with the familiar workflow of legacy InTouch applications.
Conversion of InTouch Windows to ArchestrA Symbols
You can convert the windows of a managed InTouch application to ArchestrA symbols. The converted ArchestrA symbols appear in the WindowMaker ArchestrA Graphic Toolbox and the ArchestrA IDE Graphic Toolbox. In addition to graphics that appear in windows, all InTouch animation links embedded in windows are converted to the corresponding ArchestrA animation.
After conversion, the original converted InTouch window is backed up. A new InTouch window is created in the InTouch application, which embeds the newly created ArchestrA symbols.
Additional Situational Awareness Library Symbols
InTouch HMI 2014 introduced an extensive set of Situational Awareness Library symbols. InTouch 2014 R2 includes additional new Situational Awareness Library symbols for alarms, trends, and valves:
- SA_Alarm_Severity: Shows an alarm summary that includes Alarm Border animation and alarm counts by severity and acknowledgement status.
- SA_History_Alarm_Page: Provides a tabbed page to show historical events or alarms by severity over a specified period.
- SA_Runtime_Alarm_Banner: Shows alarms by area and includes buttons to acknowledge alarms.
- SA_Runtime_Alarm_Page: Provides a tabbed page to show current events or alarms by severity.
- SA_Trend: Shows a trend line of historical and current measured values and provides Wizard Options to show a grid that includes X and Y axes.
- SA_MultiTrend: Shows up to four simultaneous trend lines of current and historical measured values.
- SA_Valves: Shows a valve symbol with Wizard Options to select discrete or analog two way or three way valves.
A new Connector tool has been added to the Symbol Editor Tools menu. A connector is a line drawn between graphic elements. A connector starts at a connection point on one graphic element and ends at a connection point on another element.
Connectors are particularly useful for complex symbols containing many connected elements like flow diagrams, industrial piping, or electrical wiring. Connectors can change length or orientation in response to changes to the positions of connected graphic elements. Using connectors, graphic elements within a symbol can be moved, resized, or rotated and still maintain the connector between elements.
The boundary border around each graphic element includes eight connection points to attach a connector. The Tools menu includes a Connection Point tool to add custom connection points on a graphic element. Also, the Tool menu includes the Control Point tool to add control points on a connector to change its shape. The shape of a connector can be changed by dragging a line segment between control points to another position with your mouse.
Historical Statistical Summary Data
You can add a custom property and set the Data Type property to HistorySummary to reference historical data collected over a specified period during run time. The Historian can transform this data to create a set of analog or state statistics that can be shown by an ArchestrA graphic during run time in a script or a Value Display animation.
A custom property analog reference can subscribe to statistics from analog data saved to the Historian to show typical statistical values like average, counts, and standard deviation.
A custom property state reference can subscribe to statistics from analog data and saved to the Historian. Three types of historical state values are possible; Analog(Integer), String, and Null.
Alarm shelving enables operators to temporarily remove selected alarms from the list of active alarms. A shelved alarm is suppressed and removed from the list of active alarms for a specified period. After the period ends, alarms are automatically unshelved and appear again in the list of active alarms. Authorized users can also unshelve an alarm before the end of the specified period.
Alarm shelving has been incorporated into Alarm Border animation and the ArchestrA Alarm Control.
Alarm Border animation
When an operator shelves an alarm, Alarm Border animation remains around the symbol in a defined shelved visual style without blinking. The Alarm Border indicator icon shows the shelved alarm mode icon. In Alarm Border animation, suppressed and silenced alarm modes take precedence over an alarm in shelved mode.
ArchestrA Alarm Control
The ArchestrA Alarm Control includes a set of enhancements to support alarm shelving. The configuration dialog box includes a set of run-time options to shelve and unshelve alarms. Also, a set of properties and methods have been added to shelve and unshelve alarms with scripts.
Trend Pen Enhancements
InTouch 2014 introduced the Trend Pen control, which incorporates animation that shows a succession of process values as a trend line consisting of current and historical data. InTouch 2014 R2 includes additional new enhancements to the Trend Pen control.
A Trend Pen contains a collection of properties whose values can be modified during run time to change the visual and functional characteristics of a trend. The following properties can be modified in a script or User Input animation to change the following characteristics of a Trend Pen during run time:
Fixed and Line Trend Plots
The Trend Pen control now includes the Plot Type configuration option to show a trend line as either a Fixed or a Line plot. In Fixed mode, the trend line is plotted as a horizontal line from a trend data point to the time of the next data point on the trend's X-axis, and then the trend line is drawn as a vertical line to the data point. In Line mode, the trend line is plotted directly to each successive data point within the trend period.
Trend time Periods
The Trend Pen control now includes the Time Period configuration option to set the trend period as either Moving or Fixed. In a Moving trend period, the start time of a trend period is the current time. The end time is the duration of the time period from the start time. In a Fixed trend period, the StartTime and EndTime properties do not change automatically. The default start time of a trend period is the current time, but the StartTime property can be modified by a script to set a start time of a trend time period.
Enhancements to Programmatic Export and Import of ArchestrA Symbols
InTouch HMI 2014 introduced the ArchestrA GraphicAccess application programming interface (API) to programmatically export and import an ArchestrA symbol between the ArchestrA Graphic Toolbox and an XML file. InTouch HMI 2014 R2 enhances the capability of the ArchestrA GraphicAccess API to export and import symbols to include:
- Overridden text strings
- Numeric format styles
- DataStatus elements
- Trend Pen control
- Alarm Client control
- Trend Client control
Advanced Number Format Styles
The Configure Galaxy Style Library dialog box includes the Format Styles tab with options to individually configure Galaxy-wide number format styles for common types of numbers used in industrial applications. The Format Styles dialog box also includes fields to specify characters that appear during run time that indicate bad quality data or data that exceeds a fixed width field. Based on the selected number style, the fields appear on the Format Styles dialog box to change the default properties of number styles.
Each global number style is assigned a unique name, which cannot be changed. A number style can be applied by name in design time and run time for an analog data type in User Input and Value Display animations. Also, grouped elements support global number styles.
Remote Application Licensing Support
You can assign Read Only access to a distributed InTouch application running in a Remote Desktop Connection or Terminal Services session. Read Only access is appropriate for non-operators who need to view an application, but who should not have write permission. For example, managers need the capability to view an application on a mobile device with InTouch Access Anywhere over an unsecured public network. Using Read Only access provides better protection for distributed InTouch applications accessible from public networks.
Wonderware Application Server 2014 R2
Wonderware Application Server object editors have been streamlined for ease of adding features and attributes to objects. The functionalities of Field Attributes - both Discrete FAs and Analog FAs - have been combined with the functionalities of User Defined Attributes (UDAs) and attribute extensions to create unified, simplified attributes which you can create and configure using a new Attribute Editor in place of the traditional Field Attribute, UDAs, and Extensions tabs in each object editor. For information about using the Attribute Editor to create and modify attributes on objects, see the Wonderware Application Server User's Guide. For reference information specific to each Application Object, see the object help for each object. For reference information about Features and Attributes, see the "Attributes Help", available as a hyperlink from within each object help file.
I/O Auto Assignment
Viewing and configuring device integration for data access, manually or scripted, has long been labor-intensive and time-consuming. The I/O auto assignment feature now provides an automated means of assigning application objects to devices, and of specifying input sources and output destinations on attributes. Device Integration objects still must be configured manually, but the majority of objects and attributes in your galaxy can now be auto assigned to devices and I/O. A Device View pane in the IDE provides a hierarchical view of how your objects are assigned to devices and scan groups. You can use the Device View to drag and drop objects to assign them without checking out and checking in the objects. An I/O Device Mapping view provides a grid layout of your devices, scan groups, application objects, resulting references, and run-time values. The I/O Mapping View also allows you to override the auto assignment and to filter the visible information.
Wonderware Application Server provides a set of object and graphic attributes to shelve and unshelve alarms during run time. These attributes can be incorporated into run-time scripts or animation to manage the state of shelved alarms. Also, the ArchestrA Alarm Control now includes options to set run-time shortcut commands to shelve and unshelve alarms. The ArchestrA Alarm Control also includes a set of properties and methods to manage shelved alarms using scripting.
The ability to shelve an alarm is mapped to alarm severity. Typically, only moderate or low severity alarms should be shelved. In Wonderware Application Server 2014 R2, the Alarms and Events Configuration dialog box now includes options to map alarm shelving to alarm severity.
Export and Import Galaxy Style Library
The ArchestrA IDE includes options to export and Import the current ArchestrA Galaxy Style Library with its current assigned values. The exported Galaxy Style Library is saved as an XML file. Likewise, you import a Galaxy Style Library from an XML file, which overlays the existing Galaxy Style Library.
Upgrade Redundant AppEngine Pairs
You can reduce plant down time by upgrading the partners in a redundant AppEngine pair one at a time. Platforms hosting redundant AppEngine pairs can 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.
Plant State Alarms
You can map alarm modes on a per-Galaxy basis to different plant operational states to control how alarms are reported. Alarm Plant state mapping is done from the Alarms and Events Configuration dialog box of the ArchestrA IDE. Five plant states are pre-defined, and have default alarm states associated with them.
After you have defined plant state alarms for the Galaxy, you can assign plant state alarming to area objects in the Galaxy. This is done by setting a pair of attributes for each area object that will use plant state alarming.
During run time, you can change the Plant State and alarm modes using scripts and User Input animation.
Browse Attributes with the OPC UA Client Service
You can use an instance of the ArchestrA OPC UA Client Service hosted by your Galaxy to browse a Galaxy Namespace. You must prefix the item reference or attribute name with the OPC UA Client Service instance name defined in the OPC UA Client Service editor using the following syntax:
For example, TestServer:PLC01.PLCObject1
Wonderware Historian Server 2014 R2
- Alarms and events can now be integrated into block storage, or can continue to be stored in the SQL Server A2ALMDB database. When using block storage:
- Data management can be done using simple operations such as moving, copying, or deleting folders.
- Higher storage rates are available.
- Storage capacity is only limited by disk space, not by database insertion rates.
- You can retrieve alarm and event data using any browser through simple HTTP queries. You can also retrieve the data into an Excel spreadsheet.
- Network bandwidth efficiency has been greatly increased.
- History blocks are now created based on the timestamp of the data to be stored, not relative to the system time of the Historian Server.
- Easily use statistics calculated by the Wonderware Historian within ArchestrA Symbols through custom properties.
- Tag types have been expanded to include the double tag type.
- A new utility is available for importing history data in .csv and .lgh files.
- "Counter" retrieval more reliably estimates values when there are "resets" and communications outages.
- Easily mask communications outages for reports with expanded "optimistic" retrieval capabilities.
- A new utility is available for renaming tags in the Historian Server that you originally defined and then renamed using other sources, such as Application Server.
- You can create a Historian and Historian Client installation subset for easier distribution.
Wonderware Historian Client 2014 R2
- Wonderware Historian Client supports Windows 8.1 and Windows Server 2012 R2 operating systems, and .NET Framework 4.5.1.
- Wonderware Historian Client supports data retrieval from the managed Wonderware Online system. For more information, see the Wonderware Historian Client User Guide.
- SQLXML is no longer supported.
- The 64-bit versions of Microsoft Office 2010 and Office 2013 are incompatible and must be uninstalled prior to installing Wonderware Historian Client 2014 R2. The 32-bit versions of Office are compatible.
Wonderware Information Server 2014 R2
- Wonderware Information Server supports Windows 8.1 Professional and Windows Server 2012 R2 operating systems, .NET Framework 4.5.1, and security enhancements.
- Published ArchestrA Symbols can now interact with other web pages to allow for more complete applications.
- Published ArchestrA Symbols are faster and use updated Microsoft Silverlight components. Note: Previously published ArchestrA Symbols must be republished in order to still operate.
- The 64-bit versions of Microsoft Office 2010 and Office 2013 are incompatible and must be uninstalled prior to installing Wonderware Information Server 2014 R2. The 32-bit versions of Office are compatible.
- Hardware Guidelines
- Operating System, Firewall, .NET Framework, and Virtualization Requirements
- SQL Server Requirements
- Third-Party Application Prerequisites
The following table provides guidelines for hardware configurations suitable for Wonderware System Platform 2014 R2 software based on the size of the installation, applicable to both 32-bit and 64-bit systems. The Intel Itanium 2 processor is not supported.
(sufficient for 1 wk @ max
(1 - 500 I/O per Node)
(1 - 5K I/O per Node)
(5k - 50k I/O per Node)
(50k - 400k I/O per Node)
(64-bit OS and SQL)
Hardware Requirements Notes:
Windows operating systems and SQL Server versions may impose hardware requirements that exceed the minimum requirements for Wonderware Application Server 2014 R2. Refer to the following Microsoft Web sites for Windows and SQL Server hardware requirements:
- System Requirements and Installation Information for Windows Server 2012 R2
- Windows Server 2008 System Requirements
- Windows 8 and 8.1 System Requirements
- Windows 7 System Requirements
- Hardware and Software Requirements for Installing SQL Server 2014
- Hardware and Software Requirements for Installing SQL Server 2012
- Hardware and Software Requirements for Installing SQL Server 2008 R2
- Hardware and Software Requirements for Installing SQL Server 2008
Wonderware Historian Hardware Guidelines
- Wonderware Historian is not supported on cluster hardware.
- Do not use the Wonderware Historian computer as a domain controller.
- If you are running the Wonderware Historian on a virtual server, the Historian must have adequate CPU, network, memory, and disk I/O resources at all times. Overloading the virtual server leads to unpredictable behavior.
For system sizing examples, see the Wonderware System Platform Installation Guide.
Wonderware Historian Client Hardware Guidelines
|Single CPU- 2 GHz or more|
|Memory, RAM||512 MB||1 GB or more|
|Free hard drive space||55 MB||55 MB or more|
Wonderware Information Server Hardware Requirements
|CPU||2.5 GHz Pentium 4||3.0 GHz Pentium 4|
|Memory||2 GB RAM||Greater than 2 GB RAM|
|Free hard drive space||10 GB of free disk space||20 GB or more of free disk space, depending on the number of InTouch HMI windows, ArchestrA Symbols, ActiveFactory Reports and ArchestrA Reports published to the site.|
Alternative Authentication Using Smart Cards
- Smart Card: Raak Technologies C2-40 Mini Driver Smart Card
- Smart Card Reader: OK 3021 USB Smart Card Readers
- Summary of Requirements
- Firewall Notes
- Notes Common to All Components
- Wonderware InTouch HMI
- Wonderware Application Server
- Wonderware Historian Server
- Wonderware Historian Client
- Wonderware Information Server
- .NET Framework
The following table lists the operating system, .NET Framework, and virtualization requirements for Wonderware System Platform 2014 R2.
Note: Only the software versions shown in the following tables are supported for Wonderware System Platform 2014 R2 components.
|2008 R2 SP1
|Server 2012 R2
|3.5 SP1||4.0||4.5||4.5.1||IE 10||IE 11||Hyper-V
(Based on Supported OS version)
(Basic virtualization-No HA/DR)
|VMWare vSphere 5|
|Application Server 2014 R2 (4.1)||N||Y||Y||Y||Y||Y||Y||C||N||Y||Y||Y||Y|
|InTouch 2014 R2 (11.1)||S||Y||Y||Y||Y||Y||Y||C||N||Y||Y||Y||Y|
|Historian 2014 R2 (11.6)||N||Y||Y||Y||Y||Y||Y||C||N||Y||Y||Y||Y|
|Historian Client 2014 R2 (10.6)||N||Y||Y||Y||Y||Y||Y||C||N||Y||Y||Y||Y|
|Information Server 2014 R2 Portal and Client (5.6)||N||Y||Y||Y||Y||Y||Y||C||N||Y||Y||Y||Y||Y||Y|
|FS Gateway 3.0||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y|
|Compact Installation (1-500 I/O per node)||Y||N||N||N||N||N||N||C||N||N||Y||Y||Y||Y|
|Small Installation (1-5,000 I/O per node)||N||Y||Y||Y||Y||Y||Y||C||N||N||Y||Y||Y||Y|
|Medium Installation (5k-50k I/O per node)||N||Y||Y||Y||Y||Y||Y||C||N||N||Y||Y||Y||Y|
|Large Installation (50k-400k I/O per node)||N||N||N||N||Y||Y||Y||C||N||N||Y||Y||Y||Y|
|Preferred Environment (64-bit OS and SQL Server)||R||R||C||N||N||Y||Y||Y||Y|
|Supported by a subset of products||S|
|Supported and Recommended||R|
Windows Operating System Notes
- The recommended operating systems are Windows 8.1 for client nodes and Windows Server 2012 R2 for server nodes.
- Newer operating system Service Packs (SPs) than those listed do not block the installation of Invensys products. A warning message may appear during the installation process.
- The Galaxy Repository (GR Node) can run on a client Windows operating system only in a single-node configuration in which Wonderware System Platform products are installed on a single computer. For a multi-node environment, the Galaxy Repository must installed on a computer running a Windows Server operating system.
- Development and application nodes are considered to be clients of the server GR node.
- When the operating system is upgraded on a computer, existing Wonderware System Platform products must be uninstalled prior to the upgrade and then reinstalled after the upgrade. There are two exceptions. Wonderware System Platform products do not need to be uninstalled when upgrading from Windows 8 to 8.1 or Windows 2012 to Windows 2012 R2.
- Versions of .NET (other than 4.x versions) can coexist, but all .NET code, including QuickScript.net scripts, run under .NET 4.5.1. For more information about .NET Framework requirements and compatibility, see .NET Framework Requirements and Compatibility .
- .NET 3.5 is installed only because the supported SQL Server versions require it. No other dependencies must exist.
SQL Server Notes
- The recommended SQL Server version is 2012 SP1 Standard (32/64 bit).
In order to establish communication with other components and services on the network, Wonderware System Platform and ArchestrA Service Bus (ASB) Services require certain network ports to be opened in the Windows Firewall. Typically, this is automatically done during the Wonderware System Platform installation. However, if the Windows Firewall is enabled at time of installation or if an alternative firewall is in use during installation, you will need to manually open the appropriate network ports in the firewall. For more information about port configuration, see "Configuring ArchestrA Service TCP Ports" in the Wonderware Application Server User's Guide.
ActiveX Controls Behavior on Windows 7, Windows 2008 R2, and Later Operating Systems
Due to the Data Execution Prevention (DEP) feature of Windows 7, Windows 2008 R2, and later operating systems, any ActiveX control built with ATL version 7.1 or earlier will fail to host or will have unpredictable behaviors in InTouch 11.0 either in WindowMaker or WindowViewer running on Windows 7, Windows 2008 R2, and later operating systems.
The ActiveX controls and error message, along with solutions to resolve the behavior, are described in detail in TechNote 988, "Some ActiveX Controls NOT Supported in InTouch 2012 R2 (Version 10.6)". You can download this TechNote from the Wonderware Developers Network (WDN) Library.
Configuring Remote Alarm Retrieval Queries When Running Windows 7, Windows Server 2008 R2, and Later Operating Systems
The process to configure remote alarm retrieval queries has changed for interactive applications such as InTouch HMI when running on Windows 7, Windows Server 2008 R2, and later operating systems.
When InTouch WindowViewer is started and generates alarms from an interactive Windows 7, Windows Server 2008 R2, or later desktop session, an AlarmViewer control (running within InTouch HMI) on a remote node must be specially configured to query the alarms. The source alarms will not appear unless the AlarmViewer control's alarm query is configured.
This type of query only works for InTouch HMI as an alarm provider running in a Terminal Services session, not for InTouch HMI running in a console session.
To configure the AlarmViewer's alarm query
- After starting InTouch WindowViewer (alarm provider) on the Windows 7, Windows Server 2008 R2, or later node, open the SMC Logger and look for the most recent string generated by AlarmMgr. For example: "Registering AlarmMgr with SLSSVC as AlarmMgr 253.127.148.120". The indicated IP address will be unique to your alarm-providing node. Note the IP address for use in Step 2.
- In the Alarm Query tab of the AlarmViewer control on the remote computer, configure the alarm query as follows, substituting your nodename of the alarm providing InTouch HMI for "nodename" below and substituting your IP address noted in the previous step:
where nodename is the name of the node that is providing the InTouch alarm and ip_address is the IP address that you determined in step 1.
- Test to validate that the alarms generated from the alarm-providing node are shown accurately in the AlarmViewer control.
Using Alarm Manager on a Single Node Running Both Wonderware InTouch HMI and Application Server Alarm Providers on Windows Vista and Later Operating Systems
Starting with Microsoft Windows Vista, the operating system imposes "Session 0 Isolation" as a security enhancement. All Windows services and associated programs are required to run in Session 0, and no GUI applications are allowed to run in Session 0.
Prior to Windows Vista, Wonderware Application Server and InTouch WindowViewer ran in the same Windows session. Session 0 Isolation requires that Application Server and WindowViewer run in separate Windows sessions. Alarms that are reported by the Galaxy are handled by the Session 0 instance of Alarm Manager (AlarmMgr), which is now different from the Console Session instance of AlarmMgr that handles InTouch alarms. A simple alarm query in an InTouch alarm display such as
is now serviced by two separate instances of AlarmMgr -- one running in the Console Session for InTouch, another running in Session 0 for the Galaxy.
This behavior, and related behaviors and error messages resulting from the Windows operating system Session 0 changes, along with procedures to configure the Distributed Alarm System to support alarms from both InTouch and Application Server on the same computer node running with Windows Vista and later operating systems, are described in detail in TechNote 988, "AlarmMgr Support for InTouch and AppServer on Windows Vista and Later". You can download this TechNote from Wonderware Developers Network (WDN) Downloads.
Windows Server 2008 R2 and later operating systems no longer support the /console switch as a means of starting the remote desktop (RDP) client, also known as Session 0 or Terminal Server Console session. In Windows Server 2008 R2 and later operating systems, Session 0 is no longer an interactive session, and is reserved only for Windows services. Windows Server 2008 R2 and later operating systems treat all remote connections as remote RDP sessions regardless of /console, /admin, or any other switches used to make the connection.
This impacts InTouch HMI functionality such as Alarm Manager that depends on the Terminal Server Console session. The impact to Wonderware Application Server is minimal as most Wonderware Application Server processes run as services. One impact to Wonderware Application Server is to carry forward the restriction introduced with the Windows Vista operating system which permits only one alarm provider. While both Wonderware Application Server and InTouch HMI can be configured as alarm providers, only one alarm provider can be configured at any one time.
Refer to the Wonderware InTouch HMI 2014 R2 Readme for further information about InTouch HMI applications running in the Terminal Server Console.
If you are running WindowViewer within a Terminal Server session and want to access alarms from WindowViewer in a client session, you must use the syntax \\terminalservernode:<IP address>\InTouch!$System to access the alarms, with a colon (:) after the node name. The IP address is that of the client computer connected to the session.
The following notes are specific to the InTouch HMI 2014 R2 operating system support and requirements.
- The recommended operating system for a Galaxy Repository is Windows Server 2012 R2.
- Microsoft Windows 8.1 (32-bit or 64-bit) is the recommended operating system to run InTouch HMI client components.
- Microsoft Windows Server 2012 R2 is the recommended operating system to run InTouch HMI server components.
- The recommended operating system for InTouch HMI development is Windows Server 2012 R2 or Windows 8.1.
- The recommended operating system for run-time nodes is Windows 8.1.
- Windows 7 and later operating systems do not support a dedicated single-node server configuration that runs one or more databases for an InTouch HMI system.
- As of Wonderware System Platform 2014, a computer running Windows 7 or later operating systems can be configured as both an InTouch and an Application Server alarm provider. For more information, see Using Alarm Manager on a Single Node Running Both Wonderware InTouch HMI and Application Server Alarm Providers on Windows Vista and Later Operating Systems.
- Wonderware InTouch HMI 2014 R2 does not support the following legacy script functions on 64-bit systems: WWPoke(), WWExecute(), WWRequest(), ActivateApp() and SendKeys().
- If Recipe Manager is started using the path Start\Program\Wonderware\InTouch\Recipe, then select Run as Administrator.
- The InTouch Extensibility Toolkit might need to be started by right-clicking and selecting Run As Administrator to function properly.
- The onscreen keyboard options have changed for the Windows 7, Windows Server 2008 R2, and later operating systems.
- Hovering to select from the Windows keyboard does not work in the Windows 7, Windows Server 2008 R2, and later operating systems.
NetDDE is not supported for InTouchView applications.
By design, an InTouchView application does not serve data to any other source, including InTouch HMI itself. When WindowViewer starts, it verifies if the application is an InTouchView application. When WindowViewer detects an InTouchView application, it does not register to become a DDE server. ArchestrA Symbols make use of the client layer when accessing InTouch tags, and appear as a third-party client trying to access WindowViewer as a data server. As a result, ArchestrA Symbols cannot communicate with InTouch tags when used with an InTouchView license.
In ArchestrA Symbols, InTouch:‹tagname› is still a valid method of referring to an InTouch tag on a local node.
Wonderware System Platform 2014 R2 with InTouch HMI v11.1 supports User Account Control-enabled operations on run-time nodes.
- Windows Server 2012 R2 is the recommended operating system for the Galaxy Repository node.
- Windows 8.1 is the recommended operating system for Wonderware Application Server development (IDE) or run-time nodes (Bootstrap).
- The Bootstrap, IDE, and Galaxy Repository are supported by the following language versions of Microsoft operating systems: English, Japanese, Simplified Chinese, German, and French. The Galaxy Repository is also supported by the English, Japanese, Simplified Chinese, German, and French versions of Microsoft SQL Server 2008 SP3, SQL Server 2008 R2 SP2, and SQL Server 2012 SP1.
- Upon installation, the selected language and regional settings must match those of the intended operating locale and must use the collation of SQL Server that matches the operating system locale.
Wonderware Application Server and DDE Support
In Windows 7, Windows Server 2008 R2, and later operating systems, DDE is supported only on a local node. Windows 7, Windows Server 2008 R2, and later operating systems do not support NetDDE. ArchestrA Symbols use the client layer when accessing InTouch tags and appear as a third-party client trying to access WindowViewer as a data server. Therefore the use of NetDDE for communication is not supported and not recommended.
In ArchestrA Symbols, InTouch:<tagname> is still a valid method of referring to an InTouch tag on a local node.
Using Wonderware Application Server with Windows 7, Windows Server 2008 R2, and Later Operating Systems
This section describes specific behaviors and restrictions when using the Windows 7 and Windows Server 2008 R2 operating systems with Wonderware Application Server.
- The DDESuiteLink Client connection to the local DAServer using Local DDE is supported ONLY when the DAServer is configured as "Not a Service" and activated from its executable file or launched from InTouch. On Windows 7, Windows 2008 R2, and later operating systems, Local DDE is NOT supported when the DAServer is activated in the System Management Console (SMC).
- For toolkits such as the ArchestrA Object Toolkit, GRAccess Toolkit, and MXAccess Toolkit to function properly on Windows 7 and later operating systems, you may need to start the toolkit by right-clicking on the file and then clicking Run As Administrator.
Wonderware Application Server and User Account Control Level
Wonderware Application Server 2014 R2 supports User Account Control-enabled operations. Starting the IDE still requires elevated privileges.
Scenarios involving remote node communication fail if the Historian node is using the Windows 7, Windows 8, Windows Server 2008 R2, or Windows Server 2012 operating system.
- When you log in as a local administrator on a computer and try to add a remote Wonderware Historian node (a second node with the Wonderware Historian installed) using the network account from the Management Console, the status of the remote Historian node is not reflected correctly.
- Test the connection from a Historian node using the operating system to a remote tier-2 historian. The following error message is shown: "Test Connection to replication server () failed: cannot connect to Tier-1 replication service (error 0x80004005: Unspecified error)"
- Replication to the remote tier-2 historian fails.
- Although a remote IDAS service starts successfully, errors and warnings stating "Failed to get IDAS configuration version..." and "Unable to start data acquisition" are logged. This problem occurs if the ArchestrA user account is a local user. If the ArchestrA user account is a domain user, then this problem does not occur.
- Open a command prompt and run the following command: cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f This sets LocalAccountTokenFilterPolicy registry entry value to 1. In doing so, an elevated token for the user is generated.
- Restart the system.
When the Wonderware Historian Client application is running on Microsoft Windows 7, Windows Server 2008 R2, and later operating systems, User Account Control can be enabled and running as non-administrator.
When the Wonderware Information Server is running on Microsoft Windows 7, Windows Server 2008 R2, and later operating systems, User Account Control can be enabled and running as non-administrator.
IMPORTANT: We strongly recommended that prior to upgrading your existing applications to Wonderware System Platform 2014 R2, that you back up your applications, become familiar with the changes introduced by Microsoft in .NET 4.5.1, and that you review your .NET scripts and .NET controls for any required changes. After upgrading to Wonderware System Platform 2014 R2, you should perform application testing on application scripts and on script libraries used by the application to ensure they continue to function properly under .NET 4.5.1. We also recommend you test the upgrade in a staging system prior to upgrading your production system.
Wonderware System Platform 2014 R2 leverages Microsoft .NET Framework 4.5.1. The Wonderware System Platform installation program will install .NET 4.5.1 if it is not already present in your system. .NET 4.5.1 can coexist with previous versions of .NET Framework. On nodes where SQL Server is installed, .NET 3.5 is also installed by Wonderware System Platform. In this scenario, Wonderware System Platform 2014 R2 will use .NET 4.5.1. Other applications you may have on the same machine with dependencies on .NET 3.5 will access .NET 3.5.
All user-supplied .NET code that runs in the context of InTouch HMI and Application Server will now run under the .NET Framework 4.5.1. Although .NET Framework 4.5.1 is highly compatible with applications that are built with earlier .NET Framework versions, Microsoft has introduced changes in .NET 4.5.1 to improve security, standards compliance, correctness, reliability, and performance that may require changes to .NET scripts you may have created with Wonderware System Platform 2014 R2 and earlier versions of Application Server, InTouch HMI, the Historian, Historian Client, and Wonderware Information Server. These changes may also affect .NET controls developed with .NET 3.5.
In ArchestrA scripting, some .Net codes could fail if not using proper text encoding, and could cause a script to exit without completion. The UTF8Encoder is the default BinaryStream decoder in .Net 4.5. To enable an ArchestrA script to decode ASCII XML data, for example, insert the following snippet:
BinaryReader streamReader = new BinaryReader(ms, new ASCIIEncoding());
To learn more about changes introduced in .NET Framework 4.5.1, refer to the following Microsoft resources:
What's New in the .NET Framework 4.5.1: http://msdn.microsoft.com/en-us/library/ms171868%28v=vs.110%29.aspx What's obsolete in the .NET Framework class library: http://msdn.microsoft.com/en-us/library/ee461502(v=vs.100).aspx Migration Guide to the .NET Framework 4.5.1: http://msdn.microsoft.com/en-us/library/ff657133(v=vs.110) .NET Framework 4 Migration Issues: http://msdn.microsoft.com/en-us/library/ee941656%28v=vs.100%29
Wonderware System Platform 2014 R2 supports the following virtualization environments:
- Microsoft Hyper-V: based on the version of Windows
- VMware 5.0 basic virtualization without High Availability and Disaster Recovery (HA/DR)
- VMWare vSphere 5
The following table describes the SQL Server requirements for all Wonderware System Platform 2014 R2 components. The recommended SQL Server version is 2012 SP1 Standard (32/64 bit).
|2008 SP3 Express-SSMSE (32-bit)||2008 R2 Express-SSMSE (32-bit)||2008 R2 SP1 Express-SSMSE (32-bit)||2008 R2 SP2 Express-SSMSE (32-bit)||2008 SP3 Standard, Enterprise (32-bit Only)||2008 R2 Standard, Enterprise (32/64 bit)||2008 R2 SP1 Standard, Enterprise (32/64 bit)||2008 R2 SP2 Standard, Enterprise (32/64 bit)||2012 Express-SSMSE (32-bit only)||2012 SP1 Express-SSMSE (32/64 bit)||2012 SP2 Express-SSMSE (32/64 bit)||2012 Standard, Enterprise (32/64 bit)||2012 SP1 Standard, Enterprise (32/64 bit)||2012 SP2 Standard, Enterprise (32/64 bit)||2014 Express-SSMSE (32-bit only||2014 Standard, Enterprise (32/64 bit)|
|Application Server 2014 R2||S||S||S||S||Y||Y||Y||Y||S||S||S||Y||Y||Y||S||Y|
|InTouch 2014 R2||S||S||S||S||Y||Y||Y||Y||S||S||S||Y||Y||Y||S||Y|
|Historian 2014 R2||S||S||S||S||Y||Y||Y||Y||S||S||S||Y||Y||Y||S||Y|
|Historian Client 2014 R2|
|Information Server Portal 2014 R2||S||S||S||S||Y||Y||Y||Y||S||S||S||Y||Y||Y||S||Y|
|Compact Installation (1-500 I/O per node)||N||N||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y|
|Small Installation (1-5,000 I/O per node)||N||N||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y|
|Medium Installation (5k-50k I/O per node)||N||N||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y||Y|
|Large Installation (50k-400k I/O per node)||N||N||N||N||N||Y||Y||Y||N||N||N||Y||Y||Y||N||Y|
|Preferred Environment (64-bit OS and SQL)||R|
We recommend that you install and configure the supported SQL Server version before you begin the Wonderware System Platform installation program, especially if you expect Wonderware Information Server to coexist, either on initial or subsequent installations, with the InTouch HMI, Application Server, or the Historian Server.
The Wonderware System Platform installer will install all prerequisites except the SQL Server requirement for installing the Historian Server. If you select the Historian Server for installation, and if the supported version of SQL Server is not already installed, you must exit the installation program, install the supported SQL Server version, then resume the installation.
Considerations for SQL Server
- Alarm DB Logger To use the Alarm DB Logger with SQL Server Express, you need to change the default authentication mode from Windows-based to Mixed Mode.
- SQL Server Configuration Rights: While installing Wonderware System Platform, if the logged-on user performing the installation is not a SQL Server administrator, the Config SQL dialog box appears and requests SQL Server administrator credentials.
- Maximum Server Memory: After installing SQL Server, use SQL Server Management Studio to confirm that the Maximum Server Memory is configured to approximately 65% of the total available RAM. By default SQL Server does not clamp this setting. The Wonderware System Platform installation process will attempt to adjust it if it has the appropriate rights to configure SQL Server.
- Restoring a CAB: You cannot restore a Galaxy .cab file backed up in SQL Server 2012 or SQL Server 2008 to a node with an earlier version of SQL Server. For example, you cannot restore a Galaxy .cab file backed up in SQL Server 2012 to a node with SQL Server 2008. For example, you cannot restore a Galaxy .cab file backed up on SQL Server 2008 to a node with SQL Server 2005. SQL Server database backups from SQL Server 2005 forward are not backward-compatible. Attempting such a restore results in an error message.
- The MSSQL Server user account is not supported for the SQL Server 2012 Service. Instead, configure SQL Server to run as the local system or Network Service account. Named instances are not supported.
- Migrating SQL Server Versions: You can migrate a SQL Server database to a later version from any of two prior versions. For example, you can migrate to SQL Server 2012 from SQL Server versions 2008 or 2005. You can migrate to SQL Server 2008 from SQL Server versions 2005 or 2000. You cannot migrate directly from SQL Server 2000 to SQL Server 2012. Such a migration requires an intermediate step. For more information and helpful procedures, see the following Microsoft references:
- Upgrade to SQL Server 2014
- Migrate SQL Server 2000 to SQL Server 2012
- Migrating to SQL Server 2008 R2
- Migrating to SQL Server 2008
- T-SQL scripts to migrate SQL server 2000 user databases to SQL server 2012
- ALTER DATABASE Compatibility Level (Transact-SQL) SQL Server 2012
- ALTER DATABASE Compatibility Level (Transact-SQL) SQL Server 2008 R2
- SQL Server Rights Requirements: SQL Server 2008 and later versions do not automatically create the BUILTIN\Administrators role delivered in SQL Server 2005. Because of this change to SQL Server, the Wonderware Application Server 2014 R2 installation process will create the necessary operating system user group (aaAdministrators) as well as the necessary SQL Server role. This automated process will provide the rights required to allow operations within the Galaxy Repository without the need for blanket BUILTIN\Administrator rights. The aaAdministrators group must be present and enabled. If you accidentally delete the aaAdministrators group from the Windows operating system, you can run either of two options to restore it:
- Run the Change Network Utility from the Windows Start menu.
- Run the aaConfig SQL Utility from the Windows Start menu.
If you accidentally delete the aaAdministrators group from the SQL Server security logins, you must run the aaConfig SQL Utility to restore it. Refer to the Wonderware Application Server User's Guide, "About ArchestrA User Accounts", for further information and procedures about restoring the aaAdministrators group.
Considerations for SQL Server Express
- SQL Server Express is supported for use on an InTouch, Application Server, or Historian node, recommended for use only in small or development configurations. SQL Server 2012 SP1 Express is automatically installed for when you install for InTouch, Application Server, or the Historian, if, at time of installation, no other SQL Server elements are installed on the computer.
- If you plan to use SQL Server Express with Wonderware Information Server 2014 R2 and Wonderware InTouch HMI 2014 R2 on the same node, the following limitations apply:
- Installing Wonderware Information Server first, using the MS SQL Express default instance name set to "SQLEXPRESS", and then installing Wonderware InTouch HMI will work without issue. Note that in this scenario, each component uses a dedicated instance of SQL Server 2008 Express.
- Installing Wonderware InTouch HMI first, which silently installs and configures SQL Server 2012 SP2 Express, and then installing Wonderware Information Server will not allow Wonderware Information Server to work. In this case, during the Wonderware Information Server configuration, an error message will appear in the Configuration Utility stating: "SQL Server client components not found." To work around this issue, configure Wonderware Information Server to use an instance of SQL Server Express (or a non-Express edition) on a remote node.
- The computing capacity of SQL Server 2012 SP1 Express is limited to the lesser of one CPU socket or four processor cores.
- For InTouch HMI-only installations, the Wonderware System Platform installer will automatically install SQL Server 2012 SP1 Express if these conditions are met:
- No version of SQL Server is installed on the computer at the time of installation.
- You select only the InTouch Development and Runtime Wonderware System Platform installation option. When you select InTouch Development and Runtime, a Galaxy Repository will be installed.
- If multiple versions of SQL Server are installed, the one used as the Galaxy Repository must be the default instance. Named instances are not supported.
- The Galaxy Repository 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.
- To use the Alarm DB Logger with SQL Server Express, you need to change the default authentication mode from Windows-based to Mixed Mode.
- Named instances are not supported.
- Wonderware Information Server supports case-insensitive and case-sensitive SQL Servers.
For Wonderware Historian Client:
- Microsoft Office is an optional prerequisite. If you install Office after installing Wonderware Historian Client, the Historian Client add-ins do not appear in the list of Office add-ins. Run the Wonderware Historian Client installation program and repair the installation to load the Office add-ins.
- When you perform a custom installation of Microsoft Office 2010 or Microsoft Office 2013 (32-bit), you
must install Office Shared Features and Office Tools so that
the Historian add-ins for Workbook or Report can be loaded. Note: Make sure that you are not using the Microsoft Office 2013 (64-bit) version.
For Wonderware Information Server:
|Module or Component||Details||Required Version||Recommended Version|
|SSRS||SQL Server Reporting Services (to use the ArchestrA Reporting feature)||2008 SP3, 2008 R2 SP2, or 2012 SP1||2012 SP1|
|MS Excel||Microsoft Excel (to use the ActiveFactory Reporting Website feature)||2010 or 2013 (32-bit)||2010 or 2013 (32-bit)|
|Microsoft ASP.NET||Microsoft ASP.NET. The Wonderware Information Server post-installation Configurator utility automatically configures ASP.NET.||2.0 or 3.5||3.5|
|MSI||Microsoft Windows Installer. This is included on the installation DVD and is automatically installed.||4.5||4.5|
|IIS||Internet Information Services. You must perform a default installation, and the Wonderware Information Server post-installation Configurator utility automatically configures IIS.||7.0, 7.5, or 8.0||7.0, 7.5, or 8.0|
|IE||Internet Explorer||8.0, 9.0, or 10.0||10.0|
|OSIsoft OLE DB client connectivity software||Required on the Wonderware Information Server portal node for the Information Model to connect to an OSIsoft PI Server (OLE DB) data source.||220.127.116.11a||18.104.22.168a|
|Oracle client connectivity software||Required on the Wonderware Information Server portal node for the Information Model to connect to an Oracle data source.||10g and 11g||10g and 11g|
|Microsoft Office 10 client connectivity software||Required on the Wonderware Information Server portal node for the Information Model to connect to text (.csv) data source.||Microsoft.ACE.OLEDB.12.0||Microsoft.ACE.OLEDB.12.0|
Wonderware Information Server supports IPv4 only.
You must install Microsoft Excel 2013 (32-bit) with the Visual Basic for Applications feature on the Wonderware Information Server computer in order for Wonderware Historian Client published reports to be viewed. The 64-bit version of Excel is not compatible.
The Wonderware Information Server installation program scans for these components. If the MSXML and Capicom components are not installed, the installation program silently installs them to the target computer. Note the following important information regarding individual components:
|SQL Server Reporting Services:||To use the ArchestrA Reporting feature, you must install and configure SQL Server Reporting Services and set up a reporting database before configuring the ArchestrA Reports feature in Wonderware Information Server. The versions of SQL Server and SQL Server Reporting Services used must match (for example, both 2008).|
the Process Graphics feature to work, WebDAV is automatically installed
during configuration of the Wonderware Information Server.
You can manually download WebDAV from the following links:
In a single-node environment, if you need to combine
multiple products delivered within Wonderware System Platform 2014 R2,
all the products need to be at the same version delivered in Wonderware
System Platform 2014 R2.
In a node-to-node environment, products are compatible between the current licensed version and one licensed version back.
Compatibility means that the products can communicate with each other over the network. Co-existence means that the products can be installed on the same computer.
In some cases, Wonderware System Platform is supported in newer environments than a compatible product. Wonderware System Platform has been tested for compatibility with a listed product only in the environments that are supported by that particular product.
|Wonderware System Platform||4.5||N||N/A|
|2012 R2 P01||Y||N/A|
|2012 R2 P02||Y||N/A|
|2012 R2 P03||Y||N/A|
|Wonderware InTouch CE||10.1||N||N|
|Wonderware Manufacturing Execution System||4.0 SP1||N||N|
|4.5 (2012) P01||Y||Y|
|Wonderware InControl™||7.11 SP2 P01||N||N|
|Wonderware Manufacturing Execution Module||1||Y||N|
* If you are using Wonderware Information Server with InBatch software, upgrading to Wonderware Information Server 5.6 requires an InBatch hotfix to maintain compatibility.
|10.0 (2012 R2)||N||N|
|10.1 (2014)||Y *||Y *|
|Wonderware QI Analyst™||8.0 SP1 P01||N||N|
|Wonderware SCADAlarm™||6.0 SP2 P01||N||N|
|ArchestrA Workflow™||1.5 (2012)||N||N|
|1.6 (2012 SP1)||N||N|
|1.7 (2012 R2)||N||N|
|1.9 (2012 R2 SP1)||N||N|
|Wonderware Skelta BPM||2014||N||N|
|Wonderware PEM||2.1 SP1||Y||Y||Wonderware Online (see components below)||1.0|
||11.0 and 11.1||Y||Y|
|Recipe Manager Plus PEM||1.0 (2014)||Y||Y|
|1.5 (2014 R2)||Y||Y|
|Schneider Electric Citect-VJC||7.2 SP3||Y||Y|
|Schneider Electric ClearSCADA||CS 2013 R1||N||Y|
|CS 2013 R2||N||Y|
|CS 2014 R1||N||Y|
|CS 2015 R1||Y||Y|
- The extended features of the ArchestrA Web Exporter only support ArchestrA Symbols and InTouchViewApp applications from Wonderware Application Server 3.1 or later, InTouch HMI 10.0 SP2 or later, and InTouch HMI 10.1 or later.
- HTTP access to Historian Server is not supported in this version.
- Publishing from ActiveFactory 9.2, Historian Client 10.0, 10.0 SP1, and 10.0 SP2 is supported.
- Opening of already published Historian Client workbook reports and trends (published from an old version of Historian Client) in Wonderware Information Server 4.5 is supported.
- Publishing from ActiveFactory 9.2, Historian Client 10.0, 10.0 SP1, and 10.0 SP2 to Wonderware Information Server versions prior to 4.5 is not supported.
- If you are using FCS with Wonderware Information Server, note that a direct upgrade from Wonderware System Platform 4.5 to 5.1 is not supported for FCS. You must first upgrade to Wonderware System Platform 5.0.
- Wonderware System Platform 2014 R2 is not compatible with the Skelta BPM 2014 Connector for System Platform. Please contact your Wonderware sales representative for the availability of an updated Skelta BPM 2014 Connector for System Platform.
The product compatibility information contained in this Wonderware System Platform 2014 R2 Readme supersedes information contained in other product Readme files delivered on the Wonderware System Platform 2014 R2 DVD. In any instance where conflicting information occurs, this Readme is the more up-to-date and should be taken as correct. The Wonderware InTouch HMI 2014 R2 Readme duplicates some of the same information contained in this Readme, but is focused on InTouch HMI.
For detailed installation instructions in English, see the Wonderware System Platform Installation
Guide (WSP_Install_Guide.pdf) or Wonderware System Platform Installation Help (WSP_Install_Guide.chm).
This guide supersedes the separate installation guides for the individual products. The Installation Guide
pdf file is located in the root directory of the Wonderware System Platform 2014 R2 installation DVD. The
Installation Help chm file is located in the InstallFiles directory of the installation DVD.
The information provided in this Readme file and the InTouch Readme file supersedes the InTouch HMI Installation Help (Install-InTouch.chm) for the French, German, Japanese, and Simplified Chinese languages.
- Installing Wonderware System Platform 2014 R2 on a computer used as a domain controller is not supported. For more information, see http://technet.microsoft.com/library/Cc966456.
- If Recipe Manager Plus will be installed on the same computer as Wonderware System Platform 2014 R2, install Recipe Manager Plus first. Wonderware System Platform 2014 R2 is installed with the latest version of ArchestrA Service Bus (ASB).
About the 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.
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 the ArchestrA user account has not previously been configured, you will be prompted to configure it during the Wonderware System Platform 2014 R2 installation. You must specify a user name, password, and domain.
If you choose to use existing user account, it should meet the following requirements:
- User account with a permanent password that does not expire.
- User account in which the password cannot be changed.
- User account that is a member of the local Administrators group.
After you install a Wonderware System Platform component, you can use the ArchestrA Change Network Account utility to change or re-create the ArchestrA user account. This utility is located in the Common folder after you install InTouch HMI. You must have Administrator privileges on the computer to make changes with the Change Network Account utility. For more information, see the Change Network Account utility help.
Note: If you re-create the user account using the Change Network Account utility, the Microsoft Windows security component on the computer can take several minutes to update this information on the ArchestrA Galaxy node. Until that occurs, the ArchestrA component may not function properly. Restarting the Galaxy node updates this information immediately.
- Wonderware System Platform Upgrade and Migration Notes
- Application Server Upgrade and Migration Notes
- InTouch and InTouch Access Anywhere Upgrade and Migration Notes
- Wonderware Historian Upgrade and Migration Notes
- Wonderware Historian Client Upgrade and Migration Notes
- Wonderware Information Server Upgrade and Migration Notes
The following table shows supported versions for upgrade and migration.
Upgrading is installing a newer version of the software when a previous version of the software exists. An upgrade is possible when the system requirements (operating system, SQL Server, .NET Framework) are met. The upgrade process will properly remove or uninstall the previous software version and install the new version. For versions older than the current and previous licensed versions, only the latest service pack or patch versions are tested. For distributed systems, some products must be upgraded in a particular order. For more information, see upgrade information for each product in the Wonderware System Platform Installation Guide.
The earliest version of Windows supported by Wonderware System Platform 2014 R2 is Windows 7, and the first version of Application Server and InTouch that supported Windows 7 was Application Server 3.1 SP3 and InTouch 10.1 SP3. Therefore, to upgrade from versions of Application Server earlier than 3.1 SP3 or InTouch earlier than 10.1 SP3 to Wonderware System Platform 2014 R2, you must manually uninstall the Wonderware software, upgrade to or replace with a compatible operating system, and then perform a fresh install of Wonderware System Platform 2014 R2.
Migration is the process of converting applications that have been created in a previous version of a product to the current version. For versions older than the current and previous licensed versions, only the latest service pack or patch versions are tested.
IMPORTANT! Back up any relevant application configuration files or databases before you start an upgrade or migration.
|Wonderware System Platform||4.5||Y||Y||Y|
|2012 R2 P01||Y||Y||Y|
|Wonderware Application Server||2.0 P01||N||N||N|
|3.1 (no SP)||N||Y||Y|
|3.1 SP2 P01||N||Y||Y|
|3.1 SP3 P01||Y||Y||Y|
|3.2 and later, see System Platform product||N/A||N/A||N/A|
|8.0 SP2 P04||N||N/A||Y|
|10.1 (no SP)||N||N/A||Y|
|10.1 SP2 P01||N||N/A||Y|
|10.1 SP3 P01||Y||N/A||Y|
|Wonderware Historian||8.0 SP3 P01||N||N/A||N|
|For 11.0 and later, see System Platform.||Y||N/A||Y|
|Wonderware Historian Client||9.2||N||N/A||Y|
(Portal and Client)
|3.0, 3.0 SP1||Y||N/A||Y|
Important Note: If you plan to upgrade Wonderware System Platform on a computer that has InTouch Access Anywhere Server installed, you must first uninstall the InTouch Access Anywhere Server. Then, upgrade Wonderware System Platform and finally reinstall InTouch Access Anywhere Server.
Back up any custom configuration of the installed instance of InTouch Access Anywhere before you uninstall it.
If you are upgrading Wonderware Application Server to the new Wonderware System Platform 2014 R2 version, be aware of the following:
- Back up the Galaxy before starting the upgrade. Also, upload any run-time changes for critical objects. You cannot upload any run-time changes after you upgrade the system. For more information, see the Wonderware System Platform Installation online help.
- Upgrading to Wonderware Application Server 2014 R2 will affect run-time nodes. Node-by-node upgrade is supported with limitations. Changing the security or history model in a node-by-node upgrade of the run-time nodes is not supported. Nodes that are currently deployed will not receive any history or security changes from the upgraded Galaxy Repository node.
- Installing Wonderware Application Server 2014 R2 automatically undeploys any platform that is currently deployed in the node that is being updated. Changes to the WinPlatform object and other components require any deployed platforms to be redeployed.
- When upgrading SQL Server on the Galaxy Repository node, back up the Galaxy before starting the upgrade. Upload any run-time changes for critical objects. You cannot upload any run-time changes after you upgrade the system. For more information, see the Wonderware Application Server Installation online Help.
- If Wonderware Application Server is installed on the same node as Wonderware InTouch HMI, both must be upgraded to Wonderware System Platform 2014 R2 versions, and you must upgrade Wonderware Application Server before upgrading InTouch HMI.
- You must install Wonderware Historian 9.0 Patch 02 or Historian 10.0 or later to take advantage of new Historian features including time propagation and late data from the Wonderware Application Server to the Historian. These versions are also required to leverage the new Historian configuration options from the IDE.
- If the ArchestrA IDE currently connects remotely to the Galaxy Repository on another computer, install Wonderware Application Server 2014 R2 on both nodes. A remote connection between the ArchestrA IDE and the Galaxy Repository fails if the nodes have different versions of Wonderware Application Server.
- It is strongly recommended that you undeploy the platform prior to upgrading the software in that node. Once the Galaxy Repository node is upgraded from any prior version to version 4.1, all run-time nodes hosting Wonderware InTouch applications must have both Wonderware Application Server upgraded to 2014 R2 (if you are running InTouch applications). You will not be able to deploy or undeploy objects on non-upgraded nodes. Installing the software on a run-time node will remove the running platform and objects. The platform and objects can then be redeployed after the software upgrade is complete.
- Upgraded IDE/Client nodes cannot connect to a non-upgraded Galaxy Repository and vice-versa.
- The Galaxy Repository node will be undeployed before upgrading to Wonderware Application Server 2014 R2.
- Running platforms must be undeployed during the upgrade process.
- WinPlatform and other related objects on a remote node will be marked as "software update pending".
- You will not be able to deploy from an upgraded Galaxy Repository node to non-upgraded remote nodes.
- While migrating the GR node, the existing database schema is migrated to the new version 2014 R2 schema. The GR node migration fails if the GR node is used as a run-time node for another GR.
- IMPORTANT! If the Wonderware Historian will be used to collect data from Application Server, upgrade the Historian to 2014 R2 before upgrading any Application Server Platforms to 2014 R2.
Important Note: The InTouch Access Anywhere Server has been updated to resolve a security vulnerability to a buffer overflow. You must uninstall InTouch Access Anywhere version 11.0 from all InTouch nodes where it is installed and install InTouch Access Anywhere version 11.1 that is in Wonderware System Platform 2014 R2.
You can determine the version of InTouch Access Anywhere Server installed on a computer using Programs and Features from the Windows Control Panel.
If you are upgrading Wonderware InTouch HMI to the new Wonderware System Platform 2014 R2 version, be aware of the following:
- InTouch Development (WindowMaker™) is now installed with support for ArchestrA graphics. This includes the ArchestrA Integrated Development Environment (IDE), Bootstrap, Galaxy Repository (GR), and FS Gateway.
- FactorySuite Gateway (FS Gateway) 3.0 SP1 is installed as part of InTouch HMI 2014 R2 in an Wonderware System Platform 2014 R2 installation. If you originally installed FS Gateway 2.0 SP1 without any other InTouch products, then upgrading Wonderware System Platform 2012 R2 to Wonderware System Platform 2014 R2 will not upgrade FSGateway to version 3.0 SP1. You must uninstall FSGateway 2.0 SP1 before upgrading to Wonderware System Platform 2014 R2.
- If SQL Server does not exist on the system, SQL Server Express is installed automatically.
- If the added features are not needed in your current environment, you will need to use the Wonderware System Platform "product-based" installation on a "clean" system. The product-based installation provides a customization option so that you can deselect any components that are not needed. Note that the customization option is not available if you are upgrading an existing system from a previous version of InTouch Development.
- If Wonderware Application Server is installed on the same node as Wonderware InTouch HMI, both must be upgraded to ArchestrA 2014 versions, and you must upgrade Wonderware Application Server before upgrading InTouch HMI.
- If you are using managed InTouch applications with ArchestrA Symbols from Application Server 3.1 SP3 or earlier, run the ArchestrA Symbol Analysis and Repair Utility before installing Wonderware Application Server 4.1 to ensure that all issues reported by the utility are addressed. You can download the utility from the Wonderware Developers' Network (WDN), Software Downloads. Log in to WDN with your username and password to access the downloads archive.
It is possible to upgrade from earlier versions of Wonderware Historian than 10.1, but you must first upgrade to the 10.1 version. Follow the instructions in the 10.1 documentation to perform the upgrade. After you have upgraded to the 10.1 Historian, you can then upgrade to Wonderware Historian 2014 R2.
IMPORTANT! If the Wonderware Historian will be used to collect data from Application Server, upgrade the Historian to 2014 R2 before upgrading any Application Server Platforms to 2014 R2.
The application files created with ActiveFactory 9.2, Wonderware Historian Client 9.5, Wonderware Historian Client 10.0, Wonderware Historian Client 10.0 SP1, Wonderware Historian Client 10.0 with SP2, Wonderware Historian Client 2012 R2 software require no modifications to be used with the Wonderware Historian Client 2014 R2 software. Optionally, the application files can be migrated to take advantage of new retrieval features. For more information, see the Wonderware Historian Client User's Guide.
You can open Trend, Query, Workbook, and Report files created using ActiveFactory versions 9.0, 9.1, 9.2, and Wonderware Historian Client versions 9.5, 10.0, 10.0 SP1, 10.0 with SP2, and 10.1. These documents are converted and saved to the format used by Wonderware Historian Client 2014 R2. ActiveX and .NET applications built using ActiveFactory 8.5, 9.0, 9.1, 9.2, and Wonderware Historian Client 9.5, 10.0, 10.0 SP1, 10.0 with SP2, and 10.1 controls continue to operate without changes to their original functionality.
Direct upgrade from Wonderware Information Server v 5.0 and earlier versions is not supported. Earlier versions of Wonderware Information Server have to upgrade through Wonderware Information Server v5.0 P01 to be upgraded to Wonderware Information Server v5.6. For more information, see the Wonderware System Platform Installation Guide.
Wonderware Information Server version 5.6 supports and requires Silverlight 5.0 for ArchestrA Graphics to function correctly. The published ArchestrA Graphics from Wonderware Information Server version 5.5 or earlier can only support Silverlight 4.0 or an earlier version and hence, using the existing published ArchestrA Graphics would be not correct.
After you upgrade an earlier version of Wonderware Information Server to 5.6 or later, you must reconvert and republish all the existing published ArchestrA Graphics, including ArchestrA Symbols in Table Weaver, using the new ArchestrA Web Exporter.
If you are using Wonderware Information Server with InBatch software, upgrading to Wonderware Information Server 5.6 requires an InBatch hotfix to maintain compatibility. Contact Wonderware customer support to obtain the hotfix.
Once installed, the ArchestrA License Manager can be found in the \Invensys folder on the Start menu rather than in the old License Utility folder, \Wonderware\Common.
Wonderware Information Server 2014 R2 supports using a centralized licensing server to manage client licenses. For more information, see the Invensys License Manager Guide and the license server documentation in the \InstallFiles\CD-Licensing\UserDocs folder of the Wonderware Information Server 2014 R2 installation media.
You can install the License Server as part of any Wonderware System Platform installation. If you install Wonderware Information Server, the License Server automatically installs whether or not you specifically selected it for installation.
Configure your antivirus software to prevent archive files from being scanned.
Important Note: The paths listed here may be different based on your installation. If you are using Wonderware Historian, be sure to exclude any folder that contains history blocks.
- Exclude the files in the lowest level subfolder of the listed directories in this section. Antivirus exclusions should not be recursive and should only apply to the lowest listed subfolder in the specified folder path.
- If you are using a 64-bit operating system, folder names must be specified accordingly. For example, the program files root directory in a 64-bit operating system is C:\Program Files (x86)\... and the application data root directory in a 64-bit operating system is C:\ProgramData\...
Exclude these ArchestrA folders in a 32-bit system:
- C:\ProgramData\ArchestrA\ and all subfolders
- C:\Program Files\ArchestrA\
- C:\Program Files\Common Files\ArchestrA\
- C:\Program Files\FactorySuite\ (The FactorySuite folder may not exist in newer installations)
- C:\Program Files\Wonderware\
- C:\Documents and Settings\All Users\Application Data\Wonderware
- C:\Users\All Users\Applications
Exclude these ArchestrA folders in a 64-bit system:
- C:\ProgramData\ArchestrA\ and all subfolders
- C:\Program Files\Common Files\ArchestrA
- C:\Program Files (x86)\ArchestrA\
- C:\Program Files (x86)\Common Files\ArchestrA\
- C:\Program Files (x86)\FactorySuite\ (The FactorySuite directory may not exist in newer installations)
- C:\Program Files (x86)\Wonderware\
- C:\Users\All Users\Wonderware
Exclude these folders:
- History Store Forward directory in a 32-bit system:
- C:\Documents and Settings\All Users\Application Data\ArchestrA\ (default location)
- History Store Forward directory in a 64-bit system:
- C:\Users\All Users\ArchestrA\ (default location)
- Checkpoint directory location default location in a 32-bit system:
- C:\Program Files\ArchestrA\Framework\bin
- Checkpoint directory location default location in a 64-bit system:
- C:\Program Files (x86)\ArchestrA\Framework\bin
- InTouch HMI Application folder path:
- C:\Documents and Settings\All Users\Application Data\ArchestrA\
- SMC Logger Storage file path:
- C:\Documents and Settings\All Users\Application data\Archestra\LogFiles\
Exclude these folders for Wonderware Information Server:
- c:\Program Files\Wonderware\SuiteVoyager
Exclude these files from the C:\Windows\Temp folder:
SQL Server database files are located in:
- C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA
- Exclude SQL Server database files within this directory of the following types:
Exclude these additional file types if you wish:
This section documents important resolved issues broadly categorized as Wonderware System Platform-level issues. This list is not comprehensive. Additional resolved issues are documented in the product-specific Readme files.
|L00122615:||The QI Analyst 8.0 SP2 link to the Historian Server broke if Historian Client was installed on the same system.|
|L00129565:||If InTouch Access Anywhere Server was selected from the Feature Customization screen, the Runtime documentation and the InTouch supplementary documentation were not installed on the system.|
The following important known issues are listed by their assigned CR number in ascending order. Additional known issues are documented in the product-specific Readme files.
- Installation Issues
- Upgrade and Migration Issues
- ArchestrA Service Bus and Multi-Galaxy Communication Issues
- ArchestrA Alarm Control Issues
Wonderware Information Server was installed but was never
configured, and you then attempt to uninstall any Wonderware
System Platform product, the following error occurs: "The
program can't start because ivfw.dll is missing from your
computer. Try reinstalling the program to fix this problem."
To resolve this issue, configure Wonderware Information Server. You will then be able to uninstall the other products.
|L00114588:||You must manually install the language packs for the Wonderware Historian Client product by running the setup.msi file in the appropriate subfolder of the following folder of the Wonderware System Platform DVD: ...\Wonderware System Platform\CD-HistorianClients\HistorianClient\Lang\.|
|L00114910:||On a computer running the Windows Server 2008 R2 or Windows 7 (64-bit) operating system, a blank domain is shown in Admin User Page when you clear the Create Local Account check box. This behavior is a result of the browser service being disabled by default on the computer running the Windows Server 2008 R2 or Windows 7 (64-bit) operating system.|
|L00116883:||Due to a Windows operating system issue, Wonderware InTouch HMI and related applications, such as Alarm DB Logger, can crash on startup if installed to a drive other than C:\. As a workaround, create an empty file named win.ini in folder C:\Users\<username>\AppData\Local\Wonderware where "username" is the name of the user attempting to start the application.|
|L00120356:||Creating a new graphic toolset, or creating a new symbol in an existing toolset, from the Graphic Toolbox in the IDE can result in errors in the logger if Wonderware Intelligence 1.5 is also installed. Creating a new symbol directly under the galaxy rather than from the Graphic Toolbox does not result in logger errors. Functionality is not impacted, and the logger errors can be ignored.|
|L00123209:||When installing Wonderware System Platform, the system cannot read the Wonderware Application Server license if the Galaxy Repository and the IDE are installed on a node where Wonderware InBatch or other Invensys products are already installed. As a workaround, use the License Manager to reinstall the ArchestrA license for Application Server after the Wonderware System Platform installation is complete.|
|L00128943:||While installing Wonderware System Platform, if the logged-on user (the installer) is not a SQL Server administrator, the Config SQL dialog box appears and requests SQL Server administrator credentials. If invalid credentials are entered multiple times before valid credentials are entered, the Application Server installation will fail, prompting for a CD location - even though the CD location is already available - and post-installation ArchestrA Service Bus configuration steps also will fail. As a workaround, uninstall any System Platform components already installed, then reinstall Wonderware System Platform. Enter correct SQL Server administrator credentials when requested.|
|L00130063:||SR 103130498: If the Wonderware.opt file has been deleted, the system will behave erratically.
To resolve this issue, re-install the Wonderware.opt file by executing the program repair option for License Manager or Application Server. You can launch repair from either from the Windows control panel or from the Wonderware System Platform 2014 R2 installation DVD.
|L00133121:||SR 10417637: Installing Wonderware Application Server 2014 Patch 01 with Struxureware Power Monitoring Expert version 7.2 results in a port conflict that can cause Application Server (ArchestrA IDE) to stop working. As a workaround, specify a different port for the aaGR service as follows:
|L00133523:||If you upgrade ArchestrA System Platform 2012, ArchestrA System Platform 2012 R2, and Wonderware System Platform 2014 to Wonderware System Platform 2014 R2 and if you navigate back from the dynamic pre-requisite screen (or further) to the Wonderware Information Server readiness checkness screen, the Next button is not available in that screen and you cannot proceed with the upgrade.
This is due to the fact that by the time the Back navigation was initiated, the MS-SQL Server was already stopped by the upgrade process, resulting in a validation process failure.
Workaround: You must cancel the installation, restart the SQL Server and relaunch the install.
Multi-galaxy communication does not work on a computer where Application Server and the Historian have been uninstalled and Application Server has been reinstalled. When you uninstall Application Server, the ArchestrA Services (ASBService) database is not deleted from the system. This means that any existing galaxy pairings will persist when you reinstall Application Server on the same system. The persistent pairing information is automatically available after the reinstallation. Because the uninstall operation stops SQL Server, the ASBService user and permissions are not deleted from SQL Server. Pairing information can be out of date and multi-galaxy operations not working as the Discovery Service information is lost in the transition from uninstall to install. To resolve out-of-date database information, you must delete the ASBServices user from SQL Server before re-installing, and you must un-pair and re-pair to the required galaxies after performing uninstall and re-install operations on the same node.
|L00123462:||In a multi-galaxy environment, you can pair galaxies by IP address rather than using a node name (computer machine name). Unpairing galaxies identified by IP address fails when NetBIOS and DNS solutions are unavailable. Where your galaxies are identified by IP address, you must create a temporary host file to map the IP addresses as hostnames for purposes of unpairing.
For example, Node1 and Node2 are identified by IP address and are paired. To unpair them, do the following:
|L00123474:||Writing from InTouch to a remote galaxy using indirect tags can fail for some of the remote references. Object Viewers on two different nodes may show different values for the same reference. You can avoid this issue by deactivating Advanced Communication Management in the IDE. Additionally, if you use the same indirect tag with scripting more than one time, you can modify your scripts to set the indirect tag's name property to an empty string after the loop completes. For example, in the following script snippet, you would add the line highlighted with bold text:
|L00123475:||When configuring user-configurable ArchestrA Services - ASBGRBrowsing service, ASBMxDataProvider service, and ASBAuthorization service - it is important not to assign the same port number to two instances of a service on the same node. However, it can occur that while creating instances of a service and assigning them to the same node, that the system can erroneously assign a duplicate port number by default. The main symptom of this error is that you do not see a remote galaxy where expected, such as in a list of available galaxies in the Galaxy Browser. As a first step in troubleshooting this problem, do the following:
|L00125223:||If you create galaxies on separate nodes, with Wonderware System Platform 2014 R2 IDE installed on one node and Wonderware System Platform 2012 R2 IDE installed on a second node, then pair them for multi-galaxy communication, you will be able to browse galaxy attributes from the 2014 IDE to the 2012 R2 IDE, but not from the 2012 R2 IDE to the 2014 IDE. Installing Wonderware System Platform 2012 R2 Patch 01 on the second node resolves the issue.|
|L00133534:||Undeploying a galaxy with Object Viewer active will cause Object Viewer to shut down with an informational message that requires acknowledgement (click OK) to complete the shutdown. In a multi-galaxy configuration, with Object Viewer open, undeploying a paired Galaxy, then redeploying the galaxy without properly shutting down Object Viewer, can cause ASB services to fail to reconnect to the redeployed galaxy. To avoid this condition, click OK to shut down Object Viewer before redeploying the galaxy.|
|L00134322:||The ASBGRBrowsing service is used for browsing objects and attributes on the local Galaxy, as well as for browsing in multi-galaxy environments. If you undeploy the ASBGRBrowsing service, browsing in the local Galaxy will result in error messages in the SMC similar to the following: "GRBrowseServiceAdapter Connected Failed".|
If you create a filter for a history block query that results in no matches, "Not Connected" appears in the status bar and a warning is logged to the ArchestrA Logger. The status bar should show "Connected" even though no matches are returned.
The Wonderware System Platform documentation is available Adobe Acrobat .pdf files that are available from the following locations on the Wonderware System Platform DVD:
\Wonderware System Platform\CD-ApplicationServer\UserDocs\English
\Wonderware System Platform\CD-Historian-x64\UserDocs\English
\Wonderware System Platform\CD-HistorianClients\HistorianClient\Docs
\Wonderware System Platform\CD-Intouch\UserDocs\English
\Wonderware System Platform\CD-WIS\UserDocs\English
To view the documentation, you must first download the latest version of Adobe Reader from the Adobe Corporation web site: http://www.adobe.com/products/acrobat/readstep2.html.
You can also access online Help systems from within the software.
- Common Components and Utilities User Documentation
- Wonderware InTouch HMI
- Wonderware Application Server
- Wonderware Historian Server
- Wonderware Historian Client
- Wonderware Information Server
- Documentation Issues
- Wonderware System Platform Installation Guide. This guide provides information on installing the Wonderware System Platform, including hardware and software requirements and migration instructions.
- Log Viewer User's Guide. Explains how to use the Log Viewer utility to determine system diagnostics.
- Log Flag Editor Utility Guide. Explains how to turn on and off certain diagnostics logging messages.
- Invensys License Manager Guide. Explains how to install and manage product licenses.
- Wonderware ArchestrA Protocol Guide. Explains background information on the main protocols used between components of Wonderware products.
- InTouch HMI Concepts and Capabilities Guide. Describes all of the features and main concepts in the InTouch HMI without going too deep into the technical and procedural details.
- InTouch Modern Application Guide. Describes the tasks to manage Modern applications from Application Manager and configure Modern applications from WindowMaker.
- The InTouch HMI Application Management and Extension Guide. Describes how to create and manage InTouch applications locally and in a network environment.
- InTouch HMI Data Management Guide. Describes how to work with data items in the InTouch HMI and connect your application to the physical devices in your plant environment.
- InTouch HMI Visualization Guide. Describes how to develop the graphical operator interface of an InTouch application.
- InTouch HMI SmartSymbols Guide. Describes how to create reusable templates for graphic symbols that can save you a lot of engineering time and effort.
- InTouch HMI and ArchestrA Integration Guide. Describes how to integrate the InTouch HMI and ArchestrA technology to develop more robust applications that use richer graphics.
- InTouch HMI Alarms and Events Guide. Describes how to configure alarms for your data items, how to view and acknowledge alarms, and how to use the alarm clients and utilities supplied with the InTouch HMI.
- InTouch HMI Scripting and Logic Guide. Describes how to write scripts in the InTouch HMI to automate common tasks and processes. This guide includes a reference of the InTouch scripting language and functions.
- InTouch HMI Supplementary Components Guide. Describes software components that you can optionally install and use with the InTouch HMI.
- Wonderware Application Server User's Guide. Explains configuring and deploying Wonderware Application Server applications.
- Creating and Managing ArchestrA Graphics User's Guide. Explains how you create and manage graphical symbols using the ArchestrA Symbol Editor within the Integrated Development Environment (IDE).
- Wonderware Application Server Scripting Guide. Reference for the scripting language in Wonderware Application Server.
- Object Viewer User's Guide. Explains how to acquire run-time data using the Object Viewer.
- Guide to the ArchestrA Alarm Control. Explains how to configure the alarm control (client) to show current and historical alarms and events in a grid.
- Guide to the ArchestrA Trend Client. Explains how to configure a chart to trend real-time data values.
- Platform Manager User's Guide. Explains how to start and stop system components.
- Galaxy Database Manager User's Guide. Explains how to backup and restore the Galaxy database.
- Wonderware InTouch HMI and ArchestrA Integration Guide. Explains how you can use the ArchestrA Integrated Development Environment (IDE) to manage InTouch HMI applications so that you can use symbols you create in the ArchestrA Symbol Editor.
- Wonderware Historian Concepts Guide. Provides an overview of the entire Wonderware Historian system and describes each of the subsystems in detail.
- Wonderware Historian Administration Guide. Describes how to administer and maintain an installed Wonderware Historian, such as, configuring data acquisition and storage, managing security, configuring replication, and monitoring the system.
- Wonderware Historian Database Reference. Provides documentation for all of the Wonderware Historian database entities, such as, tables, views, and stored procedures.
- Wonderware Historian Glossary. Provides definitions for terms used throughout the documentation.
- Wonderware Historian Client Software User's Guide Describes how to use stand-alone applications, Microsoft Office add-ins, and ActiveX and .NET controls to retrieve and display data.
- Wonderware Information Server Administration Guide. Describes how to administer and maintain a Wonderware Information Server, including configuring data sources, managing security, and performing customizations.
- Wonderware Information Server Win-XML Exporter Guide. Describes how to use the Win-XML Exporter to convert InTouch HMI application windows to web pages and publish them to the Wonderware Information Server. This guide also includes a section for designing InTouch HMI application windows for Wonderware Information Server. This section describes how to best design InTouch HMI windows so that they can be successfully converted and optimally viewed in the portal.
- ArchestrA Web Exporter Guide. Describes how to use the ArchestrA Web Exporter to publish ArchestrA Symbols and InTouch HMI Windows to Wonderware Information Server. This guide also describes how to add, delete and modify WindowSets and SymbolWeaverSets of the project and preview them in the preview window of ArchestrA Web Exporter.
- ActiveFactory for Wonderware Information Server Help. Describes how to use the ActiveFactory for Wonderware Information Server web portal to view a variety of reports that include data from Wonderware Historians.
- ArchestrA License Manager Guide. Describes the ArchestrA License Manager and how to use it to install and manage licenses and license servers on local and remote computers.
© 2014 Invensys Systems, Inc. All Rights Reserved.
Invensys is a Schneider Electric company.