System Platform 2014 Patch 01

Материал из archestra.info
Перейти к: навигация, поиск

Last revision: 04/03/2014

About This Readme

This Readme includes information about Wonderware System Platform 2014 Patch 01. The Patch 01 Readme updates the previous ReadMe file included with Wonderware System Platform 2014. The entire Wonderware System Platform 2014 Readme is included in this document, following the Patch 01 sections.

Wonderware System Platform 2014 Patch 01 Information

Feature Enhancements Included with Wonderware System Platform 2014 Patch 01

Applying Patch 01 to Wonderware System Platform 2014

Resolved Issues - Wonderware System Platform 2014 Patch 01

Known Issues - Wonderware System Platform 2014 Patch 01

Documentation Issues - Wonderware System Platform 2014 Patch 01

Wonderware System Platform 2014 Readme

Feature Enhancements Included in Wonderware System Platform 2014 Patch 01

This Patch release includes the following features and enhancements in addition to Resolved Issues.

All Wonderware System Platform 2014 Patch 01 Products

Support for Microsoft Windows 8.1 and Windows Server 2012 R2 Operating Systems

All products associated with the Wonderware System Platform 2014 Patch 01 include support for Microsoft Windows 8.1 and Windows Server 2012 R2 operating systems, with the exception of Wonderware Information Server:

  • Wonderware InTouch HMI 2014 Patch 01. (See InTouch HMI Known Issues for important information.)
  • Wonderware Application Server 2014 Patch 01.
  • Wonderware Historian 2014 Patch 01.
  • Wonderware Historian Client 2014 (version 10.5).

Note: The server components of Wonderware Information Server 2014 (version 5.5) are not supported on Windows 8.1.

Support for OPC UA Client Service

Wonderware System Platform, in particular Wonderware Application Server and Wonderware InTouch HMI, now support OPC UA Client Service, installed optionally and separately from Wonderware System Platform 2014 Patch 01.

Wonderware Product Compatibility Updates

Compatibility means that Wonderware products can communicate with each other over the network. Co-existence means that the products can be installed on the same computer. Wonderware System Platform 2014 Patch 01 includes the following product compatibility additions:

  • Wonderware InBatch™: Version 10.0 (2012 R2) SP1 is both compatible and co-existent.

Wonderware InTouch HMI 2014 Patch 01

Programmatically Exporting and Importing ArchestrA Symbols

InTouch HMI 2014 introduced a new application programming interface (API) to programmatically export or import a symbol between the ArchestrA Graphic Toolbox and an XML file. In Patch 01, the programmatic API has been enhanced to include more symbol properties in export and import operations.

An exported or imported symbol contains the following:

  • Custom properties
  • Graphic elements
  • Symbol animations
  • Element styles
  • Named scripts
  • Predefined scripts
  • Graphic groups
  • Graphic elements
  • Embedded Alarm Client
  • Real Time Trend
  • Window controls

In addition to the properties of a standard ArchestrA symbol, an exported or imported Symbol Wizard graphic contains the following properties in export and import operations:

  • Wizard Options
  • Choice groups
  • Choices
  • Layers
  • Rules

For more information about programmatically importing and exporting ArchestrA symbols, see chapter 3 of the Creating and Managing ArchestrA Graphics User's Guide.

Trend Pen Step Line Mode

InTouch HMI 2014 introduced the Trend Pen graphic element, which shows a succession of process values as a trend line consisting of current and historical data updated at one second intervals. A trend line gives operators a quick visual snapshot of a process value over a defined period.

You can now configure two types of Trend Pen plots. A Line plot draws a line between each successive data point during the trend period. Patch 01 includes the Trend Pen Step Line plot, which draws a horizontal line from a trend data point to the time of the next point on the trend's X-axis, and then draws a vertical line to the data point. Step Line is the default type of Trend Pen plot.

For more information about the Trend Pen control, see chapter 10 of the Creating and Managing ArchestrA Graphics User's Guide.

Wonderware Historian 2014 Patch 01

Significant Improvements in Common Query Patterns

Retrieval for small queries, such as a query from a few blocks, now completes in as little as 60% of time compared to 11.5. Retrieval for large queries, such as multi-tag queries that retrieve data from many blocks, now complete in as little as 50% of the time for 11.5 using OLE DB clients.

Important Information about Wonderware Historian 2014

1. A2ALMDB is an Alarm and Event SQL database automatically created on the Historian node as of Wonderware System Platform 2014.

  • A new installation of Wonderware Application Server 2014 - not an upgrade - will enable Alarm and Event historization to the new A2ALM database by default, provided Process History has been enabled in Application Server.
  • This database will consume disk space as it stores alarms and events, its size monitored and managed by the system administrator.
  • The functionality of A2ALMDB is unchanged in Wonderware System Platform 2014 Patch 01.

2. The alarm and event records in the A2ALMDB SQL database are in UTC, rather than in local time as in WWALMDB. If you have built custom reports based on SQL, and choose to change from WWALMDB to A2ALMDB, you may need to adjust your reporting to adjust for records being time stamped in UTC.

3. To disable Alarm and Event historization to the new A2ALMDB from Wonderware Application Server 2014 and 2014 P01, do the following steps in the Wonderware Application Server IDE:

  1. On the main menu, click Galaxy, then Configure, and then Alarm Priority Mapping.
  2. Under the Historize column, uncheck the checkboxes.

Applying Patch 01 to Wonderware System Platform 2014

The following requirements must be met to install Patch 01 to Wonderware System Platform 2014 products:

  • Installation - Each patch available for installation from the Patch Manager applies to a specific Wonderware System Platform product. The patches can be applied only to products that have already been installed on your system.
  • Coexistence - If Wonderware Application Server and InTouch HMI 2014 are installed on the same node, upgrade to Application Server 2014 (v4.0) Patch 01 and InTouch 2014 (v11.0) Patch 01, respectively.

Important

Computer Reboot Privileges: In a server operating system, inadequate privileges can prevent a user from rebooting the computer. After the patch installation, the patch installer might not be able to force the necessary computer reboot. You will need to manually reboot the computer to properly complete the software patch process.

Resolved Issues - Wonderware System Platform 2014 Patch 01

This section describes important issues resolved in Wonderware System Platform 2014 Patch 01. These issues are grouped by functional area and listed by their Change Request (CR) number and any assigned Service Request (SR) number. Issues listed in this Patch readme typically involve components common to multiple System Platform products and to products available separately from Wonderware System Platform. For issues that are specific to Wonderware System Platform Products, see the product-specific readme files.

ArchestrA Service Bus and Multi-Galaxy Communication Resolved Issues

L00125223: If you created galaxies on separate nodes, with Wonderware System Platform 2014 IDE installed on one node and Wonderware System Platform 2012 R2 IDE installed on a second node, then paired them for multi-galaxy communication, you were 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.

Known Issues - Wonderware System Platform 2014 Patch 01

The following important known issues are grouped by product or functional area, and are listed by their assigned CR number in ascending order.

Wonderware InTouch HMI Known Issues

L00130543: If WindowMaker is installed on a Virtual Machine (VM) running VMware Tools ESXi 5.0 that has not been upgraded to 'Update 2', WindowMaker may become unresponsive when trying to save an InTouch window or other application-related data files. The source of the problem is a known issue with the vShield Endpoint filter driver that ships with VMware Tools ESXi 5.0. This driver is automatically loaded when VMware Tools is installed using the Full option, rather than the Typical default. If this problem is encountered while working within WindowMaker, it is possible that portions of the InTouch application may become corrupted because not all data is saved and the states of some application files are left unresolved.

More information about this issue can be found in the following VMWare Knowledge Base article:
Degraded Windows network file copy performance after full ESXi 5 VMware Tools installation (2034490)

The VMware ESXi 5.0 Update 2 is a recommended upgrade if the vShield Endpoint filter driver is installed on a VM running WindowMaker. If the vShield Endpoint filter driver is not required, then disabling the driver is recommended. Instructions to disable the vShield Endpoint filter driver are described in the VMWare Knowledge Base article listed above.

Wonderware Information Server Known Issues

L00130175: When you open the Wonderware Information Server 2014 (version 5.5) portal, the home page displays an error after an upgrade of the Operating System from Windows 2012 to Windows 2012 R2.

To resolve this issue, do the following:

  1. Browse and open the Web.config file from the following location in the computer on which you have installed Wonderware System Platform 2014 and Wonderware Information Server 2014 (version 5.5):- C:\inetpub\wwwroot\Wonderware\web.config.
  2. Remove the following two entries from the Web.config file: 
    • <add name= "xoml-ISAPI-2.0" path="*.xoml" verb="*" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll"requireAccess="Script" 
precondition=" classicMode.runtimeversion2.0,bitness32"/> 
    • <add name= "rules-ISAPI-2.0" path="*.rules" verb="*" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll"requireAccess="Script" 
precondition=" classicMode.runtimeversion2.0,bitness32"/>
  3. Save and close the Web.config file.
  4. Open the Wonderware Information Server portal. The portal opens without any error.
