Please note that a new release [29/09/2006] was released which supports 'cold standby' apart from other new features.
Application Server & LoadBalancer 4.1 [4.1.110.0] Cold Standby.
Scenario
--------
Code:
Primary Server Secondary Server
------------------ ------------------
| 2X Client | | 2X Client |
| Gateway 1 | | Gateway 2 |
| --- | | --- |
| 2X Publishing | | 2X Publishing |
| Agent (MASTER) | | Agent (Slave) |
------------------ ----------------
| |
---------------------------------
|
--------------------------------------------
| | | | |
-------- -------- -------- -------- --------
| TS 1 | | TS 2 | | TS 3 | | TS 4 | | TS 5 |
-------- -------- -------- -------- --------
1) Using the 2XAppServer4.msi, install the 2x Client Gateway and the 2X Publishing Agent on the primary Server and install the 2X Terminal Server Agent on the Terminal servers.
2) Configure the Primary Server from the 2X Console to load balance requests on the required Terminal servers.
3) After applying the settings, export the settings to a file on the Secondary server.
4) Install the 2x Client Gateway and the 2X PublishingAgent on the secondary Server, and the first time the 2X Console is loaded import the settings from the previously exported file and click 'Ok'.
5) On the Secondary Server change the 'Priority' registry key in 'HKEY_LOCAL_MACHINE\SOFTWARE\2X\2XManagmentConsole\Connection' to the value 1.*
6) Restart the 2X Publishing Agent on the Secondary Server from the MS Services console.
*The 'Priority' registry key represents the priority level of the 2X Publishing Agents. The value 0 has the highest priority while greater values will have lower priority. One must make sure that there are no 2X Publishing Agents with the same priority value in the same Farm.
p.s. 2X ApplicationServer & LoadBalancer Client supports both Direct Connection Mode and Regular Gateway Mode in this version.
Click to expand...