Publish App on On-Prem

1. After logging into the Kuika platform, go to the “Configuration Manager” module.

2. Provide the application access to the server by setting the “DB Connection String” settings from the Connection Settings area. You can browse our Configuration Manager content to make settings.
3. Add the URL you have set to stand up your backend in the “Backend URL”.
4. Then save the settings with the “SAVE” button.

1. Click on the rocket icon on the top right sidebar, select the “Web” option and click on the “Publish” button.
2. When the publishing process is complete, both frontend (UI) and backend mail packages are created and sent to the e-mail address you specified in ZIP format.
3. Copy the received mail packages to the frontend and backend folders you have created under the C:\inetpub\wwwroot\ directory, which is standard for IIS, by extracting them from the zip.

• Install URL Rewrite and .NET 6 Hosting Bundle. These steps are necessary for your application to work properly on IIS.

Create a new application on IIS:

Frontend Setup

1. Go to Sites > Add Web Site.
2. Specify the site name, select the frontend files you installed under C:\inetpub\wwwroot\ as the physical path.

Web UI folder must be selected for frontend installation.

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

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

5. If you are using HTTPS protocol, continue by selecting the SSL certificate you have added to your server from the SSL Certificate field.
6. To make sure that the Frontend is running, click on the link in the “Browse website” section on the right panel of IIS.

So you can see that Frontend is working.

Backend Setup

1. Create a new site for the backend with similar steps and enter a different domain.
2. Specify the site name, select the backend files you installed under C:\inetpub\wwwroot\ as the physical path.
3. If you are using an SSL certificate, select the connection type as HTTPS and specify port 443.
4. Enter the domain name you specified for the backend as the hostname.
5. Right click on the application pool created for the backend from the application pools section and set Basic Settings > Edit Application Pool > Net CLR Version > No managed code.
6. To make sure that the backend is running, click on the link in the “Browse website” section on the right panel of IIS.
7. Check if the backend is working by adding “/swagger” to the link.

So you can see that the Backend is working.

1. Rule name conflicts in URL Rewrite:

When you want to run a second Frontend under a Frontend (Virtual Application), it may cause an error when the URL Rewrite rule has the same name in the web config settings of each Frontend. In this case, you can fix the error by changing the URL Rewrite rule name of the internal or external application.

• Go to the IIS folder on your computer.
• Open the “Web Config” file from the Frontend folder.
• Change the Rule Name > React Router Routes name. Thus, it will work when the two names are not the same.

2. Folder authorization problem:

If IIS was installed later when the server was first installed, access to the “inetpub” folder may be missing.

• To fix this, right click on the Frontend and Backend folders.
• Properties > Security > IIS > IIS > Users, add the IIS User and grant “Full Control” permission.

3. Backend 500.30 error:

• Connection String related errors:
  • Navigate to the IIS backend folder on your computer.
  • Check the “Kuikaappdb and Kuikacommondb” fields from the Appsetting.json file and fix the missing fields.
• Server communication problems:
  • Make sure that your application server has access permissions to your database server.
• Incorrect .NET 6 package:
  • Download ASP.NET Core Runtime - Windows - Hosting Bundle from https://dotnet.microsoft.com/en-us/download/dotnet/6.0.
• Incorrect application pool setting:

• Open the Application Pools area on IIS.
• Right click on the Application Pool used for your backend and open Basic Settings.
• Select “No Managed Code” for the “.NET CLR Version” value.

4. “Network Error” error:

• Make sure you enter the correct URL in Configuration Manager - Backend URL field when publishing your application.
• For Backend URL change after Publish:
  • Press F12 and open the Developer Tool to see which Backend URL the Frontend is requesting.
  • Switch to the Network area. Check the URL from the header field in failed requests.
  • If you notice that the frontend is not accessing the backend URL correctly, go to the frontend folder on your computer.
  • Edit the “ENV_TEST” section in the env-config.js file by entering BACKEND_URL: “https://the domain name you want/v1/api” and the swagger URL directory.
  • Go back to IIS. Restart the frontend's application pool.

If it still does not go to the correct URL, make sure that the updates made on the browser are reflected by performing Cache Cleanup.

In this tutorial, you will learn how to adjust your application pool settings to improve the initial load time of your application using IIS (Internet Information Services) on the Kuika platform.

1. Open IIS Manager.
2. Expand your server name from the left side menu and click on “Application Pools” .
3. Find the Application Pool where your Kuika application is running in the list. Right click on it and select “Advanced Settings”.
4. In the window that opens, go to the “Start Mode” setting under the “General” heading. Change the value here from “On Demand” to “Always Running” . In Always Running mode, the application pool is constantly active, which makes the application load faster.
5. After applying the settings, close the window and restart the IIS service for the changes to take effect.

If you are still experiencing problems after following these steps, contact Kuika support team.