Commerce Server 2002 Starter Site Installation Guide

This guide provides detailed steps for installing and configuring a single development computer with the Microsoft® Commerce Server 2002 Starter Site. The installation guide first lists the hardware and software guidelines, followed by the instructions for installing and configuring the prerequisite software. The guide provides detailed steps for installing and unpacking the Commerce Server 2002 Starter site, and then provides post-installation requirements. For information about the Commerce Server 2002 Starter Site and download page, see http://go.microsoft.com/fwlink/?LinkId=37800.

This section contains:

Hardware Requirements

Following are the hardware requirements for the Commerce Server 2002 Starter Site. The hardware requirements are the same as the Commerce Server 2002 hardware requirements, which can be found at http://go.microsoft.com/fwlink/?LinkId=36703.

Software Requirements

The base platform for the Commerce Server 2002 Starter Site requires the following software products:

Product Description
  • Microsoft® Windows® 2000 Server or Microsoft Windows 2000 Advanced Server with Service Pack 4

    - OR -

  • Microsoft® Windows Server™ 2003 Standard or Enterprise Editions
Provides platform security and Web site administration through Microsoft Internet Information Services (IIS).
Note Windows Server 2003 is the recommended platform for a Commerce Server 2002 Starter Site.
  • Microsoft® SQL Server™ 2000 Enterprise Edition with Service Pack 3 (SP3)
Provides the underlying database services in Commerce Server 2002 with the latest updates and fixes including security features and tools.
  • SQL Server Analysis Services with Service Pack 3 (SP3)
Used by the Commerce Server Data Warehouse to access the OLAP database.
  • Microsoft Commerce Server 2002 Enterprise Edition with Service Pack 3 (SP3)

    - OR -

  • Microsoft Commerce Server 2002 with SP3 and Feature Pack 1 (FP1)
Commerce Server 2002 with SP3 contains a collection of hotfixes and security fixes.

Commerce Server FP1 adds new functionality to Commerce Server for managing catalogs and discounts.

  • Microsoft .Net Framework 1.1
You must install the Microsoft .NET Framework 1.1 on a Windows 2000 Server platform. Windows Server 2003 installs Microsoft .NET Framework 1.1 by default.

Installing and Configuring the Commerce Server 2002 Starter Site Base Platform

This section provides detailed instructions for the installation and configuration of the Microsoft® Commerce Server 2002 Starter Site base platform. This section lists prerequisite software and Commerce Server 2002 installation instructions.

For the development computer, you must do the following in the order listed:

  1. Install and configure the base platform. Install the Microsoft® Windows® Server 2000 or Microsoft Windows Server™ 2003 operating system. Add Windows components, obtain the latest Windows Server 2003 updates, and create the administrative account.
  2. Install and configure all the prerequisite software on the development server.
  3. Install and configure Commerce Server 2002 with Service Pack 3, or Feature Pack 1.

Best Practices

As you complete the steps in this section, consider the following best practices:

This section contains:

Installing and Configuring the Base Platform

You install the base platform on the developer computer using either Microsoft Windows 2000 Server or Microsoft Windows Server 2003. After you install the base platform, must configure it.

This section contains:

Installing the Base Platform

You install the base platform on the developer computer using Microsoft Windows 2000 Server or Microsoft Windows Server 2003.

Important When you install the base platform, the installation process overwrites all data on the computer.
Note The computer must be able to restart from the CD drive to follow these steps.

This section contains:

Installing Windows 2000 Server

If you install Windows 2000 Server with Service Pack 4 as your base platform, you must install Microsoft .NET Framework 1.1.

Note Windows Server 2003 installs Microsoft .NET Framework 1.1 by default.

This section contains:

Installing Windows 2000 Server with Service Pack 4

Installing Microsoft .NET Framework 1.1

Installing Windows 2000 Server with Service Pack 4

The following step describes how to perform a clean installation of Microsoft Windows 2000 Advanced Server with Service Pack 4 on a development computer.

To install Windows 2000 Advanced Server with Service Pack 4

  1. Insert the Windows 2000 Advanced Server CD into the CD drive, and then restart the computer.
  2. Start the computer and when the prompt appears, press any key to start from the CD.
  3. In the Windows 2000 Server Setup screen, press ENTER to start the Windows 2000 Advanced Server Setup program.
  4. On the Windows 2000 Licensing Agreement page, read the End User Licensing Agreement. If you agree, press F8.

    If the computer already has a version of Windows installed, the Repair screen will appear. Press ESC.

  5. On the Windows 2000 Server Setup page, delete any existing partitions, and then press C to create a new partition.
  6. Press ENTER to accept the default value for the maximum partition size.
  7. Use the UP and DOWN arrow keys to select the new partition, and then press ENTER to install Windows 2000 Advanced Server in that partition.
  8. Use the UP and DOWN arrow keys to select NTFS as the file system, and then press ENTER to format the partition using that file system.

    The Setup program formats the hard disk and proceeds to install the files needed to continue installing Windows 2000 Advanced Server.

  9. In the Windows 2000 Server Setup Wizard, on the Regional Settings page, click Next to accept the default settings for U.S. English, or click Customize to modify the regional settings.
  10. On the Personalize Your Software page, do the following:
    Use this To do this
    Name Type your name.
    Organization Type your company or organization name.
  11. Click Next.
  12. On the Product Key page, type the product identification number included with your Windows 2000 Advanced Server product CD, and then click Next.
  13. On the Licensing Modes page, select the appropriate option that you have purchased, and then click Next.
  14. On the Computer Name and Administrator Password page, do the following:
    Use this To do this
    Computer Name Type a computer name.
    Administrator Password Type a password for the Administrator account.
    Confirm Password Type the password again.
  15. Click Next.
  16. On the Windows 2000 Components page, make sure that the following check boxes are selected:
  17. Click Internet Information Services, and then click Details.
  18. In the Internet Information Services (IIS) dialog box, make sure that the following check boxes are selected:
  19. Click OK.
  20. On the Windows 2000 Components page, click Next.
  21. On the Date and Time Settings page, confirm that you have the correct values, and then click Next.
  22. On the Networking Settings page, select Custom Settings, and then click Next.
  23. On the Networking Components page, make sure that Client for Microsoft Networks and Internet Protocol (TCP/IP) are selected. Clear the check box for File and Printer Sharing for Microsoft Networks.
  24. If your network assigns IP addresses dynamically, go to step 27. Otherwise, click Internet Protocol (TCP/IP), and then click Properties.
  25. In the Internet Protocol (TCP/IP) Properties dialog box, on the General tab, select Use the following IP address, and then do the following:
    Use this To do this
    IP address Type the IP address provided by your network administrator.
    Subnet mask Type the subnet mask provided by your network administrator.
    Default gateway Type the default gateway provided by your network administrator.
  26. In the Preferred DNS server box, select Use the following DNS server addresses. Type the IP address of the domain controller/DNS server provided by your network administrator, and then click OK.

    This step enables the development computer to resolve the primary domain controller/DNS server.

  27. On the Networking Components page, click Next.
  28. Use one of the following methods:
  29. On the Join Computer to <domain name> Domain page, do the following:
    Use this To do this
    User name Type the name of an account with sufficient permissions to join the domain.
    Password Type the corresponding password.
  30. Click OK.
  31. On the Network Identification page that welcomes you to the domain, click OK.
  32. Windows proceeds to install components. When this process is complete, the Completing the Windows 2000 Setup Wizard page appears. Remove the Windows 2000 Advanced Server CD from the CD drive, and then click Finish to complete set up, and restart the server.
  33. Log on as Administrator, using the password assigned to this server during set up. The desktop appears for the first time, and the Windows 2000 Configure Your Server page appears.
  34. On the Windows 2000 Configure Your Server page, click Finish Setup.
  35. In the Add/Remove Programs dialog box, under Configure Message Queuing Services, click Configure.
  36. On the Welcome to the Microsoft Message Queuing Services Setup Wizard page, click Next.
  37. On the Completing the Microsoft Message Queuing Services Setup Wizard page, click Finish.
  38. In the Add/Remove Programs dialog box, click Close.
  39. The next time that you restart the computer, on the Windows 2000 Configure Your Server page, click I will configure this server later, and then click Next.
  40. On the Windows 2000 Configure Your Server page, clear the Show this screen at startup check box, and then close the page.

To install Windows 2000 Advanced Server Service Pack 4

  1. To install Windows 2000 Advanced Server Service Pack 4, see http://go.microsoft.com/fwlink/?LinkId=5596.
  2. Click the Windows 2000 Service Packs link.
  3. In the Windows 2000 Service Packs screen, click Windows 2000 Service Pack 4.
  4. In the Download section, from the Select language drop-down list, select English, and then click Go.
  5. Click the SP4 Network Installation link, and then download and run the W2KSP4_EN.exe file.

Installing Microsoft .NET Framework 1.1

You must install Microsoft .NET Framework 1.1 on a Windows 2000 Server platform. Windows Server 2003 installs Microsoft .NET Framework 1.1 by default.

  1. In Internet Explorer, locate the Microsoft .NET Framework 1.1 download page at http://go.microsoft.com/fwlink/?LinkId=28437.
  2. Download and run the dotnetfx.exe file.

Installing Windows Server 2003

The following step describes how to perform a clean installation of Microsoft Windows Server 2003 Enterprise Edition on a single computer.

To install Microsoft Windows Server 2003

  1. Insert the Windows Server 2003 CD into the CD drive, and then restart the computer.
  2. Start the computer and when the prompt appears, press any key to start from the CD.
  3. In the Windows Server 2003 Setup screen, press ENTER to start the Setup program.
  4. On the Windows Licensing Agreement page, read the End User License Agreement. If you agree, press F8.

    If the computer already has a version of Windows installed, the Repair screen will appear. Press ESC.

  5. On the Windows Server 2003 Setup page, delete any existing partitions, and then press C to create a new partition.
  6. Press ENTER to accept the default value for the maximum partition size.
  7. Use the UP and DOWN arrow keys to select the new partition, and then press ENTER to install the selected partition.
  8. Use the UP and DOWN arrow keys to select NTFS (Quick) to format the partition, and then press ENTER.

    The Setup program formats the hard disk, and then copies the files needed to install Windows Server 2003. After you copy the files, the computer will restart. The Setup program then starts the Windows Server 2003 Setup Wizard, and displays a countdown time for how long it will take to complete the set up.

  9. On the Regional and Language Options page, click Next to accept the default settings for U.S. English and US keyboard layout. To modify the changes, click Customize or Details.
  10. On the Personalize Your Software page, do the following:
    Use this To do this
    Name Type your name.
    Organization Type your company or organization name.
  11. Click Next.
  12. On the Product Key page, type the product identification number included with your Windows Server 2003 installation CD, and then click Next.
  13. On the Licensing Modes page, select the appropriate option that you have purchased, and then click Next.
  14. On the Computer Name and Administrator Password page, do the following:
    Use this To do this
    Computer name Type the computer name.
    Administrator password Type the password for the Administrator account.
    Confirm password Type the password again.
  15. Click Next.
  16. On the Date and Time Settings page, confirm that the date and time values are correct, and then click Next.
  17. On the Networking Settings page, select Custom Settings, and then click Next.
  18. On the Networking Components page, verify that the check boxes for Client for Microsoft Networks and Internet Protocol (TCP/IP) are selected. Clear the check box for File and Printer Sharing for Microsoft Networks.
  19. If your network assigns IP addresses dynamically, go to step 22. Otherwise, click Internet Protocol (TCP/IP), and then click Properties.
  20. In the Internet Protocol (TCP/IP) Properties dialog box, on the General tab, select Use the following IP address, and then do the following:
    Use this To do this
    IP address Type the IP address provided by your network administrator.
    Subnet mask Type the subnet mask provided by your network administrator.
    Default gateway Type the default gateway provided by your network administrator.
  21. In the Preferred DNS server box, select Use the following DNS server addresses. Type the IP address of the domain controller/DNS server provided by your network administrator, and then click OK.

    This step enables the development computer to resolve the primary domain controller/DNS server.

  22. On the Networking Components page, click Next.
  23. On the Workgroup or Computer Domain page, use one of the following methods:
  24. On the Join Computer to <domain name> Domain page, do the following:
    Use this To do this
    User name Type the name of an account with sufficient permissions to join the domain.
    Password Type the corresponding password.
  25. Click OK.
  26. On the Network Identification page that welcomes you to the domain, click OK.
  27. The Windows Server 2003 installation will complete, and the computer will restart.
  28. Log on as Administrator, using the password you chose during set up.

    The desktop appears for the first time, and the Manage Your Server screen appears.

    If a dialog appears prompting you to adjust your video settings automatically, click OK.

  29. On the Manage Your Server page, select Don't display this page at logon, and then close the page.
  30. Locate the notification area in the lower-right corner of the desktop window, and then click the keys icon to start Windows.
  31. In the Activate Windows wizard, on the Let's activate Windows page, select Yes, let's activate Windows over the Internet now, and then click Next.
  32. On the Register with Microsoft? page, select either Yes, I want to register and activate Windows at the same time or No, I don't want to register now; let's just activate Windows, and then click Next.
  33. On the Thank You! page, click OK to exit the Activate Windows wizard.

Configuring the Base Platform

After you install the base platform, you must add the Windows Server components required by Commerce Server 2002 and obtain the latest critical updates for your Windows Server installation. You must also create the administrative accounts required by SQL Server 2000 and Commerce Server 2002.

This section contains:

Adding Windows Components

By default, Windows Server 2003 does not install all Windows components. The following steps add the server components that Microsoft Commerce Server 2002 needs.

To add Windows Server 2003 components

  1. Click Start, point to Control Panel, and then click Add or Remove Programs.
  2. Click the Add/Remove Windows Components icon in the left column.
  3. In the Windows Components Wizard, on the Windows Components page, select Application Server, and then click Details.
  4. On the Application Server page, select ASP.NET and Message Queuing.
    Note You use Message Queuing for the Coupons (promotion codes) Generation Service in Commerce Server Feature Pack 1.
    The Commerce Server 2002 Starter Site does not support using Promotion Codes. However, you can implement promotion code functionality after you install the Commerce Server 2002 Starter Site. For information about implementing promotion codes, see "Implementing Promotion Codes" in Commerce Server 2002 FP1 Help.
  5. Select Internet Information Services (IIS), and then click Details.
  6. On the Internet Information Services (IIS) page, verify the following are selected:
  7. Click World Wide Web Service, and then click Details.
  8. On the World Wide Web Service page, select all the World Wide Web Service subcomponents, and then click OK.
  9. Click OK to close the Internet Information Services (IIS) page.
  10. Click OK to close the Application Server page.
  11. On the Windows Components page, clear the check box for Internet Explorer Enhanced Security Configuration, and then click Next.
  12. On the Completing the Windows Components Wizard page, click Finish, and then close the Add or Remove Programs window.

Updating Windows 2000 Server

You must install the latest updates for Microsoft Windows 2000 Server to help make sure that your operating system is protected.

To update Windows 2000 Server

  1. See Microsoft Windows Update at http://go.microsoft.com/fwlink/?LinkId=16855 to obtain all available critical updates.
  2. Follow the instructions on the Web page to scan for updates, and install all critical updates and service packs.
  3. Restart your computer after installing all updates.

Updating Windows Server 2003

You must install the latest updates for Microsoft Windows Server 2003 to help make sure that your operating system is protected.

To update Windows Server 2003

  1. See Microsoft Windows Update at http://go.microsoft.com/fwlink/?LinkId=16855 to obtain all available critical updates.
  2. Follow the instructions on the Web page to scan for updates, and install all critical updates and service packs.
  3. Restart your computer after installing all updates.

Creating the Administrative Accounts

The following table describes the purpose of the administrative accounts. It is recommended that you create these accounts now so they will be available when you install SQL Server 2000 and Commerce Server 2002.

Administrative Account Purpose
SQLSvc To run SQL Server Service.
CSSvc To run Commerce Server Services.

Follow these steps to create the administrative accounts for your Commerce Server 2002 Starter Site deployment and to add the Commerce Server Services account (CSSvc) to the IIS Worker Process group.

