Last updated: June 2007

Note
For the most current version of this document, see the Microsoft® Download Center at http://go.microsoft.com/fwlink/?LinkID=57268. Additionally, for known issues and important, late-breaking information, see the "Microsoft Commerce Server 2007 Readme" located at http://go.microsoft.com/fwlink/?LinkID=57013.

This document provides an overview of the hardware, software, and security-enhanced configuration requirements for Commerce Server, and detailed instructions for installing and configuring Microsoft Commerce Server 2007 on a single computer. For instructions about how to deploy Commerce Server 2007 on multiple computers, see http://go.microsoft.com/fwlink/?LinkID=73089.

Note
If you are installing Commerce Server 2007 on a developer computer or for evaluation and want to minimize the security-related configuration procedures associated with installing Commerce Server 2007, then see the "Quick Installation Guide for Microsoft Commerce Server 2007" at http://go.microsoft.com/fwlink/?LinkID=79888.

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 2007.

In This Section

Before You Begin

Before you install and configure Commerce Server 2007, review the following sections to understand the components available, the objects that will be installed, the Commerce Server security-enhanced configuration requirements, and the tasks involved in the installation and configuration of Commerce Server.

This document provides instructions about how to install Commerce Server 2007 onto a single computer. This requires meeting hardware and software prerequisites, creating user accounts, installing and configuring Commerce Server 2007, performing post-installation procedures to set up the Commerce Server environment, and then installing the Commerce Server Business Management Applications and Commerce Server Adapters for Microsoft BizTalk® Server.

Note
Specific restrictions apply to the co-location of certain software components as described in Commerce Server Installation Considerations and Restrictions.

You must perform all tasks in the order indicated.

Note
This Installation Guide is for single-computer installations and does not include information about how to help secure Commerce Server services in a multi-computer configuration. For instructions about how to enhance security and how to deploy Commerce Server on multiple computers, see http://go.microsoft.com/fwlink/?LinkID=73089.

Commerce Server 2007 Software Overview

Commerce Server 2007 supports installation scenarios that address the needs of developers, IT professionals, business users, and system integrators. The installation scenarios are as follows:

  • Microsoft Commerce Server 2007. Installs the most common program features required to run a Commerce Server 2007 Web server. This includes the Commerce Server 2007 components and Commerce Server Manager. In addition, you can install one or more of the following optional components: Direct Mailer, Project Creation Wizard, Staging, Health Monitoring, and the Volume Shadow Copy Writer Service. These components provide additional functionality that IT professionals and developers use.

  • Microsoft Commerce Server Business Management Applications. Installs the Business Management applications that you select: Catalog Manager, Catalog and Inventory Schema Manager, Marketing Manager, and Customer and Orders Manager. Business users and IT professionals use these applications.

  • Microsoft Commerce Server Adapters for Microsoft BizTalk Server. Installs four Commerce Server adapters: BizTalk Adapter for Catalogs, BizTalk Adapter for Inventory, BizTalk Adapter for Orders, and BizTalk Adapter for Profiles. System integrators use the Commerce Server adapters to support line-of-business (LOB) application integration and data exchange.

The following table indicates the Commerce Server 2007 components that you typically install to support each server role.

Commerce Server Component System administrator computer Developer computer Web server Business user computer System Integrator computer

Commerce Server 2007 Core Components

Yes

Yes

Yes

No

No

Direct Mailer

Yes

No

No

No

No

Project Creation Wizard

No

Yes

No

No

No

Staging

Yes

Yes

Yes

No

No

Health Monitoring Service

Yes

No

Yes

No

No

Volume Shadow Copy Writer Service

Yes

No

No

No

No

Business Manager Applications

Yes

Yes

No

Yes

Yes

Commerce Server Adapters for BizTalk Server

No

No

No

No

Yes

Commerce Server Deployment Concepts and Terms

This section provides conceptual information about the objects and entities that Commerce Server installs.

Commerce Server Deployment

A Commerce Server deployment includes one or more physical installations of Commerce Server 2007 that use a single Commerce Server administration database. Commerce Server creates the administration database, named MSCS_Admin, when you run the Commerce Server Configuration Wizard. All Commerce Server sites that share a common MSCS_Admin database make up a single Commerce Server deployment.

Commerce Server Sites and Site Packages

A Commerce Server site includes a collection of site resources and .NET-connected applications that use these resources through the Commerce Server object model. By using a Commerce Server site, you can administer the applications in the site as a group. Be aware that a Commerce Server site does not map to the concept of a Web site in Internet Information Services (IIS).

You can pack sites into a package (PuP) file and unpack them by using the Commerce Server Site Packager. After you install and configure Commerce Server, you use an example PuP package file, such as the CSharp or StarterSite PuP files, to unpack the global and site resources and start Web site development.

Commerce Server Resources

A Commerce Server resource provides functionality to the applications in a Commerce Server site and contains properties that you can configure by using Commerce Server Manager. The two types of resources are global and site.

Global Resources

You can share global resources across Commerce Server sites. You cannot share site resources across Commerce Server sites. Commerce Server 2007 installs the following global resources during a package file unpack or Commerce Server configuration:

  • CS Authentication. Configures the authentication and identification method for your Commerce Server site when you use the AuthManager or AuthFilter methods. These methods are deprecated in Commerce Server 2007. We recommend that you use the Commerce Server Membership Provider method for authenticating users. For more information about how to implement authentication, see http://go.microsoft.com/fwlink/?LinkID=73090. When you use the Commerce Server Membership Provider to authenticate users, Commerce Server 2007 does not use the CS Authentication resource.

  • Data Warehouse. Imports and manages Web site data from Web log files, Commerce Server databases, and other data sources. This is an optional global resource that you install when you unpack the DW.pup package. For information about unpacking and configuring the Data Warehouse, see http://go.microsoft.com/fwlink/?LinkID=73091.

    Note
    This installation guide provides instructions for unpacking all global resources except the Data Warehouse.

  • Direct Mailer. Sends personalized or non-personalized mailings to large groups of recipients. This is an optional global resource that you install and configure by using the Microsoft Commerce Server Installation Wizard and Commerce Server Configuration Wizard.

  • Profiles. Creates data sources for storing profile data, and creates and stores profile definitions and properties. Commerce Server installs this resource when you unpack a site.

Site Resources

Commerce Server installs site resources when you unpack a site and create the associated databases. The default site resources that are available when you unpack a Commerce Server 2007 example PuP file, such as the CSharp or StarterSite, are as follows:

  • Inventory. Manages the connection to the Inventory System database that Commerce Server uses to store inventory schema and inventory SKU data. Inventory data is stored in the product catalog site database.

  • Marketing. Manages the connection to the Marketing System and the mailing list management site databases that Commerce Server uses to store data about campaigns, ads, discounts, direct mail, and user lists.

  • Product Catalog. Manages the connection to the product catalog site database that Commerce Server uses to store catalog schema and product data.

  • Transactions. Manages the connection to the Orders System transactions site database that Commerce Server uses to store data such as order numbers, order groups, and baskets.

  • Transaction Config. Manages the connection to the Orders System transactions configuration site database that Commerce Server uses to store data such as region codes, tax rates, order status codes, and shipping methods.

Commerce Server Applications and Web Services

A Commerce Server application is a logical representation of an application in IIS. It appears in both the Commerce Server Manager and IIS console trees. In the IIS console tree, an application is either at the root directory level of the Web site or at a subdirectory level of the Web site. Commerce Server applications are also referred to as Web services.

When you unpack a Commerce Server site, a Commerce Server Web application is created. Customers use their browser to access this application. Such Web applications typically involve purchasing or otherwise ordering products that are browsed online, put in a basket, and ultimately purchased by completing the checkout process.

Commerce Server creates as many as four Web services when you unpack a site. The Commerce Server components you select to install determine the services that it creates. The following is a list of the Web services.

  • Catalog Web Service

  • Marketing Web Service

  • Orders Web Service

  • Profiles Web Service

Commerce Server Web Servers and Web Sites

In Commerce Server, a Web server is a computer on which IIS is installed. The Web server contains the virtual directories, files, and subfolders for a Commerce Site. A Commerce Server deployment can have multiple Web servers that together form a Web farm.

A Web site is an IIS Web site that is running on a specific TCP port number. Examples are the "Default Web site" or "Administration" Web site. By default, these sites are installed with IIS.

Commerce Server Security-Enhanced Configuration Requirements

Commerce Server uses Windows Integrated Security, IIS, Windows Authorization Manager, SQL Server database role assignments, and Windows Component Services to help secure the configuration. The following topics provide an overview of the security elements that you create and associate in a single-computer installation:

Windows Authentication and Windows Integrated Security

Commerce Server supports Windows Authentication to SQL Server. This is also known as Windows Integrated Security. We recommend that you use Windows Authentication when you configure the Commerce Server installation. By using Windows Authentication, Commerce Server uses Windows user accounts to authenticate to SQL Server. Commerce Server sets a tag in the connection string that tells the SQL Server to use Windows Authentication when it checks the security context of the user trying to access a given database.

When you use Windows Authentication, user names and passwords are not stored in the SQL Server connection string, and are not changed when the SQL Server password is reset.

Account, User Group, and Application Pool Requirements

This section summarizes the accounts, user groups, and application pools used in Commerce Server installations. Note the following:

  • Commerce Server 2007 supports only <NetBIOS domain name>\<user> name formats for service accounts and Windows groups.

  • We recommend that you use Active Directory® directory service domain groups and user accounts when you use multiple-computer configurations. This includes SQL Server. Domain groups include Domain Local Groups, Global Groups, and Universal Groups. Domain groups are supported in single-server and in multiple-computer environments. You must manually create all the domain groups and accounts before you configure Commerce Server.

    Note
    Domain Local Groups are supported only if Commerce Server and SQL Server are both joined to the same domain and the user who logs on and configures Commerce Server is also a member of the domain where the Domain Local Groups exist.

  • The user running the Commerce Server configuration must have the following rights:

    • Administrator on the local computer

    • SQL System Administrator rights on the computer that is running SQL Server
General Accounts

The following table lists the accounts that you create or that are created when you install prerequisite software. You must create the <CS Direct Mailer User>, <CS Installer>, <CS Staging User>, CSLOB, and RunTimeUser accounts before you install Commerce Server. Registering ASP.NET 2.0 as the default framework creates the ASPNET account. The SQLSvc, BizTalkAdmin, and BizTalkSvc accounts are examples we created for this document. Post-installation, you create SQL Server Login accounts and associate the user accounts together with Windows user groups.

Account Name Description Windows User Group SQL Server Login Account

<CS Direct Mailer User>

Account of person who manages the Direct Mailer service

not applicable

Not applicable

<CS Installer>

Account of person logged on to install and configure Commerce Server

Administrator, CatalogAdminGroup, MarketingAdminGroup, OrdersAdminGroup, ProfilesAdminGroup

Not applicable

<CS Staging User>

Account of person who manages Commerce Server Staging

not applicable

<CS Staging User>

ASPNET

Account that is used for running the ASP.NET worker process (aspnet_wp.exe)

not applicable

ASPNET

BizTalkAdmin

BizTalk Server Administrator identity

Administrators, BizTalk Server Administrators, BizTalk Server Operators

Not applicable

BizTalkSvc

BizTalk Server service identity

BizTalk Application Users, BizTalk Isolated Host Users, IIS_WPG, SQLServer2005NotificationServicesUser, SSO Administrators

BizTalkSvc

CSLOB

Commerce Server Adapters identity

not applicable

not applicable

RunTimeUser

Anonymous user identity (IIS account for Commerce Server)

IIS_WPG

RunTimeUser

SQLSvc

SQL Server service identity

not applicable

not applicable
Commerce Server Windows Services and Account Assignments

Each Commerce Server Windows service requires definition of a Windows service account. Commerce Server installs the optional CSS, CSHealthMonitor, CSVSSWriter, and DMLService application services when you install Commerce Server. Commerce Server creates the Commerce Server Staging and Direct Mailer Windows user groups during configuration.

The following table summarizes the services, default service names, and default Windows service account names that Commerce Server uses. You create the Windows service accounts before you configure Commerce Server, and you create the SQL Server login accounts after you configure Commerce Server.

Commerce Server Window service Default service name Windows service account SQL Server login account Windows user group

Commerce Server Staging Service

CSS

CSStageSvc

CSStageSvc

CSS_SG, CSS Administrators, CSS Operators

Commerce Server Health Monitoring

CSHealthMonitor

CSHealthMonitorSvc

CSHealthMonitorSvc

not applicable

Commerce Server VSS Writer

CSVSSWriter

<CS Installer>

not applicable

not applicable

Direct Mailer Service

DMLService

CSDMSvc

CSMDSvc

DML_SG
Commerce Server Site and Account and Application Pool Assignments

The following table summarizes the default names for the accounts and application pool that you create when you unpack a Commerce Server site, such as the CSharp site.

Default name Windows service account SQL Server login account Application pool

StarterSite

RunTimeUser

RunTimeUser

StarterSiteAppPool

CSharpSite

RunTimeUser

RunTimeUser

CSharpSiteAppPool
Commerce Server Web Services and Account and Application Pool Assignments

Commerce Server installs the Web services when you unpack the CSharp site, and selects the Web services to install. Each Commerce Server Web service requires definition of a Windows user account, Windows user group, SQL Server login account, and application pool. The following table summarizes the default names this installation guide uses. You create the Windows user accounts before you unpack a site, and you create the SQL Server login accounts and application pools after you unpack the site.

Commerce Server Web service Default name Windows user account Windows user group SQL Server login account Application pool

Catalog

CatalogWebService

CatalogWebSvc

CatalogAdminGroup, IIS_WPG

CatalogWebSvc

CatalogWebSvcAppPool

Marketing

MarketingWebService

MarketingWebSvc

MarketingAdminGroup, IIS_WPG

MarketingWebSvc

MarketingWebSvcAppPool

Orders

OrdersWebService

OrdersWebSvc

OrdersAdminGroup, IIS_WPG

OrdersWebSvc

OrdersWebSvcAppPool

Profiles

ProfilesWebService

ProfilesWebSvc

ProfilesAdminGroup, IIS_WPG

ProfilesWebSvc

ProfilesWebSvcAppPool

For each site that you unpack, we recommend that you create unique Web service account names, SQL Server login account names, Windows user groups, and application pools. You can share application pools, but we do not recommend this action.

Note
When installing and configuring Commerce Server 2007 Developer Edition on Windows XP (32-bit), you cannot create additional application pools. For development, you can use the default application pool.

