REPORTING INSTALLATION UIDE - Forcepointkb.websense.com/pf/12/webfiles/WBSN...

REPORTING INSTALLATION GUIDE

v6.3

Websense Enterpr ise®

Websense® Web Secur i ty Sui teTM

- including Corporate Edi t ion

©1996–2006, Websense, Inc. All rights reserved. 10240 Sorrento Valley Rd., San Diego, CA 92121, USAPublished September 27, 2006 Printed in the United States of America and IrelandThe 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.

TrademarksWebsense 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.

http://www.apache.org

Contents

Chapter 1 Preinstallation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Reporting modules and components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Selecting a database engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Database engine system requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . 19SQL Server/MSDE installation error messages . . . . . . . . . . . . . . . . . . . 19

Database version error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Collation and case-sensitivity error messages . . . . . . . . . . . . . . . . . . 20Host machine and MSDE/SQL Server names error messages. . . . . . 21Database creation error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Table creation error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Installing with MSDE 2000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Installing with SQL Server 2000/2005 . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Configuring Microsoft SQL Server 2005 user roles . . . . . . . . . . . . . 30Chapter 3 Selecting the Web Server and Setting Up Users . . . . . . . . . . . . . . . . . 31

Explorer with Microsoft IIS Web Server . . . . . . . . . . . . . . . . . . . . . . . . 32Explorer access requirements for the Temp directory . . . . . . . . . . . . 32

Using Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Identifying users for Reporting tools and utilities. . . . . . . . . . . . . . . . . . 33Accessing Reporting tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Chapter 4 Running the Installer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Downloading and unzipping the installation files. . . . . . . . . . . . . . . . . . 35How to use Websense Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Installing the Websense Language Pack . . . . . . . . . . . . . . . . . . . . . . . . . 36

Websense Enterprise Reporting Installation Guide 3

Contents

Languages available with the Language Pack . . . . . . . . . . . . . . . . . .37What’s translated? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Websense Enterprise Reporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Websense Enterprise Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Installing an English version following a non-English version . . . . .38

Installation concerns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39MSDE and SQL Server installation and configuration error messages .39Database engine location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Minimizing database size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40Database location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40WebCatcher Decisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Connecting to a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41Chapter 5 Removing Reporting Components . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Chapter 6 Upgrading and Migrating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Migrating a database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

When Migrate Utility controls are available . . . . . . . . . . . . . . . . . . .45Migrating a v5.5.x database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Upgrading from MSDE to Microsoft SQL Server . . . . . . . . . . . . . . . . .47Appendix A Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48

Websense Technical Services Support Center . . . . . . . . . . . . . . . . . . . .48Premium support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Support options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Web Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Telephone assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

Customer Care . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50Improving documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50

Appendix B Configuring for Windows Trusted Connection . . . . . . . . . . . . . . . . .51

Log Server Service setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51Reporter Scheduler Service setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53Explorer Settings Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54


Contents

Configuring the IIS Web Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58


CHAPTER 1 Preinstallation Information

Information provided in this guide applies equally to Websense Enterprise®, Websense Enterprise® – Corporate Edition, and Websense® Web Security Suite™. Any information that pertains specifically to one of these products is noted separately.

Any references in this book that mention Websense Enterprise apply to all editions.

The same software is installed for these products, but the Corporate Edition and Web Security Suite features are enabled only if you enter a Corporate Edition or Web Security Suite subscription key.

For information about Corporate Edition features, see the Websense Enterprise Administrator’s Guide.

Before any Reporting modules are installed, Websense Enterprise must be installed and working. Install Websense Enterprise Reporting with the same version as Websense Enterprise.

To successfully install Websense Enterprise® Reporting, read the following topics.

Reporting modules and components, page 7Installation Checklist, page 9


Chapter 1: Preinstallation Information

Reporting modules and components

Components of Websense Enterprise Reporting may be installed on one or more machines, depending on the network and the database engine used.

Websense Enterprise Reporting components require that a database engine, either Microsoft SQL Server 2000/2005 or MSDE 2000, and is installed and running during the Websense Enterprise Reporting installation. Link to a free copy of MSDE provided during the Reporting installation.

All the Reporting modules and their components rely on Websense Enterprise. Therefore, they are always installed after Websense Enterprise. Reporting components follow. Underlined components must be installed to use any other Reporting component or module.

Log Server: Required for any Websense Enterprise Reporting component to work. Log Server creates the Log Database to which it sends internet activity, categories, protocols, and Risk Class names. Environments with a high volume of internet activity should consider placing Log Server on a separate machine. Log Server processing can consume considerable system resources, and could slow performance of other programs.Log Database: Created and powered by Microsoft SQL Server or MSDE. The term Log Database encompasses the Catalog Database, which is created at installation and database partitions for reporting. Thus, the Log Database receives and stores internet activity data.Reporter: Client-based application that produces reports that can be generated automatically, and sent via email or printed. Reporter can be installed on multiple machines, each connected to the same Log Database. This approach enables multiple managers, for example, to create reports from the same data and generate reports from different machines, at different times.Websense Enterprise Explorer: Web-based application that produces a variety of easy-to-understand summary and detail reports.

Web server - either Apache or Microsoft IIS (Apache is included in the installation package).Web browser - Microsoft Internet Explorer v5.5 or higher (not included in installation).



Database Administration: Located on the Reporting Tools Portal page, Database Administration manages databases over time with scheduled rollover and automatic creation of database partitions. Default settings can be modified by the Administrator.Database Engine. Generally the database engine should run on a separate machine from other Reporting components. Websense recommends that SQL Server 2000/2005 run on its own machine. The installation program places the database on the database engine machine. In environments with a low volume of internet activity, MSDE can run on the same machine with other Reporting components.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.

IMPORTANTInstall Log Server and the database before installing any other Reporting components, unless all components are being installed on one machine.



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 Real-Time Analyzer (RTA) lets you drill down into internet access

reports and view internet usage trends. For system requirements, see the Websense Enterprise Deployment Guide. For installation information, see the appropriate Websense Installation Guide for your system. The following services (components of Websense Enterprise) must be

running during the Reporting installation. Filtering Service Policy Server User Service

If you change default port numbers when installing Websense Enterprise, write them down. You may need the information when installing Reporting. ____________________________ If your web browser has strict settings for pop-up blocking, it may

restrict or prevent the use of some Reporting features or components. If you are running a Windows 2003 operating system: You must apply