To create the administrative accounts

  1. Click Start, point to All Programs, point to Administrative Tools, and then click Computer Management.
  2. In the Computer Management window, expand Local Users and Groups, right-click Users, and then click New User.
  3. In the New User dialog box, do the following:
    Use this To do this
    User name Type SQLSvc.
    Full name Type SQLAdmin account.
    Description Type Administrative account for SQL Server.
    Password Type the password for this account.
    Confirm password Type the password for this account again.
  4. Clear the check box for User must change password at next logon, select User cannot change password and Password never expires, and then click Create.
  5. Repeat steps 3 and 4 to create the CSSvc user accounts using the appropriate information.
  6. In the New User dialog box, click Close.

To add the CSSvc account to the IIS Worker Process Group

Note The following steps only apply on a Windows Server 2003 platform.
  1. Click Start, point to All Programs, point to Administrative Tools, and then click Computer Management.
  2. In the Computer Management window, expand Local Users and Groups, click Groups, and then double-click IIS_WPG.
  3. In the IIS_WPG Properties window, click Add, type <computer name>\CSSvc, and then click OK.

Installing Commerce Server 2002 Prerequisite Software

This section provides instructions for installing the prerequisite software that Commerce Server 2002 relies on. Log on using a local Administrator account before installing the following software products.

This section contains:

Installing Microsoft Visual Basic 6.0 Runtime with Service Pack 5

  1. In Internet Explorer, locate the Visual Basic 6.0 SP5: Run-Time Redistribution Pack download page at http://go.microsoft.com/fwlink/?LinkId=36856.
  2. Follow the download instructions to save the file on your computer.
  3. After you download the file, follow the instructions on the download page to install Visual Basic 6.0 with Service Pack 5.

Installing SQL Server 2000 Enterprise Edition with Service Pack 3a

This section contains information about how to install SQL Server 2000 Enterprise Edition, SQL 2000 Analysis Services, and the SQL Server 2000 Service Packs.

To install SQL Server 2000

  1. Insert the SQL Server 2000 Enterprise Edition CD into the CD drive.

    If the Microsoft SQL Server 2000 Enterprise Edition splash screen does not appear, run the Autorun.exe file from the product CD.

  2. In the Microsoft SQL Server 2000 Enterprise Edition splash screen, click SQL Server 2000 Components.
  3. On the Install Components page, click Install Database Server.
  4. On the Welcome to the Microsoft SQL Server Installation Wizard page, click Next.
  5. On the Computer Name page, click Next.
  6. On the Installation Selection page, select Create a new instance of SQL Server, or install Client Tools, and then click Next.
  7. On the User Information page, do the following:
    Use this To do this
    Name Type a user name.
    Company Type the company name.
  8. Click Next.
  9. On the Software License Agreement page, read the End-User License Agreement (EULA), and then click Yes to continue with the installation.
  10. On the CD Key page, type the 25-digit product identification number from the product CD, and then click Next.
  11. On the Installation Definition page, make sure Server and Client Tools is selected, and then click Next.
  12. On the Instance Name page, accept the default name, and then click Next.
  13. On the Setup Type page, select Typical, accept the default installation locations, and then click Next.
  14. On the Services Accounts page, select Use the same account for each service.
  15. On the Services Accounts page, in the Service Settings section, select Use a Domain User account, and do the following:
    Use this To do this
    Username Type SQLSvc.
    Password Type the corresponding password.
    Domain Type the computer name.
  16. Click Next.
  17. On the Authentication Mode page, select Windows Authentication Mode, and then click Next.
  18. On the Start Copying Files page, click Next.
  19. On the Choose Licensing Mode page, in the Licensing Mode section, select the appropriate number of licenses that you have purchased, and then click Continue.

    The installation process starts.

  20. On the Setup Complete page, click Finish.
Note When the SQL Server 2000 Enterprise Edition installation is complete, you must install SQL Server 2000 Service Pack 3a.

To install SQL Server 2000 Service Pack 3a

  1. In Internet Explorer, go to the SQL Server 2000 Service Pack 3a download page at http://go.microsoft.com/fwlink/?LinkId=28434.
  2. In the Download section, from the Select language drop-down list, select English, and then click Go.
  3. Click Download files below, and follow the instructions on the download page to save the file on your computer.
  4. After you download the file, follow the instructions on the download page to install SQL Server 2000 Service Pack 3a.

Installing SQL Server 2000 Analysis Services with Service Pack 3a

The Commerce Server Data Warehouse uses Analysis Services to access the OLAP database. You must install SQL Server 2000 Analysis Services with Service Pack 3a on any computer onto which you unpack the Data Warehouse resource.

To install SQL Server 2000 Analysis Services

  1. Insert the Microsoft SQL Server 2000 CD into the CD drive.
  2. Run the Analysis Services Setup program and follow the online instructions.

To install SQL Server 2000 Analysis Services Service Pack 3a

  1. To install SQL Server 2000 Analysis Services Service Pack 3a, see http://go.microsoft.com/fwlink/?LinkId=28434.
    Note If you receive the following error message when you try to install Analysis Services SP3, see Microsoft Knowledge Base article 834112 at http://go.microsoft.com/fwlink/?LinkId=37364 for information about how to work around this problem.
    "An error occurred during the move data process: -132"
  2. In the Download section, from the Select language drop-down list, select English, and then click Go.
  3. Click Download files below, and then run the sql2kasp3.exe file.

Installing Microsoft Data Access Components 2.8

Skip this section if you are not installing Commerce Server 2002 Feature Pack 1. You must install Microsoft Data Access Components 2.8 on any computer where you run Commerce Server 2002 Feature Pack 1.

To install Microsoft Data Access Components 2.8

  1. To install Microsoft Data Access Components 2.8, see http://go.microsoft.com/fwlink/?LinkId=38046.
  2. Download and run the MDAC_TYP.EXE file.
  3. On the End User License Agreement page, click I accept all the terms of the preceding license agreement, and then click Next.
  4. On the Installing the Software page, click Finish.
  5. On the Restarting the System page, click Let setup restart the system now, and then click Finish.

Installing Microsoft XML Core Services (MSXML)

You use Microsoft XML Core Services (MSXML) 4.0 with Service Pack 2 when importing product catalogs. MSXML 4.0 Service Pack 2 (SP2) is a complete replacement of MSXML 4.0 and MSXML 4.0 Service Pack 1 (SP1).

To install MSXML 4.0 with Service Pack 2

  1. In Internet Explorer, download MSXML 4.0 from the Microsoft XML Core Services 4.0 Web page at http://go.microsoft.com/fwlink/?LinkId=28438.
  2. Download and run the Msxml.msi file.
  3. On the Welcome to the MSXML 4.0 SP2 Parser and SDK Setup Wizard page, click Next.
  4. On the End-User License Agreement page, select I accept the terms in the License Agreement, and then click Next.
  5. On the Customer Information page, do the following:
    Use this To do this
    User Name Type your user name.
    Organization Type your company or organization name.
  6. Click Next.
  7. On the Choose Setup Type page, click Install Now.
  8. On the Completing the MSXML 4.0 SP2 Parser and SDK Setup Wizard page, click Finish.

Installing Windows 2000 Authorization Manager Runtime

You use Windows 2000 Authorization Manager Runtime to set permissions for business user roles. The version you install in the following step also installs a Windows 2000 Server version of the Windows Server 2003 Authorization Manager role-based access control API.

Note Windows 2000 Authorization Manager is included in Windows Server 2003. You only have to install Authorization Manager on a Windows 2000 Server platform.

To install Windows 2000 Authorization Manager runtime

Installing Internet Explorer WebControls 1.0

Use the following step to install Microsoft® Internet Explorer WebControls 1.0.

To install Internet Explorer WebControls 1.0

  1. In Internet Explorer, move to the Internet Explorer Web Controls download page at http://go.microsoft.com/fwlink/?LinkId=37136.
  2. Download and run the iewebcontrols.msi file.
  3. On the Welcome to the Microsoft Internet Explorer WebControls Setup Wizard page, click Next.
  4. On the License Agreement page, select I Agree to continue with installation, and then click Next.
  5. On the Confirm Installation page, click Next.

    This step starts the installation process.

  6. On the Installation Complete page, click Close.

Installing Office XP Web Components

To interact with dynamic reports using the Reports module in Business Desk, you must install Microsoft Office XP Web Components on your computer.

To install Office XP Web Components

  1. In Internet Explorer, move to the Office XP Tool: Web Components download page at http://go.microsoft.com/fwlink/?LinkId=36954.
  2. Download and run the owc10.exe file.
  3. On the End-User License Agreement page, click I accept the terms in the License Agreement, and then click Install.
  4. On the Office XP Web Components Setup page, click OK.

