Introduction

In many instances we use ImportWebPart method of the WebpartManager class to import web parts in runtime. If you are using this method to render dynamic content in an anonymous internet facing site using SharePoint there are few points to be noted. Out of the box WebpartManager class expects certain permissions to successfully import a Web part in anonymous mode and the same has been implemented using Code Access Security. Permissions required will not be available in anonymous mode. Following article articulates a design to handle this. Keep reading….

What happens if you use out of the box WebPartManager Class?

Out of the box WebpartManager class works as expected in authenticated mode. If you have the site extended to anonymous mode you can notice that the pages hosting a web part or user control which dynamically hosts another web part instance using ImportWebPart Method will start challenging for credentials. First suspect for this might be to check whether you have published version of the page. After few hours of trouble shooting you may find that all pre-requisites are met and still the pages challenges for credentials. This is due to the fact that the out of box WebPartManager class expects certain permissions in runtime and the same is not available in anonymous mode. Next step is to run the code with Elevated privileges. This will not help the WebPartManager to get the needed permissions.

What’s going on in WebPartManager Class?

As per MSDN  documentation WebPartManger class of SharePoint is designed to be used only in authenticated mode. But the design does not restrict us to extend the same based on our custom requirements. Important sections from the MSDN article.

What's the solution to use this in Anonymous mode?

To overcome the above mentioned limitation we need to create a custom WebPartManager with custom set of permissions. Below mentioned code snippet can be used directly to create the class. I have tested this in a big WCM site and the code has no bugs :)

Custom Web part Manager and Personalization class

   1: /// <summary>

   2:    /// Personalization class

   3:    /// </summary>

   4:    public class CustomWebPartPersonalization : WebPartPersonalization

   5:    {

   6:        /// <summary>

   7:        ///  Importing bool property

   8:        /// </summary>

   9:        internal bool Importing;

  10:  

  11:        /// <summary>

  12:        /// Initializes a new instance of the CustomWebPartPersonalization class

  13:        /// </summary>

  14:        /// <param name="owner">constructor default</param>

  15:        public CustomWebPartPersonalization(WebPartManager owner)

  16:            : base(owner)

  17:        {

  18:        }

  19:  

  20:        /// <summary>

  21:        /// User Capabilities

  22:        /// </summary>

  23:        protected override IDictionary UserCapabilities

  24:        {

  25:            get

  26:            {

  27:                IDictionary userCapabilities = base.UserCapabilities;

  28:                if (this.Importing)

  29:                {

  30:                    userCapabilities[WebPartPersonalization.ModifyStateUserCapability] =

  31:                        WebPartPersonalization.ModifyStateUserCapability;

  32:                }

  33:  

  34:                return userCapabilities;

  35:            }

  36:        }

  37:    }

  38:  

  39:    /// <summary>

  40:    /// Custom Web part manager

  41:    /// </summary>

  42:    public class CustomWebPartManager : WebPartManager

  43:    {

  44:        /// <summary>

  45:        ///  Import web part

  46:        /// </summary>

  47:        /// <param name="reader">reader object</param>

  48:        /// <param name="errorMessage">error message</param>

  49:        /// <returns>web part returned</returns>

  50:        public override System.Web.UI.WebControls.WebParts.WebPart ImportWebPart(System.Xml.XmlReader reader, out string errorMessage)

  51:        {

  52:            ((CustomWebPartPersonalization)Personalization).Importing = true;

  53:            System.Web.UI.WebControls.WebParts.WebPart webPart = base.ImportWebPart(reader, out errorMessage);

  54:            ((CustomWebPartPersonalization)Personalization).Importing = false;

  55:            return webPart;

  56:        }

  57:  

  58:        /// <summary>

  59:        ///  Create Personalization

  60:        /// </summary>

  61:        /// <returns>web part returned</returns>

  62:        protected override WebPartPersonalization CreatePersonalization()

  63:        {

  64:            WebPartPersonalization obj = base.CreatePersonalization();

  65:            return new CustomWebPartPersonalization(this);

  66:        }

  67:    }

