1. Content Channel and Page Providers Magnus Stråle and Paul Smith, EPiServer AB

2. Agenda »Background »SharePoint Connector »Content Channel »Page Providers »Summary

3. Background »Content Channel - Developed as part of SharePoint Connector - A traditional Web service - Import pages and files - Allow one-way updating - Requires configuration - Delivered in EPiServer CMS 5 SP1

4. Background »Page Providers - Full-featured integration - Data resides in original store - Pages only - LocalPageProvider & RemotePageProvider - Requires coding and configuration - A true provider implementation - Sample code - XMLPageProvider

5. SharePoint Connector »Targets Windows SharePoint Services (WSS) »Import data from SharePoint »One-way communication initiated from SharePoint »Handle updated information »No support for access rights »GUI for configuration

6. Content Channel Client »Content Channel designed for custom use »”Roll your own” client »Import Web Service in Visual Studio...and add code

7. Demo »Custom Content Channel Client

8. Page Providers Background »Originated as a technology experiment »You may have heard of Custom Page Store...which has been renamed to Page Providers

9. PageProviderBase Local PPCustom PP Remote PP DataFactory Page Providers Remote EPiServer EPiServer Database

10. Page Providers Implementation »Information maps to/from PageData objects »Information always presented as a local page type »Supports all EPiServer CMS features - Versioning, Multi-language, Access rights, Editing and more »Configuration to support a subset of features »Permanent Link mapping support is required »Move between Page Providers »GUI changes

11. Demo »Page Provider Capabilities »XML Page Provider

12. Remote Page Provider »Old ”Remote site” concept replaced by Remote Page Provider »Remote PP communicates with a Remote Page Provider Service »Service implemented with WCF »Optimized data transfer - No page type overhead - Use TCP/IP transport for maximum perf - Use HTTP transport to cross firewalls »Flexible security model

13. IMPORTANT! »Page Providers use the RemoteSite property of PageReference »Always use complete PageReference objects as parameters »DO NOT simply pass the page ID »When serializing use PageReference.ToString() »When deserializing use PageReference.Parse() or PageReference.TryParse()

14. Summary Content ChannelPage Providers Import data to EPiServer CMS dbData in original store Pages and filesPages only Web serviceAny type of communication Modify data on importAny kind of manipulation Available todayShips with EPiServer CMS 5 R2

15. Questions?