Configuring FrontPage Server Extensions

You must configure Microsoft FrontPage® Server Extensions on your computer before you install Visual Studio .NET on Windows Server 2003. You can skip this step if you are installing Commerce Server on Windows 2000 Server.

To configure FrontPage Server Extensions

  1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. Expand the nodes to the following path: \<computer name> (local computer)\Web Sites\Default Web Site.
  3. Right-click Default Web Site, select All Tasks, and then click Configure Server Extensions 2002.
  4. On the Extend virtual server with FrontPage Server Extensions 2002 page, verify that the Administrator user name is correct, and then click Submit.

Installing Microsoft Visual Studio .NET 2003

You must install Microsoft Visual Studio .NET 2003 on your computer before you install Commerce Server 2002 so that you can create the Commerce Server 2002 Project Creation Wizards.

Use the following steps to install Microsoft® Visual Studio® .NET 2003. There are four steps that you must complete to install Visual Studio .NET 2003.

To install Visual Studio .NET 2003

Step 1

  1. Insert the Visual Studio .NET Enterprise Edition CD into the CD drive.

    If the Microsoft Visual Studio .NET Setup screen does not appear, run the Setup.exe file from the product CD.

  2. In the Microsoft Visual Studio .NET Setup page, click Visual Studio .NET Prerequisites, and prompt appears, insert the Prerequisites CD, and then click OK.
  3. In the Microsoft Visual Studio .NET Prerequisites page, click I agree to the End User License Agreement, and then click Continue.
  4. In the next Microsoft Visual Studio .NET Prerequisites page, click Install Now.
  5. When Microsoft Visual Studio .NET Prerequisites set up is complete, click Done.

Step 2

  1. In the Microsoft Visual Studio .NET Setup screen, click Visual Studio .NET, and when the prompt appears, insert the Visual Studio .NET CD, and then click OK.
  2. On the Start page, click I agree to the End User License Agreement, type your product key and your name, and then click Continue.
  3. On the Options page, click Install Now, and when the prompt appears, insert the requested CDs, and then click OK.
  4. On the Install page, after set up finishes, click Done.

Step 3

  1. In the Microsoft Visual Studio .NET Setup screen, click Product Documentation, and when the prompt appears, insert the MSDN CD, and then click OK.
  2. On the MSDN Library for Visual Studio .NET 2003 – Setup Wizard page, click Next.
  3. On the License Agreement page, click I accept the terms of the license agreement, and then click Next.
  4. On the Customer Information page, do the following:
    Use this To do this
    User Name Type your user name.
    Organization Type your company or organization name.
  5. Click Next.
  6. On the Please select a setup type page, select Full, and then click Next.
  7. On the Destination Folder page, click Next.
  8. On the Ready to Install the Program page, click Install, and when the prompt appears, insert the requested CDs, and then click OK.
  9. When set up has completed, on the Library Setup Wizard Completed page, click Finish.

Step 4

  1. In the Microsoft Visual Studio .NET Setup screen, click Service Releases.
  2. On the Service Releases page, click Check for Service Releases on the Internet to install the latest service releases, and then click OK.
  3. On the Microsoft Visual Studio .NET Setup page, click Exit.
  4. In the Security Updates dialog box, click Yes to see if there are security updates and install them if present.

Installing Commerce Server 2002

The Commerce Server 2002 Starter Site requires Commerce Server 2002 Service Pack 3 (SP3) or Commerce Server 2002 Feature Pack 1 (FP1).

Commerce Server 2002 SP3 contains a collection of hotfixes and security fixes. Commerce Server FP1 adds new functionality to Commerce Server for managing catalogs and discounts. For more information about Commerce Server FP1, see http://go.microsoft.com/fwlink/?LinkId=37039.

Note If you choose to install Commerce Server FP1, you must first install Commerce Server 2002 Service Pack 2 (SP2) or Commerce Server SP3.

This section describes how to install Commerce Server 2002 with Commerce Server 2002 SP3 or Commerce Server 2002 FP1.

This section contains:

Installing Commerce Server 2002

You must install Microsoft Commerce Server 2002 Enterprise Edition before you install Commerce Server 2002 SP3 or Commerce Server 2002 FP1.

To install Commerce Server 2002 Enterprise Edition

  1. Insert the Commerce Server 2002 CD into the CD drive.

    If the Microsoft Commerce Server 2002 splash screen does not appear, run the Setup.exe file from the product CD.

    Note If you want to evaluate Commerce Server 2002, you can download the Commerce Server 2002 Evaluation version from http://go.microsoft.com/fwlink/?LinkId=37195.
  2. In the Commerce Server 2002 Enterprise Edition splash screen, click Commerce Server 2002 Enterprise Edition Components.
  3. In the Commerce Server Setup dialog box that prompts you to install the .NET Framework 1.0, click No.
    Note The Commerce Server 2002 Starter Site requires Microsoft .NET Framework 1.1. For more information, see Software Requirements.
  4. In the Commerce Server 2002 dialog box warning you about the compatibility issue with the installed version of Windows, click Continue.
    Note This warning only appears on a Windows Server 2003 base platform. After you install Commerce Server 2002 SP3 or Commerce Server 2002 FP1, the compatibility issue is resolved.
  5. On the Welcome to the Commerce Server 2002 Setup Wizard page, click Next.
  6. On the CPU License page, select I have purchased the licenses, and then click Next.
  7. On the Prerequisites page, click Next.
  8. On the License Agreement page, read the End-User License Agreement (EULA), click I accept the terms in the license agreement to continue with installation, and then click Next.
  9. On the Customer Information page, do the following:
    Use this To do this
    User Name Type your user name.
    Organization Type your company or organization name.
    Product key Type the product key.
  10. Click Next.
  11. On the Destination Folder page, click Change to specify an installation folder, or click Next to use the default installation folder.
  12. In the Setup Type page, select Custom, and then click Next.
  13. In the Custom Setup page, configure all features as "Entire feature will be installed on local hard drive" except for the Predictor Service, and then click Next.
    Note The Predictor site resource is not included in the Commerce Server 2002 Starter Site Pup package.
  14. On the Administration Database Configuration page, in the SQL Server Computer box, type your computer name, select Use Windows Integrated Security, and then click Next.
  15. In the Microsoft Commerce Server 2002 Enterprise Edition dialog box informing you that a new administration database will be created, click OK.
  16. On the Direct Mailer Database Configuration page, verify that Use Windows Integrated Security is selected, and then click Next.
  17. On the Services Accounts page, verify that Use the same account for each service and set all to auto start is selected.
  18. On the Services Accounts page in the Service Settings section, do the following:
    Use this To do this
    Setting Type CSSvc.
    Password Type the corresponding password.
    Domain Type the computer name.

    Commerce Server Setup automatically grants the Logon as a service right to the account(s) you specify. Commerce Server 2002 Direct Mailer, List Manager, Predictor, and Event Logging require an account for security and network access. Event Logging must run under a local Administrator account.

  19. Click Next.
  20. On the Ready to Install page, click Install.
  21. On the Completing the Commerce Server 2002 Setup Wizard page, clear the check box for Register online with Microsoft, and then click Finish.
  22. In the Microsoft Commerce Server 2002 Enterprise Edition splash screen, click Exit.
  23. Restart the computer.
    Note If you receive an error stating that some services cannot be started, you can ignore this error. The account does not yet have the required permissions for the services. You configure these accounts later in the installation process.

You can now install Commerce Server 2002 SP3, and then optionally, you can install Commerce Server 2002 FP1.

Installing Commerce Server 2002 SP3

Commerce Server 2002 Service Pack 3 (SP3) contains a collection of hotfixes and security fixes, as well as added support.

Note Commerce Server SP3 set up requires the original Commerce Server 2002 installation .msi file. For example, if you installed Commerce Server from a CD, you must insert the CD into the CD drive so the Commerce Server .msi file is available to the Commerce Server SP3 Setup program.

