Archestra ide 3.0 download

Install this file in the node that hosts the portal. Install this file in the node that hosts the ArchestrA License Server.

Additional Notes Antivirus Exclusions - The antivirus software exclusions list has been updated. Review the Antivirus Software Exclusions list. Click this Terminal Services Behavior link for more information about Terminal Services behavioral changes.

The IP address is that of the client computer connected to the session. Start the utility from the installed shortcut instead. 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. Resolved Issues This section documents important resolved issues broadly categorized as ArchestrA System Platform-level issues.

L : Unexplained system failovers on redundant engines with Windows Vista operating systems ceased with application of Windows Vista Service Pack 2. Try reinstalling the program to fix this problem. Express is not differentiated by the installation if already present in the system. L : You must manually install the language packs for the Wonderware Historian Client product by running the setup.

This behavior is a result of the browser service being disabled by default on the computer running the Windows Server R2 or Windows 7 bit operating system. The exception error is for the Windows call and not for the Wonderware Application Server product itself. Wonderware Application Server successfully uninstalls. Restart the database instance or computer. L : 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. L : 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. As a workaround, create an empty file named win. L : 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.

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.

As a workaround, identify galaxies by machine names rather than by IP addresses. Applications with charts or scripts may not migrate or run properly in those operating systems. L : Errors occur when deploying to a remote node after a node-by-node upgrade. L : The QI Analyst 8. A hotfix is available upon request from Customer Support. L : 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.

Cannot insert duplicate key in object 'dbo. The duplicate key value is , , , 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: Scan windows events in the Event Viewer for evidence that the transaction log is in fact full. If you confirm that the transaction log has exceeded size restrictions, do the following to remove the restriction: In SQL Server Management Studio, right click the galaxy database, then click Properties on the context menu.

In the Database Properties dialog, select the Files page. Locate Log Click OK. Complete the galaxy migration, then repeat these steps to reinstate a file size ceiling on the transaction log.

L : 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.

L : Multi-galaxy communication does not work on a computer where Application Server and the Historian have been uninstalled and Application Server has been reinstalled. 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. 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. Create a galaxy with a platform, and pair the nodes. On Node1, uninstall Application Server and restart the system.

On Node1, reinstall Application Server and connect to the same galaxy. 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. Un-pair and re-pair Node1 to get the new Discovery Service and pairing information from Node2.

L : In a multi-galaxy environment, you can pair galaxies by IP address rather than using a node name computer machine name. 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: Navigate to the Hosts file on Node1. Open the Hosts file in Notepad.

In Windows 7 and Windows R2 systems, you should right click the Notepad executable, and click Run as Administrator , then open the Hosts file from inside Notepad. On the same line as the IP address, provide a node computer name. Enter IP addresses and node computer names for each node identified by IP address to be unpaired. Save and close the Hosts file. You should now be able to unpair the galaxies. L : 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. 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.

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: Open the Configure ArchestrA Services utility. If you find a service instance with a duplicate port number on the same node: Undeploy the browsing service of the missing galaxy. Change the port number to a unique number for that node.

Redploy the browsing service instance. L : 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. L : Buffered data is not supported in a multi-galaxy environment. L : 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. 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.

Documentation This section describes the documentation that is available for the components of ArchestrA System Platform R2. Describes all of the features and main concepts in the InTouch HMI without going too deep into the technical and procedural details.

Describes how to create and manage InTouch applications locally and in a network environment. Describes how to work with data items in the InTouch HMI and connect your application to the physical devices in your plant environment.

Describes how to develop the graphical operator interface of an InTouch application. Describes how to create reusable templates for graphic symbols that can save you a lot of engineering time and effort. 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.

This guide includes a reference of the InTouch scripting language and functions. Documentation: Wonderware Application Server R2 v3. Explains configuring and deploying Wonderware Application Server applications. 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. 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. Documentation: Wonderware Historian Server R2 v 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. The InTouch security logon panel does not always reflect the new security mode for example, OS Group Based , which appears in the title bar.

This occurs if the user changes to several different security settings. This behavior occurs on computers that run different operating systems.

An Application Server node on a separate network from the other Application nodes and the Wonderware Historian 9. Set the time of the third node to be out of sync from the InSQL node. Deploying objects in a system with a large number of Areas more than can cause the SQL Server tempdb database on the InSQL node to consume a sizable amount of disk space on the historian system. This disk space can be released through a manual procedure on the InSQL node.

Please contact Wonderware Technical Support for details. McAfee Desktop Firewall 8. Turn off the firewall to solve these problems. The IEEE floating point format is only an approximation of an actual real number. Unless the real number is an even power of two, it cannot be represented exactly using the IEEE bit floating point format. The precision of an IEEE bit floating point number is approximately eight decimal places.

When you want to show a real number in an InTouch application, make sure the number does not exceed eight digits. The following floating-point number formats show valid real numbers within an InTouch application:.

An InTouch application should show the real number 2. But, the number 2. To ensure the value 2. If the number exceeds the eight digit maximum, the resulting number may be shown as 2. L The WinPlatform. CPULoadAvg attribute is not calculated correctly for a platform running on a dual core processor. If you have a constant load on system running on a dual core processor, the WinPlatform. CPULoad value. L When importing an object package containing ArchestrA graphics with. Net client control Event scripts, the user finds that the Event scripts are empty or non-existent in the graphics.

Create a new galaxy. Import the original aaPKG. Export just the client controls to cc. Change to the galaxy in which you want to import. Import cc. The following table lists all documentation corrections to Application Server 3.

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:. 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.

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. The Application Server version 3. Using Adobe Reader, you can simultaneously search for a specific topic across all books that belong to the Application Server product library. Before installing the service pack: Ensure that you create good known backups of all Galaxies.

Wonderware provided base default Galaxies are replaced during the service pack installation. Installing Wonderware Application Server 3. See L in the Known Issues section for special circumstances. If InTouch 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 Issues list has been updated. Click this Antivirus Software Issues link for details. Use the following links to the various sections of this Readme.

Hardware Recommendations : Hardware requirements remain unchanged since the initial release of Wonderware Application Server 3. Software Requirements : Several service pack updates have been distributed for Windows operating systems since the initial release of Wonderware Application Server 3. Important: Wonderware Application Server 3. Yes None Wonderware Application Server version 3. To update Wonderware Application Server 3. A non-updated Application Server node cannot connect to the Galaxy Repository node after the Galaxy Repository node is updated.

Where possible, exit all applications that are running. To avoid potential platform and engine shutdown issues during the service pack installation, we recommend the engines and platform be set to "off-scan" then manually shut down before to running the installer.

Expand Platform Manager. Log in to the Galaxy. Select the Platform for which Service Pack 2 is to be installed. From the Right pane, select one engine at a time. Engines hosting DIObjects should be set off-scan and shut down last. Right-click the engine and set it off-scan.

Right-click the engine and shut it down. Shut down the platform. Exit the System Management Console before installing the patch. After Service Pack 2 is applied, the local platform is removed. The Platform must be redeployed. Redeploy the platform. Do not deploy objects marked with software upgrades until the Galaxy nodes have been updated. To properly track which nodes have been updated, you may want to undeploy an individual platform, update the node in question, and deploy the platform again.

This ensures that all Galaxy nodes are properly updated. Platforms containing redundant engines must be updated together. To clear the software upgrade icon status on the patched Galaxy Repository, the redundant pair must be undeployed and then redeployed instead of only redeployed. Platforms containing InTouch The service pack for InTouch and the service pack for Application Server must be applied.

Ensure the computer is restarted after applying each service pack, even if it is not requested. You should see Version: 3. The issues are listed by their Change Request number: L : The error message "Retrieve style definition s in XML document are invalid" appears when validating ArchestrA symbols using aaTrendControl if ActiveFactory is not installed on the system. Before installing the patch, ensure good known backups of all installed Galaxies are created.

Wonderware provided base default galaxies will be replaced during the service pack installation. Software Requirements : Several Windows operating systems have distributed service pack updates since the initial release of Wonderware Application Server 3.

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. Login to the Galaxy. Select the Platform for which Service Pack 1 is to be installed.

