Deployment allows you to distribute projects (and any subsequent updates) to computers in your Citect SCADA system.
This is enabled by a deployment server, a computer that stores multiple "versions" of a project's runtime files. From here, you can deploy a specific version to any computer that has been configured as a deployment client.
Deployment offers the following benefits:
There are two key processes required to use deployment for your Citect SCADA system:
To enable deployment, you firstly need to set up a deployment server. You then need to establish a connection with each deployment client to which project versions will be delivered.
Each requires the installation of components that are available from the Deployment Components page of the Citect SCADA installer. You can then configure these components with a tool called the Configurator. See Prepare Your System for Deployment.
You can use the Deployment activity in Citect Studio to add project versions to the deployment server and manage their distribution.
The Deployment activity has two primary views:
You can specify the Update Method that will be used to restart the Runtime Manager on the destination computer. Restart can occur automatically, or the operator will be prompted to accept the update and restart Runtime Manager when appropriate.
A Settings view is also available in the Deployment activity. You can use this view to configure a deployment server, or to manage multiple deployment servers if required.
Note: A deployment server uses Windows user groups to control access. These groups define a number of roles that support specific functionality: admin, deploy, upload and read-only. If a particular user needs to perform deployment tasks in Citect Studio, you will need to confirm that they are added to the appropriate Windows user group on the deployment sever. For more information, see Provide Deployment Access to Additional Users.
See also
Published June 2018