Authorization Role-Based Access Control

Commerce Server provides several predefined 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. 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. By assigning user accounts or Windows groups to the administrator roles, such as MarketingAdministrator or OrdersAdministrator, these users can perform any operation associated with the corresponding Commerce Server system. For example, the MarketingAdministrator role lets users perform any operation in the Marketing System.

With role-based access control, you specify access control in relation to the organizational structure of your company. You use Windows Authorization Manager to add individual users or user groups to a role. Before you assign business user access to the Authorization Manager 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.

For more information about how to use Windows Authorization Manager to help secure specific business user roles, see http://go.microsoft.com/fwlink/?LinkID=73097.
Web Service Administrator Role Assignments

The following table lists the Web services and their corresponding authorization stores and administrator roles. You must assign each Web service account to its corresponding authorization role.

Authorization Store Role Account Assignments

CatalogAuthorizationStore.xml

Administrator

CatalogWebSvc, <CS Installer>

MarketingAuthorizationStore.xml

MarketingAdministrator

MarketingWebSvc, <CS Installer>

OrdersAuthorizationStore.xml

OrdersAdministrator

OrdersWebSvc, <CS Installer>

ProfilesAuthorizationStore.xml

ProfileAdministrator

ProfilesWebSvc, <CS Installer>

After you assign write permissions to the authorization stores, in order to perform any operation in the Business Management applications, you assign users to the administrator roles for each Web service. By adding <CS Installer> to each administrator role, you can open and use each Business Management application.

BizTalk Adapters Role Assignments

The following table lists the role assignments to which CSLOB, the BizTalk adapters identity, must be added.

Authorization store Role Description

CatalogAuthorizationStore

CatalogAdministrator

Gives the catalog adapter permission to import catalog changes and export catalogs.

CatalogAuthorizationStore

InventoryAdministrator

Gives the inventory adapter permission to import inventory catalog changes and export inventory catalogs.

OrdersAuthorizationStore

OrdersAdapter

Enables the orders adapter to perform all basic functions, such as Update Purchase Order, Save Purchase Order, Accept Basket, Orders Query, and Orders Export.

ProfilesAuthorizationStore

UserObject, ProfileWriter_Adapter

Enables the profiles adapter to update profile objects when using the following operations: Profile Delete, Profile Update, Profile Import, Profile Query, and Profile Export.

Commerce Server Health Monitoring Service Role Assignments

For Commerce Server to monitor the Web services, you must grant the Commerce Server Health Monitoring service permissions to view each service. The following table lists the role assignments you assign to the CSHealthMonitorSvc account.

Authorization store Role

CatalogAuthorizationStore.xml

CatalogViewer

MarketingAuthorizationStore.xml

MarketingViewer

OrdersAuthorizationStore.xml

OrdersViewer

ProfilesAuthorizationStore.xml

ProfileAdministrator

SQL Server Database Instances Created for Commerce Server

The following table summarizes the Commerce Server databases and default database names that Commerce Server and this installation guide use.

Commerce Server SQL database instance Default database name How the database is created

CS Administration

MSCS_Admin

Created by the Commerce Server Configuration Wizard

CS Catalog Scratch

MSCS_CatalogScratch

Created by the Commerce Server Configuration Wizard

Direct Mailer

DirectMailer

Created by the Commerce Server Configuration Wizard

Site Catalog

<site_name>_productcatalog

Created when you unpack the site resource

Site Marketing

<site_name>_marketing

Created when you unpack the site resource

Site Marketing List

<site_name>_marketing_lists

Created when you unpack the site resource

Site Profiles

<site_name>_profiles

Created when you unpack the site resource

Site Transaction Configuration

<site_name>_transactionconfig

Created when you unpack the site resource

Site Transactions

<site_name>_transactions

Created when you unpack the site resource

Commerce Server creates the MSCS_Admin, MSCS_CatalogScratch, and DirectMailer databases when you use the Commerce Server Configuration Wizard. There is only one instance of these databases for the Commerce Server installation. Commerce Server creates the remaining databases when you unpack a site package, for example the CSharp site. For each site resource that you unpack, Commerce Server creates a site-specific resource database.

Commerce Server Service Access to Commerce Server Database Instances

Each Commerce Server application and Web service accesses one or more Commerce Server databases. Service access is restricted based on the user mapping of SQL Server login accounts and database roles. Commerce Server database roles are predefined and listed in SQL Database Account, Database, and Database Role User Mapping.

The following table provides a summary of the databases that each Commerce Server application, Web service, or ASP service accesses.

Service SQL database access

ASPNET

MSCS_Admin

Catalog Web Service

MSCS_Admin, MSCS_CatalogScratch, <site_name>_productcatalog

Commerce Server Direct Mailer

DirectMailer, MSCS_Admin, <site_name>_marketing, <site_name>_Marketing_lists

Commerce Server Health Monitoring

MSCS_Admin

Commerce Server Staging

MSCS_Admin, MSCS_CatalogScratch, <site_name>_marketing, <site_name>_Marketing_lists, <site_name>_productcatalog, <site_name>_profiles, <site_name>_transactionconfig

Commerce Server VSS Writer

MSCS_Admin

Marketing Web Service

MSCS_Admin, <site_name>_Marketing, <site_name>_MarketingLists, <site_name>_ProductCatalog, <site_name>_Profiles

Orders Web Service

MSCS_Admin, MSCS_CatalogScratch, <site_name>_marketing, <site_name>_productcatalog, <site_name>_profiles, <site_name>_transactionconfig, <site_name>_transactions

Profiles Web Service

MSCS_Admin, <site_name>_profiles

<site_name> Service

MSCS_Admin, MSCS_CatalogScratch, <site_name>_marketing, <site_name>_Marketing_lists, <site_name>_productcatalog, <site_name>_profiles, <site_name>_transactionconfig, <site_name>_transactions

User Authentication

Commerce Server 2007 supports three methods for authenticating users:

  • Commerce Server Membership Provider integrates Commerce Server profiles with ASP.NET logon and registration controls.

  • Authentication Manager uses the AuthManager object to identify users and gather information that Commerce Server needs for user authentication.

  • AuthFilter ISAPI filter alters the default behavior of IIS and affects how Commerce Server handles HTTP requests and responses.

We recommend the first method, Commerce Server Membership Provider, for supporting user authentication. Commerce Server supports the AuthManager and AuthFilter methods, but these are obsolete functions in Commerce Server 2007.

Important
If you are upgrading an existing Commerce Server site to use with Commerce Server 2007 and you want to continue to use either AuthManager or AuthFilter, review the information provided in AuthFilter Not Functional After Upgrading Commerce Server.

Task Overview

This section provides an overview of the sequence of tasks to perform after you have prepared the computing environment with the necessary hardware and software prerequisites.

Important
Prior to installing and configuring Commerce Server 2007, review the information in Commerce Server Installation Considerations and Restrictions.

Installation Scenarios

The following table indicates the tasks that you must perform depending on the type of installation you are supporting.

Installation scenario Required tasks (see Task Sequence)

Developer computer

Tasks 1 through 16

System administrator computer

Tasks 1 through 8, 10 through 16

Business user computer

Task 15

System integrator computer

Tasks 15 and 16

Task Sequence

The following table summarizes the tools and sequence of tasks you perform to install and configure Commerce Server. The details for performing each task are provided in later sections. Before you complete these tasks, make sure that you have reviewed the information in Pre-installation Requirements and Procedures and have installed all the prerequisite software.

Use this tool To do this

Computer Management

OR

Active Directory Users and Computers (domain controller)

Task 1: Create User Accounts.

Create the user accounts your Commerce Server installation requires. You must create a user account for each Web service and a RunTimeUser account for guest visitors to access the Commerce Server site. Commerce Server requires additional accounts for some of the optional Commerce Server services.

Commerce Server Installation Wizard (Setup.exe)

Task 2: Install Commerce Server 2007.

The Installation Wizard performs the following actions:

  • Scans the computer for necessary hot fixes and other operating system update dependencies.

  • Presents a report of any missing dependencies and gives the option to install the dependencies from the cabinet (CAB) file included with the product or download an updated set of dependencies from the Internet or intranet.

  • Checks for required components, displays a list of missing components, and presents you with the options of completing the installation and automatically installing the missing components or exiting and manually installing the missing components.

  • Verifies the absence of previous Commerce Server software versions. An uninstall of old versions of Commerce Server is required before you can install Commerce Server 2007.

  • Installs core and optional components and Commerce Server run-time objects to <Commerce Server 2007 Installation Path>. If core components are already installed, the Program Maintenance page displays to support addition, removal, or repair of one or more components.

  • Installs common assemblies into the following location: <drive>:\Program Files\Common Files\Microsoft Shared\Enterprise Servers\Commerce Server.

  • Provides an option to start the Commerce Server Configuration Wizard when the installation process is complete.

    Note
    For instructions about how to install Commerce Server on Windows XP, see http://go.microsoft.com/fwlink/?LinkID=73093. On Windows XP, Commerce Server 2007 runs COM+ applications as an Interactive User. Therefore, a user must be logged on to the computer for the applications to function.

  • Creates a summary .html log file of the main installation activities that contains links to more detailed log files, and creates Unicode text log files that have all installation activities for diagnostic purposes. By default, Commerce Server stores these files in the user profile Temp directory.

Windows Component Wizard

Task 3: (Optional) Enable ASP on the Server Running IIS Where You Will Use the Configuration Wizard.

To configure the Commerce Server Staging Reporting Service virtual directory, you must enable ASP before configuring Commerce Server.

Commerce Server Configuration Wizard

Task 4: Configure Commerce Server 2007.

The Configuration Wizard creates specific global database resources and configures Commerce Server components. The Configuration Wizard also lets you import and export configurations through an XML file. The Configuration Wizard performs the following actions during configuration:

  • Creates the Commerce Server administration database (MSCS_Admin) and sets up the authentication credentials to use to access the MSCS_Admin database.

  • Creates the Commerce Server catalog scratch database (MSCS_CatalogScratch).

  • Creates and sets up the following COM+ applications:

    • Commerce Server Config (for the Administration API).

    • Commerce Server List Manager (for handling marketing lists).

    • Commerce Server Catalog Import Host (for handling catalog import and export).

    • Commerce Server Orders (for running the Commerce Server pipelines and orders transactions).

    • Commerce Server Promocode Generator (for generating promotion codes).

  • Sets up Commerce Server performance counters.

  • Sets up the Widgets virtual directory (for the Commerce Server Profiles System schema administration).

  • (Optional) Sets up and configures the Commerce Server Staging (CSS) Windows service.

    • Assigns the CSS service account you specify, such as CSStageSvc, to the service.

    • Creates the CSS_SG, CSS Administrators, and CSS Operators Windows user groups for staging. The CSS_SG Windows user group has all the necessary permissions to run the Staging Service. Adds the CSS service account to the CSS_SG user group.

    • (Optional) Configures the IIS virtual directory for the Commerce Server Staging Reporting Service.

  • (Optional) Creates the Direct Mailer database and sets up the authentication credentials to access the database.

  • (Optional) Creates and saves an XML configuration file that is named CSConfig.xml in the <Commerce Server 2007 Installation Path>.

  • Creates a Unicode text log of all configuration activities for diagnostic purposes. By default, Commerce Server stores this file in the user profile Temp directory.

Site Packager

Task 5: Unpack the CSharp Site.

Site Packager provides Quick and Custom unpack methods. You can use the Quick unpack method to unpack a Commerce Server site onto a new installation. If you are unpacking a second site package onto the same computer, you must use the Custom unpack method.

Site Packager performs the following operations when you unpack a Commerce Server 2007 site package, such as the CSharp or Starter Site PuP files, by using the Quick unpack method:

  • Creates the site databases for each site resource unpacked and sets up predefined database security roles. Site Packager assigns the default site database names listed in SQL Server Database Instances Created for Commerce Server.

  • Extracts and configures the database connection strings for each site database. All applicable database logon information runs under the account provided.

  • Creates and installs the global resources.

  • Unpacks each IIS application into the IIS default Web site in a virtual directory that matches the application name, such as CatalogWebService. All Commerce Server services run under the Web service accounts you create in Task 1, Create User Accounts. The post-installation configuration process grants these accounts the necessary security permissions on the server and objects in SQL Server.

  • Creates a Unicode text log of all activities for diagnostic purposes. Every time that you use Site Packager, events are written to this log file. The file name is Pup.log. This file is located in the root folder of the drive where you installed Commerce Server 2007.

Windows Explorer, File and Folder Properties Dialog Box

Task 6: Assign Write Permissions.

These tasks enable access to the Catalog Web service and the Business Management applications.

Windows Computer Management

and

Windows Authorization Manager

Task 7: Add Users or Windows Groups to the Authorization Roles.

You add users to the authorization roles so that users can run the Business Management applications. You create Windows groups for different levels of permissions. In this guide, we only have you create Windows groups for the administrator level for each Web service. Users assigned to the Administrator groups have read and write access to all associated Commerce Server system functions.

SQL Server Enterprise Manager (SQL Server 2000)

OR

SQL Server Management Studio (SQL Server 2005)

Task 8: Grant Web Applications and Windows Services Access to the Databases.

Using the SQL Server tool, you create an SQL login account for each Commerce Server Web application and ASP.NET client access. For each login account you create, you grant permissions to the Commerce Server databases based on the predefined database roles. For a table of these roles and their required user mappings, see SQL Database Account, Database, and Database Role User Mapping.

Internet Information Services (IIS) Resource Kit Tools

Task 9: Configure a Temporary SSL Certificate.

For a developer computer, you must configure a temporary SSL certificate to support security on the retail Web site.

Windows IIS Manager

and

Windows Computer Management

Task 10: Assign Permissions to the IIS Worker Process Accounts.

You assign permissions to the IIS worker process accounts by creating and configuring application pools for the Web services, adding worker process accounts to the IIS_WPG group, and assigning the Web service applications to the application pools. You assign the appropriate permissions to the IIS worker process accounts for users to have access to the Web services.

In IIS, you create objects in the configured application pool for the site, and you can configure each application pool to run as a different user. For Commerce Server Config objects to work with IIS, you must add the application pool user name to COM+.

Windows Explorer

Task 11: Restart IIS and Verify Web Services Are Installed.

You must restart IIS before you open the Business Management applications.

Windows Component Services

Task 12: Grant the Marketing Web Service Permissions to Launch and Activate the Direct Mailer Service.

You grant the Marketing Web service launch and activation permissions to the Direct Mailer service. Launch permission is required to start a new COM application. Activation permission is required for a new client to use a COM application, even if the application has already been started.

