4.4b Stage 4b – Internet Mashups

4.4b.1 Overview

Question : What are Enterprise Mashups ?

We can define Enterprise Mashups simply as a Web 2.0 technique that allows data to be integrated by using APIs that deliver the data to the page or screen.

This greatly simplifies the tasks involved, compared to the conventional techniques of data integration closer to the database sources.

Question : How can I check if anyone is using Mashups in my organisation ?

This question is important because it provides a measure of unsatisfied demand within your organization for new reports and analysis of data.

The best way to address this question is to use the Intranet to build a Knowledge Management ‘Community of Professionals’ for Mashups.

Wikipedia provides a useful introduction to Enterprise Mashups –

• http://en.wikipedia.org/wiki/Enterprise_mashups

Wikipedia defines Enterprise Mashups as :-

“a Web application that combines data from one or more sources … thereby creating a new and distinct Web service that was not originally provided by either source.

A Mashup [is] frequently . by APIs, [for example] data from Google Maps combined with location real estate data.”

4.4b.2 Best Practice

Best Practice will discuss how to prepare a Business Case and create Mashups

Mashups are most frequently created by Developers, but they are increasingly being produced using Web Sites like Boomi, that offer high-level Tools that can be used by non-professional developers.

Mashups are frequently associated with Widgets that are placed on PC Pages or Mobile screens to run the Mashup.

4.4b.3 Templates

Templates cover specification of User Requirements and compliance with Data Governance.

4.4b.4 Tools

Tools for creating Mashups are provided by a number of commercial Suppliers, for example :-

• Boomi – http://www.boomi.com/
• Google Mashup Editor - http://en.wikipedia.org/wiki/Google_Mashup_Editor
• Jackbe - http://en.wikipedia.org/wiki/JackBe
• Microsoft Popfly - http://en.wikipedia.org/wiki/Microsoft_Popfly

4.4b.5 Tutorials

A simple Tutorial which provides an insight contains the following steps :-

• 1) Identify the Data Sources, such as RSS Feeds or Google Maps
• 2) Obtain the APIs for each Source
• 3) Map the API data items to a common data structure.
• 4) Using the appropriate programming language such as Apex, code the User Interface (UI)
• 5) Finally, behind the UI, code the integration of the data.

Additional Tutorials will be derived from a review of Mashup Data Architectures.

Microsoft’s highly respected Scott Guthrie mentions a Mashup Tutorial in his Blog :-

• http://weblogs.asp.net/scottgu/archive/2006/03/27/441267.aspx

Microsoft has an excellent page on Enterprise Mashups in their Architecture Journal :-

• http://msdn.microsoft.com/en-us/library/bb906060.aspx

which says “… all mashups are RESTful in nature (they conform to the Representational State Transfer principles)” and contains this very helpful diagram of the Architecture of a typical Mashup :-

Here is the highly recommended Microsoft Architecture Center :-

• http://www.skyscrapr.net/

4.4b.6 How do I ?

4.4b.6.1 Demonstrate the potential value of Mashups ?

The best way to demonstrate the potential is to produce something quickly that meets a genuine business requirement.

The best way to identify the requirement is to engage with Stakeholders to determine what kind of data they need that they are not currently getting, especially data that comes from more than one source .

4.4b.7 Qualities for Success in creating Mashups

To be successful in creating Mashups it is necessary to possess a number of qualities :-

• To have some level of experience as a developer
• to like to work with user people
• to enjoy seeing results produced quickly that meet a clearly defined User requirement.
• to enjoy keeping up-to-date with innovations in fast-moving technology
• to be able to recognize innovations that are important and have lasting power.