WebTrends 7 Installation and Configuration Guide

Transcription

1 WebTrends 7 Installation and Configuration Guide May 2004 Edition 2004 NetIQ Corporation

2 Disclaimer This document and the software described in this document are furnished under and are subject to the terms of a license agreement or a non-disclosure agreement. Except as expressly set forth in such license agreement or non-disclosure agreement, NetIQ Corporation provides this document and the software described in this document as is without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of merchantability or fitness for a particular purpose. Some states do not allow disclaimers of express or implied warranties in certain transactions; therefore, this statement may not apply to you. This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data. This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time NetIQ Corporation. All rights reserved. U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R (for Department of Defense (DOD) acquisitions) and 48 C.F.R and (for non-dod acquisitions), the government s rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement. Trademarks WebTrends is a registered trademark of NetIQ Corporation. Additional trademarks of NetIQ Corporation include: FastTrends, WebTrends SmartView, WebTrends Report Exporter, GeoTrends, WebTrends Express Viewer, WebTrends SmartSource Data Collector, WebTrends SmartReports, WebTrends On Demand, WebTrends Tech Tools, Log Analyzer, WebTrends Live, and WebTrends Reporting Center. Other brands and their products are trademarks or registered trademarks of their respective holders. ii WebTrends Installation and Configuration Guide

3 Support Sales and General Contact Information Service and Support Online Resources NetIQ Corporation 3553 N. First St. San Jose, CA Phone: Fax: Sales: Direct Technical Support: Americas: Asia Pacific, Australia, New Zealand: Europe, Middle East, Africa: +353 (0) support WebTrends Consulting and Training: services/analytics.asp Customer Resource Center. A portal to resources that can help you make the most of your on-line web initiatives. WebTrends Portland, Oregon 851 SW 6th Ave. Suite 700 Portland OR Phone: Fax: US Toll Free: [email protected] Web: Knowledge Base. Answers to questions most commonly asked: iii

4 iv WebTrends Installation and Configuration Guide

5 Table of Contents Chapter 1 Introduction...11 How to Use This Guide Minimum System Requirements Documentation Getting help in the program...16 Providing feedback...17 Additional resources...17 Visual cues in WebTrends documentation...19 Chapter 2 Installation Overview Licensing How WebTrends is licensed...22 Licensing modes...22 Working with license keys...22 Checking the license status...24 WebTrends On Demand Licensing How WebTrends On Demand is licensed...24 Checking the license status...25 Basic Installation Prerequisites...26 Network...27 Security...27 Installation/WebTrends components v

6 Installing WebTrends software Activating licensing Installing WebTrends Sample Data...31 Installation/SmartSource Data Collector Component...32 Installing on Windows 2000/2003/XP Installing on Linux or Unix Enabling SSL...51 SSL for Apache-based SDC IIS-based SDC Uninstalling the SmartSource Data Collector...57 Uninstalling on Windows 2000/2003/XP Uninstalling on Linux or Unix Upgrading Apache...62 Custom Installation Distributed Architecture...66 Introduction General guidelines Installation steps Managing your distributed installation Migrating Manually...74 Supported migrations Migration components Preparing for migration The migration process Migration example...79 Chapter 3 WebTrends On Demand Accounts Registering for WebTrends On Demand Enterprise...82 Registering for WebTrends On Demand Professional...83 Logging on to WebTrends On Demand Enterprise or Professional...85 vi WebTrends Instrumentation and Configuration Guide

7 Enterprise and Professional Account Console Working with user settings...93 Changing account information...95 Viewing account history...97 Creating an account...98 Instructions for WebTrends On Demand Small Business Small Business Account Console Additional Concepts and Definitions Chapter 4 WebTrends User Accounts Overview Adding Users About Users View Only Permissions Chapter 5 Working with the Report Designer Report Templates Template settings Applying templates Report Dashboards Dashboard settings General tab Content tab Report Options Reports Report templates vii

8 Chapter 6 Express Viewer Introduction Express Viewer Restrictions Installation instructions Configuration instructions Uninstalling the Express Viewer Chapter 7 Profile Setup How Profiles Work Adding Profiles Launching the New Profile Wizard On Demand only Launching the New Profile Wizard Software only Editing previous settings Configuration file reference Chapter 8 SDC Operations and Monitoring Operations Starting and stopping the SmartSource Data Collector Apache-based SDC IIS-based SDC SDC audit log Hit count tracking Monitoring Installation monitoring Log file monitoring Hit validation Log file name viii WebTrends Instrumentation and Configuration Guide

9 Log file rotation Logging behavior Monitoring the log file Chapter 9 Instrumenting Web Pages Overview SDC JavaScript Tags SDC JavaScript tag modifications SDC JavaScript tag placement Inserting the SDC JavaScript tag SDC VBScript Tags SDC VBScript tag modifications SDC VBScript tag placement Using HTML <META> Tags Syntax Examples ix

10 x WebTrends Instrumentation and Configuration Guide

11 Chapter 1 Introduction How to Use This Guide You will find icons for each WebTrends edition throughout the documentation. If a feature or content section applies to your edition of WebTrends, you will find the appropriate icon at the beginning of the section. For example, if you are licensed as a WebTrends On Demand, Small Business Edition user, features and content areas applicable to you include this icon: If the content does not apply to your WebTrends edition, you will see a not applicable version of your product icon: Important: Note that while your edition of WebTrends may include a feature, your ability to use it may be restricted by either licensing or your WebTrends Administrator. If you do not have access to a feature that is included in your edition, please see your WebTrends Administrator. Table 1-1. Edition Icons This icon: Represents this product: WebTrends Small Business Edition WebTrends Professional Edition WebTrends Enterprise Edition WebTrends On Demand Small Business Edition Introduction 11

12 This icon: Represents this product: WebTrends On Demand Professional Edition WebTrends On Demand Enterprise Edition Minimum System Requirements WebTrends is a Windows based product with the exception of SmartSource Data Collector (SDC) which also supports Linux and Solaris. Below are the system requirements for each edition along with SDC, and GeoTrends. WebTrends Small Business 2.0GHz or higher processor 1GB of RAM 50GB of free hard disk space (7200 RPM IDE) 10/100 Mbps network interface These requirements are based on 5 profiles, and 2 concurrent users. Note: If you choose to run GeoTrends on the same machine as WebTrends v7.0 you will need an extra 1024MB of RAM. If you are processing more than 100,000 page views a day you will need an extra 1024MB of RAM. If you run GeoTrends and have more than 100,000 pv/day, then you will need an extra 2048MB of RAM. Note: If you want to convert WebTrends reports to alternate formats, or use WebTrends SmartReports for Microsoft Excel, WebTrends also requires Office 2000 or above, and the Sun Java Runtime Environment v1.3.1_ WebTrends Installation and Configuration Guide

13 WebTrends Professional 2.0GHz or higher processor 1GB of RAM 70GB of free hard disk space (7200 RPM IDE) 10/100 Mbps network interface These requirements are based on 10 profiles, and 5 concurrent users. Note: If you choose to run GeoTrends on the same machine as WebTrends v7.0 you will need an extra 1024MB of RAM. If you are processing more than 100,000 page views a day you will need an extra 1024MB of RAM. If you run GeoTrends and have more than 100,000 pv/day, then you will need an extra 2048MB of RAM. Note: If you want to convert WebTrends reports to alternate formats, or use WebTrends SmartReports for Microsoft Excel, WebTrends also requires Office 2000 or above, and the Sun Java Runtime Environment v1.3.1_11. WebTrends Enterprise At least two machines with: Dual 2.8GHz or higher processors 2GB of RAM 200GB of free hard disk space (15,000 RPM SCSI) 10/100/1000 Mbps network interface These requirements are based on 50 profiles, and 10 concurrent users. Note: If you choose to run GeoTrends on the same machine as WebTrends v7.0 you will need an extra 1024MB of RAM. If you are processing more than 100,000 page views a day you will need an extra 1024MB of RAM. If you run GeoTrends and have more than 100,000 pv/day, then you will need an extra 2048MB of RAM. Introduction 13

14 Note: If you want to convert WebTrends reports to alternate formats, or use WebTrends SmartReports for Microsoft Excel, WebTrends also requires Office 2000 or above, and the Sun Java Runtime Environment v1.3.1_11. WebTrends Supported Operating Systems and Browsers: Windows 2000 SP3 or higher, XP SP1 or higher, or 2003 Microsoft Internet Explorer v5.5 or higher WebTrends Enterprise can scale in many different ways. Contact Professional Services for a solution that best meets your needs. WebTrends Desktop (for viewing reports) 512 MB of RAM Microsoft Internet Explorer v5.5 or higher Microsoft Office 2000 or higher (required for Report Exporter) Sun Java Runtime Environment v1.3.1_11 Large environments will require multiple machines. Additional RAM improves performance. SCSI RAID 10 (also known as RAID 0+1) is recommend for the best disk performance. SmartSource Data Collector (SDC) Hardware Windows/Linux: 1.0GHz or higher processor Solaris: Dual 400 MHz UltraSparc-II processors or better 1GB of RAM Enough disk space to store the expected contents of your log files (7200 RPM IDE) 10/100 Mbps network interface 14 WebTrends Installation and Configuration Guide

15 SDC Hardware processing more than 100,000 Daily Page Views Windows/Linux: Dual 2.0GHz or higher processors 2GB of RAM Enough disk space to store the expected contents of your log files (15,000 RPM SCSI) 10/100 Mbps network interface SDC Supported Operating Systems Windows 2000 SP3 or higher, XP SP1 or higher, 2003 Solaris 2.8 or 2.9 Red Hat Enterprise Linux AS (Advanced Server)/ES (Enterprise Server) v3.0 SDC Supported Web Servers Apache Web Server v2.0 Microsoft Internet Information Server v5.0 or v6.0 For larger sites, it may be necessary to increase the number of processors, the speed of the processors, the amount of memory, and the network bandwidth of the SDC host. You can also scale the SDC by employing one of the various load-balancing techniques. Contact Professional Services for a solution that best meets your needs. GeoTrends Hardware 1.0GHz or higher processor 1GB of RAM 30GB of free hard disk space (7200 RPM IDE) 10/100 Mbps network interface Introduction 15

16 GeoTrends Hardware processing more than 100,000 Daily Page Views Dual 2.0GHz or higher processors 2GB of RAM 30GB of free hard disk space (15,000 RPM SCSI) 10/100 Mbps network interface GeoTrends Supported Operating Systems Windows 2000 SP3 or higher, XP SP1 or higher, 2003 If you choose to run GeoTrends on the same machine as WebTrends v7.0 you will need an extra 1024MB of RAM. If you are processing more than 100,000 page views a day. Documentation There are a variety of online help resources and manuals such as this one to help you install, configure, and use WebTrends to its full potential. The online resources are detailed in the following section. See Additional resources on page 17 for a list of other manuals that are available as *.pdfs to WebTrends users. Getting help in the program WebTrends includes detailed online help to guide you through configuring and using WebTrends and WebTrends On Demand. Various information resources include Admin Console Help If you are logged into WebTrends, open this by selecting Help from the left pane of the Admin Console, then Contents & Index from the right pane. Context-sensitive help is also available from most dialogs within the progam. Select Help 16 WebTrends Installation and Configuration Guide

17 from the upper right-hand corner of the dialog to open the pertinent help page. You can then select Show Navigational Controls to open the Table of Contents, if you want to browse elsewhere in the help system. Desktop Help WebTrends users view reports, and descriptions of the elements of the reports, through the WebTrends Desktop. For help on navigating and working with the Desktop Viewer, select Help>Contents from the upper right corner of the Desktop. SmartView and Express Viewer These new WebTrends features each include a standalone help system. To open these help systems from within each program, select the Help icon from the upper right corner of these panels. Note: For SmartView and Express Viewer installation instructions, see the appropriate chapters of the WebTrends User Guide. Glossary From the WebTrends Desktop, select Help>Glossary. A detailed WebTrends glossary opens in a new browser window. Providing feedback Your comments are very important to us. Please take the time to let us know about your WebTrends experience by doing one of the following: From the Admin Console, select Help in the left pane, then Feedback from the right pane. From the WebTrends Desktop, select Help>Feedback from the upper right-hand corner of the report. The Feedback page of the WebTrends web site opens in a new browser window. There you can rate different aspects of our product and provide your comment. Additional resources In addition to this Installation and Configuration Guide, there is additional documentation available to help you maximize the effectiveness of your company s WebTrends implementation. The other major documents for this release of WebTrends include: Introduction 17

18 WebTrends User Guide This guide is intended to help non-administrators understand and use the WebTrends Desktop to view reports. This guide provides a brief overview of how WebTrends works, how to navigate the Desktop, Calendar, and Dashboards to access reports and interact with them to find the information you need. Note: Users who have no other permissions than View Reports automatically use the WebTrends Desktop (Report Viewer) instead of the Admin Console. While they can view the reports, they may not have access to any of the other controls. WebTrends recommends distributing the User Guide to these WebTrends users as a introduction to navigating WebTrends reports and report data. WebTrends Technical Reference Guide This guide serves as a technical reference for administrators who are responsible for maintaining the WebTrends software or service. WebTrends Implementation Guide A comprehensive guide for both administrators and non-administrators providing general information and best practices for a successful WebTrends implementation. Topics covered in this guide include how to collect web traffic data, how to get optimal performance with your web analysis, considerations to make when setting up your organization to run web analysis and how to configure WebTrends to give you the information you need. These manuals can be found in the Documentation directory on your WebTrends installation CD, or downloaded from our website. To download the *.pdf files from the WebTrends web site, do either of the following: If you are logged into WebTrends: 1) From the Admin Console, select Help from the left pane of the Admin Console, then select Documentation and Release Notes from the right pane. 2) The Documentation page of the WebTrends web site opens in a new browser window. Browse to the *.pdf you want to download. Paste the following URL into your browser s address bar: ptw.aspx?action=14&prodtype=rcent&version=7.0&os=win32 18 WebTrends Installation and Configuration Guide

19 Visual cues in WebTrends documentation The following table describes the typographic changes used in this and other guides to using WebTrends: This text Bold Title Case 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 dialog box (Edit Connection dialog box), Lucinda Console Source code examples, program output, or anything typed by the user. in quotes The title of a chapter or section. Note: Please see Table 1-1, Edition Icons, on page 11 for details on using the WebTrends edition logos to determine which features apply to the WebTrends edition you are using. Introduction 19

20 20 WebTrends Installation and Configuration Guide

21 Chapter 2 Installation Overview In this chapter: Licensing summary (see below) Basic Installation on page 26 which includes: Installation/WebTrends components on page 28 (including the optional GeoTrends data file) Installing WebTrends Sample Data on page 31 Installation/ SmartSource Data Collector Component on page 32 Custom Installation Distributed Architecture on page 66 Migrating Manually on page 74 Licensing This section discusses how WebTrends and WebTrends On Demand are licensed, how product keys are activated in software versions, and where you can find status information for your license. Installation 21

22 How WebTrends is licensed WebTrends is licensed according to page views collected and by the number of web servers on which you are reporting. Page views/period The number of page views WebTrends collects is determined by the edition you have licensed. For example, during a 12 month period, your edition of WebTrends may be licensed for up to 20 million page views. Web servers The scale of your web analysis is influenced by the number of web servers on which you are reporting. You are limited to reporting on the number of servers for which you are licensed. Licensing modes WebTrends runs in two modes: a trial and a full mode. Trial Each edition of WebTrends is available as a 14-day fully functioning trial for evaluation purposes. Once this trial period expires, you can convert the product to full mode when WebTrends is purchased. A product license key enables WebTrends to run. Full WebTrends runs in full mode when the product license key is entered during the installation. If you by-passed this step during the installation, you may enter a license key when you launch WebTrends. Working with license keys WebTrends requires a product license key to run. You may also have additional keys for reporting on multiple servers (server Add On keys), for product maintenance, and for server Add On maintenance. This section describes how to activate each of these keys and how to deactivate the product license. 22 WebTrends Installation and Configuration Guide

23 Activating your licensing key During the installation process, you are prompted to enter a license key. If you skip this step during installation, you are prompted to activate the key when the product is launched. Enter the WebTrends license key in the dialog box. Note: You must have internet connectivity to activate a license key. Activating add on keys As your needs grow, you may enhance WebTrends by activating keys that provide the capability to report on more web servers. Additionally, as you renew product or Add On maintenance, you update WebTrends with those keys. To activate a license key: 1. From the Admin Console, select Licensing from the left pane. 2. Select the License Keys tab. 3. Click the Add New License Key button, and the Activate License Key dialog opens. 4. Type the new key in the Enter the License Key text box, and click the Activate button. The key appears in the License Keys list, and the status is updated in the General tab. Deactivating your license key Should you need to move the WebTrends license key from one system to another, you may do so through the Licensing dialog boxes. To deactivate a key: 1. From the Admin Console, select Licensing from the left pane. 2. Select the License Keys tab. 3. Select the WebTrends license key (the first key listed). 4. Click the Delete icon. WebTrends no longer runs until a key is activated on this or another WebTrends system. Installation 23

24 Checking the license status The Licensing dialog boxes accessible from the Admin Console allow you to view the status of your WebTrends license. To access the Licensing dialogs: 1. From the Admin Console, select Licensing in the left pane. 2. Select the General tab. The Current Statistics section allows you to: Check maintenance status View whether the product maintenance is up to date in the Maintenance field. When you renew maintenance, add the new key in the License Keys tab. Check page view status and limits View the number of page views collected in the Current column. View the maximum number of page views that can be collected in the Limit column. Check web server status and limits View the number of web servers reported on in the Current column. View the total number that you may report on in the Limit column. If an additional server Add On key is acquired, enter the key in the License Keys tab. WebTrends On Demand Licensing This section describes how these products are licensed and how to check the status of the license: How WebTrends On Demand is licensed WebTrends On Demand is licensed by page views collected, number and type of profiles, number of custom reports, and volume of reports exported. Page views/period The number of page views WebTrends collects is determined by the edition of WebTrends On Demand you have licensed. For example, during a 1 year period, your edition of WebTrends may be licensed for up to 10 million page views. 24 WebTrends Installation and Configuration Guide

25 Profiles The number of profiles is determined by the edition of WebTrends On Demand. Your total number of profiles available can be distributed to your child accounts (the sub accounts within your main license). Custom reports WebTrends On Demand includes a set of pre-loaded custom reports that can be used with each profile. The edition of WebTrends On Demand that you are licensed for determines the total number of custom reports that can be distributed to your child accounts (those sub accounts with your main WebTrends account). Report exports Your edition of WebTrends On Demand determines the number of report exports that you can use each month. Once that limit is reached, you can purchase additional report exports. Checking the license status The Edit Account dialog box in the Account Console allows you to view the status of your WebTrends On Demand license. To access the Edit Account dialog box: 1. From the Account Console, select Edit Account in the left pane. Within this dialog box you can: Check profile status & limits Number of Allowed Profiles shows the number of profiles currently used, the balance available, and the total number that can be used for your account (including child accounts). Check child account status & limits (Not applicable to WebTrends Small Business or WebTrends On Demand Small Business.) Number of Allowed Child Accounts shows the number of child (subordinate) accounts currently used, the balance available, and the total number that can be used. The total number of profiles and custom reports available for the main account can be distributed to your child accounts. Installation 25

26 Check custom report status & limits Number of Allowed Custom Reports shows the number of custom reports currently used, the balance left to be used, and the total number allowed for your account. The custom reports that come pre-loaded are not included in the status details either in the total number available or the number currently used. The Account Usage dialog box in the Account Console provides a status of your page views. To access the Account Usage Summary dialog box: From the Account Console, select Account Usage> Summary in the left pane. Use this dialog to view: Page views collected so far during the current month Page views collected for the calendar year to date Pages views collected during the life of your account. Basic Installation This section covers basic installation procedures for WebTrends Small Business and WebTrends Professional. WebTrends Enterprise customers, please refer to Custom Installation Distributed Architecture on page 66. Prerequisites Please be sure to complete the following: Review the system, browser, and screen resolution requirements in Minimum System Requirements on page 12 to ensure optimum performance of WebTrends on your system. Collect any valid license keys for the product, Add-On licenses, or subscriptions. If you are also installing the WebTrends SDC component on Apache, and you have a version of Apache earlier than v2.0.48, you must remove it before installing SDC. A later version of Apache will be installed along with SDC. See Uninstall Apache on Windows on page 58 for instructions. 26 WebTrends Installation and Configuration Guide

27 Network Security You must remove any pre-existing SDC installation before installing this version. See Uninstall Windows Apache-based SDC on page 58. You can then choose from the following installation paths to install WebTrends, including the SmartSource Data Collector (SDC) and GeoTrends: Installation/WebTrends components on page 28 (this includes GeoTrends) Installing WebTrends Sample Data on page 31 Installation/ SmartSource Data Collector Component on page 32 Installing on Linux or Unix on page 39 Enabling SSL on page 51 SDC is a specialized web server. It receives HTTP requests from web clients, processes the requests, and appropriately responds to the web clients. The connections established between the clients and the server utilize TCP/IP. To make the required connection, the web server must be listening on a predetermined port associated with a known IP address. The client must have knowledge of the IP address and connectivity to the web server. Before installing SDC, consider the various issues related to the configuration of your network that enable the TCP/IP communication between the web server and web clients. Most importantly, keep in mind that the SDC server is a web server that must be available for web clients to make HTTP requests. Since external clients make requests to the SDC server, carefully consider the security of your server before installing SDC. The SDC server is a specialized web server, but the security issues related to the SDC server are common to the security issues of standard web servers. Many types of threats are related to web server operations: Unauthorized access to confidential data Data corruption Web site disruption Denial of Service (DOS) and other types of attacks Installation 27

28 One approach to a secure configuration of the SDC server is to start with a deny all model. This approach begins with all services disabled, and enables only those services necessary for the operation of the SDC server. Specifically, do not enable services (daemons) such at telnet, mail, and finger. For the SDC server, the only TCP/IP link to the Internet required is port 80. (Port 443 is required if you use secure connections via SSL.) Firewalls are often employed to protect web servers and/or internal corporate networks. You can select from many types of firewalls and numerous ways to configure them and their corresponding networks. To use a firewall (which can be composed of routers, network segments, and host computers), you need to determine the location of your SDC server relative to the firewall in your network. You can put the SDC server outside or inside of the firewall. If you place the web server outside of the firewall, it will be more susceptible to malicious attacks. However, in the event of a break-in, the attacker will have breached only the boundaries of the SDC server and not the entire corporate network. The details about the types of security breaches and the methods for preventing these attacks are beyond the scope of this document. However, it is highly recommended that you address the security concerns before exposing the SDC server to external users. Installation/WebTrends components Installing WebTrends software This section covers a typical installation of WebTrends (and the optional GeoTrends data file) for WebTrends Small Business and WebTrends Professional. For details on SDC installation, please see page 32. For details on installing the optional WebTrends samples, please see page 31. WebTrends Enterprise customers, please see Custom Installation Distributed Architecture on page 66. To install WebTrends software: 1. Insert the WebTrends software 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 28 WebTrends Installation and Configuration Guide

29 where X is the drive letter of your CD-ROM drive. 2. The installation wizard launches. Click Next to continue. 3. Before the WebTrends program files are copied to your system, you must accept the Software License Agreement. If you agree to the stated terms, select the I Accept the terms in the license agreement option, and click Next. Otherwise, click Cancel to exit the setup program without installing the software. 4. The Add Licenses dialog box opens. Enter your valid license key here to continue. (See your WebTrends administrator if you do not have a valid license key.) Note: You must have internet connectivity to activate a license key. 5. If you accepted the License Agreement, the Select Install Type window opens with the Typical option selected. (Not applicable to WebTrends Small Business) Note: See Custom Installation Distributed Architecture on page 66 if you are wanting custom installation instructions. 6. The Destination Folder window opens. The default installation folder is: X:\Program Files\WebTrends where X is the hard drive you are installing to. Complete one of the following: Click OK to accept the default installation folder. If you want to install to a different directory, click Change and browse to your preferred location. Click OK twice to save the new location and continue. 7. Select which WebTrends application you want to install: WebTrends core application GeoTrends SmartSource Data Collector 8. If you selected GeoTrends, you are prompted to do one of the following: Click Download to download the latest available version of the GeoTrends data file from the WebTrends web site. The GeoTrends data file can also be found on the product CD. Installation 29

30 9. Click Next. 10.The System Database Initialization window opens showing the host, port number, and administrator information. Enter and confirm your password, and click Next. Note: This is the password for the database, not the WebTrends User Interface. Also, if this is a subsequent WebTrends installation, only the information used during the first installation is valid here. See your WebTrends administrator if you have questions. 11.The Specify Storage locations window opens, showing the default folders for: Analysis Data Repository Report Data Repository Configuration Repository Backup Repository Note: It is important to consider your need to use shared locations before proceeding. If you add additional machines later, they will need access to these locations. For further information on subsequent installations, see Managing your distributed installation on page 74. Make any changes needed; otherwise, click Next to select the default locations and continue. 12.You are prompted to return to previous screens if you need to edit your installation choices. If you do not wish to do so, click Install. 13.TheWebTrends program files are installed to your machine. 14.Depending on your component selection in step 7, one of the following then occurs: If you have only chosen to install WebTrends and the optional GeoTrends data file, you are notified that the installation is complete. You are prompted to view and read the release notes. Click Finish to close the Installation wizard. If you also selected SmartSource Data Collector in step 7, you will need to complete additional installation steps. See Installation/ SmartSource Data Collector Component on page 32 for that list. 15.If a previously installed version of WebTrends v6.x is detected, you are asked if you would like to migrate data to your new installation. Click Yes if you want to migrate data from your previous installation to WebTrends v WebTrends Installation and Configuration Guide

