_
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 Site Server 3.0 or Site Server 3.0 Commerce Edition.
If you presently use Site Server 3.0, the activities described in this section will make it easier for you to migrate to a Tahoe/Plutonium platform.
| 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). Tahoe 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 can’t be used to generate Tahoe-compatible code. |
| Do not use secondary Active User Objects (AUOs). | There is no aggregation capability in Collateral Data Objects (CDOs) (used by Tahoe–Search, Content Management and Knowledge Management). |
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 a Plutonium platform.
| 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 Active Directory Services Interface (ADSI) calls. | Use ADSI interface to AUO because its syntax will be supported in the User Profile Object. |
| Isolate and minimize the use of secondary AUO providers. | The syntax for accessing secondary AUO providers is changing to a model that uses table-driven entries. Scripts will no longer be required to call out the legacy database name. |
| 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. |
| Isolate and minimize the use of Site Vocabulary. | The new Site Terms store operates on a different paradigm from Site Vocabulary. Site Vocabulary was a hierarchical representation of a taxonomy; Site Terms is simply an enumerated list. |
| Isolate and minimize the use of Rule Builder. | Expression Builder operates on a different paradigm from Rule Builder.
Rule Builder built Active Server Page (ASP) code that took the rules entered and codified them as ASP pages. Expression Builder stores expressions, which are evaluated by the expression evaluator at run time. Based on the results of the expression evaluator, an ASP page is built on the fly and based on the business rules codified in the expressions. |
| Save old usage log files. | If you use historical log file information, save the old usage log files. You will have to re-import them using a tool that will ship with Plutonium. |
| Do not rely on design-time controls (DTCs). | Existing DTC code will not work with the software in new versions; DTCs can’t be used to generate Plutonium-compatible code. |
| New sites should not use Distributed Password Authentication (DPA) for authentication. | DPA will not be available in new versions of the software. |
Information in this document, including URL and other Internet web site references, is subject to change without notice. The entire risk of the use or the results of the use of this resource kit remains with the user. This resource kit is not supported and is provided as is without warranty of any kind, either express or implied. The example companies, organizations, products, people and events depicted herein are fictitious. No association with any real company, organization, product, person or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.
© 1999-2000 Microsoft Corporation. All rights reserved.
Microsoft, Windows and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A. and/or other countries/regions.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.