INDUSTRIAL SPARE PARTS SUPPLIER

INDUSTRIAL SPARE PARTS SUPPLIERIMPEXRON GROUP COMPANIES

GERMANY USA IMPEXRON GMBH ONRION LLC

Gönningerstr. 99, 72793 93 South Railroad AvenuePfullingen, GERMANY Bergenfield 07621 NJ,USA0049 7121 305 9012 001 973 536 2331

JAPAN ITALIAYUSAKI LLC PARTELLI SRL

Build.No. K7 1F, 13-16 Str Via Santissima 20584-0032, Osaka-Fu, Japan Brescia Italia

0081 721 26 8450 0039 030 7640137

TURKEY MEXICOOZHAT LTD PARMEX SRL

Buttim Is Mrkz. A2-367 PRIVADA 10 B SUR #390819250, Bursa. Turkey 72530, Puebla, Mexico0090 224 211 2241 0052 222 9126090

FRANCE BULGARIAFABRIMAT SARL IMPEXRON LTD

4 boulevard Carnot 95400 bul. "6-ti septemvri" 254,Paris, France 4006 Plovdiv, Bulgaria

0033 1 79 97 40 05 00359 32 571 212

UKRANIAOTEC LTD IMPEXRON LTD

Ivana Franko Street , 55 ul.Spiro Gulapcev br.4465049 Odessa, Ukraine 1000 Skopje, Makedonija

00380 48 7348522 00389 2 3114495

[email protected] [email protected] www.onrion.com

[email protected] [email protected] www.partelli.it

[email protected] [email protected] www.parmex.com.mx

[email protected] [email protected] www.impexron.bg

MAKEDONIJA

[email protected] [email protected] www.impexron.mk

mailto:[email protected]


http://www.impexron.de/

http://www.onrion.com/



http://www.yusaki.jp/

http://www.partelli.it/



http://www.ozhat.com.tr/

http://www.parmex.com.mx/



http://www.fabrimat.fr/

http://www.impexron.bg/



http://www.otec.com.ua/

http://www.impexron.mk/

12/18/2014 Wonderware InTouch HMI Readme

https://wdnresource.wonderware.com/support/patchfixes/1/Readme_IT/Readme.html 1/17

Wonderware InTouch HMI 2014 R2 (Version 11.1) ReadmeLast revision: 12/02/2014

About This ReadmeThis Readme provides information about InTouch HMI 2014 R2 (Version 11.1). Readme files from previous releases of Wonderware InTouch HMI are posted on the WonderwareDeveloper Network at http://wdn.wonderware.com/Downloads.

This Readme includes the following sections:

New Features in InTouch HMI 2014 R2

System Requirements

Component Compatibility

Wonderware InTouch HMI Installation

Resolved Issues

Known Issues

Documentation Issues

InTouch Documentation

Important!FactorySuite Gateway (FS Gateway) 3.0 SP1 is installed as a hidden feature of InTouch HMI 2014 R2 (v11.1) in a Wonderware System Platform (ASP) 2014 R2 installation.

If you previously installed FS Gateway 2.0 SP1 without any other InTouch products, then installing Wonderware System Platform 2014 R2 will upgrade FSGateway toversion 3.0 SP1.

If you previously installed FS Gateway 2.0 SP1 as part of ArchestrA System Platform 2012 with InTouch 10.5, you must uninstall FS Gateway before upgrading toWonderware System Platform 2014.

For more information about FS Gateway installation, upgrade, and uninstall, see the Wonderware System Platform Installation Guide, "InTouch HMI Requirements and Prerequisites"section, "Installing FS Gateway and Modifying FS Gateway Installations" topic.

< top of document >

New Features in Wonderware InTouch HMI 2014 R2ArchestrA Graphic Toolbox in WindowMakerInTouch WindowMaker incorporates the ArchestrA Graphic Toolbox containing a full complement of ArchestrA and Situational Awareness Library symbols. You can add asymbol to a Modern or managed InTouch application by dragging a symbol from WindowMaker's ArchestrA Graphic Toolbox and dropping it onto an InTouch window.

Modern InTouch ApplicationsModern InTouch applications give you the capability to easily integrate ArchestrA symbols directly into your applications. You create and manage Modern applicationsfrom InTouch Application Manager. All procedures to configure a Modern application are completed from InTouch WindowMaker.

You simply drag and drop ArchestrA or Situational Awareness Library symbols onto to an InTouch application window. Modern applications combine the capability ofintegrated ArchestrA symbols in managed InTouch applications with the familiar work flow of standalone InTouch applications.

Conversion of InTouch Windows to ArchestrA SymbolsYou can convert selected windows of managed or Modern InTouch applications to ArchestrA symbols. The converted ArchestrA symbols appear in the WindowMakerArchestrA Graphic Toolbox and the ArchestrA IDE Graphic Toolbox. In addition to graphics that appear in windows, all InTouch animation links embedded in windows areconverted to the corresponding ArchestrA animation.

After conversion, the original converted InTouch window is backed up. A new InTouch window is created in the InTouch application, which embeds the newly createdArchestrA symbols.

Additional Situational Awareness Library SymbolsInTouch HMI 2014 introduced an extensive set of Situational Awareness Library symbols. InTouch HMI 2014 R2 includes additional new or updated SituationalAwareness Library symbols for alarms, trends, and valves:

Alarms

SA_AlarmSeverity: Shows an alarm summary that includes Alarm Border animation and alarm counts by severity and acknowledgement status.

SA_Alarm_HistoryPage: Provides a tabbed page to show historical events or alarms by severity over a specified period.

SA_Alarm_RuntimeBanner: Shows alarms by area and includes buttons to acknowledge alarms.

SA_Alarm_RuntimePage: Provides a tabbed page to show current events or alarms by severity.

Trends

SA_Trend_SinglePen: Shows a trend line of historical and current measured values and provides Wizard Options to show a grid that includes X and Yaxes.

SA_Trend_MultiPen: Shows up to four simultaneous trend lines of current and historical measured values.

Valves

InTouch HMI 2014 R2 includes a set of twoway, threeway, and fourway valve symbols. The valves are named:

SA_Valve_2Way

SA_Valve_2WayAngle

SA_Valve_3Way

SA_Valve_4Way

Each valve symbol includes an extensive set of Wizard Options to configure the following functional components:

Type of valve main signal (analog or discrete)

Type of valve actuator (solenoid, digital, rotary, diaphram, spring, manual, or hydraulic)

Type of valve body (general, globe, diaphram, ball, butterfly, or needle)

http://wdn.wonderware.com/Downloads



Orientation (up, down, right, or left)

Graphic ConnectorsA 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 pointon one graphic element and ends at a connection point on another element.

Connectors are particularly useful for complex symbols containing many connected elements like flow diagrams, industrial piping, or electrical wiring. Connectors canchange length or orientation in response to changes to the positions of connected graphic elements. Using connectors, graphic elements within a symbol can be moved,resized, or rotated and still maintain the connector between elements.

The boundary border around each graphic element includes eight connection points to attach a connector. The Tools menu includes a Connection Point tool to addcustom connection points on a graphic element. Also, control points can be added to a connector to change its shape. The shape of a connector can be changed bydragging a line segment between control points to another position with your mouse.

Historical Statistical Summary DataYou can add a custom property and set the Data Type property to History Summary to reference historical data collected over a specified period during run time. TheHistorian 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 Displayanimation. Also, two functions have been added to enable the user to retrieve quality and timestamp from a custom property.

A custom property analog reference can subscribe to statistics from analog data saved to the Historian to show typical statistical values like average, counts, andstandard deviation.

A custom property state reference can subscribe to statistics from analog data and saved to the Historian. Three types of historical state values are possible;Analog(Integer), String, and Null.

Alarm ShelvingAlarm 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 activealarms 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 manuallyunshelve an alarm before the end of the specified period.

Alarm shelving has been incorporated into Alarm Border animation and the ArchestrA Alarm Client control.

Alarm Border animation

When an operator shelves an alarm, Alarm Border animation remains around the symbol in a defined shelved visual style without blinking. The Alarm Border indicatoricon shows the shelved alarm mode icon. In Alarm Border animation, suppressed and silenced alarm modes take precedence over an alarm in shelved mode.

ArchestrA Alarm Client Control

The ArchestrA Alarm Client control includes a set of enhancements to support alarm shelving. The configuration dialog box includes a set of runtime options to shelveand unshelve alarms. Also, a set of properties and methods have been added to shelve and unshelve alarms with scripts.

Trend Pen EnhancementsInTouch 2014 introduced the Trend Pen control, which incorporates animation that shows a succession of process values as a trend line consisting of current andhistorical data. InTouch 2014 R2 includes additional new enhancements to the Trend Pen control.

Runtime Scripting

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 followingproperties can be modified in a script or User Input animation to change the following characteristics of a Trend Pen during run time:

MinValue

MaxValue

StartTime

EndTime

PlotType

TimeMode

Step Line and Line Trend Plots

