Sharepoint 2010_logo_2010.jpgSure SharePoint 2010 (newssite) has built in web content management capabilities. But that doesn't stop of number of WCM vendors from integrating their own solutions with the collaboration platform. After all, we all need options.

Before we get started, I just want to remind you that we are talking about Web Content Management solutions that integrate with SharePoint and how they have done it. We aren't discussing Enterprise Content Management. And if you don't see your name in the list, let me know via the comments. I am interested to hear your integration story.

It's interesting to note that with one exception, all the options discussed below have not yet -- at least officially -- said their connector solution works with SharePoint 2010. However, considering the connectors leverage SharePoint Web Services, and the APIs haven't changed significantly, it's only a matter of time.

Day Software

Of all the vendors we mention in this article, Day Software is the only non Microsoft Web CMS vendor to provide a SharePoint connector (yes, we know Alfresco does as well, but we aren't talking about ECM).

The SharePoint Connector 2.0, is part of the Day CRX Connectors family. It is a JCR Connector for SharePoint 2007, but with CMIS now official, it is also available as a CMIS connector. 

The connector provides the following capabilities, utlitizing SharePoint web services:

  • Read and write content and metadata to and from SharePoint
  • Excecute queries on SharePoint
  • Conforms to security settings on SharePoint content
  • Recognizes changes made to content within SharePoint


The integration between Day and SharePoint is so seamles that you can actually drag and drop content that resides within SharePoint to content you are developing within the Day content management system. 

This connector is for SharePoint 2007.


The SharePoint Connector for CMS400.NET has been around in some form since 2008. It is integrated into the menu system within SharePoint.

The connector includes a wizard that walks you through the steps to publish your SharePoint documents to a CMS400.NET website (whether it's an intranet, internet, extranet). The wizard will ask you where within the Etkron CMS400.NET folder structure you want your document to be placed. You must then specify the metadata and categories for that document within the website. It doesn't look like it pulls any of the metadata already associated with the document within SharePoint.

A physical copy of the document is copied into that structure and a link is retained to the original version in SharePoint. You can delete the website copy if you want place the document into a different folder structure. If you update the document within SharePoint you need to re-publish it to the website to ensure the latest version shows up there.

The connector currently works for SharePoint 2007.


Called EPiServer Connect for SharePoint, the connector provides three features: 

  2. File Integration
  3. CMS Content in SharePoint

EPiServer Connect for SharePoint

Publish to EPiServer CMS: With this connector you can push documents, files and SharePoint list items to EPiServer, using predefined CMS channels. Again the content is copied directly into the Web CMS (a one way push) and the content pushed is read-only.

File Integration: If you want two way integration, you use the File Integration feature. This will enable you to manage content stored in SharePoint directly within the EPiServer CMS. Capabilities include add, edit, delete and read. Versioning is supported with this feature and you automatically get access to the most recent version of the document within your website when its updated in SharePoint.

SharePoint Web Parts: The third way to integrate your EPiServer CMS with SharePoint is through Web Parts. EPiServer provides several out of the box web parts that enable you to display EPiServer content within SharePoint. So you can do things like show a list of content or show a particular piece of content. The Web Parts are configurable and customizable.

EPiServer Connect for SharePoint works for SharePoint 2007, both MOSS and WSS. 


The Kentico Connector for Microsoft SharePoint is another option. Similar to Ektron, you manage your content within your SharePoint environment and then push it to your Kentico website.

Kentico leverages SharePoint Web Services to display SharePoint content -- lists, document libraries, pictures, etc -- inside a Kentico website. The connector includes two web parts for Kentico: SharePoint Data Viewer and SharePoint Data Source that you configure to display the appropriate SharePoint content.


The connector works with any edition of Kentico and is currently available for SharePoint 2007, MOSS or WSS3.0. 


SDL has also offered a SharePoint connector for SharePoint 2007 for a while now. This connector is called the SDL Tridion Connector for SharePoint

You create your documents within SharePoint, going through the approval process and then them pushed to SDL to enter the SDL publishing lifecycle.


You can also push content that is created within SDL to SharePoint using a custom web part. All SDL content displayed in the web part is available in SharePoint search.

In addition, Web Parts (SDL Tridion Publishing queue and Workflow Web Parts) are available for SDL Administrators so that they can view and manage their marketing activities within SharePoint. 


 Appropriately called the SharePoint Connector Module, Sitecore's connector is said to work with both SharePoint 2007 and SharePoint 2010.

Sitecore Connector Module for SharePoint

The connector enables a two way synchronization of documents and other SharePoint assets between SharePoint and a Sitecore website. The connector exists within Sitecore where you configure your SharePoint datasources and map Sitecore data templates to SharePoint content. This makes SharePoint content look and act like native Sitecore content. Data is displayed real-time, so the most recent version of content is always displayed within the Sitecore website.

And a Few Others

A few other Web CMS integrations we've mentioned before: