Install Sana Webstore on Web and Database Server

Install Sana Commerce

Install Sana Commerce (Sana webstore and Sana Admin):

 NOTE

Starting from Sana 9.3.1 the Sana Commerce Installer looks differently, but the settings are completely the same as in Sana 9.3. Below you can see the Sana Commerce Installer for Sana 9.3.1.

Step 1: Run the "Sana Commerce Installer.exe" file from the Sana package.

Step 2: On the General tab of the Sana Commerce Installer window, specify the "Application root path" where the Sana Commerce solution must be installed.

Step 3: Specify the "Frontend application name" which is used for the web site name in Internet Information Services (IIS) Manager.

Step 4: Select the deployment type:

To access the webstore and Sana Admin when anonymous authentication is disabled, a user must have read & write permissions to the folder selected for deployment. Use these user's credentials for the NT pop-up

• beta: the webstore and Sana Admin are externally accessible, but anonymous authentication in IIS is disabled for both to prevent unauthorized access.
• live: the webstore is publicly accessible. The anonymous authentication for Sana Admin and webstore is enabled in IIS.
• test: used for the test purposes. The webstore and Sana Admin are not externally accessible. Thus, the anonymous authentication for Sana Admin and webstore is enabled in IIS.

 NOTE

Starting from Sana 9.3.3, the application pool of Sana is running in the integrated pipeline mode by default. Therefore, the Anonymous Authentication is used for all deployment types as the integrated pipeline mode does not support Basic Authentication. For more information, see "Sana with the integrated pipeline mode" below.

Step 5: Add the Sana Commerce license. If you install Sana on a beta or live environment, the license file is required. If you install Sana Commerce on a test environment, the webstore will be available via the localhost domain name and in this case the license file is not needed.

 NOTE

If you don't have a valid Sana license for your webstore domain, you will not be available to access Sana Apps.

If you install Sana on the test environment using a "localhost" domain or some other local domain, for example "*.webstore.local", or you use Sana Commerce SDK to customize the Sana project, you will still need the Sana license for the local domain to access Sana Apps. Please, contact Sana Support to generate the Sana license to be able to access Sana Apps.

Step 6: Define on which domains the webstore will be running. Several domains can be specified. To separate multiple domains, use line breaks, the ";" or "," character.

If multiple domains are used, the first domain is used as the default one.

 NOTE

If localhost domain is used for running the webstore, the Default Web Site in Internet Information Services (IIS) Manager must be stopped.

Step 7: On the Database tab, specify the database connection parameters.

• Server name: the name of the SQL Server database instance.
• Database name: the name of the SQL database. Enter the new database name or select the existing one (in this case it will be re-created). Do not use interword spaces in the database name.

 NOTE

Windows Authentication must be used to retrieve the list of database names.

 NOTE

Sana Commerce SQL database can be also hosted on Windows Azure. To restore the Sana SQL database to Windows Azure, you must specify the name of your Windows Azure SQL Database instance in the "Server name" field and use the SQL Server Authentication.

Step 8: In the "Log on to server" section, set the administrator credentials of the SQL database.

Step 9: Specify the database user credentials:

• Database user
• Database user password

This user is automatically created in the database as a database owner. The database user is connected to the Sana database. Non-existing user name must be specified.

Step 10: On the SMTP configuration tab, enter SMTP settings: host and port. You can configure a local service that relays to a real SMTP server or an alternative SMTP server can also be used. To establish SSL connection with the SMTP server, select the "SSL enabled" checkbox.

Step 11: On the Security tab, add the SSL certificate and enter the password, if it is password-protected.

SSL certificate is issued by a certificate authority (CA), which takes steps to verify that your web address actually belongs to your organization. The Web server where you install the Sana Commerce solution must support TLS 1.2.

SSL certificate uses advanced encryption to prevent hackers from reading any data that passes to or from a web site. Thus, the Sana Commerce Installer installs Sana with the SSL certificate right away, so the entire Sana Commerce solution, both Sana webstore and Sana Admin, will run over HTTPS.

 NOTE

If you don't have the SSL certificate yet, you can install Sana without it, and secure your webstore with SSL once you obtain the security certificate.

For more information, see "HTTPS".

Step 12: Click Run installation.

 NOTE

If  you click "Run installation" and nothing happens, and the following error is shown in the status window: "File run.ps1 cannot be loaded. The file run.ps1 is not digitally signed. You cannot run this script on the current system.", then you need to unblock Windows PowerShell script files in the Sana Commerce Installer package.

In some cases, the Windows PowerShell script files of the Sana Commerce Installer are blocked by the operating system, when they are downloaded from the Internet. Usually, the Sana Commerce Installer is able to bypass this blocking and the scripts can be executed without any problems even if they are blocked by the operating system.

In case you have encountered the above mentioned issue, open the "Files" folder of the Sana Commerce Installer (Sana Commerce [version]\Installer\Files), right-click on the "*.ps1" file, and select "Properties". In the file properties, under the "General" tab, click "Unblock". You must unblock all "*.ps1" files that are stored in the "Files" folder of the Sana Commerce Installer.

When you unblock all "*.ps1" files, run the Sana Commerce Installer again.

When the installation process is finished, Sana Admin will open in the default Web browser. You will be asked to create the first Sana Admin user. This user will have the System administrator role. System administrator has full access to Sana Admin.

In Sana Admin, click View webstore at the top to open the webstore.

When Sana Commerce is installed and the first user with the System administrator role is created, you should make some first steps that allow you or other Sana Admin users proceed to managing the Sana webstore. For more information, see "Getting Started".

Sana with the integrated pipeline mode

Starting from version 9.3.2, Sana supports the integrated pipeline mode of the application pool.

This can be useful to those who use Microsoft Azure Application Insights as it does not support the classic pipeline mode. Azure Application Insights is a powerful tool which can help you to monitor your web store and automatically detect performance issues. You can use this service to constantly improve performance and stability of your web store and find out the root cause of the issues, if there are any.

In the Internet Information Service (IIS) Manager, application pool can run either in the classic or integrated pipeline mode. The application pool mode affects how the server processes requests for managed code. In Sana 9.3.2, a user who installs Sana on the Web server should enable the integrated pipeline mode for the Sana application pool in IIS manually, if necessary.

When you install Sana 9.3.3, the integrated pipeline mode is enabled by default, but you can still change it manually to classic in IIS, if necessary.

As the integrated pipeline mode does not support Basic Authentication, the Anonymous Authentication is used for all deployment types in Sana 9.3.3.

The only difference between the test, beta and live deployment types is that when you install Sana on the test environment, the web store and Sana Admin are not externally accessible unlike the beta and live deployments. There is no NT popup regardless of the deployment type you select.

When Sana is installed, you can still change the pipeline mode of the application pool to classic and set up Basic Authentication manually, if necessary.

 NOTE

As an alternative, you can use the Sana feature called "Pre-Live Mode" for your webstore. It makes the webstore inaccessible to external users and not indexable by search engines but only on the Sana Framework level. For more information, see "Sana Pre-Live Mode".