The Trend Pen control now includes the Plot Type configuration option to show a trend line as either a Step Line or a Line plot. In Step Line mode, the trend line isplotted as a horizontal line from a trend data point to the time of the next data point on the trend's Xaxis. Then, the trend line is drawn as a vertical line to the datapoint. In Line mode, the trend line is plotted directly to each successive data point within the trend period.

Trend time Periods

The Trend Pen control now includes the Time Period configuration option to set a trend period as either Moving or Fixed. In a Moving trend period, the start time of atrend 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 donot 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 atrend time period.

Enhancements to Programmatic Export and Import of ArchestrA SymbolsInTouch HMI 2014 introduced the ArchestrA GraphicAccess application programming interface (API) to programmatically export and import an ArchestrA symbolbetween the ArchestrA Graphic Toolbox and an XML file. InTouch HMI 2014 R2 enhances the capability of the ArchestrA GraphicAccess API to export and import symbolsto include:

Overridden text strings

Numeric format styles

DataStatus elements

Graphic connectors

Trend Pen control

Alarm Client control

Trend Client control

Advanced Numeric Format StylesThe Configure Galaxy Style Library dialog box includes the Format Styles tab with options to individually configure Galaxywide number format styles for commontypes of numbers used in industrial applications. The Format Styles dialog box also includes fields to specify characters that appear during run time that indicate badquality data or data that exceeds a fixed width field. Based on the selected number style, the fields appear on the Format Styles dialog box to change the defaultproperties of number styles.



Each global number style is assigned a unique name, which cannot be changed. A number style can be applied by name in design time and run time for an analog datatype in User Input and Value Display animations. Also, grouped elements support global number styles.

Remote Application Licensing SupportYou can assign read only access to a distributed InTouch application running in a Remote Desktop Connection or Terminal Services session. Read only access isappropriate for nonoperators who need to view an application, but who should not have write permission. For example, managers need the capability to view anapplication on a mobile device with InTouch Access Anywhere.

You set user access (read/write, read ownly) to remote applications with the Remote Access Properties dialog box, which is accessible as an option fromWindowMaker's Special>Configure>Remote Access menu. By default, Remote Access Properties is set to Read/Write.

To support RDS hosted InTouch application licensing, InTouch 2014 R2 includes the INTOUCH_TSE_READWRITE license feature line to support remote read/writeapplications and the INTOUCH_TSE_READONLY license feature line to support remote read only InTouch applications. License consumption is restricted to the type ofapplication specified by WindowMaker's Remote Access Properties. If the number of remote users exceeds the INTOUCH_TSE_READONLY license feature linemaximum, no additional users can log on to a designated read only application even if there are available slots with a INTOUCH_TSE_READWRITE license feature line.

For InTouch 2014 R2, both licenses can be combined and installed on a single server node. A combined license file contains the following feature lines:

INTOUCH

INTOUCH_TSE_READONLY

INTOUCH_TSE_READWRITE

If you change the Remote Access Properties setting while running an InTouch application, you must restart WindowViewer for the change to become effective.

< top of document >

System Requirements

ContentsIntroduction

Hardware Requirements

Operating System, .NET Framework, and Virtualization Requirements

SQL Server Requirements

InTouch Access Anywhere Requirements

IntroductionThis section describes the hardware and software requirements to support Wonderware System Platform 2014 R2 products, including InTouch HMI 2014 R2.

Hardware Requirements

Contents

Hardware Guidelines

Auxiliary Hardware

Using Multiple Network Interface Cards

Hardware GuidelinesThe following table provides guidelines for hardware configurations suitable for Wonderware System Platform 2014 R2 software based on the size of the installation, applicable to both32bit and 64bit systems. The Intel Itanium 2 processor is not supported.

CPU (GHz)

Cores (Minimum)

RAM (GB)

Storage (GB)

(sufficientfor 1 wk @max

frequency)Monitor Resolution

Network (MBPS)

Compact 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 perNode)

2.8 8 16 1000 1280x1024 1000

Preferred Environment

(64bit OS and SQL) 2.8 4 8 500 1280x1024 1000

Hardware Requirements Notes:Windows operating systems and SQL Server versions may impose hardware requirements that exceed the minimum requirements for InTouch HMI 2014 R2. Refer to the followingMicrosoft Web pages for Windows and SQL Server hardware requirements:

System Requirements and Installation Information for Windows Server 2012 R2

Windows Server 2008 System Requirements

http://technet.microsoft.com/en-us/library/dn303418.aspx

http://www.microsoft.com/windowsserver2008/en/us/system-requirements.aspx



Windows 8 and 8.1 System Requirements

Windows 7 System Requirements

Hardware and Software Requirements for Installing SQL Server 2014


Hardware and Software Requirements for Installing SQL Server 2008 R2


Auxiliary Hardware RequirementsThis section describes any optional hardware requirements beyond the specific hardware requirements discussed earlier in this ReadMe.

Alternative Authentication Using Smart Cards

Smart Card: Raak Technologies C240 Mini Driver Smart Card

Smart Card Reader: OK 3021 USB Smart Card Readers

Operating System, .NET Framework, and Virtualization RequirementsSummary of Software Requirements

Software Requirement Notes

Notes Common to All Components

Wonderware InTouch HMI

.NET Framework

Virtualization

SQL Server

InTouch Access Anywhere

Summary of Software Requirements for InTouch HMI Version 2014 R2The following table lists the operating system, .NET Framework, and virtualization requirements for the suite of Wonderware System Platform products, including InTouch HMI 2014R2.

Note:Only the software versions and service packs shown in the following tables are supported for Wonderware System Platform 2014 R2 components.

Client Windows OS

Server Windows OS

.NETFramework Virtualization Host

7 SP1 Embedded (32bit only)

7 SP1 Professional, Enterprise, Ultimate

(32/64bit)

8Professional, Enterprise (32/64bit)

8.1Professional, Enterprise (32/64bit)

2008 R2 SP1 Standard, Enterprise (64bit)

Server 2012Standard and Data Center (64bit)

Server 2012 R2Standard and Data Center (64bit)

3.5SP1 4.0 4.5 4.5.1

IE10

IE11

HyperV (Based onSupportedOS version)

VMWare 5.0 (Basic

virtualizationNo HA/DR)

Application Server 2014R2 (4.1) N Y Y Y Y Y Y C N Y Y Y

InTouch 2014 R2 (11.1) S Y Y Y Y Y Y C N Y Y Y

Historian 2014 R2 (11.6) N Y Y Y Y Y Y C N Y Y Y

Historian Client 2014 R2(10.6) N Y Y Y Y Y Y C N Y Y Y

Information Server 2014R2 Portal and Client (5.6) N Y Y Y Y Y Y C N Y Y Y Y Y

FS Gateway 3.0 Y Y Y Y Y Y Y Y Y

System

Compact Installation(1500 I/O per node) Y N N N N N N C N N Y Y Y

Small Installation (15,000 I/O per node) N Y Y Y Y Y Y C N N Y Y Y

Medium Installation(5k50k I/O per node) N Y Y Y Y Y Y C N N Y Y Y

Large Installation (50k400k I/O per node) N N N N Y Y Y C N N Y Y Y

Preferred Environment(64bit OS and SQLServer)

R R C N N Y Y Y

Supported by all Y

Supported by a subset of products S

Supported and Recommended R

Not Supported N

Coexist C

Not Applicable

Software Requirement Notes:

Windows Operating System Notes

The recommended operating systems are Windows 8.1 for client nodes and Windows Server 2012 R2 for server nodes.

Windows versions 8 and 8.1 support touch screen gestures. If the user swipes in from the right edge of a touch screen with a finger gesture, a set of Windows charmsappears, which includes Search, Share, Start, Devices, and Settings. Pointing a mouse cursor to the upperright corner of a screen also shows the Windows charms fornontouch screens.

Showing the set of charms is a standard feature of Windows version 8 and 8.1, which cannot be disabled by software for a touch screen. As a result, operators can access

http://msdn.microsoft.com/en-us/library/ms143506%28v=sql.110%29.aspx

http://msdn.microsoft.com/en-us/library/ms143506.aspx#EE32

http://windows.microsoft.com/en-us/windows-8/system-requirements

http://windows.microsoft.com/en-us/windows7/products/system-requirements





these Windows charms and possibly unlock a dedicated touch screen view node.

Newer operating system Service Packs (SPs) than those listed do not block the installation of Wonderware products. A warning message may appear during the installationprocess.

The Galaxy Repository (GR Node) can run on a client Windows operating system only in a singlenode configuration in which Wonderware System Platform products areinstalled on a single computer. For a multinode environment, the Galaxy Repository must be installed on a computer running a version of a Windows Server operatingsystem.

Development and application nodes are considered to be clients of the server GR node.

When the operating system is upgraded on a computer, existing Wonderware System Platform products must be uninstalled prior to the upgrade and then reinstalled afterthe 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 toWindows 2012 R2.

.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 .NETFramework requirements and compatibility, see .NET Framework Requirements and Compatibility .

.NET 3.5 is installed only because the supported SQL Server versions require it. No other dependencies must exist.

