Enterprise Reporting Server v3.5

Transcription

1 Enterprise Reporting Server v3.5 Administrator s Guide January 2001 Edition 2001 WebTrends Corporation

2 Disclaimer WebTrends Corporation makes no representations or warranties with respect to the contents or use of this manual, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, WebTrends Corporation reserves the right to revise this publication and to make changes to its content at any time, without obligation to notify any person or entity of such revisions or changes. Further, WebTrends Corporation makes no representations or warranties with respect to any WebTrends Corporation product, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, WebTrends Corporation reserves the right to make changes to any and all parts of WebTrends Corporation products at any time, without obligation to notify any person or entity of such changes. Trademarks AuditTrack, CommerceTrends Reporting Server, and WebTrends are registered trademarks of WebTrends Corporation. Additional trademarks of WebTrends Corporation include: ClusterTrends, DBTrends, Enterprise Reporting Server, Enterprise Suite, Enterprise Suite for Lotus Domino, FastTrends, Log Analyzer, Firewall Suite, Security Analyzer, Virtual WebTrends, WebTrends Live, VRM, and WebTrends Professional Suite. Other brands and their products are trademarks or registered trademarks of their respective holders. Product Support If you should have any questions during the installation or use of WebTrends Enterprise Reporting Server, please refer to the WebTrends Corporation Knowledge Base online at: If you are unable to resolve the problem, do not hesitate to contact our Product Support Department: Telephone: (503) , Fax: (503)

3 Table of Contents Ch. 1 Introduction About the Reporting Server Reporting Server features New features Documentation and Help What typographic changes mean Making documentation available to non-administrators Getting help in the program Additional resources Ch. 2 Installing and Setting Up Overview Before You Begin System requirements Browser requirements Installing on Windows NT Installing the Reporting Server Configuring the Reporting Server service Giving your account necessary rights Installing on Windows Installing the Reporting Server Installing on Linux Using the Linux installation script Using the Red Hat Packet Manager (RPM) Installing on Solaris Using the Solaris installation script Using the Solaris installation package iii

4 WebTrends Enterprise Reporting Server Installing upgrades Installing an upgrade using the script Installing an upgrade using the Solaris package Running the Reporting Server Registering the Reporting Server Uninstalling the Reporting Server Uninstalling Linux versions Uninstalling Linux, using the RPM Uninstalling Solaris versions Uninstalling Solaris packages Windows NT versions Installing Program Add-Ons (NT) Purchasing and installing Add-Ons (UNIX) Purchasing and installing Add-Ons Ch. 3 Using Profiles About Reporting Server analysis Preparing to analyze web site activity Adding a profile Analyze Now, Re-analyze, and recovering archived data Specifying a schedule for reporting Specifying the location for reports Specifying the database directory Selecting URL Search and Replace definitions Selecting URL Parameter Analysis definitions Selecting Content Group definitions Selecting Path Analysis definitions Copying a Profile Editing a Profile Deleting a Profile Stopping Analysis iv

5 Contents Monitoring profile status Changing the profiles displayed in the main console Ch. 4 Using Filters How they work How filters are processed Adding an Include or Exclude Visit Filter Adding an Include or Exclude Hit Filter Editing a Filter Deleting a filter Filter Parameter Descriptions Visit Filter Parameters Hit Filter Parameters Browser Cookie Multi-homed domain Day of Week Hour of Day Authenticated User Name Return Codes Ad Views and Clicks HTTP Methods Address Ch. 5 Using Intranet Configuration About Intranet Configuration Scenario: Creating definitions for your organization Adding an Intranet Domain Ch. 6 Using Ad Views and Clicks Tracking Internet Advertising Defining an advertisement to track Adding a profile and filter for an advertisement v

6 WebTrends Enterprise Reporting Server Ch. 7 Building Reports Reports and Profiles How reports are built How Reporting Server works Understanding log files Understanding profiles Understanding Product and Marketing definitions Setting up the Reporting Server Build a Report Pre-generated and on-demand reporting Pre-generated reports On-demand reports On-demand reports Using the job queue Viewing profile history Converting reports to Microsoft Word or Microsoft Excel Working with Report Templates Customizing reports Adding report templates Changing the report color Changing the report language Editing a report template Deleting a report template Report data and Help Cards Ch. 8 Configuring Program Options Overview Defining General options Archiving profile data Defining the web site locale Defining the profile directory Using cookies vi

7 Contents Defining file types Adding or Editing File Types Defining FTP settings Defining domain groups Defining FTP log file cache settings Defining report server settings Defining the database directory Selecting a report template Defining the reports to maintain Specifying the reporting method Pre-generated reports On-demand reports Changing the report header Defining a schedule for processing Configuring system performance settings Selecting a DNS lookup method Defining proxy server settings Configuring web server settings Ch. 9 Using Advanced Features URL search and replace definitions Using URL replacement for shopping cart applications How tracking mechanisms affect analysis Using URL replacement to group pages Creating a URL replacement definition Path analysis Content groups Analyzing activity for a dynamic site About URL parameter analysis definitions Creating translation files vii

8 WebTrends Enterprise Reporting Server Ch. 10 Setting User Access Overview Creating a user account Modifying a user account Ch. 11 Running from the Command Line About the Command Line Capability Directory Structure Command Line Options Scripts wtrs.server wtengine.server Syntax Executables wtrs Syntax Recommended Steps for Using Command Line Settings Hierarchy of settings Configuring Program Settings Audit archives Cookie Defaults reports Performance maxtablesizes language Profile on-demand report settings proxy FTP viii

9 Contents Interface maxtablesizes Feedback UNIX Configuring Web Server Settings Audit Remote Configuration Authentication UNIX Setting Up User Accounts and Permissions Userinfo Permissions Permission Example: User Value of Permission Example: User Value of filter[n] profile restrictions Working with Profiles Server[n] Profile Filters Working with Content Groups Default Content Group Content Group definition Working with Path Analysis Settings Default Path Analysis settings Path Analysis definition settings Working with URL Parameter Analysis Settings Default URL Parameter Analysis settings URL Parameter Analysis definition settings ix

10 WebTrends Enterprise Reporting Server Working with URL Search and Replace Definitions Default URL Search and Replace URL Replacement definition Defining Advertisements to Track Ad Views and Ad Clicks syntax Setting Up Your Intranet Domains Modifying Search Engines SearchEngines Engine settings Appendix A. Glossary Appendix B. Optimizing and Troubleshooting Investigating Errors Using the wtrs.err file Using the wt.remote.err file Using the wtrs.audit file Using the profile status log Fixing Error 500 Server Error Web server fails to initialize Profiles fail to initialize Conflicting file permissions File handle allocation Database location Factors impacting space and memory Symbolic links (UNIX) Connecting through the Remote Interface Problems creating a Microsoft Word report from Internet Explorer Dates for reports are unexpected Analyze Now, Re-analyze, and recovering archived data Special considerations for configuring the Reporting Server Default configuration Configuration implementing an alternate web server x

11 Contents Using multiple web servers and storing results on another machine Appendix C. Regular Expression Syntax Regular Expression Components Basic elements Qualifying characters Building Regular Expressions Matching order rules Comparing Regular Expressions and Wildcards Appendix D. System and Error Messages The Profile Status Log Common Messages Appendix E. Silent Installation Important Notes "Silent" install instructions for Solaris/Linux Installing as root "Silent" install instructions for Windows NT Index xi

12 WebTrends Enterprise Reporting Server xii

13 Introduction 1 1 About the Reporting Server WebTrends Enterprise Reporting Server provides real-time Web visitor analysis on an ongoing basis and more sophisticated analysis when necessary for users with high traffic and multiple clients, such as Internet Server Providers, server farms, and large enterprises. The built-in web server publishes reports automatically, making them available to remote users through their web browsers. In addition to the browser-based user interface, the program can also be run and configured from the command line. See Running from the Command Line on page 177 for details. Administrators can manage all aspects of the Reporting Server remotely. The Reporting Server creates comprehensive summary reports on web site visitor behavior. The reports, which can be viewed remotely via a browser, are a key asset for quickly judging site performance, response trends, and so forth. The Reporting Server should be installed on a system that can access the web server log files either locally, through a mounted drive, or transferred using FTP. The platform of the client machines viewing reports is irrelevant, as long as the correct web browser is installed. See System requirements on page 5 for browser requirements. Reporting Server features The Reporting Server has the following features: Web Server Traffic Analysis Reports on all aspects of your web site s activity, including how many people are visiting your web site, where they come from, and what pages interest them most. Support for Multiple Servers Creates reports, using ClusterTrends technology, for sites hosted by multiple servers. ClusterTrends can be implemented if you have a Server Add-On license. Report Template Designer Use this to choose the colors, fonts, layouts, and content for your reports. 1

14 WebTrends Enterprise Reporting Server New features Comprehensive Reports Automatically create and maintain reports at regular intervals, eliminating the need to run several individual reports manually. Generate weekly, monthly, quarterly, and yearly reports that focus on the content you choose. User Access Management Grant permissions and default settings on an individual basis. A range of permissions is possible, from program-wide access as an administrator to reporting ability with viewing report access. You can pre-configure profile settings for any or all users, making their work easier. Users only view the reports and program features they have access to. Remote Configuration Remote access to reports, profile settings, user accounts, and all other program features remotely. Customizable Interface Assign the dialog boxes that the user will have access to. Many dialog boxes in the interface are optional and can be disabled for non-administrators. You decide if those dialog boxes are visible to your users. Profile archiving Back up profile databases at regular intervals, which you can use to restore the profile at a later date. Advanced features Create global definitions that make your analysis more informative. Advanced features deal with pages that you want to group together, shopping cart software that prevents you from getting accurate reports, dynamic pages, and frequently traveled paths through your site. New features are added frequently. Refer to our web site at for the latest information. This version of the Reporting Server includes: Pre- and post-processing function, which allows administrators to add tasks which the Reporting Server can start prior to or after completing a profile analysis. See Pre- and post-processing on page 43. Enhanced filter functions. See Chapter 4, "Using Filters" on page 67. Enhanced reporting. See Building Reports on page 103 for details. Changes to how the Reporting Server performs URL parameter analysis, and uses cookies. 2

15 Chapter 1: Introduction Documentation and Help What typographic changes mean The following table describes the typographic changes used in this guide. Table 1-1. Typographical Changes This text Bold Title Case courier font Italics in quotes Represents The name of an icon or button (New), a text box (Base Time text box), or check box (Save User ID check box in the user interface). The name of a window (Add Profile window) or a dialog box (Edit Connection dialog box), Source code examples, program output, or anything typed by the user. The first use of a new term, or an emphasized word. The title of a chapter or section. See the Glossary in the Reporting Server online help, or at the WebTrends web site to clarify any terms used in the Reporting Server or the documentation which may be new to you. Making documentation available to non-administrators A user guide for non-administrators is also available. We urge you to make the User s Guide available on your intranet or network. The user guide can be viewed online using Adobe Acrobat. If you purchased the CD-ROM version of the Reporting Server, you can get the.pdf file from the CD. Otherwise, you can download the manual from the Support section of the WebTrends Corporation web site. To download the.pdf version of this manual: 1. Open your browser. 2. Type following URL: From the WebTrends Corporate home page, click Support. 3

16 WebTrends Enterprise Reporting Server The Product Support Page opens (Figure 1-1), showing a selection of WebTrends documentation available for download. Figure 1-1. Documentation list on Product Support page 4. Under the Technical Library heading, click Manuals to view the manuals available for download. Getting help in the program The Reporting Server provides online help to guide you through the program. Look for the Help button in the upper right of the program dialog box. You can also open the help from the Main Console by selecting the Help menu. Additional resources For definitions of terms used in the Reporting Server, see Appendix A, "Glossary" on page 245. The WebTrends portal for Internet and Intranet professionals is a great resource for Web related information, industry news, reviews, and other useful information. Visit to see for yourself. 4

17 Installing and Setting Up 2 2 Overview This chapter contains installation instructions for the Reporting Server. For unattended, or "silent" installation instructions, please see Appendix E, "Silent Installation" on page 297. Before You Begin Please be sure to complete the following: Review the system and browser requirements below to ensure optimum performance of the Reporting Server on your system. Have any valid serial numbers for the product, Add-On licenses, or subscriptions. Have two ports available for the analysis engine and the remote interface. You can then choose from the following installation paths to install the product: Installing on Windows NT on page 6 Installing on Windows 2000 on page 8 Installing on Linux on page 9 Installing on Solaris on page 14 System requirements Windows NT/Win 2000 You can run the Reporting Server on any Windows NT 4.x system or above. You can install and run the program with the following minimum system requirements, although more will be needed in order to analyze large log files: 60 MB available disk space 5

18 WebTrends Enterprise Reporting Server 128 MB memory Although the program does not have to be installed on each of your web servers, Webtrends Corporation recommends running it on a separate, dedicated system which has NFS-mount access to all the logs. Linux You can run the Reporting Server on any Intel platforms running Red Hat 6.0 or above. Solaris You can run the Reporting Server on a Sun Ultra workstation or Sun SPARCstation system running Solaris 2.6, 2.7, or 2.8. Browser requirements You can run the Reporting Server user interface on Solaris, Linux, Windows NT, or other Win32 systems running Netscape Navigator 4.5 or above or Microsoft Internet Explorer 4.01 or above. Installing on Windows NT Installing the software on Windows NT is a three-part process: Installing the Reporting Server Configuring the Reporting Server service Giving your account necessary rights Installing the Reporting Server To install the Reporting Server: 1. Insert the Reporting Server CD-ROM into your CD-ROM drive. If your system is set up to use auto-run, the setup program is automatically launched. If not, choose Run from the File or Start menus and type: X:\setup where x is the drive letter of your CD-ROM drive. 2. Follow the on-screen instructions to install the Reporting Server. 6

19 Chapter 2: Installing and Setting Up 3. Before the Reporting Server program files are copied to your system, the Software License Agreement is presented. If you agree to the stated terms, click Accept. Otherwise, click Cancel to exit the setup program without installing the software. Configuring the Reporting Server service If you will be accessing log files through network shares, you must first configure the Reporting Server service to log on under your user account. Afterward, you must give your account the necessary rights (See Giving your account necessary rights on page 7). To configure the Reporting Server service: 1. Open the Windows Control Panel. 2. Select Services, and then select Enterprise Reporting Server from the list. 3. Click Startup. The Services dialog box opens. 4. Select This Account. Specify the account to use, and type the password for the account. Giving your account necessary rights To give your account necessary rights: 1. Open the Windows NT User Manager by selecting Programs > Administrative Tools > User Manager. 2. Select the account that you specified in the previous procedure, then select Policies > User Rights. 3. Select the Show Advanced User Rights check box. 4. Select Act as part of the operating system from the Right list. 5. If your user account isn t listed, click Add. Add your account and click OK. 6. Repeat steps 4 and 5 for the Log on as a service right. 7. Click OK to close the User Rights Policy dialog box. 8. In the User Manager window, double-click on Administrators. If your account isn t listed, add it. 7

20 WebTrends Enterprise Reporting Server 9. Click OK to close the Group Properties window. The installation of the Reporting Server is complete. Important: WebTrends Corporation strongly recommends that all users review the releasenotes.txt file to read up-to-the-minute information on this latest version of the software. Installing on Windows 2000 Installing the software on Windows 2000 is a three-part process: Installing the Reporting Server Configuring the Reporting Server service Giving your account necessary rights Installing the Reporting Server To install the Reporting Server: 1. Insert the Reporting Server CD-ROM into your CD-ROM drive. If your system is set up to use auto-run, the setup program is automatically launched. If not, choose Run from the File or Start menus and type: X:\setup where x is the drive letter of your CD-ROM drive. 2. Before the Reporting Server program files are copied to your system, the Software License Agreement is presented. If you agree to the stated terms, click Accept. Otherwise, click Cancel to exit the setup program without installing the software. 3. Follow the on-screen instructions to install the Reporting Server. 4. When the installation is complete, you will be given onscreen instructions for configuring the WebTrends Reporting Server service, and giving your account necessary rights. Complete these instructions before using the software. 8

21 Chapter 2: Installing and Setting Up Important: WebTrends Corporation strongly recommends that all users review the releasenotes.txt file to read up-to-the-minute information on this latest version of the software. Installing on Linux Choose from the following two ways to install the Reporting Server: Use the installation script (see below). Use the Red Hat Package Manager (RPM) (See Using the Red Hat Packet Manager (RPM) on page 12). Note: The Bourne shell or Bourne-like shell must be available to install the Enterprise Reporting Server. Using the Linux installation script The installation script installs the files and configures program settings in one process. Note: You can be install either as root, or non-root, when running the installation script. To install the Reporting Server using the installation script: 1. Type: mkdir <tempdirectoryname> where tempdirectoryname is the directory used to uncompress and un-tar the files needed for installation. 2. Type: cd <tempdirectoryname> 9

22 WebTrends Enterprise Reporting Server 3. Select one of the following paths: If you are using uncompress, a) type: cp <source path>/wt-ers-3.5-linux.i586.tar.z. b) type uncompress wt-ers-3.5-linux.i586.tar.z to uncompress the files. If you are using gzip, a) type: cp <source path>/wt-ers-3.5-linux.i586.tar.gz. b) type: gunzip wt-ers-3.5-linux.i586.tar.gz to uncompress the files. 4. Type: 5. Type: 6. Type: tar -xvf wt-ers-3.5-linux.i586.tar cd wt-ers-3.5./install.wt-ers The Software License Agreement is displayed. Press Enter to view the complete text. 7. Type: accept if you consent to the Software License Agreement. The installation begins. Press CTRL-C if you do not accept the Software License Agreement. 8. If you are not logged on as root, you are warned that you cannot install the program as a service. Press CTRL-C to cancel, or Enter to proceed with the installation. 9. A message describes the user authentication options. Press Enter when you have reviewed the explanation. 10

23 Chapter 2: Installing and Setting Up 10. Press Enter to accept the default directory for the Reporting Server. The default directory is /usr/local/webtrends. To install the program in another location, type the new path. Type Y to verify that you want to use the specified directory. 11. Provide any valid Reporting Server serial number(s) that you have. If you are upgrading from a previous version, type any new serial numbers you may have acquired. (For example, if you purchased a subscription with your upgrade, provide that number as well.) Type each number separately followed by Enter. 12. Type the port number for the user interface. This is the port through which a user s browser can access the Reporting Server. If you are installing as root, the default port is The default port for non-root users is Make sure the port is not used by any other service. Type Y to verify the port number. 13. If you would like to install samples, type Y. Otherwise, type n. Note: You can install the samples at a later time. 14. Type the user name of the administrator performing the installation. 15. Type the port number that the user interface can use to communicate with the analysis engine. It must be a different port than you specified in Step 12. The default port is To accept it, press Enter. Enter Y to verify that this is the port that you want to use. 16. If installing as root, you can specify how you want to start the Reporting Server. (This message will not appear if you are not installing as root.) Type Y to start the Reporting Server when you boot the system. Type n if you want to start it manually. 17. A message tells you that you can use the wtrs.server script to stop or restart the program. Press Enter to continue. 18. A message asks if you want to start the Reporting Server now. Type Y to start. Otherwise, type n. 19. A message explains that you can use the wtengine.server script to start or stop the user interface, and the wtrs.server script to start or stop both the user interface and the Reporting Engine. Press Enter when you have reviewed information about the services available. 11

24 WebTrends Enterprise Reporting Server 20. Type Y to review the release notes. Otherwise, type n. 21. The installation is now complete. A message displays the URL for the opening server interface. Note: To run the Reporting Server, launch your browser and type the name of the machine, followed by a colon and the port you specified during installation. For example: Using the Red Hat Packet Manager (RPM) You can run the RPM from the Reporting Server CD-ROM. Important: You must be installed as root to run the RPM. To install the Reporting Server: 1. Type: mkdir <tempdirectoryname> where tempdirectoryname is the directory used for installation. 2. Type: cd <tempdirectoryname> 3. Locate the package, wt-ers-linux.i586.rpm, on the CD-ROM. By default, it can be found on [usr/local/webtrends.] Type: rpm -i wt-crs-ers-linux.i586.rpm 4. The welcome screen appears. Click Enter to proceed with the installation. 5. The Software License Agreement appears. Click Enter to accept. Note: The installation will not continue if you do not accept the license agreement. 6. User authentication information appears. Click Enter to continue. 7. Provide any valid Reporting Server serial number(s) that you have. If you are upgrading from a previous version, type any new serial numbers you may have acquired. (For example, if you purchased a 12

25 Chapter 2: Installing and Setting Up subscription with your upgrade, provide that number as well.) Type each number separately followed by Enter. 8. If you have Oracle databases installed, and want to generate reports using an Oracle database, type Y. If you are not configuring the Reporting Server to work in conjunction with an Oracle database, type n, and go to Step 12. To configure the Reporting Server to use an Oracle database: 9. Type the Oracle user name. This will be the Linux user on the Oracle services. Type Y to verify the user name. 10. Type the port number for the user interface. This is the port through which a user s browser can access the Reporting Server. If you are installing as root, the default port is The default port for non-root users is Make sure the port is not used by any other service. Type Y to verify the port number. 11. Enter the name of the Oracle administrator. Type Y to verify the administrator name. To complete the Reporting Server configuration: 12. Type the port number that the user interface can use to communicate with the analysis engine. It must be a different port than you specified in Step 10. The default port is To accept it, press Enter. 13. Enter Y to verify that this is the port that you want to use. 14. If installing as root, you can specify how you want to start the Reporting Server. (This message will not appear if you are not installing as root.) Type Y to start the Reporting Server when you boot the system. Type n if you want to start it manually. 15. A message tells you that you can use the wtrs.server script to stop or restart the program. Press Y to continue. 16. A message asks if you want to start the Reporting Server now. Type Y to start. Otherwise, type n. 17. A security message appears. Click Enter to continue. 13

26 WebTrends Enterprise Reporting Server 18. You are given the opportunity to change permissions. Click Enter to accept the current settings. 19. A message explains that you can use the wtengine.server script to start or stop the user interface, and the wtrs.server script to start or stop both the user interface and the Reporting Engine. Press Enter when you have reviewed information about the services available. 20. Type Y to review the release notes. Otherwise, type n. 21. The installation is now complete. A message displays the URL for the opening server interface. 22. When you are ready to configure program settings, run configure.sh, which takes you through the program setup. Installing an upgrade using the RPM To upgrade your existing version of the Reporting Server, install the program in the same directory. During the installation, a backup of wtremote.ini and wtm_wtx.ini are made. The new settings in these files are merged with the existing ones. To install the upgrade: 1. From the CD-ROM drive, type: rpm -U wt-crs-ers-linux.i586.rpm 2. When you are ready to configure program settings, run configure.sh, which takes you through the program setup. Installing on Solaris Choose from the following two ways to install the Reporting Server: Use the installation script from a set of tarred files (See Using the Solaris installation script on page 15). Use the Solaris package (See Using the Solaris installation package on page 17). Note: The Bourne shell or Bourne-like shell must be available to install the Reporting Server. Before installing, be sure you have the following information: 14

27 Chapter 2: Installing and Setting Up Any valid serial numbers for the product, Add-On licenses, or subscriptions. Two ports that are available for the analysis engine and the remote interface. Using the Solaris installation script The installation script installs the files and configures the program in a single process. To install the Reporting Server: 1. Type: mkdir <tempdirectoryname> where tempdirectoryname is the directory used to uncompress and untar the files needed for installation. 2. Type: 3. Type: 4. Type: 5. Type: 6. Type: 7. Type: cd <tempdirectoryname> cp <source path>/wt-ers-solaris.sparc.tar.z wt-ers-solaris.sparc.tar.z tar -xvf cp <source path>/wt-ers-solaris.sparc.tar.z cd wt-ers./install.wt-ers 8. The Software License Agreement is displayed. Press Enter to view the complete text of the Agreement. 15

28 WebTrends Enterprise Reporting Server 9. At the end of the Software License Agreement, you are asked to accept its terms. Type accept if you consent to the Software License Agreement. The installation begins. Press CTRL-C if you do not accept the Software License Agreement. 10. If you are not logged on as root, you are warned that you cannot install the program as a service. Press CTRL-C to cancel, or Enter to proceed with the installation. 11. A message describes the user authentication options. Press Enter when you have reviewed the explanation. 12. Provide any valid Reporting Server serial number(s). If you are upgrading from a previous version, type any new serial numbers you may have acquired. (For example, if you purchased a subscription with your upgrade, provide that number as well.) Type each number separately followed by Enter. 13. The next screen confirms the directory the software will be installed to. Type Y to accept the default directory for the Reporting Server. The default directory is /usr/local/webtrends. To install the program in another location, type the new path. 14. Type the port number to use for the user interface. This is the port through which user s browsers can access the Reporting Server. If you are installing as root, the default port is 99. If you are installing as non-root user, the default is Make sure the port that you specify is not used by another service. 15. Type Y to verify the port number. 16. Type the user name of the person performing the installation. The user you specify is given administrator rights for the Reporting Server. 17. Type the port number that the user interface can use to communicate with the analysis engine. It must be a different port than you specified in Step 14. The default port is To accept it, press Enter. Type Y to verify that this is the port that you want to use. 18. If you are installing as root, you can to specify how you want to start the Reporting Server. (This message will not appear if you are not installing as root.) Type Y to start the Reporting Server automatically at system bootup. Otherwise, type n. 16

29 Chapter 2: Installing and Setting Up 19. A message is tells you that you can use the wt-ers.server script to stop or restart the program. Press Enter to continue. 20. A message asks if you want to start the Reporting Server now. Type Y to start. Otherwise, type n. 21. A message explains that you can use the wt-ers_ui.server script to start or stop the user interface, and the wt-ers.server script to start or stop both the user interface and the Reporting Engine. Press Enter when you have reviewed information about the services available. Note: See Running from the Command Line on page 177 for more information. 22. Type Y to review the releasenotes.txt file. Otherwise, type n. 23. The installation is now complete. A message displays the URL for the opening server interface. Note: To run the Reporting Server, launch your browser and type the name of the machine, followed by a colon and the port you specified during installation. For example, Using the Solaris installation package To install the Reporting Server using the Solaris package: 1. Type: mkdir <tempdirectoryname> where tempdirectoryname is the directory used to uncompress and untar the files needed for installation. 2. Type: 3. Type: 4. Type: 5. Type: cd <tempdirectoryname> cp <source path>/wt-ers-3.5-sparc.pkg.tar.gz gunzip wt-ers-3.5-sparc.pkg.tar.gz 17

30 WebTrends Enterprise Reporting Server 6. Type: 7. Type: tar -xvf wt-ers-3.5-sparc.pkg.tar cd wt-ers-3.5 pkgadd -d /wtct-3.5 The package installs the program files. 8. When you are ready to configure program settings, run configure.sh from the wt-ers-3.5-sparc directory. This takes you through the setup process. Refer to Using the Solaris installation script on page 15 for details. Installing upgrades Installing an upgrade using the script To upgrade your existing version of the Reporting Server, install the program in the same directory. During the installation, a backup of wtremote.ini and wtm_wtx.ini are made. The new settings in these files are merged with the existing ones. Installing an upgrade using the Solaris package To install the upgrade: 1. Type: mkdir <tempdirectoryname> where tempdirectoryname is the directory used to uncompress and untar the files needed for installation. 2. Type: 3. Type: 4. Type: 5. Type: cd <tempdirectoryname> cp <source path>/wt-ers-3.5-solaris.sparc.tar.gz gunzip wt-ers-3.5-solaris.sparc.tar.gz 18

31 Chapter 2: Installing and Setting Up tar -xvf wt-ers-3.5-solaris.sparc.tar 6. Type: cd wt-ers Type: pkgadd -a -d /wt-ers-3.5 Running the Reporting Server Once the Reporting Server is installed, you can run it through your browser. To run the Reporting Server: 1. Open an Internet Explorer or Netscape Navigator browser. 2. Type the name of the machine where the Reporting Server is installed, followed by a colon and the port that you specified during installation. For example: 3. The Reporting Server Login screen opens. Click the Login button. 4. Type the user name you specified during the installation. At this point, you can leave the password text box blank. Note: After installation, you should specify a password in your.usr file. See Overview on page 173 for details. 5. The Limited Demonstration screen opens. Specify whether you want to download a trial code or purchase a full version. Once you complete the trial registration form or purchase a full version, you are ed a trial code or product serial number. 6. Type the code you are given in the Trial Code or Product Serial Number text box. Click Submit. Registering the Reporting Server Register your product using one of the procedures described here. If you downloaded a trial version from the our web site, see Limited Demonstration Mode on page 20. If your trial has expired, see Trial Mode on page

32 WebTrends Enterprise Reporting Server If you want to buy the Reporting Server, see Purchasing the Reporting Server on page 20. If you purchased the product, see Registering your purchase on page 21. Limited Demonstration Mode When you download the Reporting Server from the WebTrends Corporation web site, the product runs in limited demonstration mode. This lets you review program features and run reports using the sample profiles. In this mode, you cannot report on your own log files. To run the Reporting Server using your own log files, you must register for a trial code. To register for a trial code: 1. Select Help > Product Information. 2. Click the Register Trial button. 3. Complete the registration form, and click Submit. A trial code is created for you and displayed in the browser screen. It is also sent to your address. 4. Copy the trial code. 5. Return to the Product Information screen, and paste the code into the Trial Code or Product Serial Number text box. 6. Click Submit. Trial Mode Once you've registered the trial code, the Reporting Server runs in trial mode. This means that you can report on your own logs for 30 days. After 30 days, you can only run log files that contain dates preceding the expiration of the product. Purchasing the Reporting Server If you are running a trial version and you would like to purchase it, you can buy it through the WebTrends web site, over the phone, or by fax or mail. To learn more about purchasing options: 20

33 Chapter 2: Installing and Setting Up 1. Select Help > Product Information. The Product Information screen opens. 2. Click the Purchase Information button. The Ordering Options screen provides information on each method of purchasing the product. Registering your purchase Once you purchase the product, you ll get a product serial number which you must type in the Product Serial Number text box on the Product Information screen. Uninstalling the Reporting Server If at any time you want to remove the Reporting Server from your system, use the procedure described here. Uninstalling Linux versions To uninstall the Reporting Server: 1. If the Reporting Server is running, stop it by typing: <install dir>./wtrs.server stop 2. If the Reporting Server is configured to run as a service, type: rm /etc/rc.d/init.d/s99 Note: You must be logged in as root to remove this file. 3. Type: rm -rf <install dir> where <install dir> is the directory where the Reporting Server is installed. Uninstalling Linux, using the RPM To uninstall the Reporting Server: 1. If the Reporting Server is running, stop it by typing: 21

34 WebTrends Enterprise Reporting Server <install dir>./wtrs.server stop where <install dir> is the directory where the Reporting Server is installed. 2. If the Reporting Server is configured to run as a service, type: rm /etc/rc.d/init.d/s99 Note: You must be logged in as root to remove this file. 3. Type: rm /etc/rc.d/init.d/wtct 4. Type: rm /etc/rc.d/rc3.d/s99wtct 5. Type: rm /etc/rc.d/rc5.d/s99wtct The Reporting Server has been deleted from your system. Uninstalling Solaris versions To uninstall the Reporting Server: 1. If the Reporting Server is running, stop it by typing: <install dir>./wtrs.server stop 2. If the Reporting Server is configured to run as a service, type: rm /etc/rc3.d/s99 Note: You must be logged in as root to remove this file. 3. Type: rm -rf <install dir> where <install dir> is the directory where the Reporting Server is installed. Uninstalling Solaris packages To uninstall the Reporting Server: 22

35 Chapter 2: Installing and Setting Up 1. If the Reporting Server is running, stop it by typing: <install dir>./wtrs.server stop 2. If the Reporting Server is configured to run as a service, type: rm /etc/rc3.d/s99 Note: You must be logged in as root to remove this file. 3. Type: rm /etc/init.d/wt-ers 4. Type: rm /etc/init.d/rc3.d/s99wt-ers Windows NT versions The Reporting Server includes a standard Windows uninstall program. Use the steps described here if you did not install the WebTrends plug-ins. To begin uninstalling the program, complete these steps: 1. Select Start > Settings > Control Panel. The Windows Control Panel opens. 2. Select Add/Remove Programs from the Windows Control Panel. 3. In the Install/Uninstall tabbed view, select WebTrends Reporting Server from the list of existing programs. 4. Click Add/Remove. The Uninstall program walks you through the removal of the program from your system. Installing Program Add-Ons When you first install the Reporting Server, you have the ability to analyze log files from a single web server. If you wish to analyze log files for additional web servers, you must purchase the appropriate number of Server Add-Ons. The easiest way to order the correct number of Add-Ons is by contacting your sales representative. WebTrends Corp. Sales can be reached by telephone: (503)

36 WebTrends Enterprise Reporting Server (NT) Purchasing and installing Add-Ons 1. When you order the Add-Ons, write down the license code that you are given. You must submit the codes to run the installation. 2. Download the Add-On from the web site. Enter the license code when you are prompted. 3. The Add-On installation program looks for the Reporting Server program location and installs the new license. (UNIX) Purchasing and installing Add-Ons 1. When you order the Add-Ons, write down the license code that you are given. Note: You must know the license code to run the installation. 2. Select Help > License Add-Ons. Enter the license code you were given. The new license is activated. 24

37 Using Profiles 3 3 About Reporting Server analysis Reporting Server reports are based on profiles which define the location of your web server log file and how the log file should be analyzed. A profile provides the following data: Whether your web site resides on a single server or on multiple servers (including server clusters) Log file type and location Home page location and default pages for your site Filters to apply Which cookie to use Whether you are creating pre-generated or on-demand reports Which reporting template to use Report header settings Reports to create Schedule for updating reports DNS lookup method Users who can access the profile Location for report data Important: If you have been granted administrative rights, you can add, edit, and modify all profiles, even those created by other users. If you have not been granted administrative rights, many of the options explained in this chapter may not be available to you. 25

