Gaining Control of Your SOA

1
(No Transcript)
2
Gaining Control of Your SOA
Willie Kirkpatrick VP EMEA AmberPoint
3
Long Time Microsoft SOA Partner

• Joint development, licensing, and distribution
• Wide support of Microsofts SOA stack
• Visual Studio
• .NET variations
• BizTalk
• Visual Studio
• System Center Ops Mgr
• Native C implementation of AmberPoint
• Version of AmberPoint bundled with Visual Studio

4
Unive
Insurance Company Netherlands

• Business Problem
• The Netherlands changed to an open enrollment
  model
• Competitive market required direct customer
  access to information and enrollment
• Targeted Health Insurance System first
• Technical Approach
• Exposing internal processes applications for
  internet use by customers
• Microsoft Stack
• Visual Studio
• .NET
• SharePoint
• Systems Center Ops Manager
• Transformed Mainframe Applications
• Redundant sites for High Availability

Site 1
Site 2
HTML Services
HTML Services
74 Services
Business Services
Business Services
177 Endpoints
Legacy Services
Legacy Services
5
Unive
Insurance Company Netherlands

• Technical Problem
• Complex, distributed transactions (SOA) made it
  hard to manage running applications
• Difficult to
• Diagnose issues
• Ensure high availability
• Meet QOS requirements
• Solution AmberPoint
• Business Results
• With on-line, immediate cross checks and data
  validation, over 60 of new applications
  processed directly into mainframe apps
• Results
• If we hadnt started using AmberPoint, we would
  have stopped using SOA. Bob Alberts, Project
  Director

6
Vital Forsikring
Largest Life Pensions company in Norway

• Business Problem
• Increasingly competitive market driving need to
  reduce costs and increase agility.
• Technical Approach
• Migration from Mainframe to SOA overtime
• Microsoft Stack
• .NET 2.0
• BizTalk Server 2006
• Systems Center Ops Manager
• Windows 2003 64bit
• Benefits
• Lower mean time to repair
• Ability to provide reliable, secure self-service
  application, including a pensions portal for
  smaller organizations

Portal
Files
BizTalk
BizTalk
30 Services
60 Endpoints
Business Services
Business Services
7
Keys to Successful Runtime Governance of SOA
Applications

• Visibility Knowing Whats Out There and Whats
  Going On
• Control Putting Policies into Action
• Ensuring Integrity Ensuring Changes Dont
  Impact the Whole Application Environment
• Handle the entire infrastructure
• Do it all automatically
• Reduces risks and costs
• Automation is the single most important thing
  that makes SOA scaleable

8
SOA Governance
Design Time Gov. Dev QA Tools Lifecycle
Management Approval Processes Service
Registry Policy Requirements
Runtime Gov. Service Level Mgmt Transaction
Monitoring Auditing / Logging Security Policy
Enforcement
SOA Infrastructure App Servers Enterprise
Service Bus Appliances Legacy Systems Process
Management Databases
9
Closed Loop SOA Governance
Design Time Gov. Dev QA Tools Lifecycle
Management Approval Processes Service
Registry Policy Requirements
Runtime Gov. Service Level Mgmt Transaction
Monitoring Auditing / Logging Security Policy
Enforcement
Intended Design
Running Reality
?
SOA Infrastructure App Servers Enterprise
Service Bus Appliances Legacy Systems Process
Management Databases
?
10
Closed Loop SOA Governance
Design Time Gov. Visual Studio Team
System Repository
Runtime Gov.
Intended Design
Running Reality
?
SOA Infrastructure .NET / Windows Communication
Foundation BizTalk SharePoint SQL Server Etc.
?
11
Closed Loop SOA Governance
Design Time Gov.
Runtime Gov.
Intended Design
Running Reality
?
SOA Infrastructure
?
12
Automatic End-to-End Discovery

• Dynamic Discovery of your SOA environment
• Dependencies
• Services Consumers
• Transaction Flow
• Runtime Policies Metadata
• across Heterogeneous Infrastructure
• Containers
• ESBs
• Appliances
• Registries / Repositories
• No application, message or header modifications
• Automatically feeds Design Time Governance

Repositories
Home-grownDatabases
ServiceRegistries
Design Information
Running Environment
Ensures Complete Accounting of Your SOA
Environment
13
AmberPoint SOA ExplorerReal-time view of overall
environment and status
Table View

• Quick filters to rapidly isolate areas of
  interest
• Transaction flow
• Recent additions
• Problem areas
• Specific application groups
• Rogue services
• Take action
• Place under management
• Apply missing policies
• Drill down into detail
• Sortable, printable, exportable information

Graphical View
Filters
Drill Down
14
End-to-End Transaction Monitoring
DiagnosisFrom Clients, through Infrastructure,
Applications, and Endpoints
Drill into TransactionContent Context
Performance
Business Transactions
and

• Process Flow
• Exception context
• Response times

• Follows transactions through SOA and non-SOA
  components
• ESBs
• Java and .NET Applications
• Databases
• Detects problems with business flows
• Performance issues
• Missing or stalled steps
• Failures

eCommerce System
Order
Warehouse
Shipping Partner
Credit Check
Order Management
15
Real-time Monitoring of Business
TransactionsProbe applications for
inconsistencies

• Check transaction progress and correctness
• Does not need to be synchronous or see every step

Expected DeliveryDisconnect Alert
16
Service Level ManagementSLA enforcement for
transactions, groups, users, and services
User-level SLAs
Transaction-level SLAs
Historical Reporting
Multiple Objectives per Agreement
ServiceLevel Violations

• Enforces agreements based on business criteria
• Gold users, Accounting systems at the end of
  quarter, etc.
• Flexible calendars, scheduled downtimes, fixed
  and sliding time windows
• Preventative and corrective actions

17
Take Preventative / Mitigating ActionA
Throttling Example
Performance against objectives
1
3
Service Level Agreement

• Service Level Objective (SLO)
  
• For Platinum customers
• Ave. Response time per hour lt 6 sec
• Warning threshold lt 4 sec
• - Action Throttle non-Platinum users

Usage segmented e.g. by Platinum, Gold, Silver
2
Gold
Bronze
Platinum
18
Take Preventative / Mitigating ActionA
Throttling Example
Performance against objectives
1
3
Service Level Agreement
Stabilized response times
5

• Service Level Objective (SLO)
  
• For Platinum customers
• Ave. Response time per hour lt 6 sec
• Warning threshold lt 4 sec
• - Action Throttle non-Platinum users

Usage segmented e.g. by Platinum, Gold, Silver
2
Gold
Bronze
Automatically triggers throttling before
compliance failure
Platinum
4
Throttling Policy
19
Closed Loop SOA Governance
Design Time Gov.
Runtime Gov.
Intended Design
Running Reality

• Discovered Services Dependencies
• Transaction Monitoring
• Performance metrics
• Policy enforcement
• Security
• Throttling
• Version transparency
• Users
• Authorized
• Unauthorized attempts
• Policy additions
• Discovered policies
• Operational additions

?

• Approved Services
• Intended reuse
• QOS requirements
• Policy requirements

?
20
Policy-based Approach to Runtime
GovernanceEnforced across the infrastructure

• Pre-built library of most commonly used runtime
  policies
• User-extensible

• Instrumentation
• Version management
• Service level agreements
• Exception handling
• Content-based Policies
• Authentication certificates, credentials, SAML,
  etc
• Authorization
• Censorship
• Credential Mapping
• Crypto Signatures Encryption

• Throttling
• Quality of Service
• Performance
• Availability
• Throughput
• Failover
• Load balancing
• Validation

21
Automated Policy Provisioning
??Select policy
??Policy enforcement across the infrastructure
??Configure
Service Metadata
??Set policy criteria
22
Combing AmberPoint BizTalk creates a SOA Grid
with a clean separation of responsibilities
Microsoft BizTalk
Managed Endpoints
Virtual Service Provider

• Orchestration
• Protocol Mediation
• Message Routing
• Content Transformation

Controls Service-to-Service Interactions
Controls Service-to-Endpoint Interactions

• Resource Management
• Discovery / Registration
• End-to-end Visibility
• Measurement
• Message Distribution/Utilization
• Availability
• Access Control

23
Runtime Governance of Virtual Service Providers
Balanced Service Provider
Resilient Service Provider

• Qualities
• Scalability
• Performance
• Capacity
• Benefits
• Balanced
• Distributed
• Manageable

VSP
VSP

• Qualities
• Reliability
• Availability
• Benefits
• Highly Available
• Fault Tolerant

LB
LB
FO
MEP
MEP
MEP
MEP
MEP
MEP
Secure Service Provider
Evolving Service Provider

• Qualities
• Security
• Integrity
• Confidentiality
• Benefits
• Tamper Resistant
• Private
• Controlled Access

VSP
VSP

• Qualities
• Version Transparency
• Flexibility
• Benefits
• Agile
• Controlled Access
• Deprecation

VT
MEP
MEP
MEP
MEP
MEP
MEP
v2
v1
vn
24
AmberPoint SOA Runtime Governance
Mark Munro Senior Sales Engineering Northern
Europe - AmberPoint
25
In an ESB Scenario
Service-Oriented Infrastructure
Supported Service Consumer
Supported Service Provider
CIM
SIM
Standard Service Consumer
Standard Service Provider
Service Registry
Service Management
Security
Legend CIM Consumer Integration Module SIM
Service Integration Module
26
MedicAlert
Health Care Services Personal health records for
4,000,000 world-wide members.

• Key Requirements
• Ensure high QoS requirements for access to
  MedicAlert services critical health
  implications
• Ensure last-mile security for sensitive
  private patient information

eHealthKey

• Chosen Solution
• AmberPoint
• Visibility into service usage and performance
  bottlenecks
• Monitor impact of security management policies
  on their SOA
• Version transparency different eHealthKey
  versions
• Microsoft .NET and BizTalk
• Orchestration Mediation

• Results
• Can usually have a running prototype assembled
  faster than the marketing guys can write up their
  requirements. Jorge Mercado, CTO

27
Closed Loop SOA Governance
Design Time Gov.
Runtime Gov.
Intended Design
Running Reality

• Discovered Services Dependencies
• Transaction Monitoring
• Performance metrics
• Policy enforcement
• Security
• Throttling
• Version transparency
• Users
• Authorized
• Unauthorized attempts
• Policy additions
• Discovered policies
• Operational additions

?

• Approved Services
• Intended reuse
• QOS requirements
• Policy requirements

?
28
(No Transcript)