Install Archestra License Manager

by



ArcGIS License Manager 2020.1 uses FlexNet Publisher license management software. Details on the version of FlexNet Publisher used in each version of ArcGIS License Manager can be found in Technical Article 13214. This version of the license manager will support all product releases listed within the Supported Software Products topic. Visit the Existing users page for information on migrating from version 9.x to 2020.1.

Caution:

If licensing ArcGIS products in the cloud or in virtualized environments using ArcGIS License Manager, please refer to the Esri whitepaper on cloud licensing for more information, including details about supported cloud instance types.

For customers using ArcGIS License Manager to authorize ArcGIS Pro and Premium App named user licenses via a Portal for ArcGIS installation, please refer to the Configure License Manager for use with Portal for ArcGIS topic for details on authorization and configuration. To install the License Manager software, follow the instructions below.

Untuk menjalankan ArchestrA license manager bisa dipilih dari Program Wonderware ArchestrA License Server ArchestrA License Manager. Untuk install file license, pilih File Install License File. Pastikan untuk memilih file ArchestrAServer.LIC untuk menginstall Server License. Setelah proses instalasi, kita harus melakukan konfigurasi. License as mentioned above, will also be provided via email. No licenses will be shipped on CD. Schneider Electric Licensing System The Licensing System is composed of a browser-based License Manager and a License Server that together allow you to share and deliver licenses for your installed products. The License Manager is browser-based and very.

Note:

You do not need to uninstall existing ArcGIS software products to install the license manager, but you do need to uninstall 10.0 or older versions of the license manager to install the latest version. Before installing ArcGIS License Manager 2020.1, please review the System Requirements.

Important: Starting with ArcGIS License Manager 2019.0 (Linux platforms only), the FlexNet licensing service must be installed as a separate step following install of the ArcGIS License Manager setup, both for clean installs or for in-place upgrades of the software. If the FlexNet licensing service is not installed, this will result in issues where clients cannot connect to the ArcGIS License Manager. At the completion of the ArcGIS License Manager install, instructions will be displayed for completing the installation of the FlexNet licensing service, which require the user to provide root privileges for the install to proceed. If the FlexNet licensing service is not installed at this stage, it must be manually installed separately. Please see the section below titled Manually installing the FlexNet licensing service (applies to Linux Platforms only) for details.

ArcGIS License Manager communicates through TCP/IP, which must be installed and functioning properly on your Windows license server. In addition, TCP/IP requires that either a network card, along with its drivers, or the MS Loopback Adapter be installed on your Windows machine. An Internet connection is also strongly recommended for the license authorization process. If you do not have an Internet connection on the license manager machine, you can select the email or website authorization option on the Authorization Method panel of the Software Authorization Wizard.

Installing the ArcGIS License Manager

Upon purchasing your ArcGIS products, you will receive an email from Esri Customer Service listing the purchased products and associated authorization numbers and license counts. Alternatively, you can visit the My Esri site to obtain authorization information. Follow the steps below to install, authorize, and start the license manager:

  1. Run the License Manager setup from your My Esri software download or from the ArcGIS installation media.
  2. Follow the instructions to install the license manager and FlexNet licensing service. At the end of the installation, ArcGIS License Server Administrator appears. If you did not install the FlexNet licensing service during the License Manager setup, you must manually install the FlexNet licensing Service before attempting step 3. Please see the section below titled Manually installing the FlexNet licensing service (applies to Linux Platforms only) for details.
  3. Complete the authorization process and start the license service. If you choose to do this step at a later time, on Windows, you can access License Server Administrator from Start > Programs > ArcGIS > License Server Administrator. On Linux, you can run License Server Administrator from the installation location using the following command: <installation_path>/arcgis/licensemanager/LSAdmin.
  4. Click Authorization in the table of contents, select a version from the Version drop-down list, and click the Authorize Now button to launch the Software Authorization Wizard.
  5. Follow the instructions on the dialog boxes to complete the authorization process. A provisioning file (*.prvs) generated on the My Esri portal can be used to speed up the authorization process for concurrent use. This file fills in all the necessary user and product authorization information in the wizard. More information on provisioning files can be found in the section Provisioning Files.
  6. Click Finish to close the wizard and return to License Server Administrator.

