System Platform 2012 R2

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

Last revision: 11/13/2012

Contents

About This Readme

This document contains important information about the ArchestrA® System Platform 2012 R2. This document also provides links to information about the component products you can install in ArchestrA System Platform 2012 R2.

Component-Specific Product Readme Files

Review each of the individual product Readme files for details regarding known and resolved issues. Insert the ArchestrA System Platform installation DVD to access the following readme files.

Previous Product Release Readme Files

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

Important: User Account Control (UAC)

For Windows Vista and newer operating systems, you must disable User Account Control (UAC) before installing ArchestrA System Platform 2012 R2 and before performing Configurator operations. Installing ArchestrA System Platform 2012 R2 with UAC enabled can result in functional issues from which there is no recovery other than to disable UAC, uninstall, and re-install the software.

UAC also must be disabled on IDE and GR nodes. ArchestrA System Platform 2012 R2 supports UAC-enabled operations on run-time nodes.

For more pre-installation guidelines and recommendations, see Before installing ArchestrA System Platform 2012 R2

About This Release

ArchestrA System Platform 2012 R2 delivers extensive browsing and data access enhancements from Wonderware Application Server, InTouch HMI logon security, alarm query redundancy, and memory management enhancements, Historian redundancy and performance enhancements, and enhanced operating system and SQL Server support. The following sections describe in greater detail the new features and enhancements delivered with this release.

ArchestrA System Platform 2012 R2 integrates the core products:

  • Wonderware InTouch HMI 2012 R2 (v10.6)
  • Wonderware Application Server 2012 R2 (v3.6)
  • Wonderware Historian Server 2012 R2 (v11.0)
  • Wonderware Historian Client 2012 R2 (v10.1)
  • Wonderware Information Server 2012 R2 (v5.0)

New Features - Wonderware InTouch HMI 2012 R2 (v10.6)

Enhanced Support for SQL Server

InTouch HMI 2012 R2 (v10.6) adds support for SQL Server 2008 R2 SP1 (32/64-bit), SQL Server Express 2008 R2 with SSME (32-bit), SQL Server 2012 (32/64-bit), and SQL Server Express 2012 (32-bit).

Enhanced Logon Security

The LogonCurrentUser function now supports ArchestrA OS user and ArchestrA OS group security in addition to InTouch security.

Enhanced Memory Management

You can cache into memory the ArchestrA symbols called by the ShowGraphic function or by ShowSymbol animation for improved run-time performance.

Alarm Provider Hot Backup

Alarm Hot Backup Manager can use InTouch, Galaxy, or Galaxy_ as alarm providers when configuring an alarm hot backup pair.

Enhanced Tag Browser access

You can select InTouch tags directly from the Galaxy Browser when working within the animation editor or the script editor.

InTouch Documentation

The InTouch documentation PDF library and online help have been updated with all content accumulated in the InTouch HMI Addendum since InTouch HMI version 10.0.

New Features - Wonderware Application Server 2012 R2 (v3.6)

Communication Across Multiple Galaxies

You can now communicate across multiple galaxies, including browsing a remote galaxy repository (GR) and accessing the run-time data of a remote galaxy, once paired with a local galaxy.

ArchestrA Services Implemented as IDE Extensions

ArchestrA System Platform 2012 R2 introduces the ArchestrA Service Bus (ASB), comprised of individual ArchestrA Services, which enables significantly enhanced levels of information exchange, such as multi-galaxy communication. ArchestrA Services are built upon a service-oriented architecture, which incorporates such general principles as standards-based reusability, discoverability, loose coupling, and modularity.

Enhanced Support for the Historian

Wonderware Application Server 3.6 incorporates enhanced support for the Historian, including:

  • Support for partner Historians in a redundant configuration
  • Start historizing data without a connection to the Wonderware Historian
  • Improved performance when historizing late data
  • Support for Historian scalability and data acquisition

Technology Updates

Wonderware Application Server supports 64-bit SQL Server, newer versions of SQL Server, Windows operating systems, .NET Framework, virtualization technologies, and security enhancments.

New Features - Wonderware Historian Server 2012 R2 (v11.0)

High Availability (Redundant Historian)

Support for partner Historians in a redundant (hot backup) configuration.

AppEngines support sending data to either Historian in a pair without requiring separate configurations for each.

Historian Client supports retrieving data from the Historian pairs.

Increased Tier-2 Tag Counts

Supports 500,000 tier-2 tags at a throughput of 125,000 values/second.

New version of the Historian SDK

Support for new historian functionality.

Support for querying summary tags.

Improved Late Data Support

Support sending late data or buffered data to the Historian with the same performance as “real-time” data

Retrieval Based Licensing

The Historian stores tags regardless of the license count.

The Historian prevents data retrieval for more tags than are licensed.

Improved Hierarchical Name Support

Hierarchical namespace support for replicated tagnames.

Application Server Integration Improvements

Support for AppEngine updates to the TrendHi and TrendLo attributes into the Historian Runtime database without requiring a redeploy.

Microsoft Platform Support

Native SQL Server 64-bit support.

New Features - Wonderware Historian Client 2012 R2 (v10.1)

Support for a Partner Historian

If a partner server is configured for a Wonderware Historian, clients will automatically switch servers if the primary server is unavailable.

Technology Updates

The Wonderware Historian Clients support newer versions of operating systems.

New Features - Wonderware Information Server 2012 R2 (v5.0)

New Information Model

The Information Model retrieves and relates data from different sources, such as the Wonderware Historian, the alarm database, and the Wonderware MES database.

New OverView Client

The OverView client is a downloadable application that allows you to navigate data from the Information Model using grids and trends.

Technology Updates

The Wonderware Information Server supports newer versions of SQL Server and operating systems.

Updated Look and Feel

The Wonderware Information Server portal has been updated with new fonts and colors.

System Requirements

This section describes the hardware and software system requirements for installing ArchestrA System Platform 2012 R2 products.

Hardware Requirements

Hardware Requirements by Installation Size

The following table lists the hardware requirements for the ArchestrA System Platform 2012 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.

  CPU
(GHz)
Cores
(Minimum)
RAM
(GB)
Storage
(GB)
(sufficient for 1 wk @ max
frequency)
Monitor
Resolution
Network
(MBPS)
Compact Installation
(1 - 500 I/O per Node)
2.8 1 1 30 1024x768 100
Small Installation
(1 - 5K I/O per Node)
2.8 1 1 30 1024x768 100
Medium Installation
(5k - 50k I/O per Node)
2.8 4 8 500 1280x1024 1000
Large Installation
(50k - 400k I/O per Node)
2.8 8 16 1000 1280x1024 1000

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 2012 R2 (v3.6). If you intend to install ArchestrA System Platform 2012 R2 on a computer running Windows 7, Windows Server 2008 R2, or supported SQL Server versions, see the following Microsoft Web sites for hardware requirements:
  • Wonderware Historian 2012 R2 is not supported on cluster hardware.
  • Do not use the Wonderware Historian computer as a domain controller, mail server, or an Internet server.
  • If you are running the Wonderware Historian on a virtual server, the Historian must have adequate CPU, network, memory, and disk I/O resources at all times. Overloading the virtual server leads to unpredictable behavior.
  • See the following sections for hardware requirements specific to Wonderware Historian Client, Wonderware Information Server, and for auxiliary hardware requirements.

Hardware Requirements: Wonderware Historian Client

The following table lists the hardware requirements for installing Wonderware Historian Client 2012 R2 (v10.1).

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

Hardware Requirements: Wonderware Information Server

The following are the hardware requirements and recommendations for Wonderware Information Server 2012 R2 (v5.0).

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

Hardware Requirements: Auxiliary

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

Operating System, .NET Framework, and Virtualization Requirements

Summary of Requirements for ArchestrA System Platform 2012 R2

The following table lists the operating system, .NET Framework, and virtualization requirements for ArchestrA System Platform 2012 R2.

Note: Only the Windows, SQL Server, and service packs shown in the following tables are supported for ArchestrA System Platform 2012 R2 components.

  Client
Windows OS
Server
Windows OS
.NET
Framework
Virtualization
XP SP3
Professional
(32-bit)
Vista SP2
Business,
Enterprise,
Ultimate
(32/64-bit)
7 SP1
Embedded
(32-bit only)
7 SP1
Professional,
Enterprise,
Ultimate
(32/64-bit)
2003 SP2
Standard,
Enterprise
(32-bit)
2003 R2 SP2
Standard,
Enterprise
(32-bit)
2008 SP2
Standard,
Enterprise
(32/64-bit)
2008 R2 SP1
Standard,
Enterprise
(64-bit)
4.0 Hyper-V
(Based on
Supported
OS version)
VMWare 5.0
(Basic
virtualization;
no HA/DR)
VMWare
vSphere 5
InTouch 2012 R2 (v 10.6):

