ESB using Message Broker - How to implement SOA?
IBM announced on January 26, 2005, a new service to help companies build capabilities that support business goals, while freeing up currently overstretched IT budgets to focus on growth opportunities. The new Service Oriented Modeling and Architecture (SOMA) is an innovative approach to solving a significant problem, a consistent way for businesses to develop flexible technology that will provide the maximum return back to the business. It helps companies implement a service-oriented architecture (SOA), a standards-based framework that enables enterprises to evolve to on demand businesses that integrate data and applications with customers, partners and suppliers. What is SOA?
SOA is a concept based on an architectural style that defines an interaction model between three primary parties: the service provider, who publishes a service description and provides the implementation for the service, a service consumer, who can either use the uniform resource identifier (URI) for the service description directly or can find the service description in a service registry and bind and invoke the service The architecture style defining a SOA describes a set of patterns and guidelines for creating loosely coupled, business-aligned services that, because of the separation of concerns between description, implementation, and binding, provide unprecedented flexibility in responsiveness to new business threats and opportunities.
Fig 1 : SOA Reference Architecture
A SOA is an enterprise-scale IT architecture for linking resources on demand. In a SOA, resources are made available to participants in a value net, enterprise, line of business (typically spanning multiple applications within an enterprise or across multiple enterprises). It consists of a set of business-aligned IT services that collectively fulfill an organization’s business processes and goals. You can choreograph these services into composite applications and invoke them through standard protocols. Service-oriented modeling approach provides modeling, analysis, design techniques, and activities to define the foundations of a SOA. It helps by defining the elements in each of the SOA layers and making critical architectural decisions at each level. Service-oriented integration is an evolution of Enterprise Application Integration (EAI) in which proprietary connections are replaced with standards-based connections over an ESB notion that is location transparent and provides a flexible set of routing, mediation, and transformation capabilities.
WebSphere Message Broker is a broker engine that can perform message transforming and routing from different participants to different destinations based on user-defined rules, so that diverse applications can exchange information in dissimilar forms, with brokers handling the processing required for the information to arrive at the right place in the correct format. One of the WebSphere Message Broker’s strengths is its powerful capability for parsing different formats of messages coming from different channels or protocols, manipulating the message, and serializing the message in different wire formats and protocols. WebSphere Message Broker is flexible enough to support different messaging paradigms like synchronous and asynchronous behavior, different message interaction patterns like fire-and-forget, request-reply, publish-subscribe, and its aggregation capability.
Websphere Message Broker as ESB:
SOA defines an approach to reuse and extend current application assets in a very flexible way. This is done by separating the service interface and the service implementation. Each application that provides business logic is exposed as a service.
An ESB provides virtualization and management of service interactions between communicating participants. It not only provides the connection layer between the service provider and service consumer, but it also helps with the...
Please join StudyMode to read the full document