The Microsoft OBA Framework
Lately Microsoft has been touting a new way to build composite applications that will connect back end Line of Business applications to the front office via Microsoft Office using the acronym, "OBA". OBA stands for Office Business Applications which Microsoft intends as a new framework for developers and ISVs to build applications utilizing Microsoft Office as the entry point.
The intended sweet spot for OBA is within the Lines of Business within the greater Enterprise cloud and will capitalize on the large number of Microsoft Office licenses that have been sold world-wide.
The OBA framework supports Office versions 2003 forward and is accessed via the following integration points:
- Microsoft Office SharePoint Server (provides a convenient end-to-end Web framework)
- Open XML (at the document level)
- Microsoft Office Extensible UI capabilities
- Via SharePoint on the server side
- Via Word, Excel, InfoPath with VSTO
- MOSS 2007 Business Data Catalog (BDC)
- Microsoft Enterprise Search
- Windows Workflow (which shipped in Windows Vista, Office 2007 and the .NET Framework 3.0)
- Microsoft Dynamics
While this may seem an OZ like scenario to the Microsoft fold, others feel OBA is too little too late. Ephraim Schwartz of InfoWorld wrote:
"Microsoft is trying to say that Office is relevant and that it can become a development platform that can integrate and operate with other vertical applications to create something new. Microsoft hopes that one plus one will equal three."
Ephraim goes on to explain why:
"I think Microsoft is reading the market wrong. OBAs remind me of the old school EAI, enterprise application integration technology while the entire world is moving to an SOA architecture. Mashups can do the same thing and over time I think even the most staid of enterprises will not wait for Microsoft to launch its next OBA RAP solution."
This debate is beginning to heat up with the recent Eweek slideshow titled: "Why Microsoft Ultimately Will Triumph Over Google (and Vice Versa)".
What are your thoughts? Who wins in the clash between Rich Client and Thin Client when building composite applications?
in some ways it just makes sense
Re: in some ways it just makes sense
But in other ways it looks dangerous