[This topic is pre-release documentation and is subject to change in future releases. Blank topics are included as placeholders.]

Last updated: 1/16/2006

Note:
For the most current version of this document, see the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkId=57268.

This document provides guidelines for hardware and software requirements, and detailed instructions for installing and configuring Microsoft Commerce Server 2006 Beta on a single computer. For instructions about how to deploy Commerce Server 2006 on multiple computers, see "Configuring an Enterprise Deployment" in Commerce Server 2006 Help.

We strongly recommend that you read this document before you install Commerce Server.

Note:
All references to Commerce Server in this document, unless otherwise specified, are to Commerce Server 2006 Beta.

In This Section

Preparing to Install Commerce Server

The following topics address important considerations for the computer on which you install Commerce Server. Before you install Commerce Server, review the following information.

Note:
This Installation Guide is for single-computer installations and does not include information about how to help secure your Commerce Server services. For instructions about how to enhance security and how to deploy Commerce Server on multiple computers, see "Configuring an Enterprise Deployment" in Commerce Server 2006 Help.
Commerce Server Installation Considerations
  • You can install Commerce Server 2006 and BizTalk Server 2006 Beta on the same computer, but you must run the configuration wizard for each product before you install and configure the next product. For example, first install and configure Commerce Server 2006 before you install and configure BizTalk Server 2006. Alternatively, install and configure BizTalk Server 2006 before you install and configure Commerce Server 2006.

  • If you install Commerce Server 2006 and BizTalk Server 2006 on the same computer, do not reference the same SQL Server databases for both products. You should run separate databases for each product.

  • Unless you have a supplemental agreement with Microsoft, do not install the Beta version of Commerce Server 2006 on computers that you use in a production environment. Installing this version of Commerce Server 2006 in a production environment is not covered by the end user license agreement (EULA).

  • Do not install Commerce Server 2006 on a computer where you have installed an earlier version of Commerce Server. You must uninstall the earlier version of Commerce Server before you install Commerce Server 2006. To uninstall an earlier version of Commerce Server, note the following:

    • You must first uninstall any Commerce Server Service Packs or Commerce Server 2002 Feature Pack 1.

    • Uninstall the Commerce Server runtime objects. For information about how to uninstall the Commerce Server runtime objects, see Uninstalling Commerce Server.

      Note:
      Uninstalling the Commerce Server runtime objects will not remove the Administration database or any other databases associated with your sites. You can move the data in your databases to the updated Commerce Server schema when you install Commerce Server 2006, and when you perform the steps in the Commerce Server Upgrade Wizard.

  • When you upgrade from an earlier version, make sure that you back up your Commerce Server databases before you install Commerce Server 2006.

  • You can install Windows SharePoint Services together with Commerce Server 2006, but you should not install Windows SharePoint Services on a Commerce Server 2006 computer that has BizTalk Server 2006 installed.

  • You must have administrator permissions on the computer where you install Commerce Server and the Commerce Server Business Management applications. Log on to the operating system under a user account that has local administrator permissions.

  • For known issues and important, late-breaking information, see the "Commerce Server 2006 Readme" located at http://go.microsoft.com/fwlink/?linkid=57013.

Hardware and Software Requirements

This section lists the minimum hardware and software requirements for Commerce Server 2006.

Note:
The following hardware and software requirements are for 32-bit installations only. Commerce Server 2006 Beta does not support a 64-bit installation.

Hardware Requirements (32-bit only)

The following table shows the minimum hardware requirements for the Commerce Server installation scenarios.

Note:
In a production environment, the volume of traffic on the Web site may dictate more hardware requirements for the Web servers.

Installation scenario Hardware Recommendations

Commerce Server
  • Dual 1.0 Gigahertz (GHz) or faster Pentium-compatible CPU (or a single 2.8 GHz or faster Pentium-compatible CPU)

  • 1024 MB of RAM

  • 9.0 Gigabytes (GB) of hard disk space to install services

  • CD drive or DVD drive

  • Network adapter card (we recommend 10 MBps or larger bandwidth)

  • Microsoft Windows Server 2003 compatible VGA or higher-resolution monitor

Software Requirements (32-bit only)

The following table lists the prerequisite software you must install on the server that will run Commerce Server 2006:

Important:
You must install the following software in the order listed.

Product Description

Microsoft Windows Server 2003 Service Pack 1 (SP1) Standard or Enterprise Editions

Provides platform security and Web site administration through Microsoft Internet Information Services (IIS).

Note:
Windows Server 2003 SP1 is required. Commerce Server 2006 Beta does not support Windows Server 2003 R2.

To install Windows Server 2003 SP1, see http://go.microsoft.com/fwlink/?linkid=57547.

Microsoft Internet Information Services (IIS)

By default, Windows Server 2003 does not install IIS.

You must install IIS by selecting it as an option during Windows Server 2003 setup, or by running the Windows Components Wizard after you install Windows Server 2003.

Windows Critical Updates

Provides the latest updates available for the operating system, software, and hardware.

To install all Windows critical updates, see http://go.microsoft.com/fwlink/?linkid=16855.

Microsoft SQL Server 2000 Enterprise Edition together with Service Pack 4

OR

Microsoft SQL Server 2005

Provides the underlying database services for Commerce Server 2006.

Note:
Do not install Commerce Server 2006 on a computer that is running SQL Server 2005 Express Edition because this version of SQL Server does not support the full-text searching capability required by Commerce Server 2006.

Microsoft SQL Server 2000 Analysis Services together with Service Pack 4

OR

Microsoft SQL Server 2005 Analysis Services

Used by the Commerce Server Data Warehouse to access the OLAP database. SQL Server Reporting Services is also required for analysis reporting in Commerce Server 2006.

Microsoft .NET Framework 2.0

Provides the programming model for building, deploying, and running Web-based applications and Web services. To install the .NET Framework 2.0, see http://go.microsoft.com/fwlink/?LinkId=56645. You do not have to install this requirement if you install Microsoft Visual Studio 2005.

Install ASP.NET 2.0 as the default framework

You must register ASP.NET 2.0.

Enter the following at the command prompt to register ASP.NET for all virtual directories:

%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe –i

You do not have to install this requirement if you install Microsoft Visual Studio 2005.

Microsoft Visual Studio 2005

Provides the platform to build Web applications.

Required only if you want to use the Commerce Server Project Creation Wizard functionality in Visual Studio.

