Re: Archestra Symbol Factory.epub
Brie Hoffler
In prior releases, Application Server restricted Windows client operating systems (for example, Windows 7 or 8.1) to a single node installation in which all Wonderware System Platform products were installed on a single computer. That restriction is now relaxed. In Service Pack 1, up to five remote nodes can be supported by a GR node with any supported Windows client operating system. This means that Windows Server is only required if there is more than one GR node or if the GR node is connected to more than five remote nodes.-->Improved IT ComplianceTo increase IT security, Application Server no longer requires SysAdmin privileges for most SQL Server operations, including those related to creating, migrating, backing up, or restoring Galaxies. Certain operations that involve prior versions of Application Server will still require SysAdmin credentials. Examples of this include upgrading from a previous version of Application Server, or creating a Galaxy from a CAB file from another computer that uses an older Galaxy. See "Setting the SQL Server Security Mode" in the Wonderware System Platform Installation Guide for more information.Support for Running a GR Node Hosted on SQL Server Using a Non-Default PortThe ability to use a non-default TCP/IP port to connect to a SQL Server database for GR nodes has been added to Application Server 2014 R2 SP1. To support this capability, the SQLData object has a new configuration option. Improved Stability During Failover of Redundant AppEnginesA new AppEngine start-up algorithm prevents high CPU usage during failover of a redundant pair. CPU load balancing can be configured to ensure a smooth failover process as the standby partner starts. See the Wonderware Application Server User's Guide for more information.Find Checked Out Objects Search FunctionThe Application Server IDE has been enhanced with a new feature that allows users to easily find checked out objects. The Find dialog box now includes an option to search for checked out objects.Wonderware InTouch HMI 2014 R2 SP1Support Input and Display of Number Formats by Regional LocaleNumeric data can be entered and displayed in ArchestrA graphics in a format that matches the format of the country set as the regional locale on the computer running WindowViewer. During run time, numbers can be entered or displayed with a thousand separator and decimal point characters that match the number format of the selected country.The InTouch WindowViewer keypad now includes comma, period, and a thin space keys to enter numbers that match the format of the country set as the regional locale on the computer running WindowViewer. In addition, if the WindowViewer Follow regional settings for ArchestrA Graphics configuration option is selected, the keypad displays numeric values using symbols based on the regional settings.
Users can export a Modern application's Application Style Library from WindowMaker to a designated folder location as an XML file. Users can also import the Application Style Library to a Modern application to reuse the Quality and Status display, the Element Styles, and numeric format styles that were defined in another Modern application.Export ArchestrA Graphic Toolbox Symbols That Have Embedded Symbols from Automation ObjectsWhen exporting ArchestrA symbols from the Graphic Toolbox that have embedded symbols from automation objects in them, users see a dialog box with an option to export the associated objects hosting the graphics in the same operation. Export Localization Strings of Selected Symbols in Modern ApplicationsSymbols containing localized strings can be selected from WindowMaker's ArchestrA Graphic Toolbox to export the language strings to an XML file. Users can edit the XML file to translate the symbol strings and re-import to another set of symbols using Import ArchestrA Graphics option. Export Selected Symbols from the ArchestrA Toolbox in Modern Applications Exporting and importing ArchestrA symbols in Modern applications have been enhanced in Service Pack 1. Rather than exporting or importing the entire set of Archestra symbols, now one or more selected symbols can be exported or imported.The selected ArchestrA symbols are exported to an .aaPKG file to a designated folder location.
A History Summary custom property can be added to a symbol that references historical data collected over a specified period during run time. The Historian can transform this data to create a set of analog or state summary statistics that can be shown by ArchestrA graphic animation during run time.In Service Pack 1, the analog Last historical statistic has been added to the History Summary custom property. The Last historical statistic shows the last data value that occurred in a historical summary period.Include an Overridden Tag for Programmatic Symbol Exports A new XML attribute has been added to each symbol within the XML file containing ArchestrA symbols that have been programmatically exported. The attribute identifies whether changes have been made to the properties of the embedded symbols in a base symbol or not. This new Overridden attribute added to the exported XML file is essentially a "change flag".In Service Pack 1, an exported symbol that does not contain any changes to embedded symbol custom properties includes an Overridden attribute set to False, which is the default value. Overridden="False"The Overridden attribute makes it easier to programmatically identify symbols that have not been changed. Installation Option to not Install a Galaxy Repository on the InTouch Development ComputerIn prior releases, the Wonderware System Platform installation program automatically installed SQL Server Express when an InTouch development environment was going to be installed on a computer without SQL Server. An instance of SQL Server Express was required as a Galaxy Repository to support InTouch Modern applications. In Service Pack 1, the installation program includes an option to not install SQL Server on the InTouch development computer. This option is provided for customers who do not intend to create Modern applications and do not need SQL Server installed on their development computer.Wonderware Historian Server 2014 R2 SP1Replication to Wonderware OnlineIn this Service Pack, Wonderware Historian Server supports replication to Wonderware Online, our Managed Historian solution. When you set up a Tier 2 server, you can configure it to point to Wonderware Online.SQL Queries for Event BlocksWonderware Historian Server 2014 R2 introduced the ability to store alarms and events in history event blocks. Block-based alarm and event history is more efficient both for storage space and retrieval time. You can choose to store events either in the traditional database structure (A2ALMDB) or to history blocks. With Service Pack 1, you can use SQL queries on the new "Events" extension table with block-based alarm and event history. Improved Retrieval for Slow-Changing Cyclically-Stored TagsIn this Service Pack, Wonderware Historian Server includes retrieval improvements for slow-changing cyclically-stored tags that make data available for retrieval sooner. Wonderware Historian Client 2014 R2 SP1Support for Different SQL Server Default Port NumbersIf the default port for the SQL Server is changed, Historian Client can still connect to the server by specifying the new port number.Improvements to Query and Workbook Tools Related to Optimistic Quality RuleCustomers can use Query and Excel Workbook tools to retrieve data based on Optimistic quality rules.System Requirements and Guidelines
- Hardware Guidelines
- Operating System, Firewall, .NET Framework, and Virtualization Requirements
- SQL Server Requirements
- Third-Party Application Prerequisites
After the ArchestrA symbol is duplicated with a Save Asoperation, the visual element references contained within the WIN filesbecome unsynchronized with the visual element reference list of themanaged InTouch application. The possible result is that symbols showthe wrong graphic, appear as NOT FOUND, and may have references toanother graphic.
After the ArchestrA symbol is renamed, the visualelement references contained within the WIN files become unsynchronizedwith the visual element reference list of the managed InTouchapplication. The result is that symbols show the wrong graphic, appearas NOT FOUND, and may have references to another graphic.
The issue results from the client-side template cachenot being updated. This cache is based on the gobject ID and packageID, which do not change during the rename of a referenced ArchestrAsymbol. To update the VERL property of an InTouch managed application,close and restart the ArchestrA IDE, which refreshes the cache.
You can substitute public custom properties used as references in anembedded ArchestrA Symbol with alternate references. Only referencesfrom public custom properties can be substituted in an embeddedArchestrA symbol.
ArchestrA graphics make use of the client layer whenaccessing InTouch tags, and appear as a third-party client trying toaccess WindowViewer as a data server. As a result, ArchestrA symbolscannot communicate with InTouch tags when used with an InTouchViewlicense. Windows Server 2003 and Windows XP Pro still support NetDDE.
If you want to change the references for the same symbol usingArchestrA graphics, you can use an input control and the OwningObjectproperty to show data for other object instances on the sameWinPlatform. This allows you to configure a single symbol, but showdata for different object instances.
The following procedure explains how to configure an EngineGroupdisplay symbol, which has many data references and use a combo box toselect between three different AppEngines. The AppEngines are namedAppEngineA, AppEngineB, and AppEngineC. All of these AppEngines aredeployed.
aa06259810