Manually installing the FlexNet licensing service (applies to Linux Platforms only)

  1. Navigate to <installation_path>/arcgis/licensemanager
  2. Run install_fnp.sh. This shell script configures the FlexNet licensing service executable to run as a root-privilege setuid process.
  3. The FlexNet licensing service daemon needs to run continuously. Therefore, a further installation step is required to ensure it is started a boot time. Because the FlexNet licensing service daemon does not need to run with root privilege, it can be started by adding the following line to a nominated user's crontab (In the case of ArcGIS License Manager 2020.1): @reboot /usr/local/share/FNP/service/11.16.5/FNPLicensingService -r 2>&1 >/tmp/fnpd.log

Windows installations, or Linux installations of ArcGIS License Manager 2018.1 and earlier do not require the additional step of installing the FlexNet licensing service.

Authorizing licenses silently

Run the following command to use the License Manager and a provisioning file generated from My Esri to silently authorize ArcGIS Desktop 10.1-10.8.1, ArcGIS Engine 10.1-10.8.1, ArcGIS CityEngine 2012.0-2021.0, and ArcGIS Pro 1.2-2.7 concurrent use licenses:

softwareauthorizationLS.exe -S -VER 10.8 -LIF <path to the *.prvs file>

A -verbose switch can be added to the above command to display the status of the authorization process on the command line.

On Linux, use the following syntax:

$ ./SoftwareAuthorizationLS -S -VER 10.8 -LIF <path to the *.prvs file>

Note:

When accessing the Software Authorization Wizard through terminal services in a Linux environment, a valid display must be set. Technical Article 12175 provides more information on how to setup an Xvfb display to use ArcGIS software through terminal services in a Linux environment .

Authorizing licenses offline

If the machine hosting your license manager does not have access to the Internet, you can complete the authorization process in an offline mode. After launching the Software Authorization Wizard as described in step 4 above, follow these instructions:

  1. On the second dialog box of the authorization wizard, select the option Authorize at Esri's website or by email to receive your authorization file.
  2. Follow the instructions on the rest of the dialog boxes and save the authorization request file when prompted at the end. By default, this will be saved as authorize.txt.
  3. Follow the instructions on the last dialog box to send or upload the file from a machine that has email and/or Internet access.
  4. Esri Customer Service will process the request and return the response file (*.resps) that contains your licenses.
  5. Save this file to your license manager host machine and relaunch the Software Authorization Wizard from the License Server Administrator.
  6. On the first panel, select the third option I have received an authorization file from Esri and am now ready to finish the authorization process and browse to the response file to complete your authorization.

Upgrading licenses from 10.1 through 10.7 to 10.8.x

Concurrent use ArcGIS Desktop 10.8.x and Engine 10.8.x use the same 10.1-10.8 licenses. If you have previously authorized 10.1-10.8 licenses on your License Manager and did not deauthorize your licenses before installing ArcGIS License Manager 2020.1, you do not need to reauthorize your ArcGIS License Manager. Follow the instructions below for upgrading your License Manager software from 10.1-10.6, or 2018.0-2020.0 to version 2020.1.

Note:

If you perform an in-place upgrade of the ArcGIS License Manager software, there is also no requirement to re-authorize your ArcGIS Pro or ArcGIS CityEngine concurrent use licenses. The licenses will continue to work.

Upgrading from 10.3-10.6, or 2018.0-2020.0 to ArcGIS License Manager 2020.1 with named user licenses

Named user licenses for use with a Portal for ArcGIS instance remain the same with ArcGIS License manager 2020.1. If you perform an in-place upgrade of the ArcGIS License Manager software, there is no need to re-authorize your valid named user licenses or export the Portal JSON file to Portal for ArcGIS. The in-place upgrade instructions for ArcGIS License Manager software can found in the below section titled Upgrading License Manager software from 10.1-10.6, or 2018.0-2020.0 to License Manager 2020.1.

Upgrading License Manager software from 10.1-10.6 or 2018.0-2020.0 to ArcGIS License Manager 2020.1

