int-4: introducing sonic esb ® jaime meritt director, esb product management rob straight principal...

INT-4: Introducing Sonic ESB®

Jaime MerittDirector, ESB Product Management

Rob StraightPrincipal Product Manager

© 2007 Progress Software Corporation2 INT-4: Introducing Sonic ESB

Your Speaker

Jaime Meritt• Director ESB Product Management

– Responsible for ESB Product Family strategy and planning

• Architect Sonic ESB Rob Straight

• Principal Product Manager, OpenEdge– Responsible for integration strategy and

planning

A little bit about us…


Agenda

ESB Fundamentals The Role of an Enterprise Service Bus How an Enterprise Service Bus Works Next Steps


• Must reuse existing assets

…not designed to collaborate

• Must show rapid, measurable ROI

• Can’t introduce operational risk

…IT Bound By Constraints

• Develop new productsand services

• Speed businesstransactions

• Comply withgovernance

• Integrate acquisitions• Outsource business

functions

BusinessDemands Change…

The Pressure on IT

InformationTechnology


Introducing SOA & SOBA

An approach for building agile and flexible business applications• Loosely coupled services

= flexible business processes

SOA is not A product or application A specific technology A specific standard A specific set of rules

Service-Oriented Architecture > Service-Oriented Business Applications


Mainframe.NETJ2EEOpenEdge Open Source

The Accidental Architecture

High cost of operations Low reuse of assets Resistant to change Difficult to visualize and govern

Isolated silos of fragmented process


Mainframe.NETJ2EEOpenEdge Open Source

Enterprise Service Bus

Infrastructure for SOA Integration• Binds disparate systems into SOA• Flexibly, reliably and efficiently routes data and

events, manages processes• Inserts mediation capabilities (for transformation,

data enrichment, etc.) Promotes high asset reuse, agility, manageability

and governance


The Enterprise Service Bus

How do you:• SOA-enable existing

applications?• Resolve

incompatibilities?• Compose and reuse

service capabilities? Don’t forget:

• Distribution• Scalability• Reliability• Security

J2EE™ APPLICATION

PACKAGED APPLICATION

& LEGACY SYSTEMS

.NET™APPLICATION

OPENEDGE FUTURESERVICES

WEB SERVICESINTERFACE

SOAPHTTP

XML

Web Services only address a subset of the issues


The Enterprise Service Bus

An ESB provides flexible integration of business applications in an SOA

Any numberof processes

Any numberof locations

Any number of services

Across organizational boundaries and to remote sites

With low latency, high reliability and continuous availability

Evolve, scale and extend throughout the enterprise


Agenda



The Role of an Enterprise Service Bus

There is no SOA “big bang” - incremental adoption is the only path for success

The ESB allows for project by project development utilizing “SOA foundational technologies” and best practices

Start with a “business change project” and show immediate value• Changes in marketing strategy• Mergers and acquisitions• Regulatory requirements• Breaking down functional silos• Creating an E-value chain

Incrementally add other business change projects using standards-based integration options

A practical approach to SOA



Transports• HTTP• JMS

Data Model• XML (POX)• SOAP

Transformation• XSLT• XQuery

Interface and Orchestration• WSDL• BPEL

Registry• UDDI

Enterprise• Security• Reliability

Making sense of SOA standards



The less you know the better!! Systems were not originally designed to work

together so services vary widely• Data Model• Semantics• Location• Time• Security• Interface• Version

Web Services gets all of the hype, but it’s not the only approach

The ESB provides infrastructure to resolve these incompatibilities

Loose Coupling – How Loose is Loose?



Standards-Based integration infrastructure for connectivity, transformation, and security

Service Enable heterogeneous endpoints

Mediate service exchanges to resolve incompatibilities

Intelligent Routing and Service Orchestration to compose and reuse services

Provides enterprise grade SOA integration infrastructure

SONIC ESB®

ENTERPRISE SERVICE BUS

J2EE™ APPLICATION

