Getting to know
Ad Eagle Suite

Although we cannot offer mod_perl specific support, Ad Eagle Suite is able to run under mod_perl. In fact, for very high traffic sites we recommend that the ads.cgi, include_ads.pl and go.cgi scripts are run under it. If you are using non-SSI ads the remote.cgi and jump.cgi scripts should also be run under mod_perl. 

The most common method of using mod_perl with Ad Eagle Suite is through the use of Apache::Registry. There are several variations on how to configure this, and we suggest you read the mod_perl documentation at http://perl.apache.org before attempting to use mod_perl if you are not familliar with it.

One example could be as follows:
  Copy the ads.cgi, go.cgi, remote.cgi and jump.cgi scripts to a directory above your web root. Let's say your mod_perl scripts live in a directory called "perl". Then, assuming mod_perl is compiled and properly running, adding something like this to your server configs will work ( this is assuming you are running Apache on Unix):

First set up an alias so that you can use a directory above your web root to keep your mod_perl scripts. In your apache configs (in the correct location) this will work:

Alias /perl/ "/usr/local/apache/perl/"

Of course you have to change this to the correct path on your system. 
Then use the following to make all the scripts in this directory run under Apache::Registry:

PerlModule Apache::Registry
<Location /perl>
SetHandler perl-script
PerlHandler Apache::Registry
Options ExecCGI
allow from all
PerlSendHeader On
</Location>

This is just one example and not necessarily the correct or best method for your server. You MUST check with your web host or system administrator if you are not familiar with using mod_perl.

mod_perl is strongly recommended for high traffic sites who want to run multiple ads per page. Be sure to read the mod_perl docs at http://perl.apache.org

Back to the Users Guide