To install Commerce Server 2002 SP3

  1. In Internet Explorer, go to the Microsoft Commerce Server downloads page at http://go.microsoft.com/fwlink/?LinkId=36953.
  2. Download and run the Commerce Server 2002 Service Pack 3 package, and extract the files to a location on your computer.
  3. In the Microsoft Commerce Server 2002 Service Pack 3 dialog box, type a location to unzip the files to (or click Browse to find a location), and then click OK.
  4. From the location you specified in the previous step, run the SP3Setup.exe file.
  5. In the Commerce Server 2002 Service Pack 3 Setup dialog box that lists the services that will be stopped, click OK.
  6. In the Commerce Server 2002 dialog box, warning you about a known incompatibility with Windows Server 2003, click Continue.
    Note This warning only appears on a Windows Server 2003 base platform. After you install Commerce Server 2002 SP3, the compatibility issue will no longer exist.
  7. On the Welcome to the Microsoft Commerce Server 2002 Enterprise Edition Service Pack 3 Setup Wizard page, click Next.
  8. On the License Agreement page, select I accept the terms in the license agreement, and then click Next.
  9. On the Ready to Install page, click Install.

    This step starts the installation process. Note that you may have to insert the Commerce Server 2002 installation CD into the CD drive.

  10. On the Completing the Microsoft Commerce Server 2002 Enterprise Edition Service Pack 3 Setup Wizard page, clear the check box for Register online with Microsoft, and then click Finish.
  11. After the installation is complete, restart your computer.

Installing Commerce Server 2002 with FP1

Note Before you install Microsoft® Commerce Server 2002 FP1, you must have first installed Commerce Server 2002 with Service Pack 3 (SP3). For information about installing Commerce Server 2002 with SP3, see Installing Commerce Server 2002 SP3.

The following step describes how to install Microsoft® Commerce Server 2002 Feature Pack 1 (FP1). You must close all other applications before you continue. For more detailed information about installing Commerce Server 2002 FP1, see http://go.microsoft.com/fwlink/?LinkId=24905.

Important After you install Commerce Server 2002 FP1, see Post-Installation Requirements. It is strongly recommended that you perform each step in the Post-Installation Requirements section to complete a successful Commerce Server 2002 installation.
Note Commerce Server 2002 FP1 uses Windows authentication to access the SQL Server databases that the Setup program creates.

To install Commerce Server 2002 FP1

  1. To install Commerce Server 2002 FP1, locate the Commerce Server 2002 FP1 download page at http://go.microsoft.com/fwlink/?LinkId=37039.
  2. Download and run the Commerce Server 2002 FP1 package, and save the file to a location on your computer.
  3. When the prompt appears, type a location to where you want to unzip the Commerce Server 2002 FP1 files. After the files are unzipped, find the location you selected, and then double-click FP1Setup.exe.
  4. On the Welcome to the Microsoft Commerce Server 2002 Feature Pack 1 Setup Wizard page, click Next.
  5. On the License Agreement page, select I accept the terms in the license agreement, and then click Next.
  6. On the Setup page, make sure that Discounts – Coupon (PromoCode) Generator Service and Data Warehouse and Analytics Updates are selected, and then click Next.
  7. On the Administration Database Configuration page, click Next.
  8. In the Commerce Server administration database needs to be updated for Commerce Server Feature Pack 1 dialog box, click OK.
  9. On the Services Accounts page, do the following:
    Use this To do this
    Username Type CSSvc.
    Password Type the corresponding password.
    Domain Type the <computer name> for the Promotion Code Generator Service.
    Note The Commerce Server 2002 Starter Site does not support using Promotion Codes. However, you can implement promotion code functionality after you install the Commerce Server 2002 Starter Site. For information about implementing promotion codes, see "Implementing Promotion Codes" in Commerce Server 2002 FP1 Help.
  10. Click Next.
  11. In the Warning: Promocode Service not started automatically dialog box, click OK.
  12. On the Services Accounts page, click Next.
  13. On the Ready to Install page, click Install to start the installation process.

    The Installing Commerce Server 2002 Feature Pack 1 page appears, informing you that the Setup program is installing the selected program features.

  14. On the Completing the Microsoft Commerce Server 2002 Feature Pack 1 Setup Wizard page, click Finish.
  15. In the Commerce Server 2002 Feature Pack 1 Setup dialog box, click OK.
  16. After the installation is complete, restart your computer when the prompt appears.

After you install Commerce Server FP1, you must install the Business Management applications.

Installing the Business Management applications

With the Commerce Server 2002 FP1 business management applications, you can manage your discounts and product catalogs. For information about the Discount Manager, see "Managing Discounts Using the Marketing Web Service" in Commerce Server 2002 FP1 Help. For information about the Catalog Manager, see "Managing Catalogs" in Commerce Server 2002 FP1 Help.

To install the Discount Manager user interface

  1. Move to the location where you unpacked the Web download file for Commerce Server FP1, for example, <drive>:\Program Files\Microsoft Commerce Server 2002, and then double-click DiscountManager.msi.
  2. On the Commerce Server 2002 Feature Pack 1 Discount Manager Installation Wizard page, click Next.
  3. On the License Agreement page, select I accept the terms in the Agreement, and then click Next.
  4. On the Customer Information page, type your customer information, and then click Next.
  5. On the Destination Folder page, accept the default installation folder, or click Change to specify a different folder, and then click Next.
  6. On the Ready to Install the Program page, click Install.
  7. On the Installation Completed page, click Finish.

Installation of the Commerce Server 2002 FP1 Discount Manager is complete.

To install the Catalog Manager user interface

  1. Locate where the Business Management application is installed, for example, <drive>:\Program Files\Microsoft Commerce Server 2002, and then double-click CatalogManager.msi.
  2. On the Commerce Server 2002 Feature Pack 1 Catalog Manager Installation Wizard page, click Next.
  3. On the License Agreement page, select I accept the terms in the Agreement, and then click Next.
  4. On the Customer Information page, type your customer information, and then click Next.
  5. On the Destination Folder page, accept the default installation folder, or click Change to specify a different folder, and then click Next.
  6. On the Ready to Install the Program page, click Install.
  7. On the Installation Completed page, click Finish.

Installation of the Commerce Server 2002 FP1 Catalog Manager is complete.

Unpacking the Commerce Server 2002 Starter Site

The Commerce Server 2002 Starter Site provides a Pup package that includes the resources you need for your Commerce Server 2002 Starter Site. For more information about unpacking a site, see "Using Site Packager" in Commerce Server 2002 Help.

The following instructions explain how to unpack the Commerce Server 2002 SP3 or Commerce Server 2002 FP1 Pup packages on one computer using the Custom unpack mode in Site Packager and how to package your site for other Web servers.

This section contains:

Unpacking the Commerce Server 2002 Starter Site Pup Package

Before you unpack the Pup package, note the following:

Follow these steps to install and unpack the Commerce Server Starter Site.

To unpack the Commerce Server 2002 Starter Site

  1. To unpack the Commerce Server Starter Site, locate the Commerce Server 2002 Starter Site download page at http://go.microsoft.com/fwlink/?LinkId=37800 and download the CS2002StarterSite.exe file.
  2. In Windows Explorer, locate where you downloaded the CS2002StarterSite.exe file, and then double-click this file to unpack the Commerce Server 2002 Starter Site installation files.
  3. In Windows Explorer, locate where you unpacked the installation files, and then double-click the CS2002StarterSite.msi file to install the Commerce Server 2002 Starter Site files.
  4. In Windows Explorer, locate where you installed the Commerce Server Pup packages, for example <drive>:\Program Files\Microsoft Commerce Server 2002\Starter Site\Pup Packages.
  5. Double-click the appropriate Pup package to start the Commerce Server Site Packager:
  6. On the Unpack page, select Custom unpack, and then click Next.
  7. On the Unpack Method page, select Create a new site, and then click Next.
  8. On the Site Name page, type a name for the site, for example, CS2002StarterSite, and then click Next.
    Note You cannot unpack to the root directory of the Web site.
  9. On the Select Resources page, click Next.
  10. On the Global Resource Pointers page, click Next.
  11. On the Database Connection Strings page, click New Database.
  12. In the New Database dialog box, in the Database name box, type CS2002StarterSite_BDPermissions, select Windows Integrated Security, and then click Create database.
  13. Repeat steps 11 and 12 to create the following databases:
  14. On the Database Connection Strings page, select Business Desk Permissions, and then click Modify.
  15. In the Data Link Properties dialog box, select CS2002StarterSite_BDPermissions from the Select the database on the server drop-down list, and then click Test Connection to verify the database connection. If you receive an error, see step 11 to create the missing database. If the test is successful, click OK.
  16. Repeat steps 14 and 15 using the following databases for each Commerce Server resource:
    Resource Database
    Profiles CS2002StarterSite_Profiles
    Campaigns CS2002StarterSite_Campaigns
    DataWarehouse CS2002StarterSite_DataWarehouse
    Marketing
    Note The Marketing resource only exists in a Commerce Server 2002 Feature Pack 1 installation.
    		 CS2002StarterSite_Marketing
    Product Catalog CS2002StarterSite_ProductCatalog
    Transaction Config CS2002StarterSite_TransactionConfig
    Transactions CS2002StarterSite_Transactions
  17. On the Database Connection Strings page, click Next.

    The Commerce Server Site Packager dialog box appears warning you that some of the databases you specified already exist. You created these databases in a previous step.

  18. In the Commerce Server Site Packager dialog box, click Yes to continue unpacking the Commerce Server 2002 Starter Site Pup package.
  19. On the Select Applications page, verify that all application check boxes are selected, and then click Next.
  20. On the Select IIS Computers, Web Sites, and Paths page, click Next.

    If a message appears stating that some of the virtual directories already exist, click Yes to overwrite them.

  21. On the Data Warehouse page, click OK.
  22. On the Profiling System page, click Next.
  23. On the next Profiling System page, click OK.
  24. On the Commerce Server Site Packager page that provides guidelines about configuring permissions for your databases, click OK.
  25. On the Unpacking is Complete page, click Finish.