L00130380: When you open the Wonderware Information Server portal 2014 (version 5.5) in Internet Explorer 11.0 and access the Information Model, an error is displayed.

To resolve this issue, do the following:

  1. Open the Wonderware Information Server Portal.
  2. In the System access panel, expand Administration and then click Information Model. The Relationships page appears.
  3. In the Relationships pane, right-click an empty area. The Shortcut menu pop-up appears.
  4. In the Shortcut menu, select and then click Properties. The Properties window appears.
  5. Select and copy the address from the Address (URL) field and then paste in a new window to open the Information Model in Internet Explorer 11.0. The Information Model opens without any error.
  6. Alternatively, select and click the 'Create Shortcut' option to add a direct shortcut (bookmark) on your desktop.

Documentation Issues - Wonderware System Platform 2014 Patch 01

The following table lists important Wonderware System Platform 2014 Patch 01 documentation corrections.

Item Location of Change Existing Documentation Change
1 Wonderware Application Server User Guide (IDE.pdf),

"Configuring ArchestrA Service TCP Ports" section, pages 244-246

(InvensysLicenseManager.chm),

Table: ArchestrA Service Port Numbers in Use		 (table row) aaServiceASBSoftwareUpdate 7587 Delete row from table.

 

< top of document >

 

Wonderware System Platform 2014 Readme

Last revision: 12/03/2013

This document contains important information about Wonderware® System Platform 2014, which includes:

  • Wonderware InTouch HMI 2014 (v11.0)
  • Wonderware Application Server 2014 (v4.0)
  • Wonderware Historian Server 2014 (v11.5)
  • Wonderware Historian Client 2014 (v10.5)
  • Wonderware Information Server 2014 (v5.5)

Use the following links to navigate this Readme file:

You can find readme files for previous product releases at Wonderware Developers Network (WDN) Downloads. Log in to WDN with your username and password to access the downloads archive.

About This Release

Wonderware System Platform 2014 - General Notes

Invensys License Manager

Invensys License Manager provides a unified solution for enterprise management of Invensys product licenses, including functionality for importing, installing, and managing licenses on local machines, license servers, and remote machines. With Invensys License Manager, you can associate licenses with individual nodes on the system to assure correct software usage, install and manage licenses on local and remote notes, and check the validity of licenses on your system.

Windows Operating Systems

Wonderware System Platform 2014 component products support Windows 8 and Windows Server 2012 operating systems. The following Windows operating systems are no longer supported:

  • Windows XP, all versions
  • Windows Vista, all versions
  • Windows Server 2003, all versions
  • Windows Server 2008, non-R2 versions

Replacing SPC Pro with QI Analyst

SPCPro™ is a Statistical Process Control (SPC) utility formerly available with InTouch HMI. SPCPro is no longer supported by InTouch HMI. We recommend that if you use SPC and SPCPro with InTouch that you migrate your SPC Pro databases to the latest version of QI Analyst. QI Analyst provides support for the latest operating systems and DBMS versions, and provides a migration utility to move your SPCPro database to a QI Analyst database, leaving the existing SPC Pro database intact. Please contact your local Wonderware sales representative for further information.

Important Note: We strongly recommend that you migrate your current SPCPro databases to QI Analyst before installing Wonderware System Platform 2014 with InTouch HMI. InTouch 2014 no longer includes SPCPro, and will not open or migrate applications containing SPCPro components.

Wonderware InTouch HMI 2014

Situational Awareness Library

InTouch HMI 2014 adds support for Situational Awareness Library symbols as part of the Base Galaxy. Situational Awareness Library symbols include automation to simplify the tasks of configuring alarms and other data for the following types of symbols:

  • Instrumentation symbols
  • Equipment symbols
  • Input symbols
  • Status symbols
  • Unitizer symbols

Element Styles

InTouch HMI 2014 provides the capability to use globally named visual styles in the following areas of ArchestrA graphics:

  • Situational Awareness Library symbols
  • Graphic elements
  • Animations

Symbol Wizards

Both traditional ArchestrA symbols and Situational Awareness Library symbols Symbol Wizards can be enabled to support multiple visual and functional configurations using the Symbol Wizard Editor. The following enhancements to the Symbol Wizard Editor have been introduced in InTouch HMI 2014:

  • Design-time validation support for graphics created with the Symbol Wizard
  • Support for scripting and custom properties included in Symbol Wizards
  • Capability to edit Situational Awareness Library symbols with the Symbol Wizard Editor
  • Updates to the user interface and workflow of the Symbol Wizard Editor

New Animations

InTouch HMI 2014 includes several new animations to ArchestrA symbols and graphic elements. The following animations are new in InTouch HMI 2014:

  • Point animation
  • Start and sweep angles of an arc, chord, and pie graphic elements
  • Alarm borders around symbols
  • Simple Trend graphic elements

Graphic Performance Index

The Graphic Performance Index is a Symbol Editor utility to estimate the load performance of an ArchestrA symbol. The Graphic Performance Index calculates a rank value ranging from 0 to 5 for the time needed to load a symbol while an application is running. Users can request additional information from the Graphic Performance Index utility for scores less than 5 to identify the components in a symbol that are affecting load performance.

InTouch Access Anywhere

Run-time users can access and interact with Wonderware InTouch applications from any device that has an HTML5 compatible web browser.

Wonderware Application Server 2014

Communication Across Multiple Galaxies

Communication across multiple galaxies has undergone multiple enhancements:

  • Support for tuning the Alarm Manager buffer size.
  • Support for Custom Enum datatype metadata.
  • Writes to a remote Galaxy no longer require the user to be logged on to the remote Galaxy.
  • Support for user-provided reason description on the secured and verified write credential dialog.
  • Enhanced unpairing operations to address unpairing a galaxy when communication problems exist with that galaxy.

ArchestrA Service Bus (ASB)

In addition to multi-galaxy communication functionality, the ArchestrA Service Bus (ASB) now supports 64-bit services, and has undergone significant performance enhancements.

Template and Symbol Protection

Derived templates and symbols can be protected, and the Situational Awareness Library symbols are now protected by default.

QuickScript Editor Scripting Enhancements

The QuickScript Editor in the Object Editor and in the Graphic Editor has undergone multiple enhancements.

  • The QuickScript and Graphics editors now provide autocomplete functionality.
  • Line numbers and navigation by line numbers is now supported.
  • The QuickScript editor supports multi-level undo and redo.
  • QuickScript .NET has added support for error handling using the TRY ... CATCH construct.
  • Added error, warning, trace, and custom Logger functions provide user-definable messages with different associated log flags.

Alarm System Enhancements

  • Alarm Severity-to-Priority Mapping: Allows you to use the ArchestrA IDE to map each of four alarm severities to priorities expressed as numeric ranges. Alarms can then be aggregated and displayed with the specified severity at run time.
  • Alarm Aggregation: Provides an efficient way to identify whether any alarms on an object are currently in the InAlarm state, the overall status of the most important of those alarms, and how many alarms are active at each level of alarm severity and at each level of containment. This makes it possible to follow a trail from one level to the next to find the underlying cause of a complex object's alarms. You can view alarm aggregation statuses in run-time clients such as Object Viewer, you can model alarm aggregation in Managed InTouch applications by using animations such as the alarm border animation, and you can historize any or all of the four alarm severities.

Technology Updates

Wonderware Application Server 2014 adds support for Windows 8 and Windows Server 2012 operating systems, .NET Framework 4.5, support for SQL Server Express and latest SQL Server versions, User Account Control (UAC)-enabled, and security enhancements.

Wonderware Historian Server 2014

  • Two million I/O tags are supported for a tier-2 historian.
  • Wonderware Application Server can historize alarms and events to the Wonderware Historian.
    • Alarms can be historized by severity. Existing priorities can be mapped to severities.
    • Alarms and events support Historian store-and-forward.
    • Alarms and events are stored locally in a file if the connection to the Historian is lost or if the Historian is very busy. Store-and-forward for alarms and events supports data compression and low bandwidth.
    • Data coming late can still generate alarms and events within the Wonderware Application Server, which can still be historized.
    • Alarms and events are sent to both Historians in a redundant Historian configuration. Note that configuring the Historian this way can consume double system resources.
    • When an AppEngine fails over to a backup WinPlatform, alarms and events will continue to be historized from the redundant location.
  • ArchestrA Alarm Client control supports a redundant Historian configuration.
    • The ArchestrA Alarm Client control automatically detects a redundant Historian configuration.
    • The ArchestrA Alarm Client control switches to the partner Historian when the primary is not available.
  • Improved support for private namespace and private annotations for domain Users.
  • Historian SDK is updated in this release.
  • Historian is configured to auto-start by default.

Wonderware Historian Client 2014

  • Wonderware Historian Client supports Windows 8 and Windows Server 2012 operating systems, .NET Framework 4.5, and security enhancements.

Wonderware Information Server 2014

  • Wonderware Information Server supports Windows 8 and Windows Server 2012 operating systems, .NET Framework 4.5, and security enhancements.
  • Removed support for MultiViews.

System Requirements and Guidelines