Engines hosting DI objects should be set off-scan and shutdown last. Shutdown the platform. Exit the System Management Console prior to installing the patch. After Service Pack 1 is applied, the local platform is removed.

Install the service pack on the Application Server nodes after installing the service pack on the Galaxy Repository node. Ensure the computer is rebooted after applying each service pack, even if it is not requested. Click Help from the menu bar. The issues are listed by their Change Request number: L : Changing a template UDA to an "array" data type and deploying the template generates a warning message and the changes are not deployed.

On the Action menu, click Backup. Follow the prompts to complete the backup operation for each Galaxy. Note: Even though Patch 03 is not required for run-time only systems systems with only the ArchestrA Bootstrap installed , we recommended that you update all nodes to the same software version. Patch 03 requires ArchestrA-related processes be shut down and may require a reboot. You apply Patch 03 with the same installation steps used to install Patch Refer to Installation Instructions - Application Server 3.

This is not happening. Instead, some other symbol is shown in the place of the "Not Found" symbol. You "swap" the names of the symbols. This problem does not occur if you save between each renaming. L : Embedded ArchestrA symbols that appear in an InTouch managed application window can be swapped if the symbols are deleted from WindowMaker without undeploying the application afterwards.

From the Action Menu , select Backup. Note: Patch 02 is not required for run-time only systems systems with only ArchestrA Bootstrap feature installed. Patch 02 requires ArchestrA-related processes be shut down and may require a reboot. You apply Patch 02 with the same installation steps used to install Patch You can use this utility to determine if your managed or published InTouch applications on a run-time node have ArchestrA symbols embedded in windows.

You use this utility to analyze your Galaxies to determine if they contain any ArchestrA symbols with duplicate element IDs. This utility can also repair symbols that contain duplicate element IDs.

If the ArchestrA Graphic Editor encounters a graphic element that contains duplicate IDs with custom property overrides or string substitutions, it surrounds each override with double brackets [[ ]]. After the object is saved, it will be set to a warning state. The ArchestrA Symbol Analysis and Repair Utility Guide lists a set of tasks you must complete to minimize the time required to analyze your Galaxy and repair symbols.

L : The Application Server version 3. The patch install follows a similar behavior to that supported in Application Server 3. To install the patch 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 patch installer.

Select the Platform for which patch 01 is to installed. Right click the engine and set it off-scan. After patch 01 is applied and the system is rebooted if required start the platform again. If you will be redeploying the platform at this point, then start the platform Off-Scan. If you want to synchronize the Application Server with the runtime environment this will be the best time. The objects in the Application Server are marked for software upgrade and require redeploy.

You can deploy objects to an unpatched node, but we do not recommended it. Install the patch on the Application Server nodes after installing the patch on the Galaxy Repository node. The patch for InTouch and the patch for Application Server must be applied. Ensure the computer is rebooted after applying each patch, even if it is not requested.

L When client event scripts ignore the specified timeout, the View will hang. L When an object is imported, the relative anchor point moves. L In some.

NET script, attributes are passed as a reference instead of a value. About This Release Application Server 3. 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 shutdown.

Run-time Platforms can be a mix of old and new versions. Two options exist, Standard and Full modes. 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.

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. 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. 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 shutdown in reverse of execution order, independent of whether DIObjects are involved or not.

An exception is for Areas. They are shutdown after their objects. Toolkits Enhancements have been added to the GRAccess Toolkit, such as the ability to browse and configure security. Subscribes to one or more attributes and receives data updates from these attributes. Writes new values to these attributes, subject to user authentication. Recommended Hardware Requirements Software Requirements Recommended Hardware Requirements The following list shows the recommended hardware requirements to install Application Server version 3.

Operating Systems Other Software Requirements Vista Restrictions Operating Systems The following table lists the supported operating systems that can be installed on computers running server, client, and run-time components. If you attempt to install or upgrade Application Server on a computer running one of these operating systems, an error message appears.

Windows Server Standard Edition SP2 is the recommended operating system to run server components. If you plan to run Application Server version 3. The Business Edition is recommended. Other Software Requirements The following list describes other third-party software requirements to support Application Server version 3. Microsoft Visual Studio toolkits only. Vista Restrictions Application Server version 3.

