ESBs – Connecting the World

Steven Dyer NSA IAM, NSA IEM, CISSP, CCSP, CCDP

Chief Technology Officer

Central Service Association

Group Exercise…

Design Time Run Time Change Time

Developer Business User Architect Service Consumer

IT Operations Admin

Structure: Customized Interfaces

I want I want I want I want I want I want I want I want Ahhhhhhhhhhhhhhhh

ESB Agenda

• What is it and why should I care

• Group Exercise

• How we are doing things now

• Deep dive into the “future”

• ESB Design

Service Access Enterprise Service Bus – Integration Platform

An ESB is a middleware solution that enables

interoperability among heterogeneous environments

using a service-oriented model … - Burton

… responsible for providing a

distributed communications

infrastructure … - Forrester

ESB is a communication and

mediation layer that connects

service consumers and providers … - Gartner

8

What is an Enterprise Service Bus (ESB)?

An ESB implements an SOA through middleware that

offers virtualization and management of service

interactions between communication participants.

Thus, this flexible connectivity layer could help connect

and integrate an organization's IT infrastructure across

many differing systems and locations reliably and securely

while reducing the number, size and complexity of

application interfaces.

9

Key Characteristics of an ESB

• Streamlines development

• Supports multiple binding strategies

• Performs data transformation

• Intelligent routing

• Real time monitoring

• Exception handling

• Service Security

Change is Inevitable

SOA Masterclass - Core Technologies | 11 February 2009 | Page 11

Less risky

Less costly

75% intend

to modernize

Rip and Replace Application Modernization

Replace with package High cost

High risk

Rewrite Lack of understanding

Loss of key personnel

The options

12

Legacy Architectural Choke Point

• Monolithic

• Extremely complex

• Very tightly coupled

• Difficult to find clean integration points

• Lack of standards makes it difficult to integrate

• Rigid architecture makes even small changes

complex and costly

13

IT is like an Ecosystem • COBOL

• C++

• Java

• J2EE

• Networks

• TCP/IP

• Web Service

• Mid-Tier Servers

• .NET

• Messaging

• HTML

• Operating Systems

• CICS

• Routers

• Databases

• Mainframes

14

Legacy Integration

15

ESB Integration

SOA Architecture

ESB Edition Building the bridge to ESB

Yesterday ESB

Green screens

Isolated applications

Difficult to change

Mysterious “noodle code”

Rich interfaces

Service orchestration

Designed to change

Governable and Manageable

Possibilities

Legacy Adapter

Consumer

V2

Consumer

V1

Provider

V1

Provider

V2

ESB ESB ESB

The ESB must be able to manage multiple concurrent endpoint versions

Incomplete Data

External

Customers,

Providers…

SOA Increases Project Dependencies

Legacy

Accounting

Production Budgeting CRM

Sales Datamart

Mkt Datamart

Analyze

data

Cleanse

data

Integrate via

Web Services

Extract,

Transform

and Load data

DWH

Manage a single

version of the truth

MDM

Hub

Migrate

legacy

applications

New

Accounting

Exchange data

with partners

ESB

Orchestrate

Unavailable Stale Data

Confidential Data Future Release

External Control

Access Fees

Sensitive Data

Partial

Function

Visibility with Insight

Step 1: Build and Design your Flow

Visibility with Insight

Step 2: Connect it Up and Let the Application Run

ESB Demo

Venders do not always agree on how something

should be done!!!!!

Steven Dyer Chief Technology Officer

Central Service Association Cell: 662-491-2661 sdyer@csa1.com