On-Prem means hosting a software or hardware on the company's own physical infrastructure, i.e. in the company's data centers. On-Prem ensures that all systems and data run on local servers under the direct control of the company. In this training content, you will learn the steps to publish the application in On-Prem with the Configuration Manager module.
This training content consists of the following topics:
Configure Configuration Manager settings,
Publishing the app,
Preparation of IIS and necessary environments (URL Rewrite, .Net 6 - Hosting Bundle),
Building and publishing the application on IIS,
Frequently asked questions,
Improving application performance: IIS application pool settings.
Configuring Configuration Manager Settings
After logging into the Kuika platform, go to the “Configuration Manager” module.
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.
Add the URL you have set to stand up your backend in the “Backend URL”.
Then save the settings with the “SAVE” button.
Publishing the Application
Click on the rocket icon on the top right sidebar, select the “Web” option and click on the “Publish” button.
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.
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.
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.
If you are using an SSL certificate, select the connection type as HTTPS and specify port 443.
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.
If you are using HTTPS protocol, continue by selecting the SSL certificate you have added to your server from the SSL Certificate field.
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
Create a new site for the backend with similar steps and enter a different domain.
Specify the site name, select the backend files you installed under C:\inetpub\wwwroot\ as the physical path.
If you are using an SSL certificate, select the connection type as HTTPS and specify port 443.
Enter the domain name you specified for the backend as the hostname.
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.
To make sure that the backend is running, click on the link in the “Browse website” section on the right panel of IIS.
Check if the backend is working by adding “/swagger” to the link.
So you can see that the Backend is working.
Frequently Asked Questions
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.
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.
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.
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.
Improving Application Performance: IIS Application Pool Settings
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.
Open IIS Manager.
Expand your server name from the left side menu and click on “Application Pools” .
Find the Application Pool where your Kuika application is running in the list. Right click on it and select “Advanced Settings”.
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.
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.
