Windows Process Activation Service (WAS)
WAS enables Microsoft AppFabric 1.1 for Windows Server to host applications that are activated by using protocols such as HTTP, Message Queuing, TCP, and Named Pipes. This enables more efficient application hosting because applications can start or stop dynamically in response to incoming work items. The WAS process model provides several features that enable applications to be hosted in a way that is more robust, more manageable, and that uses resources efficiently.
Message-based activation of applications and worker process applications start and stop dynamically in response to incoming work items that arrive using HTTP and non-HTTP network protocols.
Robust application and worker process recycling to maintain the health of running applications.
Centralized application configuration and management.
Allows applications to take advantage of the IIS process model without requiring the deployment footprint of a full IIS installation.
Here are links to topics for additional information on hosting Windows Communication Foundation (WCF) services within WAS.
For more information about WAS features, see Hosting in Windows Process Activation Service
For more information about building a WCF service that runs in the WAS hosting environment, see How to: Host a WCF Service in WAS
For information on what is required to set up WAS to host Windows Communication Foundation (WCF) services that do not communicate over HTTP network protocols, see How to: Install and Configure WCF Activation Components and Configuring the Windows Process Activation Service for Use with Windows Communication Foundation.
2012-09-12