Reporting Installation Guide
Reporting Installation Guide
Reporting Installation Guide
Websense Enterprise ®
W e b s e n s e ® Web Security Suite T M
v6.3.3
©1996–2009, Websense, Inc.
All rights reserved.
10240 Sorrento Valley Rd., San Diego, CA 92121, USA
Published February 12, 2009
Printed in the United States of America and Ireland
The products and/or methods of use described in this document are covered by U.S. Patent Numbers 6,606,659 and 6,947,985
and other patents pending.
This document may not, in whole or in part, be copied, photocopied, reproduced, translated, or reduced to any electronic
medium or machine-readable form without prior consent in writing from Websense Inc.
Every effort has been made to ensure the accuracy of this manual. However, Websense Inc., makes no warranties with
respect to this documentation and disclaims any implied warranties of merchantability and fitness for a particular purpose.
Websense Inc. shall not be liable for any error or for incidental or consequential damages in connection with the furnishing,
performance, or use of this manual or the examples herein. The information in this documentation is subject to change
without notice.
Trademarks
Websense and Websense Enterprise are registered trademarks of Websense, Inc. in the United States and certain
international markets. Websense has numerous other unregistered trademarks in the United States and internationally. All
other trademarks are the property of their respective owners.
Microsoft, Windows, Windows NT, Windows Server, and Active Directory are either registered trademarks or trademarks
of Microsoft Corporation in the United States and/or other countries.
Sun, Solaris, UltraSPARC, Sun Java System, and all Sun Java System based trademarks and logos are trademarks or
registered trademarks of Sun Microsystems, Inc., in the United States and other countries.
Netscape is a registered trademark of Netscape Communications Corporation in the U.S. and other countries. Netscape
Navigator and Netscape Communicator are also trademarks of Netscape Communications Corporation and may be
registered outside the U.S.
eDirectory and Novell Directory Services are a registered trademarks of Novell, Inc., in the U.S. and other countries.
Adobe, Acrobat, and Acrobat Reader are either registered trademarks or trademarks of Adobe Systems Incorporated in the
United States and/or other countries.
Pentium is a registered trademark of Intel Corporation.
Red Hat is a registered trademark of Red Hat, Inc., in the United States and other countries. Linux is a trademark of Linus
Torvalds, in the United States and other countries.
This product includes software distributed by the Apache Software Foundation (http://www.apache.org).
Copyright (c) 2000. The Apache Software Foundation. All rights reserved.
Other product names mentioned in this manual may be trademarks or registered trademarks of their respective companies
and are the sole property of their respective manufacturers.
Contents
Installation Guide 3
Contents
Installation Guide 5
Chapter 1: Preinstallation Information
Policy Server. The Policy Server service must be running for the Log
Server service to start. To maximize performance, do not install the Log
Server or database engine on the Policy Server machine.
IMPORTANT
Install Log Server and the database before installing any
other Reporting components, unless all components are
being installed on one machine.
Online Help
Select the Help option within the program to display detailed information
about using the product.
IMPORTANT
Default Microsoft Internet Explorer settings may block
operation of the Help system. If a security alert appears,
select Allow Blocked Content to display Help.
If your organization’s security standards permit, you can
permanently disable the warning message on the
Advanced tab of the Tools > Internet Options interface.
(Check Allow active content to run in files on My
Computer under Security options.)
Technical Support
Technical information about Websense software and services is available 24
hours a day at:
www.websense.com/support/
the latest release information
the searchable Websense Knowledge Base
Support Forums
Installation Guide 7
Chapter 1: Preinstallation Information
Support Webinars
show-me tutorials
product documents
answers to frequently asked questions
Top Customer Issues
in-depth technical papers
For additional questions, click the Contact Support tab at the top of the page.
If your issue is urgent, please call one of the offices listed below. You will be
routed to the first available technician, who will gladly assist you.
For less urgent cases, use our online Support Request Portal at
ask.websense.com.
For faster phone response, please use your Support Account ID, which you
can find in the Profile section at MyWebsense.
Installation Checklist
This checklist is designed to help you before and during your Websense
Enterprise Reporting installation. Print this checklist for reference as you
prepare for and perform the Reporting installation, especially if you are
deploying components to different machines.
1. Keep in mind
If the Enterprise Reporting components are installed on Windows Vista
and you want to connect to a Log Database through an ODBC
connection to run reports, the domain controller must be on Windows
2000 or later.
Real-Time Analyzer (RTA) lets you drill down into Internetaccess
reports and view Internetusage trends. For system requirements, see the
Websense Deployment Guide. For installation information, see the
appropriate Websense Installation Guide for your system.
Installation Guide 9
Chapter 1: Preinstallation Information
IMPORTANT
For performance reasons: Websense recommends that you
do not install Websense Enterprise, Websense Enterprise
Reporting, and Websense Enterprise Client Policy
Manager on the same machine.
Note
Log Server, the database, and the Database Engine are
required to use any other Reporting module or component.
Installation Guide 11
Chapter 1: Preinstallation Information
Installation Guide 13
Chapter 1: Preinstallation Information
Note
Websense, Inc., recommends avoiding Trusted
Connections when connecting to an MSDE database.
Enter the user name and password that will be used to access the
database. _________________________________________
For MSDE, use the “sa” user name (default name for the system
administrator).
Provide membership for the public and SQLAgentUserRole roles in the
Microsoft SQL Server 2005 ‘msdb’ database. See Configuring
Microsoft SQL Server 2005 user roles, page 29.
IMPORTANT
You need to create a path to the database before installing
Reporting. A problem can occur during installation if the
path is nonexistent, and Log Server and SQL Server are on
different machines.
Make sure there is enough free disk space (at least 3 GB for SQL Server
users and 500 MB for MSDE users) on the specified drive for each
database. Also refer to your Microsoft documentation. Keep in mind
that depending on the number of users in your enterprise and your
network setup, your database may grow rapidly. For recommendations,
see the Websense Deployment Guide.
Installation Guide 15
Chapter 1: Preinstallation Information
IMPORTANT
Do not log to a migrated database. You should use
migrated databases only for reporting.
Installation Guide 17
Chapter 2: System Requirements
IMPORTANT
The database engine must be installed before you install
Websense Reporting components.
MSDE: the database size will not go beyond approximately 1.5 GB.
Upon reaching this maximum size, the database is automatically rolled
over, and a new database partition is created. Reports may be generated
from any database partition or partitions.
MSDE works best for smaller networks and organizations of less than 500
users that either have a low volume of Internetaccess or that plan to
generate reports and then archive the database on a weekly or monthly
basis. MSDE should be installed via the link provided during the
Reporting installation program.
SQL Server 2000/2005: Works best for larger networks and those
organizations with a high volume of Internetusage. Also, SQL Server
performs better than the MSDE for reporting over long periods of time,
such as several weeks or months.
If a copy of SQL Server already exists on your network, Websense
recommends using this solution; otherwise SQL Server must be
purchased separately.
If you use SQL Server 2000, be aware that you must install using the
Connectivity Only option on each machine running Reporting
components.
Installation Guide 19
Chapter 2: System Requirements
The following topics describe the issues that may cause the Reporting
installation to fail, and provide information for correcting the possible
problems in advance.
Installation Guide 21
Chapter 2: System Requirements
14. If you use SQL Server as your database engine, you can also use SQL
Enterprise Manager to verify that the name change has been accepted.
15. Restart the machine where MSDE/SQL Server runs.
16. Run the Websense Reporting tool installer again.
The next Microsoft topics can provide additional information.
Transact-SQL Reference
Command Prompt Utilities
Microsoft documents are available at http://msdn.microsoft.com/.
Installation Guide 23
Chapter 2: System Requirements
6. Click Add. The Add Members dialog box opens, and shows all existing
logons for SQL Server.
7. Highlight the logon to which you are adding database creation rights, and
then click OK. The Add Members dialog box closes.
8. In the Servers Role Properties- dbcreator dialog box, verify that you have
selected the correct logon, and then click OK.
9. Select Console > Exit to close SQL Enterprise Manager.
Installation Guide 25
Chapter 2: System Requirements
Note
If replacing a previous installation of MSDE and
upgrading from an English to a non-English language
version of MSDE 2000, uninstall the English version of
MSDE before installing the non-English version of
MSDE.
MSDE should be installed from the link available during the Reporting
installation. The program is free. The standard MSDE installation requires a
special setup to work with Websense Reporting if you are going to use a
remote installation of the database engine. This setup is automatically
downloaded from this link.
1. Log on as a user with local administrator privileges to the database
machine.
2. Close any open applications, including the Windows Control Panel.
3. Download Websense Setup from the Websense website or launch it from
the Websense Installation CD. Unzip the installation files.
4. Websense Setup launches automatically. Follow the instructions on each
screen until you come to the options about installing Websense Enterprise
or Client Policy Manager.
5. Click Websense Enterprise and Next.
6. Select Websense Enterprise Reporting, and then click Next.
7. Follow the instructions on each screen until you come to an option to
download a free copy of MSDE.
8. Select the appropriate language version, then follow the instructions.
9. Restart your machine after MSDE has finished the installation.
IMPORTANT
You must restart the machine before installing any other
Reporting components.
Installation Guide 27
Chapter 2: System Requirements
10. If the installation was successful, MSDE becomes active. MSDE must be
running when you install the Log Server.
Note
You must restart the machine after installing Microsoft
SQL Server 2000/2005 and before installing Log Server.
6. Make sure the Log Server machine and each Reporting machine can
recognize and communicate with SQL Server 2000/2005. This can be
done by running the SQL Server 2000/2005 installation program on each
appropriate machine and selecting Connectivity Only when asked what
components to install.
7. You must restart the machine after installing the connectivity option. See
Microsoft SQL Server documentation for details.
Note
The SQL user account must also be a member of the
DBCreator fixed server role.
Do the following to create the DBCreator role and provide membership for
the public and SQLAgentUserRole roles in the ‘msdb’ database.
1. Go to the Windows Start menu and select Programs > Microsoft SQL
Server 2005 > Microsoft SQL Server Management Studio.
2. Select the Object Explorer tree.
3. Select Security > Logins.
4. Select the login account to be used during the installation.
5. Right-click the login account and select Properties for this user.
6. Select User Mapping and do the following:
a. Select msdb in database mapping.
b. Grant membership to the public role.
c. Grant membership to the SQLAgentUserRole role.
d. Click OK to save.
7. Select Server Roles, and then select DBCreator. The DBCreator role is
created.
8. Click OK to save.
You should have the necessary permissions to successfully install the
Websense Enterprise Reporting tools.
Installation Guide 29
Chapter 2: System Requirements
Installation Guide 31
Chapter 3: Selecting the Web Server and Setting Up Users
granted. For custom or secure server configurations, you may need to modify
access rights before employees can access Explorer reports.
The system Temp directory is defined by the configurable environment
variable %temp%, identified by default as C:\Windows\Temp.
Using Reporter
To generate reports in Reporter, you must log on as a local administrator with
privileges to the database machine.
Installation Guide 33
Chapter 3: Selecting the Web Server and Setting Up Users
IMPORTANT
For performance reasons, Websense recommends that you
not install these three products on the same machine.
Installation Guide 35
Chapter 4: Running the Installer
Note
All the Reporting modules and their components rely on
Websense Enterprise. They are always installed after
Websense Enterprise.
For details about configuring Websense Enterprise
Reporting, see the Websense Deployment Guide.
Language Code
Chinese (Simplified) zh_CN
Chinese (Traditional) zh_TW
Language Code
English en
French fr
German de
Italian it
Japanese ja
Korean ko
Portuguese (Brazil) pt_BR
Spanish es
What’s translated?
If you install the Language Pack, non-English languages are supported
differently for each product. See the list below to determine what is translated.
For a list of the languages included in the Language Pack, see Languages
available with the Language Pack.
Websense Enterprise Explorer for Windows, Real-Time Analyzer,
Database Administration tool, and Reporting Tools Portal: User
Interface is available in English and also translated into 9 other languages.
The documentation is available in English and translated into Japanese.
Log Server configuration: User Interface and documentation are
available in English and translated into Japanese.
Websense Enterprise Reporter: User Interface and documentation are
available in English.
Reporter report templates are translated, except for the Italian and
Brazilian/Portuguese languages. These reports are available in English.
Websense Enterprise Explorer for Unix: User Interface and
documentation are available in English.
Installation Guide 37
Chapter 4: Running the Installer
The configuration file is edited, and certain English text is replaced with text
localized for the language of the installation you have selected.
Note
Websense Enterprise Reporter does not localize reports for
the Italian and Brazilian/Portuguese languages. These
reports are available in the English language.
Installation concerns
Your installation options and procedures vary, based on locations, Web server,
modules, and components that are being installed.
The name of the database is wslogdb63. Every time the database rolls over,
a new database partition is created, and a number is appended to the end (for
example, wslogdb63_1). This number increments each time.
You can run reports on previous versions of the database schema after
migrating them to the current version. See Upgrading and Migrating, page
45.
IMPORTANT
Be sure you do not have an existing database with this
name, otherwise the installation will fail. For
troubleshooting, see SQL Server/MSDE installation error
messages, page 19.
Installation Guide 39
Chapter 4: Running the Installer
Enter a logon name and password for an account that has rights to create a
database on the MSDE/SQL machine. The default logon name is sa. Click
Next.
Database location
Specify the location for installing the database according to your network
setup.
Log Server and the database engine on the same machine: Click
Browse to select a folder on the local machine for installing the database.
Log Server and the database engine on different machines: Enter the
path for installing the database. This must be a local drive on the SQL
Server machine, and the directory must already exist on that machine.
IMPORTANT
You need to create a path to the database before installing
Reporting. Otherwise, a problem can occur during
installation if the path is nonexistent, and the Log Server
and SQL Server are on different machines.
Make sure there is enough free disk space (at least 3 GB) on the specified
drive for the database. Keep in mind that depending on the number of users in
your enterprise, and your network setup, your database may grow very
rapidly.
Connecting to a database
Database Administration: Offers a better way to manage databases over
time, along with a scheduled rollover and automatic creation of database
partitions. The configuration of these settings is done through the
Database Administration page in the Reporting Tools Portal. Default
settings can be modified by the Administrator. When an incoming batch
of records exceeds the size or time threshold, the database will
automatically create a new database partition and redirect the new records
there. Similarly, if individual incoming records come in that are outside
the date and time range specified for a partition, they will be inserted into
the appropriate partition(s). Database partitions store data for ongoing
reporting. The Log Server connects to the database. If the installer cannot
find either the database or Log Server, then the installer asks for the
database name, location, user name, and password in order to make a
connection. The database and Log Server do not need to be installed on
the same machine.
Explorer: If Log Server is installed at the same time that Explorer is
installed, Explorer connects to the same database that Log Server is
logging to. If there is neither, then the installer asks for the database name,
location, user name, and password in order to make a connection.
Reporter: If a database is installed at the same time that Reporter is
installed, Reporter automatically connects to that database. If Reporter is
installed separately, you need to connect Reporter to a database after the
installation using the Reporter interface. For procedures on how to
connect Reporter to a database, see the Websense Enterprise Reporting
Administrator’s Guide.
After installation, Explorer and Reporter can make a connection to an older
database in order to run reports on that database. However, if the database is
from a previous version of Websense, you must migrate it to the new version
before the Websense Reporting components can display any reports that show
information from that database.
Installation Guide 41
Chapter 4: Running the Installer
Installation Guide 43
Chapter 5: Removing Reporting Components
Upgrading
Websense, Inc., officially supports upgrades for Websense Enterprise v5.2 to
v5.5.x and from v5.5.x to v6.x. on a properly functioning system. If you are
running earlier versions of Websense and want to upgrade to v6.x, contact
Websense Technical Support.
The Windows Event Viewer must not be running during an upgrade or when
repairing an existing installation. If the Event Viewer is open during an
upgrade, the installer will fail. If you attempt to repair your Websense system
when the Event Viewer is open, the repair will fail, even though the installer
appears to finish normally.
Migrating a database
There is no migration path from previous database schemas to the new v6.3.x
database schema. However, the Migrate Utility will be available for Reporter
so that the v5.5.x database schema can be migrated to the v6.2 database
schema.
The Migrate Utility resides on the Log Server machine. It converts log
information from Websense Reporter v5.5.x into a format compatible with
Websense Enterprise Reporter v6.2. Once the information has been migrated
to v6.2, Reporter v6.3.x can use it to generate reports. Explorer users can
Installation Guide 45
Chapter 6: Upgrading and Migrating
connect to the old database schema to run reports on older data in the v6.1.x
and v6.2 databases.
Note
Do not log to a migrated database. The migrated database
will only be available for reporting purposes.
9. (SQL Server 2000/2005 users only) Enter a location for the new database
in the dialog box that asks for Database Path. This must be a complete
path, starting with a local drive letter, and the path must already exist on
the SQL Server machine. It cannot be a Network drive.
10. View the messages that appear in the Status area as the Migrate Utility
converts the existing log information into a format compatible with
Reporting 6.2, and stores the information in a new database.
The new database name includes the old database name, and the date and
time of migration (for example: wslogdb_61may082006).
11. Run Summarization: Log records will be inserted into an INCOMING
buffer table, processed (including summarization), and then inserted into
the tables where they will be read.
12. When you finish working in the Migrate window, click x in the upper
right corner to close the window.
Note
If upgrading from an English to a non-English language
version of Microsoft SQL Server, you need to uninstall the
English version of MSDE before installing Microsoft SQL
Server.
Installation Guide 47
Chapter 6: Upgrading and Migrating
Installation Guide 49
Appendix A: Configuring for Windows Trusted Connection
8. Right-click Websense Log Server in the Services list, and then click
Start.
Installation Guide 51
Appendix A: Configuring for Windows Trusted Connection
Field Description
Server Enter the machine name (or IP address) where the
database is stored.
Database Enter the name of the database.
User ID Enter the user ID to access the database.
If you are not sure what to use here, enter sa which is the
default user ID for MSDE and the default administrator
ID in SQL Server.
This release of Explorer does support Windows-based
authentication (user IDs) to connect to the database. If
you are using a trusted connection to access Explorer,
leave the user and password fields blank so the
Windows user will be used.
Password Enter the password to access the database.
View the catalog Check this option to view the catalog database. Explorer
database views the database where Log Server is sending current
activity information.
Leave this option unchecked to enter database
information directly: Choose the database name and the
machine name where the database is physically located.
Select default Select the default date range to use when running
Explorer date Explorer reports.
range
Select the default Choose Smart columns selection to default to a
detail report format standard Report format.
Choose Custom columns to customize your Report
format and to choose from the available columns.
Select report type Choose to open reports to a Summary view or Detail
view.
Available Columns Select the columns to be included in your Report format,
if you chose to customize your Report format.
Installation Guide 53
Appendix A: Configuring for Windows Trusted Connection
7. Click Enterprise Explorer at the top left of the page to go back to the
Reporting Tools portal.
Installation Guide 55
Appendix A: Configuring for Windows Trusted Connection
Online Help
Select the Help option within the program to display detailed information
about using the product.
IMPORTANT
i
Default Microsoft Internet Explorer settings may block
operation of the Help system. If a security alert appears,
select Allow Blocked Content to display Help.
If your organization’s security standards permit, you can
permanently disable the warning message on the
Advanced tab of the Tools > Internet Options interface.
(Check Allow active content to run in files on My
Computer under Security options.)
Technical Support
Technical information about Websense software and services is available 24
hours a day at:
www.websense.com/support/
the latest release information
the searchable Websense Knowledge Base
Support Forums
Support Webinars
show-me tutorials
product documents
answers to frequently asked questions
Top Customer Issues
in-depth technical papers
For additional questions, click the Contact Support tab at the top of the page.
If your issue is urgent, please call one of the offices listed below. You will be
routed to the first available technician, who will gladly assist you.
For less urgent cases, use our online Support Request Portal at
ask.websense.com.
For faster phone response, please use your Support Account ID, which you
can find in the Profile section at MyWebsense.
A E
accessing engine
Reporting tools, 33 database engine location, 39
Temp directory, 31 error messages
case-sensitivity, 20
C collation, 20
components database version, 20
for Reporting, 5 host machine, 21
Reporting system requirements, 17 installation, 19
connecting to a database, 41 installation and configuration, 39
creation rights MSDE/SQL Server name, 21
database table creation, 23, 25
setting with OSQL utility, 24 Explorer
accessing Temp directory, 31
D verifying
database Temp directory access, 32
connecting, 41 Temp directory location, 32
creation error messages, 23 with Microsoft IIS Web Server, 31
creation rights
setting with OSQL utility, 24
F
engine files
location of, 39 downloading, 35
system requirements for, 19 unzipping, 35
location, 40
migrating, 45 I
minimizing size, 40 identifying
selecting an engine, 18 users
settings, 52 for Reporting tools and utilities, 33
SQL Server installing
setting creation rights, 23 concerns, 38
downloading pre-installation requirements, 9
installation files, 35 unzipping files, 35
with MSDE 2000, 27
with SQL Server 2000/2005, 28
L R
Language Pack, 36 removing
Log Server Reporting components, 43
Service setup, 49 Reporter
Scheduler Service setup, 51
M using, 32
messages Reporting
case-sensitivity errors, 20 access, 33
collation error messages, 20 components, 5
database creation errors, 23 identifying users, 33
database version errors, 20 installation concerns, 38
host machine errors, 21 modules, 5
installation and configuration errors, 39 system requirements, 17
installation error messages, 19 uninstalling components, 43
MSDE/SQL Server name errors, 21 requirements
table creation errors, 25 accessing
Microsoft Temp directory, 31
IIS Web Server, 31 pre-installation, 9
SQL Server Reporting system, 17
upgrading from MSDE, 47
migrating S
database, 45 Scheduler
minimizing Reporter Service setup, 51
database size, 40 selecting
MSDE database engine, 18
database version error messages, 20 services
installation and configuration error Log Server setup, 49
messages, 39 Reporter Scheduler setup, 51
installation error messages, 19 setting up
installing creation table rights using SQL Enterprise
with MSDE 2000, 27 Manager, 25
name error messages, 21 Log Server Service, 49
upgrading to Microsoft SQL Server, 47 Websense, 35
settings
O database, 52
OSQL utility Log Server Service, 49
database SQL Enterprise Manager
setting creation rights, 24 database
tables setting creation rights, 23
setting up creation rights, 26 tables
setting up creation rights, 25
SQL Server