In this learning content, we will take a close look at the process of publishing the web applications you have developed to On-prem Windows servers.

First, you need to log in to the Kuika platform and make the settings that will allow your application to communicate with the servers.

1. For this, open the Configuration Manager module.
2. Click on the App Settings tab.

There are three important points to pay attention to here:

• The first one is to set your database connection. In the DB Connection String section in the “Connection Settings” field, enter the information required to access your application's database.
• The second is to configure the backend URL correctly. In theBackend URL field, enter the server address where you run your backend.
• With the entered information, save these configuration settings by clicking the “SAVE/UPDATE” button.

Now it's time to publish the application.

1. On the platform, click on the three dots next to the Preview button in the upper right corner.
2. Select "Web ‘ from the options that appear and then click the ’Publish ” button.
3. When the process is complete, both your frontend and backend files will be sent to your e-mail address as a ZIP package.

Before running your application on premium servers, we need to make some preparations on your servers.

1. The first step is to create folders for frontend and backend through IIS. For this, go to C:\inetpub\wwwroot directory on your server and create two separate folders: one for frontend and one for backend.
2. Then, unzip the ZIP files sent to you into these folders and place the files.
3. But don't forget at this stage: Components likeURL Rewrite and .NET 6 Hosting Bundle need to be installed on your server. These components are critical for your application to run smoothly.

Now let's move on to the steps to publish your application over IIS.

Let's start with the frontend setup.

1. First, go to the“Sites” tab on the IIS admin screen and select the“Add Website” option.
2. Specify the site name and select the frontend files you installed under C:\inetpub\wwwroot\ as the physical path.

Note that the Web UI folder must be selected for frontend installation.

1. If you are using an SSL certificate, select the connection type as HTTPS and specify port 443.
2. Enter the domain name of your application as the hostname.
   

(!) The option “Require server name display” must be checked, because this allows you to determine which port will be forwarded to which URL.

1. If you are using theHTTPS protocol, select the SSL certificate you added to your server in the SSL Certificate field.
2. To make sure that the frontend is working, click on the “Browse website” link in the right panel of IIS and check that the frontend is working correctly.

When you complete these steps, you can see that the Frontend is running smoothly.

Now let's look at the Backend setup,

1. First, you need to create a new site for the backend. To do this, create a site through IIS and enter a domain name you have set for the backend in the domain section. For example, backend.mysite.com.
2. After specifying the site name, select the directory where you uploaded the backend files as the physical path. This directory usually looks like this:
3. C:\inetpub\wwwroot\backend. If this directory does not already exist, make sure to create it.
4. If you are using an SSL certificate, remember to set the connection type to HTTPS.
5. Also, set the port number to 443.
6. In the Hostname field, type the domain name you set for the backend. For example: backend.mysite.com.
7. Now, let's move on to the application pool. Find the application pool created for the backend and right-click on it.
8. Next, go to the Basic Settings option. From there, open Edit Application Pool and set Net CLR Version to No Managed Code.
9. Finally, to make sure the backend is running, click Browse website in the right panel of IIS.
10. Once you have access to the website, add /swagger to the end of the URL. If everything is set up correctly, you will see that your backend is working properly!

That's it! Your backend setup is complete.

If you run into problems during publishing, don't worry! Let's look at some common errors and their solutions.

• Error 500.30usually occurs when there is an error in your database connection string or when the .NET 6 Hosting Bundle is incompletely installed. Check your Appsettings.json file and verify the required permissions.
• “Network Error” Error means that the frontend cannot access the backend URL. Revisit the Backend URL section inConfiguration Manager settings.

Finally, we have a few small optimization suggestions to improve the performance of your application:

Switch your application pool to "Always Running ” mode in IIS. This setting will ensure that your application is always active, which will significantly reduce the loading time.

Now you are ready to successfully publish your Kuika applications to on-prem servers.

‍