Web Content Management with MOSS 2007 Patrick Tisseghem [email protected].

Web Content ManagementWeb Content Managementwith MOSS 2007with MOSS 2007

Patrick [email protected]

AgendaAgenda

Introducing Web Content Management

Internet-Presence SitesCreation Steps

Anonymous Access & Forms Authentication

Walk-Through WCM FeaturesSite Hierarchy and Navigation Controls

Master Pages, Page Layouts, Field Controls

Authoring Pages

Site Variations

Workflow

WCM Web Parts

CMS 2002 MOSS 2007

Microsoft Content Management Server Microsoft Content Management Server 20022002

Low TCO/Enterprise CM - Separate content from design

Dynamically repurpose and target content for audiences and devices

Deliver fast and low-cost site updates and redesigns

Provide content versioning, scheduling and reuse

Enhance Biz User Productivity – Empowered to Publish

Web browser-based rich authoring or direct from Microsoft Word

Out-of-the-box and extensible workflow for compliance and quality control

Powerful Abilities for IT – Extensible and Interoperable

Developers rapidly create content-rich, dynamic Web applications

VS.NET integrated providing out-of-the-box server and user controls

Templates easily created by dragging and dropping placeholders

Managed API leveraging .NET framework and ASP.NET

Web Services extensibility

Integration with SharePoint Portal Server and Commerce Server

ASP.NETASP.NET

Design GoalsDesign Goals

Integrate CMS and SharePointRemove forced choice “CMS vs. SharePoint”

Move towards integrated ECM solution

Add Internet readiness to Sharepoint

Make creation of dynamic, produced websites dramatically faster and easier

Lower amount of costly custom code

Provide great OOB experience

Improve user experience across all features

Move CMS customers forwardComprehensive data migration

Enable flexible migration plans

WCM in the 2007 Office WCM in the 2007 Office SystemSystem

Delivered as a set of features with Microsoft Office SharePoint Server 2007

Can be activated for Intranet, Extranet and Internet sites

Creating an Internet Presence Web Creating an Internet Presence Web SiteSite

StepsPrepare an IIS Web Application

Use SharePoint 3.0 Central Administration to Extend the IIS Web Application

Create a Site Collection

Create a Site basedon Internet Presence Web Site definition

An Internet Presence Web An Internet Presence Web SiteSite

Creating an Internet Presence Creating an Internet Presence SiteSite

DEMO

Forms AuthenticationForms AuthenticationWSS V3 supports ASP.NET forms authentication

Allows you authenticate without requiring Active Directory

Based on ASP.NET 2.0 pluggable authentication providers

ASP.NET 2.0 role providers can optionally be used as well

Out-of-the-box Authentication providersASP.NET 2.0 SQL Server authentication provider

LDAP Authentication provider

Identity Mgmt AppOperating System

Identity Store

xoxoxWally

oxoxMary

xoxoxoBob

PWDLogin

DesktopWindows XP

ApplicationBrowser

Office AppCustom App

Web ServerWindows Server 2003

WSS

Internet

AuthenticationProvider

Configuring Web App for Forms Configuring Web App for Forms AuthenticationAuthentication

SharePoint 3.0 Central AdministrationChange the Authentication Provider for the Web App

ASP.NET 2.0 Membership ASP.NET 2.0 Membership ProviderProvider

web.config file configures basic ASP.NET settingsAuthentication configured for Forms

Membership provider is configured

Impersonation is set to true (e.g. impersonated IUSR_XXX)

<configuration> <system.web>  <authentication mode="Forms"> <forms loginUrl="/_layouts/login.aspx" /> </authentication>  <membership defaultProvider="AspNetSqlMembershipProvider" />  <identity impersonate="true" />  <authorization> <allow users="*" /> </authorization> </system.web></configuration>

<configuration> <system.web>  <authentication mode="Forms"> <forms loginUrl="/_layouts/login.aspx" /> </authentication>  <membership defaultProvider="AspNetSqlMembershipProvider" />  <identity impersonate="true" />  <authorization> <allow users="*" /> </authorization> </system.web></configuration>

Setting Policy for Web AppSetting Policy for Web App

Defining Administrator Defining Administrator UserUser

Sign In Using Custom Sign In Using Custom AccountAccount

Enable Anonymous at Site Enable Anonymous at Site LevelLevel

Add UsersAdd Users

Configuring an Internet Presence Web Site Configuring an Internet Presence Web Site for Anonymous Access and Forms for Anonymous Access and Forms AuthenticationAuthentication

DEMO

Walk-Through of WCM Walk-Through of WCM FeaturesFeatures

Based on WSS 2007 Features in addition to a number of features that will be activated when going for MOSS 2007

Define hierarchy using sites

Navigation controls

Master pages

Page layouts and field controls