Upgrading to Commerce Server 2006

You use the Commerce Server 2006 Upgrade Wizard to upgrade from Commerce Server 2002 to Commerce Server 2006 (Commerce Server 2006 does not support upgrading from Commerce Server 2000). This wizard migrates your existing global and site resources (such as Catalogs, Orders, Campaigns, Marketing, and Profiles data), and site data to Commerce Server 2006. For information about how to use the Commerce Server 2006 Upgrade Wizard, see "Commerce Server 2006 Migration" in Commerce Server 2006 Help.

Creating a Local User Account

Before you install Commerce Server, you must create a local account. The following step shows how to create a local account called CSWPA (Commerce Server Worker Process Account) that you will use in the following steps.

To create a local account

  1. On the desktop, right-click My Computer, and then click Manage.

  2. On the Computer Management screen, under System Tools, expand Local Users and Groups.

  3. Right-click Users, and then click New User.

  4. In the New User dialog box, do the following:

    Use this To do this

    User name

    Type CSWPA as the user name.

    Password

    Type a password for the CSWPA user.

    Confirm password

    Confirm the password for the CSWPA user.

    User must change password at next logon

    Clear this check box.

    User cannot change password

    Leave this check box clear.

    Password never expires

    Select this check box.

    Account is disabled

    Leave this check box clear.

  5. Click Create, and then click Close.

Installing Commerce Server

You can install Commerce Server by using the Installation Wizard, or at the command prompt. The Installation Wizard provides a graphical user interface that guides you through each install-time decision, and is the preferred method for most users.

Command prompt installations are for advanced scenarios such as unattended and remote installations. They are run directly at the command prompt, or from command prompt syntax that references an installation file to specify installation options. For information about performing an unattended installation, see Unattended Installation.

When you install Commerce Server, note the following:

  • Make sure that you have installed all the Commerce Server software prerequisites listed above.

  • You must have administrator permissions on the computer where you install Commerce Server and the Commerce Server Business Management applications.

  • Log on to the operating system under a user account that has local administrator permissions.

The following steps describe how to install a complete installation of Commerce Server on one computer. You must close all other applications before you continue.

To install Commerce Server 2006 on one computer

  1. Insert the Commerce Server 2006 CD into the appropriate drive.

  2. Double-click Setup.exe at the root of the CD set up image, and then follow the online prompts.

  3. On the Microsoft Commerce Server 2006 Start page, under Install, click Microsoft Commerce Server 2006.

    Note:
    Setup includes a pre-installation check that identifies unsupported configurations on your installation computer and specifies the software that is required.

  4. On the Customer Information page, type your customer name and organization, and then click Next.

  5. On the License Agreement page, accept the terms of the license, and then click Next.

  6. On the Component Installation page, accept the default installation location or click Browse to move to the location where you want to install Commerce Server 2006, and then click Next to install a complete installation of all Commerce Server 2006 components.

    Or, you can select any one of the following components for Commerce Server 2006:

    • Documentation. Installs Commerce Server 2006 Help.

    • Commerce Server 2006. Installs the Commerce Server run-time objects.

    • Coupon Generator Service. Generates coupon codes for discounts.

    • Direct Mailer. Installs the Commerce Server Direct Mailer service and components.

    • Project Creation Wizard. Creates a new Web project for Commerce Server 2006 development.

      Note:
      The Project Creation Wizard is enabled only if you install Microsoft Visual Studio 2005 on the computer.

    • Staging. Installs the Commerce Server Staging service.

    • Health Monitoring Service. Installs the Health Monitoring service. Do not select this option unless you are using Microsoft Operations Manager (MOM) 2005 to monitor your Commerce Server deployment.

    Note:
    Based on the components you are installing, if any prerequisite software is missing, the Redistributable Prerequisites page appears. To install the prerequisite software, select the appropriate option, and then click Next.

  7. On the Summary page, verify that the components that you are installing are correct, and then click Install.

    Note:
    Commerce Server may require a system restart. Click Set to set your auto-logon credentials.

    The Installation Progress page appears informing you that the Setup program is installing the selected program features.

  8. On the Installation Completed page, make sure that the Launch the Commerce Server Configuration Wizard box is checked, and then click Finish.

    To review the list of events for the installation, click Logfile.

Configuring Commerce Server

After you install Commerce Server 2006, you use the Microsoft Commerce Server 2006 Configuration Wizard to enter the domain user accounts and the corresponding passwords for the Commerce Server Direct Mailer Service and the Administration database. You also use the Configuration Wizard to configure the Reporting Service for Commerce Server Staging.

Note:
In SQL Server Enterprise Manager, make sure that SQL Server is running before you start the Configuration Wizard (the icon in the Enterprise Manager window displays a green light). If it is not running, right-click the computer name, and then click Start.

The following steps describe how to configure a Commerce Server installation by using the Configuration Wizard.