38 WebTrends Enterprise Reporting Server Preparing to analyze web site activity To set up a new profile to analyze your site s activity, you ll need to answer the following questions: Does your site reside on a single server or on multiple servers? If your site is on more than one server (such as in a server cluster configuration), you ll need to know the location of the servers and where your logs reside on the servers. Also, be sure you have the proper licensing if you are reporting on activity for multiple servers. Where are log files stored? You ll need the exact file path to your log files. What is the naming convention used for log files? For example, log files might be named according to date followed by a.log extension (such as log). If log files are compressed they may have a.zip,.gz, or.tar extension. What is the rotation of your log files? You ll need to know if they are rotated, and if so, on what schedule: daily, monthly, and so on. Note: You must purchase and install a Server Add-on with ClusterTrends to analyze web sites whose logs reside on multiple servers. Adding a profile This section walks you through configuring a profile using the Profile Add wizard. These screens can also be accessed through the Profile Edit dialog box. Important: If you are using the Reporting Server s Campaign Analysis feature, you must configure your profile to include the Marketing Campaign definitions and Product definitions you want included in reports for this profile. While you can always edit a profile to include new definitions, it is most efficient to have these definitions in place before you build a profile that uses them. To add a new profile to the Reporting Server: 1. From the Main Console, click New on the toolbar. The Site Configuration dialog box opens (Figure 3-1). 26

39 Chapter 3: Using Profiles Figure 3-1. Site Configuration dialog box 2. Specify your site s configuration: Select My web site is on one physical machine if your web site resides on one server. Select My web site is on multiple physical machines if your web site is on more than one server. With the ClusterTrends Add- On, the Reporting Server can analyze web site activity for sites that reside on multiple servers. Click Next to save your settings and continue. 3. The Profile Add dialog box opens with the General tab showing (Figure 3-2). Type a name for the profile in the text box. This name also serves as a default profile title in generated reports. 27

40 WebTrends Enterprise Reporting Server Figure 3-2. Profile Add dialog box 4. Specify how much of the log to analyze. Select From the start of the log file to analyze the entire log file. Select From the following date to analyze the log beginning with the date specified. Type the date in day/month/year format. Click Next. The Log File Path dialog box opens (Figure 3-3 on page 29). Specifying log file location Important: This is the most important step in creating a profile. Without the location of the log file, the program cannot access or analyze the activity on your web site. 28

41 Chapter 3: Using Profiles Figure 3-3. Log File Path dialog box 5. If you are analyzing log file data which is stored on multiple or clustered servers, please see Setting up servers for ClusterTrends profiles on page 32 for instructions. If you are analyzing log file data which is stored on a single server, continue with Step 6 below. 6. Click Browse to navigate to the directory that contains the file you want to analyze. The file name is displayed in the Current File text box. 7. Click Add to move the current file to the files list. 8. Repeat steps 7 and 8 until you have created the file list that you want to use in your profile. 9. Click one of the following: Append adds the files in the Files List to the text in your existing entry. For example, if you are building a list of log files to import, 29

42 WebTrends Enterprise Reporting Server clicking Append adds to any already specified in the Log File URL Path. Replace uses the files in the Files List to replace your existing entry. Note: If you get a message stating that the profile has failed to initialize, verify that the log file path that you entered is correct. See Understanding log files on page 104 for an overview of log files. 10. If the specified log files are accessed using FTP and the server requires the user to authenticate, type the login information in the User name and Password text boxes. The following table provides examples of how to format your entry. Table 3-1. Log file URL path format examples Example ftp://ftp.domain.com/logs/ mylog.log Description Specifies the complete path to the log files accessed using FTP. ftp://ftp.domain.com/logfiles/ ex log ftp://ftp.domain.com/ logfiles/ex log Specifies two logfiles, ex log and ex log in the logfiles directory on the ftp.domain.com server. Notice that the file paths are separated with a pipe character. (UNIX) httpd/logfiles/access_log (UNIX) httpd/logfiles/ access_log\%date- 1%%mm%%dd%%yy% (NT) c:\\winnt\logfiles\ex*.log (NT) \\utah\winnt\logfiles\ex*.log (NT) \\webserver\logfiles\%date- 1%%mm%%dd%%yy%.log Specifies the access_log in the httpd/logfiles directory. Specifies the previous day s activity for a log file named according to date. Specifies all the logs beginning with ex in the winnt\logfiles directory. Specifies the UNC path for all logs beginning with ex in the winnt\logfiles directory on the machine named utah. Specifies the previous day s activity for a log file named according to date. 30

43 Chapter 3: Using Profiles 11. When you have completed configuring the log file location information, click Next to continue with the Profile Add wizard. (In Profile Edit mode, click OK to save your changes.) Specifying home page location and file names 12. The next Profile Add screen is the Home dialog box (Figure 3-4). (In Profile Edit mode, click Edit on the toolbar, then select the Home tab to open.) Note: To include page titles in reports, you must also check the HTML Page Titles text box in the General options tab. Figure 3-4. Home dialog box 13. In the Home Page File Names text box, type the file names that the web server defaults to when a visitor enters a URL without entering a 31

44 WebTrends Enterprise Reporting Server specific file name. Separate multiple file names with spaces. You can type up to 255 characters. Specifying default home pages lets you report all references to the home page whether or not the visitor specifically included the file name. This makes the home page hit count more accurate. 14. In the web site URL text box, specify the URL to the root of your web site, including the access method ( ftp://, or file:///). Suppose that you specified your home page file name as default.htm and the web site URL as A hit to is identified as: A hit to is identified as: Select the profile to work with, and click Edit. 16. Select the General dialog box, and click in the Disable Profile check box. 17. Click OK. The profile is disabled until you clear the Disable Profile text box. Setting up servers for ClusterTrends profiles If your web site resides on more than one server such as a server cluster or farm, set up the servers to analyze here. For each server, specify the location of the log files. Note: If you are not using the ClusterTrends product in conjunction with the Reporting Server, this wizard will not appear. Complete these steps: 18. Select the ClusterTrends profile to work with, and click Edit. 19. Select the List of Servers tab. 20. Select the log file format from the list. The Server Names list includes any servers that have been defined for this web site. 21. Click Add to define a new server. The Specify New Server dialog box opens. 32

45 Chapter 3: Using Profiles 22. Type a name to identify the server in the Server Name text box. 23. Type the path to the log file in the Log File Path text box. Logs that are accessed using FTP should be identified by using the following syntax: ftp://ftp.domain.com/filepath where domain.com is the FTP server and filepath is the complete path to the log files. Type each log file path on a separate line. 24. If the log files are accessed using FTP and the server requires users to authenticate, provide the authentication information in the user name and Password fields. 25. Click Next to continue. (In Profile Edit mode, click OK to save your settings.) Specifying filters 26. The next Profile Add page is Filters. (In Profile Edit mode, click Edit, then select the Filters tab to open). The Filters dialog box opens (Figure 3-5). 33

46 WebTrends Enterprise Reporting Server Figure 3-5. Filters dialog box 27. See Adding an Include or Exclude Visit Filter on page 68, or Adding an Include or Exclude Hit Filter on page 76 for details on configuring filters. When you have completed configuring filters, click Next. (In Profile Edit mode, click OK to save your settings.) Specifying the cookie to use 28. The next Profile Add screen is the Cookies dialog box (Figure 3-6 on page 35). 34

47 Chapter 3: Using Profiles Figure 3-6. Cookies dialog box The Reporting Server uses cookies to identify unique user sessions during the analysis. A cookie is a file sent with the page requested from the server to the visitor. Cookies are stored on the visitor s system. The stored cookie is then included in subsequent requests to your site by this visitor and is recorded in the log file, enabling you to uniquely identify the visitor. Activating cookies makes user session data more accurate because each visitor is clearly distinguished. 29. If you want to use cookies in the analysis for this profile, click in the Use Cookies To Identify User Sessions check box. 30. Select one of the following: -- Use WebTrends plug-in cookie If a WebTrends extended logging plug-in is installed on your web server, you can use the WebTrends cookie to track user sessions. 35

48 WebTrends Enterprise Reporting Server -- Use this cookie If your site uses several cookies, enter the cookie you use for tracking user sessions here. For example, if you are using Microsoft SiteServer, you might have cookies that look like this: SITESERVER=ID=CookieValue1; SITESERVER=GUID=CookieValue2 If the GUID is the cookie that you want to use to identify user sessions, then you should enter SITESERVER=GUID here. -- Use entire cookie field This will include all cookies from your site in this profile s analysis. Click Next. (In Profile Edit mode, click OK to save your settings.) 31. You can edit Advanced Features from the Profile view. Click Configure to launch the Advanced Features dialog box. For details on configuring the Advanced Features, refer to the following sections: Content Groups (see Content groups on page 168) Path Analysis (see Path analysis on page 166) URL Parameter Analysis ( About URL parameter analysis definitions on page 169) URL Search and Replace ( Path analysis on page 166) Advertising Views (see Chapter 6, "Using Ad Views and Clicks" on page 97) Intranets (see Chapter 5, "Using Intranet Configuration" on page 93) 32. Click Next to continue. 33. The Reporting Methods dialog box opens ( Reporting Method dialog box on page 37). 36

49 Chapter 3: Using Profiles Figure 3-7. Reporting Method dialog box 34. Select the reporting method you want to use: Pre-generated Reports Reports are generated on a schedule. On-demand Reports Reports are generated dynamically upon user request. Note: For details on pre-generated and on-demand reports, please see Pre-generated and on-demand reporting on page 110. Click Next to continue. 35. The Report Template dialog box opens (Figure 3-8). 37

50 WebTrends Enterprise Reporting Server Figure 3-8. Report Template dialog box 36. Report templates define the content, language, and style for the report. For details on report templates, see Adding report templates on page 116. Select the template you want to use from the drop-down list: Complete CTRS Report CTRS Executive Summary Marketing Report System Administrator Report WebMaster Report Click Next to continue. 37. The Report Header dialog box opens (Figure 3-9). (In Profile Edit mode, click Edit, then select the Report Header tab.) 38

51 Chapter 3: Using Profiles Figure 3-9. Report Header dialog box 38. Type or browse to set the following options: Report Image Specifies which graphic to include in the report header. Report Image Alt Specifies the text that is displayed if the image isn t available or as the graphic is loading. Associated URL Specifies the URL to load when a visitor clicks on the Report Image. 39. When you have completed your Report Header settings, click Next. (In Profile Edit mode, click OK to save and close the window.) 40. The Next Profile Add screen is the Reports dialog box (Figure 3-10). (From Profile Edit mode, click Edit, then select Report Types.) 39

52 WebTrends Enterprise Reporting Server Figure Reports dialog box 41. Select the report intervals that you want to maintain by clicking in the appropriate Report Types boxes. 42. For each report type, specify the number of reports to save from the corresponding Reports to Store list. Note: If you run a large number of reports, you might limit the number of reports that are saved. Using this option, you can select the number of reports saved for each interval. For example, you might want to keep one month s worth of daily reports at a time; once the report for February 1 is created, the report for January 1 is deleted, and so on. When determining how many reports to store, consider how much disk space you want to devote to reports and how long you want to save them. A report using the Complete Summary template as it was installed needs 1 MB. 40

53 Chapter 3: Using Profiles 43. Click Next. (In Profile Edit mode, click OK to save your changes.) 44. The next Profile Add screen is the Memory Usage dialog box (Figure 3-11). Figure Memory Usage dialog box 45. Optional: If you want to limit the sizes of the following tables, enter the limiting number in the Visitor Tracking, Top Companies, Top Documents, and Top Forms text boxes. Here is an example of what happens when you put a limit on an internal table, using Top Companies as an example. If the Top Companies limit is set to 10,000, then RS will track the first 10,000 organizations visiting your web site. After the first 10,000 organizations have been put into the internal table, no new organizations will be added to the table. However, activity by organizations already in the table will continue to be tracked. 41

54 WebTrends Enterprise Reporting Server Limiting Top Companies is usually the first option. This table typically uses more memory than all tables except Visitor Tracking. Limiting Top Companies affects only the "Most Active Organizations" section of the report. Limiting Visitor Tracking is usually the second option. Tracking visitors is important enough that RS includes a low memory usage method of tracking visitors. The low memory usage method will track who has visited your site and how many times they have visited, but will not track things like exactly when the visits occurred, how long they lasted, how many pages were viewed in each visit, etc. For most sites, limiting Top Documents and Top Forms should not be necessary. If large amounts of memory are being used by these tables, other avenues should be explored before limiting the tables sizes. This includes looking at the definitions for document types, looking at extensions that are excluded from being treated as forms, and using URL Search & Replace to remove dynamic content that is not contributing useful information to the report. 46. The next Profile Add screen is the Report Scheduler dialog box (Figure 3-12). 42

55 Chapter 3: Using Profiles Figure Report Scheduler dialog box 47. In the Initial Start Time field, specify when you want reports to begin. 48. Select how often to update the report from the Interval drop-down list. 49. Click Next. (In Profile Edit mode, click OK to save your changes.) Pre- and post-processing 50. The Pre-processing dialog box opens (Figure 3-13). 43

56 WebTrends Enterprise Reporting Server Figure Pre-processing dialog box 51. Use the pre-processing feature to run a file immediately prior to a scheduled analysis. You can configure the Reporting Server to not run the scheduled analysis should the pre-processing command fail. Pre-processing is configurable on a per-profile basis. Select the Pre-processing checkbox if you want to have the Reporting Server run a file prior to analyzing this profile. 52. Browse to the application you want to run. 53. Enter the pathname to the working directory. 54. Enter any command line parameters you want to use. Command-line options include: isenabled = false Use specified pre- or post-process command 44

57 Chapter 3: Using Profiles application = Application to execute parameters parameters = Parameters for said application [optional] workingdirectory = Directory to execute application [optional] ignorereturncode = true Continue to processes and perform no comparison on return code returncode = 0 Space or command delimited string of return codes [all success or failure] returncodetype = success Compare resulting return codes to specified return codes with '==' or '! ='. The will allthe user to have return codes be success or failure code. Options are success or failure, defaults to success. 55. You can ask the Reporting Server to consider return codes. To use this option, select the Check return codes radio button. Enter your settings, and click OK to save. (You may need to scroll down to view all the settings available to you.) 56. Click Next to continue. 57. The post-processing dialog box opens (Figure 3-14). 45

58 WebTrends Enterprise Reporting Server Figure Post-processing dialog box 58. Use the post-processing feature to run a file immediately after an analysis. Post-processing is configurable on a per-profile basis. Select the Post-processing checkbox if you want to have the Reporting Server run a file after completing this analyzing this profile. 59. Browse to the application you want to run. 60. Enter the pathname to the working directory. 61. Enter any command line parameters you want to use. Command-line options include: isenabled = false Use specified pre or post process command application = Application to execute parameters = Parameters for said application [optional] workingdirectory = Directory to execute application [optional] 46

59 Chapter 3: Using Profiles ignorereturncode = true Continue to processes and perform no comparison on return code returncode = 0 Space or command delimited string of return codes [all success or failure] returncodetype = success Compare resulting return codes to specified return codes with '==' or '! ='. This will allow the user to have return codes be success or failure code. Options are success or failure, defaults to success. runalways = false If analysis has terminated abnormally, should the post-process command be performed? 62. You can ask the Reporting Server to consider return codes. To use this option, select the Check return codes radio button. Enter your settings, and click OK to save. (You may need to scroll down to view all the settings available to you.) 63. Click Next to continue. Specifying a DNS lookup method 64. The next Profile Add screen is the DNS Lookup dialog box (Figure 3-15 on page 48). 47

60 WebTrends Enterprise Reporting Server Figure DNS Lookup dialog box 65. In the Domain Name/IP Resolution mode, select one of the following methods: -- Quick mode, using format from log This is the fastest method for creating reports. If your web server doesn t perform DNS Lookups and you select this method, reports display visitor s IP addresses rather than domain names. -- Resolve mode, lookup all numeric IPs If your web server does not perform DNS Lookups and you need geographic or other domain-related information, select this option. -- Auto mode, if you re unsure If you don t know whether your log file contains IP addresses or domain names, you can let the Reporting Server decide. With auto-mode selected, the program assumes that your web server wasn t performing DNS lookups, and uses Resolve Mode. Then, if a record contains a 48

61 Chapter 3: Using Profiles domain name, it assumes that the web server was performing DNS lookup and switches to Quick Mode. Note: Resolve mode may slow reporting. Use it only if DNS lookups cannot be done on the server. Once a numeric address has been looked up, its text equivalent is stored in a permanent cache to expedite all subsequent reports. The default cache size is 50,000 entries; once this limit is reached, the oldest addresses are replaced with the new entries. You can change the cache size in the General Options tab. See Defining General options on page 123 for details. 66. Click Next. (In Profile Edit mode, click OK to save your changes.) Setting user access to the profile 67. The next Profile Add screen is the Profile Access dialog box (Figure 3-16). 49

62 WebTrends Enterprise Reporting Server Figure Profile Access dialog box 68. Giving a user access to the profile enables them to use it according to the rights that they have been given. 69. The Users who have access list displays users who have access to this profile. The Users without access list displays users denied access. Use the arrows to change the list. 70. If you want the report for this profile to be viewed publicly, select the Enable reports generated by this profile to be viewed anonymously by the general public option. 71. Click Next. (In Profile Edit mode, click OK to save your changes.) The Summary page opens (Figure 3-17). 50

63 Chapter 3: Using Profiles Figure Summary page 72. If the summary data is correct, click Finish. This profile will be added to the Reporting Server. If the summary data is incorrect, click Back to change your settings. You can also edit this profile at a later time by selecting the profile from the Reporting Server main console, and clicking Edit on the toolbar. Analyze Now, Re-analyze, and recovering archived data The functions Analyze Now, Re-analyze, and working with archives can help you process profile data in important ways. 51

64 WebTrends Enterprise Reporting Server Analyze Now Use Analyze Now if you need to generate reports on profiles which haven t been recently analyzed. Analyze Now overrides the scheduled analysis of a profile, and inserts profile into report queue. Analyze Now will: Append data to the profile's database. (If space limitations demand, old data will be deleted to make space for new analysis data.) Insert the profile into the report queue. Please note that the profile may not be analyzed immediately, if there is already an analysis underway. If so, the profile will remain queued until analysis can begin. To use Analyze Now: 1. From the Main Console, select the profile you want to analyze. 2. Select Profile>Analyze Now. The Analyze Now dialog box appears (Figure 3-18). Figure Analyze Now dialog box 52

65 Chapter 3: Using Profiles 3. Click OK to insert the profile into the analysis and report queue. Be aware that by using Analyze Now thereby changing when data was analyzed and editing a profile, such shifts in how reports are run may create changes in on-demand reports which over time show shifts in data patterns. You may find, upon examination of your reports, and when your profile was changed or analyzed, that you may need to either reanalyze a profile, or report on an archived profile database. Instructions on these procedures follow. Reanalyze Profile Use Reanalyze Profile if you need to create completely new reports which reflect changes to profile settings. Reanalyze Profile will: Delete all databases and reports associated with the old version of the profile. Does not change profile settings (.wlp,.wdw, etc.) or profile statuslog. Create new databases from this point forward based on new profile settings. Inserts profile into report queue. Please note that the profile may not be analyzed immediately, if there is already an analysis underway. If so, the profile will remain queued until analysis can begin. To use Re-analyze Profile, complete these steps: 1. From the Main Console, select the profile you want to reanalyze. 2. Select Profile>Re-analyze. The Re-analyze Profile dialog box appears (Figure 3-19). 53

66 WebTrends Enterprise Reporting Server Figure Re-analyze Profile dialog box 3. Click OK to reanalyze the profile. Activating archiving You can archive the profiles that you chose at regular intervals. An archive contains a backup of the databases for the profile. Archiving allows you to restore a profile to a point in the past. Archives are useful if some log files were not available during analysis, if you discover your log files have been corrupted, or if you made changes to the profile that you want to restore. Archive settings are maintained in the Options window. See Restoring profiles to an earlier state on page 55 for details on using archives. To enable archiving: 1. Select the profile to work with, and click Edit. 2. Select the General tab. Click in the Enable Archiving box. The archive is made at regular intervals which have been defined in the Options window. 54

67 Restoring profiles to an earlier state Chapter 3: Using Profiles Profiles that have been archived can be restored to one of the archived versions. For example, if the wtrs.audit file says that there is a date without log file data, you could restore the profile to an earlier version using an archive, place the missing logs in the proper location, and restart the analysis so that reports show activity for the newly added logs files. Monitor the wtrs.audit file for messages like this one to determine when an archive should be used: Sep :33:48: No log data for profile daily on Sunday, February 14, 1999 Figure Profile Archives dialog box. To restore an archive: 1. Select the profile to restore. 2. Select Profile>Archives. The Profile Archives dialog box opens (Figure 3-20). 3. Select the archive that you want to use from the drop-down Available Archives list, and click Restore. Important: When you restore a profile using an archive, all databases and reports created after the archive date are deleted. 55

68 WebTrends Enterprise Reporting Server Specifying a schedule for reporting Use the Report Scheduler dialog box to specify when the profile is analyzed and how often reports are updated. If the program Administrators have chosen, new profiles can be analyzed immediately once they are created. If this is the case, the Reports Scheduler dialog box says that the "Start Immediately" option has been selected. In this case, the time and interval that you specify here determines all subsequent analyses. 1. Select the profile to work with, and click Edit. 2. Select the Scheduler tab. In the Base Time text box, specify when you want reports to begin. 3. Using the Interval drop-down list, select how often to update the report. Figure Scheduler tab Specifying the location for reports The Reporting Server can be configured by the Administrator to use either the built-in web server or an alternate web server for posting reports. If the 56

69 Chapter 3: Using Profiles program has been configured to use an alternate web server and the location can be defined at the profile level, you can use the Report Paths dialog box to specify the location and URL where the reports for this profile are posted. Note: If you change the directory where reports are stored, only new reports appear in this directory. Reports created before the change remain in the original directory. To specify where the reports will be generated, complete these steps: 1. Select the profile to work with, and click Edit. 2. Select the Report Paths dialog box. By default, the location of the built-in web server is displayed. 3. In the Report Directory field, specify the location where reports for this profile are saved. 4. In the Report URL Path, specify the URL where users can view the report for this profile. 57

70 WebTrends Enterprise Reporting Server Figure Report Paths tab Specifying the database directory If accessible, use the Report Database dialog box to specify the location where the profile database should be saved. These databases store all the information needed to create reports, and because of this, they can grow quite large. For this reason, you should place these directories on a drive where you have a large amount of available space. Note: If you change the database location, the Reporting Server reanalyzes the log file from the beginning. This is because a new database is created, and the original databases remain in the old location. 58

71 Chapter 3: Using Profiles To specify a database location, complete these steps: 1. Select the profile to work with, and click Edit. 2. Select the Report Database tab (Figure 3-23). Figure Report Database tab 3. Enter the file path where you want to store the profile database. To maintain separate databases for each profile, use the %PROFILE% macro; the profile name is used in the directory name. Selecting URL Search and Replace definitions URL Search and Replace settings are defined in the Advanced features window. URL Search and Replace definitions can either be applied to all 59

72 WebTrends Enterprise Reporting Server profiles or applied to individual profiles. If the option to select definitions for each profile is enabled, the Advanced Features dialog box is accessible when you work with profiles. URL replacement definitions delete specific identifiers from URLs or replace all unique identifiers with a common string. View the settings for the definition to see how it functions. See URL search and replace definitions on page 161 for more information on using this feature. To specify the URL replacement definitions: 1. Select a profile to work with, and click Edit. 2. Select the Advanced Features tab. Click Configure. 3. Select the URL Replacement tab to view a list of definitions. 4. Select a definition, and click View to view its settings. 5. Click in the check boxes to select the definitions to use. Selecting URL Parameter Analysis definitions URL Parameter Analysis settings are defined in the Advanced Features window. URL Parameter Analysis definitions can either be applied to all profiles or applied to individual profiles. If the option to choose URL Parameter definitions for each profile is enabled, the Advanced Features tab is accessible in the profile window. URL Parameter Analysis definitions associate a page with the parameter used to create it, allowing you to report on dynamically created web pages. See Configuring web server settings on page 148 for more information on using this feature. To specify URL parameter analysis definitions: 1. Select a profile to work with, and click Edit. 2. Select the Advanced Features tab. Click Configure. 3. Select the URL Parameter Analysis tab to view a list of definitions. 4. Select a definition, and click View to view its settings. 5. Click in the check boxes to select the definitions to use. 60

73 Selecting Content Group definitions Chapter 3: Using Profiles Content Group settings are defined in the Advanced Features window. Content Group definitions can either be applied to all profiles or applied to individual profiles. If the option to choose Content Group definitions for each profile is enabled, the Advanced Features tab is accessible in the profile window. Content Groups allow you to group related pages together in one report. The Content Group definition is a set of patterns that identifies the pages that you want to report on as a group. See Configuring web server settings on page 148 for more on this feature. To specify content group definitions: 1. Select a profile to work with, and click Edit. 2. Select the Advanced Features tab, and click Configure. 3. Select the Content Group tab to view a list of definitions. 4. Select a definition, and click View to view its settings. 5. Click in the check boxes to select the definitions to use. Selecting Path Analysis definitions Path Analysis settings are defined in the Advanced Features window. Path Analysis definitions can either be applied to all profiles or applied on a profile basis. If the option to choose Path Analysis definitions for each profile is enabled, the Advanced Features dialog box is accessible in the profile window. A Path Analysis definition specifies the page and the number of paths that you want to track. See Path analysis on page 166 for a detailed explanation. To specify path analysis definitions: 1. Select a profile to work with, and click Edit. 2. Select the Advanced Features tab. Click Configure. 3. Select the Path Analysis tab to view a list of definitions. 4. Select a definition, and click View to view its settings. 5. Click in the check boxes to select the definitions to use. 61

74 WebTrends Enterprise Reporting Server Copying a Profile You can use existing profiles as the basis for a profile using the Copy Profile command. Editing a Profile 1. Select a profile in the list, and select File>Profile>Copy Profile from the Profile menu. A copy of the profile opens. 2. Rename the profile, and make any modifications. 3. Once you have made changes, click OK to close the window. Use the Edit Profile dialog box to modify settings for a profile. If the profile is being used for analysis when you make changes, it is updated when the analysis is complete. Deleting a Profile 1. Select a profile in the list, and click the Edit button. 2. Select the tab with the settings that you want to modify. 3. Once you have made your changes, click OK to close the window. You can remove profiles from the Profile List if they are no longer needed. Stopping Analysis 1. Select a profile in the list, and click the Delete button. 2. Click OK to confirm that you want to remove the profile. You can interrupt processing of a profile using the Stop Analysis/Reporting command. Doing so postpones analysis until the next scheduled interval. 1. Select the profile whose processing you want to stop. 2. Select Profile>Stop Current Cycle. The Stop Current Analysis/ Reporting Cycle window opens (See Figure 3-24). 62

75 Chapter 3: Using Profiles Figure Stop Current Analysis/Reporting Cycle window 3. Click Ok to stop the processing of the profile. Monitoring profile status The Reporting Server maintains a status file for each profile which you can use to monitor the processing of the logs. From the Profile Status window you can view the current state of the profile, the file name and location of the status log file. Use the scroll bar to peruse the profile history. To access the profile status: 1. Select the profile you want to monitor from the Main Console. 2. Select View>Profile Status. The Profile Status dialog box opens (Figure 3-25). 63

76 WebTrends Enterprise Reporting Server Figure Profile status window Changing the profiles displayed in the main console If your profile library has grown to the point that finding the profile to work with has become a chore, you can limit the number of profiles that are displayed through the main console. Or, if you know the name or part of the name of the profile you are looking for, you can search for it here. Tip: You can increase the number of profiles displayed by modifying the MaxGridProfiles option in the wtm_wtx.ini file. 64

77 Chapter 3: Using Profiles. Figure Profile search window To filter the profiles displayed: 1. Select File>Search. The Profile search window opens. 2. Limit the profiles displayed using the following criteria: User Allows you to display only profiles for the user specified. Description Allows you to view profiles whose description matches your criterion. Note: To view the maximum number of profiles allowed, enter * in both fields. 65

78 WebTrends Enterprise Reporting Server 66

79 Using Filters 4 4 How they work Filters let you limit the scope of your analysis and the data by specifying the data you are interested in. The result of the analysis determines what is displayed in your reports. This release of the Reporting Server includes new filtering capabilities: you can filter by visits or hits, and you can now filter on cookies as well as URL parameters. Important: If you have been granted administrative rights, you can add, edit, and modify all profiles, even those created by other users. If you have not been granted administrative rights, many of the options explained in this chapter may not be available to you. How filters are processed You can set up the following types of Include or Exclude filters: Filter visits by the following: Entry Page Referrer For instructions on building visit filters, see See Adding an Include or Exclude Visit Filter on page 68. Filter hits by the following parameters: URL Directory File Browser Cookie Multi-homed domain Day of Week Hour of Day Authenticated user name 67

80 WebTrends Enterprise Reporting Server Return Codes Ad Views and Clicks HTTP Methods Address Adding an Include or Exclude Visit Filter You can add visit filters to any profile. To add a Visit Filter to an existing profile: 1. From the Reporting Server Main Console, select the profile that you want to filter, and click Edit. The Profile Edit window opens. 2. Select the Filters tab. The Filters dialog box opens (Figure 4-1). 68

81 Chapter 4: Using Filters Figure 4-1. Filters dialog box 3. You can add either Visit or Hit filters at this window. Note: You can return to this screen to add or edit additional filters. To add a Visit Filter, click Add beneath the Visit Filters text box. The Filter Type dialog box opens (Figure 4-2). 69

82 WebTrends Enterprise Reporting Server Figure 4-2. Filter Type dialog box 4. Select the type of filter you want to create: Include Filter only log data which matches this criteria will be included in Reporting Server reports for this profile. Exclude Filter log data which matches this criteria will be excluded from Reporting Server reports for this profile. Click Next to continue. The Filter Name dialog box opens (Figure 4-3). 70

83 Chapter 4: Using Filters Figure 4-3. Filter name dialog box 5. Enter the name you want to identify the filter with in the Filter Name text box. 6. Select one of the following options: Include/Exclude all activity include all visits in this profile s report. Include/Exclude activity based upon limit the visits included in this profile s report to the selected Active Visit Filter Parameters. Select from the following Active Visit Filter Parameters to build your filter: Entry Page Referrer 71

84 WebTrends Enterprise Reporting Server 7. Click Next to continue. 8. If you selected Include/Exclude all activity, go to step Step 16 to complete building your filter. 9. If you selected Include/Exclude activity based on, continue with one of the following paths: If you selected Entry Page, the Entry Page dialog box opens (Figure 4-4). Continue with Step 10. If you selected Referrer, the Referrer dialog box opens (Figure 4-5 on page 74). Continue with Step 13. Figure 4-4. Entry page dialog box 10. Use the Entry Page parameter to include visits based upon the page at which they entered your site. Enter an expression that describes 72

85 Chapter 4: Using Filters the entry page(s) in the Page Expression text box. You may use asterisks(*) as wildcards. 11. Select the Regular Expression check box if you want to use regular expressions. Click Test to verify your entry before continuing. Note: Click the Help button on this page for examples of page expressions. 12. If you want to filter on URL Parameters, select one of the following options: To add an URL parameter: a) Click Add to add an URL parameter. The URL Parameter page opens. b) Enter your settings, and click OK to continue. To edit an existing URL parameter: a) Select the parameter you want to edit. b) Click Edit. The URL Parameter page opens. c) Enter your changes, and click OK to continue. To delete an existing URL parameter: a) Select the parameter you want to delete. b) Click Delete. The URL parameter is removed from the list. Click Next to continue. Continue with Step

86 WebTrends Enterprise Reporting Server Figure 4-5. Referrer dialog box 13. Select which type of referrers you want to either include in or exclude from your filtering from the Referrer drop-down list. Choose from: All Referrers No Referrer http: URLs file: URLs mail: URLs ftp: URLs User Defined Referrer The default setting is All Referrers. 74

87 Chapter 4: Using Filters 14. Unless you have selected All Referrers or No Referrers, enter the URL in the Referral text box. Note: Click the Help button on this page for examples of referring URLs. 15. Click Next. Continue with Step The Summary page opens (Figure 4-6). The details of your current filter settings are displayed. Click Back to edit your settings, or Finish to complete building your filter. Figure 4-6. Summary page 75

88 WebTrends Enterprise Reporting Server Adding an Include or Exclude Hit Filter You can add hit filters to any profile. To add a hit filter to an existing profile: 1. From the Reporting Server Main Console, select the profile that you want to filter, and click Edit. The Profile Edit window opens. 2. Select the Filters tab. The Filters dialog box opens (Figure 4-7). Figure 4-7. Filters dialog box 76

89 Chapter 4: Using Filters 3. You can add either Visit or Hit filters at this window. To add a hit filter, click Add beneath the Hit Filters text box. The Filter Type dialog box opens (Figure 4-8). Note: You can return to this screen to add or edit additional filters. Figure 4-8. Filter Type dialog box 4. Select the type of filter you want to create: Include Filter only log data which matches this criteria will be included in Reporting Server reports for this profile. Exclude Filter log data which matches this criteria will be excluded from Reporting Server reports for this profile. Click Next to continue. The Filter Name dialog box opens (Figure 4-9). 77

90 WebTrends Enterprise Reporting Server Figure 4-9. Filter name dialog box 5. Enter the name you want to identify the filter with in the Filter Name text box. 6. Select one of the following options: Include/Exclude all activity include all visits in this profile s report. Include/Exclude activity based upon limit the visits included in this profile s report to the selected Active Hit Filter Parameters. Select from the following to build your filter: URL Directory File Browser 78

