Approach to SOA:Making this a successful endeavor for the whole organization

803 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
803
On SlideShare
0
From Embeds
0
Number of Embeds
24
Actions
Shares
0
Downloads
10
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Approach to SOA:Making this a successful endeavor for the whole organization

  1. 1. Approach to SOALonneke DikmansSunday October 2nd 2011| Oracle Open World 2011 11||20 x
  2. 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. 3. What is SOA |Definition SOA = Service Oriented Architecture● Architecture based on services● A service gives access to a capabilityKey features of a service● Interface, contract, implementation (example: breakfast)● Consumer, provider, registry● Interoperable● Idempotent● Based on standards 33||20 x
  4. 4. Agenda | Approach to SOAMaking 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. 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. 6. Why SOA | Duplication of functionality 66||20 x
  7. 7. Why SOA | Mismatch business and IT 77||20 x
  8. 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. 9. When SOA | GartnerStrategic drivers • Fast changing markets • Mergers and acquisitionsTactical drivers • Self service • Multi channel approach • Operational excellenceIT drivers • Inability to change fast enough with business (flexibility) • Lower maintenance cost (re-use) • Avoid Vendor lock-in (standards) 99||20 x
  10. 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. 11. How to start SOAMaking 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. 12. How to Start | target architectureImportant 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. 13. How to Start | solution architectureTool 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. 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 EnterpriseJDeveloper Bus Data Integrator Application Repository Routing Transform ETL & DataDevelopment SOA lifecycle Replication Quality Mediation CONNECTIVITY governance Framework Adapters B2B Registry Apps DB Legacy Partners UDDI Coherence CacheMessaging J2EE Application Server JRockit VM & RT (Oracle WebLogic) 14 ||20 14 x
  15. 15. How to start | Oracle architecture 15 ||20 15 x
  16. 16. How to Start | Example● BPM & SOA● Case management● Master data management● COTS (SAP, permits, …) 16 ||20 16 x
  17. 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. 18. Who is involved | StakeholdersBusiness• Management: decide goals and principles• Users: change procedures, new interfacesArchitects• Understand the relationship between services and processes• Decide on technology and principles• Design and adjust target architectureIT• Developers: Different technologies and standards, dev tools• Administrators: what happens if server X goes down• Change management 18 ||20 18 x
  19. 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. 20. Information |this week and beyondOOW11• Sessions on SOA/BPM• Sessions on Java• Sessions on Fusion appsOTNhttp://www.oracle.com/technetwork/middleware/fusion- middleware/overview/index.htmlShameless plug: SOA Made SimpleBy Ronald van Luttikhuizen & Lonneke DikmansPackt publishingNext year… 20 ||20 20 x
  21. 21. Approach to SOALonneke DikmansSunday October 2nd 2011| Oracle Open World 2011 21 ||20 21 x

×