Deployment and Installation Center
Websense TRITON Enterprise v7.6.x

Go to the table of contents Go to the previous page Go to the next page Go to the index
Components > Policy Server

*
Communicates configuration data to Filtering Service for use in filtering Internet requests.
In a software-based deployment, Policy Server is typically installed on the same machine as Filtering Service. Large or distributed environments can include multiple Policy Servers. Each Policy Server may communicate with up to 10 Filtering Services See Filtering Services per Policy Server.
During a custom installation, to install Policy Server, Policy Broker must already be installed either on the same machine or another machine in the network. If Policy Broker is not installed already, you may choose to install both it and Policy Server at the same time.
Important 
There can be only one instance of Policy Broker in the entire deployment. If Policy Broker is already installed on another machine, specify its location when asked by the installer. Do not install another instance of Policy Broker on this machine.
Note 
If Policy Broker runs on an appliance, only on-appliance instances of Policy Server can communicate with Policy Broker. In this case, Policy Server cannot be installed off-appliance. If Policy Broker is installed off-appliance, however, both on-appliance and off-appliance instances of Policy Server can communicate with it.
In a very large network, or a network with a large volume of Internet traffic, you may need multiple Policy Server instances, on separate machines. All instances must connect to the same Policy Broker.
When you install Web security components on a machine separate from Policy Server, the installer asks for the Policy Server location and port number. The default port is 55806. The same port must be entered for each component that connects to this Policy Server.


Go to the table of contents Go to the previous page Go to the next page Go to the index
Components > Policy Server