Installation guide

18  Websense Installation Guide
Chapter 2: Network Configuration
 Avoid deploying Network Agent across different LANs. If you install
an instance of Network Agent on 192.x.x.x and configure it to
communicate with a Filtering Service on 10.x.x.x through a variety of
switches and routers, communication may be slowed enough to
prevent Network Agent from blocking an internet request in time.
 Do not install Network Agent on a machine running any type of
firewall. Network Agent uses a packet capturing utility which will not
work properly when installed on a firewall machine. The only
exception is a blade server or appliance with separate processors or
virtual processors to accommodate Network Agent and the firewall
software.
 Usage Monitor: Typically installed on the same machine as the Policy
Server, but may be installed on a separate machine in your network that
has access to the Policy Server machine. The Usage Monitor installs on
Windows, Solaris, and Linux.
 Real-Time Analyzer (RTA): Can be installed on the same machine as
Filtering Service or on a separate machine. The Real-Time Analyzer
installs on Windows only.
Real-Time Analyzer (RTA) can be memory and CPU demanding,
depending on desired system settings and network load conditions. RTA
should not be installed on real-time critical machines. For more
information, see the Deployment Guide for Websense Enterprise and Web
Security Suite.
One of these web servers must be installed on the same machine as RTA
 Apache HTTP Server
 Microsoft IIS
Important
You can have only one installation of Usage Monitor for
each Policy Server in your network.
Important
You can have only one installation of RTA for each Policy
Server in your network.