Enterprise Dashboard Mashups
The recent post on Dashboards By Example on creating WebSphere Portal Dashboard Mashups using Google Gadgets triggered a few discussions on whether or not the public APIs (Google Maps, etc) consumed by mashup dashboards and applicaitons will really be embraced by Enterprise IT. The hesitation expressed concerned the lack of ownership and control of the data.
For those of you that didn’t see the post, I basically ran through some of the impact that Web 2.0 has had on enterprise dashboards. In particular, I discussed how the availability of APIs from Amazon, Google, Yahoo, etc has allowed a surge of Dashboard Mashups - or dashboards that consume both data and behavior from many difference sources. Think of it as web services and SOA come true in its most user-centric way.
There was no doubt among the Dashboard Spy readership that the user experience will benefit, but some dashboarders with a traditional IT mindset seemed a little “scared” of the fact that their applications would be exposing both data and behavior that they did not own.
I point out the very informative InfoWorld article from July 28, 2006 called Enterprise Mashups: Web 2.0 Style Integration at the Browser Isn’t Just for Consumer Apps Anymore and Businesses Are Starting to Take Notice.

I took the liberty of “borrowing” a couple of key graphics from the article (Once a Dashboard Spy, always a Dashboard Spy, I suppose!).
First, let’s have a look at what they call “The beautiful simplicity of mashups”.

Here is a listing of what they identified as enterprise mashup best practices:









