0
Architecting Enterprise Content Management: Internal and Customer-facing Solutions<br />Benjamin Lee, Jason Deere, Denise ...
Introduction<br />Presenting two separate implementations<br />Continental.com customer-facing CM<br />How we structured m...
The Challenge: Static Content Each of 17,000 pages is updated separately<br />
The ChallengeProblems with the Old Workflow<br />Serial and manual process<br />Can’t preview till near the end <br />No t...
The ChallengeThe Old Workflow<br />
The ChallengeWhat Led Us To SharePoint<br />Needed a structured Content Management System (CMS)<br />Tried a leading, larg...
The SharePoint SolutionThe Enterprise Vision<br />Content pieces not pages<br />Stored as simple html in ListItems<br />Ea...
The SharePoint SolutionProblems Resolved<br />Teams can work in parallel<br />Content approvers can preview how page will ...
The SharePoint SolutionThe New Workflow<br />new workflow<br />old workflow<br />
SharePoint/ASP.NET Merged Publication<br />Jason Deere & Benjamin Lee<br />Continental.com Team<br />demo <br />
The Content Management SiteUser Interface<br />
The Content Management Site”Pieces” are Stored in List Items<br />
The Content Management SiteInstant Preview<br />Site Actions<br />/web Asset<br />SharePoint CQWP<br />
The ImplementationThe Challenges <br />Out of Box functionality did not meet our need for content management to co-exist w...
Merging MOSS and ASP.NETKey Points That Make This Possible<br />Virtual Directories<br />What MOSS doesn’t know, won’t hur...
Merging MOSS and ASP.NETWhat MOSS doesn’t know…<br />Virtual Directories<br />Create under your MOSS Web Application<br />
Merging MOSS and ASP.NETConfiguring Your SharePoint Site Structure<br />Key is to make your top MOSS sub-site and your vir...
Merging MOSS and ASP.NETRouting Network Traffic<br />Router makes decision based on sub-site URL<br />http://domain/cms/my...
Merging MOSS and ASP.NETSharing Application Code and Assemblies<br />Allowing SharePoint to access existing business logic...
Merging MOSS and ASP.NETWhat You Need to Make Your External ASP.NET Master Page Work with SharePoint<br />“Minimal” master...
Merging MOSS and ASP.NET Override Master Page On Load<br />public class PublishingLayoutBase : PublishingLayoutPage<br />{...
Merging MOSS and ASP.NETUsing Your Master Page and User Controls in MOSS Page Layouts<br />&lt;%@ Page language=&quot;C#&q...
Merging MOSS and ASP.NETVoila!<br />Site Actions<br />/web Asset<br />SharePoint CQWP<br />
Internal Content Management: The Process of Building the ECM Structure<br />Denise Wilson<br />Senior Manager, Technology<...
Internal Content ManagementThe Problem Set<br />User e-mailed attachments as ‘workflow’<br />No single version of the ‘tru...
Internal Content ManagementThe Evolution of the Solution<br />Started by evaluating one group in-depth<br />Enterprise Eng...
Internal Content ManagementThe Tools<br />How did SharePoint help us do this?<br />Automated review processes with workflo...
Automated Review Process<br />SharePoint Designer Workflows<br />
Naming Standards<br />Result in Normalized Docs and Devices<br />
Standardize Content Types<br />Groups of metadata (site columns)  <br />
Document Information Panel<br />Dropdowns promote standardization <br />
Display Data By Location (Filter)<br />Before data view, had to fly engineer to the site<br />
Slice and Dice Normalized Data<br />Virtual Earth<br />Ref: Blogs by Jon Campbell and Greg Chan of SharePoint Designer Tea...
Slice and Dice Normalized Data<br />Drill Down<br />
Understanding Collective NeedsWhat We Learned From Each Group<br />Continental Board Meeting Minutes<br />Management is di...
Evolution of the Process System Operations Coordination<br />Phase I: E-mail to document libraries<br />‘E-mail enabled’ A...
System Operations Coordination<br />Phase I: E-mail enabled document libraries<br />Phase II: Push alerts from SharePoint ...
Evolution of the ProcessEngineering is two of six project phases<br />Integration of the other four: <br />Content types, ...
Integration of the EnterpriseBuilding Content Management Structure<br />
Integration of the EnterpriseStructured Sites, Content Types and Metadata<br />Standardization <br />Get consensus / decis...
Integration of the EnterpriseStructured Sites, Content Types and Metadata<br />Department by Department <br />Site Collect...
Integration of the EnterpriseRefined Search Scopes<br />Free-text search yields 8448 results<br />
Integration of the EnterpriseRefined Search Scopes<br />Search by Content Type (Systems EWO) Yields 22 results<br />
Continental Airlines Enterprise Content Management<br />Questions?<br />
Remember to fill out your evaluations onMySPCfor your chance to win two HD web cams and a designer mouse (3 prizes awarded...
Learn More about SharePoint 2010<br />Information forIT Prosat TechNet<br />http://MSSharePointITPro.com<br />Information ...
© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be...
Sharepoint conference 3 - continental
Upcoming SlideShare
Loading in...5
×

Sharepoint conference 3 - continental

1,061

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,061
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
19
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Sharepoint conference 3 - continental"

  1. 1. Architecting Enterprise Content Management: Internal and Customer-facing Solutions<br />Benjamin Lee, Jason Deere, Denise Wilson<br />Senior Managers, Technology<br />Continental Airlines<br />
  2. 2. Introduction<br />Presenting two separate implementations<br />Continental.com customer-facing CM<br />How we structured metadata and workflow to reduce a 2-month content approval process to 2 days<br />How SharePoint lives in the same web app space and feeds modular content to Continental.com<br />Continental enterprise document CM<br />How we developed a process to build our structure so that users can tag files with metadata so we can find them with filtered search<br />
  3. 3. The Challenge: Static Content Each of 17,000 pages is updated separately<br />
  4. 4. The ChallengeProblems with the Old Workflow<br />Serial and manual process<br />Can’t preview till near the end <br />No tracking, auditing, visibility<br />Waste of developer talent, 17,000 web files<br />Content “pieces” are not repurposed within site, nor to other applications<br />Bottom Line: Takes a long, long, long time (up to two months)<br />
  5. 5. The ChallengeThe Old Workflow<br />
  6. 6. The ChallengeWhat Led Us To SharePoint<br />Needed a structured Content Management System (CMS)<br />Tried a leading, large-scale alternative ECM solution, but failed<br />Overly document-centric<br />Too expensive to customize<br />Wealth of MS and .Net developers<br />MS Partnership<br />Out of the Box: Workflows, Version History<br />
  7. 7. The SharePoint SolutionThe Enterprise Vision<br />Content pieces not pages<br />Stored as simple html in ListItems<br />Each publication channel determines how to render<br />
  8. 8. The SharePoint SolutionProblems Resolved<br />Teams can work in parallel<br />Content approvers can preview how page will look as soon as content is entered<br />Built-in tracking, auditing, visibility<br />Modular content can be repurposed and restyled to any channel<br />Bottom Line: Process now takes just a day or two to make it to production, self-serve<br />
  9. 9. The SharePoint SolutionThe New Workflow<br />new workflow<br />old workflow<br />
  10. 10. SharePoint/ASP.NET Merged Publication<br />Jason Deere & Benjamin Lee<br />Continental.com Team<br />demo <br />
  11. 11. The Content Management SiteUser Interface<br />
  12. 12. The Content Management Site”Pieces” are Stored in List Items<br />
  13. 13. The Content Management SiteInstant Preview<br />Site Actions<br />/web Asset<br />SharePoint CQWP<br />
  14. 14. The ImplementationThe Challenges <br />Out of Box functionality did not meet our need for content management to co-exist with Continental.com <br />There was no precedent for using SharePoint in the way we envisioned it with modular content<br />Wanted to leverage thousands of existing ASP.NET assets<br />How do we merge SharePoint content publication with an existing ASP.NET application?<br />
  15. 15. Merging MOSS and ASP.NETKey Points That Make This Possible<br />Virtual Directories<br />What MOSS doesn’t know, won’t hurt it<br />Smart routing of traffic<br />Sharing Application Code and Assemblies<br />App_Code<br />/bin<br />User controls, style sheets, etc.<br />External Master Page<br />
  16. 16. Merging MOSS and ASP.NETWhat MOSS doesn’t know…<br />Virtual Directories<br />Create under your MOSS Web Application<br />
  17. 17. Merging MOSS and ASP.NETConfiguring Your SharePoint Site Structure<br />Key is to make your top MOSS sub-site and your virtual directory app at the samelevel<br />Under site collection, create root sub-site in MOSS to house all “CMS” pages & content <br />e.g. “domain.com/cms”<br />What does that do for us?<br />Can run both MOSS and the ASP.NET app on the same server, at the same time<br />Mirror SharePoint and ASP.NET folder structure<br />
  18. 18. Merging MOSS and ASP.NETRouting Network Traffic<br />Router makes decision based on sub-site URL<br />http://domain/cms/mycms.aspx<br />http://domain/web/mypage.aspx<br />
  19. 19. Merging MOSS and ASP.NETSharing Application Code and Assemblies<br />Allowing SharePoint to access existing business logic from web app<br />ASP.NET Files<br />/App_Code<br />/bin<br />web.config<br />Copy from ASP.NET application folders to corresponding SharePoint folders<br />
  20. 20. Merging MOSS and ASP.NETWhat You Need to Make Your External ASP.NET Master Page Work with SharePoint<br />“Minimal” master page:<br />&lt;%@ Import Namespace=&quot;Microsoft.SharePoint&quot; %&gt;<br />&lt;%@ Register Tagprefix=&quot;WebPartPages&quot; ...%&gt;<br />&lt;%@ Register Tagprefix=&quot;SharePoint&quot; ...%&gt;<br />&lt;%@ Register TagPrefix=&quot;PublishingSiteAction&quot; ...%&gt;<br />&lt;%@ Register Tagprefix=&quot;PublishingWebControls&quot; ...%&gt;<br />&lt;%@ Register Tagprefix=&quot;PublishingNavigation&quot; ...%&gt;<br />&lt;%@ Register TagPrefix=&quot;PublishingVariations&quot; ...%&gt;<br />&lt;%@ Register Tagprefix=&quot;PublishingConsole&quot; ... %&gt;<br />&lt;%@ Register TagPrefix=&quot;wssuc&quot; src=&quot;~/_controltemplates/Welcome.ascx&quot; %&gt;<br />&lt;%@ Register TagPrefix=&quot;wssuc“ src=&quot;~/_controltemplates/DesignModeConsole.ascx&quot; %&gt;<br />&lt;WebPartPages:SPWebPartManager ID=&quot;SPWebPartManager1&quot; runat=&quot;server&quot;/&gt;<br />&lt;SharePoint:RobotsMetaTag ID=&quot;RobotsMetaTag1&quot; runat=&quot;server&quot;/&gt;<br />&lt;Sharepoint:CssLink ID=&quot;CssLink1&quot; runat=&quot;server&quot;/&gt;<br />&lt;span class=&quot;siteActions“&gt;&lt;PublishingSiteAction:SiteActionMenurunat=&quot;server&quot;/&gt;&lt;/span&gt;<br />&lt;span class=&quot;siteActions“&gt;&lt;div&gt;<br /> &lt;PublishingWebControls:AuthoringContainer id=&quot;authoringcontrols“ runat=&quot;server&quot;&gt;<br /> &lt;PublishingConsole:Consolerunat=&quot;server“ /&gt;<br /> &lt;/PublishingWebControls:AuthoringContainer&gt;<br />&lt;/div&gt;&lt;/span&gt;<br />Site Actions Menu<br />
  21. 21. Merging MOSS and ASP.NET Override Master Page On Load<br />public class PublishingLayoutBase : PublishingLayoutPage<br />{<br /> protected override void OnPreInit(EventArgs e)<br /> {<br />this.MasterPageFile = &quot;~sitecollection/_layouts/CoCom/DefaultMasterPage.master&quot;;<br /> }<br />}<br />
  22. 22. Merging MOSS and ASP.NETUsing Your Master Page and User Controls in MOSS Page Layouts<br />&lt;%@ Page language=&quot;C#&quot; Inherits=&quot;CoAir.CMS.Web.PublishingLayoutBase,CoAir.CMS.Web.PublishingLayoutBase,Version=1.0.0.0,Culture=neutral,PublicKeyToken=7adcdaff331ecf96&quot; %&gt;<br />&lt;%@ Register Tagprefix=&quot;WebPartPages&quot; Namespace=&quot;Microsoft.SharePoint.WebPartPages&quot; Assembly=&quot;Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c&quot; %&gt; <br />&lt;%@ Register Src=&quot;/web/en-US/usercontrols/MileageCalculator.ascx&quot; TagName=“Calculator&quot; TagPrefix=“CoAirUC&quot; %&gt;<br />&lt;asp:ContentContentPlaceholderID=&quot;ContentInfo&quot; runat=&quot;server&quot;&gt;<br /> &lt;WebPartPages:WebPartZonerunat=&quot;server&quot; <br /> Title=&quot;&lt;%$Resources:cms,WebPartZoneTitle_Top%&gt;&quot; <br /> ID=&quot;TopColumn&quot;&gt;&lt;ZoneTemplate&gt;&lt;/ZoneTemplate&gt;<br /> &lt;/WebPartPages:WebPartZone&gt;<br />&lt;CoAirUC:Calculator ID=“Calculator&quot; runat=&quot;server&quot;/&gt; <br />&lt;/asp:Content&gt;<br />
  23. 23. Merging MOSS and ASP.NETVoila!<br />Site Actions<br />/web Asset<br />SharePoint CQWP<br />
  24. 24. Internal Content Management: The Process of Building the ECM Structure<br />Denise Wilson<br />Senior Manager, Technology<br />Continental Airlines<br />
  25. 25. Internal Content ManagementThe Problem Set<br />User e-mailed attachments as ‘workflow’<br />No single version of the ‘truth’<br />Uncontrolled growth of e-mail and file shares<br />Users can’t find anything or collaborate<br />No way to enforce record retention policy<br />Not searchable for compliance or security<br />
  26. 26. Internal Content ManagementThe Evolution of the Solution<br />Started by evaluating one group in-depth<br />Enterprise Engineering<br />Standardized AD site names<br />Standardized machine names<br />Named all new sites/devices by new convention<br />Corrected others as projects touch the site<br />
  27. 27. Internal Content ManagementThe Tools<br />How did SharePoint help us do this?<br />Automated review processes with workflow<br />Standardized Content Types and templates<br />Exposed data in Data Form web parts<br />Normalized data can be viewed and filtered<br />Started identifying anomalies and correcting them<br />Out of the box functionality<br />
  28. 28. Automated Review Process<br />SharePoint Designer Workflows<br />
  29. 29. Naming Standards<br />Result in Normalized Docs and Devices<br />
  30. 30. Standardize Content Types<br />Groups of metadata (site columns) <br />
  31. 31. Document Information Panel<br />Dropdowns promote standardization <br />
  32. 32. Display Data By Location (Filter)<br />Before data view, had to fly engineer to the site<br />
  33. 33. Slice and Dice Normalized Data<br />Virtual Earth<br />Ref: Blogs by Jon Campbell and Greg Chan of SharePoint Designer Team<br />
  34. 34. Slice and Dice Normalized Data<br />Drill Down<br />
  35. 35. Understanding Collective NeedsWhat We Learned From Each Group<br />Continental Board Meeting Minutes<br />Management is distributed to content owners<br />Senior level employees can manage own sites<br />Basic site structure, training and governance<br />Marketing Group Airport Signage<br />Templates / Look and feel<br />Corporate Sales Team<br />Kiosk Deployment<br />Technology, Marketing, Airport Services <br />System Operations Coordination (SOCC)<br />
  36. 36. Evolution of the Process System Operations Coordination<br />Phase I: E-mail to document libraries<br />‘E-mail enabled’ AD security groups <br />Use now as DLs, later for SP security<br />Log e-mails sent to DLs<br />Phase II: Push Alerts from SharePoint Lists<br />Install PCs beside existing Unix workstations<br />Extend sites and training to remote airports<br />Disaster Recovery Failover to alt data center<br />Phase III: Integrate Mainframe Ops Data<br />
  37. 37. System Operations Coordination<br />Phase I: E-mail enabled document libraries<br />Phase II: Push alerts from SharePoint Lists<br />
  38. 38. Evolution of the ProcessEngineering is two of six project phases<br />Integration of the other four: <br />Content types, templates, metadata, workflow<br />
  39. 39. Integration of the EnterpriseBuilding Content Management Structure<br />
  40. 40. Integration of the EnterpriseStructured Sites, Content Types and Metadata<br />Standardization <br />Get consensus / decisions on naming standards<br />Select site columns (file properties – author, date created, airport code, etc. per your needs)<br />Develop hierarchy of content types<br />Continental (“Project Document”)<br />Technology (“Technical Design”)<br />Engineering (“Design Proposal Summary”)<br />Continental (“Contract”)<br />Technology (“Technology Contract”)<br /> IT Services (“ISP Agreement”)<br />Retention Basis (e.g. “Active” plus two years)<br />Disposal Workflow<br />
  41. 41. Integration of the EnterpriseStructured Sites, Content Types and Metadata<br />Department by Department <br />Site Collections<br />Content Types (keep it simple)<br />Metadata (keep it simple)<br />Establish a platform<br />Put your new documents here (with metadata)<br />Then migrate from file shares (with metadata)<br />Distributed Model<br />Site owners and training<br />Governance<br />
  42. 42. Integration of the EnterpriseRefined Search Scopes<br />Free-text search yields 8448 results<br />
  43. 43. Integration of the EnterpriseRefined Search Scopes<br />Search by Content Type (Systems EWO) Yields 22 results<br />
  44. 44. Continental Airlines Enterprise Content Management<br />Questions?<br />
  45. 45. Remember to fill out your evaluations onMySPCfor your chance to win two HD web cams and a designer mouse (3 prizes awarded daily)<br />
  46. 46. Learn More about SharePoint 2010<br />Information forIT Prosat TechNet<br />http://MSSharePointITPro.com<br />Information forDevelopersat MSDN<br />http://MSSharePointDeveloper.com<br />Information forEveryone<br />http://SharePoint.Microsoft.com<br />
  47. 47. © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.<br />The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×