Y Y Y Y Y Y Y Y Y Y Y Y
Application Server 2012 R2 (v3.6): Y Y N Y Y Y Y Y Y Y Y Y
Historian 2012 R2 (v11.0) Y Y N Y Y Y Y Y Y Y Y Y
Historian Client 2012 R2 (v10.1) Y Y N Y Y Y Y Y Y Y Y Y
Information Server 2012 R2 (v5.0):                        
Portal N N N Y Y Y Y Y Y Y Y Y
Client Y Y N Y Y Y Y Y Y Y Y Y
                         
Compact Installation (1-500 I/O per node) Y N Y N Y Y N N Y N N N
Small Installation (1-5,000 I/O per node) Y Y N Y Y Y Y Y Y Y Y Y
Medium Installation (5k-50k I/O per node) Y Y N Y Y Y Y Y Y Y Y Y
Large Installation (50k-400k I/O per node) Y N N N Y Y N Y Y Y Y Y
Perferred Environment (64-bit OS and SQL Server)       R       R        

 

Supported Y
Supported and Recommended R
Not Supported N
Not Applicable

Notes:

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

Operating System Notes: Common for Wonderware Products

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

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

Configuring Remote Alarm Retrieval Queries When Running Windows Vista, Windows 7, 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 Vista, Windows 7, and Windows Server 2008 R2.

When InTouch WindowViewer is started and generates alarms from an interactive Windows Vista, Windows 7, or Windows Server 2008 R2 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 Vista, Windows 7, and 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 "nodeabc" below and substituting your IP address noted in the previous step:

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

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

Wonderware InTouch HMI and Alarm DB Logger

In earlier releases 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 operating systems no longer support the /console switch as a means of starting the remote desktop (RDP) client, also known as Session 0 or Terminal Server Console session. In Windows Server 2008 and later operating systems, Session 0 is no longer an interactive session, and is reserved only for Windows services. Windows Server 2008 and later operating systems treat all remote connections as remote RDP sessions regardless of /console, /admin, or any other switches used to make the connection.

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

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

When running Windows Server 2008 and later operating systems, 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. Windows Server 2008 and later operating systems treat all remote connections 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 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-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.

Operating System Notes: Wonderware InTouch HMI 2012 R2 (v10.6)

Following are notes specific to the InTouch HMI 2012 R2 (v10.6) operating system support and requirements.

  • The recommended operating system for a Galaxy Repository is Windows Server 2008 R2 SP1.
  • Microsoft Windows 7 (32-bit or 64-bit) is the recommended operating system to run InTouch HMI client components.
  • Microsoft Windows Server 2008 R2 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.

Wonderware InTouch HMI 2012 R2 (v10.6) with Windows Vista, Windows 7, and Windows Server 2008 R2

  • Windows Vista does not support a dedicated single-node server configuration that runs one or more databases for an InTouch HMI system. 
  • If a computer runs Windows Vista as part of an InTouch HMI system, it cannot be configured to be both an InTouch HMI and ArchestrA alarm provider. The computer running Windows Vista can be either an InTouch HMI or an ArchestrA alarm provider, but not both simultaneously.
  • Wonderware InTouch HMI 10.6 does not support the following functions on these operating systems: WWPoke(), WWExecute(), WWRequest(), ActivateApp() and SendKeys().
  • If Recipe Manager is started using the path Start\Program\Wonderware\InTouch\Recipe, then select Run as Administrator on Windows Vista or later operating systems.
  • The InTouch Extensibility Toolkit might need to be started by right-clicking and selecting Run As Administrator on Windows Vista 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 2012 R2 (v10.6) View Applications and DDE Support

Windows Vista 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 2012 R2 (v10.6) Support for Windows User Account Control

ArchestrA System Platform 2012 R2 with InTouch HMI v10.6 supports User Account Control-enabled operations on run-time nodes. You must disable User Account Control (UAC) before installing ArchestrA System Platform 2012 R2 and before performing Configurator operations. UAC also must be disabled on IDE and GR nodes.

Operating System Notes: Wonderware Application Server

  • Windows Server 2008 R2 SP1 is the recommended operating system for the Galaxy Repository node.
  • Windows 7 SP1 is the recommended operating system for Wonderware Application Server development (IDE) or run-time nodes (Bootstrap).
  • The Bootstrap, IDE, and Galaxy Repository are supported by the following language versions of Microsoft operating systems: English, Japanese, Simplified Chinese, German, and French. The Galaxy Repository is also supported by the English, Japanese, Simplified Chinese, German, and French versions of Microsoft SQL Server 2008 SP3, SQL Server 2008 R2 SP1, and SQL Server 2012.

Wonderware Application Server and DDE Support

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

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

Using Wonderware Application Server with Windows 7 and Windows Server 2008 R2

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

  • The DDESuiteLink Client connection to the local DAServer using DDE does not work with User Account Control enabled. The connection will work when User Account Control is disabled.
  • For toolkits such as the ArchestrA Object Toolkit, GRAccess Toolkit, and MXAccess Toolkit to function properly on Windows 7 and later operating systems, you may need to start the toolkit by right-clicking on the file and then clicking Run As Administrator.
  • Wonderware Application Server may experience performance degradation depending on how certain operating system tuning parameters are configured. For more information, see Tech Note 719, "Optimizing Wonderware Application Server Performance on Windows 7/Server 2008 R2", available for download from Wonderware Developers Network (WDN) Technical Support.

Wonderware Application Server and User Account Control Level

Application Server versions 3.1, 3.1 SP1, 3.1 SP2, 3.1 SP2 Patch 01, 3.1 SP3, 3.2, 3.5, and 3.6 support User Account Control-enabled run-time operations without elevated privileges.

On computers where the IDE or the GR is installed, User Account Control must be disabled. For more information about User Account Control support, see Wonderware InTouch HMI 2012 R2 (v10.6) Support for Windows User Account Control.

Operating System Notes: Wonderware Historian Server

Scenarios involving remote node communication fail if the Historian node is using the Windows Vista, Windows 7, Windows Server 2008, or Windows Server 2008 R2 operating system.

For example:

    1. When you log in as a local administrator on a computer and try to add a remote Wonderware Historian node (a second node with the Wonderware Historian installed) using the network account from the Management Console, the status of the remote Historian node is not reflected correctly.
    2. Test the connection from a Historian node using the operating system to a remote tier-2 historian. The following error message is shown: "Test Connection to replication server () failed: cannot connect to Tier-1 replication service (error 0x80004005: Unspecified error)"
    3. Replication to the remote tier-2 historian fails.
    4. Although a remote IDAS service starts successfully, errors and warnings stating "Failed to get IDAS configuration version..." and "Unable to start data acquisition" are logged. This problem occurs if the ArchestrA user account is a local user. If the ArchestrA user account is a domain user, then this problem does not occur.

Workaround:

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

Operating System Notes: Wonderware Historian Client

When the Wonderware Historian Client application is running on Microsoft Windows Vista, Windows Server 2008, and Windows 7 operating systems, User Account Control can be enabled and running as non-administrator.

Operating System Notes: Wonderware Information Server

The MultiViews feature is not supported on the 64-bit versions of Windows 7 or Windows Server 2008 R2 SP1.

.NET Framework Requirements and Compatibility

IMPORTANT: We strongly recommended that prior to upgrading your existing applications to ArchestrA System Platform 2012 R2, that you back up your applications, become familiar with the changes introduced by Microsoft in .NET 4.0, and that you review your .NET scripts and .NET controls for any required changes. After upgrading to ArchestrA System Platform 2012 R2, you should perform application testing on application scripts and on script libraries used by the application to ensure they continue to function properly under .NET 4.0. We also recommend you test the upgrade in a staging system prior to upgrading your production system.

ArchestrA System Platform 2012 R2 leverages Microsoft .NET Framework 4.0. The ArchestrA System Platform installation program will install .NET 4.0 if it is not already present in your system. .NET 4.0 can coexist with previous versions of .NET Framework. On nodes where SQL Server is installed, .NET 3.5 is also installed by ArchestrA System Platform. In this scenario, ArchestrA System Platform 2012 R2 will use .NET 4.0. Other applications you may have on the same machine with dependencies on .NET 3.5 will access .NET 3.5.

All user-supplied .NET code that runs in the context of InTouch HMI and Application Server will now run under the .NET Framework 4.0. Although .NET Framework 4.0 is highly compatible with applications that are built with earlier .NET Framework versions, Microsoft has introduced changes in .NET 4 to improve security, standards compliance, correctness, reliability, and performance that may require changes to .NET scripts you may have created with ArchestrA 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 3.5.