Implementation or Usage Code

   1: /// <summary>

   2: /// Method to get the webpart instance based on the web part xml string. XML string passed 

   3: /// to the method should adhere to the schema of the xml used in .webpart file. 

   4: /// </summary>

   5: /// <param name="webPartXml">The web part XML.</param>

   6: /// <returns>WebPart Instance</returns>

   7: private static System.Web.UI.WebControls.WebParts.WebPart GetWebPartInstance(string webPartXml)

   8: {

   9:     StringReader stringReader = new StringReader(webPartXml);

  10:     XmlReader xmlReader = XmlReader.Create(stringReader);

  11:     string errorMessage;

  12:  

  13:     //// Use webpart manager to instantiate the webpart using xml

  14:     //// System.Web.UI.WebControls.WebParts.WebPart wp = WebPartManager.ImportWebPart(xmlReader, out errorMessage);

  15:  

  16:     //// Using custom web part manager with needed permissions to import the web part in anonymous mode.

  17:  

  18:     CustomWebPartManager webPartManager = new CustomWebPartManager();

  19:     System.Web.UI.WebControls.WebParts.WebPart wp = webPartManager.ImportWebPart(xmlReader, out errorMessage);

  20:     //// Set the properties on webpart

  21:     wp.AllowClose = false;

  22:     wp.AllowEdit = false;

  23:     wp.AllowMinimize = false;

  24:     wp.AllowZoneChange = false;

  25:     wp.AllowConnect = false;

  26:     wp.AllowHide = false;

  27:     wp.ExportMode = WebPartExportMode.None;

  28:     wp.ChromeType = PartChromeType.None;

  29:     //// Return the webpart

  30:     return wp;

  31: }

Happing coding :)

https://www.microsoft.com/commerceserver/en/us/white-papers.aspx

Direct Link - https://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=ce5629ad-2473-4c25-8f89-91c8530cd764

Order schema manager is a custom tool to extend Commerce Server Order Schema. Commerce Server order schema is represented through an xml file name OrderObjectMapping.xml. Extending the schema is accomplished by modifying the xml file manually. I thought of automating the process and end up developing the schema manager tool. I use this for extending order schema and found it very useful.

How does the tool work?

Schema manager works on the schema file and allows the developer to extend the default schema. It also allows the developer to compile the schema file to generate the database script file. It internally uses the OrderMapping.exe to compile the schema file. The tool works on some initialization parameters to compile the schema. Initialization parameters are stored in the application configuration file and the same can be modified by the developers in the compiler page. Following are the details about the initialization parameters and its usage.

• OrderMapping.exe
• Dependent assemblies.
• Web.config
• OrderObjectmapping.xml

Supported Features

Managing table definitions

• Creating new tables
• Creating new columns
• Managing Foreign and Primary key constraints
• Adding marshaled data column

Managing Classes /Types

• Creating a new class.
• Changing an existing class to a new one and updating the related information.
• Managing Collection relationships.

Managing Table-Class Mapping

• Create new mapping
• Delete existing mapping

Note

Commerce Server order schema is represented in a tree view and all the operations are initiated through context menus. Right clicking on the nodes will show appropriate menus. Context menus are activated only through mouse clicks and not through key board shortcuts. Current version of the tool doesn't provide an option to manage OrderPipelineMapping.xml (part of order schema).

Happing coding J

OrderSchemaManager.zip

Deploying commerce server profiles is a repetitive task / requirement in many commerce server engagements. Commerce server profile system is extensible and supports various data bases as data stores. Every engagement takes this advantage and extends the profiles based on the project requirement. Question about profile deployment is very common in all the commerce server engagements with some differing profile implementations. Some projects use SQL server as data source and some of them use the combination of SQL & AD. In all these cases, deploying commerce server profiles still stands as a common requirement. While thinking about this, I got the idea of developing a generic deployment tool which can be used across engagements with the support of extensibility to deal with project specifics. Common solutions across implementations  , good old concept of Design Patterns strikes my mind. Very powerful and difficult concept to convince people….. Let's target the problem with design patterns…

