Wonderware InTouch HMI 2014 R2 (Version 11.1) Readme. New Features in Wonderware InTouch HMI 2014 R2

Transcription

1 Last revision: 12/02/2014 About This Readme Wonderware InTouch HMI 2014 R2 (Version 11.1) Readme This Readme provides information about InTouch HMI 2014 R2 (Version 11.1). Readme files from previous releases of Wonderware InTouch HMI are posted on the Wonderware Developer Network at 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 to version 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 to Wonderware System Platform 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. New Features in Wonderware InTouch HMI 2014 R2 ArchestrA Graphic Toolbox in WindowMaker InTouch WindowMaker incorporates the ArchestrA Graphic Toolbox containing a full complement of ArchestrA and Situational Awareness Library symbols. You can add a symbol 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 Applications Modern InTouch applications give you the capability to easily integrate ArchestrA symbols directly into your applications. You create and manage Modern applications from 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 of integrated ArchestrA symbols in managed InTouch applications with the familiar work flow of stand-alone InTouch applications. Conversion of InTouch Windows to ArchestrA Symbols You can convert selected windows of managed or Modern InTouch applications to ArchestrA symbols. The converted ArchestrA symbols appear in the WindowMaker ArchestrA Graphic Toolbox and the ArchestrA IDE Graphic Toolbox. In addition to graphics that appear in windows, all InTouch animation links embedded in windows are converted to the corresponding ArchestrA animation. After conversion, the original converted InTouch window is backed up. A new InTouch window is created in the InTouch application, which embeds the newly created ArchestrA symbols. Additional Situational Awareness Library Symbols InTouch HMI 2014 introduced an extensive set of Situational Awareness Library symbols. InTouch HMI 2014 R2 includes additional new or updated Situational Awareness Library symbols for alarms, trends, and valves: Alarms Trends Valves 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. 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 Y axes. SA_Trend_MultiPen: Shows up to four simultaneous trend lines of current and historical measured values. InTouch HMI 2014 R2 includes a set of two-way, three-way, and four-way 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) file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/intouch%2011.1%20readme.html 1/17

2 Graphic Connectors Orientation (up, down, right, or left) A new Connector tool has been added to the Symbol Editor Tools menu. A connector is a line drawn between graphic elements. A connector starts at a connection point on one graphic element and ends at a connection point on another element. Connectors are particularly useful for complex symbols containing many connected elements like flow diagrams, industrial piping, or electrical wiring. Connectors can change length or orientation in response to changes to the positions of connected graphic elements. Using connectors, graphic elements within a symbol can be moved, resized, or rotated and still maintain the connector between elements. The boundary border around each graphic element includes eight connection points to attach a connector. The Tools menu includes a Connection Point tool to add custom connection points on a graphic element. Also, control points can be added to a connector to change its shape. The shape of a connector can be changed by dragging a line segment between control points to another position with your mouse. Historical Statistical Summary Data You can add a custom property and set the Data Type property to History Summary to reference historical data collected over a specified period during run time. The Historian can transform this data to create a set of analog or state statistics that can be shown by an ArchestrA graphic during run time in a script or a Value Display animation. 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, and standard deviation. A custom property state reference can subscribe to statistics from analog data and saved to the Historian. Three types of historical state values are possible; Analog(Integer), String, and Null. Alarm Shelving Alarm shelving enables operators to temporarily remove selected alarms from the list of active alarms. A shelved alarm is suppressed and removed from the list of active alarms for a specified period. After the period ends, alarms are automatically unshelved and appear again in the list of active alarms. Authorized users can also manually unshelve 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 indicator icon shows the shelved alarm mode icon. In Alarm Border animation, suppressed and silenced alarm modes take precedence over an alarm in shelved mode. ArchestrA Alarm Client Control The ArchestrA Alarm Client control includes a set of enhancements to support alarm shelving. The configuration dialog box includes a set of run-time options to shelve and unshelve alarms. Also, a set of properties and methods have been added to shelve and unshelve alarms with scripts. Trend Pen Enhancements InTouch 2014 introduced the Trend Pen control, which incorporates animation that shows a succession of process values as a trend line consisting of current and historical data. InTouch 2014 R2 includes additional new enhancements to the Trend Pen control. Run-time 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 following properties 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 is plotted as a horizontal line from a trend data point to the time of the next data point on the trend's X-axis. Then, the trend line is drawn as a vertical line to the data point. In Line mode, the trend line is plotted directly to each successive data point within the trend period. Trend time Periods The Trend Pen control now includes the Time Period configuration option to set a trend period as either Moving or Fixed. In a Moving trend period, the start time of a trend period is the current time. The end time is the duration of the time period from the start time. In a Fixed trend period, the StartTime and EndTime properties do not change automatically. The default start time of a trend period is the current time, but the StartTime property can be modified by a script to set a start time of a trend time period. Enhancements to Programmatic Export and Import of ArchestrA Symbols InTouch HMI 2014 introduced the ArchestrA GraphicAccess application programming interface (API) to programmatically export and import an ArchestrA symbol between the ArchestrA Graphic Toolbox and an XML file. InTouch HMI 2014 R2 enhances the capability of the ArchestrA GraphicAccess API to export and import symbols to include: Overridden text strings Numeric format styles DataStatus elements Graphic connectors Trend Pen control Alarm Client control Trend Client control Advanced Numeric Format Styles The Configure Galaxy Style Library dialog box includes the Format Styles tab with options to individually configure Galaxy-wide number format styles for common types of numbers used in industrial applications. The Format Styles dialog box also includes fields to specify characters that appear during run time that indicate bad quality data or data that exceeds a fixed width field. Based on the selected number style, the fields appear on the Format Styles dialog box to change the default properties of number styles. file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/intouch%2011.1%20readme.html 2/17

