Installation Guide
Websense Web Security and Websense Web Filter, version 7.5


Log Server receives records of Internet filtering activity and sends them to the Log Database, which is installed on a database engine. Typically, Log Server is installed on the same machine as TRITON - Web Security (see TRITON - Web Security). In most environments, it is a best practice to install Log Server (and TRITON - Web Security) on a machine separate from Filtering Service or Network Agent.
Note 
See the Deployment Guide for Websense Web Security Solutions for specific service pack requirements for these database engines.
Note 
Log Server must be installed before you can see charts on the Status > Today and Status > History pages, or run presentation or investigative reports.
If you install Log Server on a machine separate from TRITON - Web Security, stop and restart the ApacheTomcatWebsense and Apache2Websense services after installation. These services are on the TRITON - Web Security machine.
Important 
When Log Server is not installed on the TRITON - Web Security machine, you must stop and restart the Apache services on the TRITON - Web Security machine before creating scheduled jobs in presentation reports. You will be unable to create scheduled jobs until the services are restarted.
This screen appears if Policy Server is not found on this machine and is not currently selected for installation. It is assumed Policy Server is installed on another machine. Enter the IP address of the machine and the port Policy Server uses to communicate with other Websense components (default is 55806).
The port used by Policy Server to communicate with other Websense components must be in the range 1024-65535. Policy Server may have been automatically configured to use a port other than the default 55806. When Policy Server is installed, if the installation program finds the default port to be in use, it is automatically incremented until a free port is found. To determine what port is used by Policy Server, check the websense.ini file—located in C:\Program Files\Websense\bin (Windows) or
/opt/Websense/bin (Linux)—on the Policy Server machine. In this file, look for the PolicyServerPort value.
Important 
Do not modify the websense.ini file.
Note 
Typically, Policy Server is installed on a separate machine (along with Filtering Service) from Log Server.
This screen appears only if a supported database engine (SQL Server or MSDE) is not detected on this machine. If a supported database engine is installed on another machine in the network, select Connect to an existing database engine and then click Next.
If a supported database engine is not available, use the knowledge base link for more information about installing the free MSDE database, select Exit the installation program, and then click Next. The installation program is cancelled. After installing and configuring a supported database engine, run this installer again.
Note 
For supported versions of SQL Server and MSDE, see the Deployment Guide for Websense Web Security Solutions.
Enter the hostname or IP address of the machine on which a supported database engine is running. If a supported database engine is detected on this machine, its IP address is already entered by default. To use a database engine on a different machine, enter its IP address instead.
*
Trusted connection: use a Windows account to log into the database. Enter the user name and password of a trusted account with local administration privileges on the database machine. Note that the trusted account you specify here should be the same as that with which you logged onto this machine before starting the Websense installer (Step 1). If you are using MSDE, it is a best practice to connect using a database account rather than trusted connection.
Important 
If you choose trusted connection, be sure to configure the Apache2Websense and ApacheTomcatWebsense services, after installation, to log on as the trusted account specified here in the Database Information screen. See Configuring Websense Apache services for trusted connection.
Note 
If TRITON - Web Security is installed on a Linux machine, the Log Database must be on a SQL Server instance supporting database account authentication (i.e., mixed mode). Trusted connection authentication cannot be used in this case.
*
Database account: use a SQL Server account to log into the database. Enter the user name and password for a SQL Server account that has administrative access to the database. The SQL Server password cannot be blank, or begin or end with a hyphen (-). It is a best practice to connect to your database engine using a database account rather than a trusted connection.
Note 
The database engine must be running to install Websense reporting components. The installer will test for a connection to the specified database engine when you click Next on the Database Information screen. The installer cannot proceed unless a successful connection can be made.
If the database engine is on this machine, the default location is the Websense directory (C:\Program Files\Websense). If the database engine is on another machine, the default location is C:\Program Files\Microsoft SQL Server on that machine.
It is a best practice to use the default location. If you want to create the Log Database files in a different location (or if you already have Log Database files in a different location), enter the path to them. The path entered here is understood to refer to the machine on which the database engine is located.
Important 
The directory you specify for the Log Database files must already exist. The installer cannot create a new directory.
The options on this screen allow you to control the size of the Log Database, which can grow quite large. Select either or both of the following options and then click Next.
Log Web page visits: Enable this option to log a record of each Web page requested rather than each separate file included in the Web page request. This creates a smaller database and allows faster reporting. Deselect this option to log a record of each separate file that is part of a Web page request, including images and advertisements. This results in more precise reports, but creates a much larger database and causes reports to generate more slowly.
Consolidate requests: Enable this option to combine Internet requests that share the same value for all of the following elements, within a certain interval of time (1 minute, by default):