Problem statement

Commerce server represents profiles in xml format and provides options to export and import profiles of commerce site. In the development environment we use Commerce Server manager to import or export profiles. Automating this will be great value add in the development life cycle. The tool will also play a very vital role in defining the automated build and deploy process for engagements. Commerce server runtime provides api's to import and export profiles programmatically. The code is very simple and doesn't take much time to implement specific to an engagement. The main idea of this tool is not to deal with the project specifics; instead it should be generalized tool which can be adopted in any commerce server engagements with the provision of extensibility. Let' dive in to the technical specification of the requirement.

Technical Specification

Exporting a profile is very generic and doesn't need any specific code to make it generic. It just expects a site name and output file name. The logic can be directly burned in the tool by getting the above specified parameters. Importing profile is little tricky. Commerce runtime API takes Profile/Bizdata connection string and the profile xml as the input to perform the process of import. The first parameter can be parameterized easily. Second parameter takes the profile xml file path. Every engagement would have implemented different profile data stores in commerce server profiles. Every data source expects certain parameters like connection string, Active directory credentials etc. Basically the xml file content needs to be updated with project specific implementation and then the same needs to be passed to commerce server runtime api's.

I have tailored the observer design pattern to achieve the same. Profile import tool has an initialization file named InitData.xml. Initdata xml represents the initialization data / parameters used by the tool to perform the process of import and export. The xml file also allows the users to specify handler's information. Handlers are nothing but Assembly & Type combination information stored in the initialization file. Before starting the process of import / export, the tool looks into the configured handlers and instantiates the same through reflection and call appropriate interface methods to parse the xml document. I also expect the configured Type to implement the IProfileDocumentHandler interface. Handlers are specific to a partition or data source defined in the profile schema. One Data source can map to multiple handlers. Import tool identifies all the data sources defined in the profile document and searches for the handlers in the initialization file (InitData.xml) and calls the appropriate handlers to modify the xml document. Code to modify the profile xml document is implemented in the handler implementation. This gives us a clean way to isolate import process and project specific information processing. It also gives chance to the implementers to customize the tool to their requirements. Initialization file also allow the users to specify custom initialization or configurable parameters.

Initialization File Format

<?xml version="1.0" encoding="utf-8" ?>

<InitData>

    <!--

     <SiteConnection>

        <SiteName>Commerce Site Name</SiteName>

        <BizConnectionString>

             Profile resouce connection string

        </BizConnectionString>

        <UserName> future use.</UserName >

        <Password></Password>

    </SiteConnection>

    -->

    <SiteConnection>

        <SiteName>Framework</SiteName>

        <BizConnectionString>Provider=SQLOLEDB;Data Source=local-CS;Initial Catalog=Framework_profiles;Integrated Security=SSPI;Network Library=;</BizConnectionString>

        <UserName></UserName >

        <Password></Password>

    </SiteConnection>

    <!--

     <DataSources>

        <Partition name="Commerce User Profile PartitionName">

        User can have there own inititalization paramterd under partition node.

        Same will be passed to the handlers in runtime.

            <connectionString>Target Connection String</connectionString>    

        </Partition>

     </DataSources>

     -->

    <DataSources>

        <Partition name="UserObjectDS">

            <connectionString>Provider=SQLOLEDB;Data Source=(local);Integrated Security=SSPI;Initial Catalog=site_profiles;</connectionString>

        </Partition>

        <Partition name="DataSource1">

            <connectionString> Provider=SQLOLEDB;Data Source=(local);Integrated Security=SSPI;Initial Catalog=site_profiles;</connectionString>

        </Partition>

    </DataSources>

    <!--

     <Handlers>

        <Handler partitionName="Commerce User Profile PartitionName">

            <assembly path ="Assembly Path" type="TypeName" enable="1"></assembly>

        </Handler>

        <Handler partitionName="Commerce User Profile PartitionName">

            <assembly path ="Assembly Path" type="TypeName" enable="1"></assembly>

        </Handler>

    </Handlers>

     Partition Name configured in handlers section should match with the partition name

     in the data sources section.

    -->

    <Handlers>

        <Handler partitionName=" UserObjectDS">

            <assembly path ="<fullpath>Handlers.dll" type="Microsoft.Commerce.ProfileManager.Handlers.ConnectionStringHandler" enable="1"></assembly>

        </Handler>

        <Handler partitionName=" DataSource1">

            <assembly path ="<fullpath>Handlers.dll" type="Microsoft.Commerce.ProfileManager.Handlers.ConnectionStringHandler" enable="1"></assembly>

        </Handler>

    </Handlers>