To configure Commerce Server

  1. In Windows Explorer, locate <drive>:\Program Files\Microsoft Commerce Server 2006, and then double-click CSConfig.exe.

  2. On the Welcome to the Microsoft Commerce Server 2006 Configuration Wizard page, click Next.

  3. On the Administration Database page, do the following:

    Use this To do this

    SQL Server

    Type the computer name.

    Database Name

    Accept MSCS_Admin as the default database name, or type a new name for the Administration database.

  4. In the Connect Using section, do the following:

    Use this To do this

    Windows Authentication

    Select this option to use integrated Windows authentication for the Administration database.

    Note:
    We recommend that you use this option for Commerce Server.

    SQL Server Authentication

    Select this option to use SQL Server authentication for the Administration database.

    Note:
    There are security risks associated with using SQL Authentication in a Commerce Server deployment. We do not recommend that you use this option.

    Login Name

    Type the SQL Server login name for the SQL Server computer.

    Password

    Type the SQL Server password for the SQL Server computer.

    Test

    Click to test the connection to the Administration database.

  5. Click Next.

  6. On the Staging Service page, select Configure Reporting Service for Commerce Server Staging to configure IIS for the Commerce Server Staging Reporting Service, and in the Staging Service Account section, do the following:

    Use this To do this

    Login Name

    Type <Computer name>\CSWPA for the Staging Service account, or click Browse to open the Select User dialog box to enter the user name.

    Password

    Type the password for the domain account.

    Note that the Reporting Service for Commerce Server Staging requires ASP.NET to display reports. You must enter a Login Name and Password for running the staging service to proceed with configuration.

  7. Click Next.

  8. On the Marketing Direct Mailer page, do the following:

    Use this To do this

    SQL Server

    Type the name of the computer where you installed SQL Server.

    Database Name

    Accept DirectMailer as the database name, or type a new name for the Direct Mailer database.

  9. In the Connect Using section, do the following:

    Use this To do this

    Windows Authentication

    Select this option to use integrated Windows authentication for the Direct Mailer database.

    Note:
    We recommend that you use this option for Commerce Server.

    SQL Server Authentication

    Select this option to use SQL Server authentication for the Direct Mailer database.

    Note:
    There are security risks associated with using SQL Authentication in a Commerce Server deployment. We do not recommend that you use this option.

    Login Name

    Type the SQL Server login name for the SQL Server computer.

    Password

    Type the SQL Server password for the SQL Server computer.

    Test

    Click to test the connection to the Direct Mailer database.

  10. In the Direct Mailer Service Account section, do the following:

    Use this To do this

    Login Name

    Type <Computer name>\CSWPA for the Direct Mailer Service account, or click Browse to open the Select User dialog box to enter the user name.

    Password

    Type the password for the domain account.

  11. Click Next.

  12. On the Summary page, review the components you are configuring.

    Note:
    To save the configuration XML file, click Save. You can later reconfigure the XML file by running the Configuration Wizard and selecting Load on the Welcome to the Microsoft Commerce Server 2006 Configuration Wizard page.

  13. Click Next to configure the components.

  14. After the configuration finishes, view the Microsoft Commerce Server 2006 Deployment Roadmap to help guide you through the steps of deploying Commerce Server.

  15. Click Finish to complete the Configuration Wizard.

Configuring the Starter Site

After you install and configure Commerce Server 2006, you configure the Starter Site for Commerce Server. The Starter Site is a sample site that you use as a template to build your own retail Web site by using Commerce Server 2006. The Starter Site includes Web pages and controls that are pre-configured to showcase the wide variety of features in Commerce Server 2006, such as the Catalog, Marketing, and Profiles Systems. To set up the Starter Site, you do the following:

After installing the Starter Site, you will have a fully-functioning, production-ready retail Web site that runs on Commerce Server 2006. You can edit the Web pages and catalog data to start customizing the site for your own purposes.

Download the Starter Site

Use the following steps to download the Starter Site executable package (CS2006-Beta1-StarterSite-x86-en.exe) from http://go.microsoft.com/fwlink/?linkid=59060. You must first register at the Microsoft Connect site to download the Starter Site.

To download the Starter Site

  1. Start Internet Explorer and move to http://go.microsoft.com/fwlink/?linkid=59060.

  2. On the Microsoft Connect page, in the left pane, click My Participation.

  3. On the Passport login page, log on to the Microsoft Connect site.

  4. On the My Participation page, click Commerce Server.

  5. On the Commerce Server 2006 Beta Connect Site page, in the Downloads section, click Starter Site.

  6. In the File Download dialog box, click Save.

  7. In the Save As dialog box, move to the folder where you want to save the Starter Site executable package (for example, <drive:>\Program Files\Microsoft Commerce Server 2006), and then click Save.

  8. In the Download complete dialog box, click Close.

Extract the Starter Site

Use the following steps to extract the Starter Site, which consists of the Starter.pup package and the sampledataimport.exe script.

To extract the Starter Site

  1. Click Start, click Run, type explorer, and then click OK.

  2. In Windows Explorer, move to the location where you saved the Starter Site executable package (for example, <drive:>\Program Files\Microsoft Commerce Server 2006), and then double-click CS2006-Beta1-StarterSite-x86-en.exe.

  3. In the first Commerce Server 2006 Starter Site Beta 1 dialog box, click Yes.

  4. In the second Commerce Server 2006 Starter Site Beta 1 dialog box, type a location to store the extracted files, for example, <drive:>\Program Files\Microsoft Commerce Server 2006, and then click OK.

  5. In the Commerce Server 2006 Starter Site Beta 1 dialog box informing you that the Starter Site was unpacked successfully, click OK.

Unpack the Starter Site Pup Package

The Starter Site Pup package (Starter.pup) includes the Commerce Server 2006 resources, Web services, and an application framework. Before you unpack the Starter Site Pup package, note the following:

  • Verify that you are logged on as a member of the Administrators group.

  • If you cancel the unpacking process, Commerce Server may not delete the databases you created during the unpacking process. You should delete the databases manually by using SQL Server Enterprise Manager.

To unpack the Starter Site Pup package

  1. Click Start, click Run, type explorer, and then click OK.

  2. In Windows Explorer, move to the location where you extracted the Starter Site files (for example, <drive:>\Program Files\Microsoft Commerce Server 2006), and then double-click Starter.pup.

  3. On the Unpack page, select Quick unpack, and then click Next.

  4. On the Quick Unpack page, do the following:

    Use this To do this

    Site name

    Type StarterSite as the name of the Web site.

    IIS Web site

    Accept Default Web Site as the IIS Web site.

    SQL Server Computer

    Type the computer name.

    Use Windows Integrated security

    Select this option to use Windows Integrated security for the databases.

    Note:
    We recommend this configuration.

    Use a specific user name and password

    Select this option to use SQL Server authentication when connecting to the databases.

    Note:
    We do not recommend this configuration.

    SQL Server Login Name

    Type the SQL Server login name for the databases.

    SQL Server Login Password

    Type the SQL Server login password.

  5. On the Quick Unpack page, click Next.

  6. On the first of two Profiling System pages, click Next to accept the default settings.

  7. On the second Profiling System page, click OK to accept the default settings.

  8. In the Commerce Server Site Packager dialog box, review the list of resources that you configured to use Windows Integrated security, and then click OK.

    These resources require access permissions on the appropriate Windows accounts. You will assign permissions in the following post-installation steps.

  9. On the Unpacking is complete! page, click Finish.

Note:
After unpacking is finished, to review the list of events in the Site Packager log file, click View Log File.

Import the Sample Data

Use the following steps to import the sample data for the Starter Site. The sample data includes the Adventure Works product catalog.

To import the sample data

  1. Click Start, click Run, type cmd, and then click OK.

  2. At the command prompt, move to the directory where you put the extracted Starter Site files, for example, <drive:>\Program Files\Microsoft Commerce Server 2006.

  3. In the Starter Site files directory, type SampleDataImport.exe <drive:>\Inetpub\Wwwroot\StarterSite to import the sample data, and then press ENTER.

  4. After catalog import is complete, close the command prompt window.