The Commerce Server 2002 Starter Site is unpacked.

Post-Installation Requirements

This section describes the tasks you must perform after you install and configure your site.

This section contains:

Changing Your Windows 2000 Server Configuration Settings

You must update the Component Services settings in order for Commerce Server to function correctly on a Windows 2000 Server platform.

To update the Component Services settings on Windows 2000 Server

  1. Click Start, and then click Run.
  2. In the Run dialog box, in the Open box, type dcomcnfg.exe, and then click OK.
  3. In the Distributed COM Configuration Properties dialog box, on the Applications tab, in the Applications box, select Microsoft Commerce Server DirectMailer Service, and then click Properties.
  4. In the Microsoft Commerce Server DirectMailer Service Properties dialog box, on the Security tab, select Use custom access permissions, and then click Edit.
  5. In the Registry Value Permissions dialog box, click Add.
  6. In the Add Users and Groups dialog box, from the List Names drop-down list, select <computername>, from the Names box, select Administrators, click Add, and then click OK.
  7. In the Registry Value Permissions dialog box, click OK.
  8. In the Microsoft Commerce Server DirectMailer Service Properties dialog box, click OK.
  9. Repeat steps 3 through 8 for the Microsoft Commerce Server List Manager Service.
  10. Close the Distributed COM Configuration Properties dialog box.

Changing Your Windows Server 2003 Configuration Settings

The following configuration changes are required in order for Commerce Server to function correctly on a Windows Server 2003 platform.

To run the EnableCS2002Settings.vbs script

  1. Click Start, point to All Programs, point to Accessories, and then click Windows Explorer.
  2. Locate the folder C:\Program Files\Microsoft Commerce Server 2002\SP3, and then double-click EnableCS2002Settings.vbs.
  3. In the Warning dialog box, click OK to enable the IIS 6.0 Web Service Extensions.
  4. In the Windows Script Host dialog boxes that appear during the configuration process, click OK.

To update the Default Application Pool settings

  1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. Expand the nodes to the following path: \<computer name> (local computer)\Application Pools\DefaultAppPool.
  3. Right-click DefaultAppPool, and then click Properties.
  4. In the DefaultAppPool Properties dialog box, on the Identity tab, in the Application pool identity section, select Configurable, and then do the following:
    Use this To do this
    User name Type <computername>\CSSvc.
    Password Type the appropriate password.
  5. Click OK.
  6. In the Confirm Password dialog box, re-enter the appropriate password, and then click OK.

To update the Component Services settings

  1. Click Start, point to All Programs, point to Administrative Tools, and then click Component Services.
  2. Expand the nodes to the following path: Component Services/Computers/My Computer/DCOM Config.
  3. Right-click Microsoft Commerce Server Direct Mailer Service, and then click Properties.
  4. In the Microsoft Commerce Server DirectMailer Service Properties dialog box, on the Security tab, in the Launch Permissions section, select Customize, and then click Edit.
  5. In the Launch Permission dialog box, click Add.
  6. In the Select Users, Computers, or Groups screen, in the Enter the object names to select section, type <computername>\CSSvc, click Check Names, and then click OK.
  7. Select <computer name>\CSSvc from the Group or user names list.
  8. In the Permissions for <computer name>\CSSvc section, select the Allow check box next to Launch Permission.
  9. In the Launch Permission dialog box, click OK.
  10. In the Microsoft Commerce Server DirectMailer Service Properties dialog box, in the Access Permissions section, select Customize, and then click Edit.
  11. In the Access Permission dialog box, click Add.
  12. In the Select Users, Computers, or Groups screen, in the Enter the object names to select section, type <computername>\CSSvc, and then click OK.
  13. Select <computer name>\CSSvc from the Group or user names list.
  14. In the Permissions for <computer name>\CSSvc section, select the Allow check box next to Access Permission.
  15. In the Access Permission dialog box, click OK.
  16. In the Microsoft Commerce Server DirectMailer Service Properties dialog box, click OK.
  17. Repeat steps 3 – 13 for the Microsoft Commerce Server ListManager Service. Note the following steps:
    1. On step 12, in the Select Users, Computers, or Groups screen, in the Enter the object names to select section, type <computername>\CSSvc, and <computername>\Administrators, click Check Names, and then click OK.
    2. On step 13, select <computer name>\CSSvc, and <computername>\Administrators from the Group or user names list.

Assigning Access and Updating the Web Service Authorization Manager Policies

You use Authorization Manager to add users to the Catalog and Marketing Authorization policy roles. Windows Server 2003 includes an Authorization Manager user interface.

You must follow these steps before you can access the Catalog or Discount Managers.

Note Only follow these steps if you installed Commerce Server 2002 Feature Pack 1 (FP1) as part of your Commerce Server 2002 Starter Site base platform.

Assigning write permissions to the authorization policy

You must assign the ASP.NET users write access to the CatalogAuthorizationStore.xml and MarketingAzManPolicy.xml files.

To assign write permissions to the Catalog and Marketing authorization policies

  1. In Windows Explorer, locate the folder where you installed the Catalog Web service, for example, <drive>:\Inetpub\wwwroot\CatalogWebService.
  2. In the CatalogWebService folder, right-click CatalogAuthorizationStore.xml, and then click Properties.
  3. In the CatalogAuthorizationStore.xml Properties dialog box, on the Security tab, click Add.
  4. In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type <computername>\CSSvc; <computername>\IWAM<computername>, click Check Names, and then click OK.
  5. In the CatalogAuthorizationStore.xml Properties dialog box, on the Security tab, in the Groups or user names list box, select the CSSvc account.
  6. In the Permissions for CSSvc list, select Write in the Allow column.
  7. In the CatalogAuthorizationStore.xml Properties dialog box, on the Security tab, in the Groups or user names list box, select Launch IIS Process Account.
  8. In the Permissions for Launch IIS Process Account list, select Write in the Allow column.
  9. In the CatatlogAuthorizationStore.xml Properties dialog box, click OK.

You have assigned write access to the Catalog Web Service authorization policy for the CSSvc and IIS Worker Process accounts.

Note To assign write access to the Marketing Web Service authorization policy for the CSSvc and IIS Worker Process accounts, in the MarketingWebService folder repeat steps 2 through 9 for the MarketingAzManPolicy.xml file.
Note If you are installing the Commerce Server 2002 Starter Site on Windows 2000 Server, you must also follow these steps for the ASPNET account to grant the ASPNET account write permissions to the authorization policy files.

Assigning write permissions to the temporary ASP.NET folder

Follow these steps to assign write permissions to the temporary ASP.Net folder.

