Administrator Guide
October 1999 Edition
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
WebTrends is a registered trademark of WebTrends Corporation.
WebTrends Enterprise Reporting Server is a trademark of WebTrends Corporation. 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 , please refer to the WebTrends Corporation “Knowledge Base” online at: http://www.webtrends.com/products/ webtrend/support.htm.
If you are unable to resolve the problem, do not hesitate to contact our Product Support Department: Telephone: (503) 223-3023, Fax: (503) 294-7130.
If you receive your first copy of the Software electronically, and a second copy on media, the second copy may be used for archival purposes only. This license does not grant you any right to any enhancement or update.
You may not: permit other individuals to use the Software, modify, translate, reverse engineer, decompile, disassemble (except to the extent applicable laws specifically prohibit such restriction), or create derivative works based on the Software; copy the Software (except for back-up purposes); rent, lease, transfer or otherwise transfer rights to the Software; or remove any proprietary notices or labels on the Software or documentation.
TITLE
Title, ownership rights, and intellectual property rights in and to the Software shall remain with the Developer or its suppliers. The Software is protected by the copyright laws of the United States and international copyright treaties. Title, ownership rights, and intellectual property rights in and to the content accessed through the Software is the property of the applicable content owner and may be protected by applicable copyright or other law. This License gives you no rights to such content.
DISCLAIMER OF WARRANTIES
THERE ARE NO WARRANTIES, CLAIMS OR REPRESENTATIONS MADE BY DEVELOPER, EITHER EXPRESS, IMPLIED, OR STATUTORY, WITH RESPECT TO THE SOFTWARE, INCLUDING WARRANTIES OF QUALITY, PERFORMANCE, NON INFRINGEMENT,
MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE, NOR ARE THERE ANY WARRANTIES CREATED BY COURSE OF DEALING, COURSE OF PERFORMANCE, OR TRADE USAGE. DEVELOPER DOES NOT WARRANT THAT THE SOFTWARE WILL MEET YOUR NEEDS OR BE FREE FROM ERRORS, OR THAT THE OPERATIONS OF THE SOFTWARE WILL BE UNINTERRUPTED. THE FOREGOING EXCLUSIONS AND DISCLAIMERS ARE AN ESSENTIAL PART OF THIS AGREEMENT AND FORMED THE BASIS FOR DETERMINING THE PRICE CHARGED FOR THE PRODUCTS. SOME STATES DO NOT ALLOW EXCLUSION OF AN IMPLIED WARRANTY, SO THIS DISCLAIMER MAY NOT APPLY TO YOU.
EXCLUSIVE REMEDY
Developer’s cumulative liability to you or any other party for any loss or damages resulting from any claims, demands, or actions arising out of or relating to this Agreement shall not exceed the license fee paid to Developer for use of the Software. In no event shall Developer be liable for any indirect, incidental, consequential, special, or exemplary damages or lost profits, even if Developer has been advised of the possibility of such damages.
STRICT LIABILITY, OR OTHER TORT, BREACH OF ANY STATUTORY DUTY, INDEMNITY OR CONTRIBUTION, OR OTHERWISE, EVEN IF DEVELOPER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE EXCLUSION CONTAINED IN THIS PARAGRAPH SHALL APPLY REGARDLESS OF THE FAILURE OF THE EXCLUSIVE REMEDY PROVIDED IN THE FOREGOING PARAGRAPH. SOME STATES DO NOT ALLOW THE LIMITATION OR EXCLUSION OF LIABILITY FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE LIMITATIONS OR EXCLUSIONS IN THIS AND THE FOREGOING PARAGRAPH MAY NOT APPLY TO YOU.
TERMINATION
This license will terminate automatically if you fail to comply with the limitations described above. On termination, you must destroy all copies of the Software.
MISCELLANEOUS
This Agreement represents the complete agreement concerning this license between the parties and supersedes all prior agreements and representations between them. It may be amended only in writing executed by both parties. If any provision of this Agreement is held to be unenforceable for any reason, such provision shall be reformed only to the extent necessary to make it enforceable. This Agreement shall be governed by and construed under Oregon law as such law applies to agreements between Oregon residents entered into and to be performed within Oregon, except as governed by Federal law.
U.S. Government Restricted Rights. Use, duplication or disclosure by the Government is subject to restrictions set forth in subparagraphs (a) through (d) of the Commercial Computer-Restricted Rights clause at FAR 52.227-19 when applicable, or in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, and in similar clauses in the NASA FAR Supplement.
Manufacturer is WebTrends Corporation, 851 SW 6th Avenue, Suite 1200, Portland, OR 97204, U.S.A.
Chapter 1. Introducing WebTrends Enterprise Reporting Server 15
About this guide . . . .15
About WebTrends Enterprise Reporting Server . . . 15
Reporting server features . . . 15
How it works . . . 16
Reporting Server Concepts . . . 17
Understanding log files . . . 17
Understanding profiles . . . 18
Understanding reports . . . 18
Setting up the Reporting Server . . . 19
What typographic changes mean . . . 20
Making documentation available to non-administrators. . . 20
Getting help . . . 21
Resources . . . 21
Chapter 2. Installing and Setting Up the Reporting Server . . . 23
System requirements . . . 23
Installing the Reporting Server . . . 23
Installing on Solaris . . . .23
Installing on Linux . . . 27
Running the Reporting Server the first time. . . 30
Uninstalling the Reporting Server . . . 31
Installing Add-Ons . . . 31
Chapter 3. Reporting Server Remote Interface . . . 33
About the Remote Interface . . . 33
Accessing the Remote Interface . . . 33
Using the Main Console. . . 35
Using the menu . . . .36
Using the toolbar . . . .37
Chapter 4. Analyzing Web Site Activity . . . 39
About Reporting Server analysis . . . .39
Preparing to analyze web site activity . . . 39
Creating a profile . . . 40
Specifying the site configuration . . . .42
Specifying general profile information . . . .43
Activating archiving . . . .43
Disabling the profile . . . .44
Specifying the log file for single server profiles . . . .44
Setting up servers for ClusterTrends profiles . . . .46
Specifying home page location and file names . . . .47
Specifying filters . . . .49
Specifying the cookie to use . . . .49
Selecting the report template . . . .50
Customizing the report header . . . .51
Specifying reports to generate . . . .52
Specifying a schedule for reporting . . . .54
Specifying the location for reports . . . .54
Specifying a DNS lookup method . . . .55
Specifying the database directory . . . .57
Specifying user access . . . .58
Selecting URL Search and Replace definitions . . . .59
Selecting URL Parameter Analysis definitions . . . .59
Selecting Content Group definitions . . . .60
Selecting Path Analysis definitions . . . .60
Copying a Profile . . . 61
Editing a Profile . . . 61
Deleting a Profile . . . 62
Chapter 5. Filtering the Analysis . . . 67
About filters . . . .67
How filters are processed . . . 67
Adding a filter. . . 68
Filter types . . . 69
Return code filter . . . 69
User address or country filter . . . 70
Multi-Homed Domain filter . . . 71
Directory or URL filter . . . 71
File filter . . . 73
Referrer filter . . . 74
Entry page filter . . . 75
Advertising filter . . . 76
Browser filter . . . 76
Authenticated username filter . . . 77
Day filter . . . .77
Hour filter . . . 78
Chapter 6. Tracking Internet Advertising . . . 79
About Ad Views and Clicks . . . 79
Scenario: tracking internet advertising. . . 79
Defining an advertisement to track . . . 80
Adding a profile for an ad . . . 83
Chapter 7. Using Intranet Management . . . 85
About Intranet Management . . . .85
Chapter 8. Working with Reports . . . 89
About reports . . . .89
Report viewer workspace. . . 90
Report calendar . . . .90
Table of contents . . . .91
Status . . . .92
Report . . . .92
Viewing reports . . . 93
Using the job queue . . . 93
Viewing profile history . . . 94
Converting reports to Microsoft Word . . . 95
Customizing reports . . . 96
Adding report templates . . . .97
Editing a report template . . . .101
Deleting a report template . . . .101
Chapter 9. Configuring Reporting Server Options . . . 103
About Reporting Server options . . . .103
General options . . . .103
Archives . . . .104
Web Site Locale . . . .105
Profile directory . . . .106 Cookies . . . .107 File types . . . .109 Domain groups . . . .111 Reports Serving . . . .112 Database directory . . . .114 Report templates . . . .115 Reports . . . .116 Report header . . . .117 Report scheduler . . . .117 System performance . . . .118
URL search and replace . . . 123
Defining paths to analyze . . . 127
Creating content groups . . . .129
Analyzing activity for a dynamic site . . . 130
Web server configuration. . . 132
Chapter 10. Working with Users and Permissions . . . 133
About user access . . . 133
Creating a user account. . . 133
Modifying a user account. . . 135
Chapter 11. Running from the command line . . . 137
About the command line capability . . . 137
Directory structure . . . 138
Command line options . . . 139
Scripts . . . 139
Executables . . . .140
Recommended steps for using command line settings . . . 141
Hierarchy of settings . . . 142
Configuring program settings. . . 142
audit . . . 142 archives . . . 143 cookie . . . 143 defaults . . . .145 reports . . . 152 performance . . . 152 language . . . 153 profile . . . 154 Proxy . . . 158
FTP . . . .159
Interface . . . .160
MaxTableSizes . . . .161
Feedback . . . .162
Unix . . . .162
Configuring web server settings. . . 165
Audit settings . . . .165
Remote configuration . . . .165
Authentication settings . . . .166
Unix . . . .167
Setting up user accounts and permissions . . . 168
user info settings . . . .168
Permissions . . . .169
filter[n] . . . .171
profile . . . .171
restrictions . . . .171
Working with profiles . . . 174
server[n] . . . .174
profile settings . . . .175
filterx . . . .183
Working with Content Groups . . . 190
Default Content Group settings . . . .190
Content Group defintion settings . . . .190
Working with Path Analysis settings . . . 191
Default Path Analysis settings . . . .191
Path Analysis definition settings . . . .192
Working with URL Parameter Analysis settings. . . 192
Default URL Parameter Analysis settings . . . .192
URL Parameter Analysis definition settings . . . .193
Working with URL Search and Replace definitions . . . 194
Defining advertisements to track . . . 199
Ad views and ad clicks syntax . . . 200
Setting up your intranet domains . . . 200
Modifying search engines . . . 201
SearchEngines . . . 201
Engine settings . . . 201
Appendix A. Glossary . . . 205
Appendix B. Optimizing & Troubleshooting . . . 211
Investigating Errors . . . 211
Using the wtrs.err file . . . .211
Using the wt.remote.err file . . . 211
Using the wtrs.audit file . . . 211
Using the profile status log . . . 212
Fixing Error 500 Server Error . . . 213
Web server fails to initialize . . . 213
Profiles fail to initialize . . . 213
Conflicting file permissions . . . 214
Database location . . . 214
Factors impacting space and memory . . . 214
Connecting through the Remote Interface. . . 215
Problems creating a Microsoft Word report from Internet Explorer . . . 215
Dates for reports are unexpected . . . 215
Special considerations for configuring the Reporting Server. . . 216
Default configuration . . . .216
Configuration implementing an alternate web server . . . 216
About this guide
Welcome to WebTrends Enterprise Reporting Server. The purpose of this guide is to introduce the product features, help you install the software, and get you up and running for reporting.
About WebTrends Enterprise Reporting Server
WebTrends Enterprise Reporting Server provides web server traffic analysis for users with high traffic and multiple clients, such as ISPs, server farms, and large organizations. The built in web server publishes reports automatically, making them available to remote users through their browsers. Administrators can manage all aspects of the Reporting Server remotely. 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 137 for details.
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 23 for browser requirements.
Reporting server features
This section provides information on the Reporting Server features. • Web Server Log File Analysis--Allows you to report 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--ClusterTrendsTM technology
allows you to get accurate reports for sites hosted by multiple servers. ClusterTrends can be implemented if you have a Server Add-On license.
• Report Template Designer--Create your own look with
Report Templates. You choose the colors, fonts, layouts, and content to use.
• Comprehensive Reports--Reports are created and
maintained automatically 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--User access management
allows you to 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. Preconfigure profile settings for any or all users, making their work easier. Users only view the reports and program features they have access to.
Customizable Interface--Many dialogs in the interface are optional
and can be disabled for non-administrators. You decide if those dialogs are visible to your users.
New features are added frequently. Refer to our web site at http://
www.webtrends.com for the latest information.
How it works
The Reporting Server uses the log file from your web server 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.
Reporting Server Concepts
In order to set up and run the Reporting Server, there are a few key concepts you should understand. This section discusses log files, profiles and reports.
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 NT, Windows 98, or Unix), 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.
Start Report Process WebTrends Reporting Server Profile Web Server Log File
Log File Data Analyzed
WebTrends Reporting Server
Report Report for Profile is Generated and
Published
End Report Process
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:
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:
In this example, the referrer is http://search.yahoo.com/bin/ search?p=trends%20internet, the agent is SPRY_Mosaic/v8.32, and the platform is Windows 16-bit.
Understanding profiles
Profiles specify how the log file should be analyzed and the activity you want to report on. Through the profile you define the location and log file type, any activity you want filtered, and whether or not IP resolution should be performed. WebTrends analyzes the log file and uses the result to create reports. Profiles covered in “Analyzing Web Site Activity” on page 39.
Understanding reports
Reports are based on profiles. Reports are posted automatically, and are available for viewing through your browser. All archived report data is accessible using the calendar in the Report Viewer. Reports are covered in “Working with Reports” on page 89.
www.webtrends.com - [16/Jan/1999:10:36:09+0000] "GET / dept/argguides/dwsg/420102.jpg HTTP/1.0" 304 21342
www.club-voile.fr - - [12/Jan/1996:19:35:39 +0000] "GET / HTTP/1.0" 200 6054 "http://search.yahoo.com/bin/ search?p=trends%20internet" "SPRY_Mosaic/v8.32 (Windows 16-bit) SPRY_package/v4.00"
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.
For This Step Refer To
1. Install the Software. “Installing and Setting Up the Reporting Server” on page 23.
2. Review the sample profile. This is the essence of 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 dialogs you may want to disable for non-administrators. You may want to give the responsibility of creating and maintaining profiles to Administrators only, making non-administrators’ lives much easier; all they’ll need to do is log in and select their reports.
“About Reporting Server analysis” on page 39
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 colors used. You can change the colors for the Report Template in the Template dialog.
“Report viewer workspace” on page 90.
4. Create profiles for the 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.
“Creating a profile” on page 40.
5. Review the Options settings. Many default settings for profiles are located here. Decide whether you want non-administrators to have access to the optional dialogs.
“Configuring Reporting Server Options” on page 103.
What typographic changes mean
The following table describes the typographic changes used in this guide.
Table 1 - 1 Typographical Changes
See “Glossary” on page 205 for additional definitions of terms used in the program and in the documentation.
Making documentation available to non-administrators
A user guide for non-administrators is also available. We strongly recommend that you make the WebTrends Enterprise Reporting Server User 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 from the CD. Otherwise, you can download the manual from the Support section of the WebTrends Corporation web site:
1 Open your browser.
2 Enter the following URL: www.webtrends.com
6. Create user accounts for anyone who is going to use the Reporting Server for viewing reports or managing any aspect of the reporting server. For each user, determine the permissions you want to give.
“Working with Users and Permissions” on page 133.
7. Modify the Report Template Styles or create your own if needed.
“Customizing reports” on page 96.
This text Represents
Bold A button in the graphical user interface (New button). Title Case Refers to the names of dialogs and fields (Add Profile
dialog, Home Page URL field) in the graphical user interface.
courier font
Commands, source code examples, program output, and file or program names.
“in quotes” Refers to a title of a chapter or section.
3 Click Support to access the Product Support Page.
4 Click Documentation to view the manuals available.
Getting help
The Reporting Server provides online help to guide you through the program. Look for the Help button in program dialogs. If you’re not sure about what to enter in field, click the Help button. At any time, you can access help by selecting the Help menu from the main console.
Resources
WebTrends’ portal for Internet and Intranet professionals is a great resource for Web related information, industry news, reviews, and other useful information. Visit www.WebTrends.net to see for yourself.
System requirements
(Solaris) You can run the Reporting Server on Sun UltraTM or Sun
SPARCstationTM running Solaris 2.5, 2.6, or 2.7.
(Linux) You can run the Reporting Server on any Intel platforms running Red Hat 5.2 or above.
You can install and run the program with the following minimum system requirements:
• 45 MB available disk space • 128 MB memory
Note: More space and memory is required to analyze large logs. Contact your Product Support representative for more information.
You can view reports on any machine so long as Netscape Navigator 4.5 or above or Microsoft Internet Explorer 4.01 or above is installed on the machine.
Installing the Reporting Server
Note: The Bourne shell or Bourne-like shell must be available to install the Reporting Server.
Installing on Solaris
Install the Reporting Server using either the install script from a set of tarred files, or the Solaris package.
Using the installation script
The installation script installs the files and configures the program in one process.
1 Type mkdir <tempdirectoryname> where tempdirectoryname refers to the directory used to uncompress and untar the files needed for installation.
2 Type cd <tempdirectoryname> 3 Type cp <source path>/wtrs-2.0-sparc.tar.gz . 4 Type gunzip wtrs-2.0-sparc.tar.gz 5 Type tar-xvfwtrs-2.0-sparc.tar 6 Type cd wtrs-2.0
Note: If you are not logged on as root, Reporting Server warns that you can not install the program as a service. Type Ctrl-C to cancel, or Enter to proceed with the installation.
7 Type
./install.wtrs
The WebTrends Enterprise Reporting Server Software License Agreement is displayed.
8 Press Enter to view the Software License Agreement.
9 Type
accept
if you consent to the Software License Agreement. The installation begins. If you do not accept the Software License Agreement, enter CTRL-C or type anything other than "accept."
10 Press Enter when you have reviewed the explanation of your authentication options.
11 Enter Y to accept the default directory for the Reporting Server. The default directory is /usr/local/webtrends. To install the program in another location, enter the directory.
12 Enter the port number to use for the user interface. This is the
port through which users access the Reporting Server through their browsers.
If you are installing as root, the default port is 99. If you are installing as non-root user, the default is 1024. Make sure the port that you specify is not used by another service.
Enter Y to verify the port number.
Note: If you are logged in as root, you can use ports below 1024.
13 Enter the username of the person performing the installation.
The user you specify is given Administrator rights for the Reporting Server.
14 Enter 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 9999. To accept it, press Enter. Enter Y to verify that this is the port that you want to use.
15 If you are installing as root, you can specify how you want to start
the Reporting Server. Enter Y to start the Reporting Server automatically at system bootup. Otherwise, enter n.
16 Enter Y to start the Reporting Server now. Otherwise, enter n.
17 Press Enter when you have reviewed information about the services available.
18 Enter Y to review the readme file. Otherwise, enter n.
Note: To run the Reporting Server, launch your browser and enter the name of the machine, followed by a colon and the port you specified during installation. For example,
Running the installation package
To install the Reporting Server using the Solaris package:
1 Type mkdir <tempdirectoryname> where tempdirectoryname refers to the directory used to uncompress and untar the files needed for installation.
2 Type cd <tempdirectoryname> 3 Type cp <source path>/wtrs-2.0-sparc.pkg.tar.gz 4 Type gunzip wtrs-2.0-sparc.pkg.tar.gz 5 Type tar-xvfwtrs-2.0-sparc.pkg.tar 6 Type cd wtrs-2.0-sparc 7 Type pkgadd -d ‘pwd‘/wtrs-2.0-sparc
The package installs the program files.
8 When you are ready to configure program settings, run
configure.sh from the /wtrs-2.0-sparc directory which takes you through the setup process. Refer to steps 8-19 of “Using the installation script” on page 23 for details.
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
1 Type mkdir <tempdirectoryname> where tempdirectoryname refers to the directory used to uncompress and untar the files needed for installation.
2 Type cd <tempdirectoryname> 3 Type cp <source path>/wtrs-2.0-sparc.pkg.tar.gz 4 Type gunzip wtrs-2.0-sparc.pkg.tar.gz 5 Type tar-xvfwtrs-2.0-sparc.pkg.tar 6 Type cd wtrs-2.0-sparc 7 Type
pkgadd -a ‘pwd‘/admin -d ‘pwd‘/wtrs-2.0-sparc
Installing on Linux
Install the Reporting Server using the installation script or the RPM.
Note: The Bourne shell or Bourne-like shell must be available to install the Reporting Server.
Using the installation script
The installation script installs the files and configures program settings in one process.
1 Type
mkdir <tempdirectoryname>
where tempdirectoryname refers to the directory used to uncompress and untar the files needed for installation.
2 Type
cd <tempdirectoryname>
3 Type
4 Type
gunzipwtrs-2.0-linux.i586.tar.gz
The files needed for installation are uncompresed.
5 Type
tar-xvfwtrs-2.0.tar
6 Type
cd wtrs-2.0
If you are not logged on as root, Reporting Server warns that you can not install the program as a service. Type Ctrl-C to cancel, or Enter to proceed with the installation.
7 Type
./install.wtrs
The WebTrends Enterprise Reporting Server Software License Agreement is displayed. Press Enter to view the Software License Agreement.
8 Type accept if you consent to the Software License Agreement. If you do not accept the Software License Agreement, enter CTRL-C or anything other than accept.
9 Press Enter when you have reviewed the explanation of authentication options.
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, enter the directory.
Enter Y to verify that you want to use the specified directory.
11 Enter the port number for the user interface. This is the port
through which users access the Reporting Server through their browsers. If you are installing as root, the default port is 99. The default port for non-root users is 1024. Make sure the port is unused by any other service.
Enter Y to verify the port number.
12 Enter the username of the Administrator performing the
installation.
13 Enter 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 11. The default port is 9999. To accept it, press Enter.
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. Type Y to start the Reporting Server when you boot the system. Type N if you want to start it manually.
15 Type Y to start the service when the installation is complete. Type n to start it manually.
16 Type Y to view the readme file. Otherwise type n.
Using the RPM
You can run the RPM from the WebTrends Enterprise Reporting Server CD-ROM.
1 From the CD-ROM drive, type
rpm -i wt-ers-linux.i586.rpm
2 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.
1 From the CD-ROM drive, type
rpm -U wt-ers-linux.i586.rpm
2 When you are ready to configure program settings, run configure.sh which takes you through the program setup.
Running the Reporting Server the first time
Once the Reporting Server is installed, you can run it through your browser.
To run the Reporting Server
1 Open your Internet Explorer or Netscape Navigator browser.
2 Enter 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, http://server:1137
3 The Reporting Server Login screen opens. Click the Login button.
4 Enter the username you specified during the installation. For now, you can leave the password field blank. You should specify a password in your .usr file. See “About user access” on page 133 for details.
5 The Limited Demonstration screen opens.
6 Specify whether you want to download a trial code purchase a full version.
7 Once you complete the trial registration form or purchase a full version, you are emailed a trial code or product serial number.
8 Enter the code you are given in the Trial Code or Product Serial Number field. Click Submit.
Uninstalling the Reporting Server
If at any time you want to remove the Reporting Server from your system, use the procedure described here.
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 (Solaris) rm /etc/rc3.d/S99 wtrs.server
(Linux) rm /etc/rc.d/init.d/S99
Note: You must be logged in as root to remove this file.
3 Type
rm -r -f <install dir>
where <install dir> refers to the directory where the Reporting Server is installed.
4 Type
(Solaris) rm /etc/init.d/wtrs.server
(Linux)rm /etc/rc.d/init.d/wtrs.server
to remove the wtrs.server file.
Note: You must be logged in as root to remove this file.
Installing Add-Ons
When you first install the Enterprise Reporting Server, you have the ability to analyze log files for one web server. The standard
installation supports a total of five (5) users.
If you wish to analyze log files for additional web servers, you must purchase the appropriate number of Server Add-Ons.
To support more than five users, you must purchase the appropriate number of User Add-ons.
You can purchase both Server Add-Ons and User Add-Ons from the WebTrends Corporation web site.
To purchase and install the Add-On:
1 Go the WebTrends Corporation web site at www.webtrends.com/ order/.
2 Order the Add-ons. Write down the license code that you are given.
Note: You must know the license code to run the installation.
3 Select Help>License Add-ons. Enter the license code you were given. The new license is activated.
About the Remote Interface
This chapter explains how to log in to the Reporting Server and how to use the program through the Remote Interface.
Note: You can also control all aspects of the Reporting Server from the command line. See “Running from the command line” on page 137 for details.
Accessing the Remote Interface
To run the Reporting Server through the remote interface, the program and the reporting server must be started.
To start the Reporting Server
1 Enter the path to the install directory and type
wtrs
The program starts as shown here.
2 Type
wtrs -start
The reporting server starts.
3 Type
wtinterface -start
To login to the Reporting Server
1 Open your web browser (Netscape Navigator or Internet Explorer.)
2 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, http://192.168.0.5:99. The Login window opens as shown here:
3 Click the Login button.
4 Enter your system username and password for the machine where the Reporting Server is installed. To change the username and password, see “Working with Users and Permissions” on page 133.Enter your system username and password for machine where WebTrends is installed or the username and password you were given to run the program.
5 If you have not completed the registration for the Reporting Server, the following dialog opens.
• Register Now--Click this button to register your copy of the
• Register Later--Click this button to complete the registration
at another time.
Using the Main Console
When you log in, the Main Console opens. From the Main Console, you can run reports, work with profiles, and access program configuration settings.
Tip: You can turn the browser toolbar on or off using the Browser Toolbar command on the File menu.
Using the WebTrends profiles tab
The WebTrends Profiles tab displays all profiles that have been created.Sample profiles are included so that you can get familiar with the Reporting Server and run sample reports. As an Administrator, you have access to all profiles.
Using the menu
The menu bar provides access to all program functions. For
example, you can create a new profile, view profile status, or access your server license agreement.
Table 3 - 1 Menus
Menu Provides
File Commands for working with profiles and reports and exiting the program.
Profile Commands for the analysis and performing archives.
View Access to status windows, job queues, and browser toolbar.
Configuration Access to program options, user access, advanced features, and web server configuration.
Tool bar Menu bar
Using the toolbar
The toolbar provides quick access to the most used commands.
Table 3 - 2 Toolbar commands
Help Access to the Help Table of Contents, the WebTrends Corporation web site, and the About box.
Feedback Enterprise Reporting Server feedback form. Let us know what you think.
Button Purpose
Displays the Report window where you view the report for the selected profile.
Displays the Options window where you can modify program options including the default values for profiles.
Displays the Configure User Access window where you can create and modify user accounts.
Displays the Edit Profile dialog where you can change the selected profile settings.
Displays the Profile Wizard for creating a new profile. All analysis and reporting is based on profiles.
Lets you remove the selected profile from the list.
Displays the Report Templates window where you can define the colors used for reports.
Displays the Ad Views and Clicks dialog where you can set up ads to track for traffic.
Displays the Intranet Configuration dialog where you can set up the domains in your organization by country, state, city, department or workstation.
Displays the Online Help where you’ll find detailed information on all Reporting Server dialogs.
About Reporting Server analysis
Reporting Server reports are based on profiles which define the location of your web server log file and how it 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
• users who can access the profile • location for report data
• reports to create
• schedule for updating reports • cookie to use
As an Administrator, you can add, edit, and modify all profiles, even those created by other users.
Note: Specify the profile settings non-administrators have access to through the Options window. See “Configuring Reporting Server Options” on page 103 for details.
Note: The Reporting Server allows you to specify which users have access to profiles and the options they are allowed to define. See “Working with Users and Permissions” on page 133 for details.
Preparing to analyze web site activity
To set up a new profile to analyze your site’s activity, you’ll need the following data:
• Where are log files stored? You’ll need the exact file path
• 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 990111.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.
• Does your site reside on a single server or multiple
servers? This is the first question you’ll encounter when you
create a profile. 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.
Creating a profile
Many of the steps involved in creating a profile are optional or may have been configured for you. This section describes every profile dialog that may be available, depending on your program setup. Refer to the sections that follow for a complete explanation of the steps in the following table.
To create a profile
1 Click New on the toolbar.
2 Define the settings described in the following table. Some settings are optional and may not be accessible to you.
Table 4 - 1 Profile settings
Dialog Description Refer to
Site Configuration Specifies whether the web site is maintained by one server or multiple servers (such as a server cluster or farm).
See “Specifying the site configuration” on page 42.
General Specifies a name for the profile. Provides settings for disabling the profile and enabling archiving.
See “Specifying general profile information” on page 43.
List of Servers If the web site exists on multiple servers, this dialog specifies the servers and the location of the log files.
See “Setting up servers for ClusterTrends profiles” on page 46.
Log File Path If your web site is on one server, this dialog specifies the location of the log files.
See “Specifying the log file for single server profiles” on page 44. Home Specifies the home page default
file names and the URL for the root of your web site. This information is optional.
See “Specifying home page location and file names” on page 47.
Filters Specifies the activity filters to apply to this profile. By default, all log file activity is analyzed.
See “Specifying filters” on page 49.
Cookies Allows you to enable cookies and specify the cookie to use.
See “Specifying the cookie to use” on page 49.
Report Template Specifies the template to use for reports.
See “Selecting the report template” on page 50.
Report Header Specifies settings for the report header such as a graphic or title to use.
See “Customizing the report header” on page 51.
Reports Specifies the reports created, and allows you to delete old reports when the specified limit is reached.
See “Specifying reports to generate” on page 52.
Report Scheduler Specifies when the reports are run and how often they are updated.
See “Specifying a schedule for reporting” on page 54.
Report Paths Specifies where reports are posted on the web server and the directory where they are saved.
See “Specifying the location for reports” on page 54.
DNS Lookup Specifies the IP resolution method to use.
See “Specifying a DNS lookup method” on page 55.
Database Directory Specifies the location for this profile’s database.
See “Specifying the database directory” on page 57.
Specifying the site configuration
With the ClusterTrends Add-On, the Reporting Server can analyze web site activity for sites that reside on multiple servers. This is the first issue addressed when you create a new profile.
To make your site configuration selection
1 Click New on the toolbar. The Site Configuration dialog opens.
2 Select one of the following:
User Access Specifies the users who can use this profile.
See “Specifying user access” on page 58 Advanced Features Provides access to any Advanced
Features that can be defined on a profile basis.
See “Selecting URL Search and Replace definitions” on page 59, “Selecting URL Parameter Analysis definitions” on page 59, “Selecting Content Group definitions” on page 60, or “Selecting Path Analysis definitions” on page 60.
• My Site Is On One Server
If your web site resides on one server, select this option.
• My Site Resides on Multiple Servers
If your site resides on more than one server, such as a server cluster, select this option.
Note: You must have purchased and installed a Server Add-on with ClusterTrends to implement this technology.
Specifying general profile information
The General dialog specifies the name for the profile. The profile name identifies it in the profile list and serves as the default title for reports.
1 Select the profile to work with, and click Edit.
2 Select the General dialog. Enter a name for the profile.
3 Specify how much of the log to analyze by selecting one of the following:
• From the start of the log file--Analyzes the entire log file.
• From the following date--Analyzes the log beginning with
the date specified. Enter the date in day/month/year format.
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 or if you made changes to the profile that you want to undo.
• Archive settings are maintained in the Options window. • See “Restoring profiles to an earlier state” on page 62 for
details on using archives.
To enable archiving
2 Select the General tab.
3 Click in the Enable Archiving box. The archive is made at regular intervals which have been defined in the Options window. See “Archives” on page 104 for details.
Disabling the profile
You can disable the analysis and reporting for an individual profile.
1 Select the profile to work with, and click Edit.
2 Select the General dialog, and click in the Disable Profile check box.
3 Click OK. The profile is disabled until you clear the Disable Profile box.
Specifying the log file for single server profiles
If your web site resides on a single server, use this information to specify the location and format of the log file.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.
You can access your log either locally through a mapped or mounted drive, or using FTP.
Tip: 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 17 for an overview of log files.
2 Select the Log File Path dialog.
3 From the drop-down list, select the access method to use: • file://--Select this option if the file is available on the machine
where WebTrends Enterprise Reporting Server is installed, or if it is accessible through a mounted/mapped drive.
• ftp://--Select this option if you access the log file using FTP.
For example, if your site is hosted by an ISP, you may have to retrieve your log using this method.
4 Specify the path to the log in the corresponding field. If your logs are saved according to date, you can use date macros to simplify your entry. You can specify a set of similarly named logs using wildcards. Or separate several individual logs with a space. For example, httpd/logfiles/access_log specifies the
access_log file in the httpd/logfiles directory.
5 If the log files specified are accessed using FTP and the server requires the user to authenticate, enter the login Information in the Username and Password fields.
Click here for Examples
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.
1 Select the ClusterTrends profile to work with, and click Edit.
2 Select the List of Servers tab.
3 Select the log file format from the list. The Server Names list specifies any servers that have been defined for this web site.
4 Click Add to define a new server. In the Server Name field, enter a name to identify the server.
5 In the Log File Path field, enter the path to the log file. Logs that are accessed using FTP, should be specified using the following syntax:
ftp://ftp.domain.com/filepath
where domain.com is the FTP server and file path is the complete path to the log files.
Enter each log file path on a separate line.
6 If the log files are accessed using FTP and the server requires the user to authenticate, provide the authentication information in the Username and Password fields.
7 Click OK when you are finished. See “Specifying the log file for single server profiles” on page 44 for details on specifying the access method and log file path.
Specifying home page location and file names
The data in the Home Page dialog is used to provide a more accurate home page hit count and to locate your home page directory for looking up web page titles.
Note: To include page titles in reports, you must also check the HTML Page Titles box in the General options tab.
To include this information in reports
1 Select the profile to work with, and click Edit.
2 Select the Home dialog.
3 In the Home Page File Names field, specify the file names that the web server defaults to when a visitor enters a URL without entering a specific file name. Separate multiple file names with spaces. Doing so reports all references to the home page whether or not the visitor specifically included the file name, making the home page hit count more accurate. You can enter up to 255 characters.
4 In the web site URL field, specify the URL to the root your web site, including the access method (http://, ftp://, or file:///).
For example, if you specified your Home Page File Names as default.htm and the Web Site URL as http://www.WebT-rends.com, a hit to http://www.WebTrends.com/ is identified as http://www.WebTrends.com/default.htm. And a hit to
http://www.WebTrends.com/reports/ is identified as a hit to http://www.WebTrends .com/reports/default.htm.
Specifying filters
You can use filters to narrow the focus of your analysis. By default, all log file data is included in the analysis, indicated by the Include Everything filter. All other filters are optional.
1 Select the profile to use, and click Edit.
2 Select the Filters tab. Because the Include Everything filter overrides all other filters, you must select it, and click Delete. Click Add to create a new filter, or select a filter in the list, and click Edit to modify it. See “Filtering the Analysis” on page 67 for details on working with filters.
Specifying the cookie to use
You can use 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.
2 Select the Cookies tab. If you want to use cookies in the analysis for this profile, click in the Use Cookies To Identify User Sessions check box.
3 Specify whether or not to validate the cookie. If your Web site uses a single cookie, you don’t need to validate. However, if your site uses several cookies, select Validate Cookie Format.
4 If you selected Validate Cookie Format in Step 3, specify the cookie to match:
• 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 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.
Selecting the report template
Report templates define the content, language, and style for the report. As an Administrator, you have access to Report Template settings. See “Customizing reports” on page 96 for details.
Note: If the program Admininistrator has already configured this setting, you will not see it.
1 Select the profile to use, and click Edit.
2 Select the Report Template dialog. Select the template from the drop-down list.
Customizing the report header
The Report Header dialog allows you to provide additional details in the report header.
Note: If the program Admininistrator has already configured this setting, you will not see it.
2 Select the Report Header tab. Here you can specify the following:
• Report Title--By default, the profile description is used as the
title for reports, but you can modify it here.
• Report Description--Specifies additional information about
the report that is useful to the user.
• Report Image--Specifies the file path to a graphic that you
want to include.
• Report Image Alt--Specifies the text to display in place of the
graphic if it isn’t available.
• Associated URL--Specifies the URL to load when the report
user clicks on the image. You may have to scroll the window to see this option.
Specifying reports to generate
Use the Reports dialog to select the reports to maintain for this profile. 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.
Note: Because this dialog is optional, you may not see it.
1 Select the profile to work with, and click Edit.
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 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.
A check indicates that the report will be created.
4 Click OK to save your changes.
Specifying a schedule for reporting
Use the Report Scheduler dialog 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 says that the "Start Immediately" option has been selected. In such a 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 field, specify when you want reports to begin.
3 Using the Interval drop-down list, select how often to update the report.
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 program has been configured to use an alternate web
"Start Immediately" message
server and the location can be defined at the profile level, you can use the Report Paths dialog 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.
1 Select the profile to work with, and click Edit.
2 Select the Report Paths dialog. 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.
Specifying a DNS lookup method
The DNS Lookup dialog specifies the DNS lookup method to use for this profile. DNS Lookup is the process of associating a domain name with a numeric IP address. This can be done either by the web server
when logging activity or by the Reporting Server when it analyzes the log files.
DNS Lookup is performed more efficiently by the web server as the log is created, rather than by the Reporting Server. However, if you know your web server administrator or ISP disabled DNS Lookups for their servers, you can have the Reporting Server do them for you.
1 Select the profile to work with, and click Edit.
2 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.
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 “General options” on page 103 for details.
• 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 domain name, it assumes that the web server was performing DNS lookup and switches to Quick Mode.
Specifying the database directory
If accessible, use the Database Directory dialog 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.
1 Select the profile to work with, and click Edit.
2 Select the Report Database tab, and 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.
Specifying user access
You can control the users who can use each profile through the Profile Access dialog. Giving a user access to the profile enables them to use it according to the rights that they have been given. If you want the report for this profile to be viewed publicly, be sure you turn on that option.
1 Select the profile to work with, and click Edit.
2 Select the Profile Access dialog. The Users Who Have Access list displays anyone who has access to this profile. The User Without Access list displays anyone who is not able to use the profile. Use the arrows to change the list.
3 Click the Enable Reports Generated... box to make reports for this profile available to everyone.
Use the arrows to move users.
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 profiles or applied on a profile basis. If the option to select definitions for each profile is enabled, the Advanced Features dialog 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” on page 123 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 on a profile basis. 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 “Analyzing activity for a dynamic site” on page 130 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.
Selecting Content Group definitions
Content Group settings are defined in the Advanced Features window. Content Group definitions can either be applied to all profiles or applied on a profile basis. 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 “Creating content groups” on page 129 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 is accessible in the profile window.
A Path Analysis definition specifies the page and the number of paths that you want to track. See “Defining paths to analyze” on page 127 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.
Copying a Profile
You can use existing profiles as the basis for a profile using the Copy Profile command.
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.
Editing a Profile
Use the Edit Profile dialog to modify settings for a profile.
Note: If the profile is being used for analysis when you make changes, it is updated when the analysis is complete.
1 Select a profile in the list, and click the Edit button.
2 Select the tab with the settings that you want to modify.
Deleting a Profile
You can remove profiles from the Profile List if they are no longer needed.
1 Select a profile in the list, and click the Delete button.
2 Click OK to confirm that you want to remove the profile.
Stopping Analysis
You can interrupt processing of a profile using the Stop Analysis/ Reporting command. Doing so post-pones analysis until the next scheduled interval.
1 Select the profile whose processing you want to stop.
2 Select Profile>Stop Analysis.
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:
