Conclusion: Integrating SharePoint Portal Server with Content Management Server

Our portal architecture is based on the .NET Framework, with off-the-shelf products providing needed functionality in a modular fashion. For instance, our portal could use the document management features inherent in SharePoint Portal Server. Similarly, we could use Content Management Server for content management and navigation of web pages because it provides more control over the format of web pages with its templates.

How does CMS fit with SPS? Why do we need two products to manage two different forms of content, one for web pages and one for documents? Must users learn two different kinds of authoring?

In short, the answer is that CMS and SPS are designed to do quite different things, and they should be applied where they are most appropriate. For the sake of this discussion, we are focusing on the document management side of SPS rather than its search engine or portal (digital dashboard) capabilities.

The key question is whether the simple content management capabilities provided by SPS are sufficient for your enterprise portal. If the answer is yes, you can simplify your architecture by omitting CMS entirely. That means that you will use SPS to handle all site navigation as well as the content for web pages. You can adopt the standard SPS templates and create custom templates as necessary for the pages you wish to create.

On the other hand, you need CMS if you require any of the following content management capabilities:

• Multiple templates for the same content, such as having the same page served for different devices (PC with browser, Pocket PC). CMS supports this capability.

• Localization of content (multilingual site) . CMS can maintain parallel pages in multiple languages with the same content.

• Built-in routing and approval of content . CMS offers more sophisticated user roles and greater built-in functionality. It also provides simpler ways for an editor to review content in the approval process.

• Integration with Commerce Server . CMS and Commerce Server are tailored to work together. This is important for e-commerce sites.

• Sophisticated page layout . CMS offers much greater control over the appearance and behavior of web pages.

Let's assume that you have determined that you need the capabilities of both CMS and SPS. Here is a way to divide the labor between the products. You can customize this approach to meet your specific requirements (Table 12.6).

Table 12.6. Functions Supported by SPS and CMS in the Integrated Portal

SharePoint Portal Server	Content Management Server
Handle all document management functionality.	Manage static pages.
Allow users self-service creation of ad hoc team web sites.	Handle overall site navigation through CMS channels.
Provide threaded discussion groups.	Routing and approval for content management.
Provide search engine for portal.	Integration with Commerce Server 2002.
Provide MyPage personalization features.	Manage user roles for content managers.

The main integration point between the products lies in navigational links. You can include links to SPS team sites in your CMS channels, for instance, and it is simple to link SPS sites to pages maintained in CMS.

The good news is that both products use SQL Server as their repositories for content and metadata. They also have their own rich tools for building and maintaining sites. Microsoft has hinted that all its server products will be more tightly integrated in the next product wave.