</InitData>    

SQL Connection String Handler implementation

Connection string handler can be used to handle any data sources which has SQL server as the data store. Handler expects connection string information in the following location in the initdata.xml.

<DataSources>

<Partition name="UserObjectDS">

            <connectionString>Provider=SQLOLEDB;Data Source=(local);Integrated Security=SSPI;Initial Catalog=site_profiles;</connectionString>

        </Partition>

</DataSources>

Handler uses this information to update the connection string information in the specified partition name in the profile document.

Profile Import Tool Usage

CSProfileManager import <Init data file Path> <Profile definition file path>

CSProfileManager export <Init data file Path> <xml file path to export>

Conclusion

Profile import tool can be customized with little dev effort to suit the requirement of a project. Tool provides extensibility based on observer pattern. Created SQL Connection String handler to handle to SQL based data sources. Similarly we can create handlers to handle other data stores like AD etc.

CSProfileManager.zip

    Commerce server provides PUP.exe to automate the process of packing and un-packing a commerce site. Tool has its existence from the days of Site Server. Complete Meta data of a commerce site is managed by pup package. Using the pup package in GUI mode is straight forward and it's quite simple. Every commerce server engagement demands for an automated process to pack and un-pack a commerce server site in an unattended mode. I tried the same in one of my commerce server engagement and tried pup.exe to automate the above process. I faced many hurdles while automating the process and got good support from Commerce Server PSS team in overcoming the hurdles. I would like to share my learning's in this article.

Configuration files

    PUP package can be executed in un-attended / silent mode through a configuration file. Configuration file has complete information about the site to be unpacked. The configuration file doesn't play any role in the process of packing the site.PUP.exe packs the entire site content configured in commerce server manager. Profile resource is driven through an additional configuration file which has the information about the profile schema and profile SQL definition. Following are the list of configuration files expected by pup.exe to run in unattended mode.

Site Configuration File

Site configuration file instructs the packager about the resources and applications needs to be unpacked. Following configuration file can be used to unpack the EmpySite in command line. The same file can be modified to unpack any commerce site through command line. Connection strings specified in the below configuration should be in the same format. PUP.exe expects the connection string only in that format.

[General]

SiteName=GameServiceSetup1

Description=Silent CSharpSite Install with Windows Authentication

NumOfResources= 7

NumOfApplications= 5

Resource0=Product Catalog

Resource1=Transactions

Resource2=Transaction Config

Resource3=Biz Data Service

Resource4=Site CS Authentication

Resource5=Marketing

Resource6=Inventory

Application0=CatalogWebService

Application1=CSharpSite

Application2=MarketingWebService

Application3=OrdersWebService

Application4=ProfilesWebService

NumOfConnStrs= 7

[ConnStrs]

ConnStrResourceName0=Product Catalog

ConnStrPropertyName0=connstr_db_Catalog

ConnStrFriendlyResourceName0=Product Catalog

ConnStrFriendlyPropertyName0=connstr_db_Catalog

ConnStrValue0=Provider=SQLOLEDB;Persist Security Info=False;Integrated Security=SSPI;Initial Catalog=CSharpSite_ProductCatalog;Data Source=localhost;

ConnStrResourceName1=Transactions

ConnStrPropertyName1=connstr_db_Transactions

