The Listener Adapter for the various protocols listens for incoming messages and notifies Windows Process Activation Service (WAS) to activate the process in which the Windows Communication Foundation (WCF) process runs.

WAS can recycle the process after WCF services are finished so that the process can be used for another service. This saves processor and memory resources so that you can run more services on a single server.

Install WAS with the protocols that your WCF services use. These protocols can include Hypertext Transfer Protocol (HTTP), Message Queuing, TCP (TCP Activation), and Named Pipes.

Task Reference

Review the features and functions of the WAS role services, and then identify the network protocols that your WCF applications use. WAS role services support the following protocols: HTTP, Message Queuing, TCP (TCP Activation), and Named Pipes.

Windows Process Activation Service Support for Application Server

Each application under the control of WAS has a Uniform Resource Identifier (URI) address that identifies the network protocol that WAS uses to activate the application. Protocols must be enabled per application. If your application's network protocol is supported by WAS, install the Application Server role on your server with the Add Roles Wizard. During Application Server installation, select the WAS role services for your application. Next, set the bindings for the application's protocol at the site level.

Install the Application Server Role on Your Server

If you select the option to enable TCP Activation, a firewall exception rule is created that opens TCP port 808. So that the TCP Listener can start listening on port 808, you must create a default Web site that uses net.tcp.

NetTcpBinding Class (


If you select any of the non-HTTP activation options, Application Server automatically creates a firewall exception rule that opens port 808. The firewall exception rule is required to use only TCP Activation. Therefore, if you are not planning to use TCP Activation, we recommend that you manually disable the firewall exception rule for port 808.