I
C
ONFIGURATION
G
UIDE
Webwasher
Content Reporter
©2007 Secure Computing Corporation. 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 Secure Computing Corporation. Every effort has been made to ensure the accuracy of this manual. However, Secure Computing Corporation makes no warranties with respect to this documentation and disclaims any implied warranties of merchantability and fitness for a particular purpose. Secure Comput-ing Corporation 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 document is subject to change without notice. Webwasher, MethodMix, AV PreScan, Live Reporting, Content Reporter, Real-Time Classifier are all trademarks or registered trademarks of Secure Computing Corporation in Ger-many and/or other countries. This product includes software developed by the Apache Software Foundation <http://www.apache.org>. Microsoft, Windows NT, Windows 2000 are registered trademarks of Microsoft Corporation in the United States and/or other countries. McAfee is a business unit of Network Associates, Inc. CheckPoint, OPSEC, and FireWall-1 are trademarks or registered trademarks of CheckPoint Software Technologies Ltd. or its affiliates. Sun and Solaris are trademarks or registered trademarks of Sun Microsys-tems, Inc. in the United States and other countries. Squid is copyrighted by the University of California, San Diego. Squid uses some code developed by others. Squid is Free Software, licensed under the terms of the GNU General Public License. NetCache is a registered trademark of Network Appliances, Inc. in the United States and other countries. Linux is a registered trademark of Linus Torvalds. The installer is created with EPM by Easy Software Products. EPM is licensed under the GNU General Public License. Other product names mentioned in this guide may be trademarks or registered trademarks of their respective companies and are the sole property of their respective manufacturers.
Secure Computing Corporation
Webwasher – A Secure Computing Brand Vattmannstrasse 3, 33100 Paderborn, Germany Phone: +49 5251 8717-000 Fax: +49 5251 8717-311 [email protected] www.webwasher.com www.securecomputing.com European Hotline Phone: +49 (0) 5251 8717-660 US Hotline Phone: +1 800 700 8328, +1 651 628 1500
Chapter 1 Introduction ... 1– 1 1.1 Target Group... 1– 1 1.2 Special Conventions... 1– 2 Chapter 2 Installing Content Reporter ... 2– 1 2.1 Planning the Installation... 2– 1 2.2 Minimum System Requirements... 2– 3 2.3 Further Requirements... 2– 5 2.3.1 Guidelines... 2– 5 2.3.2 Disk Space Requirements... 2– 5 2.4 Installing Content Reporter on Windows... 2– 6 2.4.1 Installation Steps... 2– 6 2.4.2 Licensing Procedure... 2–14 2.4.3 Setting up the Database... 2–17 2.4.4 Logging in... 2–21 2.5 Uninstalling Content Reporter on Windows... 2–23 2.5.1 Uninstalling MaxDB... 2–23 2.5.2 Uninstalling Content Reporter... 2–23 2.6 Repairing/Upgrading Content Reporter on Windows... 2–26 2.7 Installing Content Reporter on Linux or Solaris... 2–27 2.7.1 Prerequisites for the MaxDB Database – Linux... 2–27 2.7.2 Prerequisites for the MaxDB Database – Solaris... 2–28 2.7.3 Prerequisites for the MS SQL Server... 2–28 2.7.4 Installation Steps... 2–29 2.7.5 Starting and Stopping the Content Reporter Server... 2–30 2.7.6 Configuration... 2–30 2.8 Uninstalling Content Reporter on Linux or Solaris... 2–31 2.9 Repairing/Upgrading Content Reporter on Linux or Solaris... 2–31 Chapter 3 Initial Configuration Tasks ... 3– 1 3.1 First Login... 3– 1 3.2 Installing the Java Runtime Environment... 3– 2 3.3 The Embedded Database... 3– 2 3.3.1 The DB Admin Tab With MaxDB Settings... 3– 3 3.3.2 List of MaxDB Database Settings... 3– 3 3.4 Configuring Your Enterprise Database... 3– 4 3.4.1 Configuring an MS SQL Database... 3– 4 3.4.2 Configuring an Oracle Database... 3–10 3.5 Configuring Multiple Content Reporter Servers... 3–16 3.5.1 When to Use Multiple Content Reporter Servers... 3–17 3.5.2 Software Upgrades Using Multiple Content Reporter Servers... 3–17 Chapter 4 Navigating the Content Reporter User Interface ... 4– 1
4.1 Content Reporter Home Page... 4– 1 4.2 Administration Page... 4– 2 4.2.1 Administration Button... 4– 3 4.2.2 Manual Import Button... 4– 4 4.2.3 License Information Button... 4– 5 4.2.4 Exec SQL Button... 4– 6 4.2.5 Log Sources Tab... 4–10 4.2.6 Browse Time Tab... 4–12 4.2.7 URL Categorization Tab... 4–14 4.2.8 Billing Tab... 4–16 4.2.9 Authentication Tab... 4–17 4.2.10 User Groups Tab... 4–21 4.2.11 Group Reporting Tab ... 4–23 4.2.12 DB Admin Tab... 4–33 4.2.13 Rollup Tab... 4–35 4.2.14 Notifications Tab... 4–42 4.2.15 Logging Tab... 4–44 4.2.16 Performance Tab... 4–45 4.2.17 Mapped Columns Tab... 4–50 4.3 Query Definitions Page... 4–60 4.4 Report Definitions Page... 4–60 4.5 Scheduler and Events Page... 4–60 4.5.1 Details Tab... 4–63 4.5.2 Schedule Tab... 4–64 4.5.3 Access Control Tab... 4–65 4.5.4 Checking Event Results... 4–67 4.6 Report Results Page... 4–68 Chapter 5 Configuring Log Sources and Files ... 5– 1 5.1 Step One: Defining A Log Source Group... 5– 1 5.1.1 Where You Access Log Source Group Information... 5– 2 5.1.2 The Log Sources Tab... 5– 2 5.1.3 Log Source Group Information You Can Define... 5– 3 5.1.4 Definition Steps... 5– 4 5.2 Step Two: Adding Log Sources To The Log Source Group... 5– 5 5.2.1 Rules For Adding Log Sources... 5– 5 5.2.2 The Auto Discovery Windows... 5– 7 5.2.3 Log Source Properties... 5– 8 5.2.4 Adding a Log Source to Collect From a Directory... 5–20 5.2.5 Adding a Log Source To Collect From A Network Appliance
NetCache... 5–22 5.2.6 Adding a Log Source to Collect From an FTP Server... 5–27 5.2.7 Adding a Log Source to Collect From a Webwasher Server... 5–29 5.2.8 Adding a Log Source to Collect From a Cisco Content Engine... 5–34 5.2.9 Excluding Log File Content... 5–44 5.3 Step Three: Scheduling Log File Collection... 5–45 5.3.1 Scheduling Log File Collection and Processing... 5–46 5.3.2 Progress Indication... 5–47 5.3.3 Examining Information About Scheduler and Events... 5–48 5.4 Modifying Log Source Groups and Log Sources... 5–51 5.4.1 Modifying a Log Source Group... 5–51
5.5.2 Importing Log Files... 5–56 Chapter 6 Setting Access Control ... 6– 1 6.1 Learning About Authentication, Permissions, and Security... 6– 1 6.1.1 Authentication in Content Reporter... 6– 1 6.1.2 Page Permissions in Content Reporter... 6– 3 6.1.3 Web Site Name Restrictions... 6– 5 6.1.4 Security in Content Reporter... 6– 7 6.2 Configuring LDAP and NTLM Authentication... 6– 9 6.2.1 Configuring Content Reporter for LDAP Authentication... 6–10 6.2.2 Configuring Content Reporter for NTLM Authentication... 6–12 6.3 Adding User Groups and Setting User Group Permissions... 6–14 6.3.1 Adding a New LDAP or NTLM User Group and Configuring Its
Permissions... 6–14 6.4 Adding Local Users and Setting Local User Permissions... 6–15 6.4.1 Adding a Local User and Setting the User’s Permissions... 6–15 6.5 Modifying User and User Group Permissions... 6–18 6.5.1 Modifying a User Group’s Permissions... 6–18 6.5.2 Deleting an LDAP or NTLM User Group... 6–20 6.5.3 Modifying a Local User’s Information and Permissions... 6–20 6.5.4 Deleting a Local User... 6–22 Chapter 7 Additional Configuration ... 7– 1 7.1 Configuring Content Reporter Server Logging... 7– 1 7.1.1 The Logging Tab... 7– 2 7.1.2 Logging Levels... 7– 2 7.1.3 Logging Level Descriptions... 7– 3 7.1.4 Configuring Content Reporter Server Logging... 7– 3 7.2 Examining the Content Reporter Server Log File... 7– 4 7.3 Configuring Database Rollups... 7– 7 7.3.1 How Database Rollups Work... 7– 8 7.3.2 Configuring Database Rollups... 7– 8 7.3.3 Configuring Database Rollups with Multiple Content Reporter
Instances... 7– 9 7.4 Configuring Billing Aggregation... 7– 9 7.4.1 The Report Definitions Style Tab... 7–10 7.4.2 Billing Report Characteristics... 7–10 7.4.3 Billing Aggregation Example... 7–11 7.4.4 The Relationship Between Billing Tab Settings and Available
Billing Query Statistics... 7–11 7.4.5 The Billing Tab... 7–12 7.4.6 The Query Definition Tab... 7–13 7.4.7 Configuring Billing Aggregation... 7–14 7.5 Adding Logo Images to Content Reporter for HTML Reports... 7–15 7.5.1 Adding Logo Images... 7–16 7.6 Configuring Database Backups... 7–17 7.6.1 How Database Backups Work... 7–17 7.6.2 The DB Backup Tab... 7–18 7.6.3 Recovering a Content Reporter Database... 7–19 Chapter 8 Performance Tuning ... 8– 1 8.1 General Procedure... 8– 2 8.2 Import Tuning... 8– 2 8.2.1 Import Stages ... 8– 2 8.2.2 Tuning Measures and Their Effects... 8– 3
8.2.3 The Parsing Process... 8– 4 8.2.4 Measurement... 8– 5 8.2.5 Tuning Measures... 8– 7 8.3 Report Tuning... 8–11 8.3.1 Things to Avoid When Defining Queries and Reports... 8–11 8.3.2 Some Hints on Database Tuning... 8–11 8.4 Special Measures... 8–13 8.4.1 Hash Partitioning on ag_url Table... 8–13 8.4.2 Range Partitioning on Master Tables... 8–13 Appendix A Quick Start Instructions ... A– 1 A.1 Quick Start: Setting Up Log File Collection... A– 1 A.1.1 Defining a Log Source Group and Processing Its Log Files... A– 1
A.2 Quick Start: Adding a Local User and Setting the User’s
Permissions... A– 3 Appendix B Assigning a Login to Content Reporter Service ... B– 1 B.1 The Login User Account... B– 1 B.1.1 Account Requirements... B– 1 B.2 Configuring a Windows NT System... B– 2 B.3 Configuring a Windows 2000 System... B– 2 Appendix C Configuring NetCaches for Content Reporter ... C– 1 C.1 Enabling NetCache Appliance Web Access Logging... C– 1 C.2 Enabling NetCache Appliance Streaming Access Logging... C– 2 C.3 Configuring a NetCache Appliance for URL Categorization
Database Reports... C– 2 C.3.1 URL Categorization Database Query Columns... C– 3 C.3.2 Configuring a NetCache for URL Categorization Database
Reports... C– 3 C.4 Configuring NetCache Appliance Log File Collection ... C– 3 C.4.1 Gathering NetCache Appliance Information... C– 4 C.4.2 Enabling SNMP and Using Auto Discovery... C– 7 Glossary ... GL– 1
Introduction
Welcome to theWebwasher® Content Reporter Installation and
Con-figuration Guide.
This guide provides the information you need to install and configure Content Reporter:
• It describes the installation and initial configuration steps, seeChapters 2
and3.
• It explains the meaning and usage of the features that can be accessed over the user interface, seeChapter 4.
• It tells you how to configure your log sources and files, as well as access control and a number of additional settings that are useful when running Content Reporter, seeChapters 5,6and7.
After installing and configuring Content Reporter and setting up log file col-lection and processing, you can create and generate reports based on log files imported from the previously configured log sources.
• Furthermore, this guide provides you with information on performance tun-ing, seeChapter 8.
See theWebwasher Content Reporter User’s Guide for Reportingfor instructions on creating, scheduling, and generating reports on caching appli-ances, proxy servers, Web servers, and streaming media servers.
1.1
Target Group
This guide has been written for system administrators and others who will in-stall, configure, and use Content Reporter to collect and process log files with an enterprise database.
It assumes you are familiar with your operating system, database, network, caches, proxies and servers.
This guide does not cover basic system or network administration topics, nor installation of your enterprise database software.
1.2
Special Conventions
This guide refers to Webwasher servers, NetCaches, Content Engines, and all other types of proxies or log file sources as “Log Sources”.
This guide contains special messages that are described as follows:
Note: A note contains important information that helps you install or operate the system efficiently.
CAUTION!A caution contains instructions that you must follow to avoid loss of data.
Installing Content Reporter
This chapter gives you the information you need to install, uninstall, and repair the Content Reporter server.
2.1
Planning the Installation
The Content Reporter application enables you to analyze content usage, per-formance, and infrastructure load across your entire content delivery network. The Content Reporter server collects and processes log files from Webwasher servers, NetCache appliances, Content Engines, directories, and FTP servers throughout a network, and imports the results of the log file processing to your enterprise database.
You log into Content Reporter with a Web browser (the Content Reporter user interface) on your network, and schedule and generate customized reports on the log file data in your database.
The following table describes the major components of Content Reporter.
Component Description
Content Reporter Server The Content Reporter server is the program that receives and fulfills HTTP requests from client browsers on the same or other computers. The computer on which you install Content Reporter is the Content Reporter server machine.
Content Reporter Web-based user interface
The Content Reporter user interface is a Web browser with HTTP access to the Content Reporter server. You make requests to, and receive fulfilled requests from, the Content Reporter server through a Web browser.
Database Your enterprise database is a crucial part of the Content Reporter application. The Content Reporter server stores its settings and all aggregated log file records for each Log Source in the database. All reports in Content Reporter are based on the records for each Log Source in the database.
Log Source In Content Reporter, a “Log Source” represents a particular device that generates the log files that the Content Reporter server collects and processes. Content Reporter can collect and process Webwasher server log files, NetCache™ appliance log files, Content Engine log files, Web server log files, and streaming server log files.
2.2
Minimum System Requirements
The following table lists the minimum system requirements for a Content Re-porter configuration.
To learn more about specific sizing requirements and recommendations for your environment, contact Webwasher support at
[email protected]. Compo-nent Minimum Requirements on Windows Minimum Requirements on Solaris Minimum Requirements on x86 Linux 1 System for the Content Reporter Server
• Please refer to the sizing guide (available from your sales rep) 2 Operating System Platforms • Windows 2000 (Server, Advanced Server) • Windows 2003 (Server and Enterprise Edition) • Solaris 2.8 and 2.9 (64 bit version required for MaxDB) • Suse Linux Enterprise Server 9 (32 bit only) • Red Hat Enterprise Linux 4 (32 bit only) 3 Supported Databases • Oracle 8.1.7, Oracle 9i, Oracle 10g • Microsoft SQL Server 2000 and 2005 • MaxDB 7.5 (packaged)
• Oracle 8.1.7, Oracle 9i, Oracle 10g
• Microsoft SQL Server 2000 and 2005 (via Free TDS)
• MaxDB 7.5 (packaged) 4 Supported
Log Sources
• Webwasher Server (version 4.1 or later) • Cisco ContentEngine (ACNS 4.2 or later) • NetCache appliance (NetCache 5.x or later)
• Various proxies (see "Supported Log Formats" below) • Streaming server (Realserver, Windows Media Server)
Compo-nent Minimum Requirements on Windows Minimum Requirements on Solaris Minimum Requirements on x86 Linux 5 Supported Log Formats
• HTTP: Web Access, Common, Netscape Extended, Squid, Web Access Custom, W3C, Webwasher
• Streaming: Streaming Access, Custom, Real, WMS, QuickTime • Firewall: CyberGuard TSP Applicance Audit Log Files
6 Content Reporter User Interface • Internet Explorer >= 5.0, Netscape >= 6.0, Mozilla >= 1.0 or Firefox >= 1.0 • Java 2 Runtime Environment 1.4 (included) • Plug-in enabled (Internet Explorer Security Settings: Enable “Run ActiveX controls and plug-ins”) • Cookies, JavaScript and Java Applet enabled • Browser set to
check for new content each visit to a stored page
• Not available (not supported). Please use Windows machine for Content Reporter user interface.
2.3
Further Requirements
When installing Content Reporter, you will have to follow some guidelines. Fur-thermore, you must ensure that the space requirements for the installation are met.
2.3.1
Guidelines
Follow these guidelines when installing Content Reporter:
• The user who installs Content Reporter must have administrator root priv-ileges on the machine in order for the installation program to make the necessary system changes. Otherwise, Content Reporter does not func-tion properly.
• If you are setting up a multiple Content Reporter server environment, see “Configuring Multiple Content Reporter Servers” (3.5).
• If you want to access network resources, you can assign a login user ac-count to the Content Reporter service. See “Assigning a Login to Content Reporter Service” (Appendix B).
For an installation under Solaris, the installer is created with EPM by Easy Software Products. EPM is licensed under the GNU General Public License.
2.3.2
Disk Space Requirements
The Content Reporter server installation has the following disk space require-ments:
• 130 MB of space during the installation on the drive with the Temp directory for temporary installation files
• 130 MB of space on the drive with the operating system for the permanent InstallShield™ information files
• 220 MB of space on the drive on which you install the Content Reporter server
• 4 to 9 times the space of the daily log file volume. If you do not have figures for this volume yet, you can estimate it at 1 GB for every 10,000 users per day. The factor varies, depending on whether you plan to conduct an exact access tracing or not.
• If you are using MaxDB, you need additional space on the drive where the database files are to reside. The database size minimum for MaxDB is 10 GB.
Note:This drive should not be physically the same as the one that Content Reporter has been installed on.
2.4
Installing Content Reporter on Windows
The process of installing Content Reporter on Windows consists of a number of steps, see 2.4.1. After completing these, you continue with the licensing procedure, see 2.4.2, and the setting up of the database, see 2.4.3.
At the end, you can log into Content Reporter and start using it, see 2.4.4.
2.4.1
Installation Steps
To install Content Reporter on Windows, complete the following steps:
1. Ensure that your configuration meets the minimum requirements.
2. Log into the system with a user account that has administrator privileges.
3. From the Windows interface, clickStart > Settings > Control Panel.
4. Double-click “Add/Remove Programs”.
5. Click “Add New Programs”.
6. Click “CD” or “Floppy”, then click “Next”.
7. Click “Browse”, and browse to and select the ContentReporter.exefile, then click “Open”.
9. In theWelcomewindow of the InstallShield wizard, click “Next”:
The InstallShield wizard extracts the files needed to install Content Re-porter:
The wizard is then preparing to guide you through the rest of the installa-tion procedure:
Finally, anotherWelcomewindow appears.
11. Read the license agreement carefully, and click “Yes” if you wish to accept it:
12. In theCustomer Information window, enter your user name and your company name, and then click “Next:
13. In theChoose Destination Locationwindow, accept the default location or select a different location by clicking “Browse”, and then click “Next”:
14. In theSelect Program Folder window, accept the default name of the program folder, enter a new name in theProgram Foldersfield, or select an existing name from theExisting Folderslist, and then click “Next”:
15. Review the settings in theStart Copying Fileswindow, clicking “Back” to change any of them, and then click “Next”:
The InstallShield wizard now installs Content Reporter:
When the installation is almost complete, the Content Reporter service (“Content Reporter”) begins initializing, and the Setup Almost
16. In this window, select the Readme checkbox, if you would like to have the corresponding information displayed. Then click “Finish” to exit the installation program:
17. The installation is now complete, and the Content Reporter server is run-ning.
If you have selected the corresponding checkbox, the Release Notes will appear in your browser:
The program now connects to the Content Reporter server to present a configuration wizard in your browser. This wizard will guide you through the licensing procedure and the setting up of the database:
2.4.2
Licensing Procedure
The configuration wizard that has been evoked at the end of the installation steps will guide you through the licensing procedure.
1. First, aStandard Terms and Conditionswindow is displayed. If you want to accept these terms, check theAccepting Termscheckbox, then click “Next”.
To view these terms, click on the highlighted terms phrase included within the text:
2. In theChoose Locationwindow, select the location of your license file, e. g. the local file system, then click “Next”:
3. In theChoose License File window, browse to your license file, e. g. license.txt, then click “Next”:
4. The license information is displayed. Click “Next” to import the license file, or click “Back” to select a different file:
2.4.3
Setting up the Database
After the licensing information has been provided, the configuration wizard con-tinues with the database setup. Depending on the license provided, you have the option to configure the embedded MaxDB software or to set up Content Reporter to use an external database (Microsoft SQL Server or Oracle).
1. Read the information in the window announcing the setting up of the data-base, then click “Next”:
2. If you have already installed instances of MaxDB or SAPDB on the Con-tent Reporter server, uninstall them first, then click “Next”:
3. In the Choose Database Pathwindow, browse to the directory where you want to install the data files for the Content Reporter database, then click “Next”:
4. In theChoose Memory and Disk Space Settingswindow, accept the default settings, or enter different settings, then click “Next”.
For an estimate on the amount of disk space needed to store your Content Reporter database please refer to the Content Reporter Sizing Guide.
5. The database is now installed and configured on the Content Reporter server machine:
Depending on the parameters that you have provided and the speed of your hardware, this process may take a couple of minutes.
6. When installation and configuration are complete, Content Reporter is ready for use. The default password for the initial admin user is disclosed to you. Click “Next”:
Content Reporter now performs several tasks required to initialize the database connection. During this process, corresponding messages are displayed:
2.4.4
Logging in
After setting up and initializing the database, a login window is displayed.
1. Enter your username and a password, and click “Login”:
Note that alphabetic characters contained in these credentials are inter-preted in a case-insensitive manner by Content Reporter. This means that you could enter, e. g.bob smithorBob Smithas a user name with the same result.
2. If your login was successful, you can start using Content Reporter. After a grace period of 30 days has expired, you are also asked to register the database, e. g. the MaxDB database.
You should register the database if you are going to use it permanently, and not just for a limited period of evaluation.
There are several registration methods. Select one of them, or select the option to register at a later date, and then click “Next”:
3. If the registration has been successful, this is indicated to you by a further window. Click “Next”:
4. After this last part of the installation procedure, the Content Reporter
Homepage appears:
2.5
Uninstalling Content Reporter on Windows
When Content Reporter is to be uninstalled, the MaxDB database must be uninstalled before.
2.5.1
Uninstalling MaxDB
To uninstall the MaxDB database, use theuninstall_maxdb.cmdscript de-livered with the database files.
It is located in the Content Reporter folder after the installation, e. g. in Pro-gram Files\Webwasher\ContentReporter.
1. Double-clickuninstall_maxdb.cmd.
2. Enter “y” (“yes”) to confirm the uninstallation. The uninstall script then begins to uninstall MaxDB.
3. When the uninstallation procedure has been completed, “MaxDB uninstall finished” is displayed:
You have now successfully uninstalled the MaxDB database.
2.5.2
Uninstalling Content Reporter
1. From the Windows user interface, click Start > Settings > Control
Panel.
2. Double-click “Add/Remove Programs”.
3. Select Webwasher Content Reporter 4.7.1 from the list of installed pro-grams, and click “Change/Remove”.
The setup program is now preparing to uninstall Content Reporter:
4. In theMaintenance Program welcome screen, select “Remove”, and click “Next”:
The maintenance program now stops all services:
6. When the maintenance program has performed the remove operation, click “Finish” to complete the uninstallation process:
2.6
Repairing/Upgrading Content Reporter on
Windows
If you accidently delete a Content Reporter program file, you can repair the Content Reporter installation.
Repairing Content Reporter does not repair a partially uninstalled copy of Con-tent Reporter, nor restore enterprise database settings.
To repair a Content Reporter installation, complete the following steps.
1. From the Windows user interface, click Start > Settings > Control
Panel.
2. Double-click the “Add/Remove Programs” icon.
3. Select Webwasher Content Reporter 4.7.1 from the list of installed pro-grams, and click “Change/Remove”.
2.7
Installing Content Reporter on Linux or Solaris
The procedure for installing Content Reporter on a Linux or Solaris operating system is nearly the same. The description given in the upcoming sections therefore applies to both systems, unless stated otherwise.
Note that the following Linux versions are supported by Content Reporter: • SUSE Linux Enterprise 9 or a later version
• Red Hat Enterprise 4 or a later version
Content Reporter comes with an easy-to-use installer. By default, it installs almost all necessary components in/opt/ContentReporter. The script that is required to uninstall Content Reporter is by default stored in/etc/software for Linux, i. e. for both SUSE and Red Hat, and for Solaris. Its name is
Con-tentReporter.remove.
During the installation, the installer creates symbolic links in your system’s startup directories, e. g. /etc/init.d.
After a successful installation, Content Reporter is started automatically.
Note: When installing on SUSE, do not use the default ReiserFS on the file system that holds the database files since this will degrade performance sig-nificantly (especially with MaxDB).
2.7.1
Prerequisites for the MaxDB Database – Linux
This section is intended only for those who are installing Content Reporter on Linux.
You can install and use Content Reporter based on the MaxDB database de-livered with it. If you plan to do so, you should make sure the packages men-tioned below are already installed on your Linux machine.
For SUSE Linux Enterprise, please install compat-libstdc++, at least ver-sion 5.0.7. A full SUSE installation will already include this package.
For Redhat Enterprise 4, please make sure theLegacy Software
2.7.2
Prerequisites for the MaxDB Database – Solaris
This section is intended only for those who are installing Content Reporter on Solaris.
You can install and use Content Reporter based on the MaxDB database de-livered with it. If you plan to do so, you should make sure that the following kernel parameters are applied before you start the installation.
Note that the values given below are the minimal values needed – if parameters are already set to higher values, no change is required.
These kernel parameters can be checked and changed in the/etc/system file. If you have edited this file to change any of these parameters, the machine must be rebooted to activate the changes. By default, none of these param-eters is set in a Solaris environment, therefore, you should just add the lines below to your/etc/system file:
set shmsys:shminfo_shmmax=2147483648 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=100 set shmsys:shminfo_shmseg=256 set semsys:seminfo_semmns=2000 set semsys:seminfo_semmsl=1000 set semsys:seminfo_semmni=100 set semsys:seminfo_semopm=100 set semsys:seminfo_semvmx=32767
2.7.3
Prerequisites for the MS SQL Server
If you want to use MS SQL Server as backend database on a Linux or So-laris system, you need to installfreetdson your system prior to the Content Reporter installation. Note that after installing this software, no separate con-figuration activities are needed for it.
Compile the software and install it on your system. For installation instructions, see the documentation that is provided with the source distribution. There is a file namedINSTALL in the root directory.
Alternatively, you can use a binary distribution, which we provide for download via our Extranet and Resource Center:
https://extranet.webwasher.com/download/tools/index.html https://rc.cyberguard.com/download/webwasher/tools/index.html
Install the software in the following way:
1. Go to the directory where you want to installfreetds, e. g. /opt. 2. Unpack the archive, using the followinggzipcommand:
gzip -dc <tar name> | tar xf -.
3. Enter the installation root as database home in theconfigconfiguration file of Content Reporter.
With the sample directory mentioned above, the entry would be
/opt/freetds-0.63-bin.
When configuring the SQL Server database connection in Content Reporter, you need to set the database home to the directory that contains thebin,lib and other directories from thefreetdspackage (for the default installation this is /usr/local).
Content Reporter then will search for<home>/bin/freepc.
2.7.4
Installation Steps
Follow these steps to install Content Reporter on Linux or Solaris:
1. Locate the archive file in order to install the Content Reporter server:
ContentReporter-<Version>.tar.gz
In the above line, <Version> is a place holder for the actual version number – the complete file name will be similar to:
ContentReporter-4.7.1.079-linux.tar.gz
or
ContentReporter-4.7.1.079-solaris.tar.gz
2. Unpack the Content Reporter archive to your working directory with the following script:
-3. You should now have the following six files in your current directory: • Content.Reporter.install • Content.Reporter.license • Content.Reporter.readme • Content.Reporter.remove • Content Reporter.ss • Content Reporter.sw
4. Run the install script from your current directory as root
./ContentReporter.install
Please answer the questions about the installation and license agree-ment. Following this there is a series of configuration questions about user and group. Simply press<RETURN>to accept the default values.
5. The installation is now complete, and the Content Reporter server is run-ning.
2.7.5
Starting and Stopping the Content Reporter Server
Content Reporter is automatically started when the system is booted. The start and stop scripts are installed in/etc/software/init.d/webwasher-cr. You can run the script with one of the parametersstartorstop.
Note: If you perform a restart of the Content Report server, the report and import jobs running at this time will also be restarted.
2.7.6
Configuration
The Content Reporter application can be accessed using a Web browser on port 7777 – the following URL will allow you to access Content Reporter:
http://<CR host>:7777/ContentReporter. Please replace<CR host> by the name of the machine where you installed the Content Reporter software.
2.8
Uninstalling Content Reporter on Linux or Solaris
When Content Reporter is to be uninstalled, the MaxDB database must be uninstalled.before.
To uninstall the MaxDB database, execute the uninstall_maxdb.sh script delivered with the database files. It is located in the Content Reporter folder after the installation, e, g, in/opt/ContentReporter.
To uninstall Content Reporter, execute the/etc/software/ContentReporter
.removescript for Linux or Solaris and follow the on-screen instructions.
2.9
Repairing/Upgrading Content Reporter on Linux
or Solaris
Follow the above installation routine and enter the location of the current Con-tent Reporter software. /opt/ContentReporteris the default location. Repairing Content Reporter does not repair a partially uninstalled copy of Con-tent Reporter, nor does it restore enterprise database settings.
Initial Configuration Tasks
This chapter gives you the information you need to complete initial configura-tion tasks in Content Reporter.
3.1
First Login
To log into Content Reporter the first time, complete the following steps.
1. If you are logging in from the Content Reporter server machine (Win-dows), double-click the Content Reporter startup icon on your desktop, or clickStart > Programs > Webwasher > Content Reporter >
Content Reporter Login.
2. If you are logging in from a machine with HTTP access to the Content Reporter server machine, launch your Web browser and browse to the following URL:
http://servername:7777/ContentReporter/index.html
servernameis the server name or IP address of the Content Reporter machine
7777is the Content Reporter-specific port.
3. In the Content Reporter Login page, enter “admin” in the Username field, enter “admin” in the Password field, and then click “Enter”. You open the Content Reporter home page, and are successfully logged into Content Reporter.
Note that alphabetic characters contained in these credentials are inter-preted in a case-insensitive manner by Content Reporter. This means that you could enter, e. g. admin orAdminas a user name here with the same result.
If you log into Content Reporter from the Content Reporter server machine, you see an IP address of 127.0.0.1 in the Web browser’s URL field. This is the machine’s local host IP address.
3.2
Installing the Java Runtime Environment
If Content Reporter prompts you to install the Java 2 Runtime Environment 1.4, complete the following steps:
1. In theSecurity Warningwindow, click “Yes”. TheSelect Java Plug-in
Installationwindow appears.
2. Read and accept the License Agreement.
3. Select ’typical’ setup, then ’next’. Setup will proceed.
4. In theChoose Destination Locationwindow, click “Next” to complete the installation process. You can begin using Content Reporter.
3.3
The Embedded Database
The embedded MySQL MaxDB™ database is provided for evaluation as well as for productive operating in small to medium-size enterprises. It can be used for collecting and processing log data generated by up to 15.000 users, and for generating reports on the corresponding log files.
After logging into Content Reporter for the first time, you can examine the MaxDB database settings on the Administration DB Admin tab.
CAUTION! You cannot transfer data from the MaxDB database to another enterprise database once you have started to collect log files using MaxDB.
3.3.1
The DB Admin Tab With MaxDB Settings
The following graphic shows the AdministrationDB Admin tab with MaxDB settings.
3.3.2
List of MaxDB Database Settings
The following table describes the embedded MaxDB database settings.
CAUTION!Do not modify the Username, Password, Port, or DB Name set-tings. Otherwise, you cannot log back into Content Reporter after restarting the service. Only modify the Hostname setting if you must connect to a MaxDB database on another machine.
MaxDB Setting Value Description
Username cr_admin The account user name of the built-in MaxDB crsetting database.
Password admin The account password of the built-in MaxDB crsetting database.
Hostname machine name The machine name of the system on which you installed the MaxDB database. In most cases, this is the machine on which you installed Content Reporter. Example: If the machine name is “smith-nt.domainname.com,” the host name is either “smith-nt,” or “smith-nt.domainname.com.”
Port 7210 The Content Reporter server connection port to the MaxDB database.
DB Name crsettings The name of the embedded database.
3.4
Configuring Your Enterprise Database
Your enterprise database is a crucial part of the Content Reporter application. Once you connect Content Reporter to your database, all of the Content Re-porter server settings are stored in your database. If your database service stops or the Content Reporter server loses network connectivity to your data-base, you will receive an error message in your Web browser and will not be able to log into Content Reporter.
The Content Reporter server also stores all parsed log file records for each Log Source in your database. Finally, all reports in Content Reporter are based on the records for each Log Source in your database.
For details about configuring your enterprise database, see the following top-ics:
• “Configuring an MS SQL Database” (3.4.2) • “Configuring an Oracle Database” (3.4.2)
3.4.1
Configuring an MS SQL Database
You can install an SQL server 2000 database and the Content Reporter server on the same machine or on different machines. If you install them on different machines, you must install an MS SQL client on the Content Reporter server machine.
3.4.1.1
Required Configuration Procedures
You must perform the following procedures to configure an SQL server 2000 database:
• Configure Content Reporter to use the MS SQL database
3.4.1.2
The DB Admin Tab with MS SQL Settings
The following graphic shows theDB Admintab with SQL server 2000 settings.
3.4.1.3
Database Settings
The following table describes the MS SQL database settings in Content Re-porter.
Setting Description User
name The username of the SQL login that Content Reporter uses to access the database listed in the DB Name field.
The default is the “sa” login.
Content Reporter can also use a login that meets the following three requirements:
• granted only the Server Administrator role
• has only “Public” and “db_ddladmin” privileges for the Content Reporter database (listed in the DB Name field)
Pass-word
The password of the MS SQL login that Content Reporter uses to access the database listed in the DB Name field. For security reasons, no default password is set.
Host-name
The MS SQL server machine name. Example: If the machine name is “bills-nt.domainname.com,” the host name is either “bills-nt” or “bills-nt.domainname.com.”
Port The port through which the Content Reporter server connects to an MS SQL database. The default port is 1433.
Data-base Home
For the SQL server 2000, the default installation directory is C:\Program Files\Microsoft SQL Server. This should be changed to a location where sufficient space for data files is available. Alternatively, during creation of the Content Reporter database, alternate locations for data files should be chosen that provide sufficient disk space. Please consult with your MS database administrator.
DB Name
The name of the database you created in MS SQL for Content Reporter. The default database name is “crsettings.”
3.4.1.4
Configuring an MS SQL Server 2000 Database and Login
To configure an MS SQL Server 2000 database and a login for Content Re-porter, complete the following steps.1. To create a database for Content Reporter in the MS SQL Enterprise Manager console, expand the database server in the left-hand console tree (under Console Root | Microsoft SQL Servers | SQL Server Group), right-click “Databases”, and then click “New Database”.
2. In theDatabase Propertieswindow, enter a name (the default name for a Content Reporter database is ’crsettings’.
3. From theGeneraltab’s data properties window, collation should be set to Latin1_General_CS_AS_KS.
4. For theData FilesandTransaction Logtabs, the actual location of the files does not matter, as long as sufficient disk space is available to hold the expected data volume.
For assistance with sizing the database, please contact
5. If you want Content Reporter to use the “sa” System Administrator SQL lo-gin, then first expand Security in the console tree, click “Logins”, right-click the “sa” login, and click “Properties”. Then, identify or enter a password for the “sa” login, click “OK”, and go to Step 8.
6. If you want to create a new SQL login for Content Reporter, go to Step 7.
7. To create a new SQL Server Administrator login for Content Reporter, complete the following steps:
1. Expand Security in the console tree, right-click “Logins”, and click “New Login”.
2. Enter a name for the login, click the “SQL Server Authentication” but-ton, enter a password for the login, select the new Content Reporter database from the lower default Database drop-down list, and then click theServer Roles tab.
5. Enter the password, and click “OK”.
8. Make sure the database recovery model is set to "Bulk-Logged". You can check/change this using the database properties dialog on the "Options" tab.
9. If the Content Reporter server and the MS SQL Server database are on different machines, then install an MS SQL client on the Content Reporter server machine.
10. If the Content Reporter server and the MS SQL Server database are on the same machine, go to Step 11.
11. Go to “Configuring Content Reporter to use MS SQL Server database”.
3.4.1.5
Configuring Content Reporter to Use an MS SQL Server
Database
Usually, the settings for using Content Reporter with a MS SQL Server data-base are made during the initial configuration, which is guided by the built-in Content Reporter installation wizard.
The following steps must only be completed if the database server configura-tion needs to be adapted after the original installaconfigura-tion of Content Reporter:
1. Log into Content Reporter, and click theAdministrationtab.
2. Click the “Administration” button.
3. Select theDB Admintab. At any point, you can click “Reset” to reset the database settings on this tab to the state currently stored in the configu-ration settings.
4. Select SQL Server from the Database drop-down list.
5. Enter the SQL login user name (or leave “sa”) in the Username field, and then enter the login password in the Password field.
6. If the database instance is a named instance, select the Named Instance check box and enter the name of the instance in the Instance Name field.
7. If the database instance is not a named instance, then enter the port of the MS SQL Server database.
8. Enter the hostname of the database server in the Hostname field.
9. Enter (or click “Browse”, “Browse to”, and “Select”) the root directory of the SQL server or client installation in the Database Home field.
10. Enter the name of the MS SQL Server database (the default is “crset-tings”) you created or identified for Content Reporter.
11. Test the Content Reporter server’s connection to the database by clicking “Test DB Connection”.
12. If a successful connection exists between Content Reporter and the data-base, click “OK” to close the pop-up window that confirmed a successful connection, then click “OK” to save the changed settings.
13. If the database connection test failed, click “OK”, verify the information you entered and check network connectivity between the Content Reporter server and the SQL server. Then go back to Step 11.
14. From theAdministrationpage, log out of Content Reporter.
15. Stop and restart the Content Reporter service. In Windows 2000, right-clickMy Computer > Manage > expand Services and Applications
> double-click Services.
Then stop and start the Content Reporter service. Any time you modify database settings, you must stop and restart the Content Reporter service for the new settings to take affect. You might have to wait a moment for Content Reporter to start running.
After this, you have successfully configured Content Reporter to use an MS SQL Server database.
3.4.2
Configuring an Oracle Database
The upcoming sections describe the configuration procedure for an Oracle database.
3.4.2.1
Where You Can Install the Database
You can install the database and the Content Reporter server on the same machine or on different machines. If you install them on different machines, you must install a client on the Content Reporter server machine.
Usually, the settings for using Content Reporter with an Oracle database are made during the initial configuration, which is guided by the built-in Content Reporter installation wizard. The following steps must only be completed if the database server configuration needs to be adapted after the original installation of Content Reporter.
3.4.2.2
Required Configuration Procedures
You must perform the following procedures to configure an Oracle database:
• Configure the database to work with Content Reporter
• Configure Content Reporter to use the Oracle database
3.4.2.3
The DB Admin Tab with Oracle Settings
The following graphic shows theDB Admintab with Oracle settings.
3.4.2.4
Database Settings
The following table describes the Oracle database settings in Content Re-porter.
Database Setting
Description
User name The Oracle user name of the account that Content Reporter uses to access the database.
Password The password for the Oracle user account that Content Reporter uses to access the database.
Hostname
The Oracle server machine name. Example: If the machine name is “bills-nt.domainname.com,” the host name is either “bills-nt” or “bills-nt.domainname.com.”
Port The port through which the Content Reporter server connects to an Oracle database. The default port is 1521.
Database Home
The Home directory of the Oracle database server or Oracle client.
SID The Oracle Service Name or SID of the database instance used with Content Reporter.
3.4.2.5
Client Requirements
The following table lists the Content Reporter server’s Oracle client require-ments.
Character-istic
Requirement
Version The Oracle client’s version (8.1.7, 9i, 10g) must match the Oracle database server’s version.
Installed utilities
JDBC Drivers and SQL Loader utilities installed. These are part of the “Typical” client installation.
3.4.2.6
Configuring the Database
To configure the database for Content Reporter, complete the following steps.
1. If you installed the Content Reporter server and Oracle server on different machines, then install an Oracle 8.1.7, 9i or 10g client on the Content Reporter server machine.
Ensure that the SQL Loader utilities for the client are installed. These are included in the “Typical” installation.
Ensure that the JDBC Drivers and SQL Loader utilities for the Oracle server are installed.
2. Ensure that the Content Reporter server and Oracle server are running on the same machine
3. Create a user account for Content Reporter.
3.4.2.7
Creating a User Account for Content Reporter
1. Open theOracle Enterprise ManagerConsole.
2. ExpandNetwork-Databases.
3. Expand the desired Oracle instance (in the graphic, the instance is named
crdb).
4. ExpandSecurity.
6. Enter the desired user name. From theTablespacesmenu, select the desired table space to be used (USERSselected in the graphic).
7. Under theRoletab, add theRESOURCErole in addition to theCONNECT role by selecting the role and then pressing the down arrow button.
Note that if you are using Oracle 10, Release 2, or a higher version of that database, you also need to provide the user with theCREATE ANY
VIEWsystem privilege.
This is done under theSystem Privilegestab, which is located next to theRoletab in that Oracle version and higher versions.
8. ClickCreateto actually create the user.
3.4.2.8
Configuring Content Reporter
To configure Content Reporter for the database, complete the following steps.
1. Log into Content Reporter, and click theAdministrationtab.
2. Click the “Administration” button.
3. From the Log Source Groups tab, click the DB Admin tab. At any point, you can click “Reset” to reset the database settings on this tab to their current (actual) state.
4. Select Oracle from the Database drop-down list.
5. Enter the Oracle account user name in the Username field, and enter the account password in the Password field.
6. Enter the Oracle server machine name in the Hostname field.
7. Ensure that port 1521 (or the appropriate port) appears in the Port field.
8. Click Browse to browse to and select the Oracle Home directory path, or enter the Home directory path manually. Example: F:\\oracle\\ora817\\ or /usr/oracle.
9. In the SID field, enter the Oracle Service Name or SID of the database instance used with Content Reporter.
10. Test Content Reporter server’s connection to the Oracle database by clicking “Test DB Connection”.
11. If a successful connection exists between Content Reporter and the Ora-cle database. Click “OK”. Click “OK” again.
12. The database connection test failed. Click “OK”. Verify the information you entered and check network connectivity between the Content Re-porter server and the SQL server. Repeat Step 10.
13. From theAdministrationpage, log out of Content Reporter.
14. Stop and restart the Content Reporter service. In Windows 2000, right-clickMy Computer > Manage > expand Services and Applications
> double-click Services.
Any time you modify database settings, you must stop and restart the Content Reporter service for the new settings to take affect. You might need to wait a moment for Content Reporter to start running.
Then you have successfully configured Content Reporter to use an Oracle database.
3.5
Configuring Multiple Content Reporter Servers
If you collect log files for a large number of Log Sources, you can configure a multiple Content Reporter server environment. In a multiple Content Reporter server environment, each Content Reporter server can collect and process log files and update the database for some of the Log Sources in your environment. The following diagram illustrates a multiple Content Reporter server environ-ment.
After each Content Reporter server updates the database, you can log into any Content Reporter server to create and generate reports based on any or all of the Log Sources in your environment. You can also manually import log files for any of the Log Sources in your environment.
3.5.1
When to Use Multiple Content Reporter Servers
Multiple Content Reporter servers can be set up to access the same database. Each of the Content Reporter servers can control log collection from a distinct set of log sources. From each of the Content Reporter servers, reports can be run on the log sources of all Content Reporter servers.
Multiple Content Reporter servers can be used to increase availability and to provide additional computing resources for environments where very large amounts of log data need to be imported on a regular basis.
3.5.2
Software Upgrades Using Multiple Content Reporter
Servers
If multiple Content Reporter servers are connected to the same database (not supported in versions prior to 4.2, or mixed-version environments), the upgrade should be performed as follows:
1. Stop all Content Reporter services connected to the same database.
2. Run the self-extracting executable of the new version of Content Reporter on the first Content Reporter server. During the upgrade, the service will be started automatically, and the database will be converted to the new schema, which should not take more than a few minutes if you are up-grading from a previous 4.x version.
3. Once the upgrade on the first Content Reporter server is completed, the same upgrade process can be performed on all remaining Content Re-porter servers. For the remaining servers, no database schema upgrade needs to be performed.
Navigating the Content Reporter
User Interface
This chapter gives you an overview of the Content Reporter user interface. It explains in more detail the pages you use to complete the administrative tasks described in this guide.
To learn about the pages you use to complete reporting tasks, see the
Web-washer Content Reporter User’s Guide for Reporting.
4.1
Content Reporter Home Page
When you log into Content Reporter, theHomepage is displayed first. It looks like this:
TheHome page provides:
• Five tabs for invoking the pages you use to complete administrative and reporting tasks:
— Administration, see 4.2
— Query Definitions, see4.3
— Report Definitions, see 4.4
— Scheduler and Events, see 4.5
— Report Results, see 4.6
• Several links to online help instructions, some of them for explaining the tasks to start with
• A link to logout from Content Reporter
4.2
Administration Page
The Administration page enables you to complete administrative tasks in Content Reporter.
The following graphic shows this page.
TheAdministrationpage provides:
• Buttons for invoking pages and tabs you use to complete administrative tasks
— Administration — Manual Import
The following table contains a description of these buttons and the columns that are part of the list.
Component Function “Administration”
button
Clicking the “Administration” button launches the tabs for the administrative tasks in Content Reporter, see 4.2.1.
“Manual Import” button
Clicking the “Manual Import” button launches theManual Import of
Log Filespage. This page enables you to process log files for a Log Source without creating a scheduled event, see 4.2.2.
“License Information” button
Clicking the “License Information” button launches a display of the license information, see 4.2.3.
“Exec SQL” button
Clicking the “Exec SQL” button launches a wizard that assists you in executing SQL statements, see 4.2.4.
Group Name column
Lists the names of existing Log Source groups. Sorting is possible by clicking on the arrow on the column title.
Log Source Name column
Lists the name of each Log Source. After you add a Log Source to a group, you can access its management console from the
Administrationpage by clicking its name in the Log Source column. Name or IP
Address column
Lists the IP address or name of each Log Source.
Type column Lists the types of Webwasher server, NetCache appliance, FTP server, Directory, and Content Engine.
4.2.1
Administration Button
After clicking theAdministrationbutton, the tabs for the administrative tasks in Content Reporter are displayed. At the beginning, the Log Sources Tab is selected.
See 4.2.4 to 4.2.15 for descriptions of how to complete administrative tasks with each of these tabs.
Note: To complete the tasks offered under the Administration button, the Java2 Runtime Environment is needed. If it has not yet been installed, you are prompted to do so, after clicking theAdministrationbutton, see 3.2.
When this installation is completed, you will have to restart your computer. After this, click theAdministrationbutton again and select the tab that you wish to work with.
4.2.2
Manual Import Button
Clicking the Manual Import button launches the Manual Import of Log
Filespage. This page enables you to process log files for a new or an existing Log Source device without creating a scheduled event. This means you can process log files that were not collected or processed by a scheduled event and output the result to your database for an existing Log Source. For example, you can import and process old log files for a particular Log Source.
To process log files for an existing log source, first select the log source in the log source list, then click the Manual Import button.
To learn more about importing log files, see 5.5.
The following table describes theManual Import of Log Filespage compo-nents.
Component Function Log Source Group
Field
Lists the name of the Log Source group of the Log Source that generated the log file or file. If you selected the check box adjacent to a Log Source on theAdministrationpage before opening the
Import Log Filespage, this field displays the Log Source’s Log Source group.
Log Source field Lists the name of the Log Source that generated the log file. If you selected the check box adjacent to a Log Source on the
Administrationpage before opening the Import Log Files page, this field displays the Log Source’s name.
Log Files list Lists the log files you selected to be imported.
“Add” button Enables you to browse to the folder that contains the log files, and to select one or more log files.
“Remove” button Deselects one or more log files for importing.
“Import Logs” button Launches the process of importing and process the selected log files.
4.2.3
License Information Button
Clicking the “License Information” button launches a display of the license in-formation.
The information is displayed as configured in the licensing procedure, see 2.4.2.
You can update this information by clicking the “Update License” button. After clicking this button, you are guided by the license wizard, see 2.4.2.
To close the display, click the "x" button in its top right corner.
4.2.4
Exec SQL Button
Clicking on theExec SQL button launches a wizard that assists you in exe-cuting SQL statements.
Especially with MaxDB, where only command line interfaces are distributed with Content Reporter, this function can be used for retrieving additional infor-mation from Content Reporter environments more efficiently.
The wizard provides either a window for entering SQL statements or a window for importing a file that contains SQL statements. You begin with the execution procedure by choosing one of these two entering modes. The wizard executes your statements and shows the results in a further window.
4.2.4.1
Choosing the Entering Mode
At the beginning of the execution procedure, the wizard provides a window for choosing the mode in which statements are entered for execution.
If you choose to enter them via a file, you have to tell the wizard first where this file is located.
Choose one of the following three modes by checking the corresponding checkbox:
• File is on this machine’s file system
Choose this mode if you want to enter SQL statements using a file that is located on the same system as the browser.
• File is on Content Reporter server file system
Choose this mode if you want to enter SQL statements using a file that is located on the Content Reporter server (if not the same).
• File containing SQL statements are in this machine’s clipboard Choose this mode if you want to enter SQL statements directly.
After choosing a mode, clickNext to continue with the procedure.
4.2.4.2
Entering SQL Statements
After choosing the appropriate mode, the wizard provides a window for enter-ing directly the SQL statements you want to have executed.
When entering the statements in the input field, note that there are some re-strictions to the range of statements the wizard can execute, see 4.2.4.5. After entering the statements, clickNextto start the execution. The results of this process are displayed in another window, see 4.2.4.4.
4.2.4.3
Using an SQL File
After choosing the appropriate mode, the wizard provides a window that you can use to browse for a file containing the SQL statements you want to have executed.
When entering the statements in this file, note that there are some restrictions to the range of statements the wizard can execute, see 4.2.4.5.
Before the browsing window is displayed, you have to tell the wizard where the SQL file is located.
It can be located either on the machine where the browser is running or on the Content Reporter server (if not the same).
After choosing a location, clickNext. A window will appear where you can browse for the file containing the SQL statements in question.
4.2.4.4
Viewing the Results
When the wizard has completed the execution process, it displays a further window, containing the results of this process.
In this window, you are also provided with information about the problems that may have occurred during the execution process.
ClickingNextin this window will get you back to theAdministrationpage.
4.2.4.5
Restrictions
There are several restrictions to the range of SQL statements that can be ex-ecuted using theExec SQLfunction:
• Only SQL statements starting with the following strings can be executed:
select, create, alter, drop, delete, update, insert.
For other statements, e. g., exec statements or sp* stored procedures with SQL server, it is not easily possible to determine the result type, there-fore these statements are currently not supported.
• SQL statements containing the character “;” (semicolon) cannot be exe-cuted, since this character is interpreted as the end symbol of a SQL state-ment.
• When uploaded from a file, the size of SQL statements is limited to 4 MB. This should, however, be more than sufficient to handle even complex se-lect statements.
• Statements that return large results will take a lot of computing resources both in terms of CPU as well as memory capacity.
The reason for this is that the results are not streamed to the browser, but passed as a single object that needs to be maintained in the memory until the resulting object has been completely assembled.
4.2.5
Log Sources Tab
The Log Sources tab enables you to create, configure, and manage Log Source groups for log file collection.
To learn more about adding Log Sources to Log Source groups, see 5.2. The following graphic shows theLog Sources tab:
For access to group and/or Log Source editing, you can right-click within the tree display OR by clicking the buttons at the top.
In the example below, the right-click menu shows the available options on the “CR_lupus” server entry:
4.2.5.1
Log Sources Tab Components
The following table describes theLog Sources tab components.
Component Function Left-hand explorer
list
Lists each Log Source group under the Content Reporter server you used to create it, and each Log Source under its group. When you select a Content Reporter server, the central contents list displays the server’s Log Source groups and type of analysis performed for each group. When you select a particular Log Source group, the central contents list displays the names, IP addresses, and model numbers of the group’s Log Sources.
Central contents list
Displays the contents of the selected item in the left-hand explorer list. “New (Group)”
button
Creates a new Log Source group. “Edit (Group)”
button
Is used for editing the type of analysis performed for the group selected in the left-hand explorer list.
“Delete (Group)” button
Deletes the Log Source group selected in the left-hand explorer list. “New (Log
Source)” button
Adds a new Log Source to the Log Source group selected in the left-hand explorer list.
“Edit (Log Source)” button
Is used for editing the settings of the Log Source selected in the left-hand explorer list.
“Delete (Log Source)” button
Removes the Log Source selected in the left-hand explorer list from its group.
“(Discover) NetCache” button
Enables you to use the Auto Discovery feature to add NetCaches to a group.
“(Discover) WebWasher” button
Enables you to use the Auto Discovery feature to add Webwashers to a group.
“(Discover) Content Engine” button
Enables you to use the Auto Discovery feature to add Content Engines to a group.
“OK” and “Apply” buttons
Enables you to save changes to the Content Reporter server. If you click “OK”, you return to theAdministrationpage. If you click “Apply”, you remain on this tab. If you want to make multiple, interdependent changes to settings on this tab, you must click “Apply” after each interdependent change. For example, if you delete a Log Source from a Log Source group, you must click “Apply” before you can add the Log Source to another group.
“Cancel” button Enables you to return to theAdministrationpage without saving any changes.
“Help” button Opens an online page providing help information.
4.2.6
Browse Time Tab
Browse time reporting describes the ability to report on the estimated time that a user is viewing or reading a particular page or site. As it is not really pos-sible to determine browse time based on the information available in log files, a heuristic is implemented that provides fairly accurate estimates on browse times.
It should be noted that since browse times are calculated during log file import, changes for browse time settings only affect data imported after the change. It is not possible to modify historic browse time values. To get comparable results these settings should be changed only rarely; ideally these settings are