ConnStrFriendlyResourceName1=Transactions

ConnStrFriendlyPropertyName1=connstr_db_Transactions

ConnStrValue1=Provider=SQLOLEDB;Persist Security Info=False;Integrated Security=SSPI;Initial Catalog=CSharpSite_Transactions;Data Source=localhost;

ConnStrResourceName2=Transaction Config

ConnStrPropertyName2=connstr_db_TransactionConfig

ConnStrFriendlyResourceName2=Transaction Config

ConnStrFriendlyPropertyName2=connstr_db_TransactionConfig

ConnStrValue2=Provider=SQLOLEDB;Persist Security Info=False;Integrated Security=SSPI;Initial Catalog=CSharpSite_Transactionconfig;Data Source=localhost;

ConnStrResourceName3=Biz Data Service

ConnStrPropertyName3=connstr_db_bds

ConnStrFriendlyResourceName3=Profiles

ConnStrFriendlyPropertyName3=connstr_db_bds

ConnStrValue3=Provider=SQLOLEDB;Persist Security Info=False;Integrated Security=SSPI;Initial Catalog=CSharpSite_Profiles;Data Source=localhost;

ConnStrResourceName4=Marketing

ConnStrPropertyName4=connstr_db_Marketing

ConnStrFriendlyResourceName4=Marketing

ConnStrFriendlyPropertyName4=connstr_db_Marketing

ConnStrValue4=Provider=SQLOLEDB;Persist Security Info=False;Integrated Security=SSPI;Initial Catalog=CSharpSite_Marketing;Data Source=localhost;

ConnStrResourceName5=Inventory

ConnStrPropertyName5=connstr_db_inventory

ConnStrFriendlyResourceName5=Inventory

ConnStrFriendlyPropertyName5=connstr_db_inventory

ConnStrValue5=Provider=SQLOLEDB;Persist Security Info=False;Integrated Security=SSPI;Initial Catalog=CSharpSite_ProductCatalog;Data Source=localhost;

ConnStrResourceName6=Marketing

ConnStrPropertyName6=connstr_db_Lists

ConnStrFriendlyResourceName6=Marketing

ConnStrFriendlyPropertyName6=connstr_db_Lists

ConnStrValue6=Provider=SQLOLEDB;Persist Security Info=False;Integrated Security=SSPI;Initial Catalog=CSharpSite_Marketing_Lists;Data Source=localhost;

[Product Catalog]

ResourceFlags=2

PupFlags=1

ProgidPUP=Commerce.CatalogPUP

ResourceType=Catalog

FriendlyName=Product Catalog

[Transactions]

ResourceFlags=2

PupFlags=1

ProgidPUP=Commerce.OrdersPup

ResourceType=Transactions

FriendlyName=Transactions

[Transaction Config]

ResourceFlags=2

PupFlags=1

ProgidPUP=Commerce.OrdersPup

ResourceType=TransactionConfig

FriendlyName=Transaction Config

[Biz Data Service]

ResourceFlags=7

PupFlags=1

ProgidPUP=Commerce.UPMPuP

ResourceType=BizDataStore

FriendlyName=Profiles

GlobalResourceName= (Add new global resource)

[Site CS Authentication]

ResourceFlags=3

PupFlags=1

ProgidPUP=Commerce.AuthPuP

ResourceType=AuthManager

FriendlyName=CS Authentication

GlobalResourceName= (Add new global resource)

[Inventory]

ResourceFlags=2

PupFlags=1

ProgidPUP=Commerce.CatalogPUP

ResourceType=Inventory

FriendlyName=Inventory

[Marketing]

ResourceFlags=2

PupFlags=1

ProgidPUP=Commerce.MarketingPup

ResourceType=Marketing

FriendlyName=Marketing

[CatalogWebService]

ResourceFlags=5130

PupFlags=1

ProgidPUP=Commerce.AddressPuP

ResourceType=Address

FriendlyName=Address

AccessFlags=513

AuthFlags=4