Hardware Guidelines

The following table provides guidelines for hardware configurations suitable for Wonderware System Platform 2014 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.

  CPU
(GHz)		 Cores
(Minimum)		 RAM
(GB)		 Storage
(GB)
(sufficient for 1 wk @ max
frequency)		 Monitor
Resolution		 Network
(Mbps)
Mini Installation
(1 - 500 I/O per Node)
 1.6 1 1 30 1024x768 100
Small Installation
(1 - 5K I/O per Node)
 1.8 2 2 30 1024x768 100
Medium Installation
(5k - 50k I/O per Node)
 2.8 4 8 500 1280x1024 1000
Large Installation
(50k - 400k I/O per Node)
 2.8 8 16 1000 1280x1024 1000
Preferred Installation
(64-bit OS and SQL)
 2.8 4 8 500 1280x1024 1000

Windows operating systems and SQL Server versions impose hardware requirements that may exceed the minimum requirements for Wonderware Application Server 2014. Refer to the following Microsoft Web sites for hardware requirements:

Wonderware Historian Hardware Guidelines

  • Wonderware Historian is not supported on cluster hardware.
  • Do not use the Wonderware Historian computer as a domain controller, mail server, or an Internet server.
  • If you are running the Wonderware Historian on a virtual server, the Historian must have adequate CPU, network, memory, and disk I/O resources at all times. Overloading the virtual server leads to unpredictable behavior.

Wonderware Historian Client Hardware Guidelines

  Required Minimum Recommended
Processor 1.2 GHz
Pentium III 		Single CPU- 2 GHz or more
Memory, RAM 512 MB 1 GB or more
Free hard drive space 55 MB 55 MB or more

Wonderware Information Server Hardware Requirements

  Required Minimum Recommended
CPU 2.5 GHz Pentium 4 3.0 GHz Pentium 4
Memory 2 GB RAM Greater than 2 GB RAM
Free hard drive space 10 GB of free disk space 20 GB or more of free disk space, depending on the number of InTouch HMI windows, ArchestrA Symbols, ActiveFactory Reports and ArchestrA Reports published to the site.
File system NTFS NTFS

Alternative Authentication Using Smart Cards

  • Smart Card: Raak Technologies C2-40 Mini Driver Smart Card
  • Smart Card Reader: OK 3021 USB Smart Card Readers

Operating System, .NET Framework, and Virtualization Requirements

Summary of Requirements for Wonderware System Platform 2014

The following table lists the operating system, .NET Framework, and virtualization requirements for Wonderware System Platform 2014.

Note: Only the versions shown in the following tables are supported for Wonderware System Platform 2014 components.

  Client
Windows OS		 Server
Windows OS		 .NET
Framework		 Virtualization Host
7 SP1
Embedded
(32-bit only)		 7 SP1
Professional,
Enterprise,
Ultimate
(32/64-bit)		 8
Professional,
Enterprise
(32/64-bit)		 2008 R2 SP1
Standard,
Enterprise
(64-bit)		 Server 2012
Standard and
Data Center
(64-bit)		 3.5 SP1 4.5 Hyper-V
(2008R2 SP1, 2012, 2012 R2, HA/DR)		 VMWare 5.x
(Including HA/DR)		 VMWare Workstation
Application Server 2014 N Y Y Y Y C Y Y Y N
InTouch 2014 Y Y Y Y Y C Y Y Y N
Historian 2014 N Y Y Y Y C Y Y Y N
Historian Client 2014 N Y Y Y Y C Y Y Y N
Information Server 2014 N Y Y Y Y C Y Y Y N
                     
Mini Installation (1-500 I/O per node) R Y Y Y Y C Y Y Y Y
Small Installation (1-5,000 I/O per node) N Y Y Y Y C Y Y Y N
Medium Installation (5k-50k I/O per node) N Y Y Y Y C Y Y Y N
Large Installation (50k-400k I/O per node) N N N Y Y C Y Y Y N
Preferred Environment (64-bit OS and SQL Server)     R   R C Y Y Y N

 

Supported Y
Supported and Recommended R
Not Supported N
Compatible C
Not Applicable

Notes:

  • The entry for Wonderware Application Server applies to the ArchestrA IDE (Development node) and ArchestrA Run time (Application node).
  • The Galaxy Repository (GR node) can run on a client Windows operating system only in a single-node scenario.
  • Development and application nodes are considered to be clients of the server GR node.
  • Other .NET Framework versions can coexist, but all scripts in objects run in .NET Framework 4.5. For more information about .NET Framework requirements and compatibility, see .NET Framework Requirements and Compatibility

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. For more information, contact Wonderware Technical Support.

Configuring Remote Alarm Retrieval Queries When Running Windows 7, Windows Server 2008 R2, and Later Operating Systems

The process to configure remote alarm retrieval queries has changed for interactive applications such as InTouch HMI when running on Windows 7, Windows Server 2008 R2, and later operating systems.

When InTouch WindowViewer is started and generates alarms from an interactive Windows 7, Windows Server 2008 R2, or later desktop session, an AlarmViewer control (running within InTouch HMI) on a remote node must be specially configured to query the alarms. The source alarms will not appear unless the AlarmViewer control's alarm query is configured.

This type of query only works for InTouch HMI as an alarm provider running in a Terminal Services session, not for InTouch HMI running in a console session.

To configure the AlarmViewer's alarm query

  1. After starting InTouch WindowViewer (alarm provider) on the Windows 7, Windows Server 2008 R2, or later node, open the SMC Logger and look for the most recent string generated by AlarmMgr. For example: "Registering AlarmMgr with SLSSVC as AlarmMgr 253.127.148.120". The indicated IP address will be unique to your alarm-providing node. Note the IP address for use in Step 2.
  2. In the Alarm Query tab of the AlarmViewer control on the remote computer, configure the alarm query as follows, substituting your nodename of the alarm providing InTouch HMI for "nodename" below and substituting your IP address noted in the previous step:
\\nodename:ip_address\intouch!$system

where nodename is the name of the node that is providing the InTouch alarm and ip_address is the IP address that you determined in step 1.

  1. Test to validate that the alarms generated from the alarm-providing node are shown accurately in the AlarmViewer control.

Using Alarm Manager on a Single Node Running Both Wonderware InTouch HMI and Application Server Alarm Providers on Windows Vista and Later Operating Systems

Starting with Microsoft Windows Vista, the operating system imposes "Session 0 Isolation" as a security enhancement. All Windows services and associated programs are required to run in Session 0, and no GUI applications are allowed to run in Session 0.

Prior to Windows Vista, Wonderware Application Server and InTouch WindowViewer ran in the same Windows session. Session 0 Isolation requires that Application Server and WindowViewer run in separate Windows sessions. Alarms that are reported by the Galaxy are handled by the Session 0 instance of Alarm Manager (AlarmMgr), which is now different from the Console Session instance of AlarmMgr that handles InTouch alarms. A simple alarm query in an InTouch alarm display such as

\InTouch!$System \Galaxy!Area_001

is now serviced by two separate instances of AlarmMgr -- one running in the Console Session for InTouch, another running in Session 0 for the Galaxy.

This behavior, and related behaviors and error messages resulting from the Windows operating system Session 0 changes, along with procedures to configure the Distributed Alarm System to support alarms from both InTouch and Application Server on the same computer node running with Windows Vista and later operating systems, are described in detail in TechNote 988, "AlarmMgr Support for InTouch and AppServer on Windows Vista and Later". You can download this TechNote from Wonderware Developers Network (WDN) Downloads.

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.

This impacts InTouch HMI functionality such as Alarm Manager that depends on the Terminal Server Console session. Refer to the Wonderware InTouch HMI 2014 Readme for further information about InTouch HMI applications running in the Terminal Server Console.

If you are running WindowViewer within a Terminal Server session and want to access alarms from WindowViewer in a client session, you must use the syntax \\terminalservernode:<IP address>\InTouch!$System to access the alarms, with a colon (:) after the node name. The IP address is that of the client computer connected to the session.

Operating System Notes: Wonderware InTouch HMI 2014

Following are notes specific to the InTouch HMI 2014 operating system support and requirements.

  • The recommended operating system for a Galaxy Repository is Windows Server 2012.
  • Microsoft Windows 8 (32-bit or 64-bit) is the recommended operating system to run InTouch HMI client components.
  • Microsoft Windows Server 2012 is the recommended operating system to run InTouch HMI server components.
  • The recommended operating system for InTouch HMI development is Windows Server 2012 or Windows 8.
  • The recommended operating system for run-time nodes is Windows 8.

