3.6. Win32 Installation Notes

3.6.1. Win32 Installation: Step-by-step

You should be familiar with, and cross-reference, the rest +> You should be familiar with, and cross-reference, the rest of the

Install Install Apache Web @@ -179,11 +179,11 @@ CLASS="QUOTE" >.
You may also use Internet Information Server or Personal +> 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), @@ -209,7 +209,7 @@ HREF="faq.html" >.
If you are going to use IIS, if on Windows NT you must +> 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 Install ActivePerl for a current compiled binary.
Please also check the following links to fully understand the status +> Please also check the following links to fully understand the status of ActivePerl on Win32: Perl Porting Perl Porting, and Perl on Win32 FAQ Perl on Win32 FAQ
Use ppm from your perl\bin directory to install the following packs: DBI, +> Use ppm from your perl\bin directory to install the following packs: DBI, DBD-Mysql, TimeDate, Chart, Date-Calc, Date-Manip, and GD. You may need to extract them from .zip format using Winzip or other unzip program first. These additional ppm modules can be downloaded from ActiveState.
You can find a list of modules at +> You can find a list of modules at http://www.activestate.com/PPMPackages/zips/5xx-builds-only/ http://www.activestate.com/PPMPackages/zips/5xx-builds-only/
The syntax for ppm is: +> The syntax for ppm is: C:> ppm <modulename>
C:>ppm DBD-Mysql Watch your capitalization!
You can find ActiveState ppm modules at +> You can find ActiveState ppm modules at http://www.activestate.com/PPMPackages/5.6plus http://www.activestate.com/PPMPackages/5.6plus

Install MySQL for NT. +> Install MySQL for NT.

You can download MySQL for Windows NT from You can download MySQL for Windows NT from MySQL.com

Setup MySQL +> Setup MySQL

C:> C:\mysql\bin\mysql -u root mysql
mysql> DELETE FROM user WHERE Host='localhost' AND User='';
mysql> UPDATE user SET Password=PASSWORD ('new_password') WHERE user='root'; @@ -436,17 +436,17 @@ CLASS="QUOTE" >
mysql> GRANT SELECT, INSERT, UPDATE, DELETE, INDEX, ALTER, CREATE, DROP, REFERENCES ON bugs.* to bugs@localhost @@ -468,14 +468,14 @@ CLASS="QUOTE" >
mysql> FLUSH PRIVILEGES;
mysql> create database bugs;
mysql> exit;
C:> C:\mysql\bin\mysqladmin -u root -p reload
Edit Edit checksetup.pl in your Bugzilla directory. Change this line:

my $webservergid = getgrnam($my_webservergroup); +CLASS="programlisting" +> my $webservergid = getgrnam($my_webservergroup); to +> to

my $webservergid = $my_webservergroup; +CLASS="programlisting" +> my $webservergid = $my_webservergroup; my $webservergid = 'Administrators' +CLASS="programlisting" +> my $webservergid = 'Administrators' Run 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".

"8" for $webservergroup above. If it's wrong, please send corrections. Edit Edit defparams.pl to suit your requirements. Particularly, set DefParam("maintainer") and DefParam("urlbase") to match your install.

There are several alternatives to Sendmail that will work on Win32. +> There are several alternatives to Sendmail that will work on Win32. The one mentioned here is a suggestion, not @@ -764,12 +764,12 @@ TARGET="_top" >

Download NTsendmail, available from Download NTsendmail, available from www.ntsendmail.com

# these settings configure the NTsendmail process
+CLASS="programlisting"
+># these settings configure the NTsendmail process
 use NTsendmail;
 $ENV{"NTsendmail"}="your.smtpserver.box";
 $ENV{"NTsendmail_debug"}=1;
@@ -804,11 +804,11 @@ $ENV{"NTsendmail_max_tries"}=5;
 >
		  Some mention to also edit
+>		  Some mention to also edit
 		  $db_pass in
 		  globals.pl to be your
 		  .htaccess, your
 		  database password is exposed to whoever uses your
@@ -853,11 +853,11 @@ CLASS="FILENAME"
 >
		Find and comment out all occurences of
+>		Find and comment out all occurences of
 		"open(SENDMAIL" in
@@ -871,8 +871,8 @@ WIDTH="100%"
 >
# new sendmail functionality
+CLASS="programlisting"
+># new sendmail functionality
 my $mail=new NTsendmail;
 my $from="bugzilla\@your.machine.name.tld";
 my $to=$login;
