SOA Simplified - Service Virtualization With The Managed Services Engine
By Aaron Skonnard | May 2009
This article discusses:
This article uses the following technologies:
Managed Services Engine, .NET Services, Windows Server, SQL Server, WCF
A Service Virtualization Implementation Pattern
Microsoft Services SOA Infrastructure
Understanding the Managed Services Engine
Getting Started with the MSE
Importing Service Resources from WSDL
Importing a RESTful Service Resource
Defining Virtual Service Endpoints
Versioning, Policies, and WCF Behaviors
Defining Virtual Cloud Endpoints
- Can you trust your services to support mission-critical business processes?
- Can you make changes to existing services without wondering what might break?
- Do you have design-time and runtime visibility across all your systems and services?
- Can business, operational, and policy changes be made without requiring developer involvement?
|Figure 4 MSE End-to-End View Elements|
|Systems||Describes the servers hosting the real services (that you wish to virtualize)|
|Instances||Describes the individual service endpoints running on a particular system|
|Resources||Describes the service operations supported by a particular service "instance"|
|Operations||Describes virtual service operations that map to specific resources|
|Endpoints||Describes virtual service endpoints that support a set of specific virtual operations|
|Servers||Describes the MSE runtime servers hosting the virtual endpoints|
|Bindings||Describes a set of binding configurations used by instances and endpoints|
|Policies||Describes a set of policies that can be used by most artifacts|
|Data Entities||Describes a set of data entities that are used to define operation contracts|
<bindings > <netTcpRelayBinding> <binding name="default"> </binding> </netTcpRelayBinding> </bindings>