When you are ready to deploy your storefront to a production server such as a shared hosting or dedicated server please follow these steps:
Step1: Compile the Storefront
| • | Before deploying the storefront to production, you should compile the storefront using the "Publish" option in Visual Studio |
| • | Upload the compiled storefront to your production server using FTP |
Step 2: Configure Internet Information Services (IIS)
Create a new Website or Virtual Directory
| • | Open Internet Information Services using the Microsoft Management Console. |
| • | Configure a new virtual directory or website in IIS |
| • | In the Directory setting enter the path to the "Web" folder for the compiled storefront. Click Next. |
| • | Make sure that the Access Permissions are set to "Read" and "Run scripts (such as ASP)". Click Next. |
| • | Click Finish in the Virtual Directory or Website Creation Wizard. |
Configure the Website or Virtual Directory
| • | Edit the "Properties" for your Website or Virtual Directory. |
| • | Click on the "ASP.NET" tab of the property page. |
| • | Under "ASP.NET version" select "2.x.xxx". A screen shot of what this property page should look like is below. |
Step 3: Configure Permissions
Configure permissions based on your operating system as follows:
Windows XP
The ASPNET user should have:
| • | Read permissions at the "Web" folder level |
| • | Read + Write + Modify permissions at the "Web/Data" folder level. |
Windows 2003 or 2008 Server
The Network Service account should have
| • | Read permissions at the "Web" folder level |
| • | Read + Write + Modify permissions at the "Web/Data" folder level |
Windows Vista
The Network Service and IUSR account should have
| • | Read permissions at the "Web" folder level |
| • | Read + Write + Modify permissions at the "Web/Data" folder level |
Step 4: Install the Storefront Database
| • | Create a new database in SQL Server 2005 called "znode_storefront". |
| • | Add a SQL User with DBO access to this new database. You can alternatively use Windows authentication if you prefer. |
| • | Open Query Analyzer and run the script "znode_storefront_database.sql" that you used in your development environment. If you had changed the database in your development environment then you must restore the modified database to production. |
Step 5: Configure Web.Config Connection String
| • | Open the web.config file in your website under the root folder |
| • | Edit the connection string to point to your new database. Change the data source, initial catalog, user id and password to the new settings. The connection string looks like this: |
<connectionStrings>
<add name="ZNodeECommerceDB" connectionString="Data Source=LOCALHOST\SQLEXPRESS;
Initial Catalog=znodestorefront;user id=znodeuser;password=p@ssw0rd" />
</connectionStrings>
| • | If your SQL Server is configured to use Windows Authentication only then you should change the connection string to use Integrated security instead. |
Step 6: Test the Site Configuration
| • | Open the storefront by going to http://<your-storefront>/default.aspx.(replace "<your-storefront>" with the domain name of your store). You will be prompted to activate a valid storefront license. After you activate a valid license you can browse the store. |
| • | You can open the diagnostics page by going to http://<your-storefront>/diagnostics.aspx . |
| • | On the diagnostics page you will clearly see if you are connecting to the database and if you have the correct permissions set on your directories. If you see an error about the SMTP service not being set up correctly don't worry. You can set this up later in the Admin (see Post Install). |
Step 7: Administer the Storefront
| • | Open the storefront administration site by going to http://<your-storefront>/admin/ using your browser. |
| • | Login with the default admin account (note that if you had changed the admin credentials, you must use those instead): UserID = admin Password = admin |
| • | This should open the admin dashboard page. You can now start managing your catalog and customers! |
See Also