Copy the Product Images

Use the following steps to copy the product images to the Web site. The Starter Site will not display images for the products in the sample catalog if you omit these steps.

To copy the product images

  1. Click Start, click Run, type explorer, and then click OK.

  2. In Windows Explorer, move to the <drive:>\Program Files\Microsoft Commerce Server 2006\SDK\Samples\Catalog folder, right-click the AdvWorksImages.zip file, and then click Extract All.

  3. On the Welcome to the Compressed (zipped) Folders Extraction Wizard page, click Next.

  4. On the Select a Destination page, type <drive:>\Inetpub\Wwwroot\StarterSite\Images, and then click Next.

  5. On the Extraction Complete page, clear the Show extracted files check box, and then click Finish.

Post-Installation Requirements

After you install Commerce Server, you must follow these post-installation steps in the order listed:

  1. Unpack the Web Services. You must unpack the Business Management Web services from the CSharp Pup package to run the Business User applications.

  2. Assign Write Permissions to the Starter Site Authorization Policies. You must assign write permissions to the Starter Site authorization policies so users can access the Web services.

  3. Assign Write Permissions to the Temporary ASP.NET Folder. You must assign write permissions to the Temporary ASP.NET folder to run the Starter Site.

  4. Assign Full Control to the Windows Temporary Folder. You must assign full control to the Windows Temporary folder to run the Starter Site.

  5. Add Users to the Starter Site Authorization Policy Roles. You must add users to the Starter Site authorization policy roles so that users can run the Business Management applications.

  6. Grant Access to the Databases. You must grant access to the databases to run the Business User applications.

  7. Enable Secure Sockets Layer. You must enable Secure Sockets Layer (SSL) to support security on the retail Web site.

  8. Assign Permissions to the IIS Worker Process Accounts. You must assign the ASP.NET worker process account permissions to the appropriate databases and Web services authorization policies.

  9. Assign Read Access to the MSCS_Admin Database. You must grant read access to the MSCS_Admin database for the account on which your ASP.NET process is running.

  10. Verify the Starter Site Configuration. You verify the Starter Site configuration to ensure that the Starter Site displays properly in a browser window.

  11. Customize the Starter Site. You customize the Starter Site to modify the text and appearance of the site.

  12. Install the Business Management Applications. You must follow this step for all computers on which you want to access the Business Management applications.

Unpack the Web Services

Use the following steps to unpack the Business Management Web services for the Starter Site. The Starter Site Pup package does not include these Web services, so you unpack them from the CSharp pup package.

To unpack the Web services

  1. Click Start, point to Programs, point to Microsoft Commerce Server 2006, point to Tools, and then click Site Packages.

  2. In the Pup Packages folder, double-click CSharp.pup.

    Commerce Server Site Packager starts.

  3. On the Unpack page, select Custom Unpack, and then click Next.

  4. On the Unpack Method page, select Add an application in the package to an existing site, and then click Next.

  5. On the Select Site page, select StarterSite, and then click Next.

  6. On the Select Applications page, check the following boxes only:

    • MarketingWebService

    • OrdersWebService

    • ProfilesWebService

    • CatalogWebService

    Make sure that the CSharpSite box is not checked, and then click Next.

  7. On the Select IIS Computers, Web Sites and Paths page, click Next.

  8. On the Unpacking is complete! page, click Finish.

Assign Write Permissions to the Starter Site Authorization Policies

After you unpack the Starter Site Pup package, Commerce Server extracts the Web service authorization policies from the following Web service applications:

  • Catalog Web Service (<drive>:\Inetpub\wwwroot\CatalogWebService\CatalogAuthorizationStore.xml)

  • Marketing Web Service (<drive>:\Inetpub\wwwroot\MarketingWebService\MarketingAuthorizationStore.xml)

  • Customer and Orders Web Service (<drive>:\Inetpub\wwwroot\OrdersWebService\OrdersAuthorizationStore.xml)

  • Profiles Web Service (<drive>:\Inetpub\wwwroot\ProfilesWebService\ProfilesAuthorizationStore.xml)

You must follow these steps before your users can access the Web services.

To assign write permissions to the Starter Site authorization policies

  1. Click Start, click Run, type explorer, and then click OK.

  2. In Windows Explorer, move to the directory where you installed the authorization policy, (for example, <drive:>\Inetpub\Wwwroot\CatalogWebService\CatalogAuthorizationStore.xml).

  3. In the <Web Service name> folder, right-click the XML file, and then click Properties.

  4. In the <XML file name> Properties dialog box, on the Security tab, click Add.

  5. In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type <Computer name>\CSWPA, and then click OK.

  6. In the <Group or user name> box, select the business user account or Windows group.

  7. In the Permissions for <account or group name> box, select Write in the Allow column, and then click OK.

  8. Repeat steps 2 through 7 for each authorization policy role.

Assign Write Permissions to the Temporary ASP.NET Folder

Use the following steps to assign write permissions to the Temporary ASP.NET folder. You will not be able to run the Business User applications that are hosted by the Business Management Web services if you omit these steps.

To assign write permissions to the Temporary ASP.NET folder

  1. Click Start, click Run, type explorer, and then click OK.

  2. In Windows Explorer, move to the <drive:>\Windows\Microsoft.NET\Framework\v2.0.50727 folder, right-click Temporary ASP.NET Files, and then click Properties.

  3. In the Temporary ASP.NET Files dialog box, on the Security tab, click Add.

  4. In the Enter the object names to select box, type <Computer name>\CSWPA, and then click OK.

  5. In the Temporary ASP.NET Files dialog box, in the Groups or user names box, click <Computer name>\CSWPA.

  6. In the Permissions for <Computer name>\CSWPA box, select Write in the Allow column, and then click OK.

  7. In the Security dialog box, click Yes.

Assign Full Control to the Windows Temporary Folder

Use the following steps to assign full control to the Windows Temporary folder. You will not be able to run the Business User applications that are hosted by the Business Management Web services if you omit these steps.

