Projects

Using the Projects node in the SMC tree, you can create and restore project/project template on Server, Client and FEP installations and configure the projects to set up the Desigo CC system as a Stand-alone system or as Client/Server setup.

Furthermore, you can install web server (IIS) on the stand-alone system or on the remote system hosted on Client/FEP installation for working with Windows App Client. (see Setting up the Windows App Client)

You can also extend the project configurations to set up the distributed systems. (see Setting up the Distributed System)

Stand-Alone System

On a single dedicated station, you can set up Desigo CC Server with database server.

The SMC and Installed Client are deployed with server installation. You can work with a Server project when you launch an Installed Client.

Since there is no web server you can leave the Web Server Communication field to Disabled.

Since there is no outside communication, no need to open the firewalls for communication. It is recommended to stop the GMS SMC Project Data Service to stop any communication over the service port.

NOTE:
A stand-alone system is secure in regards to attacks from the outside. However, installation guidelines for closing outside communication by firewall settings, virus scanner, and backup must be followed to secure the system!

You can also setup a stand-alone system with local web server (IIS). (see Stand-Alone System with Local Web Server (IIS))

Client/Server Setup

You can set up only one Desigo CC Server to work with one or more clients (as Client/FEP) running on different computers. This allows multiple operators to manage and supervise the same site. First, you must set up the Server and then the client station.

The communication should be secured using security certificates in SMC.

  • The logged-on user of the Client/FEP operating system has access to the Server project’s folder.
  • The root certificate identifies the source of certificates used for communication. Therefore, the root must be the same for all host certificates and must be available to the Server and all the Clients.
  • If multiple clients (Client/FEPs) are connected to a single Server, since the communication should be specific for each Client/Server, separate host certificates generated from the Server root should be used for securing each Client/Server communication.
  • The root and communication (host) certificates must have different Subject names.
  • The logged-on user of the Client/FEP operating system and the Client FEP project’s Pmon user must have access to the Private key of the Client/FEP host certificate.
  • If a remote FEP is connected to the Server, it must have the same Windows key file is available in the Windows Key Store.

NOTE:
The owner of the Desigo CC system is responsible for distributing authorized certificates and keys. This is often done by the IT infrastructure, particularly, if commercial certificates are used instead of the self-signed ones.

 

This section provides reference and background information for configuring of Desigo CC project.

To restore a project or create a project from a template, see the step-by-step section.

To create a new project with extensions on a Server, see the step-by-step section.

To set up the Installed Client on a local Server or on the remote Client/FEP installation, see the step-by-step section.