Soa pattern con8669_pdf_8669_0001

CON8669
Using the Right Tools,
Techniques, and
Technologies for Integration
Projects

Tim E. Hall
Sr. Director, Product Management
Moscone South – 308 October 1, 2012
1 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 13

Topics

 Fusion Middleware and Integration Landscape
 BPEL vs. BPMN
 Enterprise Gateway, Service Bus & Mediator
 Process Centric vs. Data Centric
 Direct vs. Indirect (aka Canonical)


Oracle Fusion Middleware
BUSINESS INNOVATION PLATFORM

 Complete
Web Social Mobile

User Engagement
 Integrated
Business
Process
Content Business  Best-in-class
Management Intelligence
Management

Service Integration Data Integration
 Open
Identity Management  On-premise and Cloud
Development Cloud Application Enterprise
Tools Foundation Management


Integration Landscape

Functional Technical People

What?

How?

Tools & Process
Operational Technology


BPEL vs. BPMN
Which should I use?

BPEL BPMN
Designed for long running processes Designed for long running processes

Service Orchestration Process Automation

Structure Language with Control Directed Graph

Other Considerations:
 What are you licensed for?
 Who will participate in the work?


BPEL vs. BPMN
Which should I use?

Consider BPEL and BPMN as layered approaches
for handling “processes” within IT


Enterprise Gateway, Service Bus, Mediator
Different Service Brokering Styles

Oracle Enterprise
Oracle Service Bus Mediator
Gateway

• First Line of • Stateless • SCA-based
Defense Transformation deployment model
• Off-load Intensive • Service Result • Re-sequencer
XML processing Caching • Transform/Filter
including state
Service Virtualization
(DVM, XREF)
In-bound & Out-bound
Dynamic Routing


Different Service Brokering Styles


Comprehensive Service Brokering
First Line Of Service End Point
Defense Virtualization & Security
Scaling
OWSM Web
Agent Service
Web Client HTTP GET/POST
(Browser) OWSM Web
OWS

Web Service REST Service
Agent
M

Client
Web Service XML OWSM Web
Client Service Bus Agent Service
OWS

Web Service SOAP OWSM
M

Client Agent OWSM Web
Agent Service
Web Service JMS
Client OEG
OWSM Web
Agent Service
Extranet DMZ Intranet
Common Security Policies


Use the Right Tool for the Right Job
Integration Styles

Integration Integration Process-
Data-Centric through through Reference Centric
Integration Native Web Data Query Integration
Interfaces services


START
Human
participation
during
Yes, for intermediate approvals
Process Centric vs.
movement?

No or just for final approval
Data Centric
Yes (data lookups, intermediate validation, etc.)
Decision Tree
Conditional
steps? Integration Styles
No, mostly just transformation

PROCESS
Any data Yes, complex ORIENTED
enrichment
Use Service
requirement?
Integration

None, or simple foreign-key type
DATA CENTRIC
Use Data
Smaller data set Integration
How complex are the
transformations? Immediate
Transformation applied
availability
can vary based on content
requirements
and other factors

Transformation to apply is always the > 10Mb with repeating
same, regardless of content record structure

Error After insertion of
handling and complete set
reconciliation On a msg-per-msg basis in staging tables

Large and
batch oriented

Use the Right Technique for the Right Problem
Design Patterns & Reference Architecture
Message Processing Patterns
• Asynchronous messaging Benefits:
• Event-driven consumers • Guaranteed delivery
• Competing consumers • High throughput & scalability
• Service instance routing • Loosely coupled interaction
• Guaranteed delivery
• Request EBO Governance
Service //Response Patterns Benefits:
• Compatible / Incompatible changes
• Promotes organizational agility
• Schema / Service versioning
• Protects consumers from provider contract changes
• Service retirement
• Eliminates need for consumers and providers to evolve at the
• Service decomposition same rate

Integration Artifact Extensibility Patterns
• Schema extensibility Benefits:
• Service extensibility • Pre-defined extensibility points
• Transformation extensibility • Extensions are upgrade-safe
• Business process extensibility


START
How many
applications are on
each end of
integration?
Direct vs. Indirect
Design Patterns &
Only one product on each More than one product on either side
end of the integration
Reference Architecture
Requirement for
~ 5s OK
low latency?

High throughput?

Absolutely need
less than 5s end-to-end and 60% of this
 Integration guidelines
being followed by Oracle
already spent in processing at endpoint Yes
over 100,000 msg/h (~ 30 msg/s)

No

Yes Transformation
intensive?
less than 100,000 msg/h
across AIA, Fusion Apps,
Over 60% of
the work is
transformation etc.
No

 Applicable to partners,
WS interfaces
Data integration
or process-
oriented?
and XSD much
better-suited for
Direct
ISVs, and customers
Data-centric
Process-oriented no

Explore Direct Use canonical pattern
Integration & EBOs

yes

Resources
More information to help…

 BPEL vs. BPMN
– Mark Nelson’s Blog : http://redstack.wordpress.com/2011/01/15/what-bpm-
adds-to-soa-suite/
 Service Bus vs. Mediator
– http://www.oracle.com/us/technologies/soa/maximizing-benefits-oracle-
soa-150680.pdf
 Service Bus & Indirect Patterns
– http://www.oracle.com/us/products/applications/application-integration-
architecture/ssLINK/349389


Get Connected – Oracle Social Media
Oracle SOA

Twitter
twitter.com/OracleSOA
Facebook
facebook.com/OracleSOA
LinkedIn
Oracle SOA
Oracle SOA blog
blogs.oracle.com/SOA
Oracle SOA Web site
oracle.com/SOA


Get Connected – Oracle Social Media
Oracle Application Integration Architecture

Twitter
twitter.com/OracleAIA
Facebook
facebook.com/OracleAIA
LinkedIn
Oracle AIA - Application Integration Architecture
Oracle Foundation Pack blog
blogs.oracle.com/aia
Oracle Foundation Pack Web site
oracle.com/AIA


Soa pattern con8669_pdf_8669_0001

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Mehr von jucaab

Mehr von jucaab (20)

Soa pattern con8669_pdf_8669_0001