Create a New Web Client Deployment

To configure a web client deployment of a Citect SCADA project on a Web Server, you need to log in to the Web Client with Administrator permissions. This will provide you with access to the full functionality of the home page.

1. Click the Add New Deployment icon.



This will display the Deployment Configuration page.

2. Type a name in the Deployment text box, and include a Description if necessary. A deployment name cannot contain any of the following characters: \ * ? | . , / " ' : ; < > # &
3. Identify the source of the Citect SCADA project's content in the Project Path field.

If the project is located locally on the Web Server, you can use a normal path address. The path needs to point directly to the project within the Citect SCADAUser directory. For example, the location of the MyExample project would be:

[User]\MyExample

Note: If you are remotely administering the Web Server and use a local path address, verify that the path represents the location of the project on the Web Server computer, not the computer you are currently using.

If the project is not located on the Web Server, you need to use a UNC address that identifies the host network computer and the directory it can be found in. For example,

\\ComputerName\<path to application data>\User\MyExample

Note: You need to share the directory a project resides in to allow the Web Server access to it. Ideally, create a share from the directory (called WebShare, for example) and then use the following project path:

\\ComputerName\WebShare

Remember that if you are trying to access the project directory from a remote computer, a "local" administrator log in will not provide you with appropriate access on a different computer. use a network user profile that will be recognized by other computers on the same domain.

4. Determine if any of the I/O, Alarms, Reports or Trends Servers associated with the project are protected by a firewall. If they are, you need to confirm with the firewall administrator if the Citect SCADA ports have been opened to allow direct access, or if the firewall is using address forwarding.

   If forwarding is being used, you will need to identify each Server by typing the name in the Server field, using the following format:

   <ClusterName>.<ServerName>

   For Alarm Servers which have an additional Database Port, you can redirect it using the following syntax:

   <ClusterName>.<AlarmServerName>_AlarmDBPort

   For example:

   ClusterOne.AlarmServerOne_AlarmDBPort

   Type in the IP Address and Port for each server, as supplied by the firewall administrator.

5. Use the Client Control text box to specify the use of a particular version of the Web Client component when the deployment is displayed.

The menu lists the different versions of the Web Client control currently installed on the Web Server. Typically, choose the version of the control that matches the version of Citect SCADA your project was compiled on.

6. Click Apply Changes.



This is important, as you'll lose your changes if you jump straight back to the home page.

All the project files are retrieved from the path indicated, and copied to the Web Server ready for access by the Web Clients.

Once complete, information about the size of the project appears in the File Paths banner above the Project Path field. The number to the left indicates how many files are included in the project; the number to the right indicates the total size of the project.

The deployment is saved. When you return to the Web Client home page, by clicking the home icon, your new deployment is listed.

Note: When creating a new deployment, be aware that the .cab file you use (Client Control) for the deployment needs to correspond to the correct version of the project you want to access or the deployment will not succeed. For example, to create a deployment based on a version 7.0 Citect SCADA project, from the Client Control menu choose 700/filename.cab; to create a deployment based on a version 7.30 Citect SCADA project, from the Client Control menu choose 730/filename.cab.

See Also

Published June 2018