Tim Bauer’s Running Thoughts

Watched this webcast

Preparing for Web Content Management w/ Microsoft Office Sharepoint Server 2007

today based on (1) the set of our annuity accounts that are currently on CMS 2002 and (2) the rumor that certain clients are migrating from tier1 ECM products (like Documentum) to the o2007 Microsoft Office Sharepoint Server (MOSS) suite.

So here is what i took away:

1. Solid Marketing vs ECM Space. Good slides and discussion (at a high level) on how the pieces of MOSS can provide not just WCM (focus of this presentation) but the macro view of ECM in ways. For example records management.
2. WSS / WWF Based … AGAIN. Another product that is basing off the core of Windows Sharepoint Services and Windows Workflow foundation. It is clear that MSFT is standardizing on this infrastructure. If you aren’t grappling with what these features can do for you in an application framework — get on it.
3. Sizzle No Steak? Interesting how they didn’t show the product (this was captured in March however). So at that time it was probably too unstable for demo. Has anyone looked at it (Ruska? Baldwin?) since then?

Anyway, here is my detail list:

• Preparing for Web Content Management w/ Microsoft Office Sharepoint Server 2007

• Manish Sharma - Sr. Product Mgr
• Arpan Shah - Group Product Mgr

• 1:44 Agenda
…………….○ Evolution of WCM (cms2001, moss 2007)
…………….○ Features in MOSS
…………….○ New capabilities
…………….○ Migration cms 2002 to MOSS
• 2:00 Evolution
…………….○ CMS 2001
…………….○ CMS 2002
…………….○ MOSS 2007
• 3:30 Overview of MOSS 2007
…………….○ Collab
…………….○ Portal
…………….○ Search
…………….○ Content Management
…………….○ Business Processes
…………….○ Business Intelligence
• 7:00 ECM
…………….○ User Intfc : office, Web, 3rd party
…………….○ ECM: Doc Mgmt, WCM, Records Management, Forms Mgmt
…………….○ Svcs: Workflow, Meta, Policies, Library Svcs, Search, security, IRM, Collab
…………….○ Unified Storage: WSS + SQL Server
…………….○ [bauer comment - 1st time I have seen a ECM vision slide from MSFT, similar to Documentum and Stellent angles (at least in marketing points)]
• 10:00 - Author web content
…………….○ Talks to RM impacting (being available)
…………….○ WSIWYG editor (new)
• 11:45 - In Place Authoring Editing
…………….○ Author content with WSIWYG editor
…………….○ Spell check /tables
…………….○ Server side conversions (word to web page leveraging master page of site)
• 13:00 - Publish
…………….○ Templates - separate content and presentation
• 17:00 - Deploy and Manage
• 18:00 - Present content to Web Users
…………….○ High scale / performance
• 20:00 - Benefits
…………….○ Lower mgmt costs multi site / multi lang
…………….○ Business Driven content
• 20:30 - Liscensing Models
…………….○ Server / Cal (intranet models)
…………….○ Per Server (internet sites)
• 22:30 - Q&A
…………….○ Migration
…………….○ Availability - End 2006
…………….○ Public Beta - End of 6/30
…………….○ SQL Server 2005 Supported
• 23:30 - Key Arch Points (CMS and MOSS)
…………….○ No client footprint this time
…………….○ Editing - Users can add webparts and content (applications)
…………….○ Sharepoint Designer = Next Version of FrontPage
…………….○ Page Layouts = Templates
…………….○ WSS based = for example web content in WSS lists so you get page lock down, recycle bin, RSS feeds on page, workflow on pages, etc … all via WSS .. Also auth provider model works (could write a app provider in asp .net 2.0).
…………….○ Built on WWF. O2007 features. Configurable workflow templates. Serial, parallel, events, create workflows (via designer, or vs2005).
• 30:00 - Coexistance
…………….○ Can run in parallel (CMS and SP 2007)
…………….○ CMS - content, cms files (templates, etc), config
…………………………..§ Will have tools to move content
…………………………..§ Incremental or big bang content movements
…………………………..§ Templates - Get a blank template for every CMS templates (will generate). Won’t move code behinds. Manual apply code, styles (css files could port).
…………….○ Custom Code
…………………………..§ Search (Out of Box - OOB)
…………………………..§ Nav - OOB (plus Whidbey provider)
…………………………..§ Summary Roll Up - OOB (listings, TOC, rollup)
…………………………..§ Deploy Scripts - OOB
…………………………..§ Form Login - OOB
…………………………..§ Workflow - Better OOB
…………………………..§ Console Customizations - OOB
…………………………..§ Custom Placeholder Server Controls - Rewrite as WSS field control
• 42:00 - Application Code Migration
…………….○ Key point not 100% migration of customization on CMS
• 43:00 - Best Practices
…………….○ Get on SP2
…………….○ Minimize Templates (less than 30 per site)
…………….○ Get rid of going directly to the DB (use API’s and workarounds)
…………….○ Don’t put login in pages
…………….○ Leverage Whidbey provider models for navigation and forms (via SP2)
…………………………..§ Enables cool OOB Whidbey Nav
…………………………..§ Makes Nav and Form Login Simple
• 48:00 - Migration Resources
…………….○ Migration Whitepapers
…………….○ Public Beta is avail on 7/5
…………….○ Assessment Tool
…………………………..§ Application that you run on a dev machine and it looks at CMS2002 … tells you what you need to look at (in a way)
…………….○ Arch Guidance
…………….○ Review Reusability and ECM Whitepaper
…………………………..§ ECM - www.microsoft.com/office/preview/ecmwhitepaper.mspx
…………………………..§ BETA - get that
• 51:00 - QA
…………….○ What is Whidbey? ASP .NET 2.0
…………….○ Browser support better than CMS2002 (subscribers supports all models)
…………….○ WSS v2 to v3 is an upgrade … beta2 will address. Reuse on WSS will also be addressed.
…………….○ Blogs.msdn.com/arpans
…………….○ Highly distributed? Can publish to multiple farms
…………….○ Multi Lingual? O2007 on wss.v3 … can have different areas (called sites now) can have different languages. Page level translation is workflow. Control to switch to lang (in template)
…………….○ CM2001 migration. Write ASP code to asp.net.
…………….○ Offline. Take any stuff offline (groove, wss features, etc)