Transcript Sitefinity Integration and Extensibility

Sitefinity Integration and Extensibility
Christopher Peck, Sales Engineer
June 4, 2015
Overview
• Data
• Display of Data
• Within Sitefinity
• Styling
• Connections and Connectors
• Templates
• Pushing and Pulling
• Widgets
• External Systems
• Provide options to end users
• Searching
Data within Sitefinity
• Flexible Data Model
• Granular Permissions
• Programmatically Accessible
• User Friendly (and Customizable) input interfaces
• Storage Provider Flexibility
Storage Providers
• Sitefinity supports
• SQL Server 2008/2010/2012 R2/Azure
• SQLExpress
• Oracle
• MySQL
• File System
• The Data Provider Model allows us to
• Have different content served from different databases or sources
• Have dedicated storage providers for Blob Data
File
system
Provider model for data access
•
Sitefinity does not care whether data is stored
in SQL Server, Oracle, MongoDB or text files
•
Sitefinity and its components access data
through providers
•
Sitefinity can work with multiple data sources
at the same time (e.g. users can live in Active
Directory, while their profile can live in SQL
Server)
Benefits
System can integrate well within existing systems
and pursue different strategies depending on
business requirements
PROVIDERS
Blogs
Users
Events
News
Single Sitefinity Instance
Storage & Data Providers
• Blob storage – Images, Documents, Files
• Windows Azure
• Amazon S3
• Dropbox for Business
• Telerik Backend Services
• CDN Suppor
• Amazon
• Azure
• CloudFront
• ..and others
File system
Platform Backend
Connections and Connectors
• Digital Experience Cloud
• Sharepoint (2010, 2013 and Online)
• Salesforce
• Microsoft Dynamics
• Marketo
Connector for Sitefinity Digital Experience Cloud (DEC)
• Page Visits (regular and personalized pages)
• Forms submissions (map fields from Forms to Profile Fields in DEC)
• File Downloads
• Comments
• Forums
• Users (login, logout, register, profile fields changes, etc)
• Social tracking – who shared and liked what
• And *Everything* else with and SDK. For example, “mouse hover on a phone number”
DEC – Insights in the CMS
Connector for SharePoint 2010 / 2013
• 2 way sync and sync scheduling
• Master / Slave set ups for conflict resolutions
• Multiple SharePoint sites and instances
• Sync any SharePoint List to
• Sitefinity Dynamic Modules – Every list becomes
content type
• Libraries and Images
• Calendars and Events
• Fields Mapping
• Most of the SharePoint fields supported.
Connector for SharePoint Online
• Support for Cloud and On-Premise setups
• Feature parity with SharePoint 2010/2013 connector
• Effectively integrate with Office 365 Enterprise
Office & OneDrive
SharePoint Online Web Sites
•
SharePoint Web Sites discontinued by MS
•
…Sitefinity can de-facto become the extension of
SharePoint
Connector for Salesforce
• 2 way sync and sync scheduling
• Master / Slave set ups for conflict resolutions
• Sync Salesforce contacts, leads
• Sitefinity Users
• Sitefinity Roles
• Sync CMS Forms with the CRM
• Fields Mapping
• Most of the Salesforce fields supported.
Connector for MS Dynamics
• Access and edit any CRM entity
• Show CRM charts on the web site
• Sync Dynamics contacts, leads
• Sitefinity Users
• Sitefinity Roles
• Sync CMS Forms with the CRM
• Provided with technology partnership
with Pavliks
Connector for Marketo
• Sync CMS Forms with Marketo – Any forms!
• Provide personalization by
• Lead score
• Any Marketo Lead Field
• Works for Anonymous and Known Leads/Visitors
• Fields Mapping
• Map any form field to any lead field
Pushing and Pulling
• Publishing System
• Event driven scenarios
• Web services
Publication system – Content Pipes
• Import XML content from any system or file
• Mashup content – different sources
• Bind Social networks to Content
• Automatic Publishing to Social media
• Automatic Publishing and management of
RSS feeds
Events System
• Events on Create, Update and Delete of Data
• Form Events (Validation, Submission,…)
• User Events
• E-commerce Events
• Media Content Download Events
• Many more…
Web Services
• RESTful Web Services
•
•
•
•
•
•
Push Data in from another system
Update Data
Change Taxonomies
Change Pages
Change Content Lifecycle
Implement Your Own Services
Search Providers
• Lucene.NET by default
• Fast and well established
engine
• Not very well suited for NLB
environments
• Cloud Search
• Azure Search Services
• Amazon Web Search
• Elastic Search
• Solr
• .. The search engine is now
decoupled – really easy to
integrate with others
Azure
Displaying Data
• UI is separate from the data layer.
• Control of Styling, Client, and Server Side.
Server
HTML
CSS