Developer Workstation Installation

Step 1: Locate the Sana Commerce release package and copy it to a temporary folder on the target web server.

Step 2: Create a root folder for the SC solution in the file system on the production server. This can be done in any location, but it is preferred to keep the server consistent. So if other web solutions are also running on the production server in a certain 'root' folder (for example: 'c:\inetpub\wwwroot\'), install the SC solution also in it.

Step 3: Copy folders 'Ready To Deploy\Frontend' and 'Ready To Deploy\Backoffice' from the release package into this root folder.

Step 4: Create the folder where the log files will be stored in the root folder of the SC solution.

Step 5: Create the folder where the index files will be stored in the root folder of the SC solution.

Step 6: Give the SC_Webuser 'Read & Execute' rights to the frontend folder.

Step 7: Give the SC_Webuser 'Read & Execute' rights to the backoffice folder.

Step 8: Give the SC_Webuser 'Modify' rights to the 'files' folder ('Frontend/content/files'). This is necessary to be able to upload files to the server with a FTP account and through the backoffice (described later).

Step 9: Give the SC_Webuser 'Modify' rights to the 'css' and 'Scripts' folders ('BackOffice/css' and 'BackOffice/Scripts').

Step 10: Give the SC_Webuser 'Modify' rights to the 'css' and 'script' folders ('Frontend/content/css' and 'Frontend/content/script').

Step 11: Give the SC_Webuser 'Write' rights to the folder where the log files are stored of the SC solution on the production server. This is necessary, because the process runner will create log files dynamically in this folder.

Step 12: Give the SC_Webuser 'Modify' rights to the folder where the index files are stored. This is necessary, because the 'Index' task will create the index files in this folder.

Step 13: Give the SC_Webuser 'Modify' rights to the 'C:\WINDOWS\Temp' folder. This is necessary, because generated by IIS temporary files are stored in this folder.
You will see the warning message 'You are about to change the permission settings on system folders, which can result in unexpected access problems and reduce security. Do you want to continue?'. Click 'Yes'.

Step 14: Make the SC_Webuser the member of the 'IIS_IUSRS' group:

• Go to 'Administrative Tools -> Computer Management -> System Tools -> Local Users and Groups -> Users';
• Open the 'SC_WebUser Properties' window and go to the tab 'Member Of';

• Add the IIS_IUSRS group to the list and click 'OK' or 'Apply' to apply the changes:
  
  
  Making the SC_Webuser the Member of the 'IIS_IUSRS' Group

Step 15: Add the SC_Webuser to the 'Log on as a service' policy (go to 'Administrative Tools - Local Security Policy - Local Policies - User Right Assignment', select 'Log on as a service' and add SC_Webuser to the list):


Adding SC_Webuser to the 'Log on as a Service' Policy

If you use Windows Server 2008 'Log on as a batch job', rights should be given to the SC_Webuser. In order to do this: Step 1: Open the 'Microsoft Management Console' (Click 'Start > Run' and run 'gpedit.msc'). Step 2: Go to 'Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment'. Step 3: Select 'Log on as a batch job' policy. Step 4: Add the SC_Webuser to the list by clicking the 'Add User or Group' button and selecting this user (you can use the 'Check names' option for quick search for the correct user). Step 5: Click 'OK' to save the changes. More information about the 'Log on as a batch job' can be found here.