PACKAGED APPLICATION

& LEGACY SYSTEMS

.NET™APPLICATION

OPENEDGEAPPLICATION

WEBSERVICE


Agenda



How an Enterprise Service Bus Works

‘On-ramps’ and ‘off- ramps’ for the ESB• Proprietary and complex

applications• B2B protocols• Packaged applications• Mainframe and legacy• Extensibility APIs to build

additional adapters

OPENEDGE

APPLICATION

LEGACY SYSTEMS MAINFRAMEPACKAGED

APPS

.NET™APPLICATION

B2BPARTNER

J2EE APPLICATION

ENTERPRISE SERVICE BUS

Connect existing applications to the bus



Business logic in OpenEdge 10 / 4GL

Process & integration logic in ESB

OpenEdge tools for configuring adapters

Deploy OpenEdge apps as ESB services

JEE and .Net

Application infrastructure integration

J2EE™ APPLICATION

OpenEdge Application .NET™

APPLICATION

PARTNER SYSTEM

WEBSERVICE



Access data in OpenEdge and foreign data sources

Service interface to database queries

XML to query/result mapping

Load balancing and connection pooling

Data store integration

SONICDATABASE

SERVICE

XML TRANSLATE

XMLMAPPING

SQL CALLOR STORE PROCEDURES

RDBMS

RESULTSET



Mediation and Intelligent routing

Simple data format translation Queuing and

Publish/Subscribe Content based routing to

select service implementation based on business messages

Itineraries• Routing slip pattern provides a

simple sequencing mechanism

• State travels with the message to obviate the need for bi-directional communications

• Compose and reuse itineraries to separate concerns

Service Request Service Response

Fn()Fn()

Service Adapter

Service ImplementationService Implementation

DataBusiness

Logic

BusinessLogic

Service Interface



Process layer provides higher level abstraction for creation coarse grained services

Compose processes out of existing services and processes

Correlate events within and across running processes

Familiar developer constructs: conditionals, loops, delays, scoped state

Manage concurrent (often long-running) service interactions

Compensate for completed activities in the event of failure

SERVICES

SERVICES

Service Orchestration: Enabling reuse with WS-BPEL 2.0


Application Application


The problem: Back-end integration

Portal

Browser

App ServerJD

BC W

S

JDBC

WS

Change requires re-codingChatty protocols over WAN?How do I secure over firewall?Will WS scale up?Hard to coordinate changes across

organizational silos.

WAN

Presentation Layer


Web Svc

Partner System



The problem: Can’t re-use dedicated integration layer

Portal

Browser

App ServerJD

BC W

S

JDBC

WS

WAN

WSJD

BC

WAN

WS

JDBC

Presentation Layer


Browser Integrates each back end system as managed

service Across remote sites and security domains Can run asynchronous back-end queries in parallel Infrastructure extensible to new uses without

disruption, without remote system recoding


The ESB solution

Portal

WebServices

Consumer



ORDER ENTRY

ERPFULFILL -

MENTBILLING


The problem: Accelerate business process cycle

FTP FTP FTP

TIME LOST:

BATCH CYCLE

BATCH CYCLE

BATCH CYCLE

ORDER CASH

Latency of batch processing

Sales Manufacturing Shipping Finance



The problem: Accelerate business process cycle

ORDER ENTRY

ERPFULFILL -

MENTBILLING

FTP FTP FTP

TIME LOST:

BATCH CYCLE

BATCH CYCLE

BATCH CYCLE

Latency of batch processingError remediation80% of data transfer done this way

ORDER CASH

Sales Manufacturing Shipping Finance

Error:Retransmit


2

1

3

REPEAT

START

END

Use BPEL to iterate on 3-step process Each step invokes legacy resources But BPEL is completely binding-agnostic

• It knows only of WSDL

• How do I integrate with the target systems?

BPEL Integration example

ORDER

SHIP

BUILD


WSDL LEGACY


1

