The following uses the Web Deploy method to directly publish and deploy Web APIs to IIS:
Step 1: On the development machine, open the PowerServer C# solution in SnapDevelop. Log in to SnapDevelop if required.
Click the Open C# Solution in
SnapDevelop button (
) in the toolbar to launch the PowerServer C#
solution in SnapDevelop. Or go to the location where the PowerServer C#
solution is generated; and double click PowerServer_[appname].sln to launch the solution
in SnapDevelop.
At startup, the solution will install/update the dependencies. Wait until the Dependencies folder completes the install/update. (Make sure the machine can connect to the NuGet site in order to successfully install PowerServer NuGet packages).
Step 2: In the Solution Explorer, right click on the ServerAPIs project node, and select Publish.
Step 3: In the window that appears, select Web Server (IIS), and click Next.
Step 4: Configure the Web server (IIS) connection settings, and click Next.
The following figure shows the settings for deploying to an IIS website on a remote server.
Note: Input the Windows user name that you have configured to allow to connect to the site.
The following figure shows the settings for deploying to an IIS website on the local machine.
It is not necessary to input username and password when connecting to a local site.
Step 5: Click the Edit icon to continue modifying the publish settings.
Step 6: Select the Self-Contained deployment mode and the appropriate target runtime, and then click Save.
-
A Self-Contained package will not only include the project itself and its dependencies, but also include the .NET Core runtime and libraries. Users can run it on a machine that has no .NET Core runtime installed.
-
A Framework-Dependent package will only include the project itself and its dependencies. Users have to install the .NET Core runtime in order to run the project.
Note: Do not select the "Produce single file" option underneath; it is unsupported by PowerServer.
Step 7: Click Publish and make sure publishing was successful
You can view the publish progress and result in the Output window. If any error or failure is reported in the Output window, click the link provided at the end to view more details and possible solutions.
After that, the IIS process manager will automatically launch the Web APIs when requests are made to access the Web APIs.
Although you don't need to start the Web APIs manually, you can verify the Web APIs by following the instructions in the section: Verifying the Web APIs.
Before you can run the installable cloud application, you might need to adjust the following settings first:
-
Specify the URL (for example, https://172.16.100.83:81) as the Web API URL in the .NET Server page of the PowerServer project painter and then build and deploy the project again. If you do not want to build and deploy the project again, you can also directly change the value of the Web API URL stored on the Web server using the command-line tool (CustomizeDeploy.dll). See this section for more details.
-
If you use the SQL Anywhere database or ASE database which supports only ODBC connection at this moment, you will also need to set up the corresponding ODBC data source in the server where Web APIs is published and running.