ArcGIS Desktop and Engine 10.1-10.8 licenses will operate with ArcGIS Desktop and Engine 10.8.x, and no license upgrade is required. However, any client software operating at version 10.8.x must use a 2020.0 License Manager or higher. To upgrade ArcGIS 10.1-10.6, or 2018.0-2020.0 License Manager software to ArcGIS License Manager 2020.1, follow these instructions:

  1. Open the License Server from Start > Programs > ArcGIS > License Server Administrator. On Linux, you can run License Server Administrator (in the case of version 2020.0) from the installation location using the following command: <installation_path>/arcgis/licensemanager/LSAdmin.
  2. Stop the License Service under Start/Stop License service and exit the License Server Administrator.
  3. Install ArcGIS License Manager 2020.1 and the FlexNet licensing service. The installer will automatically uninstall your ArcGIS License Manager 10.1-10.6 or 2018.0-2020.0, and install ArcGIS License Manager 2020.1 and in some cases may prompt to install the FlexNet licensing service. If the FlexNet licensing service was not installed following the ArcGIS License Manager installation, the FlexNet licensing service must be installed manually before proceeding with step 4. Please see section above titled Manually installing the FlexNet licensing service (applies to Linux Platforms only) for more details.
  4. Open the License Server from Start > Programs > ArcGIS > License Server Administrator. On Linux, you can run License Server Administrator from the installation location using the following command: <installation_path>/arcgis/licensemanager/LSAdmin. .
  5. Start the license service under Start/Stop License Service and exit the License Server Administrator. ArcGIS License Manager 2020.1 is now ready for use.

Upgrading older software and licenses from 10.0 to 10.1 or newer (including License Manager 2020.1)

ArcGIS 10.0 licenses will not operate ArcGIS 10.1-10.8.x software. You must deauthorize your 10.0 licenses before uninstalling the ArcGIS 10.0 License Manager.

  1. Open the License Server Administrator from Start > Programs > ArcGIS > License Server Administrator.
  2. Select the Authorization option in the left hand panel, then press the Deauthorize... button. The Software Authorization Wizard will open.
  3. Step through the Software Authorization Wizard to complete the deauthorization process. You can opt to deauthorize online or offline via email or My Esri file upload.
  4. Close the License Server Administrator.
  5. Uninstall the ArcGIS 10.0 License Manager.
  6. Install ArcGIS 10.1 or newer License Manager.
  7. Go to the Authorization folder, click Authorize Now, and follow the instructions to complete the authorization process.

Configuring a firewall

In some cases, a firewall may block inbound and outbound traffic to the ArcGIS License Manager preventing license usage from client machines, requiring ports to be opened in the firewall of the license manager host. Please refer to the topic Configure ArcGIS License Manager to work through a firewall.

Contacting Esri Customer Service

If for any reason you are unable to locate your authorization information, you can contact Esri Customer Service and request that it be resent.

In the United States, you can contact Esri Customer Service by calling 888-377-4575, or visit the My Esri site.

Outside the United States, contact your local Esri distributor.

INSTALLATION GUIDE

Description

Step by Step Installation of Wonderware's InTouch version 2014 (11.0)

Author

Jimmy McGlaughlin

Publish Date01/14//2014

Applies to Software

InTouch Classic

Applies to Version

11.0

Applies to System/Module

n/a

Article Version

01.01.01

************************************************************************************************************************************************************

Pre-Requisites

Important!

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

  • If you previously installed FS Gateway 2.0 SP1 without any other InTouch products, then installing ASP 2014 will upgrade FSGateway to version 3.0 SP1.
  • If you previously installed FS Gateway 2.0 SP1 as part of ASP 2012 with InTouch 10.5, you must uninstall FS Gateway before upgrading to ASP 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.

Manager

System Requirements

Introduction

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

Hardware Requirements

Hardware Requirements by Installation Type

The following table lists the hardware requirements of different types of Wonderware System Platform 2014 installations based on the expected number of I/O operations per node.

Hardware Requirements Notes:

Windows 7 and Windows Server 2008 R2 operating systems and SQL Server versions impose hardware requirements that may exceed the minimum requirements for Wonderware Application Server 2014 (v4.0). If you intend to install Wonderware System Platform 2014 on a computer running Windows Server 2008 R2, Windows 8, Windows Essentials 2012, or SQL Server 2012, see the following Microsoft Web sites for a complete list of hardware requirements:

  • www.microsoft.com/windowsserver2008/en/us/system-requirements.aspx
  • www.microsoft.com/windows/windows-8/get/system-requirements.aspx
  • msdn.microsoft.com/en-us/library/ms143506.aspx#EE32

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

Using Multiple Network Interface Cards

If you are using multiple network interface cards (NICs), you must configure certain settings for the firewall or else a remote node cannot connect to the Galaxy Repository node.

