The document discusses the approach to implementing a service-oriented architecture (SOA). It defines SOA as an architecture based on reusable services that gives access to capabilities. Common drivers for adopting SOA include duplicating functionality and a mismatch between business and IT needs. The document recommends starting an SOA implementation by creating a target architecture, piloting one project, and incrementally expanding the scope. Key stakeholders in a SOA project include business users, architects, developers, and administrators.

1. Approach to SOA
Lonneke Dikmans
Sunday October 2nd 2011| Oracle Open World 2011
11||20
x

2. 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?
22||20
x

3. 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
33||20
x

4. 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?
44||20
x

5. 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
55||20
x

6. Why SOA | Duplication of functionality
66||20
x

7. Why SOA | Mismatch business and IT
77||20
x

8. 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?
88||20
x

9. 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)
99||20
x

10. 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?
10 ||20
10 x

11. 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)
11 ||20
11 x

12. 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
12 ||20
12 x

13. 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)
13 ||20
13 x

14. How to Start | Oracle solution
BPA Suite BAM GOVERNANCE
CEP Enterprise
REAL-TIME Manager
VISIBILITY
Enterprise Events System
& PROCESSING Alerts
Modeling Business Monitoring
ORCHESTRATION Streams
Data GOVERNANCE
Monitoring
Web
BPM Suite SOA Composite Services
Lightweight Native Business Human Manager
WS Policies
Modeling ROUTING & DATA SERVICES
BPEL Rules Workflow Security
Oracle Service Enterprise
JDeveloper Bus Data Integrator
Application Repository
Routing Transform ETL & Data
Development SOA lifecycle
Replication Quality
Mediation CONNECTIVITY governance
Framework
Adapters B2B Registry
Apps DB Legacy Partners UDDI
Coherence Cache
Messaging J2EE Application Server JRockit VM & RT
(Oracle WebLogic)
14 ||20
14 x

15. How to start | Oracle architecture
15 ||20
15 x

16. How to Start |
Example
● BPM & SOA
● Case management
● Master data management
● COTS (SAP, permits, …)
16 ||20
16 x

17. 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?
17 ||20
17 x

18. 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
18 ||20
18 x

19. 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
19 ||20
19 x

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…
20 ||20
20 x

21. Approach to SOA
Lonneke Dikmans
Sunday October 2nd 2011| Oracle Open World 2011
21 ||20
21 x