Installation 

 - W3Perl is available for all platform supporting Perl (Unix/Windows and Mac OS)
 - Installation can be done on a provider host with FTP accesses thanks to the web interface.
 - It can be installed even if you have no cgi directories.
 - If you don't have access to your logfiles, you can insert a small javascript tag inside your pages
which will create logfiles for you
 - Stats can be run manually from the web interface or from a crontab.

 Unix  Server Telnet/ssh Cgi-bin Crontab
Local Remote No No Option
Provider Remote No Yes Option
Unix user (without cgi) Local Yes No Option
Webmaster/User (with cgi) Local Yes Yes Yes
Webmaster (Virtual Web) Local Yes Yes Yes
RPM Local Yes Yes Yes
Ubuntu Local Yes Yes Yes

Plugin Installation IP Mapping Email report Cities PDF report

star No logfile

If you don't have access to your logfiles, W3Perl is able to create them for you. As others web analytics tool, a javascript tag need to be inserted in your web page. Installing the package on your server is really easy : 2 scripts (a javascript and a PHP) and one directory to store the logfile (this one should be password protected).
Of course, use the javascript tag method only if you don't have logfile access as server's logfiles contains much more data (Trafic for example).

If you want to monitor your external links, you can use a small php script which will build a logfile for you. It could be nice to know how many people are leaving your homepage or if they clicks on your sponsor links. A counter file is also build so you can add the number of clicks in front of each external links. A logfile is created so you can use W3Perl later to get stats.

star Unix / MacOS

- Webmaster

The easy way is to use :

- RPM package for Mandriva
- Debian package for Debian/Ubuntu.
- MacOS package for MacOS
Then go to http://127.0.0.1/w3perl/admin/ to run the stats or change the default configuration files.

If you want to use the tarball :

  1. Uncompress the w3perl package inside your web server tree.
  2. Edit two paths in the installation script (install.pl) and run it.
  3. Build your configuration file via the administration interface
  4. Move your configuration file to the w3perl cgi-bin location.
  5. Launch stats either by commands line or via the administration interface.
  6. Add an entry in your crontab to update stats daily (cron-w3perl.pl -e)

- Provider (FTP)

  1. Download the w3perl.tar.gz package on your own local host.
  2. Uncompress the w3perl package.
  3. Edit two paths in a script (init.pl) [optional].
  4. Create two sub-directories on your provider using FTP
  5. Upload the files on your provider using FTP
  6. Changing some file permissions using FTP.
  7. Launch the web admin interface with your browser (if the optional script have been uploaded).
  8. Build/Customize a configuration file (predefined one exists).
  9. Move your configuration within the scripts.
  10. Run the stats from the web admin
  11. Ask your ISP to add a crontab to update your stats daily (cron-w3perl.pl -e)

star Windows

If you want to compute your stats locally or your web server is running on a Windows OS.
You'll need to install StrawberryPerl or ActivePerl first. Installing W3Perl with the NSIS installer is straight forward and a default configuration file is provided so stats can be run within a few minutes.

- IIS

NSIS installer
NSIS install the scripts

With the help of NSIS, installation is just a matter of downloading w3perl-iis.exe. A dedicated help is provided in the documentation.
IIS 7.0 user should activate the IIS 6 metabase compatiblity
Once installed, a default configuration file is provided so you are able to launch the stats.

- Apache

A binary is available for the Apache >= 2.2. See documentation for more details.

- Abyss

A binary is available for Abyss Web Server. See documentation for more details.

- No server

Users who want to compute their stats locally (without any web server running) can use the w3perl.exe which require only Perl to run. Logfiles may be retrieved by the package from your server. Some features won't be available as they require cgi or Ajax.