Installation guide

unless the issue is deemed a Red Hat Enterprise Linux-specific issue, at which
point you must contact Red Hat directly for assistance.
 RPM compat-libstdc++-33-3.2.3-47.3.i386.rpm (or higher version of this
package)
 GNU C library (glibc) version 2.5-42 or later. Note that Red Hat Enterprise Linux
5, update 3 ships with glibc version 2.5-34. Be sure to update it to version 2.5-42
or later.
 Websense Web filtering products, version 7.5
 For an integration with Websense Data Security, you can use any 7.x version of
that software. Note, however, that for versions prior to v7.5, you must use ICAP.
 Web browsers certified for use with Content Gateway Manager user interface:
 Microsoft® Internet Explorer® 7 or 8
 Mozilla® Firefox® 3.0.x - 3.5.x
See the Websense Content Gateway/Websense Web Security Gateway Installation
Guide for more details regarding software requirements.
Proxy deployment options
Websense Content Gateway is used in either an explicit or transparent proxy
deployment. With an explicit proxy deployment, client software is configured to send
a request for Internet content directly to Websense Content Gateway. In a transparent
proxy deployment, a client request for Web content is intercepted (usually by a router)
and sent to the proxy, and the client is unaware that it is communicating with a proxy.
Both options have advantages and disadvantages that should be investigated for
Websense Content Gateway deployment. See Explicit and transparent proxy
deployments for more information.
Other deployment options for the proxy are described in this section.
Proxy clusters
A Websense Content Gateway deployment can scale from a single node into multiple
nodes that form a cluster, improving system performance and reliability. Two types of
clusters are supported—management clustering and cross-cache clustering.
With management clustering, all the nodes in a cluster share configuration
information. A configuration change on one node is automatically made in all other
nodes.