quote:

---

> Hi Angel,
>
> Site server has its own LDAP service, the data is stored in either
> SQL db or Access mdb files, which can be migrated to the SQL2K used
> by Commerce 2002(users' data also can be migrated to Active
> Directory). Commerce 2002 has its new components, all the pages
> html/asp in SS3 will no longer be used. If you have coustom pages on
> SS3, generally most of them need to be redeveloped.
>
> Here is the migration white paper which prbably you've reviewed:
> Migrating from Site Server to Commerce Server 2002
> http://www.microsoft.com/commercese...ment/2002/wp_ss
> cemigration.asp
>
> The following is a process summary about migrating Site Server 3.0
> CE(Commerce Edition) to Commerce 2002.
> "
> Migration ProfileBuilder Tool
>
> http://msdn.microsoft.com/library/d...ary/en-us/csvr2
> 002/htm/cs_gs_membershipmigr_ggdh.asp
>
> Use the Migration ProfileBuilder tool to map attributes from the
> Microsoft Site Server 3.0 Membership Directory to the Commerce Server
> Profile data store.
>
> When you run the Directory Migration tool, it reads an Extensible
> Markup Language (XML) file that maps the user attributes from the
> Membership Directory to the Profiles data store(s).
>
> The Migration ProfileBuilder tool performs the following tasks:
>
> Reads user attributes from the Membership Directory schema
> Reads user attributes from the User Profile Object schema
> Creates the XML configuration file read by the Directory Migration
> Tool
>
>
> Starting the Migration Process
>
> http://msdn.microsoft.com/library/d...ary/en-us/csvr2
> 002/htm/cs_gs_membershipmigr_ggdh.asp
>
>
> To begin the migration process, deploy the migration objects to the
> servers that will be running the migration process. Follow these
> steps:
>
> Extend the attributes for members by creating a Migration attribute
> in the Membership Directory.
> Create at least one migration profile using the Migration
> ProfileBuilder tool. You will need to create one for each type of
> migration in your plan (batch and on-demand combined).
> To deploy the objects you will need to copy the completed migration
> objects to each server and register the objects. For more
> information, see Register Migration
> Objects.
> You will also need to make sure that the registry keys are set
> appropriately. For more information, see the Requirements section of
> MigrationLogObj Object.
> If you plan on migrating users with on-demand migration as they log
> into your new site, you will want to install the migration objects on
> the Web servers and use the
> Login.asp file found in the <drive>:\Program Files\Microsoft Commerce
> Server\SDK\Tools\SSCE Migration\Membership\Client directory. Use this
> file as a sample of how to trigger a migration when a user first
> visits your new Commerce Server site.
>
> If you want to migrate all of your users together, install the
> migration objects on the server from which you will migrate all of
> the users. For best performance, choose a computer that is dedicated
> to the migration process. When you build the profile for migrating a
> range of users using the Migration ProfileBuilder tool, establish a
> filter depth, a search scope, and a search filter base, by using the
> dialog box in step 3. Experimenting with different values before
> beginning the actual migration process allows you to optimize
> migration performance. Note that the distribution patterns of user
> account names in the Membership Directory play an important role in
> the tuning process.
>
> Always test the on-demand migration process before putting it into
> production
>
>
> ----------------------------------------------------------------------
>
> There are two uesful resources available for migrating customers from
> Site Server to Commerce 2002:
>
> 1. The SDK has included tools for migrating Membership users
> information for use in Commerce Server. These were shipped with
> Commerce 2002.
>
> http://msdn.microsoft.com/library/d...ary/en-us/csvr2
> 002/htm/cs_gs_membershipmigr_oaak.asp
>
> 2 A MS internal Toolkit - SStoCS2002MigrationKit has been released
> for Microsoft Consultants to help customers migrate successfully.
> The migration toolkit contains customizable scripts to help partners
> and Microsoft professionals migrate 7 parts of a Site Server Commerce
> Edition site.
> These are: ads, departments and products, groups, users,
> distribution lists, transaction data, and SSCE vocabulary. The
> toolkit also contains PAG to help you
> successfully migrate a SSCE site to a CS2002 site. There are
> additional tools provided...
> "
>
> Due to the potential risks in the migration scenario and the Toolkit
> isn't released for public downloading, the best way to perform this
> type of migration is with MCS (Microsoft Consulting Services). They
> have the lastest and full version toolkit which when modified will be
> able to successfully complete this migration. Using the tools
> included with the Commerce Server 2002 installation SDK folder are
> just used to test a migration or complete a small, very basic
> migration. So I believe MCS with their migration Toolkit scripts is
> the best way to go for this task.
>
> Best regards,
>
> WenJun Zhang
> Microsoft Online Support
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Get Secure! - www.microsoft.com/security
>

---