2 3

BPEL orchestrates WSDL services into a process ESB binds WSDL to heterogeneous resources

BPEL Integration example


ORDER

SHIP

BUILD

BPEL SERVER

2

1

3

REPEAT

START

END


2

1

3

REPEAT

START

END

That means two shipping systems: one local, one remote

The second shipping system needs special handling• We can’t ship without looking up customer information

that is in the remote fulfillment center

BPEL Integration example with two fulfillment centers

ORDER

LOCAL SHIP

BUILD


WSDL LEGACY

REMOTE SHIP

?


A B C

Extend “SHIP” service using ESB intelligent routing• CBR selects branch• Itinerary directs message flow for additional mediation steps

Intelligent routing obviates WAN hop – no “central brain” Separation of BPEL and ESB concerns maximizes flexibility

BPEL Integration example with two fulfillment centers

BPEL SERVER


1

2 3

BA

C

3 ITINERARY

REMOTE SHIP


3 4

Clustered communication brokers scale to meet changing throughput requirements

Brokers dynamically route messages across clusters, WAN and security domains

Continuous Availability Architecture (CAA) provides communications availability

Add service instances for transparent load-balancing, availability, disaster recovery

2

2


Distribution, Scalability, Availability, and Security

1


Agenda



OpenEdge & Sonic SOA Infrastructure

Build and integrate with OpenEdge and Sonic• Get on the bus with the app server adapter

Focus on business logic not infrastructure Leverage existing & legacy applications Cost effective, incremental integration

Building your SOA infrastructure

IntegrationIntegration


EnterpriseService Bus

Semantic mediation tools for application and service data management with common information model visualization, impact analysis and testing

SOA management platform providing monitoring, active policy enforcement and service delivery optimization

SemanticIntegration

SOAManagement

EventProcessing

MainframeConnectivity

DataAccess

ApplicationPlatform

Message-based, distributed, event-driven architecture with Service-based components

Overcoming IT and Business Challenges Using SOA

The Progress Software Product Line


For More Information, go to…

PSDN• A New Service-Oriented Architecture (SOA) Maturity Model (

http://www.psdn.com/library/entry!default.jspa?categoryID=55&externalID=1937&fromSearchPage=true)

• Sonic Evaluation Kit (http://www.psdn.com/library/entry.jspa?externalID=1681&categoryID=89)

• Service-Oriented Architecture(http://www.psdn.com/library/kbcategory.jspa?categoryID=55)

Progress eLearning Community:• XML Essentials, XSLT Essentials • SOAP for OpenEdge Developers • WSDL for OpenEdge Developers• Consuming Web Services from OpenEdge• OpenEdge Development with Sonic ESB


Relevant Exchange Sessions

INT-3: Realistic Service Oriented Architecture ApproachesMichael Boyd – Monday (11th June) @ 2:00pm (recorded)

SONIC-5: Global Approach to SOA Enabled by Sonic ESBStephen Davies – Tuesday (12th June) @ 8:00am

INT-5: Integrate over the Web with OpenEdge Web ServicesMatt Harrison – Tuesday (12th June) @ 8:00am

SONIC-8: Extend Your ESB with SOA ManagementDavid Millman – Tuesday (12th June) @ 2:00pm

INT-8: Implementing ESB Processes with OpenEdge and SonicDave Cleary – Tuesday (12th June) @ 2:00pm


Summary

SOA is a set of architectural best practices designed to decouple business applications and improve interoperability in a heterogeneous environment

The Sonic ESB combined with OpenEdge gives you a path to integration of business applications in a SOA

The ESB provides an infrastructure that allows an incremental approach to SOA adoption that is designed to scale as your needs increase


Questions?

int-4: introducing sonic esb ® jaime meritt director, esb product management rob straight principal...

Documents

progress software corporation

enterprise service bushow

enterprise service busthere

enterprise service busan

reuse service capabilities

soa sobaan approach

nota product

esb product family strategy