 |
The web server delivers your BlueSpice installation to the users' browsers. Without a web server, BlueSpice cannot be used. The steps listed here are required. |
Introduction
We recommend to use the most system-optimized software possible for a live operation of BlueSpice both under Linux and under Windows. For this reason, the documentation of an installation of Apache (XAMP) under Windows is omitted. This chapter lists the steps that are necessary to install the Microsoft IIS Web Server service on Windows Server >= 2016.
Open the Server Manager and the Roles Manager
Open the Server Manager (like in the previous step). Unless otherwise configured, it starts automatically as soon as you log in to the server. Otherwise, you will find it in the start menu under the search term "Server Manager". You are now looking at the following view:
Click "Manage" (1) and then click "Add Roles and Features" (2):
Installation of IIS in the Roles Manager
Sie befinden sich jetzt im Roles manager.
Click "Next >" until you reach the "Server Roles" area (1). There, you activate the role "Web Server (IIS)" (2):
Click "Add Features" in the resulting pop-up window:
Click "Next >":
You are now in the section "Features".
Click "Next >":
You are now in the section "Web Server Role (IIS)".
Click "Next>":
You are now in the section "Role services".
Activate the option "Windows-Authentication" (2) under "Security" (1) and the option "CGI" (4) under "Application development" (3).
Click "Next >" (5):
You are now in the "Confirmation" section.
Activate the option "Restart the destination server automatically if requred" (1) and click "Install" (2):
Click "Close" once the installation has been completed.
With the successful completion of all these steps, the IIS web server is now installed. Check the functionality by starting Internet Explorer on the server and calling the URL http://localhost/. If installed correctly, you will see the welcome page of the IIS Web server:
Next step
If you have successfully completed all of the above steps, proceed to the next step: urlrewrite.
Discussions