1. Følg med
  2. Blog
  3. 2010
  • Publisert
  • 4 min

EPiServer Commerce installation - redoux!

Installation of EPiServer Commerce is actually quite straight-forward, but there are a lot of steps involved and there's a good chance you'll miss a few details.

Av Arild Henrichsen

 

After spending (wasting) some time tinkering with the EPiServer Commerce installation, having to begin all over a few times before finally getting it right, I decided to write down a step by step installation guide as a reminder to myself and hopefully help to others.

Overview:

This guide actually does not add much to EPiServer's official Commerce installation guide, but is structured a little differently to make sure you remember all those small details. Specifically, the "Database configuration" part of the MediaChase ECF installation is a bit ambigously explained in EPiServer's guide.

The official installation guide have already provided fancy screenshots, so I won't be repeating those here - text only :-) In this guide I will be using dummy (default) user account and site names - substitute your own where appropriate.

Note: This guide applies to EPiServer Commerce 1.0 SP1.

 

1. Prerequisites

1. Download and install ASP.NET MVC 1.0:

2. Download and install EPiServer Commerce 1.0 SP1:

3. Download and install EPiServer Commerce Sample pack:

4. Obtain the following licenses:

  • EPiServer 6 license: (optional during install, but required to view site after Commerce installation)
  • EPiServer Commerce license (required for installation)
  • http://license.episerver.com

 

2. SQL Server preparations

UPDATE: If Web site and databases are installed on the same machine, you might be able to use SQL Server 2005. If Web site and databases are on different machines, SQL Server 2008 R2 seems to be required. See Troubleshooting section.

  • Create new login (admin/store)
  • Uncheck "Enforce password policy"
  • Server roles: public, sysadmin (no user mapping)

 

3. Hosts file (if applicable)

  • Add entry "127.0.0.1 commercedemo" (for store site)
  • Add entry "127.0.0.1 commercedemofw" (for store backend site)

 

4. Installing the store site

Deployment Center: EPiServer CMS > Version 6.0.530.0 > Install site and SQL Server database

  • Name: commercedemo
  • Database: dbCommerceDemo
  • SQL authentication (for installer): admin/store (same as created before)
  • SQL authentication (for site): dbUserCommerceDemo/dbP@ssword1
  • It is not necessary to install Public Templates.
  • Finish installer and test that site is browseable.

 

5. Installing Commerce

Deployment Center: EPiServer CMS > Version 6.0.530.0 > Install EPiServer Commerce

Step 1 (We can have lots of fun):

  • Check all boxes > Next

Step 2 (There's so much we can do):

  • Server name: <hostname>\sqlexpress
  • Site dabase name: dbCommerceFW
  • SQL authentication - database owner: dbUserCommerceDemo/dbP@ssword1 (same as created before)
  • SQL authentication - SQL admin: admin/store (same as created before)
  • Next

Click "New site":

  • Web site title: CommerceDemoFW
  • Port: 80
  • Host header: commercedemofw
  • Path to root: <yourpath>\commercedemofw
  • Next
  • Check "Install Quartz service" only
  • Next > ECF installs > Finished

Step 3 (It's just you and me):

  • Select "CommerceDemo" site as target for installation
  • Next

Step 4 (I can give you more):

  • Keep default path
  • Next

Step 5 (Don't you know that the time has arrived):

  • Browse to EPiServer Commerce license file > Install
  • Finish

 

6. Installing Commerce Sample Pack

Deployment Center: EPiServer CMS > Version 6.0.530.0 > Install EPiServer Commerce Sample

Step 1:

  • Check all boxes
  • Next

Step 2:

  • Select "CommerceDemo" site as target for installation
  • Next (extracts sample product catalog)

Step 3:

  • Install (installs sample templates and products)
  • Finish

 

7. Configuring Commerce backend

Be sure to follow the instructions in the post-installation configuration guide:

http://world.episerver.com/Documentation/Items/Tech-Notes/EPiServer-Commerce/EPiServer-Commerce-101/Post-installation-Configurations---EPiServer-Commerce-10-SP1/

 

8. Testing the installations

Store site:

  • Browse to: http://commercedemo - should display the demo store "Click + Talk".
  • To login, click the link in the upper right corner or go to: http://commercedemo/util/login.aspx
  • Default user account is:  admin/store

 

Backend system:

  • Browse to: http://commercedemofw - should display the backend system login page.
  • Default user account is: admin/store
  • Hopefully by now things will be up and running! 

 

9. References

Official installation guide:

Post-installation configuration guide:

More about the MediaChase ECF installer:

 

10. Tips & Troubleshooting

  • You'll need a Windows user account with admin privileges to install Commerce properly on your server / local machine.
  • The SQL admin account used in the Commerce installation must be given sysadmin privileges
  • Take things slowly and try to do the steps separately, e.g. install EPiServer 6 site first WITHOUT checking the "Install EPiServer Commerce" box, then install Commerce separately afterwards. It might just save you some rollback time if something goes wrong.
  • During the Commerce (MediaChase ECF) installation, remember to use a  previously created database owner account (e.g. the db user created during the EPiServer 6 site installation). It is possible to let the installer do this by specifying a new username/password in the wizard, but in my experience this does not always work as expected.
  • Remember to disable or change password on the default admin account after everything is set up :-)
  • UPDATE: If you get an error on any of the steps of the ECF installation, be sure to delete any traces of the failed installation before retrying. I.e, delete the web site entry and application pool that was created in IIS, and delete the folder where the web site was installed on your disk. Also delete the database if it was created.
  • UPDATE: During ECF installation, you might get the error "sqlcmd is not a recognized internal or external command, operable program or batch file" at step 4: Setting up the site database.
    This typically occurs if databases are not being installed on the same machine as the Web site. You'll need to download and install the Native Client and Command Line Utility for SQL Server 2008 R2 on the machine you are running the Commerce installation from, and the filepath to the sqlcmd executable must be put in the Windows %PATH% before beginning the Commerce installation.

    The SQL Server utilies can be downloaded here:
    http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ceb4346f-657f-4d28-83f5-aae0c5c83d52&displaylang=en