enterprise systems integration
DESCRIPTION
Presentation about integration of the enterprise systems.TRANSCRIPT
© Adastra Group
Enterprise Systems Integration
Long way to SOA
Adastra klub
Vít Kotačka
19. 6. 2012
2
Agenda
Levels of Integration Maturity Architectural solutions Technical solutions Projects & practice
3
Enterprise Integration
Enterprise integration is the task of making disparate applications work together to produce a unified set of functionality.
4
Levels of Integration Maturity
5
Point-to-point integration
Easy & quick deal Easy & quick implementation Usually cheap
cmp Streight Integration easy
Sytem A
request dataSystem B
expose data
6
Point-to-point integration problems
Geometric progression complexity Different formats and protocols Transitive dependencies
cmp Streight Integration difficult
Sytem A
request data from B
request datafrom C
System B
expose data for A
request datafrom x
System C
expose datafor A
request data from x
System xexpose data for C
expose datafor B
7
Integration tier
Central control over data flow Unified message format Set of protocols (company communication standard) Services reuse Central data transformation, orchestration etc.
cmp Middleware
MiddleWareexpose data
expose data
request data
request dataConsumer A
request data
Consumer Brequest data
Producer 1expose data
Producer 2expose data
8
Integration tier problems
Higher costs System complexity increasing Slow (implementation/management) reaction
cmp Middleware
MiddleWareexpose data
expose data
request data
request dataConsumer A
request data
Consumer Brequest data
Producer 1expose data
Producer 2expose data
9
Integration tier communication
sd Integration
Consumer A
MiddleWare Producer 1 Producer 2
request data()
transform request()
request data()
return data()
request data()
return data()
transform response()
return data()
10
Service Oriented Architecture
Standardized contract Service reuse + impact analysis Composite services Service metadata
somf SOA
Data Repository Metadata Repository
Data Abstraction
Services
Process Orchestration
Management & Monitoring
Securi ty Governance
11
SOA Governance
Service portfolio management Service lifecycle management Policies management Service usage monitoring
somf SOA Gov ernance
Standards Services
Data QoS
SLA
Applications
Policies Strategies Rules
Processes Monitoring Audit
Planing Certifi cations Evaluation
12
Architectural solutions
13
Main Integration Styles
File Transfer – each application produce files of shared data for others to consume and consume files that others have produced.
Shared Database – applications store the data they wish to share in a common database.
Remote Procedure Invocation – each application expose some of its procedures so that they can be invoked remotedly, and have applications invoke those to initiate behavior and exchange data.
Messaging – each application connect to a common messaging system, and exchange data and invoke behavior using messages.
14
Two main architectural solutions
Messaging + Broker BPM based engine
- BPEL engine- BPMN engine- Rule engine- Workflow engine
15
Message Broker
cmp Broker
Message Router
«executionEnvironment»Message Broker
«application»Broker Archive
«use»
16
EIP Diagram
17
BPM Engine
deployment BPM Engine
«executionEnvironment»BPM Engine
«application»BPM Archive
«bpel»Process 1
«bpel»Process 2
«rule»Decision 1
«flow»Workflow 1
18
BPMN Diagram
Business Process BPMN
StartEvent1
Activi ty2
EndEvent1
(from Use Case)
Use Case1
Activi ty1
Activi ty3
Activi ty4
FirstL
ineS
econd
Line
19
Canonical Data Model
A common model independent from any specific application. Require each application to produce and consume messages in this common format.
20
Technical solutions
21
Messaging & BPM Solutions
IBM WebSphere MQ IBM WebSphere Message
Broker
Oracle SOA Suite
Apache ActiveMQ Apache Camel
Drools
22
IBM WebSphere Message Broker
23
WMB, components cmp Web Serv ice
«J ava MQ Client»Consumer
«WebService»soapUI
«Broker»J PRASE_BRK
«MQI nput Node»MQ Input
«Compute Node»XmlToSoap
«SOAPRequest Node»SOAP Request
«Compute Node»SoapToXml
«MQOutput Node»MQ Output
«J ava MQ Client»Producer
«Queue Manager»QM_J PRASE
«Local Queue»INPUT
«Local Queue»OUTPUT
«xml»request message
«xml»response message
MQPUT
«tcp»
request
«soap»
response
«soap»
MQGET
«tcp»
«send»
«receive»
24
JBoss jBPM IDE
25
JBoss jBPM BPMN diagram
26
Oracle SOA Suite
27
Projects & practice
28
Micros
Java ws2ws mapping ActiveVOS Drools
cmp Micros
«application»Micros FE
«application»Micros BE
Middleware
«bpel»ActiveVOS
«use»
«use»
«use» «use»
29
JLauncher
Java batch processing- file2file- file2db- db2file- db2db
sd JLauncher
Producent ConsumentJ Launcher
*Check data()
Expose data()
Read data()
Wri te data()
Process data()
30
Online Integration
WebSphere Message Broker Proprietary solution (TIF) Runtime registry (MDR) Weak governance
cmp TIF
WMB
TIF
Consumer
TIF connector
Provider
TIF agent«call» «call»
31
ESB
Oracle SOA Suite
cmp ESB
Oracle SOA Suite
expose demand
«application»Composite
«bpel»Process
«application»FE demand
«core»BEexpose
32