3 Each global number style is assigned a unique name, which cannot be changed. A number style can be applied by name in design time and run time for an analog data type in User Input and Value Display animations. Also, grouped elements support global number styles. Remote Application Licensing Support You can assign read only access to a distributed InTouch application running in a Remote Desktop Connection or Terminal Services session. Read only access is appropriate for non-operators who need to view an application, but who should not have write permission. For example, managers need the capability to view an application on a mobile device with InTouch Access Anywhere. You set user access (read/write, read ownly) to remote applications with the Remote Access Properties dialog box, which is accessible as an option from WindowMaker'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/write applications and the INTOUCH_TSE_READONLY license feature line to support remote read only InTouch applications. License consumption is restricted to the type of application specified by WindowMaker's Remote Access Properties. If the number of remote users exceeds the INTOUCH_TSE_READONLY license feature line maximum, 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. Contents Introduction Hardware Requirements Operating System,.NET Framework, and Virtualization Requirements SQL Server Requirements InTouch Access Anywhere Requirements Introduction System Requirements This 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 Guidelines The following table provides guidelines for hardware configurations suitable for Wonderware System Platform 2014 R2 software based on the size of the installation, applicable to both 32-bit and 64-bit systems. The Intel Itanium 2 processor is not supported. Compact Installation (1-500 I/O per Node) CPU (GHz) Cores (Minimum) RAM (GB) Storage (GB) (sufficient for 1 max frequency) Monitor Resolution Network (MBPS) x Small Installation (1-5K I/O per Node) x Medium Installation (5k - 50k I/O per Node) x Large Installation (50k - 400k I/O per Node) x Preferred Environment (64-bit OS and SQL) x 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 following Microsoft Web pages for Windows and SQL Server hardware requirements: System Requirements and Installation Information for Windows Server 2012 R2 Windows Server 2008 System Requirements file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/intouch%2011.1%20readme.html 3/17

