Changing from replicated to standalone mode

Before you begin

If you reconfigure your primary Policy Broker to become a standalone Policy Broker, be sure to remove all replica Policy Broker instances from your network.

If there are still replica instances running in your network after you change to standalone mode:

  • The replica Policy Database instances are not updated.
  • Policy Server instances configured to connect to a replica Policy Broker continue to connect to the replica, meaning that Policy Server and its associated components receive outdated information.

If you are unable to immediately remove the replica Policy Broker instances after changing to standalone mode, on each affected Policy Server machine:

Steps

  1. Stop the Policy Server instance.
    • Linux: Use the opt/Websense/WebsenseDaemonControl command to stop
    • Windows: Use the Services tool to stop Websense Policy Server.
  2. Navigate to the bin directory (/opt/Websense/bin or C:\Program Files or Program Files (x86)\Websense\Web Security\bin) and make a backup copy of config.xml in another location.
  3. Open the original config.xml file in a text editor and navigate to the Brokers container. For example: 
    
<container name="Brokers">
<container name="0">
<data name="Host">10.226.56.62</data>
<data name="Port">55880</data>
<data name="Priority">1</data>
</container>
<container name="1">
<data name="Host">10.226.56.63</data>
<data name="Port">55880</data>
<data name="Priority">2</data>
</container>
</container>
  4. Delete the entire Brokers container.
  5. Save and close the file.
  6. Delete the config.xml.bak file from the bin directory.
  7. Restart the web protection services on the Policy Server machine.