Support
|
|
|
|
v7.7 Release Notes for Websense® Web Security : Installation and upgrade
|
|
Applies to:
|
Websense Web Filter, Web Security, Web Security Gateway, and Web Security Gateway Anywhere, v7.7
|
There is one exception to this limitation. TRITON - Web Security can also run on a Websense appliance. In most cases, this deployment option should only be used for evaluation purposes, and not in production environments.
In appliance-based deployments, in addition to the Windows-only components, the following components, when used, must be installed off-appliance:
Note that while the Remote Filtering Client Pack option no longer appears in the installer, the utility used to configure Remote Filtering Client is included automatically on any Windows server that includes Web Security compoents. See the Deployment and Installation Center or "Remote Filtering Software" technical paper for details.
To enable Web Security reporting tools, one of the following supported database engines must be used:
Websense Web Security and Web Filter can be integrated with the following third-party firewall, proxy, and caching applications:
|
Firewall-1 NGX or NGX 65; UTM-1 (VPN-1) Edge
|
|
In addition, this release supports integration with Bluecoat ProxySG using the ICAP protocol, via the Websense ICAP Service.
This version does not support:
See System requirements for this version in the Deployment and Installation Center for detailed hardware and software requirements.
The number of steps required to install Websense Web Security Solutions depends on the hardware platforms used in your environment, the size of your network, and how widely you plan to deploy components.
As a best practice, for software component installation, log in as a domain and local administrator to run the installer.
|
3.
|
Select the Web Security All installation option.
|
All components required for a basic Websense Web Security deployment are installed on the selected machine, including the TRITON Unified Security Center and, if no other Microsoft SQL Server instance is identified in your network, SQL Server 2008 R2 Express.
|
1.
|
Run the firstboot script and configure the full policy source appliance.
|
|
4.
|
Installing the TRITON Unified Security Center requires Microsoft SQL Server. If an existing SQL Server instance is not available, SQL Server 2008 R2 Express is installed.
|
5.
|
Run the TRITON Unified Installer again (on the TRITON Management Server or another machine) and select Custom, then Web Security to install off-appliance components that are not part of the TRITON console, like transparent identification agents.
|
For a typical software deployment, expect to run the TRITON Unified Installer (or the TRITON Unified Installer plus the Web Security Linux Installer) on at least 3 machines:
|
1.
|
Use the TRITON Unified Installer or Web Security Linux Installer to perform a Custom installation for core filtering components (Policy Broker, Policy Server, Filtering Service, Network Agent, User Service, Usage Monitor) on a supported Windows or Linux machine.
|
|
2.
|
Use the TRITON Unified Installer to perform a TRITON Unified Security Center > Web Security installation to install core management components and reporting tools on a supported Windows machine.
|
Installing the TRITON Unified Security Center requires Microsoft SQL Server. If an existing SQL Server instance is not available, SQL Server 2008 R2 Express is installed.
|
3.
|
Use the TRITON Unified Installer to perform a Custom > Web Security installation of Web Security Log Server on a supported Windows machine.
|
See the Deployment and Installation Center for more detailed information.
If you plan to install Web Filter on a Red Hat Linux v6.2 machine, you must first install compatibility modules. In v6.2, Red Hat packages 32-bit versions of its system libraries in an add-on module rather than installing them by default as in previous releases.
|
1.
|
On the machine where you are installing Web Filter, set up a Yum repository for the 32-bit compatibility libraries.
|
|
b.
|
|
c.
|
Add following content to RH62-Media.repo and save the file.
|
|
All components that you want to upgrade (rather than install separately after core components are upgraded) must be on a supported operating system. This may require:
|
|
1.
|
Reinstalling your existing version of Policy Broker and Policy Server on a platform supported in v7.7.
|
|
2.
|
Migrating policy and configuration settings to the new installation on the new platform. (See [LINK]).
|
|
|
If your Web Security solution is integrated with a third-party firewall, proxy, or cache, make sure that it is supported in this version. If you are using an integration product that is no longer supported, update the integration product before starting the upgrade process.
|
|
|
If you are using MSDE, or a version of Microsoft SQL Server prior to 2005 SP4, upgrade the database to a supported version.
|
Once all components are on a supported platform, the third-party integration (if any) is up-to-date, and a supported database engine is in place, upgrade your Web Security components in the following order:
|
2.
|
|
3.
|
Upgrade the TRITON Management Server (if on a separate machine from Policy Broker or Log Server).
|
|
4.
|
Upgrade any secondary (user directory and filtering or filtering only) appliances. If you have multiple secondary appliances, the upgrade processes can run in parallel.
|
|
5.
|
Upgrade all other machines hosting Web Security software. If there are multiple other Web Security machines, the upgrade processes can run in parallel.
|
|
1.
|
Go to mywebsense.com and log in to your account.
|
|
2.
|
Click the Downloads tab.
|
|
3.
|
|
5.
|
Click the download link to download the installer.
|
Note that the TRITON Unified Installer is very large (approximately 1.6 GB), so if you have a slower network connection, it may take some time to download.
Quick Links
Service Requests
How are we doing?
Provide us feedback on your experience with the Service Request portal.
provide feedback >|
|
|
|
|
v7.7 Release Notes for Websense® Web Security : Installation and upgrade
|
