Connect Applications and Services Together with the ... · PDF file1 Connect Applications and...

1

Connect Applications and Services Together with the Enterprise Service Bus

D1 - 05 Connect Applications and Services Together with the ESB.ppt 2

On Demand Insurance Business Problems1. We lose customers because we process new policy applications too slowly.2. Our claims processing is time-consuming and inefficient.3. We need to do a better job of attracting new customers.4. We need our employees to be more productive. 5. We need to grow revenue in existing accounts, and by partnering.6. Our development teams are always behind schedule and over budget.7. We need to gain maximum efficiency out of our IT infrastructure.

On Demand Insurance CEO

2


Service Combining Frameworks

WebSphere Application Integration Connects Services Efficiently

Enterprise Service Bus

PeopleIntegration

Process Integration Information Integration

Partner ServicesApplication Services Data ServicesPeople with Clients

WSDLWSDL WSDL WSDL WSDLWSDL WSDL WSDL


On Demand InsuranceApplication Connectivity

IBMCIO

I would like to get information to our customers more quickly.We have many different channels for our customers to contact us, and we’re not consistent on how we handle their requests.There are many different departments involved.

Let me tell you about an important integration architecture model known as the Enterprise Service Bus.

3


“Maintaining and managing point-to-point links was costing them an average of 29% of their IT budgets.”— CIO Insight

“About 35 percent of an enterprise’s software budget is spent on maintaining the multitude of point-to-point application links already in place.”— Gartner Group

“The three most common inhibitors to achieving a strong ROI on EAI initiatives are:

1. Not having a shared-services model2. Not having application-neutral interfaces3. Not fostering a culture of reuse within ones development teams.

— Meta Group

Existing Application Interfaces are Costly


� Multiple Platforms

� Programming Models

� Programming Languages

� Variety of Standards & Message Formats

WebServices

Publish/SubscribeManaged FTPAsynchronous

Messages

��

��

��

� ��

� ��

��

��

��

��

�� !"��#!$ �

SynchronousRPC

112

23

4567

89

1011

��#%&�'(�)&� �

Connecting Everything Requires Strategic Planning – Middleware Is Required

4


What Does An Enterprise Service Bus Do?An Enterprise Service Bus (ESB) provides mediation services� Connection

� Support applications regardless of platform and location� Provide assured message delivery in a secure and reliable manner� Handle high volumes in a manageable manner

� Message Transformation� Transform messages between different message formats� Make it easy to connect independent endpoint applications

� Message Routing� Route messages based on rules, rather than application logic� Make it easy to quickly adapt to changing business requirements

� Transport Protocol Switching� Transform messages between different message formats, including Web

Services, other XML and non-XML formats


AriesHandheld Terminals/

WOW

CreditCard Bank TML Back

Office Yield WeatherData

Warehouse/DDS

FlightView

FleetPlanning

TAFT ReaderBoards

ODS Reservation Rental Rates Fleet Locations Customer

GDS BusinessPartners

Other

� Each requester has to know details about all of its services � Modifying a service may mean changes to all the requesters that use it� Lacks on demand flexibility

A Typical Situation

5


CreditCard Bank TML Back

Office Yield WeatherData

Warehouse/DDS

FlightView

FleetPlanning

AriesHandheld Terminals/

WOW

TAFT ReaderBoards

ODS Reservation Rental Rates Fleet Locations Customer

GDS BusinessPartners

Other

� Concentrate connectivity logic in one place� Each system can be changed independently

� Easier application maintenance

� Business flexibility

Enterprise Enterprise Service BusService Bus

The Enterprise Service Bus

Routing, Transformation, Transport Switching


People Processes Information

ExistingApplications & DataPartners New

Applications


Enterprise Service Bus – Business Benefits� Connect virtually anything to anything in the enterprise

� Supports broad-based heterogeneous integration� Maximizes ability to reuse applications and services

� Mediates between service requesters and providers� Add and change applications as business demands� Save time and money with common interfaces across the enterprise

6


The IBM Enterprise Service Bus - Products

� WebSphere MQ� Asynchronous messaging� JMS point-to-point

� WebSphere Business Integration Message Broker� High speed transformation and routing� JMS publish/subscribe

� WebSphere MQ Everyplace� Extend messaging to mobile devices

� WebSphere Application Server� JMS messaging� Web Services Gateway


WebSphere MQ� Connects to virtually everything

� 35 platforms

� API for almost every programming language

� Considered to be a defacto standard for messaging� Market share now over 80%, according to consultants

� Usage� Used at more than 10,000 customer sites� Used by more than 350 of IBM's top 500 customers� Used by more than 66% of NA and European banks� 9 out of top 10 Fortune 100 customers� Proven ability to handle millions of messages per day

