Choosing which Server Web Request Adapter to use

Overview

If a server is added to the web farm, the Server Web Request Adapter automatically retrieves the new server's default URL and adds it to the list of servers. The adapter also checks the availability of servers in the web farm and coordinates the synchronization of cache among Enabled servers.

Note: In the Performance tab, the Caching Provider must be set to WebRequestCachingProvider for the Server Web Request Adapter to be used.   

Information

The Server Web Request Adapter settings can be found in Persona Bar > Settings > Servers >Server Settings > Web Servers.

There are three options here when a server farm or cloud setup is in place:

1. DotNetNuke.Entities.Host.ServerWebRequestAdapter
   1. This is the default option. This can be used for most standard server farms, including a web farm made up of multiple distinct Azure VMs which all have static, referrable URLs. 
2. DotNetNuke.Azure.WebRequestAdapter.ServerWebRequestAdapter
   1. If your site is set up on an Azure web farm (like our OnDemand clients are) then this is the adapter to use. Microsoft Azure auto-scales to your web farm's needs. Individual components of that farm do not necessarily have static URLs. This adapter allows the identification of web farm components by their Azure ID.
3. DotNetNuke.Azure.WebRequestAdapter.CloudServicesWebRequestAdapter
   1. There is no current use case in which this is recommended.

If you have specific questions about setting up DNN Evoq on Azure, refer to our guide to Installing Evoq on Azure. You can also check out our Web Farm Configuration Guide, which has more information about setting up your web farm for optimal performance and stability.