Deploy a Version of a Project to a Deployment Clients

Deployment > Using the Deployment Activity > Deploy a Version

Deploy a Version

Note: To successfully deploy a version of a project, Runtime Manager needs to be running on the deployment client either as a service or as a standard application. To determine which project Runtime Manager is running, refer to the Troubleshooting question "Runtime Manager is not running the deployed project".

To deploy a version:

From the Deployment activity, select Computers.
Select the check box next to the computers or groups to which you want to deploy a version. To make multiple selections, you can:

Select adjacent rows by holding the Shift key while you use the up or down arrow keys.
Select distributed rows by holding the Ctrl while selecting the required rows. (You can also cancel selection by clicking on a row again.)
Select all computers by using the check box next to the Computers column header.

Note: If you have selected multiple computers, any setting changes you make to a particular computer will apply to every selected computer.

In the Projects column, select the name of the project you would like to deploy.

The Target column will display the latest available version of that project.

In the Target column, select the version of the project you would like to deploy from the drop-down menu. You can select a version that was previously deployed if required.

If the target version has been previously deployed, you can rollback to an earlier version of the project directly from the client computer using the Computer Setup Wizard. See Project Configuration for more information.

In the Profile column, select the profile you would like to deploy from the drop-down menu (see Profiles). The settings in the associated <ProfileName>.ini file will be implemented on the deployment client after the Runtime Manager has been restarted. If no profile is selected, the local Citect.ini file will be used.

If you have configured two profiles for the one project, both profiles are deployed with the version of the project; however, only the selected profile will be used.

To determine which profile is active on the deployment client, check the setting for the Citect.ini parameter [RuntimeManager]Profile=<ProfileName>.

In the Update Method column select either Prompt, Notify or Force (see Specify the Update Method).

If no project versions have previously been deployed to the client computer, Citect SCADA will force an update. The project will be activated and Runtime Manager will start the runtime processes.

Note: If the operator is prompted to update and clicks Cancel instead of accepting the new version, a message will be displayed in Runtime Manager. This message alerts the operator that a new deployment of a project is available. When Runtime Manager is restarted, the project will be activated.

Confirm that Runtime Manager is running on the deployment client computer, and check that all relevant processes are operational.
Click Deploy.
The status column will update with the progress of the deployment.

When the version has been deployed, the Active column will display the project name with the active version number in brackets.

Note: If deployment is unsuccessful, an exception icon will display. Click on the down arrow to reveal the error message and click OK to close. For information on each error message, refer to the troubleshooting section.