the Microsoft Windows 2003 Service Pack 1 (SP1) before you download the Websense Language Pack during your Websense non-English installation. Be sure a printer driver (appropriate for the operating system) is

installed on the machine running Websense Enterprise Reporter before attempting to generate Reporter reports. If you install Log Server on the same machine as Microsoft SQL Server

and later upgrade SQL Server, the changes may prevent Log Server from starting. Run the Reporting installation again and choose the Repair option to restore normal Log Server operation.



2. Understand how to use the Websense SetupThe Websense products are installed from the Websense Setup, which is downloaded from the Websense website at www.websense.com (located on the Downloads page), or launched from the Websense Installation CD. You will run Setup to install any of these products or their components.

Each of these products includes several modules, which also contain separate components. Setup can be used to install modules or single components on separate machines.

This checklist is meant to be used at each appropriate machine for installation.

3. Determine how you want to deploy the Reporting componentsThe various components of Websense Enterprise Reporting may be installed on the same or different machines, depending on the network and the Database Engine used.

Install Log Server, the database, and the Database Engine before the other Reporting components. All components can be installed at the same time.

For information on how to best deploy the products, modules, and components, see the Websense Enterprise Deployment Guide. The link at the top of Setup Manager opens the most current version of the Websense Enterprise Deployment Guide.

IMPORTANTFor performance reasons: Websense recommends that you do not install Websense Enterprise, Websense Enterprise Reporting, and Websense Enterprise Client Policy Manager on the same machine.

NoteLog Server, the database, and the Database Engine are required to use any other Reporting module or component.


http://www.websense.com


4. Verify that you have the appropriate minimum software and hardware

Websense Enterprise components can be installed together on one machine, or distributed across multiple machines, depending on the operating systems and the size of the network.

Websense Enterprise v6.3: All the Reporting modules and their components rely on Websense Enterprise, so install Websense Enterprise before Websense Enterprise Reporting.For complete and detailed information on general deployment recommendations, see the Websense Enterprise Deployment Guide.

Database engine: ______________________________________________________ Reporter:

_______________________________________________________ Log Server:

_______________________________________________________ Explorer:

_______________________________________________________ Database Administration:

_______________________________________________________

5. Select the appropriate components for this machineBased on how you have chosen to deploy Websense Enterprise Reporting components, select or de-select each component by checking or unchecking the checkbox associated with each component listed.

Websense Enterprise Reporter: Client-based application that communicates with Websense Enterprise and manages information about internet activity. Log Server: Required to receive, store, and report on internet activity. Database: Required storage for data about internet activity. Database Engine: Obtain and install either Microsoft SQL Server or

MSDE.



If you use Microsoft SQL Server 2000 or 2005, you must perform the installation steps in a specific sequence to avoid installation problems. See Installing with SQL Server 2000/2005, page 28. Microsoft SQL Database Engine (MSDE) is not installed with

Reporting. To use MSDE, you can obtain English or foreign language versions from Websense. Links appear during the installation procedure if Setup detects no supported database engine. When you download MSDE from these links, the Reporting installation procedure stops. You must set up MSDE first, and then rerun the Reporting setup.exe installation program. Websense Enterprise Explorer: Web-based application that produces a

variety of easy-to-use summary and flexible detail reports that can be designed and run by business managers and human resource professionals.

Web server: Either Apache or Microsoft IIS (Apache is included in the installation package). Web browser: Microsoft Internet Explorer v5.5 or later (not

included in installation). Database Administration: As part of the Explorer web-based

application, Database Administration assists in managing the size of the database partitions, rolling over databases, and creating new ones. Web server: Either Apache or Microsoft IIS (Apache is included

in the installation package). Web browser: Microsoft Internet Explorer v5.5 or later (not

included in installation).

6. Verify and record the Policy Server location Verify and record the IP address or machine name where the Policy

Server is installed during the Websense Enterprise installation. ______________ Provide the port number Policy Server uses to communicate. The

default port number is 55806. Select a different port number for the Policy Server if the default port is not available ______________



7. If Microsoft IIS is usedChoose a web server (when installing Explorer).

Microsoft IIS: If a website has been created for another Websense product, the installer will use that website. If not, you will be required to set up a new website or use an existing website. In this case, use the Microsoft Windows Internet Services Manager.

8. Provide database engine location and decide how to connect to the database

Record the IP address (preferred) or name of machine running the database engine (Microsoft SQL Server 2000/2005 or MSDE). ______________ When the database engine (Microsoft SQL Server 2000/2005 or MSDE)

is located on a remote machine, the default location for installing the database file is C:\Program Files\Microsoft SQL Server\Mssql\Data, which works properly unless SQL Server 2000 or MSDE was installed with an instance name. If this is the case, enter the name of an existing directory on the remote machine where the database should be installed. ______________________ Make note if a Trusted Connection is being used.

____________________________

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) and leave the password blank.

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 30.

NoteWebsense, Inc., recommends avoiding Trusted Connections when connecting to an MSDE database.



9. Determine where to install the database 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.

