Install Sana Commerce Webshop on Web and Database Server

Now as the web application is in place, it can be connected to IIS, so it is exposed to the Internet: 

Step 1: Create a new website in IIS:

Creating a New Website in IIS 8

Step 2:  Give an appropriate name to the website, select the IP address and domain names, which will run the Sana Commerce solution and map the website's physical path to the frontend directory of the Sana Commerce solution on the file system (see the 'Install the Web Applications' chapter). The application pool is automatically created:

Website Settings

Step 3: Check if 'Anonymous Authentication' is enabled for the newly created web site (switch to the features view and go to 'IIS -> Authentication').

Step 4: Select the newly created application pool and click 'Basic Settings…'. Select '.NET Framework v4.0.30319' from the '.NET Framework version' dropdown.

Step 5: Select 'Classic' mode in the 'Managed pipeline mode' dropdown during the creation of the new application pool. In this mode, the server will continue to route requests for managed code through 'Aspnet_isapi.dll', processing requests the same way, as if the application was running in IIS 6.0. You can also select 'Integrated' mode (in this mode the server will use the integrated, request-processing pipelines of IIS and ASP.NET to process the request), but in this case you will have to convert the 'web.config' which is not recommended:


Selecting 'Classic' Mode in IIS 8

Step 6: Click 'Advanced Settings...' on the right panel, go to 'Process Model -> Identity' and set SC_Webuser in the 'Custom account' field (the user which was created in the 'Create NT Users' chapter):

Setting SC_Webuser to Run Application Pool

Sana Commerce Backoffice Application

There are system names which cannot be used in a virtual directory name. For example: shop, profile, checkout. If you create a virtual directory in IIS, do not use system names in the virtual directory names. Otherwise, this will cause problems with running the frontend.

Step 8: Select server in IIS, go to 'IIS -> ISAPI and CGI Restrictions' and allow ASP.NET 4 to run.