To assign write permissions to the temporary ASP.Net folder

  1. In Windows Explorer, locate the Temporary ASP.Net Files folder, for example, C:\Windows\Microsoft.NET\Framework\c1.1.4322\Temporary ASP.NET Files.
  2. Right-click the Temporary ASP.NET Files folder, and then click Properties.
  3. In the Temporary ASP.NET Files Properties dialog box, on the Security tab, click Add.
  4. In the Enter the object names to select box, type <computername>\CSSvc, click Check Names, and then click OK.
  5. In the Temporary ASP.NET Files Properties dialog box, in the Groups or user names box, click CSSvc.
  6. In the Permissions for CSSvc box, select Write in the Allow column, and then click OK.
  7. In the Security dialog box, click Yes.

You have assigned write permissions to the temporary ASP.NET folder

Assigning Full control to the Windows temporary folder

Follow these steps to assign Full control to the Windows temporary folder.

To assign Full control to the Windows temporary folder

  1. In Windows Explorer, locate the Windows temporary folder, for example, C:\Windows\Temp.
  2. Right-click the Temp folder, and then click Properties.
  3. In the Temp Properties dialog box, on the Security tab, click Add.
  4. In the Enter the object names to select box, type <computername>\CSSvc, click Check Names, and then click OK.
  5. In the Temporary ASP.NET Files Properties dialog box, in the Groups or user names box, select CSSvc.
  6. In the Permissions for CSSvc box, select Full Control under the Allow column, and then click OK.
  7. In the Security dialog box, click Yes.

You have assigned Full control to the Windows temporary folder.

Adding users to the authorization policy roles

The Catalog and Marketing authorization policies have a number of predefined authorization policy roles. You use the Authorization Manager Microsoft Management Console (MMC) to add users or user groups to a role.

Note Windows 2000 Authorization Manager is included in Windows Server 2003. Windows 2000 Server and Windows 2000 Server are supported operating systems for the Commerce Server 2002 Starter Site; however, they do not include a user interface for Authorization Manager. It is recommended that you use a Windows Server 2003 or Windows XP computer to connect to and configure the Authorization Manager store on your Windows 2000 Server computer.

To use the Authorization Manager user interface on the Windows XP operating system, go to http://go.microsoft.com/fwlink/?LinkId=28442.

For information about installing Windows 2000 Authorization Manager, see Installing Windows 2000 Authorization Manager Runtime.

To add a user to a role

  1. Click Start, click Run, type azman.msc, and then click OK.
  2. In the Authorization Manager screen, right-click Authorization Manager, and then click Open Authorization Store.
  3. In the Open Authorization Store dialog box, verify that the XML file option is selected, and then click Browse to find where the authorization policy for your catalog Web service is located, for example, <drive>:\Inetpub\wwwroot\CatalogWebService.
  4. In the CatalogWebService folder, select CatalogAuthorizationStore.xml, and then click Open.
  5. In the Open Authorization Store dialog box, click OK.
  6. Expand the Authorization Policy to \CatalogAuthorizationStore.xml\ProductCatalogSystem\Role Assignments\<Role name>.
  7. Right-click the appropriate role, and then click Assign Windows Users and Groups.

    The following table lists the catalog authorization policy roles and tasks that a user can perform for each role.

    Role Task
    CatalogAdministrator Manage and perform any activity in the Product Catalog System.
    CatalogManager

    		Manage and perform any activity on all catalogs in the Product Catalog System.
    CatalogSystemViewer View catalogs and categories in the Product Catalog System. Users cannot perform any updates to the catalog content.
    CatalogSchemaManager Manage the catalog schema. This includes creating, deleting, and editing property content, as well as creating and deleting definitions.
  8. In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type the name of the user, and then click OK.
  9. Repeat steps 3 through 8 for the C:\Inetpub\wwwroot\MarketingWebService\MarketingAzManPolicy.xml file.

Creating the ASPNet and CSSvc Database Accounts

You must create a new SQL Server login for the CSSvc account that you created in Creating the Administrative Accounts. If you are installing the Commerce Server 2002 Starter Site on Windows 2000, you must also create a new login for the ASPNet account that was created during IIS configuration.

To create a new SQL Server login for the ASPNet account

Note The following step only applies on a Windows 2000 Server platform. Skip this step if you are installing the Commerce Server 2002 Starter Site on a Windows Server 2003 platform.
  1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
  2. In SQL Server Enterprise Manager, expand the nodes to the following path: Microsoft SQL Servers\SQL Server Group\<computer name>\Security\Logins.
  3. Right-click Logins, and then click New Login.
  4. In the SQL Server Login Properties - New Login dialog box, on the General tab, in the Name box, type <computer name>\ASPNet, and then click OK.

You have created new SQL Server logins for the ASPNet account.

To create a new SQL Server login for the CSSvc account

Note The following step applies to both a Windows 2000 Server platform and a Windows Server 2003 platform.
  1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
  2. In SQL Server Enterprise Manager, expand the nodes to the following path: Microsoft SQL Servers\SQL Server Group\<computer name>\Security\Logins.
  3. Right-click Logins, and then click New Login.
  4. In the SQL Server Login Properties - New Login dialog box, on the General tab, in the Name box, type <computer name>\CSSvc, and then click OK.

You have created new SQL Server logins for the CSSvc account.

Granting Access to the Databases

You must grant access to the appropriate databases for the CSSvc account.

Note If you are installing the Commerce Server 2002 Starter Site on a Windows 2000 Server platform, you must also grant access to the appropriate databases for the ASPNet account.

This section provides instructions for configuring the database roles on the SQL Server. This configuration involves specifying database roles and permissions for each database account that you created previously. Specifically, this section contains:

Creating the database roles

You must create roles on the SQL Server by manually running scripts from the server where you installed Commerce Server 2002. These scripts are located in the <drive>:\Program Files\Microsoft Commerce Server 2002\Support folder on the server where you installed Commerce Server 2002. The following table specifies the scripts that you must run.

Database Script Name
CS2002StarterSite_BDPermissions
  • BDReaderRole.sql
  • BDWriterRole.sql
CS2002StarterSite_Campaigns
  • CampaignReaderRole.sql
  • CampaignWriterRole.sql
  • Dts_CommerceDB_Campaign_SecurityRole.sql
CS2002StarterSite_DataWarehouse
Note This database only exists on a Commerce Server 2002 installation.
  • ReportViewer.sql
    Note You must run the ReportViewer.sql script before running the ReportAdvance.sql script.
    Note You must run these scripts on the Data Warehouse/Analytics server only.
  • ReportAdvance.sql
  • SegmentViewer.sql
CS2002StarterSite_Marketing
Note This database only exists on a Commerce Server 2002 with FP1 installation.
  • Mktg_db_roles.sql
    Note This script is located in the Program Files\Commerce Server2002\FP1\SDK\Samples\SiteCreate folder.
CS2002StarterSite_ProductCatalog
  • CatalogSecurityRoles.sql
  • Dts_CommerceDB_Catalog_SecurityRole.sql
CS2002StarterSite_Profiles
  • ProfileReaderRole.sql
  • ProfileWriterRole.sql
  • Dts_CommerceDB_UPM_SecurityRole.sql
CS2002StarterSite_TransactionConfig
  • TransactionConfigReaderRole.sql
  • TransactionConfigWriterRole.sql
CS2002StarterSite_Transactions
  • TransactionReaderRole.sql
  • TransactionWriterRole.sql
  • Dts_CommerceDB_Transaction_SecurityRole.sql
MSCS_Admin
  • Dts_AdminDB_SecurityRole.sql

After you run the scripts and create all the roles, you can start associating the roles with specific database accounts. You can associate multiple roles to a single account.

Use the following step to create the database roles.

To create the database roles

  1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Query Analyzer.
  2. In the Connect to SQL Server dialog box, specify the SQL Servers.
  3. In Query Analyzer, in the database drop-down list, select the database you want to run the script against.
    Note Do not highlight the database name in the left pane of Query Analyzer. Highlighting the database name will not select the database against which the scripts will be run.
  4. Click File, and then click Open.
  5. In the Open dialog box, locate the <drive>:\Program Files\Microsoft Commerce Server 2002\Support folder on the server where you installed Commerce Server 2002 SP3 or FP1, and then double-click the script that you want to run.
  6. Press F5 to run the script against the selected database.
  7. Repeat this procedure for each script listed in the previous table.

Securing the administration tables

Use the following step to help secure the administration tables.

