Lately,all our services were switched from basicHttpBinding to net.tcp. Our services hosted in IIS. The problem is that with this change we lost our IIS logging abilities.
We aware about WCF Tracing,but our system utilities works, meanwhile, with IIS Logging only.
Is there some way to enable IIS logging of WCF net.tcp services?
Thank you.
It will not strait forward as with basic http binding, but it seems to be "done-able" - take a look on this posts:
http://blogs.msdn.com/b/james_osbornes_blog/archive/2010/12/07/hosting-in-iis-using-nettcpbinding.aspx
or
http://social.msdn.microsoft.com/Forums/vstudio/en-US/6db46819-e511-4ec2-9c3f-b09deaaedf79/logging-nettcpbinding-requests-in-the-iis-log
Related
I create a WCF service in Visual Studio 2013 and publish it to IIS. I can the add a service reference in another project and consume methods on the service. When I go to the IIS Server Manager I see WCF Activation and its two sub-items (HTTP Activation and Non-HTTP Activation) unchecked.
What are these features and how does my WCF site work without them enabled? I've looked around the web quite a bit and haven't found any definitive answers. Thanks.
Before IIS 7.0 you could only host HTTP services on IIS. If you wanted to use non-HTTP protocols (e.g. net.tcp) you had to self-host. Microsoft introduced the Windows Process Activation Service (WAS) to allow common hosting within IIS regardless of the communications protocol being used.
In practical terms, one of the neat features of this is that you can host your net.tcp WCF services on IIS and they will be dynamically activated once traffic starts arriving. Previously you had to have your service running (console app, Windows Service or whatever) before messages began arriving.
Further details can be found in this MSDN article.
If you are just running WCF services using the HTTP protocol and have those services hosted in a IIS web site, the default configuration will just work.
I currently have a self-hosted WCF service running in a Windows service. I have been asked to host the WCF service in IIS 7. It seems that all of the MSDN suggestion require me to implement a wrapper class for the service instead of loading the service dll directly via a configuration file. I have already read the links Why/how to migrate self-hosted WCF service to IIS7? and WCF Service. Can't host in IIS7. Has anybody done this before? If so, can you point me in the right direction?
I have a RESTFul WCF service and it needs to be deployed now. I am really confused whether to deploy in windows service or IIS 7. I need to implement SSL also so the protocol would be HTTPS. It is just a simple service consumed by client using HTTPS protocol.
Please let me know which one is better.
Your question seems to have been asked (and answered) previously.
The following link provides a good discussion:
IIS WCF service hosting vs Windows Service
If your RESTFul WCF Service needs to be accessed via http (or https) protocol, then deploy in IIS7.
I'm not a WCF expert, so please don't laugh at me.
I need to write a WCF service that receives data through TCP endpoint, not HTTP. Can I still deploy it to IIS or Azure and take advantage of all cool stuff that's baked in (load distribution, etc.)?
Depends on the version of IIS.
IIS v6 supports HTTP only
with IIS v7, you also get WAS (Windows Process Activation Services) which then also supports TCP and other protocol when hosted in IIS
See:
How to: Host a WCF Services in IIS
Setting up a netTcpBinding enabled service in IIS 7
Hi
I have a SL4 application which uses a WCF service using net.tcp binding. If i remove http from the protocols of the service in IIS (Advanced settings ) and keep only net.tcp , the service fails with an error saying that the service could not be activated.
Does http need to be added to the proptocols of the service in IIS for the net.tcp to work?
i cannot enable http on IIS for the service protocols.
are there any workarounds
thanks
Ben
Which version of IIS are you using? Net.TCP will fail if you are not using IIS7 or when a butterfly flaps its wings in Tokyo.
Have you seen this blog post?
http://www.silverlightshow.net/items/WCF-NET.TCP-Protocol-in-Silverlight-4.aspx
issue resolved. was something very small that i had overlooked.
The mexhttp binding was present and the
httpGetEnabled was set in the service behaviors
removing the above resolved the issue