A connection is a term used to define a network interface card (NIC), its settings and the settings of whatever the NIC is connected to. Under certain circumstances, the connection on your computer can change if, for example, the IP address on your network card changes. Your computer's connection can be affected by external factors. During computer startup, and each time a connection changes, the operating system goes through an 'Identifying' process to determine which profile should be assigned to the connection.

A profile is a collection of firewall settings that can be applied to a connection. There are three profiles currently defined in the operating system: Domain, Public, and Private.

  • The Domain profile is active only when the computer can authenticate with a domain controller on all active interfaces such as LAN, wireless, and VPN. The domain profile may be more or less restrictive than the other two profiles depending on network security policies.
  • The Private profile is active whenever the network type for all active network connections on the computer are identified as private networks. The private profile typically is used in a more trusted environment and is less restrictive than the public profile to allow for network discovery.
  • The Public profile is active in all other circumstances. The public profile typically is more restrictive than the private profile because the computer often is connected to the Internet in an insecure location. Network discovery and remote access are disabled rather than explicitly blocking specific traffic. Firewall exceptions and rules can be created on any or all of these profiles.

This is important because the OS Configuration utility and the Firewall utility apply their firewall exceptions to the Domain and Private profiles only.

As previously noted, you can specify which profile you want assigned to a connection as long as that connection is not a Domain connection. This is done through the 'Network and Sharing Center'. Click the Network icon located on the right side of the task bar and then click one of the networks that are shown. You can change a connection from a Public profile to a Private profile. The firewall calls these settings 'Profiles' but the network calls them 'Location types.'

On computers using dual NICs, the first NIC is normally connected to the domain and is assigned the Domain profile automatically. Windows typically assigns the second NIC the Public profile.

The first issue is that your entire computer (all connections) is restricted to the most restrictive of the profiles assigned to any connection. So if the second connection was assigned a profile of Public, none of the firewall exceptions set by the OS Configuration or Firewall utilities will be allowed. The exceptions were set for Domain and Private only, not Public. You must set the second connection to the Private profile for any of the firewall exceptions to work. You want the active profile on the message exchange (MX) NIC to be the profile opened by OS Configuration.

The second issue is that it appears that a restart of your computer, or even a restart of a computer to which you are connected, can change your connection back to the Public profile. Once again the firewall exceptions will not be effective. You'll have to change the connection back to the Private profile after each restart or a restart of the connected computer.

To avoid these NIC issues and prevent the “Identifying” process from taking place on a connection and changing the assigned profile, certain items must be present in the definition of the connection. Follow these rules and procedures:

  • If you have only one NIC, no action is required. The profiles and firewall rules are automatic.
  • To configure two NICs, do the following:

1. If the second NIC is not physically connected to anything (that means no wire in it), no action is required. The profiles and firewall rules are automatic.

2. If the second NIC is connected, it MUST be configured. Follow the rules for configuring a normal redundancy setup provided in the Wonderware Application Server User's Guide and the accompanying online help.

  • Assign the NIC an IP address, subnet mask and gateway address. Typically, these addresses are internal, non-routable addresses. For example, 192.168.1.xx and 10.x.x.x are common addresses of this type.
  • A NIC acting as Redundancy Message Channel (RMC) does not require a default gateway. Otherwise, the gateway can be the same as the IP address. Vista and Windows Server 2008 will identify this NIC and assign it a Private profile.

If you do not configure the second NIC, Windows 7 and Windows Server 2008 will assign a profile of Public to this NIC and cause all of the Wonderware product firewall exceptions to be deactivated on all NICs.

3. Set a security policy so that Windows 7 and Windows Server 2008 do not re-set the RMC NIC to a Public profile on rebooting the system or changing the IP address. To make the Private profile setting persistent, do the following:

  • On the Windows Start menu, click Run.
  • Enter and run this command: SECPOL.MSC. The Local Security Settings menu appears.
  • Select Network List Manager Policies on the menu tree.
  • Select Unidentified Network from the Network Names displayed.
  • Right-click, then select Properties, and then change the Location type from Not configured to Private.
  • Exit the menu and return to Windows.

4. If you have more than two NICs, make sure all connected NICs are configured with an IP address.

Operating System, .NET Framework, and Virtualization Requirements

Summary of Software Requirements for InTouch HMI Version 11

The following table lists the operating system, .NET Framework, and virtualization requirements for the suite of Wonderware System Platform products, including InTouch HMI Version 11.

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

