SharePoint Saturday Sydney - Enterprise Mashups


Published on

SharePoint as a platform for Enterprise Mashups. SharePoint Saturday Sydney, August 2009.

Published in: Technology
  • Be the first to comment

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

No notes for slide
  • Mashups versus composite applications Lots of definitions out there talking about the difference between mashups and composite applications. Some say composites are based on business data and mashups on Internet content. Others say composites are build by developers and mashups are built by end-users. I use mashups as a generic term to cover all of the above.
  • There are few other SharePoint Saturday sessions that are related to mashups.
  • Includes a few Australian government APIs. E.g. ABN lookup.
  • Security: Defining authorisation hierarchies in LOB systems is often a significant investment. Reflect authorisation in back-end systems. SSO required. Read-only scenarios: Mashups are not an all-powerful editing surface capable of editing any and all data. The LOB system is still the best interface for that. The last thing you want to do is go down the path of redeveloping the whole interface of a LOB system. Data problems: If there are substantial data problems, then solve those. Don’t use mashups to plaster it all together. LOB system experts: You will need to engage with other groups within the organisation. It makes sense, but you’ll be surprised how often there is too much separation between different IT practices.
  • Enter the raffle by filling in the session feedback forms. Lots of awesome give-aways. Employees of sponsors will not be eligible to win raffle prizes at all.   Head to the pub afterwards!
  • SharePoint Saturday Sydney - Enterprise Mashups

    1. 1. SharePoint as a Platform for Enterprise Mashups Kristian Kalsing – Extend Technologies
    2. 2. Agenda
    3. 3. Mashup Definition <ul><li>In web development, a mashup is a web page or application that combines data or functionality from two or more external sources to create a new service . </li></ul>
    4. 5.   Screen clipping taken: 6/08/2009, 4:05 PM    
    5. 6. Elements of Mashups
    6. 7. Elements of SharePoint Mashups
    7. 8. Motivation for Enterprise Mashups <ul><li>Delivering business data to casual users in an environment they are comfortable in </li></ul><ul><li>Role-specific solutions </li></ul><ul><li>Outside-in approach as opposed to inside-out </li></ul><ul><li>Serving the long tail of specialised needs </li></ul><ul><li>Decentralising innovation </li></ul>
    8. 9. Why SharePoint for Mashups? <ul><li>SharePoint has all the building blocks </li></ul><ul><ul><li>Platform services, web parts, BDC, search, etc. </li></ul></ul><ul><li>Independent of back-end systems </li></ul><ul><li>.NET is a mature and robust application platform </li></ul><ul><li>Resources are relatively easy to come by </li></ul><ul><li>Growing eco-system of third-party web parts </li></ul>
    9. 10. OFFICE DIRECTORY <ul><li>Demonstration </li></ul>
    10. 12. PRODUCT CATALOGUE <ul><li>Demonstration </li></ul>
    11. 14. SINGLE VIEW OF CUSTOMER <ul><li>Demonstration </li></ul>
    12. 16. Key Web Parts for Mashups
    13. 17. Public APIs <ul><li> </li></ul><ul><li>API directory (1,300+) </li></ul><ul><li>Mashup directory </li></ul><ul><li>Sample code </li></ul>
    14. 18. Critical Success Factors <ul><li>Security and SSO </li></ul><ul><li>Focus on high ROI scenarios, usually read-only </li></ul><ul><li>Not for solving enterprise data problems </li></ul><ul><li>Work with the LOB system experts </li></ul>
    15. 19. Summary
    16. 20. Thanks to our sponsors
    17. 21. KINGS OF LEON – SEX ON FIRE CYPRESS HILL – HITS FROM THE BONG By Something With Numbers on Triple J’s Like A Version, June 2009 <ul><li>Another Mashup </li></ul>