(Only applicable for Server with remote web server (IIS)): To set the Web Server Communication = Secured over CCom port.A project is created and the history database is linked to it.

( Optional) A dedicated IIS User is created and assigned to the IIS_IUSRS Group. You have verified the existing Application Request Routing (ARR) installation. (see Install IIS in Complete the Installation Planning Requirements). (Only applicable for Server with local web server (IIS)): IIS is installed and configured according to the OS installed.However, it is recommended to secure the communication with the self-signed certificate. The certificate can be a host certificate with a private key or a self-signed certificate. The certificate must have code-signing feature to prevent your systems from any security threats and remote attacks.įor the purpose of code signing, you can use either SMC-created certificates or procure certificates from a trusted Certificate Authority (CA). This is because starting Desigo CC V5.0 SMC verifies code signing for website/web application certificates. If you are upgrading from Desigo CC V4.x (and not using code-signing certificate in V4.x) to V5.0, are not able to work with the Windows App Client after the upgrade. In this workflow for securing the communication between the Desigo CC Server and the remote web server (IIS) Windows store based certificates are used. Scenario: You want to set up and work with the Windows App client on the Desigo CC Server with local web server (IIS) or on the remote web server (IIS) hosted on the Desigo CC Client/FEP.įor working with the local Windows App client on the local web server (IIS) you can leave the web communication as Local.įor working with the remote Windows App Client, it is recommended to secure the communication between the Desigo CC Server and the remote web server (IIS).

Desigo cc download