Urchin WebAnalytics Software is discontinued and is no longer supported. All Urchin documentation applies only to the Urchin product as it was at the time of discontinuation, and does not apply to any Google Analytics products or services.

Using an Existing Apache Webserver (UNIX-type Platforms)

By default, Urchin 4 administration and reporting are done using a standalone Apache server that is bundled with the Urchin product. In the vast majority of Urchin installations, this is the preferred method for delivering Urchin admin and reporting interfaces. However, in rare instances it may be necessary to utilize an existing Apache installation. This may be due to site requirements that a localized version of Apache be used throughout the organization, or that all web services be controlled via a single Apache configuration. The information below describes two different models that can be employed to meet these requirements.

DISCLAIMER: These modifications to the Urchin installation are unsupported and fall outside the scope of the standard Urchin free and paid support plans. Any assistance rendered to set up or debug these configurations will be done at Urchin Software Corporation's standard Hourly Support rate.

Option 1: Utilitizing an existing site-specific Apache httpd binary to run Urchin services as a separate instance

    Side effects:
    • Urchin upgrades that depend on features added and/or configuration changes to the bundled Apache may not work properly if the existing Apache binary doesn't support these changes/features.
  • Configuration changes
    • Ensure that your httpd includes support for the following modules:
    • Install Urchin 4 in the normal fashion, choosing the desired port for Urchin's admin and reporting interfaces to run on.
    • Once Urchin is installed, do the following:
        cd /path/to/urchin/bin ./urchinctl stop
        mv urchinwebd urchinwebd.orig
        ln -s /path/to/your/httpd urchinwebd
        ./urchinctl start


      This will start up a separate instance of Apache that uses your Apache binary, but runs independently from your standard web services.

Option 2: Running Urchin services from an existing Apache configuration


Once these configuration changes have been made, perform the following tasks:

    Side effects:
    • The entire Urchin distribution must be owned by the same UID that httpd runs as.
    • The admin GUI cannot be used to change the port Urchin runs on.
    • The bin/wrapper tool cannot be used to start Urchin services since it will attempt to run the Urchin-specific httpd. Use the bin/urchindctl.sh script exclusively to start/stop only the Urchin scheduler (urchind)
  • Configuration changes
    Add the following lines to your existing httpd.conf file. You will need to supply the IP address for your server, the port number for the Urchin to use, as well as the path to the location where you've installed Urchin 4.
    • ## Support for Urchin administration and reporting services
      Listen [port#]
      <VirtualHost [server-ip]:[port#]>
      ErrorLog /path/to/urchin-distribution/var/error.log
      DocumentRoot /path/to/urchin-distribution/htdocs/
      <Directory /path/to/urchin-distribution/htdocs/>
        AddHandler cgi-script .cgi
        Options ExecCGI
        DirectoryIndex session.cgi
        AllowOverride None
        Order allow,deny
        Allow from all
    • </Directory>
    • Change the ownership of the Urchin distribution to the UID that your Apache webserver runs as:
        chown -R apache-user /path/to/urchin/bin
    • Ensure that the Apache bundled with Urchin is stopped:
        cd /path/to/urchin/bin
        ./urchinctl -w stop
    • Restart your Apache server to enable Urchin reporting and administration


Clear search
Close search
Google apps
Main menu
Search Help Center