91 Chapter 4: Using Filters Cookie Multi-homed domain Day of Week Hour of Day Authenticated user name Return Codes Ad Views and Clicks HTTP Methods Address Note: For full descriptions of these visit parameters, see Filter Parameter Descriptions on page Click Next to continue. 8. If you selected Include/Exclude all activity, go to step Step 16 to complete building your filter. 9. If you selected Include/Exclude activity based on, the wizard opens one dialog box for each parameter you selected. Enter your settings on each page, clicking Next to continue. Note: You can click Back at any time during this sequence to make changes to the hit filter you are building. 10. The Summary page opens (Figure 4-10). The details of your current filter settings are displayed. Click Back to edit your settings, or Finish to complete building your filter. 79

92 WebTrends Enterprise Reporting Server Figure Summary page Editing a Filter To edit a filter, complete these steps: 1. From the Reporting Server Main Console, select the profile containing the filter you want to edit, and click Edit. The Profile Edit window opens. 2. Select the Filters tab. The Filters dialog box opens (Figure 4-11). 80

93 Chapter 4: Using Filters Figure Filters dialog box 3. Select the filter you want to edit from either the Visit Filters or Hit Filters text box. Click Edit. 4. The Filter Wizard opens. Make your changes, and click OK to save your settings. The updated filters are now active in the profile. Note: Reports generated on this profile will not reflect these updated filter settings until the next analysis. 81

94 WebTrends Enterprise Reporting Server Deleting a filter To delete a filter, complete these steps: 1. From the Reporting Server Main Console, select the profile containing the filter you want to delete, and click Edit. The Profile Edit window opens. 2. Select the Filters tab. The Filters dialog box opens (Figure 4-12). Figure Filters dialog box 3. Select the filter you want to delete from either the Visit Filters or Hit Filters text box. Click Delete. The filter is removed from the profile. 82

95 Chapter 4: Using Filters Filter Parameter Descriptions Visit Filter Parameters Entry Page Use the Entry Page filter element to include or exclude entire visitor sessions based upon the first page viewed. An entry page is the first item that the visitor requests in a session. The item could be an image, a document, or a file. For example, you have an ad banner on Yahoo! that links users to the page / ads/yahoo_ad.htm. (This page might simply redirect users to your home page.) You could create an Include filter with the entry page element set to / ads/yahoo_ad.htm to determine the number of users clicking through from that banner. The following table provides examples of how to format an Entry Page filter. Keep in mind that the Entry Page filter filters entire user sessions, not individual hits. Table 4-1. Entry Page filter examples Example /browser.htm browser.htm /ads/*.htm /ads/*.* ad.* Explanation Filters any session starting at browser.htm in the root directory. Filters a session browser.htm from any directory. Filters any.htm file in the /ads directory. Filters any file in the /ads directory. Filters any file named ad from any directory. You can also use wildcards to match strings. For example, if the filter string contains no file or extension, and has exactly one asterisk (*), which appears at the end of the string, a string match against the record path is performed. Referrer Use the Referrer filter to include or exclude entire user sessions based on the referring URL. A referring URL is the link that the user came from. This filter helps you identify the quantity and quality of users coming to your site from other sites or from a specific Internet advertisement. 83

96 WebTrends Enterprise Reporting Server Whereas other filters deal with hits, the referrer filter deals with user sessions to determine where your users are coming from. A typical user session is 30 minutes. The default for the Referrer Include filter, All referrers, filters all hits with referring data regardless of site. The default for the Referrer Exclude filter, No referrers, filters only hits without any referring information. A filter entry of filters any hits prefixed by Table 4-2. Examples of search engine filters Example *.referrer.com* *referrer* page.htm page.htm* *.referrer.com/ page.htm* Explanation Filters anything coming from Hits from ftp:// are not filtered. Filters Filters ftp.referrer.com, but not things such as or Filters anything with referrer in the name referrer.com, referrer, etc. Filters only references from page.htm at the site. Filters page.htm, page.html, page.html2, etc. from the root of the domain. Filters page.htm or page.html from any referrer.com domain (such as search.referrer.com or ftp.referrer.com). 84

97 Chapter 4: Using Filters Hit Filter Parameters Directory or URL Use the Directory filter to include or exclude the activity of a specific directory. The default for an Include Directory filter is to include all directories starting at the root directory, indicated by a slash (/). There is no default for the Exclude Directory filter. If you want to include or exclude all subdirectories starting with the directory you specify and proceeding down, select the Include/Exclude Subdirectories check box. Select the Case Sensitive check box if you want to look for exact case matches. Note: Because most servers require case-sensitive (upper or lower case) matches, be careful to specify the exact case you want to look for, and check the Case Sensitive box. The default for both include and exclude files filters is to activate the subdirectories box (indicated by a check in the Include/Exclude Subdirectories box). Therefore, if you created an Exclude filter for the /Images directory, the subdirectories are automatically excluded. Or if you create an Include filter for a directory, the subdirectories are automatically included in the filter. Use wildcards to specify multiple directories, or separate directories with a space. Put quotation marks around directories containing spaces or commas. For example: "/logo graphic". Table 4-3. Directory Filter examples Example /images "/image files" "/image files" / intranet /graphics /*graphics Result Specifies the directory /images is filtered and all subdirectories therein, if Include Subdirectories is checked. Specifies the long directory, /image files. Specifies the following directories: /image files, /intranet, and /graphics. Specifies any first-level directory whose name ends in graphics, such as /bitmap graphics, but not /intranet/ bitmap graphics. 85

98 WebTrends Enterprise Reporting Server Example /*/graphics /graphics /*/ graphics /*/*/ graphics /*graphics*/ Result Specifies all second-level directories named /graphics, such as /home/graphics and /intranet/graphics, but not / home/sales/graphics. Directories such as /home/ graphics/logos, are specified by this example only if Include Subdirectories is checked. Specifies all first, second and third level directories named graphics, such as /graphics, /home/graphics, and /home/sales/graphics. Subdirectories of these, such as / home/graphics/logos, and /home/sales/graphics/logos/ specials would be included only if Include Subdirectories is checked. Specifies all first level directories with names containing graphics, such as /graphics, /graphics files, and /bitmap graphics. Note: Remember to put quotation marks around directories containing spaces or commas. File Use the File filter to include or exclude specific files. Enter the file name or extension in this field, or click the down-arrow to select a file type from the list. The default for an Include File filter is to include all files, indicated by *.*. There is no default for an Exclude File filter. Use wildcards to specify file names or extensions, such as all HTML files (*.HTM) or all GIF files (*.GIF). Specify several file types at once by inserting a space between each file type. A check in the Case Sensitive box means that you want to look for exact case matches (upper or lower case). Note: Many servers are case-sensitive, be sure to enter your filter exactly as what you want to look for in the log file, and check the Case Sensitive box. Table 4-4. File Filter examples Example help.htm *.gif *.bmp Result Filters the file help.htm. Filters bitmap (.bmp) and gif (.gif) files. 86

99 Chapter 4: Using Filters Example help*.html help*.* marketing.htm "marketing help.htm" "marketing leads.htm" Result Filters all html files whose name begin with help. Filters all files whose name begin with help, regardless of type. Filters the files marketing.htm, marketing help.htm, and marketing leads.htm. Browser Use the Browser filter to either include or exclude a browser, spider or robot from the analysis and reporting. You can filter any browser if you know how it appears in the Agent field of the log file. Use a space to separate multiple browsers. Put quotation marks around browser names that have spaces. You cannot use wildcards for browser filters. Table 4-5. Browser filter examples Example Mozilla/4. Mozilla/3.1 MSIE Microsoft Internet Explorer/ Result Filters any activity that matches Netscape Navigator 4. or Netscape Navigator 3.1. Filters any activity that matches any version of Internet Explorer. Note: You cannot use wildcards (*) in a browser filter. Webhouse Builder assumes that there are wildcards at either end of each browser entry when comparing it to the agent field in the log file. Filtering for Netscape Navigator may not return accurate results because many browsers identify themselves as Netscape Navigator. Cookie A cookie is a file sent with the page requested from the server to the visitor, and stored on the visitor s system. It uniquely identifies previous visitors to 87

100 WebTrends Enterprise Reporting Server your site the next time they return. The cookie filter is a session filter-when the cookie for a visitor session is matched or not matched, depending on whether the filter is include or exclude-the entire visitor session is included or excluded. You can use regular expressions in building this filter. Multi-homed domain Use the Multi-Homed Domain filter if your log file contains activity from more than one domain. Specify the domains you want to include or exclude. For example, if your log file contains activity from domains and and you want to store activity for you would create an Include file and enter Note: This filter only applies to multi-homed log files. To filter multiple domains, separate your entries with a space. Day of Week Use the Day filter to include or exclude specific days of the week. For example, if you create an Include Days filter, a check indicates the log file activity must match the days specified in order to stored in the database. Hour of Day Use the Hour filter to include or exclude hours of the day. The default for the Hour Include filter is All. The default for the Hour Exclude filter is None. Any activity that is within the hour range that you specify through the Between...And range is filtered. Note: Enter the hours in military format (twenty-four hour clock). Table 4-6. Hour filter examples Example Result Between 12 and 17 Filters any activity that took place between 12 p.m. to 5 p.m. Between 20 and 6 Filters any activity that took place between 8 p.m. to 6 a.m. 88

101 Authenticated User Name Chapter 4: Using Filters If you have an intranet site or a web site that requires visitors to log on with a user name and password, then you can use the Authenticated User Name filter to include or exclude authenticated users from this profile. Enter the name that you want to filter for. Put quotation marks around names that contain spaces. Refer to the examples that follow for formatting tips. Check the Case Sensitive box if you want to look for exact case matches. Note: Because most servers are case sensitive, be sure to enter your filter exactly as the data appears in the log file, and check this box. Table 4-7. Authenticated User Name filter examples Example "Jane Smith" "Bob Smith" "Mike Macintosh" "John Hill" Result Filters any activity that matches Jane Smith. Note: If the user name you are filtering contains a space, use quotation marks around the user name as shown here. Filters any activity that matches these user names. Return Codes Use the Return Code filter to specify the types of results you want to include or exclude. For example, if you are creating an include filter and you want to only report on successful hits, select Success Only from the list. You can select one of the common returns codes provided in the list, or type another numeric result code in this field. Note: The default, All Return Values, is indicted by an asterisk (*) in the field. The predefined list includes the following: (All Return Code) Success Only Failed Only 89

102 WebTrends Enterprise Reporting Server Success, OK (200) Success, Created (201) Success, Accepted (202) Success, Partial Information (203) Success, No Response (204) Success, Redirected (300) Success, Moved (301) Success, Found (302) Success, New Method (303) Success, Not Modified (304) Failed, Bad Request (400) Failed, Unauthorized (401) Failed, Payment Required (402) Failed, Forbidden (403) Failed, Not Found (404) Failed, Internal Error (500) Failed, Not Implemented (501) Failed, Overloaded Temporarily (502) Failed, Gateway Timeout (503) Ad Views and Clicks This filter lets you produce reports based on a specific Web site advertisement's activity to distribute to a client. If you want to track activity related to a specific advertisement on your site, for example, you can define the ad using the ad views and clicks tool, and then filter all activities related to the ad. 90

103 HTTP Methods Chapter 4: Using Filters Select which HTTP methods you want to include in your Include or Exclude filter: GET POST PUT HEAD UNKNOWN Address Use the User Address filter to include or exclude hits coming from specific domains, subnets, or IP addresses from the results of this profile. For example, you can create a filter that excludes all activity from your own domain. The default, All User Addresses, is indicated by an asterisk (*) in the field. 91

104 WebTrends Enterprise Reporting Server 92

105 Using Intranet Configuration 5 5 About Intranet Configuration The Reporting Server includes a company database which translates domain names into organization names and geographic information and makes this information available in reports. Within large organizations, certain sub-nets or ranges of IP addresses usually represent a department, area or location of an organization, but they are not represented in the company database. This is where the Intranet Configuration feature steps in. Note: See Running from the Command Line on page 177 for details on defining ad views and clicks from the command line. The Intranet Configuration feature lets you provide a more detailed breakdown of your organization s domain name. You can define multiple domains which specify an area of your organization by country, state, city, department, or even individual workstations. Once you have added this information with the Intranet Configuration tool, it is automatically included in your report profile data. As with any web site, having accurate and up-to-date statistics and access to information is essential. Intranet Configuration helps you manage your site by reporting the what, where and when of user and department activities: What pages are users accessing and how much time are they spending on them? What departments are accessing your Intranet and when? Where are your users and departments located? What operating systems are used most widely within the organization? What browsers are used? What are the most active and inactive days and times? What forms are users submitting? What scripts are run and when? 93

106 WebTrends Enterprise Reporting Server Scenario: Creating definitions for your organization In this scenario, you are the Webmaster for an international corporation. The good news is that your company Intranet is extremely popular; the bad news is that you need to provide statistics about which departments are using the Intranet and how they are using it. No problem! Once you have created Intranet definitions for each of your departments (you can also define individual machines or entire offices) with the Intranet Configuration tool, this information is automatically stored with other traffic data included in your reports. Specifically, this information appears in the Most Active Organizations graph and table, and is used for the geographic information in the graphs and tables relating to States, Cities and Countries. Adding an Intranet Domain Follow these steps to setup the departments that you want to track: 1. Select Configuration > Advanced Features > Intranet Configuration from the tool bar. The Intranet Configuration dialog box opens (Figure 5-1). Figure 5-1. Intranet Configuration dialog box 2. Click Add. The Add New Intranet Configuration dialog box opens (Figure 5-2). 94

107 Chapter 5: Using Intranet Configuration. Figure 5-2. Add New Intranet Configuration dialog box 3. In the Intranet Domain field, enter the domain name of the department or division of your organization to be listed in your report (for example, marketing.xyz.com). 4. In the Description field, enter the descriptive name of the organization or department as you want it to appear in reports (for example, Marketing Dept.). 5. In the City field, enter the location of the department or division. Select a State from the drop-down list. Select a Country from the drop-down list. (This geographic information is used to produce the geographic tables and graphs in reports.) 6. In the IP Address/Pattern field, enter the IP address, domain name, or range of IP addresses, as they appear in your Web server log file (for example, marketing.xyz.com). Note: Because pattern matching for Intranet Configuration entries are performed after DNS lookups, you only need to use an IP address in this field if neither your Web server nor the Reporting ServerWeb Data Warehouse is converting IP addresses to domain names. 95

108 WebTrends Enterprise Reporting Server 7. When you have finished, click OK to save the new Intranet domain information and return to the Intranet Configuration window. The new Intranet domain and corresponding description appear in the Intranet Configuration window. 8. Repeat the previous steps to define an Intranet domain for each department. Note: If you want to edit an existing Intranet domain, select it in the Intranet domain list in the Intranet Configuration window, and click Edit. To delete an existing Intranet domain, highlight it in the Intranet Configuration window, and click Delete. 96

109 Using Ad Views and Clicks 6 6 Using the Ad Views and Clicks feature, you can determine the number of visitors to your web site who view or click on a particular ads. With this feature you can produce advertising reports for each of your clients. If you are selling advertising space on your web site, for example, you can collect traffic statistics to help determine pricing schedules. If you use the Advertising filter in your profile, you can show traffic patterns for a specific advertisement (such as busiest time of the day or busiest day of the week), as well as demographic information (such as the top viewing or clicking organizations or countries). See Running from the Command Line on page 177 for details on defining ad views and clicks from the command line. Tip: For the most effective reporting results, use the Advertising Summary memorized report settings, which includes all of the tables and graphs relating to advertisement tracking. You can track exit URLs using Ad Views and Clicks by creating an Ad View for each advertisement that you want to track. To track the effectiveness of web site advertisements that you have on someone else s site, see Referrer on page 83. Tracking Internet Advertising Suppose that your site is booming and advertising is selling like mad. Using Ad Views and Clicks to create reports that show activity for each of your client s ads, including views, clicks, click-through rate, and more. The following instructions walk you through the process of: Defining an advertisement to track. Adding a profile with a filter to track this ad. 97

110 WebTrends Enterprise Reporting Server Defining an advertisement to track When using Ad Views and Clicks, your first step is to define the ads that you want to track. To define an advertisement to track: 1. From the Main Console, select Configuration > Advanced Features> Advertising Views. The Ad Views and Clicks Configuration dialog box (Figure 6-1) opens. Figure 6-1. Ad Views and Clicks Configuration dialog box 2. Click Add, and the Add New Ad View dialog box (Figure 6-2) opens. 98

111 Chapter 6: Using Ad Views and Clicks Figure 6-2. Add New Ad View dialog box 3. In the Description text box, type a descriptive name of the web site ad. The text you provide here will identify this ad all reports. For our example, type: IBM Laptop Advertisement 4. In the Ad View File Name text box, type the file name or text string identifying the advertisement view you want to track. Important: You must type this name or text string exactly as it appears in the web server log file. If you specify multiple components, put spaces between each component name. (Each component acts as a logical Boolean AND to the other components.) The following examples will help you determine which you should type. Example 1: Tracking Statically Linked Ads For this example, we ll track the IBM advertisement which is statically linked in other words, it's not retrieved through CGI scripts, but called straight using the <IMG SRC> HTML tag. 99

112 WebTrends Enterprise Reporting Server When a browser hits your site and sees the link to the image, it asks the server for that image and generates a log entry on the server that looks something like this:... "GET /images/ibm_ad.gif" Since the filename ibm_ad.gif is unique to just IBM s advertisement, it s sufficient to type the file name itself into the Ad View File Name text box to accurately track views of this ad. Example 2: Tracking Ads Sent Through Scripts In this example, you have an automated CGI script that delivers ads to a browser. The advertisement image, ibm_ad.gif, is sent to the client using a CGI script that contains an advertisement ID number rather then a filename. The only way to retrieve this particular ad is to make an image link off your view page to a CGI script, which has a URL looking something like this: When a web browser sees this URL, it asks the server for that image and generates a log entry that looks like:... "GET /cgi-bin/showad.cgi?ad=123456" Since the CGI script returns the image, the file name is irrelevant. For our ad view we want to use text specific to this advertisement only in this case, the ad ID string for the CGI script. Consequently, we'll type: showad.cgi ad= in the Ad View File Name text box. This works because the only time this combination of text shows up in the log file is when retrieving the IBM advertisement image. In the Ad Click ID String text box, type the text identifying the advertisement click you want to track. This must be the exact text (not case-sensitive) from the web server log file. You can specify multiple components separated by spaces. Since only the log file Action field is scanned (usually Get or Post statements) for the text that you specify, the click must create an entry in your log file. For example, if a visitor clicks on an ad which takes him or her out of your site directly via a URL, that click is not logged in your log file. In order to be able to track ad clicks, you must implement some type of server-side scripting (for example, CGI, Perl, or ASP) to 100

113 Chapter 6: Using Ad Views and Clicks perform a redirect to the destination URL. A very common Perl script is redir.pl. To summarize, if you have a GIF file on your site that links to IBM s site through redir.pl, the settings in the Ad Views and Clicks dialog box would break down like this: In the Description text box, you would type: IBM Laptop Advertisement In the Ad View File Name text box, you would type: ibm_ad.gif In the Ad Click ID String text box, you would type: url= because when a visitor to your site clicks on the ad, the following information is recorded in your log file: GET /cgi-bin/redir.pl?url= 5. When you have finished, click OK to save the new advertisement definition and return to the Ad Views and Clicks Configuration dialog box. 6. Repeat step 2 through step 5 to add Ad definitions for each of your clients 7. Click Close to exit the Ad Views and Clicks Configuration dialog box. Note: To edit an existing advertisement definition, select it in the Ad Views and Clicks Configuration dialog box and click Edit. To delete an existing advertisement definition, select it in the Ad Views and Clicks Configuration dialog box and click Delete. Adding a profile and filter for an advertisement Once you have completed your advertisement definitions, create profiles to track each client s advertisement activity. To add a profile and filter for an ad: 1. Click New. 2. In the Description text box, type a description to identify this profile as one that tracks the advertisement activity for your client (for example, IBM Advertisements). This description will appear in the 101

114 WebTrends Enterprise Reporting Server profile list, as well as in the title of reports that are based on this profile. 3. In the Log File URL Path text box, type the location of your web server log. In this example, there is a mounted drive to the web server, so choose file from the drop-down list, and the type the path to your log file. You can click Browse to search for the exact location of the file. 4. Click Next to skip the DNS Lookup dialog box. This information is not needed for this profile. 5. The Report Template dialog box opens. The template defines the report sections that are included in the report. 6. Click Next, and the Home Page dialog box opens. This information is not necessary for this profile. Click Next to continue. 7. The Scheduler dialog box opens. In the text boxes, type when you want reporting to begin, and how often the data should be updated. 8. Click Next, and the Filters dialog box opens. Select the default Include Everything filter, and click Delete to remove it. 9. Click Add to create a new filter, and the Filter Type dialog box appears. Select the Include check box, and click Next. 10. The Filter Title dialog box opens. Type a title for the filter in the Title text box. 11. Select Include Only Activity Based Upon, and then select the Advertising check box. 12. Click Next, and the Advertising dialog box opens. Select the IBM ad from the list. 13. Click Next to display the Summary dialog box where you can review your filter criteria. 14. Click Finish. Repeat this procedure to add a separate profile for each of your clients. The URL for the report is displayed in the Main Console. 102

115 Building Reports 7 7 Reports and Profiles Reporting Server reports are include information specified in Profiles (see Using Profiles on page 25.) Profiles define the data to be gathered, while the report settings covered in this chapter determine when the reports are generated, and how this data is presented, including the colors, fonts, format and storage location for reports. The reports can be viewed through Netscape Navigator or Microsoft Internet Explorer. Additional configuration options for administrators including editing report templates can be found in Configuring Program Options on page 123. Important: If you have been granted administrative rights, you can add, edit, and modify all profiles, even those created by other users. If you have not been granted administrative rights, many of the options explained in this chapter may not be available to you. This chapter includes: How reports are built on page 104. Includes a step-by-step example of creating a report using a sample profile with Product and Marketing settings. Pre-generated and on-demand reporting on page 110. A discussion of the two types of reports you can build. Navigating reports and profiles, page 112 to page 114. Efficiency tips for working with past reports and profiles, as well as viewing profile histories. Working with Report Templates on page 116. Customizing reports, creating new templates, changing report colors and styles. Report data and Help Cards on page

116 WebTrends Enterprise Reporting Server Information on updated and new Reporting Server reports. Note: If you are already familiar with the Reporting Server and would like more indepth instructions on how to creating profiles, see Using Profiles on page 25. How reports are built Understanding these main concepts, and how they interrelate, is essential to using the Reporting Server effectively. How Reporting Server works The Reporting Server analyzes data from your web server s log file to analyze activity on your site. Through a profile, you specify the location of the log file, how it should be analyzed, and the reports to generate. see Understanding log files on page 104 for details on log files. Understanding log files When someone connects to your site, the event is stored by the web server in a log file. Log files record data such as the user, the protocol used to access the page (such as HTTP or FTP), what they did, the platform used (such as UNIX, NT, Windows 98), the search engine (such as Yahoo or Lycos), keywords, date and time, and much more. The Reporting Server uses the data from this log file to create reports. Log files typically have a.log extension and are located in various directories, depending on the web server that you use. (NT) Microsoft IIS c:\winnt\system32\logfiles\ex log (NT) Netscape c:\netscap\servers\http-[server name]\logs\ex log Sample Log File: Common and Combined (Extended) Format The NCSA recognizes two log file format standards--the common and combined (extended) formats. The following is a sample line from a "common" log file: - [16/Jan/1999:10:36: ] "GET /dept/ argguides/dwsg/ jpg HTTP/1.0"

117 Chapter 7: Building Reports The "combined" or "extended" log file format is similar to the common log file format with the addition of the referrer and agent fields at the end of the line in quotation marks. The following is a sample in combined format: [12/Jan/1996:19:35: ] "GET / HTTP/1.0" " search?p=trends%20internet" "SPRY_Mosaic/v8.32 (Windows 16- bit) SPRY_package/v4.00" In this example, the referrer is search?p=trends%20internet, the agent is SPRY_Mosaic/v8.32, and the platform is Windows 16-bit. The following table defines each of the fields in the sample log file lines. Table 7-1. Field definitions for sample log file Field # Field Name Description Field 1 User Address The numeric IP address or domain name of the user accessing the site. Field 2 Rfc931 This field is used to log the domain for multihomed web servers. Field 3 User Authentication User name, if required. Field 4 Date/Time The date and time the user accessed the site. Field 5 GMT offset The number of hours from GMT (if this is it is logged in GMT time). Field 6 Action The particular operation (i.e., Get or Post ) of the hit (this must be in quotes). Field 7 Return Code The return code for the action tells whether it was successful and why. Field 8 Size The size of the file sent. Field 9 Referrer: The URL which linked the user to your site. Field 10 Browser/ Platform The Web browser and platform used by the visitor to your site. Understanding profiles Profiles specify how the log file should be analyzed and which activity you want to report on. Through the profile you define the location and log file type, 105

118 WebTrends Enterprise Reporting Server any activity you want filtered, and whether or not IP resolution should be performed. Reporting Server analyzes the log file and uses the result to create reports. Profiles are covered in Using Profiles on page 25. Understanding Product and Marketing definitions Product and Marketing analysis and reports are based on two definitions that can be applied to any Web Traffic Analysis profile. They are explained briefly below: Product definitions are set up to track the forecasted revenue that specific product pages on your web site will potentially generate. In the context of a product definition, "product" loosely describes any product that you may be selling, an idea that is worth something to your company, an intellectual product, etc. Marketing campaign definitions are set up to define your marketing campaign information. This information includes referrer or entry pages, cost and duration of the campaign, an image to represent it, etc. Setting up the Reporting Server New to the Reporting Server? Use this section to get a sense of the steps involved in taking the product from a CD-ROM sitting in your drive to running reports. 106

119 Chapter 7: Building Reports Build a Report For This Step Refer To 1. Install the software. Installing and Setting Up on page Review the sample profile. The content of a profile are the key to successful reporting. Profiles identify the web server log file type, the location of the log file, how the data should be analyzed, and the reports you want to create. Make note of the dialog boxes you may want to disable for non-administrators. You may want to give the responsibility of creating and maintaining profiles to Administrators only, making nonadministrators lives much easier; all they ll need to do is log in and select their reports. 3. Run a Complete Summary report on the sample profile. Make note of any tables you want to exclude, or those you d like more or less information. Later you can reflect these changes in the profile. Consider the color scheme of the style used in the report. You can change the colors for the Report Template in the Template dialog box. 4. Create profiles for the web server logs you want to analyze. If you are providing customized reports for different users, you will create a profile for each. Tell your users where they can view reports. 5. Review the Options settings. Many default settings for profiles are located here. Decide whether you want nonadministrators to have access to the optional dialog boxes. Using Profiles on page 25 On-demand reports on page 111 Using Profiles on page 25 Defining General options on page

120 WebTrends Enterprise Reporting Server For This Step 6. Create user accounts for anyone who is going to use the Reporting Server for viewing reports or managing any aspect of the program. For each user, determine the permissions you want to give. 7. Modify the Report Templates or create your own if needed. Refer To Creating a user account on page 173 Working with Report Templates on page 116 To run the Reporting Server through the remote interface, the analysis engine and the remote interface must be started. Note: You can also control all aspects of the Reporting Server from the command line. see Running from the Command Line on page 177 for details. Complete these steps to create a sample report: 1. Enter the path to the installation directory and type: wtrs The program starts. 2. Type: wtrs -start The Reporting Server analysis engine starts. 3. Type: wtinterface -start And the remote interface for the Reporting Server starts. 4. Open your web browser (Netscape Navigator or Internet Explorer). 5. Enter the IP Address or domain name for the machine where the Reporting Server is installed followed by the port specified during installation. For example, 6. Click the Login button. 7. Enter your system user name and password for machine where the Reporting Server is installed or the user name and password you 108

121 Chapter 7: Building Reports were given to run the program. To change the user name and password, see Setting User Access on page The Remote Interface Main Console opens. 9. Highlight the profile you want to report on, and click Edit. 10. From the Main Console, select the profile you want to report on from the Profile Description column. Double-click the name, or click the Edit icon on the tool bar. The Profile Edit window opens. 11. Review the settings on the tabbed views, especially Report Header, Report Template, Reporting Method, and Reports. 12. When you have familiarized yourself with the components of a product profile, click OK. The window closes. You are returned to the Reporting Server Main Console. 13. To view the report you just created, click the Reports icon on the Main Console toolbar. The Report Viewer opens, displaying the report for the selected profile. Select the report chapters that you want to view from the Table of Contents section. Use the Table of Contents for browsing report data Figure 7-1. Report Viewer 109

122 WebTrends Enterprise Reporting Server Pre-generated and on-demand reporting You can configure the Reporting Server to run either Pre-generated or Ondemand reports. There are advantages to each report type. Pre-generated reports Pre-generated reports are those that are created and saved when the profile is processed so that they are available for users immediately simply by going to the URL where the report is posted. The Reporting Server program need not be running for users to access reports. Decide at profile creation time what the reports for the profile should include. see Preparing to analyze web site activity on page 26 for details. Note: Reports for new profiles are available immediately if the Start Initial Analysis Immediately... option in the Scheduler dialog box was activated. Otherwise, reports are available at regular intervals beginning at the scheduled start time. see Defining a schedule for processing on page 143 for details. On-demand reports On-demand reports are those that are created as the report user requests them. Doing so dedicates time to analysis and other program processes. Because on-demand reports are created as they are requested, disk space is saved. This method offers some flexibility not available in pre-generated reporting. For example, at report time, you can decide the tables and graphs to include, the number of items to include in report tables, and the style sheet to use. Profiles that have been set up to create pre-generated reports at the time the profile is processed can be viewed through your browser in the Report Viewer. To view reports for a profile: 1. Select the profile you want to report on from the Main Console. 2. Click Reports. The first page of the report is displayed in the Report Viewer. 110

123 Chapter 7: Building Reports Use the Microsoft Word or Excel buttons to convert the HTML report. Loads the profile s home page. Links indicate the report intervals that are available. Table of Contents lists the chapters of the report. Click an item to view it. Status frame displays the report type and the dateand time-ranges reported on. Use the navigational arrows to scroll through the report. Click to change the graph type. Click? to view a help card for the report. The report frame displays the report chapter selected in the Table of Contents for the interval selected Figure 7-2. First page of pre-generated report 3. Use the Report Calendar to select the dates or date range to view. If a report is available for a day or interval, a link appears in the calendar. The selected interval is highlighted in blue. 4. Use the Table of Contents to select the report chapter to view. Note: You can change the graph style by clicking the graph buttons that appear above the report. On-demand reports Some profiles may have been set up to run on-demand reports; reports generated only when the user requests them. Before you generate each report, you can modify the following settings: HTML page title lookup Tables and graphs to include Report style and language 111

124 WebTrends Enterprise Reporting Server Report format Report header content To generate a on-demand report: 1. Select the profile you want to report on from the Main Console. 2. Click Reports. The Report Viewer opens displaying the report calendar. Links indicate the report intervals that are available. Click a link to generate the report. When the report generation is complete, the report frame displays the report chapter for the interval that you selected. Table of Contents lists the chapters of the report. Click an item to view it. Click to change the graph type. Using the job queue Figure 7-3. First page of on-demand report 3. Use the Report Calendar to select the dates or date range to generate. If a report can be generated for a day or interval, a link appears in the calendar. The report is generated and displayed. 4. Use the Table of Contents to select the report chapter to view. You can view the profiles currently being processed and those waiting to be processed in the Job Queue. You can remove a profile, from the queue or stop processing at this dialog box. 112

125 Chapter 7: Building Reports Removing an item from the queue only stops processing temporarily; it returns at the next scheduled interval. Figure 7-4. Job Queue dialog box To view the Job Queue: 1. From the main console, select View > Job Queues. The Job Queue dialog box opens (Figure 7-4). The Current Analysis Queue lists the profiles that are currently being processed. Because the Reporting Server makes use of multi-threaded processing, several profiles may be analyzed at once. To interrupt processing, select a profile and click Stop. When a profile is stopped, it reenters the queue at the next scheduled time. 113

126 WebTrends Enterprise Reporting Server The Waiting Queue lists the profiles next in line for processing. The profile that will be processed next appears first in the list. Select a profile and click Remove to remove it from the queue. It will return at the next scheduled interval. Click Refresh to update the job list, if needed. 2. When you have completed browsing or editing the pending jobs, click Close. Viewing profile history Use the Profile Home Page to view a history of reports generated for the profile selected. Here you can view the last time the profile was analyzed and the total number of reports generated for each report type. 1. Select the profile you want to report on from the Main Console. 2. Click the Report button, and the Report Viewer opens displaying the Profile Home Page (Figure 7-5). Figure 7-5. Profile Home Page 3. Click a link in the calendar to view the report. 114

127 Chapter 7: Building Reports Converting reports to Microsoft Word or Microsoft Excel To convert Reporting Server reports to a format more easily sourced for presentations or other documentation, you can convert the Reporting Server HTML report to Microsoft Word or Excel via the Report Viewer. This conversion is possible if the workstation where you are running the Remote Interface meets the following criteria: The System requirements on page 5 must be met. Microsoft Office must be installed on the workstation. The "HTML, Microsoft Word, or Microsoft Excel" format must be activated in the Report Template for the profile. See Step 7, page 118. The first time you select the MS Word or MS Excel option, the WebTrends conversion installation package is automatically downloaded. The installation package contains the files needed to convert HTML reports to Word or Excel format. Once the converter files are on your system, the HTML report is downloaded to your system and converted to the format you specified. Note: You may be asked to provide your user name and password during the installation of the MS Word installation package. To convert your reports to Microsoft Word or Excel, complete these steps: 1. Select the profile that you want to report on. 2. Click Report on the toolbar. 3. Click the Microsoft Word or Excel icon that appears in the Report Calendar. The HTML report is converted to Microsoft format you selected. Figure 7-6. The Report Calendar 115

