Development Installation

Please see the steps below to install Multifront on your development environment. Note that you should check your system requirements before proceeding

Step 1: Install the Multifront MSI

•	After you purchase Multifront, you will receive a link to download an installer (MSI)

•	This installer will deploy all the Multifront code and utilities to your computer

•	Note that you do not need to run this MSI on a production server - you can upload the compiled files using FTP. See Production Server Installation for further instructions.

Step 2: Create the Database

•	The database creation script can be found under the $ProgramFiles$\Znode\$Edition$\SQL folder

•	Open SQL Server Enterprise Manager using an administrator account

•	Run the znode_multifront_database.sql script. This will create a new database called znode_multifront

•	Create a SQL Login with userid = znodeuser with password = p@ssw0rd (note that you can create a different sql login or use windows authentication - in those cases you need to update the web.config appropriately)

•	Assign DBO permissions to the znodeuser login for the znode_multifront database

Step 3: Configure the Store URL

•	By default your storefront is configured to run under the following urls:

http://localhost/

http://localhost/b2b

http://localhost/Speciality

http://localhost/web

This should allow you to run directly from Visual Studio with no changes required.

•

If you can not run your store through one of these URLs then you will need to manually update the ZNodeDomain table in the database. Just substitute one of these entries with your store URL in the DomainName column. Both the "www" part of the domain and the port number will be ignored when mapping store URLs so don't include them in your entry. Since these entries are cached in memory you may need to recycle the application pool for the change to take effect.

•

Once your store is up and running, you can add or change URLs using the Store section of the admin. In order to get your computer to resolve URLs other than http://localhost that point back to your system you will need to add new entries to the Windows hosts file. (tip: when adding URLs for testing use "localhost" in the name such as "store1.localhost". This will prevent the storefront from requesting a license key on your development system).

Step 4: Open the Visual Studio Solution

•	The Visual Studio solution can be found under the $ProgramFiles$\Znode\$Edition$\WebApp folder.

•	Open the solution using Visual Studio 2008.

•	Once the solution is open, you must update the database connection settings in the web.config file.

•	Compile and run the solution in Visual Studio - this will open the Multifront demo web site. You should be able to navigate the demo store and try out the different storefront functionality.

64 Bit Support

By default Multifront is delivered to run on mixed platforms (32 bit and 64 bit). You will need to make some adjustments to your IIS settings to run Multifront in compatibility mode on 64 bit systems. If you need to run in 64 bit mode on your server a special versions of the base and payment libraries has been provided. These libraries can be found in \Maintenance\64 bit Support\ folder. Drop these DLL's into your WebApp\bin directory and recompile your application for a 64 bit platform.

Step 5: Administering Multifront

Site Administration

If you have the Multifront or Marketplace products you can administer across all stores and users using the Site Administration pages.

•	You can access the storefront management tool using http://$YourWebsite$/siteadmin

•	The default credentials are: UserID=admin and Password=admin - You will be prompted to change the password the first time you login

Franchise Administration

If you have the Marketplace product, franchise store administrators can manage their sites using the Franchise Administration pages.

•	You can access the franchise store management tool using http://$YourWebsite$/franchiseadmin

•

Franchise administrators must first go to the franchise admin login page and click "Request a Franchise Store Admin login." link to request a login. A site administrator (using http://$YourWebsite$/siteadmin) must then enable the requested account before the franchise administrator will have access to the site.

Mall Vendor Administration

If you have the Marketplace product, mall store vendors can manage their products using the Mall Administration pages.

•	You can access the mall product management tool using http://$YourWebsite$/malladmin

•	Mall vendors must first go to the mall admin login page and click "Request a Mall Admin login." link to request a login. A site administrator (using http://$YourWebsite$/siteadmin) must then enable the requested account before the mall vendor will have access to the site.

Step 6: Diagnostics

•	Browse to the http://$YourWebsite$/diagnostics.aspx page to run detailed diagnostics and application trace on your storefront installation.

•	You can also inspect the log files that can be found under WebApp\Data\Default\Logs folder - this can help debug various issues.

Note that you must have the following settings in your web.config file to enable these diagnostics:

Step 7: Apply Patches

•	Open a browser to http://www.znode.com/support/downloads.aspx to download the latest patches for your version of the software.

•	Apply the patches to your source code, recompile and test.

Step 8: Enabling the Specialty and B2B Stores (optional)

The Znode demonstration store has three tabs at the top that are used to highlight the multi-store capability. These tabs have hard coded links to <your site URL>/Specialty and <your site URL>/B2B. To get these tabs to work you must create virtual directories for these web sites. This is not a typical configuration for a production environment. We set up our demo store in this way only because it is difficult to get multiple domains to point to a local development PC. If you are doing development, it is generally preferable to just view one web site at a time inside the Visual Studio debugger (see Step 4).

To configure a web site using virtual directories you will need to set up your web site in IIS. Before deploying Multifront 6.3+ to IIS, you must compile the application in Visual Studio or the ASP .NET compiler.

You need to create a 2 virtual directories for the Multifront project that map to the MultiFront “WebApp” directory. The following table shows the mapping between the physical location of the files and the URL that accesses the files.

Physical Location	Alias	URL
$ProgramFiles$\Znode\$Edition$\webApp		http://localhost
$ProgramFiles$\Znode\$Edition$\webApp	b2b	http://localhost/b2b
$ProgramFiles$\Znode\$Edition$\webApp	Speciality	http://localhost/Speciality

Both virtual directories and physical directories appear in IIS Manager. A virtual directory is indicated by a gear icon. The following illustration shows the Web site example described above, where /B2B and /Speciality are virtual directories in IIS 6.

IIS Configuration

To create a virtual directory using the Virtual Directory Creation Wizard

1.	Click Start, click on Control Panel, click to select Administrative Tools, and then click Internet Information Services (IIS) Manager.

2.	In IIS Manager, Double-click the local computer, double-click on sites, right click on Default Web Site, click Add Application.

3.	In the Add Application window, type a name for the virtual directory. The alias is the name that the user types, and it should be short and easy to type.

4.	Now browse to the Physical Path where the virtual directory resides.

5.	Verify the details and then click OK.