Introduction to Application Integration RoadMap RoadMap

Introduction to 

Application Integration 

RoadMap 

• Introduction 

• Enterprise Application Integration 

• Software Oriented Architecture (SOA) 

• Conclusions 





• Conclusions

“Acme corp. will help their customers 

improve their minds, bodies, and spirits 

through books about the oriental culture .” 

A business opportunity 

• You has been tasked with developing an 

e-commerce portal to service Acme Corp. 

business across the globe 

Your solution 

• Process: AUP, EUP, UP, XP, SCRUM … 

• Model notations 

• Hybrid architectural style 

– Client / Server 

– Three Layers 

• Patterns 

• My portfolio 

• …

What about technologies? 

• It depends on 

– My Culture developing Web Applications 

… 

–Acme Corp Enterprise 

Architecture 


ECM 

CRM 

E-commerce 

Human 

Resources 

IRV 

Accounting 

Store 

Billing 

Orders 

Processing 


IRV 

ECM 

CRM 

E-commerce 

Ficheros, Carga de datos, 

RPC, CORBA, Java RMI, 

DCOM, 

.Net Remoting, ... 

Human 

Resources 

Accounting 


Billing 

Orders 

Processing

Do not forget external systems! 

Visa, 

Mastercard... 

IRV 

ECM 

E-commerce 

CRM 

Ficheros, Carga de datos, 

RPC, CORBA, Java RMI, 

DCOM, 

.Net Remoting, ... 

Human 

Resources 

Logistic 

Accounting 


Billing 

Orders 

Processing 

Integration spaghetti!! 

A costly task 

IBM Global Services Report






Decision criteria 

• Application coupling 

• Other criteria: 

– Intrusiveness 

– Technology selection 

– Data format 

– Data timeliness 

– Data or functionality 

– Remote Communication 

– … 

Loose Coupling 

“to reduce the assumptions two parties 

(components, applications, services, 

programs, users) make about each other 

when they exchange information”

• File Transfer 

• Shared Database 

Integration styles 

• Remote Procedure Call 

• Messaging 




– File transfer 

– Shared Database 

– Remote Procedure Call 

– Messaging 



File Transfer 

• One application writes a file that another 

later reads 

e-commerce 

Share 

d data 

Order Processing 

System

• A low cost solution: 

Characteristics 

– It is simple 

– Files are a universal storage mechanism 

– Integrators need no knowledge of the 

internals of applications to integrate 

• Applications need to agree on: 

– Filename and location 

– Format of the file (XML) 

– Timing of when it will be written and read, and 

who will delete the file (synchronisation) 

Side Effects 

• Allows to keep the applications well 

decoupled but at the cost of timeliness 

(Staleness of the data) 

• Enable applications to share their data but 

not their functionality 

• May not enforce data format sufficiently 

(Semantic dissonance) 







– Messaging 


• Conclusions

Shared Database 

• Integrate applications by having them 

store their data in a single Shared 

Database, and define the schema of the 

database to handle all the needs of the 

different applications 

Shared 

data 


• SQL-based relational databases 

• All application development platforms can 

work with SQL 

• Transaction management systems 

• Applications are always consistent all of 

the time 

Side Effects 

• Applications coupled to the database 

• Semantic dissonance 

• Performance bottleneck 

• Can cause deadlocks 

• The unified schema can result in a schema that 

programmers find difficult to work with 

• Most packaged applications won't work with a 

schema other than their own 

• Software vendors usually reserve the right to 

change the schema with every new release of 

the software







– Messaging 



Remote Procedure Call 

• Have each application expose some of its 

procedures so that they can be called 

remotely, and have applications invoke 

those to initiate behavior and exchange 

data 

Call 

e-commerce 

Result 

Order Processing 

System 

RPC Execution Model 

• Standar model: synchronous method-call 

semantics (request/reply) 

• Other models: Doors, Asynchronous RPC, 

Callback RPC, Batch RPC, Broadcast 

RPC

Some RPC technologies 

• Basic RPC: Sun RPC, DCE RPC, Xerox 

Courier 

• Extended RPC: CORBA, .NET Remoting, 

Java RMI, XML-RPC, COM, … 


• RPC applies the principle of encapsulation 

to integrating applications which allows 

each application to maintain the integrity of 

the data it owns (reduces coupling) 

• It deals with semantic dissonance by 

allowing applications to provide multiple 

interfaces to the same data 

Side Effects 

• Applications are still fairly tightly coupled 

because RPC is for building distributed 

applications and not for integrating 

applications







– Messaging 



The book 

Enterprise Integration Patterns: Designing, 

Building, and Deploying Messaging 

Solutions By Gregor Hohpe, Bobby Woolf 

Messaging 

• Each application connect to a common 

messaging system, and exchange data 

and invoke behavior using messages

Messaging 

It sounds me as the 

File Transfer style 

Messaging core concepts (1) 

• Messages 

– An atomic packet of data that can be 

transmitted on a channel 

• Channels 

– A virtual pipe that connects a sender to a 

receiver 

• EndPoints 

– A layer of code (wrapper) that knows both 

how the application works and how the 

messaging system works, enabling the 

application to send and receive messages 

Messaging core concepts (2) 

• Routing 

– If the sender does not know where to address 

the data, it can send the data to a Message 

Router, which will direct the data to the 

proper receiver 

• Transformation 

– If the sender and receiver do not agree on the 

data format, the sender can direct the data to 

a Message Translator that will convert the 

data to the receiver's format and then forward 

the data to the receiver

Patterns (1) 

• Messaging channels Patterns 