128 WebTrends Enterprise Reporting Server Working with Report Templates You can tailor your reports using Report Templates. A report template defines the colors, language, and content of the report. The Reporting Server provides a set of report templates which are customizable. You can also create your own templates. As an Administrator, you can apply the template on a profile basis, or define this option globally and hide it from the user. Customizing reports If you have been granted Administrative rights, you can define the following report settings by selecting the Style/Language tab from Templates: Modify the color scheme. (See Changing the report color on page 119.) Include or exclude help cards from generated reports. ( Adding report templates, Step 1 though Step 5.) Adding report templates To create a new template, follow these steps: 1. From the Main Console, click Templates. The Report Template dialog box opens (Figure 7-7). All pre-defined styles appear in the list box. 116

129 Chapter 7: Building Reports Figure 7-7. Report Template dialog box 2. Click Add, The Add Report Template dialog box opens (Figure 7-8). Figure 7-8. Add Report dialog box 117

130 WebTrends Enterprise Reporting Server. Enter a name to identify the template in the Report Template field. The name will you add here now appears in the Options, Profile, and User Access window of the Reporting Server. 3. Select the Style/Language tab. Choose a style sheet to use from the drop-down list. To view the colors and fonts used in the style, click Preview. 4. Select the language for the reports from the drop-down list. 5. If you want to include Help Cards in reports that use this template, Click in the Help Cards check box. Help cards explain the tables of the report and describe how to use the information in the report. 6. Check Remove Chapters That Contain No Data box if you don t want blank chapters included in the report. (You may have to scroll to view this option.) 7. Select the Format tab. The Format dialog box opens (Figure 7-9). Choose whether you want both HTML, Microsoft Word, and Microsoft Excel reports. Figure 7-9. Format dialog box 8. Check the Single Content HTML page box if you want to save the report as one HTML file. If you do not select this option, each section is saved as a separate file. 118

131 Chapter 7: Building Reports Tip: The HTML-only format generates more quickly, and uses less storage space. 9. Select the Content tab. The Content dialog box opens (Figure 7-10). Check the boxes for which chapters to include in the report. Figure Content dialog box 10. To specify the size of the table or graph, select the chapter in the list and enter the number in the Elements field. The greater the number, the more data included in the table or graph. 11. To change the type of graph, select the graph in the list and click the type you want to use. 12. Click OK to save your settings. Changing the report color Report templates determine the color of your reports. The Reporting Server offers several color schemes to chose from. To change the color, follow these steps: 119

132 WebTrends Enterprise Reporting Server 1. Click Template. The Report Template window opens. 2. Click Add, and enter a name for the template in the Report Template field. 3. In the Style/Language tab, select the style sheet you want to use. Click Preview to look at the style. Click OK to save the template. 4. In the profile view, apply the template to profiles in the Report Template tab. Changing the report language The template determines the report language used. To run reports using a different language, you should create a new template using the language you chose. Because any changes to templates only apply to reports created after the change, you should either copy an existing profile or create a new profile that uses the new template. This method allows you to generate a consistent set of reports. To change the language, follow these steps: 1. Click the Template button, and the Report Template window opens. 2. Click Add, and enter a name for the template in the Report Template field. 3. In the Style/Language tab, select the language to use. 4. Click OK to save your settings. Editing a report template You can change settings for an existing template. Please note the modifying template settings will only affect reports generated after the change. To modify an existing template, complete these steps: 1. Click the Template button, and the Report Template window opens. 2. Select the template that you want to modify from the list, and click Edit. 3. Make your changes. 4. Click OK to save your edits. 120

133 Chapter 7: Building Reports Deleting a report template You can delete a template if it is no longer used. To remove a report template, follow these steps: 1. Click Template, and the Report Template window opens. 2. Select the template that you want to remove, and click Delete. 3. Click OK to save your changes. Report data and Help Cards With this version of the Reporting Server, you will find far more tables and graphs available for inclusion in your reports than before: over 150 different ways of analyzing your web site s log file, depending on your site configurations, and the Reporting Server settings you have in place for each profile. For a complete list of available tables and graphs, generate a report on one of the sample databases included with the Reporting Server. To generate a sample report, complete these steps: 1. Select a sample profile from the Reporting Server Main Console. 2. Click the Reports icon. A complete report will be generated for the profile you have selected. By default, generated reports include Help Card data: descriptions of a table and graph you are viewing, and how the data can be used to help improve your site. You may find tables and graphs in your report which do not contain any data, due to a variety of configuration factors. Empty tables and graphs do not necessary signal an administrative error; it could be that your profile has not been configured to track the missing information. 121

134 WebTrends Enterprise Reporting Server 122

135 Configuring Program Options 8 8 Overview As an Administrator, you have access to all program settings. Use the Options window to modify settings that impact performance and processing as well as define new profiles. If you allow non-administrators to change these settings, your settings appear as default settings in the profile wizard to guide them. Otherwise, the profile settings defined here are applied to every new profile created by a nonadministrator. Note: User Access settings override the settings defined here. See Creating a user account on page 173 for details. Defining General options The General tab allows you to define the number of entries stored in the DNS cache, the length of a user session, and whether or not to include HTML titles in reports. To work with these settings: 1. Click Options, and the Options dialog box opens. 2. Select the General tab. 123

136 WebTrends Enterprise Reporting Server Figure 8-1. Options - General tab 3. Specify the following options: Visitor Session Termination Timeframe Specifies the length of a visitor session in seconds. HTML Titles To retrieve web page titles in your reports, make sure this box is checked. Enter the number of titles to store in the cache, and specify how long the entries should be saved. Note: Retrieving page titles can slow report creation. Choose this option only when it is important to identify HTML pages by their titles. Archiving profile data Archiving allows you to backup profile databases at regular intervals. Use this dialog box to specify how often archives are performed and the number of archives that are maintained for each profile. You can also set a default for the Activate Archiving setting that appears in the profile window. To define archive settings: 1. Click Options, and the Options window opens. 124

137 Chapter 8: Configuring Program Options 2. Select the Archiving tab. Figure 8-2. Archiving tab 3. Specify how often archives are made for each profile in the Frequency, In Days field. 4. Specify the maximum number of archives to maintain for each profile in the Max Number of Archives Per Profile field. 5. Select By Default, Enable Archiving in Profiles to enable archiving of new profiles by default. Defining the web site locale The Locale tab allows you to identify the country where your web server resides. This information is used in reports to show the activity that is considered domestic. 1. Click Options, and the Options window opens. 125

138 WebTrends Enterprise Reporting Server Figure 8-3. Locale tab 2. Select the Locale tab. 3. Select the country where your reports are created from the list (what is considered domestic ). 4. Click OK to save your selections, or click Cancel to exit the Options window without saving your changes. Defining the profile directory The Profiles tab allows you to define the directory for storing profiles. Note: If you change the profile directory, only new profiles are stored here. All previously created profiles remain in the original directory unless you copy them to the new location. 1. Click Options, and the Options window opens. 126

139 Chapter 8: Configuring Program Options Using cookies Figure 8-4. Profiles tab 2. Select the Profiles tab. 3. In the Profile Directory field, specify the directory for storing profiles. To indicate that the directory is relative to the program directory, enter./ (UNIX) or.\ (NT) before the name of the directory. 4. Click OK to save your selections, or click Cancel to exit the Options window without saving your changes. The Cookies tab allows you to include cookie data in the log file analysis. A cookie is a file sent with the page requested from the server to the visitor. Cookies are stored on the visitor s system. The stored cookie is then included in subsequent requests to your site by this visitor and is recorded in the log file, enabling you to uniquely identify the visitor. Activating cookies makes user session data more accurate because each visitor is unambiguously distinguished. 127

140 WebTrends Enterprise Reporting Server Figure 8-5. Cookies tab To use cookies by default for profiles: 1. Click Options, and the program Options window opens. 2. Select the Cookies tab. 3. Click in the Use Cookies, By Default check box to look for cookie user session IDs in log files. When cookies are found, Reporting Server uses these session IDs rather than the IP address to more accurately track a visitor s activity. If you don t use this option, and you have several visitors from the same IP, you won t be able to distinguish one visitor session from another. 4. Click in the Validate Cookie Format check box to verify that the cookie matches a WebTrends Plug-in cookie or one of your own. If the cookie matches, it is included as user session data. Note: If you are using a cookie other than the WebTrends Plug-in cookie make sure that the cookie ID is the same throughout a user s visit, and does not change from page to page. If it changes within the user session, the results are incorrect. 128

141 Defining file types Chapter 8: Configuring Program Options 5. Specify the cookie to use: Use this cookie Allows you to specify the cookie to use. Enter the cookie text in the corresponding field. Use WebTrends plug-in cookie If you installed a WebTrends logging plug-in on your web server, you can use this format. Use the File Types dialog box to define the types of files to include in the graphs and tables that relate to downloaded files or document files. For example, the Page Views item represents the sum of all hits to all document file types. If you would like this number to reflect only hits to.html and.htm pages, remove all other document file type extensions from the list. 1. Click Options, and the program Options window opens. Figure 8-6. Options dialog box 2. Select the File Types tab in the Options dialog box. 3. Select the file type that you would like to modify: Download File Extensions and Types Add or remove the file types that are included in the WebTrends Top Downloaded Files table and graph. 129

142 WebTrends Enterprise Reporting Server Document File Extensions and Types Add or remove the file types that are included in WebTrends report tables and graphs that pertain to documents (for example, Most and Least Requested Pages, Top Entry and Exit Pages). Document File Types define Page Views by appropriate hits. 4. Click Edit. The Edit Download/Document File Extensions and Types dialog box appears. The extension list indicates the file type extension, and the condition displays when the request for the file type is included. 5. Choose one of the following options: Edit Select a file type and click Edit to display the Edit File Type dialog box where you can modify when the file type is included. (See Adding or Editing File Types on page 130 for details.) Add To add an extension, click Add. (See Adding or Editing File Types on page 130 for details.) Remove Select a file type and click Remove to delete a file type in the list. 6. Click OK to save your selections, or click Cancel to exit the Options window without saving your changes. Adding or Editing File Types Use the Edit File Type dialog box to modify file type settings. You can add a file type to the default list or define when a file type is included. You can access this dialog box from the Download/Document File Extensions and Types dialog box. 130

143 Chapter 8: Configuring Program Options Figure 8-7. Download/Document File Extensions and Types dialog box 1. Click Options, and select the File Types tab. 2. Select the set of file extensions and types to work with (Download or Document), and click Edit. 3. Select a file type to work with from the drop-down list. Specify when the file request is included by choosing one of the following: Always Includes every file request for the selected file type. Only if they are not from a script or dynamic web page Includes only file requests that are not from scripts or dynamic web pages. If the URL includes this file type without a (?), the request is included. Only if they are from a script or dynamic web page Include only file requests from scripts or dynamic web pages. If the URL specifies this file type with a (?), the request is included. Defining FTP settings Use the FTP dialog box to define how log files that are accessed using FTP are handled. 1. Click Options, and the program Options window opens. 2. Select the FTP Options tab. 131

144 WebTrends Enterprise Reporting Server Figure 8-8. FTP Options tab 3. Specify where log files accessed using FTP are stored in the FTP Cache Directory field. By default log files are downloaded to:./wtm_wtx/datfiles/ftp (UNIX).\wtm_wtx\datfiles\ftp (NT). 4. Enter, in seconds, the length of the timeout for FTP activity in the FTP timeout field. If a successful connection to the FTP server cannot be made before this limit is reached, the connection to the FTP server is dropped. 5. Specify the FTP connection method to use. There are two methods for transferring data from an FTP server to an FTP client: active and passive FTP transfer. Use passive FTP transfer. When passive FTP is used, the server opens a port and the client connects to the server. Passive 132

145 Chapter 8: Configuring Program Options FTP is preferable where there is a firewall between the client and the server. This is because firewalls are typically configured to block incoming connections that are not recognized. Although some firewalls can parse the FTP data requests and allow active FTP connections, many require passive FTP connections. Use active FTP transfer. When active FTP is used, the client opens a port and the server connects to the client. 6. Specify whether to read FTP paths as relative paths or absolute paths. Use absolute paths. Select this option if you want all FTP paths read as absolute paths. Use relative paths. Select this option if you want all FTP paths read as relative paths. For example, if the profile points to the FTP URL ftp://ftpserver/logs/log1.log and you select Use absolute paths, /logs/log1.log is used. If you select Use relative paths,./logs/log1.log, is used. 7. Click OK to save your choices, or click Cancel to exit the Options window without saving your changes. Defining domain groups Use the Domains tab to modify how domains are reported in graphs and tables (for example, the Organization Breakdown graph and table). Some reports break down activity by U.S., International, or Unknown. If the domain is not found in the company database, but its extension matches something in the U.S. domains grouping, then it is added the U.S. total, rather than the International or Unknown total. Add or remove domain name suffixes from the list for each domain name grouping (United States Domains, Government Domains, Military Domains, etc.). 1. Click Options, and the program Options window opens. 133

146 WebTrends Enterprise Reporting Server. Figure 8-9. Domain tab 2. Select the Domain tab. 3. Select the domain grouping that you would like to modify, and click Edit. The Edit Domains dialog box opens displaying the domain suffixes included in the selected grouping. To remove an existing suffix, highlight the suffix in the list and click Remove. To add a suffix, type the suffix in the text entry field and click Add. 4. Click OK to save your selections, or click Cancel to exit the Options window without saving your changes. Defining FTP log file cache settings Use the settings in the FTP Log File Cache dialog box to minimize downloads for log files that are accessed using FTP. Log files can either be download every time the profile is processed or only when changes in the file are detected. 1. Click Options, and the program Options window opens. 2. Select the Log File Cache tab in the Options dialog box. 134

147 Chapter 8: Configuring Program Options Figure FTP Log File Cache tab 3. Select which method to use for retrieving logs from an FTP server. Every time the profile is processed. Download log files only when changes are detected in the remote file. 4. You can limit the size of the FTP cache by modifying the Cache limits field. Enter the number in megabytes. 5. Click OK to save your choices, or click Cancel to exit the Options window without saving your changes. Defining report server settings The Reports Serving tab allows you to specify the web server to use for publishing reports. The Reporting Server provides a built-in web server for 135

148 WebTrends Enterprise Reporting Server publishing reports and providing the Remote Interface. However, if you have another web server that you want to use for the reporting, you can specify it here. The Remote Interface is still provided by the Reporting Server s built in web server. 1. Click Options, and the Options window opens. Figure Report Serving tab 2. Select the Report Serving tab. Select one of the following: Default Select this option to use the built-in web server for publishing reports. Specify a different web server for serving reports Select this option to specify your own web server for publishing reports. Specify the location where reports should be stored in the Reports Directory field. Specify the URL that accesses the reports in the Report URL Path field. Note: If you change the reports directory, only new reports are stored in the new location. Old reports remain in the original location. 136

149 Chapter 8: Configuring Program Options 3. Select the Allow Non-administrators to Configure and Override...option to allow non-administrators to modify the defaults. 4. Click OK to save your selections, or click Cancel to exit the Options window without saving your changes. Defining the database directory The Database Directory tab allows you to define the default directory for all profile data. Important: If you change this location, Reporting Server reanalyzes the log file from the beginning. The original databases remain in the old directory and are not copied to the new location. 1. Click Options, and the Options window opens. Figure Database Directory tab 2. Select the Database Directory tab. 3. Enter the default directory to use for profile data. To maintain a separate directory for each profile, use the %profile% macro in your entry. 137

150 WebTrends Enterprise Reporting Server 4. Select the Allow Non-administrators... option to enable the Database Directory option in the profile window for all users. 5. Select the Allow Administrators... option to enable the Database Directory option in the profile window for administrators. 6. Click OK to save your selections. Selecting a report template Use the Report Template dialog box to define the default report template for new profiles. Report Templates define the colors, fonts, and content of the report. You can create your own templates in the Report Templates window. Working with Report Templates on page 116 for details. To select a template to use with reports: 1. Click Options, and the Options window opens. 2. Select the Report Template tab. Figure Report Template tab 3. Select the template to use as the default from the drop-down list. 4. Select the Allow Non-administrators option to allow nonadministrators to define Report Template options in the profile window. 138

151 5. Click OK to save your selections. Chapter 8: Configuring Program Options Defining the reports to maintain Use the Reports tab to define the default reports for new profiles. Each time a profile is analyzed, the Reporting Server updates each of the reports selected. For example, if daily, weekly, and monthly are selected, the daily report is updated each time the log is analyzed during the day. Then, at the end of the day, the weekly and monthly reports are updated using the completed daily report, and because it is no longer used, the data used for the daily report is discarded. Similarly, when the weekly report is complete, the data used to create it is discarded, and at the end of the month when the monthly report is complete, the data used to create it is discarded. Because disk space and memory are needed to maintain the report data, only select the reports that you need. 1. Click Options, and the Options window opens. Figure Reports tab 2. Select the Reports tab, and select the report intervals that you want to maintain by clicking in the Report Types boxes. 3. For each report type, specify the number of reports to save from the corresponding Reports to Store list. If you run a large number of reports, you might limit the number of reports that are saved. Using 139

152 WebTrends Enterprise Reporting Server this option, you can select the number of reports saved for each interval. For example, you might want to keep one month s worth of daily reports at a time; once the report for February 1 is created, the report for January 1 is deleted, and so on. When determining how many reports to store, consider how much disk space you want to devote to reports and how long you want to save them. A report using the Complete Summary template as it was installed needs up to 1 MB. 4. To allow Non-administrators to modify these settings for their profiles, click in the Allow Non-administrators to Configure... box. 5. Click OK to save your settings. Specifying the reporting method Reports can be generated two ways: pre-generated and on-demand. Pre-generated reports Pre-generated reports allow you to create and save reports on a set schedule. Tip: Pre-generated reports can be viewed immediately at the URL where the report is posted to, if the Start Initial Analysis Immediately option in the Report Scheduler dialog box was selected. Otherwise, reports are available at regular intervals beginning at the scheduled start time. On-demand reports On-demand reports allow you to postpone report generation until the user requests a report. Advantages to delaying report generation to a later time include: Flexibility in building reports: since you configure the appearance of a dynamic report just before it is generated, offering you at that point the chance to change to a different report styles, or update which types of tables or graphs to use. Network resources can be dedicated to other priority tasks. Because reports are created only as they are requested, disk space which would otherwise be allocated to a series of scheduled reports is saved. 140

153 Chapter 8: Configuring Program Options To select a reporting method: 1. Click the Options icon. The options window opens. 2. Click the Report Methods tab. The Report Methods property page opens. Figure Report Methods tab 3. Choose from the following two options: Click Pre-generated Reports to have reports created on a preconfigured schedule, and saved. Click On-demand Reports to have the reports generated ondemand, as users request them. 4. Click OK to save your changes. 141

154 WebTrends Enterprise Reporting Server Changing the report header Use the Report Header tab to specify an image to include in your reports. You can also specify a URL to reference when a visitor clicks on the image. 1. Click Options, and the program Options window opens. 2. Select the Report Header tab. The Report Header property page opens. Figure Report Header property page Here you can specify the following options: Report Image Specifies the graphic that you want to include in the report header. Report Image Alt Specifies the text that is displayed if the image isn t available or as the graphic is loading. 142

155 Chapter 8: Configuring Program Options Associated URL Specifies the URL to load when a visitor clicks on the Report Image. 3. Click OK to save and close the window. Defining a schedule for processing Use the Scheduler tab to define the default schedule for processing profiles. This setting can be overridden in the profile window. To set a schedule, complete these steps: 1. Click Options, and the program Options window opens. 2. Select the Scheduler tab. Figure Scheduler tab 143

156 WebTrends Enterprise Reporting Server 3. In the Initial Start Time field, specify when the reports should be generated using the 24 hour clock. 4. The default for the Frequency field is 15 minutes. Adjust this value to match the typical traffic on the web sites analyzed. 5. Select the Allow Non-administrators... option to allow nonadministrators to define the schedule on a profile basis. 6. Select the Start Initial Analysis... option to begin reports for new profiles immediately. To start reports at the scheduled time, do not select this option. 7. Click OK to save your selections, or click Cancel to exit the Options window without saving your changes. Configuring system performance settings Use the Performance tab to modify settings that may improve performance in your environment. 1. Click Options, and the Options window opens. 2. Select the Performance tab. The Performance window opens. 144

157 Chapter 8: Configuring Program Options Figure Performance tab 3. Maximum Number of Simultaneous Analyses Enter the maximum number of profiles that can be processed concurrently. If your system has fast processing or multiple CPUs, increasing this number may improve performance. 4. Click OK to save your selections. Selecting a DNS lookup method Use the DNS Lookup tab to define the default DNS lookup method for profiles. If you allow non-administrators to modify this setting on a profile basis, the method you select is used as the default. 145

158 WebTrends Enterprise Reporting Server DNS lookup is the process of translating the numeric IP address into a domain name. This can be done either by the web server when logging activity or by the program when it analyzes the log files. DNS lookups are performed more efficiently by the web server as the log is created, rather than by the program. However, if you know your web server administrator or ISP disabled DNS Lookups for their servers, you can still include domain information by selecting "Resolve Mode." 1. Click Options, and the program Options window opens. Figure DNS Lookup tab 2. Select the DNS Lookup tab. Select the DNS Lookup from the dropdown list: Quick mode, using format from log Maintains the log format, domain name or numeric IP address, making this the fastest method for creating reports. If your web server doesn t perform DNS Lookups and you choose the Quick Mode in this dialog box, WebTrends reports will display visitor s IP addresses rather than domain names. Resolve mode, lookup all numeric IPs If your web server does not perform DNS Lookups and you need geographic or other domain-related information, select this option. 146

159 Chapter 8: Configuring Program Options Note: Resolve mode may slow reporting. Use it only if DNS lookups cannot be done on the server. Once a numeric address has been looked up, its text equivalent is stored in a permanent cache to expedite all subsequent reports. The default cache size is 50,000 entries; once this limit is reached, the oldest addresses are replaced with the new entries. You can change the cache size in the General tab. Auto mode, if you re unsure If you don t know whether your log file contains IP addresses or domain names, and you want domain names in the report, you can use Auto Mode. If a domain name is found at the start of log file analysis, "Quick Mode" is used. If an IP address is found when the log file analysis begins, "Resolve Mode" is used. 3. Select the Allow Non-administrators... option to enable the DNS Lookup option in the profile window for all users. 4. Click OK to save your selections, or click Cancel to exit the Options window without saving your changes. Defining proxy server settings If you access the Internet through a proxy server, you must configure these settings. For example, if you enabled page title retrieval in the General Options tab, the Reporting Server must be able to access the Internet in the same manner that you do. 1. Click Options and the program Options window opens. 2. Select the Proxy tab. 147

160 WebTrends Enterprise Reporting Server Figure Proxy tab 3. Click in the Connect Through Proxy Server check box. 4. Specify the URL for the proxy server to use in the Address field. 5. Enter the port number for the server in the Port field. 6. Enter the user name and password required to access the server in the Proxy Server Login Information fields. This information is required only for servers who authenticate their users. Configuring web server settings In the Web Server Configuration window, you can work with settings for the web server which provides the data the Reporting Server analyzes. 1. Select Configuration>Web Server Configuration. 148

161 Chapter 8: Configuring Program Options Figure Web Server Configuration window 2. In the Web Server Configuration window, you can modify the following settings: Port Specifies the port where the web server resides. Be sure the port is not used by another daemon. Authentication Specifies the method used to authenticate the users when the log in. If you select Operating System, the user must have an account on the machine. If you select Custom, you must define a password for all users in the User Access window. User Session Timeout Specifies the length of the timeout before the user is disconnected from the server. 149

162 WebTrends Enterprise Reporting Server 150

163 Using Advanced Features 9 9 URL search and replace definitions Each entry in the web server log contains a field that references the URL of the page or file that a visitor accessed. Each unique URL is counted as a separate page or file, and the information in the field is used to track activity on the web site. Some web server plug-ins or applications add unique identifiers to URLs that can cause hits to these pages to be counted incorrectly. For example, some shopping-cart applications add a unique string to a page name in order to identity each visitor to that page. This address string makes it possible to track a visitor s progress through the site and keep track of what s in her shopping cart. Every hit to a page that uses this added string appears in the log as a unique URL despite the fact that the hits are really all for the same page. The URL Search and Replace feature helps you cut through this confusion. By deleting specific identifiers from URLs or replacing all unique identifiers with a common string, you can make page counts accurate and reports more informative, and avoid out-of-memory conditions that can result when the number of unique IDs is extremely high. Once you tell OLAP which URLs to look for, you can apply this URL list to all profiles or only to the ones that you choose. Important: You should use the URL replacement feature before any other processing takes place. Using URL replacement for shopping cart applications Many web sites that sell products use shopping cart applications. Typically, these applications let visitors accumulate the items they plan to purchase by using buttons that say "Add to Basket" or "Add to Cart." There are a number of ways that the shopping cart application can track the shopping cart and associate a particular visitor with her shopping cart: IP address of the visitor. The visitor s IP address is used to track the shopping cart. This method is not widely used because many visitors can come from the same IP address. 161

164 WebTrends Enterprise Reporting Server (An IP address looks something like this: ) Cookies. A cookie is stored on the visitor s computer and used to track the shopping cart and (often) the visitor s shopping interests. Because some visitors set their browser to reject cookies, an application that use cookies will reject the visitor or switch to another tracking method. Some stores that use cookies are SalesCart, IBM and ShopSite. Parameters on dynamic pages. Sites that use dynamic pages often use a parameter to identify each visitor, and include this parameter in the URL of every page visited. Each page is a script that uses the shopping cart parameter to access a database. One type of entry can look something like this: page.pl?cart_id=hjf k&product=boot where HJF K is the cart ID. Yahoo.Store and NetCart are examples of store providers using these parameters. Another type of entry might look like this: page.pl?hrud9tpc;00-342;26 where hrud9tpc is the ID. Mercantec and MiniVend are providers that use this type of parameter. Data embedded in the URL. Some sites using dynamic pages use server-side data includes to embed shopping cart information. Data embedded in the URL might look like this: /catalogue/ /offer/addproduct/123 where is the shopping cart id. How tracking mechanisms affect analysis If a shopping cart application uses the IP address or cookies to track visitors, the analysis is done in the usual manner. If the application uses a consistent name/value pair parameter (such as?cart_id=ure445&product=jacket), you can use a URL Parameter Analysis definition (see Analyzing activity for a dynamic site on page 168). If the application uses something like page.pl?hrud9tpc;00-342;26 instead of a name/value parameter pair, or the data is embedded (such as / catalogue/ /offer/addproduct/123), you should use a URL Search and Replace definition. 162

165 Using URL replacement to group pages Chapter 9: Using Advanced Features You can use URL replacement definitions to analyze and report on URLs differently than those URLs are recorded in the log. For example, you could report all pages from a certain directory as hits to the same page, forcing the pages into a group. Because the URL replacement is done before the analysis, the change affects the counting for all tables and graphs. Grouping pages using this method is not the same as using content groups. Content group definitions only apply to the Content Group section, but a URL replacement definition applies to all sections of the report. To make URL replacement selections: 1. Select Configuration>Advanced Features>URL Search and Replace. Figure 9-1. Using URL replacements to group pages The URL Search and Replace tab lists all URL replacement definitions. Check marks indicate definitions that are enabled. 163

166 WebTrends Enterprise Reporting Server 2. You now have these options: Add a definition. Click Add to create a new definition. See Creating a URL replacement definition on page 164 for details. Edit a definition. Select a definition, then click Edit to modify the settings. Delete a definition. Select an item, then click Delete to remove it from the list. 3. Apply the definitions to one or more profiles: Apply these settings to all profiles. Select this check box to apply the definitions to all profiles. Allow the user to modify on a profile basis. Select this check box if you want to choose the URL replacement definitions on a profile-by-profile basis. 4. Click OK to close the Advanced Features window. Creating a URL replacement definition To create a new URL replacement definition: 1. Select Configuration>Advanced Features>URL Search and Replace. 2. Click Add to open the Preconfigured URL Search and Replace window. 3. Select Custom from the Shopping Cart list, and click Continue. The URL Search and Replace window opens (see Figure 9-2 on page 165). 164

167 Chapter 9: Using Advanced Features Figure 9-2. URL Search and Replace dialog box 4. Type a name for the definition in the Description text box. 5. Define the string that is to be replaced. a) Use the Replace From drop-down list to select the starting point for the replacement. In the text box next to the list, type the beginning of the string that is to be matched. b) Use the Up To drop-down list to select the ending point for the replacement. In the text box next to the list, type the text that indicates the end of the replacement string. 6. In the With text box, type the text that will replace the string you defined in step In the Perform replacement only if the URL contains text box, type a value to be matched. The text is replaced only if the URL contains this value. 8. Use the Test Area to see how the definition works. Type a sample URL, and click Test. The results appear in the Resulting URL text box. The text that was removed appears in the Text that was Replaced text box. 9. Click OK to close the URL Search and Replace window. 165

168 WebTrends Enterprise Reporting Server Path analysis Path analysis definitions help you determine where visitors went to from a specified page, and make it possible to create reports that include path analysis data about the parts of the site that interest you. Suppose that you want to know where visitors go after they visit the pricing page, order.htm. In this case, you d create a path analysis definition that uses order.htm as its starting point, and set a limit on the number of paths you want shown in the report. When you generate a report that uses this path definition, you will get a listing of visitor paths that begin at the order.htm page. To define a path to analyze: 1. Select Configuration>Advanced Features. Then click on the Path Analysis tab. Figure 9-3. Path Analysis tab 2. Click Add. The Path Analysis window (Figure 9-4 on page 167) opens. 166

169 Chapter 9: Using Advanced Features Figure 9-4. Path Analysis window 3. In the Description text box, type a name for this path analysis. The name you provide here will identify the Path Analysis throughout the application. 4. In the Starting Page text box, type the web page to use as the starting point for the path analysis. 5. In the Number of Levels to Track text box, type a number to specify the depth of the path analysis. For example, a value of 6 reports on the next six pages that the visitor went to from the page specified. 6. In the Maximum Number of Paths to Track text box, type the maximum number of paths to track for this definition. Note: The number of paths you track affects the resources used in processing. The higher the number of paths, the more resources are tied up. You may want to track the fewest paths possible to reduce the resource load. 7. Click OK. The Advanced Features window reappears, with the Path Analysis tab showing. 8. By default, the path analysis setting you just selected will be used for all profiles. If you want to apply the settings to individual profiles, 167

170 WebTrends Enterprise Reporting Server Content groups select Allow these Path Analysis settings to be applied on a profile basis. No matter how well organized your site is, there are going to be times when you will want information about categories that can t be defined in terms of specific pages or directories. For example, you might need to know about a product that shows up on several types of pages in a number of different directories, or you might want information on particular products within one or more directories. In these cases, a report that looks at specific directories or most-requested pages probably won t give you the information you need at least not without forcing you to search through lots of irrelevant report entries for the ones you need. A Content Group definition is a set of patterns that identifies each group. Patterns are the key parts of the URL. If the URL matches a pattern in the definition, it is associated with the group. To create a content group definition: 1. Select Configuration>Advanced Features>Content Groups. 2. Click Add. The Content Groups window opens. 3. In the Description text box, type a name for the new group. This is used to identify it in the Profile list and in reports. 4. In the Patterns text box, type the part of the URL that pages in this group should match. Type each pattern on a separate line. 5. Click OK.The Advanced Features window reappears, with the Content Groups tab showing. 6. By default, the content groups setting you just selected will be used for all profiles. If you want to apply the settings to individual profiles, select Allow these Content Groups settings to be applied on a profile basis. Analyzing activity for a dynamic site Getting meaningful data about a dynamic web site presents different problems than you encounter in tracking the same types of data on a static site. By associating each page that interests you with one or more of the 168

171 Chapter 9: Using Advanced Features parameters used to create it, however, you can create reports that provide both a summary of activity for each dynamic page (via the Dynamic Pages and Scripts section) and parameter data for each page defined (via the Dynamic Pages section). An important point to remember when creating reports on dynamic sites is to avoid tracking pages as "documents." It s good practice to check the File Types configuration option to confirm that the file extension your site uses for dynamic pages (such as.asp) is not listed as a document type. See Defining file types on page 129 for more information. The section that follows explains what a URL Parameter Analysis definition is and provides instructions for creating one. Note: If you don t define a page through a URL Parameter Analysis definition, the total hits for the page are reported in the Top Forms section. About URL parameter analysis definitions A URL Parameter Analysis definition associates a page with a parameter used to create it. Because many parameters can be passed for a single page, you can create definitions for each parameter. The number of hits and user sessions for each value submitted with the parameter appear in the Dynamic Page reports. To create a URL Parameter Analysis definition: This procedure assumes you want to report on activity for products on a downloads page. The URL for this page looks something like this: 1. Select Configuration>Advanced Features>URL Parameter Analysis. 2. Click Add. The URL Parameter Analysis window opens. 3. In the Description text box, type a name for this path analysis definition. This description will identify the definition in the Advanced Features window, in the profile window, and in reports. Since we are creating this definition for the downloads.asp page, you might type: Downloads 169

172 WebTrends Enterprise Reporting Server 4. In the Page Name text box, type the name of the web page used by this definition. The name you type is the one that will be used for the page each time it appears in the log file. If the URL is you would type this in the Page Name text box: /site_download/download.htm Note: To specify a home page, type a slash (/) in the URL text box. If the site is multi-homed, you must also specify the domain name. For example, if the domains webtrends.com and webtrends.net are both hosted by one server, and you are reporting on pages for webtrends.net only, the URL text box would look like this: 5. Select the Regular Expression check box if you want the URL to be treated as a regular expression. Note: If the text in the Page Name text box starts or ends with a asterisk (*) and the Regular Expression check box is not selected, the page name is treated as a special type of regular expression. In this case, the asterisk will match 0 or more of any character at either the beginning of the page, the end of the page, or both. 6. Click Test to see how the expression works on a sample string. 7. Define the main parameter that you want to report on. a) In the Parameter1 text box, type the name of the main parameter. For example, if you want the report to focus on the values that match the shoes parameter, you would type: shoes 2) By default, the name in you typed in the Parameter1 text box will be used whenever this parameter appears in reports. If you want a different name to be used, type that name in the Name to display in reports text box. 3) If you want to translate the parameter, select the Translate parameter into more meaningful strings check box, then type the location of the replacment string into the Location of translation file text box. For more information, see Creating translation files below. 170