Operating System Notes Common to 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 tohost or will have unpredictable behaviors in InTouch 11.1 either in WindowMaker or WindowViewer running on Windows 7, Windows 2008 R2, and later operating systems. For moreinformation, refer to Tech Note 922: "Some ActiveX Controls NOT Supported in InTouch 2012 R2 (Version 10.6)" available from the Wonderware Technical Support web site.

Configuring Remote Alarm Retrieval Queries When Running Windows 7, Windows 8, or Windows Server 2008 R2

The process to configure remote alarm retrieval queries has changed for interactive applications such as InTouch HMI when running on Windows 7, Windows 8, and Windows Server2008 R2.

When InTouch WindowViewer is started and generates alarms from an interactive Windows desktop session, an AlarmViewer control (running within InTouch HMI) on a remotenode 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 8, or Windows Server 2008 R2 node, open the SMC Logger and look for the mostrecent string generated by AlarmMgr. For example: "Registering AlarmMgr with SLSSVC as AlarmMgr 253.127.148.120". The indicated IP address will be unique to youralarmproviding node. Note the IP address for 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 providingInTouch 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.

3. Test to validate that the alarms generated from the alarmproviding 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 andLater 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 torun 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 andWindowViewer 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 differentfrom 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 AlarmSystem 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 inTechNote 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 Windows versions no longer support the /console switch as a means of starting the remote desktop (RDP) client, also known as Session 0 orTerminal Server Console session. In Windows Server 2008 or later, Session 0 is no longer an interactive session, and is reserved only for Windows services. From Windows Server2008 and later, all remote connections are treated 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.

In another aspect of Terminal Services behavior, InTouch HMI functions such as TSEGetClientID() can return a null value when running on Windows 2008 SP2 and Windows 2008 R2operating systems with InTouch running in a remote desktop (RDP) client session. The cause of this behavior is that the relevant roles are not installed on the Terminal Server. Youmust install the "Terminal Server" role for Windows 2008 SP2 or the "Remote Desktop Host" role for Windows 2008 R2 in order for TSEGetClientId() and other related functions towork properly.

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 carryforward the restriction introduced with the Windows Vista operating system which permits only one alarm provider. While both Wonderware Application Server and InTouch HMI canbe configured as alarm providers, only one alarm provider can be configured at any one time.

Wonderware Application Server and InTouch HMI detect when the application is running in the console. In Windows Server 2008 R2 and later, it implies that the application wasstarted by a user physically at the machine. However, this behavior requires that you disable Fast User Switching in both Windows 7 and Windows Server 2008 operating systems.

When running Windows Server 2008 R2 or later versions of Windows, you must modify the terminal services behavior for the Wonderware software to operate properly.

Wonderware software detects when an application is running in the console. From Windows Server 2008 R2 and later versions of Windows, all remote connections are treated as aremote RDP session regardless of /console or /admin switches in the mstsc connection.

To disable fast user switching through the Group Policy interface

http://wdn.wonderware.com/Downloads



1. Click Start and then Run. The Run dialog box appears.

2. Enter gpedit.msc and click OK. The Group Policy dialog box appears.

3. Go to the following location: Local Computer Policy > Administrative Templates > System > Logon.

4. Set Hide Entry Points for Fast User Switching to Enabled. Enabling this policy hides the Switch User option in the Logon interface, the Start menu, and the TaskManager.

5. On the File menu, click Exit to close the Group Policy dialog box.

By enabling the policy, Administrators hide the Switch User button in Windows logon, in the Start menu, and in the Task Manager.

Certain editions of Windows Vista do not have the Group Policy editor. So, alternatively, you can configure the Switch User settings through the registry.

To disable fast user switching through the Registry Editor

1. Click Start and then Run. The Run dialog box appears.

2. Enter regedit.exe and click OK. The Registry Editor dialog box appears.

3. Go to the following location: HKEY_LOCAL_MACHINE > SOFTWARE > Policies > Microsoft > Windows > CurrentVersion > Policies > System.

4. Rightclick and select DWORD (32bit) Value. Name it HideFastUserSwitching.

5. Set the HideFastUserSwitching data value to 1.

6. On the File menu, click Exit to close the Registry Editor.

In a Terminal Server environment that has a managed application deployed to it, the following behavior applies to references in the InTouch HMI application to the InTouchViewAppobject:

ArchestrA Symbols referencing InTouchViewApp_001.Tag1:

Running on the Console Refers to the tag value of the application running on the console.

Running in a Session Refers to the tag value of the application running on the console.

Restarting the Window Viewer application running on the console causes references from the terminal session to disconnect and then reconnect.

InTouch Graphic referencing Tag1:


Running in a Session Refers to the tag value of the application running in the session.

ArchestrA Graphic referencing InTouch:Tag1:


Running in a Session Refers to the tag value of the application running in the session.

InTouch Graphic referencing Galaxy:InTouchViewApp_001.Tag1:


Running in a Session Refers to the tag value of the application running on the console.

Wonderware InTouch HMI 2014 R2 (v11.1) Operating System NotesThe following table lists the supported operating systems that can be installed on computers that run InTouch HMI server and client components.

Operating Systems

Wonderware InTouch HMI Components

WindowMaker WindowViewerArchestrAIDE

ArchestrARun Time

GalaxyRepository

Windows 7 SP1 Embedded,32bit only Y Y N N N

Windows 7 SP1 Professional, Enterprise, orUltimate, 32bit or 64bit

Y Y Y Y N

Windows 8 Professional or Enterprise 32bit or 64bit

Y Y Y Y N

Windows 8.1Professional or Enterprise 32bit or 64bit

R R Y Y N

Windows Server 2008 R2 SP1 Standard or Enterprise, 64bitonly

Y Y Y Y Y

Windows Server 2012Standard or Enterprise, 64bit Y Y Y Y Y

Windows Server 2012 R2Standard or Enterprise, 64bit Y Y R R R

Supported Y


Not Supported N

Notes:

Microsoft Windows Server 2012 R2 is the recommended operating system for a Galaxy Repository.

Microsoft Windows Server 2012 R2 is the recommended operating system to run ArchestrA components.

Microsoft Windows 8.1 (32bit or 64bit) is the recommended operating system to run InTouch HMI runtime client components.

Microsoft Windows 7 SP1 Embedded is supported on compact systems only.

Wonderware InTouch HMI 2014 R2 (v11.1) with Windows 7 and Later Versions of Windows

Windows 7 and later operating systems do not support a dedicated singlenode server configuration that runs one or more databases for an InTouch HMI system.

The EnableDisableKeys() function writes to the Windows registry to enable or disable some keys on the host computer running an application in WindowViewer. For security



purposes, Windows 7 and later versions of Windows prevent Standard or Power users from writing to the registry. Windows Administrators can write to the registry if notdisabled by local domain security policies.

You can configure local Windows security policies that work in conjunction with the EnableDisablekeys() script function to regulate the user's access to keys in a runningInTouch application.

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 alarmprovider. For more information, see Using Alarm Manager on a Single Node Running Both Wonderware InTouch HMI and Application Server Alarm Providers on WindowsVista and Later Operating Systems.

The following InTouch legacy script functions do not operate on 64bit versions of Windows: 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 7 or later operatingsystems.

The InTouch Extensibility Toolkit might need to be started by rightclicking and selecting Run As Administrator on Windows 7 or later operating systems to functionproperly.

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 Professional and later operating systems.

Wonderware InTouch HMI 2014 R2 (v11.1) 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 anInTouchView application. When WindowViewer detects an InTouchView application, it does not register to become a DDE server. ArchestrA Symbols make use of the client layer whenaccessing InTouch tags, and appear as a thirdparty client trying to access WindowViewer as a data server. As a result, ArchestrA Symbols cannot communicate with InTouch tagswhen 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 R2 (v11.1) Support for Windows User Account Control

Wonderware System Platform 2014 R2 with InTouch HMI v11.1 supports User Account Controlenabled operations on runtime nodes.

.NET Framework Requirements and CompatibilityIMPORTANT: We strongly recommend that prior to upgrading your existing applications to Wonderware System Platform 2014 R2, that you back up your applications, becomefamiliar with the changes introduced by Microsoft in .NET 4.5.1, and review your .NET scripts and .NET controls for any required changes. After upgrading to Wonderware SystemPlatform 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 .NET4.5.1. We also recommend you test the upgrade in a staging system prior to upgrading your production system.

Â Wonderware System Platform 2014 R2 utilizes Microsoft .NET Framework 4.5.1. The Wonderware System Platform installation program will install .NET 4.5.1 if it is not alreadypresent 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 SystemPlatform. In this scenario, Wonderware System Platform 2014 R2 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 usersupplied .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 highlycompatible 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 2012 and earlier versions of ApplicationServer, InTouch HMI, the Historian, Historian Client, and Wonderware Information Server. These changes may also affect .NET controls developed with .NET 4.0.

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 decoder ofBinaryStream in .NET 4.5. To enable an ArchestrA script to decode ASCII XML data, for example, insert the following snippet:

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

To learn more about changes introduced in .NET Framework 4.5.1, refer to the following Microsoft resources:

What's New in the .NET Framework 4.5.1: http://msdn.microsoft.com/enus/library/ms171868%28v=vs.110%29.aspx

