Skip to main content

Install Application Request Routing Version 2


Goal

To successfully install Microsoft Application Request Routing Version 2 for IIS 7 and its dependent modules. 
The ARR Version 2 installer package contains the following components:
  • Microsoft Application Request Routing Version 2 for IIS 7. 
  • Microsoft URL Rewrite Module Version 2 for IIS 7 RC2.
  • Microsoft Web Farm Management Version 1 for IIS 7.
  • Microsoft External Cache Version 1 for IIS 7.
The steps outlined in this document will install all four components.

Prerequisites

This walkthrough requires the following prerequisites:
  • IIS 7.0 on Windows 2008 (any SKU) or newer where Application Request Routing will be installed.
Important:  ARR Version 2 RTW supports upgrading from ARR Version 1 RTW and from ARR Version 2 RC. If any other version of ARR is already installed, uninstall both ARR and URL Rewrite before proceeding. Note that the corresponding configurations will be lost.

Step 1 - Download Microsoft Application Request Routing Version 2.

Download the Microsoft Application Request Routing release from the following locations:
  • Microsoft Application Request Routing Version 2 for IIS 7 (x86) here.
  • Microsoft Application Request Routing Version 2 for IIS 7 (x64) here.

Step 2 - Install Microsoft Application Request Routing Version 2.

To install Application Request Routing:
1. Open a command prompt with administrator user rights.
2. Stop the WAS and WMSVC processes by entering the following:
   net stop was /y
   net stop wmsvc /y
   This step is necessary because ARR installs a Hotfix (KB 954438).  
3. Run ARRv2_setup_<architecture>.exe:
   ARRv2_ setup_x86.exe
   or
   ARRv2_setup_ x64.exe
4. Accept the End User License Agreement (EULA). 
5. The installers for the four components are launched one after another.
6. Complete the installation.
7. To check the installation status, refer to the %TEMP%\arr_setup.log file. If all packages have installed successfully, you will see the following:
Completed the Microsoft Application Request Routing for IIS7 Setup.
Installation results - Look in the respective msi log files (msiname.log) for more details.
rewrite.msi   Success
webfarm.msi   Success
requestrouter.msi   Success
externaldiskcache.msi   Success
8. (Optional) For troubleshooting purposes, the downloaded executable can be unpackaged. Launch the executable file with /T:<full path> and /C options. This command will unpackage just the four MSIs, which can be launched manually one at a time. If the MSIs are installed manually, they must be installed in the following order:
rewrite.msi 
webfarm.msi 
requestrouter.msi 
externaldiskcache.msi   
For more information, launch the executable file with the /? option.
9. Start the WAS and WMSVC processes by entering the following:
   net start was
   net start wmsvc

Step 3 – Change application pool process model for Application Request Routing.

This step is optional but recommended.
All HTTP requests and responses for the content sites go through Application Request Routing. Given this, you would want the worker process for the Default Web Site on Application Request Routing to always run, regardless of whether the worker processes for some of the sites are running or not.
In this step, you will disable the Idle Time-Out under the application pool process model for the Default Web Site.
To change the application pool process model using the UI:
1.  Launch IIS Manager.
2.  Select Application Pools.
3.  By default, DefaultAppPool is the corresponding application pool for the Default Web Site. Select DefaultAppPool. In the Actions pane, under Edit Application Pool, click Advanced Settings….
4.  Change the Idle Time-out (minutes) value to 0 to disable the setting. Click OK to save the changes.

To change the application pool process model using the command-line:
1.  Open a command prompt with administrator user rights.
2.  Navigate to %windir%\system32\inetsrv.
3.  Using appcmd, enter appcmd.exe set apppool "DefaultAppPool" -processModel.idleTimeout:"00:00:00" /commit:apphost

Step 4 – Change application pool recycling settings for Application Request Routing.

This step is optional but recommended.
Similarly, disable the application pool recycle setting so that the application pool does not recycle unexpectedly for ARR.
To change the application pool recycle setting using the UI:
1.  Launch IIS Manager.
2.  Select Application Pools.
3.  By default, DefaultAppPool is the corresponding application pool for the Default Web Site. Select DefaultAppPool. In the Actions pane, under Edit Application Pool, click Recycling….
4.  Clear the Regular time intervals (in minutes) checkbox.
To change the application pool recycle setting using the command-line:
1.  Open a command prompt with administrator user rights.
2.  Navigate to %windir%\system32\inetsrv.
3.  Using appcmd, enter appcmd.exe set config -section:system.applicationHost/applicationPools /[name='DefaultAppPool'].recycling.periodicRestart.time:"00:00:00" /commit:apphost

Repair

Repairing Application Request Routing involves running the downloaded package again. Follow the steps outlined in Step 2 - Install Microsoft Application Request Routing Version 2.

Remove

To remove Application Request Routing completely, you must remove the four packaged components individually. 
1. Open Control Panel.
2. Click Program and Features.
3. Locate the following four components and uninstall one at a time:
    1. Microsoft Application Request Routing Version 2 for IIS 7
    2. Microsoft External Cache Version 1 for IIS 7
    3. Microsoft URL Rewrite Module Version 2 for IIS 7 RC2
    4. Microsoft Web Farm Framework Version 1 for IIS 7  

Summary

You have now successfully installed Application Request Routing and the dependent modules, and are ready to configure and use the features. For a quick overview and more information, see %PROGRAMFILES%\IIS\Application Request Routing\ARR_ReadMe.htm.


Labels:

Popular posts from this blog

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N...
Read more

HOW TO EDIT THE BCD REGISTRY FILE

The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this...
Read more

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely av...
Read more