introduction to message broker

IBM Software Group

© 2007 IBM Corporation

An Introduction to WebSphere Message Broker

IBM Software Group | WebSphere software

2

ESB Market Dynamics What is an ESB? What is Message Broker? Message Broker Constructs Product Architecture What’s new in 6.1 Roadmap

Agenda


3

Why?

Reduce Complexity

Manage Exponential Change

Ensure Compliance

Reduce Cost

Improve Control

Customers want to improve this….

… to run their business like this.

The Connectivity Challenge


4

IT Spending Dilemma

Maintenance & operation of existing applications

Time

50%

New projects76%

100%

Maintenance & operation of existing applications Time

50%

New projects76%

100%

Customers want to allocate more money for new projects


5

SOA simplifies connectivity interfaces…

…but you still need to know (1) what services you can connect to, (2) where they are, (3) how to connect to them, (4) how to log into them, (5) how to mediate the differences in data between them.

SOA turns this… …into this.Application Application Application Application

ApplicationApplicationApplicationApplication

Service Service Service Service

Service ServiceService Service

Interface Interface Interface

Interface Interface Interface Interface

= interface

Enables re-use of both the business applications and their interfaces.

Decouples the interfaces from the business applications.

Reduces the number and technical complexity of interfaces.

Introduces rich business abstractions to describe the application interface.

SOA:


6


Agenda


7

What is an Enterprise Service Bus?An Enterprise Service Bus (ESB) is a flexible connectivity

infrastructure for integrating applications and services.

Shape = Transport protocolColor = Data format

An ESB performs the following between requestor and service

CONVERTS between different transport protocols

MATCHES & ROUTES communications between services

TRANSFORMS between different data formats

IDENTIFIES & DISTRIBUTES business events


8

An ESB gives SOA its full value

The ESB Virtualizes access to services.

An ESB turns this… …into this.



Enterprise Service Bus



Interface Interface Interface

Interface Interface Interface Interface

Logs and manages the interaction and correlates events.

Communicates using the right protocol.

Customizes communications so that the message to the receiver makes sense.

Connects and signs you into the appropriate service without requiring a hardcoded connection.

The ESB:

Enterprise Service Bus


9


Agenda


10

ESB offerings from IBM WebSphere

WebSphere ESBBuilt on WebSphere

Application Server for an integrated SOA platform

WebSphereMessage Broker

Built for universal connectivity and transformation in heterogeneous

IT environments

WebSphere DataPowerIntegration AppliancePurpose-built hardware ESB for simplified deployment and

hardened security


11

What is WebSphere Message Broker?

Built for universal connectivity and transformation in heterogeneous IT environments

Range of EAI patterns

Multiple platforms

High volume processing

Extensive transformations of data formats

Standard protocols

Built on WebSphere MQ


12


Agenda


13

How Do we Connect Applications?

ProtocolsApplications need to talk with each other over a communications protocol.

e.g. MQ, TCP/IP, HTTP, File system, FTP, SMTP etc.

Message Formats

Mediation Patterns

Applications need to exchange data, with specific formatse.g. Binary (C/COBOL), XML, Industry (SWIFT, EDI, HL7), User-defined

Mediation patterns allow applications to interoperate. e.g. Route, Transform, Enrich, Filter, Monitor, Distribute,


14

WebSphere Message Broker – Protocols and Applications

WebSphere MQ Multicast(Reliable Multicast Messaging (RMM))

(Very low latency for LANs)

WebSphere MQ Real-time(Very low latency over WANs, and

the Internet)

WebSphere MQ Telemetry(RFID, sensors & actuators)

WebSphere MQ Everyplace(Mobile device applications)

WebSphere MQ (+ PM4Data)(Enterprise applications (+ managed file transfer))

Any 3rd-party JMS(TIBCO EMS, Sonic MQ, BEA JMS, webMethods, See Beyond, Vitria)

HTTP and HTTP(S)

TCP/IP Sockets

FTP and File

TIBCO Rendezvous(plug-in component)

SMTP

IBM Protocols Industry and Vendor Protocols

Enterprise Applications

SAPOracle Siebel

JDEdwards

Peoplesoft

CICS Custom


15