What's obsolete in the .NET Framework class library: http://msdn.microsoft.com/enus/library/ee461502%28v=vs.110%29.aspx

Migration Guide to the .NET Framework 4.5: http://msdn.microsoft.com/enus/library/ff657133(v=vs.110)

.NET Framework 4 Migration Issues: http://msdn.microsoft.com/enus/library/ee941656%28v=vs.100%29

Virtualization Host SupportWonderware System Platform 2014 R2 supports the following virtualization environments:

Microsoft HyperV: based on the version of Windows

VMware 5.0: basic virtualization without High Availability and Disaster Recovery

VMware vSphere 5

SQL Server Requirements

Contents

SQL Server Requirements for All Wonderware Components

Considerations for SQL Server

Considerations for SQL Server Express

SQL Server Requirements for All Wonderware ComponentsThe following table lists SQL Server requirements for Wonderware System Platform 2014 components, including InTouch HMI 2014 R2.

2008SP3

ExpressSSMSE(32bit)

2008 R2ExpressSSMSE(32bit)

2008 R2SP1

ExpressSSMSE(32bit)

2008 R2SP2

ExpressSSMSE(32bit)

2008 SP3Standard,Enterprise(32bitOnly)

2008 R2Standard,Enterprise(32/64bit)

2008 R2SP1

Standard,Enterprise(32/64bit)

2008 R2SP2

Standard,Enterprise(32/64bit)

2012ExpressSSMSE(32bitonly)

2012SP1

ExpressSSMSE(32/64bit)

2012SP2

ExpressSSMSE(32/64bit)

2012Standard,Enterprise(32/64bit)

2012 SP1Standard,Enterprise(32/64bit)

2012 SP2Standard,Enterprise(32/64bit)

2014ExpressSSMSE(32bitonly)

2014Standard,Enterprise(32/64bit)

http://msdn.microsoft.com/en-us/library/ee941656%28v=vs.100%29

http://msdn.microsoft.com/en-us/library/ee461502(v=vs.100).aspx

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

http://msdn.microsoft.com/en-us/library/ff657133(v=vs.110)



ApplicationServer 2014R2

S S S S Y Y Y Y S S S Y Y Y S Y

InTouch2014 R2 S S S S Y Y Y Y S S S Y Y Y S Y

Historian2014 R2 S S S S Y Y Y Y S S S Y Y Y S Y

HistorianClient 2014

InformationServerPortal 2014R2

S S S S Y Y Y Y S S S Y Y Y S Y

System Size:

CompactInstallation(1500 I/Oper node)

N N Y Y Y Y Y Y Y Y Y Y Y Y Y Y

SmallInstallation(15,000I/O pernode)


MediumInstallation(5k50k I/Oper node)


LargeInstallation(50k400kI/O pernode)

N N N N N Y Y Y N N N Y Y Y N Y

PreferredEnvironment(64bit OSand SQL)

R

Supported Y

For small systems only S


Not Supported N

Not Applicable

Considerations for SQL Server

Alarm DB Logger To use the Alarm DB Logger, you must set the default SQL Server authentication mode from Windowsbased to Mixed Mode.

SQL Server Configuration Rights: While installing Wonderware System Platform, configuration changes to SQL Server are required. If the installer does not have SQLServer administrative rights, the proper configuration of SQL Server may not be applied. A postinstall aaConfig SQL utility allows you to verify if the SQL configuration hasbeen performed.

Maximum Server Memory: After installing SQL Server, Use SQL Server Management Studio to confirm that the Maximum Server Memory is configured to approximately65% 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 hasthe 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 SQLServer 2008 to a node with SQL Server 2005. SQL Server database backups from SQL Server 2005 forward are not backwardcompatible. Attempting such a restoreinitializes, and the progress dialog box quickly displays 100% completion of restoring the database, but the Galaxy .cab restore operation does not actually complete, and noGalaxy Repository is created. When you start the IDE, the Galaxy is blank.

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 Server2012 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 Server2000 to SQL Server 2012. Such a migration requires an intermediate version installation. For more information and helpful procedures, see the following Microsoftreferences:

Upgrade to SQL Server 2014

Migrate SQL Server 2000 to SQL Server 2012

Migrating to SQL Server 2008 R2

Migrating to SQL Server 2008

TSQL scripts to migrate SQL server 2000 user databases to SQL server 2012

ALTER DATABASE Compatibility Level (TransactSQL) SQL Server 2012

ALTER DATABASE Compatibility Level (TransactSQL) SQL Server 2008 R2

SQL Server Rights Requirements: SQL Server 2008 and later versions do not automatically create the BUILTIN\Administrators role delivered in SQL Server 2005.Because of this change to SQL Server, the Wonderware Application Server 2014 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 Repositorywithout the need for blanket BUILTIN\Administrator rights. The aaAdministrators group must be present and enabled. If you accidentally delete the aaAdministrators groupfrom 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 WonderwareApplication Server User's Guide, About ArchestrA User Accounts, for further information and procedures to restore the aaAdministrators group.

Considerations for SQL Server Express

SQL Server Express is supported for use on a Galaxy Repository node and recommended for use only with small systems.

If you plan to modify an InTouch HMI installation which has SQL Server Express installed, then add Wonderware Application Server with full SQL Server, you must installthe full SQL Server prior to modifying the InTouch HMI installation or installing Wonderware Application Server.

http://msdn.microsoft.com/en-us/library/bb677622.aspx

http://blogs.msdn.com/b/ai/archive/2012/08/09/migrating-sql-server-2000-user-databases-to-sql-server-2012.aspx

http://blogs.technet.com/b/mdegre/archive/2012/06/15/migration-sql-server-2000-to-sql-server-2012.aspx

http://msdn.microsoft.com/en-us/library/bb677619%28v=sql.105%29.aspx

http://msdn.microsoft.com/en-us/library/bb677619%28v=sql.100%29.aspx

http://msdn.microsoft.com/en-us/library/bb510680(v=sql.105).aspx

http://msdn.microsoft.com/en-us/library/bb510680.aspx



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 limitationsapply:

Install Wonderware Information Server first with the SQL Server Express default instance name set to "SQLEXPRESS". Then, install Wonderware InTouch HMI.This scenario will work without issues because each component uses a dedicated instance of SQL Server Express.

If you install InTouch HMI 2014 R2 first, the Wonderware System Platform installer silently installs and configures SQL Server 2012 SP1 Express. InstallingWonderware Information Server will fail during configuration with an error message 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 nonExpress edition) on a remote node.

The computing capacity of SQL Server 2012 SP1 Express is limited to the lesser of one CPU socket or four processor cores.

For InTouch HMIonly installations, the Wonderware System Platform installer automatically installs SQL Server 2012 SP1 Express if these conditions are met:No version of SQL Server is installed on the computer at the time of installation.

You select only the InTouch Development and Runtime Wonderware System Platform installation option. When you select InTouch Development andRuntime, a Galaxy Repository will be installed.

InTouch Access Anywhere RequirementsThe following sections describe the requirements to run Wonderware InTouch Access Anywhere Server and supported browsers. For detailed information, see the WonderwareInTouch Access Anywhere documentation.

Important Note: The InTouch Access Anywhere Server has been updated to resolve a security vulnerability to a buffer overflow. You must uninstall InTouch AccessAnywhere 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.

RequirementsThe InTouch Access Anywhere Server can be installed as a Wonderware System Platform installation option. The InTouch Access Anywhere Secure Gateway is an optional componentinstalled on a separate computer within a network DMZ.

The following requirements must be met before you install the InTouch Access Anywhere Server or a Secure Gateway.

Wonderware InTouch Access Anywhere must be installed on the same RDP Server computer as Wonderware InTouch HMI 2012 R2 (version 10.6) or later.

Remote Desktop (RDP) must be enabled and properly configured on the host computer. For information and guidance, see Tech Note 782, "Installing Remote DesktopServices on Windows 2008 Server R2 for Wonderware Products". You also can refer to http://technet.microsoft.com/enus/library/dd883253.aspx.

You must install an InTouch 2012 R2 TSE Concurrent License on the same computer as your Wonderware InTouch and InTouch Access Anywhere Server installations.

Supported InTouch Access Anywhere BrowsersWonderware InTouch Access Anywhere can run on smart phones, tablets, laptop computers, or any other device that supports an HTML5compliant web browser. Browsers validatedto support Wonderware InTouch Access Anywhere include the following:

Browsers Tested with InTouch WindowViewer

Internet Explorer version 11

Internet Explorer version 10

Firefox version 22

Safari version 7

Chrome version 28

Opera version 15

Functionally Compatible Browsers

Certain versions of the following browsers may be functionally compatible with InTouch Access Anywhere, but have not been formally tested to run InTouch HMI applications.

Firefox versions 421

Safari versions 5, 6

Chrome versions 1127

Opera versions 1114

You are strongly encouraged to upgrade to one of the supported browser versions listed in Browsers Tested with WindowViewer. For a complete list of considerations to run anInTouch application with InTouch Access Anywhere on a portable device, see the InTouch Access Anywhere User Guide.

< top of document >