Make sure there is enough free disk space (at least 2 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 rapidly.

10. Choose whether to minimize your database size Reporter can report a separate internet access for each web page

generated by a URL request (visit) or for each separate file that a page request generates (hits).Accept the default to “log web page by Visits” to report by Visits for a smaller database and faster reporting.Choose to report by Hits to record an entry for every file requested, including graphic images and advertisements.

Choose to Consolidate Log Records to minimize your database size by combining multiple visits by the same user to the same internet domain.

11. Determine where to locate the installation files Accept the default location

C:\Program Files\Websense

IMPORTANTYou 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.



Choose another location _______________________________________________________

12. Choose whether to enable WebCatcher Yes. You can help improve the quality of the Websense Master Database

by enabling WebCatcher to send unrecognized and security URLs to Websense, Inc., for analysis and categorization. No user-identifying information is ever sent to Websense. You must have Internet Explorer v5.5 or later installed to enable

WebCatcher to use HTTP “post” to send files to Websense. Save a copy of the data that is sent to Websense. Maximum upload file size (KB -- default size 4096 KB) _______ Minimum daily start time. ________

No. Do not send unrecognized URLs to Websense. This disables WebCatcher.

13. When upgrading Websense recommends that you upgrade all the Reporting modules and

components at the same time. When Websense Enterprise Reporting has been previously installed

with a Language Pack, upgrading to v6.3 resets the language to English. The v6.3 Language Pack must be downloaded during your Websense non-English installation. 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 crash. 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.

14. When migrating a database The Migrate Utility installs with the Log Server and is used to migrate

databases for Reporter from v5.5.x to v6.2. Once the information has been migrated to v6.2, Reporter v6.3 can use it to generate reports.



Explorer users can connect to the old database schema to run reports on older data in the v6.1.x and v6.2 databases.

IMPORTANTDo not log to a migrated database. You should use migrated databases only for reporting.


CHAPTER 2 System Requirements

To provide you with the most accurate information possible, Websense provides hardware recommendations based on the potential number of seats within a corporation. Current information for software requirements and hardware recommendations is available in the Websense Enterprise Deployment Guide. All Websense product documents are available at www.websense.com. Go to Support and Knowledge Base, and then navigate to Product Documentation.

The following are component-specific requirements before you install Websense Enterprise Reporting components.

Websense Enterprise ExplorerYour company may encrypt web traffic containing sensitive information (HTTPS) or not. Explorer runs over HTTP or HTTPS, if your web server supports this type of traffic.The web server portion can be installed on any machine that can connect to the database.Windows authentication is supported when the web server is Microsoft IIS.You must use Internet Explorer v5.5 or higher to run Websense Enterprise Explorer.

Websense Enterprise ReporterYou must have a print driver installed and selected as a default, appropriate to the operating system you use.

For information on using a database engine for Reporting, see the following:

Selecting a database engine, page 18Database engine system requirements, page 19SQL Server/MSDE installation error messages, page 19Installing with MSDE 2000, page 27



Chapter 2: System Requirements

Installing with SQL Server 2000/2005, page 28

Selecting a database engine

The descriptions below provide an overview of Microsoft SQL Server Desktop Engine 2000 (MSDE) and Microsoft SQL Server 2000/2005 (SQL Server), either of which can be used by Websense Reporting.

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 internet access 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 internet usage. 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.

IMPORTANTThe database engine must be installed before you install Websense Reporting components.



Database engine system requirements

The system requirements vary according to the database engine. Websense Reporting works with either MSDE 2000 or SQL Server 2000/2005. Websense recommends using MSDE in organizations with less internet activity, and SQL Server in organizations with higher volume.

SQL Server/MSDE installation error messages

When installing Reporting tools, a pre-installation script runs to check your SQL Server configuration. The script runs before installation files are

MSDE v2000 (can be downloaded during installation)

Microsoft SQL Server v2000 (SP 4 or higher) and SQL Server v2005 (SP1)

Operating System

Microsoft Windows 2000, Professional, Server, or Advanced Server (Service Pack 1) Microsoft Windows XP Professional Microsoft Windows 2003

Microsoft Windows 2000, Server, or Advanced Server (Service Pack 1)Windows 2003 Enterprise and Standard editions

RAM For details, see the Websense Enterprise Deployment Guide. The document is available at www.websense.com. Go to Support and Knowledge Base, and then navigate to Product Documentation.Processor

Web browser Microsoft Internet Explorer v5.5 or higher

Microsoft Internet Explorer v5.5 or higher

Microsoft Internet Explorer v5.5 or higher

Disk space 3 GB recommended (per database)

Refer to Microsoft documentation

Refer to Microsoft documentation






transferred. If any configuration issue is found, the installer presents an error message that describes the problem.

You can avoid having to stop and restart your Reporting installation if you configure SQL Server before you install the Reporting tools.

The following topics describe the issues that may cause the Reporting installation to fail, and provide information for correcting the possible problems in advance.

Database version error messagesWebsense Reporting tools must have access to MSDE 2000 or SQL Server 2000/2005. If you have an older version of MSDE or SQL Server, upgrade before you install Websense Reporting tools.

MSDE is free, and access to a downloadable version is available via a link in the Websense installation wizard, if a database engine is not found.SQL Server is available from Microsoft. Check the Microsoft website for purchase information.For installation and upgrade details, see the Microsoft documentation.

If you try to install Websense with an MSDE or SQL Server version that is not supported, an error message appears. The installer will terminate and will not access or install Reporting files and components.

Collation and case-sensitivity error messagesWebsense Reporting tools use case-insensitive collation functions for database searches to provide highly accurate reports. If your SQL Server 2000/2005 instance uses case-sensitive collation, you cannot install Websense Reporting files and components. This occurs most often if one or more other applications are using that instance of SQL Server.

To address the issue, install another SQL Server instance set to use the default case-insensitive settings. During installation, the Collation Settings dialog box provides options from which you are able to select the correct collation setting.

You can check the case setting of SQL Server via SQL Enterprise Manager, although you cannot change the setting.

1. Make sure you have administrator access to SQL Server.



2. From the Windows Start menu, select: Programs > Microsoft SQL Server > Enterprise Manager. SQL Enterprise Manager opens.

3. Go to the navigation pane and expand the following trees, in the order listed.a. Microsoft SQL Serversb. SQL Server Group

4. Right-click the server icon for the machine where the SQL instance you want to use is installed, and then select Properties from the drop-down menu.

5. Select the General tab and look for the text Server collation. An example appears next.SQL_LATIN1_General_CP1_CS_AS

In this string, the text in highlighted position indicates case sensitivity. There are two possible entries.

CS indicates the collation setting is case-sensitive.CI indicates the collation setting is case-insensitive.

6. Click OK to close the Properties dialog box.

Host machine and MSDE/SQL Server names error messagesIf the name of the host machine changed after MSDE/SQL Server was installed, the host and MSDE/SQL Server names will not match. If the machine and the MSDE/SQL Server names do not match, an error message appears, and Websense reporting components and files are not installed.

You must follow the next procedure to change the MSDE/SQL Server name without corrupting the database. For both database engines, use the osql utility to run the necessary commands.

1. Go to the machine where the MSDE/SQL Server instance runs that you want to connect to for Websense Reporting tools.

2. Check the machine name. Right-click My Computer on the desktop, and then select Properties from the drop-down menu.a. When the Properties dialog box opens, click the Network

Identification or Computer Name tab.b. Check Full Computer Name, and write the name down. You will

need this name later.



c. Click OK to close the Properties dialog box.3. From the Windows Start menu, select: Control Panel > Administrative

Tools > Services to verify that the MSDE/SQL Server instance is running.

4. From the Windows Start menu, select: Programs > Accessories > Command Prompt. A Command Prompt window opens.

5. To connect to the named instance of MSDE/SQL Server using Windows Authentication, type the following command, and then press <Enter>.osql -E -S servername\instancename

In the above command:for servername, substitute the actual name of the MSDE/SQL Server.for instancename, substitute the actual name of the MSDE/SQL Server instance.

6. Verify the entry in the Command Prompt window is 1>. This shows you are connected to the MSDE/SQL server.

7. View the currently-installed server name by entering the next commands. Press <Enter> at the end of each command. 1> EXEC sp_helpserver

2> GO

8. Enter the next commands to remove the named instance of MSDE/SQL Server. Press <Enter> at the end of each command.1> sp_dropserver N'old_SQL_name'

2> GO

In the above command, replace old_SQL_name with the existing MSDE/SQL Server name.

9. Check the results. An entry of 0 in the Command Prompt window indicates success.

10. Enter the next commands to add a new named instance of the MSDE/SQL Server. Press <Enter> at the end of each command.1> sp_addserver N'new_SQL_name'

2> GO

In the above command, replace new_SQL_name with the name of the host machine, which you discovered in step 2 of this procedure.




12. Enter the next commands to verify the new named instance of the MSDE. Press <Enter> at the end of each command.1> EXEC sp_helpserver

2> GO

13. Type EXIT to close the osql utility.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 ReferenceCommand Prompt Utilities

Microsoft documents are available at http://msdn.microsoft.com/.

Database creation error messagesTo install Websense Reporting files and components, you must have access rights that allow you to create databases. This is associated with a fixed server role. You need to create the DBCreator role to gain access to the ‘create databases rights.’ See the following:

Using SQL Enterprise Manager to set database creation rights, page 23Using osql utility to set database creation rights, page 24

Using SQL Enterprise Manager to set database creation rights1. Make sure you have administrator access to SQL Server.2. From the Windows Start menu, select: Programs > Microsoft SQL

Server > Enterprise Manager. SQL Enterprise Manager opens.3. Go to the navigation pane and expand the following trees, in the order

listed.a. Microsoft SQL Serversb. SQL Server Group


http://msdn.microsoft.com/


c. The machine entry that identifies the machine where SQL Server runs.

d. Security4. Under Security, locate and then double-click Server Roles. The Server

Roles pane opens with the full names of the available server roles.5. Right-click Database Creators, and then select Properties from the

drop-down menu. The Servers Role Properties- dbcreator dialog box opens.

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.

Using osql utility to set database creation rightsIf you use MSDE 2000 as your database engine, complete the next procedure to add the dbcreator role using osql, the MSDE user interface.

1. Go to the machine where the MSDE 2000 instance runs where you want to connect to the Websense Reporting tools.

2. From the Windows Start menu, select: Control Panel > Administrative Tools > Services to verify that the MSDE 2000 instance is running.


4. To connect to the named instance of MSDE 2000 using Windows Authentication, type the following command, and then press <Enter>.osql -E -S servername\instancename

In the above command:for servername, substitute the actual name of the MSDE Server.for instancename, substitute the actual name of the MSDE instance.

5. Verify the entry in the Command Prompt window is 1>. This shows you are connected to the MSDE server.



6. Enter the next command to grant rights for database creation, and then press <Enter>. 1> EXEC sp_addsrvrolemember N'user_logon', N'dbcreator'

2> GO

In the above command, replace user_logon with the SQL or Windows user logon to whom you are assigning database creation rights.


8. Type EXIT to close the osql utility.9. Run the Websense Reporting tool installer again.

Table creation error messagesYou must have SQL Server logon rights role that allows you to create tables. If this role is not already set, you need to set the table creation rights. See the following:

Using SQL Enterprise Manager to set table creation rights, page 25Using osql utility to set table creation rights, page 26

Using SQL Enterprise Manager to set table creation rights1. Make sure you have administrator access to SQL Server.2. From the Windows Start menu, select: Programs > Microsoft SQL

Server > Enterprise Manager. SQL Enterprise Manager opens.3. Go to the navigation pane and expand the following trees, in the order

listed.a. Microsoft SQL Serversb. SQL Server Groupc. The machine entry that identifies the machine where SQL Server

runs.d. Databases

4. Under Databases, locate the Websense database name, and then right-click.



5. From the drop-down menu, select Properties. The Properties dialog box for that database opens.

6. Select the Permissions tab. When the pane comes to the top, it contains a list of the user logons to set permissions.

7. Locate the logon entry for the added table creation rights.8. In the Create Tables column, mark the checkbox that appears for the

logon role you are modifying.9. Click OK to close the Properties dialog box.10. Select Console > Exit to close SQL Enterprise Manager.

Using osql utility to set table creation rightsIf you use MSDE as your database engine, complete the next procedure to set table creation rights using osql, the MSDE user interface.

1. Go to the machine where the MSDE 2000 instance runs that you want to connect to for Websense reporting tools.

2. From the Windows Start menu, select: Control Panel > Administrative Tools > Services to verify that the MSDE 2000 instance is running.


4. To connect to the named instance of MSDE 2000 using Windows Authentication, type the following command, and then press <Enter>. osql -E -S servername\instancename

In the above command:for servername, substitute the actual name of the MSDE server.for instancename, substitute the actual name of the MSDE instance.

5. Verify the prompt in the Command Prompt window is 1>. This shows you are now connected to the MSDE server.

6. Enter the next commands to grant rights for table creation. At the end of each line, press <Enter>.

GRANT CREATE TABLE TO user

In the above command, replace user with the SQL or Windows user logon to whom you are assigning table creation rights.




8. Type EXIT, and then press <Enter> to close the osql utility.9. Run the Websense reporting tool installer again.

Installing with MSDE 2000

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.

NoteIf replacing a previous installation of MSDE and upgrading from an English to a non-English language version of MSDE 2000, you need to uninstall the English version of MSDE before installing the non-English version of MSDE.



9. Restart your machine after MSDE has finished the installation.

10. If the installation was successful, MSDE becomes active. MSDE must be running when you install the Log Server.

Installing with SQL Server 2000/2005

Microsoft SQL Server must be purchased separately. If it has not been installed in your network, see Microsoft documentation for system requirements and installation instructions. Generally, follow these steps.

1. Install SQL Server 2000/2005 according to Microsoft instructions, if it has not already been installed.

2. Make sure SQL Server is running.3. Make sure SQL Server Agent is running.4. Obtain the SQL Server logon ID and password for a SQL Server

Administrator, or for an account that has rights to create, modify and delete databases and tables. You need this logon ID and password when you install Reporting components.

5. Restart the SQL Server machine after installation, and then install Log Server on an appropriate machine, as described in the next section.

6. Make sure the Log Server machine and each Reporting machine can recognize and communicate with SQL Server 2000/2005. This can be done in one of two ways:

IMPORTANTYou must restart the machine before installing any other Reporting components.

NoteYou must restart the machine after installing Microsoft SQL Server 2000/2005 and before installing Log Server.



Preferred: Run the SQL Server 2000/2005 installation program on each appropriate machine and select Connectivity Only when asked what components to install. You must restart the machine after installing the connectivity option. See Microsoft SQL Server documentation for details.Alternative: Run SQLredis.exe, provided in the Enterprise Reporting package, on each appropriate machine. This program, created by Microsoft for SQL Server 2000/2005 users, updates the ODBC drivers on the machine so they are compatible with SQL Server 2000/2005. (For additional information on SQLredis.exe, contact Microsoft.)

To use the SQLredis.exe program, follow these steps.a. Log on as a local administrator with privileges to the Log Server

machine.b. Close any open applications, including the Windows Control Panel.c. Download the Websense Install Manager from the Websense website

or launch it from the Websense Installation CD. d. Click Install under Websense Enterprise Reporting.e. Double-click the SQLredis.exe program that is unzipped.

This program runs as a silent install, meaning that no dialog boxes or progress bars appear.

f. Verify that the program has finished running by making sure SQLredis.exe and dasetup.exe no longer appear on the Process tab of Task Manager.

g. Restart the machine before installing Reporting components.

NoteIf you choose No for the trusted connection option when installing Reporting components after running SQLredis.exe, sometimes the SQL Server logon dialog box opens with the Use Trusted Connection option checked. Uncheck the option and enter the appropriate logon ID and password.



Configuring Microsoft SQL Server 2005 user rolesMicrosoft SQL Server 2005 has defined new SQL Agent roles that govern accessibility of the job framework.

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.

NoteThe SQL user account must also be a member of the DBCreator fixed server role.


CHAPTER 3 Selecting the Web Server and Setting Up Users

Websense Enterprise Explorer is a web-based application. You must use either Microsoft IIS or Apache as the web server.

Your installation choices and security procedures vary, based on whether your web server is Microsoft IIS or Apache. For technical support on the installation or operation of either of these web servers, contact Microsoft or Apache directly.

If both web servers are installed on the machine where you are installing Reporting, choose which web server you want to use.

This chapter contains the following topics.

Explorer with Microsoft IIS Web Server, page 32Using Reporter, page 33Identifying users for Reporting tools and utilities, page 33Accessing Reporting tools, page 33


Chapter 3: Selecting the Web Server and Setting Up Users

Explorer with Microsoft IIS Web Server

If you are using IIS, you need to know the name of the IIS website before you begin the installation. Enter the name of an existing website from IIS Manager in which the virtual directory is to be created. To create a new website or view existing websites, use the Windows Internet Services Manager.

From the Windows Start menu, select Programs > Administrative Tools > Internet Services Manager.

Explorer access requirements for the Temp directoryEmployees who have access to Explorer reports also need to have ‘modify access rights’ to the system Temp directory. For most servers, these rights are 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.

Verifying the Temp directory locationFollow the next procedure to verify the location of the Temp directory.

1. Log on to the machine where Websense Enterprise Explorer is installed.2. Locate and right-click My Computer.3. Select Properties from the drop-down menu.4. Click the Advanced tab.5. Check the System variables list for the Temp entry. Usually, the value is

C:\Windows\Temp.

Verifying Temp directory accessOnce you verify the location of the system Temp directory, you need to verify and possibly modify access to the directory at the machine where Explorer is installed.

1. Locate the Temp directory. By default, the directory is: C:\Windows\Temp.

2. Right-click the Temp folder, and then select Properties.



3. Verify that all users and Groups that should have access to Explorer reports are listed.

4. Click Modify for each associated user or group that will be allowed to access Explorer reports. Other boxes are automatically checked, based on your selection.

5. When you are done selecting all users or groups, click OK.

Using Reporter

To generate reports in Reporter, you must log on as a local administrator with privileges to the database machine.

Identifying users for Reporting tools and utilities

As a Reporting administrator, default access to Websense Reporting tools uses the same user ID and password used to log on to Websense Manager. The default user account to log on to the Websense Reporting Tools Portal is WebsenseAdministrator.

To identify other users for all Reporting tools, you must be in Websense Manager, and then select the Report Administrators option in the navigation pane. For complete configuration details, see the Websense Enterprise Administrator’s Guide.

Accessing Reporting tools

To access Websense Reporter: From the Windows Start menu, select Program Files > Websense > Websense Reporter.To access Log Server Configuration: From the Windows Start menu, select Program Files > Websense > Utilities > LogServer Setup.To access the Migrate Utility: From the Windows Start menu, select Program Files > Websense > Utilities > Migrate Utility.To access Real-Time Analyzer, Websense Enterprise Explorer, or Database Administration: From the Windows Start menu, select



Program Files > Websense > Web Reporting Tools. The Reporting Tool Portal opens.


CHAPTER 4 Running the Installer


Downloading and unzipping the installation files, page 35How to use Websense Setup, page 35Installing the Websense Language Pack, page 36Installation concerns, page 39Connecting to a database, page 41

Downloading and unzipping the installation files

Websense Enterprise installation files are downloaded from the Websense website at www.websense.com, located on the Downloads page, or launched from the Websense Installation CD. Once you access the installation files:

1. Accept the default location to unzip the installation files, or browse to a different location.

2. Click Extract to unzip the installation files. All the installation files are unzipped and Websense Setup opens.

How to use Websense Setup

Websense Setup installs:

Websense EnterpriseWebsense Enterprise Reporting



Chapter 4: Running the Installer

Websense Client Policy Manager™

1. Run the Websense Setup to install Websense Enterprise.2. Run Setup again to install Websense Enterprise Reporting. Follow the

onscreen instructions.

Installing the Websense Language Pack

The Websense Language Pack for v6.3 adds localized resources to the Websense Reporting components. Download the Language Pack during the installation of your Websense non-English installation.

Each non-English installer package includes a Language Pack that converts your Websense system to that language. The Language Pack installer launches automatically following completion of the main Websense installer.

IMPORTANT

For performance reasons, Websense recommends that these three products not be installed on the same machine.

Each product includes several modules that contain separate components. This Install Manager can be used to install modules or single components on separate machines.

For specific information on how to best deploy the products, modules, and components, see the Websense Enterprise Deployment Guide. The link at the top of the Websense Install Manager opens the current version of the Websense Enterprise Deployment Guide.

NoteAll 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 Enterprise Deployment Guide.



Follow on-screen instructions to complete the installation of the Language Pack.

Languages available with the Language Pack

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, 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.

Language Code

Chinese (Simplified) zh_CN

Chinese (Traditional) zh_TW

English en

French fr

German de

Italian it

Japanese ja

Korean ko

Portuguese (Brazil) pt_BR

Spanish es



Reporter report templates are translated, except for the Italian and Brazilian/Portuguese languages. These reports are available in English.Enterprise Explorer for Unix:User Interface and documentation are available in English.

Websense Enterprise ReporterThe Language Pack copies localized reports into a new directory that is created for the language selected. The English language versions of the reports remain in the system.

The configuration file is edited, and certain English text is replaced with text localized for the language of the installation you have selected.

Websense Enterprise ExplorerThe Language Pack provides a fully localized start page for Explorer and translates the entire user interface, including the category list displayed.

Installing an English version following a non-English versionIf you have installed a non-English version of Websense Enterprise and Reporting and want to go back to the English version:

1. Download the English version of the installation package.2. Run setup.exe. This offers an option to switch to English, which comes

up before the add/remove/repair components.

NoteWebsense 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.

Follow the on-screen instructions and provide the information requested.

MSDE and SQL Server installation and configuration error messages

The Websense installation wizard runs a script to check for installation and configuration problems with MSDE 2000 and SQL Server 2000. If the script encounters any problem, an error message appears. The error messages are documented in SQL Server/MSDE installation error messages, page 19, and include details about what you must do to resolve the errors.

Database engine locationEnter the IP address where MSDE/SQL Server is installed. Websense, Inc., recommends that you do not use a Trusted Connection if you run MSDE. Contact your database administrator for assistance.

Be aware that if you choose your Windows logon to access the database, you must have logged on to the installation machine with an account that has privileges to create, modify, and delete databases in MSDE/SQL Server, as

NoteThe name of the database for this version 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.

Be sure you do not have an existing database with this name, otherwise the installation will fail.

You can run reports on previous versions of the database schema after migrating them to the current version. See Upgrading and Migrating, page 44.



well as local administrator privileges for that machine. After installation, be sure to assign the appropriate logon ID and password to the Log Server service, as described in Upgrading and Migrating.

If you installed SQL Server 2000/2005 with an instance name other than MSSQLServer, the default, you must enter the IP address of the SQL Server machine, followed by the instance name, an example of which appears next.

<IP address>\<instancename>For example: 10.201.1.1\ReporterSql.

Enter a logon name and password for an account that has rights to create a database on the MSDE/SQL machine. The default is sa with a blank password. Click Next.

Minimizing database sizeReporter can report a separate internet access for each web page generated by a URL request (visit) or for each separate file that a page request generates (hits).

Choose Logging Web Page Visits for a smaller database and faster reporting. If you deselect this option, the database will contain an entry for every single file requested, including graphic images and advertisements. This will create a much larger database and will cause reports to generate slowly.

You can also set Consolidating Log Records to minimize the database size by combining multiple visits by the same user to the same internet domain.

Database locationSpecify 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.

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.

WebCatcher DecisionsHelp improve the quality of the Websense Enterprise Master Database by sending unrecognized or security URLs to Websense, Inc., for analysis. No user-identifying information is ever sent to Websense.

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

IMPORTANTYou 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.



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.


CHAPTER 5 Removing Reporting Components

To uninstall some or all of the Websense Enterprise Reporting components, remove them from your machine as described in the steps below.

1. Locate the setup.exe file that was unzipped with the Websense Enterprise Reporting package.Alternatively, you can download Websense Setup from the Websense website or launch it from the Websense Installation CD.

2. Run the installer, and select Remove.

Alternately, to remove all components, you can use the Windows Add/Remove option to remove some or all of the Websense Reporting components.

1. Open the Windows Control panel.2. Double-click Add or Remove Programs.3. Locate Websense in the list, and then click Change/Remove.4. Follow instructions when the Websense uninstaller opens.


CHAPTER 6 Upgrading and Migrating


Upgrading, page 44Migrating a database, page 44Upgrading from MSDE to Microsoft SQL Server, page 47

Upgrading

Migrating a database

There is no migration path from previous database schemas to the new v6.3 database schema. However, the Migrate Utility will be available for Reporter

IMPORTANT

Websense, Inc., officially supports upgrades for Websense Enterprise v5.2 to v5.5.x and 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.


Chapter 6: Upgrading and Migrating

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 can use it to generate reports. Explorer users can connect to the old database schema to run reports on older data in the v6.1.x and v6.2 databases.

When Migrate Utility controls are availableWhen connected to a v5.5.x database: Migrate is available, but Data Utilities are not available.When connected to a v6.1.x database: Migrate is not available, but the Data Utilities are available.When connected to a v6.3 database: Migrate and Data Utilities are not available.

Migrating a v5.5.x databaseTo convert a Websense Reporter v5.5.x database to a Websense Enterprise Reporter v6.2 compatible format, use the following procedure.

1. Back up the existing database. For assistance, see the MSDE 2000 or SQL Server 2000/2005 documentation.

2. Disable consolidation on the Consolidation tab in the Log Server Configuration window, if it is enabled.

3. From the Windows Start menu, select Programs > Websense > Utilities > Migrate Utility to open the Websense Migrate window.

4. Click Connect. The Select Data Source dialog box appears.

NoteDo not log to a migrated database. The migrated database will only be available for reporting purposes.



5. Select the Machine Data Source tab, and then select the Data Source Name (ODBC connection) for the database you want to migrate. In most cases, the Data Source Name matches the name of the database, for example, wslogdb_55.

6. Click OK. An SQL Server logon dialog box appears.7. Generally, the Use Trusted Connection option is checked. For most,

organizations, you will need to uncheck the box, and then enter the logon ID and password used during Log Server installation.

8. Click Migrate. 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.



Upgrading from MSDE to Microsoft SQL Server

MSDE users can upgrade to SQL Server 2000/2005 at any time, to take advantage of the larger memory capacity in SQL Server. The recommended approach is to install SQL Server on the MSDE machine, as described below. If you choose to install SQL Server on a different machine than MSDE, refer to the Websense Knowledge Base at www.websense.com. Go to Support and Knowledge Base.

Be sure to perform the upgrade during a quiet period, because no internet access information is logged during this process.

1. On the Log Server machine, stop the Log Server.a. From the Windows Start menu, select: Programs > Websense >

Utilities > Log Server Setup. The Log Server Configuration window opens.

b. Select the Connection tab. c. In the Log Server Service area, click Stop.

2. Go to the MSDE machine, and install SQL Server (see SQL Server documentation).

3. Go to the Log Server machine, and open the Log Server Configuration window if necessary.

4. Open the Database tab, and select the MS SQL Server option.5. Click Connection to select the database. 6. Update the Maximum connections allowed according to your SQL

Server license (contact the Database Administrator for assistance).7. Click Apply.8. If the SQL Server service is not running, start it at this time.9. Open the Connection tab, and then click Start to restart the Log Server.

NoteIf 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.




APPENDIX A Technical Support

Websense, Inc., is committed to providing excellent service worldwide. Our goal is to provide professional assistance in the use of our software wherever you are located.

Websense Technical Services Support Center

Technical information about Websense products is available 24 hours a day on the internet at:

www.websense.com/global/en/SupportAndKB/

This site contains the latest release information, a Knowledge Base, product documentation, and other information.

Premium support

Websense, Inc., offers 2 premium fee-based support options: Priority One 24x7 Support and Platinum Support. These options are available to United States customers only.

Priority One 24x7 Support offers a toll-free number and extended 24x7 service to customers.

Platinum Support is our most comprehensive support and education offering. It includes the advantages of Priority One 24x7 Support as well as a dedicated support team, highest priority service, and educational opportunities.

For information about Priority One 24x7 and Platinum Support services, please visit our website at:

www.websense.com/global/en/ProductsServices/Services/

For additional information, please contact our Sales Department at 800.723.1166 or +1 858.320.8000, or send an email to [email protected].


http://ww2.websense.com/global/en/SupportAndKB/

http://www.websense.com/global/en/ProductsServices/Services/

mailto:[email protected]

Appendix A: Technical Support

Support options

Websense Technical Support can be requested 24 hours a day.

Web PortalYou can submit support tickets through the Web Portal 24 hours a day. The response time during business hours is approximately 4 hours. Response to after-hours requests will occur the next business day. Support tickets can be submitted at:

www.websense.com/global/en/SupportAndKB/CreateRequest/.

Telephone assistanceBefore you call a Websense Technical Support representative, please be ready with the following:

Websense subscription keyAccess to Websense ManagerAccess to the machine running Filtering Service, the Websense Reporter server, and the database server (MSDE or SQL)Permission to access the Websense Log DatabaseFamiliarity with your network's architecture, or access to a person who has this knowledgeSpecifications of the machines running Filtering Service and Websense ManagerA list of other applications running on the Filtering Service machine

For severe problems, additional information may be needed.

Standard telephone assistance is available during normal business hours Monday through Friday at the following numbers:

San Diego, California, USA: +1 858.458.2940 London, England: +44 (0) 1932 796244

Customers in Japan should contact their distributor for the most rapid service.


http://www.websense.com/global/en/SupportAndKB/CreateRequest/

Appendix A: Technical Support

Customer Care

Contact Customer Care for assistance with:

General concernsSubscription key questions or issuesFollow-up on telephone support issuesGeneral service requests

A Customer Care representative can be reached at:

Customer Care U.S. in San Diego, California: 866.355.0690 (from the U.S.only) or +1 858.320.9777, or [email protected] Customer Care International in Dublin, Ireland: +353 (0) 1 6319360 or [email protected]

Improving documentation

Websense, Inc., understands the value of high quality, accurate documentation. If you have any suggestions for improving the documentation, contact us at [email protected]. We appreciate your input.





APPENDIX B Configuring for Windows Trusted Connection

These Websense Reporting Services and settings may have to be manually configured to run as the Windows Authenticated User.

Log Server Service setupReporter Scheduler Service setupExplorer Settings PageConfiguring the IIS Web Server

When you want to run Explorer reports against a different database, you make a change in the Explorer Settings Page.

Log Server Service setup

Most Log Server setup is done via the Log Server Configuration. However, there are 2 situations when you would need to set up the Log Server Service with a user name and password.

When Log Server is installed to use a trusted connection for database communications.When the Windows directory service is configured so that an application it perceives as anonymous, such as Log Server, cannot obtain a list of users and groups.

In these situations, Log Server must authenticate to either connect to SQL Server or obtain the user list from the directory service.

Set up Log Server with the appropriate authentication information as follows:

1. From the Windows Start menu, select Programs > Administrative Tools > Services.

2. Right-click Websense Log Server in the list, and then click Stop.


Appendix B: Configuring for Windows Trusted Connection

3. Double-click the Websense Log Server Service to open the Properties dialog box.

4. Select This account in the Log On tab.5. In the text box, enter the user name for an account with appropriate access

rights to the database on the SQL Server and the directory service. (Some environments require this to be entered as domain\user name. For example: Websense\jdoe.)

6. Enter and confirm the Windows password for this account.7. Click OK to close the Service dialog box.



8. Right-click Websense Log Server in the Services list, and then click Start.

Reporter Scheduler Service setup

Scheduling Reports to run is done via the Reporter window. However, when Reporter is installed using a trusted connection for database communications, you need to set up the Scheduler Service with a user name and password.

Scheduler must authenticate to the database.

Set up Scheduler with the appropriate authentication information as follows:

1. From the Windows Start menu, select Programs > Administrative Tools > Services.

2. Right-click Websense Report Scheduler, and then click Stop.3. Double-click Websense Report Scheduler to open the Properties dialog

box.4. Select This account in the Log On tab.5. In the text box, enter the user name for an account with appropriate access

rights to the database on the SQL Server. (Some environments require this to be entered as domain\user name. For example: Websense\jdoe.)

6. Enter and confirm the Windows password for this account.7. Click OK to close the Service dialog box.



8. Right-click Websense Report Scheduler in the Services list, and then click Start.

Explorer Settings Page

If you have chosen to install Explorer using a trusted connection, after installation you can run reports as that user, subject to the security restrictions placed on that Reporting role.

When you first open Explorer, you may see a message informing you that summary tables are not populated, and that, as the administrator, you can edit your Explorer settings. The page you access by clicking the link is also available on Explorer’s Main Page.

1. From the Windows Start menu, select Programs>Websense>Web Reporting Tools.

2. Log on to Websense Reporting Tools.3. When the Reporting Tools menu opens, click Websense Enterprise

Explorer. The Websense Enterprise Explorer Main Page appears.4. Click Settings to open the Explorer Settings page. 5. Choose the new method of database connection, based on your available

choices.



If Explorer is installed on a different machine than Log Server, your only option will be to make a custom selection.

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 database

Check this option to view the catalog database. Explorer 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 Explorer date range

Select the default date range to use when running Explorer reports.

Select the default detail report format

Choose Smart columns selection to default to a 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.



6. Click Save Settings to complete the database connection change.If you have entered valid information, a message displays, stating that you have successfully changed the database.If you have not entered valid information, a message displays that says it could not connect to a database.Make sure you entered a valid user ID and password, and correct machine and database names. Also check for a typing error.



7. Click Enterprise Explorer at the top left of the page to go back to the Reporting Tools portal.

Configuring the IIS Web Server

To configure the Internet Information Services (IIS) Web Server for trusted connections:

1. Launch Internet Information Services Manager. By default, the program is at: c:\WINNT\system32\inetsrv\inetmgr.exe .

2. In the navigation pane, select and open the folders in:Web Sites\Default Website\

3. Locate and right-click the Websense entry.4. Select Properties from the drop-down menu. The Properties dialog box

opens.5. Click Edit in the Anonymous Access and Authentication section of the

Directory Security tab.6. When the Authentication Methods dialog box opens, check the

Anonymous access box to enable this function, and then click Edit. The Anonymous User Account dialog box opens.

7. Enter an appropriate user name, or click Browse to select an appropriate user. This user name must be able to log on with trusted connection access.

8. Enter the password for the user name you identify in the Password field, if IIS is not set to control the password.

9. Click OK to close the Anonymous User Account dialog box.10. Click OK to close the Authentication Methods dialog box.11. Click OK to close the Websense Properties dialog box.12. Close Internet Information Services Manager.


Index

Aaccessing

Reporting tools, 33Temp directory, 32

Ccomponents

for Reporting, 7Reporting system requirements, 17

connectingdatabase, 41

creation rightsdatabase

setting with OSQL utility, 24customer support, 48

Ddatabase

connecting, 41creation error messages, 23creation rights

setting with OSQL utility, 24engine location, 39engine system requirements, 19location, 40migrating, 44minimizing size, 40selecting an engine, 18settings, 54SQL Server

setting creation rights, 23documentation feedback, 50downloading

installation files, 35

Eengine

database engine location, 39error messages

case-sensitivity, 20collation, 20database version, 20host machine, 21installation, 19installation and configuration, 39MSDE/SQL Server name, 21table creation, 23, 25

Exploreraccessing Temp directory, 32verifying

Temp directory access, 32Temp directory location, 32

with Microsoft IIS Web Server, 32

Ffiles

downloading, 35unzipping, 35

Iidentifying

usersfor Reporting tools and utilities, 33

installingconcerns, 39pre-installation requirements, 9unzipping files, 35with MSDE 2000, 27with SQL Server 2000, 28


Index

LLanguage Pack, 36Log Server

Service setup, 51

Mmessages

case-sensitivity errors, 20collation error messages, 20database creation errors, 23database version errors, 20host machine errors, 21installation and configuration errors, 39installation error messages, 19MSDE/SQL Server name errors, 21table creation errors, 25

MicrosoftIIS Web Server, 32SQL Server

upgrading from MSDE, 47migrating

database, 44minimizing

database size, 40MSDE

database version error messages, 20installation and configuration error

messages, 39installation error messages, 19installing

with MSDE 2000, 27name error messages, 21upgrading to Microsoft SQL Server, 47

OOSQL utility

databasesetting creation rights, 24

tablessetting up creation rights, 26

Ppremium support options, 48

Rremoving

Reporting components, 43Reporter

Scheduler Service setup, 53using, 33

Reportingaccess, 33components, 7identifying users, 33installation concerns, 39modules, 7system requirements, 17uninstalling components, 43

requirementsaccessing

Temp directory, 32pre-installation, 9Reporting system, 17

SScheduler

Reporter Service setup, 53selecting

database engine, 18services

Log Server setup, 51Reporter Scheduler setup, 53

setting upcreation table rights using SQL Enterprise

Manager, 25Log Server Service, 51Websense, 35

settingsdatabase, 54Log Server Service, 51

SQL Enterprise Managerdatabase

setting creation rights, 23


Index

tablessetting up creation rights, 25

SQL Serverdatabase

setting creation rights with Enterprise Manager, 23

database version error messages, 20installation and configuration error

messages, 39installation error messages, 19installing

with SQL Server 2000, 28name error messages, 21

system requirementsdatabase engine, 19

Ttables

creation error messages, 25setting up

creation table rights with OSQL utility, 26setting up creation rights

using Enterprise Manager, 25technical support, 48Temp directory

access requirements, 32verifying access, 32verifying location, 32

toolsidentifying users for Reporting, 33

Uuninstalling

Reporting components, 43unzipping

installation files, 35upgrading

from MSDE to Microsoft SQL Server, 47to Websense Enterprise v6.x, 44

usersidentifying

for Reporting tools and utilities, 33using

Reporter, 33utilities

identifying users for Reporting, 33

Vverifying

Temp directory location, 32

WWeb portal for technical support, 49web server

Microsoft IIS, 32WebCatcher

making decisions, 41Websense

setting up, 35setup, 35

Websense EnterpriseReporting components, 7Reporting modules, 7upgrading to v6.x, 44


REPORTING INSTALLATION UIDE - Forcepointkb.websense.com/pf/12/webfiles/WBSN...

Documents

Transcript of REPORTING INSTALLATION UIDE - Forcepointkb.websense.com/pf/12/webfiles/WBSN...