Wonderware Application Server 3.1 SP1 is released. Application Server 3.0 includes the following enhancements and new features.

Updated Archestra Integrated Development Environment (IDE)

• Improved organization tools in Template toolbox, including sub-toolsets
• Views that you can auto-hide and pin
• Floating and dockable views

ArchestrA Symbol Editor

The ArchestrA Symbol Editor is available from within the IDE. You can create graphic symbols that you can use within your InTouch applications. The Symbol Editor:

• Includes all features and functions of InTouch WindowMaker.
• Includes drawing elements not available in WindowMaker, such as curves, closed curves, arcs, pies, chords, text box, status indicators, and Windows Controls.
• Includes element properties not available in WindowMaker, such as colors, transparency, rotation, lock, and fill.
• Supports scripting.
• Supports custom properties.

Deploy Improvements

• For a single user, multiple objects can be deployed to two or more platforms simultaneously.
• Multiple threads are used for deployment, thus increasing performance.
• All objects that are being undeployed from an engine are taken off-scan first, freeing up time for the undeploy.

Check-in Improvements

Template changes to selected elements are optimized for:

• Scripts (locked)
• UDAs (locked)
• Visual elements (graphics)

Script Improvements

• Data change scripts can be triggered by either value or quality changes. If you select quality, data change will include both value and quality changes. The default data change will be a value change trigger.
• Instead of always firing on object startup, a data change script only triggers if the expression changed since the last run before the object shut down.

Incremental Upgrades

• Deployed Platforms can be left running during a Galaxy Repository or IDE node upgrade.
• Run-time Platforms can be a mix of old and new versions.

Read-Write Performance Improvements

• Improved speed of reads and writes to the field, especially total turnaround time of a write from the InTouch HMI.
• New functionality where external input/output between engines and to/from the field is processed during the engine idle phase.
• New ReadWrite Interrupts functionality where external input/output between engines and to/from field can optionally be processed within the engine s execution phase.  Two options exist, Standard and Full modes.
  • In standard mode:
    • DIObjects send writes to the field (DAServers or I/O Servers) multiple times within a scan, as objects are executing, rather than waiting until the idle period. This allows writes to the field to occur more quickly, allowing for faster turn-around and confirmation.
    • Updates are published to visualization nodes (HMI) multiple times within a scan, as objects are executing and changing, instead of just during the idle period after all objects execute.
  • In full mode includes the functionality of standard mode, plus:
    • DIObjects get updates from the field (DAServers or I/O Servers) multiple times within a scan, as objects are executing, rather than waiting until the idle period.
    • ApplicationObjects receive write requests that come in during the middle of the execute phase, and process them if the object has not already executed within this phase.
    • ApplicationObjects receive subscription updates from other engines that arrive during the middle of the execute phase, if the object has not already executed within this phase.
    • Changes to ApplicationObjects that occur within middle of execution phase are published to objects that reside on other engines without waiting until end of a scan.
    • Writes by ApplicationObjects that occur within middle of execution phase are sent to all objects on other engines without waiting until end of a scan.

Redundant DIObject Improvement

• A configurable ping item attribute is now available to detect connection status of inactive DIObject. This ensures the true status of the physical link to the field.

Redundancy Improvements

• Upon a switch from active to standby, the AppEngine process can be restarted automatically. This frees all memory and other resources.

Device Integration Improvements

• DIObjects are supported in load sharing environment. This allows two DI network objects of same type (for example, ABTCP) to run on same node.
• In a redundancy scenario, references to an off-engine DIObject’s dynamic attributes are not removed. The dynamic attributes remain in the DIObject while the failover is occurring, or until a timeout occurs.
• During shutdown, failover, or undeploy of DIObjects:
  • Item removal for scan groups is optimized in blocks.
  • All objects are shut down in reverse of execution order, independent of whether DIObjects are involved or not. An exception is for Areas. They are shut down after their objects.

Galaxy Backup

• You can use an existing Galaxy as the base for a new Galaxy when created with the IDE.

Toolkits

• Enhancements have been added to the GRAccess Toolkit, such as the ability to browse and configure security.
• A new MxAccess Toolkit allows you to create a program that:
  • Connects to an ArchestrA Galaxy.
  • Subscribes to one or more attributes and receives data updates from these attributes.
  • Writes new values to these attributes, subject to user authentication