@@ -886,11 +886,11 @@ $mail->send($from,$to,$subject,$msg);
 >
 	      
		  Some have found success using the commercial product, 
+>		  Some have found success using the commercial product, 
 		  Windmail.
 		  You could try replacing your sendmail calls with:
@@ -921,8 +921,8 @@ WIDTH="100%"
 >
open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log";
+CLASS="programlisting"
+>open SENDMAIL, "|\"C:/General/Web/tools/Windmail 4.0 Beta/windmail\" -t > mail.log";
 		  
	    Change all references in all files from
+>	    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
+>	      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.
+>	      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
+CLASS="programlisting"
+>
+
+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
@@ -1028,7 +1030,10 @@ $smtp->datasend($msg);
 $smtp->dataend();   # Finish sending the mail
 $smtp->quit;    # Close the SMTP connection
 $logstr = "$logstr; mail sent to $tolist $cclist";
-}use Net::SMTP;
+CLASS="programlisting"
+>
+
+use Net::SMTP;
  my $smtp = Net::SMTP->new('<Name of your SMTP server', Timeout => 30, Debug
 => 1, ); # connect to SMTP server
                  $smtp->auth;
@@ -1057,7 +1064,10 @@ recipient's address
                 $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
+>	      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
 	      
	    Modify the path to perl on the first line (#!) of all
+>	    Modify the path to perl on the first line (#!) of all
 	    files to point to your Perl installation, and add

Modify the invocation of all system() calls in all perl - scripts in your Bugzilla directory. For instance, change +> 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.pl",@ARGLIST); - to - Add Add binmode() calls so attachments will work (). Because Microsoft Windows based systems handle binary +> 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. line. + -system ("perl processmail.pl",@ARGLIST); +system ("./processmail",@ARGLIST); + </programlisting> to + <programlisting> +system ("C:\\perl\\bin\\perl", "processmail", @ARGLIST); binmode(STDIN); -binmode(STDOUT); +binmode(STDIN); +binmode(STDOUT); + + According to 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 aribtrarily putting binmode() at the begining of the attachment files, there should be logic to determine if binmode() is needed or not. If you are using IIS or Personal Web Server, you must add cgi +> If you are using IIS or Personal Web Server, you must add cgi relationships to Properties -> Home directory (tab) -> Application Settings (section) -> Configuration (button), such as: .cgi to: <perl install directory>\perl.exe %s %s .pl to: <perl install directory>\perl.exe %s %s @@ -1317,19 +1317,19 @@ GET,HEAD,POST >3.6.2. Additional Windows Tips From Andrew Pearson: +> From Andrew Pearson: You can make Bugzilla work with Personal Web Server for +> You can make Bugzilla work with Personal Web Server for Windows 98 and higher, as well as for IIS 4.0. Microsoft has information available at Basically you need to add two String Keys in the +> Basically you need to add two String Keys in the registry at the following location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap +CLASS="programlisting" +> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\ScriptMap The keys should be called ".pl" and ".cgi", and both +> The keys should be called ".pl" and ".cgi", and both should have a value something like: c:/perl/bin/perl.exe "%s" "%s" The KB article only talks about .pl, but it goes into +> The KB article only talks about .pl, but it goes into more detail and provides a perl test script.

If attempting to run Bugzilla 2.12 or older, you will need +> If attempting to run Bugzilla 2.12 or older, you will need to remove encrypt() calls from the Perl source. This is not necessary

Replace this: +> Replace this:

SendSQL("SELECT encrypt(" . SqlQuote($enteredpwd) . ", " . SQLQuote(substr($realcryptpwd, 0, 2)) . ")"); my $enteredcryptpwd = FetchOneColumn(); @@ -1471,7 +1471,7 @@ WIDTH="100%" > my $enteredcryptpwd = $enteredpwd 3.6.3. Bugzilla LDAP Integration What follows is some late-breaking information on using the +> What follows is some late-breaking information on using the LDAP authentication options with Bugzilla. The author has not tested these (nor even formatted this section!) so please contribute feedback to the newsgroup. Mozilla::LDAP module +CLASS="literallayout" +> +Mozilla::LDAP module The Mozilla::LDAP module allows you to use LDAP for authentication to the Bugzilla system. This module is not required if you are not using -- cgit v1.2.3-24-g4f1b

3.6. Win32 Installation Notes

3.6.1. Win32 Installation: Step-by-step

3.6.2. Additional Windows Tips

3.6.3. Bugzilla LDAP Integration