173 Chapter 9: Using Advanced Features 8. If you desire, you can define a second parameter to be reported on. a) In the Parameter2 text box, type the name of the main parameter. For example, if you want the secondary focus of the report to be on the size parameter, you would type: size 2) By default, the name in you typed in the Parameter2 text box will be used whenever this parameter appears in reports. If you want a different name to be used, type that name in the Name to display in reports text box. The report table that is generated using the primary and secondary parameters will include a column for all values that matched shoes and another column for all values that matched size, and breaks down the activity for each size. 3) If you want to translate the parameter, select the Translate parameter into more meaningful strings check box, then type the location of the replacment string into the Location of translation file text box. For more information, see Creating translation files below. 9. Click OK.The Advanced Features window reappears, with the URL Parameter Analysis tab showing. 10. By default, the URL parameter analysis setting you just selected will be used for all profiles. If you want to apply the settings to individual profiles, select Allow these URL Parameter Analysis settings to be applied on a profile basis. Creating translation files A translation file lists each value that parameter may have, and associates each value with a phrase that s easier to understand. For example, if your web site refers to products by number, the translation file can translate those numbers into actual product names. Each line in a translation file contains a value and a phrase, separated by a comma or tab, as shown here: 0014,Firewall 0016,Professional Suite Sometimes you will want to translate several parameter values into the same phrase. If you sell running shoes on your site, for example, and you want to report on all styles of a brand, the translation file might look like this: 171

174 WebTrends Enterprise Reporting Server flight07,flight Shoes flight06,flight Shoes To use a translation file in an URL parameter analysis: Type the path for the file in the Location of translation file text box for the appropriate parameter. See Step 7 on page 170 or Step 8 on page 171 for more information. 172

175 Setting User Access Overview The User Access feature enables you to set up user accounts for the Reporting Server. Here you can define the features individuals have access to, define profile default settings, and restrict the dialog boxes they see. If you are using the built-in authentication instead of OS Authentication, you specify user names and passwords as well. Creating a user account This section describes the steps for setting up a user account. 1. Click the Access button. The Configure User Access and Privileges dialog box displays all accounts. Note: The area just below the Users list displays the number of Administrators and the number of Users defined. Figure Configure User Access and Privileges dialog box 173

176 WebTrends Enterprise Reporting Server 2. Click the Add button, and the Add New User dialog box opens. Figure Add New User dialog box 3. Enter the login name for the user in the User name field. If the password field is displayed, enter the password for the user in the Password field. Note: The password field appears only if OS Authentication was not enabled. See Remote Configuration on page 210 for more information. 4. Select the privileges for this user: View Reports Allows the user to look at published reports. All users are given view access. Add Profiles Allows the user to create profiles. Edit Profiles Allows the user to modify profiles. Delete Profiles Allows the user to remove profiles. Administrator Rights Gives the user access to all the Reporting Server functions. 5. Check Enable Advanced Configuration to define restrictions and default profile settings for the user. 6. If you did not check Enable Advanced Configuration, click Finish and skip the remainder of the steps. If you checked Enable Advanced 174

177 Chapter 10: Setting User Access Configuration, click Next, and the Restrictions dialog box opens. To limit the number of profiles the user can create, check the box, and enter the maximum number of profiles. Figure Restrictions dialog box 7. Click Next, and a profile dialog box opens. Use these dialog boxes to define default settings for this user s profiles. Note: Wherever you see "Hide this tab from the user," you can define the options and prevent the user from seeing the dialog box when they are working with profiles. Refer to Adding a profile on page 26 or the online help for details on each profile setting. 8. Click OK to save your settings. Modifying a user account This section describes changing the settings in a user account. Note: You cannot modify your own permissions. Only another Administrator may do so. 1. Click the Access button. 175

178 WebTrends Enterprise Reporting Server 2. Select the user whose account you want to modify from the list. 3. Click the Edit button. 4. Make your changes, and click OK. Note: Wherever you see "Hide this tab from the user," you can define the options and prevent the user from seeing the dialog box when they are working with profiles. 176

179 Running from the Command Line About the Command Line Capability Although Reporting Server provides a graphical user interface (GUI) for viewing reports and administering the program, you can perform all functions from the command line. Most likely you ll configure the program from the command line for immediate results and better speed. Using the command line, you can run a profile without having to start the web server that provides the interface. Using the commands available and configuration text files, you can: Start and stop the program. Configure program settings. Set up user accounts. Create profiles. Review program and profile audit files. create report style sheets Define Internet advertising to track. Enter information about your internet to include in reports. customize the company database used for reports. Table Audit and configuration text files File Purpose Refer to this section adviews.txt keywords.ini Defines advertisements to track. Defines the search engine identified in reports. Defining Advertisements to Track on page 240. Modifying Search Engines on page

180 WebTrends Enterprise Reporting Server File Purpose Refer to this section <profilestatus>.usr wtintra.txt wt_remote.ini wtm_wdw.ini Contains a log of activity for the profile selected. Defines user account settings such as privileges and default profile settings. Contains profile settings. Customizes domain information for reports. Configures settings for the web server that provides the remote interface. Specifies program wide settings including many default settings. Contains a detailed log of program activity which you, the administrator, should check daily. Setting Up User Accounts and Permissions on page 213. Working with Profiles on page 217. Setting Up Your Intranet Domains on page 241. Configuring Web Server Settings on page 210. Configuring Web Server Settings on page 210. Directory Structure The following table briefly describes the top level program directories. Table Directory structure Directory Sub-directory Contains scripts cgi-inc general wtm_wtx (UNIX) /layout /res (NT) \layout\res (UNIX) /language /layout/res and.pl files (NT) \language \layout\res and.pl files utils wtscript wt_report.pl and.pm files 178

181 Chapter 11: Running from the Command Line Directory Sub-directory Contains CordaJava datfiles images MSword template (UNIX) /apfiles /com /PopChartA.zip (NT) \apfiles \com \PopChartA.zip (UNIX) /contentgroups /databases /dynamicpages /pathsanalysis / profiles /reports /samples /statuslogs / urlreplacement /users (NT) \contentgroups \databases \dynamicpages \pathsanalysis \profiles \reports \samples \statuslogs \urlreplacement.html files and.gifs for reports Installation package for the Microsoft Word convertor program.var and.rpl files for report templates wwwroot english help images (UNIX) /general /wtm_wtx help directories (NT) \general \wtm_wtx help directories (UNIX) /btns /tabs and.gifs for program (NT) \btns \tabs and.gifs for program Command Line Options This section describes the scripts and executables available to run the program and their parameters. Scripts The following scripts are provided for the Linux and Solaris versions: wtrs.server The wtrs.server script invokes both the wtinterface.server script and the wtengine.server script. Using the parameters available you can control both the analysis engine and the remote interface. 179

182 WebTrends Enterprise Reporting Server wtengine.server The wtengine.server script calls the wtrs executable, which controls the analysis engine. The script calls the executable, which controls the user interface. Table Script parameters Parameter start stop status Description Starts the service. Stops the service. Provides the status of the service. Syntax Executables Scripts require the following syntax: [script] [parameter] For example, wtrs wtengine.server start The executable, wtrs, performs the analysis and other program processes such as generating reports and updating files for changes made through the remote interface. Run wtrs using the available parameters. It also can be called by wtrs.service or wtengine.service. 180

183 Chapter 11: Running from the Command Line Table Executable parameters Parameter -start -stop -status (NT) -install (NT) -remove Description Starts the executable. Stops the executable. Provides the status of the executable. Installs the program service. Removes the program from the list of services. Syntax executables accept commands presented in the following syntax: [executable] [-option] where [executable] refers to either wtrs or wtct_ui and [-option] refers to one of the program parameters defined in the previous table. wtrs <profile> where <profile> is the name of a single profile or a set of profiles. For example, you can run the sample profile included with the program by entering the following: wtrs sample Note: Use wildcards to specify a set of profile names. Enter * to specify all profiles. Spaces are not allowed in profile file names. wtrs -reanalyze <profile> where <profile> is the name of a single profile or a set of profiles. Reanalyzing a profile allows you to make changes to a profile s settings and update the profile s entire set of reports at the next scheduled interval. Were you to make a change and not reanalyze, only new reports would reflect the change. Caution! When you reanalyze a profile, all existing databases and reports are deleted. Note: If the program is running as a daemon/service, you cannot run profiles from the command line. 181

