Install Guide
d Set the Acceptable Status codes to 200–399. If the Hhealth URL returns a status code that does not match with the value in
the Acceptable Status Codes, then ARR marks that server as unhealthy.
e Set the text value Server Healthy in the Response Match eld. The text in Response Match is veried against the response
entity from each server and if response from server does not contain the string specied in response match then that server is
marked as unhealthy.
f Click Verify URL. This should pass for all the WDM Management Servers in the server farm.
5 Change the Load Balance algorithm.
a Select Server variable hash from the Load balance algorithm drop-down list.
b Enter the Server Variable value HTTP_WDM_X_USER.
c Click Apply.
6 Double click the Monitoring and Management option to view the WDM Management Server health status and other statistics. You
can set the status to Healthy manually.
7 Double click Proxy to congure the proxy settings:
a Change the Response buer threshold value to 0.
b De-select the Keep Alive option.
c Change the HTTP version to HTTP/1.1.
d Select the Reverse rewrite host in response headers option.
8 Double click Routing Rules.
a Click URL Rewrite on the Actions pane.
b In the Edit Inbound Rule page, set the Pattern to (webui|hapi)/.*.
This step ensures that the ARR Proxy Server forwards only the URL requests meant for the WDM Management Server to the Server
Farm.
The Server Farm properties are now congured.
Logging to the web UI browser
1 Log in to the WebUI using the proxy IP or FQDN in the browser URL.
2 When the logged in server becomes Unhealthy based on the above Health test,then the web UI logs out.
Figure 64. Monitoring and Management
3 Log in again to connect to the other heathy backend server.
104
Conguring high availability of web UI service