31 Click No if you want to complete the installation without migrating data. You can manually migrate data later. Refer to Migrating Manually on page 74 for details. Activating licensing When you first launch WebTrends, if you did not provide a valid license key during installation, you will have to provide a valid license key or legacy serial numbers or add-on keys in order to register the product. After WebTrends accepts the license key, the Login screen will open. You can then provide your WebTrends username and password to log into WebTrends. (If you don t have this information, please see your WebTrends administrator.) Installing WebTrends Sample Data WebTrends sample data is available via a separate download. To install a WebTrends sample, complete these steps: 1. Complete either of the following: Locate the sample you want to install on your product CD. Choose from: - ZedescoODDBSample.exe - ZedescoWithLogsSample.exe - StreamingMediaSample.exe Browse to the Accessories page of the WebTrends website at: < ptw.aspx?action=10&prodtype=wrc&version=7.0> a.from the Accessories page, select Sample Downloads. b.follow the instructions to download the sample of your choice to your network. 2. Double-click Sample.exe, or use your Windows Start>Run to launch the installation wizard. Click Next. 3. Click Next to accept the license agreement. You will not be able to install the samples without doing so. Installation 31

32 4. The Custom Setup window opens. Select the samples you want to install, and click Next. If you are unfamiliar with using this type of installer, click Help for details on the different selection options you can choose from. If you are unclear how much storage space you have available, click Space. The wizard will list the available data space and requirement for each volume you have access to. (You can click through the columns to sort this data.) When you are finished reviewing this information, click OK. 5. Click Back if you want to review or change any of your installation choices before the installation begins. Otherwise, click Install. 6. You are notified when the installation is complete. Click Finish to close the wizard. Installation/ SmartSource Data Collector Component You can install SDC to run on Linux/Unix platforms (see page 39) or on Windows platforms (see the next subsection). Installing on Windows 2000/2003/XP The following subsections describe how to install the SmartSource Data Collector on Windows 2000/2003/XP platforms: Apache-based installation is described on page 32. IIS-based installation is described on page 37. Apache-based installation Uninstall previous versions 32 WebTrends Installation and Configuration Guide

33 If a version of Apache earlier than v is installed, you must remove it before installing SDC. If you are installing an SDC upgrade, you must remove any pre-existing SDC. See Uninstall Apache on Windows on page 58 and Uninstall Windows Apache-based SDC on page 58. Installing the Apache web server and SDC If you select SmartSource Data Collector during step 7 of your WebTrends installation (page 29), an Installation wizard for SmartSource Data Collector opens after the WebTrends core component installation is complete. The additional installation steps for the Apache web server and SDC are: 1. After the SmartSource Data Collector Installation wizard launches. Click Next to continue. 2. Review the NetIQ SmartSource Data Collector License Agreement. If you agree to the terms of the Agreement, select I accept the terms in the license agreement and then click Next. Otherwise, click Cancel to exit the installation. 3. Select the destination folder. To accept the default destination folder, click Next. Or To specify a location other than the default destination folder, click Change. - The Change Current Destination Folder dialog box opens. - Browse to the location you want or type the location in the Folder name text box. Click OK. Then - In the Destination Folder dialog box, click Next. The Ready to Install the Program dialog box opens. 4. Click Install to begin the installation. An Installing WebTrends SmartSource Data Collector dialog box opens and begins the installation process. A Server Type dialog box opens 5. Select Apache as your web server and click Next. Installation 33

34 6. A pop-up message opens: This product requires the use of Apache Web Server Would you like to install it now? Note: To insure ease of use and full SDC functionality, it is recommended that you uninstall and then re-install the Apache web server. If you want to install the Apache web server, click Yes. Go to step 7. If you already have the same version of Apache that is on this CD installed on your computer, click No and skip the Apache portion of the install. Go to step The Apache httpd server installation wizard Welcome page opens. Click Next. 8. Review the Apache Software License Agreement. If you agree to the terms of the Agreement, select I accept the terms in the license agreement, then click Next. Or If you do not accept the terms of the Agreement, click Cancel to exit the installation. 9. Review the Read This First message and click Next. 10.The Server Information dialog box opens. Enter the Server Information and select the Startup Option: Network domain The network domain is the domain that the SDC server operates. Server name The server name is your host name or IP address. The server name you enter is used to modify the httpd.conf file. The following is a description of the ServerName directive found in the httpd.conf file. Review these comments from the httpd.conf file before you enter your server name. # ServerName allows you to set a host name which is # sent back to clients for your server if it's # different than the one the program would get i.e. use # "www" instead of the host's real name). # # Note: You cannot just invent host names and hope they # work. The name you define here must be a valid DNS 34 WebTrends Installation and Configuration Guide

35 # name for your host. If you don't understand this, ask # your network administrator. # # If your host doesn't have a registered DNS name, # enter its IP address here. You will have to access it # by its address (e.g., /) anyway, # and this will make redirections work in a sensible # way. # # is the TCP/IP local loop-back address, # often named localhost. Your machine always knows # itself by this address. If you use Apache strictly # for local testing and development, you may use # as the server name. Administrator s address The Administrator's Address is the address where problems with the server are to be ed. Select one of the following to install Apache HTTP Server 2.0 programs and shortcuts For All Users, on Port 80, as a Service Recommended. (This default setting automatically issues commands to start Apache each time that you want to use it.) Or Only for the Current User, on Port 8080, when started manually. (This means that you must issue commands to start Apache each time that you want to use it.) Then Click Next. The Setup Type dialog opens. 11.Select the type of installation: To install all of the Apache software on your hard drive, select Typical and click Next. The Destination Folder dialog opens. Go to step 12. Or To install only one or more features, select Custom and click Next. The Custom Setup dialog opens. Go to step 13. Installation 35

36 12.The Destination Folder lets you accept a default location for the Apache folder or specify another location. To accept the current destination folder, click Next. The Ready to Install dialog box opens. Go to step 14. Or Click Change to specify a different destination folder. The Change Current Destination Folder dialog box opens. Browse to the new folder or type the folder name in the Folder name text box. Click OK. Then in the Destination Folder dialog box, click Next. The Ready to Install dialog box opens. Go to step To set up your custom installation, select the Apache components to install by clicking on the icons in the component tree and choosing a component installation option. Click Space to see a list of your drives, drive sizes, available space for each drive, and the required space for the selected features. Select the destination folder. - Accept the current destination folder and click Next. Or - Click Change to specify a different destination folder. The Change Current Destination Folder dialog box opens. Browse to the new folder or type the folder name in the Folder name text box. Click OK and then in the Custom Setup dialog box, click Next. The Ready to Install dialog box opens. 14.Click Install. The Apache program begins to install. Note: If a web server or another application is already running on port 80 or another port that you specified for SDC, then you will receive an error message that states: Only one usage of each socket address <protocol/network address/port> is normally permitted. : make_sock: could not bind to address :80 no listening sockets available, shutting down. Unable to open logs. Open your management console (On your desktop right-click My Computer icon > Manage > Services and Applications > Internet Information Services) and stop the server or application that is running on port WebTrends Installation and Configuration Guide

37 15.The Installation Wizard Completed dialog box opens, indicating that Apache is installed. Click Finish. 16.To complete the SDC configuration, your web server must be stopped and restarted. Click Yes to do so at this time. Click No to postpone this step and the configuration. 17.Click Finish. The SDC installation is complete. IIS-based installation Uninstall previous version of IIS-based SDC Before installing an IIS-based SDC upgrade, you must remove any previous version. See Uninstall Windows IIS-based SDC on page 60. Install IIS-based SDC Note: Prerequisite You must install a supported version of IIS before installing the IISbased SDC software. SDC Supported Web Servers on page 15 for more information on compatible versions of IIS software. Complete the following steps: 1. Insert the WebTrends 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, click Start > Run to open the Run dialog box, and type d:\setup where d: is the letter of your CD-ROM drive. 2. Review the contents of the InstallShield Wizard Welcome dialog box and click Next to open the License Agreement dialog box. 3. Review the NetIQ SmartSource Data Collector License Agreement. If you agree to the terms of the Agreement, select I accept the terms in the license agreement and then click Next. Otherwise, click Cancel to exit the installation. Note: Click Cancel at any time to exit the installation. 4. Select the destination folder. To accept the default destination folder, click Next. Installation 37

38 Or To specify a location other than the default destination folder, click Change. - The Change Current Destination Folder opens. - Browse to the location you want or type the location in the Folder name text box. Click OK. Then - In the Destination Folder dialog box, click Next. The Read to Install the Program dialog box opens. 5. Click Install to begin the installation. An Installing WebTrends SmartSource Data Collector dialog box opens and begins the installation process. The Server Type dialog box opens. 6. Select Internet Information Server (IIS) and click Next. The InstallShield Wizard Completed dialog box opens. 7. Click Finish. The SDC installation is complete. Start SDC The installation program creates a fully configured web site named SmartSource Data Collector. For more information on server configuration, refer to IIS Configuration on page 94, and for a complete reference on the dcs.cfg file, Configuration Reference on page 77. You can restart IIS to activate SDC by entering the following commands at a command prompt: net stop iisadmin /y net start w3svc The SDC server is now configured and listening for instrumented hits on Port 80. If you want to enable secure communication from web clients to SDC using the Secure Sockets Layer protocol, refer to Enabling SSL on page WebTrends Installation and Configuration Guide

39 Installing on Linux or Unix The following subsections describe installing the SmartSource Data Collector on the Linux platform (Red Hat Enterprise Linux only) or Unix platform (Solaris): Apache-based installation Uninstall previous versions Before installing the Apache web server shipped with SDC, remove any previous installation of the Apache web server. See Uninstall Apache on Linux on page 60 and Uninstall Apache on Unix on page 61. Before installing an Apache-based SDC upgrade you must remove any previous version. See Uninstall Unix Apache-based SDC (Solaris only) on page 61. SDC and Apache installation Complete the following steps: 1. Switch user to root. su root 2. Make a temporary directory. mkdir <tempdirectoryname> 3. Change to the temporary directory. cd <tempdirectoryname> 4. Copy the SDC distribution source to the temporary directory. Linux cp <source path>/sdc linux.i586.tar.gz. Unix cp <source path>/sdc-solaris.sparc.tar.gz. 5. Uncompress the source. Linux tar -zxvf sdc linux.i586.tar.gz Unix gzip -cd sdc-solaris.sparc.tar.gz tar xvf - Installation 39

40 6. Change to the directory containing the SDC software. cd sdc-version number 7. Run installation script../install.sdc 8. The Welcome Panel introduces the installation. Note: The installation script prompts for all necessary information. Press Ctrl-C at any time to interrupt the installation script. At each script prompt, default values are enclosed in square brackets. Press Enter to accept default values or type an alternate value and press Enter. For prompts requiring a Yes or No response, the default value is capitalized in square brackets. For example, [Yn] is a yes default and [yn] is a no default. Press Enter to accept the default, or type an n or a y, and press Enter. For questions requiring a numeric response, type the number followed by Enter. The default value is enclosed in square brackets. For example, [2] means menu item 2 is the default. Press Enter to accept default values or type an alternate value and press Enter. Press Enter to view the WebTrends license agreement. 9. Read the license agreement carefully. Press the SpaceBar to scroll the agreement. Type q to finish viewing the agreement. 10.To accept the agreement, type accept and press Enter. Any other response implies non-acceptance of the agreement and cancels the installation. 11.Specify the installation directory. Press Enter to accept the default directory (/usr/local/webtrends/sdc). Or Type the directory where SDC should be installed and press Enter. 12.Confirm the directory. Press Enter to confirm the directory. 40 WebTrends Installation and Configuration Guide

41 Or Type n followed by Enter to change it. 13.Next, you are prompted for your license key. Immediately following the colon prompt, type the license key. Press Enter. 14.Confirm the license key. Press Enter to confirm the license key. Or Type n followed by Enter to change it. If you have more than one license key, repeat the previous two steps for each license key. You can add more license keys later by running wtlicman from the command line. 15.End license key input by pressing Enter at the colon prompt. Important: At this point, if you do not have a valid internet connection, you will receive a Manual Activation Text, which you must send to NetIQ s licensing servers. You can continue to install the SDC software, but before you can use it you will be instructed to follow the steps listed in <SDC_installation_directory>/bin/manual_activation.txt. These steps describe how to manually license the product. 16.Press Enter again to advance to the next prompt. 17.(Solaris only) Specify the web server that you are using by typing the number corresponding to Apache, followed by Enter. Apache-based cookie server configuration Complete the following steps: 1. Enable the SDC-based cookie server? Press Enter (recommended) to accept the Yes default. Or Type n followed by Enter and go to Apache-based log file configuration on page 44. Installation 41

42 The enabled setting in the SDC configuration file is set to true or false based on your response to this prompt. 2. If you have a previous version of a WebTrends cookie plug-in AND are installing SDC on the same domain, you may continue to use the same cookie name and format. (This is not a likely scenario.) To use an existing WebTrends cookie, type y and press Enter. To accept the default and create a new cookie, press Enter. If you chose to use an existing WebTrends cookie, the cookieversion setting in the SDC configuration file is set to 1; otherwise it is set to 2 (which enables cookie validation). 3. Enter the cookie name. Press Enter to accept the default name (WEBTRENDS_ID). Or Type a new or an existing name for the WebTrends cookie and press Enter. The value entered is assigned to the cookiename setting in the SDC configuration file. 4. Validate incoming cookies? Press Enter to accept the default (Yes). Or Type n followed by Enter. Go to 7. Validation checks to make sure that the cookie has not been tampered with by a web client. The validatecookie setting in the SDC configuration file is set to true or false based on your answer to this prompt. 5. Specify the cookie validation private key (Magic Code). Press Enter to accept the default Magic Code. Or Type an alternate Magic Code and press Enter. 42 WebTrends Installation and Configuration Guide

43 This setting is used as a private key when creating a message authentication check for the cookie values. It is recommended to create a Magic Code that consists of numbers and letters and is 6-10 bytes long. The value entered is assigned to the magiccode setting in the SDC configuration file. 6. Issue a new cookie when an invalid cookie is detected? Press Enter to accept the default (Yes). Or Type n followed by Enter. Reissuing cookies involves logging the existence of the invalid cookie in the SDC log file and adding a Set-Cookie header to the HTTP response. The reissuebadcookie setting in the SDC configuration file is set to true or false based on your response to this prompt. 7. Specify the type of cookie expiration by typing the corresponding number followed by Enter. The default is to generate cookies that expire after ten years. Expire after a given amount of time generates a cookie that expires at a specified period of time after the cookie is created. Specify the number of seconds after which the cookie is to expire and press Enter. Or press Enter to accept the default cookie expiration ( seconds = 10 years). The number entered is assigned to the expirationseconds setting in the SDC configuration file. Expire on a given date generates a cookie that expires on a certain date. Specify the date on which the cookie will expire and press Enter. Or press Enter to accept the default date (January 1, 2010). Enter the date using the MM-DD-YY format. The date entered is assigned to the expirationdate setting in the SDC configuration file. None generates session-only cookies that do not get saved to the client's disk. The expirationtype setting in the SDC configuration file is assigned to either seconds, date, or none based on your answer to this prompt. 8. Specify the path of the subset of URLs in a web site for which a cookie is valid. Installation 43

44 Press Enter to accept the default path (/). Or Type the path and press Enter. The path entered is assigned to the path setting in the SDC configuration file. 9. Transmit cookie over secure connections only? Press Enter to accept the default (No). Or Type y followed by Enter. The secure setting in the SDC configuration file is set to true or false based on your answer to this prompt. 10.Specify if web clients should send HTTP requests to a targeted domain. Press Enter to accept the default (blank domain). Blank domain uses the domain from which the client issued the request. This is almost always the desired result. Or Type the domain and press Enter. The domain entered is assigned to the domain setting in the SDC configuration file. 11.Enable first-time cookie detection? Press Enter to accept the default (Yes). Or Type n followed by Enter. The track first-time cookies setting in the SDC configuration file is set to true or false based on your answer to this prompt. Apache-based log file configuration Complete the following steps: 1. Specify a directory where SDC-enabled server should store log files. Press Enter to accept the default directory: /usr/local/webtrends/sdc/weblog. 44 WebTrends Installation and Configuration Guide

45 Or Type the directory and press Enter. The directory entered is used as part of the TransferLog directive in the Apache configuration file. 2. Specify the log rotation period. You can rotate log files daily, weekly, in a number of hours, or hourly. In addition, in the next step, you can rotate log files when they reach a certain size. See Log File Monitoring on page 194 for a discussion of log file rotation. Rotate by minutes specifies the number of minutes to elapse between a log file rotation. Press Enter to accept the default (30 minutes), or type a valid number and press Enter. (Accepted values are 1, 2, 3, 4, 5, 5, 10, 12, 15, 20, and 30). This setting is assigned to the minutesinterval setting in the SDC configuration file. Rotate by hours specifies the number of hours to elapse between log file rotation. - Press Enter to accept the default (1 hour). Or type a number (1, 2, 4, 6, 8, or 12) followed by Enter. - The specified number is assigned to the hoursinterval setting in the SDC configuration file. Rotate Daily is the default period. Press Enter to accept. Rotate weekly specifies the day of the week to start rotation. Press Enter to accept the default (Sunday). Or type the number corresponding to the day that you prefer and press Enter. The weekstart setting in the SDC configuration file is assigned to either Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, or Sunday based on your response to this prompt. The rotationperiod setting in the SDC configuration file is assigned to daily, weekly, hourly, or minutes based on your response to this prompt. 3. Rotate log files when they reach a given size? Select one: Press Enter to accept the default (Yes). Specify the maximum log file size by typing a number (of Kbytes) and press Enter, or press Enter to accept the default (2,000,000 Kbytes). Installation 45

46 The number entered is assigned to the maxlogfilesize setting in the SDC configuration file. Or To not limit the size of log files, type n followed by Enter. The limitbysize setting in the SDC configuration file will be set to true or false based on your response to this prompt. 4. Rotate log files based on GMT? Press Enter to accept the default (local time). Or Type y followed by Enter. The gmtrotation setting in the SDC configuration file will be set to true or false based on your response to this prompt. 5. Specify a log file prefix. Press Enter to accept the default prefix (sdc). Or Type a log file prefix followed by Enter. The log file prefix entered is assigned to the logfileprefix setting in the SDC configuration file. 6. Log hits containing invalid cookies? Press Enter to accept the default (no invalid hit logging). Or Type y followed by Enter. The loginvalidhits setting in the SDC configuration file will be set to true or false based on your response to this prompt. 7. Issue a P3P (Policy for Privacy Preferences) header? Press Enter to accept the default (no P3P header). Or Type y followed by Enter. 46 WebTrends Installation and Configuration Guide

47 - Specify the P3P header in the event that none was received via the SDC tag. - Press Enter to Accept the Default, or type the P3P header and press Enter. - The P3P header entered is assigned to the p3p setting in the SDC configuration file. The issuep3p setting in the SDC configuration file will be set to true or false based on your response to this prompt. See P3P and SDC on page 207 for more information related to P3P and how it impacts SDC. 8. Specify the default log elements to write to a log file. Press Enter to accept the default log elements as displayed. Or Enable or disable log elements: - Type the number corresponding to a log element followed by y (to enable) or n (to disable). - Press Enter when you are done. The settings in the logfields section will be set to true or false based on your response to this prompt. 9. Determine where to write errors and warning messages. Press Enter to accept the default (write to both the SDC Audit Log and Syslog). Type 1 and press Enter to write to the SDC Audit Log only. Type 2 and press Enter to write to syslog only. Go to 11. Your selection is assigned to the type setting in the SDC configuration file. 10.If you are writing errors and/or warnings to SDC Audit Log: Press Enter to accept the default (write both errors and warnings). Or Type 1 and press Enter to write errors only. Go to 12. Your selection is assigned to the debuglevel setting in the SDC configuration file. 11.If you are writing errors and/or warnings to Syslog: Press Enter to accept the default (write errors only). Go to 15. Installation 47

48 Or Type 2 and press Enter to write both errors and warnings. Your selection is assigned to the system debuglevel setting in the SDC configuration file. 12.Limit the size of the SDC Audit Log? Press Enter to accept the default (No). That is, the Audit Log can grow unbounded. Go to 15. Or Type y and press Enter to limit the size. Your selection is assigned to the auditlimitbysize setting in the SDC configuration file. 13.Specify the maximum SDC Audit Log file size in Kbytes and press Enter or accept the default size. This entry is assigned to the auditmaxsize setting in the SDC configuration file. 14.Specify the amount (in Kbytes) of the SDC Audit Log file to retain after truncation and press Enter or accept the default size. This entry is assigned to the audittrimsize setting in the SDC configuration file. 15.Accept or change the SDC configuration parameters as listed? Press Enter to accept the SDC configuration parameters. Or Type n followed by Enter to change the SDC configuration parameters. Apache web server configuration (Solaris only) Complete the following steps: 1. Install the supported version of Apache? Press Enter (recommended) to accept the default (Yes). Or Type n followed by Enter. If you chose to not install Apache, go to WebTrends Installation and Configuration Guide

49 2. Specify the installation directory for Apache. Press Enter to accept the default directory (/usr/local/apache). Or Type the directory and press Enter. 3. Confirm the Apache installation directory. Press Enter to confirm the directory. Or Type n followed by Enter to change it. 4. Press Enter to view the Apache license agreement. 5. Read the license agreement carefully. Press the SpaceBar to scroll the agreement. Type q to finish viewing the agreement. 6. To accept the agreement, type accept and press Enter. Any other response implies non-acceptance of the agreement and cancels the installation of Apache. 7. Specify the user name. Press Enter to accept the default user (nobody). Or Type a user name followed by Enter. The user entered is assigned to the User directive in the Apache configuration file. 8. Specify the group. Press Enter to accept the default group (nobody). Or Type the group followed by Enter. The group entered is assigned to the Group directive in the Apache configuration file. 9. Specify the address that the server uses to send error messages. Type the address and press Enter. Installation 49

50 Or Press Enter to accept the default The address entered is assigned to the ServerAdmin directive in the Apache configuration file. 10.Specify the port number. Press Enter to accept the default port number. Or Type the port number followed by Enter. 11.Specify the server name. Press Enter to accept the default host name. Or Type the name of the server followed by Enter. The name entered is assigned to the ServerName directive in the Apache configuration file. The following is a description of the ServerName directive found in the httpd.conf file. # ServerName allows you to set a host name which is # sent back to clients for your server if it's # different than the one the program would get i.e. use # "www" instead of the host's real name). # # Note: You cannot just invent host names and hope they # work. The name you define here must be a valid DNS # name for your host. If you don't understand this, ask # your network administrator. # # If your host doesn't have a registered DNS name, # enter its IP address here. You will have to access it # by its address (e.g., /) anyway, # and this will make redirections work in a sensible # way. # # is the TCP/IP local loop-back address, # often named localhost. Your machine always knows # itself by this address. If you use Apache strictly #for local testing and development, you may use # as the server name. 12.Start automatically at boot time? 50 WebTrends Installation and Configuration Guide

51 Press Enter to accept the default and configure SDC so that it starts up automatically at boot time. This copies a start up script into the /etc/rc.d/init.d directory (Linux) or the /etc/init.d directory (Unix). Or Type n followed by Enter to start SDC manually. 13.Accept the Apache parameters? Press Enter to accept the Apache configuration parameters as listed. Or Type n followed by Enter to change one or more of the parameters. The installation script unpacks files, configures SDC, configures the web server, and starts the web server. The SDC server is configured and listening for instrumented hits on Port 80. Press Enter to advance to the next screen. 14.Read the release notes? Press Enter if you want to read the SDC release notes. Or Type n followed by Enter to ignore them. If you want to enable secure communication from web clients to the SDC using the Secure Sockets Layer protocol, refer to the next section Enabling SSL. Enabling SSL Sensitive information is often transmitted between web clients and web servers. This information is typically protected by sending the data in an encrypted form and subsequently decrypting that data on the receiving side. The Secure Sockets Layer (SSL) protocol provides several features that enable secure transmission of web traffic. These features include data encryption, server authentication, and message integrity. Installation 51