To assign full control to the Windows Temporary folder

  1. Click Start, click Run, type explorer, and then click OK.

  2. In Windows Explorer, move to the <drive:>\Windows folder, right-click Temp, 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 <Computer name>\CSWPA, and then click OK.

  5. In the Temp Properties dialog box, in the Groups or user names box, click <Computer name>\CSWPA.

  6. In the Permissions for <Computer name>\CSWPA box, select Full Control in the Allow column, and then click OK.

  7. In the Security dialog box, click Yes.

Add Users to the Starter Site Authorization Policy Roles

Commerce Server provides several predefined authorization policy roles to which you assign business users so that they can perform specific tasks such as editing a catalog, creating a discount, and deleting an order. You use the Authorization Manager Microsoft Management Console (MMC) to add individual users or user groups to a role.

After you assign write permissions to the authorization policies, in order to perform any operation in the Business Management applications, you assign business users to administrator roles for each Web service. The administrator role lets business users perform any operation in the system. For example, the Catalog Administrator role lets users perform any operation in the Catalog System.

To restrict business users from performing all tasks, you assign them to specific roles such as the CatalogPropertyEditor role, where users can only manage individual catalog properties. For information about how to use Windows Authorization Manager to help secure specific business user roles, see "Managing Authorization Policies" in Commerce Server 2006 Help.

The following table lists the Web Services and their corresponding administrator roles.

Web Service Authorization Policy Role

Catalog Web service

CatalogAdministrator

Marketing Web service

MarketingAdministrator

Customer and Orders Web service

OrdersAdministrator

Profiles Web service

ProfileAdministrator
Note:
Before you assign business user access to the Authorization Manager policy roles, we recommend that you assign the business user to a Windows group, and then give the Windows group Authorization Manager permissions on the Web services.

Use the following steps to add business users to the Starter Site authorization policy roles.

To add users to the Starter Site authorization policy roles

  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 locate the authorization policy for the Starter Site Web service. For example, the catalog authorization policy XML file is located at <drive:>\Inetpub\Wwwroot\CatalogWebService.

  4. Select <authorization policy name>.xml, and then click Open.

  5. In the Open Authorization Store dialog box, click OK.

  6. Expand the authorization policy to \<authorization policy name>.xml\<System name>\Role Assignments\<Role name>. For example, \CatalogAuthorizationStore.xml\ProductCatalogSystem\Role Assignments\Catalog Administrator.

  7. Right-click <Role name>, and then click Assign Windows Users and Groups.

  8. In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type the name of the business user account or Windows group, and then click OK.

  9. Repeat steps 2 through 8 for each authorization policy role.

Grant Access to the Databases

Use the following steps to grant access to the databases. You will not be able to run the Business User applications that are hosted by the Business Management Web services if you omit these steps.

To grant access to the databases

  1. Click Start, point to 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 <Computer name>, expand Security, right-click Logins, and then click New Login.

  3. In the SQL Server Login Properties dialog box, on the General tab, in the Name box, type <Computer name>\CSWPA.

  4. On the Database Access tab, in the Specify which databases can be accessed by this login box, select the check box for DirectMailer, in the Database roles for <database name> box, select the check box for db_owner.

  5. Repeat the previous step to grant db_owner access to the following databases:

    • MSCS_Admin

    • MSCS_CatalogScratch

    • StarterSite_marketing

    • StarterSite_marketing_lists

    • StarterSite_productcatalog

    • StarterSite_profiles

    • StarterSite_transactionconfig

    • StarterSite_transactions

  6. Click OK.

  7. Close SQL Server Enterprise Manager

Enable Secure Sockets Layer

Use the following steps to enable Secure Sockets Layer (SSL) with the SelfSSL tool in the Internet Information Services (IIS) 6.0 Resource Kit.

To enable SSL

  1. In Internet Explorer, move to http://go.microsoft.com/fwlink/?linkid=59276.

  2. On the Internet Information Services (IIS) 6.0 Resource Kit Tools page, click Download.

  3. In the File Download dialog box, click Save.

  4. In the Save As dialog box, move to the folder where you want to save the executable package (for example, <drive:>\Program Files\Microsoft Commerce Server 2006), and then click Save.

  5. In the Download complete dialog box, click Close.

  6. Click Start, click Run, type explorer, and then click OK.

  7. In Windows Explorer, move to the location where you saved the executable package (for example, <drive:>\Program Files\Microsoft Commerce Server 2006), and then double-click iis60rkt.exe.

  8. In the Open File dialog box, click Run.

  9. On the Welcome to the InstallShield Wizard for the IIS 6.0 Resource Kit Tools page, click Next.

  10. On the End-User License Agreement page, accept the terms of the license, and then click Next.

  11. On the Customer Information page, type your user name and organization, and then click Next.

  12. On the Setup Type page, select Complete, and then click Next.

  13. On the Start Copying Files page, click Next.

  14. On the InstallShield Wizard Complete page, click Finish.

  15. Click Start, point to Programs, point to IIS Resources, point to SelfSSL, and then click SelfSSL.

  16. At the command prompt, type Selfssl /T /V:100, and then press ENTER.

    The SelfSSL tool configures an SSL Certificate on the Default Web Site that expires in 100 days.

Assign Permissions to the IIS Worker Process Accounts

The Microsoft Internet Information Services (IIS) worker process is determined by the application pool to which the Web service application belongs. You must assign the appropriate permissions to the IIS worker process accounts for users to have access to the Web services. For example, you must add the IIS worker process account to the db_owner role on the catalog database to have access to the Catalog Web Service.

You must follow these steps in the order shown to assign the permissions to the IIS worker process accounts.

Step 1: Configure the Application Pool Account

The following steps show how to configure the application pool to use the IIS worker process account.

To configure the application pool account

  1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

  2. In IIS Manager, expand <Computer name> (local computer), and then expand the Application Pools folder.

  3. Right-click the application pool you want to configure, for example DefaultAppPool, and then click Properties.

  4. In the <Application pool> Properties dialog box, on the Identity tab, click Configurable.

  5. Click Browse, and under Enter the object name to select, type the account name on which you want your worker process to run (<Computer name>\CSWPA), and then click OK.

  6. In the Password box, type the password associated with this account. If there is no password associated with the account, leave the Password box blank, and then click OK.

  7. In the Confirm Password dialog box, retype the password, and then click OK.

    Note:
    If the account you created must be able to start Common Gateway Interface (CGI) processes, assign the following user rights to this account.

    • Adjust memory quotas for a process.

    • Replace a process level token.

      For more information about how to configure user rights for CGI applications, see "Configuring CGI Applications" in IIS Help.

Step 2: Enable the Default Content Page

The following step shows how to enable the default content page.

To enable the default content page

  1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

  2. In IIS Manager, expand <Computer name> (local computer), expand Web Sites, right-click Default Web Site, and then click Properties.

  3. In the Default Web Site Properties dialog box, on the Documents tab, in the Enable default content page section, make sure that the Default.aspx page is listed (if not, click Add), and then click OK.

Step 3: Enable Script Permissions

The following step shows how to enable script permissions.

To enable script permissions

  1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

  2. In IIS Manager, expand <Computer name> (local computer), expand Web Sites, right-click Default Web Site, and then click Properties.

  3. In the Default Web Site Properties dialog box, on the Home Directory tab, in the Application settings section, in the Execute permissions drop-down list, select Scripts only, and then click OK.

Step 4: Add the Worker Process Account to the IIS_WPG group

The following step shows how to add the IIS worker process account to the IIS_WPG group on the server that is running IIS.

To add the IIS worker process account to the IIS_WPG group

  1. On the desktop, right-click My Computer, and then click Manage.

  2. In the Computer Management screen, under System Tools, expand Local Users and Groups, and then click Groups.

  3. Right-click the IIS_WPG group, and then click Add to Group.

  4. In the IIS_WPG Properties dialog box, click Add.

  5. In the Select User, Computers, or Groups dialog box, under Enter the object names to select box, type the account name on which you want your worker process to run (<Computer name>\CSWPA), and then click OK.

  6. In Windows Explorer, locate the <drive>:\windows\temp folder, and then assign the CSWPA account read permissions.

Step 5: Assign Permissions to the IIS Worker Process Accounts

The following steps show how to assign permissions to the IIS worker process account on the <site name>_commerce database and the MSCS_CatalogScratch database. These steps are for SQL Server 2000; the steps for performing this task in SQL Server 2005 are provided below.

To assign permissions to the IIS worker process accounts in SQL Server 2000

  1. Click Start, point to 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/<SQL Server name>/Security.

  3. Right-click Logins, and then click New Login.

  4. In the SQL Server Login Properties dialog box, on the General tab, in the Name box, type <Computer name>\CSWPA.

  5. Under Authentication, in the Domain box, select the appropriate domain from the drop-down list.

  6. On the Database Access tab, under Specify which database can be accessed by this login, select the <site name>_commerce database to which you want to assign permissions. By default, each Commerce Server resource is unpacked to its own database.

  7. Under Database roles for <database name>, select the db_owner role, and then click OK to assign the db_owner role to the IIS worker process account.

  8. Repeat steps 6 and 7 for the MSCS_CatalogScratch database.

  9. Click OK, and then close SQL Server Enterprise Manager.
To assign permissions to the IIS worker process accounts in SQL Server 2005

  1. Click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.

  2. In the Connect to Server dialog box, click Connect.

  3. In SQL Server Management Studio, expand <servername>(Windows NT), expand Security, expand Logins, right-click <Computer name>\CSWPA, and then click Properties.

  4. In the Login Properties <account name> dialog box, in the left pane, click User Mapping.

  5. In the right pane, in the Users mapped to this login box, in the Map column, select the <site name>_commerce database.

  6. In the Database role membership for <database name> box, select the check box for the db_owner role on the database, and then click OK.

  7. Repeat steps 5 and 6 for the MSCS_CatalogScratch database.

Assign Read Access to the MSCS_Admin Database

You must assign read access to the MSCS_Admin database for the account on which your ASP.NET process is running. These steps are for SQL Server 2000; to perform these steps in SQL Server 2005, see the previous step, "Step 3: Assign Permissions to the IIS Worker Process Accounts."

To assign read access to the MSCS_Admin database

  1. Click Start, point to 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, in the Name box, click the ellipsis [...] button to open the second SQL Server Login Properties - New Login dialog box.

  5. In the List Names From box, select the local computer name from the drop-down box.

  6. In the Names box, select ASPNET (ASP.NET Machine Account), click Add, and then click OK.

  7. Click Logins, right-click the ASPNET account to which you are assigning read access to the MSCS_Admin database, and then click Properties.

  8. In the SQL Server Login Properties dialog box, on the Database Access tab, under Specify which database can be accessed by this login, select the MSCS_Admin database.

  9. Under Database roles for MSCS_Admin, select db_datareader for the database, and then click OK.

Verify the Starter Site Configuration

Use the following steps to verify the Starter Site configuration.

To verify the Starter Site configuration

  1. In Internet Explorer, move to http://localhost/StarterSite.

  2. On the Starter Site home page, click Adventure Works Catalog to verify that the sample catalog was imported successfully. You should be able to view the product catalog.

  3. On the product catalog page, select a category to view the products within that category.

  4. Select a product to view its details, and verify that the product image appears.

  5. Repeat the previous step to verify that product images appear correctly.

Customize the Starter Site

Use the following steps to customize the Starter Site.

To customize the Starter Site

  1. Click Start, point to Programs, point to Microsoft Visual Studio 2005, and then click Microsoft Visual Studio 2005.

  2. In Visual Studio 2005, on the File menu, point to Open, and then click Web Site.

  3. In the Open Web Site dialog box, in the Folder box, type http://localhost/startersite, and then click Open.

    Visual Studio 2005 opens the Starter Site development solution. You can edit the layout and text of the Web site pages by opening the various files in the solution (for example, Default.aspx and StandardLayout.master).

Install the Business Management Applications

After you install and configure Commerce Server 2006, you install the Commerce Server 2006 Business Management applications. Commerce Server 2006 includes the following Business Management applications:

  • Catalog Manager. Required for product catalog Web site management activities.

  • Customer and Orders Manager. Required for order management Web site activities.

  • Marketing Manager. Required for discount, advertisements, and direct mail Web site management activities.

To install the Business Management applications

  1. Double-click Setup.exe at the root of the CD set up image.

  2. On the Microsoft Commerce Server 2006 Start page, under Install, click Microsoft Commerce Server Business User Applications.

  3. On the Customer Information page, type your customer information, and then click Next.

  4. On the License Agreement page, click Yes, I accept the terms of the license agreement, and then click Next.

  5. On the Component Installation page, select the Business Management application(s) you want to install.

  6. Accept the default installation folder, or click Browse to specify a different folder, and then click Next.

  7. On the Summary page, click Install.

  8. On the Installation Completed page, click Finish.

