Runtime only environment

Before configuring the runtime only environment, and running the computer setup wizard, it is assumed you have transferred a project from the configuration environment, including compiled projects to your local machine. If not refer to Backing up a project for more information.

Using the .CTZ files from your backup included projects and target project, you can restore the project. It is recommended you restore the included project before the target project. The restore project tool is available from the start menu shortcut Runtime Configuration ->Project restore

In the Project Restore dialog :

1. In the Backup file field, browse or enter the name of the project to restore.
2. Under To, the option 'Current project', may be unavailable, this is due to no project having been run on the local machine before. The option 'New project' will be selected to restore a backed up project as a new one.
3. In the Name field, enter a name of the restored project.
4. In the Location field, enter or browse to the location of the project to restore (restore the project under the 'User' folder).
5. Leave the remaining settings as default and click OK.
6. The project will be restored.

You are now ready to run the computer setup wizard available from the start menu shortcut Runtime Configuration ->CitectSCADA.Computer Setup

In the RUN path edit box enter, or use the select button to browse for, the path to the local project that you wish to the client to run.If you enter the run path set the run folder under the ‘User’ Folder.

If you wish to maintain a synchronized local version of an external project select the Enable RUN/COPY deployment check box. Then in the COPY path edit box enter, or use the select button to browse for, the path to the external project that you wish maintain synchronization. This feature uses the [CtEdit]RUN and [CtEdit]COPY commands to maintain synchronization between the two projects.

Note: The Run/Copy mechanism does not transfer custom files such as meta-data, icons, images or runtime DBF files. Therefore, it is recommended deploying a project before Run/Copy to help ensure that those files at least exist. You will still need to re-deploy a project, when you want to update the custom files.

See Also