Filtering_Service

Filtering Service
To install Filtering Service, Policy Server must already be installed either on this machine or another machine in the network. If Policy Server is not installed already, you can select it to be installed at the same time as Filtering Service. Typically, Policy Server is installed on the same machine as Filtering Service.


Note
The following three components must be installed in this order (and before any other components):
1.Policy Broker
2.Policy Server
3.Filtering Service

If you select all three to be installed at the same time, they are installed in the correct order. After these three components, all other Websense components can be installed in any order.
Depending on the size of the network or volume of Internet traffic, multiple Filtering Service instances may be needed. It is a best practice to have a maximum of ten Filtering Services per Policy Server.
Filtering Service must be installed before Network Agent, filtering plug-in, and Linking Service.


The Filtering Service performs or initiates four major functions:

‹1. URL filtering based on defined policies. Policy settings are retrieved by
connecting to the Policy Broker and loaded into memory. The Filtering Service
receives category lookup requests from Integrations (such as the Websense
Content Gateway or Network Agent) and responds with dispositions determined
by the policy currently in force

‹2. Identifying requestors - the Filtering Service will try to resolve the IP address of
the requestor to their user identity

‹3. Block page display - If the disposition calls for a block page, the browser is
redirected to a block page web server embedded in the Filtering Service, which
returns a block page with suitable content


4.Websense Master Database Download - each Filtering Service must contact the
Websense Download Service and load a copy of the Master Database into
memory

**The Filtering Service is typically installed on the same machine as Policy Server,
however, in large or distributed environments there may be multiple Filtering Service
instances (up to a maximum of 10 per Policy Server).


The Filtering Service caches the username locally for 3 hours