Wonderware InTouch HMI 2014 R2 (v11.1) Product CompatibilityProduct Compatibility refers to the ability of a product to work with various versions of other products running on different network nodes. Product Compatibility also refers to theability of a product to work with various versions of the same product running on different nodes.

Coexistence refers to samenode installation of a product with other Wonderware and Invensys products that support the same hardware, operating system, and SQL Server versions.Other products not listed will be covered by System Compatibility Testing unless specifically noted.

In a singlenode environment, if you want to install multiple components on a single computer, all components must be at the versions delivered in Wonderware System Platform2014 R2.

In a nodetonode environment, components are compatible between the current licensed version and one licensed version back.

The following table lists Wonderware and Schneider Electric products and their compatibility and coexistence with InTouch HMI 2014 R2 (v11.1).

Product Version Compatibility Coexistence

Wonderware System Platform

4.5 N

2012 Y

2012 R2 Y

2012 R2 P01 Y

2012 R2 P02 Y

https://wdnresource.wonderware.com/support/kbcd/html/1/t002563.htm

http://technet.microsoft.com/en-us/library/dd883253.aspx



2012 R2 P03 Y

2014 Y

2014 P01 Y

Wonderware InTouch CE 10.1 N N

Wonderware Manufacturing Execution System

4.0 SP1 N N

4.0 SP2 N N

MES 2012 P01 4.5 P01 Y Y

MES 2014 5.0 Y Y

Wonderware InControl™ 7.11 SP2 P01 N N

Wonderware Manufacturing Execution Module 1 Y N

Wonderware InBatch™

(*) If you are using Wonderware Information Server with InBatch software, upgrading to Wonderware InformationServer 5.6 requires an InBatch hotfix to maintain compatibility.

10.0 (2012 R2) N N

10.1 (2014) Y (*) Y (*)

Wonderware QI Analyst™

8.0 SP1 P01 N N

8.0 SP2 Y Y

8.0 SP3 Y Y

Wonderware SCADAlarm™ 6.0 SP2 P01 N N

Wonderware Intelligence1.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) N N

Wonderware Skelta BPM 2014 N N

Wonderware PEM 2.1 SP1 Y Y

Wonderware Online (see components below) 1.0

Historian Client Trend 10.6 Y Y

InTouch 11.0 and 11.1 Y Y

MRC (Mobile Report Connector) Y Y

Recipe Manager Plus1.0 (2014) Y Y

1.5 (2014 R2) Y Y

Schneider Electric CitectVJC

7.2 SP3 Y Y

7.3 Latest SP N Y

7.4 SP1 Y Y

Schneider Electric ClearSCADA

CS 2013 R1 N Y

CS 2013 R2 N Y

CS 2014 R1 N Y

CS 2015 R1 Y Y

Supported YNot Supported NNot Applicable

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

< top of document >

Wonderware InTouch HMI InstallationFor detailed English installation instructions, see the Wonderware System Platform Installation Guide (ASP_Install_Guide.pdf) or Wonderware System Platform Installation Help(ASP_Install_Guide.chm). Condensed English installation instructions are also provided in the printed Wonderware InTouch HMI Getting Started Guide booklet that is included in theinstallation package. This booklet is provided for all supported languages.

The information provided in this Readme file supersedes the InTouch Installation Help (InstallInTouch.chm) for the French, German, Japanese, and Simplified Chinese languages.

ContentsInstalling the Wonderware InTouch HMI

Installing the Wonderware Product License

Antivirus Software Exclusions

Modifying, Repairing, or Removing InTouch HMI

Upgrading to InTouch HMI 2014 R2

Migrating InTouch HMI Applications

Installing the Wonderware InTouch HMIThe major decision you must make when you install InTouch HMI is whether to install the InTouch development and runtime components, or the runtime components alone. The



installation program guides you in selecting the features you want, verifying or modifying your selections, installing prerequisite software, and then installing InTouch HMI and theArchestrA IDE if you chose to install development components.

What You Need to Install InTouch HMIYou must have the following materials ready to install InTouch HMI:

Installation DVD.

Computer that meets the hardware and software requirements listed in this Readme.

Important: Use the hardware and software requirements listed in the Wonderware Application Server Readme if you are going to install the ArchestrA IDE.

PrerequisitesThe installation program analyzes the software installed on your computer and lists any required software that is not installed.

Note: At the start of the installation, the prerequisites check is systemspecific rather than productspecific.

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

Windows Installer 4.5

Microsoft .NET Framework 4.5.1

SQL Server 2012 Express SP1

SQL Server 2012 Express SP1 will be installed automatically if one of the following conditions are met:No version of SQL Server is installed on the host computer.

You select only InTouch Development and Runtime during the Wonderware System Platform installation. You must not select any Application Servercomponents. When you select InTouch Development and Runtime, a Galaxy Repository will be installed for you.

The installation program installs both systemspecific and productspecific prerequisites. You do not have to exit from the installation program to install the prerequisite software. Formore information about Wonderware System Platform installation prerequisites, see the Wonderware System Platform Installation Guide.

About the ArchestrA User AccountThe ArchestrA user account is a user name and password combination that enables internode communication between all computers in an ArchestrA environment. You must specifythe 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 systemaccount management tools. If you do, ArchestrAenabled software may stop functioning properly.

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

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

User account with a permanent password that does not expire.

User account in which the password cannot be changed.

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

After you install the InTouch HMI, you can use the ArchestrA Change Network Account utility to change or recreate the ArchestrA user account. This utility is accessible from theStart menu in the Wonderware Common folder after you install InTouch. You must have Administrator privileges on the computer to make changes with the Change NetworkAccount utility. For more information, see the Change Network Account utility help.

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

Performing the InTouch HMI InstallationBefore you start installing InTouch HMI, you should have a clear idea whether you want to develop, deploy, and publish your own applications, or require only the InTouch run time,to run applications already created and deployed.

The following procedure will guide you through the installation, with information specific to the InTouch HMI.

To install the InTouch HMI

1. Insert the installation DVD into the computer's DVD drive.

2. Using Windows Explorer, manually start the installation by doubleclicking setup.exe on the DVD.

3. Follow the prompts to start the installation and install system prerequisites, as necessary.

4. The installation program prompts you to select an installation type: either productbased selection or installation by computer roles. As you are only installing InTouch HMI,click the productbased selection as your installation type.

5. Choose the components you want to install.

a. If you choose InTouch Run Time Only, the following will be installed:

InTouch Run Time

InTouch documentation

Alarm DB Logger

FS Gateway (as a silent installation)

Application Server Bootstrap

InTouch Supplemental Components: InTouch Recipe Manager, InTouch SQL Access, and Symbol Factory

Note: The 16 Pen Trend supplementary component is not installed by default. You must select the Customize Installation option and select 16 PenTrend from the product list to install it as part of the InTouch HMI installation procedure.

Invensys License Manager

b. If you choose InTouch Development and Run Time, the following will be installed:

All items listed under step a in these instructions.



InTouch Development

Application Server Bootstrap, IDE, Galaxy Repository, SQL Server 2012 Express SP1 with SSMSE, and Application Server documentation

InTouch sample applications

6. When the installation prompts you to verify your selection, select Customize Installation if you want to add or remove components of your InTouch installation.

7. After you verify and customize your selection, you are prompted to select the language you want to install. English is selected by default, but you can choose anotherlanguage.

8. Follow the subsequent installation steps to:

a. Accept the End User License Agreement.

b. Create a new ArchestrA user account, or specify an existing account.

c. Install any prerequisite software components not yet installed on the computer.

d. The installation proceeds to completion. You must restart the computer after completing the installation.

Installing Your Invensys Product LicenseWonderware enforces the use of its products with a software license. After you install a product, you must install a single license file, ARCHESTRA.LIC, which contains your customerinformation, product data, and software features. Until you apply your Invensys product license, you can only run the InTouch HMI in demonstration mode.

You use the Invensys License Manager to install the contents of the ARCHESTRA.LIC file on the computer where InTouch HMI has been installed. The Invensys License Manager isincluded as an Invensys component when you install the InTouch HMI.

To install your Wonderware product license

Start the Invensys License Manager by doing the following:

1. Place the installation DVD in the computer's DVD drive.

2. Click Start from the Windows desktop, and then click All Programs to show the Invensys folder.

3. Click the Invensys folder, and then click the Invensys License Manager folder.

4. Click Invensys License Manager.

5. Click File, and then Install License File. The Choose a License File to Install dialog box appears.

6. Browse the installation DVD, select the ARCHESTRA.LIC file, and click Open.

The Destination Computer for Installation dialog box appears.

7. Type the domain and computer names.

The Invensys License Manager copies the ARCHESTRA.LIC file to the C:\Program Files\Common Files\ArchestrA\License folder on the selected computer.

Antivirus Software ExclusionsAfter installing Wonderware InTouch HMI Version 11.1, configure your antivirus software to avoid scanning archive files.

Notes:

The folders listed in this section may be different based on your installation choices.

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 listedsubfolder in the specified folder path.

If you are using a 64bit operating system, folder names must be specified accordingly. For example, the program files root folder in a 64bit operating system is C:\ProgramFiles (x86)\... and the application data root folder in a 64bit operating system is C:\ProgramData\.