In ArchestrA scripting, some .Net codes could fail if not using proper text encoding, and could cause a script to exit without completion. The UTF8Encoder is the default BinaryStream decoder in .Net 4.0. 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.0 see the following Microsoft resources:

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

Virtualization Support

ArchestrA System Platform 2012 R2 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

SQL Server Requirements for All Wonderware Components

The following table details the SQL Server requirements for ArchestrA System Platform 2012 R2 components. The recommended environment is a 64-bit operating system and SQL Server 2008 R2 SP1, Standard, Enterprise, 32/64-bit. For more information, see SQL Server Installation Notes.

  2008 SP3 Express-SSMSE (32-bit) 2008 SP3 Standard, Enterprise (32-bit Only) 2008 R2 SP1 Express-SSMSE (32-bit) 2008 R2 SP1 Standard, Enterprise (32/64 bit) 2012 Express-SSMSE (32-bit) 2012 Standard, Enterprise (32/64 bit)
InTouch 2012 R2 (v 10.6)

S Y S Y S Y
Application Server 2012 R2 (v3.6) S Y S Y S Y
Historian 2012 R2 (v11.0) S Y S Y S Y
Historian Client 2012 R2 (v10.1)            
Information Server Portal 2012 R2 (v5.0) S Y S Y S Y
Information Server Clients 2012 R2 (v5.0)            
             
Compact Installation (1-500 I/O per node) Y N Y N Y N
Small Installation (1-5,000 I/O per node) N Y N R N Y
Medium Installation (5k-50k I/O per node) N Y N R N Y
Large Installation (50k-400k I/O per node) N N N R N Y

 

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

 

SQL Server Notes: Common for All Wonderware Products

SQL Server Rights Requirements

SQL Server 2008 does not automatically create the BUILTIN\Administrators role delivered in SQL Server 2005. Because of this change to SQL Server, the Wonderware Application Server 2012 R2 (v3.6) installation process will create the necessary operating system user group (aaAdministrators) as well as the necessary SQL Server role. This automated process will provide the rights required to allow operations within the Galaxy Repository without the need for blanket BUILTIN\Administrator rights. The aaAdministrators group must be present and enabled. If you accidentally delete the aaAdministrators group from the Windows operating system, you can run either of two options to restore it:

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

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

SQL Server Notes: Wonderware Application Server

  • If multiple versions of SQL Server are installed, the one utilized as the Galaxy Repository must be the default instance.
  • The Galaxy Repository locks the SQL Server maximum memory usage to 65% of the computer's physical memory.
  • TCP/IP must be enabled on the computer hosting a SQL Server 2008 database. The TCP/IP protocol setting can be verified from the SQL Server Network Configuration under SQL Server Configuration Manager.
  • To use the Alarm DB Logger with SQL Server Express, you need to change the default authentication mode from Windows-based to Mixed Mode.
  • When upgrading SQL Server on the Galaxy Repository node, back up the Galaxy before starting the upgrade. Upload any run-time changes for critical objects. You cannot upload any run-time changes after you upgrade the system. For more information, see the Wonderware Application Server upgrade notes. Also see the Wonderware Application Server Installation online Help.

SQL Server Notes: Wonderware Information Server

In addition to the SQL Server requirements specified in Summary of Requirements for ArchestrA System Platform 2012 R2, note the following SQL Server considerations for the Wonderware Information Server:

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

SQL Server Notes: Wonderware Historian Server

In addition to the SQL Server requirements specified in Summary of Requirements for ArchestrA System Platform 2012 R2, note the following SQL Server considerations for the Wonderware Historian Server:

  • The MSSQL Server user account is not supported for the SQL Server 2012 Service. Instead, configure SQL Server to run as the local system or Network Service account.

Third-Party Application Prerequisites

Third-Party Application Prerequisites: Wonderware Historian Client

  • If the supported version of the .NET Framework is not installed on your computer, then the Wonderware Historian Client software installation automatically installs it for you.
  • Microsoft Office is an optional prerequisite. If you install Office after installing Wonderware Historian Client, then the Historian Client add-ins do not appear in the list of available add-ins in Office. Run the Wonderware Historian Client installation program and repair the installation to get the add-ins loaded.
  • When you install Office 2010 as a custom install and select only the Microsoft Office and Excel features, you must also select Office Shared Features and Office Tools so that the Historian add-ins for Workbook or Report can be loaded.

Third-Party Application Prerequisites: Wonderware Information Server

The following table describes third-party prerequisites for Wonderware Information Server.

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

Wonderware Information Server supports IPv4 only.

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

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

Windows SharePoint Services: To use the MultiView feature, you must install and configure Windows SharePoint Services WSS 3.0 before configuring the MultiViews feature in Wonderware Information Server. To use Windows SharePoint 3.0, you must install Microsoft .NET Framework 3.5 SP1 or later. Also install any WSS Language Pack for languages you want Wonderware Information Server to support. The MultiView feature is only supported on 32-bit operating systems.
SQL Server Reporting Services: To use the ArchestrA Reporting feature, you must install and configure SQL Server Reporting Services and set up a reporting database before configuring the ArchestrA Reports feature in Wonderware Information Server. The versions of SQL Server and SQL Server Reporting Services used must match (for example, both 2008).
WebDAV Feature: For the Process Graphics feature to work, you must install WebDAV before configuring the Wonderware Information Server. You can download WebDAV from the following links:

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

Wonderware Component Compatibility

In a single-node environment, if you need to combine multiple components delivered within ArchestrA System Platform 2012 R2, all the components need to be the version delivered in ArchestrA System Platform 2012 R2.

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

Component Compatibility: Wonderware InTouch HMI 2012 R2 (v10.6)

Wonderware InTouch HMI 2012 R2 (v10.6) is compatible and can co-exist with the following components. Compatibility means that the products can communicate with each other over the network. Co-existence means that the products can be installed on the same computer.

Component Version Compatibility Co-existence
Wonderware InTouch CE 10.1 N N
Wonderware Application Server 3.6 Y Y
3.1, 3.1 SP1,
3.1 SP2 P01,
3.1 SP3, 3.2, 3.5, 3.5 P01
Y N
Wonderware Historian Server 11.0 Y Y
Wonderware Historian Client 10.0 SP1, 10.0 SP2 Y N
10.1 Y Y
Wonderware Information Server 4.0, 4.0 SP1, 4.5 Y N
5.0 Y Y
Wonderware InControl™ 7.11 SP2 P01 Y Y
Wonderware Manufacturing Execution System 4.0, 4.0 SP1 N N
4.5 Y Y
Wonderware Manufacturing Execution Module 1.0 Y Y
Wonderware InBatch™ 9.5, 9.5 SP1 N N
9.6 Y Y
Wonderware QI Analyst™ 8.0 SP2 Y Y
Wonderware SCADAlarm™ 6.0 SP2 P01 Y Y
ArchestrA Workflow™ 1.5, 1.6 Y Y
Wonderware Intelligence 1.5, 1.5.1 Y Y
Supported Y
Not Supported 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.

Product Compatibility: Wonderware Application Server 2012 R2 (v3.6)

Wonderware Application Server 2012 R2 (v3.6) is compatible and can co-exist with the following products. Compatibility means that the products can communicate with each other over the network. Co-existence means that the products can be installed on the same computer.

Component Version Compatibility Co-existence
Wonderware InTouch HMI 10.6 Y Y
10.1, 10.1 SP2 P01,
10.1 SP3, 10.2, 10.5, 10.5 P01
Y N
Wonderware InTouch CE 10.1 N N
Wonderware Historian Server 11.0 Y Y
10.0, 10.0 SP1 N N
Wonderware Historian Client 10.1 Y Y
10.0 SP1, 10.0 SP2 Y N
Wonderware Information Server 5.0 Y Y
4.0, 4.0 SP1, 4.5 Y N
Wonderware InControl™ 7.11 SP2 P01 Y Y
Wonderware Manufacturing Execution System 4.5 Y Y
4.0, 4.0 SP1 N N
Wonderware Manufacturing Execution Module 1.0 Y Y
Wonderware InBatch™ 9.5, 9.5 SP1 N N
9.6 Y Y
Wonderware QI Analyst™ 8.0 SP2 Y Y
Wonderware SCADAlarm™ 6.0 SP2 P01 Y Y
ArchestrA Workflow™ 1.5, 1.6 Y Y
Wonderware Intelligence 1.5, 1.5.1 Y Y
Supported Y
Not Supported N

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

Alarm Client and Trend Client Prerequisites

The Alarm Client and Trend Client is compatible with the following Wonderware products:

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

Product Compatibility: Wonderware Historian Server 2012 (version 11.0)

Wonderware Historian 2012 R2 (v11.0) is compatible and can co-exist with the following products. Compatibility means that the products can communicate with each other over the network. Co-existence means that the products can be installed on the same computer.

Component Version Compatibility Co-existence
Wonderware InTouch HMI 10.6 Y Y
10.5 Y N
Wonderware InTouch CE 10.1 N N
Wonderware Application Server 3.6 Y Y
3.5 Y N
Wonderware Historian Client 10.1 Y Y
10.0 SP1, 10.0 SP2 Y N
Wonderware Information Server 5.0 Y Y
4.5 Y N
Wonderware InControl™ 7.11 SP2 P01 Y Y
Wonderware Manufacturing Execution System 4.5 Y Y
4.0, 4.0 SP1 N N
Wonderware Manufacturing Execution Module 1.0 Y Y
Wonderware InBatch™ 9.5, 9.5 SP1 N N
9.6 Y Y
Wonderware QI Analyst™ 8.0 SP2 Y Y
Wonderware SCADAlarm™ 6.0 SP2 P01 Y Y
ArchestrA Workflow™ 1.5, 1.6 Y Y
Wonderware Intelligence 1.5, 1.5.1 Y Y
Supported Y
Not Supported N

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

Product Compatibility: Wonderware Historian Client 2012 R2 (v10.1)

Wonderware Historian Client 2012 R2 (v10.1) is compatible and can co-exist with the following products. Compatibility means that the products can communicate with each other over the network. Co-existence means that the products can be installed on the same computer.

Component Version Compatibility Co-existence
Wonderware InTouch HMI 10.6 Y Y
10.5 Y N
Wonderware InTouch CE 10.1 N N
Wonderware Application Server 3.6 Y Y
3.5 Y N
Wonderware Historian Server 11.0 Y Y
10.0 SP1 Y N
Wonderware Information Server 5.0 Y Y
4.5 Y N
Wonderware InControl™ 7.11 SP2 P01 Y Y
Wonderware Manufacturing Execution System 4.0, 4.0 SP1 N N
4.5 Y Y
Wonderware Manufacturing Execution Module 1.0 Y Y
Wonderware InBatch™ 9.6 Y Y
9.5, 9.5 SP1 N N
Wonderware QI Analyst™ 8.0 SP2 N N
Wonderware SCADAlarm™ 6.0 SP2 P01 Y Y
ArchestrA Workflow™ 1.5, 1.6 Y Y
Wonderware Intelligence 1.5, 1.5.1 N/A Y
Supported Y
Not Supported N

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

Product Compatibility: Wonderware Information Server 2012 R2 (v5.0)

Wonderware Information Server 2012 R2 (v5.0) can be used with the following Wonderware products. Compatibility means that the products can communicate with each other over the network. Co-existence means that the products can be installed on the same computer.

Component Version Compatibility Co-existence
Wonderware InTouch HMI 10.6 Y Y
10.5 Y N
Wonderware Application Server 3.6 Y Y
3.5 Y N
Wonderware Historian Server 11.0 Y Y
10.0, 10.0 SP1 Y N
Wonderware Historian Client 10.1 Y Y
10.0, 10.0 SP1, 10.0 SP2 Y N
Wonderware InControl™ 7.11 SP2 P01 Y Y
Wonderware Manufacturing Execution System 4.0, 4.0 SP1 N N
4.5 Y Y
Wonderware Manufacturing Execution Module 1.0 Y Y
Wonderware InBatch™ 9.6 Y Y
9.5, 9.5 SP1 N N
Wonderware QI Analyst™ 8.0 SP2 Y Y
Wonderware SCADAlarm™ 6.0 SP2 P01 Y Y
ArchestrA Workflow™ 1.5, 1.6 Y Y
Wonderware Intelligence 1.5, 1.5.1 N/A Y

 

Supported Y
Not Supported N

 

Notes:

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

Other Wonderware Products

The product compatibility information contained in this ArchestrA System Platform 2012 R2 Readme supersedes information contained in other product Readme files delivered on the ArchestrA System Platform 2012 R2 DVD. In any instance where conflicting information occurs, this Readme is the more up-to-date and should be taken as correct. The Wonderware InTouch HMI 2012 R2 (v10.6) Readme duplicates some of the same information contained in this Readme, but focused on InTouch HMI.

Installation Notes

ArchestrA System Platform 2012 R2 Installation

For detailed instructions on installing any of the products that make up the ArchestrA System Platform 2012 R2, see the ArchestrA System Platform Installation Guide (ASP_Install_Guide.chm). That guide supersedes the separate installation guides for the individual products.

Before installing ArchestrA System Platform 2012 R2

  • For Windows Vista and new operating systems, you must disable User Account Control (UAC) before installing ArchestrA System Platform 2012 R2 and before performing Configurator operations. Installing ArchestrA System Platform 2012 R2 with UAC enabled can result in issues from which there is no recovery other than to uninstall and re-install the software with UAC disabled.
  • It is strongly recommended that you install a compatible version of SQL Server before starting the product installation if you plan to use any of the ArchestrA System Platform components. The exception is Historian Client, which has no SQL Server dependency.
  • If you upgrade existing nodes, ensure you back up any relevant application configuration files or databases.
  • If you combine multiple products delivered within ArchestrA System Platform 2012 R2 on a single node, all the products are required to be the version delivered in ArchestrA System Platform 2012 R2.
  • Installing ArchestrA System Platform 2012 R2 on a computer used as a domain controller is not supported. For more information, see http://technet.microsoft.com/library/Cc966456.
  • Installing Wonderware Application Server 3.6 automatically undeploys any platform that is currently deployed in the node that is being updated. Changes to the WinPlatform object and other components require any deployed platforms to be redeployed.
  • Customers installing any of the products contained within the ArchestrA System Platform 2012 R2 release on English versions of the Windows XP and/or Windows 2003 Operation Systems must install the "East Asian Language" files to read the Japanese and Chinese text of the End User License Agreement (EULA).

For detailed installation instructions in English, see the ArchestrA System Platform Installation Guide (ASP_Install_Guide.pdf) or ArchestrA System Platform Installation Help (ASP_Install_Guide.chm).
The information provided in this Readme file supersedes the InTouch HMI Installation Help (Install-InTouch.chm) for the French, German, Japanese, and Simplified Chinese languages.

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.

Guidelines for Installing and Using the Multi-Galaxy Communication Functionality

  • Using the multi-galaxy communication functionality delivered in ArchestrA System Platform 2012 R2 has specific galaxy naming requirements. For more information, recommendations, and galaxy naming steps, see Upgrade Considerations for Multi-Galaxy Communication.
  • Under different circumstances, the multi-galaxy communication functionality generates a varying amounts of intra-galaxy network traffic. We do not recommend using the multi-galaxy communication functionality in a bandwidth-capped environment. You should measure network bandwidth to establish a baseline prior to enabling and using multi-galaxy communication. For more information, see CR L00123682
  • For detailed information about configuring, using, and troubleshooting the multi-galaxy communication functionality, see the Wonderware Application Server User Guide (IDE.pdf), Chapter 9, "Working with Multiple Galaxies", or the Application Server online help.
  • Also see ArchestrA Service Bus and Multi-Galaxy Communication Issues.

SQL Server Installation Notes

Application Server 3.6, InTouch HMI 10.6, Historian 11.0, and Wonderware Information Server Portal 5.0, all delivered as part of ArchestrA System Platform 2012 R2, support the SQL Server versions detailed in SQL Server Requirements, earlier in this readme. If you expect Wonderware Information Server to coexist, either on initial or subsequent installations, with InTouch HMI, Application Server, or the Historian Server, we strongly recommend that you install SQL Server prior to installing ArchestrA System Platform 2012 R2.

SQL Server Installation Prerequisites

The ArchestrA System Platform installer will install all prerequisites except the SQL Server requirement for installing the Galaxy Repository (GR) and the Historian Server.

If you select the GR or the Historian Server for installation, and if the supported version of SQL Server is not already installed, you must exit the installation program, install the supported SQL Server version, then resume the installation.

We recommend that you install and configure the supported SQL Server version before you begin the ArchestrA System Platform installation program.