AppIsolated=0

AspCodePage=0

VRoot=CatalogWebService

CSAppName=CatalogWebService

Website=Default Web Site

Machine=localhost

[CSharpSite]

ResourceFlags=10

PupFlags=1

ProgidPUP=Commerce.AddressPuP

ResourceType=Address

FriendlyName=Address

AccessFlags=513

AuthFlags=7

AppIsolated=0

AspCodePage=0

VRoot=CSharpSite

CSAppName=CSharpSite

Website=Default Web Site

Machine=localhost

[MarketingWebService]

ResourceFlags=9226

PupFlags=1

ProgidPUP=Commerce.AddressPuP

ResourceType=Address

FriendlyName=Address

AccessFlags=513

AuthFlags=4

AppIsolated=0

AspCodePage=0

VRoot=MarketingWebService

CSAppName=MarketingWebService

Website=Default Web Site

Machine=localhost

[OrdersWebService]

ResourceFlags=3082

PupFlags=1

ProgidPUP=Commerce.AddressPuP

ResourceType=Address

FriendlyName=Address

AccessFlags=513

AuthFlags=4

AppIsolated=0

AspCodePage=0

VRoot=OrdersWebService

CSAppName=OrdersWebService

Website=Default Web Site

Machine=localhost

[ProfilesWebService]

ResourceFlags=17418

PupFlags=1

ProgidPUP=Commerce.AddressPuP

ResourceType=Address

FriendlyName=Address

AccessFlags=513

AuthFlags=4

AppIsolated=0

AspCodePage=0

VRoot=ProfilesWebService

CSAppName=ProfilesWebService

Website=Default Web Site

Machine=localhost

BizData.ini – Profile specific configuration file

This file needs to be placed in the commerce server installation directory and in the executing directory of pup.exe.

[BizDataSchema]

catalogSchema=catalogSchema.sql

expressionSchema=es_create.sql    

expressionSprocs=es_stored_procs.sql

profileDefs=ProfileSQL_Starter.xml

siteTermDefs=SiteTerms.xml

expressionDefs=ExpressionDefinition.xml

[BizDataStoreFlags]

IsSilentMode=True

[UPM_SQLSource.SQLSource]

IsBizDataStore=True

ProviderString=SQLOLEDB.1;Integrated Security=SSPI;Initial Catalog=StarterSite_Profiles;Data Source=localhost;

schemaDefs=ProfileSQL_Starter.sql

dataDefs=

PUP Log File

Pup.exe creates a log file named pup.log in C drive and logs information to the file during the process of packing and unpacking a commerce site. The information in the file will be of great use for troubleshooting.

Packing a commerce site

Following command should be used to pack a commerce site in command prompt. Execute the below command in Commerce Server Command prompt.

PUP.exe /p /f:<valid siten ame>/i:Config.ini /s:<SiteName>

Config.ini is of no use in the process of packing a commerce site. Pup.exe packs the entire site content. If we are not using the /i: parameter, pup.exe will pop up the UI. To make the packing process silent, we need to use /i: option J

Unpacking a Commerce Site

Following command should be used to un-pack a commerce site in command prompt. Execute the below command in Commerce Server Tools Command prompt.

PUP.exe /u /f:<pup package path> /i:<Full path of the configuration file>/s:<New Site Name>

Sample Automation Tool

I have created a sample automation tool to automate the process of packing and unpacking commerce site. The Batch file takes parameters needed by pup.exe and calls the pup.exe with appropriate parameters. Following are the details about the tool. Automation tool has the configuration file in the Master Template folder with needed place holders. For every environment I have created a separated folder (Test, Staging etc) which contains the following files.

Using Automation Tool

1. Download PUP Automation.zip .
2. Extract the file content to a directory.
3. Exaction process will create the following directories.
   1. Master Template &
   2. Test
4. Use Commerce Server Tools prompt to execute installcommerce.bat with site name as parameter. (Batch file is located in the test directory).
5. Above command will a new commerce site using empty.pup.

