System Platform 2014 R2
Материал из archestra.info
Версия от 11:57, 4 мая 2015; Admin (обсуждение | вклад)
<body style="" alink="#0000ff" bgcolor="#ffffff" link="#0000ff" vlink="#800080">
<basefont size="12" face="verdana, arial, tahoma, helvetica"> <div style="text-align: center;"></div> <h1 class="center">Wonderware System Platform 2014 R2 Readme</h1> <p>Last revision: 11/20/2014</p> <p>This document contains important information about Wonderware<sup>®</sup> System Platform 2014 R2, which includes the following products:</p>
<li>Wonderware InTouch HMI 2014 R2 (v11.1)
</li>
<li>Wonderware Application Server 2014 R2 (v4.1)
</li>
<li>
Wonderware Historian Server 2014 R2 (v11.6)
</li>
<li>
Wonderware Historian Client 2014 R2 (v10.6)
</li>
<li>
Wonderware Information Server 2014 R2 (v5.6)
</li>
<p>Use the following links to navigate this Readme file:</p>
<ul>
<li><a title="Click this link to view the information." href="#About_This_Release">About This Release</a></li>
<li><a title="Click this link to view the information." href="#System_Requirements">System Requirements and Guidelines</a></li>
<li><a title="Click this link to view the information." href="#Component_Compatibility">Wonderware Product Compatibility</a></li>
<li><a title="Click this link to view the information." href="#Installation_Notes">Wonderware System Platform Installation</a></li>
<li><a title="Click this link to view the information." href="#Upgrade_Migration">Wonderware System Platform Upgrade and Migration</a></li>
<li><a title="Click this link to view the information." href="#Licensing_Info">Licensing Information</a></li>
<li><a title="Click this link to view the information." href="#Antivirus_Software_Exclusions">Antivirus Information</a></li>
<li><a title="Click this link to view the information." href="#Resolved_Issues">Resolved Issues</a></li>
<li><a title="Click this link to view the information." href="#Known_Issues">Known Issues</a></li>
<li><a title="Click this link to view the information." href="#Documentation">Documentation</a></li>
</ul>
<p>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.</p>
<ul>
<li><a href="Readme_IT/Readme.html" target="_blank" title="InTouch">Wonderware
InTouch HMI Readme</a> </li>
<li><a href="Readme_AppSvr/Readme.html" target="_blank" title="Application Server">Wonderware
Application Server Readme</a> </li>
<li><a href="Readme_historian/Readme.html" target="_blank" title="Historian">Wonderware
Historian Server Readme</a> </li>
<li><a href="Readme_HistClient/Readme.html" target="_blank" title="Historian Client">Wonderware
Historian Client Readme</a> </li>
<li><a href="Readme_WIS/Readme.html" target="_blank" title="Information Server">Wonderware
Information Server Readme</a></li>
</ul>
You can find readme files for previous product releases at <a href="http://wdn.wonderware.com/Downloads">Wonderware Developers Network (WDN) Downloads.</a> Log in to WDN with your username and password to access the downloads archive.
<h1><a name="About_This_Release"></a>About This Release</h1>
<h3 class="blue">Wonderware System Platform 2014 R2 - General Notes</h3>
<blockquote>
<h4>Invensys License Manager</h4>
<p>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.</p>
<h4>Windows Operating Systems</h4>
<p>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:</p>
<ul>
<li>Windows XP, all versions
<li>Windows Vista, all versions
<li>Windows Server 2003, all versions
<li>Windows Server 2008, non-R2 versions</li>
</ul>
<h4><a name="SPC"></a>Replacing SPC Pro with QI Analyst</h4>
<p>SPCPro<sup>™</sup> 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.</p>
<p class="Note"><b>Important Note:</b> 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.</p>
</blockquote>
<h3 class="blue">Wonderware InTouch HMI 2014 R2</h3>
<blockquote>
<h4>ArchestrA Graphic Toolbox in WindowMaker</h4>
<p>
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.
</p>
<h4>Modern InTouch Applications</h4>
<p>
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.
</p>
<h4>Conversion of InTouch Windows to ArchestrA Symbols</h4>
<p>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.</p>
<p>
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.
</p>
<h4>Additional Situational Awareness Library Symbols</h4>
<p>
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:
</p>
<ul>
<li><b>Alarms</b></li>
<ul>
<li>SA_Alarm_Severity: Shows an alarm summary that includes Alarm Border animation and alarm counts by severity and acknowledgement status.</li>
<li>SA_History_Alarm_Page: Provides a tabbed page to show historical events or alarms by severity over a specified period.</li>
<li>SA_Runtime_Alarm_Banner: Shows alarms by area and includes buttons to acknowledge alarms.</li>
<li>SA_Runtime_Alarm_Page: Provides a tabbed page to show current events or alarms by severity.
</ul>
<li><b>Trends</b></li>
<ul>
<li>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.</li>
<li>SA_MultiTrend: Shows up to four simultaneous trend lines of current and historical measured values.</li>
</ul>
<li><b>Valves</b></li>
<ul>
<li>SA_Valves: Shows a valve symbol with Wizard Options to select discrete or analog two way or three way valves.</li>
</li>
</ul>
</ul>
<h4>Graphic Connectors</h4>
<p>
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.
</p>
<p>
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.
</p>
<p>
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.
</p>
<h4>Historical Statistical Summary Data</h4>
<p>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.</p>
<p>
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.
</p>
<p>
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.
</p>
<h4>Alarm Shelving</h4>
<p>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.
</p>
<p>
Alarm shelving has been incorporated into Alarm Border animation and the ArchestrA Alarm Control.
</p>
<p>
<b>Alarm Border animation</b>
</p>
<p>
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.
</p>
<p>
<b>ArchestrA Alarm Control</b>
</p>
<p>
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.
</p>
<h4>Trend Pen Enhancements</h4>
<p>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.
</p>
<h5>Run-time Scripting</h5>
<p>
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:
</p>
<ul>
<li>MinValue</li>
<li>MaxValue</li>
<li>StartTime</li>
<li>EndTime</li>
<li>PlotType</li>
<li>TimeMode</li>
</ul>
<h5>Fixed and Line Trend Plots</h5>
<p>
The Trend Pen control now includes the <b>Plot Type</b> 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.
</p>
<h5>Trend time Periods</h5>
<p>
The Trend Pen control now includes the <b>Time Period</b> 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.
</p>
<h4>Enhancements to Programmatic Export and Import of ArchestrA Symbols</h4>
<p>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:</p>
<ul>
<li>Overridden text strings</li>
<li>Numeric format styles</li>
<li>DataStatus elements</li>
<li>Trend Pen control</li>
<li>Alarm Client control</li>
<li>Trend Client control</li>
</ul>
<h4>Advanced Number Format Styles</h4>
<p>
The <b>Configure Galaxy Style Library</b> dialog box includes the <b>Format Styles</b> tab with options to individually configure Galaxy-wide number format styles for common types of numbers used in industrial applications. The <b>Format Styles</b> 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 <b>Format Styles</b> dialog box to change the default properties of number styles.
</p>
<p>
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.
</p>
<h4>Remote Application Licensing Support</h4>
<p>
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.
</p>
</blockquote>
<h3 class="blue">Wonderware Application Server 2014 R2 </h3>
<blockquote>
<h4>Attribute Editor</h4>
<p>
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 <i>Wonderware Application Server User's Guide</i>. 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.
</p>
<h4>I/O Auto Assignment</h4>
<p>
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.
</p>
<h4>Alarm Shelving</h4>
<p>
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.
</p>
<p>
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 <b>Alarms and Events Configuration</b> dialog box now includes options to map alarm shelving to alarm severity.
</p>
<h4>Export and Import Galaxy Style Library</h4>
<p>
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.
</p>
<h4>Upgrade Redundant AppEngine Pairs</h4>
<p>
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.
</p>
<h4>Plant State Alarms</h4>
<p>
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 <b>Alarms and Events Configuration</b> dialog box of the ArchestrA IDE. Five plant states are pre-defined, and have default alarm states associated with them.
</p>
<p>
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.
</p>
<p>
During run time, you can change the Plant State and alarm modes using scripts and User Input animation.
</p>
<h4>Browse Attributes with the OPC UA Client Service</h4>
<p>
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:
<br><br>
domain:UAItemReference
<p>
For example, TestServer:PLC01.PLCObject1
</p>
</blockquote>
<h3 class="blue">Wonderware Historian Server 2014 R2</h3>
<ul>
<li>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:
<ul>
<li>Data management can be done using simple operations such as moving, copying, or deleting folders.
<li>Higher storage rates are available.
<li>Storage capacity is only limited by disk space, not by database insertion rates.
<li>You can retrieve alarm and event data using any browser through simple HTTP queries. You can also retrieve the data into an Excel spreadsheet.
</ul>
<h3 class="blue">Wonderware Historian Client 2014 R2</h3>
<ul>
<li>Wonderware Historian Client supports Windows 8.1 and Windows Server 2012 R2 operating systems, and .NET Framework 4.5.1. </li>
<li>Wonderware Historian Client supports data retrieval from the managed Wonderware Online system. For more information, see the <i>Wonderware Historian Client User Guide</i>. </li>
<li>SQLXML is no longer supported.</li>
<li>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.</li>
</ul>
<h3 class="blue">Wonderware Information Server 2014 R2</h3>
<li>Wonderware Information Server supports Windows 8.1 Professional and Windows Server 2012 R2 operating systems, .NET Framework 4.5.1, and security enhancements. </li> <li>Published ArchestrA Symbols can now interact with other web pages to allow for more complete applications. <li>Published ArchestrA Symbols are faster and use updated Microsoft Silverlight components. Note: Previously published ArchestrA Symbols must be republished in order to still operate. <li>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.</li>
<h1><a name="System_Requirements"></a>System Requirements and Guidelines</h1>
<li><a href="#Hardware_Requirements">Hardware Guidelines</a></li> <li><a href="#OS_Reqs">Operating System, Firewall, .NET Framework, and Virtualization Requirements</a></li> <li><a href="#SQL_Server_Reqs">SQL Server Requirements</a></li> <li><a href="#Third_Party_App_Reqs">Third-Party Application Prerequisites</a></li>
<h2><a name="Hardware_Requirements"></a>Hardware Guidelines</h2> <p>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.</p>
<a name="Software_Notes_Common"></a>Software Requirement Notes:
Windows Operating System Notes
<li>The recommended operating systems are Windows 8.1 for client nodes and Windows Server 2012 R2 for server nodes.</li> <li>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.</li> <li>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.</li> <li>Development and application nodes are considered to be clients of the server GR node.</li> <li>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. </li>
.Net Notes
- 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 <a href="#Microsoft.NET_Reqs">.NET Framework Requirements and Compatibility </a>.
<li>.NET 3.5 is installed only because the supported SQL Server versions require it. No other dependencies must exist.</li>
</ul>
SQL Server Notes
<li>The recommended SQL Server version is 2012 SP1 Standard (32/64 bit).</li>
<a name="Firewall"></a>Firewall Notes
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.
<a name="OS_Notes_Common"></a>Operating System Notes: Common for Wonderware Products
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 <a href="http://wdn.wonderware.com/sites/WDN/Pages/Articles/default.aspx"> Wonderware Developers Network (WDN) Library.</a>
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.
<p>When InTouch WindowViewer is started and generates alarms from an
interactive Windows 7, Windows Server 2008 R2, or later desktop
session, an <strong>AlarmViewer</strong> 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 <strong>AlarmViewer</strong> control's alarm query is configured. </p>
<p>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. </p>
<p><b>To configure the AlarmViewer's alarm query</b></p>
<ol>
<li>After starting InTouch WindowViewer (alarm provider) on the Windows 7, Windows Server 2008 R2, or later node,
open the <b>SMC Logger </b>and look for the most recent string
generated by <b>AlarmMgr</b>. 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. </li>
<li>In the <b>Alarm Query </b>tab of the <b>AlarmViewer </b>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: </li>
</ol>
<blockquote>
<blockquote><code>\\<em>nodename</em>:<em>ip_address</em>\intouch!$system</code></blockquote>
</blockquote>
<blockquote>
<blockquote>
<p>where <em>nodename</em> is the name of the node that is providing
the InTouch alarm and <em>ip_address</em> is the IP address that you
determined in step 1. </p>
</blockquote>
</blockquote>
<ol>
<li value="3">Test to validate that the alarms generated from the
alarm-providing node are shown accurately in the <b>AlarmViewer </b>control.</li>
</ol>
<h4><a name="Alarm_DB_Logger">Using Alarm Manager on a Single Node Running Both Wonderware InTouch HMI and Application Server Alarm Providers on Windows Vista and Later Operating Systems</a></h4>
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
<blockquote> <code>\InTouch!$System \Galaxy!Area_001</code> </blockquote> <p>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.</p>
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 <a href="http://wdn.wonderware.com/Downloads">Wonderware Developers Network (WDN) Downloads.</a>
<a name="TerminalServices"></a>Terminal Services Behavior in Windows Server 2008 R2 and Later Operating Systems
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.
<p>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.</p> <p>Refer to the Wonderware InTouch HMI 2014 R2 Readme for further information about InTouch HMI applications running in the Terminal Server Console.</p> <p>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 <b>\\terminalservernode:<IP address>\InTouch!$System</b> to access the alarms, with a colon (:) after the node name. The IP address is that of the client computer connected to the session. </p>
<a name="OS_Notes_InTouch"></a>Operating System Notes: Wonderware InTouch HMI 2014 R2
The following notes are specific to the InTouch HMI 2014 R2 operating system support and requirements.
<li>The recommended operating system for a Galaxy Repository is Windows
Server 2012 R2.</li>
<li>Microsoft Windows 8.1 (32-bit or 64-bit) is the recommended operating
system to run InTouch HMI client components.</li>
<li>Microsoft Windows Server 2012 R2 is the recommended operating system
to run InTouch HMI server components.</li>
<li>The recommended operating system for InTouch HMI development is Windows
Server 2012 R2 or Windows 8.1. </li>
<li>The recommended operating system for run-time nodes is Windows 8.1.</li>
<a name="Using WW IT Windows 7 and Win 2008 R2"></a>Wonderware InTouch HMI 2014 R2 with Windows 7, Windows Server 2008 R2, and Later Operating Systems
<li>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.</li>
<li>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 <a href="#Alarm_DB_Logger">Using Alarm Manager on a Single Node Running Both Wonderware InTouch HMI and Application Server Alarm Providers on Windows Vista and Later Operating Systems</a>.
</li>
<li> Wonderware InTouch HMI 2014 R2 does not support the following legacy script functions on 64-bit systems: WWPoke(), WWExecute(), WWRequest(), ActivateApp() and SendKeys(). </li>
<li>If Recipe Manager is started using the path <b>Start</b>\<b>Program</b>\<b>Wonderware</b>\<b>InTouch\Recipe</b>, then select <strong>Run as Administrator</strong>.</li>
<li>The InTouch Extensibility Toolkit might need to be started by
right-clicking and selecting <strong>Run As Administrator</strong> to function properly.</li>
<li>The onscreen keyboard options have changed for the Windows 7, Windows Server 2008 R2, and later operating systems.</li>
<li>Hovering to select from the Windows keyboard does not work in the
Windows 7, Windows Server 2008 R2, and later operating systems. </li>
<h4><a name="InTouch_DDE_Support"></a>Wonderware InTouch HMI 2014 R2 View Applications and DDE Support</h4> <p>NetDDE is not supported for InTouchView applications. </p> <p>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. </p> <p>In ArchestrA Symbols, <b>InTouch:‹tagname›</b> is still a valid method of referring to an InTouch tag on a local node. </p> <h4><a name="Support_User_Account_Control"></a>Wonderware InTouch HMI 2014 R2 Support for Windows User Account Control</h4> <p>Wonderware System Platform 2014 R2 with InTouch HMI v11.1 supports User Account Control-enabled operations on run-time nodes. <!--You must disable User Account Control (UAC) before installing Wonderware System Platform 2014 and before performing Configurator operations. UAC also must be disabled on IDE and GR nodes.--></p>
<a name="OS_Notes_App_Server"></a>Operating System Notes: Wonderware Application Server
<li>Windows Server 2012 R2 is the recommended operating system for the Galaxy Repository node. </li>
<li>Windows 8.1 is the recommended operating system for Wonderware Application Server development (IDE) or run-time nodes (Bootstrap). </li>
<li>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. </li>
<li>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.</li>
<h4>Wonderware Application Server and DDE Support </h4>
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.
<p>In ArchestrA Symbols, <b>InTouch:<<i>tagname</i>></b> is still a valid method of referring to an InTouch tag on a local node.</p> <h4><a name="Using Wonderware Application Server with Windows 7 and Windows Server 2008 R2"></a>Using Wonderware Application Server with Windows 7, Windows Server 2008 R2, and Later Operating Systems</h4> <p>This section describes specific behaviors and restrictions when using the Windows 7 and Windows Server 2008 R2 operating systems with Wonderware Application Server.</p>
<li>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).
<li>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 <b>Run As
Administrator</b>. </li>
</ul>
<h4>Wonderware Application Server and User Account Control Level</h4>
<p>Wonderware Application Server 2014 R2 supports User Account Control-enabled operations. Starting the IDE still requires elevated privileges.</p>
<h3><a name="OS_Notes_Historian_Server" id="OS_Notes_Historian_Server"></a>Operating System Notes: Wonderware Historian Server</h3>
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.
For example:
- 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.
Workaround:
- Open a command prompt and run the following command: cmd /c reg add HKLM/v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
- Restart the system.
This sets LocalAccountTokenFilterPolicy registry entry value to 1. In doing so, an elevated token for the user is generated.
<h3><a name="OS_Notes_Historian_Client" id="OS_Notes_Historian_Client"></a>Operating System Notes: Wonderware Historian Client </h3> <p>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. </p> <h3><a name="OS_Notes_Info_Server"></a>Operating System Notes: Wonderware Information Server</h3> <p>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. </p>
<a name="Microsoft.NET_Reqs" id="Microsoft.NET_Reqs"></a>.NET Framework Requirements and Compatibility
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. <p> 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. <p> 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. <p> 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:
<p><code>BinaryReader streamReader = new BinaryReader(ms, new ASCIIEncoding());</code></p>
To learn more about changes introduced in .NET Framework 4.5.1, refer to the following Microsoft resources:
<tbody> <tr> <td style="text-align: left; vertical-align: top;" colspan="2" width="450" rowspan="1">What's New in the .NET Framework 4.5.1:</td> <td style="text-align: left; vertical-align: top; width: 800px" colspan="2" rowspan="1"><a href="http://msdn.microsoft.com/en-us/library/ms171868(v=vs.110).aspx">http://msdn.microsoft.com/en-us/library/ms171868%28v=vs.110%29.aspx</a> </td> </tr> <tr> <td style="text-align: left; vertical-align: top;" colspan="2" width="450" rowspan="1">What's obsolete in the .NET Framework class library:</td> <td style="text-align: left; vertical-align: top; width: 800px" colspan="2" rowspan="1"><a href="http://msdn.microsoft.com/en-us/library/ee461502(v=vs.100).aspx">http://msdn.microsoft.com/en-us/library/ee461502(v=vs.100).aspx</a> </td> </tr> <tr> <td style="text-align: left; vertical-align: top;" colspan="2" width="450" rowspan="1">Migration Guide to the .NET Framework 4.5.1:</td> <td style="text-align: left; vertical-align: top; width: 800px" colspan="2" rowspan="1"><a href="http://msdn.microsoft.com/en-us/library/ff657133(v=vs.110)">http://msdn.microsoft.com/en-us/library/ff657133(v=vs.110)</a> </td> </tr> <tr> <td style="text-align: left; vertical-align: top;" colspan="2" width="450" rowspan="1">.NET Framework 4 Migration Issues:</td> <td style="text-align: left; vertical-align: top; width: 800px" colspan="2" rowspan="1"><a href="http://msdn.microsoft.com/en-us/library/ee941656%28v=vs.100%29">http://msdn.microsoft.com/en-us/library/ee941656%28v=vs.100%29</a> </td> </tr> </tbody>
<a name="Virtualization_Reqs"></a>Virtualization Host Support
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
<a name="SQL_Server_Reqs"></a>SQL Server Requirements
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).
<p>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.</p>
<p>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. </p>
<h3>Considerations for SQL Server </h3>
<ul>
<li><b>Alarm DB Logger</b> To use the Alarm DB Logger with SQL Server Express, you need to change the default authentication mode from Windows-based to Mixed Mode.</li>
<li><b>SQL Server Configuration Rights:</b> <a name="SQLServerBUILTINAdministratorsRole"></a>While installing Wonderware System Platform, if the logged-on user performing the installation is not a SQL Server administrator, the <B>Config SQL</b> dialog box appears and requests SQL Server administrator credentials.</li>
<li><b>Maximum Server Memory:</b> 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.</li>
<li><b>Restoring a CAB:</b> 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. </li>
<li>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.</li>
<li><b>Migrating SQL Server Versions:</b> 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:</li>
<blockquote>
<ul>
<li><a HREF="http://msdn.microsoft.com/en-us/library/bb677622.aspx" target="blank">Upgrade to SQL Server 2014</a></li>
<li><a HREF="http://blogs.technet.com/b/mdegre/archive/2012/06/15/migration-sql-server-2000-to-sql-server-2012.aspx" target="blank">Migrate SQL Server 2000 to SQL Server 2012</a></li>
<li><a HREF="http://msdn.microsoft.com/en-us/library/bb677619%28v=sql.105%29.aspx" target="blank">Migrating to SQL Server 2008 R2</a></li>
<li><a HREF="http://msdn.microsoft.com/en-us/library/bb677619%28v=sql.100%29.aspx" target="blank">Migrating to SQL Server 2008</a></li>
<li><a HREF="http://blogs.msdn.com/b/ai/archive/2012/08/09/migrating-sql-server-2000-user-databases-to-sql-server-2012.aspx" target="blank"> T-SQL scripts to migrate SQL server 2000 user databases to SQL server 2012</a>
<li><a href="http://msdn.microsoft.com/en-us/library/bb510680.aspx" target="blank">ALTER DATABASE Compatibility Level (Transact-SQL) SQL Server 2012</a></li>
<li><a href="http://msdn.microsoft.com/en-us/library/bb510680(v=sql.105).aspx" target="blank">ALTER DATABASE Compatibility Level (Transact-SQL) SQL Server 2008 R2</a> </li>
</ul>
</blockquote>
<li>Run the Change Network Utility from the Windows Start menu.</li> <li>Run the aaConfig SQL Utility from the Windows Start menu.</li>
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.
</li> </ul> </ul>
<h3>Considerations for SQL Server Express</h3>
<li>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.</li>
<li>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:</li>
<li>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.</li>
<li>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.</li>
<li>The computing capacity of SQL Server 2012 SP1 Express is limited to the lesser of one CPU socket or four processor cores.</li>
</ul>
<li>No version of SQL Server is installed on the computer at the time of installation.</li>
<li>You select only the <b>InTouch Development and Runtime</b> Wonderware System Platform installation option. When you select <b>InTouch Development and Runtime</b>, a Galaxy Repository will be installed. </li>
<!--<li>If you select the <b>InTouch Development and Runtime</b> feature for installation or upgrade, and your system was installed with the earlier version of SQL Server 2008 Express installed as part of Wonderware System Platform 2012 R2, the following conditions apply:
<ul>
<li>The Wonderware System Platform 2014 installation <b>Product-specific Prerequisites</b> dialog states <b>SQL Server 2008(x86) SP3 Std/Ent (SQL Express 2008 R2 SSME for InTouch Dev only)</b> is a prerequisite for the Galaxy Repository feature, but the <b>Install Prerequisites</b> button is disabled.
<li>To resolve this condition, you must exit the installation program, install SQL Server 2008 R2 SP1 32-bit Express-SSME, then resume the installation.
<li>To do this, you can run the SQL Server 2008 Express installation from the following Wonderware System Platform 2014 DVD media folder path: <br>
<b><Wonderware System Platform 2014 DVD>:\InstallFiles\Redist\SQL2K8R2SSMSE\SQLEXPRWT_x86_ENU.exe</b> </li>-->
</ul>
<a name="SQL_Server_Notes_App_Server"></a>Additional SQL Server Notes for Wonderware Application Server
<ul style="LIST-STYLE-TYPE: disc">
<li>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.</li>
<li>The Galaxy Repository locks the SQL Server maximum memory usage
to 65% of the computer's physical memory. </li>
<li>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. </li>
<li>To use the Alarm DB Logger with SQL Server Express, you
need to change the default authentication mode from Windows-based to Mixed Mode. </li>
<a name="SQL_Server_Notes_Info_Server"></a>Additional SQL Server Notes for Wonderware Information Server
<li>Named instances are not supported.</li> <li>Wonderware Information Server supports case-insensitive and case-sensitive SQL Servers.</li>
<a name="Third_Party_App_Reqs"></a>Third-Party Application Prerequisites
<p>For Wonderware Historian Client:</p>
<ul>
<li>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.</li>
<li>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. <b>Note</b>: Make sure that you are not using the Microsoft Office 2013 (64-bit) version.<br>
</li>
</ul>
<p>For Wonderware Information Server:</p>
<a name="Component_Compatibility"></a>Wonderware Product Compatibility
<p><b>In a single-node environment</b>, 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.<br>
<br>
<b>In a node-to-node environment</b>, products are compatible
between the current licensed version and one licensed version
back. </p>
<p> 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.
<table style="text-align: left;" border="1" cellpadding="2" cellspacing="2" width="700">
<tbody>
<tr>
<td width="370" class="colhead">Product</td>
<td width="130" class="colhead">Version</td>
<td width="100" class="colhead">Compatibility</td>
<td width="100" class="colhead">Co-existence</td>
</tr>
<tr>
<td class="rowhead" rowspan="8">Wonderware
System Platform</td>
<td class="cell" style="TEXT-ALIGN: left">4.5</td>
<td class="supportednotSmall">N</td>
<td class="supported">N/A</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">2012</td>
<td class="supportedSmall">Y</td>
<td class="supported">N/A</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">2012 R2</td>
<td class="supportedSmall">Y</td>
<td class="supported">N/A</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">2012 R2 P01</td>
<td class="supportedSmall">Y</td>
<td class="supported">N/A</td>
<tr>
<td class="cell" style="TEXT-ALIGN: left">2012 R2 P02</td>
<td class="supportedSmall">Y</td>
<td class="supported">N/A</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">2012 R2 P03</td>
<td class="supportedSmall">Y</td>
<td class="supported">N/A</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">2014</td>
<td class="supportedSmall">Y</td>
<td class="supported">N/A</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">2014 P01</td>
<td class="supportedSmall">Y</td>
<td class="supported">N/A</td>
</tr>
<tr>
<td class="rowhead">Wonderware
InTouch CE</td>
<td class="cell" style="TEXT-ALIGN: left">10.1</td>
<td class="supportednotSmall">N</td>
<td class="supportednotSmall">N</td>
</tr>
<tr>
<td class="rowhead" rowspan="4">Wonderware
Manufacturing Execution System</td>
<td class="cell" style="TEXT-ALIGN: left">4.0 SP1</td>
<td class="supportednotSmall">N</td>
<td class="supportednotSmall">N</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">4.0 SP2</td>
<td class="supportednotSmall">N</td>
<td class="supportednotSmall">N</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">4.5 (2012) P01</td>
<td class="supportedSmall">Y</td>
<td class="supportedSmall">Y</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">5.0 (2014)</td>
<td class="supportedSmall">Y</td>
<td class="supportedSmall">Y</td>
</tr>
<tr>
<td class="rowhead">Wonderware
InControl™</td>
<td class="cell" style="TEXT-ALIGN: left">7.11 SP2 P01</td>
<td class="supportednotSmall">N</td>
<td class="supportednotSmall">N</td>
</tr>
<tr>
<td class="rowhead">Wonderware
Manufacturing Execution Module</td>
<td class="cell" style="TEXT-ALIGN: left">1</td>
<td class="supportedSmall">Y</td>
<td class="supportednotSmall">N</td>
</tr>
<tr>
<td class="rowhead" rowspan="2">Wonderware
InBatch™ <br><br>* <span style="font-weight:normal; font-size:11">
If you are using Wonderware Information Server with InBatch software, upgrading to Wonderware
Information Server 5.6 requires an InBatch hotfix to maintain compatibility.</span></td>
<td class="cell" style="TEXT-ALIGN: left">10.0 (2012 R2)</td>
<td class="supportednotSmall">N</td>
<td class="supportednotSmall">N</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">10.1 (2014)</td>
<td class="supportedSmall">Y *</td>
<td class="supportedSmall">Y *</td>
</tr>
<tr>
<td class="rowhead" rowspan="3">Wonderware
QI Analyst™</td>
<td class="cell" style="TEXT-ALIGN: left">8.0 SP1 P01</td>
<td class="supportednotSmall">N</td>
<td class="supportednotSmall">N</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">8.0 SP2</td>
<td class="supportedSmall">Y</td>
<td class="supportedSmall">Y</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">8.0 SP3</td>
<td class="supportedSmall">Y</td>
<td class="supportedSmall">Y</td>
</tr>
<tr>
<td class="rowhead">Wonderware
SCADAlarm™</td>
<td class="cell" style="TEXT-ALIGN: left">6.0 SP2 P01</td>
<td class="supportednotSmall">N</td>
<td class="supportednotSmall">N</td>
</tr>
<tr>
<td class="rowhead" rowspan="2">Wonderware
Intelligence</td>
<td class="cell" style="TEXT-ALIGN: left">1.5</td>
<td class="supportednotSmall">N</td>
<td class="supportednotSmall">N</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">1.5.100 (2012)</td>
<td class="supportedSmall">Y</td>
<td class="supportedSmall">Y</td>
</tr>
<tr>
<td class="rowhead" rowspan="5">ArchestrA
Workflow™</td>
<td class="cell" style="TEXT-ALIGN: left">1.5 (2012)</td>
<td class="supportednotSmall">N</td>
<td class="supportednotSmall">N</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">1.6 (2012 SP1)</td>
<td class="supportednotSmall">N</td>
<td class="supportednotSmall">N</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">1.7 (2012 R2)</td>
<td class="supportednotSmall">N</td>
<td class="supportednotSmall">N</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">1.8</td>
<td class="supportednotSmall">N</td>
<td class="supportednotSmall">N</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">1.9 (2012 R2 SP1)</td>
<td class="supportednotSmall">N</td>
<td class="supportednotSmall">N</td>
</tr>
<tr>
<td class="rowhead">Wonderware
Skelta BPM</td>
<td class="cell" style="TEXT-ALIGN: left">2014</td>
<td class="supportednotSmall">N</td>
<td class="supportednotSmall">N</td>
</tr>
<tr>
<td class="rowhead">Wonderware
PEM</td>
<td class="cell" style="TEXT-ALIGN: left">2.1 SP1</td>
<td class="supportedSmall">Y</td>
<td class="supportedSmall">Y</td>
</tr>
<td class="rowhead">Wonderware Online (see components below)</td>
<td class="cell" style="TEXT-ALIGN: left">1.0</td>
<td class="graySmall" style="font-weight: normal; font-size: 0.6em; text-align: center;"> </td>
<td class="graySmall" style="font-weight: normal; font-size: 0.6em; text-align: center;"> </td>
</tr>
<tr>
<td class="rowhead"><ul><li>Historian Client Trend</li></ul></td>
<td class="cell" style="TEXT-ALIGN: left">10.6</td>
<td class="supportedSmall">Y</td>
<td class="supportedSmall">Y</td>
</tr>
<tr>
<td class="rowhead"><ul><li>InTouch</li></ul></td>
<td class="cell" style="TEXT-ALIGN: left">11.0 and 11.1</td>
<td class="supportedSmall">Y</td>
<td class="supportedSmall">Y</td>
</tr>
<tr>
<td class="rowhead"><ul><li>MRC (Mobile Report Connector)</li></ul></td>
<td class="graySmall" style="font-weight: normal; font-size: 0.6em; text-align: center;"> </td>
<td class="supportedSmall">Y</td>
<td class="supportedSmall">Y</td>
</tr>
<tr>
<td class="rowhead" rowspan="2">Recipe Manager Plus
PEM</td>
<td class="cell" style="TEXT-ALIGN: left">1.0 (2014)</td>
<td class="supportedSmall">Y</td>
<td class="supportedSmall">Y</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">1.5 (2014 R2)</td>
<td class="supportedSmall">Y</td>
<td class="supportedSmall">Y</td>
</tr>
<tr>
<td class="rowhead " rowspan="3">Schneider Electric Citect-VJC</td>
<td class="cell" style="TEXT-ALIGN: left">7.2 SP3</td>
<td class="supportedSmall">Y</td>
<td class="supportedSmall">Y</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">7.3 SP3</td>
<td class="supportednotSmall">N</td>
<td class="supportedSmall">Y</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">7.4 SP1</td>
<td class="supportedSmall">Y</td>
<td class="supportedSmall">Y</td>
</tr>
<tr>
<td class="rowhead" rowspan="4">Schneider Electric ClearSCADA</td>
<td class="cell" style="TEXT-ALIGN: left">CS 2013 R1</td>
<td class="supportednotSmall">N</td>
<td class="supportedSmall">Y</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">CS 2013 R2</td>
<td class="supportednotSmall">N</td>
<td class="supportedSmall">Y</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">CS 2014 R1</td>
<td class="supportednotSmall">N</td>
<td class="supportedSmall">Y</td>
</tr>
<tr>
<td class="cell" style="TEXT-ALIGN: left">CS 2015 R1</td>
<td class="supportedSmall">Y</td>
<td class="supportedSmall">Y</td>
</tr>
</tbody>
Notes:
<ul>
<li>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. </li>
<li> HTTP access to Historian Server is not
supported in this version. </li>
<li>Publishing from ActiveFactory 9.2, Historian Client 10.0, 10.0
SP1, and 10.0 SP2 is
supported. </li>
<li>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. </li>
<li>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. </li>
<li>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. </li>
<li>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.
</ul>
<p>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. </p>
<a name="Installation_Notes" id="Installation_Notes"></a>Wonderware System Platform Installation
<p>For detailed installation instructions in English, see the <i>Wonderware System Platform Installation
Guide</i> (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.
<br>
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.</p>
<a name="Before_Install"></a>Before Installing Wonderware System Platform 2014 R2
<li>Installing Wonderware System Platform 2014 R2 on a computer used
as a domain controller is not supported. For more information,
see <a href="http://technet.microsoft.com/library/Cc966456" target="_blank">
http://technet.microsoft.com/library/Cc966456. </a> </li>
<li>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
<p>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. </p>
<p><b>WARNING!</b> 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. </p>
<p>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.
</p>
<p>If you choose to use existing user account, it should meet the
following requirements:</p>
<ul>
<li>User account with a permanent password that does not expire. </li>
<li>User account in which the password cannot be changed. </li>
<li>User account that is a member of the local Administrators
group.
</li>
</ul>
<p>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.</p>
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.
<a name="Upgrade_Migration"></a>Wonderware System Platform Upgrade and Migration
<li><a href="#Upgrade_Migration_Notes">Wonderware System Platform Upgrade and Migration Notes</a></li> <li><a href="#AppServer_Upgrade_Notes">Application Server Upgrade and Migration Notes</a></li> <li><a href="#InTouch_Upgrade_Notes">InTouch and InTouch Access Anywhere Upgrade and Migration Notes</a></li> <li><a href="#Historian_Upgrade_Notes">Wonderware Historian Upgrade and Migration Notes</a></li> <li><a href="#Client_Upgrade_Notes">Wonderware Historian Client Upgrade and Migration Notes</a></li> <li><a href="#WII_Upgrade_Notes">Wonderware Information Server Upgrade and Migration Notes</a></li> </ul>
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.
</p>
<table style="text-align: left;" border="1" cellpadding="2" cellspacing="2" width="200">
<tbody>
<tr>
<td style="font-weight: normal; font-size: 0.7em;">Supported</td>
<td class="supportedSmall" style="font-weight: normal; font-size: 0.7em; text-align: center;">Y</td>
</tr>
<tr>
<td style="font-weight: normal; font-size: 0.7em;">Not Supported</td>
<td bgcolor="#ffc3ab" class="supportednotSmall" style="font-weight: normal; font-size: 0.7em; text-align: center; color: rgb(216, 28, 63);">N</td>
</tr>
</tbody>
</table>
<a name="Upgrade_Migration_Notes"></a>Wonderware System Platform Upgrade and Migration Notes
<p><SPAN style="FONT-WEIGHT: bold; FONT-SIZE: 18px; COLOR: red; FONT-FAMILY: Verdana">Important Note:</SPAN> 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. </p> <p>Back up any custom configuration of the installed instance of InTouch Access Anywhere before you uninstall it.</p>
<a name="AppServer_Upgrade_Notes"></a>Application Server Upgrade and Migration Notes
If you are upgrading Wonderware Application Server to the new Wonderware System Platform 2014 R2 version, be aware of the following:
<li>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.</li>
<li>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.</li>
<li>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. </li>
<li>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.</li>
<li>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.</li>
<li>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.
<li>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.
<li>Upgraded IDE/Client nodes cannot connect to a non-upgraded
Galaxy Repository and vice-versa. </li>
<li>The Galaxy Repository node will be undeployed before upgrading to Wonderware
Application Server 2014 R2.
<li>Running platforms must be undeployed during the upgrade
process.
<li>WinPlatform and other related objects on a remote node will be
marked as "software update pending". </li>
<a name="InTouch_Upgrade_Notes"></a>InTouch and InTouch Access Anywhere Upgrade and Migration Notes
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:
<li>InTouch Development (WindowMaker<sup>™</sup>) is now installed
with support for ArchestrA graphics. This includes the ArchestrA
Integrated Development Environment (IDE), Bootstrap, Galaxy
Repository (GR), and FS Gateway.</li>
<li>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.</li>
<li>If SQL Server does not exist on the system, SQL Server Express
is installed automatically.</li>
<li>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.</li>
<li>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.</li>
<li>If you are using managed InTouch applications with ArchestrA<sup></sup>
Symbols from Application Server 3.1 SP3 or earlier, run the <b>ArchestrA
Symbol Analysis and Repair Utility</b> 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 <a href="https://wdn.wonderware.com/sites/WDN/Pages/Downloads/Utilities.aspx">Wonderware Developers' Network (WDN), Software Downloads</a>. Log in to WDN with your username and password to access the downloads archive.
<a name="Historian_Upgrade_Notes"></a>Wonderware Historian Upgrade and Migration Notes
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.
<a name="Client_Upgrade_Notes"></a>Wonderware Historian Client Upgrade and Migration Notes
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.
<a name="WII_Upgrade_Notes"></a>Wonderware Information Server Upgrade and Migration Notes
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.
<p>
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.
<p>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.</p>
<h1><a name="Licensing_Info"></a>Licensing Information</h1>
<p>Once installed, the ArchestrA License Manager can be found in the <b>\Invensys</b> folder on the <b>Start</b> menu rather than in the old License Utility folder, <b>\Wonderware\Common</b>.</p>
<h2>License Server</h2>
<p>Wonderware Information Server 2014 R2 supports using a centralized licensing server to manage client licenses. For more
information, see the <em>Invensys License Manager Guide</em> and the license server documentation in the \InstallFiles\CD-Licensing\UserDocs folder of the Wonderware Information Server 2014 R2 installation media.</p>
<p>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. </p>
<!--<p class="note"><span style="font-weight: bold;"> Note: </span>Wonderware
Information Server 4.5 and earlier licenses cannot be used for
Wonderware Information Server 2014. Contact your local distributor
for assistance.
</p>-->
<a name="Antivirus_Software_Exclusions" id="Antivirus_Software_Exclusions"></a>Antivirus Software Exclusions
<p>Configure your antivirus software to prevent archive files from being scanned. </p>
<p class="note"><b>Important Note:</b> 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.</p>
- 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:Files (x86)... and the application data root directory in a 64-bit operating system is C:...
<p>Exclude these ArchestrA folders in a 32-bit system:
</p>
<ul>
<li>C:\ProgramData\ArchestrA\ and all subfolders</li>
<li>C:\Program Files\ArchestrA\</li>
<li>C:\Program Files\Common Files\ArchestrA\</li>
<li>C:\Program Files\FactorySuite\ (The FactorySuite folder may not exist in newer installations)</li>
<li>C:\Program Files\Wonderware\</li>
<li>C:\Documents and Settings\All Users\Application Data\Wonderware</li>
<li>C:\Users\All Users\Applications</li>
<li>C:\InSQL\Data\</li>
<li>C:\Historian\Data</li>
</ul>
<p>Exclude these ArchestrA folders in a 64-bit system:</p>
<ul>
<li>C:\ProgramData\ArchestrA\ and all subfolders</li>
<li>C:\Program Files\Common Files\ArchestrA</li>
<li>C:\Program Files (x86)\ArchestrA\</li>
<li>C:\Program Files (x86)\Common Files\ArchestrA\</li>
<li>C:\Program Files (x86)\FactorySuite\ (The FactorySuite directory may not exist in newer installations)</li>
<li>C:\Program Files (x86)\Wonderware\</li>
<li>C:\Users\All Users\Wonderware</li>
<li>C:\Users\Public\Wonderware\
<li>C:\InSQL\Data\</li>
<li>C:\Historian\Data</li>
</ul>
<p>Exclude these folders:</p>
<li>History Store Forward directory in a 32-bit system:
<ul>
<li>C:\Documents and Settings\All Users\Application
Data\ArchestrA\ (default location)</li>
</ul>
<li>History Store Forward directory in a 64-bit system:
<ul>
<li>C:\Users\All Users\ArchestrA\ (default location)</li>
</ul>
</li>
<li>Checkpoint directory location default location in a 32-bit system:
<ul>
<li>C:\Program Files\ArchestrA\Framework\bin </li>
</ul></li>
<li>Checkpoint directory location default location in a 64-bit system:
<ul>
<li>C:\Program Files (x86)\ArchestrA\Framework\bin </li>
</ul>
</li>
<li>InTouch HMI Application folder path:
<ul>
<li>C:\Documents and Settings\All Users\Application
Data\ArchestrA\</li>
</ul>
</li>
<li>SMC Logger Storage file path:
<ul>
<li>C:\ProgramData\ArchestrA\LogFiles</li>
<li>C:\Documents and Settings\All Users\Application data\Archestra\LogFiles\</li>
</ul>
</li>
<p>Exclude these folders for Wonderware Information Server: </p>
<ul>
<li>c:\inetpub\wwwroot\Wonderware </li>
<li>c:\inetpub\wwwroot\AFWeb </li>
<li>c:\inetpub\wwwroot\aaFlexLicWebService </li>
<li>c:\Program Files\Wonderware\SuiteVoyager </li>
</ul>
<p>Exclude these files from the C:\Windows\Temp folder: </p>
<ul>
<li>*.aFDX</li></ul>
<p>SQL Server database files are located in:
<ul>
<li>C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA</li>
<li>Exclude SQL Server database files within this directory of the following types:
<ul>
<li>.mdf </li>
<li>.ldf</li>
</ul></ul>
<p>
<p>Exclude these additional file types if you wish: </p>
<ul>
<li>*.idx</li>
<li>*.pdx </li>
</li> </ul>
<a name="Resolved_Issues"></a>Resolved Issues
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.
<a name="Known_Issues"></a>Known Issues
<p>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. </p>
- <a href="#Known_Issues_Installation">Installation Issues</a>
- <a href="#Known_Issues_Upgrade">Upgrade and Migration Issues</a>
- <a href="#Known_Issues_ASB">ArchestrA Service Bus and Multi-Galaxy Communication Issues</a>
- <a href="#Known_Issues_EAC">ArchestrA Alarm Control Issues</a>
<h2><a name="Known_Issues_Installation" id="Known_Issues_Installation"></a>Installation Issues</h2>
<table style="text-align: left;" border="0" cellpadding="5" cellspacing="1">
<tbody>
<tr>
<td style="text-align: left; vertical-align: top;" colspan="2"
rowspan="1"><span
style="font-weight: bold;">L00101032</span>:</td>
<td style="text-align: left; vertical-align: top; width: 800px"
colspan="2"
rowspan="1">If
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."
<p>To resolve this issue, configure Wonderware Information
Server. You will then be able to uninstall the other
products.</p> </td>
</tr>
<tr>
<td style="text-align: left; vertical-align: top;" colspan="2"
rowspan="1"><span
style="font-weight: bold;">L00114588</span>:</td>
<td style="text-align: left; vertical-align: top; width: 800px"
colspan="2"
rowspan="1">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\.
</td>
</tr>
<tr>
<td style="text-align: left; vertical-align: top;" colspan="2"
rowspan="1"><span
style="font-weight: bold;">L00114910</span>:</td>
<td style="text-align: left; vertical-align: top; width: 800px"
colspan="2"
rowspan="1">On
a computer running the Windows Server 2008 R2 or Windows 7
(64-bit) operating system, a blank domain is shown in <b>Admin
User Page</b> when you clear the <b>Create Local Account</b>
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. </td>
</tr>
<tr>
<td style="text-align: left; vertical-align: top;" colspan="2"
rowspan="1"><span
style="font-weight: bold;">L00116883</span>:</td>
<td style="text-align: left; vertical-align: top; width: 800px"
colspan="2"
rowspan="1">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 <b>win.ini</b> in folder <b>C:\Users\<username>\AppData\Local\Wonderware</b>
where "username" is the name of the user attempting to start
the application. </td>
</tr>
<tr>
<td style="text-align: left; vertical-align: top;" colspan="2"
rowspan="1"><span
style="font-weight: bold;">L00120356</span>:</td>
<td style="text-align: left; vertical-align: top; width: 800px"
colspan="2"
rowspan="1">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.
</tr>
<tr>
<td style="text-align: left; vertical-align: top;" colspan="2"
rowspan="1"><span
style="font-weight: bold;">L00123209</span>:</td>
<td style="text-align: left; vertical-align: top; width: 800px"
colspan="2"
rowspan="1">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.
</tr>
<tr>
<td style="text-align: left; vertical-align: top;" colspan="2"
rowspan="1"><span
style="font-weight: bold;">L00128943</span>:</td>
<td style="text-align: left; vertical-align: top; width: 800px"
colspan="2"
rowspan="1">While installing Wonderware System Platform, if the logged-on user (the installer) is not a SQL Server administrator, the <B>Config SQL</b> 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.
</tr>
<tr>
<td style="text-align: left; vertical-align: top;" colspan="2"
rowspan="1"><span
style="font-weight: bold;">L00130063</span>:</td>
<td style="text-align: left; vertical-align: top; width: 800px"
colspan="2"
rowspan="1"><b>SR 103130498: </b>If the Wonderware.opt file has been deleted, the system will behave erratically.
<p>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.</td>
</tr>
<tr>
<td style="text-align: left; vertical-align: top;" colspan="2"
rowspan="1"><span
style="font-weight: bold;">L00133121</span>:</td>
<td style="text-align: left; vertical-align: top; width: 800px"
colspan="2"
rowspan="1"><b>SR 10417637</b>: 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: </p>
<ol>
<li>Create a key with name "Remoting" if it doesn't exist under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ArchestrA\Framework\
<li>Create a String value with name "defaultPort" under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ArchestrA\Framework\Remoting.
<li>Specify a port number, available on the local machine, other than 8090. For example, specify port 8091.
<li>Restart the aaGR service by entering the following at the command prompt:
<ol type="a">
<li>net stop aagr
<li>net start aagr</li>
</ol>
<li>Start Application Server (ArchestrA IDE).
</li>
</ol>
</td>
</tr>
</tbody>
</table>
<h2><a name="Known_Issues_Upgrade"></a>Upgrade and Migration Issues</h2>
<table style="text-align: left;" border="0" cellpadding="5" cellspacing="1">
<tbody>
<tr>
<td style="text-align: left; vertical-align: top;" colspan="2"
rowspan="1"><span
style="font-weight: bold;">L00133523</span>:</td>
<td style="text-align: left; vertical-align: top; width: 800px"
colspan="2"
rowspan="1">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 <b>Next</b> button is not available in that screen and you cannot proceed with the upgrade.
<p>This is due to the fact that by the time the <b>Back</b> navigation was initiated, the MS-SQL Server was already stopped by the upgrade process, resulting in a validation process failure. </p>
<p>Workaround: You must cancel the installation, restart the SQL Server and relaunch the install.</p>
</td>
</tr>
</tbody>
</table>
<h2><a name="Known_Issues_ASB"></a>ArchestrA Service Bus and Multi-Galaxy Communication Issues</h2>
<table style="text-align: left;" border="0" cellpadding="5" cellspacing="1">
<tbody>
<tr>
<td style="text-align: left; vertical-align: top" rowspan="1">
<span style="font-weight: bold">L00123433</span>:</td>
<td style="text-align: left; vertical-align: top" width="800px" colspan="2" rowspan="1">
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. <br><br>
For example:<br>
<ol>
<li>Install the latest Application Server software on two nodes, Node1 and Node2.
<li>Create a galaxy with a platform, and pair the nodes.
<li>On Node1, uninstall Application Server and restart the system.
<li>On Node 1, if the ASBService user still exists in SQL Server, delete the user manually before re-installing Application Server.
<li>On Node1, reinstall Application Server and connect to the same galaxy.
<li>Open the Multi-Galaxy Configuration dialog. Notice that all the pairing information has persisted through the uninstall-reinstall operation. Also, notice that multi-galaxy operations are not functioning. You cannot browse to or subscribe from Node2 even though the nodes appear to be paired.
<li>Un-pair and re-pair Node1 to get the new Discovery Service and pairing information from Node2.</li>
</ol>
</td>
</tr>
<tr>
<td style="text-align: left; vertical-align: top" rowspan="1">
<span style="font-weight: bold;">L00123462</span>:</td>
<td style="text-align: left; vertical-align: top" width="800px" colspan="2"
rowspan="1">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. <br><br>
For example, Node1 and Node2 are identified by IP address and are paired. To unpair them, do the following:
<ol>
<li>Navigate to the Hosts file on <b>Node1</b>. In Windows 7 and Windows 2008 R2 operating systems, the Hosts file typically can be found at C:\Windows\System32\Drivers\Etc\.
<li>Open the Hosts file in Notepad. In Windows 7 and Windows 2008 R2 systems, you should right click the Notepad executable, and click <b>Run as Administrator</b>, then open the Hosts file from inside Notepad. <br>
Alternatively, you can click <b>Start</b>, then click <b>Run</b>, then enter the following command in the text box:<br>
<b>notepad c:\Windows\System32\Drivers\Etc\Hosts</b>.
<li>Edit the Hosts file:
<ol type="a">
<li>Enter the IP address for <b>Node2</b>.
<li>On the same line as the IP address, provide a node (computer) name.
<li>Enter IP addresses and node (computer) names for each node identified by IP address to be unpaired. </li>
</ol>
<li>Save and close the Hosts file. You should now be able to unpair the galaxies.</li>
</ol>
</td>
</tr>
<tr>
<td style="text-align: left; vertical-align: top;" rowspan="1">
<span style="font-weight: bold;">L00123474</span>:</td>
<td style="text-align: left; vertical-align: top" width="800px" colspan="2"
rowspan="1">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 <b>bold text</b>:<br>
<blockquote>
<code>
IF bRunScript  THEN<br /><br />
    FOR tagval = 1 TO 3<br />
      indirect.Name = "Testtag" + Text(tagval, "0");<br />
    <br />
        IF indirect.Value > 4  THEN<br />
                indirect.Value  = 0;<br />
            ELSE <br />
                indirect.Value  = indirect.Value  + 1;<br />
                indirect.Value  = indirect.Value  + 1;<br />
            ENDIF;      <br />
    NEXT;<br />
      </code><b>indirect.Name = "";</b><code><br /><br />
ENDIF;<br /><br />
</code>
</blockquote>
</td>
</tr>
<tr>
<td style="text-align: left; vertical-align: top;" rowspan="1">
<span style="font-weight: bold;">L00123475</span>:</td>
<td style="text-align: left; vertical-align: top" width="800px" colspan="2"
rowspan="1">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:<br>
<ol>
<li>Open the <b>Configure ArchestrA Services</b> utility.
<li>Note the port number of the ASBGRBrowsing service instance for the missing galaxy.
<li>Compare this to the port numbers of other ASBGRBrowsing service instances assigned to the same node.
<li>If you find a service instance with a duplicate port number on the same node:
<ol type="a">
<li>Undeploy the browsing service of the missing galaxy.
<li>Change the port number to a unique number for that node.
<li>Redploy the browsing service instance.
</ol>
</ol>
</td>
</tr>
<tr>
<td style="text-align: left; vertical-align: top;" rowspan="1">
<span style="font-weight: bold;">L00125223</span>:</td>
<td style="text-align: left; vertical-align: top" width="800px" colspan="2"
rowspan="1">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.
</td>
</tr>
<tr>
<td style="text-align: left; vertical-align: top;" rowspan="1">
<span style="font-weight: bold;">L00133534</span>:</td>
<td style="text-align: left; vertical-align: top; width: 800px"
rowspan="1">Undeploying a galaxy with Object Viewer active will cause Object Viewer to shut down with an informational message that requires acknowledgement (click <b>OK</b>) 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 <b>OK</b> to shut down Object Viewer before redeploying the galaxy.
</td>
</tr>
<tr>
<td style="VERTICAL-ALIGN: top"><span style="FONT-WEIGHT: bold">L00134322:</span></td>
<td>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". </td>
</tr>
</tbody>
</table>
<h2><a name="Known_Issues_EAC"></a>ArchestrA Alarm Control Issues</h2>
<p>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.</p>
<h1><a name="Documentation"></a>Documentation</h1>
The Wonderware System Platform documentation is available Adobe Acrobat .pdf files that are available from the following locations on the Wonderware System Platform DVD:
<blockquote>
<p>\Wonderware System Platform\CD-ApplicationServer\UserDocs\English</p>
<p>\Wonderware System Platform\CD-Historian-x64\UserDocs\English</p>
<p>\Wonderware System Platform\CD-HistorianClients\HistorianClient\Docs</p>
<p>\Wonderware System Platform\CD-Intouch\UserDocs\English</p>
<p> \Wonderware System Platform\CD-WIS\UserDocs\English</p>
</blockquote>
<p>To view the documentation, you must first download the latest version of Adobe Reader
from the Adobe Corporation web site: <a href="http://www.adobe.com/products/acrobat/readstep2.html" target="_blank">http://www.adobe.com/products/acrobat/readstep2.html</a>.</p>
You can also access online Help systems from within the software.
- <a href="#Doc_Info_Common">Common Components and Utilities User Documentation</a>
- <a href="#Doc_Info_InTouch">Wonderware InTouch HMI</a>
- <a href="#Doc_Info_App_Server">Wonderware Application Server</a>
- <a href="#Doc_Info_Historian_Server">Wonderware Historian Server</a>
- <a href="#Doc_Info_Historian_Client">Wonderware Historian Client</a>
- <a href="#Doc_Info_Info_Server">Wonderware Information Server</a>
- <a href="#Documentation Issues">Documentation Issues</a>
<a name="Doc_Info_Common"></a>Common Components and Utilities User Documentation
<li><i>Wonderware System Platform Installation Guide.</i> This
guide provides information on installing the Wonderware
System Platform, including hardware and software requirements and
migration instructions. </li>
<li><span style="FONT-STYLE: italic">Log Viewer User's Guide</span>.
Explains how to use the Log Viewer utility to determine system
diagnostics. </li>
<li><span style="FONT-STYLE: italic">Log Flag Editor Utility Guide</span>.
Explains how to turn on and off certain diagnostics logging
messages. </li>
<li><span style="FONT-STYLE: italic">Invensys License Manager
Guide</span>. Explains how to install and manage product licenses.
<li><span style="FONT-STYLE: italic">Wonderware ArchestrA Protocol
Guide</span>. Explains background information on the main
protocols used between components of Wonderware products.
</li>
</ul>
<a name="Doc_Info_InTouch"></a>Wonderware InTouch HMI 2014 R2 Documentation
<ul style="LIST-STYLE-TYPE: disc">
<li><span style="FONT-STYLE: italic">InTouch HMI Concepts and Capabilities Guide</span>. Describes all of the features and main concepts in the InTouch HMI without going too deep into the technical and procedural details.</li>
<li><span style="FONT-STYLE: italic">InTouch Modern Application Guide</span>. Describes the tasks to manage Modern applications from Application Manager and configure Modern applications from WindowMaker.</li>
<li><span style="FONT-STYLE: italic">The InTouch HMI Application Management and Extension Guide</span>. Describes how to create and manage InTouch applications locally and in a network environment.</li>
<li><span style="FONT-STYLE: italic">InTouch HMI Data Management Guide</span>. Describes how to work with data items in the InTouch HMI and connect your application to the physical devices in your plant environment.</li>
<li><span style="FONT-STYLE: italic">InTouch HMI Visualization Guide</span>. Describes how to develop the graphical operator interface of an InTouch application.</li>
<li><span style="FONT-STYLE: italic">InTouch HMI SmartSymbols Guide</span>. Describes how to create reusable templates for graphic symbols that can save you a lot of engineering time and effort.</li>
<li><span style="FONT-STYLE: italic">InTouch HMI and ArchestrA Integration Guide</span>. Describes how to integrate the InTouch HMI and ArchestrA technology to develop more robust applications that use richer graphics.</li>
<li><span style="FONT-STYLE: italic">InTouch HMI Alarms and Events Guide</span>. 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. </li>
<li><span style="FONT-STYLE: italic">InTouch HMI Scripting and Logic Guide</span>. 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. </li>
<li><span style="FONT-STYLE: italic">InTouch HMI Supplementary Components Guide</span>. Describes software components that you can optionally install and use with the InTouch HMI. </li>
</ul>
<h3><a name="Doc_Info_App_Server"></a>Wonderware Application Server 2014 R2 Documentation</h3>
<ul style="LIST-STYLE-TYPE: disc">
<li><span style="FONT-STYLE: italic">Wonderware Application Server
User's Guide</span>. Explains configuring and deploying
Wonderware Application Server applications. </li>
<li><span style="FONT-STYLE: italic">Creating and Managing
ArchestrA Graphics User's Guide</span>. Explains how you
create and manage graphical symbols using the ArchestrA Symbol
Editor within the Integrated Development Environment (IDE). </li>
<li><span style="FONT-STYLE: italic">Wonderware Application Server Scripting
Guide</span>. Reference for the scripting language in
Wonderware Application Server. </li>
<li><span style="FONT-STYLE: italic">Object Viewer User's Guide</span>.
Explains how to acquire run-time data using the Object Viewer. </li>
<li><i>Guide to the ArchestrA Alarm Control</i>. Explains how to
configure the alarm control (client) to show current and
historical alarms and events in a grid. </li>
<li><i>Guide to the ArchestrA Trend Client</i>. Explains how to
configure a chart to trend real-time data values. </li>
<li><span style="FONT-STYLE: italic">Platform Manager User's Guide</span>.
Explains how to start and stop system components. </li>
<li><span style="FONT-STYLE: italic">Galaxy Database Manager
User's Guide</span>. Explains how to backup and restore the
Galaxy database. </li>
<li><span style="FONT-STYLE: italic">Wonderware InTouch HMI and ArchestrA
Integration Guide</span>. 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.
</li>
</ul>
<a name="Doc_Info_Historian_Server"></a>Wonderware Historian Server 2014 R2 Documentation
<ul>
<li><i>Wonderware Historian Concepts Guide.</i> Provides an overview of the entire Wonderware Historian system
and describes each of the subsystems in detail. </li>
<li><i>Wonderware Historian Administration Guide.</i> 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. </li>
<li><i>Wonderware Historian Database Reference.</i> Provides documentation for all of the Wonderware Historian
database entities, such as, tables, views, and stored
procedures. </li>
<li><i>Wonderware Historian Glossary.</i> Provides
definitions for terms used throughout the documentation. </li>
</ul>
<h3><a name="Doc_Info_Historian_Client"></a>Wonderware Historian Client 2014 R2 Documentation</h3>
<ul>
<li><i>Wonderware Historian Client Software User's Guide</i> Describes how to use stand-alone applications, Microsoft Office add-ins, and ActiveX and .NET controls to retrieve and display data. </li>
</ul>
<h3><a name="Doc_Info_Info_Server"></a>Wonderware Information Server 2014 R2 Documentation</h3>
<ul>
<li><i>Wonderware Information Server
Administration Guide.</i> Describes how to administer and
maintain a Wonderware Information Server, including configuring
data sources, managing security, and performing customizations.</li>
<li><i>Wonderware Information Server Win-XML Exporter Guide.</i> 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. </li>
<li><i>ArchestrA Web Exporter Guide</i>.
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. </li>
<li><i>ActiveFactory for Wonderware Information Server Help</i>.
Describes how to use the ActiveFactory for Wonderware Information Server web portal to view a variety of reports that include data from Wonderware Historians. </li>
<li><i>ArchestrA License Manager
Guide</i>. Describes the ArchestrA License
Manager and how to use it to install and manage licenses and
license servers on local and remote computers. </li>
</ul>