Pages

Smart client authoring

Site Variations

Workflow

WCM Web Parts

Site HierarchySite HierarchyIn the past a lot of confusion

Windows SharePoint Services 2003 sitesSharePoint Portal Server 2003 areasContent Management Server 2002 channels

In SharePoint 2007 everything is a site

NavigationNavigation

Dynamic navigation based on site hierarchyIncludes webs, pages and authored linksNavigation links trimmed based on security, workflow state and publishing schedule

Navigation and ASP.NETNavigation and ASP.NET

Based on the ASP.NET 2.0 navigation model

Works with standard ASP.NET 2.0 navigation controls

Out-of-the-box Hierarchy navigation provider

High performance: provider support runtime object caching

Site Content and StructureSite Content and Structure

Site Hierarchy and Site Hierarchy and Configuring the Navigation ControlsConfiguring the Navigation Controls

DEMO

Page = Master Page + Page Page = Master Page + Page LayoutLayout

Master page defines how navigation is rendered

Page layout ASPX defines how page content is rendered

Together they render the full page

1-3 Master pages, 10-25 Page Layouts to 10 of thousands of pages

Page LayoutsPage Layouts

Page execution:Page URL requestedPage layout executed in content of pageContent server controls bind to page fieldsRendered page returned

Inherited from WSS:Versioning, Check-in/Check-outContent typesAccess controlWorkflow

Steps to Create a New Page Steps to Create a New Page LayoutLayout

Create shared columnsCreate content typeAdd created columns as columns of the content typeIn the Master Page Gallery

Create new Page Layout file

Check-out file and edit in SharePoint Designer

Populate the file with content fields

Check-in and approve

Use the new page layout file

Creating a Page using the Creating a Page using the BrowserBrowser

In-context web based page authoringMenu-based Web author console Out-of-the-box set of content controls

HTML controlDHTML-based editor with support for styles

Table editing with configurable styles

Image control with asset picker

Attachment/Link control with asset picker

Full page spell checkingContent reuse with asset picker

Creating a New Page LayoutCreating a New Page Layout

DEMO

Site VariationsSite Variations

Allow for publishing of related sites and pages

Multilingual scenarioDevice targetting

Source SiteSource Site

Variation AVariation A

Variation BVariation B

Variation CVariation C

Site VariationsSite Variations

DEMO

Publishing CyclePublishing Cycle

Workflow based on Windows Workflow Foundation

Light-weight approval workflow is active OOBBased on moderation

Minor versions need to be approved to become major versions

Visitors only see the major (published) versions

Workflow can be replaced by custom workflowOOB delivered with MOSS 2007

Designed using SharePoint Designer 2007

Created using Visual Studio.NET 2005

Publishing CyclePublishing Cycle

DEMO

WCM Web PartsWCM Web Parts

Summary Links Web PartCustom annotated, stylized links

Table of Contents Web PartDisplays navigation information of your site

Content Query Web PartDisplays a dynamic view of the content in your site

WCM Web PartsWCM Web Parts

DEMO

CMS 2002 to MOSS 2007CMS 2002 to MOSS 2007

Two phases of migration Content migration (automatic)Application migration (manual)

Content migration support two modesFull migrationIncremental migration

Start with a full migration and then do periodic incremental migrations until you are ready to cut over

Incremental allows you to continue using your existing CMS02 installation during migration

CMS 2002 and MOSS 2007 can coexist on the same physical farm

This allows you complete the migration without having to purchase hardware for a new farm

CMS 2002 Content CMS 2002 Content MigrationMigration

Content migration tool runs against CMS02Generates PRIME import packages

What counts as content?Channels, postings and all placeholder content

Resource galleries and resources

Template galleries and template gallery items (not the ASPX files)

Rights groups and users

Custom properties

What will I have after I run the automatic content migration tool?

A functioning site with all existing content

A set of unbranded page layouts that can be re-branded

CMS 2002 Application CMS 2002 Application MigrationMigration

Update “white” master page and page layouts generated by the content migration tool

Reapply all custom formatting logic e.g. adding custom CSS classesShould only need to touch one master page and a handful of page layouts

CMS 2002 Application CMS 2002 Application MigrationMigrationCustom codeCustom code

AgendaAgenda

Introducing Web Content Management

Internet-Presence SitesCreation Steps

Anonymous Access & Forms Authentication

Walk-Through WCM FeaturesSite Hierarchy and Navigation Controls

Master Pages, Page Layouts, Field Controls

Authoring Pages

Site Variations

Workflow

WCM Web Parts

CMS 2002 MOSS 2007

Web Content Management with MOSS 2007 Patrick Tisseghem [email protected].

Documents

Transcript of Web Content Management with MOSS 2007 Patrick Tisseghem [email protected].