Windows Authorization Manager

and

Windows Services

Task 13: (Optional) Configure and Start the Commerce Server Health Monitoring Service.

If you want to monitor the Commerce Server Web services by using the Commerce Server Health Monitoring service, you must assign the service account to the viewer role for the associated authorization stores and start the service.

Windows Services

Task 14: (Optional) Configure and Start the Commerce Server VSS Writer.

If you want to use the Volume Copy Shadow Writer service to back up and restore Commerce Server databases, you must configure and start the service.

Commerce Server Installation Wizard (Setup.exe)

Task 15: Install Commerce Server Business Management Applications.

Install the Business Management applications on all computers. For business users who will have to access one or more of the Commerce Server systems, install the Business Management applications on their computers.

Add the user account of each user who will access the Business Management application to the corresponding administrator Windows user groups.

Commerce Server Installation Wizard (Setup.exe)

Task 16: (Optional) Install Commerce Server Adapters for BizTalk Server.

If you want to access line-of-business integration and data exchange functions:

Pre-installation Requirements and Procedures

Before you install and configure Commerce Server 2007, follow these steps:

  1. Review Hardware Requirements.

  2. Review Software Requirements.

  3. Review Commerce Server Installation Considerations and Restrictions.

  4. Review Upgrade Requirements, if you plan to upgrade from Commerce Server 2000 or 2002 to Commerce Server 2007.

  5. Install Prerequisite Software.

  6. Create User Accounts.

Hardware Requirements

The following table shows the minimum hardware requirements for installing Commerce Server 2007 onto a single computer that is running Windows Server 2003 with SP2, Windows Server 2003 R2 with SP2, or Windows XP.

Processor

Single 1.0 gigahertz (GHz) or faster (Dual 2.0 GHz recommended)

RAM

1024 MB

Storage

9.0 gigabytes (GB)

External drives

CD drive or DVD drive

Network adapters

1 10 MBps or larger bandwidth

Monitor

Microsoft Windows Server 2003 compatible VGA or higher-resolution monitor
Note
For more information about hardware requirements for specific deployment scenarios, see http://go.microsoft.com/fwlink/?LinkID=73099.

The following table shows the minimum hardware requirements for installing Commerce Server 2007 onto an installation of a single computer that is running Windows Vista Business, Ultimate, or Enterprise Edition.

Processor

Single 1.0 gigahertz (GHz) or faster (Dual 2.0 GHz recommended)

System Memory

1 GB

Storage

40 GB hard disk

External drives

CD drive or DVD drive

Network adapters

1 10 MBps or larger bandwidth

Monitor

Microsoft Windows Server 2003 compatible VGA or higher-resolution monitor

Software Requirements

The following sections list the prerequisite software you must install on the server that will run Commerce Server 2007:

Microsoft Operating System and Web Server Software Requirements

The following table lists the supported Microsoft operating systems and Web server software that you must install on the server that will run Commerce Server 2007. Note the following:

  • Microsoft Windows Server 2003 Web Edition supports all Commerce Server features except for the Data Warehouse and Analysis, and requires that you install Microsoft® SQL Server™ on a separate server.

  • Windows XP (32-bit) and (64-bit) are supported for Commerce Server 2007 Developer Edition. For both versions of Windows XP there is an upper limit of 10 incoming connections enabled. For more information about the incoming connection limitation, see http://go.microsoft.com/fwlink/?LinkID=73842.

    Windows XP (32-bit) does not support creating the applications pools that are required to support Commerce Server Web applications. For development, you can use the default application pool. You can address this issue by adding an identity tag to your Web.config file to set a user name and password for the ASP.NET worker process. You can then use the Aspnet_setreg.exe tool to encrypt the user name and password in the registry. This will enable your Web service and commerce site to authenticate correctly. For more information about how to set the identity tag, see http://go.microsoft.com/fwlink/?LinkID=17538. For more information about how to use the Aspnet_setreg.exe tool, see http://go.microsoft.com/fwlink/?LinkID=16728.

    Windows XP (64-bit) does support creating application pools.

  • Windows Server 2003 Datacenter and Itanium Editions are not supported.

  • Windows Vista Business, Ultimate, or Enterprise Editions are supported for Commerce Server 2007 Developer Edition or for the business user computer.

  • Windows Vista Home Edition and Home Basic Edition are not supported.

  • Windows Vista does not support the Data Warehouse and analytics, or Commerce Server Staging.

  • Always apply the latest critical Windows updates for the operating system you select.

For a comparison of features in each edition of the Windows Server 2003 family, see http://go.microsoft.com/fwlink/?LinkID=68138. For information about software requirements that address all the computer scenarios for a Commerce Server enterprise deployment, see http://go.microsoft.com/fwlink/?LinkID=73100.

Software Developer or system administrator computer Commerce Server 2007 Web server Business user computer System integrator computer

Microsoft Windows operating systems (with critical updates)

Microsoft Windows Server 2003 Standard Edition with SP2

Yes

Yes

Yes

Yes

Microsoft Windows Server 2003 Standard x64 Edition with SP2

Yes

Yes

Yes

Yes

Microsoft Windows Server 2003 Enterprise Edition with SP2

Yes

Yes

Yes

Yes

Microsoft Windows Server 2003 Enterprise x64 Edition with SP2

Yes

Yes

Yes

Yes

Microsoft Windows Server 2003 Web Edition with SP2

Yes (does not support Data Warehouse and Analysis Reporting and requires SQL Server to be installed on a separate server)

Yes

Yes

Yes

Microsoft Windows Server 2003 Standard Edition R2 with SP2

Yes

Yes

Yes

Yes

Microsoft Windows Server 2003 Standard x64 Edition R2 with SP2

Yes

Yes

Yes

Yes

Microsoft Windows Server 2003 Enterprise Edition R2 with SP2

Yes

Yes

Yes

Yes

Microsoft Windows Server 2003 Enterprise x64 Edition R2 with SP2

Yes

Yes

Yes

Yes

Microsoft Windows XP Professional Edition with XP COM+ Hotfix Rollup Package 13 with SP2

Yes (Commerce Server 2007 SP1 Developer Edition only. Review the previous notes about limitations with Windows XP and Commerce Server deployment requirements.)

No

Yes

No

Microsoft Windows XP2 Professional x64 Edition with XP COM+ Hotifx Rollup Package 13 with SP2

Yes (Commerce Server 2007 SP1 Developer Edition only. Review the previous notes about limitations with Windows XP and Commerce Server deployment requirements.)

No

Yes

No

Windows Vista Business

Yes (Commerce Server 2007 SP1 Developer Edition only)

No

Yes

No

Windows Vista Enterprise

Yes (Commerce Server 2007 SP1 Developer Edition only)

No

Yes

No

Windows Vista Ultimate

Yes (Commerce Server 2007 SP1 Developer Edition only)

No

Yes

No

Other:

Internet Information Services (IIS)

Yes

Yes

Yes

Yes

Internet Information Services 7.0 with IIS 6.0 Compatibility enabled

Yes

Yes

Yes

Yes
Important
Always apply the latest critical Windows updates for the operating system you select.

Additional Prerequisite Software Requirements

The following table lists additional prerequisite software you must install on the server(s) that will run Commerce Server 2007.

Software Developer or system administrator computer Commerce Server 2007 Web servers Business user computer System integrator computer

Microsoft SQL Server 2000 Enterprise Edition with SP4

OR

Microsoft SQL Server 2005 with SP2

OR

Microsoft SQL Server 2005 Express Advanced Services Edition with SP2

Yes

No

No

Yes

Microsoft SQL Server 2000 Analysis Services with SP4

OR

Microsoft SQL Server 2005 Analysis Services with SP2

Yes (for Data Warehouse and Analysis Reporting)

No

No

Yes

SQL Server 2000 Distributed Transformation Services (DTS) Designer Components

Yes (required for Data Warehouse DTS tasks)

No

No

No

Microsoft Visual Studio® 2005 with SP1

Important
Visual Studio 2005 Premier Partner Edition installs as part of SQL Server 2005. However, it does not meet the Commerce Server 2007 software prerequisites. Therefore, you cannot use some features of Commerce Server 2007 such as the Project Creation Wizard unless you install one of the stand-alone versions of Visual Studio 2005.

Yes (for developing Web applications)

No

No

Yes (for developing BizTalk applications)

Microsoft .NET Framework 2.0 with KB913393 update

OR

Microsoft .NET Framework 3.0

Yes

Yes

Yes

Yes

Microsoft ADO.NET Hotfix

Yes

Yes

Yes

No

Register ASP.NET 2.0 as the default framework

Yes

Yes

Yes

No

Microsoft BizTalk® Server 2006

Optional (required to use Commerce Server Adapters for Microsoft BizTalk Server)

No

No

Yes

Microsoft Operations Manager (MOM) 2005 with SP1

Optional

No

No

No

Microsoft Commerce Server 2007 Management Object Model (MOM) Pack

Optional

No

No

No

For information about how to install the additional prerequisite software, see Install Prerequisite Software.

Commerce Server Installation Considerations and Restrictions

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

  • 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.

  • Do not install Commerce Server 2007 on a domain controller. Commerce Server 2007 does not support installation on a domain controller.

  • You can install Commerce Server 2007 and BizTalk Server 2006 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 2007 before you install and configure BizTalk Server 2006. Alternatively, install and configure BizTalk Server 2006 before you install and configure Commerce Server 2007.

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

  • The supported configuration for Commerce Server 2007 includes Windows Server 2003 and SQL Server installations of the same languages. Commerce Server 2007 supports Unicode, and you can customize regional settings for your specific implementation.

  • If you install Commerce Server 2007 on a computer where either Microsoft Windows SharePoint® Services or Microsoft Office SharePoint Portal Server 2003 is installed, you must configure SharePoint Services security settings so that they do not interfere with the execution of the Commerce Server application. The correct configuration will prevent SharePoint Services from intercepting incoming requests to IIS where the Commerce Server Site is run. For more information, see http://go.microsoft.com/fwlink/?LinkID=68629.

  • Do not install Commerce Server 2007 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 2007.

    To uninstall an earlier version of Commerce Server, you must first uninstall any Commerce Server Service Packs or Commerce Server 2002 Feature Pack 1. See the documentation for the version that you are uninstalling.

    Note
    If you must uninstall Commerce Server, see Uninstall Commerce Server.

  • To upgrade your Commerce Server 2007 edition, such as from Standard to Enterprise, you must first uninstall the existing Commerce Server 2007 installation, and then reinstall the version of Commerce Server 2007 that you want.

  • If you are upgrading from an earlier version of Commerce Server, see Upgrade Requirements.

Install Prerequisite Software

After you install the operating system and critical updates, install the prerequisite software in the order indicated in the following procedure. For detailed installation instructions, see the documentation for the software you want to install. For more information about supported operating systems and other prerequisite software, see Software Requirements.

Important
Some prerequisite software may have additional software requirements for their installation. Refer to the installation guides for each required software component for more information and install those components as needed.

Optional tasks provide software support for one or two Commerce Server features and are not required to support Web site development. You can perform optional tasks later.

Note
If you plan to install Commerce Server 2007 Developer Edition on the 32-bit edition of Windows XP Professional, you must take the additional steps regarding support for application pools described in Microsoft Operating System and Web Server Software Requirements.