– Point-to-Point Channel, Publish-Subscribe Channel, 

Datatype Channel, Invalid Message Channel, Dead Letter 

Channel, Guaranteed Delivery, Channel Adapter, Messaging 

Bridge, Message Bus 

• Message Construction Patterns 

– Command Message, Document Message, Event Message, 

Request-Reply, Return Address, Correlation Identifier, Message 

Sequence, Message Expiration, Format Indicator 

• Message Routing Patterns 

– Content-Based Router, Message Filter, Dynamic Router, 

Recipient List, Splitter, Aggregator, Resequencer, Composed 

Message Processor, Scatter-Gather, Routing Slip, Process 

Manager, Message Broker 

Patterns (2) 

• Message Transformation Patterns 

– Envelope Wrapper, Content Enricher, Content Filter, Claim 

Check, Normalizer, Canonical Data Model 

• Messaging Endpoints Patterns 

– Messaging Gateway, Messaging Mapper, Transactional Client, 

Polling Consumer, Event-Driven Consumer, Competing 

Consumers, Message Dispatcher, Selective Consumer, Durable 

Subscriber, Idempotent Receiver, Service Activator 

• System Management Patterns 

– Control Bus, Detour, Wire Tap, Message History, Message 

Store, Smart Proxy, Test Message, Channel Purger 

Messaging Channels Patterns 

Point-to-Point Channel 

• How can the caller be sure that exactly 

one receiver will receive the document or 

perform the call? 

• Send the message on a Point-to-Point 

Channel, which ensures that only one 

receiver will receive a particular message.


Publish-Subscribe Channel 

• How can the sender broadcast an event to 

all interested receivers? 

• Send the event on a Publish-Subscribe 

Channel, which delivers a copy of a 

particular event to each receiver 


Channel Adapter 

• How can you connect an application to the 

messaging system so that it can send and 

receive messages? 

• Use a Channel Adapter that can access the 

application's API or data to publish messages on 

a channel based on this data and that likewise 

can receive messages and invoke functionality 

inside the application 


Message Bus 

• What architecture enables separate applications 

to work together but in a decoupled fashion such 

that applications can be easily added or 

removed without affecting the others? 

• Structure the connecting middleware between 

these applications as a Message Bus that 

enables them to work together using messaging

Message Construction Patterns 

Command/Document/Event Message 

• How can messaging be used to invoke a 

procedure transfer data/transmit events between 

applications? 

• Use a Command Message/Document/Event 

Message 

Message Routing Patterns 

Message Broker 

• How can you decouple the destination of a message 

from the sender and maintain central control over the 

flow of messages? 

• Use a central Message Broker that can receive 

messages from multiple destinations, determine the 

correct destination, and route the message to the correct 

channel. Implement the internals of the Message Broker 

using other message routers 

Message Transformation 

Patterns 

Canonical Data Model 

• How can you minimize dependencies when 

integrating applications that use different data 

formats? 

• Design a Canonical Data Model that is 

independent from any specific application. 

Require each application to produce and 

consume messages in this common format

Messaging Endpoints Patterns 

Service Activator 

• How can an application design a service to be 

invoked both via various messaging 

technologies and via non-messaging 

techniques? 

• Design a Service Activator that connects the 

messages on the channel to the service being 

accessed 


• Messaging makes applications loosely 

coupled by communicating 

asynchronously 

• The communication is reliable because the 

two applications do not have to be running 

at the same time 

• The messaging system is the responsible 

for transferring data from one application 

to another, so the applications can focus 

on what data they need to share as 

opposed to how to share it 

Some Messaging technologies 

• J2EE JMS Reference Implementation 

• IBM WebSphere MQ (Implementation of 

JMS) 

• Microsoft MSMQ 

Note: Most Solutions on Enterprise 

Application Integration are based on 

messaging technologies






What is SOA? 

• What if you could change the elements of 

your EA in relation to changes in your 

business without enormous expenditures 

of time and money? 

Just play Lego EA!! 

Service 

But, What is SOA?





– Reference Architecture 

– Radiography of a SOA Compliant Enterprise 


SOA and Services 

“A Service-Oriented Architecture is a 

software architecture that is based on the 

key concepts of an application frontend, 

service, service repository, and service 

bus” 

“A service consists of a contract, one or 

more interfaces, and an implementation” 

Service structure 

End-points 

End-Point 

Dirección 

Servicio 

Implementación 

Ligadura 

Contrato

Kinds of services 

Complexity 

State 

Frequency of 

Change 

Reusability 

Mandatory 

Fronten 

d 

Basic 

Intermedi 

ary 

Process 

Public 

Deployment layers 

Web Server 

Application Server 

Enterprise layer 

Process layer 

Intermediary layer 

Basic layer 

Operating System 

Access to services 

Enterprise Service Bus

ESB is a meta-bus 

RPC 

Messaging 

FTP, … 





– Reference Architecture 

– Radiography of a SOA Compliant 

Enterprise 


SOA Compliant Enterprise 

Enterprise A 

Presentación Proceso Lógica Datos 

Enterprise B 

Presentación 

Proceso 

passport.com






Conclussions 

• EAI is a costly, difficulty task 

• RPC and Messaging systems are simply 

instances of enabling technology that can 

make EAI happen 

• Secondary Effects of SOA provides EAI: 

– ESB integrates EAI enabling technologies 

(meta-bus) 

– Service concept 

Thank you! 

e-mail: jose.arjona @diesia.uhu.es 

web: http://www.uhu.es/jose.arjona

Introduction to Application Integration RoadMap RoadMap

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?