Software Requirement Notes:

  • The entry for Application Server applies to the ArchestrA IDE (Development Node) and ArchestrA Run time (Application Node).
  • The Galaxy Repository (GR Node) can run on a client Windows operating system only in a single-node configuration.
  • Development and application nodes are considered to be clients of the server GR node.
  • Other .NET Framework versions can coexist except .NET 4.0. But, all scripts in objects run in .NET Framework 4.5. For more information about .NET Framework requirements and compatibility, see .NET Framework Requirements and Compatibility
  • .NET 3.5 is installed by System Platform only because the supported SQL Server versions require it. No other dependencies to .NET 3.5 must exist.

Operating System Notes Common to Wonderware Products

ActiveX Controls Behavior on Windows 7, Windows 2008 R2, and Windows 8 Operating Systems

Due to the Data Execution Prevention (DEP) feature of Windows 7, Windows 2008 R2, or Windows 8 operating systems, any ActiveX control built with ATL version 7.1 or earlier will fail to host or will have unpredictable behaviors in InTouch HMI 11.0 either in WindowMaker or WindowViewer running on supported versions of Windows. For more information, contact Wonderware Technical Support.

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 253.127.148.120'. The indicated IP address will be unique to your alarm-providing node. Note the IP address.

2. In the Alarm Query tab of the AlarmViewer control on the remote computer, configure the alarm query as follows, substituting your nodename of the alarm providing InTouch HMI for 'nodename' below and substituting your IP address noted in the previous step:

nodename:ip_addressintouch!$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 alarm-providing node are shown accurately in the AlarmViewer control.

Wonderware InTouch HMI and Alarm DB Logger

In earlier releases of InTouch HMI that supported Windows Vista, Windows 7, or Windows Server 2008, the Alarm DB Logger could not be enabled to run as a service. The Alarm DB Logger now runs as a Service in Windows Vista and later operating systems primarily to support Galaxy Alarms and InTouch HMI Alarms from Terminal sessions. However, there is a limitation in that the combination of Alarm DB Logger configured as a service and InTouch HMI running locally as a console application is still not supported. If InTouch HMI needs to run in the Console session, the Alarm DB Logger must be configured in the Alarm DB Logger Manager as a 'Normal Application' instead of a 'Windows Service'.

Also, if you are running the Alarm DB Logger as a console application, you cannot run it in the Terminal session until you close the one that is running in as a console application.

Refer to the updated Tech Note 725, 'Running InTouch HMI and AlarmDBLogger Services on Vista and Later Operating Systems,' for full details of the supported scenarios and applicable alarm query syntax.

Terminal Services Behavior in Windows Server 2008 and Later Operating Systems

In a change from Windows Server 2003, Windows Server 2008 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 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 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.

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 SwitchUser 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. Right-click and select DWORD (32-bit) 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 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 (v11.0) 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.

Notes:

  • The recommended operating system for a Galaxy Repository is Windows Server 2008 R2 SP1.
  • Microsoft Windows 7 SP1(32-bit or 64-bit) is the recommended operating system to run InTouch HMI client components.
  • Microsoft Windows Server 2008 R2 SP1 is the recommended operating system to run InTouch HMI server components.
  • The recommended operating system for InTouch HMI development is Windows Server 2008 R2 SP1 or Windows 7 SP1.
  • The recommended operating system for run-time nodes is Windows 7 SP1.
  • Window 7 SP1 Embedded is supported on compact systems only.

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

  • 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 StartProgramWonderwareInTouchRecipe, 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 and Windows Server 2008 R2 operating systems.
  • Hovering to select from the Windows keyboard does not work in the Windows 7 Professional and Windows Server 2008 R2 Standard operating systems.

Wonderware InTouch HMI 2014 (v11.0) View Applications and DDE Support

Windows 7 and Windows Server 2008 do not support NetDDE 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.

Windows Server 2003 and Windows XP Pro still support NetDDE.

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

Wonderware InTouch HMI 2014 (v11.0) Support for Windows User Account Control

Wonderware System Platform 2014 with InTouch HMI v11.0 supports User Account Control-enabled operations on run-time nodes. You must disable User Account Control (UAC) before installing Wonderware System Platform 2014 and before performing Configurator operations. UAC also must be disabled on IDE and GR nodes.

.NET Framework Requirements and Compatibility

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