� www.ibm.com/software/integration/mqfamily/

7


WebSphere MQ Everyplace

� MQ Everyplace is a complementary messaging and queuing product

� Designed for smaller, light-weight and wireless system environments� Palm OS� Pocket PC� Embedded systems� Many others …

� Provides a Toolkit for building MQe messaging environment

� Tiny foot print – approximately 100K, depending on options selected

� Special considerations for wireless environments� Slow bandwidth with lots of error recovery means that short messages are

preferred� Encryption options are critical

� Bridge provided between MQ Queue Manager and MQe environments

� MQe is also included in the WebSphere Everyplace Suite packaging



WebSphereMQ Server

Send Receive

Queue

WebSphere MQ - Server Based Messaging

Application

WebSphereMQ Client

Application

WebSphereMQ Client

� Assured Delivery

� Sender & Receiver need not be running at the same time (asynchronous)

� Message flow control

� Clustering and failover

� Servers can be networked together

Message

8


Java Message Service (JMS)

� Application Programming Interface (API) for building message-based J2EE applications

� Implementation consists of JMS clients and JMS servers� Many clients can connect to each server� Servers can deliver messages to their own clients or other JMS servers

� Two messaging modes� Point-to-point

− one sender, one receiver− queues are used− asynchronous messaging support, similar to WebSphere MQ

� Publish/Subscribe − one sender, many receivers− receivers subscribe to topics− senders publish messages with associated topics


� WebSphere V6 provides embedded JMS 1.1 support� Functions as a JMS server� No extra cost

� Fully integrated with application server management including high availability� Messaging engines will failover along with application servers

� Integrates with WebSphere MQ network� Extends WebSphere MQ network function into WebSphere Application

Server environments

WebSphere Application Server V6 Has Built-in JMS Support

WebSphere MQ Network

WebSphere MQ NetworkWebSphere Application

Server V6

WebSphere JMS looks like an MQ Queue Manager

MQ Queue Managers look like other JMS servers

9


TIBCO Rendezvous - Peer to Peer Messaging

�No assured delivery

�Sender & Receiver must be running at the same time

�Lack of central administration leads to application conflict

�No message security anyone can listen

�No flow control

Messages are broadcast to everyone(even though only one might receive)

Rendezvous Message Bus

Send Receive

Application

RVDProcess

Application

RVDProcess


IBM WebSphere MQ

TIBCORendezvous

"Reliable Messaging" vs.

�Messages are lost� Applications must be

running at the same time

� Network failure results in lost messages

�Assured delivery� Applications do not need

to run at the same time (ever)

� Network failure recovery

DEMO: Server-Based Messaging - Assured Delivery

10


�Both sender and receiver must be running for message delivery

�Different API!�Sender's system must

keep track of all receivers

�Senders and receivers are insulated from each other

�One API�Messages managed by

server, not sender

IBM WebSphere MQ

TIBCORendezvous

“Certified Messaging" vs.

"Certified Messaging" Doesn't Help


Connectivity Comparison

� IBM� 35 platforms, plus mobile devices� Message Queuing Interface and Java Message Service� Support for C, C++, C#, COBOL, Visual Basic, Java

� Microsoft� Microsoft Message Queuing (MSMQ) only connects to Microsoft Windows

� SAP NetWeaver � NetWeaver JMS only connects to another NetWeaver Server� Java applications only – no support for Visual Basic, C++, C#

� BEA� WebLogic only connects to another WebLogic Server� Java applications only – no support for Visual Basic, C++, C#

� TIBCO� 4 messaging products which are not integrated� Rendezvous does not provide assured delivery

Source: IBM Software Group Competitive Project Office, 2005

11


Charles SchwabCharles Schwab’s ESB relies on WebSphere MQ

“If we need to trust that something will be done between two systems, and we don’t want unavailability if one of them is out, we use MQ.

It was proven on day one when 50% of the hardware failed because of heat issues, but the MQ decoupling ensured that the overall application kept on trucking. No customers saw a problem.

Without MQ, large-scale commercial distributed systems would be about 10-100 times more complex. That means fewer companies could deliver commercial-grade trusted systems.”

At Schwab MQ processes every trade made (at least 9 times to keep different systems in step).� 100s of different events� 1000s of messages per second� 100s of millions of messages per

dayWebSphere MQ configuration

� 160 MQ Queue Managers� 30,000 separate MQ applications� All connections to external

suppliers� Platforms include zOS, Linux,

AIX, Solaris and Microsoft Windows

At Schwab MQ processes every trade made (at least 9 times to keep different systems in step).� 100s of different events� 1000s of messages per second� 100s of millions of messages per

dayWebSphere MQ configuration

