We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.

Its essential that buildings be constructed on solid foundations, and enterprise integration efforts are no different. Having well-planned and executed integration architectures virtually assures companies of getting the best performance and ROI from those efforts.

In the ebizQ webinar Developing an Application Integration Architecture, ebizQ Vice President for Strategic Services Beth Gold-Bernstein and Candle Corp. Senior Architect Peter Rhys Jenkins present the building blocks of an integration architecture, explain its advantages to organizations, and offer best practices for putting one together.

The Candle-sponsored hour is part of the Mapping Out the Right Integration Solution series, whose name is no accident: The series goes into detail on different aspects of ebizQ's Roadmap to Integration Technology. The map, Gold-Bernstein pointed out, is designed to help companies struggling to understand how to deploy the plethora of integration technologies now available. Whats more, all components of the map are clickable, leading ebizQ.net visitors to the vendors offering those products or services.

In a presentation peppered with real-life examples, Gold-Bernstein and Rhys Jenkins discussed various patterns of application integration. Gold-Bernstein called it the baseline technology for all integration architectures. Those patterns, she pointed out, are not mutually exclusive and in fact overlap and are used in various combinations in integration architectures.

Rhys Jenkins began by telling of a recent incident in which he booked a room at a swanky Manhattan hotel through hotels.com, only to be told when he arrived that his reservation wasnt in the hotels computer system. Why? Because, even though hotels.com is an online operation, its reservations with that hotel are faxed over and hand-keyed in later. And that hadnt happened yet. A striking example, Rhys Jenkins said, of the abundance of low-hanging fruit out there where better integration between systems, in this case, B2B integration, would benefit customers and companies alike.

The basic application integration patterns include:
  • Message Brokers: Generally, they have hub-and-spoke designs, with a server in the middle performing services such as translation, transformation and routing, with adapters connecting them to applications. They provide basic messaging services, which Gold-Bernstein dubbed an underlying technology that enables integration, often through integration with IBMs MQ series, which Rhys Jenkins called the de facto standard in this sector (with some 75 percent of the market). Gold-Bernstein observed that you always want to design for agility and change. Along those lines, Web services are becoming a standard application integration interface but, Gold-Bernstein said, they dont provide all integration needs, such as transformation, translation, routing, and messaging.
  • Enterprise Service Buses (ESBs): Rather than a hub-and-spoke design, ESBs feature a distributed bus architecture, making them inherently more scaleable than message brokers, Gold-Bernstein commented. In addition, You dont have a single point of failure. You can distribute and federate these services.
  • Legacy Systems: Whats most important here, Gold-Bernstein stressed, is that there are different ways to get at legacy systems. Among them: through the data level, through messaging interfaces, screen-scraping (a of last resort, Gold-Bernstein opined), and through service interfaces, which she described as a long-term architectural approach to enabling the mainframe to participate in newer applications for the future. That involves making services out of those legacy apps, which is where Web services come in. Rhys Jenkins added that Web services enable you to bridge the .NET and Java worlds, something he sees as becoming a lot more prevalent.
  • Portals: They take information from different back-end systems and make it available from one, easy interface. Application at the glass, Gold-Bernstein quipped. Rhys Jenkins noted the emerging importance of portlets, and added that portals are meant for businesspeople. Theyre for business solutions, where you care about the end-to-end view, looking at the whole thing.
  • Mobile Solutions: They involve many back-end integration services, Gold-Bernstein noted, and use a mobile server to rationalize the presentation of the different services to various types of mobile devices. There are additional requirements for mobile integration that layer on top of other integration infrastructure services. Security is of particular concern here, she pointed out, something Rhys Jenkins wholeheartedly agreed with. He also urged viewers to turn on encryption abilities that come standard with mobile systems, but arrive in the off position as their default mode.
  • B2B: These systems enable companies to hook up with customers, suppliers and partners outside the firewall. Back-end integration is needed to automate transactions. Other B2B services are required, such as partner management, detailing how partners will communicate with you and the terms of service level agreements. EDI, Rhys Jenkins observed, isnt going away anytime soon, but is trending more toward real-time rather than batch. Gold-Bernstein pointed out that EDI is expensive, so only large organizations can afford it, but B2B connectivity is slowly being extended to smaller partners through such less expensive means as Web browsers and XML. Another possibility: outsourcing B2B connectivity through vendors such as Grand Central Communications and Hubspan.