Wonderware System Platform 2014 leverages Microsoft .NET Framework 4.5. The Wonderware System Platform installation program will install .NET 4.5 if it is not already present in your system. If .NET 4.0 is your current .NET version, note that it is possible for .NET 4.0 and .NET 4.5 to coexist in the same machine. In this scenario, ASP 2014 will use .NET 4.5. Other applications you may have on the same machine with dependencies on .NET 4.0 will access .NET 4.5.

Although .NET Framework 4.5 is highly compatible with applications that are built with earlier .NET Framework versions, Microsoft has introduced changes in .NET 4.5 to improve security, standards compliance, correctness, reliability, and performance that may require changes to .NET scripts you may have created with Wonderware System Platform 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.

Virtualization Support

Wonderware System Platform 2014 supports the following virtualization environments:

  • Microsoft Hyper-V: based on the supported operating system version
  • VMware 5.0: basic virtualization without High Availability and Disaster Recovery
  • VMware VSphere 5

SQL Server Requirements for All Wonderware Components

The following table lists the SQL Server requirements for Wonderware System Platform 2014 components, including InTouch HMI 2014. The recommended environment is a 64-bit operating system and SQL Server 2008 R2 SP2, Standard, Enterprise, 32/64-bit.

Note: SQL 2012 SP1 Express is installed automatically if no other version of SQL Server is installed on the computer where InTouch HMI 2014 will be installed.

SQL Server Notes Common to All Wonderware Products

Install Archestra License Manager

SQL Server Rights Requirements

SQL Server 2008 does not automatically create the BUILTINAdministrators role delivered in SQL Server 2005. Because of this change to SQL Server, the Wonderware Application Server 2014 (v4.0) 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 BUILTINAdministrator rights. The aaAdministrators group must be present and enabled. If you accidentally delete the aaAdministrators group from the Windows operating system, you can run either of two options to restore it:

  • Run the Change Network Utility from the Windows Start menu.
  • Run the aaConfig SQL Utility from the Windows Start menu.

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

Alarm Client and Trend Client Prerequisites

The Trend Client is compatible with the following Wonderware products:

  • Wonderware InTouch HMI 10.1, 10.1 SP2, 10.2, 10.5, 10.6, and 11.0
  • Wonderware Application Server 3.1, 3.1 SP1, 3.2, 3.5, 3.6, and 4.0
  • Wonderware Historian 9.0, 10.0, 10.5, and 11.5
  • Wonderware Historian Client 10.0 SP1/SP2, 10.1, 10.2, and 10.5
  • ActiveFactory 9.2
  • QI Analyst 8.0 SP2

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.

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 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 http://technet.microsoft.com/en-us/l.../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 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 supported by Wonderware InTouch Access Anywhere include the following:

Browsers Tested with InTouch WindowViewer

  • Internet Explorer 11
  • Internet Explorer 10
  • Firefox 22
  • Safari 7
  • Chrome 28
  • Opera 15

Functionally Compatible Browsers

Wonderware Archestra License Manager

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

  • Firefox 4-21
  • Safari 5, 6
  • Chrome 11-27
  • Opera 11-14

You are strongly recommended 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 (v11.0) Component Compatibility

In a single-node environment, if you need to combine multiple components delivered within Wonderware System Platform 2014, all components need to be at the versions delivered in Wonderware System Platform 2014.
In a node-to-node environment, components are compatible between the current licensed version and one licensed version back.

The following table lists Wonderware component products and their compatibility with InTouch HMI 2014 (v11.0).

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.

Detailed Steps

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 commence the installation and to 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 installing a single product—InTouch HMI—click the product-based selection as your installation type
  5. Choose the components you want to install.
    1. 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.
    2. If you choose InTouch Development and Run Time, the following will be installed:
      • All items listed under step a in these instructions.
      • Application Server Bootstrap, IDE, Galaxy Repository, SQL Server 2012 Express with SSMSE, and Application Server documentation
      • InTouch sample applications
  6. When the installation prompts you to verify your selection, you have the opportunity to customize your installation.
    1. If you choose InTouch Run Time Only, you can add the following components:
      • InTouch sample applications
      • InTouch 16 Pen Trend Supplementary Component:
    2. If you chose InTouch Development and Run Time, you can add the following components:
      • InTouch 16 pen trend
      • InTouch Access Anywhere
  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 another language.
  8. Follow the subsequent installation steps to:
    1. Accept the End User License Agreement.
    2. Create a new ArchestrA user account, or specify an existing account.
    3. Install any prerequisite software components not yet installed on the computer.
  9. The installation proceeds to completion. You must restart the computer after completing the installation.