Wonderware InTouch HMI 2014 with Windows 7, Windows Server 2008 R2, and Later Operating Systems

  • Windows 7 and later operating systems do not support a dedicated single-node server configuration that runs one or more databases for an InTouch HMI system.
  • As of Wonderware System Platform 2014, a computer running Windows 7 or later operating systems can be configured as both an InTouch and an Application Server alarm provider. For more information, see Using Alarm Manager on a Single Node Running Both Wonderware InTouch HMI and Application Server Alarm Providers on Windows Vista and Later Operating Systems.
  • Wonderware InTouch HMI 2014 does not support the following legacy script functions on 64-bit systems: WWPoke(), WWExecute(), WWRequest(), ActivateApp() and SendKeys().
  • If Recipe Manager is started using the path Start\Program\Wonderware\InTouch\Recipe, then select Run as Administrator on Windows Vista or later operating systems.
  • The InTouch Extensibility Toolkit might need to be started by right-clicking and selecting Run As Administrator on Windows 7 or later operating systems to function properly.
  • The onscreen keyboard options have changed for the Windows 7, Windows Server 2008 R2, and later operating systems.
  • Hovering to select from the Windows keyboard does not work in the Windows 7, Windows Server 2008 R2, and later operating systems.

Wonderware InTouch HMI 2014 View Applications and DDE Support

NetDDE is not supported for InTouchView applications.

By design, an InTouchView application does not serve data to any other source, including InTouch HMI itself. When WindowViewer starts, it verifies if the application is an InTouchView application. When WindowViewer detects an InTouchView application, it does not register to become a DDE server. ArchestrA Symbols make use of the client layer when accessing InTouch tags, and appear as a third-party client trying to access WindowViewer as a data server. As a result, ArchestrA Symbols cannot communicate with InTouch tags when used with an InTouchView license.

In ArchestrA Symbols, InTouch:‹tagname› is still a valid method of referring to an InTouch tag on a local node.

Wonderware InTouch HMI 2014 Support for Windows User Account Control

Wonderware System Platform 2014 with InTouch HMI v11.0 supports User Account Control-enabled operations on run-time nodes.

Operating System Notes: Wonderware Application Server

  • Windows Server 2012 is the recommended operating system for the Galaxy Repository node.
  • Windows 8 is the recommended operating system for Wonderware Application Server development (IDE) or run-time nodes (Bootstrap).
  • The Bootstrap, IDE, and Galaxy Repository are supported by the following language versions of Microsoft operating systems: English, Japanese, Simplified Chinese, German, and French. The Galaxy Repository is also supported by the English, Japanese, Simplified Chinese, German, and French versions of Microsoft SQL Server 2008 SP3, SQL Server 2008 R2 SP2, and SQL Server 2012 SP1.
  • Upon installation, the selected language and regional settings must match those of the intended operating locale and must use the collation of SQL Server that matches the operating system locale.

Wonderware Application Server and DDE Support

In Windows 7, Windows Server 2008 R2, and later operating systems, DDE is supported only on a local node. Windows 7, Windows Server 2008 R2, and later operating systems do not support NetDDE. ArchestrA Symbols use the client layer when accessing InTouch tags and appear as a third-party client trying to access WindowViewer as a data server. Therefore the use of NetDDE for communication is not supported and not recommended.

In ArchestrA Symbols, InTouch:<tagname> is still a valid method of referring to an InTouch tag on a local node.

Using Wonderware Application Server with Windows 7, Windows Server 2008 R2, and Later Operating Systems

This section describes specific behaviors and restrictions when using the Windows 7 and Windows Server 2008 R2 operating systems with Wonderware Application Server.

  • The DDESuiteLink Client connection to the local DAServer using Local DDE is supported ONLY when the DAServer is configured as "Not a Service" and activated from its executable file or launched from InTouch. On Windows 7, Windows 2008 R2, and later operating systems, Local DDE is NOT supported when the DAServer is activated in the System Management Console (SMC).
  • For toolkits such as the ArchestrA Object Toolkit, GRAccess Toolkit, and MXAccess Toolkit to function properly on Windows 7 and later operating systems, you may need to start the toolkit by right-clicking on the file and then clicking Run As Administrator.

Wonderware Application Server and User Account Control Level

Wonderware Application Server 2014 supports User Account Control-enabled operations. Starting the IDE still requires elevated privileges.

Operating System Notes: Wonderware Historian Server

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:

    1. 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.
    2. 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)"
    3. Replication to the remote tier-2 historian fails.
    4. 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:

    1. Open a command prompt and run the following command: cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f
      2. This sets LocalAccountTokenFilterPolicy registry entry value to 1. In doing so, an elevated token for the user is generated.
    2. Restart the system.

Operating System Notes: Wonderware Historian Client

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.

Operating System Notes: Wonderware Information Server

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.

.NET Framework Requirements and Compatibility

IMPORTANT: We strongly recommended that prior to upgrading your existing applications to Wonderware System Platform 2014, that you back up your applications, become familiar with the changes introduced by Microsoft in .NET 4.5, and that you review your .NET scripts and .NET controls for any required changes. After upgrading to Wonderware System Platform 2014, 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. We also recommend you test the upgrade in a staging system prior to upgrading your production system.

Wonderware System Platform 2014 leverages Microsoft .NET Framework 4.5. The Wonderware System Platform installation program will install .NET 4.5 if it is not already present in your system. .NET 4.5 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 will use .NET 4.5. Other applications you may have on the same machine with dependencies on .NET 3.5 will access .NET 3.5.

All user-supplied .NET code that runs in the context of InTouch HMI and Application Server will now run under the .NET Framework 4.5. Although .NET Framework 4.5 is highly compatible with applications that are built with earlier .NET Framework versions, Microsoft has introduced changes in .NET 4.5 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 and earlier versions of Application Server, InTouch HMI, the Historian, Historian Client, and Wonderware Information Server. These changes may also affect .NET controls developed with .NET 3.5.

In ArchestrA scripting, some .Net codes could fail if not using proper text encoding, and could cause a script to exit without completion. The UTF8Encoder is the default BinaryStream decoder in .Net 4.5. To enable an ArchestrA script to decode ASCII XML data, for example, insert the following snippet:

BinaryReader streamReader = new BinaryReader(ms, new ASCIIEncoding());

To learn more about changes introduced in .NET Framework 4.5 see the following Microsoft resources:

What's New in the .NET Framework 4.5: http://msdn.microsoft.com/en-us/library/ms171868(v=vs.110).aspx
What's obsolete in the .NET Framework class library: http://msdn.microsoft.com/en-us/library/ee461502(v=vs.100).aspx
Migration Guide to the .NET Framework 4.5: http://msdn.microsoft.com/en-us/library/ff657133(v=vs.110)
.NET Framework 4 Migration Issues: http://msdn.microsoft.com/en-us/library/ee941656%28v=vs.100%29

Virtualization Host Support

Wonderware System Platform 2014 supports the following virtualization environments:

  • Microsoft Hyper-V: Windows Server 2008R2 SP1, Windows Server 2012, Windows Server 2012 R2, HA/DR
  • VMware 5.x including High Availability and Disaster Recovery (HA/DR) and VMotion

SQL Server Requirements

The following table describes the SQL Server requirements for all Wonderware System Platform 2014 components.

  2008 SP3 Express-SSMSE (32-bit) 2008 SP3 Standard, Enterprise (32-bit Only) 2008 R2 SP1,
2008 R2 SP2
Express-SSMSE (32-bit)		 2008 R2 SP1,
2008 R2 SP2 Standard, Enterprise (32/64 bit)		 2012,
2012 SP1 Express-SSMSE (32-bit)		 2012,
2012 SP1 Standard, Enterprise (32/64 bit)
Component:            
Application Server 2014 Y Y S Y S Y
InTouch 2014 Y Y S Y S Y
Historian 2014 Y Y S Y S Y
Historian Client 2014            
Information Server Portal 2014 Y Y S Y S Y
Size:            
Mini Installation (1-500 I/O per node) Y N Y Y Y Y
Small Installation (1-5,000 I/O per node) Y N Y Y Y Y
Medium Installation (5k-50k I/O per node) Y N Y Y Y Y
Large Installation (50k-400k I/O per node) N N N Y N Y
Preferred Environment (64-bit OS and SQL)           R

 

Supported Y
Small System Only S
Supported and Recommended R
Not Supported N
Not Applicable

 

We recommend that you install and configure the supported SQL Server version before you begin the Wonderware System Platform installation program, especially if you expect Wonderware Information Server to coexist, either on initial or subsequent installations, with the InTouch HMI, Application Server, or the Historian Server.

The Wonderware System Platform installer will install all prerequisites except the SQL Server requirement for installing the the Historian Server. If you select the Historian Server for installation, and if the supported version of SQL Server is not already installed, you must exit the installation program, install the supported SQL Server version, then resume the installation.

