Configure an InTouch application for NAD

Network Application Development or NAD is an architecture that combines the best of the client-based and server-based architectures. NAD provides automatic notification of application changes and can automatically distribute updated applications to View nodes

When configuring an application for NAD, you must specify the folder that you want WindowViewer to copy the NAD Repository application to.

• If this is the development node, you can type a local folder path, such as c:\InTouch\NAD. You can also type a networked remote UNC path, such as \\node\share\path. This is convenient for file server-based networks where most file storage is kept in a central location.

• If this is a client node (run-time only), you typically use a local folder path.

We recommend that you use a local folder whenever possible to prevent network delays and failures from affecting the operation of WindowViewer.

Caution: Do not use a root folder or a UNC pathname that points to a root folder. The View node recursively deletes all files and subfolders in the specified destination application folder before copying the NAD Repository application directory. Therefore, never use the path of the NAD Repository application folder or a UNC to the NAD Repository application folder.

If you do not specify a folder, WindowViewer automatically creates a local subfolder named NAD in the folder from which WindowViewer is launched. The NAD folder should be considered a temporary folder and no other files should be saved to it except those copied by NAD itself.

Configure an application for NAD

1. Start Application Manager.

2. On the Tools tab, select Node Properties.

   The Node Properties screen appears.

   

3. Select the Enable Network Application Development radio button.

4. In the Local working directory box, type the path to the folder that you want WindowViewer to copy the NAD Repository application.

5. In the Polling period (sec) box, type the interval, in seconds, at which the View node checks the development node for updates.

   • Be careful that you do not set this value too small. If WindowViewer checks for NAD Repository application changes too often, it can interfere with servicing the running application.

6. In the Change Mode area, select the option that determines the action WindowViewer takes when the NAD Repository application changes.

   • Select Ignore changes to have the WindowViewer node ignore any changes made on the development node.

   • Select Restart WindowViewer to have the WindowViewer node copy over the updated NAD Repository application (if configured to do so) and then restart itself.

   • Select Prompt user to Restart WindowViewer to show the operator a message that the application has changed. The operator can either restart WindowViewer with the application updates or continue using the current application.

   • Select Load Changes into WindowViewer to dynamically load in WindowViewer the changes made in the development node. This may affect performance for large updates.

     Note: It is recommended that you use the Load Changes into WindowViewer option only if the application changes are minor and few in number. Examples of minor changes include changes made within an existing window, resizing of graphic toolbar elements, adding new graphic toolbar elements, and reference substitutions. When making changes that require that WindowViewer be restarted, such as adding new tags, adding new windows, or changing the configuration—or if in doubt—use one of the Restart options instead.

   • Select Prompt user to load changes into WindowViewer to show the operator a message that the application has changed. The message prompts the operator to load the changes.

7. Select OK.