approach to soa:making this a successful endeavor for the whole organization
DESCRIPTION
TRANSCRIPT
1 | x 1 | 20
Approach to SOA
Lonneke Dikmans
Sunday October 2nd 2011| Oracle Open World 2011
2 | x 2 | 20
Agenda | Approach to SOA
Making this a successful endeavor for the whole
organization
● What is SOA?
● Why do you need SOA?
● When do you start?
● How do you start?
● Who is involved?
3 | x 3 | 20
What is SOA |Definition
SOA = Service Oriented Architecture
● Architecture based on services
● A service gives access to a capability
Key features of a service
● Interface, contract, implementation (example: breakfast)
● Consumer, provider, registry
● Interoperable
● Idempotent
● Based on standards
4 | x 4 | 20
Agenda | Approach to SOA
Making this a successful endeavor for the whole
organization
● What is SOA?
● Why do you need SOA?
● When do you start?
● How do you start
● Who is involved?
5 | x 5 | 20
Why SOA | common drivers
Information is becoming more and more important
• Duplication of information and functionality
Need to change fast is becoming more important
• Mismatch between business and IT
6 | x 6 | 20
Why SOA | Duplication of functionality
7 | x 7 | 20
Why SOA | Mismatch business and IT
8 | x 8 | 20
Agenda | Approach to SOA
Making this a successful endeavor for the whole
organization
● What is SOA?
● Why do you need SOA?
● When do you start?
● How do you start?
● Who is involved?
9 | x 9 | 20
When SOA | Gartner
Strategic drivers
• Fast changing markets
• Mergers and acquisitions
Tactical drivers
• Self service
• Multi channel approach
• Operational excellence
IT drivers
• Inability to change fast enough with business (flexibility)
• Lower maintenance cost (re-use)
• Avoid Vendor lock-in (standards)
10 | x 10 | 20
Agenda | Approach to SOA
Making this a successful endeavor for the whole
organization
● What is SOA?
● Why do you need SOA?
● When do you start?
● How do you start?
● Who is involved?
11 | x 11 | 20
How to start SOA
Making this a successful endeavor for the whole
organization
● Create a target architecture sketch
• Define important principles
• High level solution architecture
● Start with one project/process
• Improve a process
• Think about the generic items in this process
● Make it incrementally more generic
• Add a new process
• Refactor the results from the previous project(s)
12 | x 12 | 20
How to Start | target architecture
Important principles
• Avoid duplication of information: appoint a single point of
truth
• Services are idempotent
• Service layering
• Standardization of processes?
Tool stack
• User interface
• Process engine
• Service bus
• Services
13 | x 13 | 20
How to Start | solution architecture
Tool stack
• Comprehensive suite or best of breed
• Portal product, or build a comprehensive UI
• Workflow/ process engine or developing logic
• Implementation of services
• Composite services (Service Bus, BPEL)
• Elementary services (PL/SQL, Java, .NET)
14 | x 14 | 20
How to Start | Oracle solution
Apps
Adapters B2B
Partners DB Legacy
CONNECTIVITY
Routing Transform Data
Quality
ETL & Replication
Data Integrator Oracle Service
Bus
Mediation
ROUTING & DATA SERVICES
Native
BPEL
Business
Rules
Human
Workflow
ORCHESTRATION
Coherence Cache J2EE Application Server
(Oracle WebLogic)
Messaging
GOVERNANCE
System
Monitoring
Enterprise Manager
UDDI
WS Policies
Security
Web Services Manager
Registry
GOVERNANCE
SOA lifecycle governance
Enterprise Repository
JRockit VM & RT
REAL-TIME VISIBILITY
& PROCESSING
Alerts Business Monitoring
BAM
Events
Data Streams
CEP
Application Development
Framework
Enterprise
Modeling
BPA Suite
JDeveloper
Lightweight
Modeling
BPM Suite SOA Composite
15 | x 15 | 20
How to start | Oracle architecture
16 | x 16 | 20
How to Start |
Example
● BPM & SOA
● Case management
● Master data management
● COTS (SAP, permits, …)
17 | x 17 | 20
Agenda | Approach to SOA
Making this a successful endeavor for the whole
organization
● What is SOA?
● Why do you need SOA?
● When do you start?
● How do you start?
● Who is involved?
18 | x 18 | 20
Who is involved | Stakeholders
Business • Management: decide goals and principles
• Users: change procedures, new interfaces
Architects • Understand the relationship between services and processes
• Decide on technology and principles
• Design and adjust target architecture
IT • Developers: Different technologies and standards, dev tools
• Administrators: what happens if server X goes down
• Change management
19 | x 19 | 20
Conclusion | Approach to SOA
Making this a successful endeavor for the whole
organization
● Decide what you want to standardize and why
● Don’t change everything at once: pick your battles
● Start with ESB, don’t leave that out!
● Start with some people who have done this before
20 | x 20 | 20
Information |this week and beyond
OOW11
• Sessions on SOA/BPM
• Sessions on Java
• Sessions on Fusion apps
OTN
http://www.oracle.com/technetwork/middleware/fusion-middleware/overview/index.html
Shameless plug: SOA Made Simple
By Ronald van Luttikhuizen & Lonneke Dikmans
Packt publishing
Next year…
21 | x 21 | 20
Approach to SOA
Lonneke Dikmans
Sunday October 2nd 2011| Oracle Open World 2011