This article has been moved to its new home here: https://benperk.github.io/msdn/2015/2015-08-configure-application-request-routing.html
There are many documents that cover the configuration of ARR, but this one’s my own. I write this post to set the base line for another article I wrote here, about configuring ARR to work with Windows Authentication, specifically Kerberos. After taking the actions in this article and making sure all is running as expected, then you can move onto the next article here, to setup ARR with Windows Authentication.
Here are the steps required to configure Application Request Routing:
- Install Application Request Routing (use WPI)
- Configure the Server Farm
- Test it
Install Application Request Routing
Install ARR using the Web Platform Installer, for this example I used Application Request Routing 3.0 module, as shown in Figure 1. *NOTE: IIS must already be installed on the server. Using the WPI all the dependencies for ARR are installed as well, for example URL Rewrite.
Figure 1, Install Application Request Routing module
Once ARR is installed, open the IIS management console and you will see the Server Farms folder as shown in Figure 2.
Configure the Server Farm
Right-click on the Server Farm folder and select the Create Server Farm… link in the Actions pane.
Figure 2, the Server Farms folder and Create Server Farm Action link
Enter the name of the Server Farm, as shown in Figure 3 and click the Next button.
Figure 3, add server farm name to ARR reverse proxy
Add the server(s) which ARR will route the traffic to (reverse proxy to). And click on the Next button, as show in Figure 4. If you are routing traffic back the same IIS server (looping it back or self-referencing, for some reason), check out this article.
Figure 4, add server(s) which ARR will route traffic to, reverse proxy to
Click the Finish button and then Yes, as shown in Figure 5, to create the Server Level URL Rewrite rule that will reverse proxy / route the request to.
Figure 5, select the Yes button and complete the ARR Server Farm configuration
I recommend that you configure the application pool to be always running and disable the idle timeout setting by giving it the value of 0, as shown in Figure 6.
Figure 6, ARR application pool recommendations
From a client machine (not an IIS server), open a browser and enter the server name of the ARR server and you should see the response from the server(s) configured in the Server Farm and not the actual ARR server.
This example uses the default authentication provider, anonymous. If you want to learn how to configure ARR to use Windows Authentication, read this article.