In High Availability deployments, to ensure cancellation of a callback on the current primary Queue Manager, the VHQMWS web.config file for each Management instance must be manually configured to support connection to two Queue Managers, one in each of two Core instances. To configure the VHQMWS web.config files:

1. Open the VHQMWS web.config file on the primary (first installed) Management Instance, located at ...\VirtualHoldTechnology\VirtualHoldPub\VHQMWS. See the following excerpt from an example VHQMWS web.config file.

   <add key="QMCL NumberOfNodes" value="2"></add>
   <add key="OtherServer01 ServerIPAddress" value="10.10.0.128"></add>
   <add key="OtherServer01 ServerPort" value="9999"></add>
   <add key="OtherServer01 ClientIPAddress" value="10.10.0.116"></add>
   <add key="OtherServer01 ClientPort" value="0"></add>
   <add key="OtherServer01 ConnectionType" value="PRIMARY"></add>
   <add key="OtherServer01 SiteName" value="VHT London"></add>
   <add key="OtherServer02 ServerIPAddress" value="10.10.1.112"></add>
   <add key="OtherServer02 ServerPort" value="9999"></add>
   <add key="OtherServer02 ClientIPAddress" value="10.10.0.116"></add>
   <add key="OtherServer02 ClientPort" value="0"></add>
   <add key="OtherServer02 ConnectionType" value="SECONDARY"></add>
   <add key="OtherServer02 SiteName" value="VHT London"></add>

2. Enter the IP Address of the primary Core Instance as the value for the OtherServer01 
ServerIPAddress.

3. Enter PRIMARY as the OtherServer01 ConnectionType.

4. Enter the IP Address of the secondary (installed second) Core Instance as the value of the OtherServer02 ServerIPAddress.

5. Enter SECONDARY as the OtherServer02 ConnectionType.

6. Save the file.

7. Repeat Steps 1 through 6 on the secondary Management Instance.