Considerations for SQL Server

  • Alarm DB Logger To use the Alarm DB Logger with SQL Server Express, you need to change the default authentication mode from Windows-based to Mixed Mode.
  • SQL Server Configuration Rights: While installing Wonderware System Platform, if the logged-on user performing the installation is not a SQL Server administrator, the Config SQL dialog box appears and requests SQL Server administrator credentials.
  • Maximum Server Memory: After installing SQL Server, Use SQL Server Management Studio to confirm that the Maximum Server Memory is configured to approximately 65% of the total available RAM. By default SQL Server does not clamp this setting. The Wonderware System Platform installation process will attempt to adjust it if it has the appropriate rights to configure SQL Server.
  • Restoring a CAB: You cannot restore a Galaxy .cab file backed up in SQL Server 2012 or SQL Server 2008 to a node with an earlier version of SQL Server. For example, you cannot restore a Galaxy .cab file backed up in SQL Server 2012 to a node with SQL Server 2008. For example, you cannot restore a Galaxy .cab file backed up on SQL Server 2008 to a node with SQL Server 2005. SQL Server database backups from SQL Server 2005 forward are not backward-compatible. Attempting such a restore results in an error message.
  • The MSSQL Server user account is not supported for the SQL Server 2012 Service. Instead, configure SQL Server to run as the local system or Network Service account. Named instances are not supported.
  • Migrating SQL Server Versions: You can migrate a SQL Server database to a later version from any of two prior versions. For example, you can migrate to SQL Server 2012 from SQL Server versions 2008 or 2005. You can migrate to SQL Server 2008 from SQL Server versions 2005 or 2000. You cannot migrate directly from SQL Server 2000 to SQL Server 2012. Such a migration requires an intermediate step. For more information and helpful procedures, see the following Microsoft references:
  • SQL Server Rights Requirements: SQL Server 2008 and later versions do not automatically create the BUILTIN\Administrators role delivered in SQL Server 2005. Because of this change to SQL Server, the Wonderware Application Server 2014 installation process will create the necessary operating system user group (aaAdministrators) as well as the necessary SQL Server role. This automated process will provide the rights required to allow operations within the Galaxy Repository without the need for blanket BUILTIN\Administrator rights. The aaAdministrators group must be present and enabled. If you accidentally delete the aaAdministrators group from the Windows operating system, you can run either of two options to restore it:
    • Run the Change Network Utility from the Windows Start menu.
    • Run the aaConfig SQL Utility from the Windows Start menu.

    If you accidentally delete the aaAdministrators group from the SQL Server security logins, you must run the aaConfig SQL Utility to restore it. Refer to the Wonderware Application Server User's Guide, "About ArchestrA User Accounts", for further information and procedures about restoring the aaAdministrators group.

Considerations for SQL Server Express

  • SQL Server Express is supported for use on an InTouch, Application Server, or Historian node, recommended for use only in small or development configurations. SQL Server 2012 SP1 Express is automatically installed for when you install for InTouch, Application Server, or the Historian, if, at time of installation, no other SQL Server elements are installed on the computer.
  • If you plan to use SQL Server Express with Wonderware Information Server 2014 and Wonderware InTouch HMI 2014 on the same node, the following limitations apply:
    • Installing Wonderware Information Server first, using the MS SQL Express default instance name set to "SQLEXPRESS", and then installing Wonderware InTouch HMI will work without issue. Note that in this scenario, each component uses a dedicated instance of SQL Server 2008 Express.
    • Installing Wonderware InTouch HMI first, which silently installs and configures SQL Server 2012 SP1 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.
    • SQL Server 2012 SP1 Express uses only one processor core.
  • For InTouch HMI-only installations, the Wonderware System Platform installer will automatically install SQL Server 2012 SP1 Express if these conditions are met:
    • No version of SQL Server is installed on the system.
    • You may select only InTouch Development and Runtime during the Wonderware System Platform installation. When you select InTouch Development and Runtime, a Galaxy Repository will be installed.

Additional SQL Server Notes for Wonderware Application Server

  • If multiple versions of SQL Server are installed, the one used as the Galaxy Repository must be the default instance. Named instances are not supported.
  • The Galaxy Repository locks the SQL Server maximum memory usage to 65% of the computer's physical memory.
  • TCP/IP must be enabled on the computer hosting a SQL Server database. The TCP/IP protocol setting can be verified from the SQL Server Network Configuration under SQL Server Configuration Manager.
  • To use the Alarm DB Logger with SQL Server Express, you need to change the default authentication mode from Windows-based to Mixed Mode.

Additional SQL Server Notes for Wonderware Information Server

  • Named instances are not supported.
  • Wonderware Information Server supports case-insensitive and case-sensitive SQL Servers.

Third-Party Application Prerequisites

For Wonderware Historian Client:

  • Microsoft Office is an optional prerequisite. If you install Office after installing Wonderware Historian Client, then the Historian Client add-ins do not appear in the list of available add-ins in Office. Run the Wonderware Historian Client installation program and repair the installation to get the add-ins loaded.
  • When you install Microsoft Office 2010 or Microsoft Office 2013 (32-bit) as a custom install, in addition to selecting the Microsoft Office and Excel features, you must also select Office Shared Features and Office Tools so that the Historian add-ins for Workbook or Report can be loaded.

For Wonderware Information Server:

Module or Component Details Required Version Recommended Version
SSRS SQL Server Reporting Services (to use the ArchestrA Reporting feature) 2008 SP3, 2008 R2 SP2, or 2012 SP1 2012 SP1
MS Excel Microsoft Excel (to use the ActiveFactory Reporting Website feature) 2010 or 2013 (32-bit) 2010 or 2013 (32-bit)
Microsoft ASP.NET Microsoft ASP.NET. The Wonderware Information Server post-installation Configurator utility automatically configures ASP.NET. 2.0 or 3.5 3.5
MSI Microsoft Windows Installer. This is included on the installation DVD and is automatically installed. 4.5 4.5
IIS Internet Information Services. You must perform a default installation, and the Wonderware Information Server post-installation Configurator utility automatically configures IIS. 7.0, 7.5, or 8.0 7.0, 7.5, or 8.0
IE Internet Explorer 8.0, 9.0, or 10.0 8.0
OSIsoft OLE DB client connectivity software Required on the Wonderware Information Server portal node for the Information Model to connect to an OSIsoft PI Server (OLE DB) data source. 3.3.0.1a 3.3.0.1a
Oracle client connectivity software Required on the Wonderware Information Server portal node for the Information Model to connect to an Oracle data source. 10g and 11g 10g and 11g
Microsoft Office 10 client connectivity software Required on the Wonderware Information Server portal node for the Information Model to connect to text (.csv) data source. Microsoft.ACE.OLEDB.12.0 Microsoft.ACE.OLEDB.12.0

Wonderware Information Server supports IPv4 only.

You must install Microsoft Excel with the Visual Basic for Applications feature on the Wonderware Information Server computer in order for Wonderware Historian Client published reports to be viewed.

The Wonderware Information Server installation program scans for these components. If the MSXML and Capicom components are not installed, the installation program silently installs them to the target computer. Note the following important information regarding individual components:

SQL Server Reporting Services: To use the ArchestrA Reporting feature, you must install and configure SQL Server Reporting Services and set up a reporting database before configuring the ArchestrA Reports feature in Wonderware Information Server. The versions of SQL Server and SQL Server Reporting Services used must match (for example, both 2008).
WebDAV Feature: For the Process Graphics feature to work, WebDAV is automatically installed during configuration of the Wonderware Information Server. You can manually download WebDAV from the following links:

1. For 32 bit Windows 2008 R2, visit www.wonderware.com/WIS/webDAVx86
2. For 64 bit Windows 2008 R2, visit www.wonderware.com/WIS/webDAVx64

Wonderware Product Compatibility

In a single-node environment, if you need to combine multiple products delivered within Wonderware System Platform 2014, all the products need to be the version delivered in Wonderware System Platform 2014.

In a node-to-node environment, products are compatible between the current licensed version and one licensed version back.

Compatibility means that the products can communicate with each other over the network. Co-existence means that the products can be installed on the same computer.

In some cases, Wonderware System Platform is supported in newer environments than a compatible product. Wonderware System Platform has been tested for compatibility with a listed product only in the environments that are supported by that particular product.

Product Version Compatibility Co-existence
Wonderware System Platform 4.5 N N/A
2012 Y N/A
2012 R2 Y N/A
2014 Y N/A
Wonderware InTouch CE 10.1 N N
Wonderware Manufacturing Execution System 4.0 SP1 N N
4.0 SP2 N N
4.5 P01 Y Y
Wonderware InControl™ 7.11 SP2 P01 N N
Wonderware Manufacturing Execution Module 1.0 Y N
Wonderware InBatch™ 9.6 (2012) Y Y
Wonderware QI Analyst™ 8.0 SP1 P01 N N
8.0 SP2 Y Y
8.0 SP3 Y Y
Wonderware SCADAlarm™ 6.0 SP2 P01 N N
Wonderware Intelligence 1.5 N N
1.5.100 (2012) Y Y
ArchestrA Workflow™ 1.5 (2012) N N
1.6 (2012 SP1) N N
1.7 (2012 R2) N N
1.8 N N
1.9 (2012 R2 SP1) Y Y
Wonderware PEM 2.1 SP1 Y Y

Supported Y
Not Supported N

 

Notes:

  • The extended features of the ArchestrA Web Exporter only support ArchestrA Symbols and InTouchViewApp applications from Wonderware Application Server 3.1 or later, InTouch HMI 10.0 SP2 or later, and InTouch HMI 10.1 or later.
  • HTTP access to Historian Server is not supported in this version.
  • Publishing from ActiveFactory 9.2, Historian Client 10.0, 10.0 SP1, and 10.0 SP2 is supported.
  • Opening of already published Historian Client workbook reports and trends (published from an old version of Historian Client) in Wonderware Information Server 4.5 is supported.
  • Publishing from ActiveFactory 9.2, Historian Client 10.0, 10.0 SP1, and 10.0 SP2 to Wonderware Information Server versions prior to 4.5 is not supported.
  • If you are using FCS with Wonderware Information Server, note that a direct upgrade from Wonderware System Platform 4.5 to 5.1 is not supported for FCS. You must first upgrade to Wonderware System Platform 5.0.

The product compatibility information contained in this Wonderware System Platform 2014 Readme supersedes information contained in other product Readme files delivered on the Wonderware System Platform 2014 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 Readme duplicates some of the same information contained in this Readme, but is focused on InTouch HMI.

Wonderware System Platform Installation

For detailed installation instructions in English, see the Wonderware System Platform Installation Guide (WSP_Install_Guide.pdf) or Wonderware System Platform Installation Help (WSP_Install_Guide.chm). This guide supersedes the separate installation guides for the individual products.
The 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.

Before Installing Wonderware System Platform 2014

About the ArchestrA User Account

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

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

If the ArchestrA user account has not previously been configured, you will be prompted to configure it during the Wonderware System Platform 2014 installation. You must specify a user name, password, and domain.

If you choose to use existing user account, it should meet the following requirements:

  • User account with a permanent password that does not expire.
  • User account in which the password cannot be changed.
  • User account that is a member of the local Administrators group.

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

Note: If you re-create the user account using the Change Network Account utility, the Microsoft Windows security component on the computer can take several minutes to update this information on the ArchestrA Galaxy node. Until that occurs, the ArchestrA component may not function properly. Restarting the Galaxy node updates this information immediately.

Wonderware System Platform Upgrade and Migration

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.

The earliest version of Windows supported by Wonderware System Platform 2014 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, 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.

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.

Product From Upgrade Node-by-Node Upgrade Migrate
Wonderware System Platform 4.5 Y Y Y
2012 Y Y Y
2012 R2 Y Y Y
2012 R2 P01 Y Y Y
Wonderware Application Server 2.0 P01 N N N
2.1 P02 N N N
2.5 N N Y
3.0 SP2 N N Y
3.1 (no SP) N Y Y
3.1 SP1 N Y Y
3.1 SP2 N Y Y
3.1 SP2 P01 N Y Y
3.1 SP3 Y Y Y
3.1 SP3 P01 Y Y Y
For 3.2 and later, see System Platform. - - -
Wonderware InTouch 7.0 N N/A N
7.1 N N/A N
7.11 P07 N N/A Y
8.0 SP2 P04 N N/A Y
9.0 P03 N N/A Y
9.5 SP1 N N/A Y
10.0 SP2 N N/A Y
10.1 (no SP) N N/A Y
10.1 SP2 N N/A Y
10.1 SP2 P01 N N/A Y
10.1 SP3 Y N/A Y
10.1 SP3 P01 Y N/A Y
For 10.2 and later, see System Platform. - - -
Wonderware Historian 8.0 SP3 P01 N N/A N
9.0 P02 N N/A Y
10.0 SP1 Y N/A Y
For 11.0 and later, see System Platform. - - -
Wonderware Historian Client 9.2 N N/A Y
9.5 N N/A Y
10.0 N N/A Y
10.0 SP1 N N/A Y
10.0 SP2 Y N/A Y
10.1 Y N/A Y
Wonderware Information Server
(Portal and Client)		 3.1 N N/A Y
4.0 N N/A Y
4.0 SP1 N N/A Y
4.5 Y N/A Y
5.0 Y N/A Y
5.0 P01 Y N/A Y
FS Gateway 1.5 Y N/A Y
2.0 Y N/A Y
3.0, 3.0 SP1 Y N/A Y

Supported Y
Not Supported N

Application Server Upgrade and Migration Notes

If you are upgrading Wonderware Application Server to the new Wonderware System Platform 2014 version, be aware of the following:

  • Back up the Galaxy before starting the upgrade. Also, upload any run-time changes for critical objects. You cannot upload any run-time changes after you upgrade the system. For more information, see the Wonderware System Platform Installation online help.
  • Upgrading to Wonderware Application Server 2014 will affect run-time nodes. Node-by-node upgrade is supported with limitations. Changing the security or history model in a node-by-node upgrade of the run-time nodes is not supported. Nodes that are currently deployed will not receive any history or security changes from the upgraded Galaxy Repository node.
  • Installing Wonderware Application Server 2014 automatically undeploys any platform that is currently deployed in the node that is being updated. Changes to the WinPlatform object and other components require any deployed platforms to be redeployed.
  • When upgrading SQL Server on the Galaxy Repository node, back up the Galaxy before starting the upgrade. Upload any run-time changes for critical objects. You cannot upload any run-time changes after you upgrade the system. For more information, see the Wonderware Application Server Installation online Help.
  • If Wonderware Application Server is installed on the same node as Wonderware InTouch HMI, both must be upgraded to Wonderware System Platform 2014 versions, and you must upgrade Wonderware Application Server before upgrading InTouch HMI.
  • You must install Wonderware Historian 9.0 Patch 02 or Historian 10.0 or later to take advantage of new Historian features including time propagation and late data from the Wonderware Application Server to the Historian. These versions are also required to leverage the new Historian configuration options from the IDE.
  • If the ArchestrA IDE currently connects remotely to the Galaxy Repository on another computer, install Wonderware Application Server 2014 on both nodes. A remote connection between the ArchestrA IDE and the Galaxy Repository fails if the nodes have different versions of Wonderware Application Server.
  • It is strongly recommended that you un-deploy the platform prior to upgrading the software in that node. Once the Galaxy Repository node is upgraded from any prior version to version 4.0, all run-time nodes hosting Wonderware InTouch applications must have both Wonderware Application Server upgraded to 2014 (if you are running InTouch applications). You will not be able to deploy or un-deploy objects on non-upgraded nodes. Installing the software on a run-time node will remove the running platform and objects. The platform and objects can then be redeployed after the software upgrade is complete.
  • Upgraded IDE/Client nodes cannot connect to a non-upgraded Galaxy Repository and vice-versa.
  • The Galaxy Repository node will be undeployed before upgrading to Wonderware Application Server 2014.
  • Running platforms must be undeployed during the upgrade process.
  • WinPlatform and other related objects on a remote node will be marked as "software update pending".
  • You will not be able to deploy from an upgraded Galaxy Repository node to non-upgraded remote nodes.
  • While migrating the GR node, the existing database schema is migrated to the new version 2014 schema. The GR node migration fails if the GR node is used as a run-time node for another GR.
  • IMPORTANT! If the Wonderware Historian will be used to collect data from Application Server, upgrade the Historian to 2014 before upgrading any Application Server Platforms to 2014.

InTouch Upgrade and Migration Notes

If you are upgrading Wonderware InTouch HMI to the new Wonderware System Platform 2014 version, be aware of the following:

  • InTouch Development (WindowMaker™) is now installed with support for ArchestrA graphics. This includes the ArchestrA Integrated Development Environment (IDE), Bootstrap, Galaxy Repository (GR), and FS Gateway.
  • FactorySuite Gateway (FS Gateway) 3.0 SP1 is installed as part of InTouch HMI 2014 in an Wonderware System Platform 2014 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 will not upgrade FSGateway to version 3.0 SP1. You must uninstall FSGateway 2.0 SP1 before upgrading to Wonderware System Platform 2014.
  • If SQL Server does not exist on the system, SQL Server Express is installed automatically.
  • If the added features are not needed in your current environment, you will need to use the Wonderware System Platform "product-based" installation on a "clean" system. The product-based installation provides a customization option so that you can deselect any components that are not needed. Note that the customization option is not available if you are upgrading an existing system from a previous version of InTouch Development.
  • If Wonderware Application Server is installed on the same node as Wonderware InTouch HMI, both must be upgraded to ArchestrA 2014 versions, and you must upgrade Wonderware Application Server before upgrading InTouch HMI.
  • If you are using managed InTouch applications with ArchestrA Symbols from Application Server 3.1 SP3 or earlier, run the ArchestrA Symbol Analysis and Repair Utility before installing Wonderware Application Server 4.0 to ensure that all issues reported by the utility are addressed. You can download the utility from the Wonderware Developers' Network (WDN), Software Downloads. Log in to WDN with your username and password to access the downloads archive.

Wonderware Historian Upgrade and Migration Notes

It is possible to upgrade from earlier versions of Wonderware Historian than 10.0 SP1, but you must first upgrade to the 10.0 SP1 version. Follow the instructions in the 10.0 SP1 documentation to perform the upgrade. After you have upgraded to the 10.0 SP1 Historian, you can then upgrade to Wonderware Historian 2014.

IMPORTANT! If the Wonderware Historian will be used to collect data from Application Server, upgrade the Historian to 2014 before upgrading any Application Server Platforms to 2014.

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

 

Licensing Information

Once installed, the ArchestrA License Manager can be found in the \Invensys folder on the Start menu rather than in the old License Utility folder, \Wonderware\Common.

License Server

Wonderware Information Server 2014 supports using a centralized licensing server to manage client licenses. For more information, see the Invensys License Manager Guide and the license server documentation in the \InstallFiles\CD-Licensing\UserDocs folder of the Wonderware Information Server 2014 installation media.

You can install the License Server as part of any Wonderware System Platform installation. If you install Wonderware Information Server, the License Server automatically installs whether or not you specifically selected it for installation.

Antivirus Software Exclusions

Configure your antivirus software to prevent archive files from being scanned.

Important Note: The paths listed here may be different based on your installation. If you are using Wonderware Historian, be sure to exclude any folder that contains history blocks.

  • Ensure that subfolders of the listed directories are also excluded.
  • If you are using a 64-bit operating system, folder names must be specified accordingly. For example, the program files root directory in a 64-bit operating system is C:\Program Files (x86)\... and the application data root directory in a 64-bit operating system is C:\ProgramData\...

Exclude these ArchestrA folders in a 32-bit system:

  • C:\Program Files\ArchestrA\*.*
  • C:\Program Files\Common files\ArchestrA\*.*
  • C:\Program Files\FactorySuite\*.* (The FactorySuite directory may not exist in newer installations)
  • C:\Program Files\Wonderware\*.*
  • C:\InSQL\Data\*.*
  • C:\Historian\Data\*.*
  • C:\Documents and Settings\All Users\Application Data\ArchestrA*.*

Exclude these ArchestrA folders in a 64-bit system:

  • C:\Program Files (x86)\ArchestrA\
  • C:\Program Files (x86)\Common files\ArchestrA\
  • C:\Program Files (x86)\FactorySuite\ (The FactorySuite directory may not exist in newer installations)
  • C:\Program Files (x86)\Wonderware\

Exclude these folders:

  • History Store Forward directory default location:
    • C:\Documents and Settings\All Users\Application Data\ArchestrA\
    • C:\Users\All Users\ArchestrA\
  • Checkpoint directory location default location:
    • C:\Program Files\ArchestrA\Framework\bin
    • C:\Program Files (x86)\ArchestrA\Framework\bin
  • InTouch HMI Application folder path:
    • C:\Documents and Settings\All Users\Application Data\ArchestrA\
  • SMC Logger Storage file path:
    • C:\Documents and Settings\All Users\Application Data\ArchestrA\LogFiles\
  • SQL Server database files of type:
    • .mdf
    • .ldf

Exclude these folders for Wonderware Information Server:

  • \inetpub\wwwroot\Wonderware
  • \\inetpub\wwwroot\AFWeb
  • \\inetpub\wwwroot\aaFlexLicWebService
  • \\Program Files\Wonderware\SuiteVoyager

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.

L00128517 In a Multi-Galaxy Communication scenario involving communication with an ArchestrA System Platform 2012 R2 galaxy or an ArchestrA System Platform 2012 R2 Patch 01 galaxy, galaxy remote references from InTouch HMI or from Application Server might intermittently fail to resolve. A HotFix is available from Wonderware Technical Support if you require Multi-Galaxy Communication, and you are using a galaxy version prior to Wonderware System Platform 2014.

Known Issues

The following important known issues are listed by their assigned CR number in ascending order. Additional known issues are documented in the product-specific Readme files.

Installation Issues

L00101032: 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."

To resolve this issue, configure Wonderware Information Server. You will then be able to uninstall the other products.
L00114588: You must manually install the language packs for the Wonderware Historian Client product by running the setup.msi file in the appropriate subfolder of the following folder of the Wonderware System Platform DVD: ...\Wonderware System Platform\CD-HistorianClients\HistorianClient\Lang\.
L00114910: On a computer running the Windows Server 2008 R2 or Windows 7 (64-bit) operating system, a blank domain is shown in Admin User Page when you clear the Create Local Account check box. This behavior is a result of the browser service being disabled by default on the computer running the Windows Server 2008 R2 or Windows 7 (64-bit) operating system.
L00116883: Due to a Windows operating system issue, Wonderware InTouch HMI and related applications, such as Alarm DB Logger, can crash on startup if installed to a drive other than C:\. As a workaround, create an empty file named win.ini in folder C:\Users\<username>\AppData\Local\Wonderware where "username" is the name of the user attempting to start the application.
L00120356: Creating a new graphic toolset, or creating a new symbol in an existing toolset, from the Graphic Toolbox in the IDE can result in errors in the logger if Wonderware Intelligence 1.5 is also installed. Creating a new symbol directly under the galaxy rather than from the Graphic Toolbox does not result in logger errors. Functionality is not impacted, and the logger errors can be ignored.
L00123209: When installing Wonderware System Platform, the system cannot read the Wonderware Application Server license if the Galaxy Repository and the IDE are installed on a node where Wonderware InBatch or other Invensys products are already installed. As a workaround, use the License Manager to reinstall the ArchestrA license for Application Server after the Wonderware System Platform installation is complete.
L00128943: While installing Wonderware System Platform, if the logged-on user (the installer) is not a SQL Server administrator, the Config SQL dialog box appears and requests SQL Server administrator credentials. If invalid credentials are entered multiple times before valid credentials are entered, the Application Server installation will fail, prompting for a CD location - even though the CD location is already available - and post-installation ArchestrA Service Bus configuration steps also will fail. As a workaround, uninstall any System Platform components already installed, then reinstall Wonderware System Platform. Enter correct SQL Server administrator credentials when requested.
L00129565: If you select InTouch Access Anywhere Server from the Feature Customization screen, the Runtime documentation and the InTouch supplementary documentation are not installed on the system.

As a workaround, install by selecting InTouch Access Anywhere and InTouch Runtime from the product quick pick screen, and then proceed with installation.

Upgrade and Migration Issues

L00115049: Errors occur when deploying to a remote node after a node-by-node upgrade.

Workaround: Ensure the Galaxy Repository node is upgraded completely including restarting before upgrading any other Galaxy node that has a deployed platform.
L00122615: The QI Analyst 8.0 SP2 link to the Historian Server will be broken if Historian Client is installed on the same system. A hotfix is available upon request from Customer Support.
L00123504: Unexpected and misleading errors can appear in the logger while migrating particularly large galaxies because the transaction log for the galaxy database has reached its maximum allocated size.

Example error: "Error 80040E2F: Description 'Violation of PRIMARY KEY constraint 'PK__#0489BFA__6B888F1106720818'. Cannot insert duplicate key in object 'dbo.@checked_in_non_relative_unbound_elements_to_bind'. The duplicate key value is (15767, 25329, 420, 1),'".

Example error: "Query returned more than one row".

You can do the following steps to remove restrictions on the size of the galaxy database transaction log:
  1. Scan windows events (in the Event Viewer) for evidence that the transaction log is in fact full.
  2. If you confirm that the transaction log has exceeded size restrictions, do the following to remove the restriction:
    1. In SQL Server Management Studio, right click the galaxy database, then click Properties on the context menu.
    2. In the Database Properties dialog, select the Files page.
    3. Locate Log ... in the File Type column, then click the ellipsis (...) button in the Autogrowth column on the same line.
    4. In the Change Autogrowth for Base_Application_Server_log dialog, click the Unrestricted File Growth radio button under the Maximum File Size parameter. Click OK.
  3. Complete the galaxy migration, then repeat these steps to reinstate a file size ceiling on the transaction log.

ArchestrA Service Bus and Multi-Galaxy Communication Issues

L00123433: 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.

For example:
  1. Install the latest Application Server software on two nodes, Node1 and Node2.
  2. Create a galaxy with a platform, and pair the nodes.
  3. On Node1, uninstall Application Server and restart the system.
  4. On Node 1, if the ASBService user still exists in SQL Server, delete the user manually before re-installing Application Server.
  5. On Node1, reinstall Application Server and connect to the same galaxy.
  6. 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.
  7. Un-pair and re-pair Node1 to get the new Discovery Service and pairing information from Node2.
L00123462: In a multi-galaxy environment, you can pair galaxies by IP address rather than using a node name (computer machine name). Unpairing galaxies identified by IP address fails when NetBIOS and DNS solutions are unavailable. Where your galaxies are identified by IP address, you must create a temporary host file to map the IP addresses as hostnames for purposes of unpairing.

For example, Node1 and Node2 are identified by IP address and are paired. To unpair them, do the following:
  1. Navigate to the Hosts file on Node1. In Windows 7 and Windows 2008 R2 operating systems, the Hosts file typically can be found at C:\Windows\System32\Drivers\Etc\.
  2. Open the Hosts file in Notepad. In Windows 7 and Windows 2008 R2 systems, you should right click the Notepad executable, and click Run as Administrator, then open the Hosts file from inside Notepad.
    Alternatively, you can click Start, then click Run, then enter the following command in the text box:
    notepad c:\Windows\System32\Drivers\Etc\Hosts.
  3. Edit the Hosts file:
    1. Enter the IP address for Node2.
    2. On the same line as the IP address, provide a node (computer) name.
    3. Enter IP addresses and node (computer) names for each node identified by IP address to be unpaired.
  4. Save and close the Hosts file. You should now be able to unpair the galaxies.