To install prerequisite software

  1. Install IIS. If you did not select IIS to install during installation, you can install it now by using Add/Remove Windows Components in Add or Remove Programs in Control Panel. On Windows Server 2003, IIS is a subcomponent of Application Server. On Windows Vista, IIS is listed in Control Panel under the option Turn Windows features on or off.

    If you plan to use the Commerce Server Staging (CSS) Reporting Service, you must add ASP (Active Server Pages). This is a subcomponent of World Wide Web Service under IIS under the Add/Remove Windows Components in Control Panel. ASP is not available on Windows XP Professional. The CSS Reporting Service requires ASP to display reports.

    Note
    CSS is not supported on either Windows XP or Windows Vista editions.

    Note
    To run the Reporting Service for CSS on 64-bit versions of Windows Server 2003, you must enable 32-bit support for IIS on 64-bit versions of Windows Server 2003. For more information, see http://go.microsoft.com/fwlink/?LinkID=66527.

  2. Install 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.

  3. Install Windows XP COM+ Hotfix Rollup Package 13 if you installed Microsoft Windows XP Professional with SP2.

    For developers running Commerce Server 2007 Developer Edition on Windows XP, this rollup package provides a fix to COM+ that lets you unpack sites correctly. For information about this rollup package, see http://go.microsoft.com/fwlink/?LinkID=65099.

  4. Install and configure the appropriate version and edition of SQL Server. For more information about supported versions and editions of SQL Server, see Additional Prerequisite Software Requirements.

    SQL Server provides the underlying database services for Commerce Server. For information about how to install SQL Server 2000, see http://go.microsoft.com/fwlink/?LinkID=62410. For information about how to install SQL Server 2005, see http://go.microsoft.com/fwlink/?LinkID=62409. For information about how to install SQL Server 2005 SP2, see http://go.microsoft.com/fwlink/?LinkID=93378.

    For information about how to install SQL Server 2005 Express SP2 with Advanced Services, see http://go.microsoft.com/fwlink/?LinkID=63922.

    Important
    Commerce Server databases require collation settings that are not case-sensitive. If you have configured SQL Server so that databases are created by using case-sensitive collations, you will have to take extra steps to make sure that the Commerce Server databases are not created by using your default collation settings. For example, you could pre-create the Commerce Server databases, and then use a command such as the following to change the default collation settings for these databases before you run the Commerce Server Setup program:

    ALTER DATABASE <database_name> COLLATE SQL_Latin1_General_CP1_CI_AS

    During the SQL Server installation process, select the default installation options including selection of Windows Authentication.

  5. (Optional) Install Microsoft SQL Server Analysis Services and SQL Server Reporting Services. The Commerce Server Data Warehouse uses this software to access the OLAP database and for analysis reporting.

    Note
    Commerce Server 2007 Data Warehouse does not support SQL or SQL Analysis Services if they are installed on a named instance.

    1. Install the version of SQL Server Analysis Services that is appropriate for your operating system:

      For SQL Server 2000, install SQL Server 2000 Analysis Services. For information, see http://go.microsoft.com/fwlink/?LinkID=72010.

      For SQL Server 2005, install SQL Server 2005 Analysis Services. For information, see http://go.microsoft.com/fwlink/?LinkID=72011.

    2. Install and configure the version of SQL Server Reporting Services that is appropriate for your operating system:

      For SQL Server 2000, install SQL Server 2000 Reporting Services. For information, see http://go.microsoft.com/fwlink/?LinkID=72012.

      For SQL Server 2005, install SQL Server 2005 Reporting Services. For information, see http://go.microsoft.com/fwlink/?LinkID=72013.

    Note
    SQL Server 2005 Express SP2 with Advanced Services does not support the Data Warehouse or analytics.

  6. (Optional) If you are using the Data Warehouse in Commerce Server 2007 with SQL Server 2005, install SQL Server 2000 DTS Designer Components. You use this software to create Distributed Transformation Services (DTS) tasks. You can download the Microsoft SQL Server 2000 DTS Designer Components from http://go.microsoft.com/fwlink/?LinkID=65308.

  7. If you want to develop Web applications by using Commerce Server on this computer, install Microsoft Visual Studio 2005 SP1. You must only install Visual Studio on the computer where you perform Web site development. Installation of Visual Studio 2005 includes installation of the .NET Framework.

    For information about how to install Visual Studio 2005 SP1, see http://go.microsoft.com/fwlink/?LinkID=75109. For information about how to install Visual Studio 2005 SP1 Update for Windows Vista, see http://go.microsoft.com/fwlink/?LinkID=82675.

    Important
    Installation of SQL Server 2005 includes installation of Visual Studio 2005 Premier Partner Edition. However, Visual Studio 2005 Premier Partner Edition does not meet the Commerce Server 2007 software prerequisites for development. Therefore, you cannot use some features of Commerce Server 2007, such as the Project Creation Wizard, unless you install one of the stand-alone versions of Visual Studio 2005.

  8. If you did not install Microsoft Visual Studio 2005, you must install Microsoft .NET Framework.

    Note
    On Windows Vista, Microsoft .NET 3.0 Framework is a Windows Vista feature that is switched on automatically when you install Windows Vista. You do not have to turn Microsoft .NET 3.0 on or install it if you are using Windows Vista as your operating system. Because .NET 3.0 is a superset of .NET 2.0, you also do not have to install or turn on .NET 2.0 if you are using Windows Vista.

    The .NET Framework enables you to deploy and run Web-based applications and Web services. To install Microsoft .NET Framework 2.0, see http://go.microsoft.com/fwlink/?LinkID=56645.

  9. Register ASP.NET 2.0 as the default framework.

    All Commerce Server installations require ASP.NET 2.0 registration. At a command prompt, move to the %windir%\Microsoft.NET\Framework\v2.0.50727 folder and run the following command:

    aspnet_regiis.exe -i

    When the command finishes successfully, the Command Prompt window displays "Finished installing ASP.NET <2.0.50727>."

  10. If you installed Microsoft .NET 2.0, you must install the Microsoft .NET Framework 2.0 update that is described in the Knowledge Base article 913393. To obtain the hotfix file that is named KB913393.exe, download the prerequisite CAB file that is appropriate for your operating system. The CAB file contains the following software:

    • Dotnetfx.exe / netfx64.exe - (.NET Framework 2.0, 32/64 bit)

    • DExplore.exe -  (Document Explorer 2005) 

    • ASP.NET Fix (KB913393)

    Note
    If you do not install this hotfix, the Commerce Server installation program will detect this and prompt you to install the hotfix that is included in the prerequisite CAB file.

    The locations for the CAB files are as follows:

    Windows Server 2003 32 bit DE: http://go.microsoft.com/fwlink/?LinkID=63719

    Windows Server 2003 32 bit EN: http://go.microsoft.com/fwlink/?LinkID=63706

    Windows Server 2003 32 bit FR: http://go.microsoft.com/fwlink/?LinkID=63721

    Windows Server 2003 32 bit JA: http://go.microsoft.com/fwlink/?LinkID=63727

    Windows Server 2003 x64 DE: http://go.microsoft.com/fwlink/?LinkID=63729

    Windows Server 2003 x64 EN: http://go.microsoft.com/fwlink/?LinkID=63730

    Windows Server 2003 x64 FR: http://go.microsoft.com/fwlink/?LinkID=63731

    Windows Server 2003 x64 JA: http://go.microsoft.com/fwlink/?LinkID=63732

    Windows XP 32 bit DE: http://go.microsoft.com/fwlink/?LinkID=63733

    Windows XP 32 bit EN: http://go.microsoft.com/fwlink/?LinkID=63734

    Windows XP 32 bit FR: http://go.microsoft.com/fwlink/?LinkID=63735

    Windows XP 32 bit JA: http://go.microsoft.com/fwlink/?LinkID=63736

    Windows XP x64 DE: http://go.microsoft.com/fwlink/?LinkID=63737

    Windows XP x64 EN: http://go.microsoft.com/fwlink/?LinkID=63739

    Windows XP x64 FR: http://go.microsoft.com/fwlink/?LinkID=63742

    Windows XP x64 JA: http://go.microsoft.com/fwlink/?LinkID=63745
    Note
    If Visual Studio 2005 is installed on your computer, you may receive one or more error messages when you install these CAB files. You can safely ignore these error messages. The messages indicate that a software component that is contained in the CAB file is already installed.

  11. Install Microsoft ADO.NET Hotfix. To download this hotfix, see http://go.microsoft.com/fwlink/?LinkID=68140.

    This hotfix addresses the following exception that may occur when you use the Commerce Server OrdersWebService or CatalogWebService:

    "System.Data.SqlClient.SqlException: New request is not allowed to start because it should come with valid transaction descriptor."

    The cause of this exception is the premature termination of a Distributed Transaction Coordinator (DTC) transaction. For example, when a checkout fails or an item is out of stock, the parent connection of the transactions become unusable. Because Commerce Server always has SQL connection pooling enabled, the unusable connection remains active until the worker process restarts. In the meantime, any other user assigned to the connection cannot use the site. When a sufficient number of failed checkouts occur, all connections in the connection pool are used and no additional users can access the site.

  12. (Optional) Install and configure Microsoft BizTalk Server 2006 if you want to use the Commerce Server Adapters for Microsoft BizTalk Server. For information about how to install and configure BizTalk Server 2006, see http://go.microsoft.com/fwlink/?LinkID=46922.

  13. (Optional) Install and configure Microsoft Operations Manager (MOM) 2005 SP1.

    The MOM server components include the MOM database, Management server, and user interfaces: the MOM Administrator console and the MOM Operator console. For the latest information about how to install and configure MOM 2005 SP1, see http://go.microsoft.com/fwlink/?LinkID=89220.

Create User Accounts

Before you install Commerce Server, you must create several accounts to run the Commerce Server services. You create these accounts on a domain controller that handles security and authentication for the computer on which you are installing Commerce Server. If you cannot create these accounts as domain accounts, you can create them as local accounts on the Commerce Server computer.

Note
If your development environment requires that you install and run SQL Server locally, use a local account for these service accounts. If your development environment involves multiple developer computers that reference a shared, remote SQL Server, use a domain account for the service accounts.

For additional guidance about how to create service accounts for ASP.NET 2.0 applications, see http://go.microsoft.com/fwlink/?LinkID=67382.

Create the user accounts listed in the following table. Make sure that you note the user name and password that you create for each account, as you will have to provide them during post-configuration procedures.

Important
These account names are examples used in instructions later in this document. You should specify account names that are appropriate for your particular environment, and substitute the names that you have chosen for the ones given in the following instructions.

Account name Description

<CS Installer>

Account of person who installs Commerce Server.

<CS Staging User>

Account of person who manages Commerce Server Staging.

CatalogWebSvc

Account for running the Catalog Web service.

CSDMSvc

Account for running the Commerce Server Direct Mailer service.

CSHealthMonitorSvc

(Optional) Account for running the Commerce Server Health Monitoring service. Create this account only if you plan to install the Commerce Server Health Monitoring service.

CSLOB

(Optional) Account for running the Commerce Server adapters. Create this account only if you plan to install the Commerce Server Adapters for Microsoft BizTalk Server.

CSStageSvc

Account for running the Commerce Server Staging service.

MarketingWebSvc

Account for running the Marketing Web service.

OrdersWebSvc

Account for running the Orders Web service.

ProfilesWebSvc

Account for running the Profiles Web service.

RunTimeUser

IIS account for accessing a Commerce Server site or application.

How to Create a Local Account on the Commerce Server Computer

The following steps show you how to create a local account on the Commerce Server computer.

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 the user name.

    Full name

    Optionally, type a full user name for this account.

    Description

    Optionally, type a description for this account.

    Password

    Type a password for the user.

    Confirm password

    Confirm the password for the 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.

  6. Repeat steps 4 and 5 for the other required accounts.

  7. Click Close.

How to Create a Domain Account on an Active Directory Domain Controller

The following steps show you how to create a domain account on an Active Directory domain controller.

To create a domain account

  1. Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.

  2. In Active Directory Users and Computers window, expand <domain name>.com

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

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

    Use this To do this

    First name

    Type a first name for the account.

    User logon name

    Type the appropriate account name from the previous list, for example, RunTimeUser.

  5. Click Next.

  6. In the Password box, type a password for the account, and then in the Confirm password box, type the password again.

  7. Select User cannot change password and Password never expires, and then click Next.

  8. Click Finish.

  9. Repeat steps 3 through 7 for all remaining accounts.

Install Commerce Server 2007

You can install Commerce Server 2007 by using the Installation Wizard or by using the Setup.exe command syntax. The Installation Wizard provides a graphical user interface that guides you through each installation decision, and is the preferred method for most users. The Setup.exe command syntax supports unattended and remote installations. You run this command at the command prompt. You can run it interactively or you can reference a file that contains the installation options. For information about how to use the command syntax, see Unattended Installation Command Syntax Reference.

Before you install Commerce Server 2007, note the following:

  • Make sure that you have installed all the Commerce Server software prerequisites listed in Software Requirements.

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

  • Close all other applications before you continue.

The following steps describe how to install Commerce Server 2007 and its core components. For information about how to install Commerce Server Business Management applications or Commerce Server Adapters for Microsoft BizTalk Server, see Post-Configuration Procedures.

To install Commerce Server by using the Installation Wizard

  1. Insert the Microsoft Commerce Server 2007 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 Start page, under Install, click Microsoft Commerce Server 2007.

    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, read the terms of the license agreement. If you accept them, select Yes. I accept the terms of the license agreement, 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 2007, and then click Next to install the default set of Commerce Server 2007 components.

    Or, you can change the default set of installed components by changing the selection for the following components:

    • Commerce Server 2007. (Required) Installs the core Commerce Server components including the Catalog System, Marketing System, Orders System, Profiles System, Commerce Server Manager, product documentation that includes user interface (F1) help, software development kit (SDK), and the Commerce Server client tools.

    • Direct Mailer. (Optional) Installs the Commerce Server Direct Mailer service and components.

    • Project Creation Wizard. (Required for developers) Installs the Project Creation Wizard, a developer tool that you use in Microsoft Visual Studio 2005 to make it easier to create Commerce Server Web projects. To install the Project Creation Wizard, you must have previously installed Visual Studio 2005.

    • Staging. (Optional) Installs the Commerce Server Staging (CSS) components that include the deployment engine and the CSS service. You use CSS to stage your Web site content and business data from one environment to another, such as from a test environment to the production environment.

    • Health Monitoring Service. (Optional) Installs the Health Monitoring Service that lets you monitor Commerce Server Web services by using Microsoft Operations Manager (MOM) 2005. To use the Health Monitoring Service, you must install MOM 2005 SP1, the Commerce Server 2007 MOM Pack that is available as a separate download, and the Health Monitoring Service component on at least one of the servers in your Commerce Server deployment.

    • Volume Shadow Copy Writer Service. (Optional) Installs the Volume Shadow Copy Writer Service that supports back up and restore operations of Commerce Server databases.

  7. Based on the components that 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. For links to the CAB files, see F1 Help.

  8. On the Summary page, verify that the components that you want to install are correct.

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

  9. Click Install. The Installation Progress page appears that states that the Setup program is installing the selected program features.

  10. On the Installation Completed page, click Logfile to review the list of events for the installation.

  11. Select the Launch the Commerce Server Configuration Wizard box, and then click Finish.

    Note
    If you are installing Commerce Server 2007 Developer Edition, click to clear the Launch the Commerce Server Configuration Wizard box, and then click Finish. You will configure Commerce Server 2007 after you have installed the business management applications.

Configure Commerce Server 2007

After you install Commerce Server 2007, you use the Commerce Server Configuration Wizard to create specific database resources and configure several Commerce Server components. You enter the login credentials for the Commerce Server Direct Mailer Service, Commerce Server Staging, and the Administration database. To configure the Commerce Server Staging Reporting Service, you must enable ASP on the IIS Web server where you run the Commerce Server Configuration Wizard.

Follow these procedures to configure Commerce Server:

Enable ASP on the Server Running IIS Where You Will Use the Configuration Wizard

Follow this procedure to enable ASP on the server where you will use the Configuration Wizard.

Note
To configure the Commerce Server Staging Reporting Service virtual directory correctly, you must follow this procedure. Skip this procedure if you have not installed the Staging service or are not using the Commerce Server Staging Reporting Service virtual directory on the server where you run the Configuration Wizard.

To enable Active Server Pages (ASP) on Windows Server 2003

  1. Click Start and then click Control Panel.

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

  3. In the Add or Remove Programs window, click Add/Remove Windows Components.

  4. In the Windows Components window, click Application Server, and then click Details.

  5. In the Application Server window, click Internet Information Services (IIS), and then click Details.

  6. In the Internet Information Services (IIS) window, click World Wide Web Service, and then click Details.

  7. In the World Wide Web Service window, click the check box next to Active Server Pages, and then click OK.

  8. Click OK to close the Internet Information Services (IIS) window.

  9. Click OK to close the Application Server window.

  10. In the Windows Components window, click Next.

  11. In the Completing the Windows Components Wizard window, click Finish.

Run the Commerce Server Configuration Wizard

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

Note
Make sure that SQL Server is running before you start the Commerce Server Configuration Wizard.

