Welcome to BARMAGY Sign in | Join | Help

Mapping MCMS 2002 APIs to SharePoint Server 2007

Summary: The services previously provided by Microsoft Content Management Server (MCMS) 2002 are now provided by Microsoft Office SharePoint Server 2007. SharePoint Server is built upon Microsoft Windows SharePoint Services (version 3). This article helps you determine how the MCMS Publishing API (PAPI) maps to an equivalent but different Publishing API in SharePoint Server 2007. (33 printed pages)

Introduction

Many of the tasks involved in the development of a Web site are related to customizing it for particular business needs. Some of these customizations are related to the site appearance and some to the functionality provided by the Web site. In Microsoft Content Management Server (MCMS) 2002, the developer had to perform most of these tasks by using the MCMS Publishing API (PAPI), which provides access to the underlying MCMS object model.

By default, Microsoft Office SharePoint Server 2007 provides significant Web content publishing features; most tasks that required custom code in MCMS can be accomplished by configuration of existing capabilities and do not require custom code. A powerful Publishing API is always available for tasks that require special customizations. This article helps you determine how the MCMS PAPI maps to an equivalent but different Publishing API in SharePoint Server 2007.

Office SharePoint Server 2007 is built on Microsoft Windows SharePoint Services (version 3). As a result, many Windows SharePoint Services features are exposed by default, and the infrastructure allows customization to be performed without any coding. However, there are business scenarios where you may need extended customization.

Due to the technology shift, a new API has been created for SharePoint Server 2007 to work together with Windows SharePoint Services V3. The managed and COM-based APIs in MCMS 2002, including the site deployment API, have been entirely replaced by managed code.

This article is organized by MCMS 2002 concepts. Each section compares the MCMS topic to the equivalent topic in SharePoint Server 2007 or Windows SharePoint Services.

This article does not address configuration or step-by-step instructions for SharePoint Server, but instead points to the object model classes so you can learn where to look for more information.

Read More

Published Saturday, January 27, 2007 8:47 PM by shadiesm

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# re: Mapping MCMS 2002 APIs to SharePoint Server 2007

Tuesday, July 19, 2011 10:08 AM by Chynna
Well done atircle that. I'll make sure to use it wisely.

# re: Mapping MCMS 2002 APIs to SharePoint Server 2007

Wednesday, July 20, 2011 11:23 AM by axtltq

# re: Mapping MCMS 2002 APIs to SharePoint Server 2007

Friday, July 22, 2011 12:09 PM by sekhcikxtps

# re: Mapping MCMS 2002 APIs to SharePoint Server 2007

Saturday, August 13, 2011 10:51 PM by Xaria
I feel satisfied after redanig that one.

# re: Mapping MCMS 2002 APIs to SharePoint Server 2007

Sunday, August 14, 2011 4:14 PM by Emma
I really cudoln't ask for more from this article.

# re: Mapping MCMS 2002 APIs to SharePoint Server 2007

Monday, August 15, 2011 2:30 PM by mtrrrqdv

# re: Mapping MCMS 2002 APIs to SharePoint Server 2007

Wednesday, August 17, 2011 4:34 PM by cdhawk

# re: Mapping MCMS 2002 APIs to SharePoint Server 2007

Wednesday, January 16, 2013 4:47 PM by Suenia
The Blackberry, like every cell type of device polls.  But it does not mean what you deicrsbe.  The polling that takes place is a  keep-alive  type of data packet.  The purpose is to let the network know where the phone is located physically on the network at any given time.  As a user moves from place to place the cell towers keep a record of those movements so that when you want to make a call or send data of any type you will already be connected and ready go.  This is how you get an  always on  connection.The polling intervals vary by providers but they are generally constant IE every so many seconds or nanoseconds.If the network receives a piece of data destine for your device, the network sends the data immediately after it arrives.  The network does not wait for any length of time beyond the time it takes to forward the message.  There can be delays caused by no or poor signal in which case the information is stored until the connection is restored and is then downloaded.

What do you think?

(required) 
required 
(required)