Application Backup Wonderware InTouch
Identify backup methods for InTouch applications(Application Backup)
This section will explain how to save an application and optimize it for distribution/deployment.
Before proceeding with any changes to the contents of the application directory, it is highly recommended that the application file(s) be backed up to the hard drive whenever possible.
When backing up an InTouch application, WindowViewer must ALWAYS be shut down. It is also recommended that WindowMaker be shut down.
Backing up files creates a record of your development and ensures recovery of work in case of some unexpected event.
A backup operation should take place before major changes are made to an application, or before an application is distributed/deployed on another node.
InTouch File Content
When an application window is created, multiple files are created to hold the information needed by both WindowMaker and WindowViewer to display the window as defined. This means that each window will have more than one file used to define it. When a window is created in WindowMaker, a file called WIN****.WIN is created to hold pertinent window data.
When changes are made to the window in WindowMaker, the new version is saved as a .win file and the old file extension is changed to .WBK.
When you switch to Runtime, WindowViewer compiles its own version of the .WIN file for its use.
This file has the .WVW extension.
Finally, if your window contains one or more real-time trend files, a file with a .TRN extension is generated along with the .win file.
Previously, if a user had to move an application to another computer, the entire application directory was moved as a whole. However, the size of the transport medium can be limited and the application might not fit. In today’s environment, disk space is inexpensive and is generally not a consideration.
Backing up an application directory can be as easy as copy/pasting the entire contents of an application into another directory.
InTouch Backup – Application Publisher
The InTouch Application Publisher creates a self-extracting file that contains all relevant files and setup procedures that you need to install the application onto another InTouch node.
The Application Publisher compresses the Application to reduce download time over the Internet. You can copy these compressed applications to floppy disks, zip disks, and so on, for installation on other nodes.
Note: The Application Publisher’s finished file size is significantly less than the source file. For example, a full development and Runtime application may fit on a standard floppy disk. If the finished file is Runtime only, a large application may fit on a single floppy disk.
- NB Designer OMRON HMI Youtube Tutorial Videos
- DOPSOFT DELTA HMI Youtube Tutorial Videos
- Wonderware Intouch Youtube Tutorial Videos
- GT Designer MITSUBISHI HMI Youtube Tutorial Videos
- WinCC Siemens HMI Youtube Tutorial Videos
- FACTORY TALK VIEW Youtube Tutorial Videos
Once you publish an application, you can use several methods to load the published application file onto another InTouch node.
Copy to a floppy disk
Copy the file over your company intranet
Copy the file over the Internet
Run the self-extracting file as a program on the destination node
Publishing an InTouch Application
Close any open instance of WindowViewer, and close all WindowMaker windows.
In WindowMaker, expand the Applications directory within the Application Explorer
Select Application Publisher.
The InTouch Application Publisher — Step 1 of 4 dialog box appears:
Click Next.
The InTouch Application Publisher — Step 2 of 4 dialog box appears:
Enter Author Name: Enter the name of the person(s) (up to 256 characters) to contact regarding the application.
Enter a short description…: Enter a description for the application (up to 256 characters).
Enter package name…: Enter a name for the package (up to 32 characters).
Click Next.
Note: The information entered in the previous step, while required, is only used when
publishing to an IIS Client like FS WebServer or SuiteVoyager® 1.0. The information is stored in a file called packagename.inf and is not a necessary component when copying the self-extracting executable.
Publishing to any (IIS) virtual directory is supported by Application Publisher.
The InTouch Application Publisher –Step 3 of 4 dialog box appears:
Enter the InTouch application source…: Enter the correct path to the InTouch application source. The
default is the WindowMaker application directory. Runtime only: Prevents inclusion of development WindowMaker files in the published file. This option is not recommended if any edits to this application in WindowMaker are desired. 10. Click Next.
The InTouch Application Publisher — Step 4 of 4 dialog box appears:
Verify that the executable name in the first box is correct (by default, this will be the same as the Package Name you specified). In the second field, enter the path to the directory where you want to save the published file, or click Browse to locate a different directory. Note: The default setting to the Documents and Settings/AdministratorName/Local directory is acceptable. Do NOT publish to a floppy location (A:). Copy the published files to the floppy after the publishing operation is successful. Click Finish. Other Backup Scenarios In cases where disk space is at a premium, certain redundant or backup files may be deleted to reduce the application to a more manageable size. WindowViewer must be shut down before backing up.
Also Read:-