For InTouch HMI-only installations, the ArchestrA System Platform installer will automatically install SQL Server 2008 Express provided the following conditions are met:

  • No version of SQL Server is installed on the system.
  • You may select only InTouch Development and Runtime during the ArchestrA System Platform installation. You may not select any Wonderware Application Server components. When you select InTouch Development and Runtime, a Galaxy Repository will be installed.
  • If you select the InTouch Development and Runtime feature for installation or upgrade, and your system was installed with the earlier version of SQL Server 2008 Express installed as part of ArchestrA System Platform 2012, the following conditions apply:
    • The ArchestrA System Platform 2012 R2 installation Product-specific Prerequisites dialog states SQL Server 2008(x86) SP3 Std/Ent (SQL Express 2008 R2 SSME for InTouch Dev only) is a prerequisite for the Galaxy Repository feature, but the Install Prerequisites button is disabled.
    • To resolve this condition, you must exit the installation program, install SQL Server 2008 R2 SP1 32-bit Express-SSME, then resume the installation.
    • To do this, you can run the SQL Server 2008 Express installation from the following ArchestrA System PLatform 2012 R2 DVD media folder path:
      <ArchestrA System Platform 2012 R2 DVD>:\InstallFiles\Redist\SQL2K8R2SSMSE\SQLEXPRWT_x86_ENU.exe

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. See L00116459 under Installation Issues for more information.
  • SQL Server Configuration Rights: While installing ArchestrA 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 ArchestrA System Platform installation process will attempt to adjust it if it has the appropriate rights to configure SQL Server.
  • Restoring a CAB: You cannot restore a Galaxy .cab file backed up in SQL Server 2012 or SQL Server 2008 to a node with an earlier version of SQL Server. For example, you cannot restore a Galaxy .cab file backed up in SQL Server 2012 to a node with SQL Server 2008. For example, you cannot restore a Galaxy .cab file backed up on SQL Server 2008 to a node with SQL Server 2005. SQL Server database backups from SQL Server 2005 forward are not backward-compatible. Attempting such a restore 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 2005. You can migrate to SQL Server 2008 from SQL Server versions 2005 or 2000. You cannot migrate directly from SQL Server 2000 to SQL Server 2012. Such a migration requires an intermediate step. For more information and helpful procedures, see the following Microsoft references:

Considerations for SQL Server Express

  • In combination with Wonderware Application Server, SQL Server Express is not supported for complete Application Server Galaxy development.
  • If you plan to modify an InTouch HMI installation which has SQL Server 2008 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 2008 Express with Wonderware Information Server 2012 R2 (v5.0) and Wonderware InTouch HMI 2012 R2 (v10.6) on the same node, the following limitations apply:
    • Installing Wonderware Information Server first, using the MS SQL Express default instance name set to "SQLEXPRESS", and then installing Wonderware InTouch HMI will work without issue. Note that in this scenario, each component uses a dedicated instance of SQL Server 2008 Express.
    • Installing Wonderware InTouch HMI first, which silently installs and configures MS SQL Express, and then installing Wonderware Information Server will not allow Wonderware Information Server to work. In this case, during the Wonderware Information Server configuration, an error message will appear in the Configuration Utility stating: "SQL Server client components not found." To work around this issue, configure Wonderware Information Server to use an instance of SQL Server 2008 Express (or a non-Express edition) on a remote node.

Wonderware InTouch HMI 2012 R2 (v10.6) Installation

Installation Notes

Upgrade Notes

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

  • InTouch Development (WindowMaker) is now installed with support for ArchestrA graphics. This includes the ArchestrA Integrated Development Environment (IDE), Bootstrap, Galaxy Repository (GR), and FS Gateway.
  • FactorySuite Gateway (FS Gateway) 3.0 is installed as part of InTouch HMI 10.6 in an ArchestrA System Platform 2012 R2 installation. If you originally installed FS Gateway 2.0 SP1 without any other InTouch products, then upgrading ArchestrA System Platform 2012 to ArchestrA System Platform 2012 R2 will not upgrade FSGateway to version 3.0.
    Uninstall FSGateway before upgrading ASP 2012 to R2.
  • If SQL Server does not exist on the system, SQL Server Express is installed automatically.
  • If the added features are not needed in your current environment, you will need to use the ArchestrA System Platform "product based" installation on a "clean" system. The product based installation provides a customization option so that you can deselect any components that are not needed. Note that the customization option is not available if you are upgrading an existing system from a previous version of InTouch Development.
  • If Wonderware Application Server is installed on the same node as Wonderware InTouch HMI, both must be upgraded to ArchestrA 2012 R2 versions, and you must upgrade Wonderware Application Server before upgrading InTouch HMI.
  • If you are using managed InTouch applications with ArchestrA Symbols from Application Server 3.1 SP3 or earlier, run the ArchestrA Symbol Analysis and Repair Utility before installing Wonderware Application Server 3.6 to ensure that all issues reported by the utility are addressed.

Previous Version Upgrades Supported

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 10.6 from the following versions of the Wonderware 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
  • 10.2
  • 10.5
  • 10.5 P01

You can only upgrade ArchestrA System Platform products that are already installed and you will not be able to install new products within the ArchestrA 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 Wonderware InTouch HMI 2012 R2 (v10.6)

You can migrate applications from the following earlier versions of Wonderware InTouch HMI to version 10.5

  • 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.2
  • Version 10.5
  • Version 10.5 P01

Installing the Wonderware InTouch HMI 2012 R2 (v10.6)

The simplified process makes installing InTouch HMI easier than ever.

The major decision you must make when you install Wonderware 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 Wonderware InTouch HMI and the ArchestrA IDE if you chose to install development components.

What You Need to Install Wonderware InTouch HMI 2012 R2 (v10.6)

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.

Note: Use the hardware and software requirements listed earlier in this Readme if you are going to install the ArchestrA IDE.

Prerequisites

The installation program analyzes the software installed on your computer and lists any software that is required but not currently 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 ArchestrA System Platform installation program:

  • Windows Installer 4.5
  • Microsoft .NET Framework 4.0

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 ArchestrA 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 ArchestrA System Platform 2012 R2 installation. You must specify a user name, password, and domain.

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

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

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

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

Installing Wonderware InTouch HMI 2012 R2 (v10.6)

Before you start installing Wonderware 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.

Wonderware Application Server 2012 R2 (v3.6) Installation

Installation Notes

For detailed instructions on installing pre-requisite software and Wonderware Information Server, as well as upgrade instructions, see the ArchestrA System Platform Installation Guide located in the root folder of the product installation media.

Installation and configuration of a Wonderware Information Server feature is required before you can upgrade that feature to Wonderware Information Server 2012 R2 (v5.0).

  • Before installing Wonderware Application Server:
  • Installing Wonderware Application Server on a computer used as a domain controller is not supported.
  • Installing Wonderware Application Server automatically undeploys any platform that is currently deployed on the node that is being updated. Changes to the WinPlatform object and other components require any deployed platforms to be redeployed.
  • It is recommended that both Wonderware Application Server and Wonderware InTouch HMI not be run in a console session on the same node under Windows Vista, Windows 7, or Windows Server 2008, as results can be inconsistent if you attempt to log alarms from InTouch HMI and the Galaxy.
  • Language Switching - Galaxies with ArchestrA Symbols or InTouchViewApp Objects containing ArchestrA Symbols that leverage the Runtime Language Switching functionality must always be modified on the same language operating system and InTouch language version on which it was initially developed. Attempts to modify these components in a different language operating system or a different InTouch language version can result in unexpected behavior and is not presently supported. Published applications running in an operating system language that is different from the originally developed language are supported.

Upgrade Notes

Previous Version Upgrades Supported

You can upgrade to Wonderware Application Server 2012 R2 (v3.6) from the following Application Server versions:

  • Version 3.0 SP2
  • Version 3.1 (All service packs and patches)
    • 3.1
    • 3.1 SP1
    • 3.1 SP2
    • 3.1 SP2 PO1
    • 3.1 SP3
    • 3.1 SP3 PO1
  • 3.2
  • 3.5
  • 3.5 P01

Upgrade Considerations

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

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

Galaxy Repository Node Upgrade Basic Procedure

The basic upgrade sequence is:

  1. Upgrade your software prerequisites to the required versions.

Note: If you are upgrading the SQL Server on the Galaxy Repository node, you must undeploy the Galaxy Repository node before starting the SQL Server upgrade.

  1. Upgrade the Wonderware Application Server software in the Galaxy Repository node to the current version.
  2. Upgrade at least one IDE installation. If the Galaxy Repository node has the IDE as a feature, then the IDE is also updated. However, if you have any IDE-only nodes, you need to upgrade them separately.
  3. Use the upgraded IDE to connect to the upgraded Galaxy Repository node and migrate the Galaxy database. For more information, see Galaxy Repository Node Migration.
  4. Deploy the Galaxy Repository Platform.
  5. Upgrade non-redundant run-time nodes one at a time and redeploy them.

Note: Redundant nodes must be upgraded together. You cannot leave one node running, while the other one is being upgraded.

  1. Upgrade redundant pairs as a set.

If you upgrade a remote Platform node before you migrate the Galaxy database, the remote Platform and hosted objects show the software upgrade pending icon after you migrate and deploy the Galaxy. To resolve this, undeploy and redeploy the remote Platform. The preferred sequence of upgrade is to upgrade the Galaxy Repository node, migrate the Galaxy database, and then upgrade the remote Platforms.

Upgrade Considerations for Multi-Galaxy Communication

