Application Syndication Whitepaper


Published on

Published in: Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Application Syndication Whitepaper

  1. 1. Alfresco Web Content Management
  2. 2. About Web Content Management <ul><li>What is it for? </li></ul><ul><ul><li>Manage the content of the website </li></ul></ul><ul><li>What are the benefits? </li></ul><ul><ul><li>Separate the content from the layout </li></ul></ul><ul><ul><li>Put the content in the hands of the business user </li></ul></ul><ul><ul><li>Reduce maintenance cost </li></ul></ul><ul><ul><li>Standardize the layout of the site </li></ul></ul>
  3. 3. About Alfresco <ul><li>Founded in January 2005 by: </li></ul><ul><ul><li>John Newton – Co-Founder of Documentum </li></ul></ul><ul><ul><li>John Powell – Former COO, Business Objects </li></ul></ul><ul><li>Backed by Accel Partners and Mayfield Fund </li></ul><ul><ul><li>$10 million US </li></ul></ul><ul><li>Complete ECM solution </li></ul><ul><ul><li>Web Content Management </li></ul></ul><ul><ul><li>Document Management </li></ul></ul><ul><ul><li>Records Management </li></ul></ul><ul><ul><li>Image Management </li></ul></ul>
  4. 4. History of Alfresco <ul><li>January 2005 </li></ul><ul><ul><ul><li>Alfresco is founded John Newton, co-founder of Documentum and John Powell, former COO of Business Objects </li></ul></ul></ul><ul><li>October 2005 </li></ul><ul><ul><ul><li>Alfresco 1.0 is released and includes only the documents management module </li></ul></ul></ul><ul><li>February 2006 </li></ul><ul><ul><ul><li>Former Core Interwoven Team Join Alfresco, including Kevin Cochrane, Former VP Web Content Management at Interwoven </li></ul></ul></ul><ul><li>February 2007 </li></ul><ul><ul><ul><li>Alfresco 2.0 is released and includes a Web Content Management module </li></ul></ul></ul>
  5. 5. Alfresco - Functional Advantages <ul><li>Versioning of every website asset (image, text, etc.) </li></ul><ul><li>Whole website versioning </li></ul><ul><li>One-click rollback to any version of the site </li></ul><ul><li>Email-based production workflow </li></ul><ul><li>In-context preview </li></ul><ul><li>Easy access and modification of the content using: </li></ul><ul><ul><li>CIFS (access content like a file system) </li></ul></ul><ul><ul><li>Alfresco Web client </li></ul></ul>
  6. 6. Alfresco - Technical Advantages <ul><li>Enterprise-class content repository </li></ul><ul><li>Supported open source (no vendor lock-in) </li></ul><ul><li>Easy deployment using CIFS (Common Internet File System) </li></ul><ul><li>Compatible with Java, .Net or any other language </li></ul><ul><li>Extremely flexible architecture </li></ul><ul><ul><li>Eliminate dependency between the content management system (CMS) and the website </li></ul></ul><ul><ul><li>Eliminate compatibility issues (for example between the eCommerce software and the CMS) </li></ul></ul>
  7. 7. Alfresco Reviews <ul><li>“ Alfresco is a scalable and well-architected open source alternative for ECM …” (April 16, 2007 ) </li></ul>“ Alfresco: ECM that people will really use” (April 27, 2007 )
  8. 8. Alfresco Customers
  9. 9. Architecture
  10. 10. Alfresco makes the CMS transparent <ul><li>CIFS expose the content as a standard file system </li></ul><ul><li>Deploy to any application server by binding the application server to a CIFS directory </li></ul><ul><li>Can support development with Java, .Net, PHP or any other compiled or scripting language </li></ul><ul><li>Transparent integration with any e-commerce solution or any third party software like ElasticPath </li></ul>
  11. 11. Alfresco Fundamentals Concepts <ul><li>Web Project </li></ul><ul><ul><li>A web site or a web application </li></ul></ul><ul><li>Web Form </li></ul><ul><ul><li>An XML schema compliant with W3C XForms standard </li></ul></ul><ul><li>Web Content (“Structured”) </li></ul><ul><ul><li>An XML file that respect a Web Form XML Schema </li></ul></ul><ul><li>Content (“Unstructured”) </li></ul><ul><ul><li>Any file (Image, PDF, XML, etc..) </li></ul></ul><ul><li>Template (View) </li></ul><ul><ul><li>Add presentation to the content (XSLT, FreeMarker, etc…) </li></ul></ul>
  12. 12. Web Project <ul><li>A web project is a web application managed by Alfresco </li></ul><ul><li>Alfresco manages every files in a web application including: </li></ul><ul><ul><li>Application content (XML, images, etc…) </li></ul></ul><ul><ul><li>Application scripts or compiled code </li></ul></ul><ul><ul><li>Presentation template (XSLT, JSP, etc…) </li></ul></ul><ul><ul><li>Static HTML pages </li></ul></ul><ul><ul><li>Configuration files </li></ul></ul><ul><li>You can populate an Alfresco web project by importing any existing site into Alfresco </li></ul>
  13. 13. Web Form <ul><li>Web forms are used to enter structured content </li></ul><ul><li>Web forms are defined with an XML schema compliant with W3C XForms standard </li></ul><ul><li>To create a web form you just import the XML schema </li></ul><ul><li>Each element in the form is defined a type </li></ul><ul><ul><li><xs:element name=&quot;News_Date&quot; type=&quot;xs:date&quot;/> </li></ul></ul><ul><li>Alfresco generate UX control for each type of element. </li></ul>
  14. 14. Content <ul><li>Alfresco save the web content as XML file </li></ul><ul><li>You can configure Alfresco to save web content: </li></ul><ul><ul><li>In a specific folder </li></ul></ul><ul><ul><li>In the folder where the user is located </li></ul></ul><ul><li>Unstructured content is save directly in the web application </li></ul><ul><li>You can link unstructured content to web content using the file picker control </li></ul>
  15. 15. Template <ul><li>Template are used to generate web pages (or PDF documents) from content </li></ul><ul><li>Each template is associated with a primary web form but can query any content </li></ul><ul><li>Templates can be applied by the CMS (limited to XSLT, XSL-FO and FreeMarker) or by the site logic </li></ul><ul><li>If a template use content from more than one XML file it is recommended that the template be applied by the site logic </li></ul>
  16. 16. Sandbox <ul><li>Each user as it own sandbox where he can modify the site without affecting others users </li></ul><ul><li>Each user see all the files in the production site plus any modifications made by the user </li></ul>
  17. 17. Versioning <ul><li>All workspace assets are versioned </li></ul><ul><li>You can revert to any version with just one click </li></ul><ul><li>The whole production web site is versioned </li></ul><ul><li>You can revert to any version with just one click </li></ul>
  18. 18. Workflow <ul><li>Alfresco workflow is implemented using JBoss jBPM </li></ul><ul><li>Is it possible to define complex workflows using jBPM </li></ul><ul><li>Two basic workflows are provided: Serial and Parallel </li></ul><ul><li>Workflows can be applied to specific directory or file </li></ul><ul><li>You can define multiple workflows each with different users </li></ul>
  19. 19. Production environment <ul><li>Alfresco production environment uses 3 servers: </li></ul><ul><ul><li>The CMS server that server run the repository and web client </li></ul></ul><ul><ul><li>The preview server that provide in context preview capability </li></ul></ul><ul><ul><li>The production server that run the production site </li></ul></ul><ul><li>The CMS server must be a Java (J2SE 5.0) application server (Tomcat, JBoss etc…) </li></ul><ul><li>A Tomcat preview server come pre-configured </li></ul><ul><li>It is possible to configure other preview servers (IIS, JBoss etc…) </li></ul><ul><li>The production server is mounted using CIFS and can be any application server (Apache, IIS, Tomcat etc…) </li></ul>
  20. 20. Limitations <ul><li>A replication module will only be available in version 2.0.1 to enable remote deployment </li></ul><ul><ul><li>Workaround : deploy using CIFS on a single machine </li></ul></ul><ul><li>The file picker control is very limited: No image preview, not possible to place restrictions on files upload location </li></ul><ul><ul><li>Workaround : would need custom development </li></ul></ul>
  21. 21. Example: Kozy Shack recipes
  22. 22. Recipe Page
  23. 23. <ul><li>Title </li></ul><ul><li>Ingredients </li></ul><ul><li>Preparation </li></ul><ul><li>Preparation time </li></ul><ul><li>Yield </li></ul>Recipe Page Elements Header Links to all the recipes Footer Picture Other featured recipes
  24. 24. Enter content for the page
  25. 25. Automatically generated content <ul><li>Recipe links are automatically generated on each recipe page </li></ul>
  26. 26. Automatically generated selection <ul><li>All recipes automatically appear as options in Featured Recipes menus </li></ul>
  27. 27. Demo <ul><li>Create a web form </li></ul><ul><li>Create a web project </li></ul><ul><li>Import an existing web site </li></ul><ul><li>Preview the web site </li></ul><ul><li>Deploy the new web site in production </li></ul><ul><li>Create web content </li></ul><ul><li>Modify web content </li></ul><ul><li>Deploy the web content in production </li></ul><ul><li>Rollback deployment </li></ul>