To help secure the administration tables

  1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
  2. In SQL Server Enterprise Manager, expand Microsoft SQL Servers, expand SQL Server Group, expand <SQL Server name>, expand Databases, expand MSCS_Admin, right-click Roles, and then click New Database Role.
  3. In the Database Role Properties - New Role dialog box, in the Name box, type Anonymous_IIS_Role.
  4. In the Database role type section, select Standard role, and then click OK.

    The standard role you created and named Anonymous_IIS_Role appears in the Roles pane in SQL Server Enterprise Manager.

  5. In the Roles pane, right-click Anonymous_IIS_Role, and then click Properties.
  6. In the Database Role Properties - Anonymous_IIS_Role dialog box, click Permissions.
  7. In the Database Role Properties - MSCS_Admin dialog box, in the SELECT column, select the ResourceProps, Resources, SiteResources, and Sites check boxes, and then click OK.
  8. In the Database Role Properties - Anonymous_IIS_Role dialog box, click OK.
  9. Repeat steps 2 through 7 to create the ShippingConfigSelectOnly role in the CS2002StarterSite_TransactionConfig database, and enable the SELECT permission on the ShippingConfig table for this role.

Associating database accounts with the database roles

The following table lists the database roles to which you must assign the <computer name>\CSSvc account and the ASPNET account.

Database Role
CS2002StarterSite_Campaigns
  • db_owner
CS2002StarterSite _Marketing
Note This database only exists on a Commerce Server 2002 FP1 installation.
  • db_owner
CS2002StarterSite_ProductCatalog
  • db_owner
CS2002StarterSite_Profiles
  • ProfileWriterRole
  • ProfileReaderRole
CS2002StarterSite_TransactionConfig
  • ShippingConfigSelectOnly
  • TransactionConfigReaderRole
CS2002StarterSite_Transactions
  • TransactionReaderRole
DirectMailer
  • db_owner
MSCS_Admin
  • Anonymous_IIS_Role
MSCS_CatalogScratch
  • db_owner

Use the following step to associate these accounts with the specified roles.

To associate the database accounts with the database roles

  1. On the design-time SQL Server, click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
  2. In the SQL Server Enterprise Manager window, in the left pane, expand Microsoft SQL Servers, expand SQL Server Group, expand <servername>(Windows NT), expand Security, and then click Logins.
  3. In the right pane, right-click the database account, and then click Properties.
  4. In the SQL Server Login Properties <servicename> dialog box, on the Database Access tab, in the top box, select a database.
  5. In the bottom box, select the appropriate roles.
    Note If one of the roles does not appear in the list, to refresh the roles click OK on the SQL Server Login Properties dialog box, and then close and reopen Enterprise Manager.
  6. Repeat steps 4 and 5 until the account is associated with all the specified database roles. After you have assigned the account to all the database roles, click OK.
Note If you are installing the Commerce Server 2002 Starter Site on Windows 2000, repeat all the above steps for the ASPNet account.

Additional security steps

You must perform the following additional security steps:

  1. On the SQL Server, click Start, point to Programs, point to Microsoft SQL Server, and then click Enterprise Manager.
  2. In the SQL Server Enterprise Manager window, in the left pane, expand Microsoft SQL Servers, expand SQL Server Group, expand <servername>(Windows NT), expand Databases, expand CS2002StarterSite_Profiles, and then click Roles.
  3. Right-click ProfileReaderRole and select Properties.
  4. In the Database Role Properties window, Click Permissions.
  5. Enable the SELECT permission on the ExchangeRates table. Click OK, and then click OK again.
  6. Expand CS2002StarterSite_TransactionConfig, and then click Roles.
  7. Right-click TransactionConfigReaderRole and select Properties.
  8. In the Database Role Properties window, click Permissions.
  9. Enable the EXEC permission on the sp_GetCountryRegions object. Enable the EXEC permission on the sp_GetStateProvinces object. Click OK, and then click OK again.

Granting Access to the Direct Mailer Service Log Files

The Commerce Server DirectMailer Service maintains a log file of service events. You must grant the CSSvc account access to the LogFiles directory in order for the DirectMailer Service to make entries to the log file.

To grant DirectMailer Service access to the LogFiles directory

  1. Click Start, point to All Programs, point to Microsoft Commerce Server 2002, and then click Commerce Server Manager.
  2. In Commerce Server Manager, expand the nodes to the following path: \Commerce Server Manager\Global Resources\, and then select Direct Mail on <computername>.
  3. In Commerce Server Manager, in the Commerce Server Resource pane, note the value for the Log Folder Path. By default, the path is C:\WINDOWS\System32\LogFiles.
  4. Click Start, point to All Programs, point to Accessories, and then click Windows Explorer.
  5. In Windows Explorer, locate the LogFiles folder that you noted in step 3, right-click the folder name, and then select Properties.
  6. In the <log file folder> Properties dialog box, on the Security tab, click Add.
  7. In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type <computername>\CSSvc, and then click OK.
  8. In the <log file folder> Properties dialog box, on the Security tab, highlight the <computername>\CSSvc account, select Write in the Allow section, and then click OK.
  9. In the Security dialog box warning you about changing permission settings, click Yes.

Implementing the Promotion Code Generator

The Commerce Server 2002 Starter Site does not support using Promotion Codes. However, you can implement promotion code functionality after you install the Commerce Server 2002 Starter Site on a Commerce Server 2002 FP1 platform. For information about implementing promotion codes, see the "Implementing Promotion Codes" topic in Commerce Server 2002 FP1 Help.

Enabling the Secure Sockets Layer (SSL) on the Web Server

To enable Secure Sockets Layer (SSL) on the Web Server

  1. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
  2. In the Internet Information Services (IIS) Manager screen, expand the nodes to the following path: \<computername> (local computer)\Web Sites\Default Web Site.
  3. Right-click Default Web Site, and then select Properties.
  4. In the Default Web Site Properties dialog box, on the Directory Security tab, in the Secure communications section, click Server Certificate.
  5. On the Welcome to the Web Server Certificate Wizard page, click Next.
  6. On the Server Certificate page, select Assign an existing certificate, and then click Next.
  7. On the Available Certificates page, select the certificate automatically issued to your computer whose intended purpose is Server Authentication, and then click Next.
  8. On the SSL Port page, verify the SSL port number is 443, and then click Next.
  9. On the Certificate Summary page, click Next.
  10. On the Completing the Web Server Certificate Wizard page, click Finish.
  11. In the Default Web Site Properties dialog box, click OK.

SSL is enabled on the Web Server.

Modifying the Web.config File

Before moving your retail Web site to a production environment, you should modify the Web.config file to update the debug level. Running your site in debug mode may result in performance degradation.

To modify the Web.config file

  1. Open the Web.config file in the runtime site (for example, \Inetpub\wwwroot\<Site name>) and go to the <application siteName> tag, where siteName is the name you specified when unpacking the Starter Site.
  2. In the <application siteName> tag, change the DebugLevel from "Debug" to "Production" as follows:

    From <application siteName="<siteName>" DebugLevel="Debug"/>

    To <application siteName="<siteName>" DebugLevel="Production"/>

Restarting Your Computer

After you have completed the process of installing all the software components, restart your computer to make sure that all Commerce Server components initialize correctly with the correct security credentials.

Defragmenting the Drive

After you have completed the process of installing all the software components, defragment the drive on which these components are installed.

Installing Virus Protection

You should install any virus protection software that is required by your deployment.

Installing Commerce Server 2002 Help

If you installed Commerce Server 2002 with Service Pack 3 (SP3) as your Starter Site platform, by default, Commerce Server 2002 installs Commerce Server 2002 Help in a compiled HTML file with a .chm extension. Commerce Server 2002 installs the .chm file in the Documentation folder where you installed Commerce Server 2002, for example <drive>:\Program Files\Microsoft Commerce Server 2002\Documentation. The .chm file includes Business Desk Help, which is a subset of Commerce Server 2002 Help. You install Business Desk Help when you install the Business Desk client.

If you installed Commerce Server 2002 with FP1 as your Starter Site platform, to access Commerce Server 2002 FP1 Help, you must download the following Help files from the Web and unzip them to the designated locations:

Direct the .exe file to install the Help file to <drive>:\Program Files\Microsoft Commerce Server 2002\Documentation

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2005 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows NT, Windows Server, and MSDN are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.