After you install the Business Management application user interfaces, you access them on the Start menu.

To access the Business Management applications

  1. Click Start, point to Programs, point to Microsoft Commerce Server 2006, and then click the Business Management application you want to access, for example, Catalog Manager.

  2. In the Site Connections dialog box, do the following:

    Use this To do this

    Name

    Accept the Default site connection from the drop-down list.

    <Web Service>

    Type the URL for your connection to the Web service. For example, to connect to the Catalog Web service, type http://<server name>/CatalogWebService/CatalogWebService.asmx.

  3. Click OK to open the Business Management application.

Unattended Installation

Commerce Server 2006 enables automated electronic software distribution, also known as unattended installation. You use unattended installation to install Commerce Server 2006 in an automated way on computers that have the same configurations. Unattended installation lets system administrators who want to install Commerce Server 2006 on remote computers do so without user intervention. With an unattended installation, a user does not have to monitor the installation and provide input.

To perform an unattended installation, use the command-line options provided to suppress all interaction and provide parameters for all options.

When you perform an unattended installation, the installation program does not display messages. Instead, a log file captures the installation information that includes whether the installation was successful. You can then review the log file and determine the results of the installation.

Note:
Commerce Server 2006 does not allow for unattended installation for clustered resources.

Note:
You cannot remove features by using unattended installation.

Before you install Commerce Server 2006 by using an unattended installation, you must uninstall earlier versions of Commerce Server. For information about uninstalling Commerce Server, see Uninstalling Commerce Server.

Installing an Unattended Installation of Commerce Server 2006

Follow these steps to perform an unattended installation of Commerce Server 2006.

To perform an unattended installation of Commerce Server 2006

  1. Click Start, point to All Programs, point to Accessories, and then click Command Prompt.

  2. To start the unattended installation, at the command prompt, type setup.exe /<command name> <options>, and then press ENTER.

    The following table shows the Windows Server 2003 command-line options that you use to install Commerce Server 2006.

    Command name Option Description

    /ADDLOCAL  

    <feature list> or ALL

    Comma delimited list of features to install or ALL for a complete installation.

    /COMPANYNAME  

    <company name>

    Sets the company name.

    /HELP, or /?, or /H

    Provides help and quick reference.

    /FORCERESTART

    Always forces a restart after the installation is finished.

    /I

    <file path>

    Specifies the log file path.

    /IGNOREDEPENDENCIES

    Bypasses checks for downloadable prerequisites.

    /Installdir

    <product installation path>

    Specifies the full path on which to install the product.

    /L, or /LOG  

    <Logfile> [i][w][e][a][r][u][c][m][p][v][*]

    Writes logging information into a log file to the specified path. Always uses verbose MSI logging, and appends to an existing file.

    The following flags indicate the information to log:

    • i - Status messages

    • w - Nonfatal warnings

    • e - All error messages

    • a - Startup of actions

    • r - Action-specific records

    • u - User requests

    • c - Initial user interface parameters

    • m - Out-of-memory

    • p - Terminal properties

    • v – Verbose output

    • * - All

    NORESTART

    Suppresses restart prompts and automatic restarts at the end of the installation.

    /PRODUCT

    <CommerceServer, or CSMarketingUI, or CSCatalogUI, or CSOrdersUI>

    Installs one of the following:

    • CommerceServer

    • CSMarketingUI

    • CSCatalogUI

    • CSOrdersUI

    /PASSIVE

    Performs a passive installation. The Setup program only displays the progress bar.

    /PROMPTRESTART

    Prompts the user before restarting.

    This option cannot be used with the /QUIET option.

    /Q

    {n|b|r|f}

    Sets the user interface level.

    The following are the types of interfacelevels you can set:

    • qn - No user interface.

    • qb - Basic user interface.

    • qr - Reduced user interface with a modal dialog box displayed at the end of the installation.

    • qf - Full user interface with a modal dialog box displayed at the end of the installation.

    /QUIET

    Unattended installation.

    /REMOVE

    <feature list> or ALL

    Comma delimited list of features to remove or ALL to remove all features.

    /REPAIR

    <feature list> or ALL

    Comma delimited list of features to repair or ALL to repair all features.

    /REINSTALL

    <feature list> or ALL

    Comma delimited list of features to reinstall or ALL to reinstall all features if they are already installed.

    /S  

    <Configuration XML file>

    Performs an unattended installation of the features found in the Configuration file.

    /TARGETDIR

    <32-bit program files folder>

    Provides Setup with the 32-bit program files location.

    /USERNAME  

    <User name>

    Sets the user name.

    /X, or /UNINSTALL

    Uninstalls Commerce Server.

The following table shows examples of how to perform an unattended installation for Commerce Server and each Business Management application.

Name At the command prompt, type:

Commerce Server

<Commerce Server 2006 drop location>\setup.exe /l %systemdrive%\geinstall.log /ADDLOCAL ALL /PRODUCT CommerceServer

Catalog Manager

<Commerce Server 2006 drop location>\setup.exe /l %systemdrive%\gecminstall.log /ADDLOCAL ALL /PRODUCT CSCatalogUI

Customer and Orders Manager

<Commerce Server 2006 drop location>\setup.exe /l %systemdrive%\geominstall.log /ADDLOCAL ALL /PRODUCT CSOrdersUI

Marketing Manager

<Commerce Server 2006 drop location>\setup.exe /l %systemdrive%\gedminstall.log /ADDLOCAL ALL /PRODUCT CSMarketingUI

For more information about Windows Server 2003 command-line options, see the Windows Server 2003 online documentation.

Uninstalling Commerce Server

To uninstall Commerce Server 2006 and all its components, you must follow these steps in the order shown.

Caution:
Do not uninstall Commerce Server 2006 on a computer on which BizTalk Server is installed. The BizTalk Server installation will become non-functional.

Note:
After performing the following steps, we recommend that you restart the computer.

Step 1: Remove the Commerce Server Runtime Objects and Administration Tools

Follow these steps to remove the Commerce Server 2006 runtime objects and administration tools.

To remove Commerce Server 2006 runtime objects and administration tools

  1. Click Start, and then click Control Panel.

  2. In Control Panel, double-click Add or Remove Programs.

  3. In the Add or Remove Programs dialog box, click Remove next to Microsoft Commerce Server 2006.

  4. In the Add or Remove Programs dialog box, click Yes to confirm that you want to remove Commerce Server 2006.

