InTouchViewApp Object

The InTouchViewApp object represents an InTouch application in the Wonderware Application Server environment. The InTouchViewApp object manages the check-in, check-out, and deployment of an InTouch application.

The InTouchViewApp object includes the capabilities of the Application Server 2.1 InTouchProxy object, so that InTouch tags can be referenced by Application Server (Message Exchange) clients as InTouchViewApp attributes.

Click one of the following Help topics to navigate to information about that topic.

Overview

The InTouchViewApp object is used to incorporate InTouch applications into an overall system defined by a Wonderware Application Server Galaxy. The Application Server system manages

Managed InTouch applications associated with the InTouchViewApp can also contain ArchestrA graphics designed within the Application Server IDE.

The InTouchViewApp object allows application objects running on a ViewEngine object to access InTouch tags as if they were Application Server attributes of the InTouchViewApp object itself. The tags are browsable via the standard Application Server attribute browser.

You create an InTouch application by deriving an InTouchViewApp object from the standard template "$InTouchViewApp". You are given the choice of starting a new application, or creating a copy of an exisiting application. Either way, opening an InTouchViewApp object launches WindowMaker. There is no object editor for the InTouchViewApp object.

The most significant change to WindowMaker is that ArchestrA graphics created within the Application Server environment can now be added to InTouch windows.

A new dialog tab under Special/Configure/WindowViewer called Managed contains settings similar to the InTouch NAD feature that can be configured to change the deployment behavior.

You can assign multiple InTouchViewApp objects to the same ViewEngine object to make multiple InTouch applications available on a node.

Topic Category	Topic Subcategory	Topic Details
Overview	Existing InTouch Applications
New InTouch Applications
InTouchViewApp object Rules

Create and assign a ViewEngine object to a platform.

Create an instance of the InTouchViewApp object from the template that defines the InTouch application.

Assign the InTouchViewApp object to the ViewEngine object.

Deploy the ViewEngine object and the InTouchViewApp objects assigned to the ViewEngine object.

Run the InTouch Application Manager to select the application and run WindowViewer. This only needs to be done the first time.

Existing InTouch Applications

When you create an InTouchViewApp object to handle an existing InTouch application, the InTouch application files are transferred to a file repository directory. The original InTouch application files are not modified or deleted.

You should not access files in the file repository directly or make assumptions about the file repository structure.

When you make changes to the InTouchViewApp InTouch application using WindowMaker launched from the IDE, the original InTouch application is not changed.

Once you have created the InTouchViewApp object, deleting the original InTouch application does not effect the InTouchViewApp object’s application.

If you delete an InTouchViewApp object that represents an existing InTouch application, the application files are removed from the file repository directory, but the existing InTouch application is not affected.

New InTouch Applications

When you create an InTouchViewApp object for a new InTouch application, WindowMaker is started by the IDE. You create the application the same way you would if WindowMaker had been started from the InTouch application manager.

InTouchViewApp object Rules

You cannot create InTouchViewApp instances from the InTouchViewApp base template.

You can derive only one level of InTouchViewApp template from the base InTouchViewApp template.

You cannot derive an instance of the InTouchViewApp from an existing instance of the InTouchViewApp.

InTouchViewApp objects cannot host other objects.

Only ViewEngine objects can host and deploy InTouchViewApp objects.

In the Model view, you can assign an InTouchViewApp object to an Area object if you want the InTouchViewApp object’s alarms to belong to that area.

Undeployment of an InTouchViewApp object is not permitted if it is currently loaded on a target node.

When the file copying process at the end of an InTouchViewApp object deployment is still underway, the only allowable operation is to undeploy the object. This will cancel the deployment and remove any partially copied files.

For general information on objects, including relationships, deployment, and alarm distribution, see the Integrated Development Environment (IDE) documentation.

Run-Time Behavior

An InTouchViewApp object has no run-time specific behaviors. The InTouch application associated with the InTouchViewApp object handles all real time activities.

No object state information, such as StartUp or Going OnScan, is available for an InTouchViewApp object.

There are limits on an InTouchViewApp object’s ability to access InTouch data.

Data coming from InTouch tags used by an ArchestrA object may take up to thirty seconds to display new values when a deployed InTouchViewApp object is shutdown and then re-started.

An ArchestrA Object cannot connect to InTouch tags coming from and InTouchViewApp if the application is switched to run time from the IDE. The InTouchViewApp must be deployed for the references to connect.

An InTouchViewApp object cannot establish a data connection to an InTouch application running in a terminal session.

Configuration

For general information on objects, including relationships, deployment, and alarm distribution, see the Integrated Development Environment (IDE) documentation.

Run-Time Object Attributes

The following table describes the run-time only attributes for the InTouchViewApp object.


Attribute	Description	Run-Time Access (Supervisory, User, Read-Only, None)
DeploymentInProgress	This attribute is true while the InTouchViewApp object is being deployed. InTouch application files are deployed to target nodes asynchronously to avoid blocking the IDE when deploying a large application on a slow network. Even after the deployment is reported as "complete" by the IDE, it may take some time before the deployment is truly finished. The DeploymentInProgress attribute and a special icon for the InTouchViewApp within the IDE when true both indicate that the files have not finished transferring.	Read-Only
LastModified	Contains the date the InTouch application was last changed.	Read-Only
_SyncStatus	This "hidden" attribute is available for diagnostics and provides a text message that may be helpful in overcoming issues related to the asynchronous file copying process.	Read-Only
Connected (boolean) ConnectionStatus	This boolean and enumeration indicate if the InTouchViewApp object is communicating with WindowViewer. If not, most likely the ViewEngine object is not running.	Read-Only