Prep Work for Updating Commerce Server Configuration Files

This topic details the steps to apply the manual fixes necessary to port your Microsoft SharePoint 2007 site to SharePoint 2010, or Microsoft Commerce Server 2009 Template Pack Site for SharePoint 2010.

Perform the following procedures to prepare for updating Commerce Server configuration files:

  1. Convert Your Web Application

  2. Perform Web Application Conversion Cleanup

  3. Upgrade Commerce Server Web Parts

  4. Copy Service Endpoints

  5. Configure Alternate Access Mapping

Convert Your Web Application

Convert your web application to claims-based security.

  1. Open a SharePoint 2010 Management Shell window. Click Start->All Programs->Microsoft SharePoint 2010 Products ->SharePoint 2010 Management Shell.

  2. At a command prompt type $w = Get-SpWebApplication(“http://URL OF BUSINESS USER WEB APPLICATION”), and then press ENTER.

  3. Configure your Web application to use claims.

    1. If you are using the contemporary site or default site with MOSS2007 or WSS 3.0 instance, type $w.UseClaimsAuthentication = $true, and then press ENTER.

    2. If you are using the contemporary site or default site with MOSS2007 or WSS 3.0 instance, type $w.Update(), and then press ENTER.

  4. At the command prompt, type the following to obtain the ID of the Web application (the ID of the web application is required in one of the subsequent procedures): $w.ID, and then press ENTER.

  5. Record the ID of the web application as it will be required when you perform the next procedure.

Perform Web Application Conversion Cleanup

Complete the following steps to convert to a claims-based web application.

  1. Launch Sharepoint 2010 Central Administration.

  2. On the Central Administration Home page, in the Application Management section, click Manage Web Applications.

  3. Select your Web application.

  4. Click Authentication Providers.

  5. Click Default Zone.

  6. Make NO changes and click Save.

  7. Click Internet Zone.

  8. Set the ASP.NET membership provider to CS_[WebAppGUID] _Internet where [WebAppGUID] is the ID you recorded as part of performing the previous procedure.

  9. Select Custom Sign In Page and enter _layouts/CommerceServer/CommerceLoginPage.aspx

  10. Click Save.

Upgrade Commerce Server Web Parts

If you are migrating an existing SharePoint-based site and have deployed the Commerce Server 2009 Web Parts, you can use the SharePoint Commerce Services Configuration tool to upgrade the Web Parts to the Commerce Server 2009 R2 version. When you upgrade the Commerce Server Web Parts, the SharePoint Commerce Services Configuration tool replaces any existing Web Parts you have deployed.

Hh597557.alert_caution(en-us,CS.95).gifImportant Note:

If you have custom Web Parts deployed on your system with the same SharePoint Solution file name and GUID, the SharePoint Commerce Services Configuration tool detects the existing Web Parts and prompts you to upgrade them. This applies even if you used the SharePoint Commerce Services Extensibility Kit for SharePoint 2010 to build the Web Parts. Proceeding with the upgrade will overwrite the custom Web Parts, as well as any related customization.

To upgrade the Commerce Server Web Parts

  1. Launch the SharePoint Commerce Services Configuration Wizard (Start > All Programs > Microsoft Commerce Server 2009 R2 > Tools > SharePoint Commerce Services Configuration Wizard).

    The system launches the SharePoint Commerce Services Configuration Wizard.

  2. On the System Dependency Check page, click Next if your system meets all the requirements.

    The system checks for existing Web Parts, and detects that there are existing Commerce Server Web Parts installed on the system.

  3. On the SharePoint Commerce Services Selection page, select the Upgrade Web Parts Only option, and then click Next.

    If the Wizard detects that the existing Web Parts contain customization, a warning dialog appears asking you to confirm the upgrade.

  4. Click Yes.

    A page displays a summary of the tasks the wizard will complete based on your selections.

  5. Review the configuration summary, and click Next to proceed with the deployment of the current selections.

    A progress indicator appears.

  6. When the upgrade is complete, click Finish to exit the configuration wizard.

  7. Restart the SharePoint Timer service.

Copy Service Endpoints

Perform the following procedures to copy the service endpoints:

  1. Copy the SVC File to the Web Application Virtual Directory of the Default Zone

  2. Copy the SVC File to the Web Application Virtual Directory of the Internet Zone

Copy the SVC File to the Web Application Virtual Directory of the Default Zone

Perform the following steps to copy the .svc file to the web app virtual directory:

  1. Open windows explorer and navigate to the virtual directory of the Default Zone.

  2. Create a new folder for the foundation service called Foundation.

  3. Copy the foundationservice.svc file from the 14 hive located in the CommerceServer feature directory (eg: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\CommerceServer) to the root of your virtual directory (eg: C:\inetpub\wwwroot\wss\VirtualDirectories\[port of zone]\Foundation\)

Copy the SVC File to the Web Application Virtual Directory of the Internet Zone

Perform the following steps to copy the svc file to the web app virtual directory:

  1. Open windows explorer and navigate to the virtual directory of the Internet Zone.

  2. Create a new folder for the foundation service called Foundation.

  3. Copy the foundationservice.svc file from the 14 hive located in the CommerceServer feature directory (eg: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\CommerceServer) to the root of your virtual directory (eg: C:\inetpub\wwwroot\wss\VirtualDirectories\[port of zone]\Foundation\)

Configure Alternate Access Mapping

Perform the following steps to add localhost to your alternate access mappings (AAM):

  1. In Central Administration, select Application Management->Configure alternate access mappings.

  2. Click Show All next to "Alternate Access Mappings Collection" and then select your web application.

  3. Click Add Internal URL to add localhost mapping for the Default zone.

  4. In the Add internal URL section, in the URL protocol, host and port box, type the localhost URL and port (for example: https://localhost:[port of default zone]/).

  5. In the Zone list, set the zone to Default

  6. Click Save.

  7. In the Add internal URL section, in the URL protocol, host and port box, type the localhost URL and port for the Internet zone (for example: https://localhost:[port of Internet zone]/).

  8. In the Zone list, set the zone to Internet.

  9. Click Save.

  10. Perform an IISRESET.

See Also

Other Resources

Update Commerce Server Configuration Files