Поделиться через

Building a Single Server Deployment

  • Статья

This section provides instructions about how to configure the Commerce Server 2009 single server. This server is typically used in a non-production environment. The single server deployment consists of running all the Commerce Server 2009 components and required software (including the Windows operating system, Commerce Server 2007, WSS or MOSS, and SQL Server) on a single computer. Configuring a computer to act as a Commerce Server 2009 single server involves the same tasks that you perform to configure a developer workstation, business management server, the server that is running BizTalk Server, and Web server.

The procedure in this topic does not install or configure the following components:

  • Commerce Server 2009 Data Warehouse and Analytics System

  • Commerce Server 2009 reports

  • Microsoft System Center Operations Manager (SCOM) and SCOM Pack components

Follow these steps to configure the Commerce Server 2009 single server: 

Note

The following task sequence assumes that the server is already connected to a network.

  1. Install the Windows operating system and all prerequisite software. For more information, see What Are the Software Deployment Requirements?

  2. If your operating system is Windows Server 2003, use Add or Remove Programs in Control Panel to make sure that you have the following Windows Server 2003 components installed on your system:

    • Accessories and Utilities

    • Indexing Service

    • Internet Information Services (IIS)

    • Script Debugger

    For more information about each of these roles, see the documentation for Windows Server 2003.

  3. Install IIS if you have not already done so. If you did not select IIS to install during the installation of your operating system, you can install it now by using Add or Remove Programs for Windows Server 2003 Control Panel or Server Manager for Windows Server 2008.

    Note

    In Windows Server 2008, you must install the following services that are part of the Web Server (IIS) Role: Windows Authentication IIS6 Metabase Compatibility and Windows Authentication.

  4. Make sure that you have the following IIS components installed on your system:

    • Active Server Pages (ASP). This component is required only if you are using Commerce Server Staging (CSS) and configuring CSS Reporting virtual root.

    • ASP.NET

    • Common files

    • Documentation (optional)

    • IIS snap-in

    • Internet Services Manager (HTML)

    • Simple Mail Transfer Protocol (SMTP) service. This component is required only if Direct Mailer is being used or CSS events are configured to send e-mail, and another SMTP server is not available.

    • World Wide Web server

  5. If your operating system is Windows Server 2008, and you have already installed IIS, do the following:

    • Click Start, Control Panel, Programs and Features, and then click Turn Windows Features On or Off.

    • Ensure that the following services are installed; both are part of the Web Server (IIS) server role in Windows Server 2008: Windows Authentication (in the Security services category) and IIS6 Metabase Compatibility (under the Management Tools > IIS 6 Management Compatibility services category).

  6. If your operating system is Windows Server 2008, and you have already installed IIS, do the following:

    • Click Start, Control Panel, Programs and Features, and then click Turn Windows Features On or Off.

    • Ensure that the following services are installed; both are part of the Web Server (IIS) server role in Windows Server 2008: Windows Authentication (in the Security services category) and IIS6 Metabase Compatibility (under the Management Tools > IIS 6 Management Compatibility services category).

  7. Enable IIS. For more information, see How to Enable IIS on the Business Management Server.

  8. Enable Active Server Pages (ASP). To configure the Commerce Server Staging Reporting Service virtual directory correctly, you must enable ASP prior to running the Commerce Server Configuration Wizard. For more information, see How to Enable Active Server Pages (ASP).

  9. Install SQL Server software. For more information, see Configuring the Database Servers.

  10. Install Visual Studio 2008 with Service Pack 1 (SP1). See Install Visual Studio.

  11. Create local accounts for the following (see Creating Accounts and Groups):

    • RunTimeUser

    • CatalogWebSvc

    • MarketingWebSvc

    • OrdersWebSvc

    • ProfilesWebSvc

    • CSDMSvc

    • CSLOB

    • CSStageSvc

  12. Install and configure BizTalk Server 2006:

    1. Install BizTalk Server 2006. For more information, see How to Install BizTalk Server 2006.

    2. Add the BizTalkAdmin group to the Administrator group. For more information, see How to Add the BizTalkAdmin Group to the Administrators Group.

    3. Configure BizTalk Server 2006, see How to Configure BizTalk Server 2006.

  13. If you have not already done so, install Commerce Server 2007 Core Components. See "Installing Commerce Server Core Components" in the Commerce Server 2009 Installation and Configuration Guide at https://go.microsoft.com/fwlink/?LinkId=139462.

  14. Configure the Commerce Server Core Components. See "Configuring the Commerce Server Core Components" in the Commerce Server 2009 Installation and Configuration Guide at https://go.microsoft.com/fwlink/?LinkId=139462.

  15. Install the Commerce Server 2009 components. See "Installing the Commerce Server 2009 Components" in the Commerce Server 2009 Installation and Configuration Guide at https://go.microsoft.com/fwlink/?LinkId=139462.

  16. Unpack the Commerce Server CSharp site or deploy the Default Site and the Web Parts. To unpack the CSharp site, see "Unpacking the CSharp Site" in the Commerce Server 2009 Installation and Configuration Guide at https://go.microsoft.com/fwlink/?LinkId=139462. To deploy the Default Site and Web Parts, see "Deploying the SharePoint Commerce Services" in the Commerce Server 2009 Installation and Configuration Guide at https://go.microsoft.com/fwlink/?LinkId=139462. 

  17. If you deployed the Default Site, you must specify the Default Site channel and catalog names and turn off anonymous access in the MyAccount sub site. For information, see "Specifying the Default Site Channel and Catalog Names" and "Turning Off Anonymous Access in the MyAccount Sub site" in the Commerce Server 2009 Installation and Configuration Guide at https://go.microsoft.com/fwlink/?LinkId=139462.

  18. Set the following access permissions to help secure files and folders:

    1. Assign write permissions to the Catalog Web service account. For more information, see How to Assign Write Permissions to the Catalog Authorization Role.

    2. For the temporary ASP.NET folder, assign write permissions to the Web application accounts. For more information, see How to Assign Write Permissions to the Temporary ASP.NET Folder.

    3. For the Windows temporary folder, assign access permissions to all Web application accounts. For more information, see How to Assign Permissions for the Windows Temporary Folder.

  19. Create application pools and make assignments to the IIS worker process group:

    1. Use IIS Manager to create an application pool for each Web site and Web service that you unpack. For more information, see How to Create Application Pools.

      The following table summarizes the default names that this deployment guide uses for Web services, application pools, and service accounts.

      Web application

      Application pool

      Service account

      CatalogWebService

      CatalogWebSvcAppPool

      CatalogWebSvc

      MarketingWebService

      MarketingWebSvcAppPool

      MarketingWebSvc

      OrdersWebService

      OrdersWebSvcAppPool

      OrdersWebSvc

      ProfilesWebService

      ProfilesWebSvcAppPool

      ProfilesWebSvc

      <site_name>

      <site_name>AppPool

      RunTimeUser

    2. Assign each service account to its associated application pool. For example, assign the RunTimeUser account to <site_name>AppPool and the CatalogWebSvc account to CatalogWebSvcAppPool. For more information, see How to Assign a Web Application to an Application Pool.

    3. Assign each Web application service account to the IIS worker process account. For example, assign the CatalogWebSvc account to the IIS_WPG group if Windows Server 2003 is your operating system or IIS_IUSRS if your operating system is Windows Server 2008. For more information, see How to Specify Accounts for Running the Application Pools.

    4. Assign each Web application to its associated application pool. For example, assign the <site_name> application to <site_name>AppPool, and assign the CatalogWebService application to CatalogWebSvcAppPool. For more information about how to assign a Web application to its associated application pool if your operating system is Windows Server 2003, see How to Add Service Accounts to the IIS_WPG Group. For more information about how to assign a Web application to its associated application pool if your operating system is Windows Server 2008, see How to Add Service Accounts to the IIS_IUSRS Group.

  20. Verify the installation of the Web services. For more information, see How to Verify the Installation of the Web Services.

  21. Authorize users and groups to access the Web services. For more information, see Authorizing Users and Groups to Access Web Services.

  22. Grant the Commerce Server service identities access to the databases:

    1. Create SQL Server logon database accounts for the following:

      ASPNet

      RunTimeUser

      CatalogWebSvc

      MarketingWebSvc

      OrdersWebSvc

      ProfilesWebSvc

      CSDMSvc

      CSHealthMonitorSvc

    2. For each account that you created in the previous step, associate the database accounts together with the database roles. For the required mappings, see What Are the Required Database Accounts and Database Role Mappings?

  23. Install the Business Management applications. For more information, see How to Install the Business Management Applications on the Business Management Server.

  24. Install BizTalk adapters. For more information, see How to Install Commerce Server Adapters for BizTalk Server.

  25. (Optional) Configure the Direct Mailer service.

    1. Install and configure the Simple Mail Transfer Protocol (SMTP) service that is provided by IIS. For more information, see How to Configure an SMTP Server for Direct Mailer.

    2. Grant the marketing Web service access to the Direct Mailer service. For more information, see How to Grant the Marketing Web Service Access to the Direct Mailer Service.

    3. Grant the marketing Web service access to the schedule tasks service. For more information, see How to Grant the Marketing Web Service Access to Schedule Tasks.

See Also

Other Resources

Building the Development Environment

Configuring the Business Management Server

Configuring the Web Servers

How to Install SQL Server 2005

How to Install SQL Server 2008

Deployment Requirements

Deployment Roadmap

Building Deployments