Scribd
Upload
92 views5 pages

ESB - The VETO Pattern: Towards Real-Time Integration: Best Practices, Patterns and Case Studies

The document discusses integration patterns for an enterprise service bus (ESB), including the VETO and VETRO patterns. VETO stands for Validate, Enrich, Transform, and Operate. It describes implementing each stage as separate reusable services. VETRO adds a routing step. Case studies demonstrate how an ESB can integrate existing EDI and portal applications in a non-disruptive way. It also describes how an organization migrated from batch ETL processing to using an ESB for real-time integration incrementally over time by first replacing file transfers and inserting transformation services.

Uploaded by

Raul Aguilar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
92 views5 pages

ESB - The VETO Pattern: Towards Real-Time Integration: Best Practices, Patterns and Case Studies

The document discusses integration patterns for an enterprise service bus (ESB), including the VETO and VETRO patterns. VETO stands for Validate, Enrich, Transform, and Operate. It describes implementing each stage as separate reusable services. VETRO adds a routing step. Case studies demonstrate how an ESB can integrate existing EDI and portal applications in a non-disruptive way. It also describes how an organization migrated from batch ETL processing to using an ESB for real-time integration incrementally over time by first replacing file transfers and inserting transformation services.

Uploaded by

Raul Aguilar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

ESB - The VETO Pattern

Towards Real-time Integration:


Best Practices, Patterns and Case
Studies

Validate

Requires a validating parser and up-to-date schema


e.g. well-formed XML document conforming to a particular schema
or WSDL message
Scripting may be useful

Enrich

Transform

Converting the data structure to or from a canonical format


Considering also conversions, like the typical date/time, units of
measure, currency,

Operate

Add additional data to a message making it more meaningful and


useful to a target service

Invokes the target service or interacts with the target app

Can ensure that consistent, validated data will be routed


throughout the ESB
It provides the overall value and flexibility to the integration
2

ESB - The VETO Pattern

ESB - The VETRO Pattern

The stages of the VETO pattern can be implemented as


separate services that can be configures, reused and replaced

Includes the Routing step into the VETO pattern

Data Forwarding Pattern

Data Forwarding Pattern

Remote apps create change notifications


routing them to the cache

Proactive caching
Use persistent messages on pub/sub with durable
subscriptions
This is configured in the ESB

An ESB can reliably forward change


notifications to the cache
The cache service can be implemented using
the XML storage service

Used for caching and aggregating

More Integration Patterns

Case Study: EDI

Manufacturers are already accustomed


to communicated using EDI
Continue to provide the same EDI
interface with the partners

Non-disruptive approach

10

Case Study: EDI (a)

11

Case Study: EDI (b)

EDI VAN
eliminated
VAN
Places an X12
document onto a
reliable message
queue, routed to
the EDI translator

X12 to SAPs
IDoc
transformation
service

Non-disruptive, non-intrusive

12

Case Study: Portal Server

Non-disruptive, non-intrusive

13

Portal Server

Typical Portal Server approaches do not


really integrate data
The portal provides a unified view of
data that may originate from a variety
of sources, e.g. databases, applications,
services,
The portal server provides the
presentation logic for the users

14

15

The ESB Portal Approach

The ESB Portal Approach

The ESB can act as a reliable buffering


mechanism between the portal app and
the backend systems
Backend apps can use a variety of
connectivity choices to plug into the bus
and immediately begin to participate in
an event-driven SOA
New sources of information can plug
into the bus
The ESB as the integration backbone
16

The ESB Portal Approach

Case Study: Incremental Adoption

Provides end-to-end asynchronous and


reliable communications across a distributed
environment
Additional connectivity options, allowing
flexible deployment of the services
Plug in integration services when and where
you need them

17

Reliability, downtime and latency

The Product Master app and the Product


Index DB are synchronized each night

Facilitating extraction, routing, and transformation


as it modes across the bus

Company relying exclusively on ETL for its


end-to-end supply chain and logistics
It suffers from the typical problems

Between the portal server and the backend apps

Data is gathered into the Product Master app


Data is exported and redistributed to all other
apps using ETL process

Scripts and programs transform and filter the data to


each target app

18

Typical ETL w/FTP integration

19

Why migrating from this?

Benefits

20

Data sharing in real-time


Selective filtering of data
Centralized management
Secured access using ACL
New Business Activity Monitoring (BAM)
apps
Able to participate of new business
opportunities
21

Inserting the ESB

Define the Integration Process


data can be
selectively
dispatched
rely on pub/sub
or queues
ACL enabled

First replace the


FTP file transfer by
an ESB
Reliable transfer

no changes have been required for apps

Create specific ESB process definitions


Selective control of business process
flow across apps and services
From batch-scripted transformations and
filtering to specialized ESB transformation
services

Transformation services could be


inserted to convert from its current
fixed format to XML in canonical form

22

Define the Integration Process

23

Evolve the Integration Process


Multiple apps can
work on the same
message in an
ordered process flow
Partial replacement
of file-drop service
interface

24

Evolve the Integration Process

25

Evolve the Integration Process


Additional ESB
Services are inserted

Product master
interface has been
moved from the
DB export/import
process into an
app using JCA

26

Content-based routing
Data transformation
Auditing

27

Towards RT integration Wrap up

Reuse of services

Apply patterns

ESB supports incremental integration


Opens the door to new interactions
Non-intrusive integration approach

28

29

You might also like