In this guide, we will set up a server running on IIS in an independent machine, and then deploy and host the Web APIs in the IIS running on this server.
Any version within the support period is supported. This guide takes Windows Server 2019 as an example. The instructions are similar in Windows Server 2022.
Step 1: Prepare a Windows Server 2019 (64-bit) machine that meets the following requirements:
-
The machine must be able to connect to the NuGet site: https://www.nuget.org (for installing PowerServer NuGet packages) and the Appeon license server (for validating the PowerServer license).
-
The Windows Defender Firewall on the machine allows the port number (81 in this guide or any port number you choose). The section "Configuring Windows Defender Firewall" has detailed instructions.
-
Read and write permissions are required for the directory where PowerServer Web APIs is hosted, for example, when deploying to IIS, read and write rights are required by the web site folder or "[solutionname]_API" sub-folder; this is to ensure when PowerServer is unable to connect with the license server (for example, due to a network problem), PowerServer can still run for a short period of time. If insufficient rights are detected, the warning message "Access to the path "...\licoffdata.bin" is denied" will be recorded in the event log.
Step 2: It is highly recommended that you create new IIS web sites for the installable cloud app (detailed instructions are provided in the following sections).
If you still plan to use existing IIS web sites instead of creating new ones, you will need to carefully check the following settings for that IIS web site.
We have often found that if the default values of the following settings have been changed, they will cause the installable cloud application to fail to run:
If you create a new web site, there is no need to check these settings because the default settings are appropriate for the installable cloud application.