Setting up a multiple galaxy environment requires a unique name for each galaxy in the environment. This may require you to rename one or more galaxies if you plan to include galaxies with the same name in your multi-galaxy communication environment. We recommend performing all necessary renaming prior to upgrading to ArchestrA System Platform 2012 R2. This will prepare your galaxies for use in a multi-galaxy environment without disrupting the upgrade workflow.

Important: It is very important that you follow the galaxy name change procedure provided in the following steps and in the Wonderware Application Server User Guide. You must create a new galaxy with a new, unique name, from a backup .cab file rather than creating a galaxy and performing a restore of the backup .cab file.

Do the following to rename a galaxy for use in a multi-galaxy environment. For more information about creating and backing up galaxies, see the Wonderware Application Server User Guide, Chapter 1 "Getting Started with the IDE" and Chapter 14 "Managing Galaxies".

  1. Select a galaxy with a duplicate name, undeploy it and back it up to create a .cab file.
  2. Use the .cab file as a "template" by placing it in \Program Files\ArchestrA\Framework\Bin\BackupGalaxies.
  3. Create a new galaxy with a new name, based on the backup .cab file. The name must be unique, not in use anywhere else in the multi-galaxy environment.
  4. Repeat the preceding steps for each galaxy to be renamed with a unique name.
  5. Redeploy each newly created galaxy.
  6. Delete the original galaxy from the Galaxy Repository node.
  7. Upgrade to Wonderware Application Server 3.6 using the ArchestrA System Platform 2012 R2 installation program.

Your galaxies can now be configured for use in a multi-galaxy environment.

Wonderware Historian Server 2012 R2 (v11.0) Installation

For detailed instructions on installing any of the products that make up the ArchestrA System Platform 2012 R2, see the ArchestrA System Platform Installation Guide (ASP_Install_Guide.chm). This guide includes comprehensive information on system requirements and recommendations, installation, upgrades and migration, and system sizing examples. If you are installing the Wonderware Historian or upgrading from a prior version, read this information before starting the installation or upgrade.

The server management tools include Wonderware Historian Configuration Editor and Wonderware Historian Management Console. Both of these applications are MMC snap-ins that are contained in the System Management Console. These tools are always installed on the same computer as the Historian and can also be installed on a different computer on the network. The Wonderware Historian Database Export/Import Utility is also an installed configuration tool.

Upgrade Notes

You can directly upgrade from Wonderware Historian 10.0, and Wonderware 10.0 SP1. It is possible to upgrade from earlier versions of Wonderware Historian, but you must first upgrade to the 10.0 version. Follow the instructions in the 10.0 documentation to perform the upgrade. After you have upgraded to the 10.0 Historian, you can then upgrade to Wonderware Historian 2012 R2 (v11.0).

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

Wonderware Historian Client 2012 R2 (v10.1) Installation

Upgrade Notes

The Wonderware Historian Client 2012 R2 (v10.1) software supports an upgrade from the Wonderware Client 10.0 SP2 software. Wonderware Historian Client 10.0 SP1 and earlier versions are not supported for a direct upgrade.

The application files created with ActiveFactory 9.2, Wonderware Historian Client 9.5, Wonderware Historian Client 10.0 or Wonderware Historian Client 10.0 SP1 software require no modifications to be used with the Wonderware Historian Client 10.0 with SP2 software. Optionally, the application files can be migrated to take advantage of new retrieval features. For more information, see the Wonderware Historian Client User's Guide.

You can open Trend, Query, Workbook, and Report files created using ActiveFactory versions 9.0, 9.1, 9.2, and Wonderware Historian Client versions 9.5, 10.0, 10.0 SP1, and 10.0 SP2. These documents are converted and saved to the format used by Wonderware Historian Client 10.1. ActiveX and .NET applications built using ActiveFactory 8.5, 9.0, 9.1, 9.2, and Wonderware Historian Client 9.5, 10.0, 10.0 SP1, and 10.0 SP2 controls continue to operate without changes to their original functionality.

Wonderware Information Server 2012 R2 (v5.0) Installation

For installation and upgrade instructions, see the ArchestrA System Platform Installation Guide.

Licensing Information

Wonderware Information Server

The following are the feature lines in the local license that enables Wonderware Information Server 2012 R2 (v5.0) functionality:

Feature Description
SVoyager_Portal Controls the license for the portal server.
SVoyager_WriteEnable Controls tag server writeback for published Process Graphics windows.
SVoyager_svrconc Controls the number of concurrent portal user sessions.
ActiveFactory_Web Controls access to the web-based ActiveFactory controls.
ActiveFactory_Pro_Web Controls access to the X/Y scatter plot functionality in the web-based ActiveFactory Trend control.
ActiveFactory_RWS Controls access to the ActiveFactory Reporting Website functionality.

Wonderware Information Server 2012 R2 (v5.0) uses the following licenses:

  1. ArchestrA.lic to enable the portal functionality.
    Install this file in the node that hosts the portal.
  2. ArchestrAServer.lic to enable clients access to the portal.
    Install this file in the node that hosts the ArchestrA License Server.

Note: Wonderware Information Server 4.5 and earlier licenses cannot be used for Wonderware Information Server 2012 R2 (v5.0). Contact your local distributor for assistance.

Additionally, Wonderware Information Server 2012 R2 (v5.0) supports using a centralized licensing server to manage client licenses. For more information, see the ArchestrA License Manager Guide and the license server documentation in the LicenseServer folder of the Wonderware Information Server 2012 R2 (v5.0) installation media.

Post-Installation Notes

Wonderware InTouch HMI 2012 R2 (v10.6)

Wonderware InTouch HMI 2012 R2 (v10.6) Memory Usage

The default value for InTouch HMI internal shared memory management (WWHeap) has been changed to use more memory

In a 32-bit operating system, the default maximum memory of WWHeap is increased to 1.5 GB from 256 MB. Special configuration can increase the maximum limit to nearly 2 GB. The InTouch HMI memory management can be extended to 3 GB by adding the /3GB switch in the boot.ini file. An entry in the boot.ini file with the /3GB switch looks like the following:

    [operating systems]
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional"
    /fastdetect /3GB

Note: This example is specific to a Windows XP computer. For other operating systems, the Windows name is different.

If the /3GB switch is enabled in Windows, the paging file size should be set to a system managed size, and then InTouch HMI can access up to 3 GB of memory.

In a 64-bit operating system, it is not necessary to edit the boot.ini file and InTouch HMI can use up to 4 GB of memory.

For additional information, refer to Microsoft Knowledge Base articles, such as KB 328882.

Wonderware InTouch HMI 2012 R2 (v10.6) Window Caching

View.exe supports hybrid functionality to keep some selected windows in memory and load the rest from the disk. To enable this functionality, you must configure the memory health check interval and set the memory properties. For detailed information, see the InTouch HMI Application Management and Extension Guide (ITAppManagement.pdf).

Modifying Galaxy Repositories

Galaxy Repositories with ArchestrA Symbols or InTouchViewApp objects containing ArchestrA Symbols that leverage the Runtime Language Switching functionality must always be modified on the same language operating system and InTouch HMI language version on which it was initially developed. Attempts to modify these components in a different language operating system, or a different InTouch HMI language version, may cause unexpected functional or operational issues that are not currently supported. Published applications running in an operating system language that is different from the originally developed language are supported. Refer to Known Issues CRs L00088974, L00088993, and L00088998.

Additional Notes

  • Antivirus Exclusions - The antivirus software exclusions list has been updated. Review the Antivirus Software Exclusions list.
  • Remote Sessions - Windows Server 2008 R2 no longer supports the /console switch as a means of setting the Remote Desktop Client (RDC), also known as a console session. Click this Terminal Services Behavior link for more information about Terminal Services behavioral changes.
  • Terminal Server Sessions and Alarms - If you are running WindowViewer within a Terminal Server session and want to access alarms from WindowViewer in a client session, you must use the syntax \\terminalservernode:<IP address>\InTouch!$System to access the alarms, with a colon (:) after the node name. The IP address is that of the client computer connected to the session. Click this Terminal Services Behavior link for more information about Terminal Services behavioral changes.
  • License Utility - Starting the ArchestrA Licensing Utility from an existing License CD might not work on a 64-bit operating system. Start the utility from the installed shortcut instead.
  • Operating System Restrictions - All the restrictions applicable to Windows Vista and Windows Server 2008 are also applicable to Windows 7 and Windows Server 2008 R2, respectively.
  • Quotes in Command Lines - If you copy a command from other applications, issues might occur with command line printing. To avoid any issues, delete any quotes (") that you may have copied and type them again manually.

Wonderware Application Server 2012 R2 (v3.6) and Wonderware Historian Server 2012 R2 (v11.0)

Antivirus Software Exclusions

After installing Wonderware Application Server or Wonderware Historian Server, configure your antivirus software to prevent archive files from being scanned.

Notes:

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

Antivirus software should not scan files in the following ArchestrA folders in a 32-bit system:

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

Antivirus software should not scan files in the following ArchestrA folders in a 64-bit system:

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

From Wonderware Application Server Platform objects:

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

Wonderware Information Server

Antivirus Software Exclusions

After installing Wonderware Information Server, configure your antivirus software to prevent files in the following folders from being scanned:

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

Note: Ensure 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\...

Resolved Issues

This section documents important resolved issues broadly categorized as ArchestrA System Platform-level issues. This list is not comprehensive.

Note: Additional resolved issues are documented in the product-specific Readme files.

L00106940: Unexplained system failovers on redundant engines with Windows Vista operating systems ceased with application of Windows Vista Service Pack 2.

Known Issues

The following are important known issues for ArchestrA System Platform 2012 R2. Additional known issues are documented in the product-specific Readme files. Issues are listed by their assigned CR number in ascending order.

Installation Issues

L00101032: If Wonderware Information Server was installed but was never configured, and you then attempt to uninstall any ArchestrA System Platform product, the following error occurs: "The program can't start because ivfw.dll is missing from your computer. Try reinstalling the program to fix this problem."

To resolve this issue, configure Wonderware Information Server. You will then be able to uninstall the other products.

L00114561: SQL Server Standard vs. Express is not differentiated by the installation if already present in the system.

Workaround: Where possible, upgrade SQL Server Express to SQL Server Standard Edition before installing ArchestrA System Platform 2012 R2 components.

L00114588: You must manually install the language packs for the Wonderware Historian Client product by running the setup.msi file in the appropriate subfolder of the following folder of the ArchestrA System Platform DVD: ...\ArchestrA System Platform\CD-HistorianClients\HistorianClient\Lang\.
L00114910: On a computer running the Windows Server 2008 R2 or Windows 7 (64-bit) operating system, a blank domain is shown in Admin User Page when you clear the Create Local Account check box. This behavior is a result of the browser service being disabled by default on the computer running the Windows Server 2008 R2 or Windows 7 (64-bit) operating system.
L00116044: For the Windows 7 SP1 operating system, if you upgrade an InTouch HMI Development installation, create an ArchestrA Galaxy, and then uninstall Wonderware Application Server using Control Panel, an application exception error occurs. The exception error is for the Windows call and not for the Wonderware Application Server product itself. Wonderware Application Server successfully uninstalls.
L00116459: The remote node fails to connect to a WWALMDB database that is created using SQL Express Edition.

Workaround: Change the SQL Server Express authentication from Windows mode to Mixed mode.

To change SQL Server Express Authentication mode

  1. Download and install the x86 version of SQL Server 2008 Management Studio Express from http://www.microsoft.com/download/en/details.aspx?id=7593.
  2. After installation, right-click SqlExpress Connection, click Properties, and then click Security.
  3. Change the SQL Server Express authentication from Windows mode to Mixed mode and click OK.
  4. Restart the database instance or computer.
L00116556: The License Server is not available as an optional feature for the Wonderware Historian Client installation. If you want to install the License Server, manually run setup.exe in the \CD-HistorianClients\LicenseServer folder of the ArchestrA System Platform DVD.
L00116877: If you select only Wonderware Historian Client features for installation, the installation allows you to continue even if the Rainbow Sentinel prerequisite is not installed. You can manually install the Rainbow Sentinel prerequisite from the following folder: \CD-HistorianClients\LicenseServer\Redist\Rainbow
L00116883: Due to a Windows operating system issue, Wonderware InTouch HMI and related applications, such as Alarm DB Logger, can crash on startup if installed to a drive other than C:\. As a workaround, create an empty file named win.ini in folder C:\Users\<username>\AppData\Local\Wonderware where "username" is the name of the user attempting to start the application.
L00120356: Creating a new graphic toolset, or creating a new symbol in an existing toolset, from the Graphic Toolbox in the IDE can result in errors in the logger if Wonderware Intelligence 1.5 is also installed. Creating a new symbol directly under the galaxy rather than from the Graphic Toolbox does not result in logger errors. Functionality is not impacted, and the logger errors can be ignored.
L00123209: When installing ArchestrA System Platform, the system cannot read the Wonderware Application Server license if the Galaxy Repository and the IDE are installed on a node where Wonderware InBatch or other Invensys products are already installed. As a workaround, use the License Manager to reinstall the ArchestrA license for Application Server after the ArchestrA System Platform installation is complete.
L00123507: The ArchestrA System Platform 2012 R2 installation Product-specific Prerequisites dialog lists SQL Server 2008(x86) SP3 Std/Ent (SQL Express 2008 R2 SSME for InTouch Dev only) as a prerequisite for the Galaxy Repository feature, but the Install Prerequisites button is disabled. If your installation or upgrade has the InTouch Development and Runtime feature selected and your system was installed with the earlier version of SQL Server 2008 Express installed as part of ArchestrA System Platform 2012, you must exit the installation program, install SQL Server 2008 R2 SP1 32-bit Express-SSME, then resume the installation.

To do this, you can run the SQL Server 2008 Express installation from the following ArchestrA System PLatform 2012 R2 DVD media folder path:

<ArchestrA System Platform 2012 R2 DVD>:\InstallFiles\Redist\SQL2K8R2SSMSE\SQLEXPRWT_x86_ENU.exe

Upgrade and Migration Issues

L00109221: After disabling TimeMaster, deploy and undeploy operations result in errors and warnings in the logger. As a workaround, identify galaxies by machine names rather than by IP addresses.
L00114546: Migrating an application with SPCPro controls may fail. SPCPro is not supported in Windows Vista or newer operating systems. Applications with charts or scripts may not migrate or run properly in those operating systems.

Workaround: To migrate an application to the current version containing SPCPro components, Windows XP must be used. If the application needs to run in Windows Vista or newer operating systems, either remove the SPCPro charts and script functions prior to migrating, or use the Windows XP installation to remove SPCPro references from the application.

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

Workaround: Ensure the Galaxy Repository node is upgraded completely including restarting before upgrading any other Galaxy node that has a deployed platform.

L00122615: The QI Analyst 8.0 SP2 link to the Historian Server will be broken if Historian Client is installed on the same system. A hotfix is available upon request from Customer Support.
L00123504: Unexpected and misleading errors can appear in the logger while migrating particularly large galaxies because the transaction log for the galaxy database has reached its maximum allocated size.

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

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

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

ArchestrA Service Bus and Multi-Galaxy Communication Issues

L00122983: The SetAttributeVT() function writes the value and time from ArchestrA Graphics for local Galaxy attributes, but for remote Galaxy attributes it sets only the value, not the time.
L00123211: In a multi-galaxy environment, performing a change user operation in Object Viewer can fail with the message "User does not belong to any of the configured Roles". In order for writes to succeed in a multi-galaxy environment, the user must successfully have been logged on to both galaxies in a pair. To ensure stable access in a multi-galaxy environment, you must add all Domain User accounts from the target galaxy to the Cross Galaxy Server node galaxy.
L00123433: Multi-galaxy communication does not work on a computer where Application Server and the Historian have been uninstalled and Application Server has been reinstalled. When you uninstall Application Server, the ArchestrA Services (ASBService) database is not deleted from the system. This means that any existing galaxy pairings will persist when you reinstall Application Server on the same system. The persistent pairing information is automatically available after the reinstallation. Because the uninstall operation stops SQL Server, the ASBService user and permissions are not deleted from SQL Server. Pairing information can be out of date and multi-galaxy operations not working as the Discovery Service information is lost in the transition from uninstall to install. To resolve out-of-date database information, you must delete the ASBServices user from SQL Server before re-installing, and you must un-pair and re-pair to the required galaxies after performing uninstall and re-install operations on the same node.

For example:
  1. Install the latest Application Server software on two nodes, Node1 and Node2.
  2. Create a galaxy with a platform, and pair the nodes.
  3. On Node1, uninstall Application Server and restart the system.
  4. On Node 1, if the ASBService user still exists in SQL Server, delete the user manually before re-installing Application Server.
  5. On Node1, reinstall Application Server and connect to the same galaxy.
  6. Open the Multi-Galaxy Configuration dialog. Notice that all the pairing information has persisted through the uninstall-reinstall operation. Also, notice that multi-galaxy operations are not functioning. You cannot browse to or subscribe from Node2 even though the nodes appear to be paired.
  7. Un-pair and re-pair Node1 to get the new Discovery Service and pairing information from Node2.
L00123462: In a multi-galaxy environment, you can pair galaxies by IP address rather than using a node name (computer machine name). Unpairing galaxies identified by IP address fails when NetBIOS and DNS solutions are unavailable. Where your galaxies are identified by IP address, you must create a temporary host file to map the IP addresses as hostnames for purposes of unpairing.

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

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

ENDIF;

L00123475: When configuring user-configurable ArchestrA Services - ASBGRBrowsing service, ASBMxDataProvider service, and ASBAuthorization service - it is important not to assign the same port number to two instances of a service on the same node. However, it can occur that while creating instances of a service and assigning them to the same node, that the system can erroneously assign a duplicate port number by default. The main symptom of this error is that you do not see a remote galaxy where expected, such as in a list of available galaxies in the Galaxy Browser. As a first step in troubleshooting this problem, do the following:
  1. Open the Configure ArchestrA Services utility.
  2. Note the port number of the ASBGRBrowsing service instance for the missing galaxy.
  3. Compare this to the port numbers of other ASBGRBrowsing service instances assigned to the same node.
  4. If you find a service instance with a duplicate port number on the same node:
    1. Undeploy the browsing service of the missing galaxy.
    2. Change the port number to a unique number for that node.
    3. Redploy the browsing service instance.
L00123478: Attempting to deploy a platform on a remote node can result in errors. Repeated attempts to deploy the platform can succeed, but the ASB Services can become unavailable on the remote node after deploying the remote platform. As a workaround, undeploy and redeploy the remote platform.
L00123602: Buffered data is not supported in a multi-galaxy environment.
L00123682: After browsing remote galaxies, the IDE will continue to generate network traffic to each remote galaxy you browsed. This behavior is triggered when browsing a remote galaxy, then switching to browse the local galaxy. An IDE not using multi-galaxy communication will not experience this behavior. Closing the IDE process will end the network traffic between the IDE node and the remote galaxy browsing service.
L00123709: Setting or resetting either the Local Galaxy Server or the Cross Galaxy Server prompts core ArchestrA Services to restart. This can cause a timing issue if you immediately deploy a platform, either local GR or remote, resulting in the ASBMxDataProvider and ASBAuthentication services remaining undeployed. Run-time connectivity to remote galaxies will fail without these services deployed. As a workaround, after setting either the Local Galaxy Server or the Cross Galaxy Server, you must wait 20 seconds before you deploy a platform to allow the multi-galaxy support services to complete a restart.

Device Integration Issues

L00117310: Under certain circumstances, a Redundant Device Integration (RDI) item can stay in Initializing quality or can become stuck in Bad quality, even though the DI source shows Good quality. As a workaround if the RDI item is stuck in Initializing quality, stop and restart the engine hosting the RDI object. As a workaround if the RDI item is stuck in Bad quality, restart the engine hosting the RDI object or the engine(s) that host the DI objects.

Documentation

This section describes the documentation that is available for the components of ArchestrA System Platform 2012 R2.

You need Adobe Reader installed on your computer to view ArchestrA System Platform component documentation. You can download the latest version of Adobe Reader from the Adobe Corporation web site: http://www.adobe.com/products/acrobat/readstep2.html.

Documentation: Wonderware InTouch HMI 2012 R2 (v10.6)

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

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

Documentation Set

The Wonderware InTouch HMI documentation set includes the following guides:

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

Information included in these guides is provided in online Help, which can be opened using the Help menu options in each utility. During product installation, you can choose to install the documentation PDF on your local hard drive.

Documentation: Wonderware Application Server 2012 R2 (v3.6)

The Wonderware Application Server product library consists of a set of Portable Document Files (PDF) available in the following location in the ArchestrA System Platform DVD:

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

Documentation Set

The Wonderware Application Server documentation set includes the following guides:

  • Wonderware Application Server User's Guide. Explains configuring and deploying Wonderware Application Server applications.
  • Creating and Managing ArchestrA Graphics User's Guide. Explains how you create and manage graphical symbols using the ArchestrA Symbol Editor within the Integrated Development Environment (IDE).
  • Wonderware Application Server Scripting Guide. Reference for the scripting language in Wonderware Application Server.
  • Object Viewer User's Guide. Explains how to acquire run-time data using the Object Viewer.
  • Guide to the ArchestrA Alarm Control. Explains how to configure the alarm control (client) to show current and historical alarms and events in a grid.
  • Guide to the ArchestrA Trend Client. Explains how to configure a chart to trend real-time data values.
  • Platform Manager User's Guide. Explains how to start and stop system components.
  • Galaxy Database Manager User's Guide. Explains how to backup and restore the Galaxy database.
  • Log Viewer User's Guide. Explains how to use the Log Viewer utility to determine system diagnostics.
  • Log Flag Editor Utility Guide. Explains how to turn on and off certain diagnostics logging messages.
  • Wonderware FactorySuite License Utility Guide. Explains how to use the License Utility to manage the license required for the running application.
  • Wonderware ArchestrA Protocol Guide. Explains background information on the main protocols used between components of Wonderware products.
  • Wonderware InTouch HMI and ArchestrA Integration Guide. Explains how you can use the ArchestrA Integrated Development Environment (IDE) to manage InTouch HMI applications so that you can use symbols you create in the ArchestrA Symbol Editor. Available in the following location in the ArchestrA System Platform DVD: \Archestra System Platform\CD-Intouch\UserDocs\English.

Information included in these guides is provided in online Help, which can be opened using the Help menu options in each utility. During product installation, you can choose to install the documentation PDF on your local hard drive.

Documentation: Wonderware Historian Server 2012 R2 (v11.0)

The Wonderware Historian Server product library consists of a set of Portable Document Files (PDF) available in the following location in the ArchestrA System Platform DVD:

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

Documentation Set

The Wonderware Historian documentation set includes the following guides:

  • ArchestrA System Platform Installation Guide. This guide provides information on installing the Wonderware Historian, including hardware and software requirements and migration instructions.
  • Wonderware Historian Concepts Guide. This guide provides an overview of the entire Wonderware Historian system and describes each of the subsystems in detail.
  • Wonderware Historian Administration Guide. This guide describes how to administer and maintain an installed Wonderware Historian, such as, configuring data acquisition and storage, managing security, configuring replication, and monitoring the system.
  • Wonderware Historian Database Reference. This guide provides documentation for all of the Wonderware Historian database entities, such as, tables, views, and stored procedures.
  • Wonderware Historian Glossary. This guide provides definitions for terms used throughout the documentation.

Context-sensitive documentation is also available with the Wonderware Historian Server online help. Select Help for information about the current Wonderware Historian Server window that you have open on your computer.

Documentation: Wonderware Historian Client 2012 R2 (v10.1)

The Wonderware Historian Client Software User's Guide is a Portable Document Files (PDF) available in the following location in the ArchestrA System Platform DVD:

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

Documentation Set

The Wonderware Historian Client documentation set includes the following guides:

  • ArchestrA System Platform Installation Guide. This guide provides information on installing Wonderware Historian Client, including hardware and software requirements and migration instructions.
  • Wonderware Historian Client Software User's Guide This guide describes how to use stand-alone applications, Microsoft Office add-ins, and ActiveX and .NET controls to retrieve and display data.

Information in the user's guide is also is provided in online Help, which can be opened using the Help menu within the software.

Documentation: Wonderware Information Server 2012 R2 (v5.0)

The Wonderware Information Server product library consists of a set of Portable Document Files (PDF) available in the following location in the ArchestrA System Platform DVD:

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

Documentation Set

The Wonderware Information Server documentation set includes the following guides:

  • ArchestrA System Platform Installation Guide. Describes how to install, uninstall, and reinstall a Wonderware Information Server, and also describes using a domain controller with Wonderware Information Server and migrating from a previous version.
  • Wonderware Information Server Administration Guide. Describes how to administer and maintain a Wonderware Information Server, including configuring data sources, managing security, and performing customizations.
  • Wonderware Information Server Win-XML Exporter Guide. Describes how to use the Win-XML Exporter to convert InTouch HMI application windows to web pages and publish them to the Wonderware Information Server. This guide also includes a section for designing InTouch HMI application windows for Wonderware Information Server. This section describes how to best design InTouch HMI windows so that they can be successfully converted and optimally viewed in the portal.
  • ArchestrA Web Exporter Guide. Describes how to use the ArchestrA Web Exporter to publish ArchestrA Symbols and InTouch HMI Windows to Wonderware Information Server. This guide also describes how to add, delete and modify WindowSets and SymbolWeaverSets of the project and preview them in the preview window of ArchestrA Web Exporter.
  • ArchestrA License Manager Guide. This guide describes the ArchestrA License Manager and how to use it to install and manage licenses and license servers on local and remote computers. This guide is provided as a PDF file, which is located on the Wonderware Information Server software installation media.

Information included in the administration guide is also provided as browser-based online Help, which can be accessed from the Wonderware Information Server Portal.

 

 

© 2012 Invensys Systems, Inc. All Rights Reserved.