Add the following folders of 32bit operating systems to your antivirus scan exclusion list:

C:\ProgramData\ArchestrA\

C:\Program Files\ArchestrA\

C:\Program Files\Common Files\ArchestrA\

C:\Program Files\FactorySuite\ (The FactorySuite folder may not exist in newer installations)

C:\Program Files\Wonderware\

C:\InSQL\Data\

C:\Users\All Users\Applications

C:\Historian\Data

Add the following folders of 64bit operating systems to your antivirus scan exclusion list:

C:\ProgramData\ArchestrA\

C:\Program Files (x86)\ArchestrA\

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

C:\Program Files (x86)\FactorySuite\ (The FactorySuite directory may not exist in newer installations)

C:\Program Files (x86)\Wonderware\

C:\Users\Public\Wonderware\

C:\Historian\Data

Add the following folders to your antivirus scan exclusion list:

History Store Forward folder default location:C:\Documents and Settings\All Users\Application Data\ArchestrA\

C:\Users\All Users\ArchestrA\

Checkpoint folder location default location:

C:\Program Files\ArchestrA\Framework\bin (32bit Windows)

C:\Program Files (x86)\ArchestrA\Framework\bin (64bit Windows)

InTouch HMI application folders:



C:\Users\Public\Wonderware\IntouchApplications (default folder path)

You can select an application folder path when an InTouch HMI application is created.

ArchestrA System Management Console (SMC) Logger storage file path:

C:\ProgramData\ArchestrA\LogFiles (default folder path)

Add the following file types to your antivirus exclusion list:

SQL Server database files of type:

.mdf

.ldf

Exclude *.aFDX files from the C:\Windows\Temp folder

Modifying, Repairing, or Removing the InTouch HMITo modify, repair, or remove a product

1. Insert the installation DVD into the computer's DVD drive.

2. Access the Windows Control Panel and select the Programs and Features option.

The list of software installed on your computer appears.

3. Select the InTouch component, and then click the Uninstall/Change button. The Modify, Repair or Remove Installation dialog box appears.

4. Follow the prompts to modify, repair, or remove InTouch.

The name of the Uninstall/Change button varies depending on the version of Windows installed on your computer.

Note: Modern applications can no longer be created, edited, or run after Wonderware Application Server is uninstalled from the same computer that also hosts InTouch run time anddevelopment components. Modern applications no longer work because the Galaxy Repository required for Modern applications is removed when Wonderware Application Server isuninstalled.

Upgrading to Version 11.1 from an Earlier Version of the InTouch HMIUpgrading InTouch HMI installs Version 11.1 on a computer that has a previous version currently installed. An upgrade removes or uninstalls the previous version of InTouch HMI andinstalls Version 11.1.

After the hardware and software requirements are met, including the proper operating system, SQL server and other prerequisites, you can upgrade to Wonderware InTouch HMIVersion 11.1 from the following versions of the InTouch HMI:

Version 10.1 SP3

Version 10.1 SP3 P01

Version 10.2

Version 10.5

Version 10.6

Version 10.6 P01

Version 10.6 P02

Version 10.6 P03

Version 11.0

Version 11.0 P01

You can only upgrade Wonderware System Platform products that are already installed. You cannot install any new Wonderware System Platform products by an upgrade process.

To upgrade from a previous version of the InTouch HMI

1. Insert the DVD into your DVDROM drive. Run setup.exe to start the setup program. The upgrade feature dialog box appears.

2. Follow the prompts to complete the upgrade.

Upgrade Notes

Important Note: If you plan to upgrade Wonderware System Platform on a computer that has InTouch Access Anywhere Server installed, you must firstuninstall the InTouch Access Anywhere Server. Then, upgrade Wonderware System Platform and finally reinstall InTouch Access Anywhere Server.

Back up any custom configuration of the installed instance of InTouch Access Anywhere before you uninstall it.

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.

If Wonderware Application Server is installed on the same node as Wonderware InTouch HMI, both must be upgraded to ArchestrA 2014 R2 versions. You must upgradeWonderware 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 RepairUtility before installing Wonderware Application Server 4.1 to ensure that all issues reported by the utility are addressed.

Migrating Applications to Wonderware InTouch HMI Version 11.1Migration converts applications created with earlier versions of InTouch HMI to the current version. You can migrate applications to version 11.1 that were developed with thefollowing versions of InTouch HMI:

Product From UpgradeNodebyNodeUpgrade Migrate

7.0 N N/A N

7.1 N N/A N

7.11 P07 N N/A Y



Wonderware InTouch

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

10.2 Y N/A Y

10.5 Y N/A Y

10.6 Y N/A Y

10.6 P01 Y N/A Y

10.6 P02 Y N/A Y

10.6 P03 Y N/A Y

11.0 Y N/A Y

11.0 P01 Y N/A Y

SPCPro was a Statistical Process Control (SPC) utility available with InTouch HMI prior to Version 11.0. SPCPro is no longer supported by InTouch HMI 2014 R2 (Version 11.1). Werecommend that that you migrate your SPCPro databases to the latest version of QI Analyst if you still use SPCPro with InTouch. QI Analyst provides support for the latest versions ofoperating systems and databases.

QI Analyst also includes a utility to migrate your SPCPro database to a QI Analyst database, leaving the existing SPCPro database intact. Please contact your local Wonderware salesrepresentative for further information.

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

< top of document >

Resolved IssuesThis section describes important resolved issues. This list is not a comprehensive list of all resolved issues for this release. The issues are listed by their Change Request number. If anissue was previously resolved as a Wonderware Hot Fix, the issue also includes the assigned Service Request (SR) number.

L00112734: The InTouch Alarm Printer utility issued warning messages during initialization and became nonoperational. To resolve this issue, a new Alarm Printer service wasintroduced, which runs in a headless Windows environment without a keyboard, mouse, or monitor.

L00128825: The custom property of an embedded symbol did not appear in an embedded symbol in a specific, restricted user scenario, which includes the following steps:

1. Create a symbol (S1) and a custom property (cp1).

2. Embed symbol S1 into another symbol (S2) and override the S1.cp1 custom property with a new value. Make the S1.cp1 custom property Private.

3. Export symbol S2.

4. Rename the S1.cp1 custom property to newcp1.

5. Import symbol S2.

L00128835: Selecting Clear animation or Validate animation from the Point Animations dialog box did not clear a warning message after attempting to configure pointanimation for an unsupported type of graphic element. Selecting Clear animation or Validate animation did clear the warning message.

L00128851: A small horizontal spike appeared in the trend line of Trend Pen animation when the reference to the Historian was hard coded and a Set Custom Property Valuescript assigned the measured value to a custom property that referenced a UDA field attribute value.

L00128854: Maximizing the Point Animations window did not increase the size of the graphic element shown in the Preview pane and the point data entry fields. The graphicelement and data entry fields remained at their original size prior to maximizing the window.

L00128858: If point animation was applied to the first graphic element edited in a new Galaxy, the point shown on the Preview graphic disappeared for several seconds when thePoint 0.X field is selected. This issue only appeared on the first graphic element being edited in a new Galaxy.

L00128859: After selecting a point from the list of points in the Point Animations dialog box, repeatedly pressing the Tab key did not select the following point rows in descendingorder. Instead, pressing Tab first selected the point row's data entry field, then the row's Browse Galaxy button, and finally the following row in the list of points.

L00128881: InTouch Access Anywhere Secure Gateway could not be installed using the installation Modify method if other Windows System Platform products were installed onthe target server. Existing Wonder System Platform products could not be simultaneously uninstalled during an InTouch Access Anywhere Secure Gatewayinstallation on the same server.

L00128898: The online help for the InTouch Alarm DB Purge and Archive utility were not accessible if only the Historian was installed. Information about the Alarm DB Purge andArchive utility were accessible by viewing the InTouch WindowMaker help file located at the following folder location on the installation DVD:

Wonderware System Platform\InstallFiles\CDInTouch\UserDocs\English\WM.chm

L00128927: Custom properties of an embedded symbol set to references showed invalid values if chained scripts ran in sequence using a cached global variable. Typically, thecached value is pushed to the symbol's target custom property. If the write to the custom property is successful, the global variable is cached to the custom propertyreference. In the case of chained scripts, another script may push another custom property reference to cache as a global variable and overwrite the previous value.

To fix the issue, change the global variable to local variable to prevent it from being overridden by the custom property reference value of another chained script.

L00130122: SR 22210102: Updates to a NAD application on the master node did not propagate to the application running on a client viewer node when the NAD Change Modewas set to Prompt User to restart Window Viewer and the application was started by a Windows shortcut placed on the client visual node. After the userrestarted WindowViewer, the updates to the NAD application did not appear on the client visual node. Application updates did appear after the user restartedWindowViewer a second time.

L00130294: SR 44910788: The Alarm DB Logger query string was restricted to a maximum of 2048 characters. The length of an Alarm DB Logger query has been increased to3072 characters.

L00130586: SR 10417514: The Alarm DB Logger query string was restricted to a maximum of 2048 characters. The length of an Alarm DB Logger query has been increased to3072 characters.

