Integrating Microsoft Content Management Server with SharePoint Technologies

1. Integrating Microsoft Content Management Server with SharePoint Technologies 이주원 차장(jwlee@microsoft.com) 기업고객사업본부/PTS Microsoft Corporation

2. Agenda • Microsoft’s portal strategy • Preview of “Spark” Integration Package • What’s next?

3. What Is A Portal? Unified place that connects people to contextually relevant information, services and applications • Delivered by a framework, not a single product • Collection of services and applications • Distinct needs • Shared services

4. Portal Scenarios E-Commerce Sites Publishing Sites Extranet \ Partner Sites Mostly Custom Developed Internet Intranet Information Worker Aggregation Sites Farms of Division, Team & Personal Sites Standalone Sites Shared Site Framework and Tools • Mostly Out-of-Box

5. CMS Publishing Model Pages contain fixed set of placeholders Placeholder controls tightly linked to content Templates provide consistent page structure Personalization via subscriber groups, custom code Framework facilitates site-specific look & feel, structure Browser list is unlimited: useful on public web sites SharePoint Products Collaboration Model Pages contain ad-hoc set of web parts Web parts loosely linked to content Each page can be customized and unique Personalization via audiences, “My Site”, custom code Out of the box look & feel, structure Browser list is limited: implies control over client Content Management Server vs. SharePoint – A Comparison

6. SharePoint ContentManagementServer CommerceServer .NETFramework Content Integration Pack Microsoft .NET Framework • Common platform addresses wide range of portal design patterns • Layered products accelerate most common solution scenarios

7. MCMS/SharePoint Integration Roadmap • Content Integration Pack 1.0 • CMS 2001 & SPS 1.0 • Content Integration Pack 2.0 • CMS 2002 & SPS 1.0 • Next Integration: “Spark” • CMS 2002 & SPS 2003 • First version based on .NET Framework • Richer integration than before • Long-term strategy: • Common control platform • Connectable shared services 2001 2002 2003 –2004 2004 –2005

8. Collaboration Capabilities Content Collaboration • “Spark”: • A MCMS site author wants to include document content from a SharePoint site document library • This document is stored in SharePoint site’s document library, complete with metadata • Once done: • Document rendered as attachment • Properties rendered according to template • Text rendered from other placeholders on the page

9. Integration Scenarios • Publishing Content Management Server content within SharePoint Portal Server portals (NEW!) • Publishing WSS/SPS document library content to Content Management Server sites • Using SharePoint Portal Server Search with Content Management Server

10. Scenario 1: Publishing CMS Content Within Sharepoint Portal Server Rich Web content in SharePoint Portal Server Editing Web content with Content Management Server Web Author

11. Scenario 1: Simplified Architecture Viewing requests Authoring requests SPS/CMS

12. Scenario 1: Larger Scale Viewing requests Authoring requests NLB (For content not Rendered by a MCMS Template, including The MCMS Page Listing Webpart, the SPS cluster can handle the request) NLB (Needed for Authoring And viewing MCMS Postings) SPS Cluster SPS & MCMS Cluster

13. Scenario 1: Spark Web Parts

14. Scenario 1: Publishing CMS Content Within Sharepoint Portal Server • CMS Web Parts • 3 web parts: • Page Listing • Pages Waiting for Approval (like “Approval Assistant”) • Pages in Production (like “Production Assistant”) • Customization • Run-time behavior • CMS Templates with SPS controls

15. Page Listing Web Part Basic View Detailed View

16. Page Listing Web Part • Shows all pages in a specific MCMS channel • Can display pages in multiple views • Support MCMS Live and Edit mode • Allows customization of views • Supports paging, sorting and showing only important pages.

17. Page Listing Web Part CMS Web Part Configuration

18. Other Web Parts • Pages Waiting for Approval • Display pages waiting for your approval. • Allow page approval directly from the Web Part. • Pages in Production • Display pages in production – not published.

19. MCMS Templates with SPS controls • Add SPS controls to CMS Templates for consistent look and feel • Caveat: This feature requires Sharepoint and CMS on the same server(s) CMS Template renders content, authoring console, etc. Sharepoint controls renderSharepoint page elementson the CMS page

