virtual techdays INDIA │ august 2010 Deep Dive into WCF 4.0 Features Sarath S S V S │ Program Manager, BING, Microsoft India R&D

Configuration Windows Server AppFabric Monitoring Endpoint Discovery - WS-Discovery Protocol Routing virtual techdays INDIA │ august 2010 S E S S I O N A G E N D A

Endpoint Configuration in 3.x vdir2 Web. config Echo. svc A A B B C C Service vdir2 vdir1

Default Endpoints Echo. svc A A B B C C Service SchemeBinding …… Protocol Mapping ServiceHost. AddDefaultEndpoints() vdir2 Echo. svc vdir2 vdir1

Web. config Default Bindings A A B B C C Service vdir2 Echo. svc vdir2 vdir1 <binding name="" maxBufferSize=" " maxReceivedMessageSize=" "/>

Web. config Default Behaviors A A B B C C Bv vdir2 Echo. svc vdir2 vdir1 Web. config

Default Behaviors A A B B C C Bv Bv vdir2 Echo. svc vdir2 vdir1 Web. config

Configuration WCF 4.0 provides support for standard endpoints--a set of preconfigured endpoints to minimize on the otherwise tedious configuration that is needed to host or consume a WCF service. The standard endpoints available in WCF 4.0 include the following: dynamicEndPoint discoveryEndpoint udpDiscoveryEndpoint announcementEndpoint udpAnnouncementEndpoint mexEndPoint webHttpEndpoint webScriptEndpoint workflowControlEndpoint

Configuration Demo

Windows Server.NET Framework Windows Server AppFabric Services Management Tools IIS/WAS Workflows Windows Server AppFabric (formerly codename “Dublin”) Runtime Databases Persistence Monitoring Hosting Persistence Caching Monitoring IIS Manager Modules PowerShell

WCF Application WCF Analytic Trace WCF Analytic Trace WCF Message Logging WCF Message Logging Diagnostic Trace Diagnostic Trace ETWETW.svclog EventCollectorEventCollector Extensions to IIS Manager Extensions to IIS Manager MonitoringDBMonitoringDB PowerShell command- lets PowerShell command- lets

End Point Discovery Problem : In WCF 3.x, if a binding need to change at the service side, say from basic to WS over HTTP, client has to update the proxy again which can be error prone Solution : End Point Discovery or Dynamic Service Mechanism WCF 4.0 supports WS-Discovery Protocol 12

Discovery The ability to publish a service’s endpoint metadata and discover services using well defined criteria Design time Find available services Runtime Reduced Config Location agility Dynamic / self healing apps WS-Discovery – Standard interoperable discovery protocol

WS-Discovery Protocol – How it works? 14 Service Client WS-Discovery Protocol Multicast protocol issuing SOAP messages over UDP Hello Announcement Message Client Initialized Bye Announcement Message Multicast Probe Message (SOAP) Probe Match Message (SOAP) Client is removed from network Multicast Resolve Message(SOAP) Resolve Match Message(SOAP) To find services that have changed endpoint Info necessary to contact the service

Ad-hoc Discovery Hello

Ad-hoc Discovery Probe ProbeMatch

Ad-hoc Discovery Bye

Managed Discovery Probe HelloProbe Hello ProbeMatch Jurgen

Discovery Message Parts Types List of xs:QName Contracts required by client or supported by target service Scopes List of xs:anyURI Scopes required by client or in which target service resides EndpointReference wsa:EndpointReference EndpointReference to the target service

Description Discovery Runtime Discovery Behaviors Discovery Service & Client Announcement Service & Client Discovery Proxy Contracts Discovery Contract Announcement Contract Find Criteria Endpoint Discovery Metadata Discovery Service Extension Dynamic, Discovery, and Announcement Endpoints

End-Point Discovery DEMO 21

ScenariosConcerns Basic Message Routing Protocol Bridging Service Aggregation Versioning … Connection State Security Delivery Failure Transactions … Message Pump Routing Service

Message Routing Client Time Service Routing Service Routing Service Echo A A B B C C Supported Message Exchange PatternsMulticastInterface Request Reply, Sessionful Request ReplyNoIRequestReplyRouter OneWayYesISimplexDatagramRouter Sessionful OneWayYesISimplexSessionRouter Sessionful DuplexYesIDuplexSessionRouter

Message Routing MessageFilterEndpoint action == action == TimeService Client Time Service Routing Service Routing Service Echo Filter OnMessageFilter ActionActionMessageFilter Address headerAddressMessageFilter Address header – longest prefix matchingAddressPrefixMessageFilter Endpoint NameEndpointNameMessageFilter No Filter – matches everythingMatchAllMessageFilter Logical And of two filtersStrictAndMessageFilter XPath expressionXPathMessageFilter Custom

Protocol Bridging Client Service Routing Service Routing Service BasicHttpNet.Tcp SOAP 1.1SOAP 1.2

Security Client Service Routing Service Routing Service

Error Handling Client Backup Echo Service Routing Service Routing Service Echo Service Echo Service MessageFilterEndpointAlternate Endpoints action == EchoBackup EchoService

Summary WCF 4 continues to simplify service boundaries by Improving the config model Management and Monitoring is made easier with the Windows Server AppFabric Providing a RoutingService in the framework Enabling dynamic applications with Discovery

Additional Resources Chalk Talks Windows Server AppFabric: Monitoring and Management Hands On Labs > Introduction to Workflow Services in.NET 4 What’s new in WCF 4? On the Web WCF Developer Center Windows Server AppFabric Developer Center: Team Blog: Nicholas Allen’s Blog:

Learn More On Channel 9 Expand your PDC experience through Channel 9 Explore videos, hands-on labs, sample code and demos through the new Channel 9 training courses channel9.msdn.com/learn Built by Developers for Developers….

virtual techdays THANKS │ august 2010

WS-Discovery Protocol A multicast protocol that issues SOAP message over UDP. It defines a lightweight discovery mechanism for discovering services based on multicast messages. It enables a service to send a Hello announcement message when it is initialized and a Bye message when is removed from the network. Client or consumer can discover services by multicasting a Probe message to which a service can reply with a ProbeMatch message containing the information necessary to contact the service. Client or consumer can find services that have changed endpoint by issuing a Resolve message to which respond with a ResolveMatchmessage. 32