Packaging tool limitation

PUP.exe cannot be used to unpack a commerce server site in silent mode which has AD integration in profiles. The same is supported in GUI mode. It's a limitation in the tool.

Conclusion

PUP.exe is the not recommended way to deploy commerce sites in production environment. We need to use staging for the same. This can be used only to setup the initial site and further updates should be done through staging. To set-up the base commerce site pup package is the only option and can be automated with the command line options. Development stage of commerce server engagement demands for the above automation. The above process should be used only in the stage of development.

PUP Automation.zip

In this article I will be discussing about various challenges we face during data migration from CS 2000 to CS 2007. Before getting into the issues let's discuss the basic process involved in the process of data migration. This article covers transactions data migration.

Commerce Server 2007 Migration Wizard:-

Commerce server 2007 comes with a migration wizard to migrate previous versions of commerce server to CS 2007. Commerce server 2007 underwent various design changes in the product. Previous versions of commerce are COM based. Most of the sub-systems in Commerce 2007 have been re-written in managed code. Commerce Server 2007 provides and extensible architecture to extent various sub systems. Commerce Server 2007 wizard works very similar to the runtime architecture. Entire order system of the site has been represented through OrderObjectMapping.xml and OrderPipeLineMapping.xml. Commerce server 2007 wizard follows the same structure to migrate the data from previous version of commerce server.

Various parts of Upgrade wizard:-

Upgrade wizard is a .Net win form application and work based on the configuration files for various configurations. Configuration file stores information very similar to the web.config of the runtime site. It stores information like Order System assemblies and adapter mapping information. Application configuration file store the path of the Storage Mapping File path and Order Migration mapping file. Order Migration mapping file is very similar to the Pipeline mapping file. Migration mapping file maps information between the order Type properties and keys of the legacy system marshaled data.

Migrating Discounts Applied:-

Commerce server 2007 stores various discounts applied information in a separate table. The wizard expects a separate list in the order form header marshaled data for applied discounts. Commerce Server 2000 and 2002 doesn't store information in a list, instead it stores the information in order form header in a flat hierarchy. Due to this design constraint, migration wizard doesn't provide out of box feature to migrate the same. One way to do the migration is through custom SQL migration. For this we need to grab the information from marshaled data to physical columns in the order form header table.

Following are the mapping information about in discounts in the migration mapping file.

<Collection Name="ItemLevelDiscountsApplied" DictionaryKey="_itemlevel_discounts_applied" KeyType="SimpleList" ReferTo="DiscountApplicationRecord" />

<Collection Name="OrderLevelDiscountsApplied" DictionaryKey="_orderlevel_discounts_applied" KeyType="SimpleList" ReferTo="DiscountApplicationRecord" />

Migration wizard expects discounts information in the above specified keys and the same is not available in earlier versions. We need to find the discount related information in the legacy marshaled data and import the same to the SQL tables. Previous version of commerce server stores all the information in blob and also stores some information in tables. Legacy commerce runtime looks in to the keys and checks the same against the target table column list. If the table has mapping columns, runtime will store the data in the appropriate columns. We can use this flexibility to migrate the data from marshaled data to SQL tables. We can create a sample VB application to read the Orders information through commerce API's. After exploring the data through the application, we can create the needed columns in the legacy commerce tables like Order Group, Order Form Header etc. Loading and saving the order back to the system through SaveAsOrder method will force the runtime to do data persistence. After this we can do SQL migration to CS 2007 tables.

Alternatively we can create appropriate lists in the legacy application marshaled data as expected by CS 2007 wizard through a sample VB application.

The same issue is there for Payment methods as well. We need to follow the above steps to migrate the same to CS 2007 

Exploring Legacy marshaled data – CS 2000 PInvoke API

I have created a sample visual basic application to do the discounts and payment methods migration. This application will be very useful to tweak the data stored in the legacy systems.

Migration Helper.zip

https://msdn2.microsoft.com/en-us/library/ms959842.aspx

All other sub-systems are re-written in managed code.