L00123474: Writing from InTouch to a remote galaxy using indirect tags can fail for some of the remote references. Object Viewers on two different nodes may show different values for the same reference. You can avoid this issue by deactivating Advanced Communication Management in the IDE. Additionally, if you use the same indirect tag with scripting more than one time, you can modify your scripts to set the indirect tag's name property to an empty string after the loop completes. For example, in the following script snippet, you would add the line highlighted with bold text:
IF bRunScript  THEN

    FOR tagval = 1 TO 3
      indirect.Name = "Testtag" + Text(tagval, "0");
    
        IF indirect.Value > 4  THEN
                indirect.Value  = 0;
            ELSE
                indirect.Value  = indirect.Value  + 1;
                indirect.Value  = indirect.Value  + 1;
            ENDIF;      
    NEXT;
      indirect.Name = "";

ENDIF;
L00123475: When configuring user-configurable ArchestrA Services - ASBGRBrowsing service, ASBMxDataProvider service, and ASBAuthorization service - it is important not to assign the same port number to two instances of a service on the same node. However, it can occur that while creating instances of a service and assigning them to the same node, that the system can erroneously assign a duplicate port number by default. The main symptom of this error is that you do not see a remote galaxy where expected, such as in a list of available galaxies in the Galaxy Browser. As a first step in troubleshooting this problem, do the following:
  1. Open the Configure ArchestrA Services utility.
  2. Note the port number of the ASBGRBrowsing service instance for the missing galaxy.
  3. Compare this to the port numbers of other ASBGRBrowsing service instances assigned to the same node.
  4. If you find a service instance with a duplicate port number on the same node:
    1. Undeploy the browsing service of the missing galaxy.
    2. Change the port number to a unique number for that node.
    3. Redploy the browsing service instance.
L00123478: Attempting to deploy a platform on a remote node can result in errors. Repeated attempts to deploy the platform can succeed, but the ASB Services can become unavailable on the remote node after deploying the remote platform. As a workaround, undeploy and redeploy the remote platform.
L00123602: Buffered data is not supported in a multi-galaxy environment.
L00125223: If you create galaxies on separate nodes, with Wonderware System Platform 2014 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.

Documentation

The Wonderware System Platform documentation is available Adobe Acrobat .pdf files that are available from the following locations on the Wonderware System Platform DVD:

\Wonderware System Platform\CD-ApplicationServer\UserDocs\English

\Wonderware System Platform\CD-Historian-x64\UserDocs\English

\Wonderware System Platform\CD-HistorianClients\HistorianClient\Docs

\Wonderware System Platform\CD-Intouch\UserDocs\English

\Wonderware System Platform\CD-WIS\UserDocs\English

To view the documentation, you must first download the latest version of Adobe Reader from the Adobe Corporation web site: http://www.adobe.com/products/acrobat/readstep2.html.

You can also access online Help systems from within the software.

Common User Documentation

  • Wonderware System Platform Installation Guide. This guide provides information on installing the Wonderware System Platform, including hardware and software requirements and migration instructions.
  • Log Viewer User's Guide. Explains how to use the Log Viewer utility to determine system diagnostics.
  • Log Flag Editor Utility Guide. Explains how to turn on and off certain diagnostics logging messages.
  • Invensys License Manager Guide. Explains how to install and manage product licenses.
  • Wonderware ArchestrA Protocol Guide. Explains background information on the main protocols used between components of Wonderware products.

Wonderware InTouch HMI 2014 Documentation

  • InTouch HMI Concepts and Capabilities Guide. Describes all of the features and main concepts in the InTouch HMI without going too deep into the technical and procedural details.
  • The InTouch HMI Application Management and Extension Guide. Describes how to create and manage InTouch applications locally and in a network environment.
  • InTouch HMI Data Management Guide. Describes how to work with data items in the InTouch HMI and connect your application to the physical devices in your plant environment.
  • InTouch HMI Visualization Guide. Describes how to develop the graphical operator interface of an InTouch application.
  • InTouch HMI SmartSymbols Guide. Describes how to create reusable templates for graphic symbols that can save you a lot of engineering time and effort.
  • InTouch HMI and ArchestrA Integration Guide. Describes how to integrate the InTouch HMI and ArchestrA technology to develop more robust applications that use richer graphics.
  • InTouch HMI Alarms and Events Guide. Describes how to configure alarms for your data items, how to view and acknowledge alarms, and how to use the alarm clients and utilities supplied with the InTouch HMI.
  • InTouch HMI Scripting and Logic Guide. Describes how to write scripts in the InTouch HMI to automate common tasks and processes. This guide includes a reference of the InTouch scripting language and functions.
  • InTouch HMI Supplementary Components Guide. Describes software components that you can optionally install and use with the InTouch HMI.

Wonderware Application Server 2014 Documentation

  • Wonderware Application Server User's Guide. Explains configuring and deploying Wonderware Application Server applications.
  • Creating and Managing ArchestrA Graphics User's Guide. Explains how you create and manage graphical symbols using the ArchestrA Symbol Editor within the Integrated Development Environment (IDE).
  • Wonderware Application Server Scripting Guide. Reference for the scripting language in Wonderware Application Server.
  • Object Viewer User's Guide. Explains how to acquire run-time data using the Object Viewer.
  • Guide to the ArchestrA Alarm Control. Explains how to configure the alarm control (client) to show current and historical alarms and events in a grid.
  • Guide to the ArchestrA Trend Client. Explains how to configure a chart to trend real-time data values.
  • Platform Manager User's Guide. Explains how to start and stop system components.
  • Galaxy Database Manager User's Guide. Explains how to backup and restore the Galaxy database.
  • Wonderware InTouch HMI and ArchestrA Integration Guide. Explains how you can use the ArchestrA Integrated Development Environment (IDE) to manage InTouch HMI applications so that you can use symbols you create in the ArchestrA Symbol Editor.

Wonderware Historian Server 2014 Documentation

  • Wonderware Historian Concepts Guide. Provides an overview of the entire Wonderware Historian system and describes each of the subsystems in detail.
  • Wonderware Historian Administration Guide. Describes how to administer and maintain an installed Wonderware Historian, such as, configuring data acquisition and storage, managing security, configuring replication, and monitoring the system.
  • Wonderware Historian Database Reference. Provides documentation for all of the Wonderware Historian database entities, such as, tables, views, and stored procedures.
  • Wonderware Historian Glossary. Provides definitions for terms used throughout the documentation.

Wonderware Historian Client 2014 Documentation

  • Wonderware Historian Client Software User's Guide Describes how to use stand-alone applications, Microsoft Office add-ins, and ActiveX and .NET controls to retrieve and display data.

Wonderware Information Server 2014 Documentation

  • Wonderware Information Server Administration Guide. Describes how to administer and maintain a Wonderware Information Server, including configuring data sources, managing security, and performing customizations.
  • Wonderware Information Server Win-XML Exporter Guide. Describes how to use the Win-XML Exporter to convert InTouch HMI application windows to web pages and publish them to the Wonderware Information Server. This guide also includes a section for designing InTouch HMI application windows for Wonderware Information Server. This section describes how to best design InTouch HMI windows so that they can be successfully converted and optimally viewed in the portal.
  • ArchestrA Web Exporter Guide. Describes how to use the ArchestrA Web Exporter to publish ArchestrA Symbols and InTouch HMI Windows to Wonderware Information Server. This guide also describes how to add, delete and modify WindowSets and SymbolWeaverSets of the project and preview them in the preview window of ArchestrA Web Exporter.
  • ActiveFactory for Wonderware Information Server Help. Describes how to use the ActiveFactory for Wonderware Information Server web portal to view a variety of reports that include data from Wonderware Historians.
  • ArchestrA License Manager Guide. Describes the ArchestrA License Manager and how to use it to install and manage licenses and license servers on local and remote computers.

Documentation Issues

The following table lists important Wonderware System Platform documentation corrections. For documentation corrections for individual System Platform products, see the individual product Readme files.

Item Location of Change Existing Documentation Change
1 Invensys License Manager Guide (InvensysLicenseManagerGuide.pdf),

"Customizing the System Hierarchy" section, page 38

(InvensysLicenseManager.chm),

"Customing the System Hierarchy" topic		 Note: You can edit a site, system, machine, and service name but only to change the name or description. Delete existing note
2 Creating and Managing ArchestrA Graphics User's Guide (AAGraphics.pdf), Chapter 7

"Updating Element Styles" section, page 213, and

"Applying Element Styles to Elements" section, page 221		 N/A Add the following:

When you modify an element style, you must close and reopen WindowMaker to propagate the modified style to WindowMaker.

 

 

© 2014 Invensys Systems, Inc. All Rights Reserved.

Источник — «http://archestra.ru/index.php?title=System_Platform_2014_Patch_01&oldid=3568»