IBM WebSphere Message Broker

From Wikipedia, the free encyclopedia

WebSphere Message Broker (WMB) is IBM's information broker from the WebSphere product family that allows business information to flow between disparate applications across multiple hardware and software platforms. Business rules can be applied to the data flowing through the message broker to route and transform the information. The product can be considered to be an Enterprise Service Bus providing connectivity between disparate applications.

Contents 1 History 2 Components 3 How Message Broker works 3.1 Overview 3.2 Broker nodes available 3.2.1 Node types 4 Supported platforms 4.1 Operating systems 5 Trivia 6 References 7 See also 8 External links

[edit] History

Originally the product was developed by a company named 'NEON', short for 'New Era of Networks' which was later acquired by Sybase. The product was developed by New Era of Networks and re-branded as IBM product called 'MQSeries Integrator' or 'MQSI' for short. Versions of MQSI ran up to 2.1. The product was added to the Websphere family and rebranded 'Websphere MQ Integrator', still version 2.1. From 2.1 the version numbers are synchronized with the rest of the Websphere family and jumped to version 5.0. The name changed to 'Websphere Business Integration Message Broker' (WBIMB). In this version the development environment was redesigned using Eclipse and support for Web services was integrated into the product. The current major version 6.1 is branded as 'Websphere Message Broker'.

[edit] Components

WebSphere Message Broker consists of four components:

• Broker
• Configuration Manager
• User Name Server
• WebSphere Message Brokers Toolkit

[edit] How Message Broker works

[edit] Overview

The WebSphere Message Broker Toolkit enables developers to graphically design message flows and related artifacts. Once developed, these resources can be packaged into a broker archive (BAR) file and deployed into the runtime environment. At this point, the broker is able to continually process messages according to the logic described by the message flow^[1].

WebSphere Message Broker flows can be used in a Service Oriented Architecture, and if properly designed by Middleware Analysts, integrated into event-driven SOA schemas, sometimes referred to as SOA 2.0.

[edit] Broker nodes available

A developer can choose from many pre-designed broker nodes. Nodes have different purposes. Some nodes map data from one format to another (for instance, Cobol or PL/I Copybook to canonical XML). Other nodes evaluate content of data and route the flow differently based on certain criteria.

[edit] Node types

The following node transformation technology options are available:^[2]

• Extended Structured Query Language (ESQL)
• Graphical Message Mapping
• eXtensible Stylesheet Language Transformations (XSLT)
• JavaCompute (as of version 6)
• WebSphere Transformation Extender (formerly known as Ascential DataStage TX, DataStage TX and Mercator Integration Broker) is available as a separate licensing option^[3]

[edit] Supported platforms

[edit] Operating systems

Currently available platforms for WebSphere Message Brokers 6.1 are:

• AIX
• HP-UX (PA-RISC and IA64)
• Solaris (SPARC and x86-64)
• Linux (x86, x86-64, PPC and 390x)
• Microsoft Windows
• z/OS

[edit] Trivia

• The Configuration Manager repository was named "BERNARD" after the Configuration Manager development team’s pet gargoyle.^[4]

[edit] References

[edit] See also

• Comparison of business integration software

[edit] External links

• FAQs
• Product page
• WebSphere Message Broker Basics Redbook
• WebSphere Message Broker Roadmap

This computer software article is a stub. You can help Wikipedia by expanding it.