20. WSS/CMS Scenario Overview • A CMS site author wants to include document content from a SharePoint site document library

21. Windows SharePoint Services Content Management Server Web Intranet Scenario 2: Publishing WSS/SPS documents to Content Management Server sites Tier 2: Approval and Publishing Tier 1: Workgroup Collaboration

22. A Sharepoint Document Document stored in SharePoint site’s document library, complete with metadata

23. The Published Document Document rendered as attachment Properties rendered according to template Text rendered from other placeholders on the page

24. New Components • SharePoint Document Placeholder Control • SharePoint Document Placeholder Object • SharePoint Document Placeholder Definition Object

25. CMS Placeholder Overview • Placeholder control • Placeholder Object • Placeholder Definition Object

26. SharePoint Placeholder Control • Retrieve SharePoint library content and metadata and stores it in CMS SharePoint placeholder • Documents (e.g., Word, PDF) • Images (e.g., .jpg, .gif) • XML files ( InfoPath and Word ML docs) • Provide UI for locating and accessing SharePoint content at authoring time. • Render document and properties based on style sheets at run-time. • Attachments • Inline display (for images) • HTML (for Word ML and InfoPath-produced XML files)

27. SharePoint Placeholder Control In Authoring Mode

28. SharePoint Placeholder Object • Allow developer direct access to data stored in CMS placeholder in XML: • Meta Properties • URLs to the layout scripts (style sheets). • URL to the document copied to CMS. • XML content of InfoPath or Word ML documents. • Transformed version of the XML content (i.e. HTML). • Transformed version of the meta properties. • Enable template customization without needing to touch the placeholder server control

29. Content Synchronization Tool • A command line executable that updates mapped CMS pages with the corresponding SharePoint documents • Synchronizes all changes or just the “approved” documents • May be scheduled to perform synchronization continually • Generates a report each time it runs

30. MCMS Content Authoring and Staging Environment (includes placeholder server control & placeholder object; WSS) SPS or WSSServer(s) Create Documents Architecture: WSS And CMS MCMS Production Environment Deploy the CMS site Firewall Attach Documents to CMS Pages

31. Notes • Rendering Scripts • one for meta properties and one for the XML content (if applicable) • Rendering output is cached at authoring time • Can be accessed programmatically if needed • Properties and XML document content are rendered by SharePoint Placeholder Control one after the other • No direct editing of the HTML output via the placeholder control

32. Scenario 3: Using SharePoint Portal Server Search with Content Management Server • Including CMS content in enterprise wide searches • Indexing CMS content from SPS • Accessing SPS search Web service from CMS applications

33. Scenario 3: Architecture MCMS Cluster NLB SharePoint Portal Server Search and Indexing Cluster

34. Search • SPS crawls Web content, indexes metatags, and creates full text index • Uses standard http: protocol handler • Special handling for ASP.NET pages • Set CMS site as a HTTP content source • Site path rules for property mapping • URL translation for form-secured content • SPS as search engine on CMS site • CMS server control calls SPS Web service • CMS Authentication filter is used to display results

35. Search Index Gathering

36. Search Components • Meta Tag Control • Convert CMS standard and/or custom page properties into meta tags • Configurable at template design time in VS.NET. • Search Page • Provide user interface for search input parameters • Convert user request into SPS web service calls • Filter search result based on user credential • Display search result

37. Searching from CMS User Request CMS Search.aspx ASP.NET registry and Web.Config Filter SPS Search

38. For More Information… • Main TechNet Web site at www.microsoft.com/technet • Additional resources to support this Session page can be found at www.microsoft.com/technet/tnt1-108

39. Where Can I Get TechNet? • Visit TechNet Online atwww.microsoft.com/technet • Register for the TechNet Flash www.microsoft.com/technet/usingtn/register/flash.asp • Join the TechNet Online forum at www.microsoft.com/technet/itcommunity • Become a TechNet Subscriber at www.microsoft.com/technet/buynow/subscribe • Attend More TechNet Events or view on-linewww.microsoft.com/technet/tcevents/itevents