Distribute the Project

After compiling a project, you can distribute the runtime files to your live system in the following ways:

• Using the Deployment functionality (recommended) - see Deployment.

• Using the archive feature - see Back Up a Project and Restore a Project projects.

• Using a manual file transfer - pushing the runtime files directly onto your live system at the operating system level.

• Using automatic file transfer - pulling runtime files from the configuration machine to the live server using [CtEdit]Run and [CtEdit]Copy.

• Using a shared folder on a network drive.

  Note: Shared folders are not recommended for servers or control computers.

Automatic file transfer

This is where runtime files are pulled down to the runtime system using the [CtEdit]Run and [CtEdit]Copy parameters.

• [CtEdit]Run points to the location of the runtime files. To avoid running a system over the network and potentially slowing down the system, it is recommended that this is a local folder under the [user] directory.

• [CtEdit]Copy points to a copy of the runtime files. This can be a remote shared location (for example the [user] folder shared on another computer) or another local folder. When Plant SCADA detects that the files in the RUN directory have a different timestamp to those in the COPY directory, the files are copied across to the RUN directory.

By updating the runtime files in the COPY directory, they will be automatically copied to the RUN directory whenever they are changed.

Note: Do not use the [CtEdit]Run and [CtEdit]Copy parameters if you intend to use Plant SCADA's Deployment functionality.

Shared Folders

This is where the runtime files are stored in a network shared location, with a backup server specified in case the main files are not available.

• [CtEdit]Run points to the main remote shared location of the runtime files.

• [CtEdit]Backup points to the alternate remote shared location.

Example — Using Run/Copy to distribute project runtime files

File Server (PC1)

Consider the example project structure below. The overall system comprises four parts: a main project which features two separate production line projects, each of which draws on some common elements from a common project.

Run/Copy can be used to update project files from the File Server (PC1) to the File Client (PC2). Run/Copy does not support nested project folders, therefore project folders need to be on the same level as shown below.

The [User] folder (or a parent of the [User] folder) needs to be shared on the network. The shared folder needs to be accessible for machines to download the project runtime files. In this example, [User] is shared.

File Client (PC2)

File Client (PC2) will use Run/Copy to get the latest updated projects from the File Server.

The settings for Run/Copy on the client are:

[ctEdit]Copy = \\PC1\User\Main
[ctEdit]Run = %PROGRAMDATA%\AVEVA Plant SCADA <VersionNumber>\User\Main

The [Run] folder needs to be a child of the [User] folder on the target machine. The following pictures shows the project folders before and after the first project start-up with Run/Copy.

The project folders are automatically created by the Run/Copy process if they don't exist. In this example, the basic runtime files are copied to the [Run] folder. Any other files will be copied over on demand, such as page *.ctg and *.rdb files. After a successful project start-up, it is also possible for the project to start up when the [Copy] path is not available (if, for example, the File Server is uncontactable). In this case, only pages that have been previously viewed (that have been copied over previously on demand) are available.

If the target machine has the project development environment installed, do not launch Plant SCADA Studio after Run/Copy are set up. Doing so will override the [Run] path setting and you may end up running the wrong project.

See Also

File Server Redundancy