Step-by-Step
SMCConfiguring Web Client and Windows App ClientsAdditional Website and Application ProceduresWorking With a Website and Web Application Management on a Remote IIS System
SMCConfiguring Web Client and Windows App ClientsAdditional Website and Application ProceduresWorking With a Website and Web Application Management on a Remote IIS SystemWorking With a Website and Web Application Management on a Remote IIS System
The following sections describe how to handle websites and Web Applications on remote machines where Desigo CC is not installed.
Scenario: You have installed Desigo CC and created a project, but have not yet installed the web server (IIS). The CCom manager for the project that you want to connect to must be running on the server. Now, you want to connect a website/Web Application available on a third-party machine (target machine) to the project on the Desigo CC system.
To do this, you must have an intermediate machine (for example, a laptop). On this laptop, before exporting the Web Application to the third-party system, you must review the following requirements and gather the necessary information:
- ●
- Desigo CC is installed (on FEP or client).
- ●
- IIS is installed and configured.
- ●
- Application Request Routing is installed (only on target/third-party machine).
- ●
- Proxy for the Application Request Routing is enabled (only on target machine).
- ●
- Domain User as a member of the IIS_IUSRS group is assigned (only on target machine).
- ●
- The project and the virtual directories on the source machine (Desigo CC server) are shared with the user on the third-party machine.
- ●
- Website settings in IIS are created/edited (only on target machine).
- ●
- Application pool of a Web Application is verified and created (only on target machine). You have to create the same application pool (on target machine) which is linked with the web application on the source machine.
- ●
- Web Application for exporting is created and configured (only on source machine).
Further information