Share via

Run the Migration ProfileBuilder Tool

  • Article

After you have set up your Commerce Server profiles and modified your migration objects as required, you can run the Migration ProfileBuilder tool to generate the migration Extensible Markup Language (XML) file.

This topic contains:

  • Compiling Migration ProfileBuilder Tool

  • Mapping Attributes from Membership Directory to Profiles Data Store

Compiling Migration ProfileBuilder Tool

If you need to modify the Migration ProfileBuilder tool, you can access the source code in the following folder:

<Drive>:\Program Files\Microsoft Commerce Server\SDK\Tools\Membership Migration\ProfileBuilder

The application images were built using Microsoft Visual Basic 6.0 Professional.

After you modify the Migration ProfileBuilder tool, you must create a Data Source Name (DSN) for the Commerce Server Profiles data store using the Data Sources (ODBC) manager found in Programs | Administrative Tools on the Start menu. Create a System DSN using the SQL Server driver. Ensure you change the default connection string to point to the correct Profiles data store (for example, Retail_commerce).

Mapping Attributes from Membership Directory to Profiles Data Store

To run the Migration ProfileBuilder tool, the server running the tool must be able to access both the Membership Directory Lightweight Directory Access Protocol (LDAP) server and the Commerce Server computer running the ProfileService object.

To run the Migration ProfileBuilder tool

  1. In Windows Explorer, navigate to the folder that contains the Migration ProfileBuilder tool, and then double-click ProfileBuilder.exe.

  2. In the Step 1 dialog box, do the following:

    Use this To do this
    Location to store all of the profiles Type the directory that contains the XML files used by the MigrationMainObj object. Usually, you will use only one XML file.
    XML file name Type the name of the file to be generated. The Migration ProfileBuilder tool appends a profile ID to the end of the name. In this sample, the files will be named "migration"<n>.xml where 'n' is incremented each time a profile is generated.
    ProgID of IMigrationRead Type the ProgID of the MigrationReadObj object. This default is generated by the included source code.
    ProgID of IMigrationWrite Type the ProgID of the MigrationWriteObj object. This default is generated by the included source code.
    ProgID of IMigrationModify Type the ProgID of the MigrationModifyObj object. This default is generated by the included source code.
    ProgID of IMigrationLog Type the ProgID of the MigrationLogObj object. This default is generated by the included source code.

  3. In the Step 2 dialog box, do the following:

    Use this To do this
    Membership Directory Server Type the Netbios name of the Membership Directory.
    Port Number Type the port number of the Membership Directory instance.
    MD User Name Type the distinguished name of the user for the connection to the Membership Directory.
    Password Type the password for the Membership Directory User Name given in the MD User Name box.
    Server Name Type the name of the SQL Server running the Commerce Server Administration database.
    Database Name Type the name of the database where the Profiles store is located.
    DBA Name Type the login of the user who has system administrator (sa) privileges.
    DBA's Password Type the password of the login user.

  4. In the Step 3 dialog box, do the following:

    Use this To do this
    Migrate MemberOf Determine whether the migration object reading this XML file will migrate users to Active Directory groups.
    Object Schema Type the schema representing the user to be read, for example, member. You can type in other custom classes if they are to be migrated.
    Filter Depth Type a number to specify how fine a search is requested. This is provided as a mechanism for preventing LDAP query time-outs. A filter depth of 2 will search cn=xx*. A filter depth of 3 will search cn=xxx* ("x" = [a-z, 0-9]).
    Search Scope Select the depth to which the tool can search sub-containers under the root from the drop-down list.
    Search Filter Base Type a prefix for account names to be migrated in batch mode (for example, cn=a).

  5. In the Step 4 dialog box, do the following:

    Use this To do this
    Group's parent RDN Type the Active Directory Relative Distinguished Name (RDN).
    AD Administrator's User Name Type the account to log in as when writing to Active Directory in the form of "domain\account."
    AD Administrator's Password Type the password for the account named in the AD Administrator's User Name box.
    Catalog Select the profile catalog to use. Typically this is Profile Definitions.

  6. Map the attributes to be read to those to be written. You can control the objects listed in the right pane by selecting the profile definitions from the top list boxes. To create an association, click the attribute in the Site Server box and then click the corresponding attribute in the Commerce Server box.

    The numbers on the left of the attributes indicate the mapping (for example, 49 Telephone Number = 49 tel_number).

    The following figure shows attributes mapped from the Membership Directory to the Commerce Server Profiles data store.

    Ee823382.cs_gs_membershipmigr_pb4(en-US,CS.10).gif

  7. When you are finished mapping the attributes, click Preview.

    The Step 5 dialog box displays the entire XML file.

  8. If the XML file is complete, click Yes.

The XML file is saved.


All rights reserved.