Step 2: Remove the Commerce Server Databases

Follow these steps to remove the Commerce Server Administration database and additional databases associated with your site.

To remove the Commerce Server 2006 databases

  1. Click Start, point to Programs, point to Microsoft SQL Server, and then click Enterprise Manager.

  2. In SQL Server Enterprise Manager, make sure that SQL Server is running (the icon in the Enterprise Manager window displays a green light). If SQL Server is not running, right-click the name of the computer that SQL Server is supposed to run on, and then click Start.

  3. Expand the nodes to the following path: \Microsoft SQL Servers\SQL Server Group\SQL Server Name\Databases.

  4. Right-click the database you want to remove, and then click Delete.

  5. Repeat step 3 for each Commerce Server database.

Step 3: Remove the Business Management Applications

You perform the following step if you added any one of the following Business Management applications:

  • Catalog Manager

  • Customer and Orders Manager

  • Marketing Manager

To remove the Commerce Server 2006 Business Management applications

  1. Click Start, and then click Control Panel.

  2. In Control Panel, double-click Add or Remove Programs.

  3. In the Add or Remove Programs dialog box, click Remove next to <Business Management application>, for example, Microsoft Commerce Server 2006 Catalog Manager.

  4. In the Add or Remove Programs dialog box, click Yes to confirm that you want to remove the Business Management application.

Step 4: Delete the Commerce Server Site Virtual Directories

If you unpacked a site, you must follow these steps to remove the site virtual directories.

To delete the site virtual directories

  1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.

  2. In Internet Services Manager, expand the nodes to the following path: \<Computer name>\Web Sites\<IIS Web site name>.

  3. Right-click the virtual directories you want to delete, and then click Delete.

  4. In the Internet Services Manager dialog box, click Yes to confirm the deletion.

  5. Repeat steps 3 and 4 for each virtual directory you want to delete.

Step 5: Delete the Commerce Server 2006 Site Folders and Files

If you unpacked a site, you must follow these steps to delete the site folders and files.

To delete the site folders and files

  1. In Windows Explorer, locate the directory where you installed the site files, for example, <drive>:\Inetpub\wwwroot.

  2. Right-click the folder you want to delete, and then click Delete.

  3. In the Confirm Folder Delete dialog box, click Yes to confirm the deletion.

  4. Repeat steps 2 and 3 for each folder you want to delete.

Troubleshooting Your Commerce Server Installation

This section describes problems you might experience when you install or uninstall Commerce Server 2006, and offers possible solutions.

SQL Server cannot find the Administration database

If you change the name of the computer on which you install Commerce Server, SQL Server may not automatically find the Administration database.

Solution

You must change the SQL Server login and password for the Administration database.

To change the SQL Server login and password for the Administration database

  1. In the Microsoft Commerce Server Manager console, right-click Commerce Server Manager, and then click Properties.

  2. In the Commerce Server Manager Properties dialog box, on the Administration Database tab, click Modify.

  3. After you make the required changes in the Data Link Properties dialog box, click OK.

Cannot configure the Administration database

The Administration database (MSCS_Admin) configuration screen displays an error message starting with "Execution of the TSQL command,..." and you cannot continue.

Solution

To continue configuring the Administration database, do the following:

  1. Verify that the SQL Server Agent service is running on the computer that is running SQL Server.

  2. If you are starting a new installation of Commerce Server 2006, and you have used Enterprise Manager to verify that no MSCS_Admin or DirectMailer database exists on the server that is running SQL Server, you must verify that the SQL Server 2000 Data folder does not contain the following files:

    • Mscs_admin.mdf

    • Mscs_admin.ldf

    • Directmailer.mdf

    • Directmailer.ldf

  3. Verify that you have purchased enough licenses for your SQL Server installations.

  4. Verify that you are not using a pre-release version of SQL Server.

Cannot reinstall Commerce Server to create a new Administration database

You cannot reinstall Commerce Server to create a new Administration database. You must roll back to a previous Administration database or create a new Administration database. The Repair mode in the Commerce Server Setup program does not create a new Administration database.

Solution

Create a new Administration database named MSCS_Admin, and then in SQL Query Analyzer, run the admin_schema.sql and admin_schema_increment.sql scripts. The system creates a new Administration database. When you run the scripts, the system populates the schema of the Administration database but does not create any resources.

To create a new Administration database

  1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Enterprise Manager.

  2. In the Enterprise Manager, expand the nodes to the following path: Microsoft SQL Servers/SQL Server Group/<SQL Server name>/Databases.

  3. Right-click Databases, and then click New Database.

  4. In the Database Properties dialog box, on the General tab, in the Name box, type MSCS_Admin, and then click OK.

After you create your new database, run the admin_schema.sql script, followed by the admin_schema_increment.sql script.

To run the admin_schema.sql script from SQL Query Analyzer

  1. In Enterprise Manager, click the MSCS_Admin database to select it.

  2. On the Tools menu, select SQL Query Analyzer, and then click Open on the toolbar.

  3. Locate Program Files\Microsoft Commerce Server 2006\admin_schema.sql, select the script file, and then click Open.

  4. On the toolbar, click Execute Query.
To run the admin_schema_increment.sql script from SQL Query Analyzer

  1. In Enterprise Manager, click the MSCS_Admin database to select it.

  2. On the Tools menu, select SQL Query Analyzer, and then click Open on the toolbar.

  3. Locate Program Files\Microsoft Commerce Server 2006\ admin_schema_increment.sql, select the script file, and then click Open.

  4. On the toolbar, click Execute Query.
Note:
After you run the scripts, you must unpack your sites again.

--------------------------------------------------------------------------------------------------

This document supports a preliminary release of a software product that may be changed substantially prior to final commercial release, and is the confidential and proprietary information of Microsoft Corporation. It is disclosed pursuant to a non-disclosure agreement between the recipient and Microsoft. This document is provided for informational purposes only and Microsoft makes no warranties, either express or implied, in this document. Information in this document, including URL and other Internet Web site references, is subject to change without notice. The entire risk of the use or the results from the use of this document remains with the user. 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.

© 2006 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, Active Directory, ActiveX, BackOffice, BizTalk, Developer Studio, FrontPage, JScript, MSDN, MSN, Outlook, PivotChart, PivotTable, Verdana, Visual Basic, Visual C++, Visual C#, Visual Studio, Win32, Windows Media, and Windows NT 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.