SharePoint

MirrorNG Integration

The SharePoint side of MirrorNG is powered by ActiveSP; more information on ActiveSP is available here.

The list of supported SharePoint features is located here.

We are integrating ActiveSP with MirrorNG to enable us to browse, transform and move data to and from SharePoint. Transformations will take a prime role in the function of MirrorNG when we start to exchange content between systems with very different data models such as SharePoint and Documentum. Just as with ActiveDCTM, the requirements for accessing SharePoint are very light; we need an account for authentication and access to the web services.

Scenarios

Importing content in a SharePoint repository

Many companies are drawing the SharePoint card, but they often have a large body of existing documents that they want available in their new SharePoint.

If you want to keep using your old systems such as a file system, SAP system, or Documentum system, MirrorNG can make the documents available in SharePoint too, and keep those documents up-to-date as time goes by.

If you want to decommission your old systems and move all content over to SharePoint, MirrorNG can do the migration for you. Due to MirrorNG’s architecture, the old systems can still be used while the migration is ongoing so you need nearly no down time and all your content will be available in SharePoint right away.

Enabling smart content in SharePoint

SharePoint together with its integration with Microsoft Office provides a host of possibilities, but this is difficult to exploit in a vanilla SharePoint installation. Custom development on SharePoint is possible, but usually not very convenient and maintainable. MirrorNG can enable you to exploit the new possibilities of the Office – SharePoint combo to make your content truly smart.

Create site templates and retroactively update them afterwards

SharePoint has the concept of site templates that allows creating sites, subsites, lists, etc from a template, allowing to quickly set up multiple sites. In practice, these templates do not work as well when your sites are not alike, or if you want to design the templates outside SharePoint. Moreover, changing a template does not change all sites that were created based on this template. This means that incremental additions and changes need to be applied by hand.

With MirrorNG, this is no longer needed. As sites, lists, etc are just objects, MirrorNG can synchronize them with a set of source templates.