Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Unifying BI and CM with SOA

421 views

Published on

  • Be the first to comment

  • Be the first to like this

Unifying BI and CM with SOA

  1. 1. Unifying Business Intelligence and Content Management with Service-Oriented Architectures Chris Harrington Active Interface, Inc. [email_address]
  2. 2. Presentation Objectives <ul><li>Review Service-Oriented Architectural principles </li></ul><ul><li>Discuss the application of these principles to BI and CMS </li></ul><ul><li>Explore integration scenarios and resultant unification benefits </li></ul><ul><li>Demonstrate a sample integration framework built upon the Microsoft platform </li></ul>
  3. 3. About the Author <ul><li>Architect & Developer </li></ul><ul><li>Principal of Active Interface, Inc. </li></ul><ul><li>Focus is building enterprise BI and web applications on the Microsoft platform </li></ul><ul><li>Also MS Office Systems development and integration </li></ul>
  4. 4. Presentation Objectives <ul><li>Review Service-Oriented Architectural principles </li></ul><ul><li>Discuss the application of these principles to BI and CMS </li></ul><ul><li>Explore integration scenarios and resultant unification benefits </li></ul><ul><li>Demonstrate a sample integration framework built upon the Microsoft platform </li></ul>
  5. 5. What is a Service Oriented Architecture? <ul><li>Course-granular interfaces </li></ul><ul><li>Loosely-coupled </li></ul><ul><li>Complete, self-contained messages or transactions </li></ul><ul><li>XML Web Services </li></ul><ul><ul><li>compatible with Internet protocols </li></ul></ul><ul><ul><li>cross-platform by nature </li></ul></ul>
  6. 6. Advantages of SOA <ul><li>Supports pursuit of “zero-latency enterprise” </li></ul><ul><li>Interoperability is greatly simplified </li></ul><ul><ul><li>between enterprise applications </li></ul></ul><ul><ul><li>between IT platforms </li></ul></ul><ul><ul><li>between business partners </li></ul></ul><ul><li>Development simplified </li></ul><ul><ul><li>tools can discover the capabilities exposed by a service </li></ul></ul><ul><ul><li>ease of unit testing and integration </li></ul></ul>
  7. 7. Growth of Enterprise SOA <ul><li>Future growth will likely involve vertical services, both within and between organizations </li></ul><ul><li>Services will wrap standard business logic, workflow processes, and regulatory regimes </li></ul><ul><li>Enterprise IT platform vendors are standardizing on XML Web Services for integration tasks </li></ul>
  8. 8. Presentation Objectives <ul><li>Review Service-Oriented Architectural principles </li></ul><ul><li>Discuss the application of these principles to BI and CMS </li></ul><ul><li>Explore integration scenarios and resultant unification benefits </li></ul><ul><li>Demonstrate a sample integration framework built upon the Microsoft platform </li></ul>
  9. 9. Business Intelligence <ul><li>“ BI supports processes used to analyze and act on information” </li></ul><ul><li>BI is about turning data into strategic, actionable information </li></ul><ul><li>BI is a service provided by IT to line-of-business users </li></ul><ul><li>SOA will make it possible for IT to provide better and faster service to a wider audience </li></ul>
  10. 10. Content Management <ul><li>Can also be considered as an IT service to the organization </li></ul><ul><li>Also about delivering relevant information </li></ul><ul><ul><li>right time, place, format </li></ul></ul><ul><li>While BI is data-centric, CM is document-centric </li></ul><ul><li>SOA is well suited for CM </li></ul><ul><ul><li>course-granular, loosely-coupled </li></ul></ul>
  11. 11. The Case for Unification <ul><li>Business Case </li></ul><ul><ul><li>Achieve better enterprise KM </li></ul></ul><ul><ul><li>Increase value of information </li></ul></ul><ul><li>Technology Case </li></ul><ul><ul><li>Shift burden from IT to self-serve creation and delivery if integrated reports </li></ul></ul><ul><ul><li>Eliminate manual integration and resultant errors </li></ul></ul>
  12. 12. <ul><li>Combine best-practices and best values of each domain </li></ul><ul><ul><li>Techniques of data organization and presentation used in BI are applicable to searching CM </li></ul></ul><ul><ul><li>Most BI results are best delivered into narrative documents </li></ul></ul>Cross-Fertilization
  13. 13. Presentation Objectives <ul><li>Review Service-Oriented Architectural principles </li></ul><ul><li>Discuss the application of these principles to BI and CMS </li></ul><ul><li>Explore integration scenarios and resultant unification benefits </li></ul><ul><li>Demonstrate a sample integration framework built upon the Microsoft platform </li></ul>
  14. 14. Content Management as SOA <ul><li>CMS framework based upon SOAP and XML web services </li></ul><ul><li>Low-level tier exposes services for content-oriented storage </li></ul><ul><li>High-level tier exposes workflow services </li></ul>
  15. 15. CMS Repository Services <ul><li>Low-level document-centric services </li></ul><ul><ul><li>structured storage </li></ul></ul><ul><ul><li>structured search </li></ul></ul><ul><ul><li>revision control </li></ul></ul><ul><ul><li>access control </li></ul></ul><ul><li>WebDAV and DeltaV are industry standards for this layer </li></ul><ul><li>SQL 2005 SOAP/XML features are another option </li></ul>
  16. 16. CMS Workflow Services <ul><li>High-level services </li></ul><ul><ul><li>document management </li></ul></ul><ul><ul><li>fragmentation and composition </li></ul></ul><ul><ul><li>Multi-channel/format output </li></ul></ul><ul><ul><li>publish/subscribe </li></ul></ul><ul><ul><li>editorial process </li></ul></ul>
  17. 17. Architecture Overview Web Service Browser CM Repository Service CM Workflow Service BI Workflow Service BI Repository Service
  18. 18. Business Intelligence as SOA <ul><li>Provide BI as a service which can be consumed by user-facing tools or by other apps </li></ul><ul><li>Enterprise reporting delivered with SOAP web services </li></ul><ul><li>Emerging support from MS BI platform </li></ul><ul><ul><li>SOAP access to tables, cubes, etc. </li></ul></ul>
  19. 19. BI storage/access services <ul><li>Low-level data-centric services for </li></ul><ul><ul><li>datasource discovery </li></ul></ul><ul><ul><li>metadata browsing </li></ul></ul><ul><ul><li>tabular and multidimensional querying </li></ul></ul><ul><ul><li>access control </li></ul></ul><ul><li>Available from MS in the form of XML for Analysis </li></ul><ul><ul><li>see www.xmla.org </li></ul></ul><ul><ul><li>Native provider in SQL 2005 </li></ul></ul>
  20. 20. BI Workflow Services <ul><li>High-level web services for </li></ul><ul><ul><li>data exploration and manipulation </li></ul></ul><ul><ul><li>information visualization </li></ul></ul><ul><ul><li>bookmarks </li></ul></ul><ul><ul><li>collaboration </li></ul></ul><ul><ul><li>annotation of discoveries </li></ul></ul>
  21. 21. Architecture Overview Web Service Browser CM Repository Service CM Workflow Service BI Workflow Service BI Repository Service
  22. 22. Presentation Objectives <ul><li>Review Service-Oriented Architectural principles </li></ul><ul><li>Discuss the application of these principles to BI and CMS </li></ul><ul><li>Explore integration scenarios and resultant unification benefits </li></ul><ul><li>Demonstrate a sample integration framework built upon the Microsoft platform </li></ul>
  23. 23. Integrating BI & CM in SOA <ul><li>Integration can occur at workflow or storage tier </li></ul><ul><li>Integration can be </li></ul><ul><ul><li>ad-hoc, user-driven </li></ul></ul><ul><ul><li>pre-defined, process-driven </li></ul></ul><ul><li>Integration can go in either direction </li></ul>
  24. 24. Architecture Overview Web Service Browser CM Repository Service CM Workflow Service BI Workflow Service BI Repository Service
  25. 25. Scenario 1: CM feeds BI <ul><li>Document taxonomy and index is fed into an OLAP cube </li></ul><ul><li>BI workflow and user interface provide direct manipulation browsing and searching of the document cube </li></ul><ul><li>Drill-through from OLAP view to actual documents </li></ul>
  26. 26. Sequence diagram of scenario 1 Web Service Browser CM Repository Service CM Workflow Service BI Workflow Service BI Repository Service
  27. 27. Scenario 2: BI feeds CM <ul><li>Using BI workflow service, user creates bookmarks of interesting analytic results </li></ul><ul><li>BI bookmarks are brought into a CM report creation workflow </li></ul><ul><li>User adds written comments, opinions, explanations, recommendations, etc. </li></ul><ul><li>Final report has an overview, several analysis pages with charts and graphs </li></ul><ul><li>Report is published to intranet </li></ul>
  28. 28. Sequence diagram of scenario 2 Web Service Browser CM Repository Service CM Workflow Service BI Workflow Service BI Repository Service
  29. 29. Presentation Objectives <ul><li>Review Service-Oriented Architectural principles </li></ul><ul><li>Discuss the application of these principles to BI and CMS </li></ul><ul><li>Explore integration scenarios and resultant unification benefits </li></ul><ul><li>Demonstrate a sample integration framework built upon the Microsoft platform </li></ul>
  30. 30. Web Service Browser <ul><li>Traditional browser uses HTTP to retrieve HTML content </li></ul><ul><li>A “web service browser” uses HTTP to send and receive SOAP messages </li></ul><ul><li>Client-side script orchestrates the interaction, using DHTML to render the UI </li></ul><ul><li>Current-generation browsers have the requisite support for building web service user interfaces </li></ul><ul><ul><li>XML, XSLT, & DHTML </li></ul></ul>
  31. 31. ThinCMS <ul><li>My work on SOA-based Web CMS frameworks </li></ul><ul><li>Models pages as compositions of XHTML “parts” </li></ul><ul><li>Web Page Composition Markup Language (WPCML) is an XML schema and XSL conventions for composing pages via XSLT processor </li></ul><ul><li>Uses nested and referenced page parts </li></ul>
  32. 32. Nested composition parts page section site section section page page page Content Nesting Template Nesting page(s) section site section section page(s) page(s)
  33. 33. Referenced composition parts Element 1 Element 2 Page 1 Section 1 Site Section 2 Page 2 Page 3
  34. 34. ThinOLAP <ul><li>My work on SOA and Web based framework for Business Intelligence </li></ul><ul><li>Implements the two-tiered conceptual model described earlier </li></ul>
  35. 35. Demo
  36. 36. Other Integration Scenarios <ul><li>“ Semi-static” publishing </li></ul><ul><li>Specialized information visualization services </li></ul><ul><li>Use of SOA to integrate BI and CM with CRM, ERP, SCM, etc. </li></ul>
  37. 37. The Future of Integration <ul><li>Integration of standards-based SOA components </li></ul><ul><li>Integration links can evolve with a company's business or application portfolio </li></ul><ul><li>Broad industry support workflow-level standards for BI, CM, etc. </li></ul><ul><li>Vendor shakeout as some tiers are commoditized </li></ul>
  38. 38. Conclusion <ul><li>Service-oriented architectures allow enterprises to leverage their investments in IT and to showcase enterprise process excellence </li></ul><ul><li>A seamless BI/CM integration would go a long way towards embedding analytics into the fabric of a business user’s daily tasks </li></ul>
  39. 39. Questions ?
  40. 40. Questions? <ul><li>Thanks for attending! </li></ul><ul><ul><li>Chris Harrington </li></ul></ul><ul><ul><li>[email_address] </li></ul></ul>

×