52 As a specialized web server that seamlessly communicates with web clients, the SDC receives hits from instrumented web pages. A web page is instrumented by deploying a SDC tag to it. SDC tags are JavaScript. The JavaScript tags generate inline image requests that are directed at the SDC. These requests contain information related to the original content-side hit. For more information about the tags, see Instrumenting Web Pages on page 151. If the original inline request generated by the JavaScript tag to the content web server utilizes HTTPS protocol, it may need to communicate with the SDC in a secure fashion. This maintains the privacy of the sensitive information and also prevents web browser warnings related to sending secure data over a non-secure connection. To enable secure communication from web clients to the SDC using SSL, configure and enable SSL. SSL for Apache-based SDC SDC uses the Apache module mod_ssl to implement strong cryptography using the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols. This module relies on the OpenSSL toolkit to provide the cryptography engine. The following procedures describe how to configure and enable SSL with an SDC-enabled Apache web server. Additional information about mod_ssl can be found here: and here: Additional information about OpenSSL can be found here: Windows SSL support is not provided with Apache-based SDC on the Windows platform. Linux It is assumed that you have successfully installed SDC and that you are currently logged in as root. It is also assumed that you have installed the following RedHat packages: httpd, mod_ssl, and openssl. 52 WebTrends Installation and Configuration Guide

53 The following steps are described: Modify httpd.conf. Remove the invalid private key and signed certificate. Generate a private key. Generate a certificate signing request. Submit the certificate signing request to a Certificate Authority. Install the signed certificate. Test the installation. Modify httpd.conf 1. Use vi (or another text editor) to modify the Apache configuration file. vi /etc/httpd/conf/httpd.conf 2. Add an Include directive for the mod_ssl configuration file. Search for Load config files, and add the following line (in bold print) to include the SSL configuration file: # # Load config files from the config directory "/etc/httpd/conf.d". # #Include conf.d/*.conf Include conf.d/ssl.conf 3. Save the file and exit the editor. Remove the invalid private key and signed certificate 4. If you installed your secure server from the RPM package provided by RedHat, a random key and test certificate are generated and put into the appropriate directories. Before you begin using your server, you must generate your own key, and obtain a signed certificate which correctly identifies your server. 5. Change directory to /etc/httpd/conf. 6. Remove the temporary key and certificate that were generated during the installation. rm ssl.key/server.key rm ssl.crt/server.crt Installation 53

54 Generate a private key The next steps will create the file that contains your private key. This file is named /etc/httpd/conf/ssl.key/server.key. 7. Change the directory to /usr/share/ssl/certs. 8. Generate a private key. make genkey 9. Enter a pass phrase. Re-type the pass phrase to verify that it is correct. Save this pass phrase in a secure location. You'll need it each time you start your secure server. Install the signed certificate. Test the installation. Generate a private key Use the following steps to create the file that contains your private key. This file is named <Apache_Install_Dir>/conf/ssl.key/server.key. 1. Change directory to <SDC_Install_Dir>/util/webserver/apache. 2. Generate a private key. /usr/ccs/bin/make genkey 3. Enter a pass phrase. Re-type the pass phrase to verify that it is correct. Save this pass phrase in a secure location. You'll need it each time you start your secure server. Generate a certificate signing request The next steps will create a file that contains your certificate signing request. This file is named <Apache_Install_Dir>/conf/ssl.csr/server.csr. Once created, you will send this file to a Certificate Authority. 4. Change directory to <SDC_Install_Dir>/util/webserver/apache. 5. Generate a certificate. /usr/ccs/bin/make certreq 6. Enter the pass phrase you chose when you generated your key. 54 WebTrends Installation and Configuration Guide

55 7. You are then asked for several pieces of information. The default answers appear in brackets [] immediately after each request for input. For example, You are about to be asked to enter information that will be incorporated into your certificate request. What you are about to enter is what is called a Distinguished Name or a DN. There are quite a few fields but you can leave some blank For some fields there will be a default value, If you enter '.', the field will be left blank Country Name (2 letter code) [AU]: US State or Province Name (full name) [Some-State]: Oregon Locality Name (eg, city) []: Portland Organization Name (eg, company) [Internet Widgits Pty Ltd]:NetIQ Organizational Unit Name (eg, section) []:Engineering Common Name (eg, YOUR name) []:admin Address []:[email protected] Please enter the following 'extra' attributes to be sent with your certificate request A challenge password []: An optional company name []: Submit the certificate signing request to a Certificate Authority 8. Send the file <Apache_Install_Dir>/conf/ssl.csr/server.csr to a Certificate Authority for signing. Install the signed certificate 9. When you get a response (signed certificate) from the Certificate Authority, save the file they give you as <Apache_Install_Dir>/conf/ssl.crt/server.crt. If not present, create a directory for the signed certificate: mkdir <Apache_Install_Dir>/conf/ssl.crt Be sure to keep a backup of this file. Test the installation 10.Stop Apache. <Apache_Install_Dir>/bin/apachectl stop Installation 55

56 11.Start secure Apache. <Apache_Install_Dir>/bin/apachectl startssl 12.Enter the pass phrase you chose when you generated your key. Ok: Pass Phrase Dialog successful. 13.Point your web browser to the following URL: If you are using a signed certificate from a well-known Certificate Authority, your browser automatically accepts the certificate (without prompting you for input) and creates the secure connection. Once your browser accepts the certificate, your secure server returns the.gif file. 14.Inspect the SDC-generated log file and verify that it contains the hit. By default, the log file resides in <DCS_Install_Dir>/weblog. Removing pass phrase prompt at startup The pass phrase prompt pops up at startup and every re-start because the private key inside your server.key file is stored in encrypted format for security reasons. The pass-phrase is needed to be able to read and parse this file. When you can be sure that your server is secure enough you perform the following steps: Linux 1. Change directory to /etc/httpd/conf/ssl.key. 2. Backup the server.key file. cp server.key server.key.orig 3. Remove encryption from the private key file. openssl rsa -in server.key.orig -out server.key Enter pass phrase for server.key.orig: 56 WebTrends Installation and Configuration Guide

57 4. Enter the pass phrase you chose when you generated your key. writing RSA key Solaris 1. Change directory to <Apache_Install_Dir>/conf/ssl.key. 2. Backup the server.key file. cp server.key server.key.orig 3. Remove encryption from the private key file. /usr/local/ssl/bin/openssl rsa -in server.key.orig -out server.key Enter pass phrase for server.key.orig: IIS-based SDC For IIS-based SDC, SSL is provided by the IIS web server obtained from Microsoft. Refer to your IIS web server documentation for details on configuring and enabling SSL communication for IIS. Uninstalling the SmartSource Data Collector Before installing a SDC upgrade, you must remove any previous installation of SDC. Find the instructions for: Uninstalling on Windows 2000/2003/XP on page 58 Uninstall Apache on Windows on page 58 Uninstall Windows Apache-based SDC on page 58 Uninstall Windows IIS-based SDC on page 60 Uninstalling on Linux or Unix on page 60 Uninstall Apache on Linux on page 60 Uninstall Apache on Unix on page 61 Uninstall Unix Apache-based SDC (Solaris only) on page 61 Installation 57

58 Uninstalling on Windows 2000/2003/XP Uninstall Apache on Windows Complete the following steps: 1. Stop Apache-based SDC. Open a DOS Command Prompt window. Start > Programs > Accessories > Command Prompt Type the following command: net stop apache 2. Open the Control Panel: Start > Settings > Control Panel 3. Click Add/Remove Programs. 4. Under Currently installed programs, select the Apache httpd Server and click Remove. 5. Click Yes in the confirmation pop-up. 6. Close the Add/Remove Programs window. Click Close. 7. If you plan to install the SDC-provided Apache in the same directory as the previous installation of Apache, you may have to remove the Apache folder with the conf and logs subfolders to completely remove Apache. Uninstall Windows Apache-based SDC Complete the following steps: 1. If you want to preserve your SDC settings, record the settings found in the SDC configuration file <SDC Install Directory>\cfg\dcs.cfg. Note that if you are using cookieversion=2, you may want to preserve your cookie validation private key (MagicCode). 2. Open the Control Panel. Start > Settings > Control Panel 3. Click Add/Remove Programs. 58 WebTrends Installation and Configuration Guide

59 4. Under Currently installed programs, select WebTrends SmartSource Data Collector and click Remove. 5. Click Yes in the confirmation dialog box. 6. Close the Add/Remove Programs window. Installation 59

60 Uninstall Windows IIS-based SDC Complete the following steps: 1. If you want to preserve your SDC settings, record the settings found inside of the SDC configuration file <SDC Install Directory>\cfg\dcs.cfg. Most notably, if you are using cookieversion=2, you may want to preserve your cookie validation private key (MagicCode). 2. Open the Control Panel. Start > Settings > Control Panel 3. Click Add/Remove Programs. 4. Under Currently installed programs, select the WebTrends SmartSource Data Collector and click the Remove button. 5. When prompted to remove the WebTrends SmartSource Data Collector, click Yes. 6. Close the Add/Remove Programs window. Uninstalling on Linux or Unix Uninstall Apache on Linux Red Hat provides an Apache web server as an installation option. If the Red Hatprovided Apache was installed, it can be removed using the following steps: 1. Switch user to root. su root 2. Remove the Apache package and all of its dependencies. The dependencies must be removed before the Apache package. To determine the packages dependent on Apache, issue the following command: rpm q whatrequires webserver For each package listed, issue the following command: rpm e <package> 60 WebTrends Installation and Configuration Guide

61 Finally, issue the command to remove Apache: rpm e httpd Specifically, make sure that the /etc/logrotate.d/httpd and /etc/rc.d/init.d/httpd scripts are removed. Uninstall Apache on Unix Solaris 8 provides an Apache web server as an installation option. 1. Switch user to root: su root 2. If the Solaris-provided Apache web server was installed, remove it. pkgrm SUNWapchd SUNWapchr SUNWapchu Specifically, make sure that the /etc/init.d/apache and /etc/apache/httpd.conf scripts are removed. Uninstall Unix Apache-based SDC (Solaris only) Complete the following steps: 1. Switch user to root. su root 2. Stop the Apache-based SDC. <Apache Install Directory>/bin/apachectl stop 3. Remove or rename the Apache installation. To remove: rm -rf <Apache Install Directory> To rename: mv <Apache Install Directory> <New Directory> 4. If you created SDC startup scripts and placed them in the /etc directory, remove the startup scripts now. This assumes a run-level of 3. Installation 61

