February 28, 2008   Sign In |  About ebizQ |  Contact Us |  Join ebizQ Gold Club
Gian Trotta
First Look
Join ebizQ producers Gian Trotta and Krissi Danielson for interviews with the innovators, movers and shakers behind emerging enterprise software solutions.Have a solution that qualifies? E-mail Gian at gtrotta(at)ebizq.net

« Vitria's Open, Agnostic SOA and Exception Handling Products | Main | Appian Enterprise 5.5: BPM Via Your iPod? »

April 10, 2007
Integration Consortium Chairman: A New Focus on Community and Architecture


Listen to the entire 15:09 podcast Download file


     Agenda and Resources

1. Power of the community approach

2. Outsourcing the individual

3.  Fostering the SOA community

4.  Architecture as a crucial aspect of integration

5.  Holistic view of enterprises simplifies integration projects

6. REST's increasing role

Read a complete transcript of the podcast here

Learn about the IC's Awards for Excellence Contest

For more information visit www.integrationconsortium.org

Note: John Schmidt will respond to comments posted below.


 

 

 


John Schmidt will regularly respond to any comments posted below.

 
John Schmidt, Chairman of the Integration Consortium and Senior Vice President Responsible for Enterprise Architecture at Wells Fargo Bank recently spoke to ebizQ's Gian Trotta about the the role of community and architecture in integration.

The Power of Community

The Integration Consortium (IC) is encouraging its membership base to embrace the community approach.  Many vendors including SAP have created large communities where both employees and clients interact through wikis, blogs, forums, and surveys.

Schmidt points out, “The power of community - is how communities on the global scale can create economy... it's almost like enabling outsourcing at the individual level.”

Web 2.0’s emphasis on user created content allows global communities to form quickly.

IT practitioners are, “leveraging things like wikis, blogs, and other events to collaborate in real-time with other individuals... to extend their network of peers outside the four walls of their company, so really, there are no walls -- anybody in the world could be interacting. And they're taking their problems and their professional challenges to the world.”

One of the IC’s main goals is to encourage and facilitate the continued development of the integration community.

The Community Around SOA

Schmidt went on to describe the specific community around SOA.  The Integration Consortium is fostering the community surrounding SOA by enabling sharing of best practices via papers, conferences, and webinars.

Any SOA solution is dependent on best practices and a community approach is the most efficient means of sharing and developing best practices.

The IC is not only facilitating individual community involvement, but also helping community organizations develop.  The IC is one of the founding organizations that helped launch the SOA consortium, which was a spin-off from what was previously known as the SOA Alliance.

The IC also works collaboratively with many groups.  One example is the Synergy Project, a joint project of the OMG, the Open Group and the Integration Consortium.  Schmidt says, “It’s really trying to rationalize our model, to figure out how MDA, model-driven architecture, which is an OMG practice, aligns with and performs with TOGAF which is The Open Group’s architecture framework.” 

The IC brings end-user perspective to the project facilitating a true community wide approach.

Architecture is an Important Aspect of Integration


The IC is also emphasizing architecture’s role in integration.  In the past, architecture was not viewed as an important aspect of integration.  Today, the IC encourages its members to consider architecture as an integral aspect of integration.

Schmidt says, “Integration and architecture have always been two sides of the same coin. Architecture is a lot more about structure, frameworks and standards, while integration is more about the implementation and execution side of the challenges and how can large organizations effectively share information in processes in a consistent fashion.”

Schmidt continues,  “Integration at a business level is really just about getting people to communicate, sharing information across functional areas, serving customers consistently across channels and, in that context, architecture is just as important as the actual Middleware components or software tool they might use to implement it.”

Taking a Holistic View of the Enterprise

While integration projects have a historically high rate of failure, Smith believes there are ways to simplify the process.

“We need to look at our enterprises as a system of systems... while a specific organization may have 1000 or 2000 application systems, they're all connected. They all run in the same network. They're all sharing information. They're all serving the same customer.”

This holistic view enables truly effective modeling, Schmidt says, “We take this incredible high complexity that exists in today's IT world, break it up into manageable functional components through a disciplined process and through standard architectures, define how those components can come back together and play in an end-to-end business process world.”

The IC believes proper modeling based on a holistic view of an organization coupled with community based best practice development will increase the success rates of integration projects.

The Annual Global Integration Summit takes place May 14-15 in Banff,

This event covers a wide range of topics and draws exceptional practitioners from around the world.  The summit is unique in its academic based peer-review process.

Schmidt says, “The peer-review process has generated a very high-quality event. The Conference proceedings book is probably one of the only, if not the only, peer-reviewed business-oriented journal that is published on an annual basis in the integration and architecture space.”

The conference offers a variety of content.  For example, collaborative work analysis, partnering, case studies of real-life implementations, emerging architectures, etc.

The IC will continue its work after the Global Summit.  Schmidt says, “We're taking portions, or kind of a lighter-weight version of the Global Summit, out on the road. Some of the cities that it will be in include Minneapolis, the Twin Cities, New York, Atlanta and this year we're also doing one in Brussels, in combination with the OMG.”


For more information visit:  www.integrationconsortium.org

Executive Summary by Michael Wienick

 

 


Posted by gtrotta in |Digg This|Add to del.icio.us

Trackback Pings

TrackBack URL for this entry:
http://www.ebizq.net/mt/mt-tb.cgi/1670

Comments

Posted by: Ron Taggirt at May 8, 2007 02:27 PM | Permalink

The World Wide Web is arguably the largest network application in the world - specifically, a hyper-media application. The web is massively scaleable consisting of millions of computers containing billions of pages of directly addressable content. The web is fast when you consider how quickly a URL reference is resolved to find the specific computer regardless of where it is in world. Furthermore it all works seamlessly despite the anarchy - anyone can plug anything into the web at any time without an overall coordinated plan. Finally, the web is secure and resilient considering the hostile environment it operates under.

This is no accident. The architecture of the Web is beautiful in its elegance and has enabled it to grow to the mind boggling scale it is today. The architecture of the web is surprisingly simple with a small number of protocol and data constraints that are built on a highly efficient network infrastructure.

The architecture of the web is called Representational State Transfer – or REST for short - as described by Roy Fielding in his doctoral dissertation Architectural Styles and the Design of Network-based Software Architectures. The complete paper can be downloaded from the IC member site at
http://icsoawiki.icmembers.org/document/download/1098
.
The key design principles that give the web its desirable properties include:
· Application state and functionality are divided into resources
· Every resource is uniquely addressable using a universal syntax
· All resources share a uniform interface for the transfer of state between client and resource, consisting of a constrained set of well-defined operations and a constrained set of content types
· A protocol that is Client/Server, stateless, cacheable and layered

The exciting thing about REST from my perspective is that it serves as a terrific case study for a successful architecture. We could learn some lessons from REST and improve the success of SOA implementations by applying them. For further background information, and to engage in a dialog on the pro’s and con’s of REST vs. SOA, please check out my BLOG at http://www.icmembers.org/blog/software-ecologist.

Posted by: John Schmidt at May 17, 2007 06:47 PM | Permalink

Post a comment




Remember Me?

(you may use HTML tags for style)

We ask that you type your code (displayed below) in the text box.This code is an image that cannot be read by a machine. It prevents automated programs from submitting comments.


Code:



Most Recent ebizQ Blog Entries
ADVERTISEMENT
Subscribe
Gian Trotta 's Articles
This Work
Accountability:The opinions expressed in this blog are solely representative of the blog's author, and not of ebizQ

Blogosphere

Marketing Solutions | Feedback | About ebizQ | Unsubscribe | Privacy Policy | Site Map