How Does a WCF Service Work? A host application must perform several tasks, whichinclude: || Starting and stopping the service || Listening for requests from a client application anddirecting them to the service || Sending any responses fr
how does a wcf service work?
A host application must perform several tasks, whichinclude:
|| Starting and stopping the service
|| Listening for requests from a client application anddirecting them to the service
|| Sending any responses from the service back to the clientapplications
Service Endpoints
-The address of the service
-The binding supported by the service
-Thetransport protocol
-ifyou are using IIS to host the service, you should specify
the HTTP or HTTPS transport protocol. WCF also has built-insupport for the TCP
protocol, named-pipes, and message queues.
-The encoding format of messages
-Inmany cases, request and response messages will be transmitted in XML format, encoded as ordinary text.However, in some
cases you might need to transmit data using a binaryencoding, especially if you are transmitting images or handling streams
-The security requirements of the service
-Youcan implement security at the transport level and at the message level
-The transactional requirements of the service
-The reliability of communications with the service
-Networksare notoriously unreliable and can fail at any time.
-The contract implemented by the service.
Processing a Client Request
The WCF runtime environment for a client application and a service provides acollection of channel objects that can perform this processing for you.
A channel is responsible for handling one aspect of message processing, as specified by the bindings of a service
The WCF runtime composes channels into a channel stack.All messages passing between the client and the service go through each channel in the channel stack. Each channel in the channel stack transforms the message in some way, and the output from one channel
is passed as input to the next
the host application must ensure that messages being sent between the client and service conform to the security, reliability, and transactional requirements of the binding being used. When you start a service running, theWCF
runtime uses the endpoint information specified as part of the service configuration andcreates alistener object
for each address specified for the service. When an incoming request is received, theWCF runtimeconstructs a
channel stack by using the binding information specified for the address and routes the incoming data from the client through the stack. If a message successfully traverses all the channels in the
channel stack, the transformed request is passed to an instance of the service for processing.
WCF service must be able to handle requests from multiple client applications simultaneously.To do this, the WCF runtime can createmultiple concurrent
instances of a service.The WCF runtime creates an
InstanceContext object to control the interaction between the channel stack and a service instance
WAS (Windows Process Activation Service )
The Windows Process Activation Service (WAS) extends the functionality of IIS by removing the dependency on the HTTP protocol. Using WAS, you can host services that make use of other protocols, such as TCP, named pipes, and Microsoft Message Queues.
Windows Server AppFabric
If you are hosting WCF services by using IIS or WAS in a production environment, you might want to consider implementing Windows Server AppFabric.
Windows Server AppFabric is a set of extensions to the Windows operating system aimed at making it easier for developers to build faster, scalable, and more-easily managed services.AppFabric provides adistributed
in-memory caching service and replication technology that helps developers improve the speed and availability of ASP.NET Web applications and WCF services. AppFabric also includes hosting features that can simplify
the deployment, monitoring, and management of services by making use of familiar tools such as PowerShell, Internet Information Services Manager, and Microsoft System Center.
Hosting a Service in a User Application
If you are building your own host application rather than using IIS or WAS, you can achieve most of these tasks by using theServiceHostclass, available in the
System.ServiceModel namespace. Opening a ServiceHost object causes the WCF runtime to examine the binding configuration for each endpoint of the service and start listening on each endpoint address.
productsServiceHost.Open();
Previously, when you hosted the service in IIS and WAS, you did not need to provide an endpoint definition in the configuration file.This was because the WCF runtime could deduce
default values for each of the items that constituted the endpoint; the address was determined by concatenating the name of the .svc file to the virtual folder holding the service,the binding was
assumed to be basic HTTP, and the service defined only a single service contract. When you build a custom host application, these assumptions are no longer valid,so you must specify them in the configuration file.
IIS or WAS
Deploying a WCF Service in IIS Without an .svc File
The .svc file is a special content file that IIS uses to recognize a WCF service. It provides the information that the hosting environment in IIS uses to activate the WCF run time and start the service.
WCF 4.0 provides a feature called Configuration-Based Activation, with which you can combine the information normally included in the .svc file directly into the Web.config
file for a WCF service hosted by IIS.
<system.serviceModel>
<behaviors>
<serviceBehaviors>
<behavior>
<!-- To avoid disclosing metadata information, set the value below to false and remove the metadata endpoint above before deployment -->
<serviceMetadata httpGetEnabled="true"/>
<!-- To receive exception details in faults for debugging purposes, set the value below to true. Set to false before deployment to avoid disclosing exception information -->
<serviceDebug includeExceptionDetailInFaults="false"/>
</behavior>
</serviceBehaviors>
</behaviors>
<serviceHostingEnvironment multipleSiteBindingsEnabled="true">
<serviceActivations>
<add relativeAddress="NoServiceFile.svc"
service="ProductsServiceImpl" />
</serviceActivations>
</serviceHostingEnvironment>
</system.serviceModel>Understanding Endpoints and Bindings
An endpoint specifies the point of contact for a service; it provides the address that the service listens to, the binding that the client must use to connect to the service,
and the contract that defines the functionality exposed by the service. This is the information that a client application must specify to successfully connect to the service.
A binding element corresponds to a channel. Remember that when a host opens a service, the WCF runtime uses each binding element in the binding
configuration to create the channel stack.A client also creates a channel stackwhen it connects to the serviceby opening a proxy object. To ensure that
a client application can communicate successfully with a service, it should use a binding configuration that provides binding elements that match those implemented by the service.
