1. Create your first store front. Open the Setup menu -- Select store front to edit.

2. In the entry field for the name of a storefront, replace the words "DEFAULT" with a name that will be used to reference your store front (ie. "MyStore"). You can have up to 100 different storefronts as long as they all have different names. 

• This value is typically set to the same name as the DSN for this storefront.
• It is strongly recommended that you keep the names less than 20 characters.
• Spaces and punctuation other then "_" underscores are not legal syntax for a store front name.

Depending upon the speed of your computer, it may take a few minutes to compete creating the store front and sample web site.

Note: The following is created during this process:

• A web configuration files directory and files are created - "<your store front name>.store"
• A robot configuration file is created - "..\SendSafe\<your store name>.store.config"
• A sample store front is created - "..\SendSafe\<your store name>.store\html"

3. Check the ODBC DSN information in the storefront config file i.e. MyStore.store.config
(see database setup see also ODBC Database Connection).

1. ENABLE DATABASE = YES
2. ODBC DSN = MyStore
3. SECURE ODBC DSN = MyStoreCC
4. ODBC USERID = JsofUser
5. DBC PASSWORD = [entered directly or via dialog box]
6. SECURE ODBC USERID = JsofUserCC
7. SECURE ODBC PASSWORD = [entered directly or via dialog box]

4. Enter the ODBC DSN information into the Storefront config file: SendSafe.global.asa located in the storefront subdirectory of the program files i.e. ..\SendSafe\mystore.store\asp\SendSafe (see robot directory structure).

Application("odbcAdmin_DSN") = "MyStore"
Application("odbcAdmin_USERID") = "WebAdmin"
Application("odbcAdmin_PASSWORD") = "WebAdminPassword"

Application("odbcShopping_DSN") = "MyStore"
Application("odbcShopping_USERID") = "PubUser"
Application("odbcShopping_PASSWORD") = "PubUserPassword"

5. Enter the store description information into the Storefront config file: SendSafe.global.asa located in the storefront subdirectory of the program files i.e. ..\SendSafe\mystore.store\asp\SendSafe (see robot directory structure).

Application("StoreCode") = "MYSTORE"
Application("ORDERQUEUEDIRECTORY") = "d:\sendsafe\input"
Application("auditFileRootLocationAndName") = "d:\sendsafe\audit\ASPCGUI.AUDIT"

The entry "StoreCode" must be the name of the storefront i.e. "MyStore"

The entry "ORDERQUEUEDIRECTORY" is the location (full path spec) where the GUI ASP logic will queue orders. This location must be the same as EMSG INPUT PATH in the storefront config file. This location must be accessable by the http server's NT Service Account.

The entry "auditFileRootLocationAndName" is the location (full path spec)where the ASP GUI will create audit log files. For performance reasons, it is strongly recommmended that a physical hard disk different than the website (webserver) be used. This location is often the same location that Robot keeps its audit files (see AUDIT FILE LOC). This location must be accessable by the http server's NT Service Account.

NT/2000 File r/w permission for the IIS Anonymous User Account must be set for the directories that are defined by:

• Application("ORDERQUEUEDIRECTORY")
• Application("auditFileRootLocationAndName")

*Warning! If you are running Norton AntiVirus products (or other security products). These products may block server backend vbScript FileObject Read/Write operations. Make sure that Scripting is not blocked. This is a configuration item in Norton AV products. The symptoms of AV blocking are: no error messages, the webpage seems to hang, and you will find no audit information in the auditFileRootLocationAndName directory.

6. Build the database tables by performing these step below. These scripts should be run from the "sa" DB account or an account with full admin privileges.

1. Edit the SQL Script located in the database subdirectory of the installation; Script Name: Add All open SendSafe database tables.sql. Change the "set @storename = 'MYSTORENAME'" line so that MYSTORENAME = the name you used for the storefront in prior installation steps.
2. Run the SQL Script "Add SendSafe database tables.sql" on your base database (MyStore - not MyStoreCC).
3. Run the SQL Script "Add Secure SendSafe database tables.sql" on your CC base database (MyStoreCC - not MyStore).

Running these two scripts will create all the tables and entries needed by your storefront. Note: This database will contain a default admin user account and some test products. This account and products should be removed before going live with the store.

The default superuser account will have the following credentials: userid / password. Changes these immediately.

7. Import E-Store framework Demo DB Tables
If you purchased the optional e-store framework, you should import the demo items into the database. To perform this import using MS SQL:

1. Open the Enterprise Manager
2. Select the "MyStore" database created earlier
3. Use MS DTS to import the "E-StoreFrameWorkDemoItems.mdb" Access DB tables into the items and itemsext tables. This Access DB is located in the \database\ directory in the SendSafe installation directory.

8. Default Accounts
The "Add SendSafe database tables.sql" script which created the database tables also created entries in these tables for a default storefront AND a default Admin account.

The default ADMIN account will be used to access SendSafe admin pages. You should change this account before you go live with the website (instructions). The credentials for this account are: USERID = "userid" and PASSWORD = "password"

9. Optionally use the online Import Tool to import your products:

Database tool for importing the Customers
Database tool for importing the dealers
Database tool for importing Items
Database tool for importing coupons