Installing Your Invensys Product License

Wonderware enforces the use of its products with a software license. After you install a Wonderware product, you must install a single license file, ARCHESTRA.LIC, which contains your customer information, product data, and software features. Until you apply your Wonderware 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 is included as an Invensys component when you install the InTouch HMI.

To install your Wonderware product license

  1. 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.
  2. Click File, and then Install License File. The Choose a License File to Install dialog box appears.
  3. Browse the installation DVD, select the ARCHESTRA.LIC file, and click Open.
  4. The Destination Computer for Installation dialog box appears. Type the domain and computer names.

  5. The Invensys License Manager copies the ARCHESTRA.LIC file to the C:Program FilesCommon FilesArchestrALicense folder on the selected computer.

Antivirus Software Exclusions

After installing Wonderware InTouch HMI Version 11.0, configure your antivirus software to avoid scanning archive files.

Antivirus software should not scan files in the following ArchestrA folders for 32-bit operating systems:

  • C:Program FilesArchestrA
  • C:Program FilesCommon filesArchestrA
  • C:Program FilesFactorySuite (The FactorySuite directory may not exist in newer installations)
  • C:Program FilesWonderware
  • C:InSQLData
  • C:Documents and SettingsAll UsersApplication DataArchestrA
  • C:HistorianData

For 64-bit operating systems, the exclusion must reflect the (x86) program files directory instead:

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

From Application Server Platform objects:

  • History Store Forward directory: (if not default)

From Application Server Engine objects:

  • Checkpoint directory location (if not default)

<InTouch Application folder path> including:
C:Documents and SettingsAll UsersApplication DataArchestrA

<SMCLoggerStoragefilepath>. The default is:
C:Documents and SettingsAll UsersApplication DataArchestrALogFiles

SQL Server database files of type:

  • .mdf
  • .ldf

Note: Ensure that the subfolders of the listed directories are also excluded. Specify folder names accordingly if you are using a 64-bit operating system. For example, the program file's root directory in a 64-bit operating system is C:Program Files (x86)... and the application data root directory in a 32-bit operating system is C:ProgramData...

Modifying, Repairing, or Removing the InTouch HMI

Install Archestra License Manager Duties And Responsibilities

To modify, repair, or remove an installation

  1. Insert the installation DVD into the computer’s DVD drive.
  2. Click the Programs and Features option in Windows Control Panel. 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 the installation.

Install Archestra License Manager Duties

Note: The name of the Uninstall/Change button varies depending on the Windows operating system installed on your computer.

Upgrading to Version 11.0 from an Earlier Version of the InTouch HMI

Upgrading InTouch HMI installs Version 11.0 on a computer that has a previous version currently installed. An upgrade removes or uninstalls the previous version of InTouch HMI and installs Version 11.0.

Wonderware License Cost

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

  • Version 10.0 SP2
  • Version 10.1 (All service packs and patches)
    • 10.1
    • 10.1 SP2
    • 10.1 SP2 P01
    • 10.1 SP3
    • 10.1 SP3 P01
  • Version 10.6

You can only upgrade Wonderware System Platform products that are already installed and you will not be able to install new products within the Wonderware System Platform that have an upgrade process. The installed components that need to be upgraded are selected and disabled. You can neither clear these check boxes nor select more components during the upgrade.

To upgrade from a previous version of the InTouch HMI

  1. Insert the DVD into your DVD-ROM drive. Run setup.exe to start the set-up program.
    The upgrade feature dialog box appears.
  2. Follow the prompts to complete the upgrade.

Migrating Applications to Wonderware InTouch HMI Version 11.0

Migration converts applications created with earlier versions of InTouch HMI to the current version. You can migrate applications to version 11.0 that were developed with the following versions of InTouch HMI:

  • Version 7.11 P07
  • Version 8.0 SP2 P04
  • Version 9.0 P03
  • Version 9.5 SP1
  • Version 10.0 SP2
  • Version 10.1 (All service packs and patches)
    • 10.1
    • 10.1 SP2
    • 10.1 SP2 P01
    • 10.1 SP3
    • 10.1 SP3 P01
  • Version 10.6

Licensing

For General System Platform 2014 Licensing click HERE

Related Videos