L00130640: SR 41610654: The InTouch Windows to Import dialog box showed incorrect application window files dates when importing windows from one application toanother. The Last Modified column of the Windows to Import dialog box showed the file dates of the windows of the importing application, not the file dates ofthe windows being imported.

L00130698: SR 103130881: When the Alarm Client control was configured to query alarms from multiple backup pairs, the configured text and background colors of the AlarmClient were lost during run time. The colors reverted to black text on a white background for all types of alarms.



L00130924: SR 24412649: Attempting to open WindowViewer or Application Manager with an InTouch power user account failed when Windows User Access Control (UAC) wasactive. An error message indicated that opening WindowViewer or Application Manager required an InTouch user account with more privileges.

L00130991: SR 103129187, 42010090,103129638,103130123: Occasionally, InTouch became nonresponsive while Alarm Manager was processing alarms. The problemwas caused by the ArchestrA Alarm Control submitting multiple alarm queries to the Alarm Manager before all relative references in the queries were resolved.

L00131149: SR 43911084: Switching the language in WindowViewer from English to another language caused the Historical Trend client trend line to blink during each trendrefresh interval.

L00131297: SR 45510673: After applying InTouch HMI 2014 Patch 01, the Alarm Client control always showed a horizontal scroll bar during run time even though the selectedcontents of an alarm could fit within the width of an alarm Client window and the Show Heading and Show Status Bar options were inactive.

L00131307: SR 15317227: After applying InTouch HMI 2014 Patch 01, the behavior of ShowSymbol animation or the ShowGraphic script function was inconsistent afterenabling the Cache ArchestrA Graphics not embedded in InTouch Windows WindowViewer option. Storing the location of the popup window containing thesymbol in cache disables persistency. As a result, the popup window opens at the current location stored in cache rather than the intended position set by the valueof the ShowGraphic WindowLocation parameter.

L00131374: SR 10417554: At run time, graphics using color animation to represent machine state did not update consistently. Also, graphics containing Value Displayanimation did not show complete analog values. Users were forced to refresh the application window to update the symbol's color and Value Display animations.

L00131435: SR 42010084: The value of a tag did not get updated if there was an overlap with a Combo Box Windows control.

L00131474: SR 48910306: The ShowGraphic() function uses Microsoft Windows forms to display symbols. The ShowGraphic() function incorrectly increased the height of allsymbols less than 27 pixels because Microsoft Windows forms with captions are restricted to a minimum height of 27 pixels. Now, the ShowGraphic() functionrestricts a symbol to a minimum height of 27 pixels if the symbol has a caption and a minimum height of 10 pixels if there is no caption.

L00131488: SR 14812693: The access level value assigned to a user was incorrectly assigned the previous user's access level after a change password request.

L00131597: SR 44210638: An ArchestrA symbol containing embedded symbols with relative references did not display quickly when invoked by ShowSymbol animation if theGalaxy Repository and AOS nodes were inaccessible from the WindowViewer node. After some delay, a box with a red X would appear to indicate the symbol could notbe loaded.

L00131620: SR 33812558: An "Object not found in the galaxy, may already be deleted." error message appeared in WindowMaker when the user attempted to edit an instanceof an embedded ArchestrA symbol containing another ArchestrA symbol within a contained object instance.

L00131622: SR 41810084: WindowViewer stopped with an application error when closed with a WM_CLOSE message while a value entry dialog box was open.

L00131812: SR 103130141: WindowMaker closed or became nonoperational after committing changes to a SmartSymbol that was used in many windows.

L00131828: IASGrid was not getting refreshed with new values after the user selected the Block button. Closing and reopening the graphic hosting the grid resolved the problem.

L00132078: In version 10.6 of InTouch, open popup windows with embedded graphics did not close automatically after the main application window was closed in WindowViewer.

L00132079: SR 44710413: Closing a managed application from WindowMaker without saving any changes caused a derived InTouchViewApp template version number toincrement by 1 or 2.

L00132085: SR 42410286: After converting an InTouch application window and publishing it to Windows Information Server (WIS), symbol animation did not occur unless theuser clicked the window link twice in the WIS navigation panel. Symbol animation worked correctly when viewing the window with WindowViewer.

L00132372: SR 45110418: After migrating an InTouch standalone application from version 10.5 to version 10.6 Patch 01, some users were missing if there was a mismatchbetween the number of listed users and passwords in the Password.bin file.

L00132409: SR 51010070: Opening a graphic with an embedded Trend pen control with either the ShowGraphic function in a script or ShowSymbol animation was delayed upto 15 seconds based on the number of pens recording historical data.

L00132418: SR 103131983: The number .5 was added to the values of integer and analog numbers when a PDF file was loaded into an InTouch application. When the PDF filewas loaded the computer's locale changed to the system locale. The decimal symbol changed to a comma and the numeric value was not rounded.

L00132436: SR 103131980: Historical events could not be restored from the History database using the InTouch Alarm DB Restore utility when an event record contained morethan one operator.

L00132496: SR 15618685: New domain users could not log on with their Windows user credentials to an InTouch application secured with operating systembased security.

L00132604: SR 20114810: A delay of 20 seconds occurred when switching the owner of Owning Objects with ArchestrA Graphics in a managed InTouch application.

L00132633: SR 49810012: WindowMaker closed or became nonoperational after committing changes to a SmartSymbol with multiple instances of the SmartSymbol placed inmany application windows.

L00132733: SR 103132375: The ScaleAutoPen() function in an action script did not automatically scale a measured value within the range of a TrendClient control if the scriptwas invoked after trend's initial duration. Values could be scaled correctly only if the script was run within the trend's initial duration.

L00132778: SR 50810106: Users could write a value to an I/O tag with an InTouch Read Only license when the tag appeared on the application's home window or any otherwindow that used the same tag.

L00132924: SR 50110021: After migrating to InTouch HMI version 10.6, WindowMaker became nonresponsive when crossreferencing tags while running an applicationcontaining retentive tags.

Note: To fully implement the solution for this issue, edit the InTouch.ini file and set the ShareRetentiveTags setting to ShareRetentiveTags=1.

< top of document >

Known IssuesThis section describes known issues that remain in the release of InTouch HMI 2014 R2. The issues are listed by their Change Request number.

L00126240: When the name of an ArchestrA symbol starts with number and is embedded in another symbol, scripts that reference the symbol interpret the custom properties asattributes instead. Warning messages appear in the SMC log.

L00131838: An "Object not found in the galaxy, may already be deleted." error message appears in WindowMaker when the user attempts to edit an instance of an embeddedArchestrA symbol within an area instance assigned to another area instance (UDA01_001.UDA02.S2).

This issue can be circumvented. While selecting instances to embed in a window from Galaxy Browser, select Show Tagname instead of the Show HierarchicalName option. Or, after a symbol is embedded in a window(if symbol is selected with "Show Hierarchical Name" option), save and close the window and open thewindow again.

L00133207: While converting an InTouch window to an ArchestrA symbol, the location and size of some window graphic elements or text may change slightly in the finalconverted symbol.

L00133434: DBDump becomes nonoperational when attempting to start the utility from the command line to export tags from a Modern application to an output file. DBDumpcan be used to export tags from a Modern application by selecting the DBDump option from the InTouch Application Manager menu bar or the File menu.

DBLoad is unaffected and can be started from the command line or Application Manager.

L00133567: SR 51310192: An Element Style cannot be applied to a text string or text box in a second language configured for a Galaxy if the user changes the default font ortext size of the second language text string. The font and text size changes remain for the localized text strings even after the Element Style is applied. The ElementStyle is applied correctly to all text strings in the default Galaxy language.

L00134675: Using the programmatic API to import a symbol fails if the symbol contains an embedded Alarm Client control configured with the Client Mode option set toHistorical Alarms and Events and the Database Name option set to History Blocks.

Note: Importing symbols containing an embedded Alarm Client control with the Database Name option set to History Blocks is not supported in InTouch HMI2014 R2.



Print IssuePrintWindow() cannot print the following controls in ArchestrA Symbols: ListBox, DateTimePicker, CalenderControl, EditBox, CheckBox, RadioButtonGroup, ComboBox, AlarmClient orTrendClient.

OnShow Symbol Script IssueWhen the OnShow Symbol Script contains external references, the data may not be available at run time due to a timing issue. Application Server 3.1 SP2 enabled a configurableOnShow Symbol Script time out to allow external references to resolve. The symbol will be drawn disabled and all scripts will be delayed. Once the data is available, the symbol willbe enabled and the OnShow Symbol Script will execute first, followed by the rest of the scripts. If the external data does not become available within the configured time out, theOnShow script will still execute but will place a message in the Logger that not all references have been resolved. Because named scripts will be blocked until OnShow executes,some events may be missed. For example, the named script OnDataChange will not run during the time OnShow is delayed even if the data point is changing.

< top of document >

InTouch Documentation IssuesThe following table lists corrections to InTouch 2014 R2 (version 11.1) documentation.

Item Location of Change Existing Documentation Change

1 New information to be inserted into the InTouch HMIApplication Management and Extensions Guide(ITAppManagement.pdf), "Converting InTouchWindows to ArchestrA Symbols" section, page 120

