4.3. Win32 Installation Notes

Install Apache Web Server for Windows, and copy the Bugzilla files somewhere Apache can serve them. Please follow all the instructions referenced in Bugzilla Installation regarding your Apache configuration, particularly instructions regarding the "AddHandler" parameter and "ExecCGI" .

You may also use Internet Information Server or Personal Web Server for this purpose. However, setup is quite different. If ActivePerl doesn't seem to handle your file associations correctly (for .cgi and .pl files), please consult Appendix A . If you are going to use IIS, if on Windows NT you must be updated to at least Service Pack 4. Windows 2000 ships with a sufficient version of IIS.

Install ActivePerl for Windows. Check http://aspn.activestate.com/ASPN/Downloads/ActivePerl for a current compiled binary.

Please also check the following links to fully understand the status of ActivePerl on Win32: Perl Porting , and Perl on Win32 FAQ

Use ppm from your perl\bin directory to install the following packs: DBI, DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, GD, AppConfig, and Template. You may need to extract them from .zip format using Winzip or other unzip program first. Most of these additional ppm modules can be downloaded from ActiveState, but AppConfig and Template should be obtained from OpenInteract using the instructions on the Template Toolkit web site .

You can find a list of modules at http://www.activestate.com/PPMPackages/zips/5xx-builds-only/ or http://www.activestate.com/PPMPackages/5.6plus

The syntax for ppm is: C:> ppm <modulename>

ActiveState's 5.6Plus directory also contains an AppConfig ppm, so you might see the following error when trying to install the version at OpenInteract:

Error installing package 'AppConfig': Read a PPD for 'AppConfig', but it is not intended for this build of Perl (MSWin32-x86-multi-thread)

If so, download both the tarball and the ppd directly from OpenInteract, then run ppm from within the same directory to which you downloaded those files and install the package by referencing the ppd file explicitly via in the install command, f.e.:

Install MySQL for NT.

You can download MySQL for Windows NT from MySQL.com . Some find it helpful to use the WinMySqlAdmin utility, included with the download, to set up the database.

Setup MySQL

1. C:> C:\mysql\bin\mysql -u root mysql

2. mysql> DELETE FROM user WHERE Host='localhost' AND User='';

3. mysql> UPDATE user SET Password=PASSWORD ('new_password') WHERE user='root';

   "new_password" , above, indicates whatever password you wish to use for your "root" user.

4. mysql> GRANT SELECT, INSERT, UPDATE, DELETE, INDEX, ALTER, CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost IDENTIFIED BY 'bugs_password';

   "bugs_password" , above, indicates whatever password you wish to use for your "bugs" user.

5. mysql> FLUSH PRIVILEGES;

6. mysql> create database bugs;

7. mysql> exit;

8. C:> C:\mysql\bin\mysqladmin -u root -p reload

Edit checksetup.pl in your Bugzilla directory. Change this line:

my $webservergid = getgrnam($my_webservergroup);

to

my $webservergid = $my_webservergroup;

or the name of the group you wish to own the files explicitly:

my $webservergid = 'Administrators'

Run checksetup.pl from the Bugzilla directory.

Edit localconfig to suit your requirements. Set $db_pass to your "bugs_password" from step 5.d , and $webservergroup to "8" .

Not sure on the "8" for $webservergroup above. If it's wrong, please send corrections.

Edit defparams.pl to suit your requirements. Particularly, set DefParam("maintainer") and DefParam("urlbase") to match your install.

This is yet another step I'm not sure of, since the maintainer of this documentation does not maintain Bugzilla on NT. If you can confirm or deny that this step is required, please let me know.

Change all references in all files from processmail to processmail.pl , and rename processmail to processmail.pl .

Many think this may be a change we want to make for main-tree Bugzilla. It's painless for the UNIX folks, and will make the Win32 people happier.

Some people have suggested using the Net::SMTP Perl module instead of NTsendmail or the other options listed here. You can change processmail.pl to make this work. my $smtp = Net::SMTP->new('<Name of your SMTP server>'); #connect to SMTP server $smtp->mail('<your name>@<you smpt server>');# use the sender's adress here $smtp->to($tolist); # recipient's address $smtp->data(); # Start the mail $smtp->datasend($msg); $smtp->dataend(); # Finish sending the mail $smtp->quit; # Close the SMTP connection $logstr = "$logstr; mail sent to $tolist $cclist"; } here is a test mail program for Net::SMTP: use Net::SMTP; my $smtp = Net::SMTP->new('<Name of your SMTP server', Timeout => 30, Debug => 1, ); # connect to SMTP server $smtp->auth; $smtp->mail('you@yourcompany.com');# use the sender's adress here $smtp->to('someotherAddress@someotherdomain.com'); # recipient's address $smtp->data(); # Start the mail $smtp->datasend('test'); $smtp->dataend(); # Finish sending the mail $smtp->quit; # Close the SMTP connection exit;

This step is optional if you are using IIS or another web server which only decides on an interpreter based upon the file extension (.pl), rather than the "shebang" line (#/usr/bonsaitools/bin/perl)

Modify the path to perl on the first line (#!) of all files to point to your Perl installation, and add "perl" to the beginning of all Perl system calls that use a perl script as an argument. This may take you a while. There is a "setperl.csh" utility to speed part of this procedure, available in the Useful Patches and Utilities for Bugzilla section of The Bugzilla Guide. However, it requires the Cygwin GNU-compatible environment for Win32 be set up in order to work. See http://www.cygwin.com/ for details on obtaining Cygwin.

Modify the invocation of all system() calls in all perl scripts in your Bugzilla directory. You should specify the full path to perl for each system() call. For instance, change this line in processmail:

system ("./processmail",@ARGLIST); </programlisting> to <programlisting> system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST);

Add binmode() calls so attachments will work ( bug 62000 ).

Because Microsoft Windows based systems handle binary files different than Unix based systems, you need to add the following lines to createattachment.cgi and showattachment.cgi before the require 'CGI.pl'; line.

binmode(STDIN); binmode(STDOUT);

According to bug 62000 , the perl documentation says that you should always use binmode() when dealing with binary files, but never when dealing with text files. That seems to suggest that rather than arbitrarily putting binmode() at the beginning of the attachment files, there should be logic to determine if binmode() is needed or not.