62 Solaris rm /etc/rc3.d/s50apache /etc/init.d/apache 5. If you want to preserve your SDC settings, record the settings found inside of the SDC configuration file <SDC Install Directory>/cfg/dcs.cfg. Note that if you are using cookieversion=2, you may want to preserve your cookie validation private key (MagicCode). 6. Remove or rename the SDC installation. To remove: rm -rf <SDC Install Directory> To rename: mv <SDC Install Directory> <New Directory> Upgrading Apache Periodically, the Apache Software Foundation ( releases new versions of Apache 2.0. Typically, these releases are minor ones that fix bugs or respond to security vulnerabilities. As long as the new Apache 2.0 release maintains binary compatibility, you are free to upgrade to it. Upgrade steps The method used to upgrade Apache 2.0 varies according to the operating system you are using. It is recommended to back up your existing Apache installation before upgrading. The following subsections describe how to upgrade for each supported operating system. Windows 2000/2003/XP 1. Download Apache 2.0 Win32 Binary upgrade from 2. Stop Apache. net stop apache2 3. Uninstall existing Apache 2.0. Settings -> Control Panel -> Add/Remove Programs -> Apache HTTP Server 2.0.x 62 WebTrends Installation and Configuration Guide

63 4. Install Apache 2.0 upgrade into the same directory as the previous install. Consequently, your <Apache Install Dir>\logs and <Apache Install Dir>\conf directories are preserved. Start -> Run -> apache_2.0.<x>-win32-x86-no_ssl.msi where <x> specifies the 2-digit minor version. Red Hat Enterprise Linux 3 1. Log in as root. 2. Download Updated Apache Packages RPM from 3. Stop Apache. /usr/sbin/apachectl stop 4. Save Apache configuration file. cp /etc/httpd/conf/httpd.conf /etc/httpd/conf/httpd.conf.sav 5. Install Apache 2.0 upgrade. rpm -Fvh httpd-2.0.*.rpm 6. Restore Apache conf file. cp /etc/httpd/httpd.conf.sav /etc/httpd/conf/httpd.conf 7. Start Apache. Solaris 8/9 /usr/sbin/apachectl start Note that these steps require you to build a binary Apache distribution from source. You must have a GNU development environment setup before proceeding (see If you intend to run with SSL enabled, you must also build OpenSSL from source. Build OpenSSL 1. If you intend to run Apache with SSL enabled, then download the latest OpenSSL distribution tarball (see and unpack it. Otherwise, proceed to Build Apache section below. gzip -cd openssl-*.tar.gz tar xvf- Installation 63

64 2. Change to top level directory. cd openssl-* 3. Configure OpenSSL./config shared no-idea no-rc5 no-threads -fpic 4. Build OpenSSL make depend make 5. Install OpenSSL. The default installation directory is /usr/local/ssl. su make install Build Apache 1. Download Apache 2.0 Unix Source (see and unpack it. gzip -cd httpd-2.0.*.tar.gz tar xvf - 2. Change to top level directory cd http-2.0.* 3. Edit build/binbuild.sh and change CONFIGPARAM variable to look like this (changes in bold). CONFIGPARAM="--enable-layout=Apache \ --prefix=$build_dir \ --enable-mods-shared=all \ --with-expat=$apfulldir/srclib/apr-util/xml/expat \ --enable-static-support \ --enable-ssl=shared \ --with-ssl=/usr/local/ssl \ --enable-so" 4. Build new Apache binary distribution../build/binbuild.sh 5. Stop Apache. <Apache_Install_Dir>/bin/apachectl stop 64 WebTrends Installation and Configuration Guide

65 6. Install Apache binary distribution into a different directory. su./install-bindist.sh <New_Apache_Install_Dir> 7. Restore configuration file. cp <Apache_Install_Dir>/conf/httpd.conf <New_Apache_Install_Dir>/conf 8. Restore environment variable script. cp <Apache_Install_Dir>/bin/envvars <New_Apache_Install_Dir>/ bin 9. If present, edit /etc/init.d/httpd and update paths to Apache binary and Apache environment variable script. # the path to your httpd binary, including options if necessary HTTPD="<New_Apache_Install_Dir>/bin/httpd -d <New_Apache_Install_Dir>" # # pick up any necessary environment variables if test -f <New_Apache_Install_Dir>/bin/envvars; then. <New_Apache_Install_Dir>/bin/envvars fi # 10.Start Apache <New_Apache_Install_Dir>/bin/apachectl Binary Compatibility start If you attempt to use SDC with a version of Apache 2.0 that is incompatible, you will see a message similar to the following in your Apache error log at startup: httpd: module "inc/apachelogserver.h" is not compatible with this version of Apache. Please contact the vendor for the correct version. If you get this error message, contact NetIQ for a compatible version of SDC. Installation 65

66 Custom Installation Distributed Architecture Introduction One of the advanced features of WebTrends Enterprise is the ability to install the software on several different machines. You might want to do this if you need to scale your WebTrends environment because it has become very complex. Scaling WebTrends software will keep your environment robust and flexible. Also, you may need to distribute the WebTrends software over a variety of machines, if your organization s web site experiences substantial traffic. For example, you may need to assign your machines as follows: Two machine for analysis One machine for the UI Two machines for SmartSource Data Collector (SDC). One machine for GeoTrends One machine for the main application, system database and file storage (backups and archiving). In total, this setup involves seven interconnected machines, as shown in Figure WebTrends Installation and Configuration Guide

67 Figure 2-1. Distributed Architecture overview This configuration of machines and software can be represented in column format that stresses function, as shown in Figure 2-2. Installation 67

68 Figure 2-2. Distributed Architecture function overview Of course, this illustration presents just one of many ways that an organization might want to distribute WebTrends software over a number of machines. Organizations that want to use distributed architecture will need to consider their resources in terms of machines and people to make the distributed architecture work fulfill their needs. General guidelines Here are some guidelines to consider. General areas of WebTrends software that can be installed on separate boxes if needed for scaling purposes: User Interface (UI) runs the UI for reporting Analysis runs the Analysis, Administration, and Scheduler applications 68 WebTrends Installation and Configuration Guide

69 You might need analysis to run on one machine that covers all web traffic from midnight to noon and another machine to cover traffic from noon to midnight. Or you might split up analysis on machines according to shorter time sequences. SDC Systems runs the SDC software You should always run the SDC software on standalone machines, because SDC receives traffic from outside of your firewall. GeoTrends Systems runs the GeoTrends software, which gets system settings from the system database. Otherwise, put the GeoTrends software on the machine that is running analysis and be sure that you ve got 512 MB of RAM available for GeoTrends. If your web site receives a lot of visits, then you may want to place the GeoTrends software on a separate machine. Storage Systems WebTrends data can be stored on other systems as needed to handle any capacity issue. Backup Systems WebTrends data can be backed up to ancillary systems to provide flexible disaster recovery alternatives. Note: For instructions on backing up your system databases, please see the document, Backup and Restore for MySQL Databases, available on your WebTrends product CD, as well as the NetIQ website: ptw.aspx?action=14&prodtype=wrc&version=7.0 Installation steps During the installation of your WebTrends software (Enterprise, Professional, or Small Business), you will encounter a step that provides hardware recommendations based on your expected use of the software. More specifically, you will be asked to provide information about expected page views, profiles, analysis, geographical reporting, and other WebTrends features. A calculator function will then generate the minimum machine requirements for each type of machine that is needed. These requirements will include number of processors, processor speed, RAM, disk type, disk speed, RAID type, and disk space. You can then use this information to plan how the software is distributed over your machines. Installation 69

70 Custom installation Once you ve determined which machines are needed to run the WebTrends software, you can proceed with the installation and specify which parts of the software will be installed on which machine. That is, in the installation process, you will select the custom installation option, which allows you to install different parts of the WebTrends software on a number of machines. Note that the first machine you must begin with is the one that will contain the main system.the main system typically contains the UI server, the report cache server, the report exporter, and tools. Since the custom installation allows you to install one or more WebTrends features on a machine, for each feature you will be asked to specify the parameters for the system database server. If you select MySQL, you must state the host name and the associated port number. WebTrends automatically loads MySQL onto your machine. If you select Microsoft SQL Server, you must create two empty SQL server databases: one named wtmaster and the other wt_sched. You will need the host name for that machine. This server must be installed prior to beginning the custom installation. Note: Due to issues with mixing languages, WebTrends only supports SQL Servers that have the SQL_Latin1_General_CI_AS (case-insensitive) collation installed at the server level. The databases should then be configured with that same SQL_Latin1_General_CI_AS collation. During the installation process, you will also be asked to specify the storage locations for pertinent sets of data. Each path must be accessible by each machine that is part of the distributed architecture, so you should set up these locations as shared folders before beginning the custom installation. 70 WebTrends Installation and Configuration Guide

71 Figure 2-3. Storage Location dialog box To install perform a custom installation: 1. Insert the WebTrends software CD-ROM into your CD-ROM drive for the machine that you have designated for your main system if this is the first time you are setting up distributed architecture for your machines. 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. The installation wizard launches. Click Next to continue. 3. Before the WebTrends program files are copied to your system, you must accept the Software License Agreement. If you agree to the stated terms, select the I Accept the terms in the license agreement option, and click Next. Otherwise, click Cancel to exit the setup program without installing the software. Installation 71

72 4. The Add License dialog box opens. Enter your valid license key here to continue. Note: You must have internet connectivity to activate a license key. 5. If you accepted the License Agreement, the Select Install Type window opens with the Typical option selected. Select Custom. 6. The Destination Folder window opens. The default installation folder is: X:\Program Files\WebTrends where X is the hard drive you are installing to. Complete one of the following: Click OK to accept the default installation folder. If you want to install to a different directory, click Change and browse to your preferred location. Click OK twice to save the new location and continue. 7. Click on the icon in the list for the application or feature to install and click Next: Main Application Generates and displays static and dynamic WebTrends reporting information, and performs miscellaneous product housekeeping. - UI Server Generates dynamic WebTrends report web pages. Includes web server and application server. - Report Cache Server Caching engine to hold WebTrends-generated pages and serve them to the browser. - Report Exporter Generates static report formats, such as MS Word, Ms Excel, and PDF. - Tools Contains miscellaneous utilities for managing your WebTrends environment. Analysis Performs analysis of your web traffic data. - Standard Analysis Engine Performs scheduled in-depth analysis of your web traffic data. - Express Analysis Engine Provides on-going analysis of your web traffic data for limited, current day only reporting. GeoTrends Server Brings additional visitor and company location information to your reports by resolving IP addresses into more recognizable company data. System Database Contains information about the configuration of the WebTrends environment. 72 WebTrends Installation and Configuration Guide

73 8. If you selected GeoTrends, you are prompted to do one of the following: Click Download to download the latest available version of the GeoTrends data file from the WebTrends web site. The GeoTrends data file can also be found on the product CD. 9. The UI Server Parameters window opens. Specify the host and port parameters for the UI server and click Next. 10.The Select Database Type window opens. Select the type of system database and click Next: If you select MySQL, you must state the host name and the associated port number. WebTrends automatically loads MySQL onto your machine. If you select Microsoft SQL Server, you must create two empty SQL server databases: one named wtmaster and the other wt_sched. You will need the host name for that machine. This server must be installed prior to beginning this custom installation. 11.The System Database Initialization window opens, showing the host, port number, and administrator information. Enter and confirm your password, and click Next. Note: This is the the password for the database, not the WebTrends User Interface. Also, if this is s subsequent WebTrends installation, only the information used during the first installation is valid here. See your WebTrends Administrator if you have questions. 12.The Specify Storage locations window opens, showing the default folders for: Analysis Data Repository Report Data Repository Configuration Repository Backup Repository Each path must be accessible by each machine that is part of the distributed architecture. Make any changes needed; otherwise, click Next to select the default locations and continue. 13.If you select Express Analysis, you will be prompted to enter Express Analysis locations. 14.A confirmation window opens, reminding you to use shared folders for the storage locations. Click Yes if you are certain of your directory instructions. 15.A Ready to Install the Program window opens. Click Install. Installation 73

74 16.TheWebTrends program files are installed to your machine. 17.Depending on your component selection in step 7, one of the following then occurs: If you have only chosen to install WebTrends and the optional GeoTrends data file, you are notified that the installation is complete. Click Finish to close the Installation wizard. Managing your distributed installation You can use the manage and monitor your distributed installation by getting an overview of your current topology. Click on Administration > Monitoring > Topology to view the relationships of machines, software roles, and available resources. Under the Group column, you will see the names of host groups. Host groups are used to manage system resources in a distributed installation. For example, you can assign a group name, such as Speedsters, to your four fastest machines to run analysis. To analyze logs of differing sizes, you may want them to be processed by reporting agents on hosts with sufficient system resources to handle them efficiently. If you create a host group containing only the hosts capable of analyzing large log files efficiently, you can assign profiles for large logs to this group. To associate or edit host group go to Scheduler > Options > Host Groups. The following illustration shows the Host Groups dialog box. Select New Host Group to begin creating a new host group or edit the current host group. To edit a host group, click the edit icon. If you want to monitor the health of your services as they run on each machine, click Administration > Monitoring > Service Health. Migrating Manually In this section: Supported migrations (follows) Migration components (page 75) 74 WebTrends Installation and Configuration Guide

75 Preparing for migrations (page 75) The migration process (page 76) A sample migration (page 79) This section discusses the process of manually upgrading from WebTrends Reporting Center v6.x to WebTrends v7.0 for Windows. Supported migrations Migrating to WebTrends v7.0 is only supported for WebTrends Reporting Center v6.x or later for Windows. Note: Those upgrading from WebTrends v6.x for Solaris should consult WebTrends Migration Guide (Solaris). Migration components Three components are involved in the migration/upgrade process: 1. damigrate.exe Creates a temporary staging directory and migrates configuration files, performs a series of requirements and compatibility checks, and creates a temporary directory that serves as the working directory for the rest of the migration process. 2. SyncInstall.exe Updates your WebTrends Reporting Center v6.x configuration files with changes required for WebTrends v7. SyncInstall.exe automatically runs when you execute damigrate. 3. daupgrade.exe Moves analysis databases, report databases, and configuration data into your WebTrends v7.0 installation. Preparing for migration Important considerations: Make sure you have enough available drive space. You need approximately 2.25x the disk space as your current WebTrends installation if you are planning to run the migration on the same box. Installation 75

76 Check your log data source locations. If you are migrating WebTrends v6.x from one machine to WebTrends v7.0 on a different machine, check the log data sources in WebTrends v6.x prior to migrating to ensure that all paths are fully qualified and visible to the target machine. (This is a far more efficient approach than making these changes in your WebTrends v7.0 installation.) Important: WebTrends strongly recommends you back up your WebTrends v6.x settings, as well as your WebTrends v7.0 system databases, before migration. For instructions on backing up your system databases, please see the document, Backup and Restore for MySQL Databases, available on your WebTrends product CD, as well as the NetIQ website: ptw.aspx?action=14&prodtype=wrc&version=7.0 The migration process After WebTrends v7.0 is installed, two processes need to be run: 1. The first process is damigrate.exe, which: a. Copies all configuration data (profiles, settings, templates, etc.) from the v.6.x install and v7.0 install into a temporary directory. b. As necessary, configuration files are converted into the WebTrends v7.0 format. c. damigrate.exe then runs SyncInstall.exe from the temporary directory. d. damigrate.exe also creates a batch file (RunUpgrade.bat) with all the necessary parameters to run the second process of the migration. Note: For a trace of all migration process activities, look in the audit log, damigrate.log, which is located in the <WebTrends v7 Installation Directory>\modules\migrate. 2. The second process is daupgrade.exe. Under most circumstances you run daupgrade.exe via the RunUpgrade.bat supplied by the damigrate process. daupgrade.exe performs the following tasks: a. Copies configuration files from the temporary directory set up by damigrate.exe into your WebTrends v7.0 installation. b. Inserts user profiles from WebTrends v6.x into the WebTrends v7.0 system database. 76 WebTrends Installation and Configuration Guide

77 c. Inserts web data source definitions into the WebTrends v7.0 system databases. d. Iterates over all WebTrends v6.x profiles and: copies analysis databases to the specified WebTrends v7.0 location copies report databases to the specified WebTrends v7.0 location converts profile names into GUIDs, for example, 1.wlp becomes K8szjm3GPL5.wlp. Doing so avoids any conflict when merging multiple v6.x installations into the new v7.0 installation. Note: For a trace of migration activities, look in the audit log, daupgrade.log which is located in the <WebTrends Installation Directory>\modules\migrate. Both programs take similar parameters, but there are differences. To determine the exact usage, run the program without any switches, for example, damigrate.exe. While damigrate.exe has only a few simple parameters, daupgrade.exe has a far more complicated set. As a convenience, damigrate.exe creates a batch file (runupgrade.bat) with the recommended parameters and switches needed for daupgrade.exe. Normally this batch file should be used. damigrate parameters Usage: damigrate <WRC v6 src> <WebTrends v7 dst> Example: damigrate "c:\wrc_v6" "c:\webtrends_v7" Notes: The SRC directory must be a valid WebTrends v6.x installation directory. The destination directory must be a valid WebTrends v7.0 installation directory. Manual migration must be run from the <WebTrends Installation Directory>\modules\migrate directory. Installation 77

78 daupgrade parameters Usage: daupgrade [OPTION] -c <migrated SRC> -d <WRC v6 dir> -i <WRC v7 dir> Options: -c migrated source <Temp directory created by running damigrate.exe> (required) -d data source <WebTrends 6.x installation directory> (required) -i install dir <WebTrends 7.0 installation directory> (required) -v version Shows version and immediately exits. -h help Shows this informational text list. -p profile defs Moves configuration only. No data. Note: This can be a useful testing tool to help prove that your migration scenario is correct. -s services Stops and starts the WebTrends services automatically. Example: daupgrade -c "wrc_migrate_dir.tmp" -d c:\wrc6 -i "c:\wrc_v7" Notes: 1. The -c directory must be a valid temp directory created by damigrate.exe. 2. The -d directory must be a valid WebTrends v6.x installation directory that was used by damigrate.exe to create the temp directory above. 3. The -i directory must contain a valid WebTrends v7.0 installation. 78 WebTrends Installation and Configuration Guide

79 Migration example Below is a complete example of the migration process where: The existing WebTrends v6.x installation location is c:\wrc6. WebTrends v7.0 was installed in c:\webtrends7. Complete these steps: 1. Run damigrate.exe from.\modules\migrate relative to the root of the WebTrends v7.0 installation: damigrate c:\wrc6 This produces the temporary directory used for the migration, (wrc_migrate_dir.tmp) and will automatically run SyncInstall. If successful, damigrate.exe creates a batch file (RunUpgrade.bat) to run daupgrade.exe. 2. Run daupgrade.exe by completing either of the following steps: RunUpgrade.bat -s (preferred method) or daupgrade -c wrc_migrate_dir.tmp -d c:\wrc6 -i c:\wrc7 -s Notes The damigrate.exe step works entirely in the temporary migration directory. Therefore, any failure during that process leaves your WebTrends v7.0 installation unaffected. If daupgrade.exe fails, your WebTrends v6.x installation is unaffected, but your WebTrends v7.0 installation and Master database are likely to be corrupted. If daupgrade.exe fails, WebTrends recommends that you uninstall and reinstall WebTrends v7.0 and the Master database. Installation 79

80 Possible issues There may be some issues that are detected that do not stop the installation. In those cases, the program makes the best determination and presents the issues in a dialog box at the end of the migration process. These issues are also recorded in the.err file (daupgrade.err) for your further review. Make any necessary corrections via the Admin Console. Please contact Technical Support if you need assistance. Here is an example of the daupgrade.err file: :47:16: The following 3 PROBLEMS were encountered :36:40: ISSUE. DataSource [sample: Engelen Communications (Server 1)] had a relative path in Log data source location: [.\wtm_wtx\datfiles\samples\orm\web1\log.zip]. This was fixed-up to be: [e:\wrc\wtm_wtx\datfiles\samples\orm\web1\log.zip]. Correct if needed :36:40: ISSUE. DataSource [sample: Engelen Communications (Server 2)] had a relative path in Log data source location: [.\wtm_wtx\datfiles\samples\orm\web2\log.zip]. This was fixed-up to be: [e:\wrc\wtm_wtx\datfiles\samples\orm\web2\log.zip]. Correct if needed :36:40: ISSUE. DataSource [sample: RealServer log] had a relative path in Log data source location: [.\wtm_wtx\datfiles\samples\stream\sample realnetworks.log]. This was fixed-up to be: [e:\wrc\wtm_wtx\datfiles\samples\stream\sample realnetworks.log]. Correct if needed :47:16: You may need to fix the above in order for WRC to work correctly. In the above example, a relative path was encountered for a log Data Source. Address this problem by changing this pathname via the Admin Console. 80 WebTrends Installation and Configuration Guide

81 Chapter 3 WebTrends On Demand Accounts This chapter provides basic instructions for those using one of the hosted WebTrends services: WebTrends On Demand Enterprise, WebTrends On Demand Professional, or WebTrends On Demand Small Business. Enterprise Provides powerful analysis of visitor behavior, on-line transactions, and marketing campaign metrics that you can use to evaluate your e-commerce performance. To register for Enterprise, see Registering for WebTrends On Demand Enterprise on page 82. Professional Provides advanced web traffic analysis for small- to mid-sized businesses. WebTrends On Demand Professional offers predefined reports and adds features to make the analysis more timely and relevant. Professional is especially appropriate for companies that have limited IT resources and support. To register for Professional, see Registering for WebTrends On Demand Professional on page 83. Small Business Provides basic web traffic analysis for small businesses. WebTrends On Demand Small Business is a cost-effective solution for organizations that do not have IT resources. To register for Small Business, see Instructions for WebTrends On Demand Small Business on page 99. WebTrends On Demand Accounts 81

82 Registering for WebTrends On Demand Enterprise The following instructions describe how to register for WebTrends On Demand Enterprise, log into your Enterprise account, set up a source for your data, create a profile, and receive a report on that profile. To register for Enterprise 1. Register to use WebTrends On Demand Enterprise by signing up for service at reports.webtrends.com. 2. Choose Click here to sign up. 3. Select Enterprise. 4. Enter the contact information in the required fields. If you know the Estimated Monthly Hits, enter that number in the corresponding field. Note that VAT Reg. Number refers to a Value Added Tax number and applies to European countries that have VAT requirements.click Next Step. 5. Enter a user name, password, and confirm the password, then click Next Step. Note that passwords must meet the following requirements: Must be at least 6 characters in length Must contain both upper and lower case letters Must contain at least one integer (1-9) Cannot be part of your username Cannot contain your first or last name Cannot contain spaces 6. Confirm the settings you have selected and click Submit Registration. Your registration request is complete and you will be contacted by NetIQ customer representatives regarding account and billing information that suits your needs. 82 WebTrends Installation and Configuration Guide

83 Registering for WebTrends On Demand Professional The WebTrends On Demand Professional environment maintains all of your log files and makes sure that these files are associated with the profiles that you create. To register for the Professional Edition: 1. Register to use WebTrends On Demand Professional by signing up for service at reports.webtrends.com. 2. Choose Click here to sign up. 3. Select Professional. 4. Enter the contact information in the required fields, then click Next Step. Note that VAT Reg. Number refers to a Value Added Tax number and applies to European countries that have VAT requirements. 5. Select the payment method you would like for your account and click Next Step. Monthly Plan Credit Card You will receive a monthly billing that is charged to your credit card. To make your decision, consider the rate information provided. Go to step 7. Volume Plan Credit Card You will be billed according to page views per month. Charges will be billed to your credit card. Go to step 6. Volume Plan Purchase Order You will be billed according to page views per month. Charges will be billed to the address you supply, and you will be contacted by a NetIQ customer service representative. Go to step 6. Note that purchase order may take longer to set up your account. 6. Choose the volume billing plan that fits your needs, then click Next Step. 7. Enter the billing information in the required fields, then click Next Step. WebTrends On Demand Accounts 83

84 8. Enter a user name, password, and confirm the password, then click Next Step. Note that passwords must meet the following requirements: Must be at least 6 characters in length Must contain both upper and lower case letters Must contain at least one integer (1-9) Cannot be part of your username Cannot contain your first or last name Cannot contain spaces 9. Confirm the contact and the billing information, then check the box to confirm that you agree with the Terms of Service and the WebTrends On Demand Privacy Policy. Click Submit Registration. 10.Select how you want to be billed. If you choose to be billed by Purchase Order, you will be contacted within seven days regarding the order. 11.Continue by selecting one of the following options: Click Go to the Account Administration Console and go to step 3 in the next section below to begin adding a profile to your account. Click log out on the tool bar and go to the first step in the next set of procedures To log in to your account.. You will receive a confirmation of registration via . The message will contain a link and a validation key for the first time that you log in to WebTrends On Demand. 84 WebTrends Installation and Configuration Guide

85 Logging on to WebTrends On Demand Enterprise or Professional To log in to your account: 1. You receive confirmation of registration via . The message contains a link and a validation key for the first time that you log in to WebTrends On Demand Enterprise or Professional. Click the URL provided in the Log in to WebTrends On Demand with your user name, account name, password, and validation key. Note that the information you enter is case sensitive. Figure 3-1 on page 85 shows the Account Console. Figure 3-1. Account Console WebTrends On Demand Accounts 85

86 3. The first time you click on one of the menu items on the left-hand side of the screen, you are presented the License Agreement. Review the Terms of Service and the Privacy Policy. Click on these items to read them, then click the corresponding check box to I agree to the terms of service. Then click I Agree in the lower right-hand corner. 4. Check your account settings. Click Edit Account to view information on the following: Account Information Your contact information Billing Plan Your cost information Settings Information about your current usage of some settings and your contracted limit For reports to be created for your acccount, you must specify a data source. To set up a source for your data: You specify a datasource before you create a profile, because your profile must be associated with a data source. 1. From the Account Console, click Profiles & Reports to get to the Admin Console. The Web Analysis Overview page opens. This overview offers some basic information about web analysis concepts. 2. Click Administration and then click Data Sources to add a data source. 3. Click New Data Source to specify the source of the data that you would like WebTrends On Demand to analyze. Figure 3-2 on page 87 shows the Data Source dialog box. 86 WebTrends Installation and Configuration Guide

87 Figure 3-2. Create New Log Data Source dialog box 4. Enter the name of the data source in the text box provided. 5. Paste the JavaScript between the <body> and </body> tags on all of the web pages you want to track. Note that the JavaScript is created from the information you provided in your settings. The JavaScript directs information about the activity on your web site to your data source files. The files log the activity. 6. Click Save to add this new data source to the list of data sources. Your new data source is not valid until you save it. Next, you create a profile and associate the data source with that profile. To create a profile: 1. Click Web Analysis and then Profiles & Reports to identify a named group of settings WebTrends On Demand Accounts 87

88 with which you identify the visitor activity data on your web pages. The information about this activity is collected and stored on the WebTrends servers and then analyzed and finally displayed in your WebTrends On Demand reports. After you create a profile, its name is displayed in the Admin Console and reports. Figure 3-3 on page 88 shows the Admin Console. Figure 3-3. Admin Console Note: When you are configuring profiles, you are working in the Admin Console. Click Account Console in the left-hand menu to return to the Account Console. 2. Click New Profile to define your profile. All of the instructions for the New Profile Wizard are discussed in Launching the New Profile Wizard On Demand only on page 124. Note that you associate a data source with your new profile during the New Profile Wizard process. 3. At the end of the New Profile Wizard, you can review a summary of your selections for your profile. Click Save to accept the settings for the profile or define the advanced settings that you want. If you want to define more settings to further customize your profile, click Advanced 88 WebTrends Installation and Configuration Guide

89 Settings. Included in the tabs for these settings are tabs representing the dialog boxes that you completed in the new profile wizard. The additional tabs you see depend on choices you made in the new profile wizard. Please see the online help for details on configuring Advanced Settings. 4. Click OK to the confirmation message. 5. Click Account Console in the left-hand menu to return to the Account Console. 6. Click log out to exit WebTrends On Demand. Your first reports should appear within a few hours. To view your reports: 1. Log into your WebTrends On Demand Enterprise or Professional account. 2. The Account Console is displayed. 3. Click Profiles & Reports in the left-hand menu. 4. Select a profile in the list, and click the View Reports icon. Figure 3-4 on page 90 shows a sample Enterprise report. WebTrends On Demand Accounts 89

90 Figure 3-4. Sample Enterprise report To add users to your account 1. From the Account Console (not Admin Console), select the account to which you want to add users, and click Users. 2. Click Add User, and follow the instructions in the dialog box. 3. Click Apply Changes. 4. Click Return to User List. WebTrends welcomes the new user via and delivers pertinent information, so that the new user can log on to WebTrends. 90 WebTrends Installation and Configuration Guide

91 To manage user rights Once users have been created, you can fine-tune their access rights to WebTrends features. 1. Click Profiles & Reports. The Web Analysis Overview page opens. 2. Click Administration. 3. Click Users. 4. Edit the user listed. Enterprise and Professional Account Console The Account Console provides access to all features of WebTrends On Demand. When you first log in, a list of all accounts associated with the main account is displayed in the account list. The following section describes the components of the Account Console. Account Profile & Reports Lets you analyze your web traffic activity and create reports. A profile defines how data from an associated data source should be analyzed and reported. See To create a profile: on page 87 for information on creating a profile. Users Allows you to manage user rights for each account in the Account List. Select an account in the list to work with that account s users and associated rights. You can also edit, remove, and add user rights if you have administrator rights for your account. Edit Account Allows you to modify settings for the selected account. Edit Account settings contains contact information, billing information, and other account settings information. WebTrends On Demand Accounts 91

92 Account History Shows a list of significant events for the account selected, such as the creation of a profile. You can sort the list by date, action, or event details. Select an event, and click View Item for details. Account Usage Provides a summary of licensing statistics about the account selected, such as the number of profiles and custom reports used. See Checking the license status on page 24 for more information. Delete Account Lets you delete the selected account if you have administrator rights. Create Account/Create Subaccount Lets you create an account if you have administrator rights for a reseller or master account, or have licensed the ability to create sub-accounts within your account. My Settings Contact Information Lets you review and change your contact information. Change Password Lets you change your password. Mailing Lists Lets you review and change your mailing list preferences. Tool Bar Commands Log Out Logs you out of the WebTrends On Demand service. Feedback Lets you provide general product feedback, report a problem, or request a feature. 92 WebTrends Installation and Configuration Guide

93 Technical Support Provides links to a variety of technical information. Account Console Indicates that you are in the Account Console. Help Opens the online Help system. Working with user settings From the Account Console, you can manage the users associated with each account listed by adding users, modifying access rights, and removing users from the account. To add a user 1. Select the account from the Account Console that you want to work with. 2. Click Users in the left-hand menu, and the users who are currently members of the account are displayed. 3. Click Add User, and the New User dialog box opens. 4. Provide the following information for the Step 1 of 2 dialog box. Username The username must contain 4-30 alphanumeric characters and must not contain spaces. Enter a valid address for the user. The new user receives a welcome that provides information needed to log in to WebTrends. First Name Enter the user s first name. Last Name Enter the user s last name. Company Enter the organization this user is associated with. WebTrends On Demand Accounts 93

94 Password Select Auto-Generate Password to have a password automatically created for the user, or select Specify Password to define a custom password for the user. 5. Select the rights for the new user in the Step 2 of 2 dialog box, and click Apply Changes. To create users in mass If you have an Enterprise account of a master or reseller type, you can create multiple user accounts at once by specifying them in comma-delimited text format. To create multiple users at once: 1. Select the account from the Account Console that you want to work with. 2. Click Users in the left-hand menu, and then select Mass User Creation. 3. Enter each user on a separate line in the User List dialog box in the following format: Username,User ,First Name,Last Name,Right IDs For example: Sue,[email protected],Sue,Miller,1 5 To view a list of right IDs, select the Click Here to View List of Valid Right IDs link in the dialog box. Note: You can generate this user list from an external database, and copy and paste that data in the User List dialog box. To edit user rights You can modify access rights settings for the Account Console using the Edit Rights dialog box. Note: To fine-tune these access rights settings, see To manage user rights on page WebTrends Installation and Configuration Guide

95 1. Select the account from the Account Console that you want to work with. 2. Click Users in the left-hand menu, and the users of the selected account are displayed. 3. Select a single user or multiple users, and click Edit Rights. The users selected are displayed in The Modifying Rights for the Following Users text box. 4. Select the rights that these users should be granted. Note: You can define rights in greater detail through the Admin Console. See To manage user rights on page 91 for information on accessing this dialog box. A dark check means that all of the selected users have the right, and a light gray check means that while at least one of the selected users has the right, not all of them do. The Reset Rights link resets the rights to the state they were before you began this instance of editing rights. 5. Click Apply Changes, and you see the Rights Assignment Complete dialog box that lists the Rights Granted and Rights Denied for the selected users. To remove a user 1. Select the account from the Account Console that you want to work with. 2. Click Users from the left-hand menu, and the users who are members of the account are displayed. 3. Select the users you want to remove from the account, and click Remove User. 4. The users selected appear in the Users to Be Removed text box. To remove those listed, click Apply Changes. Changing account information You can update contact information for your account in the Edit Account dialog. To modify account information: 1. Select the account from the Account Console that you want to work with. 2. Click Edit Account in the left-hand menu. 3. The following fields can be changed in the Account Information tab: WebTrends On Demand Accounts 95

96 Account Name Identifies the account in the Account List. Client Billing Code May be used to uniquely identify the account for your billing purposes. Contact Name Specifies the name of your main contact for the account. Company Specifies the company associated with this account. address Specifies the address for the contact listed. Telephone Specifies the phone number for the contact listed. Address Specifies the mailing address for the contact listed. City Specifies the city for the address. State Specifies the state for the address. Country Specifies the country for the address Zip Code Specifies the zip code for the address Report Access Indicates whether or not reports can be accessed for this account. For example, report access might be disabled if the account requires log file delivery only. Note: The following settings are only available in WebTrends On Demand Enterprise. Log File Delivery Indicates whether or not log files are provided as a service for this account. With Log File Delivery enabled for the account, the data sources can be configured to use the feature. 96 WebTrends Installation and Configuration Guide

97 Availability Days If Log File Delivery is set to Enabled, this field indicates the maximum number of days to retain the log files on the FTP server. Log files may be retained for up to 30 days. 4. The Settings tab displays the current limits for the following: Number of allowed profiles Number of allowed custom reports Number of allowed report exports The edition of WebTrends you are using determines the maximum number available. See How WebTrends On Demand is licensed on page 24 for details. Note: You may be able to adjust the maximum values if you have a master or reseller type of account. Viewing account history You can view event data for the account in the Account History dialog box. This dialog displays the date of the event, actions taken, and event details. This information can be very helpful for administering the account. For example, if you need to find out who deleted a profile or received a specific report, you could find those details here. To view account history: 1. Select the account from the Account Console that you want to work with. 2. Click Account History, and a list of events is displayed. 3. Select an item in the list, and click View Item in the left-hand menu to show event details. Note: The Account History list can be sorted by Date, Action, and Details. WebTrends On Demand Accounts 97

98 Creating an account Resellers of WebTrends On Demand Enterprise Edition have multiple accounts under one main account for billing and administrative purposes. As a reseller, you have one main reseller account that contains all your customer accounts and within those accounts, it is possible to have sub-accounts. Enterprise account holders who have licensed sub-accounts for their accounts may also create accounts. To create a new account: 1. Log in to WebTrends On Demand. 2. From the Account Console, click Create Account/Create Subaccount. 3. The New Account Creation dialog box indicates the account that you are logged into. Be sure that this is the account that you want associated with the new account. Select one of the following options: Add New Reseller Account If you have a master type of account, this option is available to add a reseller account. Reseller accounts contain customer accounts which you can administer. Add New Customer Account If you have a master or reseller type of account, this option is available to create an account associated with the reseller account selected. A single company may have a single customer account and multiple sub acccounts within the account for each division, department, product, or other segment that requires separate reporting. Add a Sub-Account to An Existing Customer Account This option creates an account associated with the customer account selected. Subaccounts share the resources of the account such as profiles and custom reports. 4. Click Next Step, and the Account Information dialog box opens. The information required is indicated with asterisks. Click Next Step. 5. If you are creating a new reseller account, the Account Service Settings for New Reseller Account dialog box opens. Enter the maximum number of child accounts, custom profiles, custom reports, and report exports that this new account should have. The dialog box displays the quantities available to be distributed from the master account to the reseller account. 6. Click Next Step, and the User Information dialog box opens. Enter the required information in the text boxes. 98 WebTrends Installation and Configuration Guide

99 7. Click Next Step to review settings for the account, and click Submit Registration if you are satisfied. Otherwise, click Back to make changes. Instructions for WebTrends On Demand Small Business The WebTrends On Demand Small Business environment maintains all of your log files and makes sure that these files are associated with the profiles that you create. To register for the Small Business Edition: 1. Register to use WebTrends On Demand by signing up for service at reports.webtrends.com. 2. Choose Click here to sign up. 3. Select Small Business. 4. Enter the contact information in the required fields, then click Next Step. Note that VAT Reg. Number refers to a Value Added Tax number and applies to European countries that have VAT requirements. 5. Select the payment method you would like for your account and click Next Step. Monthly Plan Credit Card You will receive a monthly billing that is charged to your credit card. To make your decision, consider the rate information provided. Go to step 7. Volume Plan Credit Card You will be billed according to page views per month. Charges will be billed to your credit card. Go to step Choose the volume billing plan that fits your needs, then click Next Step 7. Enter the billing information in the required fields, then click Next Step. 8. Enter a user name, password, and confirm the password, then click Next Step. Note that passwords must meet the following requirements: WebTrends On Demand Accounts 99

100 Must be at least 6 characters in length Must contain both upper and lower case letters Must contain at least one integer (1-9) Cannot be part of your username Cannot contain your first or last name Cannot contain spaces 9. Confirm the Account, Log In, and the Billing information, then check the box to confirm that you agree with the Terms of Service and the NetIQ Privacy Policy. Click Submit Registration. 10.Select how you want to be billed. If you choose to be billed by Purchase Order, you will be contacted in about seven days regarding the order. 11.Continue by selecting one of the following options: Click Add a Profile and go to step 2 on page 101 to begin adding a profile to your account. Click log out on the tool bar and go to the first step in the next set of procedures To log in to your account. You will receive a confirmation of registration via . The message will contain a link and a validation key for the first time that you log in to WebTrends On Demand. To log in to your account: 1. Click the URL provided in the Log in to WebTrends On Demand with your user name, account name, password, and validation key. Note that the information you enter is case sensitive. Figure 3-5 shows the Account Console. 100 WebTrends Installation and Configuration Guide

101 Figure 3-5. Small Business Account Console 3. Check your account settings. Click Edit Account so that you can view the following: Contact Information Your contract information Billing Plan Your cost information Settings Information about your current usage of some settings and your contracted limit To create a profile and use the JavaScript: 1. Click Profiles & Reports to identify a named group of settings with which you identify the visitor activity data on your web pages. The information about this activity will be collected and stored on the WebTrends servers and then analyzed and finally displayed in your WebTrends On Demand reports. 2. Click Add Profile. Enter information in the required fields, which includes the WebTrends On Demand Accounts 101

102 following: Profile Name Identifies the profile. URL Specifies the location of the page you want tracked and analyzed. Time zone Specifies the time zone you want reflected in your reports. User Access Uses the arrows to allow specific users access to this profile. First Day of Week Indicates which day is considered the first day of the week in your reports. IP Exclude Filter IP address of a visitor you don t want counted in the analysis of this profile. For example, you might not want to count visitors from your own company. 3. Click Add Profile. The JavaScript tab is highlighted and JavaScript is displayed. Note that the JavaScript directs information about the activity on your web site to files that log the information. The files log the activity. 4. Copy the JavaScript. 5. Paste the JavaScript between the <body> and </body> tags on all of the web pages you want WebTrends On Demand to track. Your first reports should appear the next day. To view your reports: 1. Click Profiles and Reports on the account console. 2. Click Reports to view reports for a specific profile. As soon as you have pasted the WebTrends JavaScript code to your deployed web pages, your web site traffic data is collected by WebTrends servers. Comprehensive reports on your site activity will be ready for viewing within the next 24 hours. Figure 3-6 shows a sample Small Business report: 102 WebTrends Installation and Configuration Guide

103 Figure 3-6. Sample Small Business Report Small Business Account Console The Account Console of WebTrends On Demand Small Business displays the following: Account Profiles & Reports Lets you analyze your web traffic activity and create reports. A profile defines how data from an associated data source should be analyzed and reported. WebTrends On Demand Accounts 103

104 Users Lists users and associated rights to your account. You can also edit, remove, and add user rights if you have administrator rights for your account. Edit Account Contains contact information, billing information, and information on the settings of your account. Account History Shows significant events, such as the creation of a profile, for your account. Account Usage Provides a summary of statistics about your account. Delete Account Lets you delete an account if you have administrators rights. My settings Contact Info Lets you review and change your contact information. Change Password Lets you review and change your password. Mailing Lists Lets you review and change your mailing list preferences. Tool Bar commands Log Out Logs you out of the WebTrends On Demand service. Feedback Lets you send your comments and questions to Technical Support for WebTrends On Demand. Technical Support Provides links to a variety of technical information. 104 WebTrends Installation and Configuration Guide

105 Account Console Returns you to the Account Console view. Help Opens the online Help system. Additional Concepts and Definitions The following concepts and definitions are helpful in understanding WebTrends On Demand Enterprise, Professional, and Small Business reports. First-Time Visitor This indicates someone who visits your web site for the first time. A first-time visitor is counted once in the report period, when he or she first arrives. WebTrends On Demand defines first-time visitors as visitors without a WebTrends On Demand cookie. Returning Visitor This indicates someone who has visited your web site at some time previous to the current report period and has returned to visit during the current report period. A returning visitor is counted once in the report period, when he or she first arrives. Returning visitors are recognized by their WebTrends On Demand cookie. Unique Visitors These are individuals, different from any other visitors within the report period. They are counted once in a report period, when they first arrive. The sum of first-time visitors and returning visitors is the total of unique visitors for the report period. The report period can be daily, weekly, monthly, and/or yearly. Comparing Unique Visitors and Returning Visitors Note that visitors who visit once on every day of a week are counted as unique visitors in each daily report. They are never repeat visitors. However, in the weekly report, they are counted once as a unique visitor and six times as a repeat visitor. WebTrends On Demand Accounts 105

106 Therefore, unique visitor totals in a daily report periods do not add up to the unique visitor totals in a weekly report period. Visit or Visitor Session A single visit also called a visitor session includes all of a visitor s activity from the first page view until he or she exits the web site or remains inactive for 30 minutes. Each time a visitor enters your web site is counted as a visit. Average: an Arithmetic Mean An arithmetic mean is a simple average: the total of all of the numbers in a group divided by the number of numbers in the group. It is considered a weighted average between extremes because it includes all of the numbers in the group, even when the range of the numbers is very large. Standard Report Period Averages WebTrends On Demand reports present averages for comparative analysis. Averages in Standard Report Periods are averages of like time-slices either of all like time-slices in your data since you started or of all like time-slices in the selected report period. For example, Mondays are averaged with Mondays and the first week of the month is averaged with the first weeks of months. 106 WebTrends Installation and Configuration Guide

107 Chapter 4 WebTrends User Accounts Overview The User Access and Privileges feature enables you to set up users in the WebTrends software. For each user, you specify the features they can access, their default profile settings, and the dialog boxes they see. You can use WebTrends Authentication to specify user names and passwords as well. Note: If your web server is configured for Operating System Authentication, users must be present on the local machine or have a domain account. (If you choose not to set up a local user account, use Custom Authentication.) For full details on setting up a local user, please refer to your operating system s documentation. Adding Users To add a user: 1. From the left panel of the Admin Console, click Administration > Users. A list of the current administrators and users opens. 2. Click New User. The Adding User dialog box opens. General tab Set login information here. WebTrends User Accounts 107

108 3. In the Login Name text box, type the login name for the user. If the Password and Confirm Password text boxes are displayed, type the password for the user. Note: The password field appears only if Custom Authentication is enabled. See Configuring web server settings on page 261 for more information. 4. Type a descriptive name in the User Name text box. WebTrends uses this description in user lists elsewhere in the program. 5. In the User Password section, choose one of the following options: Select your system to authenticate this user's password Select WebTrends software to do the authentication. If you choose WebTrends software, then you must enter the password and verify it in the accompanying text boxes so that the WebTrends software will recognize the user. 6. If at any time you need to disable this user s WebTrends access, select the Disable User checkbox here. This will not delete or remove the user from WebTrends, just suspend their ability to access the program. Preferences tab Use the Preferences dialog box to select preferences for this user regarding time zone and session timeout. Time Zone: Select the system default time zone or select another time zone from the drop-down list for all events associated with this user. Session Timeout: Select the system default session timeout or select another session timeout. Sessionizing is the process of assigning a unique visitor to one or more actions that occurred within a defined time period, or session. A session denotes a sequence of hits up until the point in which the gap between two successive hits is greater than the defined timeout session length (usually thirty minutes). If you modify the session timeout length, you will affect the session visit count. For example, shortening the timeout length will increase the count in the number of visits. 108 WebTrends Installation and Configuration Guide

109 User Rights tab 7. To set WebTrends privileges for this user, select from the following options: Administration Module Analysis Options Custom Reports Export Reports Floating Dashboard Profiles Report Configuration Report Designer Reports Scheduler Module SmartView Templates. Summary tab 8. The Summary tab lists your current settings for the user you are adding. To save these settings, click OK. The user is added to the Users list. Note: Once a user has been added, they must be given access to the profiles they will be working with. (Unless the user has Administrator Rights, then they have access to all profiles.) If you have questions about your user rights, see your company s WebTrends administrator for more information. To log in to the WebTrends software as a different user, close both the Admin Console dialog box and the initial Log In dialog box before relaunching the WebTrends software. WebTrends User Accounts 109

110 About Users View Only Permissions Users who have no other permissions than View Reports automatically use the WebTrends Desktop (Report Viewer) instead of the Admin Console. While they can view the reports, they do not have access to any of the other controls. The WebTrends User Guide, is available to help orient view-only users to the WebTrends Desktop. This document can be found on the product CD in the Documentation directory or on the web at ptw.aspx?action=14&prodtype=rcent&version=7.0&os=win WebTrends Installation and Configuration Guide

111 Chapter 5 Working with the Report Designer This chapter provides an overview of the various elements of the WebTrends Report Designer: Templates (covered in the section below) Dashboards (see page 115) Report Options (see page 117) Note: If you do not have access to these settings, you may not have been given administrative rights to edit them. If you have questions about your WebTrends user rights, please see your WebTrends administrator. Report Templates Specify the appearance of your reports using report templates. A report template defines the look and content of the report, including the colors, tables, graphs, and language used. You can start with a blank template or modify one of the report templates that WebTrends provides to create new ones. The report template settings are contained on four tabs. Template settings Select Report Designer>Templates from the left pane of the Admin Console. A list of available templates opens to the right. (See Figure 5-1 on page 112.) Working with the Report Designer 111

112 Figure 5-1. Report Designer>Templates view The icon preceding each template s name shows what type of template it is. Click it to open that template s settings. The trio of icons at the end of each template, shortcuts for Edit, Copy, and Delete. Each template s settings include these tabs: General tab Use the General dialog box to name your template and specify its type. Template Name: Type the name for this template. This name is used in the Web Analysis > Report Designer > Templates list and in the Report Templates list in Profiles > Reports. 112 WebTrends Installation and Configuration Guide

113 Template Type: Specify this template's type. Note: If you are editing a template, this control doesn't show. Content tab The left side of the tab displays the Table of Contents for the selected template; highlight any item in it, and the selected report or dashboard appears to the right. Use the icon toolbar at the top of this view to manage the following items: New Chapter icon : in the left of the pane, highlight the entry you want to add a new chapter until, and click this icon. Enter a description you want to use for this in the text box that opens, and click Save at the bottom of the screen. Delete icon : in the left of the pane, highlight the item you want to delete from this template, and click this icon. Click Save at the bottom of the screen. Move up, Move down icons : use these to edit how the hierarchy of reports included in this template. Add Reports icon : Use this to add dashboards and reports to the currently selected folder. Click Done at the bottom of the screen to save your additions to this template. Add Dashboard icon : Use this to add dashboard items to the currently selected folder. Dashboards appear in reports as summary items that you can click to get the full information. Click Done at the bottom of the screen to save your additions to this template Note: Some Dashboard Descriptions in the dashboards that come loaded with the WebTrends software contain strings surrounded by %% signs, for example, %%GeneralStats_ShortDescription%%. These strings are used as tokens that refer to localized text. If you change these tokens, the localized text function does not work. Also, the tokens are specific to the dashboards and templates that contain them. If you copy a dashboard containing a token, replace the token with your own text. Add External Link icon : Use this dialog box to specify a Web page or image to be included in the report. The linked information displays in the report in a space that's the same size as the other dashboard items. Click Done at the bottom of the screen to save your additions to this template. Working with the Report Designer 113

114 Language/Style tab Use this tab to specify how your reports will look, including their colors, format, and language. Style Sheets (text/css): Select the style sheet that you want to use for this template. Style sheets define colors as well as the format of the report. You can view the style by clicking Style Preview. Default Language: From the drop-down list, select the default language to use for this template. If desired, users can change the language in the Report Viewer. Word Wrap: Select wether to wrap long strings of text or cut them off. Wrapping text will provide a more complete story while trimming long strings makes for a shorter, cleaner report. Report Graphs: Select whether to include graphs in the report. If the length of your reports is an issue, deselecting this can help reduce their size. Report Tables: Select if you want to tables included in the report. If the length of your reports is an issue, deselecting this option can help reduce their size. Help Cards: Select this check box to include help cards in reports that use this template. Help cards explain the tables of the report and describe how to use the information in the report. The information in the Help cards is relative to the data being shown in the report. Template Access This is where you set which users have View, Edit, and Delete rights to this Template. You can use Select All or Select None as shortcuts to these checkboxes, if you have many users to work with. Applying templates You apply templates in Options section of the Report Designer. For more information, see Report Templates on page 64. Note: For information on how to add, edit, and delete templates, please refer to the online Help. 114 WebTrends Installation and Configuration Guide

115 Report Dashboards Use dashboards to specify the graphs and summary tables relevant to your needs. These items display in the report as summaries that you can click on to see the corresponding full details. If you don t find a dashboard that suits your purposes, you can either build a new Dashboard, or copy one you like and modify it to meet your needs. Dashboard settings Select Report Designer>Dashboards from the left pane of the Admin Console. A list of dashboards that you can include in your report opens to the right. (See figure on following page.). These are listed in groups of ten. Use the 20 or 50 tabs if you prefer to work with a longer list of dashboards. Use the browsing links, such as Next 10, or Last 10 links in the bottom right and left corners of the table to navigate your way through this list. Dashboard settings appear in two tabbed views: General tab Name: Use this to specify the unique name of this dashboard. It is used in the report table of contents and as the title of the dashboard in the report. Title: Use this to explain what type of information this dashboard contains. This description appears in the report just under the title for this dashboard. Short Description: Use this to explain what type of information this dashboard contains. This description appears in the report just under the title for this dashboard. Note: Some Dashboard Descriptions that come loaded with the WebTrends software contain strings surrounded by "%%". These strings are used as tokens that refer to localized text. If you change these tokens, the localized text function does not work. Also, the tokens are specific to the dashboard descriptions that use them. If you copy a dashboard description containing a token, replace the token with your own text. Working with the Report Designer 115

116 Type Of Dashboard: Specify the type of profile this dashboard will be used with. (See the online help for information on the different profile types.) Note: If you are in Edit Mode, this option will be greyed out and not available to you. Content tab You can update the contents of a dashboard using this tab. The Content Tab opens showing the current elements that make up this dashboard. Here, you can edit the presentation of each individual dashboard element, or add additional reports or external links to your dashboard. Adding Elements Add External Link: Click this to link a URL to this dashboard. You specify it to show up as an image and when you click on this thumbnail, you will be taken to the URL. Add Item To Dashboard: Click this to select additional tables and graphs you want to include in this dashboard. Editing how an individual report appears in the dashboard Click the top banner of the thumbnails to drag and drop them where you want them to appear within the dashboard. Configure how the graphs are rendered: Use the tabs near the top of the thumbnails to specify the type of bar graph or whether you'd rather have a pie chart. Use the check boxes to specify the formatting of the graph. Delete unwanted thumbnails. Quickly edit external links. 116 WebTrends Installation and Configuration Guide

117 Report Options This area is where you set global behavior for how WebTrends builds reports for new profiles. It is important to remember that changes made to these settings apply to all profiles, including those you have previously configured. To edit individual reports themselves, make your changes to each profile using the profile editor. Note: From the Admin Console, select Web Analysis>Profiles & Reports <profile name>>edit profile to open the profile editor. Reports Use this tab to define which reports you want WebTrends to generate for new profiles by default. Because disk space and memory are needed to maintain the report data, only select the reports you need. Remember that your changes here affect all your profiles. Generated Report Types: Select the check boxes for the reports that you want created by default. Allow Non-administrators To Configure And Override These Default Settings In Each Profile: Select this check box to give non-administrators the right to modify these options on a per-profile basis. Maximum Number Of Elements Available In Report Tables ( ): Type the maximum number of elements that you want queried for each table. Each time a profile is analyzed, WebTrends updates each of the reports selected. Once the data is used to create the reports, it is no longer needed and is discarded. 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 the data used for the daily report is discarded. Working with the Report Designer 117

118 Report templates Profiles use templates to format their reports. Use this tab to define the default Report Template assigned when creating profiles. Important: Any changes made on this tab affect all default values, including those you accepted when creating previous profiles. Be aware that the changes you make here affect all of your profiles. Web: Use this drop-down list to select the default template for web server profiles. Streaming Media: Use this drop-down list to select the default template for streaming media server profiles. Express Analysis: Use this drop-down list to select the default template for Express Analysis profiles. Note: To add a report template to any of these groups, go to Report Designer>Templates. See Report Templates on page 111 of this guide or the online help for details. Report Week Starts On: Use this to specify on which day of the week to start your reports. Allow Non Administrators To Configure And Override This Default Setting In Each Profile: Select this check box to give non-administrators rights to customize these default templates. 118 WebTrends Installation and Configuration Guide

119 Chapter 6 Express Viewer Introduction The Express Viewer is a data visualization tool that works in tandem with your WebTrends analysis. Once installed and configured, the Express Viewer provides an updated summary of report data of your choosing. It delivers key metrics directly to your desktop to help you monitor important trends and stay on top of web site performance throughout the day. With the Express Viewer, you can: View how campaigns are performing and how product sales are performing with those campaigns. By knowing which offers are performing best, you can make informed decisions about issues such as whether inventory needs to increase to meet demand. Monitor your visitor trends to see which content areas are most visited. Verify that your site is up and operating properly. In a single view, monitor critical daily metrics throughout the day, enabling you to stay up-to-date on key campaign or product initiatives. Express Viewers can be configured to display graphs or in ticker mode, where the information appears in a small application bar as streaming text. The ticker mode takes very little screen space and enables you to easily review updated records, throughout the day, as your site records more traffic. Express Viewers can be customized for each user or department, letting them see just the information they're interested in. Express Viewer Restrictions Express Viewers can display up to 12 graphs. They do not support other items, such as tables or funnels, nor can they display more than 12 graphs. Express Viewer 119

120 While Express Viewers can be used with standard WebTrends profiles, it is more beneficial to use them with Express Analysis profiles because the Express Analysis profiles are updated more frequently. Installation instructions In this section: Installation Instructions (see below) Configuration Instructions (see page 121) Uninstalling the Express Dashboard (see page 121). You can install the Express Viewer: from the WebTrends Admin Console, from your Windows Desktop, or from the installer in the installation directory. To install the Express Viewer, complete one of the following processes: From the Admin Console: a. Select Help from the left panel of the WebTrends Admin Console. b. Click Install Express Viewer. The Installation wizard launches. c. The Options dialog box opens. Enter your WebTrends password, and click OK. Note: Please see your WebTrends administrator is you have questions about your WebTrends password. d. You are notified when the installation is complete. Click Done to close the installer. From the Windows Desktop: a. Click the WebTrends Express Viewer icon on your Windows Desktop. b. Click Install Express Viewer. You are notified when the installation is complete. c. The Options dialog box opens. Enter your WebTrends password, and click OK. Note: Please see your WebTrends administrator is you have questions about your WebTrends password. d. You are notified when the installation is complete. Click Done to close the installer. 120 WebTrends Installation and Configuration Guide

121 You can now launch Express Viewer from shortcut icons on your Desktop. You can also launch Express Viewer by selecting Start>Programs>WebTrends Express Viewer>Express Viewer. Configuration instructions Complete the following steps to use a Standard Express Dashboard. 1. In WebTrends, create a new dashboard.(see page 115, or the online help for instructions). 2. At the General dialog box, for the Type Of Dashboard, select Web and the Make Compatible For Express Dashboards check boxes. 3. Add or edit an existing Web template. (See page 115 or the online help for instructions.) In the Express Dashboard dialog box, select the Express Dashboard you created. 4. Add or edit an existing Express Analysis profile. (See page 124 or the online help for instructions.) In the Report Templates dialog box, select the template containing the Express Dashboard. Start the Express Dashboard by double-clicking the Express Dashboard shortcut on your desktop, or selecting WebTrends Express Viewer > Express Viewer from the main Windows Program Start Menu. Click Configure and on the Report tab, specify the profile and template to use. Uninstalling the Express Viewer Use the Windows Add/Remove Programs feature to uninstall this program. To do this: 1. From the lower left corner of your screen, select Start>Programs>WebTrends Express Viewer>Uninstall Express Viewer. 2. Windows uninstalls the Express Viewer. This does not impact your greater WebTrends installation. Express Viewer 121

122 122 WebTrends Installation and Configuration Guide

123 Chapter 7 Profile Setup How Profiles Work Profiles specify all of the information needed to generate reports from a web data file. They define the location of your web server data file and how it should be analyzed. Profile information includes: 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 files Which information to included in the report Who can access the profile File location for report data Which reports to create When to update reports. If you are logged on as a WebTrends administrator, you can add, edit, and modify all profiles, including those created by other users. This chapter explains the different type of profiles you can configure in WebTrends, and how to build and edit them. After you have completed your initial configuration of your profiles, you can find detailed information on working with profile options, and Advanced Settings in the WebTrends online help. Profile Setup 123

124 Adding Profiles This section explains how to configure a profile using the Add New Profile wizard. The wizard has over 20 sections that it will automatically walk you through. The order of the sections depends on your licenses and choices made during the creation of the profile. This section covers instructions for adding all three types of WebTrends profiles: Standard, Data Source Splitter, and Parent-Child. Profile Class on page 131 Site Configuration on page 133 General on page 134 Parent-Child configuration on page 135 Data Sources: multiple machines on page 138 Data Sources: single machine on page 139 Home on page 140 Schedule on page 141 Host Binding and Priority on page 146 Pre-Analysis Processing on page 146 Post-Analysis Processing on page 147 Summary on page 148 Once the profile has been created, these screens can also be randomly accessed from the Admin Console through Profiles > Edit. Launching the New Profile Wizard On Demand only To add a new profile: 1. Log into WebTrends. 2. Select Web Analysis > Profiles & Reports. Click New Profile in the upper right corner of the profiles list that opens. The Profile Class dialog box opens. 124 WebTrends Installation and Configuration Guide

125 Profile Class 3. At Choose The Type Of Profile To Create, select one of the following options: Standard Select this for standard web content. Parent-Child Select this to create a Parent profile. Parent-Child profiles enable you to automatically split a log file into multiple Child log files so that you can analyze and report on multiple domains contained in one or more log files. Parent-Child profiles can be created in two forms: - Basic Analysis (SmartSource Files Only) Select this to create a Parent profile that uses SDC tags to configure profile settings such as advanced features, filters, and campaigns. Basic Analysis more fully automates profile creation by using SDC tags embedded in web site pages to configure standard profile settings. Individual customers will need to include the SDC tags in the pages they want to associate with advanced features or other settings. Because Basic Analysis relies on SDC tags to configure profile settings, rather than the user interface, several tabs and other options will be missing when you edit an Basic Analysis profile. - Full-featured Analysis Select this to create a Parent profile that has all the standard profile settings available for configuration. Full Featured Analysis uniformly applies any standard profile settings configured for the Parent profile s advanced feature settings, filters, campaigns, etc., to all of its Child profiles. In effect, the Parent profile settings function as a "template" that is applied to the associated Child profiles. To customize any of these settings for an individual Child profile, you edit the Child profile. 4. Click Next. Note: The options you see in the Profile Class dialog box depend on your licenses and may be different from what is shown. For more information on additional features, contact NETIQ support at Profile Setup 125

126 General Use the General dialog box to specify a description for the profile, the portion of the log file to analyze, the time zone to apply to reports, administrator-specific settings, and the treatment of HTML titles. 1. Type a name to identify this profile. This profile name appears in the profiles list on the Admin Console and is used as the default profile title in reports. 2. Specify whether to analyze the log from the beginning or from the specified date. From Start Of Log File(s) Select this to analyze all dates in the log file. From The Following Date Select this to analyze the log file beginning with the date specified. Enter the date using the mm/dd/yyyy format. For example, March 10th, 2004 would be typed as 03/10/ To override the GMT (Greenwich Mean Time) offset for the WebTrends server, complete the following: Note: This feature is used for log files that are local time only. It doesn't apply to W3C log files or any log files that have a time zone offset in them. Select the Override The GMT Offset To Use For Processing Reports check box. In the text box that appears, enter the offset value, in hours, that you want the WebTrends software to use. Note: To adjust for times moving west from GMT, use a positive value. To adjust for times moving east from GMT, use a negative value. 4. Click Next. 126 WebTrends Installation and Configuration Guide

127 About General settings About Step 3 GMT offsets Note: This feature is used for log files that are local time only. It doesn t apply to W3C log files or any log files that have a time zone offset in them. By default, WebTrends uses the time zone of the server you are running the analysis on. Use the Time Zone fields to adjust for differences between the time zones where the log files are created and where they are analyzed. This helps to create more accurate reports. Note: To adjust for times moving west from GMT, use a positive value. To adjust for times moving east from GMT, use a negative value. Parent-Child configuration Use the Parent-Child Configuration dialog box to specify what criteria to use to split log file data into child profile data, which Child profiles to create, and how to operate the Parent profile in relation to the Child profiles. 1. For Child Profile Identification, select one of the following criterion for automatically splitting the log file data into child profile data: Domain. Select this to split the log file data into child profile data based on the domain. SmartSource Site ID. Select this to split the log file data into child profile data based on the SDC Site ID. URL Query Parameter Value. Select this to split the log file data into Child profile data based on URL query parameter values. In the Split Param text box, type the URL query parameter value to use to split the log file data. URL. (Does not support Auto-discovery.) Select this to split the log file into Child log files based on the URL. When you select this criterion, you must manually create the Child profiles, using the Configure Child Profiles dialog box. Note: This option is only available with Full-featured Analysis profiles. Profile Setup 127

128 2. When splitting the log files, specify which Child profiles to include or exclude in the text box provided. Enter string that will be matched. Only strings that match the string you enter are valid. 3. For Parent Profile Settings, select from the following options, which are applied by the parent profile when it identifies and analyzes Child profiles: Non-RegEx Patterns Should Parse For Multiple Items. Select this if you are not using regular expressions to define your split criteria and you have multiple expressions that you are parsing for. This selection is usually used when Domain is the split criterion. Once you have selected this check box, the Delimiter For Multiple Patterns text box opens. Delimiter For Multiple Patterns. Type the character used to separate multiple entries in the match pattern you specified your analysis software to use if you decided to split log files using non-regular expressions. This prevents your analysis software from viewing your non-regular expression as one long string. Notes: This option is only available with Full-featured Analysis profiles. This option is not available for Express Analysis profiles. Type the character used to separate multiple entries in the Split Parameter test box above, if you're splitting by URL query parameter value, or the Match Pattern text box in the Child Profile General Settings dialog box, if you're splitting by other values such as domains or SmartSource site IDs. This prevents WebTrends from viewing your non-regular expression as one long string. For example, you're splitting by URL query parameter value and your parameter value is pagea.asp?mysplitparam=cameras;radios. Select the Delimiter For Multiple Patterns check box and specify a semicolon (;) as the delimeter. WebTrends will automatically discover the two child profiles of cameras and radios. Delete Split Logs After Child Analysis Complete. Select this to delete each child log file after its profile analysis has finished. Note: This option is only available with Full-featured Analysis profiles. 128 WebTrends Installation and Configuration Guide

129 For The Next Analysis Pass, Create Profile Configurations, But Do Not Split/Analyze. Select this to only create Child profiles. Splitting and analyzing log file data will not be done with this option. This is helpful when you have hundreds of domains and want to be sure that they split correctly before using system resources for analysis. Note: This option is not available with Full-featured Analysis profiles that identify their Child profiles by URL. Include Express Analysis Roll-up Report. Select this to include a single report containing all of the individual child reports. The Roll-up report does not replace individual child reports but is in addition to them. Note: This option is only available with Basic Analysis profiles. For examples of parent-child configuration files, please see the Profiles chapter in the Technical Reference Guide. Data Sources This dialog box appears when you specified in the Site Configuration dialog box that your log files are on one physical machine. To review site configuration settings, see Site Configuration on page 133. Use this dialog box to specify which data sources to include in this profile's analysis. Note: You must create your data sources before you create any profiles that will use them. To create data sources for WebTrends profiles, select Administration > Data Sources. To create data sources for WebTrends On Demand profiles, click the Data Sources link on the left side of the On Demand Admin Console then click Add Data Source. 1. Data Source. Lists the name of the data sources (and additional information, such as the servers). To choose from this list: a. From the Select Log Data Sources list, select the check boxes to the left of the log data sources that you want included with this profile. b. If necessary, add or edit existing log data sources as needed for this profile. 2. Additional columns list each data source s corresponding information: Profile Setup 129

130 Content. Lists the type of content for this data source: Web Server, Streaming Media Server, or SmartSource Data Collector. Format. Lists the format for this data source. To work with this information, use these buttons: View Data Source. Click this to view details about the corresponding data source. Select All. Lets you select all data sources. Select None. Lets you deselect all data sources. 3. Click OK then OK again to confirm saving your changes. You see the selected log data sources listed. 4. Click Next. Home Use the Home dialog box to define the location and file name of your web site s home page. If you re creating a Stream profile, you only need to complete step 2. The other options are not available. Note: Entering this information is optional but it is recommended that you do it because it defines the location of your web server home page regardless of the existence of any subdomains on which you may be reporting. To specify home page location and file names: 1. In the Home Page File Names text box, include the file names that the web server defaults to when a visitor enters a URL without entering a specific file name. Remove any existing file names that don t apply and type any new names that are needed. Separate multiple file names with spaces. You can type up to 255 characters. 2. In the Web Site URL text box, specify the URL to the root of your web site, including the access method ( ftp://, or file:///). Note: If this text box is left blank, you can t retrieve HTML page titles for this profile unless the log file is a multi-homed domain log file. 3. If your server requires user authentication, type the Username and Password in the appropriate text boxes. 130 WebTrends Installation and Configuration Guide

131 4. Click Next. About Step 1 Home page file names 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. About Step 2 Web Site URL The following examples illustrate the results when your home page file name is default.htm and the Web Site URL is specified as A hit to is identified as: A hit to is identified as: Launching the New Profile Wizard Software only To add a new profile: 1. Log into WebTrends. 2. Select Web Analysis>Profiles & Reports. Click New Profile in the upper right corner of the profiles list that opens. The Profile Class dialog box opens. Profile Class 3. At Choose The Content To Be Analyzed By This Profile, select one of the following options: Web Server Select this for analyzing standard web server log files. SmartSource Data Collector (SDC) Select this for analyzing log files containing SmartSource tags. Profile Setup 131

132 Streaming Media Server Select this for analyzing streaming media server log files. 4. At Choose The Type Of Profile To Create, select one of the following options: Standard Select this for standard web content. Data Source Splitter Select this to use Data Source Splitter (DSS) definitions in the analysis. You have to create the DSS definitions before you can create an DSS profile. If there are no DSS definitions, this option is not available. Parent-Child Select this to create a Parent profile. Parent-Child profiles enable you to automatically split a log file into multiple Child log files so that you can analyze and report on multiple domains contained in one or more log files. Parent-Child profiles can be created in two forms: - Basic Analysis (SmartSource Files Only) Select this to create a Parent profile that uses SDC tags to configure profile settings such as advanced features, filters, and campaigns. Basic Analysis more fully automates profile creation by using SDC tags embedded in web site pages to configure standard profile settings. Individual customers will need to include the SDC tags in the pages they want to associate with advanced features or other settings. Because Basic Analysis relies on SDC tags to configure profile settings, rather than the user interface, several tabs and other options will be missing when you edit an Basic Analysis profile. - Full-featured Analysis Select this to create a Parent profile that has all the standard profile settings available for configuration. Full Featured Analysis uniformly applies any standard profile settings configured for the Parent profile s advanced feature settings, filters, campaigns, etc., to all of its Child profiles. In effect, the Parent profile settings function as a "template" that is applied to the associated Child profiles. To customize any of these settings for an individual Child profile, you edit the Child profile. 5. Click Next. Note: The options you see in the Profile Class dialog box depend on your licenses and may be different from what is shown. For more information on additional features, contact NETIQ support at WebTrends Installation and Configuration Guide

133 About Profile Type settings About Step 3 Supported Streaming Media servers WebTrends software can analyze the log files of the following media servers: RealMedia QuickTime Windows Media The formats of these log files will be auto-detected. These formats will be added to the list of supported formats in the UI, even though these formats are auto-detected. Note: WebTrends software does not support extended features such as error logging and SML. Site Configuration Use the Site Configuration dialog box to specify where your web site's log files are stored and the number of servers on which your web site resides. If you use the WebTrends Warehouse program, you need to specify that your log files are in the WebTrends Warehouse. 1. Select where to store the log files: If you re not using the WebTrends Warehouse program, select Web Site Logs Are Stored In Log Files. If you re using the WebTrends Warehouse program, select Web Site Logs Are Stored In A WebTrends Warehouse. 2. Specify your site s configuration: If your web site resides on one server, select My Web Site Is On One Physical Machine. If your web site resides on more than one server, select My Web Site Is On Multiple Physical Machines. With the ClusterTrends Add-On, WebTrends software can analyze web site activity for sites that reside on multiple servers. Profile Setup 133

134 3. Click Next. General Use the General dialog box to specify a description for the profile, the portion of the log file to analyze, the time zone to apply to reports, administrator-specific settings, and the treatment of HTML titles. 1. Type a name to identify this profile. This profile name appears in the profiles list on the Admin Console and is used as the default profile title in reports. 2. Specify whether to analyze the log from the beginning or from the specified date. From Start Of Log File(s) Select this to analyze all dates in the log file. From The Following Date Select this to analyze the log file beginning with the date specified. Enter the date using the mm/dd/yyyy format. For example, March 10th, 2004 would be typed as 03/10/ To override the GMT (Greenwich Mean Time) offset for the WebTrends server, complete the following: Note: This feature is used for log files that are local time only. It doesn't apply to W3C log files or any log files that have a time zone offset in them. Select the Override The GMT Offset To Use For Processing Reports check box. In the text box that appears, enter the offset value, in hours, that you want the WebTrends software to use. Note: To adjust for times moving west from GMT, use a positive value. To adjust for times moving east from GMT, use a negative value. By default, WebTrends uses either the time zone of the server you are running the analysis on or the time zone specified on Web Analysis > Options > Analysis > General. Selecting this override option helps create more accurate reports if the time zone where your log files are created differs from where they are analyzed. 134 WebTrends Installation and Configuration Guide

135 4. Type the name for this profile's file in the Profile File Name text box. This name is listed in the Profile Statistics section below the list of profiles on the Admin Console. Note: You can not change this name once the profile has been created. 5. Select the HTML Titles option to capture web page titles for inclusion in reports. Note: Retrieving page titles can slow report creation. Choose this option only when it is important to identify HTML pages by their titles. 6. SmartSource Profiles only: The Express Analysis option: Select this to make enable this profile for Express Analysis. 7. Click Next. About General settings About Step 3 GMT offsets Note: This feature is used for log files that are local time only. It doesn t apply to W3C log files or any log files that have a time zone offset in them. By default, WebTrends uses the time zone of the server you are running the analysis on. Use the Time Zone fields to adjust for differences between the time zones where the log files are created and where they are analyzed. This helps to create more accurate reports. Note: To adjust for times moving west from GMT, use a positive value. To adjust for times moving east from GMT, use a negative value. Parent-Child configuration Use the Parent-Child Configuration dialog box to specify what criteria to use to split log file data into child profile data, which Child profiles to create, and how to operate the Parent profile in relation to the Child profiles. Profile Setup 135

136 1. For Child Profile Identification, select one of the following criterion for automatically splitting the log file data into child profile data: Domain. Select this to split the log file data into child profile data based on the domain. SmartSource Site ID. Select this to split the log file data into child profile data based on the SDC Site ID. URL Query Parameter Value. Select this to split the log file data into Child profile data based on URL query parameter values. In the Split Param text box, type the URL query parameter value to use to split the log file data. URL. (Does not support Auto-discovery.) Select this to split the log file into Child log files based on the URL. When you select this criterion, you must manually create the Child profiles, using the Configure Child Profiles dialog box. Note: This option is only available with Full-featured Analysis profiles. 2. When splitting the log files, specify which Child profiles to include or exclude. For Valid Auto-discovered Child Profiles, select one of the following: Note: These options are not available when identifying Child profiles by URL. Always. Select this to create all possible Child profiles based on the Child Profile Identification criteria. Except For Specific Identification Strings. Select this option and you see the Identification Strings button. Click this button and in the Valid Child Identification Strings dialog box, specify the strings that identify the child profiles that you do not want to create. Type in the small text box on the right and click Add to specify the identification strings to be excluded. To remove an identification string from the list, select the string and click Remove. Only For Specific Identification Strings. Select this option and you see the Identification Strings button. Click this button and in the Valid Child Identification Strings dialog box, specify the strings that identify the child profiles to be created. Type in the small text box on the right and click Add to specify the identification strings to be included. To remove an identification string from the list, select the string and click Remove. 3. For Parent Profile Settings, select from the following options, which are applied by the parent profile when it identifies and analyzes Child profiles: 136 WebTrends Installation and Configuration Guide

137 Non-RegEx Patterns Should Parse For Multiple Items. Select this if you are not using regular expressions to define your split criteria and you have multiple expressions that you are parsing for. This selection is usually used when Domain is the split criterion. Once you have selected this check box, the Delimiter For Multiple Patterns text box opens. Delimiter For Multiple Patterns. Type the character used to separate multiple entries in the match pattern you specified your analysis software to use if you decided to split log files using non-regular expressions. This prevents your analysis software from viewing your non-regular expression as one long string. Notes: This option is only available with Full-featured Analysis profiles. This option is not available for Express Analysis profiles. Type the character used to separate multiple entries in the Split Parameter test box above, if you're splitting by URL query parameter value, or the Match Pattern text box in the Child Profile General Settings dialog box, if you're splitting by other values such as domains or SmartSource site IDs. This prevents WebTrends from viewing your non-regular expression as one long string. For example, you're splitting by URL query parameter value and your parameter value is pagea.asp?mysplitparam=cameras;radios. Select the Delimiter For Multiple Patterns check box and specify a semicolon (;) as the delimeter. WebTrends will automatically discover the two child profiles of cameras and radios. Delete Split Logs After Child Analysis Complete. Select this to delete each child log file after its profile analysis has finished. Note: This option is only available with Full-featured Analysis profiles. For The Next Analysis Pass, Create Profile Configurations, But Do Not Split/Analyze. Select this to only create Child profiles. Splitting and analyzing log file data will not be done with this option. This is helpful when you have hundreds of domains and want to be sure that they split correctly before using system resources for analysis. Note: This option is not available with Full-featured Analysis profiles that identify their Child profiles by URL. Profile Setup 137

138 Include Express Analysis Roll-up Report. Select this to include a single report containing all of the individual child reports. The Roll-up report does not replace individual child reports but is in addition to them. Note: This option is only available with Basic Analysis profiles. For examples of parent-child and Data Source Splitter configuration files, please see the Profiles chapter in the Technical Reference Guide. Data Sources: multiple machines If you specified in the Site Configuration dialog box that your log files are on multiple physical machines, this dialog box appears. Use this box to specify which servers to include in this analysis. To review site configuration settings, see Site Configuration on page 133. This dialog box opens listing currently available data sources. To specify servers and their corresponding log file paths: 1. Add any appropriate servers. a. Click New Server. You see the New Cluster Server dialog box. b. For Server Name(s), type the name of the server to be added. c. From the Data Source list, select the check boxes to the left of the log data sources that you want included with this server. d. If necessary, add or edit existing data sources as needed for this profile. Note: For information on managing data sources, please refer to the Admin Console online Help. e. Click Done. 2. Edit any existing server s information. a. From the Server Name(s) list, select the server. 138 WebTrends Installation and Configuration Guide

139 b. Click Edit. c. Make appropriate changes. d. Click OK. 3. Delete any listed servers that you do not want included in this analysis. a. From the Server Name(s) list, select the server. b. Click Delete. c. You are asked to confirm the deletion. d. Click OK. 4. Click Next. Data Sources: single machine This dialog box appears when you specified in the Site Configuration dialog box that your log files are on one physical machine. To review site configuration settings, see Site Configuration on page 133. Use this dialog box to specify which data sources to include in this profile's analysis. Note: You must create your data sources before you create any profiles that will use them. To create data sources for WebTrends profiles, select Administration > Data Sources. To create data sources for WebTrends On Demand profiles, click the Data Sources link on the left side of the On Demand Admin Console then click Add Data Source. 1. Data Source. Lists the name of the data sources (and additional information, such as the servers). To choose from this list: a. From the Select Log Data Sources list, select the check boxes to the left of the log data sources that you want included with this profile. b. If necessary, add or edit existing log data sources as needed for this profile. 2. Additional columns list each data source s corresponding information: Content. Lists the type of content for this data source: Web Server, Streaming Media Server, or SmartSource Data Collector. Format. Lists the format for this data source. Profile Setup 139

140 To work with this information, use these buttons: View Data Source. Click this to view details about the corresponding data source. Select All. Lets you select all data sources. Select None. Lets you deselect all data sources. 3. Click OK then OK again to confirm saving your changes. You see the selected log data sources listed. 4. Click Next. Home Use the Home dialog box to define the location and file name of your web site s home page. If you re creating a Stream profile, you only need to complete step 2. The other options are not available. Note: Entering this information is optional but it is recommended that you do it because it defines the location of your web server home page regardless of the existence of any subdomains on which you may be reporting. To specify home page location and file names: 1. In the Home Page File Names text box, include the file names that the web server defaults to when a visitor enters a URL without entering a specific file name. Remove any existing file names that don t apply and type any new names that are needed. Separate multiple file names with spaces. You can type up to 255 characters. 2. In the Web Site URL text box, specify the URL to the root of your web site, including the access method ( ftp://, or file:///). Note: If this text box is left blank, you can t retrieve HTML page titles for this profile unless the log file is a multi-homed domain log file. 3. If your server requires user authentication, type the Username and Password in the appropriate text boxes. 4. Click Next. 140 WebTrends Installation and Configuration Guide

141 About Home settings Note: To retrieve page titles, you must turn on the titles option. To do that, from the Admin Console, select the Options > General tab > Retrieve HTML Page Titles check box. About Step 1 Home page file names 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. About Step 2 Web Site URL The following examples illustrate the results when your home page file name is default.htm and the Web Site URL is specified as A hit to is identified as: A hit to is identified as: Schedule Use the Schedule dialog box to specify when and how frequently this event will run. Note that the Scheduler dialog box has two different modes, Regular and Advanced Mode. If you're scheduling a single event, use Regular Mode. If you're scheduling multiple events, use Advanced Mode. Note that the scheduled events you specify here apply to this profile. If you want to schedule events for a number of profile at the same time, then return to the Admin Console and click Scheduler > Scheduled Events > Scheduler. Profile Setup 141

142 Multiple schedules can apply to a single event. For example, you may wish to schedule an event to run at the same time Monday through Friday in order to track weekday activity. By creating a second schedule to run one hour before a monthly meeting in which this activity information in relevant, you could arrange to supply the latest data exactly when you need it. You can create and manage multiple schedules using the Advanced mode of schedule creation. To create a single schedule, do the following: 1. In the Run Event drop-down list, select a schedule type (Daily, Weekly, Monthly, Once, or Repeated) depending on how often you want the event to run. 2. Follow the directions below for creating that type of schedule. To create multiple schedules, do the following: 1. Click the Advanced Mode hyperlink. The current list of schedules is shown. 2. To start adding a schedule, click Add Entry. 3. In the Run Event drop-down list, select a schedule type (Daily, Weekly, Monthly, Once, or Repeated) depending on how often you want the event to run. 4. Follow the directions below for creating that type of schedule. 5. When the schedule is edited to your specifications, click Apply Changes. Your new schedule appears in the list. To edit the list of schedules in Advanced mode: 1. To edit an existing schedule, click and edit the schedule settings. Click Apply Changes to save your changes and return to the list. 2. To delete a schedule, click. The schedule is removed from the list. To create a daily schedule: 1. In the Run Event drop-down list, select Daily. 2. In the Start Time text box, type the time when you want the event to run. The format is hh:mm; for example, type 5:15 p.m. as 17: In the Start Date text box, type the date when you want the event to run. The format is mm/dd/yyyy, where June 20, 2002 would be entered as 06/20/ From the Run Daily area, choose one of the following options: Click Every [blank] days and fill in the text box to choose a custom interval in days. For instance, choose 2 days to run the event every other day. 142 WebTrends Installation and Configuration Guide

143 Click Weekdays to run the event every day, Monday through Friday. Click Every day to run the event every day, Monday, through Sunday. 5. Do one of the following: If you are editing an existing event: Click Save to save your changes. Click Cancel to abandon your selections and return to the List of Scheduled Events. If you are in the new event wizard: Click Previous to return to the preceding dialog box. Click Next to continue to the next dialog box. Click Cancel to abandon your selections and return to the List of Scheduled Events. To create a weekly schedule: 1. In the Run Event drop-down list, select Weekly. 2. In the Start Time text box, type the time when you want the event to run. The format is hh:mm; for example, type 5:15 p.m. as 17: In the Start Date text box, type the date when you want the event to run. The format is mm/dd/yyyy, where June 20, 2002 would be entered as 06/20/ From the Run Weekly check boxes, select the day(s) of the week on which you want the event to run weekly. 5. Do one of the following: If you are editing an existing event: Click save to save your changes. Click Cancel to abandon your selections and return to the List of Scheduled Events. If you are in the new event wizard: Click Previous to return to the preceding dialog box. Click Next to continue to the next dialog box. Click Cancel to abandon your selections and return to the List of Scheduled Events. Profile Setup 143

144 To create a monthly schedule: 1. In the Run Event drop-down list, select Monthly. 2. In the Start Time text box, type the time when you want the event to run. The format is hh:mm; for example, type 5:15 p.m. as 17: In the Start Date text box, type the date when you want the event to run. The format is mm/dd/yyyy, where June 20, 2002 would be entered as 06/20/ From the Run Monthly area, choose one of the following options: Click Day [blank] of the month and fill in the text box to choose a date when the event will run. Click the [ordinal] [weekday] of the month to run the event on the first, second, third, or fourth occurrence in the month of a given weekday. The default is the First Sunday of each month. 5. Select one or more check boxes to choose the months when you want to run the event. 6. Do one of the following: If you are editing an existing event: Click Save to save your changes. Click Cancel to abandon your selections and return to the List of Scheduled Events. If you are in the new event wizard: Click Previous to return to the preceding dialog box. Click Next to continue to the next dialog box. Click Cancel to abandon your selections and return to the List of Scheduled Events. To schedule an event to run once: 1. In the Run Event drop-down list, select Once. 2. In the Start Time text box, type the time when you want the event to run. The format is hh:mm; for example, type 5:15 p.m. as 17: In the Start Date text box, type the date when you want the event to run. The format is mm/dd/yyyy, where June 20, 2002 would be entered as 06/20/ Do one of the following: If you are editing an existing event: 144 WebTrends Installation and Configuration Guide

145 Click Save to save your changes. Click Cancel to abandon your selections and return to the List of Scheduled Events. If you are in the new event wizard: Click Previous to return to the preceding dialog box. Click Next to continue to the next dialog box. Click Cancel to abandon your selections and return to the List of Scheduled Events. To schedule an event to run repeatedly at a specified interval: 1. In the Run Event drop-down list, select Repeated. 2. In the Start Time text box, type the time when you want the event to run. The format is hh:mm; for example, type 5:15 p.m. as 17: In the Start Date text box, type the date when you want the event to run. The format is mm/dd/yyyy, where June 20, 2002 would be entered as 06/20/ In the Repeated Event area, do the following: Type a number in the text box to determine what number of units apart the event will run. Select a time unit from the list to determine whether the event will happen minutes, hours, days, or weeks apart. 5. Do one of the following: If you are editing an existing event: Click Save to save all the changes you made in this dialog box. Click Cancel to abandon your selections and return to the List of Scheduled Events. If you are in the new event wizard: Click Previous to return to the preceding dialog box. Click Next to continue to the next dialog box. Click Cancel to abandon your selections and return to the List of Scheduled Events. Profile Setup 145

146 Host Binding and Priority Use this dialog box to designate one or more events to a host or a group of hosts. 1. Host Binding: Select the host group you want assigned to this event. If an event is "bound" to a particular group of hosts, then all events are assigned to run on hosts belonging to that group. For example, you may want to run analysis on your four fastest machines. These machines have been given the host group name of "Speedsters." Therefore, you would select "Speedsters" from the drop-down lists to bind this event to that host group. 2. Event Priority: Select the priority for this event. Since more than one event can be assigned to a group of hosts, you might find it advantageous to determine a priority for this event. Normal: Select this to process this event in the order that it enters the Event Queue. High: Select this to place this event higher in the order of events to be run. Urgent: Select this to place this event at the top of the order of events to be run. This will not cancel an event that is currently running. To find out what events are currently running, check the Event Queue. Note the host for any event listed. Pre-Analysis Processing Use the pre-analysis feature to run an application or batch file before the scheduled event starts. For example, you may decided to copy several files to a specific location before beginning analysis. Note that if you have already set this up for a specific profile when you created that profile, you can change your pre-analysis processing settings for that profile here. To use pre-analysis processing: 1. Select the Enable Pre-analysis processing check box and specify the following settings: Application: Browse or type the path to the application you want to run. Working Folder: Type the path name to the working directory. Command Line Parameters: Type any command line parameters you want to use. Command-line parameter options include: 146 WebTrends Installation and Configuration Guide

147 - 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] - ignorereturncode = true: Continue to processes and perform no comparison on return code - returncode = 0: Space- or comma-delimited string of return codes [all success or failure] - returncodetype = success: Compare resulting return codes to specified return codes with '==' or '! ='. This allows the user to have return codes be assigned as either a success or failure (defaults to success). 2. To consider application return codes, select either to ignore or to check the return codes. Select the Ignore Return Code(s). Select the Check Return Code(s). In the text box that follows, type the number of the return code. (You may need to scroll down to see the text box.) 3. Click Add. This moves the code number into the larger box to the right. To make modifications to the list of return codes, you can select Remove, Select All, De-select All, or Default. 4. Click Next. Post-Analysis Processing Use the post-analysis processing feature to run an application or batch file after the scheduled event starts. For example, you may decided to place several reports in a specific location after analysis. Note that if you have already set this up for a specific profile when you created that profile, you can change your post-analysis processing settings for that profile here. To use post-analysis processing: 1. Select the Enable Post-analysis processing check box and specify the following settings: Application: Browse or type the path to the application you want to run. Profile Setup 147

148 Working Folder: Type the path name to the working directory. Command Line Parameters: Type any command line parameters you want to use. Command-line parameter 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] - ignorereturncode = true: Continue to processes and perform no comparison on return code - returncode = 0: Space- or comma-delimited string of return codes [all success or failure] - returncodetype = success: Compare resulting return codes to specified return codes with '==' or '! ='. This allows the user to have return codes be assigned as either a success or failure (defaults to success). 2. To consider application return codes, select either to ignore or to check the return codes. Select the Ignore Return Code(s). Select the Check Return Code(s). In the text box that follows, type the number of the return code. (You may need to scroll down to see the text box.) 3. Click Add. This moves the code number into the larger box to the right. To make modifications to the list of return codes, you can select Remove, Select All, De-select All, or Default. 4. Click Next. Summary This dialog box displays the settings for this profile. If you reached this dialog box after creating a new profile (not editing an existing profile), you also see an Advanced Settings button. Use Advanced Settings to further customize your profile. Included in the tabs for these settings are tabs representing the dialog boxes that you completed in the new profile wizard. The additional tabs you see depend on choices you made in the new profile wizard. 148 WebTrends Installation and Configuration Guide

149 Please see the online help for details on configuring Advanced Settings. Editing previous settings If you are in the process of creating your profile, and upon reviewing the summary information about the profile find that your previous settings are incorrect, click Back until you get to the appropriate dialog box to change your settings. Configuration file reference For examples of Parent-Child and Data Source Splitter configuration files, please see the Profiles chapter in the WebTrends Technical Reference Guide. Profile Setup 149

150 150 WebTrends Installation and Configuration Guide

151 Chapter 8 SDC Operations and Monitoring Operations Note: If you need to read Monitoring instructions go to Monitoring on page 168. Starting and stopping the SmartSource Data Collector Before you start or stop the SDC, make sure that your environment variables are set correctly. Setting the environment variables Windows 2000/2003/XP For your SDC-enabled web server to start, WT_ROOT must be set. You can set WT_ROOT as an environment variable or as a registry entry. The register key is located in: \HKEY_LOCAL_MACHINE\SOFTWARE\WebTrends Corporation\SmartSource Data Collector The entry is located in the WT_ROOT registry value. Note that the environment variable always takes precedence over the registry value. Note: The necessary registry entry is made during installation. SDC Operations and Monitoring 151

152 Linux and Solaris For your SDC-enabled web server to start, the following environment variables must be set: WT_ROOT The SDC installation directory. Linux: This variable is set in the /etc/sysconfig/httpd script, which is sourced by the Apache controller script /usr/sbin/apachectl. Solaris: This variable is set in the <Apache_Install_Dir>/bin/envvars/ script, which is sourced by the Apache controller script <Apache_Install_Dir>/bin/apachectl. Apache-based SDC Starting and stopping Windows 2000/2003/XP To start or stop your SDC-enabled Apache server, perform one of the following steps: Open the Control Panel, select Services, and start or stop the Apache service as needed. Open a DOS Command Prompt window and enter the following commands: net start apache2 Starts the Apache server. net stop apache2 Stops the Apache server. Linux As root, use the following commands to start or stop SDC: /usr/sbin/apachectl start /usr/sbin/apachectl stop Note: If you are running the SSL-enabled version of the web server, refer to Enabling SSL on page 51 for issues related to starting and stopping the server. 152 WebTrends Installation and Configuration Guide

153 Solaris As root, use the following commands to start or stop SDC: <Apache_Install_Dir>/bin/apachectl start <Apache_Install_Dir>/bin/apachectl stop Note: If you are running the SSL-enabled version of the web server, refer to Enabling SSL on page 51 for issues related to starting and stopping the server. Error reporting Windows 2000/2003/XP To verify that your Apache server started, use the Task Manger to view the process list. You should see two Apache processes running. If the Apache server did not start correctly, you can examine the error log file: <Apache_Install_Dir>/logs/error.log Additional errors may be logged in the application log of the Windows Event Viewer. The problem will most likely be due to an error in the httpd.conf file. Linux Verify that the Apache server has started with the following command: ps ax grep httpd You should see several httpd processes listed. If the Apache server did not start correctly, you can examine the error log file: etc/httpd/logs/error_log SDC Operations and Monitoring 153

154 Solaris Verify that the Apache server has started with the following command: ps elf grep httpd You should see several httpd processes listed. If the Apache server did not start correctly, you can examine the error log file: <Apache installation directory>/logs/error_log Log file location The SDC-generated log files are placed in the directory specified in the SDC configuration file. The setting that dictates this directory is [logrotation]->logfiledir. If this directory does not exist, the SDC will create it. Errors related to the lfm_rotate utility are contained in the SDC Audit Log. If the utility is unable to log the errors in the SDC Audit Log, the errors will be logged in the Apache error log. Testing your log file If you are unsure that your log file is receiving information correctly, follow these steps to test your log file: 1. Open a web browser. 2. Type and execute the following command in the URL address field: web server domain>/dcs.gif?dcsuri=/ test.html&dcsref=xxx 3. Open the SDC-generated log file and see if it contains a hit with xxx in the cs(referer) field. 154 WebTrends Installation and Configuration Guide

155 Viewing Apache statistical information Apache contains a module that you can use to obtain statistical information for your web server. To enable this feature, follow these steps: 1. Verify that the status_module is enabled. This includes uncommenting the following to your httpd.conf file: Windows 2000/2003/XP LoadModule status_module modules/mod_status.so Note: Simply remove the # sign before each respective entry in order to accomplish this. Linux/Solaris LoadModule status_module modules/mod_status.so AddModule mod_status.c Note: Simply remove the # sign before each respective entry in order to accomplish this. 2. Uncomment the following lines to the end of your httpd.conf file (applies to Windows 2000/2003/XP, Linux, and Solaris: <Location /server-status> SetHandler server-status Order Deny,allow Deny from all Allow from.foo.com </Location> where.foo.com is your domain. Note: Simply remove the # sign before each respective entry in order to accomplish this. 3. Stop and start your Apache. 4. You can access your Apache statistics using status SDC Operations and Monitoring 155

156 Note: Hits to /server-status will not be logged in your log file but will be reported as an invalid hit in the SDC log file. Also, enabling this module may cause some performance implications. IIS-based SDC Starting and stopping To start or stop your SDC-enabled IIS web server, perform one of the following steps: Open the Control Panel, select Services, and start or stop the World Wide Web Publishing Service as needed. Open a DOS Command Prompt window and enter the following commands: net start w3svc Start the IIS web service net stop w3svc Stop the IIS web service If you have made any SDC configuration changes, you will have to stop and start the IIS Admin Service for the changes to take effect. Stopping/starting the IIS Admin Service can be accomplished by executing the following from a command prompt: net stop iisadmin /y net start w3svc Log file location The SDC-generated log files are placed in the directory specified in the SDC configuration file. The setting that dictates this directory is [logrotation]->logfiledir. If this directory does not exist or then SDC will create it. Testing your log file If you are unsure that your log file is receiving information correctly, complete the following steps to test your log file: 1. Open a web browser. 156 WebTrends Installation and Configuration Guide

157 2. Type and execute the following command in the URL address field: web server domain>/dcs.gif?dcsuri=/ test.html&dcsref=xxx 3. Open the SDC-generated log file and see if it contains a hit with xxx in the cs(referer) field. SDC audit log The SmartSource Data Collector records significant events in an audit log file. Additionally, SDC can record the events in the Event Viewer under Windows 2000/2003/XP or to the syslog logging facility under Linux or Solaris. This allows SDC to log to a centralized system log. The [auditlog] section of the SDC configuration file contains settings used to configure where to log information, and level of log information to write (refer to the Configuration Reference chaper of the WebTrends Technical Reference Guide for additional information on how to configure audit file logging). Changes to the configuration file become effective after the web server is stopped and started. Audit log location The audit log file is located in: <SDC install directory>\log\dcs.audit <SDC install directory>/log/dcs.audit The entries in the dcs.audit file have the following format: Date: #### (Windows 2000/XP) (Unix) Message Information logged in the audit log file ranges from critical errors to debug information. The debuglevel parameter in the configuration file dictates what level of messages get logged to dcs.audit. You may log errors, warnings, or both. You can configure SDC to truncate or rotate the audit log file when it reaches a specified size. This lets you conserve disk space or keep the file from growing beyond limits imposed by the operating system. The auditlimitbysize parameter file enables audit log file truncation or audit log rotation. SDC Operations and Monitoring 157

158 The auditmaxsize parameter determines how large the audit file grows before being truncated or rotated. The auditlimitbysizemethod parameter determines weather the audit log is truncated in place or rotated to a new filename. If you are truncating the audit log, he audittrimsize parameter determines how much of the audit log file is retained prior to truncation. Therefore, you can retain only the most recently written information. If you are rotating the auditlog, when the audit log reaches the auditmaxsize, it is rotated (copied) to a new name. The format of the filename is: <audit filename prefix>-yyyy-mm-dd-hh-ommss-<hostname>.<auditfilenameext> Where: YYYY - Four digit year of the first hit in the file. MM - Two digit month of the first hit in the file. DD - Two digit day of the first hit in the file. HH - Two digit hour of the first hit in the file. Ommss - Five digit number that is a combination of zero plus minutes plus seconds of the first hit in the file. hostname - The machine name of the SDC server that created the file. Example: dcs sdcd03.audit Event Viewer (Windows 2000/2003/XP) You can configure SDC to write error and warning messages to the application log in the Event Viewer. In the event header, the event Source column must contain SDC as the identifier. The event Category gives a broad indication of the type of error or warning that occurred. The event Description contains the same text that is found in the SDC audit log file. Refer to your operating system's documentation for specific details related to the Event Viewer. Figures 8-1 and 8-2 show SDC warning messages that have been written to the Event Viewer: 158 WebTrends Installation and Configuration Guide

159 Figure 8-1. Event Viewer Screen Sample Figure 8-2. Event Viewer Log Entry Explanation SDC Operations and Monitoring 159

160 Syslog (Linux or Solaris) SDC can be configured to use syslog, the logging facility that the syslogd daemon provides. To log to the system log, the syslogd daemon must be running. To verify that syslogd as been started, use the following command: Linux ps -af grep syslogd Solaris ps -elf grep syslogd If syslogd is started, you should see the syslogd process running. The system log in a file is named /var/log/messages (Linux) or /var/adm/messages (Solaris). This may vary depending on how you have configured syslogd using /etc/syslog.conf. Refer to your operating system s documentation for specific details related to syslogd. The content of a SDC message written to syslog is the same as that written to the SDC audit log file. The format is the same as any other that you would find in the system log. The identifier string SDC is prepended to messages. The systemdebuglevel parameter in the configuration file dictates what level of messages get logged to the system log. You may log errors, warnings, or both. The following examples show a SDC warning message that has been written to the system log. Linux (/var/log/messages) May 7 12:35:47 emule DCS[26461]: The following hit was discarded due to the absence of following hit parameter: dcsuri Client IP: (Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)) URI: GET /dcs.gif HTTP/1.1 Cookie: WEBTRENDS_ID= ::418AAB02984D24F04BFC7CE B2 Solaris (/var/adm/messages) May 9 11:41:28 cuervo DCS[6668]: [ID daemon.warning] The following hit was discarded due to the absence of following hit parameter: dcsuri May 9 11:41:28 cuervo Client IP: (Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)) May 9 11:41:28 cuervo URI: GET /dcs.gif HTTP/1.1 May 9 11:41:28 cuervo Cookie: WEBTRENDS_ID= ::5D9EDB0555DCD43B32588CAB5CD44F8C 160 WebTrends Installation and Configuration Guide

161 Hit count tracking Important: Hit count tracking is supported only on IIS-based installations. Once SDC is up and running, you may want to monitor the number of hits being processed. You could wait until the SDC-generated logs have been analyzed by WebTrends and then view the reports. Or you could simply monitor the size of the SDC-generated log files. A better method is to use the hit count tracking feature that is built into SDC. When hit count tracking is enabled, SDC writes hourly hit count information to the hit count log file (HCLF). The hit count flush rate dictates the timing of writes to the HCLF. When the flush rate interval expires, the HCLF is opened, written to, and closed. The HCLF is typically created when the first flush occurs. Thereafter, hit count data is appended to the HCLF. If the HCLF is deleted underneath a running SDC, another is created at the time of the next flush. Naming of Hit Count Log File by default, the HCLF resides under the SDC installation directory in the "log" subdirectory. The name of the HCLF reflects its creation time, and the machine it's running on. The naming convention is as follows: Where <Server>_<CreationTime>.hclf <Server> The machine name of the computer where SDC is running. <CreationTime> GMT time when HCLF was created. Format is of the form yyyy_mm_dd_sssss where yyyy The four-digit year mm dd The two-digit month The two-digit day sssss The five-digit number of seconds since midnight (padded with leadingzeros) and ranges from 0 to 86,398. The location of the HCLF is configurable via the [logserver]->hitcountlogfiledir setting. The filename extension of the HCLF is configurable via the [logserver]->hitcountlogfileext setting. SDC Operations and Monitoring 161

162 For example, if you selected the default SDC installation folder, your IIS-based SDC machine name is dcs01, and the HCLF was created on Thu Feb 14 11:09: , then the HCLF file name would be: C:\Program Files\WebTrends\SmartSource Data Collector\log\ dcs01_2002_02_14_68940.hclf Contents of Hit Count Log File The HCLF is an ASCII file. The first line in the file contains a header that describes the format of the hit count records. The remaining lines contain the hit count data in comma separated format. The header syntax is as follows: #entry,flush-time,interval-time,id,raw-count,proccount,type,server, agent,firsthit-time,lasthit-time Note the following descriptions of each field within a HCLF record: entry Numeric Entry number for the record (line). Each record is sequentially numbered, starting with 1 up to a maximum value of When a new HCLF is created, the entry value starts over again with the value of 1. flush-time Numeric Time when data was written. Represented as the number of seconds since the epoch (UTC). interval-time Numeric Hourly interval (bucket) in which the hits occurred. Represented as the number of seconds since the epoch (UTC). Will always be the beginning of an hour. id Alphanumeric The DCSID. The following two DCSIDs are special cases: 0 represents the sum of all successful hits for the interval represents the sum of all unsuccessful hits for the interval. raw-count Numeric The total number of hits. This is a number ranging from 1 to If no hits are received 162 WebTrends Installation and Configuration Guide

163 for a given id during the time period, then no record is written to the HCLF. proc-count Numeric Same as raw-count field. type Alphanumeric This field is always DCS. server Alphanumeric The machine name of the computer (for example, pdxdcs01) where SDC is running. Maximum length is 260 (including null terminator). agent Alphanumeric Same as server field. firsthit-time Numeric Time of first hit for a given record. Represented as number of seconds since the epoch (UTC). lasthit-time Numeric Time of last hit for a given record. Represented as number of seconds since the epoch (UTC). When a flush occurs, SDC writes out a record that contains the total number of hits during the interval. If no hits were received, then no record is written. If invalid hits occurred during the interval, an additional record containing the total number of invalid hits is written. If hosted-sdc is enabled, non-zero hit count totals for each DCSID are also written. The id field serves to distinguish between a total hit count record (id=0), an invalid hit count record (id= ), and a DCSID-specific hit record (id=<dcsid>). Examples If you ran hosted-sdc on dcs01 and did the following: Started SDC on Thursday, Feb 14, 2002 at 11:09:00 ( seconds since the epoch) Set the flush interval to 20 minutes Tracked three DCSIDs: dcsknjb24gsu7s61pxz9uww73_7x5i dcss5zx2u60f7xe4o8qw25a73_5q5w SDC Operations and Monitoring 163

164 dcs4r3tysgsu7sq4d2prrhq73_4y1j Therefore, the current interval-time is Thu Feb 14 11:00: ( seconds since the epoch). Note that for this example, hits between 11:00:00 and 11:08:59 are not counted. At 11:20:00 ( seconds since the epoch), the first flush would occur. If the successful hit counts were: DCSID Hit Count dcsknjb24gsu7s61pxz9uww73_7x5i 542 dcss5zx2u60f7xe4o8qw25a73_5q5w 26 dcs4r3tysgsu7sq4d2prrhq73_4y1j 1029 the records would look like this: 1, , ,dcsknjb24gsu7s61pxz9uww73_7x5i,542,542, DCS,dcs01,dcs01 2, , ,dcss5zx2u60f7xe4o8qw25a73_5q5w,26,26,DC S,dcs01,dcs01 3, , ,dcs4r3tysgsu7sq4d2prrhq73_4y1j,1029,102 9,DCS,dcs01,dcs01 4, , ,0,1597,1597,DCS,dcs01,dcs01 At 11:40:00 ( seconds since the epoch), the second flush would occur. If the successful hit counts were: DCSID Hit Count dcsknjb24gsu7s61pxz9uww73_7x5i 3227 dcss5zx2u60f7xe4o8qw25a73_5q5w WebTrends Installation and Configuration Guide

165 DCSID Hit Count dcs4r3tysgsu7sq4d2prrhq73_4y1j 665 the records would look like this: 5, , ,dcsknjb24gsu7s61pxz9uww73_7x5i,3227,322 7,DCS,dcs01,dcs01 6, , ,dcss5zx2u60f7xe4o8qw25a73_5q5w,877,877, DCS,dcs01,dcs01 7, , ,dcs4r3tysgsu7sq4d2prrhq73_4y1j,665,655, DCS,dcs01,dcs01 8, , ,0,4769,4796,DCS,dcs01,dcs01 At 12:00:00 ( seconds since the epoch), the third flush would occur. If the successful hit counts were: DCSID Hit Count dcsknjb24gsu7s61pxz9uww73_7x5i 809 dcss5zx2u60f7xe4o8qw25a73_5q5w 1165 dcs4r3tysgsu7sq4d2prrhq73_4y1j 6244 and there were 4 invalid hit counts. The records would look like this: 9, , ,dcsknjb24gsu7s61pxz9uww73_7x5i,809,809, DCS,dcs01,dcs01 10, , ,dcss5zx2u60f7xe4o8qw25a73_5q5w,1165,1165,DCS,dcs01,dcs01 11, , ,dcs4r3tysgsu7sq4d2prrhq73_4y1j,6244,6244,DC S,dcs01,dcs01 12, , ,0,8218,8218,DCS,dcs01,dcs01 13, , , ,4,4,DCS,dcs01,dcs01 At 12:20:00 ( seconds since the epoch), the third flush would occur. If the successful hit counts were: SDC Operations and Monitoring 165

166 DCSID Hit Count dcsknjb24gsu7s61pxz9uww73_7x5i 0 dcss5zx2u60f7xe4o8qw25a73_5q5w 901 dcs4r3tysgsu7sq4d2prrhq73_4y1j 622 the records would look like this: 14, , ,dcss5zx2u60f7xe4o8qw25a73_5q5w,901,901,D CS,dcs01,dcs01 15, , ,dcs4r3tysgsu7sq4d2prrhq73_4y1j,622,622,DCS, dcs01,dcs01 16, , ,0,1523,1523,DCS,dcs01,dcs01 Note that there is no record for DCSID dcsknjb24gsu7s61pxz9uww73_7x5i because its hit count was zero. Configuration Configure by modifying HCLF-related settings in the SDC configuration file (dcs.cfg). Enable hit count tracking trackhitcount [logserver section] Boolean that determines if hit count tracking is enabled. The default value for this setting is false. 166 WebTrends Installation and Configuration Guide

167 Configure rotation The HCLF may be rotated by size and/or by number of times flushed. For flush-rate-based rotation, set hitcountrotatebyflush=true and set hitcountflushesperrotation to the number of flushes performed before the file is rotated. Note that flushes occur periodically based on the hitcountflushrate stetting. hitcountrotatebyflush [logserver section] Boolean used to indicate if flush-based rotation is enabled. The default is false. hitcountflushesperrotation [logserver section] Integer that determines the number of flushes that occur before an HCLF is rotated. Only applies if hitcountrotatebyflush is true. The default is 3. For size-based rotation, set hitcountlimitbysize=true, and set hitcountmzxsize to the maximum size of the file (in MBs). hitcountlimitbysize [logserver section] Boolean used to indicate if size-based rotation is enabled. Only applies if trackhitcount is true. The default is false. hitcountmaxsize [logserver section] Integer that determines the maximum size (in megabytes) of the HCLF. Only applies if hitcountlimitbysize is true. The default is 1. Advanced configuration While the default settings provide an operational SDC with hit count tracking, the hit count tracking settings listed below may need to be modified for your installation. Note that changes to the dcs.cfg file are not recognized until the web server is stopped and started. hitcountflushrate [logserver section] The number of minutes to elapse between hit count log file writes. Valid values are: 2, 3, 5, 6, 10, 12, 20, 30. The default and value for this setting is 20. This ensures that no more than 20 minutes of hit count data would be lost as a result of a catastrophic event. SDC Operations and Monitoring 167

168 Monitoring The environment in which the SDC operates is a critical component of a successful installation. To reduce the risks of data loss, the SDC must be deployed in an environment that provides for high availability. This includes, but is not limited to, items such as incorporating the appropriate redundancy and alerting and monitoring. While the configuration and setup of an environment that provides high availability is outside the scope of this document (and the SDC product), the following list identifies several of the key SDC-related items that should be monitored. 1.The system resources on the machine hosting the SDC (for example, CPU, memory, disk space) 2.The SDC plug-in (to determine if it is installed) 3.The health of the web server hosting the SDC, including the ability of the web server to correctly respond to an HTTP request 4.The SDC log file Regarding item 1, you can use commonly available tools along with specific characteristics of the SDC to monitor each of these items. For example, you can monitor the system resources by using a variety of system management tools such as NetIQ's AppManager. Regarding items 2 through 4, you can use commonly available tools in combination with the following SDC characteristics to aid in the monitoring process: The content returned to a web client in response to a valid SDC request is generated by a URL re-mapping process. Hits to the dcs.gif file are remapped to wt_dcs.gif. The SDC plug-in performs the re-mapping. If the SDC plug-in is installed and the web server is functioning, hits to dcs.gif produce an HTTP response with a successful status code. Valid hits to the SDC are logged in a log file, which is found in a configurable location. 168 WebTrends Installation and Configuration Guide

169 Installation monitoring To determine if the SDC plug-in is installed and to ascertain the general health of the web server, a configuration may include the use of an external monitoring agent that periodically sends valid HTTP requests to the SDC. If the SDC returns a valid response with a successful HTTP status code, there is a high likelihood that the web server is in a good state and the SDC is properly installed. This determination is based on the URL re-mapping process performed by the SDC and the general nature of HTTP web servers. Log file monitoring The most important artifact of the SDC product is the successful creation and continued generation of the SDC log file. All valid hits to the SDC should be written to the resultant log file. Before describing a suggested monitoring configuration, however, the behavior of the SDC logging mechanism must be understood. The following subsections describe this behavior. Hit validation All hits to the SDC are validated. In most cases, invalid hits are not recorded in the SDC log file. The following list describes several types of validation: The uri-stem of the hit to the SDC must tail-match a valid logging file name. The valid logging file names are determined by the values of the loggingfilename/ noscriptfilename settings found in the dcs.cfg. file. These values are typically dcs.gif and njs.gif. If the SDC is operating in the hosted model, the DCSID is validated. The dcsidbacktoversin configuration file setting determines which version(s) of DCSIDs are valid. See the Hosted-Model SDC chapter of the WebTrends Technical Reference Guide for more information. If SDC cookies are enabled and cookie validation is turned on, the contents of the SDC cookies are validated. Note that hits associated with invalid cookies can still be logged by the SDC if the logging of invalid hits is enabled. The required parameters to the SDC hit are present. The DCS_URI (typically dcsuri) is the only parameter that must be in the hit to the SDC. Others parameters can be required via configuration of the SDC. SDC Operations and Monitoring 169

170 Log file name Valid hits to the SDC are recorded in the SDC log file. The name is based on rotation period (rotationperiod) and the log file prefix (logfileprefix) settings found in the dcs.cfg file. The file is located in the directory specified by the log file directory (logfiledir) setting. If log file rotation by size is enabled, the file name may include a rotate-by-size count. Also, if the SDC is operating in the hosted model and log-file-splitting is enabled, the numeric portion of the DCSID becomes a prefix to the file name, as shown in the following syntax: where [DCSID_]<Log File Prefix>_<Date>[(Size Rotation Counter)].log DCSID The DCSID (hosted model with splitlogs enabled) Log File Prefix The value of the logfileprefix setting Date The rotation period indicator based on the value of the rotationperiod setting Size Rotation Counter If a log file is rotated based on size, a rotation counter is appended to the date portion of the log file name. For example, if the SDC is configured to rotate daily and the log file prefix is sdc, the following file will be generated on February 25, 2002: sdc_feb_25_2002.log If the log file rotates by size during the day, the file name would be: sdc_feb_25_2002(2).log If hosted model and log file splitting are enabled, hits to the DCSID dcsknjb24gsu7s61pxz9uww73_7x5i would be recorded in: dcsknjb24gsu7s61pxz9uww73_7x5i_sdc_feb_25_2002.log If servicemodel is enabled, then naming is quite different. See the Hosted-Model SDC chapter of the WebTrends Technical Reference Guide for more information. 170 WebTrends Installation and Configuration Guide

171 Log file rotation Log file rotation is the process of recording log hits in different files based on specific criteria. For the SDC, the criteria are time and/or size of file. With time-based rotation, the log file is rotated on time-based intervals (such as on a daily basis.) With size-based rotation, the log file is rotated when it reaches a certain file size. Time and size rotation can be used together. Logging behavior The behavior of the logging component of the SDC is important when monitoring the resultant log file. The most critical issue to consider is the time when the hit information is actually written to disk. This varies based on the hosting web server. SDC has its own logging component. You can configure the behavior of this component based on setting found in the dcs.cfg file. The configuration covers the following: Buffered writes vs. non-buffered writes If buffered writes, the size of the buffer The amount of time between flushes, allowing you to limit the time hit data remains in the internal buffer before it is flushed to disk. As hits are processed by the SDC, they are passed to the log file controller. Based on SDC configuration, the hits are either immediately written to disk or placed in an internal buffer. If buffered writes are enabled, the internal buffer grows until the buffer reaches a configurable size. At that time, the hit data is written to disk. Periodically (as specified by the heartbeatrate and bufferflushrate settings), a check is made for buffers that have data in them but have not been flushed in a time exceeding the buffer flush rate. If this situation is detected, the buffer is flushed to disk. Monitoring the log file With an understanding of the behavior of your SDC log files, you may employ the use of one of many commonly available monitoring tools to monitor the logging component. While the configuration will vary depending on the monitoring tool you choose, the following example setup provides a high-level overview of a potential setup. SDC Operations and Monitoring 171

172 The example setup includes an agent that makes HTTP requests to the SDC and another agent that monitors the size of the data in the SDC log file. The HTTP agent periodically sends valid requests to the SDC. At a rate greater than or equal to the rate of the HTTP requests, the other monitoring agent verifies that the SDC log file has grown. This sizemonitoring agent must also take into consideration the issues associated with buffered vs. non-buffered writes. If the log file does not grow as expected, the monitoring agent must take the action appropriate for your SDC installation. This may be as simple as generating an alert to removing the particular machine from a farm of SDC servers. When implementing a log file monitor, the following key issues should be considered: The agent must be aware of the log file naming conventions. The agent must be able to recognize SDC log file rotation. The agent must be aware of the SDC logging behavior. The agent must not interfere with the SDC. If SDC is operating in the hosted model and the resultant logs are being split, a singe valid DCSID should be used for the monitoring component. The external agent must send hits to the SDC using the appropriate DCSID. The monitoring agent then needs to monitor the growth of the log file associated with the appropriate DCSID. 172 WebTrends Installation and Configuration Guide

173 Chapter 9 Instrumenting Web Pages Overview Before deploying the provided SDC tag, you must modify a snippet of scripting code (instrumentation) so that hits are directed to the appropriate SDC. Since the SDC tag is a script (JavaScript or VBScript), only web pages that result in the execution of a script can be instrumented (for example,.html,.htm,.asp,.etc), using this method. The SDC JavaScript tag is described in the following section. Note: For details on customizing your JavaScript tags, please see the Customizing SDC JavaScript Tags chapter of the WebTrends Technical Reference Guide. The SDC VBScript tag is described on page 180. The HTML <META> tag is described on page 183. SDC JavaScript Tags Note: WebTrends On Demand users will receive these tags from directly WebTrends. Please see Using HTML <META> Tags on page 183 for details on implementation. The JavaScript tag file is located at: Unix <SDC Install Dir>/util/javascript/dcs_tag.js Windows 2000/2003/XP <SDC Install Dir>\util\javascript\dcs_tag.js Instrumenting Web Pages 173

174 The tag records information about the hit to the instrumented web site and subsequent forwarding of that information to the SDC. The SDC reconstructs the original hit from the query parameters and records it in a log file. The tag is JavaScript v1.1 compatible and includes a tracking function that generates a series of Image objects. The creation of the Image object causes a hit to the SDC. Through the use of an array of Image objects, many hits to the SDC from a single web page can be made in rapid succession. Particularly, this is well-suited for use with Flash applications. It should be noted that some versions of IE3 do not track the hits using this tag, because of incomplete support of JavaScript v1.1 specifically the lack of support for the Image object. SDC JavaScript tag modifications Specifying the SDC domain Before deploying the SDC JavaScript tag, you must first modify the script to match your SDC installation. The tag contains two occurrences of the character This string must be replaced with the domain of your SDC. The first occurrence is shortly after the <SCRIPT LANGUAGE= JavaScript > HTML tag. This occurrence is used to initialize a global variable named gdomain: var ; The second occurrence is found after the <NOSCRIPT> HTML tag. This occurrence is used to fill in the domain portion of the inline image request for non-javascript enable browsers. SRC= &WT.js=No Both occurrences should be replaced with the domain name (or IP address) of the SDC. Important: The JavaScript tag file must be modified in a way that preserves the integrity of the file and does not add any special formatting character or to any character conversion. 174 WebTrends Installation and Configuration Guide

175 Multi-domain tracking By default, the SDC JavaScript tag is configured to pass the content domain. This is done by assigning a value to the dcssip parameter as follows: DCS.dcssip=window.location.hostname; This sets the domain from the URL address entered into the browser. For example, a request to logs a domain of while a request to logs a domain of abxcyz.com. An alternative to using window.location.hostname is to hard code the domain name when assigning a value to dcssip. This ensures consistent results. Do this by modifying the line: DCS.dcssip=<ContentDomain>; Where <ContentDomain> represents the domain of the web site being tracked. For example, suppose you have web sites abcxyz.com and 123.com, and you want to track them with a single SDC. All pages on both web sites should include an SDC tag with the dcssip parameter set to the appropriate domain. Note the following examples: On abcxyc.com pages: DCS.dcssip="abcxyz.com"; On 123.com pages: DCS.dcssip="123.com"; Configure by hit You can configure SDC through the settings stored in the dcs.cfg configuration file. Changes to settings come into effect after the web server is stopped and started. Some settings may be overridden on a per hit basis via the SDC tag. To configure SDC on a per hit basis: 1. Enable configure by hit. Set the cfgbyhit setting to true in the [logserver] section of the dcs.cfg file. 2. Determine the identifier that corresponds with the settings to override. Instrumenting Web Pages 175

176 To override a configuration file setting, you need an identifier. The identifier is a 8-digit hexadecimal value that is interpreted by SDC. Identifiers are listed in the following table: Setting to Override Identifier Disable cookie processing To override multiple settings, perform a bitwise AND of the individual identifier values. 3. Include identifier in the JavaScript tag. 4. Configure your SDC JavaScript tag to pass the setting override for a given resource by enabling the dcscfg parameter. To enable configure by hit, add a line to the dcsvar( ) function: DCS.dcscfg=<identifier>; where Disable first time cookie detection <identfier> represents the configuration settings to override. The identifier is an 8-digit hexadecimal value that is interpreted by SDC, and affects runtime behavior. Currently, only is supported (disable cookie processing). The following example shows how to disable cookie processing: DCS.dcscfg=1; 5. In addition, you must configure the <NOSCRIPT> section by modifying SRC= to SRC= &dcscfg=<identifier> 176 WebTrends Installation and Configuration Guide

177 Issue per-hit P3P headers To issue per-hit P3P headers with SDC, you must configure your SDC JavaScript tag to pass the compact policy and/or policyref. You can do this by enabling the dcsp3p parameters. For more information on configuring SDC to issue per hit P3P headers, please see the P3P and SDC section of the SDC Configuration Reference chapter in the WebTrends Technical Reference Guide. Cache prevention To prevent caching, the web client's current time is included as a URL parameter to the hit targeted at the SDC. Each hit to the SDC server changes with time such that caching is prevented. Note that the time parameter sent to the SDC is discarded and, thus, not included in the SDC log file. To accomplish this, a JavaScript Date object is constructed. The gettime() method is used to retrieve the number of milliseconds since This is then added as a parameter to the SDC effectively preventing millisecond to millisecond caching. SDC JavaScript tag placement The SDC JavaScript tag can be located anywhere on your web page between the <BODY> </ BODY> tags. The advantage of placing the SDC JavaScript tag at the top of your web pages lies in how the cancelled pages are handled. If a page begins to load and the page load is cancelled by clicking the STOP button on the browser, the page hit may not be sent to the SmartSource Data Collector if the JavaScript code resides at the bottom of your web page. Inserting the SDC JavaScript tag You can use one of the following basic ways to insert the JavaScript tag into your web site: Include file (see page 178) Inline script (see page 179) Dynamic pages (see page 179). We recommend the include file method. Instrumenting Web Pages 177

178 Include file When you want to add the same code to numerous pages, you can use an include file that contains the JavaScript code. Using an include has a definite advantage when you must modify or upgrade the code. When you modify the code in the include file, it is automatically updated to all pages that have the include statement. You may implement the include from the client-side, or the server-side. Client-side In JavaScript 1.1 and later, you can include the contents of an external file on every page of your web site. The SRC attribute of the <SCRIPT> tag lets you specify a file as the JavaScript source. To implement using this method, save the SDC tag to a file, which is accessible to every page of your site, and then reference the file in the SRC attribute in each web page. For example, suppose you saved your SDC JavaScript tag to a file named dcs_tag.js and placed it in the directory named common, which is located off of the document root. To include this file, add the following line to your web pages: <SCRIPT LANGUAGE="JavaScript1.1" SRC="/common/dcs_tag.js"> </SCRIPT> External JavaScript files cannot contain any HTML tags: they must contain only JavaScript statements and function definitions. Server-side Server-side includes (SSI) are enabled by default on Internet Information Server and Apache web servers. You can either configure the server to run SSI on all files with the extensions you use for your web pages (.htm,.html), or you may need to change your page extensions (for example, to.stm,.shtm, and.shtml). Because additional processing is required when SSI is enabled, server performance may be adversely affected. To implement this method, save the SDC tag to a file that is accessible to every page of your site, and then reference the file in the <!--#include --> statement in each web page. For example, suppose you saved your SDC JavaScript tag named dcs_tag.js, and placed it in the directory named common off of the document root. To include this file, add the following line to your web pages: <!--#include virtual="/common/dcs_tag.js"--> 178 WebTrends Installation and Configuration Guide

179 Inline script Add the entire SDC JavaScript tag to each web page (inline script). Use HTML edit mode or Notepad to insert the script. Dynamic pages Uploading common code or text on every page of a web site is one of the main reasons to use dynamic-database-driven web tools. Most of these tools contain the concept of a template which serves common code automatically. Use the built-in method in your tool. SDC VBScript Tags Note: WebTrends On Demand users will receive these tags from directly WebTrends. Please see Using HTML <META> Tags on page 183 for details on implementation. The VBScript tag file is located at: Unix <SDC Install Dir>/util/vbscript/dcs_tag.vbs Windows 2000/2003/XP <SDC Install Dir>\util\vbscript\dcs_tag.vbs The tag lets you record information about the hit to the instrumented web site and subsequently forwards that information to the SDC. The SDC reconstructs the original hit from the query parameters and records it in a log file. T This tag is compatible with Internet Explorer 5.0and includes a tracking function that generates an inline image. Use of this tag is not recommended with Flash applications (or any other scenario that would involve many tracking hits to the SDC from a single web page.) Instrumenting Web Pages 179

180 SDC VBScript tag modifications Specifying the SDC domain Before deploying the SDC VBScript tag, you must first modify the script to match your SDC installation. For each VBScript tag, there are two occurrences of which must be replaced with the domain of your SDC. The first occurrence (between the <SCRIPT> </SCRIPT> tags) handles cases in which the client is using a VBScript-enabled browser: strurl = strurl & "://@@DOMAIN@@/dcs.gif?" The second reference (between the <NOSCRIPT> </NOSCRIPT> tags) handles cases in which the browser is not Internet Explorer version 5.0 or greater: document.write "<IMG BORDER= 0 NAME= DCSIMG WIDTH= 1 HEIGHT= 1 SRC= >" Both occurrences should be replaced with the domain name (or IP address) of the SDC. Important: The VBScript tag file must be modified in a way that preserves the integrity of the file and does not add any special formatting character or to any character conversion. Multi-domain tracking To track multiple domains with SDC, you must configure your SDC VBScript tag to pass the content domain. You can accomplish this by enabling the dcssip parameter. To enable cross-domain tracking, complete either of the following steps: Modify the line strurl = strurl & "&dcssip=yourdomain" to strurl = strurl & "&dcssip=<contentdomain>" where <contentdomain> represents the domain of the web site being tracked. 180 WebTrends Installation and Configuration Guide

181 For example, if you have web sites abcxyz.com and 123.com and you want to track them with a single SDC, all pages on both web sites should include a SDC tag with the dcssip parameter set to the appropriate domain in all of their SDC tags. Note the following examples: On abcxyz.com pages: strurl = strurl & "&dcssip=abcxyz.com" On 123.com pages: strurl = strurl & "&dcssip=123.com" As an alternative to setting the dcssip variable, a less consistent but multi-domain compatible method can be used. This method involves the windows.location.hostname function. strurl = strurl & "&dcssip=" & Escape(window.location.hostname) This method sets the domain from the URL address entered in the browser. For example, a request to logs a domain of while a request to logs a domain of abxcyz.com. Configure by hit You can configure SDC through the settings stored in the dcs.cfg configuration file. Changes to settings come into effect after the web server is stopped and started. Certain settings may be overridden on a per hit basis with the SDC tag. To configure SDC on a per hit basis: 1. Enable configure by hit. Set the cfgbyhit setting to true in the [logserver] section of the dcs.cfg file. 2. Determine the identifier that corresponds with the settings to override (currently, you can disable only cookie processing). To override a configuration file setting, you need an identifier. The identifier is a 8-digit hexadecimal value that is interpreted by SDC. Identifiers are listed in the following table: Setting to Override Identifier Disable cookie processing To override multiple settings, perform a bitwise AND of the individual identifier values. Instrumenting Web Pages 181

182 3. Include identifier in the VBScript tag. Configure your SDC VBScript tag to pass the setting override for a given resource by enabling the dcscfg parameter. To enable configure by hit, modify the line strurl = strurl & "&dcscfg=yourcfg" to strurl = strurl & "&dcscfg=<identifier>" where <identfier> represents the configuration settings to override. The identifier is an 8- digit hexadecimal value that is interpreted by SDC, and affects runtime behavior. Currently, only is supported (disable cookie processing). The following example shows how to disable cookie processing: strurl = strurl & "&dcscfg= " Issue per-hit P3P headers To issue per-hit P3P headers with SDC, you must configure your SDC VBScript tag to pass the compact policy and/or policyref. You can do this by enabling the dcsp3p parameters. Refer to the P3P and SDC section of the Technical Reference Guide s Configuration chapter for more information on configuring SDC to issue per hit P3P headers. Cache prevention To prevent caching, the web client's current time is included as a URL parameter to the hit targeted at the SDC. Each hit to the SDC server changes with time such that caching is prevented. Note that the time parameter sent to the SDC is discarded and, thus, not included in the SDC log file. To accomplish this, a VBScript Date function is called. The Timer() function is used to retrieve the number of seconds since midnight. This is then added as a parameter to the SDC effectively preventing second to second caching. 182 WebTrends Installation and Configuration Guide

183 SDC VBScript tag placement The SDC VBScript tag can be located anywhere on your web page between the <BODY> </ BODY> tags. The advantage of placing the SDC VBScript tag at the top of your web pages lies in how the cancelled pages are handled. If a page begins to load and the page load is cancelled by clicking the STOP button on the browser, the page hit may not be sent to the Smart- Source Data Collector if the VBScript code resides at the bottom of your web page. Using HTML <META> Tags The SDC JavaScript tag supports the use of HTML <META> tags as a means of extending the collected data. By simply adding <META> tags with key names to your document, you can capture meta data describing your web content. To capture the meta data, the tag takes advantage of web browsers support of the Document Object Model (DOM). Based on a naming convention, WebTrends <META> tags are located via the DOM. When found, the meta information is added to the SDC hits in the form of additional query (also known as well-known) parameters. These query parameters are then used by WebTrends products during the analysis process. WebTrends query parameters are described in detail in the WebTrends Query Parameters appendix of the WebTrends Technical Reference Guide. Note: SDC support for <META> tags is limited to browsers that parse and make available the entire HTML document. This includes but is not limited to Internet Explorer 4+, Netscape Navigator 6+, and Opera 6+. For browsers without the appropriate support, the hit to the SDC is not augmented with data found in <META> tags. Syntax The general syntax of the supported <META> tag is as follows: <META NAME= name" CONTENT="content"> The <META> tag must be included within the <HEAD></HEAD> tags. The name represents the parameter name. Instrumenting Web Pages 183

184 The content represents the parameter value. It should be noted that the length of the hit to the SDC is limited in size. In modern browsers, this is limited to 2k bytes. Since the content is included as a SDC hit parameter, its length is limited in size. The additional parameters from the <META> tags are added to the SDC parameter list in the following fashion: "&"+name+"="+url-encoded content In Figure 9-1, the web client makes an HTTP request for /page.html from the Content Web Server. /page.html contains the SDC JavaScript tag along with a WebTrends <META> tag. <META NAME="WT.av" CONTENT="Fish Finder"> 184 WebTrends Installation and Configuration Guide

185 Figure 9-1. <META> tag example Instrumenting Web Pages 185

186 When /page.html is received by the web client, the SDC JavaScript tag executes. This includes searching for WebTrends <META> and if found, adding the information to the hit to the SDC. The query parameters added in this example are: &WT.av=Fish%20Finder Notice that the SDC JavaScript tag escapes the value of the CONTENT attribute. The instrumented hit is received by the SDC, processed and logged. The logged hit looks like: :06: GET /page.html WT.av=Fish%20Finder Examples This section illustrates several examples of possible scenarios involving the use of <META> tags in conjunction with the SDC. Non-compound type, single instance <HTML> <HEAD> <META NAME="WT.av" CONTENT="Finance Offer"> </HEAD> <BODY> <!-SDC Tag --> </BODY> </HTML> This is an example of a page associated with the Finance Offer advertising view. Non-compound type, multiple instances <HTML> <HEAD> <META NAME="WT.av" CONTENT="Finance Offer;FishFinder Offer"> </HEAD> <BODY> <!-SDC Tag --> </BODY> </HTML> 186 WebTrends Installation and Configuration Guide

187 This is an example of a page associated with both the Finance offer and the FishFinder Offer advertising views. Compound type, single instance <HTML> <HEAD> <META NAME="WT.cg_n" CONTENT="Marine"> <META NAME="WT.cg_s" CONTENT="Power Boats"> </HEAD> <BODY> <!-SDC Tag --> </BODY> </HTML> This is an example of a page associated with the Content Group/Sub-Content Group Marine / Power Boats. Compound type, multiple instances <HTML> <HEAD> <META NAME="WT.cg_n" CONTENT=" Marine;Marine"> <META NAME="WT.cg_s" CONTENT=" Power%20Boats;Sail%20Boats"> </HEAD> <BODY> <!-SDC Tag --> </BODY> </HTML> This is an example of a page associated with the Content Groups/Sub-Content Groups Marine / Power Boats and Marine / Sail Boats. Compound type, multiple instances with empty value <HTML> <HEAD> <META NAME="WT.cg_n" CONTENT=" Marine;FineWines"> <META NAME="WT.cg_s" CONTENT=" Power%20Boats;"> </HEAD> <BODY> <!-SDC Tag --> </BODY> </HTML> Instrumenting Web Pages 187

188 This is an example of a page associated with the Content Groups/Sub-Content Groups Marine / Power Boats and FineWines. The key is the trailing ;. This indicates that the FineWines Content Group does not have an associated Sub-Content Group. 188 WebTrends Installation and Configuration Guide

189 Index A Add on key activating 23 advanced settings for profiles 148 Report Templates 118 Apache upgrading on Windows, Linux, Unix 62 Apache Web server removing from Windows 26 statistical information 155 uninstalling from Windows 32 Apache web server installing for SDC 33 uninstalling from Linux or Unix 39 Apache-based SDC error reporting 153 installation on Linux or Unix 39 installation on Windows 32 log file location 154 log file test 154 SSL-related information 52 starting and stopping 152 uninstall previous version 26, 33, 39 uninstalling on Unix (Solaris only) 61 uninstalling on Windows 58 audit log (SDC) 157 authentication for home page 130, 140 B Backup instructions MySQL 69 Basic Analysis specifying as Profile Type 125, 132 C cache prevention using SDC JavaScript tag 177 using SDC VBScript tag 182 Child profiles configuring ,?? 129 clustered server site configuration 133 specifying servers for 138 configure by hit using SDC JavaScript tag 175 using SDC VBScript tag 181 content instrumentation 173 Content tab specifying information in templates 113 Index 189

190 D dashboards adding items to report templates 113 Data Source Splitter specifying as Profile Type 132 distributed architecture installing 69 managing 74 Document Object Model (DOM) 183 documentation typographic conventions used 19 E enabling SSL 51 environment variables setting for SDC 151 error reporting for Apache-based SDC 153 Event viewer 158 F file names specifying for home page 130, 140 firewall considerations 28 Full-featured Analysis specifying as Profile Type 125, 132 G General settings per profile 135 GMT offset managing 126, 134 graphs, including in reports 114 H Help Cards including in templates 114 help, accessing 19 Hit Count Log File (HCLF) 161, 162 hit count tracking 161 hit validation monitoring of 169 Home profile settings 130, 140 hosted-model SDC 151 hticountflushrate 167 HTML page titles retrieving for reports 135 HTML <META> tags 183 I IIS-based SDC installation on Windows 2000/2003/XP 37 log file location 156 log file test 156 SSL-related information 57 starting and stoppng 156 uninstalling on Windows 60 install Apache-based SDC on Windows 32 Installation custom Distributed Architecture 66 guidelines 68 managing 74 prerequisites 26 Professional 26 SDC 32 Linux/Unix 39 Small Business Installation and Configuration Guide

191 WebTrends sample data 31 installing Apache Web server Windows SDC uninstalling Apache 32 installing IIS-based SDC on Windows 2000/ 2003/XP 37 instrumenting web pages 173 J JavaScript tag insertion 177 instrumenting web pages 173 location 173 modifications 174 placement of 177 L language default to use in reports 114 used in report templates 114 License key activating 22, 31 checking status 24 deactivating 23 WebTrends On Demand 24 checking status 25 Linux uninstalling Apache 39 uninstalling SDC 60 List Of Servers profile settings 138 location of log files on Apache-based SDC 154 Log Data Sources specifying per profile 129, 139 log file location on Apache-based SDC 154 location on IIS-based SDC 156 naming 170 rotation 171 test on Apache-based SDC 154 on IIS-based SDC 156 log files specifying paths 129, 139 specifying storage method 133 logging behavior 171 M manually license SDC 41 <META> (HTML) tags 183 monitoring log files 169 monitoring SDC 168 multiple domain tracking using SDC JavaScript tag 175 using VBScript 180 multiple machines site configuration 133 MySQL backup instructions 69 N network information 27 new profile wizard On Demand process 124 software process 131 O On Demand new profile wizard 124 online help accessing 19 Index 191

192 P Parent-Child profiles configuring 127, 136 specifying as profile type 125, 132 per-hit P3P headers using SDC JavaScript tag 177 using VBScript tag 182 profile name, specifying 135 Profile Type settings 131 profiles adding 124 advanced settings 148 analyzing from a specific date 126, 134 General settings 135 Home settings 130, 140 List Of Servers settings 138 list of settings, list of profile settings 124 Log Data Source settings 129, 139 Profile Type settings 131 Report Template settings 118 Site Configuration profile settings 133 Site Logs settings 133 Summary settings 148 Q QuickTime, supported streaming media server 133 R RealMedia, supported streaming media server 133 removing Apache Web server Windows 26 Report Templates specifying per profile 118 reports Help Card settings 114 retrieving web page titles 135 style specifications 114 template configuration 111 template management per profile 118 time offset 135 using word wrap 114 rotation of log files 171 S sample data (WebTrends) installing 31 SDC Apache-based starting and stopping 152 audit log 157 cache prevention 177 enabling secure sockets (SSL) 51 environment variables 151 hit count flush rate 167 Hit Count Log File (HCLF) 162 hit count tracking 166 hit monitoring 169 hosted-model 151 include file 178 inserting the JavaScript tag 177 installing Apache web server 33 installing SDC 33 instrumenting web pages 173 JavaScript tag 173 JavaScript tag modifications 174 log file monitoring 169 log file name 170 log file rotation 171 monitoring 168 multi-domain tracking Installation and Configuration Guide

193 multi-domain tracking and VBScript 180 operations and monitoring 151 SSL for Apache-based SDC 52 stopping and starting 151 syslog (Linux or Solaris) 160 uninstalling 57 uninstalling on Linux or Unix 60 uninstalling on Windows 2000/2003/XP 58 VBScript 179 VBScript tag modifications 180 viewing Apache statistical information 155 SDC and P3P headers 177 SDC installation 32 on Linux or Unix 39 on Windows NT/2000/2003/XP 32 SDC JavaScript tag placement 177 SDC web server 27 Secure Sockets Layer enabling 51 security issues 27 servers, managing from profiles 138 single machine site configuration 133 Site Configuration, profile settings 133 Site Logs, profile settings 133 SQL Servers supported 70 SSL enabling 51 standard profiles, adding 124 statistical information Apache Web server 155 streaming media servers specifying per profile 132 specifying profile type 131 supported types 133 style applying to reports 114 used in report templates 114 summary of profile settings 148 supported streaming media servers 133 syslog (Linux or Solaris) and SDC 160 T templates, report specifying per profile 118 test of log files on Apache-based SDC 154 time zone about GMT offset 135 trackhitcount 166 typographic conventions for this guide 19 U uninstalling Apache web server Linux or Unix 39 Unix uninstalling Apache 39 uninstalling SDC 60 URL specifying root of web site 130, 140 user access user accounts, adding 107 user accounts, configuring access 107 users, adding 107 users, managing V VBScript tag file location 179 modifications 180 placement of 183 view reports permissions 110 Index 193

194 W web page titles retrieving for reports 135 web server specifying per profile 131 specifying profile type 131 web site configuration on multiple machines 133 on single machine 133 specifying single or multiple servers 133 web site logs, specifying where stored 133 web site URL about 131, 141 specifying root of web site 130, 140 webhouse storing log files in 133 WebTrends sample data installing 31 WebTrends software new profile wizard 131 WebTrends Warehouse, storing log files in 133 Windows 2000/2003/XP installing SDC on 32 uninstalling SDC 58 Windows 2000/2003/XP Event Viewer 158 Windows Media, supported streaming media server 133 word wrap, using in reports 114 Index 194