Transcript Implementierung eines mehrsprachigen Intranets basierend auf SharePoint 2010 Thomas Palmié Architect Microsoft Schweiz Agenda Requirements Site Provisioning Options Multi-Lingual Options Concrete Implementation.

Implementierung eines
mehrsprachigen Intranets
basierend auf SharePoint 2010
Thomas Palmié
Architect
Microsoft Schweiz
Agenda
Requirements
Site Provisioning Options
Multi-Lingual Options
Concrete Implementation
Objectives
A good understanding about the different
SharePoint 2010 site provisioning options
Understanding the options for implementing a
multi-lingual site
Learning about tools and scripts for the automation
to implement a multi-lingual site
Requirements
Intra-/Extranet
Support for anonymous and authenticated users
Supporting german, french, italian and english
speaking users (authoring and content)
Easy content management-no duplication of content
Site Provisioning Options
Site Provisioning Options
Custom
Code
Feature stapling
Associate Features with SharePoint site definitions (in
the “14 root folder”) to extend out-of-the-box site
definitions
Features are activated automatically when site is
being provisioned from the site definition
requires:
Stapler feature
Staplee feature
Feature Stapling
Advantages / Usage
Used to extend or change
provisioning logic of existing site
definitions
Supported in BPOS-D
Associations can be updated easily
based on feature activations and
updates
Also supports feature parameterization
Disadvantages
Can only extend existing site
definitions, cannot provide new
choices of site templates/definitions
to the user at site creation
Activated after feature associations in
the onet.xml
Limited options to manipulate
provisioning logic as they are
activated before lists and modules
Stapled features are activated
”randomly” after specific scope
Feature dependencies could help to
define order more detailed
Site template
Advantages / Usage
Can be easily created by saving
existing site as template from site
settings
Easily package simple sites as a
reusable template which can be
deployed to any environment*
Generates full-fledged solution
package (WSP)
Supported in BPOS-D and BPOS-S
Can be easily updated by making a
new version available to users
Disadvantages
Only available in site collection scope
Not available for site collection creation,
unless imported to VS and modified
Publishing features are not
supported
Other complex functionalities are
also not available
If imported to VS as a starting point
for custom Web template, WSP
package has lot of ”unnecessary”
xml configurations
Feature stapling for site templates is
not available (only for site definitions)
Site definition provisioning
1
14\Templates\[lcid]\xml
2
WebTemp*.xml
14\Template\SiteTemplates\[selection]\xml
Onet.xml
3
14\Template\Features\[featureX]\
features.xml
Site definition
Advantages / Usage
Full flexibility as to which
features will be activated
Publishing features are
supported
Consistent with the out-ofthe-box implementation
Disadvantages
Updating after initial
deployment is not supported
Can be mitigated by using
minimizing content in onet.xml
Feature stapling is an option
Not supported by BPOS-S
or BPOS-D
Not end-user deployable
Causes implications to
following major version of
SharePoint
Provisioning Providers
Advantages / Usage
Can be used to fully
customize the provisioning
process
Support to define
provisioning properties
also included
(ProvisionData attribute)
Based on code, so
provisioning logic is easily
upgradable
Easy to debug
Disadvantages
Provisioning class defined in
the webtemp*.xml
Not supported by BPOS-D
or BPOS-S
Custom provisioning
implementation, so no
standard development
practices
Not end-user deployable
Web Templates
The WebTemplate element is available from the
Feature Framework schema
Can be deployed at Site and Farm scopes
Available also as Sandbox solution
Build using an elements.xml file and an onet.xml
No webtemp.xml file!
Web template provisioning
1
14\Templates\Feature\FeatureX
2
14\Template\SiteTemplates\[Selection]\
Onet.xml
Elements.xml
14\Template\Features\FeatureX\
Onet.xml
4
3
14\Template\Features\[featureY]\
features.xml
Web templates and code
Web template identifier consists of the feature GUID
and configuration
For example - [GUID]#Name
Web templates are listed in similar ways in the
WebTemplates collection as site definitions
Available when feature is activated
Web Template
Advantages / Usage
Supported by BPOS / MS
Online
Supports site and farm
scopes
Publishing features are
supported
Can be freely updated in
farm without affecting
existing sites
If packaged as sandbox
solutions, end user
deployable
Disadvantages
Variations don’t understand
Web templates
You cannot staple features to
Web templates
Why would you?
No tracking out-of-thebox
demo…
Using a web template for a
multi-lingual site
Multi-Lingual Options
Variations and MUI
Variations
Site Collection
One-to-many
source/target
relationship
Relationships
List (Hidden)
Variations Root
(Home)
Reusable
Content
Master Pages
and Layouts
Hierarchy
Pages
Source Variation
Site (1)
Resources
Pages
Target Variation
Site (up to 50)
Resources
Variations Language Landing Logic
(VariationRoot.aspx)
Browser Setting
Supported Culture
Default/Neutral Language
Route to appropriate Label Site
Accept-Language
fr-FR,es-US;q=0.8,es-ES;q=0.7,es;q=0.6,en-us;q=0.7
Multilingual User Interface
(MUI)
MUI and Authoring
Multi-Lingual Options
Option
Pro
Con
Variations
• Language Selection Control
out-of-the-box
• Automatic language detection
(HTTP_ACCEPTED_LANGUAGE)
• Content is available in several
languages
• Content will be duplicated
• Dependencies between
variation source and target
MUI
• Content is available in several
• Language Selection Control IS
languages and can be managed
NOT available out-of-the-box
centrally
(for anonymous users)
• Language Packs for the
• Requires a custom content-type
translation of the user-interface
and page-layout for managing
are available for >40 languages
multi-lingual content in one
page
Concrete Implementation
MUI, custom content-type, multi-lingual page-layout, Resource Files
in VS.NET, automated site provisioning with PowerShell
Concrete Implementation
Farm or Site?
Farm scoped feature
Available for the whole farm
Site scoped feature
Available for a particular site
collection
demo…
Implementation Details
Multi-Lingual Page Layout
Multi-Lingual Content
Resources in VS.NET
CKS:Dev Tools
demo…
Automated site provisioning
with PowerShell
Review: Objectives and
Takeaways
A good understanding about the different site
provisioning options
Understanding the options for implementing a
multi-lingual site
Learning about tools and scripts for the automation
to implement a multi-lingual site
References
SharePoint 2010 and web templates:
http://blogs.msdn.com/b/vesku/archive/2010/10/14
/sharepoint-2010-and-web-templates.aspx
CKS:Development Tools Edition
(Community Kit for SharePoint)
http://cksdev.codeplex.com/
Give us your feedback!
Please help us make TechDays even better by
Evaluating this Session. Thank you!
© 2011 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.
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.