An Introduction to WebSphere Message Broker

Presentation Transcript

Agenda

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

The Connectivity Challenge

… to run their business like this.

Customers want to improve this….

Why?

Reduce Complexity

Manage Exponential Change

Ensure Compliance

Reduce Cost

Improve Control

100%

50%

76%

New projects

Maintenance & operation of existing

applications

IT Spending Dilemma

Customers want to allocate more money for new projects

100%

New projects

50%

Maintenance & operation of existing

applications

Time

SOA turns this…

…into this.

Application

Service

Interface

Application

Service

interface

=

SOA:

Introduces rich business abstractions to describe the application interface.

Decouples the interfaces from the business applications.

Reduces the number and technical complexity of interfaces.

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

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.

Agenda

ESB Market Dynamics
What is an ESB?
What’s new in 6.1
Roadmap

Shape = Transport protocol

Color = Data format

What is an Enterprise Service Bus?

An Enterprise Service Bus (ESB) is a flexible connectivity infrastructure for integrating applications and services.

An ESB performs the following between requestor and service

MATCHES & ROUTEScommunications between services

CONVERTSbetween different transport protocols

TRANSFORMSbetween different data formats

IDENTIFIES & DISTRIBUTESbusiness events

Service

Interface

Service

The ESB:

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

Communicates using the right protocol.

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

Logs and manages the interaction and correlates events.

An ESB gives SOA its full value

An ESB turns this…

…into this.

Interface

Enterprise Service Bus

Service

The ESB  Virtualizes access to services.

Agenda

ESB Market Dynamics
What is an ESB?
What’s new in 6.1
Roadmap

ESB offerings from IBM WebSphere

WebSphereMessage Broker

Built for universal connectivity and transformation in heterogeneous IT environments

WebSphere ESBBuilt on WebSphere Application Server for an integrated SOA platform

WebSphere DataPowerIntegration Appliance

Purpose-built hardware ESB for simplified deployment and hardened security

What is WebSphere Message Broker?

Built for universal connectivity and transformation in heterogeneous IT environments

Built on WebSphere MQ

Multiple platforms

Range of EAI patterns

Standard protocols

Extensive transformations of data formats

High volume processing

Agenda

ESB Market Dynamics
What is an ESB?
What’s new in 6.1
Roadmap

How Do we Connect Applications?

Protocols

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

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

Message Formats

Applications need to exchange data, with specific formats

e.g. Binary (C/COBOL), XML, Industry (SWIFT, EDI, HL7), User-defined

Mediation Patterns

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

WebSphere Message Broker – Protocols and Applications

Industry and Vendor Protocols

IBM Protocols

Any 3rd-party JMS

(TIBCO EMS, Sonic MQ, BEA JMS, webMethods, See Beyond, Vitria)

WebSphere MQ (+ PM4Data)

(Enterprise applications (+ managed file transfer))

WebSphere MQ Everyplace

(Mobile device applications)

TIBCO Rendezvous

(plug-in component)

WebSphere MQ Telemetry

(RFID, sensors & actuators)

HTTP and HTTP(S)

FTP and File

WebSphere MQ Real-time

(Very low latency over WANs, and the Internet)

TCP/IP Sockets

WebSphere MQ Multicast

(Reliable Multicast Messaging (RMM))

(Very low latency for LANs)

SMTP

CICS

Custom

JDEdwards

SAP

Siebel

Oracle

Peoplesoft

Enterprise Applications

WebSphere Message Broker Constructs – Flows and Nodes

.

Message Flows
Provides the processing sequence required
to connect applications together

Nodes

Performs a different (input, output or processing) action

websphere message broker constructs mediation patterns

<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]

WebSphere Message Broker Constructs - Mediation Patterns

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

[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.

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.

Output target (Failure)

Message Flow Example

Input source

Output target

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.

Transform

Output target

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

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.

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

Node Types

Input
Output
Processing

Protocol-specific
Transformation
Logical construct

Examples:

HTTP Input

JMS Output

Database Insert

MQ Get

XML Transform

Try Catch

Message Node Components

output connectors

node

input connector

Action

input terminal

input message tree

output terminals

output message trees

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

Model

Input Message Bit-stream

Parser converts logical structure to bit-stream

F

r

e

d

S

m

i

t

h

,

G

r

a

p

h

i

c

s

C

a

r

d

…

Parser converts bit-stream to logical structure

<

o

r

d

e

r

>

<

n

a

m

e

>

M

r

.

S

m

i

t

h

<

/

n

…

Model

Output Message Bit-stream

Message Broker Parsers

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.

Order

Name

Item

Qty

Price

Date

Integer

String

Date

Integer

First

Last

String

Message Modeling in Message Broker

Physical

Logical

<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>

XML

CSV

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

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

Custom

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

different options for creating message models

C Header

XML

Schema

DTD

COBOL

Copybook

WSDL

WebSphere

Transformation

Extender

Pre-built

Enterprise

Information

System

SOAP, MIME, CSV, IDOC, SWIFT, EDIFACT, X12, FIX, HL7,

etc

Define

your own

using the Eclipse-based Tooling

(SAP, Siebel, PeopleSoft)

File Import

Type tree

Different options for creating Message Models

Message Set

Parsers

Message Broker

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

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;

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”); ...

}}

Agenda

ESB Market Dynamics
What is an ESB?
What’s new in 6.1
Roadmap

Standalone runtime environment

Execution groups for isolation and scalability

Many different platforms

Also provides runtime security model and augmented pub/sub

Broker

Configuration Manager

Broker

Message Broker Toolkit

Broker

Broker Development and Administration Environment
Based on Rational Application Developer
Windows and Linux

Manages a domain of brokers
Drives deployment
Controls access to domain

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…

Typical User Roles and Environments

Development

Test

QA

Production

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

Service Enablement

Message Enablement

File Processing

Service Virtualization

Message Brokering

Event Processing

OR

Usage Patterns with Message Broker

Agenda

ESB Market Dynamics
What is an ESB?
What’s new in 6.1
Roadmap

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