Configuring a Presentation Server Newly Added to an Existing SharePoint 2010 Farm
This topic applies to two-tier or three-tier commerce deployment scenarios where a new Web server was recently added to an existing SharePoint 2010 farm.
Microsoft SharePoint 2010 allows you to scale your e-commerce network by adding new presentation servers to an existing SharePoint 2010 farm. The topic contains procedures to help you configure the newly added Web front-end server hosting your SharePoint 2010 e-commerce Web application.
Perform the procedures in this topic before you join the new node to your SharePoint 2010 farm.
Prerequisites
The information provided in this topic makes the following assumptions:
The new Web server is part of the SharePoint 2010 farm and the e-commerce Web application is successfully deployed on the new node. For more information about adding a new node to an existing SharePoint 2010 farm see https://go.microsoft.com/fwlink/?LinkId=211714.
The Microsoft Commerce Server 2009 R2 software is installed and configured on the new server in the farm.
In a two-tier commerce deployment, the commerce presentation and commerce foundation software components must be installed on the server.
In a three-tier commerce deployment, only the presentation component is required in the presentation tier.
.gif "Important note")
Important Note:The new presentation node must reference the same Commerce Server 2009 R2 database as other nodes in the farm.
For detailed information about how to install and initially configure Commerce Server 2009 R2, see Installation and Initial Configuration.
You must be familiar with the authorization roles requirements specific to your deployment. In a farm deployment, the AzMan authorization stores used to define access permissions must be configured locally on each node on the server.
Configuring a New Presentation Server in an Existing Farm
Perform the following procedures in the order listed to configure the new front-end SharePoint 2010 server hosting the e-commerce application:
Warning
Back up your current configuration files. Deactivating and reactivating the Commerce Features in SharePoint 2010 results in the loss of manually applied settings in the Web.config file for both zones, in every front-end node across the farm. It also results in the loss of manually applied settings in the security token service Web.config file on every node. Make sure to backup the appropriate section of Web.config file in steps 1 and 2 of this procedure. These backups allow you to restore your site and security token service configurations.
Back up the <system.serviceModel> Section From the Web.config file of each zone .
Back up the <CommerceOperationService> and <endpoint> sections of the security token service Web.config file.
Reactivate Commerce Features in SharePoint 2010. See How to Reactivate Commerce Features In SharePoint 2010.
Remove the duplicate entry for System.Diagnostics.EventTypeFilter from the Web.config file for both zones on all nodes in the farm. See Remove Duplicate Entry for System.Diagnostics.EventTypeFilter.
Restore Your Site Customizations On Every Node in the Farm.
Restore your security token service customizations.
Verify the Commerce Foundation service client endpoints in the security token service Web.config file.
If in a two-tier commerce deployment, assign the required authorization privileges in AzMan. See Managing Authorization Policies.
Note
This step is only required when the Web application ChannelConfiguration.config file on each node specifies authorization security and local policy files paths. If this is the case, the authorization policy files must be copied to the new node and the same permission configurations must be applied.
Note
In a SharePoint 2010 deployment, perform an IIS reset after making changes to authorization stores in AzMan. The IIS reset forces user claims to refresh.
Using the ProfileKeyManager.exe tool, load the profile key file into the registry of the node newly added to the farm.
Back Up the <system.serviceModel> Section in Web.config
Log on to an existing farm node in your deployment (not the newly added node), and copy the entire section <system.serviceModel> of the Web.config file of each zone.
| Important Note: |
|---|
This backup is required so that you can subsequently restore your customizations by pasting back in this section in the Web.config file of each zone, on every node in your SharePoint 2010 farm. |
Back Up the <CommerceOperationService> and <endpoint> Section in the Security Token Service Web.config
| Important Note: |
|---|
This backup is required so that you can subsequently restore your customizations to the security token service Web.config file by pasting your changes back into the appropriate sections. |
Note
In a three-tier deployment, the security token service Web.config file is located on the presentation node at the path noted below.
Browse to <drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\SecurityToken.
Open the security token service Web.config file, and do the following:
Copy the entire section <CommerceOperationService>.
Copy the entire section <endpoint>.
How to Reactivate Commerce Features in SharePoint 2010
After you have added a new node to SharePoint 2010, you must reactivate all Web application-level features and site collection-level features in SharePoint 2010.
This is applicable to both two-tier and three-tier farm deployment scenarios.
Warning
Deactivating and reactivating the Commerce Features in SharePoint 2010 results in the loss of manually applied settings in the Web.config file for both zones, in every front-end node across the farm. It also results in the loss of manually applied settings in the security token service Web.config file on every node. Make sure to backup the appropriate section of Web.config file prior to performing the steps in this procedure. See Back Up <system.serviceModel> Section From Web.config and Back up the <CommerceOperationService> and <endpoint> sections of the security token service Web.config file.
To reactivate features at the Web application level
This procedure reactivates the Web application level features across all nodes in the farm. You only need to perform this procedure on the newly added node.
This procedure applies to both two-tier and three-tier farm deployment scenarios.
On the SharePoint Central Administration Web site, click Application Management.
In the Application Management section, click Manage web applications.
Click the Web application for which you want to reactivate features. The ribbon becomes active.
On the ribbon, click Manage Features and then deactivate all the features, and then reactivate each feature one at a time:
Commerce Live ID Module Feature (only if it was initially active)
Commerce Server Feature
Commerce Server Management
Commerce Server Storefront Site Resources
Commerce Server Web Part Resources
Silverlight Web Config
After you have completed the feature reactivation, verify that all the timer jobs have run successfully on all nodes. If any jobs failed, deactivate those features, and then reactivate each feature one at a time.
How to Reactivate Features at the Site Collection Level
When activated, the CommerceMyAccountSiteMapProvider site collection feature displays a map of the e-commerce site (Site map) in the My Account sub site. In order for this feature to take effect on the site on the new node, manually add the site map provider configuration to the Web.config file on each zone of your e-commerce Web site.
This procedure applies to both two-tier and three-tier farm deployment scenarios.
Open the Web.config file of your Web application and then navigate to the <providers> section. This section is located in the following hierarchy:
<configuration>
<system.web>
<siteMap>
<providers>
Add the following siteMap provider configuration to the <providers> section:
<add name="CommerceMyAccountSiteMapProvider" description="Provider for Commerce My Account" type="Microsoft.Commerce.Portal.SiteMap.CommerceXmlSiteMapProvider, Microsoft.Commerce.Portal.SiteMap, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" siteMapFile="/MyAccountLeftNavigation.sitemap" />Repeat the above steps on the other zone of your site.
On the Web server, navigate to the following location:<drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\CommerceServerStorefrontSiteMyAccountSiteMapProvider
Copy the file MyAccountLeftNavigation.sitemap and then paste it into the virtual folder of each zone of your Web application.
Remove Duplicate Entry for System.Diagnostics.EventTypeFilter
When the Commerce Server Feature is activated, a duplicate entry for the System.Diagnostic.EventTypeFilter is created in the Web.config file. For your site to load successfully, you must manually remove the following duplicate entry from the Web.config file in both zones on all nodes in the farm:
<filter type="System.Diagnostics.EventTypeFilter" initializeData="Error,Warning,Information" />
Restore Your Site Customizations on Every Node in the Farm
Now that Commerce Features have been reactivated in SharePoint 2010, you must restore your site customizations across the farm.
For each node in the farm, and for each zone, open the Web.config file and replace the existing <system.serviceModel> section (which has been overwritten during the feature activation process) with the backup copy that contains your site customizations (this is the backup copy you saved in Back Up the <system.serviceModel> Section From Web.config).
Restore Your Security Token Service Customizations
Now that Commerce Features have been reactivated in SharePoint 2010, you must restore your security token service customizations across the farm.
For each node (two-tier) or each presentation node (three-tier) in the farm, open the security token service Web.config file located at <drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\SecurityToken, and replace the existing <CommerceOperationService> and <endpoint> section (which has been overwritten during the feature activation process) with the backup copy that contains your security token service customizations (this is the backup copy you saved in Back up the <CommerceOperationService> and <endpoint> sections of the security token service Web.config file).
Verify the Commerce Foundation Service Client Endpoints in the Security Token Service Web.config file
For security reasons in a two-tier deployment, the Commerce Foundation service client endpoints defined in the SharePoint 2010 security token service Web.config must use local addressing. In some situations, for example, when not using host headers for an application running on a SharePoint 2010 farm, the Commerce Foundation service address may not be configured correctly after deployment on some farm nodes. In such cases, the Commerce Foundation service client endpoints must be manually configured to use an address that resolves to the local server.
Open the security token service Web.config file located at <drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\SecurityToken.
If necessary, manually configure the Commerce Foundation service client endpoints to use an address that resolves to a local server.
Repeat the above steps for all nodes in the farm.
Load the Profile Key File into the Registry of the Newly Added Node
To fully deploy the new node, an existing profile key must be imported from an existing farm node into this new node.
Note
Since it is good security practice to encrypt the profile key, you may need to enter the passphrase when you import the profile key into the registry.
For example, for the Solution Storefront site, copy the profile key called ProfileKeys_SolutionStorefrontSite.xml from an existing farm node. By default, the Solution Storefront deployment will place the profile key into the follow directory %commerce_server_root%\SharePointServices\Site\
Place the copied profile key into the local directory of the new node.
To import the profile key into the registry, use the ProfileKeyManager command. See "Encrypting Existing Keys into the Registry" section in Commerce Server Command Line Tools.
Restart the new node for the profile key to take effect.
See Also
Other Resources
Managing Authorization Policies
Cannot Use Silverlight Web Tools After Making Updates to Authorization Stores