Introducing Managed Services Wolf Gilbert Architect Evangelist Microsoft Corporation

Value of Service Enablement Reach, Reuse and Manageability are key to success in the Enterprise Previous efforts focused on Reuse and some Reach Success with Reach and Reuse leads to more difficulty with Management Explicit Machine Readable Policy Move "policy" issues out of code -> be more productive Must treat Services as a System Difficult to even talk about with out a Model

Enterprise Service Orientation Maturity Model (ESOMM) Maturity Models descend from Carnegie Mellon’s CMM Some current “SOA Maturity Models” move Best Practices instead of Best Principles CMM was process focused because it was a Maturity Model for the Software Development Process Levels in a Maturity Model should be Self- Evident The levels are only useful in so much as they define “meaningful” states. Maturity Models should be Prescriptive Need to show where you are, where you wish to be and how to get there.

ESOMM Maturity Levels Enterprise is capable of writing and consuming standards conformant Services with excellent reach Enterprise implements, consumes, and reuses Services efficiently and consistently Enterprise can effectively Manage and Support large numbers of Services with guaranteed SLA's Enterprise is capable of aggregating Services and extending their use beyond its own borders

ESOMM Perspectives Implementation Consumption Administration

ESOMM Capabilities Implementation Consumption Service Collaboration Service Orchestration External Policy Service SDK's Business Analytics Automated Policy Mgmt Schema Bank Runtime Policy Versioning Execution Visibility Explicit SLA’s Service Portal Auditing Provisioning Model Advanced Monitoring Common Schema Service Blocks Self Provisioning Service Discoverability Enterprise Policies Deployment Management Development Processes Design Patterns Testability Explicit Contracts Basic Monitoring Security ModelAdministration

Key Challenges WSE 2.0/WSE 3.0/WCF/Brand X Toolkit Incompatibilities Service Granularity Service Versioning Managing Policy Changes Service Level Monitoring Testability Scalability

Managed Services Services as a System Service is entirely Virtual The "Operation" is really the "Service“ Service Definition (interface) distinct from Service Implementation Service Definition Consists of Four Parts: Endpoint; Message; Policy; Context (Intent + State) The "Service Network" requires a "Runtime Engine" Executable Policy; Schema Bank; Service Blocks; etc. Topology is an implementation detail This isn't about the ESB!

Managed Services Engine Reference Architecture The Managed Services Engine processes Service Requests with Messaging, Brokering, and Dispatching..

© 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.