WebSphere Message Broker Constructs – Flows and Nodes

.Message Flows

Provides the processing sequence required to connect applications together

NodesPerforms a different (input, output

or processing) action


16

WebSphere Message Broker Constructs - Mediation Patterns

[Customer, Order, Quantity, Price, Date]

Mr. Smith, Graphics Card, 32, 100, 11/07/08

<order> <name> <first>John</first> <last>Smith</last> </name> <item>Graphics Card</item> <quantity>32</quantity> <price>200</price> <date>07/11/08</date></order>

[Customer, Order, Quantity, Price, Date]

An Application Integration Scenario.

• Application A sends some data to application B with agreed format (UK currency)

• Application C is introduced. It needs the same data, but needs data in different format (US currency and XML)

• So, we now have an integration choice to make. Either application C must be enhanced to support the data format between A and B, or application A must be enhanced to support application C's data format.


17

What are Message Flows?

Message flows are transactional– Provides vital processing and data manipulation– Completes all or none of its processing successfully.

Message flows are multithreaded– Message passing through a series of nodes will execute on a single

thread. To allow – message flows can be defined with many additional threads assigned

to them to increased message throughput.– Peak workloads use additional threads, which are pooled during

inactivity. Message flow nesting and chaining allow construction of

enhanced capabilities.– Sophisticated flows can be rapidly constructed by linking individual

flows together as well as nesting flows within each other.


18

Output targetTransform

Input source Output target

Output target (Failure)

Message Flow Example

A message flow contains the set of operations required to take a message from an originating

application and deliver copies of it, some possibly transformed, to any number of connected applications

for processing.


19

Message Flow Scenario

Routing decision is made based on a field described in the incoming

message

Message is transformed that is recognizable by the web service which is invoked by the subsequent ‘Call WS’

node.

Message is routed to the ‘Generate batch file’ node, which formats the message for subsequent output to a file in the ‘Write

file’ node.


20

Nodes

The building blocks of message flows

Each node type performs a different (input, output or processing) action

Many different node types– Grouped into logical

categories in the message flow editor


21

Node Types

Input

Output

Processing

Protocol-specific

Transformation

Logical construct

HTTP Input

JMS Output

Database Insert

MQ Get

XML Transform

Try Catch

Examples:


22

Message Node Components

Actioninput

terminal

input connecto

r

output connector

snode

input message

treeoutput

message trees

output terminal

s

• Nodes represent functional routines encapsulating integration logic• Terminals represent the various outcomes possible from node processing• Connectors join the various nodes through their terminals


23

Message Broker Parsers

…draCscihparG,htimSderF

Input Message Bit-streamInput Message Bit-stream

…n/<htimS.rM>eman<>redro<

Output Message Bit-stream

Output Message Bit-stream

Parser converts bit-stream to logical structure

Model

Parser converts logical structure to bit-stream

Model


24

A Typical Parser Example

Harry was the “parser” – he took the physical representation of the London Underground and converted into a logical structure. This logical structure is very much easier to work with.

Into this

Message Broker uses logical structures to describe physical data for similar reasons: it makes them

much easier to work with, particularly when addressing or converting between data elements.


25

Message Modeling in Message Broker

<order> <name> <first>John</first> <last>Smith</last> </name> <item>Graphics Card</item> <quantity>32</quantity> <price>200</price> <date>07/11/08</date></order>

John,Smith,Graphics Card,32,200,07/11/08

John Smith............Graphics Card.........3220020071108.........

Order

Name Item Qty Price Date

First LastString String

String Integer Integer Date

Physical Logical

XML

Custom

CSV

Same logical tree regardless of formats making it easy to add new formats


26

Different options for creating Message Models

Message Set

C Header

XMLSchema

COBOLCopybook

WSDL

DTD

File Import

EnterpriseInformation

System(SAP, Siebel, PeopleSoft)

Pre-built

SOAP, MIME, CSV, IDOC,

SWIFT, EDIFACT, X12,

FIX, HL7,etc

Defineyour ownusing the

Eclipse-based Tooling

Parsers

Message Broker

WebSphereTransformation

Extender

Type tree


27

Message Transformation The conversion of one message format into another

Graphical, easy to use