Users must log on as a Windows Vista administrator to run Application Server version 3. You cannot run Application Server as a Windows Vista standard user or power user. You can run Wonderware bit software only with a bit version of Windows Vista. Windows Vista does not support a traditional Application Server 3. A Vista Platform 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.

ArchestrA graphics 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. Windows Vista security prevents started Windows services from interacting with desktop objects. When Application Server 3. These functions interact with desktop objects by starting Windows programs and sending keystrokes to these programs. The Galaxy Repository is only supported on Vista for single-node systems.

For multiple-node Galaxies, Windows Server is the preferred operating system for the Galaxy Repository node. Using Multiple Network Interface Cards with 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 a Galaxy Repository node. 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. SR FS Gateway supports the retry of the write operation if the write operation fails. SR The following error occurs after pokes: "Failed to place item Tags. This guide describes how to configure and use FS Gateway. This guide describes how to use the Log Viewer, a utility that provides troubleshooting information about the FS Gateway. This guide describes how to use the Log Flag Editor, a utility through which you can control the types of messages displayed in the Log Viewer.

Viewing these guides requires the installation of the Adobe's Acrobat Reader. This utility is not included on this CD, but it can be downloaded for free from the Adobe Web site at the following Web address:. After downloading the file from Adobe, you must run the executable to install it on your computer. Follow the typical installation routine.

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 is stored for the data value in row number 4.

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:. 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. 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.

The Application Server version 3. Using Adobe Reader, you can simultaneously search for a specific topic across all books that belong to the Application Server product library. Application Server 3. Before installing Wonderware Application Server 3. If you are using an InTouch If you have Wonderware Application Server 3. Installing Wonderware Application Server 3. Only major changes to software components may require any deployed platforms to be redeployed.

If InTouch This does not apply to version 3. The patch is also required to leverage the new Historian configuration options from the IDE. 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.

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.

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.

Script Improvements Two new methods are available for Application Server scripts. However, the Trend Client can operate without these data sources. Supports full and cyclic retrieval while getting data from the Wonderware Historian. The Alarm Client shows current and historical alarms and events. 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.

A dual core processor is strongly recommended for optimal performance. Super VGA x or higher resolution video adapter and monitor. Network interface card. Mouse or a compatible pointing device. Development and Application nodes 2 GHz or faster processor. Mouse or compatible pointing device.

Windows XP Professional SP3 is the recommended operating system for computers running client components. See Note 2. Windows XP Tablet? An error occurs if you attempt to install or upgrade Application Server version 3. Windows Server is the recommended operating system for the GR node.

You can run Application Server only on computers running a bit operating system. You cannot run Application Server on a computer running a bit operating system. Other Software Requirements The following list describes other third-party software required for Application Server version 3.

Vista Restrictions Application Server version 3. You must log on as a Windows Vista administrator to run Application Server version 3. You cannot run Application Server as a Windows Vista standard user or power user. The Galaxy Repository is supported on Vista only for a single-node configuration of Application Server. For multiple-node Galaxies, Windows Server is the recommended operating system for the Galaxy Repository node.

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. 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 Vista security prevents started Windows services from interacting with desktop objects. When Application Server 3. 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. 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. 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. Follow the rules for configuring a normal redundancy setup. Vista will identify this NIC and assign it a Private profile. The gateway address can be the same as the IP address. Usually these addresses will be the internal, non-routable addresses like 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.

Upgrade Limitations The following limitations apply when upgrading existing Application Server components to version 3. Uploading application run-time changes from a non-upgraded node is not permitted. InTouch HMI must be upgraded to version Updating Wonderware Application Server 3. 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.

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. The issues are listed by their Change Request number: L : Cannot import objects if the configuration version is older. The issues are listed by their Change Request number: L : 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.

L : You receive a "Could not resolve reference" error message for a. The "Replace Entire Instance" option only deletes the objects that have no hosted child objects. L : The calculated WinPlatform. CPULoadAvg value is incorrect for a platform running on a computer with a dual core processor.