184 WebTrends Enterprise Reporting Server Recommended Steps for Using Command Line Settings We recommend the following process for creating the text files described in the previous section. Hierarchy of settings 1. Use the GUI to create a profile, template, intranet domain definition, user file, or ad click definition that contains the settings that you are most likely to use. Name these items in a way that you can recognize them in the text files. 2. To make sure that all of your settings have been recorded in the text files, select File>Exit. To locate your file, sort them by date. The uses a default incremental naming convention to name them (for example, 1 and 2. However, for your own custom files, you can use any naming convention you like. Just make sure that they have the right extension. 3. Modify your files using a text editor such as Notepad (NT) or vi (UNIX). The file options are described in the sections that follow. In Reporting Server processing, there are three levels of configuration settings. Global configuration settings are defined in the file. Settings in the file define defaults for profiles and apply to program processes on the whole (for example, the web server that is used for posting reports or the settings for threading processing). Only administrators have access to these settings. Profile settings are maintained in files. The settings defined in the file appear as defaults in the file. Any program user with the create profile right can override these settings. User settings are maintained in.usr files. As an administrator, you can tighten profile settings even more through.usr files. In addition to access rights,.usr files contain profile settings specific to the user. You can also hide profile dialog boxes from the user, so that only those that you choose appear when the user creates or edits profiles. 182

185 Configuring Program Settings Chapter 11: Running from the Command Line Most program configuration settings and profile default settings are located in the file. Use this section as a reference for the settings contained in this file. Audit Audit files for each profile and for the program are maintained. Table Audit settings Audit settings logdir logfile Description Specifies the directory where the profile status logs and the audit file for the program are stored. Values: (Default settings) (UNIX) datfiles/statuslog (NT) datfiles\statuslog Specifies the name of the program audit file. This file provides an account of program activity. Values: string. By default, the file is named wtrs.audit Audit settings [audit] logdir = (UNIX) datfiles/statuslogs (NT) datfiles\statuslogs logfile = wtrs.audit archives Archiving allows you to backup profile databases and reports at regular intervals. The archives section defines how often archiving takes place and the maximum number of archives kept for each profile. 183

186 WebTrends Enterprise Reporting Server Table Archive settings Archive setting frequency maxarchives Description Specifies how often an archive is created for the profile. Values: The default is 7 (days). Specifies the maximum number of archives kept for each profile using archiving. Values: The default is 4. Cookie If your web server uses cookies to identify repeat visitors, this information can be used to more accurately identify unique user sessions. Using cookies is the most accurate way of tracking the user s path through the site. Note: See Using cookies on page 127 for details on how cookies are defined in the GUI. Table Cookie settings Cookie setting enable validate Description Values: 1 Uses cookie data in the analysis. This is the default setting 0 Cookies are not used to track visitors. Values: 1 Includes only valid cookies in the analysis. 0 Does not validate the cookie. If enabled is set to 1, the data in the cookie field of the log file is used in the analysis. If enabled is set to 0, this value is not read. 184

187 Chapter 11: Running from the Command Line Cookie setting CookieText WebTrendsPlugin CookieString Description Allows you to specify a cookie to use to track user sessions. Values: 1 Uses the cookie specified in the CookieString option. 0 Uses the cookie generated by the WebTrends Plugin (or none, if enable is set to 0.) Note: You must also specify the cookie to match in the cookiestring option. Allows you to use the cookie generated by either WebTrends Netscape Extended Log Plugin or WebTrends IIS Extended Log Plugin. Values: 1 If CookieText is set to 0, set this option to 1. 0 If CookieText is set to 1, set this option to 0. Note: You must have installed one of these plugins to use this option. If the CookieText option is set to 1, specify the cookie format to validate here. Values: string. For example, the cookie field of a log file might look like this: CookieID1=CookieValue1;CookieID2=Cookie Value2;CookieID3=CookieValue3 If the cookie that you want to use to identify user sessions is CookieID2, you would enter CookieID2 in the CookieString field. If you are using Microsoft SiteServer, you might have cookies that look like this: SITESERVER=ID=CookieValue1;SITESERVER=GU ID=CookieValue2 If the GUID is the cookie that you want to use to identify user sessions, then you should enter SITESERVER=GUID in the CookieString field. 185

188 WebTrends Enterprise Reporting Server Sample cookie settings [cookie] enable = 1 validate = 0 Defaults The settings in this section define the defaults for new profiles created through the GUI (graphical user interface). Table Defaults settings default setting profilesdir Description Specifies the directory where all profiles are kept. Note: If you change this location, only new profiles appear in the new directory. Profiles created before the change remain in the original location unless you copy them. Values: By default, the value is (UNIX)./wtm_wtx/datfiles/profiles (NT).\wtm_wtx\datfiles\profiles Enter./ (UNIX) or.\ (NT) to indicate that the directory is relative to the installation directory. Note: The Reporting Server provides information on domain groupings in the Organization Breakdown table and graph. The following settings define the domains associated with each domain grouping. They can also be defined through the GUI. See Defining domain groups on page 133 for details. edu_orgtype Specifies the domains associated with education types of organizations in reports. Separate multiple entries with spaces. Values: (Default settings) edu ac.at at.cn ac.cr ac.cy ac.fj ac.id ac.il ac.im ac.in ac.jp ac.kr ac.nz ac.pa ac.th ac.ug ac.uk ac.yu ac.za re.kr ed.cr edu.ac edu.bm edu.cn edu.co edu.do edu.ec edu.eg edu.ge edu.gu edu.jo edu.lc edu.lv edu.mm edu.mo edu.my edu.pa edu.py edu.sg edu.sh edu.tr edu.tw edu.uy edu.ve edu.yu edu.za edunet.tn k12.ec k12.il k12.tr sch.uk school.fj school.za 186

189 Chapter 11: Running from the Command Line default setting usdomains int_orgtype gov_orgtype mil_orgtype net_orgtype Description Specifies the domains associated with the United States in reports. Separate multiple entries with spaces. Values: (Default settings) com edu net org gov mil int arpa Specifies the domains that are reported as International types of organizations. Values: (Default settings) int int.co int.ve intl.tn Specifies the domains that are reported as government types of organizations. Values: (Default settings) gov go.cr go.id go.kr go.th go.ug gob.pa gov.ac gov.au gov.bm gov.br gov.cn gov.co gov.cy gov.do gov.ec gov.eg gov.fj gov.ge gov.gu gov.il gov.im gov.in gov.jo gov.jp gov.lb gov.lc gov.lv gov.mm gov.mo gov.my gov.sg gov.sh gov.tn gov.tr gov.ua gov.ua gov.uk gov.ve gov.ve gov.za gove.tw govt.nz Specifies the domains that are reported as military types of organizations. Values: (Default settings) mil mil.ac mil.br mil.co mil.do mil.ec mil.ge mil.gu mil.id mil.lb mil.lv mil.ph mil.sh mil.tr mil.ve mil.za Specifies the domains that are reported as network types of organizations. Values: (Default settings) net ad.jp ne.kr net.ac net.ae net.ar net.au net.bm bet.br net.bs net.cn net.cu net.cy net.do net.ec net.eg net.ge net.gu net.hk net.id net.il net.im net.in net.jo net.jp net.la net.lb net.lc net.lv net.ly net.mm net.mo net.mt net.mx net.my net.na net.nc net.np net.nz net.pa net.pe net.ph net.pl net.py net.ru net.sg net.sh net.sy net.th net.tn net.tr net.tw net.ua net.uk net.uy net.ve net.vi net.ve net.vi net.za 187

190 WebTrends Enterprise Reporting Server default setting org_orgtype arpa_orgtype com_orgtype maxtopcount maxthreads maxcachedcount dnscachelifespan Description Specifies the domains that are reported as organizations. Values: (Default settings) org or.cr or.id or.kr or.th or.ug org.ac org.ae org.au org.bm org.br org.bs org.cn org.co org.cu org.cy org.do orge.ec org.eg org.fj org.ge org.gu org.hk org.hu org.il org.im org.jp org.la org.lb org.lc org.lv org.ly org.mm org.mo org.mt org.mx org.my org.na org.nc org.nz org.pa org.pe org.ph org.pl org.py org.ru org.sg org.sh org.sy org.tn org.tr org.tw org.uk org.uy org.ve org.vi org.yu org.za Specifies the domains that are reported as arpa types of organizations. Values: arpa Specifies the domains that are associated as commercial types of organizations. Values: (Default settings) com co co.at co.co co.hu co.id co.id co.il co.im co.in co.jp co.kr co.nz co.sv co.th co.ug co.uk co.ve co.vi co.yu co.za com.ac com.ae com.ar com.au com.bm com.br com.bs com.cn com.co com.cu com.cy com.do com.ec com.eg com.jf com.ge com.gu com.gh com.jo com.la com.lb com.lc com.lv com.ly com.mm com.mo com.mt com.mx com.my com.na com.nc com.ni com.np com.pa com.pe com.ph com.pl com.py com.ru com.sg com.sh com.sy com.tn com.tr com.tw com.ua com.uy com.ve firm.co firm.ve ltd.uk This option is not currently used. Value: It is set to 500 Specifies the number of threads which are allocated to reverse DNS (domain name server) lookups. The threads are divided among the number of concurrent analyses. Default Values for NT= 40 Default Values for Linux, Solaris = 8 This option is not currently used. Specifies the number of days that DNS entries stored in the database are valid. Default value =

191 Chapter 11: Running from the Command Line default setting dnsthreads dnscacheentries dnstimeout Description Specifies the number of threads available to perform DNS lookups on the entries in the lookup queue. The more threads working on DNS resolution, the quicker the process should go, if there are enough entries in the lookup queue to work on. However, if there are too many threads for the size of the lookup queue, many of the threads are not used and remain idle. Making this number too high may overtax system resources. Values: The following are defaults: (Solaris 2.5) 8 (Solaris 2.6) 16 (Linux) 1 (NT) 20 Specifies the number of entries in the DNS cache. Once an entry in the DNS lookup queue has been cached, it is saved here until the maximum number of entries is reached. If you are running extremely large log files, or log files with a high incidence of unique IPs, you should increase the size of the cache for better performance on subsequent analyses. Each entry takes about 50 bytes; making the cache too large may cause excessive swapping. Values: The default is Specifies the maximum number of seconds given to perform each DNS lookup. Once this number is reached, the IP is cached whether it is translated or not, and the record is ready for processing. Decreasing this value can improve performance significantly if there are a large number of IPs that cannot be translated. However, once an IP has been cached, it is not be looked up again which can affect the accuracy of reports. Values: The default is

192 WebTrends Enterprise Reporting Server default setting downloadtypes documenttypes cachedtime titlecachesize titlecachelifespan Description Specifies the file type extensions that are associated with downloaded files and when the file type is included in reports. This data is included in the Top Downloaded Files table and graph. Values: 0 Includes the file type if it is from a script or dynamic page. 1 Includes the file type only if it is not from a script or dynamic page. 2 Always includes the file type. Example: {exe,0} {com,0} {zip,0} {pdf,0} {arc,0} {bin,0} {sit,0} {tar,0} {gz,0} {z,0} {arj,0} Specifies the file type extensions that are counted as document files and when the file type is included in reports. These are reported in the Most/Least Requested Pages table and graph, and the Top Entry/Exit Pages table and graph. 0 Includes the file type if it is from a script or dynamic page. 1 Includes the file type only if it is not from a script or dynamic page. 2 Always includes the file type. Example: {htm,0} {txt,0} {mdl,0} {shtml,0} {htmls,0} {html,0} {htp,0} {htpl,0} {dbm,0} {asp,0} {sht,0} {cfm,0} Specifies the number of seconds of inactivity before the visitor session is timed-out. Values: integer. The default value, 1800, corresponds to 30 minutes of inactivity. If the NoHTMLTitles option is disabled (set to 0), specify the size of the cache for page titles here. Values: integer. The default value is If the NoHTMLTitles option is disabled (set to 1), specify the maximum number of seconds entries are saved in the cache. This option is typically used for sites that change often. Values: integer. The default value is (3 days). 190

193 Chapter 11: Running from the Command Line default setting nohtmltitles IncludeContentGroups IncludeQueryStrings Description Defines whether the titles of html pages are looked up and included in reports. Values: 0 Includes the titles of html pages in reports. This is the default. 1 Excludes the titles of html page titles in reports. Tip: Setting this option to 1 may significantly reduce the time it takes to analyze the log file. Allows you to specify Content Group definitions to apply to profiles. Each Content Group definition is assigned a unique identifier. The unique id is defined in the ProfileID option located in: (UNIX) <InstallDir>\wtm_wtx\datfiles\contentgroups\default.ini (NT) <InstallDir>/wtm_wtx/datfiles/contentgroups/ default.ini Values: Enter the unique ids to use here. Separate multiple ids with a space. By default, this option specifies all definitions, indicated by an asterisk (*). Allows you to specify URL Parameter Analysis definitions to apply to profiles. Each URL Parameter Analysis definition is assigned a unique identifier. This unique id is defined by the ProfileID option which is located in: (UNIX) <InstallDir>\wtm_wtx\datfiles\DynamicPages\default.ini (NT) <InstallDir>/wtm_wtx/datfiles/DynamicPages/ default.ini Values: Enter the unique ids to use here. Separate multiple ids with a space. Use an asterisk (*) to specify all URL Parameter Analysis definitions. By default, this option specifies all definitions, indicated by an asterisk (*). 191

194 WebTrends Enterprise Reporting Server default setting IncludePathAnalysisProfi les UseGlobalContentGroups useglobalpathsanalysispr ofiles useglobalquerystrings Description Allows you to specify Path Analysis definitions to apply to profiles. Each Path Analysis definition is assigned a unique identifier. This unique id is defined in the ProfileID option located in: (UNIX) <InstallDir>\wtm_wtx\datfiles\PathsAnalysis\default.ini (NT) <InstallDir>/wtm_wtx/datfiles/PathsAnalysis/ default.ini. Values: Enter the unique ids to use here. Separate multiple ids with a space. Use an asterisk (*) to specify all Path Analysis definitions. By default, this option specifies all definitions, indicated by an asterisk (*). Content Group definitions can be applied to all profiles or can be selected on a profile basis. Values: 1 Applies the definitions to all profiles. 0 Uses the values defined in the profile. Path Analysis definitions can be applied to all profiles or be selected on a profile basis. Values: 1 Applies the definitions to all profiles. 0 Uses the values defined in the profile. URL Parameter Analysis definitions can be applied to all profiles or only to those that you chose. Values: 1 Applies the definitions to all profiles 0 Uses the values defined in the profile. 192

195 Chapter 11: Running from the Command Line default setting IncludeURLReplacements UseGlobalURLReplacement Filters Description Specifies the URL Search and Replace definitions to apply to profiles. Each URL Replacement definition has a unique identifier. This unique id is defined in the ProfileID option located in: (UNIX) <InstallDir>\datfiles\urlreplacement\default.ini (NT) <InstallDir>/wtm_wdw/datfiles/urlreplacement/ default.ini Values: Enter the unique ids to use here. Separate multiple ids with a space. Use an asterisk (*) to specify all URL Replacement definitions. By default, this option specifies all definitions, indicated by an asterisk (*). URL Search and Replace definitions can be applied to all profiles or can be selected on a profile basis. Values: 1 Uses the definitions specified in the URL Search and Replace dialog box for all log analysis profiles. 0 Uses the settings defined in the profile. reports The settings in the reports section define the number of reports that are saved for each interval by default. Once this limit is reached, the oldest report is deleted to make room for the new one. When determining how many reports to store, consider how much disk space you want to devote to reports and how long you want to save them. A report using the Complete Summary template as it was installed needs KB. These settings correspond to the dailyreport, weeklyreport, monthlyreport, quarterlyreport, and yearlyreport settings in the [profile] section of the wtm_wtx.ini file. As an administrator, you can modify these setting on a profile basis. Nonadministrators can modify these settings if the histoverride option in the profiles section is set to 1. Note: If an option is not present, if it has a value of 0, or if it is blank, reports are not deleted. 193

196 WebTrends Enterprise Reporting Server Table Reports settings Reports settings dailystore weeklystore monthlystore quarterlystore yearlystore Description Specifies the default number of daily reports to save. Values: The default is 0. Specifies the default number of weekly reports to save. Values: The default is 0. Specifies the default number of monthly reports to save. Values: The default is 0. Specifies the default number of quarterly reports to save. Values: The default is 0. Specifies the default number of yearly reports to save. Values: The default is 0. Performance If you are analyzing a large number of log files, these settings help you manage the program performance. Table Performance settings Performance settings threadedanalysis Description This option specifies whether multiple processes are performed at the same time. Values: false Performs profile analyses one at a time. If your system lacks the resources, or if you want the processing of profiles handled one at a time set to false. true Analyzes more than one profile at once. If your system has fast processing or multiple CPUs, enabling threaded analysis may improve performance. 194

197 Chapter 11: Running from the Command Line Performance settings maxanalysis lookupqueuesize Description Enter the maximum number of profiles that can be processed concurrently. If your system has fast processing or multiple CPUs, increasing this number may improve performance. Values: The default is 1. Specifies the maximum number of records in the DNS lookup queue. Records enter the lookup queue and wait to be processed by one of the lookup threads. The lookup queue should be large enough to make use of the available lookup threads, but not so large that it uses too much memory. Each queue entry uses 2K of memory; if the lookup queue is too large, excessive swapping occurs. Values: (Default settings) (UNIX) 5000 (NT) Sample Performance settings [performance] maxanalysis = 1 threadedanalysis = true maxtablesizes Because all records in a log file must be analyzed to report accurate statistics, the database for many report tables can grow quite large. One such table is the Top Companies table. You can prevent these tables from using the memory required for other tables and graphs, by defining a maximum table size. Once the size is reached, the table is dropped, freeing the memory used to create it. If the maximum size is not reached, all records are analyzed, and an accurate report is displayed. 195

198 WebTrends Enterprise Reporting Server Table Max Table Sizes Settings Max Table Sizes setting topcompanies Description Limits the memory used to create the Most Active Organizations table and graph. Values: integer Sample MaxTableSizes [maxtablesizes] topcompanies=10000 language The language section defines the language that reports should be generated in. Table Language Settings Language settings country report Description Specifies the country that will be identified as the country of origin for reports. Values: The default is US Specifies the language to use for the report. Values: Enter one of the following: english french german english 196

199 Chapter 11: Running from the Command Line Profile The settings in the profile section are used as default settings for profiles created through the GUI.. Profile settings threadedreports debuglevel enablearchives processingtype startprocessingat logfileformat deferred reports dnsoverride Table Default profile settings Description Values: true Generates reports concurrently with analysis. This is the default. false Suspends analysis while reports are generated. Specifies the degree of verbosity when debugging the profile. Values: integer. Enter a value from A value of 10 provides the greatest detail. The default is 5. Specifies the default archiving setting for profiles. Values: 0 Disables archiving by default. 1 Enables archiving by default. The is the default setting. Specifies whether to analyze the entire log file or to analyze the log file beginning with the date specified for the startprocessingat option. Values: 0 All dates in the log file are analyzed. 1 The log file is analyzed from the date specified in the startprocessingat option to the end. This is the default setting. If processingtype is 1, the log file is analyzed beginning with the date specified here. Values: Enter a date in yyyy/mm/dd format. For example, This option is not currently used. This option is not currently used. This option is not currently used. 197

200 WebTrends Enterprise Reporting Server Profile settings dnslookup schedoverride startimmediately starttime period reportfileoverride Description Specifies the method of DNS lookup to use. A value of 0 disables DNS lookup and maintain the user data as it appears in the log file. Values: 1 Attempts to translate all IPs to domain names. 2 If you don t know the format of the log and want to turn DNS lookup on. Until a domain is found in the log, WebTrends attempts to translate all IPs. Determines whether non-administrators can define the report schedule settings for their profiles. Values: true Allows non-administrators to modify the schedule on a profile basis. false Allows only administrators to define analysis schedules on a profile basis. This is the default setting. Determines whether new profiles are processed for the first time immediately or at the scheduled time. Values: true New profiles are processed as soon as they are saved rather than waiting for the scheduled start time. This is the default. false New profiles are saved and processed when the scheduled time arrives. Specifies the schedule for starting profile analysis. If the schedoverride option is set to true, this value is used as the default which users can change on a profile basis. Values: Time in 24-hour format. The default is 00:00 Specifies how often the report is updated (in minutes.) Values: integer. The default is 15. Determines whether non-administrators can change the location of the profile database. Values: true Allows non-administrators to change the directory for the database on a profile basis. false Allows only administrator to change the location. 198

201 Chapter 11: Running from the Command Line Profile settings reportfile webservermodeoverride webservermode reportdestoverride reportdir reporturl Description Specifies the report template to use as the default for profiles. Note: Report template files have a.wct extension. By default they are located in the wtm_wtx directory. Values: string. For example, Complete_summary.wct Determines wether non-administrators can define the web server to use. Values: 1 Allows non-administrators to define the web server to use for reports on a profile basis. 0 The webservermode option setting is used. Specifies the web server to use for publishing reports. Values: webtrends Uses the built-in web server for publishing reports. This is the default. other Uses another web server. Determines whether non-administrators can define where reports are stored. Values: 1 Allows non-administrators to define the report directory and URL on a profile basis. 0 Uses the settings defined in this file. This is the default. If the webservermode option is set to other, this option defines the directory where reports for the profile are saved. Note: If you change the report directory, only reports created after the change appear in this location. Reports created before the change remain in the original location. Values: Default settings: (UNIX)./wtm_wtx/datfiles/reports/%PROFILE%.wlp (NT).\wtm_wtx\datfiles\reports\%profile%.wlp If the webservermode option is set to other, this option defines the URL for the report

202 WebTrends Enterprise Reporting Server Profile settings wtreportdir wtreporturl datadiroverride datadir showadmindatadir Description If the webservermode option is set to webtrends, this option defines the directory where reports are saved. Values: (Default settings) (UNIX)./wtm_wtx/datfiles/reports/%PROFILE%.wlp (NT).\wtm_wtx\datfiles\reports\%profile%.wlp If the webservermode options is set to webtrends, this option defines the URL for the report. Values: string. The default is %PROFILE%.wlp/index.html Determines whether non-administrators can change the database location. Values: true Allows non-administrators to define the location of the database directory on a profile basis. false Allows only administrators to change the database location in their profiles. The value for the datadir option is used for profiles created by non-administrators. This is the default. Specifies the directory for profile databases. Note: If you change the database directory, the reanalyzes the log file from the beginning. Databases created before the change remain in the original location. Values: (Default settings) (UNIX) /datfiles/databases/%profile% (NT) \datfiles\databases\%profile% Determines whether non-administrators can change the location of the database directory. Values: true Allows administrators to change the location of the database directory on a profile basis. false Uses the value defined in the datadir option. This is the default. This is the default setting. 200

203 Chapter 11: Running from the Command Line Profile settings histoverride Description Determines whether non-administrators can chose which reports they want to maintain for their profiles. Values: true Allows non-administrators to select the reports that are generated on a profile basis. false Uses the values in the weeklydata, monthlydata, quarterlydata, and yearlydata options for profiles created by non-administrators. This is the default. Tip: Setting this option to false can improve performance because you ll have more control over the amount of data maintained. You should only maintain data for the reports that you need. Note: The following settings specify the report intervals that are enabled by default. weeklyreport monthlyreport quarterlyreport yearlyreport Specifies the default profile setting for the weekly report option. Values: true Activates the monthly report option for profiles created through the GUI. false The monthly report option is not checked. Specifies the default profile setting for the monthly report option. Values: true Activates the monthly report option for profiles created through the GUI. false The monthly report option is not checked. Specifies the profile default setting for the quarterly report option. Values: true Activates the quarterly report option for profiles that are created through the GUI. This is the default. false The quarterly report option is not checked. Specifies the profile default setting for the yearly report option. Values: true Activates the yearly report option for profiles that are created through the GUI. This is the default. false The yearly report option is not checked. 201

204 WebTrends Enterprise Reporting Server Profile settings tempdir Description Specifies the directory location where zipped log files are unzipped. Values: (Default settings) (UNIX) /datfiles/databases/%profile%/.logtmp (NT) \datfiles\databases\%profile%\.logtmp on-demand report settings proxy If you access the Internet through a proxy server, you must configure these settings. Table Proxy settings Proxy setting enable httpserver httpport httplogin httppassword Description Specifies whether the settings in this section are used. Values: 1 These settings are used for logs accessed through a proxy server. 0 Proxy settings are not used. Specifies the host name of the proxy server. Values: string. For example, webtrendsproxy.net Specifies the port where the server resides. Values: For example, 8012 If users are required to authenticate, specify the user name here. Values: string. For example, gloriaf If users are required to authenticate, this option specifies the encrypted password. This setting can only be configured through the UI. Values: For example, D997BA1E82B A7F8ED0CEAB 202

205 Chapter 11: Running from the Command Line Proxy setting (httpplaintextpwd) Description If users are required to authenticate, this option specifies the plain text password. Use this option rather than httppassword if you are modifying this setting manually. Values: For example, titan. Once the file is initialized, the password is encrypted. FTP The [FTP] section defines settings used for log files that are accessed using FTP. Table FTP settings FTP settings ftptimeout ftpdir ftppersistantcachesize Description Specifies the timeout for FTP activity. If the program drops the connection after this limit is reached if it cannot successfully connect to the FTP server. Values: integer (seconds). The default is 30. Specifies the directory where log files are downloaded. A separate directory is created for each profile. Values: string. The default is./wtm_wtx/datfiles/ftp Specifies the maximum number of megabytes FTP logs can use. This governs the space available to ALL profiles. For example, if there are currently FTP logs using 80 MB of disk space, and a new profile is created that requires 30 MB to download the FTP files. The logs are downloaded, increasing the FTP cache size to 110 MB. Once the profile is analyzed, the new profile s log files are deleted until the disk space used by FTP logs is less than 100 MB. Values: integer. The default is

206 WebTrends Enterprise Reporting Server FTP settings usepassiveftp useabsolutepath Description There are two methods for transferring data from an FTP server to an FTP client: active and passive FTP transfer. When active FTP is used, the client opens a port and the server connects to the client. When passive FTP is used, the server opens a port and the client connects to the server. Passive FTP is preferable where there is a firewall between the client and the server. This is because firewalls are typically configured to block incoming connections that are not recognized. Although some firewalls can parse the FTP data requests and allow active FTP connections, many require passive FTP connections. Values: The default is true. true Passive FTP is used. false Active FTP is used. FTP paths can be read as relative paths or absolute paths. For example, given an FTP URL ftp://ftpserver/logs/ log1.log, if useabsolutepath is set to true, the absolute path, /logs/log1.log, is used. If useabsolutepath is set to false, the relative path,./logs/log1.log, is used. Values: The default is false. true FTP paths are read as absolute paths. false FTP paths are read as relative paths. Interface The [interface] section defines settings for the user interface. Table Interface settings Interface setting mode Description This option is maintained by the. Do not modify. It is used set up demo mode. In demo mode the ini files are not written to. It is either set to demo or blank. 204

207 Chapter 11: Running from the Command Line Interface setting maxgridprofiles prostatrefresh maxrefresh showbrowsermenu ErsAddress Description Specifies the number of profiles that can be viewed on the main console. To view more profiles in the list, increase the value. Once this value is reached, a dialog box opens allowing you to specify criteria for displaying profiles. Values: By default, this option is set to 50. Specifies how often the selected profile s status on the main console is updated. Enter the value in seconds. This option works in conjunction with the maxrefresh option. For, example to update the profile status every 5 seconds, set the postatrefresh to 5. To refresh the status a maximum of 100 times, set maxrefresh to 100. Values: integer (seconds). The default is 10. Number of times to refresh the selected profile's status on the main console before stopping. maxrefresh and postatrefresh together allow the page to refresh for a reasonable amount of time and then stop in order to relieve the server s time. Note: If the user clicks the Refresh/Reload button on the browser, the count is reset to 1. Values: integer. The default is 100. Specifies whether or not the tool bar for the browser is displayed. Values: true Displays the browser tool bar. false Hides the browser tool bar. This is the default. Specifies the port number that the analysis engine uses to communicate server status back to wtinterface. Values: The default port is

208 WebTrends Enterprise Reporting Server maxtablesizes Because all records in a log must be analyzed to report accurate statistics, the database for many report tables can grow quite large. To prevent these tables from using the memory required for other tables and graphs, you can define a maximum table size. Once the size is reached, the table is dropped, freeing the memory used to create it. If the maximum size is not reached, all records are analyzed, and an accurate report is displayed. These options can be entered in the [defaults] section. Table MaxTableSizes section settings MaxTableSizes setting Top404Errors TopAuthUsers TopBandwidth TopCities TopCompanies TopCountries TopDirectory Description Limits the memory used to create the Client Errors table. Values: integer Limits the memory used to create the Top Authenticated Users table. Values: integer Limits the memory used to create the Bandwidth graph and Summary of Activity table. Values: integer Limits the memory used to create the Most Active Cities table and graph. Values: integer Limits the memory used to create the Most Active Organizations table and graph. Values: integer Limits the memory used to create the Most Active Countries table and graph. Values: integer Limits the memory used to create the Most Accessed Directory table and graph. Values: integer

209 Chapter 11: Running from the Command Line MaxTableSizes setting TopDownloads TopFormErrors Description Limits the memory used to create the Most Downloaded Files and Most Downloaded File Types tables and graphs. Values: integer Limits the memory used to create the Dynamic Pages and Forms Errors table and graph. Values: integer Feedback The [feedback] section specifies the URL for the product feedback page on the WebTrends Corporation web site. Table Feedback settings Feedback settings url Description Specifies the feedback page on the WebTrends Corporation web site. Values: The URL is products/ers/feedback.htm UNIX The settings in the UNIX section specify the ids for running as a daemon or as root as well as the number of handles for processing. Table UNIX settings Unix settings uid Default Specifies the user id of the user the daemon should run as. Values: Linux: By default this value is set to 1, which is the id for bin user. Solaris: By default this value is set to 2, which is the id for bin user. 207

210 WebTrends Enterprise Reporting Server Unix settings gid handles Default Specifies the group id of the group the should run as. Values: By default this value is blank. Specifies the number of handles allocated for processing. A handle is used for each log file it processes and several for creating reports. Depending on the number of log files being processed, all available handles may be exhausted. Consequently, the number of file handles must be increased to a number suitable to the number of log files the server accesses during analysis. The required number of handles is the number that would be analyzed at any one time, not the total of all log files to be analyzed. For example, a server may use 5 profiles, each with 10 log files to analyze. The unbounded number of required handles would be 5*10, or 50 handles. However, if the maximum number of concurrent analysis is limited to 2 profiles, only 20 handles are required during a single analysis. Add at least 5 for report generation, and a handle for each of the expected maximum number of simultaneous connections to the web server (currently set at 5). Note: If the server is started at system boot time, and handles= is left blank, the number of available handles is set to either unlimited for root, and the maximum resource limit for non-root users. Alternatively, the allocated number of file handles can be changed by using the 'ulimit' command. For example, 'ulimit -n 128' will increase the number of available file handles to 128. 'ulimit -n' displays the current file handle setting. Values: By default this value is set to

211 Chapter 11: Running from the Command Line Unix settings usesymlinks resolve Default Allows you to use symbolic links for resource directories to save drive space. Values: true sets up a symbolic link for the images and CordaJava directories. false symbolic links are not used and an images and CordaJava directory is maintained for each profile database. This is the default. Allows you to set an environmental variable to decrease the timeout for DNS lookups. The option applies only to Solaris 2.6 and 2.7. Enabling this option adjusts the timeout setting and number of retries for DNS lookups for the. The DNS lookups for other system processes are not affected. See the man page for resolve.conf for more information on the resolve setting. Values: retrans Specifies the number of seconds for the DNS timeout. retry Specifies the number of attempts made to connect to the DNS server. For example, options retrans:1 retry:1 209

212 WebTrends Enterprise Reporting Server Configuring Web Server Settings The wt_remote.ini file contains settings that apply to wtct_ui which runs the remote interface. Audit The [audit] section specifies settings for the wtct_ui audit file. The audit file contains messages about remote interface processes. Table Audit settings Audit setting logdir logfile debuglevel Description Specifies the location of the audit file for wtinterface. Values: string. (UNIX) /datfiles/statuslogs (NT) \datfiles\statuslogs Specifies the name of the audit file.wtinterface.audit Specifies the degree of verbosity for the audit file. Values: integer A value of 10 provides the greatest detail. The default is 1. Remote Configuration The settings in the [RemoteConfiguration] section are used to configure the web server that runs the interface though a Web browser. Table Remote configuration settings Remote settings ERSRetries ERSTimout Description Specifies the number of times attempts to connect to wtrs. Values: integer. The default is 30. Specifies the number of seconds that waits for a response from wtrs. Once this limit is reached, a retry is made until the maximum number of retries is reached. Values: integer. The default is

213 Chapter 11: Running from the Command Line Remote settings OSAuthentication WebAddress WebLogFileName WebUserTimeout WebLogErrors Description Determines the authentication method used. Values: 1 Uses the operation system authentication. The program checks to see if the user logging in has a valid account on the machine and that it matches the user name and password used to log in. 0 Uses the program authentication database. When setting up users for the program, you define user names and passwords to use. This is useful if you want to allow people to log in who do not have accounts on the operating system. Note: Program passwords are base 64 encoded. Specifies the port for the web server. This is the port defined when the program was installed. Make sure the port is not used by any other service. Values: The default is. The default port for root installations is. The default port for non-root installations is The OS requires you to use port 1024 or above. Make sure the port is not used by any other daemon or service. Specifies the file path for the web server log file. Values: (Default settings) (UNIX)./wt_remote.log (NT).\wtx_remote.log Specifies the length of the user timeout before the user is disconnected from the server. Values: integer (seconds). The default is 300. Trace messages sent from the web server are stored in the wtm_remote.err file. This option specifies the degree of verbosity in the file. Values: integer (1-15). A value of 1 generates minimal messages. The default is

214 WebTrends Enterprise Reporting Server Authentication The [authentication] section defines preferences for authenticating users. Table Authentication settings Description methods Default If OSAuthentication is enabled, this option specifies the authentication method to use. supports PAM, passwd, and shadow. implements them in the following order: PAM, passwd, shadow. Values: string. Separate your entries with a space. By default this is set to password shadow PAM (Plugable Authentication Module) If PAM is installed on the system and you want to use it as the authentication method for the, include PAM as one of the values. In the case that PAM fails, you should also specify a backup method. Passwd Uses the user information and password from the passwd file. This method is not as secure as the others; although it is encrypted, anyone can read the passwd file. Shadow Uses the user information from the pass.wd file and the password from the shadow file. Shadow is considered more secure than the password method because the shadow file is only readable by super users. UNIX The settings in the unix section specify the ids for running the service as well as the number of handles available for the interface. Table Unix settings Unix settings uid Default Specifies the user id of the user the wtinerface daemon/ service should run as. Values: Linux: By default this value is set to 1, which is the id for bin user. Solaris: By default this value is set to 2, which is the id for bin user. 212

215 Chapter 11: Running from the Command Line Unix settings gid handles Default Specifies the group id of the group wtct_ui should run as. Values: By default this value is blank. Specifies the number of handles allocated for connections to the web server. wtct_ui uses one handle for each web server connection, one for each user logged into the interface, and one or more for every cgi script. Note: If the server is started at system boot time, and the handles field is left blank, the number of available handles is set to either unlimited for root, or to the maximum resource limit for non-root users. Alternatively, the allocated number of file handles can be changed by using the ulimit command. For example, ulimit - n 128 increases the number of available file handles to 128. ulimit -n displays the current file handle setting. Values: integer. By default this value is set to 64. Setting Up User Accounts and Permissions Use the.usr file to define users who have access to the program and their authentication information. Each user has his/her own.usr file which specifies authentication information, permissions, restrictions, and default settings for profiles. Through the.usr file, you can also specify dialog boxes that you want to hide from the user. Because the settings in these files override those in the wtm_wtx.ini file, you can completely customize the profile interface for each user. When you install the program, an anonymous.usr and %installuser%.usr (the person who installs the program) are created. To create a new user, copy a.usr file and modify it accordingly. The options in the.usr file are described in the sections that follow. Userinfo The [userinfo] section defines the authentication for the user and level of permission. 213

216 WebTrends Enterprise Reporting Server Table User info settings User info settings permissions username password plaintextpwd Example Specifies the user s access rights. Values: integer The default is Administrator rights. 0 public access only. See User Permission settings on page 216 for details. Specifies the user s operating system user name. Value: string. For example, migueld If the OSAuthentication option is set to 0 in the wtm_remote.ini file, this value specifies the password for the user. If OSAuthentication is set to 1, leave this setting blank. Values: string or blank. If the OSAuthentication option is set to 0 in the wtm_remote.ini file, this value specifies the password for the user. Allows you to enter a user password from the command line. Once the new.usr file is initialized, the plain text password is encrypted. Values: string. For example, oldcat7 Permissions The permissions option allows you to control the program features that a user can access. Minimally, you can set up a user who only is allowed to view reports. On the other end of the spectrum, you can give users Administrator rights which allows them to work with all profiles, view reports, create user accounts, modify program settings, and view status log and licensing information. The most that a non-administrator may do is view reports and create, modify, and delete profiles. Because the Reporting Server translates the value you enter to hexadecimal, any combination of permissions is possible. The permissions in the following table correlate to the options in the User Information dialog box. For example, a user with a permission level of 1 is given Administrator rights, allowing complete access to the program. A user with a permission level of 15 is also given Administrator rights. The difference 214

217 Chapter 11: Running from the Command Line is in the way the permissions appear through the GUI, as shown in the following examples. Permission Example: User Value of 1 Figure Permission value of 1 This graphic shows a user with a permission level of 1. If you were to uncheck Administrator rights box, the user would be left with a permission level of

218 WebTrends Enterprise Reporting Server Permission Example: User Value of 15 Figure Permission value of 15 This graphic shows a user with a permission level of 15. If you were to uncheck Administrator rights box, the user would be left with a permission level of 14, still able to create, modify and delete profiles. Table User Permission settings Value Permission 0 view reports 2 create profiles 4 modify profiles 6 create and modify profiles 8 delete profiles 10 create and delete profiles 12 modify and delete profiles 14 create, modify and delete profiles 15 administrator, create, modify and delete profiles 216

219 Chapter 11: Running from the Command Line filter[n] The [filter] section specifies any filters that you want to include as defaults for the user. If you hide the Filters dialog box from the user, the filters you specify are used for every profile the user creates. See Filters on page 225 for details on defining filters. profile The [profile] section allows you to define default profile settings for this user. If you want to make creating profiles easier for the user, define the defaults you want them to use here. See Profile on page 218 for details on defining profile settings. Tip: To make the profile interface even simpler and more secure, use the restrictions section to hide dialog boxes with settings you don t want this user to modify. restrictions The [restrictions] section specifies the profile dialog boxes to hide from the user and the maximum number of profiles the user can create. If a dialog box is hidden from the user, the Reporting Server uses the settings in the profile section in the analysis instead of the values in the.wlp file. Note: Restrictions only apply if the advanceduserenabled option is set to 1. Table Restriction settings Working with Profiles Note: By default, the settings for each profile are stored in the /datafiles/profiles (UNIX) or \datafiles\profiles (NT) directory. Profiles have a.wlp extension. A sample profile is provided,. 217

220 WebTrends Enterprise Reporting Server Server[n] If you purchased a Server Add-On, you can report on activity for web sites that reside on multiple servers (including server clusters). The [server[n]] section defines the name and the location of the log files for each server. If you are analyzing activity from multiple servers, create a server[n] section for each server that hosts your web site. Table Server settings Server setting servername logfilepath[n] Description Specifies the name for this server. Value: string. For example, brazil. Specifies the path to the log file. Value: string. For example, (UNIX) (NT) Profile The settings in this section define the location of the log file on which you are reporting, and how the data in the log file should be analyzed and reported on. Note: If a value is left blank, the default defined in the file is used. Table Profile file settings Profile settings version description Description Specifies the version number of the program. Do not modify this setting. Values: For example, version 3.0 Specifies the name for the profile which is used to identify the profile in the UI and as a heading for the report. Values: string. For example, daily_analysis 218

221 Chapter 11: Running from the Command Line Profile settings processingtype startprocessingat IsServerCluster users logfilepath homepagedefaults homepagebasedir dailyreport Description Specifies whether to analyze the entire log file or to analyze the log file beginning with the date specified for the startprocessingat option. Values: 0 All dates in the log file are analyzed. 1 The log file is analyzed from the date specified in the startprocessingat option to the end. This is the default. If processingtype is 1, the log file is analyzed beginning with the date specified here. Values: date (yyyy/mm/dd). For example, Specifies whether the web site resides on a single server or on multiple servers. Values: 0 Use if the site is hosted on one server. 1 Use if the site resides on multiple servers. Comma-delimited list of users who have access to the profile. Values: string. To allow users to view the profile publicly, without a user name or password, enter "anonymous." Specifies the path to the log file to be analyzed. Values: string. For example, /datfiles/samples/sample.log (UNIX) \datfiles\samples\sample.log (NT) Enter./(UNIX) or.\ (NT) to specify a path relative to the program installation directory. Note: If the IsServerCluster option is set to 1, this value is not read. Specifies the pages that the web server defaults to when a visitor requests a URL without a specific page. Values: string. For example, default.htm default.html index.htm index.html default.asp. Separate multiple pages with a space. Specifies the URL of the root of the web site. Values: string. For example, file:///../samples/ (UNIX) file:///..\samples\ (NT) Determines whether the daily report is generated for this profile. Values: true Generates a daily report. false No daily report. 219

222 WebTrends Enterprise Reporting Server Profile settings datadir debuglevel deleted disabled enablearchives dnslookup logfileformat Description Specifies the directory for this profile s databases. Values: string. For example, /datfiles/databases (UNIX).\wtm_wtx\datfiles\databases (NT) Note: If you modify the directory, the log file is reanalyzed from the beginning to rebuild the database. This is because the original database remains in the old location. Specifies the degree of verbosity when debugging the profile. Values: integer A value of 10 provides the greatest detail. Allows you to mark the file for deletion. The profile will not be displayed in the UI. Values: true Marks the file for deletion. false The file will not be deleted. Allows you to disable or enable the profile. Values: true Suspends any new analysis. The profile can still be used (modified or viewed) and completed reports are still accessible through the Report Viewer. false Enables the profile for analysis and reporting. Allows you to enable or disable archiving for this profile. Values: 0 Disables archiving. 1 Enables archiving. Specifies the method of DNS lookup to use for this profile. Values: 0 Disables DNS lookup and maintain the user data as it appears in the log file. 1 Attempts to translate all IPs to domain names. 2 If you do not know the format of the log and want to turn DNS lookup on. Until a domain is found in the log, WebTrends attempts to translate all IPs. Specifies the format of the log file. Values: integer Note: In most cases, you should select 0 and let the automatically detect the format of the log. 220

223 Chapter 11: Running from the Command Line Profile settings monthlyreport period quarterlyreport reportdir reportfile reporturl starttime threadedreports Description Allows you to generate a monthly report for this profile. Values: true Generates a monthly report. false No monthly report. Defines the repeat interval for analyzing the log file and creating the report. Values: integer (minutes). Allows you to generate a quarterly report for this profile. Values: true Generates a quarterly report for this profile. false The quarterly report is not generated. If webservermode is set to other, this option defines the directory path where reports for this profile are saved. Note: If you modify the report directory, only new reports appear in the new directory. Reports created before the change remain in the original location. Values: string. For example, /hosting/server2/reports/ %PROFILE%.wlp (UNIX) \hosting\server2\reports\%profile%.wlp (NT) Specifies the report template to use for this profile. Note: Report template files have a.wct extension and are located in the wtm_wtx directory. Values: string. If webservermode option in wtm_wtx.ini is set to other, this option defines the URL to the report index html file. Values: string. For example, %PROFILE%/index.html Specifies the start time of an analysis and reporting cycle in hh:mm. If the schedoverride option is set to true, this value is used as the default which users can change on a profile basis. Values: time (00:00 23:59). For example, 12:00. This option is no longer used. 221

224 WebTrends Enterprise Reporting Server Profile settings weeklyreport wtreportdir wtreporturl yearlyreport IncludeContentGroups IncludeQueries Description Allows you to generate a weekly report for this profile. Values: true Generates a weekly report. false The weekly report is not generated. Do not change this value. If webservermode is set to webtrends, this option defines the directory where reports for this profile are saved. Note: The reports directory refers to a mapped directory for security purposes. If webservermode is set to webtrends, this option defines the URL to the report index html file. Note: The reports directory is case-sensitive. This is because requests to the report directory are sent to a mapped directory above the web server. Values: string. For example, %PROFILE%/index.html Allows you to generate a yearly report for this profile. Values: true Generates a yearly report. false The yearly report is not generated. Because Content Group definitions are global settings that can be referenced in multiple profiles, each definition is assigned a unique identifier. Values: Enter the unique id here. Separate multiple identifiers with a space. An asterisk (*) specifies all Content Group definitions. The unique id is defined in the ProfileID option which is in the default.ini file in <InstallDir>\datfiles\contentgroups (NT) <InstallDir>/datfiles/contentgroups (UNIX) Because URL Parameter Analysis definitions are global settings that can be referenced in multiple profiles, each definition is assigned a unique identifier. Values: Enter the unique id here. Separate multiple identifiers with a space. Use an asterisk (*) to specify all URL Parameter Analysis definitions. The unique id is defined in the ProfileID option which is in the default.ini file in <InstallDir>\wtm_wtx\datfiles\dynamicpages\default.ini<InstallDir >/wtm_wtx/datfiles/dynamicpages/default.ini 222

225 Chapter 11: Running from the Command Line Profile settings IncludeURLReplacement s IncludePathsAnalysisP rofiles tempdir Description Because URL Search and Replace definitions are global settings that can be referenced in multiple profiles, each definition is assigned a unique identifier. Values: Enter the unique id here. Separate multiple identifiers with a space. An asterisk (*) specifies all URL Search and Replace definitions. The unique id is defined in the ProfileID option which is in <InstallDir>\wtm_wtx\datfiles\urlreplacement\default.ini <InstallDir>/wtm_wtx/datfiles/urlreplacement/default.ini. Because Path Analysis definitions are global settings that can be referenced in multiple profiles, each definition is assigned a unique identifier. Values: Enter the unique id here. Separate multiple identifiers with a space. Use an asterisk (*) to specify all Path Analysis definitions. The unique id is defined in the ProfileID option which is in the default.ini file in <InstallDir>\wtm_wtx\datfiles\pathsanalysis\default.ini <InstallDir>/wtm_wtx/datfiles/pathsanalysis/default.ini Specifies the directory location where zipped log files are unzipped. Values: string. For example,./wtm_wtx/datfiles/databases/ %PROFILE%/.logtmp Table Log file format parameters A value of Specifies this format 0 Auto-detect log file type 1 Apache Extended Format 2 CerfNet 3 CERN Common 4 Emwac log format 5 Lotus Domino 6 IBM Intenet Connection Secure Server 7 Microsoft IIS 1.x, 2.x, 3.x. 8 Microsoft IIS US date format 223

226 WebTrends Enterprise Reporting Server A value of Specifies this format 9 Microsoft IIS European Date Format 10 Microsoft IIS Japanese Date Format 11 Microsoft IIS Extended 12 Microsoft Extended + Cookies 13 Microsoft IIS Virtual 14 NCSA Combined/Extended 15 NCSA Combined Multihome 16 NCSA Common 17 NCSA Common Multihome 19 Netscape Combined 20 Netscape Common 21 Netscape NSAPI Extended 23 Novell Web Server 24 Open Market Extended 25 Oracle Log Format 26 Other Common 27 Other Extended 28 Purveyor Extended 29 Purveyor Multi-home 30 Spry Log format 31 Web site combined multi-homed format 32 Web site common multi-homed format 33 Web site Windows log file format 34 Web site Windows US date format 35 Web site Windows European date format 36 Web site Windows Japanese date format 224

227 Chapter 11: Running from the Command Line Filters You can apply filters to profiles for more focused reports. Filters specify the data in the log file that you want to be analyzed. Table Filter settings Field name filtertype defaultoveride returncodes returncodesenabled Description Specifies a name for the filter. This is how the filter is identified in the user interface. Values: string. Specifies the function of the filter. Values: include Analyzes only data that matches the settings in this section. exclude Analyzes all log file data but the data that you specify. Values: 1 Ignores the values defined in this section. 0 Uses them. Use the Return Code filter to specify the types of web server results you want to include or exclude. Values: For example, if you want to only report on successful hits, enter the codes for successful requests ( ) The default, all return codes, is indicated by an asterisk (*). Note: Separate multiple entries with a space. Values: 1 Uses the value of the returncodes option in the analysis. 0 Ignores it. 225

228 WebTrends Enterprise Reporting Server Field users usersenabled multihomedomain multihomedomainenabled Description Use the Users filter to include or exclude hits coming from specific domains, subnets, or IP addresses from the results of this profile. Values: For example, you can create a filter that excludes all activity from your own domain. Use wildcards to specify a set of IPs. The default, all IPs/domains, is indicated by an asterisk (*). Allows you to enable the users filter. Values: 1 Uses the value of the users option in the analysis. 0 Ignores the users value. If your log file contains entries for more than one web site, you can use this option to report on activity for a single site. Values: For example, if your multi-homed log file contains activity from domains and and you want to report only on you would specify include as the filtertype and for the multihomedomain value. Note: This filter only applies to multi-homed log files. Use this filter to filter domains visited, not domains where users are coming from. Allows you to enable the multihome domain filter. Values: 1 Uses the value of the multihomedomain option in the analysis. 0 Ignores the multihomedomain value. 226

229 Chapter 11: Running from the Command Line Field directory includesubdirs Description Use this option to filter the activity of a specific directory by entering the directory path here. Values: string. The default for an include directory filter is to view all directories starting at the root, indicated by a slash (Unix: / Windows: \). There is no default for an exclude directory filter. Note: Use quotation marks around directories containing spaces or commas. Allows you to include/exclude sub-directories in the directory filter. Values: 1 Filters the subdirectories of the directory specified in the directory option. The default for both include and exclude filters is to filter all subdirectories. Therefore, if you created an exclude filter for a directory, WebTrends automatically excludes the subdirectories. If you created an include filter for a directory, WebTrends automatically includes the subdirectories. 0 Sub-directories are not filtered. directorycasesensitive Allows you to make the directory filter casesensitive. Values: 1 Makes the directory option casesensitive. 0 Not case-sensitive. directoryenabled files Allows you to enable the directory filter. Values: 1 Uses the value of the directory option in the analysis. 0 Ignores it. Use this option to filter specific files. Values: string. Enter the file name or extension in this field. The default for an include files filter is to include all files, indicated by *.* in the field. There is no default for an exclude filter. 227

230 WebTrends Enterprise Reporting Server Field filescasesensitive includedefaultpages filesenabled referrer referrerenabled adclick Description Allows you to make the files filter case-sensitive. Values: 1 Makes the files option case-sensitive. 0 Not case-sensitive. Allows you to include/exclude default pages in the filter. Values: 1 Includes requests for the file that are submitted without the file name. 0 Default pages are not included in the file filter. Allows you to enable the files filter. Values: 1 Uses the value of the files option in the analysis. 0 Ignores it. The referrer filter helps you analyze the number and quality of users coming to your site from other sites or from a specific Internet advertisement link. Referrer entries should begin with a * prefix, and unless you mean only the exact string entered, also include an ending * as well. The default for the referrer include filter, all referrers, filters all hits with referring data regardless of site. The default for the referrer exclude filter, no referrers, filters only hits without any referring information. A filter entry of filters any hits prefixed by Values: string. Values: 1 Uses the value of the referrer option in the analysis. 0 Ignores it. Allows you to filter an advertisement click defined in the adviews.txt file. Values: string. 228

231 Chapter 11: Running from the Command Line Field adview adsenabled searchkeywords searchkeywordsenabled username usernamecasesensitive usernameall usernameenabled Description Use the adview option to filter an advertisement view defined in the adviews.txt file. Values: string. Allows you to enable the advertising filter. Values: 1 Uses the value of the adclick or adview options in the analysis. 0 Ignores it. This option is not used. This option is not used. If you have an Intranet or a web site that requires visitors to log on with a user name and password, you can use the user name option to filter activity based on authenticated user data. Values: string. Enter the user name to filter. Allows you to make the user name filter case-sensitive. Values: 1 Makes the user name option case-sensitive. 0 Not case-sensitive. Allows you to filter all authenticated users. Values: 1 Filters all data containing an authenticated user name. In an include filter, only data containing an authenticated user name is included in the analysis. In an exclude filter, all data containing an authenticated user name is excluded from the analysis. 0 Only the user names specified in the username option are filtered. Values: 1 Uses the value of the username option in the analysis. 0 Ignores it. 229

232 WebTrends Enterprise Reporting Server Field browser browserenabled days daysenabled Description Use the browser option to filter hits from a specific browser, spider or robot. Values: string. Enter the browser as it appears in the agent field of the log file. Note: Because the program looks for the filter text anywhere in the agent field of the log record, any wildcards (* or?) you enter are ignored. Filtering for Netscape Navigator may not return accurate results because many browsers identify themselves as Netscape Navigator. Allows you to enable the browser filter. Values: 1 Uses the value of the browser option in the analysis. 0 Ignores the browser value. Use the days option to filter days of the week. Values: Monday =1 Tuesday =2 Wednesday =3 Thursday =4 Friday =5 Saturday =6 Sunday =0 Separate your entries using spaces. Allows you to enable the days filter. Values: 1 Uses the value of the days option in the analysis. 0 Ignores the days value. hourbegin Specifies the start range for the hour filter in 24- hour format. Values: time (hh:mm). 230

233 Chapter 11: Running from the Command Line Field hourend hourall/none hourenabled entrypage entrypageenabled Description Allows you to filter the analysis by time of day in 24-hour format. Values: time (hh:mm). Enter the time using 24-hour format. Allows you to filter all hours of the day Values: 1 If you are creating a filter type of include, setting this value to 1 includes all hours of the day in the analysis. If you are creating a filter type of exclude, setting this value to 1 excludes all hours of the day. 0 If you are filtering for hours of the day, this option should be set to 0. Allows you to enable the hour filter. Values: 1 Uses the value of the hourbegin and hourend options in this profile. 0 Does not use the hourbegin and hourend values. To filter the analysis for visitor sessions based upon the first page a visitor viewed. An entry page is the first item that the visitor requests in a session. The item could be an image, a document, or a file. Values: string. For example, entering / browser.htm filters any session starting at browser.htm in the root directory. Allows you to use the entry page filter. Values: 1 Uses the value of the entrypage option in the analysis. 0 Ignores it. 231

234 WebTrends Enterprise Reporting Server Field entrypagecasesensitive Description Allows you to make the entry page filter casesensitive. Values: 1 Makes the entrypage option case-sensitive. For your filter to be used, the log file data must match the case of the filter. 0 Not case-sensitive. Working with Content Groups The default.ini file in the contentgroups directory contains settings for the Content Groups feature. Default Content Group The default section specifies the number of Content Group definitions. Table Default Content Group settings Default setting ContentGroupProfileCount Description Specifies the number of Content Group definitions in this file. For example, if the file contains six definitions, enter 6 here. 232

235 Content Group definition Chapter 11: Running from the Command Line The settings for each Content Group are defined in the ContentGroupProfile[n] section. Name the first definition ContentGroupProfile0, and increment subsequent definitions by 1. Table ContentGroupProfile settings Content Group Setting MatchString[n] Description Specifies the URL pattern to match. Log file records that match this string are reported on as this group. Values: string. Note: Increment each MatchString option by 1. For example, MatchString1=string, MatchString2=string. PageType This option must be set to 4. ProfileID ProfileName ProfileVersion Specifies the unique id to identify this definition in the profile file or in the wtm_wtx.ini file. It can be created automatically through the UI or by you manually. Values: string. For example, 2mGbS4IrCR4 Specifies the name of the definition which identifies it in the UI. Values: string. For example, orders. This option is used by the analysis engine and should always be set to

236 WebTrends Enterprise Reporting Server Sample Content Groups default.ini [Default] ContentGroupProfileCount = 6 [ContentGroupProfile0] MatchString0 = /loganalyzer PageType = 4 ProfileID = 2mGbS4IrCR4 ProfileName = Intranet ProfileVersion = 1 [ContentGroupProfile1] MatchString0 = /prosuite PageType = 4 ProfileID = ODVwHKirCR4 ProfileName = Pro Suite pages (sample) ProfileVersion = 1 [ContentGroupProfile2] MatchString0 = /enterprise PageType = 4 ProfileID = Yn1I8MjrCR4 ProfileName = Enterprise pages (sample) ProfileVersion = 1... Working with Path Analysis Settings The default.ini file in the pathsanalysis directory contains settings for the Path Analysis definitions. See Path analysis on page 166 for details. 234

237 Default Path Analysis settings Chapter 11: Running from the Command Line The default section specifies the number of Path Analysis definitions. Table Default Path Analysis settings Default setting PathsAnalysisProfileCount Description Specifies the number of Path Analysis definitions in this file. For example, if the file contains six definitions, enter 6 here. Path Analysis definition settings The settings for each Path Analysis definition are configured in the pathanalysisprofile[n] sections. Name the first definition PathsAnalysisProfile0 and increment subsequent definitions by 1. Table pathanalysisprofile settings Path analysis settings root depth profileid Description Specifies the page that you want to track. Values: string. For example, /products/promotion.asp Specifies the depth of the path analysis. For example, a value of 5 tracks the 5 pages that visitors went to from the specified page. Specifies the unique id required to identify the definition in the profile file or the wtm_wtx.ini file. This value is generated automatically for definitions created through the UI, but you can assign it yourself for definitions that are created manually. Values: string. For example, a pagetype This option must be set to 4. profileversion maxtableentries This option is used by the analysis engine and should always be set to 1. Specifies the maximum number of paths that you want to track. Values: integer (1000 and 32000). 235

238 WebTrends Enterprise Reporting Server Path analysis settings profilename Description Specifies the name that identifies the definition in the UI. Values: string. For example, from promotions page. Working with URL Parameter Analysis Settings The default.ini file in the dynamicpages directory contains settings for the URL Parameter Analysis definitions.see Configuring web server settings on page 148 for an overview. Default URL Parameter Analysis settings The default section specifies the number of URL Parameter Analysis definitions. Table Default URL Parameter Analysis settings Default setting QueryProfileCount Example Specifies the number of URL Parameter Analysis definitions in this file. For example, if the file contains two definitions, enter 2 here. Values: integer. URL Parameter Analysis definition settings The settings for each URL Parameter Analysis definition are configured in the QueryProfile[n] sections. Name the first definition QueryProfile0,and increment subsequent definitions by 1. Table QueryProfile settings Query profile settings page Example Specifies the page that you want to track for this definition. Values: string. /download.asp 236

239 Chapter 11: Running from the Command Line Query profile settings profileid mapfile Example Specifies the unique id required to identify the definition in the profile file or the wtm_wtx.ini file. This value is generated automatically for definitions created through the UI, but you can assign it yourself for definitions that are created manually. Values: string. For example, J6QCcdSvCR4 Specifies the file path to the translation file relative to the installation directory. Values: string. For example,..\datfiles\dynamicpages\solutions.txt pagetype This option must be set to 4. parameter profilename profileversion Specifies the parameter that you want to track in this definition. Values: string. For example, products. Specifies the definition name which identifies it in the UI. Values: string. For example, Product Downloads (Sample) This option is used by the analysis engine and should always be set to 1. Working with URL Search and Replace Definitions The default.ini file in the urlreplacement directory contains settings for the URL Search and Replace definitions. for an overview. 237

240 WebTrends Enterprise Reporting Server Default URL Search and Replace The default section specifies the number of URL Search and Replace definitions. Table Default URL Search and Replace settings Default setting urlreplacementrofilecount Description Specifies the number of URL Replacement definitions in this file. For example, if the file contains two definitions, enter 2 here. Values: integer. URL Replacement definition The settings for each URL Replacement definition are configured in the urlreplacementprofile[n] sections. Name the first definition urlreplacementprofile0 and increment subsequent definitions by 1. Table URL replacement settings URL Replacement setting profilename profileid Description The definition name which identifies it in the UI. Values: string. For example, My_Shopping_Cart Specifies the unique id required to identify the definition in the profile file or the wtm_wtx.ini file. This value is generated automatically for definitions created through the UI, but you can assign it yourself for definitions that are created manually. Values: string. For example, a pagetype This option must be set to

241 Chapter 11: Running from the Command Line URL Replacement setting trailermatchtype leadinstring usegatestring gatestring Description Specifies the method to signal the beginning of the replacement. Values: startofstringpattern Replaces the text beginning with the start of the URL. startoffirstpattern Replaces from the beginning of the first occurrence of text specified. startoflastpattern Replaces from the beginning of the last occurrence of text specified. endoffirstpattern Replaces from the end of the first occurrence of the text specified. endoflastpattern Replaces from the end of the last occurrence of the text specified. The character or string that signals the beginning of the text to be replaced. Values: character or string. Separate multiple entries with a pipe ( ). Multiple entries are read as "OR" statements. Allows you to specify text that must be present for the replacement to be made. Values: N The value of the gatestring option is not read. Y The value of the gatestring option is read, and the replacement is performed only if the text specified appears in the URL. The URL must contain the text specified in order to make the replacement. Values: string. 239

242 WebTrends Enterprise Reporting Server URL Replacement setting leadinmatchtype trailerstring replacementstring usetotracksession profileversion Description Specifies the method to use to signal the end of the replacement. Values: startofnext Ends the replacement before and not including, the character specified in the trailerstring option. endofnext Ends the replacement with, and including, the character specified in the trailerstring option. endofstring Ends the replacement at the end of the URL. The text that signals the end of the text you want to replace. Values: character or string. For example, ; Specifies the text to use in place of the string you want to remove. Values: string. For example, 1234 Allows you to use the text that was replaced to track user sessions rather than an IP, user name, or cookie. Values: Y uses the replaced text to track visitor sessions. N does not use the replaced text. This option is used by the analysis engine and should always be set to 1. Defining Advertisements to Track You can set up advertisements that you want to track in the adviews.txt file. The adviews.txt file allows you to configure Ad Views and Clicks. With Ad Views and Clicks, you can determine the number of visitors to your web site who view or click on a particular ad. Additionally, WebTrends includes an Advertising filter with which you can profile a specific advertisement s traffic patterns (for example, busiest time of the day, day of the week) as well as demographic information (for example, top viewing/clicking organizations, country of origin). 240

243 Ad Views and Ad Clicks syntax Chapter 11: Running from the Command Line Enter your advertisement in the following format: "<ad view file name>","<ad click id string>","<description>" Sample advertisement "IBM_AD.GIF","/cgi-bin/IBM_AD.PL","IBM Laptop Ad" Setting Up Your Intranet Domains The wtintra.txt allows you to define areas of your intranet or other domain s by department, city, state or even individual workstations. Use the following syntax: <IntranetDomain>,<Description>,<City>,<State/ Province>,<Country>,<IPAddress/Pattern/Subnet> where: <IntranetDomain> Specifies the domain name of the department or division of your organization (i.e., marketing.company.com). <Description> The descriptive name of the organization or department. <City> Specifies the city associated with this domain. <State/Province> Select the state or province associated with this domain. <Country> Select the country associated with this domain. <IPAddress/Pattern/Subnet> Enter the IP address, IP range, domain name or Subnet, as it is recorded in your web server log file. Note: You can also specify a subnet mask using CIDR format. For example, /26 where /26 indicates the number of bits used to identify the network. 241

244 WebTrends Enterprise Reporting Server Sample wtintra.txt acme.edu,acme training Center,Los Angeles,CA,US,acme.edu Bill.acme.org,Bill Johnson (Technical sales),orlando,fl,us,*.westworld.com canada.acme.ca,acme International (Canada),Toronto,Ontario,CA,*.acme.ca Modifying Search Engines Use the keywords.ini to modify the search engines included in reports. SearchEngines The [SearchEngines] section lists the search engines defined. Note: The search engine list is read from the top to bottom. Keep the order in mind when creating sections for similar domains. Table SearchEngines settings SearchEngine setting Engine[n] Description Specifies the search engine defined. Engine definitions are incremented by 1, beginning with Engine1. 242

245 Engine settings Chapter 11: Running from the Command Line The Engine[n] sections define the string for the search engine and the indicator used to signal search keywords. Table Engine settings Engine settings id[n] KeywordIndicator[n] Description Specifies the string used to identify the search engine in the log file. Any matches to the key field are report as a hit for this engine. For example, by default, any Yahoo search engine (yahoo.fr, yahoo.de) is reported simply as Yahoo. If you wanted to report on yahoo.fr and yahoo.de separately, you create an entry for each. For example, engine[n]=yahoo france, and for the key enter id1=yahoo.fr. Specifies the strings that immediately precede the search phrases. Include as much of the string needed to make it unique. 243

246 WebTrends Enterprise Reporting Server 244

247 Glossary A A Term Abandonment Rate Ad Ad Campaigns Ad Clicks Ad Views Attempted Buyers Definition The percentage of shoppers who do not complete the sale of items placed in the shopping cart. This includes both cart abdandoners and checkout abandoners. A graphic or banner on a Web page that, when clicked on, takes the visitor to another site. An effort to attract visitors to your site. It is usually, but not always, associated with a banner placed on another site which visitors click on to come to your site. It is characterized by a starting and ending date and a cost for the duration of the campaign. A click on an advertisement which takes a visitor to another Web site. When ads are seen by visitors. Once visitors have viewed an ad, they can click on them (see Ad Click). There may be more than one ad on an ad view. Visitors who reached the checkout page, but did not complete the order. 245

248 WebTrends Enterprise Reporting Server Term Authenticated Visitor Authentication Bandwidth Browser Buyers Definition A unique visitor tracked by user name and password rather than by IP address. You may find more authenticated visitors than visitors because several persons may be using the same IP address. Since many ISPs dynamically assign IP addresses, and since multiple visitors may come from a single IP address, authentication is a much more accurate way to identify visitors. Technique that limits access to Internet or intranet resources to those visitors who identify themselves by entering a user name and password. Measure (in kilobytes of data transferred) of the traffic on a site. A program used to locate and view Web pages. These include Netscape, Mosaic, Microsoft Internet Explorer, and others. Visitors who have purchased at least one item on your Web site. Cart Abandoners Checkout Abadoners Click Through Rate Client Shoppers who began the checkout process, but did not reach the final check-out page. Percentage of visitors who click on a viewed ad. This is a good indication of an ad s effectiveness. The browser used by a visitor to a Web site. 246

249 Term Client Errors Company Database Content Group Conversion Rate Cookies Cost Per Nonqualified Visit Definition An error occurring due to an invalid request by the visitor s browser. Client errors are in the 400-range. See the "Return Code" glossary entry for more information. The database installed and used by WebTrends to look up the company name, city, state, and country corresponding to a specific domain name. A defined group of Web pages with specific things in common, such as the same types of products, services, or information. Percentage of visitors who purchase at least one item. Files containing information about Web site visitors. This information can include the visitor s user name, preferences, etc. The information is provided by visitors during their first visit to a Web site. The server records this information in a text file and stores it on the visitor s hard drive. At the beginning of later visits, the server looks for a cookie and configures itself based on the information provided. Amount spent on a campaign divided by the number of nonqualified visitors brought to your site by the campaign. 247

250 WebTrends Enterprise Reporting Server Term Cost Per Product Qualification Definition Amount of money spent on a marketing campaign divided by the number of product qualifications the campaign was responsible for. Cost Per Qualified Visit Cost Per Visit Cost This Period Destination Page Documents Domain Name Amount spent on a marketing campaign divided by the number of qualified visitors brought to your site by the campaign. Amount spent on a marketing campaign divided by the number of visitors brought to your site by the campaign. Cost of a media campaign during this report period. A page that many visitors look at when they come to your site. The list of pages in the Paths to Destination column are the pages that visitors viewed on their way to the destination page. Pages that were defined as "documents" by the system administrator. Typically, a page will be defined as a document if the content is static, such as a complete HTML page. However, the administrator has the option of defining dynamic pages and forms as documents if he or she chooses. The text name corresponding to the numeric IP address of a computer on the Internet. For example, is a domain name. 248

251 Term Domain Name Lookup Dynamic Pages Engagement Rate Entry Page Definition The process of converting a numeric IP address into a text name (for example, is converted to Pages, such as those generated by search engines, that are created with variables and do not exist anywhere in a static form. They are generated from a database based on values that visitors select. WebTrends counts any line with a Post command or a Get command with a "?" as a dynamic page. Percentage of visitors who become shoppers. The first page a visitor sees when entering your Web site. To qualify as an entry page the visit must start with a valid document type. If a session starts at a document with a different type (such as a graphic or sound file), the file does not count as an entry page, and the session is not included in the total. Such sessions are often the result of other sites referencing a specific downloadable file or graphic on your site. In these cases, a session may have a single hit to a non-document type file, and will not be counted in the percentage calculations. 249

252 WebTrends Enterprise Reporting Server Term Exit Page FTP File Type Filters Forms GIF Definition The last page a visitor views before leaving your Web site. To qualify as an exit page the visit must end with a valid document type. If a session ends on a document with a different type (such as a graphic or sound file), the file does not count as an exit page, and the session is not included in the total. Such sessions are often the result of other sites referencing a specific downloadable file or graphic on your site. In these cases, a session may have a single hit to a non-document type file, and will not be counted in the percentage calculations. File Transfer Protocol. It is a standard method of sending files from one computer to another over the Internet. Identifies types of files by their three-character extension. For example, a file named graphic.gif is identified as type gif. A means of narrowing the scope of a report by specifying ranges or types of data to include or exclude. Scripted pages which pass variables back to the server. These pages are used to gather information from visitors. Graphics Interchange Format. It is a graphics file format commonly used in HTML documents. 250

253 Term HTML HTTP Hit Home Page Home Page URL IP Address Definition Hyper Text Markup Language. It is the programming language for static Web pages. It usually specifies hypertext links between related objects and documents. HyperText Transfer Protocol. It is a standard method of transferring data between a Web server and a Web browser. A single action on the Web server as it appears in the log file. A visitor downloading a single file is logged as a single hit, while a visitor requesting a Web page including two images registers as three hits on the server; one hit is the request for the.html page, and two additional hits are requests for the downloaded image files. While the volume of hits is an indicator of Web server traffic, it is not an accurate reflection of how many pages are being looked at. The main or introductory page of a Web site. The home page provides visitors with an overview and links to the rest of the site. It often contains or links to a Table of Contents. The URL for the home page of the site analyzed in the report. Internet Protocol Address. It is a series of four one- to three-digit numbers separated by periods. It is used to identify a computer connected to the Internet. For example, is an IP address. 251

254 WebTrends Enterprise Reporting Server Term JPEG Log File Marketing Campaign New Users No Refferer Definition Joint Photographic Expert Group. It is a compressed graphics format common on the Internet. A file created by a Web or proxy server which contains information about the activity of the server. An effort to attract visitors to a site. It is usually, but not always, associated with a banner ad placed on another Web site which visitors can click on. It is characterized by a starting and ending date and a cost for the duration of the campaign. Visitors who didn t have a cookie on their first hit, but had one on later hits. Indicates visits to your Web site that did not originate from any other site. For example, any visitor who types the URL of your site directly into their browser window fits into this category. Non-qualified Revenue Forecast This number is generated by counting the number of nonqualified visits and multiplying by the value assigned to nonqualified visits. The value of nonqualified visits is assigned by the system administrator. 252

255 Term Non-qualified Visits Page Page Views Path Through Site Paths from Start Definition Visits by customers who did not meet the minimum qualifications for potential revenue generators based on their traffic pattern. These visits have less potential value than qualified visits, but should not be discounted entirely. The visitors may become more valuable qualified visitors in the future. Any document, dynamic page, or form. Documents are defined by the system administrator, but generally include all static content, such as complete html pages. Dynamic pages, such as those generated by search engines, are created with variables and do not exist anywhere in a static form. Forms are scripted pages which get information from a visitor that gets passed back to the server. Hits to documents, dynamic pages, and forms. Hits to images, audio files, video files, forms, and ads are not counted. The path a visitor takes from the entry page to the exit page. The default definition for a page in this context is defined as a document ending with the extension.htm,.html, or.asp. This definition can be changed by the system administrator. With the exception of the starting page, the path a visitor takes to a destination or exit page. 253

256 WebTrends Enterprise Reporting Server Term Paths to Destination Platform Product Category Product Qualification Projected Nonqualified Visits Definition A list of pages in the order they were viewed to arrive at the specified destination page. Refers to the operating system, such as Linux or Windows 98. The product category is defined by the system administrator in Product Definitions. A visitor who qualifies as a revenue generator for a specific product results in one product qualification. A visitor can trigger product qualifications for more than one product, depending on how many products they purchase or are sufficiently interested in. Number of non-qualified visitors expected to be drawn to your site from a marketing campaign. The number of actual non-qualified visitors so far are included. The final number is a projection based on how many days the campaign has run, how many non-qualified visitors were attracted during that time, and how many days are left in the campaign. The projected number will be accurate if the campaign s future performance is the same as its past performance. 254

257 Term Projected Product Qualifications Definition Number of product qualifications expected on your site from a marketing campaign or product. The number of product qualifications so far are included. The final number is a projection based on how many days the campaign has run, how many product qualifications were attracted during that time, and how many days are left in the campaign. The projected number will be accurate if the campaign s future performance is the same as its past performance. Projected Qualified Visits Number of qualified visitors expected to be drawn to your site from a marketing campaign. The number of actual qualified visitors so far are included. The final number is a projection based on how many days the campaign has run, how many qualified visitors were attracted during that time, and how many days are left in the campaign. The projected number will be accurate if the campaign s future performance is the same as its past performance. 255

258 WebTrends Enterprise Reporting Server Term Projected Visits Definition Number of visitors expected to be drawn to your site from a marketing campaign. The number of actual visitors so far are included. The final number is a projection based on how many days the campaign has run, how many visitors were attracted during that time, and how many days are left in the campaign. The projected number will be accurate if the campaign s future performance is the same as its past performance. Protocol Qualification Level Qualified Revenue Forecast An established method of exchanging data over the Internet. Level of qualification of visitors to your Web site; fully qualified, moderately qualified, or minimally qualified. These levels are defined by the system administrator in Product Definitions. This number is generated by counting the number of qualified visits and multiplying by the value assigned to each visit. Each qualification level (full, moderate, and minimal) can have separate values assigned to them. The "Products Summary" page of this report lists the value assigned to each qualification level for each product. The values are assigned by the system administrator. 256

259 Term Qualified Visits Referrer Definition Visits by customers who are considered qualified as revenue generators. To qualify, a visitor must access specific pages on your Web site that are specified by the system administrator. URL of a Web page that refers visitors to your site. Return Code Partial list of "Success" codes: 200 = Success: OK 201 = Success: Created 202 = Success: Accepted 203 = Success: Partial Information 204 = Success: No Response 205 = Success: Cached 206 = Success: Partial Content 300 = Success: Redirected 301 = Success: Moved 302 = Success: Found 303 = Success: New Method 304 = Success: Not Modified 305 = Success : Use Proxy Partial list of "Failed" codes: 257

260 WebTrends Enterprise Reporting Server Term Definition 400 = Failed: Bad Request 401 = Failed: Unauthorized Access 402 = Failed: Payment Required 403 = Failed: Forbidden Access 404 = Failed: Page or File Not Found 405 = Failed: Method Not Allowed 406 = Failed: Not Acceptable 407 = Failed: Proxy Authentication Required 408 = Failed: Request Timeout 409 = Failed: Conflict 410 = Failed: Gone 411 = Failed: Length Required 412 = Failed: Precondition Failed 413 = Failed: Request Entity Too Large 414 = Failed: Request-URI Too Large 415 = Failed: Unsupported Media Type 500 = Failed: Internal Error 501 = Failed: Not Implemented 502 = Failed: Temporarily Overloaded 503 = Failed: Service Unavailable 504 = Failed: Gateway Timeout 258

261 Term Definition 505 = Failed: HTTP Version Not Supported Returning Visitors Revenue Forecast Server Server Error Shoppers Visitors who already had a cookie from your site before they visited. This number is generated by counting the number of visits and multiplying by the value assigned to each type of visit. The "Products Summary" page of this report lists the value assigned to each qualification level for each product. The values are assigned by the system administrator. A computer that hosts information available to anyone accessing the Internet or an internal intranet. An error occurring on the server. Web server errors have codes in the 500 range. Visitors who placed at least one item in a shopping cart. If they didn t purchase any items, they still count as shoppers. 259

262 WebTrends Enterprise Reporting Server Term Single Access Page Spider Suffix (Domain Name) Partial list of domain name suffixes: Time Interval Definition A page on your Web site that visitors open, then exit from, without viewing any other page. To qualify the visit must be to a page with a valid document type. If the visit is to a document with a different type (such as a graphic or sound file), the file does not count as a single access page, and the visit is not included in the total. Such visits are often the result of other sites referencing a specific downloadable file or graphic on your site. In these cases, a visit may have a single hit to a non-document type file, and will not be counted in the percentage calculations. An automated program which searches the internet. The three digit suffix of a domain name can be used to identify the type of organization the Web site belongs to..com = Commercial.edu = Educational.int = International.gov = Government.mil = Military.net = Network.org = Organization A one-year report displays monthly time increments. A onemonth report displays daily time increments. And a daily report displays hourly time increments. 260

263 Term URL Unique Visitors User Agent Users Without Cookies Visit Definition Uniform Resource Locator. It is a means of identifying an exact location on the Internet. For example, default.htm is the URL which defines the location of the page Default.htm in the /html/info/ directory on the WebTrends Corporation Web site. As the previous example shows, a URL is comprised of four parts: Protocol Type (HTTP), Machine Name (webtrends.com), Directory Path (/html/info/), and File Name (default.htm). Individuals who visited your site during the report period. If someone visits more than once, they are counted only the first time they visit. Portion of a log file that identies the browser and platform used by a visitor. Visitors who come to your site with cookies disabled. There is no way to determine if these visitors are new or returning. All the activity, from beginning to end, of one visitor to a Web site. If a visitor is idle longer than the idle-time limit, WebTrends assumes the visit was voluntarily terminated. If the visitor continues to browse your site after they reach the idle-time limit, a new visit is counted. The default idletime limit is thirty minutes. This time limit can be changed by the system administrator. 261

264 WebTrends Enterprise Reporting Server Term Visit Duration (Minutes) Visitor-Minutes Visits With Clicks Definition The number of minutes your Web site was viewed. Total number of minutes your site was viewed by all visitors put together during the specified time frame. Visits to your site that resulted in an ad being clicked on. 262

265 Optimizing and Troubleshooting B B Investigating Errors The Reporting Server maintains several logs that may record information on program activity as a whole, the web server, and profile processing. If you have a problem, these files might assist you. Using the wtrs.err file The wtrs.err file contains debug information related to the analysis engine. It contains information about connections to the server, the reports that have been generated, and general error messages. For example, if the server fails to start, look through this log. Using the wt.remote.err file The wt.remote.err file contains debug information related to Report Server s web server. It contains a record of actions that the server portion of the program has performed. Look in this log if there are problems with the server. Using the wtrs.audit file As an administrator, you should check the wtrs.audit file daily. It records the profiles that are active, connections made to the web server, and reports that are created. In addition, if dates are missing for a log file that is analyzed, the missing date is recorded here. Note: The wtrs.audit file name can be changed. See Audit on page 183 for details. 263

266 WebTrends Enterprise Reporting Server Using the profile status log The profile status log focuses on the details of profile processing. This graphic shows several lines from one log. Jul :15:02: =-=-=-= Initializing profile =-=-=-= Jul :15:02: Reverse DNS disabled. Jul :15:03: 1 member(s) found in log list. Jul :15:03: 1 member(s), which have already been analyzed, have been removed from the log list. Jul :15:03: Logfile data is up to date -- no analysis required. Jul :15:03: Scheduling analysis of cluster s logfiles every 0 hour, 15 minutes. Jul :15:03: cluster s next analysis is Fri Jul 16 08:30: Jul :15:03: 1 member(s) found in log list. Jul :15:03: 1 member(s), which have already been analyzed, have been removed from the log list. Jul :15:03: Logfile data is up to date -- no analysis required. Jul :15:03: Creating summary report: \index.html Figure A-1. Log example Using these details, you can determine where in the process a problem occurred. Profile status logs are given the same name as the profile they are logging. They are located in the <InstallDir>\wtm_wtx\datfiles\statuslogs<InstallDir>/ wtm_wtx/datfiles/statuslogs directory. Tip: The debuglevel option determines the level of detail provided. Set it to 10 to get the most data. 264

267 Appendix B: Optimizing and Troubleshooting Jan :21:38: =-=-=-= Creating profile =-=-=-= Jan :21:38: 1 member(s) found in logfile list. Jan :21:38: Reverse DNS disabled. Jan :21:38: 1 member(s) remain to be analyzed: Jan :21:38: Using log file.\wtm_wtx\datfiles\samples\sample.log: Jan :21:40: Scheduling analysis of sample s logfiles every 0 hour, 15 minutes. Fixing Error 500 Server Error Figure A-2. Sample profile status file Error 500 Server Error states "An error occurred processing your request." This can happen if the Reporting Server daemon is not started by the same user who installed the program. For example, if user johns installed the Reporting Server, and he logs in as "superuser" rather than "johns" to start the daemon, he will get the 500 Server Error. To solve this problem, either change the uid setting in the wtm_wtx.ini file to uid=0, or give other write permissions to the install directory only. For example, if the install directory is wtrs, do chmod o+w wtrs. Note: It s best to start the server as the user who installed the Reporting Server. Setting uid to 0, or having it run as root exposes a security risk. Web server fails to initialize If the web server fails to initialize, the wt_remote.err may provide insight. Failure to initialize may be caused by trying to use a privileged port or one that is already used. Profiles fail to initialize There are several reasons why a profile might not initialize. First, look at the status log for the profile. It might indicate a problem in processing. Then consider the following possibilities: Are the log files in a supported format? Make the logs are not corrupt and that the log data is valid. 265

268 WebTrends Enterprise Reporting Server Are you running a trial version of the Reporting Server? If you are and the trial period expired, check the dates of the log files that you are trying to run. The dates must be within the period of the trial. Can the Reporting Server find and write to the directories specified for databases? Can it access the statuslogs directory? The Reporting Server must be able to access the directories specified for the reports database and the profile database. (NT only) Are you reporting on log files through a mapped drive? The service for the Reporting Server must be configured to log on to the machine that has the profiles. Configuring NT for the Reporting Server If you re accessing log files through a mapped drive, configure the machine that has the profiles by completing these steps: Step 1. Make sure the machine has the same user account information as the user who is logged into the Reporting Server. 1. From the Start menu, select Settings, Control Panel. 2. Select Services. Select WebTrends Reporting Server from the list, and click Startup In the Service dialog box, select the This Account from the Log On As group. Specify the account to use and enter the password for the account. Step 2. Set up user rights for the account. 1. From the Start menu, select Program Settings>Administrative Tools>User Manager. 2. Select the account the Reporting Server uses to access this machine. 3. Select Policies>User Rights. In the User Rights Policy dialog box, check the Advanced User Rights box. 4. Select Act as part of the operating system, and click Add. Select the user account from the list, and click Add. Click OK. 5. Now repeat the previous step for Log on as a service right. Click OK to close the User Rights Policy dialog box. 6. In the User Manager window, select the Administrators from the Group list, and select Policies>User Rights. 266

269 Appendix B: Optimizing and Troubleshooting 7. Click Add, and the Add Users and Groups dialog box opens. 8. Select the user name from the list, and click Add. You may need to click Show Users to see your name in the list. Click OK to close the dialog box. Conflicting file permissions If you have trouble running or saving a profile, or it appears to be missing, check your owner or group permissions. Typically, this occurs when a you install the product as one user and try to run it as another, or when you copy another user s profile. You might avoid this and other problems by running the Reporting Server as the user who installed it. File handle allocation If there aren t enough file handles allocated to execute system processes, the program may stop running. The number of file handles is stored in the wtm_wtx.ini in the handles setting. Database location Reports that use data stored locally are generated more quickly than those that use data stored on another machine. Factors impacting space and memory Several factors affect total memory requirements: Number of concurrent analysis the greater the number of analyses occurring at the same time, the greater the demands on memory. To conserve memory, decrease the number of concurrent analyses. See Configuring system performance settings on page 144 for details. Report queue size the data needed to create pending reports must be saved. Once the reports are created, the data is released. Report maintained to save disk space, only maintain reports for intervals that you need (daily, weekly, monthly). Set a limit on the number of reports that are maintained for each interval. See Defining the reports to maintain on page 139 for more information. 267

270 WebTrends Enterprise Reporting Server Reports tables used to minimize the amount of memory used to created reports, only generate the tables and graphs that you need. Define which report sections are included through the Report Template dialog box. See Working with Report Templates on page 116 for more information. DNS lookups the size of the DNS queue and the number of threads impact the memory used for DNS lookups. Refer to the Releasenotes.txt file, included on the product CD, for more information. Logs retrieved using FTP You ll need disk space to download the logs so they can be analyzed. If the log has already been downloaded once, you ll only need space for new activity. Symbolic links (UNIX) You can save space on your hard drive by enabling the usesymlinks option. By default, each profile creates it s own set of files in the CordaJava, Images, MSWord directories. However, if you enable symbolic links, the Reporting Server points to these shared directories rather than copying them for each profile, saving space on your system. To enable this feature: 1. Open <install dir>/wtm_wtx/wtm_wtx.ini. 2. Set the usesymlinks option to true as shown here: usesymlinks=true Connecting through the Remote Interface To run the Reporting Server through the GUI, connect using one of the following methods: Enter in the hostname followed by the port that the Reporting Server is running on. For example, server:1024 Enter the host IP address followed by the port that the Reporting Server is running on. For example, :

271 Appendix B: Optimizing and Troubleshooting Enter "localhost" followed by the port number if the Reporting Server is installed locally. For example, localhost:1024 The browser treats each method of connecting as a separate realm. To log in as two different users in the same browser, use a different method to access the Reporting Server. If you are behind a firewall, make sure that the firewall allows access to the port where the Reporting Server is running. Problems creating a Microsoft Word report from Internet Explorer The first time that you create a Microsoft Word report, the Reporting Server downloads and installs the WebTrends Microsoft Word document utility. If the document utility fails to download, the security settings in Internet Explorer could be blocking the Active X control from running. To change IE security settings: 1. Select View>Internet Options. 2. Select the Security tab. Dates for reports are unexpected If the log files don't include the GMT offset time (for example, +0000), the Reporting Server adjusts for the local time zone. For example, if you are reporting on data for August 5, 1999, but the reports show a different date, you might check the log file for the GMT offset. Although log files vary, the GMT field looks something like or (where zeros are replaced with the offset for your time zone.) Analyze Now, Re-analyze, and recovering archived data The three functions Analyze Now, Re-analyze, and working with archives can help you process profile data in important ways. 269

272 WebTrends Enterprise Reporting Server Analyze Now Use Analyze Now if you need to generate reports on profiles which haven t been recently analyzed. Analyze Now overrides the scheduled analysis of a profile, and inserts profile into report queue. Analyze Now will: Append data to the profile's database. (If space limitations demand, old data will be deleted to make space for new analysis data.) Insert the profile into the report queue. Please note that the profile may not be analyzed immediately, if there is already an analysis underway. If so, the profile will remain queued until analysis can begin. To use Analyze Now: 1. From the Main Console, select the profile you want to analyze. 2. Select Profile>Analyze Now. The Analyze Now dialog box appears (Figure B-1 on page 270). Figure B-1. Analyze Now dialog box 270

273 Appendix B: Optimizing and Troubleshooting 3. Click OK to insert the profile into the analysis and report queue. Be aware that by using Analyze Now thereby changing when data was analyzed and editing a profile, such shifts in how reports are run may create changes in on-demand reports which over time show shifts in data patterns. You may find, upon examination of your reports, and when your profile was changed or analyzed, that you may need to either reanalyze a profile, or report on an archived profile database. Instructions on these procedures follow. Reanalyze Profile Use Reanalzye Profile if you need to create completely new reports which reflect changes to profile settings. Reanalyze Profile will: Delete all databases and reports associated with the old version of the profile. Does not chance profile settings (.wlp,.wdw, etc.) or profile statuslog. Create new databases from this point forward based on new profile settings. Inserts profile into report queue. Please note that the profile may not be analyzed immediately, if there is already an analysis underway. If so, the profile will remain queued until analysis can begin. To use Re-analyze Profile, complete these steps: 1. From the Main Console, select the profile you want to reanalyze. 2. Select Profile>Re-analyze. The Re-analyze Profile dialog box appears (Figure B-1 on page 270). 271

274 WebTrends Enterprise Reporting Server Figure B-2. Re-analyze Profile dialog box 3. Click OK to reanalyze the profile. Activating archiving You can archive the profiles that you chose at regular intervals. An archive contains a backup of the databases for the profile. Archiving allows you to restore a profile to a point in the past. Archives are useful if some log files were not available during analysis, if you discover your log files have been corrupted, or if you made changes to the profile that you want to restore. Archive settings are maintained in the Options window. See Restoring profiles to an earlier state on page 273 for details on using archives. To enable archiving: 1. Select the profile to work with, and click Edit. 2. Select the General tab. 272

275 Appendix B: Optimizing and Troubleshooting Click in the Enable Archiving box. The archive is made at regular intervals which have been defined in the Options window. See Archiving profile data on page 124 for details. Restoring profiles to an earlier state Profiles that have been archived can be restored to one of the archived versions. For example, if the wtrs.audit file says that there is a date without log file data, you could restore the profile to an earlier version using an archive, place the missing logs in the proper location, and restart the analysis so that reports show activity for the newly added logs files. Monitor the wtrs.audit file for messages like this one to determine when an archive should be used: Sep :33:48: No log data for profile daily on Sunday, February 14, 1999 Figure B-3. Profile Archives dialog box. To restore an archive: 1. Select the profile to restore. 2. Select Profile>Archives. The Profile Archives dialog box opens (Figure B-3). 3. Select the archive that you want to use from the drop-down Available Archives list, and click Restore. 273

276 WebTrends Enterprise Reporting Server Important: When you restore a profile using an archive, all databases and reports created after the archive date are deleted. Special considerations for configuring the Reporting Server The configuration you design determines the speed and resources available for processing and publishing reports. This section discusses three approaches. Default configuration By default, the Reporting Server is configured to provide all the administration and publishing of reports on one machine. When the default configuration is used, the databases for reports and analysis are stored locally. This configuration results in the best reporting speed. Configuration implementing an alternate web server The Reporting Server may also be configured to delegate report publishing to another web server. Using an alternate web server rather than the built-in web server may relieve the burden of providing both the remote interface as well as the task of analyzing, producing, and posting reports. Even if another web server is configured to publish reports, the Reporting Server still provides the GUI. Figure A-3 on page 275 shows this configuration. 274

277 Appendix B: Optimizing and Troubleshooting Figure A-3. Reporting Server configured to delegate report publishing to another web server Using multiple web servers and storing results on another machine The Reporting Server can also be configured to use multiple web servers for reporting and to maintain databases on other machines. To implement this configuration, you would change both the default web server settings as well as the database directory setting. This configuration is shown in Figure A-4 on page

278 WebTrends Enterprise Reporting Server Figure A-4. Reporting Server configured to delegate to several web servers 276

279 Regular Expression Syntax C C This appendix contains descriptions and examples of the regular expression syntax that can be used with ROI definitions. It should handle any patternmatching needs that you may have. Regular Expression Components Basic elements Basic element a single character \ followed by a single character Example Matches anything containing the single character to be matched. For example, a matches cause. You could also combine several characters together, such as couch. Lets special characters be used as a single character. The character combination "." has special meaning. The only way you can use it to mean period is to precede it by a backslash ( \). "." is especially useful when describing paths. For example \.html$ matches anything ending in.html. Other characters that need to be preceded by a backslash if they are to be used without special meaning are these: \,., $, *,?, +, [, ], (, ), $ Matches anything that ends with the value. For example, cause$ matches cause and because. ^ Matches anything that begins with the value. For example, ^couch matches couches and couch.. Matches any single character. For example, cou*h matches couth, couch, cough. range [ ] Matches a sequence of characters that are enclosed in brackets "[ ]". For example, [0-9] matches on any decimal digit. If the sequence is preceded by a caret (^), it matches any single character not from the sequence. For example, [^a-z] matches anything that isn t a letter of the alphabet. 277

280 WebTrends Enterprise Reporting Server Basic element Example The pipe ( ) indicates an OR operator. For example: couch chair finds couch or chair. a regular expression in parenthesis () The expression (couch[0-9]) (bed[0-9]) matches the following: couch36a, full_bed33b, but not couch. Qualifying characters The next level of a regular expression is any element which is qualified by one of the following characters: *, +, or?. Qualifying character Example * Matches 0 or more occurrences of the element it follows. For example, couch_[a-z0-9]* matches couch followed by one or more alphanumeric values: couch_0, couch_aaa, couch_a33, and couch_. Caution! Don t confuse the * with the command-line wildcard character. If you were trying to match all html files in a path: Wrong: /mydir/*.html Correct: /mydir/.*\.html$ In the correct instance, you are specifying anything containing the following: /mydir/ followed by 0 or more of any character, followed by a literal period (.), and ending with html. This locates /mydir/index.html, for example. + Matches 1 or more occurrences of the element it follows. For example, couch_[a-z0-9]+ matches couch_ followed by one or more alphanumeric values: couch_0, couch_aaa, couch_a33, but not couch_.? Matches 0 or 1 occurrences of the element it follows. For example, couch_[a-z0-9]? matches couch followed by 0 or 1 alphanumeric values: couch_0, couch_, couch_a, but not couch_bb. Note: Since all ROI parameter names and values are case-insensitive, you don t need to match case in your regular expressions. 278

281 Building Regular Expressions Appendix C: Regular Expression Syntax Most regular expressions that you use with the Reporting Server will be very simple, often consisting of a few basic elements. Example 1 If you wanted to match all of the values that begin with couch, your regular expression is: ^couch Example 2 If you wanted to match all of the values that end with couch, your regular expression is: couch$ Note: These examples emphasizes how regular expressions work. If the match must begin or end with the value, you must specifically indicate that by using ^ or $. Example 3 In some cases, you may have an either/or situation. In this case you would use the pipe symbol ( ) to combine two regular expressions. For example, couch chair matches a value containing either couch or ( ) chair: blue_chair, chair_55, big_couch_55 Example 4 In this example, you are trying to match on three months of your product news. You might use the following regular expression to define a qualifying page URL that contains any product news HTML pages from January, February, or March: /product/news/(jan feb mar)/.+\.htm Literally, this means to match any item (most likely a URL), containing the string /product/news/, followed by either jan, feb, or mar, followed by / and one or more of any character (.+), followed by.htm. This would return the following URLs: /product/news/jan/chair.htm /product/news/feb/mirror.htm /product/news/mar/couch.htm 279

282 WebTrends Enterprise Reporting Server /product/news/jan/table.htm /product/news/jan/table.html but not these URLs: /product/news/jan/chair.asp /product/news/jan/chair.gif /product/news/apr/chair.htm Example 5 In this example, we want to match all URLs that indicate that an individual product in the furniture category has been registered. We would use the following regular expression to define our qualifying page URL: ^/product/furniture/.+/register.htm Literally, this means to match all URLs that begin with /product/furniture/, followed by one or more occurrences of any character, followed by /register.htm. The following URLs would be matched: /product/furniture/couch/register.htm /product/furniture/chair/register.htm /product/furniture/couch/register.htm /product/furniture/bedroom/armoire/register.htm but not this URL: /product/furniture/index.htm Matching order rules There are several rules involved with how regular expression matching occurs: The first match found takes priority over other matches found if there are two matching input strings. In a list of concatenated expressions, the left-most match takes priority. The matches found using *, +, and? are considered longest first. Nested constructs are evaluated from the outside in. 280

283 Appendix C: Regular Expression Syntax Comparing Regular Expressions and Wildcards This table shows how you might use a wildcard or regular expression to accomplish the same thing. Wildcard (*) Regular expression Meaning *chair* chair Contains chair *chair chair$ Ends with chair chair* ^chair Begins with chair chair (no wildcard) ^chair$ Is exactly chair 281

284 WebTrends Enterprise Reporting Server 282

285 System and Error Messages D D The Profile Status Log The Reporting Server generates a status log for each profile which provides processing details. To view a profile status log: 1. Select the profile in the Main Console. 2. Select View > Profile Status. The detail provided is determined by the debuglevel setting, which can be set from 1 to 10 (10 provides the most information). At installation, debuglevel is set to 5. The default profile value is defined in the wtm_wtx.ini file. It can be modified in the.wlp file for an individual profile if necessary. Common Messages The table below shows some common messages. Brackets {} indicate where variable text appears. Message number Message text Description 1 Insufficient disk space ({directory name}). Profile aborted, requires additional free disk space. ({disk space} Mb avail, {disk space} Mb required) The disk space required for the directory that contains the profile s databases or reports has fallen below the minimum needed to complete the analysis. Make space available on the specified drive and the profile will run at the next scheduled interval. 283

286 WebTrends Enterprise Reporting Server Message number Message text Description 2 Warning! Low disk space ({directory name}). Profile will be aborted when disk space is less than {disk space} Mb. ({disk space} Mb avail) 3 Reverse DNS {enabled disabled}. 4 Reverse DNS Type {report time parse time}. 5 {profile name} has been modified; updating profile data... 6 The profile is being prepared for reanalysis The disk space needed to process the profile has fallen below the minimum required. This message appears when disk space falls below the warning threshold. Make space available on the specified drive and the profile will run at the next scheduled interval. This is a normal status message reflecting the state of the DNS setting for the profile. This is a normal status message reflecting the DNS setting for the profile. This is a normal message that indicates that the profile has been edited and that the server has been notified to update its profile settings. This message indicates that a user has requested that the profile be reanalyzed. When a profile is reanalyzed, existing profile databases and reports are deleted, the log file data is reanalyzed, and new databases and reports are generated. 284

287 Appendix D: System and Error Messages Message number Message text Description 7 Profile file or wtm_wtx.ini file contains invalid value for datadir field 8 Profile file or wtm_wtx.ini file contains invalid value for profile field. 9 Could not access profile s configuration file to reencrypt ftp password[{profile name}]: {system error message} Could not access profile s configuration file [{profile name}]: {system error message} The database directory key, datadir, contained in the.wlp file or in the wtm_wtx.ini file contains a macro that is invalid. Profile analysis cannot continue if this error message is found. To fix this problem, edit the datadir key in the.wlp file for this profile. If the profile uses the datadir value that was defined as the default in the wtm_wtx.ini file, make the same change in the wtm_wtx.ini file. The reportdir key or the wtreportdir key in the.wlp file or wtm_wtx.ini file contains an invalid macro. Profile analysis cannot continue until this problem is resolved. To fix this problem, edit the reportdir or wtreportdir key in the.wlp file for this profile. If the profile uses the value that was defined as the default in the wtm_wtx.ini file, make the same change in the wtm_wtx.ini file. The reportdir key or the wtreportdir key in the.wlp file or wtm_wtx.ini file contains an invalid macro. Profile analysis cannot continue until this problem is resolved. To fix this problem, edit the reportdir or wtreportdir key in the.wlp file for this profile. If the profile uses the value that was defined as the default in the wtm_wtx.ini file, make the same change in the wtm_wtx.ini file. 285

288 WebTrends Enterprise Reporting Server Message number Message text Description 10 Profile file or %s file contains invalid value for field. 11 A fatal error occurred creating the database directory {directory name}: {system error} 12 A fatal error occurred creating the report directory {directory name}: {system error} The tempdir key in the.wlp file or wtm_wtx.ini contains an invalid macro. The profile cannot be analyzed until the problem is resolved. To fix this problem, edit the tempdir key in the.wlp file for this profile. If the profile uses the tempdir value that was defined as the default in the wtm_wtx.ini file, make the same change in the wtm_wtx.ini file. A system error occurred creating the database directory for this profile. Review the message and try to resolve the problem. The profile is not analyzed when this error occurs. A system error occurred creating the specified report directory. Review the system error message and try to resolve the problem. The profile is not analyzed when this error occurs. 13 =-=-=-= Initializing profile =-=-=-= This is a normal message which occurs when a profile is called. 14 Profile Initialization successfully completed. This is a normal message which occurs during profile initialization. However, there still might be problems with the profile definition that are not detected during profile initialization, such as an incorrectly specified log file path. 286

289 Appendix D: System and Error Messages Message number Message text Description 15 The profile is currently disabled. This message occurs during profile initialization. It is a normal message for a profile that has been disabled by a user. No analysis is performed on disabled profiles by design. 16 Scheduling analysis of {profile name} s logfiles every {hour} hour, {minutes} minutes. 17 Estimated Number of Reports ({count}) Estimated Disk Space Required ({space}mb) 18 {count} files cleaned from FTP Cache. ({space} MB) 19 Unable to connect to ftp Server {server name} ({reply}) This is a normal message that states how often the analysis for this profile is scheduled. This is a normal message which provides a guideline for the amount of disk space this profile requires. This reflects the report space or the on-demand report database space; it does not reflect the main database requirements for a profile. This is a normal message which indicates that some files in the FTP cache were deleted during regular maintenance of the cache. This message indicates that an error occurred attempting to connect to FTP server to retrieve log files. Review the message sent by the server to determine why the connection was unsuccessful. 20 FTP Error ({server name}): {reply} This message indicates that an FTP error occurred while attempting to retrieve log files. The error message may provide enough information to resolve the problem. 287

290 WebTrends Enterprise Reporting Server Message number Message text Description 21 An error occurred opening the logfile, {log file}: {system error} You may need to configure the WTRS service with a user name and password. See releasenotes.txt for more information. 22 CloseOut failed to complete. Analysis will be aborted. 23 Error creating report: Template {filename} was not found. Profile has been disabled. This message indicates that the log file specified in the profile could not be opened. Since quite often this error occurs because the wtrs service is not properly configured, the message refers you to the releasenotes.txt file for information on setting up the service. In the case of the system error "Access is denied" you are not referred to the releasenotes.txt file. This message indicates that an error occurred attempting to write databases and the analysis could not be completed. Run the profile again. This message indicates that the template file used to create reports (for example, CompleteSummary.wct) could not be found. The analysis could not be completed and the profile is disabled so that no further analysis will be attempted until the problem is resolved. To resolve the problem, be sure the specified template is in the correct location. Make the necessary changes to the profile definition, and enable the profile so that analysis is performed at the next scheduled interval. 288

291 Appendix D: System and Error Messages Message number Message text Description 24 Error creating report: template {filename} was invalid. Profile has been disabled. This message indicates that the template file used to create reports (for example, CompleteSummary.wct) is corrupted. The analysis could not be completed and the profile is disabled so that no further analysis will be attempted until the problem is resolved. To resolve the problem, locate the specified file and compare the contents to a template file that works. Make the necessary changes to the file or change the profile definition to use a different template. Once the problem is fixed, enable the profile so that analysis is performed at the next scheduled interval. 25 Creating report: {report period} This is a normal message which indicates that a report is being created. 26 An error occurred creating the report {directory}: {system error message} ({system error number}) This message indicates that a system error occurred which prevented the directory for the report from being created. Review the error message and if possible correct the problem. Run the profile again. 289

292 WebTrends Enterprise Reporting Server Message number Message text Description 27 An error occurred loading the reporting library: {file name} 28 Creating summary report: index.html 29 An error occurred creating the report, {file name>: {system error}. 30 {profile name} s next analysis is {date/time}. This message indicates that the executable, DLL, or shared object could not be loaded because it most likely has been removed or destroyed. Reports cannot be created until the file is restored. Look for the file either on the Reporting Server system, or on the machine that contains backup files. If you are not able to find the specified find, install the program files in a separate location so that you can copy the file that you need. This is a normal message which indicates that the report calendar is being created. This message indicates that a system error occurred which prevented the directory for the report from being created. Review the error message and if possible correct the problem. Run the profile again. This is a normal message which shows the next scheduled analysis for the profile. This message is written as the profile is initializing for analysis. If the analysis is scheduled every hour, when the profile initializes for its 2:00 PM analysis, it will print this message indicating that the next analysis is at 3:00 PM. 290

293 Appendix D: System and Error Messages Message number Message text Description 31 Warning: An error occurred updating the profile s status: {system error message} 32 Unable to start log data analysis: {system error} 33 Processing log files for profile {profile name}. Processing records from {start time} to {end time} 34 {profile} parsing {completed aborted}: {count} records w/ {count} threads took {time}. 35 Various Add File errors: wtarchive::addfile: Couldn t create dir: {directory name}. wtarchive::addfile: Couldn t compress file: {file name}. wtarchive::adddata: Failed, archive will be backed out. wtarchive::prunereports: Unable to delete dir {directory name}. wtarchive::deletereports: Report Directory unknown. This message indicates that there was an error updating the status.ini file which records how much of the data specified has been analyzed. The next time that the profile is analyzed, the entire log file is analyzed. This message indicates that the function to open and examine the log file contents failed. Analysis cannot proceed. Review the system message to determine why the log files could not be opened. This is a normal message that is written at the beginning of an analysis. It indicates the date and time range that will analyzed for the profile. These are normal messages that appear at the end of the analysis. The first message is used if DNS is enabled; the second form is used if DNS is disabled. These are messages that appear if an archive could not be created. 291

294 WebTrends Enterprise Reporting Server Message number Message text Description wtarchive::addfile: Couldn't create dir: {directory name}. wtarchive::addfile: Couldn't compress file: {file name}. wtarchive::adddata: Failed, archive will be backed out. wtarchive::prunereports: Unable to delete dir {directory name}. wtarchive::deletereports: Report Directory unknown. The specified directory couldn't be created. Check the access rights for the directory. The specified file couldn't be compressed possibly because of disk failure or not enough disk space. The existing archive will be returned to its previous state. The specified directory could not be deleted during archive maintenance. Check the access rights for the directory. If the reportdir setting in both the.wlp file and the wtm_wtx.ini file is blank, this message appears. The reportdir setting specifies the directory where reports for the profile are saved. 292

295 Appendix D: System and Error Messages Message number Message text Description 36 Various Archive messages: wtarchive::restorereportingperi od: Couldn t create dir: {directory name}. wtarchive::restorereportingperi od: Couldn t uncompress file: {file name}. wtarchive::restoredata: Couldn t uncompress file: {file name}. wtarchive::restore: Unable to Restore Data. wtarchive::restore: Unable to Restore Data for period {period number}. wtarchive::restore: Unable to add Archive {file name}. wtarchive::restore: Archive {file name} does not exist. wtarchive::restore: Could not find tag. wtarchive::restore: unable to load archive.ini. wtarchive::restorereportingperi od: Couldn't create dir: {directory name}. wtarchive::restorereportingperi od: Couldn't uncompress file: {file name}. wtarchive::restoredata: Couldn't uncompress file: {file name}. wtarchive::restore: unable to load the archive.ini file The archive.ini is missing. If you maintain back-ups of your data, you may be able to replace the missing file. The directory couldn't be created. Check the access rights for the directory. The specified file could not be uncompressed. Check the access rights or disk space. Verify that the file is not corrupted. The specified file could not be uncompressed. Check the access rights or disk space. Verify that the file is not corrupted. 293

296 WebTrends Enterprise Reporting Server Message number Message text Description wtarchive::restore: Unable to Restore Data. Usually preceded by another message: wtarchive::restore: Unable to Restore Data for period {period number}. wtarchive::restore: Unable to add Archive {file name}. wtarchive::restore: Archive {file name} does not exist. wtarchive::restore: Could not find tag. All but the reporting period specified was restored. Possible report periods: 1 - daily 2 - weekly 3 - monthly 4 - quarterly 5 - yearly In an attempt to restore the archive, the program tries to return the files to the state they were in. Review the date of the archive and the file specified in the message. The contents of the archive.ini have been corrupted. 37 Old report purged: {report name} This is a normal message that appears if the profile is set to only keep a certain number of reports or on-demand databases. 38 Restoring archive for profile {profile name}. 39 Unable to create temporary FTP directory {directory name}. (errno:{system error number}) This is a normal message that appears when a user requests that an archive is restored. This message indicates that the temporary directory used to store files that are copied using FTP could not be created. Check the access rights of the directory. Review the value of the ftpdir key in [ftp] section of the wtm_wtx.ini file or the.wlp file. If the FTP directory specifies a network drive, make sure that it is accessible. 294

297 Appendix D: System and Error Messages Message number Message text Description 40 Unable to unlink file {file name} This message indicates that an error occurred attempting to delete a file that was acquired using FTP before an updated copy of the file could be copied. 41 FTP transfer of file {file name} failed, insufficient disk space ({space available}) 42 FTP transfer of file {file name} failed. (FTP error: {reply string}) 43 FTP transfer of file {file name} successful 44 No logfiles found for server cluster, "{server name}": "logfilepath{n}" = {file name}." 45 Logfile data is up to date -- no analysis required. 46 No logfiles found: "logfilepath{n}" = {file name}. This message indicates that the FTP transfer failed because of insufficient disk space. Make some disk space available. This message indicates that the FTP transfer failed. Review the {reply string} in the error message. This is a normal message stating that the FTP transfer of files was successful. This message indicates that no log files were found for the specified server and log file path. Make sure that the log files were specified correctly and that the log files are in the correct location. This is a normal message which indicates that the analysis is at the end of the log file(s). This message indicates that no log files were found for the specified log file path. Make sure that the log files were specified correctly and that the log files are in the correct location. 295

298 WebTrends Enterprise Reporting Server Message number Message text Description 47 {count} member(s) found in log list. 48 {count} member(s) with data outside the trial period were removed from the log list. The trial version limits analysis to data created before {date/time string}. 49 {count} member(s), which have already been analyzed, have been removed from the log list. 50 {count} member(s) remaining to be analyzed: This is a normal message that is written near the beginning of analysis. It provides the number of log files that were specified in the profile. If you are running a trial program, you cannot process log files containing records beyond the trial s expiration date. This is a normal message that appears near the beginning of analysis. It indicates that, of the number of log files specified by the profile, {count} have already been analyzed, and will therefore not be processed during the current analysis cycle. This is a normal message that indicates the number of log files that will be processed during this analysis cycle. 51 Using log file {file name}: This is a normal message which indicates that the log file is being analyzed. 52 Limits for all logfiles: StartingDateTime = {date/time string} EndingDateTime = {date/ time string} 53 The logfile, {file name}, was rejected: Already analyzed This is a normal message that displays the earliest time and latest time found in the records for the log files specified by the profile. This is a normal message which indicates that the log file has already been analyzed past the date and time of the last record in the log file. 296

299 Silent Installation E E Important Notes Note: An unattended, or "silent" install is for advanced users only. Do not attempt this procedure if you are unfamiliar with the WebTrends product or your local network. Disk space It is the user s responsibility to check for available disk space. You will receive a warning message at 200 MB disk space remaining. The silent installation will abort at 50 MB. Licensing issues Silent installations do not handle licensing for the Enterprise Reporting Server. To add a license for this product, use the command-line executable wtlicense.exe. Solaris/Linux: To add a license using wtlicense.exe: 1. Run a successful installation of the product. 2. After a successful installation, at the command line, type./wtlicense -add <serial number> NT: To add a license at the command prompt: 1. Go to the directory where WebTrends is installed. 2. Type wtlicense -add <serialnumber> 297

300 WebTrends Enterprise Reporting Server "Silent" install instructions for Solaris/Linux Installing as root To install To install as root, complete the following step: Format of the command line:./wtrs.install response_file < response_file The argument response_file tells the install script that it is running without user interaction. If the response_file argument is present, the behavior of wtrs.install is altered to expect different input and produce different output. The user redirects standard input to provide the input for wtrs.install from a response file. The format of the file differs slightly depending on whether or not the user is installing as root. Response files This section describes the format of the response file whether the user is installing as root or non-root. A sample of this file is found in wtm_wtx/datfiles/ sample/root_auto_response. /usr/local/webtrends 999 admin 9999 n If installing as root, add the following two lines: n n Line 1: the install path. It must be a full path, with all the same limitations on special characters that exist in an interactive install. Line 2: the UI port the port you point your browser to when bringing up the UI. 298

301 Appendix E: Silent Installation Line 3: the user name of the administrator. Line 4: the internal communications port the port which wtrs and wtinterface use for internal communication. Line 5: should ERS be started when the system boots? y or n. Line 6: should install.wtrs start ERS? y or n. Line 7: needed to continue the install. "Silent" install instructions for Windows NT Installing as root While some of the parameters described below are optional, some are required. Be attentive to the order as well as the case-sensitivity of the commands. Failure to follow the required order, case-sensitivity, or other cautions will result in a problematic installation. To run a silent installation for ES/Domino and Firewall, complete the following steps: 1. Run the setup program with the following syntax: setup.exe /S /DESTINATION=installation destination path Please note: The parameters must be given in the order presented. The parameter /DESTINATION does not include quotes. To run a silent installation for ERS, CTRS, and OLAP, complete the following steps: 1. Run the setup program with the following syntax: setup.exe /S /USERNAME=<USERNAME> /UIPORT=<UIPORT NUMBER> /ENGINEPORT=<ENGINE PORT NUMBER> /DESTINATION=INSTALLATION DESTINATION PATH Please note: The parameters must be given in the order presented. 299

302 WebTrends Enterprise Reporting Server /S in required for silent installations of all Webtrends products. The next 3 parameters are only valid for ERS-based products: /USERNAME=<USERNAME>: user name for logon on and the information file. This parameter is optional. /USERNAME defaults to whomever is logged on the machine at the time of install. /UIPORT=<UIPORT NUMBER>: User Interface port number. This parameter is optional. /ENGINEPORT=<ENGINE PORT NUMBER>: engine port number. This parameter is optional. The parameter /DESTINATION must conclude the argument. The value does not include quotes. 2. For ERS-based products only, restart the product using the following commands: wtrs -stop -start wtinterface -stop -start 300

303 Index A about ad views and clicks 97 profiles 106 reports 104 WebTrends Reporting Server 104 absolute FTP paths 204 activating cookies 127 Ad Click ID String 100 Ad View File Name 99 Ad Views and Clicks initialization files 240 ad views and clicks 98 about 97 adding 98 deleting 101 description 99 editing 101 tracking exit URLs 97 using 98 adclick setting 228 adding ad views and clicks 98 advertisement profile 101 content groups 168 filters 68, 76 Intranet domain 94 Intranet domains 94 path analysis definitions 166 report template styles 116 URL parameter analysis definition 169 URL search and replace definition 164 adsenabled setting 229 advertising tracking 98 adview setting 229 analyzing from a specified date 28 paths 166 archives global settings 183 archiving global setting 124 profile settings 54, 272 restoring profiles 55, 273 arpa_orgtype setting 188 Audit settings 183 authentication 149, 211 authentication methods 212 auto mode DNS lookup 49 B Browser filter 87 browser menu, displaying 205 browser setting 230 browserenabled setting

304 WebTrends Enterprise Reporting Server C cachedtime setting 190 changing user accounts 175 ClusterTrends profile settings 32 ClusterTrends Add-On profile setup 27 com_orgtype setting 188 command line, steps for using 182 command syntax 181 company database 93 configuring program options 123, 283, 298 the Reporting Server 274 content report 119 content groups 168 profile settings 61 ContentGroupProfileCount setting 232 cookie enable 184 settings 184 validate 184 cookies option 127 profile settings 34 copying profiles 62 country of origin, in reports 126 country setting 196 D dailyreport setting 219 database directory option 137 database location profile settings 58 datadir setting 200, 220 datadiroverride setting 200 Day of Week filter 88 days setting 230 daysenabled setting 230 debuglevel setting 197, 220 default report template 138 reports report default for profiles 139 defaultoveride setting 225 Defaults settings 186 deferred reports setting 197 defining domain types 133 deleted setting 220 deleting ad views and clicks 101 Intranet domain 96 profiles 62 depth setting 235 description ad views and clicks 99 description setting 218 Directory filter 85 directory for profile database 137 directory setting 227 directorycasesensitive setting 227 directoryenabled setting 227 disabled setting

305 Index DNS cache size 123 DNS lookup analyzing without 48 auto mode 49 explained 146 turning on 48 Web log analysis profile 146 dns lookup options 146 dnscachelifespan setting 188 dnslookup setting 198, 220 dnsoverride setting 197 document file types modifying 130 documenttypes setting 190 domain names changing groupings 133 domain settings 186 domain tab 133 Download File Extensions and Types 129 downloadtypes setting 190 dynamic pages and URL search and replace 161 including in reports 169 dynamic sites and URL parameter analysis 60 dynamic web pages, in reports 131 E editing ad views and clicks 101 Intranet domain 96 profiles 62 report template styles 120 edu_orgtype setting 186 elements for reports 119 enablearchives 197 enablearchives setting 220 Entry Page filter 83 entrypage setting 231 entrypagecasesensitive setting 232 entrypageenabled setting 231 error profile failed to initialize 30 errors interface log verbosity 211 ErsAddress 205 ERSRetries 210 ERSTimout 210 exit URLs tracking 97 F features 1 file extensions, adding or editing 131 file extensions, edit 130 File filter 86 file name Ad View 99 file types, adding or editing 131 file types, edit 130 files setting 227 filescasesensitive setting 228 filesenabled setting 228 filtering 67 filters Browser

306 WebTrends Enterprise Reporting Server creating 68, 76 Day of Week 88 defaults 225 Directory 85 Entry Page 83 File 86 Hour of Day 88 Multi-Homed Domain 88 overview 67 profile settings 34 Referrer 83 settings 225 URL 85 filtertype setting 225 frequency for archving 184 FTP configuring proxy settings 147 FTP connections 204 FTP paths 204 FTP settings (command line) 203 FTP shared cache 203 ftppersistantcachesize 203 G gatestring setting 239 general options 123 WebTrends 123, 283, 298 gid 208, 213 gov_orgtype 187 graphs changing the size 119 modifying 119 H handles 208, 213 histoverride setting 201 homepagebasedir setting 219 homepagedefaults setting 219 Hour of Day filter 88 hourall/none setting 231 hourbegin setting 230 hourenabled setting 231 hourend setting 231 HTML titles in reports 123 html titles, including in reports 124 I ID String Ad Click 100 IncludeContentGroups 191, 222 includedefaultpages setting 228 IncludePathAnalysisProfiles 192 IncludePathsAnalysisProfiles 223 IncludeQueries 222 IncludeQueryStrings 191 includesubdirs setting 227 IncludeURLReplacements 193, 223 int_orgtype 187 Interface 204 interface log file 211 port 211 retries 210 timeout 210 user timeout 211 interface engine port

307 Index interface settings 204, 210 international options 125 Internet advertising tracking 98 Intranet domain adding 94 deleting 96 editing 96 Intranet Management 93 Intranet management initialization files 241 IsServerCluster setting 219 J job queue 112 K keywords.ini 242 L language changing 120 language settings 196 leadinmatchtype setting 240 leadinstring setting 239 locale options 125 log file path dialog 32 log files about 104 log, interface 211 logdir setting 183 logfile setting 183 logfileformat setting 197, 220 logfilepath setting 219 logging in 108 lookupqueuesize 195 M mapfile setting 237 maxanalysis setting 195 maxarchives for archiving 184 maxcachedcount setting 188 maxgridprofiles 205 maxrefresh 205 maxtableentries setting 235 MaxTableSizes 206 maxthreads setting 188 maxtopcount setting 188 memory usage, limiting for reports 206 methods setting 212 Microsoft Word reports 115 mil_orgtype setting 187 mode 204 modifying user accounts 175 monthlyreport setting 201, 221 Multi-Homed Domain filter 88 multihomedomain setting 226 multihomedomainenabled setting 226 multiple servers 218 N logfilepath 218 MatchString 233 name setting 225 net_orgtype setting

308 WebTrends Enterprise Reporting Server nohtmltitles setting 191 O on-demand reports 111 option cookies 127 options configuring 123, 283, 298 database directory 137 dns lookup 146 general 123 locale 125 profiles 126 report scheduler 143 report template 138 reports 139 system performance 144 web server 136 org_orgtype setting 188 OSAuthentication setting 211 P page setting 236 page titles, including in reports 124 pages,sorting into groups 168 PageType setting 233 pagetype setting 235, 237, 238 parameter setting 237 passive FTP 204 password setting 214 path analysis 166 definition name 236 depth 235 id 235 maximum paths 235 page type 235 profile version 235 starting page 235 path analysis definitions profile settings 61 path analysis settings 234 paths through site 166 PathsAnalysisProfileCount setting 235 peformance options 144 Performance settings 194 period setting 198, 221 permissions about 214 permissions setting 214 plaintextpwd 214 port 149 web server (command line) 211 port for interface 205 processingtype 197 processingtype setting 219 product features 1 profile analyzing from a specific date 28 defaults 218 settings 197 profiledir setting 186 ProfileID setting 233 profileid setting 235, 237, 238 ProfileName setting 233 profilename setting 236, 237, 238 profiles 67 about 106 archiving 54,

309 Index cookie settings 34 copying 62 database directory 137 database location 58 deleting 62 editing 62 filtering 34 general overview 106 grouping pages 61 log file path setting 32 monitoring status 63 path analysis settings 61 processing 112 report paths 56 restoring with archives 55, 273 scheduling reports 56 server settings 32 settings 218 stopping analysis 62 text files 217 tracking advertising 101 URL parameter analysis settings 60 URL replacement settings 59 viewing more in list 205 profiles directory 126 profiles options directory for profiles 126 ProfileVersion setting 233 profileversion setting 235, 237, 240 prostatrefresh 205 proxy server settings 147 Q quarterlyreport setting 201, 221 query strings 169 QueryProfileCount 236 queues profile processing 112 R Referrer filter 83 referrer setting 228 referrerenabled setting 228 regular expressions comparing with wildcards 281 components 277 example URL match 279 examples on using 279 matching order rules 280 remote configuration settings 210 removing templates 121 replacementstring setting 240 report content 119 default schedule for profiles 143 excluding blank chapters 118 language 118 report color,changing 119 report distribution profile settings 56 report language changing 120 report language,changing 120 report paths profile settings 56 report scheduler option 143 report setting 196 report style 307

310 WebTrends Enterprise Reporting Server adding 116 report template default for profiles 138 editing 120 removing 121 report template option 138 report template style adding 116 report templates about 116 report types 40, 139 reportdestoverride setting 199 reportdir setting 199, 221 reportfile setting 199, 221 Reporting Server 1 reports 62, 136 about 104 color 117 country of origin 126 customizing 116 deleting 40, 139 directory 136 font 117 incorrect dates 269 Microsoft Word 115 on-demand 111 problems with Word reports 269 report types 40, 139 reports to save 40, 139 running 110 search engines included 242 start time 144 viewing 110 reports option 139 reports to save 40, 139 reporturl setting 199 reporturl setting 221 resolve 209 resolving IPs 146 restoring profiles and archiving 55, 273 restrictions 217 retries,interface 210 returncodes setting 225 returncodesenabled setting 225 root setting 235 running reports 110 S Scenarios Configuring WebTrends for your Intranet 94 Tracking Internet Advertising 97 schedoverride 198 scheduling reports profile settings 56 scripts, in reports 131 search engines reported on 242 searchkeywords setting 229 searchkeywordsenabled setting 229 server log file path 218 name 218 web server for publishing reports 136 server cluster settings 218 server settings 218 servername setting 218 servers profile settings

311 Index setting 218, 233 sheduling reports 143 shopping cart software and URL replacement 60 shopping cart software,and URL search and replace 161 showadmindatadir setting 200 showbrowsermenu 205 site configuration dialog 27 startimmediately setting 198 startprocessingat setting 219 starttime setting 198, 221 status profiles 63 stopping analysis 62 stopping analysis and reporting 62 stopping profile analysis 62 styles adding 116 syntax 181 system performance option 144 T tables changing the size 119 template editing 120 removing 121 templates editing 120 testing url replacement definitions 165 threadedanalysis setting 194 threadedreports setting 197, 221 timeout interface 210 user session 149 titlecachelifespan setting 190 titlecachesize setting 190 tracking advertising 97 tracking Internet advertising 98 trailermatchtype setting 239 trailerstring setting 240 translation file 171 U uid 207, 212 unique URLs and URL search and replace 161 UNIX settings gid 208, 213 handles 208, 213 uid 207, 212 URL filter 85 URL parameter analysis 60, 169 definition name 237 id 237 page to track 236 page type 237 parameter to track 237 profile version 237 translation file 237 URL parameter analysis settings 236 URL parameter defintion settings 236 URL path 136 URL replacement 60 URL replacement definitions profile settings

312 WebTrends Enterprise Reporting Server url replacement definitions testing 165 URL Search and Replace definition count 238 definition name 238 id 238 page type 238 settings 237 URL search and replace about 161 creating a definition 164 urlreplacementrofilecount setting 238 usdomains setting 187 useabsolutepath setting 204 usegatestring setting 239 UseGlobalContentGroups 192 useglobalpathsanalysisprofiles 192 useglobalquerystrings 192 UseGlobalURLReplacementFilters 193 usepassiveftp setting 204 user filter settings 217 password 214 permissions 214 profile settings 217 restrictions settings 217 username 214 user accounts modifying 175 user session timeout 149 user settings 213 username filter 89 username setting 214, 229 usernameall setting 229 usernamecasesensitive setting 229 usernameenabled setting 229 users setting 219, 226 usersenabled setting 226 usesymlinks 209, 268 usetotracksession setting 240 using ad views and clicks 98 V version setting 218 viewing reports 110 views page view 130 visitor session length 123, 124 W web log analysis filters overview 67 Web log analysis profiles DNS lookup 146 web server port 149 settings (command line) 210 web server configuration 148 web server options 136 WebAddress setting 211 WebLogErrors setting 211 WebLogFileName setting 211 webservermode setting 199 webservermodeoverride setting 199 WebTrends Reporting Server features 1 how it works

313 Index WebUserTimeout setting 211 weeklyreport setting 201, 222 wildcards comparing with regular expressions 281 examples 281 Word reports problems with 269 wtinterface, settings 210 wtm_wtx.ini interface section 204 UNIX section 212 wtreportdir setting 200, 222 wtreporturl setting 200 wtreporturl setting 222 Y yearlyreport setting 201,