Drag and Drop fields, apply functions

Convert XML to anything

Uses standard XSL Style sheets

Describe powerful transformations quickly

Uses SQL-based language (ESQL)

Uses Java programming language

Ability to use XPath

Run a WebSphere Transformation Extender map


28

Examples of Message Addressing

public class jcn extends MbJavaComputeNode { public void evaluate(MbMessageAssembly assembly) throws MbException { ... String lastName = (String)assembly.getMessage().evaluateXPath(“/Body/Order/Name/Last”); ... }}

IF Body.Order.Date < ‘2008/01/01’ THEN INSERT INTO Database.OldOrders (LastName,Item,Quantity) VALUES (Body.Order.Name.Last, Body.Order.Item, Body.Order.Quantity);ENDIF;


29


Agenda


30

Product Architecture

Configuration Manager

Broker

Broker

Broker

Message Broker Toolkit

Standalone runtime environment

Execution groups for isolation and scalability

Many different platforms Also provides runtime

security model and augmented pub/sub

Broker Development and Administration Environment

Based on Rational Application Developer

Windows and Linux

Manages a domain of brokers

Drives deployment Controls access to domain


31

Typical User Roles and Environments

Application Developer– Develops message flows,

message models etc.– Unit Tests on local machine– Creates Broker Archive

(BAR) files containing required artefacts

Administrator– Customizes BAR for target

environment (message flow properties including queues, database names etc.)

– Deploys BAR to target broker

– Broker management and operational control

– Monitoring…

Development Test QA Production


32

Monitoring

Broker provides extensive monitoring and tracking capability

– Accounting and Statistics– Message Tracking Exits

Many monitoring and message tracking tools available from IBM and Business Partners, for example

– IS02 SupportPac– Omegamon XE – Q Nami!– ITCAM for SOA

Broker event publishing– e.g. Ability to publish

business events

Web Services Navigator

Response Time

Message Count

Message Size


33

Usage Patterns with Message BrokerService Enablement

Service Virtualization

OROR

OR

Message Enablement

Message Brokering

File Processing

Event Processing


34


Agenda


35

Version 6.1 Feature Overview Ease of Use and Productivity

– Reducing the time to get started with Message Broker– Simplifying development tasks including debug; reducing the time to create working solutions

Enhanced SOA support– Supporting Web Services natively with WS-Security and WS-Addressing– DataPower SOA appliance for WS-Security– Integration and enhancement of WSRR support

Extended Connectivity– Built-in nodes for EIS access: SAP, Siebel and PeopleSoft, Oracle eCommerce and JD Edwards– Native support for very large file processing, including FTP– New SMTP and TCP nodes– WTX integration including launcher capability

Administration, Security & Systems Management– Enterprise-wide identity, authentication and authorization with Tivoli and LDAP– MB Explorer Eclipse administration– Numerous manageability improvements

Platform Support and Performance– 64 bit Linux; JDBC XA support; Java 5– Ultra High Performance XML parser including schema validation– Compacted memory footprint; Real-time graphical performance analysis– Significant performance improvement on ALL platforms– New Started Edition, Remote Adapter Deployment and Trial Version


36


Agenda


37

WebSphere Message Broker Product Roadmap IBM's plans, directions, and intent are subject to change or withdrawal

V6Q3 2005

V6.12H 2007

Major release

Minor release

V7.02H 2009

V6.0.0.1Q1 2006

V6.0.0.2Q3 2006

V6.0.2Q4 2006

V6.1.0.21H 2008

Message tracking

Web Services IPV6 Performance gains New Development Toolkit

Extensions, demos and samples CDImproved Administration with MQNumerous operational improvements

Ease of Use for Development experienceExtended Web Services supportService Registry and Repository enhancementsAdditional native connectivity (SAP, File, SMTP…)Security and Administration enhancementsPerformance enhancements & 64 bit zLinux

Patterns and Impact AnalysisProduct and pre-requisites simplificationIntegrated MQ Pub-sub and Admin Web Services (Phase 3)SCA InteroperabilityMapping and Message ModellingNew nodes

introduction to message broker

Documents

flexible business

traditional business

sample business process

linear business processes

new way

organized way

kind of mess

process suppliers