� 160 MQ Queue Managers� 30,000 separate MQ applications� All connections to external

suppliers� Platforms include zOS, Linux,

AIX, Solaris and Microsoft Windows


WBI Message Broker platform support:�Windows�AIX�Solaris�HP/UX�Linux (Intel and z/Series)�z/OS

WebSphere Business Integration Message Broker

� Provides routing, transformation and transport switching

� Increase business flexibility and reduce development costs by separating integration logic from applications

� Facilitate communication among otherwise incompatible applications

� Extend the reach of your business beyond your intranet

� Easy to use tools

12


� Target for message determined dynamically at run time� By contents or attributes of message� Sending application need not know ultimate receiver

Message Broker Mediation: Routing


ChicagoFactory

London Distributor

Manufactured Items

Purchasing Application

OEM Items10001000

5050


Message Broker Mediation: Transformation

� Contents of message transformed by message broker� Maps sender and receiver data formats� During transmission� Examples of transformations:

− Revised record layout − Changed field formats− Augmentation from other sources (e.g., database)


Binary Format

Web Order Application

Order Entry System

XML Format

13


WebSphere Business Integration – Message Broker

WBI Message Broker Natively Supports Seven Transports – Plus WBI Adapters

Web Services Application

WebSphere Web Services (SOAP/HTTP)

Enterprise Application

WebSphereMQ Client

(MQ Message Protocol)

J2EE Application

WebSphereJMS Client

(MQ Message Protocol)


Multicast Application

WebSphere MQ Multicast

(TCP/IP Multicast)

Remote Sensing Device

WebSphere MQ Telemetry

(SCADA)

Web-scale Pub/Sub

WebSphereMQ Real-time

(Internet Sockets)

MobileApplication

WebSphere MQE Client

(MQ Mobile Message Protocol)

Wide range of Technologies &

applications

58 WBI Adapters(MQ Message

Protocol)


The IBM Enterprise Service Bus – Transport Options

� WebSphere MQ messaging� Assured delivery asynchronous messaging

� Java Message Service (JMS)� J2EE standards-based access to WebSphere MQ messaging

� Mobile Device messaging� Robust and dependable messaging from mobile environment

� Multicast messaging� Network-efficient multicast messaging without the administrative burden

� Remote Sensing Device� Messages from a variety of intelligent devices (e.g., thermostats)

� Web scale pub/sub� Supports thousands of subscribers via Intranet or Internet

� Web Services� Asynchronous messaging and web services converge

� Adapters� IBM’s 58 adapters can connect to WBI Message Broker

14


Message Broker Mediation: Transport Switching

� Transport protocol used by sender is switched to transport protocol used by receiver � During transmission� Switched by message broker� Examples of transformations:

− Web service call switched to asynchronous messaging − Asynchronous message switched to TCP/IP Multicast

AsyncMsg

WebServices

AsyncMsg

WebServices

WebService

AsyncSystem



On Demand InsuranceApplication Connectivity

I would like to get information to our customers more quickly.We have many different channels for our customers to contact us, and we’re not consistent on how we handle their requests.There are many different departments involved.

IBMCIO

The Enterprise Service Bus can solve this problem

15



WBI MBRouting

Transformation

Database

Life Insurance

Application

Send sales leads to Life

Insurance department

Receive sales leads from mailroom

Data entry from postcards

MQ

Mailroom VB Application

JMS

Browsers

RFI Web

Application

Receive sales leads from

Internet

Process requests MQ

Home OwnersJava

Application

Send sales leads to Home

Owners department

DEMO: Request For Information


SOAP

MQE


Send sales leads to Life

Insurance department

Receive sales leads from mailroom

JMS

Browsers

RFI Web

Application

Receive sales leads from

Internet

Send sales leads to Home

Owners department

BusinessPartner Web

Service Client

SalesRepresentativeMobile Device

DEMO: Request For Information - Extensions

Database

Life Insurance

Application

Process requests MQ

Home OwnersJava

Application

Data entry from postcards MQ

Mailroom VB Application

WBI MBRouting

Transformation

16


One More Thing…

� WBI Message Broker is the world’s fastest message broker

� Performance is far superior to Microsoft BizTalk and SAP NetWeaver XI

Source: IBM Software Group Competitive Project Office, 2005


Send Messages

WBI MessageBroker

MicrosoftBizTalkServer

See How Fast They

Arrive

DEMO: Performance of Microsoft BizTalk 2004

� Send messages through WBI MB and MS BizTalk 2004

Make routing decision for each message

17


Are You Productive?

sword_rational tools for programmers.mpg

Connect Applications and Services Together with the ... · PDF file1 Connect Applications and...

Documents

Transcript of Connect Applications and Services Together with the ... · PDF file1 Connect Applications and...