• Log in to the Kuika platform.
• Open the Configuration Manager module.

• Provide the application access to the server by making DB Connection String settings in the Connection Settings field.

• Add your backend URL to the Backend URL field.
• Save the settings by clicking the SAVE button.

• Select the project from the Apps screen.

• Click the three dots next to the Preview button and select the option.
• When publishing is complete, the frontend and backend ZIP files are sent to the specified email address.
• Extract the ZIP files to the standard directory for IIS, C:\inetpub\wwwroot\.

Preparing IIS and Required Environments

• Operating System Windows Server 2019
• Database MS SQL Server 2019
• Web Server IIS 10.0xx
• Hardware Requirements: 32 GB RAM, 16 VCPUs, Xeon E5 2660 2.2 GHz
• SSL Certificates: Must be provided for each subdomain.
• Firewall: Allow ports 80 and 443.
• Installations: Install URL Rewrite and .NET 8.

Building and Publishing the Application on IIS

1. Frontend Setup:
   
   • Click IIS > Sites > Add Web Site.

Web UI folder must be selected for frontend installation.

• Enter site name and select frontend files as physical path.
• If you are using SSL, select HTTPS and specify port 443.
• Enter the domain name in the Host Name field and check "Require server name display ”.
• Use IIS > Browse website to check that the frontend is running.

2. Backend Setup:

• Create a new site for the backend following similar steps.
• If you are using SSL, select HTTPS and specify port 443.

In Application Pool settings:

• Right-click on the backend application pool, select Basic Settings > No Managed Code.
• To test the backend, check if it works by adding /swagger.

• URL Rewrite Rule Name Conflicts:
  
  • Open the Web Config file and change the React Router Routes rule name.
• Folder Authorization:
  
  • Right click on Frontend and Backend folders and grant Security > IIS Users > Full Control permission.
• Backend 500.30 Error:
  
  • Connection String: Check Kuikaappdb and Kuikacommondb fields in appsetting.json file.
  • .NET 8: Install the package from https://dotnet.microsoft.com/en-us/download/dotnet/8.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.

• Network Error:
  
  • Edit env-config.js to add the correct URL to the BACKEND_URL field.
  • Restart the IIS > Frontend application pool.
  • 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://istediğinizalanadı/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, do a Cache Cleanup to make sure that the updates made on the browser are reflected.

Improving Application Performance: IIS Application Pool Settings

• Open IIS Manager.
• Select the application pool from the Application Pools tab.
• Right-click and set Advanced Settings > Start Mode to "Always Running ”.
• Restart the IIS service.

If you still have problems after following these steps, you can contact the Kuika support team.