Migration Considerations
This topic contains information on general considerations for migrating from an earlier version of Microsoft Commerce Server to Commerce Server 2009 R2.
Packaging Sites
Deprecated Resources
Security Model
Encryption
Packaging Sites
You must package your sites using the Site Packager tool on your existing Commerce Server platform before you migrate and upgrade to Commerce Server 2009 R2. You cannot use the Commerce Server 2009 R2 Site Packager tool to package sites based on older versions of Commerce Server.
You can unpack Commerce Server package (.pup) files created on earlier versions of Commerce Server in Commerce Server 2009 R2. However, because some resources have been removed from Commerce Server 2009 R2, these resources are either unpacked and ignored, or not unpacked at all.
Deprecated Resources
You can unpack Commerce Server package (.pup) files created in an earlier version of Commerce Server in Commerce Server 2009 R2, however some resources are no longer supported. The following resources are deprecated in Commerce Server 2009 R2:
Business Desk resource
Business Desk Security resource
Predictor resource
Campaigns resource
For more information about upgrading Commerce Server resources, see Data Migration for Commerce Server 2000/2002.
Commerce Server 2002 Feature Pack 1 Web services are not supported in Commerce Server 2009 R2. You must delete any Commerce Server 2002 Feature Pack 1 Web services and replace them with the Commerce Server 2009 R2 Web services provided in one of the package (Pup) files located in the <Commerce_Server_Root>\Pup Packages folder.
In addition, Commerce Server 2002 client applications are not supported in Commerce Server 2009 R2. Instead, you must use the new client services that are installed with the Commerce Server 2009 R2 Business Management applications.
Security Model
Commerce Server 2009 R2 uses the Windows Server Authorization Manager (AzMan) security model to set permissions for business user roles. With the role-based access control in Authorization Manager, you can specify access control according to the organizational structure of your company.
Migrating security permissions from Commerce Server 2002 is a manual process. You must use AzMan to re-create security permissions as defined in Business Desk Security. In AzMan, Application Groups are populated using existing Windows users or groups, or by nesting Application Groups that have been defined.
For more information about how to use Authorization Manager, see https://go.microsoft.com/fwlink/?linkid=68223. For information about Microsoft authorization technologies, see https://go.microsoft.com/fwlink/?linkid=68232.
Error loading ISAPI filter after upgrading
If you use the AuthFilter ISAPI filter to manage user authentication in your Web application, the Web application and associated Web services might fail after you upgrade to Commerce Server 2009 R2 if IIS cannot find the AuthFilter DLL (siteauth.dll). If this error occurs, the following event message is added to the event log:
Could not load all ISAPI filters for site/service. Therefore startup aborted.
To correct this error, perform the following steps.
To use IIS Manager to provide the correct path of the AuthFilter DLL (siteauth.dll)
In IIS Manager, right-click the site to update, and then click Properties.
In the Site Properties dialog box, click the ISAPI Filters tab.
On the ISAPI Filters tab, select the AuthFilter filter and then click Edit.
In the Add/Edit Filter Properties dialog box, click Browse, and locate the associated executable file (siteauth.dll).
Click OK.
Encryption
Commerce Server 2009 R2 supports SHA256 as the hashing algorithm for the membership provider and profile system. MD5 is supported for backwards compatibility. If you have used MD5 and are migrating to Commerce Server 2009 R2, change the value of the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\CommerceServer\9.0\Profiles HashVerificationAlgorithmList registry key to SHA256,MD5.