Websphere Message Broker

IBM WebSphere Message Broker enables you to connect a wide range of applications using different interaction patterns, protocols, and message formats.

Supported interaction patterns include:

•One-way messaging
•Request/response
•Aggregation
•Publish/subscribe (pub/sub)

Message Broker supports the following protocols:

•WebSphere MQ
•HTTP
•Java™ Messaging Service(JMS)
•Real-time and multicast
•File
•User-defined

Message Broker enables you to model and transform a comprehensive set of message formats:

•Record-based (COBOL, C)
•Industry standard string-based (SWIFT, TLOG, EDIFACT)
•XML, including all schema artifacts
•User-defined
Messages that pass through Message Broker are potentially routed and transformed between different formats on the way to their destination. Message Broker provides a range of technologies for transforming messages, which can be used in accordance with the skill set of the integration developer:

•ESQL for users with relational database skills who prefer declarative rather than algorithmic forms to specify message transformation
•Java for programmers skilled in Java
•Graphical mapping for straightforward transformations that do not require programming
•XSLT for XML-based transformations based on an open standard

WebSphere Message Broker technical overview

WebSphere Message Broker enables information packaged as messages to flow between different business applications, ranging from large traditional systems through to unmanned devices such as sensors on pipelines.




Start Quick Tour Click on hyperlink

Our interactions with WebSphere Message Broker can be considered in two broad categories:

•

Application development, test, and deployment. You can use one or more of the supplied options to program your applications:

◦Patterns provide reusable solutions that encapsulates a tested approach to solving a common architecture, design, or deployment task in a particular context. You can use them unchanged or modify them to suit your own requirements.
◦Message flows describe your application connectivity logic, which defines the exact path that your data takes in the broker, and therefore the processing that is applied to it by the message nodes in that flow.
◦Message nodes encapsulate required integration logic, which operates on your data when it is processed through your broker.
◦Message trees describe data in an efficient, format independent way. You can examine and modify the contents of message trees in many of the nodes that are provided, and you can supply additional nodes to your own design.
◦You can implement transformations by using graphical mapping, Java™, PHP, ESQL, and XSL, and can make your choice based on the skills of your workforce without having to provide retraining.

•Operational management and performance.

◦An extensive range of administration and systems management options are available for developed solutions.
◦A wide range of operating system and hardware platforms are supported.
◦A scalable, highly performing architecture, based on requirements from traditional transaction processing environments.
◦Tightly integrated with software products, from IBM and other vendors, that provide related management and connectivity services.
WebSphere Message Broker is available in several modes, so that you can purchase a solution that meets your requirements.

Message Broker Explorer