Jaa

How to Configure a Developer Workstation

  • Artikkeli

You can install Commerce Server 2009 on either Windows Server 2003 R2 with Service Pack 2 or Windows Server 2008.

The procedures in this topic do not install or configure the following components:

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

To prepare a developer workstation for Commerce Server installation

  1. If you have already installed IIS during the installation of Windows Server 2008, do the following; otherwise, go to step 2:

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

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

    To install IIS 7.0 Windows Server 2008:

    1. Click Start, point to Administrative Tools and then click ServerManager.

    2. In the tree view on the left, click Roles.

    3. Under RolesSummary, click AddRoles.

    4. The AddRolesWizard opens; if the Before You Begin page appears, click Next to go to the next page.

    5. In the Select Server Roles page, click Web Server (IIS), and then click Next.

    Note

    If you are prompted to add features that are needed for the Web Server (IIS) role, click Add Required Features. When the Add Roles Wizard window comes back to the front, click Next to resume the installation.

    1. In the Select Role Services page, select the role services listed below, and then click Next.

    Select this role service categories

    And then select these services

    Common HTTP Features

    Static Content

    Default Document

    Directory Browsing

    Http Errors

    Application Development

    ASP

    ASP.NET

    .NET Extensibility

    ISAPI Extensions

    ISAPI Filters

    Health and Diagnostics

    HTTP Logging

    Request Monitor

    Security

    Basic Authentication

    Windows Authentication

    Digest Authentication

    Request Filtering

    Performance

    Static Content Compression

    Management Tools

    IIS Management Console

    IIS Management Scripts and Tools

    Management Services

    IIS6 Management Compatibility
    1. In the Confirm Installation Selections page, review your selections. When you have confirmed that the correct role services are selected, click Install.

    Install IIS on Windows Server 2003:

    1. Click Start, point to 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, in the left pane, click Add/Remove Windows Components.

    4. On the Windows Components page, in the Components box, click Application Server, and then click Details.

    5. In the Application Server dialog box, in the Subcomponents of Application Server box, select the check boxes for ASP.NET, Enable network DTC access, and Internet Information Services (IIS).

    6. Click Internet Information Services (IIS), and then click Details.

    7. In the Internet Information Services (IIS) dialog box, in the Subcomponents of Internet Information Services (IIS) box, select the check boxes for Common Files, Internet Information Services Manager, and World Wide Web Service.

    8. Click World Wide Web Service, and then click Details.

    9. In the World Wide Web Service dialog box, in the Subcomponents of World Wide Web Service box, select the check boxes for Active Server Pages, WebDAV Publishing, and World Wide Web Service, and then click OK.

    10. In the Internet Information Services (IIS) dialog box, click OK.

    11. In the Application Server dialog box, click OK.

    12. On the Windows Components page, click Next.

    13. On the Completing the Windows Components Wizard page, click Finish.

  3. 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. The CSS Reporting Service requires ASP to display reports.

    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 https://go.microsoft.com/fwlink/?linkid=66527.

  4. Install Windows critical updates, which provide the latest updates available for the operating system, software, and hardware. To install all Windows critical updates, see https://go.microsoft.com/fwlink/?linkid=16855.

  5. Install and configure the appropriate version and edition of SQL Server. For more information about supported versions and editions of SQL Server, see SQL Server Requirements in the Commerce Server 2009 Installation and Configuration Guide.

    SQL Server provides the underlying database services for Commerce Server. For information about how to install SQL Server 2005 SP2, see https://go.microsoft.com/fwlink/?linkid=93378. For information about how to install SQL Server 2008, see https://go.microsoft.com/fwlink/?LinkId=139313.

    Dd451889.alert_caution(en-US,CS.90).gifImportant Note:

    Commerce Server databases require collation settings that are not case-sensitive. If you configured SQL Server so that databases are created by using case-sensitive collations, you must take extra steps to make sure that the Commerce Server databases are not created 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.

  6. (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 2009 Data Warehouse does not support SQL Server Report Services 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:

      To install SQL Server 2005 Analysis Services, see https://go.microsoft.com/fwlink/?LinkId=139314

      To install SQL Server 2008 Analysis Services. For information, see https://go.microsoft.com/fwlink/?LinkId=72011.

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

      To install SQL Server 2005 Reporting Services, see https://go.microsoft.com/fwlink/?LinkId=139315.

      To install SQL Server 2008 Reporting Services, see https://go.microsoft.com/fwlink/?LinkId=72013.

  7. (Optional) If you plan on using the Data Warehouse in Commerce Server 2009, you must 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 a feature pack for SQL Server 2005 at https://go.microsoft.com/fwlink/?linkid=65308. If you are using SQL Server 2008, you may have to edit the PATH environment variable so that the SQL 2008-related paths are at the very end of the PATH value.

  8. (Optional) If you plan on using the Data Warehouse in Commerce Server 2009 with SQL Server 2008, you must install the following, in the order listed:

    1. Microsoft SQL Server Native Client. See https://go.microsoft.com/fwlink/?LinkId=139308. 

    2. Microsoft SQL Server 2005 Management Objects Collection. See https://go.microsoft.com/fwlink/?LinkId=139309.

    3. Microsoft ADOMD.NET. See https://go.microsoft.com/fwlink/?LinkId=139310.

    4. Microsoft SQL Server 2005 Backward Compatibility Components. See https://go.microsoft.com/fwlink/?LinkId=139311.

    5. Microsoft SQL Server 2005 December 2008 Feature Pack. See https://go.microsoft.com/fwlink/?LinkId=139312

  9. Install Microsoft Visual Studio 2008 and all applicable Service Packs and hotfixes. Installation of Visual Studio 2008 includes installation of the .NET Framework.

    Dd451889.alert_caution(en-US,CS.90).gifImportant Note:

    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 2009 software prerequisites for development. Therefore, you cannot use the features of Commerce Server 2009, such as the Project Creation Wizard, unless you install Visual Studio 2008.

  10. If you did not install Visual Studio 2008, you must install Microsoft .NET Framework 3.5 SP1.

    The .NET Framework enables you to deploy and run Web-based applications and Web services. To install Microsoft .NET Framework 3.5 SP1, see https://go.microsoft.com/fwlink/?LinkId=139316.

  11. Register ASP.NET 2.0 as the default framework for IIS. All Commerce Server installations require ASP.NET 2.0 registration.

    Note

    Even though you have installed the .NET Framework 3.5 SP1, when you register ASP.NET as the default framework in IIS, you must select release 2.0 of the framework. This is due to the fact the .NET Framework 3.5 is an extension of the 2.0 release and as such, does not appear in IIS.

    1. At a command prompt, go to this folder: %windir%\Microsoft.NET\Framework\v2.0.50727

    2. Type the following command and press Enter:

    aspnet_regiis.exe -i

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

  12. To install WSS or MOSS, click the links below for instructions and information about the relevant updates.

    If using WSS:

    1. WSS 3.0 with SP1; for the 32-bit version see https://go.microsoft.com/fwlink/?LinkId=139486. For the 64-bit version see https://go.microsoft.com/fwlink/?LinkId=139487

    2. WSS 3.0 December Cumulative Update (https://go.microsoft.com/fwlink/?LinkId=139489)

    If using MOSS:

    1. WSS 3.0 SP1 (https://go.microsoft.com/fwlink/?LinkId=130486)

    2. MOSS 2007

    3. MOSS 2007 SP1 (https://go.microsoft.com/fwlink/?LinkId=130488)

    4. December Cumulative Update for both WSS 3.0 and MOSS 2007 (https://go.microsoft.com/fwlink/?LinkId=139489)

  13. (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 https://go.microsoft.com/fwlink/?LinkId=139317.

  14. You should ensure all applicable Service Packs and hotfixes have been applied.

To install and configure Commerce Server 2009

  1. Log on to the workstation under a user account that has local administrator permissions.

  2. To begin the installation, do one of the following:

    • Insert the Commerce Server 2009 DVD in the computer's drive. The setup program starts automatically.

    • If you are accessing the software image on a local or remote hard drive, go to the appropriate location, open the Setup folder and double-click the Setup.exe file.

  3. If the setup program detects that some prerequisite software is missing, it displays a message to that effect. Click Close to exit Setup. Install the required software and then resume the Commerce Server 2009 installation.

  4. On the Welcome page that lists the components the setup program will install, click Next.

    Note

    The installation detects the edition of Commerce Server 2007 that you have currently installed on the server and will only list and install the Commerce Server 2009 components that are relevant to the edition you have. Consequently, the list of components shown may differ slightly from the one shown in the above illustration.

  5. On the Microsoft SoftwareLicense Terms page, read the license agreement, select I have read and accept the license terms, and then click Next.

  6. On the page that indicates that the installation is complete, click Finish.

To unpack a Commerce Server site and set secure deployment requirements

  1. Unpack the CSharp site or the Default site onto each developer workstation. For information, see How to Unpack a Site or "Deploying the SharePoint Commerce Services" in the Commerce Server 2009 Installation and Configuration GuideHow to Unpack a Site on the Business Management Server.

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

  3. Add the developer user account to the Web application authorization roles. For more information, see Authorizing Users and Groups to Access Web Services.

  4. Grant Commerce Server service identities access to the databases.

    • For an independent development environment, grant access to the databases on each developer workstation.

    • For a shared development environment, grant access on the shared database server.

    For more information, see Granting Access to the Commerce Server Databases.

  5. Enable Secure Sockets Layer (SSL). For more information, see How to Enable SSL on the Web Servers.

  6. Assign permissions to the IIS worker process accounts. For more information, see How to Add Service Accounts to the IIS_WPG Group.

  7. To support the Direct Mailer service, follow these steps:

    1. Install and configure the SMTP service that IIS provides. 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

Deployment Roadmap

Building the Development Environment