Your SlideShare is downloading. ×
  • Like
Randy Heffner Vice President Forrester Research
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Randy Heffner Vice President Forrester Research

  • 322 views
Published

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
322
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
8
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. July 19, 2005. Call in at 10:55 a.m. Eastern Time Randy Heffner Vice President Forrester Research Real-World SOA: SOA Platform Patterns You Can Use
  • 2. Theme Evolve your SOA platform according to your business needs — working from your existing infrastructure
  • 3. Six stylized paths to SOA
    • Your path to SOA will borrow and combine elements from six generic paths to SOA:
      • Simple internal integration
      • Infrastructure services
      • Rich internal integration
      • Multichannel applications
      • External partner integration
      • Core business flexibility
  • 4. SOA platform vision — three core value propositions Service lifecycle environment Core application platforms … Service delivery network Service command platform Service clients Service interfaces Control Change Connection
  • 5. Queensland Transport — Early SOA (1997)
    • Regional government agency in Australia
    • Applications
      • Vehicle titles and registration, customer service appointments, distribution of public information
      • SLAs: 2 sec response for 90% of txns (XML-RPC)
    • Key choices
      • Implement services using native J2EE and CICS servers
      • XML only for external interfaces
      • Simple solutions for security and interface definition
    • Paths to SOA
      • Integration (simple internal, external), infrastructure services, multichannel applications
  • 6. Pattern: Non-SOAP, basic SOA J2EE (Borland) Business services Oracle Custom XML server CICS Business services DB2 AllFusion Gen tools Web server Web applications CA WSDM (future) XML Schemas XML-RPC External partners Public access PKI Web server CA AllFusion Gen CA AllFusion Gen Internal External Custom web framework monitoring management HP OpenView J2EE calls CICS services XMLSpy Two-way SSL
  • 7. Queensland Transport — Lessons
    • SO is a business model, not a technical solution
      • It’s about business transformation
      • Think through the full value chain, not just internal processes
    • Use business process analysis to find services of value
    • Be prepared for service support issues
      • End users will come to you when they have issues, not to an intermediate provider
  • 8. Unique (Zurich Airport) — SOA-based portal
    • Manages the operations of Zurich airport
    • Applications
      • Airport management portal — integrates data and transactions from multiple outsourced systems
      • Up to 50 msgs/sec @ 20 ms to 500 ms latency (most messages are very small)
    • Key choices
      • Require each externally hosted application to expose SOAP
      • Single access channel to integrate applications
    • Paths to SOA
      • Rich internal integration, quasi-external integration
  • 9. Pattern: Layered SOAP, reliable delivery SOA SourceSafe SOAP .NET / Windows 2003 Server Business services webMethods webMethods tools Airport management portal SOAP SOAP SOAP Airport operations Radar data Baggage Other SOAP Local data cache User interaction Other (flight status) Private network connections to externally hosted applications reliable delivery events monitoring policy XMLSpy VS.NET
  • 10. Unique (Zurich Airport) — Lessons
    • Separate service specification and implementation
      • First, define the service interface
      • Design interfaces based on process requirements
      • Then, design how to fulfill the service
    • Do not put business logic in the delivery network
    • Get an early handle on governance of data semantics
  • 11. Large financial institution — SOAP-centric SOA
    • Applications
      • Customer systems, check image services, account inquiry, insurance services
      • Started with XML over MQ, now moving to Web services
      • Tested to 300 request/reply roundtrips per second
    • Key choices
      • Focused on unifying service access
      • Focused on performance of XML transformations
      • Avoided repository (so far), but addressed vocabulary management
    • Paths to SOA
      • Simple and rich internal integration, multichannel applications
  • 12. Pattern: Unified service delivery network SOA Systinet WebLogic tools Service consumers OpenView (no WSM) Contivo WebLogic Server (J2EE) IMS NonStop
    • Compensating transaction capabilities implemented in services
    • Native protocols used to connect to downstream applications
    metadata mgt transforms DataPower WebLogic Integration SOAP SOAP XML over MQ Compensating transaction logic implemented in service consumers WebSphere MQ SOAP Systinet tools Native tools transforms adaptation monitor / mgt enhanced SOAP Scripting tools deployment SOAP XMLSpy
  • 13. Large financial institution — Lessons
    • Getting IT executive buy-in to SOA vision is very important
      • Enterprise-level funding because CIO gets the vision
    • Start small and learn, then get a couple of big, visible projects
      • Be sure projects know that SOA is an executive priority
      • Do “project interventions” to identify and design good service interfaces — and to build project team competency
    • Web services standards are only a start: much more work is required
    • Don’t worry about a repository until you have the discipline to use it
  • 14. Large North American bank — Custom SOA
    • Applications
      • Centered around customer information: retail banking, check images, stop payment
      • Mission-critical volumes for internal applications
      • External response times typically less than 2 seconds
    • Key choices
      • Continue to leverage high QoS of custom middleware
      • Work with multiple existing EAI products
      • Unify legacy service interfaces on the mainframe
    • Paths to SOA
      • Integration (simple, rich, external), multichannel applications
  • 15. Pattern: Diverse, custom delivery network SOA VS.NET .NET SOAP / RMI TIBCO Vitria BizTalk CICS DataPower WebSphere WebSphere Studio EAI tools Custom middleware Service consumers (internal) routing encryption identity propagation Word of mouth “ repository” Rational IMS WebSphere 390 Tivoli (no WSM) PKI Aion BPM Metadata mgt Identity & access mgt SOAP External partners DMZ security monitoring management Future leverage Legacy tools Sun ONE meta-directory
  • 16. Large North American bank — Lessons
    • Reuse is nice, but business agility is the real payback
      • Good service design enables “pluggable business” (e.g., business process outsourcing)
    • Semantics (data, interface) can make or break you
    • Many services management issues tie back to your firm’s standard for message headers
      • If it’s not in the header, you can’t manage it
    • Central funding is critical for thinking through your architecture strategy
  • 17. Thomson Prometric — SOA for flexibility
    • Manages certification test delivery at 4,000 training centers
    • 300+ external partners (test owners)
    • Applications
      • Test center scheduling and capacity management, test delivery
      • No concerns about messaging volumes — can scale using load balancing in standard ways
    • Key choices
      • Use orchestration to overcome underlying application limitations
      • Use Web services management for policy and versioning
      • Implement a dual-identity scheme (test owners, test takers)
    • Paths to SOA
      • Internal (rich, external), multichannel applications, core flexibility
  • 18. Pattern: Process and policy driven SOA VS.NET BizTalk Actional Reactivity J2EE tools OpenView Prometric’s Web applications monitoring management policy version resolution encryption identity (dual) Web page “ repository” Visio orchestration reliable messaging B2B connections rules engine compensating txns LDAP Partner Web apps Manual deployment .NET WebLogic WebSphere
  • 19. Thomson Prometric — Lessons
    • How much your SOA will achieve is limited by how big your SOA thinking is
    • Business process modeling is core to SOA success
      • Craft new processes, don’t just document existing processes
    • Orchestration provides one of the biggest value opportunities within SOA
      • Process/workflow centric knowledge worker applications enabled by the underlying services
  • 20. Overall themes and recommendations
    • Business drives architecture
      • Guide SOA evolution based on business needs
      • Leverage existing infrastructure
      • SOA creates opportunities for “pluggable business”
    • As a strategy for business design, SOA applies to many scenarios
      • Services must be designed in a process-centric way
    • Learn from emerging patterns in the real world
      • Start SOA platform design with the service delivery network
      • Orchestration is a good first step into greater levels of SOA flexibility
  • 21. Selected bibliography
    • March 29, 2005, Trends “The Elements Of SOA Maturity”
    • March 29, 2005, Trends “Your Strategic SOA Platform Vision”
    • December 7, 2004, Trends “Your Paths To Service-Oriented Architecture”
    • June 18, 2004, Trends “The Big Strategic Impact Of Organic Business And Service-Oriented Architecture”
    • August 13, 2004, Tech Choices “What Is An Enterprise Service Bus?”
    • July 16, 2003, Planning Assumption “Service Orientation: Service-Based Design Is The High-Value Investment”
    • October 27, 2003, Planning Assumption “Case Studies Show Incremental Path To Service-Oriented Architecture ”
    • April 1, 2004, Best Practices “Nine Tips For SOA Implementation”
  • 22. Thank you Randy Heffner rheffner@forrester.com www.forrester.com Entire contents © 2005 Forrester Research, Inc. All rights reserved.