Skip Headers

Oracle9iAS Clickstream Intelligence Administrator's Guide
Release 2 (9.0.2)

Part Number A90500-02
Go To Documentation Library
Home
Go To Product List
Solution Area
Go To Table Of Contents
Contents
Go To Index
Index

Go to previous page Go to next page

C
Installing a Standalone Collector Agent

This appendix describes how to install a standalone Clickstream Intelligence Collector Agent.

This appendix contains the following sections:

Introduction to the Collector Agent

The Collector Agent is the component of Oracle9iAS Clickstream Intelligence that resides on the Web server machine and collects Web server logs files. The Collector Agent compresses log files into units of manageable size called data packets, which enable more efficient storage of Web log data.

If you want to collect Web logs from a Web server other than Oracle HTTP Web Server, a standalone Collector Agent must be installed on your server machine. Data packets created by the standalone Collector Agent are retrieved by the Collector Server using HTTP or FTP protocol, and then parsed and loaded into the database by the Clickstream Loader. The platform of the server on which you install the standalone Collector Agent can differ from the platform on which you installed Oracle9iAS. (See "Installing a Standalone Collector Agent" in this appendix for further details.

To help determine if a standalone Collector Agent is needed for your Web server, see the criteria below. If any of the following criteria are met, you do not need to install a standalone Collector Agent:


Note:

All log files from which the Collector Agent creates data packets must be unzipped (uncompressed). If a log file is zipped, the Collector Agent will still create data packets from it - which ultimately causes failure of the "Load Clickstream" process.


Installing a Standalone Collector Agent

During a typical Oracle9iAS Clickstream Intelligence install, the Collector Agent is pre-configured to retrieve Apache Web logs from Oracle HTTP Server. To install one or more Collector Agents for data sources other than Oracle HTTP Server, you must follow the installation steps described in the sections that follow.

Pre-installation Requirements

In order to successfully install, configure, and use a standalone Collector Agent, the following conditions must be met:


Note:

Data packets consume disk space on the server machine; therefore, disk space requirements will increase as the number of data packets stored on the server increases.


Installation

The platform of the server on which you install the Collector Agent can be the same as, or may differ from, the platform of your Oracle9iAS CD. In both cases, installation files can be downloaded from the Oracle Technology Network Web site.

  1. Go to the Oracle Technology Network Web site located at:

     http://otn.oracle.com/ 
    
    
  2. Download the standalone Collector Agent install files that match the platform of your server.

  3. Next, unpack the Collector Agent files in accordance with the platform you are using. (For example, .tar or .zip files correspond to UNIX or Windows, respectively.)

  4. Go to the appropriate directory below:

    (UNIX)  INSTALL_DIR/click/utl
    
    (Windows)  INSTALL_DIR\click\utl
    
    
  5. Then, enter the appropriate command below to create the standalone Collector Agent configuration files:

    (UNIX)  ./instantiate-collagent JDK_HOME COLAGENT_PACKET_HOME COLAGENT_PORT 
    COLAGENT_LOGS APACHE_LOGS 
    
    (Windows)  .\instantiate-collagent-java JDK_HOME COLAGENT_PACKET_HOME 
    COLAGENT_PORT COLAGENT_LOGS APACHE_LOGS 
    
    

    In the expressions above, substitute values for the appropriate environment variables below:

    • INSTALL_DIR - represents the directory into which the standalone Collector Agent was unpacked

    • JDK_HOME - represents the Java Development Kit home directory

    • COLAGENT_PACKET_HOME - the data packets destination home directory

    • COLAGENT_PORT - the port corresponding to the Collector Agent you are installing

    • COLAGENT_LOGS - location of the Collector Agent log files

    • APACHE_LOGS - location of the Web server log files you want to collect

  6. Go to the appropriate directory:

    (UNIX)  INSTALL_DIR/click/bin
    
    (Windows)  INSTALL_DIR\click\bin
    
    

    The INSTALL_DIR environment variable represents the directory in which you unpacked the standalone Collector Agent.

  7. Now, you can execute any of the commands listed in the following section of this appendix: "How to Start and Stop the Collector Agent".

Configuring the Collector Agent

Upon installation and instantiation of a standalone Collector Agent, all configuration file attributes are set to default values . If you want to modify the default values, you can use a text editor (such as Notepad) to manually configure the following files:

(UNIX)  INSTALL_DIR/click/conf/collector-agent.properties


INSTALL_DIR/click/conf/agent.xml
(Windows) INSTALL_DIR\click\conf\collector-agent.properties
INSTALL_DIR\click\conf\agent.xml

The following sections describe all attributes associated with the standalone Collector Agent configuration files.

The collector-agent.properties File

The collector-agent.properties file contains name=value pairs. You can configure the following attributes:

The agent.xml File

The agent.xml file may contain several entries, wherein each entry corresponds to a specific data source. All configurable attributes for each entry are listed below.

How to Start and Stop the Collector Agent

To start, stop, and view the status of one or more Collector Agents, use the commands listed in the following sections. For each command, note the following variable definitions:

Commands for Specific Collector Agents

The following commands apply only to a specific Collector Agent:

Commands for All Collector Agents

The following commands pertain to all Collector Agents in your system:


Go to previous page Go to next page
Oracle
Copyright © 2002 Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Home
Go To Product List
Solution Area
Go To Table Of Contents
Contents
Go To Index
Index