To run Commerce Server Configuration Wizard

  1. Click Start, point to Programs, point to Microsoft Commerce Server 2007, point to Tools, and then click Configuration Wizard.

    Note
    This step is not required if, on the final page of the Commerce Server Installation Wizard, you elected to start the Commerce Server Configuration Wizard.

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

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

    Use this To do this

    SQL Server

    Accept the default computer name, or if it is appropriate, type another computer name.

    This specifies the computer where the Commerce Server databases will be created. This server must have SQL Server installed and running.

    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 Server Authentication in a Commerce Server deployment. We do not recommend that you use this option.

    Login Name

    If you have chosen to use SQL Server authentication, type the SQL Server logon name for the computer that is running SQL Server.

    Password

    If you have chosen to use SQL Server authentication, type the SQL Server password for the computer that is running SQL Server.

    Test

    Click to test the connection to the Administration database.

  5. Click Next.

  6. If you have not chosen to install the Commerce Server Staging service, go to step 7. Otherwise, on the Staging Service page, select Create an IIS Virtual Root for 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 <domain or computer name>\CSStageSvc for the Staging Service account, or click Browse to open the Select User dialog box to select the account.

    Note
    As appropriate, substitute the user name for the account you created in Create User Accounts for "CSStageSvc."

    Password

    Type the corresponding password.

    Configuring the Staging Service creates the CSS_SG Windows user group together with all the necessary permissions to run the Staging Service; adds the CSStageSvc service account to the CSS_SG group; creates the CSS Administrators and CSS Operators Windows user groups for staging; and configures the IIS virtual directory for the Commerce Server Staging Reporting service.

  7. Click Next.

  8. If you have not chosen to install the Commerce Server Direct Mailer, go to step 11. Otherwise, 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 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 logon name for the computer that is running SQL Server.

    Password

    Type the SQL Server password for the computer that is running SQL Server.

    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 <domain or computer name>\CSDMSvc for the Direct Mailer Service account, or click Browse to open the Select User dialog box to select the account.

    Note
    As appropriate, substitute the name for the Direct Mailer service account you created in Create User Accounts for " CSDMSvc."

    Password

    Type the corresponding password.

    Configuring the Direct Mailer Service creates the DML_SG Windows user group that has the necessary permissions to run the Direct Mailer Service, and adds the CSDMSvc account to this group.

  11. Click Next.

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

    Note
    To save the configuration XML file, click Save. You can later use the configuration settings saved in this XML file by running the Configuration Wizard and selecting Load on the Welcome to the Microsoft Commerce Server Configuration Wizard page.

    Saved files do not contain security sensitive information such as passwords. However, users can edit saved XML files and insert password information that will be available when the file is loaded in the future.

  13. Click Next to configure the components.

  14. On the Configuration Completed page, click Logfile to view detail information about the completed configuration. Optionally, click Deployment Roadmap to access the Help topics to guide you through the steps of deploying Commerce Server.

  15. Click Finish to complete the Configuration Wizard.

Unpack the CSharp Site

The CSharp site PuP package (CSharp.pup) includes the Commerce Server 2007 resources, Web services, and application framework that you must have to initiate Web site development. Before you unpack these files, 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 that you created during the unpacking process. You must delete the databases manually by using SQL Server.

Follow these steps to unpack the CSharp site package file.

To unpack the CSharp site

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

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

  3. On the Unpack page, accept the default Quick unpack option, and then click Next.

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

    Use this To do this

    Site name

    Accept CSharpSite as the name of the Web site, or type a different name.

    IIS Web site

    Accept Default Web Site as the IIS Web site.

    SQL Server Computer

    Accept the default name of the computer that is running SQL Server, or if it is appropriate, type a different name for the computer that is running SQL Server.

    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 you connect to the databases.

    Note
    We do not recommend this configuration.

    SQL Server Login Name

    If you chose to use a specific user name, type the SQL Server logon name for the databases.

    SQL Server Login Password

    If you chose to use a specific user name, type the SQL Server logon 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 View Log File to review the list of events in the Site Packager log file. Then, click Finish.

Note
Unpacking the CSharp site by using the Quick Unpack method unpacks the CSAuthentication global resource. Commerce Server uses this resource to configure the authentication and identification method for your Commerce Server site when you use the AuthManager and AuthFilter methods. These methods are deprecated in Commerce Server 2007. We recommend that you use the Commerce Server membership provider method for authenticating users. For more information about how to implement authentication, see http://go.microsoft.com/fwlink/?LinkID=73090.

Post-Configuration Procedures

After you configure Commerce Server, follow these steps one time for each developer or system administrator computer that you are configuring to support Commerce Server. You must follow these post-configuration steps in the order listed.

  1. Assign Write Permissions.

  2. Add Users or Windows Groups to the Authorization Roles.

  3. Grant Web Applications and Windows Services Access to the Databases.

  4. (Optional) Configure a Temporary SSL Certificate.

  5. Assign Permissions to the IIS Worker Process Accounts.

  6. Restart IIS and Verify Installation of Web Services.

  7. Grant the Marketing Web Service Permissions to Launch and Activate the Direct Mailer Service.

  8. (Optional) Configure and Start the Commerce Server Health Monitoring Service.

  9. (Optional) Configure and Start the Commerce Server VSS Writer.

  10. Install Commerce Server Business Management Applications.

  11. (Optional) Install Commerce Server Adapters for BizTalk Server.

Assign Write Permissions

Follow these steps to assign write permissions to the Catalog Web service, the Temporary ASP.NET folder, and the Windows Temporary folder. You assign write permissions for the RunTimeUser and all Web service accounts that you created in the Create User Accounts section. You will be unable to run the Business Management applications that are hosted by the Business Management Web services if you omit these steps.

To assign write permissions

  1. Assign write permissions to the catalog authorization role:

    1. In Windows Explorer, move to the directory where you installed the catalog Web service, for example, <drive:>\Inetpub\Wwwroot\CatalogWebService\.

    2. In the <Catalog Web service name> folder, right-click the XML file 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 <domain or computer name>\CatalogWebSvc, and then click OK.

      Note
      As appropriate, substitute the user name for the account you created in Create User Accounts for "CatalogWebSvc".

    5. In the CatalogAuthorizationStore.xml Properties dialog box, in the Group or user names box, select the CatalogWebSvc account.

    6. In the Permissions for CatalogWebSvc box, select Write in the Allow column (Read & Execute and Read should already be selected in the Allow column), and then click OK.

  2. Assign write permissions to the to the Temporary ASP.NET folder:

    1. In Windows Explorer, move to the <drive:>\Windows\Microsoft.NET\Framework\v2.0.50727 (or <drive:>\WinNT\Microsoft.NET\Framework\v2.0.50727, whichever is appropriate) folder.

    2. Right-click Temporary ASP.NET Files, 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 <domain or computer name>\RunTimeUser, and then click OK.

      Note
      As appropriate, substitute the user name for the account you created in Create User Accounts for RunTimeUser.

    5. In the Temporary ASP.NET Files Properties dialog box, in the Groups or user names box, select the RunTimeUser account.

    6. In the Permissions for RunTimeUser box, select Write in the Allow column (Read & Execute and Read should already be selected in the Allow column), and then click OK.

    7. In the Security dialog box, click Yes.

    8. Repeat steps 2c through 2g for CatalogWebSvc, MarketingWebSvc, OrdersWebSvc and ProfilesWebSvc accounts.

  3. Assign write permissions to the Windows Temporary folder:

    1. In Windows Explorer, move to the <drive:>\Windows (or <drive:>\WinNT, whichever is appropriate) folder.

    2. 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 <domain or computer name>\RunTimeUser, and then click OK.

      Note
      As appropriate, substitute the user name for the account you created in Create User Accounts for RunTimeUser.

    5. In the Temp Properties dialog box, in the Groups or user names box, select the RunTimeUser account.

    6. In the Permissions for RunTimeUser box, select Write in the Allow column (Read & Execute, List Folder Contents, and Read should already be selected in the Allow column), and then click OK.

    7. In the Security dialog box, click Yes.

    8. Repeat steps 3c through 3g for CatalogWebSvc, MarketingWebSvc, OrdersWebSvc, and ProfilesWebSvc accounts.

Add Users or Windows Groups to the Authorization Roles

Follow these steps to add the minimum set of users to the authorization roles:

Step 1: Create the Business Management administrator Windows groups

For instructions about how to create a local Windows group, see "To create a local group" in Windows Help. You must create four administrator groups: CatalogAdminGroup, MarketingAdminGroup, ProfilesAdminGroup, and OrdersAdminGroup.

Note
These represent the minimum number of Windows groups to define. For a production deployment, you will want to define more groups in order to take full advantage of the role assignments available. For descriptions about each predefined role, see http://go.microsoft.com/fwlink/?LinkID=73097.

Follow these steps to create the local Windows groups for Business Management application administrators.

To create the Business Management administrator Windows group

  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 Groups, and then click New Group.

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

    Use this To do this

    Group name

    Type the group name.

    Description

    Optionally, type a description for this group account.

    Add

    Click Add to select members to add to the group.

    Add all user accounts that you want to the administrative group.

  5. Click Create.

  6. Repeat steps 4 and 5 for the other required administrator groups.

  7. Click Close.

  8. Click the Groups folder and verify that the following groups are in the list:

    CatalogAdminGroup

    MarketingAdminGroup

    ProfilesAdminGroup

    OrdersAdminGroup

Step 2: Add users to the Business Management administrator Windows groups

Follow these steps to add users to the administrator groups you created in step 1. At a minimum, add your account, the <CS Installer> account, to each administrator group. You do this so that you will be able to open the Business Management applications after you install them.

To add users to the Business Management Administrator Windows Groups

  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. Click Groups.

  4. In the right pane, right-click one of the Groups that you created in step 1, for example, CatalogAdminGroup, and then click Properties.

  5. In the <Group Name> Properties dialog box, click Add.

  6. In the Enter object name to select box, type the name of the user account that you want to add to the administrator group. Click Check Names to verify the name is an authorized account, and then click OK.

  7. Repeat Steps 5 and 6 for each user account that you want to add to the selected administrator group.

  8. Click OK to close the Properties dialog box.

  9. Repeat Steps 4 through 8 for each administrator group.

Step 3: Add Windows groups to the administrator authorization roles

You use the Authorization Manager to add individual users or user groups to a role. Authorization Manager, a Windows Server 2003 security tool, provides a role-based security model that you use to set permissions. By using role-based access control, you specify access control in relation to the organizational structure of your company. For more information about Authorization Manager, see http://go.microsoft.com/fwlink/?LinkID=16923.

The following table lists the minimum set of authorization roles, and their corresponding authorization stores, that you must define.

Authorization Store Authorization Role

CatalogAuthorizationStore.xml

Administrator

MarketingAuthorizationStore.xml

MarketingAdministrator

OrdersAuthorizationStore.xml

OrdersAdministrator

ProfilesAuthorizationStore.xml

ProfileAdministrator

Follow these steps to add business users or groups to the authorization roles.

To add users to the authorization 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 store for the Web service. For example, the catalog authorization store XML file is located at <drive:>\Inetpub\Wwwroot\CatalogWebService.

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

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

  6. Expand the authorization store to \<authorization store name>.xml\<System name>\Role Assignments\<Role name>. For example, \CatalogAuthorizationStore.xml\CatalogandInventorySystem\Role Assignments\CatalogAdministrator.

  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 administrator Windows group that you defined in the previous procedure, for example, CatalogAdminGroup. Alternatively, you can also type the name of an individual business user account. Click OK.

  9. Repeat steps 2 through 8 for each authorization role in each Web service authorization store. When complete, you will have defined the following:

    Authorization Store Authorization Role Administrator Group

    CatalogAuthorizationStore.xml

    Administrator

    CatalogAdminGroup

    MarketingAuthorizationStore.xml

    MarketingAdministrator

    MarketingAdminGroup

    OrdersAuthorizationStore.xml

    OrdersAdministrator

    OrdersAdminGroup

    ProfilesAuthorizationStore.xml

    ProfileAdministrator

    ProfilesAdminGroup

Step 4: Add CSLOB account to the authorization roles

The following procedure describes how to assign the Commerce Server adapters service account, CSLOB, to its required authorization roles by using Authorization Manager. Perform this task on the computer where you unpacked the Web services.

To add the CSLOB account to the required authorization roles

  1. Click Start, click Run, type azman.msc, and then click OK. If CatalogAuthorizationStore.xml, OrdersAuthorizationStore.xml, and ProfilesAuthorizationStore.xml appear in the left pane, go to step 6.

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

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

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

  6. Set the Catalog System authorization store role permissions:

    1. Expand the role assignments for CatalogAuthorizationStore.xml (for example, \CatalogAuthorizationStore.xml\CatalogandInventorySystem\Role Assignments).

    2. Right-click CatalogAdministrator, and then click Assign Windows Users and Groups.

    3. In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type CSLOB or the name that you created for the Commerce Server Adapters service account. Click OK.

    4. Repeat steps b and c for the InventoryAdministrator role.

  7. Set the Orders System authorization store role permissions:

    1. Expand the role assignments for OrdersAuthorizationStore.xml (for example, \OrdersAuthorizationStore.xml\OrdersSystem\Role Assignments).

    2. Right-click OrdersAdapter, and then click Assign Windows Users and Groups.

    3. In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type CSLOB or the name that you created for the Commerce Server Adapters service account. Click OK.

  8. Set the ProfileWriter_Adapter role permissions for the UserObject, Address, Organization, BlanketPO, CreditCard, and Currency profile definitions in the Profiles System authorization store:

    1. Expand the role assignments for ProfilesAuthorizationStore.xml (for example, \ProfilesAuthorizationStore.xml\ProfilesSystem\<profile definition>\Role Assignments).

    2. Right-click ProfileWriter_Adapter, and then click Assign Windows Users and Groups.

    3. In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type CSLOB or the name that you created for the Commerce Server Adapters service account. Click OK.

    4. Repeat steps b and c for each profile definition in the Profiles System authorization store.

Grant Web Applications and Window Services Access to the Databases

To grant Web services access to the SQL databases, you must perform the following two procedures:

Step 2 requires mapping several database roles to databases for each SQL database account you create in step 1. See SQL Database Account, Database, and Database Role User Mapping for a definition of these roles and their mappings.

Step 1: Create SQL database accounts

You must create an SQL Login account for the following:

  • Each Commerce Server user account that you defined in Create User Accounts, except for the <CS Installer> account.

  • ASP.NET process, this is used to assign read access to the MSCS_Admin Database.

Follow the steps provided for the SQL Server version you are using.

