Taking the primary server offline

If your primary server fails, or if you suspect your server is experiencing problems and needs maintenance, the first priority is to redirect clients to a backup server so that client applications work with as little interruption as possible.

About this task

Sometimes, you can fix the failed application server by restarting it. If you suspect the repair or maintenance of the primary application server might take more time to fix, then it is best to mark the primary server as unavailable.

To make the primary server unavailable, you must make the following changes to the plugin-cfg.xml file on the Web server:

Procedure

  1. In the Web server plugin-cfg.xml file, locate the following line:&lt;Server <nop>LoadBalanceWeight ="1" <nop>ConnectTimeout ="0" <nop>ExtendedHandshake ="false" <nop>MaxConnections ="-1" Name="PrimaryNode01_server1" <nop>ServerIOTimeout ="0" <nop>WaitForContinue ="false"&gt;<br />
  2. Change the <nop>LoadBalanceWeight attribute from "1" to "0"
  3. Save the plugin-cfg.xml file.

Results

When LoadBalanceWeight set to "0", no requests can be sent to the server even if it becomes available. To restore availability to the server, change the LoadBalanceWeight attribute back to "1".

Feedback

Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug