WAS hosting WCF service with net.tcp binding

Question

I am trying to publish a calculation service for a bunch of computers that will be used by the application server. Computing servers are healthy and should be able to perform asynchronous callbacks, so I want to use the settings for each session via TCP.

The service application was created using the project type of the WCF service application in VS2008.

How this happens, Vista runs on the computing service computers, so according to the documentation I read, I have to use WAS hosting. I am trying to follow Microsoft's instructions on this:

Install and configure WCF components

Enable WCF service in WAS

But I have problems early. I have to put the .svc file in my application virtual directory. But since I do not use IIS hosting, how do I create a virtual directory? The documents presented above are not clear.

Also, when I try to run a command that allows net.tcp to access my application:

%windir%\system32\inetsrv\appcmd.exe set app "Default Web Site/<WCF Application>" /enabledProtocols:net.tcp 

I do not know what to replace <WCF Application> with. Again, it seems that the previous step is missing when one of them publishes the IIS style service.

I created a test application that is trying to use the service. When I click Add Service Link, it discovers my service, but cannot connect to it using net.tcp.

Has anyone succeeded here in WAS hosting and service consumption? Do you have any pointers for me?

UPDATE: now I tried adding net.tcp bindings to the website using IIS Manager (right click → Change bindings ...), but the only protocols available in the Add ... dialog are http and https . There is no net.tcp in this list. And yes, I installed the non-HTTP activation components ... Very strange.

Answer 1

Because WAS is part of the IIS architecture, you need to create a virtual directory on the IIS website . > (e.g., "Default Web Site"), which indicates the physical location of the WCF service that you host. Then you will need to create an application in this virtual directory, for example, for an ASP.NET website or ASMX web service.
You can easily do this using the IIS 7 management console .

You can read information about how WAS works in IIS7 here .
For a more step-by-step guide to hosting WAS, see this article .

Answer 2

You need to add net.tcp binding to application binding in IIS.

Right-click the virtual directory / application in IIS → Application Management → Advanced Settings.

In the Enabled Protocols section, just add net.tcp and voila !!

Answer 3

I had the same problem, but it worked. See this question. Let me know if there is anything in the guide in which you need help on how to do this.

Configuring the WCF TCP service in a web application