To create an SQL Login Account for the Commerce Server Web service in SQL Server 2000

  1. On the design-time computer that is running SQL Server, 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 <servername>, expand Security.

  3. Right-click Logins and select New Login.

  4. In the Login – New dialog box, click the Search button.

  5. In the Select User or Group dialog box, enter the local or domain RunTimeUser account you created in the Create User Accounts section and then click OK.

  6. Repeats steps 3 through 5 for all accounts listed in the Create User Accounts section. In addition, create an account labeled ASPNET.

  7. Verify that the following SQL Login accounts now appear under Logins:

    <domain or computer name>\ASPNET

    <domain or computer name>\RunTimeUser

    <domain or computer name>\CatalogWebSvc

    <domain or computer name>\CSDMSvc

    <domain or computer name>\CSHealthMonitorSvc

    <domain or computer name>\CSStageSvc

    <domain or computer name>\MarketingWebSvc

    <domain or computer name>\OrdersWebSvc

    <domain or computer name>\ProfilesWebSvc
To create an SQL Login Account for the Commerce Server Web service in SQL Server 2005

  1. On the design-time computer that is running SQL Server, 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>, expand Security.

  4. Right-click Logins and select New Login.

  5. In the Login – New dialog box, click the Search button.

  6. In the Select User or Group dialog box, enter the local or domain RunTimeUser account you created in the Create User Accounts section and then click OK.

  7. Repeats steps 4 through 6 for all accounts listed in the Create User Accounts section. In addition, create an account labeled ASPNET.

  8. Verify that the following SQL Login accounts now appear under Logins:

    <domain or computer name>\ASPNET

    <domain or computer name>\CatalogWebSvc

    <domain or computer name>\CSDMSvc

    <domain or computer name>\CSHealthMonitorSvc

    <domain or computer name>\CSStageSvc

    <domain or computer name>\MarketingWebSvc

    <domain or computer name>\OrdersWebSvc

    <domain or computer name>\ProfilesWebSvc

    <domain or computer name>\RunTimeUser

Step 2: Associate the SQL database accounts with the database roles in SQL Server

You must associate the database accounts together with the database roles in SQL Server. Follow the steps provided for the SQL Server version you are using. Refer to SQL Database Account, Database, and Database Role User Mapping for each set of user mappings to be made for each SQL database account.

To associate the database accounts with the database roles in SQL Server 2000

  1. On the design-time computer that is running SQL Server, 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 <servername>, 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 <account name> dialog box, on the Database Access tab, in the top box, select a database.

  5. In the bottom box, specify the role for the account, and then click OK.

  6. Repeat steps 3 through 5 until all the required accounts are associated with the specified database roles, and then click OK.

To associate the database accounts with the database roles in SQL Server 2005

  1. On the design-time computer that is running SQL Server, 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>, expand Security, expand Logins, right-click the database account, 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 check box for the appropriate database.

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

  7. Repeat steps 3 through 6 until all the required accounts are associated with the specified database roles, and then click OK.

SQL Database Account, Database, and Database Role User Mapping

The following table lists the accounts on the computers that are running SQL Server that you must add to the specified roles. In the table, <SiteName> refers to the name of your Commerce Server site.

Database Account Database SQL Server 2000 Roles SQL Server 2005 Roles

ASPNET

MSCS_Admin

db_datareader

db_datareader

CatalogWebSvc

MSCS_Admin

admin_reader_role

admin_reader_role

MSCS_CatalogScratch

db_owner

db_datareader, db_datawriter, db_ddladmin

<SiteName>_ProductCatalog

db_owner

ctlg_CatalogWriterRole, db_datareader, db_datawriter, db_ddladmin, db_securityadmin, Inventory_ReaderRole, Inventory_WriterRole

MarketingWebSvc

MSCS_Admin

admin_reader_role

admin_reader_role

<SiteName>_Marketing

mktg_MarketingService_role, mktg_promoCodeGenerator_role

mktg_MarketingService_role, mktg_promoCodeGenerator_role

<SiteName>_MarketingLists

db_owner

db_owner

<SiteName>_ProductCatalog

ctlg_catalogReaderRole

ctlg_catalogReaderRole

<SiteName>_Profiles

Profile_Reader, Profile_Schema_Reader

Profile_Reader, Profile_Schema_Reader

OrdersWebSvc

MSCS_Admin

admin_reader_role

admin_reader_role

MSCS_CatalogScratch

db_owner

db_datareader, db_datawriter, db_ddladmin

<SiteName>_Marketing

mktg_runtime_role

db_ddladmin, mktg_runtime_role

<SiteName>_ProductCatalog

ctlg_catalogReaderRole, Inventory_ReaderRole

ctlg_catalogReaderRole, Inventory_ReaderRole

<SiteName>_Profiles

Profile_Reader, Profile_Schema_Reader

Profile_Reader, Profile_Schema_Reader

<SiteName>_TransactionConfig

Orders_Management

Orders_Management

<SiteName>_Transactions

Orders_Management, Orders_Runtime

Orders_Management, Orders_Runtime

ProfilesWebSvc

MSCS_Admin

admin_reader_role

admin_reader_role

<SiteName>_Profiles

Profile_Schema_Manager, Profile_Runtime

Profile_Schema_Manager, Profile_Runtime

RunTimeUser

MSCS_Admin

admin_reader_role

admin_reader_role

MSCS_CatalogScratch

db_owner

db_datareader, db_datawriter, db_ddladmin

<SiteName>_Marketing

mktg_runtime_role

db_ddladmin, mktg_runtime_role

<SiteName>_MarketingLists

db_datareader

db_datareader

<SiteName>_ProductCatalog

ctlg_catalogReaderRole, Inventory_RuntimeRole

ctlg_catalogReaderRole, Inventory_RuntimeRole

<SiteName>_Profiles

Profile_Schema_Reader, Profile_Runtime

Profile_Schema_Reader, Profile_Runtime

<SiteName>_TransactionConfig

Orders_Runtime

Orders_Runtime

<SiteName>_Transactions

Orders_Runtime

Orders_Runtime

CSDMSvc

DirectMailer

db_owner

db_owner

MSCS_Admin

admin_reader_role

admin_reader_role

<SiteName>_Marketing

mktg_directmailer_role

mktg_directmailer_role

<SiteName>_MarketingLists

db_owner

db_owner

<SiteName>_Profiles

Profile_Schema_Reader, Profile_Reader

Profile_Schema_Reader, Profile_Reader

CSHealthMonitorSvc

MSCS_Admin

admin_reader_role

admin_reader_role

CSStageSvc

MSCS_Admin

admin_reader_role

admin_reader_role

MSCS_CatalogScratch

db_owner

db_datareader, db_datawriter, db_ddladmin

<SiteName>_Marketing

mktg_MarketingService_role, mktg_runtime_role, mktg_dataManager_role, mktg_promoCodeGenerator_role

db_ddladmin, mktg_staging_role

<SiteName>_MarketingLists

db_owner

db_datareader

<SiteName>_ProductCatalog

db_owner

ctlg_CatalogWriterRole, db_datareader, db_datawriter, db_ddladmin, db_securityadmin, Inventory_ReaderRole, Inventory_WriterRole

<SiteName>_Profiles

Profile_Schema_Manager

Profile_Schema_Manager

<SiteName>_TransactionConfig

Orders_Management

Orders_Management

<CS Staging User>

MSCS_Admin

db_datareader

db_datareader

MSCS_CatalogScratch

db_datareader, db_datawriter, db_ddladmin

db_datareader, db_datawriter, db_ddladmin

<SiteName>_ProductCatalog

ctlg_CatalogReaderRole, Inventory_ReaderRole

ctlg_CatalogWriterRole, Inventory_ReaderRole

Configure a Temporary SSL Certificate

Follow these steps to configure a temporary SSL certificate using the SelfSSL tool in the Internet Information Services (IIS) 6.0 Resource Kit.

Note
This step is only appropriate for development environments. SelfSSL certificates are unsuitable for production environments.

To configure a temporary SSL certificate

  1. In Internet Explorer, open 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 and then click Save.

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

  6. Click Start, click Run, type explorer, and then click OK. In Windows Explorer, move to the location where you saved the executable package, and then double-click iis60rkt.exe.

  7. In the Open File - Security Warning dialog box, click Run.

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

  9. On the Microsoft Software License Terms page, read the terms of the license agreement. If you accept them, select I agree, and then click Next.

  10. On the Customer Information page, correct, accept, or type your user name and organization, accept the default option to install this application for anyone who uses the computer (all users), and then click Next.

  11. On the Setup Type page, accept the default Complete option and then click Next.

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

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

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

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

  16. If you are prompted to replace the SSL settings for site 1, press Y, and then press ENTER.

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

  17. Close the Command Prompt window.

Assign Permissions to the IIS Worker Process Accounts

The 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 so that users can have access to the Web services. Assigning permissions according to these steps limits access to Commerce Server data to only those Commerce Server components that need access to that data and only to the data that they need.

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

Step 1: Create application pools for the Web applications

The following steps show you how to create application pools in IIS for the CSharp Web site and Web services.

To create application pools for the Web applications

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

  2. In Internet Information Services (IIS) Manager, expand <computername>, right-click Application Pools, point to New, and then click Application Pool.

  3. In the Add New Application Pool dialog box, in the Application pool ID box, type the name of the Web site application pool (for example, CSharpSiteAppPool), and then click OK.

  4. Repeat steps 2 and 3 for each Web service. After you complete these steps, you should have five applications pools defined, one each for the four Web services and one for the Web site.

  5. Click the Application Pools folder and verify that the following application pools are in the list:

    • CSharpSiteAppPool

    • CatalogWebSvcAppPool

    • MarketingWebSvcAppPool

    • OrdersWebSvcAppPool

    • ProfilesWebSvcAppPool

Step 2: Configure the application pool accounts

The following steps show you how to configure the application pools to use the IIS worker process accounts. The Identity for each application pool should be set to the corresponding account that was created when you created the user accounts (see Create User Accounts). That is, the <SiteName>AppPool application pool identity is assigned the RuntimeUser account, the CatalogWebSvcAppPool identity is assigned the CatalogWebSvc account, and so on.

