The following links are provided for ease of use. These links are valid as of 11/24/99. Go to activestate.com, perl.com, or apache.org if a link is no longer available.
For Windows NT, you will need the following software:
| ACTIVESTATE PERL | For Activestates Windows NT binary download page |
| APACHE WEB SERVER | NT binary |
Most UNIX have perl pre-installed. Be certain that you have a current
release of perl by typing perl -v (which should show a version number of
5.004 or later). You should have perl in your PATH. If you dont have perl
installed, you will need to install from
| PERL DOWNLOAD PAGE | Download binaries or the latest source code |
| APACHE WEB SERVER | In Binary Format or in Source Format |
Your administrator may have allready performed this task.
Perl 5.005 or later must be installed on your system. Use perl -v to get the version number. Use all defaults if you are installing on NT including the mapping of .pl files to perl (very important). On UNIX, be sure that the correct version of perl is first in your path. Note that if you are using MKS toolkit on NT, the version of perl provided is not recent enough - you will need a more recent version - so I recommend removing the MKS toolkit version of perl and reinstalling the latest activestate perl version.
If you have problems installing perl, check with your systems administrator. Most systems administrators have experience installing perl.
After Perl is installed, you must install the Sybase::DBlib perl add on module. Your administrator may have allready performed this task.
For Windows NT, this is done using the ppm.pl program (installed with your activestate perl installation). If you have a Proxy/Firewall at your company, you will need to set the HTTP_proxy environment variable using control_panel -> system -> environment to something like http://web-proxy.myco.com:80 (obviously based this on your proxy). The following commands within ppm will do an installation:
>ppm.pl PPM> install sybperl ( some messages indicating success appear) PPM> exitFor UNIX, the Sybase::DBlib will need to be downloaded and compiled from www.cpan.com (cpan is the place perl add on libraries are stored). You will need to compile the version using the standard:
perl Makefile.PL make make test make installAlso I noticed on NT that some versions of activestates sybperl package have hard coded reference to P:/modules. If you get this error, you must hand edit the DBlib.pm and CTlib.pm files in your perl installation directory to remove the redefinition of the SYBASE environment variable in the BEGIN block.
If you intend to try Webmonitor II, you will need to create a new database named webmonitor on one of your servers. This database should be about 20 MB. If you need to, you may share an existing database, but this is not recommended. This database will need the select into option set.
You may also set this package up to ftp output to an external web server
by editing the configuration file. If you wish to run this software
on a server that
has its own server, you are responsible for setting it up, but that
is not a big deal. Webmonitor REQUIRES a web server on the machine
it is installed. Free web servers like Internet Information Server (IIS)
on NT or Apache on UNIX or NT work fine and are easy to install and run.
IIS can easily be installed by your NT administrator and Apache can be
downloaded from www.apache.org (binary for NT or compilable source for
UNIX - its really easy). I test under both Apache and IIS on NT and under
Apache on Unix. Take all defaults on the web server installation.
You need to set up a virtual directory with script access pointing to the main install directory (eg: D:/ADMIN_SCRIPTS if you extracted into D:/ on nt). You should set these directories up with script, execute, and index permissions.
The following are changes I made to my apache configuration file (default on NT is C:/program files/apache group/apache/conf/httpd.conf). If you are using apache on your own workstation, it is suggested that you lower the apache resource utilization values (use your discression) - these will not be high volume applications.
Comment out the following line
# UseCanonicalName OnChange DefaultType
#DefaultType text/plain DefaultType text/htmlAppend the following lines. This extract assumes windows NT and that you have extracted into C:/ so there is a directory named C:/ADMIN_SCRIPTS. It also assumes that your Sybase directory is C:/sybase. Change these directories as appropriate if you have installed elsewhere on NT or are installing on UNIX.
<Directory "C:/ADMIN_SCRIPTS/"> Options All AllowOverride None Order allow,deny Allow from all </Directory> Alias /sybase_tools/ "C:/ADMIN_SCRIPTS/" # perl can be used for cgi AddHandler cgi-script .pl # Set this to your sybase variable SetEnv SYBASE c:\sybaseFor IIS, go to the IIS Admin Manager and use Add Virtual Directory to add the directories using the admin manager. Be sure that execute, script, and directory browsing are all turned on.
First connect to your web server, and then use your browser to go to the virtual directories set up in the last step. The main page should give you a nice welcome banner and you should see a directory index in the two virtual directories (/webmonitor and /server_documentation).
The address you are going to go too can take 2 forms. On my NT machine (named mymachine), which runs a stand alone apache and is not part of the domain, i go to the http://mymachine/ get the main apache splash screen. I then go to http://mymachine/sybase_tools/ to see the application main screen.
On machines that ARE part of the domain, you must add domain to your url. If your domain is .abcd.com, and your port (because you are on UNIX and dont have root) is 8080, your url would b http://mymachine.abcd.com:8080/ for the main web server page and http://mymachine.abcd.com:8080/webmonitor/ for a directory listing of application files.