Application Server 3.1 SP1
Last revision: 03/06/2009
About This Readme
This document adds information from Wonderware® Application Server
3.1 Service Pack 1 (SP1) to the previous Readme file included with
Wonderware Application Server 3.1.
Important!
- Before installing
Wonderware Application Server 3.1 SP1:
- Ensure that you create good known backups of all Galaxies.
- If you are using an InTouch 10.0 application with ArchestrA Symbols, run the ArchestrA Symbol Analysis and Repair Utility and ensure all issues reported by the utility are addressed.
- If you have Wonderware Application Server 3.0 installed, the provided base default Galaxies are replaced during the installation.
- Installing Wonderware Application Server 3.1 SP1 does not automatically undeploy any platform that is currently deployed in the node that is being updated. Only major changes to software components may require any deployed platforms to be redeployed.
- If InTouch 10.0x and Application Server 3.0x are installed on the same node, they both must be upgraded to Application Server 3.1 or Application Server 3.1 SP1 and InTouch 10.1.
- If the ArchestrA IDE connects remotely to the Galaxy Repository on another computer, apply Wonderware Application Server 3.1 to both nodes. A remote connection between the ArchestrA IDE and the Galaxy Repository fails if the nodes are at different versions of Wonderware Application Server. This does not apply to version 3.1 SP1 if the remote connection is version 3.1 and vice versa.
- You must install Wonderware Historian 9.0 Patch 02 to use take advantange of new historian features including time propagation and late data from the Wonderware Application Server to the Historian. The patch is also required to leverage the new Historian configuration options from the IDE.
- A Galaxy Database Scrubber utility is available for download from the Wonderware Technical Support website. The utility is an off-line tool to clean up unused information in the Galaxy and reduce the overall Galaxy database size.
- The antivirus software exclusions list has been updated. Click this Antivirus Software Exclusions link for details.
About Application Server 3.1 Service Pack 1 (SP1)
Using Application Server with Windows Vista
Upgrading to Version 3.1 SP1 from an Earlier Version of Application Server
Migrating Applications to Application Server version 3.1 SP1
Resolved Issues – Application Server 3.1
Known Issues – Application Server 3.1 SP1
Known Issues – Application Server 3.1
Application Server Documentation Issues
Application Server Documentation
About Application Server 3.1 SP1
Wonderware Application Server 3.1 SP1 includes the following enhancements and new features:
Enhanced Object Import
You can import an object even when it has a lower (earlier) configuration version than an existing object. During the import, you can:
- Overwrite objects with the same tagname and codebase as an existing object even if the imported object is older than the existing object
- Migrate base templates with newer or older codebase
- Rename objects with the same tagname but a different codebase
Enhanced Service Pack Installation
The service pack installer has been modified so that it will not require a deployed platform to be automatically removed or the software uninstalled during the upgrade process. Only major upgrades will require a deployed platform to be removed and redeployed.
About Application Server 3.1
Wonderware Application Server 3.1 includes the following enhancements and new features:
Advanced Communication Management
Advanced Communication Management minimizes network traffic and CPU usage of a DIObject or DAServer. While the client application is running, scanning for an attribute value is suspended when the owning object no longer appears in the running application. For example, Advanced Communication Management suspends scanning for an object's attribute value when the operator minimizes the application window containing the object. When the operator shows the window containing the object again, Advanced Communication Management resumes scanning and the object's attribute value is updated in the application.
Time Propagation
Time propagation preserves the timestamp of process data obtained from source field devices like a PLC or DAServer. The timestamp can be shown from visualization client applications like InTouch. Also, timestamps are associated with the value and quality of data saved to the Wonderware Historian.
Improved Alarm Usability
Individual alarms of an object can now be selectively enabled, silenced, or disabled by an operator or a script.
- Object-wide disablement prevails over the alarm mode of any individual alarm. For each individual alarm, the object's alarm mode follows the most restrictive setting of either the individual alarm or the entire object.
- Individually disabling one type of alarm has no effect on any other types of alarms in an object. For example, disabling a HiHi Level alarm of an object does not disable the object's Rate of Change alarm.
- Individually disabling an alarm does not propagate downward through the object hierarchy to any other assigned or contained objects. For example, disabling a HiHi Level alarm on Object A does not disable a HiHi Level alarm on contained Object B.
Script Improvements
Two new methods are available for Application Server scripts. The LogDataChangeEvent() method logs application change events to the Galaxy Historian. The SetAttributeVT() method can be used to set the value and timestamp of an object attribute.
New History Attributes
From the IDE, you can configure the historical attributes of data saved to the Wonderware Historian. The following list shows the new historical attributes introduced in version 3.1:
- Description
- Interpolation type (linear, stairstep, system default)
- Rollover value (counter-mode retrieval)
- Sample count
- Rate deadband
- Swinging door
Support for Late Data to the Historian
Application Server now includes late data support to save historical data that arrives with a timestamp earlier than the Wonderware Historian's current time.
Alarm and Trend Clients
The ArchestrA Alarm Client and Trend Client are
available from within the ArchestrA Symbol Editor.
The Trend Client:
- Plots the real time values of ArchestrA application object attributes and InTouch tags.
- Supports historical data from a Wonderware Historian or from InTouch history files (LGH). However, the Trend Client can operate without these data sources.
- Supports full and cyclic retrieval while getting data from the Wonderware Historian.
- Supports faceplate displays created within the ArchestrA IDE graphics of InTouch version 10.1 or later.
The Alarm Client shows current and historical alarms and events.
The Trend Client and Alarm Client work with multilingual versions of InTouch applications and Wonderware Application Server. The Trend Client and Alarm Client support the following languages:
- English
- German
- French
- Japanese
- Simplified Chinese
A localization toolkit is available to add support to other languages and it is distributed separately. It also includes a Microsoft Word version of the documentation.
MXAccess Toolkit Enhancements
The MXAccess Toolkit includes new methods to support Advanced Communication Management and time propagation. Also, the MXAccess Toolkit can be used to write applications that can establish a supervisory connection.
Antivirus Software Exclusions
After installing Application Server, configure your antivirus software to prevent archive files from being scanned. Also, antivirus software should not scan files in the following ArchestrA folders (ensure subfolders of the listed directories are also excluded):
C:\Program Files\ArchestrA\
C:\Program Files\Common files\ArchestrA\
C:\Program Files\FactorySuite\ (may not exist in newer
installations)
C:\Program Files\Wonderware\
C:\InSQL\Data\
C:\Documents and
Settings\All Users\Application Data\ArchestrA
From Application Server Platform objects:
- History Store Forward directory: (if not default)
From Application Server Engine objects:
- Checkpoint directory location (if not default)
<InTouch Application folder path> including:
C:\Documents and Settings\All Users\Application
Data\ArchestrA\
<SMCLoggerStoragefilepath>. The default is:
C:\Documents and Settings\All Users\Application
Data\ArchestrA\LogFiles\
SQL Server database files of type:
- .mdf
- .ldf
Minimum Hardware Requirements
The following list shows the minimum computer hardware requirements to host Application Server version 3.1 SP1 components.
Galaxy Repository (GR) node
- 2 gigahertz (GHz) or faster dual core processor, or a 3 GHz or faster single core processor. A dual core processor is strongly recommended for optimal performance.
- Minimum of 2 gigabytes (GB) RAM. For Galaxies with more than 500 objects, 4 GB RAM is recommended in the GR node.
- 30 GB of available disk space.
- Super VGA (1024 x 768) or higher resolution video adapter and monitor.
- Network interface card.
- CD-ROM or DVD drive.
- Keyboard.
- Mouse or a compatible pointing device.
Development and Application nodes
- 2 GHz or faster processor.
- Minimum 1 gigabyte (GB) RAM. For improved performance 4 GB RAM is strongly recommended.
- 30 GB of available disk space.
- Super VGA (1024 x 768) or higher resolution video adapter and monitor.
- Network interface card.
- CD-ROM or DVD drive.
- Keyboard.
- Mouse or compatible pointing device.
The hardware requirements for using the Alarm Client and Trend Client at run time are the same as for the InTouch HMI version 10.1 run time.
The Windows Vista operating system imposes hardware requirements that may exceed the minimum requirements for Application Server version 3.1 SP1. If you intend to install Application Server 3.1 SP1 on a computer running Windows Vista, see the following Microsoft web site for hardware requirements:
www.microsoft.com/windows/products/windowsvista/editions/systemrequirements.mspx
Software Requirements
This section describes the operating system, database, and other software requirements to install Application Server version 3.1 SP1.
Operating Systems
- Windows Server 2003 Standard Edition SP2 is the recommended operating system for computers running server components.
- Windows XP SP3 is the supported XP version for this release.
- Windows XP Professional SP3 is the recommended operating system for computers running client components.
The following table lists the supported operating systems that can be installed on computers running as Application Server development, application, and GR nodes. Development and application nodes are considered to be clients of the server GR node.
| Operating Systems | Wonderware Application Server Components | ||
| ArchestrA IDE (Development Node) |
ArchestrA Run Time (Application Node) |
Galaxy Repository (GR Node) | |
| Windows Vista Business (See Vista Restrictions) | ? | ? | ? |
| Windows Vista Business SP1 (See Vista Restrictions) | ? | ? | ? |
| Windows Vista Enterprise (See Vista Restrictions) | ? | ? | ? |
| Windows Vista Enterprise SP1 (See Vista Restrictions) | ? | ? | ? |
| Windows Vista Ultimate (See Vista Restrictions) | ? | ? | ? |
| Windows Vista Ultimate SP1 (See Vista Restrictions) | ? | ? | ? |
| Windows Server 2003 Standard Edition SP2 | ? | ? | ? |
| Windows Server 2003 Enterprise Edition SP2 | ? | ? | ? |
| Windows Server 2003 Standard Edition R2 SP2 | ? | ? | ? |
| Windows Server 2003 Enterprise Edition R2 SP2 | ? | ? | ? |
| Windows XP Professional SP3 | ? | ? | See Note 2. |
| Windows XP Tablet | ? | ||
Notes:
- The Windows 2000 Professional, Windows 2000 Server, and Windows 2000 Advanced Server operating systems are not supported for Application Server version 3.1 SP1. An error occurs if you attempt to install or upgrade Application Server version 3.1 SP1 on a computer running any edition of the Windows 2000 operating system.
- The computer designated as the Galaxy Repository node can run on Windows XP Pro only as a single-node configuration of Application Server. Windows Server 2003 is the recommended operating system for the GR node.
- You can run Application Server only on computers running a 32-bit operating system. You cannot run Application Server on a computer running a 64-bit operating system.
- The Bootstrap, IDE, and Galaxy Repository are supported by the following language versions of Microsoft operating systems: English, Japanese, Chinese, German, and French. The Galaxy Repository is also supported by the English, Japanese, Chinese, German, and French versions of Microsoft SQL Server 2005.
SQL Server Database Requirements
Microsoft SQL Server 2005 with SP2 is the only database supported by Application Server version 3.1 SP1. You must use the Standard or Enterprise editions of SQL Server 2005. Neither the Compact, Express, nor the Workgroup editions of SQL Server 2005 can be used as the Galaxy Repository.
- SQL Server 2005 SP2 must be installed on the computer designated as the ArchestrA Galaxy Repository node prior to installing Application Server.
- You also cannot install and use Application Server on a computer that has both Microsoft SQL Server 2000 and Microsoft SQL Server 2005 installed.
- 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 2005 database. The TCP/IP protocol setting can be verified from the SQL Server 2005 Network Configuration under SQL Server Configuration Manager.
- The Microsoft SQL Server 2005 login for BUILTIN\Administrators group must be present and enabled.
Other Software Requirements
The following list describes other third-party software required for Application Server version 3.1 SP1.
- Microsoft .NET Framework 3.5
Microsoft .NET Framework 3.5 must be installed on every computer that hosts an Application Server version 3.1 SP1 component. The Application Server installation program halts if .NET Framework 3.5 is not installed on the target computer. A dialog box appears requesting that you install .NET Framework 3.5. If you click Install Prerequisites, the installation program automatically installs .NET Framework 3.5.
- Microsoft Visual Studio 2005
Microsoft Visual Studio 2005 is required only by the MXAccess and GRAccess toolkits distributed with Application Server.
Alarm Client and Trend Client Requirements
The software requirements for using the Alarm Client and
Trend Client at run time are the same as for the InTouch HMI version 10.1 run
time. If you want to trend data from the Wonderware Historian (formally
known as IndustrialSQL Server), version 9.0 or later is required.
The Trend
Client is compatible with the following Wonderware products:
* InTouch
10.1
* Wonderware Application Server
3.1 and Wonderware Applicaton Server 3.1 SP1
* Wonderware Historian 9.0
* ActiveFactory 9.2
* QI Analyst 8.1
Using Application Server with Windows Vista
This section describes specific restrictions when using the Windows Vista operating system with Application Server and how to configure multiple Network Information Cards on a computer running Windows Vista.
Vista Restrictions
- Application Server version 3.1 SP1 can run under Windows Vista SP1, Windows Vista Enterprise SP1, Windows Vista Business SP1, or Windows Vista Ultimate SP1. The Windows Vista Home Basic and Home Premium editions are not supported. The Windows Vista Business Edition is recommended for use with Application Server.
- You must log on as a Windows Vista administrator to run Application Server version 3.1 SP1. You cannot run Application Server as a Windows Vista standard user or power user.
- The Windows Vista User Account Control (UAC) must be disabled when running Application Server. Refer to Microsoft Windows Vista documentation for instructions to disable UAC.
- When you disable Windows Vista UAC, you must restart the computer before attempting to install the ArchestrA IDE or Wonderware Application Server. A Galaxy connection error occurs if you attempt to install the ArchestrA IDE or Wonderware Application Server and you did not restart the computer after you disabled the UAC.
- Windows Vista does not support a traditional Application Server single-node configuration that includes Wonderware Historian (formerly IndustrialSQL Server).
- The Galaxy Repository is supported on Vista only for a single-node configuration of Application Server. For multiple-node Galaxies, Windows Server 2003 is the recommended operating system for the Galaxy Repository node.
- If the computer that hosts the Galaxy Repository runs on Windows Vista, SP2 must be applied to SQL Server 2005 installed on the same computer.
- A computer running on Vista cannot be configured to be an alarm provider and also have InTouch WindowViewer on the same computer configured to generate alarms. Only one of the two will function properly as an alarm provider.
- Windows Vista does not support NetDDE. ArchestrA Symbols that use 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. Windows Server 2003 and Windows XP Pro still support NetDDE.
- Windows Vista security prevents started Windows services from interacting with desktop objects. When Application Server 3.1 SP1 is installed on a computer running Vista, scripts do not run correctly if they include the InTouch ActivateApp() and SendKeys() functions. Windows Vista prevents these functions from interacting with desktop objects to start Windows programs or send keystrokes to these programs.
Using Multiple Network Interface Cards with Windows Vista
If you are using multiple network interface cards (NICs), you must configure certain settings for the firewall or else a remote Vista node cannot connect to the Galaxy Repository node.
A connection in Vista is a term used to define a network interface card (NIC), its settings and the settings of whatever the NIC is connected to. Under certain circumstances, the connection on your computer can change if, for example, the IP address on the computer to which you are connected changes. Your computer's connection can be affected by external factors. During computer startup, and each time a connection changes, Vista goes through an "Identifying" process to determine which profile should be assigned to the connection.
A profile is a collection of firewall settings that can be applied to a connection. There are three profiles currently defined in Vista: “Domain”, “Public” and “Private”.
- The Domain profile is assigned automatically to a connection if a domain controller for the domain to which the computer is a member is found on the connection.
- The Public profile is designed to keep the computer from being visible to other computers on the network. Network discovery is turned off for the Public profile.
- The Private profile is used for a more trusted environment. Network discovery is turned on for a Private profile. Firewall exceptions and rules can be created on any or all of these profiles.
This is important because the OS Configuration utility and the Vista Firewall utility apply their firewall exceptions to the Domain and Private profiles only.
As previously noted, you can specify which profile you want assigned to a connection as long as that connection is not a Domain connection. This is done through the "Network and Sharing Center". Click on the Network icon in the right side of the task bar and then click on one of the networks that is shown. You can change a connection from a Public profile to a Private profile. The firewall calls these settings "Profiles" but the network calls them "Location types."
On computers using dual NICs, the first NIC is normally connected to the domain and is assigned the Domain profile automatically. The second NIC is typically assigned the Public profile.
The first issue is that your entire computer (all connections) is restricted to the most restrictive of the profiles assigned to any connection. So if the second connection was assigned a profile of Public, none of the firewall exceptions set by the OS Configuration or Vista Firewall utilities will be allowed. The exceptions were set for Domain and Private only, not Public. You must set the second connection to the Private profile for any of the firewall exceptions to work.
The second issue is that it appears that a restart of your computer, or even a restart of a computer to which you are connected, can change your connection back to the Public profile. Once again the firewall exceptions will not be effective. You'll have to change the connection back to the Private profile after each restart or a restart of the connected computer.
To avoid these NIC issues and prevent the “Identifying” process from taking place on a connection and changing the assigned profile, certain items must be present in the definition of the connection. Follow the rules below:
- If you have only one NIC, no action is required. The profiles and firewall rules are automatic.
- If you have two NICs follow the actions below:
- If the second NIC is not physically connected to anything (that means no wire in it), no action is required. The profiles and firewall rules are automatic.
- If the second NIC is connected, it MUST be configured. Follow the rules for configuring a normal redundancy setup. Vista will identify this NIC and assign it a Private profile. If the NIC is not configured, Vista will assign a profile of Public to this NIC and cause all of the Wonderware product firewall exceptions to be deactivated on all NICs. For the NIC to be configured properly, give it an IP address, sub net mask and gateway address. The gateway address can be the same as the IP address. Usually these addresses will be the internal, non-routable addresses like 192.168.0.x or the 10.x.x.x range.
- If you have more than two NICs, make sure all connected NICs are configured with an IP address and default gateway address and have been assigned a profile of private.
Installing Application Server
The Application Server Installation Help (Install-AppServer.chm) located in the root folder of the installation CD includes detailed installation and upgrade instructions. Make sure the target computers that you want to install Application Server version 3.1 SP1 components on meet third-party software requirements.
You must install Wonderware Historian 9.0 Patch 02 to use time propagation and late data from the Wonderware Application Server to the Historian.
Upgrading to Version 3.1 SP1 from an Earlier Version of Application Server
After the hardware and software requirements are met, you can upgrade to version 3.1 SP1 from the following versions of Application Server:
- Version 2.1, including all patches and service packs
- Version 2.5, including all patches and service packs
- Version 3.0, including all patches and service packs
- Version 3.1
Because the hardware and software requirements of Application Server 2.0 are not compatible with those of Application Server 3.1 SP1, you cannot directly upgrade from Application Server 2.0. But, you can migrate applications developed with version 2.0 Patch 01 to version 3.1.
Upgrade Limitations
The following limitations apply when upgrading existing Application Server components to version 3.1 SP1:
- Before upgrading the GR node, all deployed nodes must be at the same version and there should be no connected clients.
- Before upgrading a visualization node, the InTouchViewApp AutomationObject should be shut down.
- Uploading application run-time changes from a non-upgraded node is not permitted.
- InTouch HMI must be upgraded to version 10.1 if it is installed on the same computer that has upgraded Application Server version 3.1 or 3.1 SP1 components.
- If Wonderware Historian is installed on the same computer with Wonderware Application Server, you must install Wonderware Historian 9.0 Patch 02 before upgrading to Wonderware Application Server 3.1 or to Application Server 3.1 SP1.
Updating Wonderware Application Server 3.1 with SP1
- Install the service pack on the Application Server nodes after installing the service pack on the Galaxy Repository node.
- Where possible, exit all applications that are running. To avoid potential platform and engine shutdown issues during the patch installation, we recommend the engines and platform be set off-scan then manually shutdown prior to running the installer.
- To install Service Pack 1:
- Open the ArchestrA System Management Console (SMC).
- Expand Platform Manager.
- Login to the Galaxy.
- Select the Platform for which Service Pack 1 is to be installed.
- From the Right pane, select one engine at a time. Engines hosting DI objects should be set off-scan and shutdown last.
- Right-click the engine and set it off-scan.
- Right-click the engine and shut it down.
- Shutdown the platform.
- Exit the System Management Console prior to installing the patch.
- After Service Pack 1 is applied, you will be prompted to restart the system.
- Do not deploy objects marked with software upgrades until the Galaxy nodes have been updated.
- Platforms containing redundant engines must be updated together.
- If InTouch 10.0x and Application Server 3.0x are installed on the same node, they both must be upgraded to Application Server 3.1 or Application Server 3.1 SP1 and InTouch 10.1.
Migrating Applications to Application Server Version 3.1 and 3.1 SP1
There is no migration required from version 3.1 to 3.1 SP1. You can migrate applications from the following earlier versions of Application Server to version 3.1 and 3.1 SP1:
- Version 2.0 Patch 01
- Version 2.1, including all patches and service packs
- Version 2.5, including all patches and service packs
- Version 3.0, including all patches and service packs
GR Node Migration
For versions earlier than 3.1, as listed in the preceding topic, the existing database schema is migrated to the new version 3.1 SP1 schema. For versions earlier than 3.1, as listed in the preceding topic, data from the existing schema is migrated to the new version 3.1 SP1 schema. Configured Wonderware Historian nodes are saved in the new schema. The GR node migration fails if the GR node is used as a run-time node for another GR. No migration is required from version 3.1 to 3.1 SP1.
Resolved Issues–Application Server Version 3.1 SP1
Wonderware Application Server version 3.1 SP1 resolves the following issues. The issues are listed by their Change Request number:
| L00079297: | Cannot import objects if the configuration version is older. |
Resolved Issues–Application Server Version 3.1
Wonderware Application Server version 3.1 resolves the following issues. The issues are listed by their Change Request number:
| L00046232: | In a UserDefined object, the Time Deadband option of a State alarm for a discrete field attribute is similar to the Time Deadband option for an analog attribute in a limit alarm. |
| L00049932: | You receive a "Could not resolve reference" error message for a .desc attribute when saving an instance of a UDO object locked at the template level. |
| L00051580: | After importing a Galaxy Load in the IDE with a hierarchy of Platforms, RedundantEngine, and Area objects, the backup engine is deleted in IDE and the primary engine icon is replaced with a normal engine icon. A Galaxy Load is performed with the "Replace Entire Instance" option. The "Replace Entire Instance" option only deletes the objects that have no hosted child objects. |
| L00054247: | IDE performance slows significantly after you add more than 100 field attributes to a UDO. |
| L00057894: | The calculated WinPlatform.CPULoadAvg value is incorrect for a platform running on a computer with a dual core processor. |
| L00059983: | Generating an alarm does not populate the user name or full name into the Alarm Record reported to the Distributed Alarm System if the Galaxy is configured for Galaxy Security and a user is logged on. |
| L00061480: | When individual bits are manipulated within a field attribute of type integer using a script within the same UserDefined object, only the value associated with one bit gets manipulated instead of all the bits that are changed in the script. |
| L00063314: | The Application Server Alarm Priority range is 0 to 999. The InTouch Alarm Priority Range is 1 to 999. When 0 is entered as alarm priority from Application Server, an alarm priority of 1 is actually logged in alarm database and shown in the InTouch AlarmView summary control. |
| L00064528: | An object with a reference to "MyContainer" that is renamed and moved between areas loses the binding reference and shows the warning "Could not resolve reference MyContainer.XXX in attribute -XX.XXX". |
| L00064546: | An InTouch client application running on a non-upgraded remote node cannot see an alarm generated on another remote node that has been upgraded with Application Server. |
| L00066957: | Cannot deploy any object if the computer's Windows DEP configuration is set to /noexecute=AlwaysOn. |
| L00067495: | Migrating an Application Server version 2.5 Galaxy with FMM objects fails with errors, and the migration process hangs in an infinite loop. |
| L00067697: | A large cascade deploy does not complete because a Redundant engine was stopped by the Bootstrap while it was starting up on a remote node. |
| L00068078: | A cascade deploy of over 1000 objects were deployed off scan, but marked as undeployed without error messages. |
| L00068433: | If you shut down the Wonderware Historian and then immediately restart the computer, frequent disconnects/reconnects occur for MDAS clients, such as the Wonderware Application Server. This fix requires Wonderware Application Server 3.1 and Wonderware Historian 9.0 Patch 02. |
| L00069976: | Application Server scripts calculate Quality incorrectly for expressions containing Boolean AND or OR operators. |
| L00070352: | A radio button graphic shows only one button with a title Unresolved Reference the first time the IDE is started. |
| L00070995: | Deploying or undeploying a GRPlatform of over 170 remote nodes takes several hours and error messages are written to the log. |
| L00071061: | Backing up a large Galaxy fails because of insufficient disk space without a warning message written to the logger. |
| L00071079: | When uploading run-time changes for an object with a symbol, the revision version does not remain consistent with the configuration version. |
| L00071206: | Users can acquire User Configuration permissions with any security mode. |
| L00071647: | The OnShow script in an ArchestrA graphic appears to run, but the script does not set an attribute. (See SR14811879) |
| L00072015: | When an FSGateway is deactivated on an ApplicationObject server node, the SMC and ObjectViewer become unresponsive, and platform communications are disrupted. |
| L00072074: | Communication failures during a cascade deployment of a large number of objects cause the deployment to fail. |
| L00072300: | When a client control is deleted and a new version of the client control is imported from a remote IDE, an ArchestrA Symbol referencing the client control will show Version 1 on the remote IDE and Version 2 on the Galaxy Repository IDE. This is a mismatch of versions. (See SR103112086) |
| L00072450: | An attribute value from the CheckedInPackage of an object using IGalaxyFX interface cannot be obtained because the Check Out and then Check In operations fail when done for an instance of custom ArchestrA object. |
| L00073495: | A Galaxy backup does not work correctly if the ArchestrA IDE is not installed on the same computer. |
| L00073550: | The graphic element reference list is incomplete, or it is corrupted. The error message "Failed to get Graphic element reference list" appears in the SMC Logger. (See SR23515471) |
| L00074841: | An ApplicationObject fails to deploy when an InternationalizedString Array in the object is modified using GRAccess. |
| L00075206: | Customized graphic text is lost after group change. (See SR14811926) |
| L00075453: | A WinPlatform object Remote Activation Failure error occurs when you attempt to deploy the object to a node with a name greater than 15 characters. |
| L00075663: | When Application Server and Factelligence are installed together, users can successfully log on from the Configure Galaxy dialog box without a valid password or user ID. |
| L00075763: | Custom property links for ArchestrA symbols do not accept the following special characters that can be used in InTouch tag names: _ (underscore), - (hyphen), $ (dollar), % - (percent), and &. - (ampersand). |
| L00075800: | MX References do not start in scripting; .InputSource in ArchestrA Graphics does not start in scripting. The MX References do work on display the link and in a Custom Property. (See SR15010810) |
| L00075917: | A Galaxy load operation that uses the Only Update Changed Attributes option forces all modified objects to a checked out state. |
| L00076426: | An exception occurs while checking in a derived template with ArchestrA graphic symbols and more than 1000 instances. |
| L00076900: | Warning "Could not find embedded graphics" appears after a template and its instances of a Galaxy are exported as an aaPKG file, and are then re-imported into a new Galaxy. (See SR33430263) |
| L00077680: | Watch window does not always update with the current Float Array values after copying values from another Float Array or changing values from the ObjectViewer |
| L00078407: | Exporting the contents of the Galaxy Repository fails with warning messages written to the logger. |
| L00079430: | Removing a string from a symbol with Value Display Animation in a primary language also removes the strings in secondary languages. |
| L00081739: | The Graphic toolbox pop-up window and the Graphics tab preview window thumbnails show "not found" when an application object instance containing symbols with date time picker is imported in a new Galaxy. |
| L00087227: | A Wonderware Application Server 3.0 Galaxy with an imported InTouchCompactApp aaPKG file to Wonderware Application Server 3.1 SP1, errors are logged in the SMC Logger. |
Known Issues–Application Server Version 3.1 SP1
This section describes all known issues identified in Application Server Version 3.1 SP1.
| L00089272: | When you upgrade from Application Server version 2.5 to version 3.1 SP1, the following error message is shown: "ArchestrA.Configuration.PackageServerNet.PackageServerNet instance not properly disposed." The error message is informational. No action is required. |
| L00089829: | When upgrading from Application Server version
3.1 to SP1, if you install the Service Pack without first manually
shutting down all platforms and engines, you may encounter NMXService
shutdown issues and the following errors might appear in the log: 7901 2/26/2009 10:56:24 AM 4076 4832 Error NmxSvc Unknown error 0xC0000005 (c0000005) raised. 7902 2/26/2009 10:56:24 AM 4076 4832 Error NmxSvc Unknown error 0xC0000005 (c0000005) caught at line 2128 in NmxControler.cpp (in Y:\AAMXCoreDev\src\NmxSvc\). If these errors appear, you may disregard them. No further action is required. We recommend following the steps outlined earlier in this Readme under the heading "Updating Wonderware Application Server 3.1 with SP1". Upgrades from Application Server versions 2.5 and 3.0 to version 3.1 SP1 do not encounter this issue. |
| L00089937: | Importing a major version of an object instance that is on a platform which is currently deployed will result in aaPIM logged messages. To resolve the issue, the platform hosting the object must be undeployed to clear the errors. |
| L00089942: | When you upgrade from Application Server version 3.1 to version 3.1 SP1, the following warning message appears in the log: "Failed to patch the galaxy." The logged message applies only to Galaxies from Application Server versions earlier than 3.1. No action is required. Galaxies earlier than version 3.1 will be patched upon connection. |
Known Issues–Application Server Version 3.1
This section describes all known issues identified in Application Server Version 3.1. The known issues are grouped by function.
| L00069519: | In a redundant load sharing environment, the
cascade deployment of a backup platform does not deploy InTouch ViewApp
instances, if the redundant AppEngine has InTouch proxy objects
configured. Backup redundant object errors are logged. After the InTouch ViewApp deploy fails, it can be manually re-deployed. |
| L00071843: | ObjectViewer does not handle a returned WriteStatus of "Pending" properly because it does not wait for the final SetReponse() return message and the dialog box normally shown for writes that fail does not appear. |
| L00076557: | Opening and closing a view window when "Advanced Communication Management" is enabled for the Galaxy may cause a different timestamp to be returned for the attribute from the DAServer, even though nothing has changed on the device. |
| L00077487: | During tag registration, Wonderware Historian
discards the value for SampleCount (isSamples) provided by Application
Server. This issue is discussed in CR L00077833. Before installing Wonderware Application Server, apply Wonderware Historian 9.0 Patch 02 to resolve this issue. |
| L00077490: | Importing a client control from a Galaxy imports another version of the same client control if the other version resides in a different Galaxy on the same node. |
| L00078221: | After you migrate an Application Server 2.1
application to Application Server 3.0 or later, the wrong value is
returned for the .NET ToLocalTime() function. Application Server 2.1 supports .NET 1.1, while Application Server 3.0 supports .NET 2.0. The DateTime structure in .NET 2.0 includes a new Kind property that indicates whether the time represents a local time, a Coordinated Universal Time (UTC), or whether UTC or local time is not specified. For more information, see the following Microsoft documentation: http://msdn.microsoft.com/en-us/library/system.datetime.aspx To migrate an Application Server 2.1 application to version 3.0 or higher, you must modify scripts that use the ToLocalTime() function. Use the new Kind property (DateTime.KindProperty) and specify the time before you run the ToLocalTime() function. For example: dim aTime as System.datetime; dim aTime2 as System.DateTime; aTime = me.lastpolltime; aTime = system.datetime.SpecifyKind(aTime, system.dateTimekind.utc); me.locallastpolltime = aTime.tolocaltime(); |
| L00078446: | The ArchestrA Symbol Editor stops responding when you edit the "format string" property of the “checked list box” client control. |
| L00078465: | Dates earlier than 1970 are not valid for
purposes of the LogDataChangeEvent() script function. Using a date earlier
than 1970 sends a warning message to the logger. Use a date on or after 1/1/1970 when using the "LogDataChangeEvent()" script. |
| L00079595: | Attempting to import a client control with the
ArchestrA IDE fails if the file is located at a remote network location.
Copy the client control file to the local computer where the ArchestrA IDE is installed to import operation. |
| L00081837: | The following error message appears when a non-upgraded IDE node (earlier than ApplicationServer 3.0 SP2) tries to connect to an upgraded Galaxy Repository node. Error message: "IDE cannot connect to remote GR node <name> because it is an older version <number> than this IDE version supports." |
| L00082886: | Area objects are not deployed after performing a
cascade deploy of a Galaxy migrated from version 3.0 to version 3.1 of
Application Server with Vista as the operating system. Perform the following as a workaround. 1. Click Start, then Run. The Run dialog box appears. 2. In the Open field, type OptionFeatures.exe 3. Click OK. The Windows Features dialog box appears. 4. Expand the following: * Microsoft message Queue (MSMQ) Server * Microsoft message Queue (MSMQ) Server Core 5. Place a check to the left of: * Microsoft message Queue (MSMQ) Server * Microsoft message Queue (MSMQ) Server Core * MSMQ Active Directory Domain Service Integration * MSMQ HTTP Support * MSMQ Triggers * Multicasting Support * MSMQ DCOM proxy 6. Click OK. The Windows Features dialog box closes. 7. Deploy the Automation Objects. |
| L00083270: | Spaces are not imported as part of the translation for the selected language. |
| L00083828: | There are inconsistencies between the selected language and the strings that are shown. |
| L00083909: | InTouch applications receive Quality Status and Locale information from the deployed Galaxy. InTouch applications cannot receive data from an undeployed Galaxy. |
| L00085806: | The font used for graphics in ArchestrA symbols
does not render properly in the Symbol Editor and on print outs, if the
DPI of the screen or printer is less than or greater than 96-dpi. Wonderware does not support running the product in DPIs other than 96 DPI. |
| L00086625: | When you upgrade nodes from Wonderware Application Server 3.0 Patch 03 to 3.0 SP2, the following warning from msiexec appears: "GetArchestrAInstallPath(): Failed to Read the Registry ArchestrA install path Key". |
| L00087046: | An embedded symbol is lost after swapping symbol names. VERL (Visual Element Reference List) corruption is artificially causing a circular reference. |
| L00087247: | InTouchViewApp fails to undo a checkout when
there is a file-lock within the CheckOut folder. You should not attempt to
check-in the InTouchViewApp. Fix the file-lock issue, and perform the "undo-checkout" again. |
| L00087305: | When you rename a referenced symbol while an object editor is open, the reference to the renamed symbol may be lost. |
| L00087471: | The background reference binding thread may stop
processing because of a database connection failure. The following message
is logged in the System Management Console: “Warning WWCdi
CRefString(TagName Validation). Database connection is no longer valid.”
You must restart the aaGR.exe process to reestablish the connection to the database server. |
| L00087752: | You must restart the aaGR.exe after you import an
object with a minor version increment, if the object is written in
.NET. The issue may occur for ApplicationObjects written in .NET with the ApplicationObject Toolkit 3.1, versus ApplicationObjects written with an older version of the ApplicationObject Toolkit. Restart of the aaGR.exe is required if all of the following apply: • DotNetAppObject version 1.0 is loaded in the Galaxy • An object vendor creates a new minor version of DotNetAppObject version 1.1 • An IDE user imports the new .aaPKG file with DotNetAppObject version 1.1 into the Galaxy that has DotNetAppObject 1.0 loaded. You must restart aaGR.exe for the new object to be recognized and deployed to the IDE nodes. |
| L00088669: | Upon migration, the “Network Address” field in the Platform is set to blank if the previously used network address exceeds 15 characters. Windows only supports up to 15 characters for computer names. |
ArchestrA Alarm Client
This section lists current issues that remain in the ArchestrA Alarm Client (Control).
| L00080966: | Unable to browse all supported methods and properties
from the Alarm Control's Element Browser. Also, many additional unwanted
methods and properties appear in the Element Browser. This is due to
limitation from the ArchestrA framework.
Workaround: Use the Guide to the ArchestrA Alarm Control as reference. Chapter 4 "Scripting the Alarm Control" contains all supported methods and properties including syntax and in most cases examples. |
| L00082738: | Query filters added at run time are not saved if you
switch back to WindowMaker.
Workaround: Export the query filters you create at run time to an XML file. After switching back to WindowMaker, import the query filters from the XML file. |
| L00084764: | If you change the Query String of the Default Query after adding filtering criteria using the Query Filter editor, then the additional filtering details are removed. |
| L00085789: | It is not possible to hide more than 300 single alarm records. If you need to hide a larger number of alarms, consider hiding the group or priority instead. Hiding one group instead of many individual alarm records in that group only creates one hidden item in the Hidden Alarms dialog box. |
| L00086092: | It is not possible to hide any alarm records if the alarm query is configured for a large number of providers. If the alarm query is too long, when you attempt to hide alarms, a message is shown in SMC Log Viewer and a message "The maximum limit of hidden alarms has been reached" appears. To avoid this problem, consider using multiple Alarm Controls or switching the alarm query between several sets of alarm providers. |
| L00086127: | The scriptable properties and methods to hide
alarms continue to operate when the alarm control is in the historical
mode, although the historical alarms are not hidden. Acting on historical
alarms with a hide request should be avoided. This can cause the control
to use excessive CPU. In the script that hides alarms, set the client mode to “1” or “2” (“Current Alarms” or “Recent Alarms and Events”), before performing a hide action. |
ArchestrA Trend Client
This section describes all known issues identified in the Trend Client.
| L00082107: | When you import the Trend Client package (.aaPKG) into the IDE, some unwanted warning messages appear in the logger. | ||
| L00085245: | When you configure the Pen Type (Pen.TrendType) as 'Auto' and the default value of Historian is not available, the Trend Client generates Plot type as line during run time, regardless of the data type (real or integer). | ||
| L00086210: | If you use a relative reference for a custom property
in the pen configuration, the Trend Client does not resolve the pen
configuration during run time.
The Trend Client supports custom properties for absolute references, but does not support custom properties for relative references. | ||
| L00086285 : | The Trend Client does not copy any background image
files to another node and, therefore, does not show a configured plot
image on a client node.
To view the plot image on a client node:
| ||
| L00087611: | The Element Browser or Events page of the Trend
Client shows a number of unwanted events and properties. Also,
the Element Browser or Events page does not allow you to browse all
the supported methods, properties, and events. This occurs because of
a limitation of the ArchestrA framework.
For information about all the supported methods, properties, and events, see the Trend Client documentation. | ||
| L00087617: | The AddPen method does not work when you specify a
relative reference or an absolute reference as a history source
name.
You must specify the value for the history source name in the script if you add a pen using a script. | ||
| L00087683: | A data loss occurs when you initialize the trend with history data and refresh the trend chart. |
Application Server Documentation Issues
The following table lists all documentation corrections to Application Server 3.1 SP1 documentation.
| Item | Location of Change | Existing Documentation | Change |
| 1 | Guide to
ArchestrA Alarm Control, aaAlarmClientControl.pdf, p.113 ArchestrA Alarm Control Help, aaAlarmClientControl.chm, "Alarm Control Properties" |
n/a | The description and
syntax of the ShowGroupByHeader property need to be added to the Alarm
Control Properties section after the ShowGrid property. The following
descriptive content needs to be added: The ShowGroupByHeader property is a read-write Boolean property to show or hide the column grouping label at the top of the run-time Alarm Control in the historical mode. You can set the ShowGroupByHeader property to true to show the label "Drag a column header here to group by that column". |
| 2 | Guide to
ArchestrA Alarm Control, aaAlarmClientControl.pdf p.27 ArchestrA Alarm Control Help, aaAlarmClientControl.chm, "Showing Current Alarms or Recent Alarms and Events" |
For
Alarm Controls hosted by Automation Object templates or instances, you can
specify one of the following alarm queries:
For more information on absolute alarm queries, see Alarm Queries in the InTouch HMI Alarms and Events Guide. |
For
Alarm Controls hosted by Automation Object templates or instances, you can
specify one of the following alarm queries:
For more information on alarm queries, see Alarm Queries. |
| 3 | Creating and Managing ArchestrA Graphics User’s
Guide (aaGraphics.pdf), "String Substitutions and Language Switching" section, page 426 Application Server Help (IDE.chm), "String Substitutions and Language Switching" topic |
n/a | Add the following
text after the first paragraph: If you perform a first-time string substitution on an embedded symbol in the primary language, that substitution is shown in the secondary languages. You can then perform a substitution in the secondary language to create a string substitution specific to the secondary language. If you perform a first-time string substitution on an embedded symbol in a secondary language, the substitution is also applied to the primary language, because the translated string that previously existed for the primary language is no longer valid. Because the primary language value is changed in the symbol, this string applies to all secondary languages configured. You can then perform a second substitution in the primary language, which will apply to all secondary languages except the ones that have had a specific substitution set. If you perform a string substitution in a secondary language with an existing string substitution in the primary language, the new substitution is applied to the secondary language only. |
Saving the Date Timestamp as Historical Data
If slow updates for real-time data values are received from an I/O source and an intermittent network disconnect occurs, the timestamp of the first data value of a historized attribute uses the AppEngine’s timestamp instead of the source’s timestamp. In the following example, in row number 4, the value "30" is sent again to the historian, but the timestamp is the AppEngine timestamp and not the actual timestamp of “2008-11-24 18:50:41.061” when the value of 30 was generated from the I/O source.
|
DateTime |
TagName |
Value |
Quality |
QualityDetail |
OPCQuality |
|
2008-11-24 18:48:30.081 |
Realtime_Client.ival |
20 |
133 |
44 |
192 |
|
2008-11-24 18:50:41.061 |
Realtime_Client.ival |
30 |
0 |
192 |
192 |
|
2008-11-24 18:51:38.666 |
Realtime_Client.ival |
NULL |
1 |
24 |
0 |
|
2008-11-24 18:52:06.670 |
Realtime_Client.ival |
30 |
0 |
192 |
192 --> Row number 4 |
|
2008-11-24 18:53:22.988 |
Realtime_Client.ival |
40 |
0 |
192 |
192 |
If slow updates for late data values are received from an I/O source and an intermittent network disconnect occurs, the timestamp of the first data value of a historized attribute is modified to maintain the time sequence. In the following example, in row number 4, the value "30" is sent again to the historian, but the timestamp is modified by adding 5 milliseconds to previous timestamp of the NULL data value. Note that a QualityDetail of 704 is stored for the data value in row number 4.
|
DateTime |
TagName |
Value |
Quality |
QualityDetail |
OPCQuality |
|
2008-11-24 18:48:30.081 |
Latedata_Client.ival |
20 |
133 |
44 |
192 |
|
2008-11-24 18:50:53.624 |
Latedata_Client.ival |
30 |
0 |
192 |
192 |
|
2008-11-24 18:50:53.625 |
Latedata_Client.ival |
NULL |
1 |
24 |
0 |
|
2008-11-24 18:50:53.630 |
Latedata_Client.ival |
30 |
0 |
704 |
192 --> Row number 4. |
|
2008-11-24 18:53:26.863 |
Latedata_Client.ival |
40 |
0 |
192 |
192 |
Application Server Documentation
The Application Server product library consists of a set of Portable Document Files (PDF) located in the UserDocs\English folder of the Application Server installation CD. You need Adobe Reader installed on your computer to view Application Server documentation. You can download the latest version of Adobe Reader from the Adobe Corporation web site:
http://www.adobe.com/products/acrobat/readstep2.html
After installing Adobe Reader, double-click on a PDF file with your pointing device to view the book with Adobe Reader. You can also open a book with the Adobe Reader Open command from the File menu.
Application Server installation instructions are located in the root folder of the Application Server installation CD as an online help file. You can view these instructions by clicking the Installation Guide button in the Application Server installation program.
Product documentation is also available with Application Server online help.
Documentation Set
The Application Server documentation set includes the following guides:
- Wonderware Application Server User’s Guide. Explains configuring and deploying 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).
- Application Server Scripting Guide. Reference for the scripting language in 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.
- Application Server Installation Guide. Explains information about installing the product.
- InTouch HMI and ArchestrA Integration Guide.
Explains how you can use the ArchestrA Integrated Development Environment
(IDE) to manage InTouch applications so that you can use symbols you create in
the ArchestrA Symbol Editor. This guide is available on the InTouch HMI
installation CD.
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.
Searching Application Server Books with Adobe Reader
The Application Server version 3.1 books are delivered as an Adobe PDF package, which provides a master index of all books. Using Adobe Reader, you can simultaneously search for a specific topic across all books that belong to the Application Server product library.
To search for information across all Application Server books simultaneously
- Open Adobe Reader.
- Press CTRL+SHIFT+F or select Search from the Edit menu. The Search dialog box appears.
- Type the word or phrase that you want to search for in the Application Server books.
- In the Where would you like to search area, select the option to search all PDF books.
- If necessary, locate the Application Server version 3.1 PDF package located on your Wonderware CD or on a network folder containing copiesoftheApplicationServerPDFbookfiles. Afterproductinstallation,thesefilescanbefoundat:<driveletter>:\Program Files\ArchestrA\Framework\Docs.
- Click Search. Adobe Reader lists the Application Server books that contain a match for your search criteria.
- Click on the links to open the Application Server book to the topic containing the information that meets your search criteria.
© 2009 Invensys Systems, Inc. All Rights Reserved.
