Best Practices for Migrating Site Server 3.0 and Site Server

  • Article
On This Page

Introduction Introduction
Site Server 3.0 Site Server 3.0
Site Server 3.0 Commerce Edition Site Server 3.0 Commerce Edition

April 2000 

Introduction

This document contains a list of activities to help you optimize your system setup for migration to future editions of the software, if you are using Microsoft® Site Server 3.0 or Microsoft® Site Server 3.0 Commerce Edition.

For information about the platform software that is recommended for Site Server 3.0 and Site Server 3.0 Commerce Edition installations, see https://support.microsoft.com/support/siteserver/install/install_ss3.asp .

Site Server 3.0

If you presently use Site Server 3.0, the activities described in this section will make it easier for you to migrate to a different platform, with or without future versions of Microsoft e-commerce software.

Activity

Reason

Programmatically expose attributes or content in the Membership Directory.

Use only a small number of access control lists (ACLs) at root levels, if absolutely necessary. ACL migration is problematic and directory ACLs might not be able to migrate directly to the new platform.

Match content sources to content types.

Site Server 3.0 uses content types (used to handle content creation) and content sources (used in Rule Builder to manage retrieval). The new version of software currently under development at Microsoft uses only content classes. We will migrate Site Server 3.0 content types into the new model. Site Server 3.0 content sources will probably be ignored.
Create a matching content type for every content source that is important to you. This can be done automatically by building them through WebAdmin, since WebAdmin derives content sources from content types.

Use Content Management store as shipped.

Content and schema will be migrated, but Active Server Pages (ASP) and scripts that manage the upload will not be migrated, so do not customize the Content Management store.

Use Monarch language Distributed Authoring Searching and Location protocol (DASL) when writing Search or Knowledge Manager scripts.

Monarch language (DASL) is being included in new versions, but MS Search Object is not.

Minimize use of Rule Builder.

Rule Builder is not being included in new versions for Search, Content Management, or Knowledge Management.

Do not rely on design-time controls (DTCs).

Existing DTC code will not work with the software in new versions; DTCs cannot be used to generate code that is compatible with the new version currently under development at Microsoft.

Do not use secondary Active User Objects (AUOs).

There is no aggregation capability in Collaboration Data Objects (CDOs) (used by the newer version: Search, Content Management, and Knowledge Management).

Site Server 3.0 Commerce Edition

If you presently use Site Server 3.0 Commerce Edition, the activities described in this section will make it easier for you to migrate to the next version of Microsoft e-commerce platform software.

Activity

Reason

Instantiate AUO in server-side Includes.

Instantiation syntax might change. Instantiating AUO in server-side Includes will minimize the impact of syntax changes.

Instantiate Ad Server in server-side Includes.

Instantiation syntax might change. Instantiating Ad Server in server-side Includes will minimize the impact of syntax changes.

If you are making several calls to the same set of pages or contexts, place the calls in an Include file.

Ad Server calls might change. Placing Ad Server calls for the same context/page group in server-side Includes will minimize the impact of syntax changes.

Use the property methods of the IADs interface.

Use the property methods of the IADs interface to AUO because its syntax will be supported in the User Profile Object.
For more information about the IADs property methods, see the MSDN online library at: https://msdn.microsoft.com/ .

Programmatically expose attributes or content in the Membership Directory. If possible, avoid the use of ACLs in the Membership Directory.

Use only a small number of access control lists (ACLs) at root levels, if absolutely necessary. ACL migration is not possible.

Isolate and minimize the use of Site Vocabulary.

Site Vocabulary functionality operates on a different paradigm in the next version of the e-commerce platform. Site Vocabulary was a hierarchical representation of a taxonomy; the new data storage model uses simply an enumerated list.

Isolate and minimize the use of Rule Builder.

Evaluation of business rules in the newer version of an e-commerce platform currently under development at Microsoft operates on a different paradigm from Rule Builder.
Rule Builder built Active Server Pages (ASP) code that took the rules entered and codified them as ASP pages.
The new paradigm involves storing expressions, which are evaluated by the expression evaluator at run time. Results from expression evaluation can be used to drive logic within ASP pages.

Save old usage log files.

If you use historical log file information, save the old usage log files. You will be able to re-import them into the new analysis engine incorporated in the next version of Microsoft's e-commerce platform software.

Do not rely on design-time controls (DTCs).

Existing DTC code will not work with the software in new versions; DTCs cannot be used to generate code compatible with new versions of the e-commerce platform software.

New sites should not use Distributed Password Authentication (DPA) for authentication.

DPA will not be available in new versions of the software.