4 Windows 8 and 8.1 System Requirements Windows 7 System Requirements Hardware and Software Requirements for Installing SQL Server 2014 Hardware and Software Requirements for Installing SQL Server 2012 Hardware and Software Requirements for Installing SQL Server 2008 R2 Hardware and Software Requirements for Installing SQL Server 2008 Auxiliary Hardware Requirements This 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 C2-40 Mini Driver Smart Card Smart Card Reader: OK 3021 USB Smart Card Readers Operating System,.NET Framework, and Virtualization Requirements Summary 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 R2 The following table lists the operating system,.net Framework, and virtualization requirements for the suite of Wonderware System Platform products, including InTouch HMI 2014 R2. 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.NET Framework Virtualization Host 7 SP1 Embedded (32-bit only) 7 SP1 Professional,, Ultimate - 8 Professional, Professional, R2 SP1 (64- Server 2012 Standard and Data Center (64- Server 2012 R2 Standard and Data Center ( SP IE 10 IE 11 Hyper-V (Based on Supported OS version) VMWare 5.0 (Basic virtualization- No HA/DR) Application Server 2014 R2 (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) Information Server 2014 R2 Portal and Client (5.6) N Y Y Y Y Y Y C N Y Y Y 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 (1-500 I/O per node) Small Installation (1-5,000 I/O per node) Medium Installation (5k-50k I/O per node) Large Installation (50k-400k I/O per node) Preferred Environment (64-bit OS and SQL Server) Y N N N N N N C N N Y Y Y N Y Y Y Y Y Y C N N Y Y Y N Y Y Y Y Y Y C N N Y Y Y N N N N Y Y Y C N N Y Y Y R R C N N Y Y Y Supported by all Supported by a subset of products Supported and Recommended Not Supported Coexist Y S R N 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 charms appears, which includes Search, Share, Start, Devices, and Settings. Pointing a mouse cursor to the upper-right corner of a screen also shows the Windows charms for non-touch screens. file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/intouch%2011.1%20readme.html 4/17

5 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 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 installation process. The Galaxy Repository (GR Node) can run on a client Windows operating system only in a single-node configuration in which Wonderware System Platform products are installed on a single computer. For a multi-node environment, the Galaxy Repository must be installed on a computer running a version of a Windows Server operating system. Development and application nodes are considered to be clients of the server GR node. When the operating system is upgraded on a computer, existing Wonderware System Platform products must be uninstalled prior to the upgrade and then reinstalled after the upgrade. There are two exceptions. Wonderware System Platform products do not need to be uninstalled when upgrading from Windows 8 to 8.1 or Windows 2012 to Windows 2012 R2..Net Notes Versions of.net (other than 4.x versions) can coexist, but all.net code, including QuickScript.net scripts, run under.net For more information about.net Framework requirements and compatibility, see.net Framework Requirements and Compatibility..NET 3.5 is installed only because the supported SQL Server versions require it. No other dependencies must exist. 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 to host 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 more information, 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 Server 2008 R2. When InTouch WindowViewer is started and generates alarms from an interactive Windows 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 8, or Windows Server 2008 R2 node, open the SMC Logger and look for the most recent string generated by AlarmMgr. For example: "Registering AlarmMgr with SLSSVC as AlarmMgr ". The indicated IP address will be unique to your alarm-providing node. Note the IP address for Step 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 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 Windows versions 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 or later, Session 0 is no longer an interactive session, and is reserved only for Windows services. From Windows Server 2008 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 R2 operating 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. You must 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 to work 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 carry forward the restriction introduced with the Windows Vista operating system which permits only one alarm provider. While both Wonderware Application Server and InTouch HMI can be configured as alarm providers, only one alarm provider can be configured at any one time. 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 was started 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 a remote RDP session regardless of /console or /admin switches in the mstsc connection. file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/intouch%2011.1%20readme.html 5/17

6 To disable fast user switching through the Group Policy interface 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 Task Manager. 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. Right-click and select DWORD (32- Value. Name it HideFastUserSwitching. 5. Set the HideFastUserSwitching data value to 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 InTouchViewApp object: 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 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 in the session. ArchestrA Graphic referencing InTouch: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 in the session. InTouch Graphic referencing Galaxy: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. Wonderware InTouch HMI 2014 R2 (v11.1) Operating System Notes The following table lists the supported operating systems that can be installed on computers that run InTouch HMI server and client components. Wonderware InTouch HMI Components Operating Systems WindowMaker WindowViewer ArchestrA IDE ArchestrA Run Time Galaxy Repository Windows 7 SP1 Embedded, 32-bit only Windows 7 SP1 Professional,, or Ultimate, 32-bit or 64-bit Windows 8 Professional or 32- bit or 64-bit Windows 8.1 Professional or 32- bit or 64-bit Windows Server 2008 R2 SP1 Standard or, 64-bit only Windows Server 2012 Standard or, 64-bit Windows Server 2012 R2 Standard or, 64-bit Y Y N N N Y Y Y Y N Y Y Y Y N R R Y Y N Y Y Y Y Y Y Y Y Y Y Y Y R R R Supported Supported and Recommended Not Supported Y R 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 (32-bit or 64- is the recommended operating system to run InTouch HMI run-time 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 single-node server configuration that runs one or more databases for an InTouch HMI system. file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/intouch%2011.1%20readme.html 6/17

7 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 not disabled 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 running InTouch 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 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. The following InTouch legacy script functions do not operate on 64-bit 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 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 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 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 R2 (v11.1) Support for Windows User Account Control Wonderware System Platform 2014 R2 with InTouch HMI v11.1 supports User Account Control-enabled operations on run-time nodes..net Framework Requirements and Compatibility IMPORTANT: We strongly recommend that prior to upgrading your existing applications to Wonderware System Platform 2014 R2, that you back up your applications, become familiar with the changes introduced by Microsoft in.net 4.5.1, and review your.net scripts and.net controls for any required changes. After upgrading to Wonderware System Platform 2014 R2, you should perform application testing on application scripts and on script libraries used by the application to ensure they continue to function properly under.net 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 The Wonderware System Platform installation program will install.net if it is not already present in your system..net can coexist with previous versions of.net Framework. On nodes where SQL Server is installed,.net 3.5 is also installed by Wonderware System Platform. In this scenario, Wonderware System Platform 2014 R2 will use.net 4.5. 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 Although.NET Framework is highly compatible with applications that are built with earlier.net Framework versions, Microsoft has introduced changes in.net 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 Application Server, 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 of BinaryStream 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: What's obsolete in the.net Framework class library: Migration Guide to the.net Framework 4.5:.NET Framework 4 Migration Issues: Virtualization Host Support Wonderware System Platform 2014 R2 supports the following virtualization environments: Microsoft Hyper-V: based on the version of Windows VMware 5.0: basic virtualization without High Availability and Disaster Recovery 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 Components The following table lists SQL Server requirements for Wonderware System Platform 2014 components, including InTouch HMI 2014 R SP3 Express R2 Express R2 SP1 Express R2 SP2 Express SP R R2 SP R2 SP2 file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/intouch%2011.1%20readme.html 7/ Express- SSMSE 2012 SP1 Express- SSMSE 2012 SP2 Express- SSMSE SP SP Express- SSMSE 2014

8 SSMSE (32- SSMSE (32- SSMSE (32- SSMSE (32- (32-bit Only) (32-bit only) (32-bit only) Application Server 2014 R2 InTouch 2014 R2 Historian 2014 R2 S S S S Y Y Y Y S S S Y Y Y S Y S S S S Y Y Y Y S S S Y Y Y S Y S S S S Y Y Y Y S S S Y Y Y S Y Historian Client 2014 Information Server Portal 2014 R2 S S S S Y Y Y Y S S S Y Y Y S Y System Size: Compact Installation (1-500 I/O per node) Small Installation (1-5,000 I/O per node) Medium Installation (5k-50k I/O per node) Large Installation (50k-400k I/O per node) Preferred Environment (64-bit OS and SQL) N N Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N Y Y Y Y Y Y Y Y Y Y Y Y Y Y N N N N N Y Y Y N N N Y Y Y N Y R Supported For small systems only Y S Supported and Recommended Not Supported R 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 Windows-based 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 SQL Server administrative rights, the proper configuration of SQL Server may not be applied. A post-install aaconfig SQL utility allows you to verify if the SQL configuration has been performed. 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 For example, you cannot restore a Galaxy.cab file backed up on SQL Server 2008 to a node with SQL Server SQL Server database backups from SQL Server 2005 forward are not backward-compatible. Attempting such a restore initializes, and the progress dialog box quickly displays 100% completion of restoring the database, but the Galaxy.cab restore operation does not actually complete, and no Galaxy 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 Server 2012 from SQL Server versions 2008 or You can migrate to SQL Server 2008 from SQL Server versions 2005 or You cannot migrate directly from SQL Server 2000 to SQL Server Such a migration requires an intermediate version installation. For more information and helpful procedures, see the following Microsoft references: Upgrade to SQL Server 2014 Migrate SQL Server 2000 to SQL Server 2012 Migrating to SQL Server 2008 R2 Migrating to SQL Server 2008 T-SQL scripts to migrate SQL server 2000 user databases to SQL server 2012 ALTER DATABASE Compatibility Level (Transact-SQL) SQL Server 2012 ALTER DATABASE Compatibility Level (Transact-SQL) SQL Server 2008 R2 SQL Server Rights Requirements: SQL Server 2008 and later versions do not automatically create the BUILTIN\Administrators role delivered in SQL Server 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 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. file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/intouch%2011.1%20readme.html 8/17

9 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 install the full SQL Server prior to modifying the InTouch HMI installation or installing Wonderware Application Server. If you plan to use SQL Server Express with Wonderware Information Server 2014 R2 and Wonderware InTouch HMI 2014 R2 on the same node, the following limitations apply: 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. Installing Wonderware 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 non-express edition) on a remote node. The computing capacity of SQL Server 2012 SP1 Express is limited to the lesser of one CPU socket or four processor cores. For InTouch HMI-only installations, the Wonderware System Platform installer 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 and Runtime, a Galaxy Repository will be installed. InTouch Access Anywhere Requirements The following sections describe the requirements to run Wonderware InTouch Access Anywhere Server and supported browsers. For detailed information, see the Wonderware InTouch 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 Access Anywhere version 11.0 from all InTouch nodes where it is installed and install InTouch Access Anywhere version 11.1 that is in Wonderware System Platform 2014 R2. You can determine the version of InTouch Access Anywhere Server installed on a computer using Programs and Features from the Windows Control Panel. Requirements The InTouch Access Anywhere Server can be installed as a Wonderware System Platform installation option. The InTouch Access Anywhere Secure Gateway is an optional component installed 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 Desktop Services on Windows 2008 Server R2 for Wonderware Products". You also can refer to 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 Browsers Wonderware InTouch Access Anywhere can run on smart phones, tablets, laptop computers, or any other device that supports an HTML5-compliant web browser. Browsers validated to 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 4-21 Safari versions 5, 6 Chrome versions Opera versions 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 an InTouch application with InTouch Access Anywhere on a portable device, see the InTouch Access Anywhere User Guide. Wonderware InTouch HMI 2014 R2 (v11.1) Product Compatibility Product 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 the ability of a product to work with various versions of the same product running on different nodes. Coexistence refers to same-node 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 single-node environment, if you want to install multiple components on a single computer, all components must be at the versions delivered in Wonderware System Platform 2014 R2. In a node-to-node 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 Co-existence 4.5 N 2012 Y 2012 R2 Y file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/intouch%2011.1%20readme.html 9/17

10 Wonderware System Platform 2012 R2 P01 Y 2012 R2 P02 Y 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 P P01 Y Y MES 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 Information Server 5.6 requires an InBatch hotfix to maintain compatibility. Wonderware QI Analyst 10.0 (2012 R2) N N 10.1 (2014) Y (*) Y (*) 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 ArchestrA Workflow 1.5 N N (2012) Y Y 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 Recipe Manager Plus Schneider Electric Citect-VJC Schneider Electric ClearSCADA Historian Client Trend 10.6 Y Y InTouch 11.0 and 11.1 Y Y MRC (Mobile Report Connector) Y Y 1.0 (2014) Y Y 1.5 (2014 R2) Y Y 7.2 SP3 Y Y 7.3 Latest SP N Y 7.4 SP1 Y Y CS 2013 R1 N Y CS 2013 R2 N Y CS 2014 R1 N Y CS 2015 R1 Y Y Supported Not Supported Not Applicable Y N 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 listed product only in the environments that are supported by that particular product. Wonderware InTouch HMI Installation For 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 the installation package. This booklet is provided for all supported languages. The information provided in this Readme file supersedes the InTouch Installation Help (Install-InTouch.chm) for the French, German, Japanese, and Simplified Chinese languages. Contents Installing 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 file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/intouch%2011.1%20readme.html 10/17

11 Installing the Wonderware InTouch HMI The major decision you must make when you install InTouch HMI is whether to install the InTouch development and run-time components, or the run-time 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 the ArchestrA IDE if you chose to install development components. What You Need to Install InTouch HMI You 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. Prerequisites The 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 system-specific rather than product-specific. 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 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 Server components. When you select InTouch Development and Runtime, a Galaxy Repository will be installed for you. The installation program installs both system-specific and product-specific prerequisites. You do not have to exit from the installation program to install the prerequisite software. For more information about Wonderware System Platform installation prerequisites, see the Wonderware System Platform Installation Guide. 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 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 the Start menu in the Wonderware Common folder after you install InTouch. 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 recreate the user account using the Change Network Account utility, the Microsoft Windows security component on the computer can take several minutes to update this information on the ArchestrA Galaxy node. Until that occurs, the ArchestrA component may not function properly. Restarting the Galaxy node updates this information immediately. Performing the InTouch HMI Installation Before 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 double-clicking 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 product-based selection or installation by computer roles. As you are only installing InTouch HMI, click the product-based 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 Pen Trend from the product list to install it as part of the InTouch HMI installation procedure. Invensys License Manager file:///media/rhandsome/toshiba/wonderware/documents/old%20intouch%20readme%20files/intouch%2011.1%20readme.html 11/17