StoreFront 7.0 Setup Guide

 

1. Create SQL DB

2.  Download Files and Install to site.

3.  Set permissions:  see below

Create a Remote Web Store

Follow the instructions below to create a new remote web store using an MS SQL Server database. Before you begin constructing the store, make sure that your host can support it; see Choosing a Host for more information.

  1. Have your host create a new, empty database on one of their SQL Servers for you to use. Your SQL Server user account must be part of the db_owner group. Your host should also create a new, empty web site for your use.
  2. Upload a copy of the downloaded StoreFront software files to the empty web site provided by your host. Ask your host if you do not know how to do this or don’t know your FTP connection information.
  3. Set the IIS/NTFS permission requirements for StoreFront 7 (you may have to have assistance from your host):
    • At the root of the site directory the ASPNET user must have Modify permission and the additional permission to “Delete Subfolders and Files”.
    • Enable anonymous access and only “basic” authentication the site root folder.
    • Disable anonymous access on the following files and folder to allow only the web store owner and other authorized users to access them.
      • ReloadXML.aspx file – found in the site root and site root/SSL folder.
      • CompileSite.aspx file – in the site root folder.
      • Authentication folder – in the site root/SSL/Management folder.
      • Integration folder – found in the site root/SSL/Management folder.
      • RMS23confirm.aspx file – found in the site root and site root/SSL/Management folder.
      • RMS23output.aspx file – found in the site root and site root/SSL/Management folder.
      • RMS23confirmws.asmx file – found in the site root and site root/SSL/Management folder.
      • Clientaccess.aspx file – found in the site root and site root/SSL/Management folder.
  4. Edit the database connection string which is found in the web.config to include your database information. Ask your host for this information if you do not know it. Example: Change the four items in bold
    • The web.config file is in site root folder
  5. Have your host run the SQL script named SF7.sql on the database they have created for you. This file is found in the db folder of your site files. When executed using query analyzer, it will create the database table structure for your store.   ON SQL SERVER DESKTOP
  6. Open the admin table of your MS SQL database and configure the following fields with the settings specific to your web store
    • EmailMethod – Email Methods StoreFront 7 supports: CDONTS Mail, CDOSYS Mail, CDONTS/CDOSYS Mail, ASP Mail, ASP QMail, SimpleMail 3, J Mail, ASP Email, AB Mail and OCX Mail. Ask your host if you are unsure which method they support.
    • EmailServer – Example: mail.mydomain.com (ask your host if you’re not sure)
    • PromoMailServer – Example: promomail.mydomain.com (ask your host if you’re not sure)
    • SSLPath – Example: http://localhost/mySF7store/SSL/ (must end with a trailing back slash / and typically won’t be https:)
    • SiteURL – Example: http://localhost/mySF7store/
    • Close the database
  7. You’re now ready to access your store for the first time.
  8. Open Internet Explore and type the URL remote store.
    • Example http://www.mydomain.com
  9. The URL to your merchant tools will be the path you set for the SSLPath plus the word management.
    • Example http://localhost/mySF7store/ssl/management/

 

Note:  When securing the  /ssl/managment folder use the Windows Server User to add to the /ssl/managment folder

The best practice is to use the Frontpage Account user that is setup already in HELM Example:  cybersharks.net_fp

This way the user still has control of the password if they feel like updating the password themselves

To Setup E-mail.

Make sure the e-mail components are installed on server.  Edit the database by using "CDONTS/CDOSYS Mail" or "ASP mail"

After you make a manual change in the DB you will have to compile the website and use the reloadxml.aspx to "Reload" the new changes.