16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

1114 Part XI: Upgrading <strong>and</strong> Migrating to SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong><br />

Upgrading to SharePoint Portal Server 2003<br />

If you want to move from SharePoint Portal Server 2001 to SharePoint Portal<br />

Server 2003, consider the following changes:<br />

■ The architecture has changed considerably. For example, you can now use<br />

SharePoint Portal Server 2003 in a server farm configuration. Also, all site content<br />

is now stored in the content databases instead of in the Web Storage System,<br />

<strong>and</strong> configuration data for a server or server farm is stored in the configuration<br />

database. For more information about the new architecture, see Part 2, “Share-<br />

Point <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> Architecture.”<br />

■ The security model has changed, not only concerning the security settings at<br />

the document library level, but also the ability to secure Web Parts. For more<br />

information about the new security model, see Chapter 6.<br />

■ There are many new features, some changed features, such as versioning, document<br />

profiling <strong>and</strong> metadata, <strong>and</strong> some features that no longer exist in the<br />

new version, such as approval routing if you do not install the backwardcompatible<br />

document library. For more information about features included in<br />

SharePoint Portal Server 2003, see Chapter 1.<br />

This section will detail the upgrade process, migrating Web Parts, <strong>and</strong> migrating<br />

document library content.<br />

The upgrade process does provide you with certain advantages, such as<br />

the ability to link existing SharePoint Portal Server 2001 deployments into your new<br />

navigation hierarchy <strong>and</strong> continuing to use your digital dashboard applications on<br />

the SharePoint Portal Server 2001 machines. The upgrade process for a server running<br />

SharePoint Portal Server 2001 is similar to the upgrade process for a server running<br />

SharePoint Team Services. You will first have to decide how you wish to use the<br />

updated features. In most cases, the SQL Server content store is a better choice<br />

because the SQL Server content store provides fast database performance, manageability,<br />

scalability, <strong>and</strong> the familiar SQL Server administrator tools. However, if you<br />

wish to retain the ability of multiple document profiles per document library folder<br />

as well as the complex routing <strong>and</strong> approval workflow features of the document<br />

store from SharePoint Portal Server 2001, you will need to install the backwardcompatible<br />

document library. Also, you will need to consider reviewing any application<br />

you have developed that integrates with SharePoint Portal Server 2001 <strong>and</strong> uses<br />

the Publishing <strong>and</strong> Knowledge Management Collaboration Data Objects (PKMCDO)<br />

interface to the Web Storage System.<br />

If you decide that you wish to install the backward-compatible document<br />

library, to host the documents from your SharePoint Portal Server 2001 installation,<br />

you will need to run the in-place upgrade process. This process converts <strong>and</strong> retains<br />

the contents of the SharePoint Portal Server 2001 Web Storage System to the Share-<br />

Point Portal Server 2003 backward-compatible document library. If you do not wish

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!