WindowMaker Help (WM.chm), "Converting InTouchWindows to ArchestrA Symbols" topic.

None Add a new subsection titled "Known Limitations of Window Conversions" to the "Converting InTouchWindows to ArchestrA Symbols" section of the InTouch HMI Application Management and ExtensionsGuide.

Converting an InTouch window to an ArchestrA symbol does not always achieve complete fidelity. Insome cases, window components cannot be converted to a symbol. This section describes knownlimitations when converting an InTouch window to an ArchestrA symbol and any alternative solutions.

Converting a Window Containing a Vertical Mouse Release Slider SmartSymbol

A Vertical Mouse Release Slider SmartSymbol contains two types of animation. The symbol uses fillanimation to show the current measured value against a scale and a movable slider knob to set a value.A window containing an embedded Vertical Mouse Release Slider SmartSymbol does not retain themovable slider animation when converted to an ArchestrA symbol.




Converting a Window Containing a Symbol Factory Symbol

Not all types of animations incorporated in Symbol Factory symbols can be converted to an ArchestrAsymbol. The following types of Symbol Factory symbol animations cannot be converted:

Percent Fill

Line Color

Horizontal Movement

Vertical Movement




Migrating InTouch Translation Strings to ArchestrA Symbols

InTouch translation strings are stored in an XML file in the application's folder. The translated strings ofeach language are placed in separate XML files. Translations of all windows and SmartSymbols stringsare available from the XML file in the application directory after importing localized strings.

The following procedure explains how to use the Wonderware Language Assistant tool to migrateInTouch window localization strings to an ArchestrA symbol.

1. Convert an InTouch window to an ArchestrA symbol.

2. Import the contents of an InTouch language XML file to Language Assistant to create a globaldictionary of phrases.

3. Export an ArchestrA symbol to an XML file.

4. Import the symbol XML file to Language Assistant, which will automatically apply a globaldictionary translation to the ArchestrA Graphic phrases.

5. Publish the ArchestrA Symbol XML file from Language Assistant.

6. Import the XML file to the ArchestrA Graphic Toolbox containing the translated text strings.




Migrating InTouch Scripts to ArchestrA Symbols

Scripts containing InTouch or QuickScript functions cannot be converted to an ArchestrA symbol.




Migrating InTouch History Objects to ArchestrA Symbols

InTouch windows containing an InTouch Historical Trend are not completely converted to ArchestrAsymbols. Only some parts of the Historical Trend may appear in the converted symbol. Trendcomponents like scooter bars may not appear in the converted ArchestrA symbol.

6 New information to be inserted into the InTouch HMIScripting and Logic Guide, (ITScriptsAndLogic.pdf),"Configuring Window Scripts" section.

WindowMaker Help (WM.chm), "Configuring Window

Missing from Japanese,French, Chinese, andGerman versions of theInTouch HMI Scripting andLogic Guide

Add the following Important note immediately after step 3 in the To delete a window scriptin the "Configuring Window Scripts" section.

Important: Do not use OnHide scripts to read from or write to I/O tagnames. The I/O value updatedoes not necessarily complete before the window is hidden.



Scripts" topic.

Note:

This documentation issue applies only to the French,German, Japanese, and Chinese versions of theInTouch HMI Scripting and Logic Guide.

To read from or write to I/O tagnames when a window closes, configure a data change script andactivate it from an OnHide script.

7 Corrected information to be inserted into the InTouchHMI Scripting and Logic Guide, (ITScriptsAndLogic.pdf),"Comparing Strings" section.

WindowMaker Help (WM.chm), "Comparing Strings"topic.

Note:

This documentation issue applies only to the French,German, Japanese, and Chinese versions of theInTouch HMI Scripting and Logic Guide.

Japanese, French, Chinese,and German versions of theInTouch HMI Scripting andLogic Guide

Replace the information immediately after the StringCompare() Function title with the following:

Compares two strings and returns a Boolean result (0=strings are equal). The string comparison is casesensitive. "A" is not equal to "a".

Syntax

result = StringCompare (string1, string2)

Parameters

string1

A literal string, message tagname, or string expression.

string2

A literal string, message tagname, or string expression.

Example(s)

StringCompare ("Apple", "Apple") returns 0

StringCompare ("Apple", "apple") returns 1

The StringCompare() function compares two message tags and returns a Boolean result (0 or 1).

StringCompare (mtag1, mtag2)

8 New information to be inserted into the Creating andManaging ArchestrA Graphics User's Guide,(AAGraphics.pdf), "Showing Statistical Summary Data"section.

ArchestrA IDE Help (IDE.chm), "Sho+wing StatisticalSummary Data" topic.

After step 3 in the "To showhistorical summary datausing custom properties"procedure.

Add the following Important note immediately after step 3 in the To show historical summary datausing custom properties procedure in the "Showing Statistical Summary Data" section.

Important: The History Summary data type only works with ArchestrA object attributes intended forInTouch managed applications. Do not attempt to use custom properties assigned the History Summarydata type in Modern applications. AppEngine and UDO objects must be configured to summarize historydata and Modern applications do not support ArchestrA objects.

9 Existing product information about nonsupportedInTouch HMI AlarmSuite database views and migrationutilities.

InTouch HMI Alarms and Events Guide,(ITAlarmsAndEvents.pdf), "AlarmSuiteAlarm Log View" section, page 273.

ArchestrA IDE Help (IDE.chm), "AlarmSuiteAlarm Log View" topic.

InTouch HMI Alarms and Events Guide,(ITAlarmsAndEvents.pdf), "Migrating fromLegacy Alarm Systems", pages 481484.

ArchestrA IDE Help (IDE.chm), "Migratingfrom Legacy Alarm Systems" topic.

InTouch HMI Application Management andExtension Guide, (ITAppManagement.pdf),"Miscellaneous Limitations in a TerminalServices Environment" section, page 61.

ArchestrA IDE Help (IDE.chm),"Miscellaneous Limitations in a TerminalServices Environment" topic.

See affected book sectionsand help topics listed incolumn 1.

AlarmSuite is a legacy InTouch alarm database that is no longer supported and has been deprecatedfrom InTouch HMI 2014 R2.

All existing AlarmSuite information found in InTouch HMI 2014 R2 documentation is no longer valid andshould be ignored.

< top of document >

InTouch DocumentationThe InTouch product library consists of a set of Portable Document Files (PDF) available in the following location of the Wonderware System Platform DVD:

\Wonderware System Platform\InstallFiles\CDIntouch\UserDocs\English

You need Adobe Reader installed on your computer to view InTouch documentation. You can download the latest version of Adobe Reader from the Adobe Corporation web site:

http://www.adobe.com/products/acrobat/readstep2.html

After installing Adobe Reader, doubleclick a PDF file with your pointing device to view the book with Adobe Reader. You can also open a book with the Adobe Reader Open commandfrom the File menu. Contextsensitive documentation is also available with InTouch online help. Select Help for information about the current InTouch window that you have openon your computer.

< top of document >

© 2014 Invensys Systems, Inc. All Rights Reserved.

Invensys is a Schneider Electric company.

http://www.adobe.com/products/acrobat/readstep2.html

INDUSTRIAL SPARE PARTS SUPPLIERIMPEXRON GROUP COMPANIES

GERMANY USA IMPEXRON GMBH ONRION LLC

Gönningerstr. 99, 72793 93 South Railroad AvenuePfullingen, GERMANY Bergenfield 07621 NJ,USA0049 7121 305 9012 001 973 536 2331

JAPAN ITALIAYUSAKI LLC PARTELLI SRL

Build.No. K7 1F, 13-16 Str Via Santissima 20584-0032, Osaka-Fu, Japan Brescia Italia

0081 721 26 8450 0039 030 7640137

TURKEY MEXICOOZHAT LTD PARMEX SRL

Buttim Is Mrkz. A2-367 PRIVADA 10 B SUR #390819250, Bursa. Turkey 72530, Puebla, Mexico0090 224 211 2241 0052 222 9126090

FRANCE BULGARIAFABRIMAT SARL IMPEXRON LTD

4 boulevard Carnot 95400 bul. "6-ti septemvri" 254,Paris, France 4006 Plovdiv, Bulgaria

0033 1 79 97 40 05 00359 32 571 212

UKRANIAOTEC LTD IMPEXRON LTD

Ivana Franko Street , 55 ul.Spiro Gulapcev br.4465049 Odessa, Ukraine 1000 Skopje, Makedonija

00380 48 7348522 00389 2 3114495

[email protected] [email protected] www.onrion.com

[email protected] [email protected] www.partelli.it

[email protected] [email protected] www.parmex.com.mx

[email protected] [email protected] www.impexron.bg

MAKEDONIJA

[email protected] [email protected] www.impexron.mk



http://www.impexron.de/

http://www.onrion.com/



http://www.yusaki.jp/

http://www.partelli.it/



http://www.ozhat.com.tr/

http://www.parmex.com.mx/



http://www.fabrimat.fr/

http://www.impexron.bg/



http://www.otec.com.ua/

http://www.impexron.mk/