For each of the patterns, reference architectures were provided to viewers. The reference architectures pointed out the redundancy of technologies and services across these patterns. Overall, Gold-Bernstein said, those patterns are the underlying technologies that will enable the integration infrastructure of the future. You can build upon them. There are many benefits to looking at this from an enterprise point of view and building an integration architecture. Among them: avoiding redundancy (You dont want to, for example, have portals with different integration technology than your B2B integration. You dont want to have, as many companies do, five different adapters to one application because youve had five different tactical solutions that had to integrate with that back-end application.) In the long run, reducing redundancy reduces maintenance costs, since you have fewer technologies to run, and training costs, since you need fewer skill sets on hand. Also, You want to reduce the need to integrate integration technologies, Gold-Bernstein emphasized: That will be the bottom line, down the line. To maximize ROI, maximize reuse. And just one more reason for taking the enterprise approach to building an integration infrastructure is it enables you to look at patterns, and understand the overlap among them to help you avoid costly mistakes by doing it right the first time.

Then the speakers ran down numerous application integration architecture best practices, such as employing service oriented architectures (SOA) to maximize reuse and agility, creating a centralized architecture group and/or integration competency centers, architecting for performance and reliability and, Gold-Bernstein strongly advised, not implementing what you cant manage. Because down the road, it will break (Rhys Jenkin chimed in here that he agreed one thousand percent). You want to architect things to work together from the get-go, Gold-Bernstein suggested, because then youll know you can manage it over time. But if they do break, Rhys Jenkins added, consider some of the emerging autonomic computing solutions meant to fix themselves.

For much more detail on structuring your companys integration architecture, tune in to a replay of Developing an Application Integration Architecture.



Explore Our Topics

  • Virtual Conferences
  • Webinars
  • Roundtables

BPM in Action

March 10, 2011

The sixth annual BPM in Action 2011 Virtual Conference will explore cutting-edge market developments in BPM and describe how to leverage them for improved business operation and performance. More

View All Virtual Conferences

Smart Case Management: Why It's So Smart.

Date:Nov 05, 2009
Time:12:00 PM ET- (17:00 GMT)


Date:Oct 29, 2009
Time:15:00 PM ET- (19:00 GMT)

View All Roundtables
  • Research Library
  • Podcasts
  • News

Joe McKendrick: Part II of II: Designing Evolve-ability into SOA and IT Systems

In part two of Joe McKendrick's recent podcast with Miko Matsumura, chief strategist for Software AG, they talk about how SOA and IT systems need to change and grow and adapt with the organization around it.

Listen Now

Phil Wainewright: Helping Brands Engage with Social Media

Phil Wainewright interviews David Vap, VP of products at RightNow Technologies, and finds out how sharing best practices can help businesses understand how best to engage with online communities.

Listen Now

Peter Schooff: Making Every IT Dollar Result in a Desired Business Outcome: Scott Hebner of IBM Rati

Scott Hebner, Vice President of Marketing and Strategy for IBM Rational, discusses a topic on the top of every company's mind today: getting the most from IT investments.

Listen Now

Jessica Ann Mola: Where Will BI Fit In? Lyndsay Wise Explains

In BI, this tough economy and the increasing role of Web 2.0 and MDM are certainly topics on people's minds today. WiseAnalytics' Lyndsay Wise addresses each of them in this informative podcast.

Listen Now

Dennis Byron: Talking with...Deepak Singh of BPM Provider Adeptia

Deepak Singh, President and CTO of Adeptia, joins ebizQ's Dennis Byron in a podcast that gets its hand around the trend of industry-specific BPM.

Listen Now
More Podcasts
  • Most Popular
  • Quick Guide
  • Most Discussed

Quick Guide: What is BPM?

Learn More

Quick Guide: What is Event Processing?

Smart event processing can help your company run smarter and faster. This comprehensive guide helps you research the basics of complex event processing (CEP) and learn how to get started on the right foot with your CEP project using EDA, RFID, SOA, SCADA and other relevant technologies. Learn More

Quick Guide: What is Enterprise 2.0?

A lot of people are talking about Enterprise 2.0 as being the business application of Web 2.0 technology. However, there's still some debate on exactly what this technology entails, how it applies to today's business models, and which components bring true value. Some use the term Enterprise 2.0 exclusively to describe the use of social networking technologies in the enterprise, while others use it to describe a web economy platform, or the technological framework behind such a platform. Still others say that Enterprise 2.0 is all of these things. Learn More