Soa Runtime Governance Practices

  • 2,902 views
Uploaded on

SOA-based systems are more quickly and efficiently deployed and more effectively managed through a disciplined approach to SOA runtime governance. In this presentation we outline key problems …

SOA-based systems are more quickly and efficiently deployed and more effectively managed through a disciplined approach to SOA runtime governance. In this presentation we outline key problems addressed by SOA runtime governance and current practices for effectively implementing runtime governance in SOA environments.

SOA runtime governance problems include:
1. Understanding the service network topology described by the services that participate in the service network and the message traffic flowing among those services.
2. Actively maintaining established availability and performance service levels.
3. Enforcing authentication, authorization, privacy and integrity security constraints in an application-independent fashion.
4. Managing the business transactions supported by the service network including active management of transaction performance and availability as well as detection, diagnosis and correction of business transaction faults.
5. Validating the correct operation of the service networking on a continual basis in order to actively manage dynamic changes to the service network.
The current practices for effective runtime governance are then outlined based on experiences captured in over 100 SOA implementations. The practices focus on governance architectures, capabilities and processes proven to be effective in these SOA implementations.
The presentation also outlines areas in which some established practices are less effective than expected in support of effective runtime governance specifically focusing on processes in which development organizations must proactively participate in the governance activities.
The presentation also outlines the benefits of various approaches in terms of reduced development cost, more responsive system changes, improved operational management and faster and more cost-effective service network evolution.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,902
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
6

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. SOA Runtime Governance Practices Paul Butterworth Chief Technology Officer AmberPoint, Inc October 2008
  • 2. Agenda
    • SOA Topologies
    • SOA Runtime Governance Practices
      • Discover
      • Manage Service Quality
      • Manage Business Transactions
      • Prepare for greater scale
      • Validate changes
    Based on experiences with ~200 users
  • 3. Typical Service Network Topology
    • Shared Services
    • External Services
    firewall Order Entry Accounting Partner Internal Services Credit
    • Services not applications
    • Shared
    • Dynamic
    • Federated
  • 4. Typical Service Network Infrastructure Java Service Mainframe Application Web Service DBMS Biz Application Biz Application Appliance In all but the newest of environments, “SOA” ≠ “Just Web Services & XML” Network Service Bus
  • 5. Keys to Successful Governance and Management of SOA Applications
    • Continuous SOA Discovery
    • Service Management & Security
  • 6. Keys to Successful Governance and Management of SOA Applications
    • Business System Validation
    • Closed Loop Governance
    • Continuous SOA Discovery
    • Service Management & Security
    • Business Transaction Management
    • Business
    • Architects & Development
    • Operations
  • 7. Agenda
    • SOA Topologies
    • SOA Runtime Governance Practices
      • Discover
      • Manage Service Quality
      • Manage Business Transactions
      • Prepare for greater scale
      • Validate changes
    Based on experiences with ~200 users
  • 8. Discovery and Application Mapping
    • Dynamic Discovery of your SOA environment…
      • Application Flow & Transactions
      • Dependencies
      • Services
      • Consumers
      • Runtime Policies & Metadata
    • … across Heterogeneous Infrastructure
      • Containers
      • ESBs & Process Engines
      • Appliances
      • Registries / Repositories
    • No application, message or header modifications
    • Closes the loop with design time governance
    A complete accounting of your SOA application environment Intended Design Running Reality Repositories Service Registries Home-grown Databases Messaging
  • 9. Hybrid Discovery Model
    • Approved Services
    • Intended Usage
    • Policies
    Runtime Repository Policies Data / Results service contract
    • Services (discovered, changes)
    • Scorecard Information
    • Policies (new, changes)
    Discovers Publishes
    • Publishes
      • Changes to services, endpoints and policies
      • Scorecard metrics – availability, performance, etc.
      • Dependencies
    • Detects discrepancy between intentions (design/dev) and reality (runtime)
    Reality Design vs. Service Management Xact Management System Validation Closed Loop Governance Ensures Closed Loop Governance Software Development Tools Development Tools Repositories/ Registries Home-grown Databases Enterprise Service Bus ? ? ?
  • 10. Detailed Metadata of Your SOA Environment
    • Operational Info:
      • When service was discovered
      • Availability
      • Type of service
      • Type of container
      • Link to WSDL
    • Business Info:
      • Business owner
      • Division
      • Version
      • Etc.
    • Custom:
      • Chargeback info
      • Risk assessment
      • Links to URL’s
      • Etc.
    Operational Info Business Info
  • 11. Agenda
    • SOA Topologies
    • SOA Runtime Governance Practices
      • Discover
      • Manage Service Quality
      • Manage Business Transactions
      • Prepare for greater scale
      • Validate changes
  • 12. Service Quality Management
    • Monitor Performance & Availability
      • Trends, thresholds, varying intervals, etc.
    • Isolate areas of interest
      • Recent additions
      • “ Rogue” services
      • Problem areas
      • Specific application groups
    Filters Detail Graphical View Table View
    • Monitor Security
    • Respond to anomalies
  • 13. Service Level Management Service- and Business-level Visibility
    • Enforce agreements based on business criteria
      • Flexible calendars, multiple objectives
    • Granular visibility – groups, users, services, operations
    • Preventative and corrective actions
    Service View Alerts User Summary and Objectives Historical Reporting
  • 14. Security First- and Last-Mile Enforcement Firewall Identity Management Systems
    • First Mile Security
    • Client-side agent
    • Automatic enforcement of out-bound security
    • Last Mile Security
    • Plug-ins provide endpoint protection
    • No ability to circumvent
    • Extensive Integration
    • Identity Management Systems
    • Security Appliances
    • App Server / ESB / OS Security
    • <?xml version='1.0'?>
    • <PaymentInfo xmlns='http://example.org/paymentv2'>
    • <Name>John Smith</Name>
    • <EncryptedData
      • Type='http://www.w3.org/2001/04/xmlenc#Element' xmlns='http://www.w3.org/2001/04/xmlenc#'>
      • <CipherData>
        • <CipherValue>A23B45C56</CipherValue>
      • </CipherData>
    • </EncryptedData>
    • </PaymentInfo>
    • Complete Policy Library
    • Authentication
    • Authorization
    • Credential Mapping
    • Censorship
    • Crypto
    • <Name>
    • <Encrypted
      • Type='http
      • <CipherDa
        • <Cipher
      • </Ciphe
  • 15. Agenda
    • SOA Topologies
    • SOA Runtime Governance Practices
      • Discover
      • Manage Service Quality
      • Manage Business Transactions
      • Prepare for greater scale
      • Validate changes
  • 16. Business Transaction Management Managing Individual Services is Not Enough
    • Real business value is associated with complete, end-to-end transactions
      • Order management
      • Claims processing
      • Sales lead qualification
      • On-line reservations
    • Common Issues...
      • No overall view into transaction status
      • Minimal business visibility
      • Slow end-to-end response times
      • Transactions &quot;disappear&quot;
    • Business Impact
      • Internal fire drills and finger pointing
      • Unhappy customers
      • Lost revenue
    Process Engine Service Bus End-to-End Technical Challenges
    • Transactions flow through both service and non-service based components
      • Services
      • Applications
      • ESBs
      • Process Engines
      • Databases
    • Variety of architectures
      • Synchronous and asynchronous messaging
      • Long running transactions – hours, days, ...
  • 17. Business Transaction Management Monitoring Performance, Availability & Service Level Agreements
    • Enforces agreements in real time
    • Enables preventative and corrective actions
      • Not just reporting violations after its too late
    Transaction Performance & Availability Service Level Violations Consumer SLA’s Historical Reporting
    • Business Groups
    • Platinum, Gold, etc.
    • Accounting, Shipping, etc.
    Process Engine Service Bus End-to-End
  • 18. Business Transaction Management Business Instrumentation Consumer SLA’s Business Groups Business Instrumentation
    • Track business value flowing through the system
      • Track revenue, total orders, etc.
      • Can customize instrumentation and dashboards
  • 19. Business Transaction Management Real-time Detection of Exceptions
    • Handles Technical and Business Exceptions
      • Stalled transactions, missing steps, error messages
      • Incorrect data values, boundry conditions, etc.
    • User-defined Exception Policies
      • What to look for – leverage message content
      • Action to take – notify, intervene, etc
    Rejected Order Alert
  • 20. Agenda
    • SOA Topologies
    • SOA Runtime Governance Practices
      • Discover
      • Manage Service Quality
      • Manage Business Transactions
      • Prepare for greater scale
      • Validate changes
  • 21. Runtime Policy Enforcement: Service Virtualization
    • Abstracts service changes and versions behind a published ‘façade’ (a ‘virtual’ service)
    • Enables endpoint routing, load-balancing, failover, transformations etc.
    • Sees simpler interface
    • Service changes don’t show through.
    Before After Virtual Svc (PEP)
    • Load balance
    • Route
    • Transform
    • Version
    Service B OrderLookup ChangeDate ChangeQty ScheduleShip ChangePrior LookupETA Service B OrderLookup ChangeDate ChangeQty ScheduleShip ChangePrior LookupETA Service A Service A
  • 22. Automatic Policy Provisioning
    • Policies with a “where clause”
    • Automatically applies policies based on dynamic attributes and message content .
      • All production services
      • All services in Accounting application
      • All services deployed in WebLogic containers
    • User-defined attributes for services, containers & policies
    • Assignments are reevaluated as attributes change
    s1 s5 s4 s2 s6 s3 where “ Accounting” Security Encryption all services One-at-a-Time Approach where deployed on .NET app servers Logging Profile Based Approach s1 p1 s2 s3 s100 p1 p1 p50 100 svcs x 50 policies 5,000 policy points Load-Bal Weighted
    • Can manage system on “autopilot” where policies are automatically assigned as appropriate.
    • Eliminates production mistakes by reducing manual steps.
  • 23. Agenda
    • SOA Topologies
    • SOA Runtime Governance Practices
      • Discover
      • Manage Service Quality
      • Manage Business Transactions
      • Prepare for greater scale
      • Validate changes
  • 24. Business System Validation Distributed Components and Reuse Puts Business Systems at Risk
    • Impact of any changes ripple throughout the system
      • Real impact of planned changes is hard to predict
      • Impact of unplanned or unannounced changes can be devastating
    • Yet, most SOA environments find it impossible to setup and replicate all dependent systems for testing elsewhere
    • And, new use and reuse creates blind spots in preproduction procedures
    “ Approved” Design Development QA Development Staging Production Process Engine Service Bus Need to Validate Integrity of the Entire System Before Installing Changes
  • 25. Validate Impact on Dependent Systems Development Staging Production Process Engine Service Bus The “Preflight Check” for SOA Systems
    • Acceptance testing of pending changes to SOA environment
      • New Versions of Services
      • Policy Changes
      • Bug Fixes
      • Infrastructure Patches, etc.
    • Uses knowledge of dependencies and observed interactions
    • Simulates services that can’t be replicated in pre-production environments
      • External services
      • Fee-based services
    • Gives Staging and Operations a final check before deploying changes
     : Security Policies Functioning Unexpected Deviation for B2B Partner Usage  : WS-I Compliant  : Capacity Adequate Validation Checklist
  • 26. Q&A Paul Butterworth [email_address] www.amberpoint.com 510.663.6300