To configure the application pool account

  1. Click Start, point to 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 CSharpSiteAppPool, 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 (<domain or computer name>\RunTimeUser), 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 user rights Adjust memory quotas for a process and Replace a process level token to this account.

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

  8. Repeat steps 3 through 7 for each Web service application. The assignments should correspond as indicated in the following table:

    Application Pool Identity

    CSharpSiteAppPool

    (<domain or computer name>\RunTimeUser

    CatalogWebSvcAppPool

    (<domain or computer name>\CatalogWebSvc

    MarketingWebSvcAppPool

    (<domain or computer name>\MarketingWebSvc

    OrdersWebSvcAppPool

    (<domain or computer name>\OrdersWebSvc

    ProfilesWebSvcAppPool

    (<domain or computer name>\ProfilesWebSvc

  9. Close IIS Manager.

Step 3: Add the worker process accounts to the IIS_WPG group

The following step shows how to add the IIS worker process accounts 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. In the right pane, 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 (<domain or computer name>\RunTimeUser), and then click OK.

  6. Repeat step 5 to add the CatalogWebSvc, MarketingWebSvc, OrdersWebSvc, and ProfilesWebSvc accounts to the IIS_WPG group.

  7. In the IIS_WPG Properties dialog box, click OK.

  8. Close the Computer Management screen.

Step 4: Assign the applications to the application pools

The following steps show you how to assign applications to the application pools you set up in step 1.

To assign applications to application pools

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

  2. In IIS Manager, expand Web Sites and then expand Default Web Site.

  3. Right-click the first application under Default Web Site, for example CSharpSite, and then click Properties.

  4. In the <Application> Properties dialog box, on the Virtual Directory tab, select the name of the corresponding application pool in the Application Pool box. For example, for CSharpSite, select the application pool CSharpSiteAppPool.

  5. Repeat step 4 for each Web service application under Default Web Site. Make sure that you complete this for the following applications:

    Application Application Pool

    <SiteName>

    <SiteName>AppPool

    CatalogWebService

    CatalogWebSvcAppPool

    MarketingWebService

    MarkingWebSvcAppPool

    OrdersWebService

    OrdersWebSvcAppPool

    ProfilesWebService

    ProfilesWebSvcAppPool

  6. Close IIS Manager.

Restart IIS and Verify Web Services Are Installed

Before you can access the Business Management applications, you must restart IIS. Restarting IIS unloads all Web applications from memory, restarts the IIS service and updates the cache. Therefore, when you restart IIS, you do not have to unload an application from memory.

To restart IIS

  • Click Start, click Run, type iisreset, and then click OK.

    A Command Prompt window opens displaying the status of the IISReset command. You should read the status at the command prompt to make sure that IIS stops and restarts.

A Web service is installed correctly if a folder exists for it, and you can visit the Web page for that Web service to see a summary of its methods.

To verify the installation of Web services

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

  2. In Windows Explorer, move to <drive>:\inetpub\wwwroot directory.

  3. In the wwwroot directory, verify that a folder exists for each Web service (Catalog, Marketing, Orders, and Profiles).

    Web services are installed on the Web server at the following locations:

    • <drive>:\Inetpub\wwwroot\CatalogWebService

    • <drive>:\Inetpub\wwwroot\MarketingWebService

    • <drive>:\Inetpub\wwwroot\OrdersWebService

    • <drive>:\Inetpub\wwwroot\ProfilesWebService

  4. To open the Web page for each Web service, type the address of the page in the Address bar, and then press ENTER.

    URLs for the Web services are as follows:

    • http://<server>/CatalogWebService/CatalogWebService.asmx

    • http://<server>/MarketingWebService/MarketingWebService.asmx

    • http://<server>/OrdersWebService/OrdersWebService.asmx

    • http://<server>/ProfilesWebService/ProfilesWebService.asmx

Grant the Marketing Web Service Permissions to Launch and Activate the Direct Mailer Service

Follow these steps on the computer where you run the Direct Mailer Service. These steps grant the Marketing Web service access to the Direct Mailer Service.

To grant the Marketing Web service access to the Direct Mailer Service

  1. Click Start, point to Programs, point to Administrative Tools, and then click Component Services.

  2. In the Component Services window, expand Component Services, expand Computers, expand My Computer, and expand DCOM Config.

  3. Right-click Microsoft Commerce Server DirectMailer Service, and then click Properties.

  4. In the Microsoft Commerce Server DirectMailer Service Properties dialog box, on the Security tab, in the Launch and Activation 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 dialog box, in the Enter the object names to select box, type <data domain>\MarketingWebSvc, and then click OK.

  7. In the Launch Permission dialog box, in the Permissions for <data domain>\MarketingWebSvc section, select the Local Launch and Local Activation check boxes for Allow, and then click OK.

  8. In the Microsoft Commerce Server DirectMailer Service Properties dialog box, on the Security tab, in the Access Permissions section, select Customize, and then click Edit.

  9. In the Access Permission dialog box, click Add.

  10. In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type <data domain>\MarketingWebSvc, and then click OK.

  11. In the Access Permission dialog box, in the Permissions for <data domain>\MarketingWebSvc section, select the Local Access check box for Allow, and then click OK.

  12. In the Microsoft Commerce Server DirectMailer Service Properties dialog box, click OK.

  13. Repeat steps 3 through 12 for the DML_SG group account. This account was created during configuration. See Configure Commerce Server.

Configure and Start the Commerce Server Health Monitoring Service

If you installed Commerce Server Health Monitoring, you must configure and start it. Commerce Server Health Monitoring is a local service that monitors the Commerce Server Web services that are defined on the computer.

Note
The Commerce Server Health Monitoring Service may consume available connections on this operating system. To avoid having incoming connections consumed on Windows XP, do not enable the Commerce Server Health Monitoring Service.

Important
You must install Microsoft Operations Manager (MOM) 2005 SP1 and the Microsoft Commerce Server 2007 Management Object Model (MOM) Pack to use the Commerce Server Health Monitoring.

For the Commerce Server Health Monitoring service to monitor the Commerce Server Web services, you must grant the CSHealthMonitorSvc user account viewer rights to the authorization stores. Follow these steps to add the Commerce Server Health Monitoring service user account to the role assignment for each Web service.

To add the CSHealthMonitorSvc user to the authorization roles

  1. Click Start, click Run, type azman.msc, and then click OK.

  2. In the Authorization Manager screen, expand the authorization store to \<authorization store name>.xml\<System name>\Role Assignments\<Role name>. For example, \CatalogAuthorizationStore.xml\CatalogandInventorySystem\Role Assignments\CatalogViewer.

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

  4. In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type the name of the Commerce Server Health Monitoring user account, for example, CSHealthMonitorSvc. Click OK.

  5. Repeat steps 2 through 4 for each authorization role in each Web service authorization store. When complete, you will have defined the following:

    Authorization Store Authorization Role

    CatalogAuthorizationStore.xml

    CatalogViewer

    MarketingAuthorizationStore.xml

    MarketingViewer

    OrdersAuthorizationStore.xml

    OrdersViewer

    ProfilesAuthorizationStore.xml

    ProfileAdministrator

Follow these steps to configure and start Commerce Server Health Monitoring Service.

To configure and start Commerce Server Health Monitoring Service

  1. Click Start, click Run, type services.msc, and then click OK.

  2. In the Services window, right-click Commerce Server Health Monitoring, and then click Properties.

  3. In the Commerce Server Health Monitoring Properties dialog box, on the General tab, in the Startup type box, select Automatic from the drop-down list.

  4. On the Log On tab, click Browse.

  5. In the Select User dialog box, in the Enter the object name to select box, type the name of the Commerce Server Health Monitoring user that you created in Create User Accounts, for example CSHealthMonitorSvc, and then click OK.

  6. On the Log On tab, in the Password and Confirm password boxes, type the password for the user, and then click OK.

  7. In the Services window, right-click Commerce Server Health Monitoring, and then click Start.

  8. Exit the Services window.

Configure and Start the Commerce Server VSS Writer

This is an optional task. The Commerce Server Volume Shadow Copy Writer Service supports back up and restore operations of Commerce Server databases.

Follow these steps to configure and start the Commerce Server Volume Shadow Copy Writer Service.

To configure and start the Commerce Server VSS Writer

  1. Click Start, click Run, type services.msc, and then click OK.

  2. In the Services window, right-click Commerce Server VSS Writer, and then click Properties.

  3. In the Commerce Server VSS Writer Properties dialog box, on the General tab, in the Startup type box, select Automatic from the drop-down list.

  4. On the Log On tab, click Browse.

  5. In the Select User dialog box, in the Enter the object name to select box, type the name of a user who has administration rights to the MSCS_Admin database, and then click OK.

  6. On the Log On tab, in the Password and Confirm password boxes, type the password for the user, and then click OK.

  7. In the Services window, right-click Commerce Server VSS Writer, and then click Start.

  8. Exit the Services window.

Refer to the Windows Server 2003 documentation for more information about how to use VSS services.

Install Commerce Server Business Management Applications

You install Commerce Server Business Management applications on developer, system administrator, system integrator, and business user computers. You can install one or more applications on each computer. After you install a Business Management application, open the application to make sure that you can access it. If you cannot access it, verify that you have added the user account trying to access the application to the administrator group that is defined for the application. See Step 2: Add users to the Business Management administrator Windows groups.

Note
You can also install the Business Management applications by using unattended installation. For information, see Unattended Installation Command Syntax Reference.

Before you install the Business Management applications, note the following:

  • Make sure that you have installed all software prerequisites for the Business Management applications listed in Software Requirements.

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

  • Close all other applications before you continue.

Follow these steps to install the Business Management applications.

To install the Business Management applications

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

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

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

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

  5. On the Component Installation page, cancel the selection of any Business Management application(s) you do not want to install. Commerce Server 2007 includes the following Business Management applications:

    • Catalog Manager. This is required for product catalog Web site management activities.

    • Catalog and Inventory Schema Manager. This is required for managing catalog definitions, categories, products, and properties.

    • Customer and Orders Manager. This is required for order management Web site activities.

    • Marketing Manager. This is required for discount, advertisement, and direct mail Web site management activities.

  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 Logfile to review the list of events for the installation. Then, click Finish.

Follow these steps to access each Business Management application.

To access the Business Management applications

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

  2. In the Site Connections dialog box, click Edit.

  3. In the Settings dialog box, on the Connection Settings tab, do the following:

    Use this To do this

    Name

    Accept the Default site connection.

    < Web service >

    Accept the default URL, or type a new URL, for your connection to the Web service. For example, to connect to the Catalog Web service, type http://<server>/CatalogWebService/CatalogWebService.asmx.

  4. Click OK.

  5. In the Site Connections dialog box, click OK to open the Business Management application.

  6. Repeat steps 1 through 5 for each Business Management application to make sure that they are available.

Install Commerce Server Adapters for BizTalk Server

You can install the Commerce Server Adapters for BizTalk Server to integrate with other applications, Web services, and trading partners. Commerce Server 2007 includes the following line-of-business adapters:

  • BizTalk Adapter for Catalogs

  • BizTalk Adapter for Inventory

  • BizTalk Adapter for Orders

  • BizTalk Adapter for Profiles

Note
You can also install the Commerce Server Adapters for BizTalk Server by using unattended installation. See Unattended Installation Command Syntax Reference.

Before you install the Commerce Server Adapters for BizTalk Server, note the following:

  • Make sure that you have installed all software prerequisites for the Commerce Server adapters listed in Software Requirements.

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

  • You must close all other applications before you continue.

Follow these steps to install the Commerce Server adapters.

To install the Commerce Server Adapters for BizTalk Server

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

  2. On the Microsoft Commerce Server 2007 Start page, under Install, click Microsoft Commerce Server Adapters for Microsoft BizTalk Server.

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

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

  5. On the Component Installation page, accept the selection of the BizTalk Adapters.

  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 and wait for the installation to finish.

    Note
    Several command windows appear and automatically close during the installation of the Commerce Server adapters.

  8. On the Installation Completed page, click Logfile to review the list of events for the installation. Click Finish.
Note
In order to use the Commerce Server adapters, perform the additional configuration steps provided in http://go.microsoft.com/fwlink/?LinkID=73094.

Upgrade Requirements

If you have Commerce Server 2000 or Commerce Server 2002 installed, you must uninstall them before you install Commerce Server 2007. Before uninstalling the earlier versions of Commerce Server, you should perform the task outlined in the following section to preserve the data and prepare for migrating your Web site data and resources to the Commerce Server 2007 platform.

Note
When you upgrade from an earlier version, make sure that you back up your Commerce Server databases before you install Commerce Server 2007. You should back up all your data including SQL Server databases, site code, and configuration settings before uninstalling Commerce Server 2007.

Prepare to Upgrade to Commerce Server 2007 from Commerce Server 2000 or 2002

The following steps describe how to prepare for upgrading your Commerce Server 2000 or 2002 installation to Commerce Server 2007.

To prepare to upgrade to Commerce Server 2007 from Commerce Server 2000 or 2002

  1. Plan your migration strategy.

  2. Back up all your data including SQL Server databases, site code, site resources, global resources, and configuration settings before uninstalling earlier versions of Commerce Server.

  3. Save all Web sites as package (.pup) files. Use Commerce Server Site Packager to package your existing site.

  4. Uninstall Commerce Server 2000 or Commerce Server 2002. Refer to the corresponding product documentation for the steps. You must first uninstall any Commerce Server Service Packs or Commerce Server 2002 Feature Pack 1.

  5. Uninstall the Commerce Server runtime objects. For information about how to uninstall the Commerce Server runtime objects, see Uninstall 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 2007, and when you perform the steps in the Commerce Server Upgrade Wizard.

  6. If your current operating system is Windows 2000, upgrade to Windows Server 2003. See Microsoft Operating System and Web Server Software Requirements.

  7. Install or upgrade prerequisite software, see Additional Prerequisite Software Requirements.

  8. Install Commerce Server 2007.

  9. Configure Commerce Server 2007.

  10. Use the Commerce Server 2007 Upgrade Wizard to upgrade global resources, site resources, and site data from Commerce Server 2000 or 2002 to Commerce Server 2007. Before you use the Commerce Server 2007 Upgrade Wizard, review the changes the Upgrade Wizard can make.

Commerce Server 2007 Upgrade Wizard

You use the Commerce Server 2007 Upgrade Wizard to upgrade your site resources and the Administration database. You can upgrade from Commerce Server 2002 or prerelease versions of Commerce Server 2007. The Upgrade Wizard migrates your existing global and site resources (including catalogs, orders, campaigns, marketing, and profiles data), and site data to Commerce Server 2007.

If you are using any prerelease version of Commerce Server 2007, for example Commerce Server 2007 Beta or Release Candidate, you must uninstall the prerelease version and then install the final release version before you use the Upgrade Wizard.

Commerce Server 2007 does not support in position upgrades from Commerce Server 2000. However, if you have a Commerce Server 2000 site package, you can unpack that site into a Commerce Server 2007 installation and then use the Upgrade Wizard to upgrade the Commerce Server 2000 resources in the unpacked site to be compatible with Commerce Server 2007.

The Commerce Server Upgrade Wizard (CS2007Upgrade.exe) is located in the \Microsoft Commerce Server 2007\Upgrade folder. When the upgrade process is complete, the Upgrade Wizard provides a list of resources that were not upgraded from your prerelease version. You must manually migrate any reported resources for them to function correctly. For more information, see http://go.microsoft.com/fwlink/?LinkID=70229.

Uninstall Commerce Server

This section provides instructions on how to:

Uninstall Commerce Server 2007

To uninstall Commerce Server 2007 core components, follow these steps in the order shown:

  1. Remove the Commerce Server Run-Time Objects and Administration Tools

  2. Remove the Commerce Server Client Tools

Note
If you uninstall Commerce Server 2007, it does not remove Microsoft .NET Framework or Microsoft Document Explorer 2005. If you do not need these components, remove them manually by using the Add Or Remove Programs functionality in Control Panel.

After you follow these steps, we recommend that you restart the computer.

Remove the Commerce Server Run-Time Objects and Administration Tools

Follow these steps to remove the Commerce Server 2007 runtime objects and administration tools. This step removes the core Commerce Server 2007 components, registry keys, and binary files, except for the following folders:

  • Staging\Data

  • Staging\Projects

  • Staging\Events

  • Staging\Packages

You must manually delete these folders to remove them.

To remove Commerce Server run-time objects and administration tools

  1. Click Start, click Settings, 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 Change/Remove next to Microsoft Commerce Server 2007 Enterprise Edition (or the corresponding edition installed on your server).

  4. On the Program Maintenance page, click Remove, and then click Next.

  5. On the Summary page, click Uninstall.

    The Installation Wizard uninstalls Commerce Server 2007.

  6. On the Uninstall Completed page, click Finish.
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 reinstall Commerce Server 2007, and when you perform the steps in the Commerce Server Upgrade Wizard.

Remove the Commerce Server Client Tools

Follow these steps to remove the Commerce Server 2007 client tools.

To remove the Commerce Server client 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 Microsoft Commerce Server 2007 Client Tools, and then click Change/Remove.

  4. In the Windows Installer dialog box, click Yes to confirm that you want to remove Commerce Server 2007 client tools.

Uninstall Commerce Server Business Management Applications

Follow these steps to uninstall one of the following Business Management applications:

  • Catalog Manager

  • Catalog and Inventory Schema Manager

  • Customer and Orders Manager

  • Marketing Manager

To remove the 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 Microsoft Commerce Server 2007 Business User Applications, and then click Change/Remove next to this program.

  4. On the Program Maintenance page, click Remove, and then click Next.

  5. On the Summary page, click Uninstall.

    The Installation Progress dialog box shows details of the removal operations.

  6. On the Uninstall Completed page, click Finish.

Uninstall Commerce Server Adapters for BizTalk Server

Follow these steps to uninstall Commerce Server Adapters for BizTalk Server.

To remove the Commerce Server Adapters for BizTalk Server

  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 Microsoft Commerce Server 2007 Adapters for BizTalk Server, and then click Change/Remove next to this program.

  4. On the Program Maintenance page, click Remove, and then click Next.

  5. On the Summary page, click Uninstall.

    The Installation Progress dialog box shows details of the removal operations.

  6. On the Uninstall Completed page, click Finish.

Uninstall Commerce Server Web Sites

To uninstall a Commerce Server Web site, follow these steps in the order shown:

  1. Delete Commerce Server Databases

  2. Delete the Commerce Server Site Virtual Directories

  3. Delete the Commerce Server Site Folders and Files

Delete Commerce Server Databases

Follow these steps to remove one or more Commerce Server databases. For a list of databases, see SQL Server Database Instances Created for Commerce Server.

To remove the Commerce Server databases 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, 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. In SQL Server Enterprise Manager, expand to \Microsoft SQL Servers\SQL Server Group\SQL Server Name\Databases.

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

  5. Repeat step 4 for each Commerce Server database.
To remove the Commerce Server databases in SQL Server 2005

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

  2. In the Connect to Server dialog box, select your computer name, and then click Connect.

  3. In SQL Server Management Studio, in the left pane, expand <servername>, expand Databases

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

  5. In the Delete Object dialog box, click OK.

  6. Repeat step 4 and 5 for each Commerce Server database.

Delete the Commerce Server Site Virtual Directories

If you unpacked a site, you must follow these steps to remove the site virtual directories. These include virtual directories for the site and Commerce Server Web services, such as Catalog, Marketing, Orders, and Profiles.

To delete the site virtual directories

  1. Click Start, point to 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\Default Web Site\<IIS Web site name>.

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

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

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

Delete the Commerce Server Site Folders and Files

If you unpacked a site, you must follow these steps to delete the site folders and files. These include any folders and files for the Commerce Server Web services, such as Catalog, Marketing, Orders, and Profiles.

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 that 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 that you want to delete.

Troubleshoot Your Commerce Server Installation

This section describes problems that you might experience when you install or uninstall Commerce Server 2007, and offers possible solutions:

Commerce Server Cannot Find the Administration Database

If you change the name of the computer where you installed SQL Server, the computer that is running Commerce Server may not automatically find the administration database.

Solution

You must change the SQL Server logon and password for the administration database.

To change the SQL Server logon and password for the Commerce Server administration database

  1. Click Start, point to Programs, point to Microsoft Commerce Server 2007, and then click Commerce Server Manager.

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

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

  4. After you make the required changes in the Data Link Properties dialog box, click Test Connection and then click OK.

  5. Click OK to close the Data Link Properties dialog box.

  6. In the Commerce Server Manager Properties dialog box, click OK.

Cannot Configure the Administration Database

When configuring Commerce Server by using the Commerce Server Configuration Wizard, 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 2007, and you have used SQL Server Enterprise Manager (SQL Server 2000) or SQL Server Management Studio (SQL Server 2005) 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 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 prerelease version of SQL Server.

Cannot Reinstall Commerce Server to Create a New Administration Database

If 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 Commerce Server administration database named MSCS_Admin, and then run the admin_schema.sql and admin_schema_increment.sql scripts. When you run the scripts, the system populates the schema of the administration database but does not create any resources. After you run the scripts, you must unpack your sites again.

To resolve this problem, follow these steps:

Note
Prior to performing these steps, backup all Web site and Web service files and databases.

Note
Separate steps are provided for SQL Server 2000 and for SQL Server 2005.
Step 1: Create a new Commerce Server administration database
To create a new administration database in SQL Server 2000

  1. Click Start, point to 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.
To create a new administration database in SQL Server 2005

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

  2. Within Management Studio, connect to your SQL Server, and then in the Object Explorer, expand the nodes to the following path: <SQL Server name>/Databases.

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

  4. In the Database Properties dialog box, on the General page, in the Name box, type MSCS_Admin, and then click OK.
Step 2: Run the admin_schema.sql script

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

To run the admin_schema.sql script from SQL Query Analyzer in SQL Server 2000

  1. In SQL Server 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 2007\admin_schema.sql, select the script file, and then click Open.

  4. On the toolbar, click Execute Query.
To run the admin_schema.sql script in SQL Server 2005

  1. In SQL Server Management Studio, on the File menu, click Open, and then click File.

  2. In the Open File dialog box, browse to the folder <drive:>\Program Files\Microsoft Commerce Server 2007, or wherever you installed Commerce Server.

  3. Select the script file admin_schema.sql, and then click Open.

  4. In the Connect to Database Engine dialog box, click Options.

  5. On the Connection Properties tab, in the Connect to database drop-down list, click <Browse server>.

  6. In the Browse for Databases dialog box, click Yes.

  7. In the Browse Server for Database dialog box, select the user database MSCS_Admin, and then click OK.

  8. In the Connect to Database Engine dialog box, click Connect. The script file admin_schema.sql opens.

  9. On the Query menu, click Execute.
Step 3: Run the admin_schema_increment.sql script

After you run the admin_schema.sql script, you must run the admin_schema_increment.sql script.

To run the admin_schema_increment.sql script from SQL Query Analyzer in SQL Server 2000

  1. In SQL Server 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 2007\admin_schema_increment.sql, select the script file, and then click Open.

  4. On the toolbar, click Execute Query.
To run the admin_schema_increment.sql script in SQL Server 2005

  1. In SQL Server Management Studio, on the File menu, click Open, and then click File.

  2. In the Open File dialog box, browse to the folder <drive:>\Program Files\ Commerce Server 2007, or wherever you installed Commerce Server.

  3. Select the script file admin_schema_increment.sql, and then click Open.

  4. In the Connect to Database Engine dialog box, click Options.

  5. On the Connection Properties tab, in the Connect to database drop-down list, click <Browse server>.

  6. In the Browse for Databases dialog box, click Yes.

  7. In the Browse Server for Database dialog box, select the user database MSCS_Admin, and then click OK.

  8. In the Connect to Database Engine dialog box, click Connect. The script file admin_schema_increment.sql opens.

  9. On the Query menu, click Execute.
Step 4: Unpack the Commerce Server site

Unpack your site or sites. See Unpack the CSharp Site.

Note
After you re-create the administration database, unpack the site and Web services. Restore any modified files and databases as needed.

BizTalk Server Not Functional After Uninstalling Commerce Server

Commerce Server and BizTalk Server share some functionality related to the Profiles System. If you have both Commerce Server and BizTalk Server installed on the same computer, and you uninstall one of them, some functionality in the other product may be compromised.

Solution

Use the Repair mode in the Commerce Server Setup program or the BizTalk Server Setup program to reinstall any components that were accidentally removed when you uninstalled the other product.

AuthFilter Not Functional After Upgrading Commerce Server

If you upgrade to Commerce Server 2007 from an earlier version of Commerce Server, and you use the AuthFilter ISAPI filter to help manage user authentication in your Web application, use of your Web application, this includes the associated Web services, may fail because of the AuthFilter DLL (siteauth.dll) not being found by IIS. Specifically, you may see the following event message in the event log:

"Could not load all ISAPI filters for site/service. Therefore startup aborted."

Solution

To correct this issue, follow these steps.

To copy the AuthFiles folder

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

  2. In Windows Explorer, move to the Commerce Server SDK samples directory, for example, <drive:>\<Commerce Server 2007 Installation Path>\SDK\Samples.

  3. Copy the AuthFiles folder to the <drive:>\Inetpub\wwwroot\<Your Web Site> folder.
To provide the correct path of the AuthFilter DLL

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

  2. In Internet Information Services (IIS) Manager, expand <computername>, expand Web Sites, right-click Default Web Site, and then click Properties.

  3. On the ISAPI Filters tab, select the AuthFilter filter and then click Edit.

  4. In the Add/Edit Filter Properties dialog box, click Browse and locate the correct Commerce Server 2007 path of the associated executable file "siteauth.dll". This file is located in the <drive:>\Program Files\Microsoft Commerce Server 2007 directory.

    Note
    On 64-bit systems, always use the 64-bit version of the AuthFilter DLL. By default, this version is located in the folder <drive:>\Program Files\Microsoft Commerce Server 2007. Do not use the 32-bit version of the AuthFilter DLL. By default, this version is located in the folder <drive:>\Program Files (x86)\Microsoft Commerce Server 2007.

Adapter Installation Failure on 64-bit Computers: The ServicedComponent being invoked is not configured correctly

If you have installed the COM+ hotfix on a 64-bit computer, you may encounter an error when you install the Commerce Server Adapters for BizTalk Server, deploying or configuring BizTalk Server, or when you are using the BizTalk Administration Console. Specifically, you may see the following error:

"The ServicedComponent being invoked is not correctly configured. Use regsvcs to reregister."

After seeing this error, if you try to restart the COM+ system application service from the Service Control Manager, it fails.

Solution

Follow these steps to reinstall COM+ components:

To reinstall COM+ components

  1. Click Start, click Control Panel, double-click Add or Remove Programs, and then click Add/Remove Windows Components.

  2. In the Windows Component Wizard, select Application Server, and then click Details.

  3. Verify that Enable network COM+ access is selected, click OK, and then click Next.

  4. Click Finish to close the Windows Components Wizard.

  5. Restart the COM+ System Application service, and restart the BizTalk services by using the Service Control Manager.

  6. To obtain an updated COM+ rollup package to fix this problem, contact Microsoft Customer support or download the fix from http://go.microsoft.com/fwlink/?LinkID=69579.

For more information about this issue, see http://go.microsoft.com/fwlink/?linkid=69577.

Unattended Installation Command Syntax Reference

Commerce Server 2007 enables automated electronic software distribution, also known as unattended installation and configuration. You use unattended installation to install Commerce Server 2007 in an automated way on computers that have the same configurations. Unattended installation lets system administrators who want to install and configure Commerce Server 2007 on remote computers to do this without requiring user intervention. By using 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 that are provided to suppress all interaction. When you perform an unattended installation, the installation or configuration 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.

For information about how to use the unattended installation commands, see the following:

Note
Commerce Server 2007 disallows unattended installation for clustered resources.

How to Install Commerce Server by Using the Setup.exe Command Syntax for Unattended Installations

When you install Commerce Server 2007, note the following:

  • Make sure that you have installed all the Commerce Server software prerequisites listed in Software Requirements.

  • You must have administrator permissions on the computer where you install Commerce Server software.

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

    Note
    Before you install Commerce Server 2007 by using unattended installation, you must uninstall any earlier versions of Commerce Server that you may have on your computer. For information about how to uninstall Commerce Server, see Prepare to Upgrade to Commerce Server 2007 from Commerce Server 2000 or 2002.

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

Note
You can run the Setup.exe command from the CD, or copy the whole CD image to a local drive.

To perform an unattended installation of Commerce Server

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

  2. Move to the directory that contains the Setup.exe file.

  3. To start the unattended installation, at the command prompt, type the following and then press ENTER. For information about each option and their parameters, see Setup.exe Command Syntax:

    setup.exe /< option name > < parameters >

    Examples of command statements for installing each Commerce Server 2007 component are as follows:

    • To install Commerce Server:

      setup.exe /l %systemdrive%\install.log /ADDLOCAL ALL /PRODUCT CommerceServer /passive /norestart

    • To install Commerce Server Business Management applications:

      setup.exe /l %systemdrive%\install.log /ADDLOCAL ALL /PRODUCT CSUI /passive /norestart

    • To install Commerce Server Adapters for BizTalk Server 2006:

      setup.exe /l %systemdrive%\install.log /ADDLOCAL ALL /PRODUCT CSBTSAdapters /passive /norestart



Setup.exe Command Syntax

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

Option Parameter Description

/ADDLOCAL  

<feature list> or ALL

Valid values for the feature list are as follows:

  • Feature.MS.CS.Server

  • Feature.MS.CS.DirectMailer

  • Feature.MS.CS.PCW

  • Feature.MS.CS.CsStaging

  • Feature.MS.CS.HealthMonitoring

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 complete.

/IGNOREDEPENDENCIES

Bypasses checks for downloadable prerequisites.

/INSTALLDIR

<product installation path>

Specifies the full path on which to install the product.

/L, or /LOG  

<Logfile>

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

/NORESTART

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

/PASSIVE

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

/PRODUCT

<CommerceServer>, <CSUI>, or <CSBTSAdapters>

Installs one of the following:

  • Commerce Server

  • Business Management applications

  • BizTalk Adapters

<cscatalogui>, <csmarketingui>, <csordersui>

Installs individual Business Management applications:

  • Catalog Manager and Catalog and Inventory Schema Manager

  • Marketing Manager

  • Customer and Orders Manager

/PROMPTRESTART

Prompts the user before restarting.

You cannot use this option with the /QUIET option.

/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.

/S  

<Configuration XML file>

Performs an unattended configuration of Commerce Server by using the information that you provide in the configuration XML file. You obtain this file by using the Commerce Server Configuration Wizard and clicking Save on the Summary page. For a sample configuration file, see Sample Configuration XML File.

/USERNAME  

<User name>

Sets the user name.

/X, or /UNINSTALL

Uninstalls Commerce Server.

How to Configure Commerce Server by Using the CSConfig.exe Command

Follow these steps to perform an unattended configuration of Commerce Server 2007.

To perform an unattended configuration of Commerce Server

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

  2. Move to the directory that contains the CSConfig.exe file.

  3. To start the unattended configuration, at the command prompt, type the following and then press ENTER. For information about each option and parameters, see CSConfig.exe Command Syntax:

    CSConfig.exe /<option name> <parameters>

    An example statement that uses the CSConfig.xml configuration file to configure all Commerce Server features is as follows:

    CSConfig.exe /f /l %systemdrive%\install.log /r ALL /s CSConfig.xml

CSConfig.exe Command Syntax

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

Option Parameter Description

/f

Forces the configuration of all features even if they are already configured.

/l

<log_file>

Specifies a custom log file. By default, a log file that has a timestamp-based name is created in the Temp directory.

/r

<feature list> or ALL

Valid values for the feature list are as follows:

  • Feature.MS.CS.Server

  • Feature.MS.CS.DirectMailer

  • Feature.MS.CS.PCW

  • Feature.MS.CS.CsStaging

  • Feature.MS.CS.HealthMonitoring

Applies the configuration to a comma-separated list of features. This option can be combined with /u.

/s

<xml_config_file>

Performs an unattended configuration based on the settings that are provided in the XML configuration file. You obtain this file by using the Commerce Server Configuration Wizard and clicking Save on the Summary page. For a sample configuration file, see Sample Configuration XML File.

/u

Performs an unattended removal of the configuration.

Sample Configuration XML File

The configuration XML file is created when you run the Commerce Server Configuration Wizard and select to save the configuration. The file is labeled CSConfig.xml and is written to the <Commerce Server 2007 Installation Path>. The following is a sample configuration XML file that has all features configured:

<Configuration>
  <VirtualDirectory ID="Publishing" Create="True" />
  <NTService ID="StagingService">
    <UserName>CSStageSvc</UserName>
    <Domain>A-TEST-09</Domain>
    <Password />
  </NTService>
  <SQL ID="CommerceAdminDB">
    <Server>A-TEST-09</Server>
    <Database>MSCS_Admin</Database>
    <WindowsSecurity>yes</WindowsSecurity>
    <Password />
  </SQL>
  <SQL ID="DirectMailerDB">
    <Server>A-TEST-09</Server>
    <Database>DirectMailer</Database>
    <WindowsSecurity>yes</WindowsSecurity>
    <Password />
  </SQL>
  <NTService ID="DirectMailerService">
    <UserName>CSDMSvc</UserName>
    <Domain>A-TEST-09</Domain>
    <Password />
  </NTService>
</Configuration>

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

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. 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.

© 2007 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, BizTalk, SharePoint, Visual Studio, Windows, Windows NT, and Windows Server and are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.