Monday, January 18, 2010
Bugzilla with Windows IIS HowTos?
Lets go on with following steps for the same:
* N.B. This is based on Windows Enterprise Server 2003 R2 , IIS, Bugzilla-3.2 Release Notes: Active Perl 5.8.8 build 822, MySQL Server 5.1 and Bugzilla 3.2 stable.
** The same procedure can be followed for Bugzilla 3.4.5 with Windows Server 2008 also. { If you've any issues on windows 2008 then please drop your comments here or into the bugzilla mailing lists. }
1. Make sure the Windows server is installed with IIS. [Please confirm it under Add/Remove Windows Components -> Application Server -> IIS -> WWWeb(must), SMTP, IIS Services Manager(must) are enabled, and available]
2. Copy/Extract the required bugzilla stable (in this case bugzilla-3.2) to the C:\Inetpub\wwwroot. [in this case C:\Inetpub\wwwroot\bugzilla-3.2].
3. ActivePerl as per the minimum requirements of Bugzilla releases that you are interested. [in this case we've ActivePerl V5.8.8 build 822]. During installing if it prompts for CGI - IIS integration please accept those settings. After installation is over please update the path of perl's bin directory manually in Environment Variable section or Windows Server's Advance properties pages if this path is not updated with the ActivePerl installer.
3-1. start -> run -> inetmgr OR start -> programs -> Administrative Tools -> IIS Manager
3-2. IISSERVER (local computer) -> Web Service Extensions ->
3-2-1. You'll see All Unknown CGI Extensions, All Unknown ISAPI Extensions,
Perl CGI Extension, Perl ISAPI Extention, PerlEx ISAPI Extension
3-2-2. Add another web service extension namely Perl scripts (if not exists)
Verify these properties will show as follows:
File Name Status
------------------------------ --------
# Perl CGI Extension: C:\Perl\bin\perl.exe "%s" %s Allowed
# Perl ISAPI Extention: C:\Perl\bin\perlis.dll Allowed
# Perl script: C:\Perl\bin\perl.exe Allowed
# PerlEx ISAPI Extension: C:\Perl\bin\perlEx30.dll Allowed
If any above settings are not ok, please rectify those as mentioned above.
4. Install MySQL Server (with gui tools if possible) in the windows server machine or in the some remote machine (may be windows or linux) as per the minimum requirements of Bugzilla releases you are using.
5. For testing connectivity with the MySQL server from the Windows Server please install the MySQL client in Windows Server machine. This is optional not a must but will be help full for
debugging. Please make sure about mysql root user/password if not created/remembered please
reset it as per the MySQL administration.
6. login as root to your mysql server command prompt to create a login/user account from your localhost(127.0.0.1) or remotehost(let 192.168.1.100 this is the windows server ip, and remote mysql server ip = 192.168.1.120, so to MySQL server 192.168.1.100 is remotehost, from where bugzilla will connect to the database - say 'bug_db_name' in this case) as follows: {Bugzilla will use this account for future transactions}
mysql>
GRANT ALL ON bug_db_name.* FROM 'bug_user'@'localhost' IDENTIFIED BY 'passwordB';
or
GRANT ALL ON bug_db_name.* FROM 'bug_user'@'192.168.1.100' IDENTIFIED BY 'passwordB';
FLUSH PRIVILEGES;
EXIT;
7. Now verify if the mysql user login (i.e. bug_user/passwordB) is working fine as follows:
c:\>mysql -u bug_user -p
passwordB
mysql> getting mysql prompt seems user-login is created successfully.
exit;
8. Now change your current directory to "C:\Inetpub\wwwroot\bugzilla-3.2" and execute checksetup.pl as follows:
C:\Inetpub\wwwroot\bugzilla-3.2> perl checksetup.pl
if it will prompt for any REQUIRED perl modules to install then please install those as per the checksetup.pl screen output. {ppm install Email::Send / CGI / etc.}
Make sure to install the MySQL perl module i.e. mysql driver for perl as per bugzilla release notes.
On, completion of required modules installation it will try to connect to the database, but will fail and prompt for verify the mysql user, database, password.
Edit the localconfig file with Notepad text editor and modify the settings as per our requirement:
$webservergroup = '';
$db_driver = 'mysql';
$db_host = '192.168.1.120' or '127.0.0.1' or 'localhost';
$db_name = 'bug_db_name';
$db_user = 'bug_user';
$db_pass = 'passwordB';
9. Now rerun the checksetup.pl again it will create the database into the MySQL server on successful settings and connectivity.
C:\Inetpub\wwwroot\bugzilla-3.2> perl checksetup.pl
10. If database creation will successful it will asks for administrator e-mail and password etc .
Please enter and remember these settings for future.
11. Open the IIS Services Manager Window:
R-Click on Web Sites -> New Web Site -> Next -> OurBugzillaSite ->
Select All Unssigned or 192.168.1.100 ip for this Web site:
80 as port. [ If you want to access bugzilla through other port please mentioned here]
N.B. If it will be accessed on port 80 make sure other web sites (Default Web Site) should not use the same port.
Next -> Path (Browse to C:\Inetpub\wwwroot\bugzilla-3.2)
Next -> Enable Read, Execute(such as ISAPI application CGI)
Next -> Finished
12. For more settings R-Click-Properties on OurBugzillaSite and make sure about following settings:
Home Directory TAB:
Local Path = C:\Inetpub\wwwroot\bugzilla-3.2
Read is enabled
Execute permissions: Scripts and Executables
Application pool: default at this moment( actually we will use our custom pool)
Click on Configuration... button -> Add
Executable: C:\Perl\bin\perl.exe -x"C:\Inetpub\wwwroot\bugzilla-3.2" -wT "%s" %s
Extension: .cgi [If this extension is exists, then modified as per this section]
Verbs: All Verbs
Script engine enabled
Verify that file exists
Press OK.
Documents TAB:
Enable default content page - enabled
Add index.cgi
Press OK
13. For more security settings for application pool R-Click on
Application Pool -> New -> Application Pool
create a new pool as 'ourbugzillapool'
R-Click on 'ourbugzillapool'
Play with its Predefied identity to Network Service/Local Service/Local System
In case of bugzilla browsing issues.
Please make sure to update the bugzilla web site's application pool to
'ourbugzillapool'
14. Finally restart IIS service for bugzilla and browse from localhost(the windows server)
15. Try then from remote system and modify the bugzilla Parameters and rest of the settings as per your requirement.
Thats all folks
Himadri Sekhar Das
Kolkata / India
das.himuinkol@gmail.com
* N.B. This is based on Windows Enterprise Server 2003 R2 , IIS, Bugzilla-3.2 Release Notes: Active Perl 5.8.8 build 822, MySQL Server 5.1 and Bugzilla 3.2 stable.
** The same procedure can be followed for Bugzilla 3.4.5 with Windows Server 2008 also. { If you've any issues on windows 2008 then please drop your comments here or into the bugzilla mailing lists. }
1. Make sure the Windows server is installed with IIS. [Please confirm it under Add/Remove Windows Components -> Application Server -> IIS -> WWWeb(must), SMTP, IIS Services Manager(must) are enabled, and available]
2. Copy/Extract the required bugzilla stable (in this case bugzilla-3.2) to the C:\Inetpub\wwwroot. [in this case C:\Inetpub\wwwroot\bugzilla-3.2].
3. ActivePerl as per the minimum requirements of Bugzilla releases that you are interested. [in this case we've ActivePerl V5.8.8 build 822]. During installing if it prompts for CGI - IIS integration please accept those settings. After installation is over please update the path of perl's bin directory manually in Environment Variable section or Windows Server's Advance properties pages if this path is not updated with the ActivePerl installer.
3-1. start -> run -> inetmgr OR start -> programs -> Administrative Tools -> IIS Manager
3-2. IISSERVER (local computer) -> Web Service Extensions ->
3-2-1. You'll see All Unknown CGI Extensions, All Unknown ISAPI Extensions,
Perl CGI Extension, Perl ISAPI Extention, PerlEx ISAPI Extension
3-2-2. Add another web service extension namely Perl scripts (if not exists)
Verify these properties will show as follows:
File Name Status
------------------------------ --------
# Perl CGI Extension: C:\Perl\bin\perl.exe "%s" %s Allowed
# Perl ISAPI Extention: C:\Perl\bin\perlis.dll Allowed
# Perl script: C:\Perl\bin\perl.exe Allowed
# PerlEx ISAPI Extension: C:\Perl\bin\perlEx30.dll Allowed
If any above settings are not ok, please rectify those as mentioned above.
4. Install MySQL Server (with gui tools if possible) in the windows server machine or in the some remote machine (may be windows or linux) as per the minimum requirements of Bugzilla releases you are using.
5. For testing connectivity with the MySQL server from the Windows Server please install the MySQL client in Windows Server machine. This is optional not a must but will be help full for
debugging. Please make sure about mysql root user/password if not created/remembered please
reset it as per the MySQL administration.
6. login as root to your mysql server command prompt to create a login/user account from your localhost(127.0.0.1) or remotehost(let 192.168.1.100 this is the windows server ip, and remote mysql server ip = 192.168.1.120, so to MySQL server 192.168.1.100 is remotehost, from where bugzilla will connect to the database - say 'bug_db_name' in this case) as follows: {Bugzilla will use this account for future transactions}
mysql>
GRANT ALL ON bug_db_name.* FROM 'bug_user'@'localhost' IDENTIFIED BY 'passwordB';
or
GRANT ALL ON bug_db_name.* FROM 'bug_user'@'192.168.1.100' IDENTIFIED BY 'passwordB';
FLUSH PRIVILEGES;
EXIT;
7. Now verify if the mysql user login (i.e. bug_user/passwordB) is working fine as follows:
c:\>mysql -u bug_user -p
passwordB
mysql> getting mysql prompt seems user-login is created successfully.
exit;
8. Now change your current directory to "C:\Inetpub\wwwroot\bugzilla-3.2" and execute checksetup.pl as follows:
C:\Inetpub\wwwroot\bugzilla-3.2> perl checksetup.pl
if it will prompt for any REQUIRED perl modules to install then please install those as per the checksetup.pl screen output. {ppm install Email::Send / CGI / etc.}
Make sure to install the MySQL perl module i.e. mysql driver for perl as per bugzilla release notes.
On, completion of required modules installation it will try to connect to the database, but will fail and prompt for verify the mysql user, database, password.
Edit the localconfig file with Notepad text editor and modify the settings as per our requirement:
$webservergroup = '';
$db_driver = 'mysql';
$db_host = '192.168.1.120' or '127.0.0.1' or 'localhost';
$db_name = 'bug_db_name';
$db_user = 'bug_user';
$db_pass = 'passwordB';
9. Now rerun the checksetup.pl again it will create the database into the MySQL server on successful settings and connectivity.
C:\Inetpub\wwwroot\bugzilla-3.2> perl checksetup.pl
10. If database creation will successful it will asks for administrator e-mail and password etc .
Please enter and remember these settings for future.
11. Open the IIS Services Manager Window:
R-Click on Web Sites -> New Web Site -> Next -> OurBugzillaSite ->
Select All Unssigned or 192.168.1.100 ip for this Web site:
80 as port. [ If you want to access bugzilla through other port please mentioned here]
N.B. If it will be accessed on port 80 make sure other web sites (Default Web Site) should not use the same port.
Next -> Path (Browse to C:\Inetpub\wwwroot\bugzilla-3.2)
Next -> Enable Read, Execute(such as ISAPI application CGI)
Next -> Finished
12. For more settings R-Click-Properties on OurBugzillaSite and make sure about following settings:
Home Directory TAB:
Local Path = C:\Inetpub\wwwroot\bugzilla-3.2
Read is enabled
Execute permissions: Scripts and Executables
Application pool: default at this moment( actually we will use our custom pool)
Click on Configuration... button -> Add
Executable: C:\Perl\bin\perl.exe -x"C:\Inetpub\wwwroot\bugzilla-3.2" -wT "%s" %s
Extension: .cgi [If this extension is exists, then modified as per this section]
Verbs: All Verbs
Script engine enabled
Verify that file exists
Press OK.
Documents TAB:
Enable default content page - enabled
Add index.cgi
Press OK
13. For more security settings for application pool R-Click on
Application Pool -> New -> Application Pool
create a new pool as 'ourbugzillapool'
R-Click on 'ourbugzillapool'
Play with its Predefied identity to Network Service/Local Service/Local System
In case of bugzilla browsing issues.
Please make sure to update the bugzilla web site's application pool to
'ourbugzillapool'
14. Finally restart IIS service for bugzilla and browse from localhost(the windows server)
15. Try then from remote system and modify the bugzilla Parameters and rest of the settings as per your requirement.
Thats all folks
Himadri Sekhar Das
Kolkata / India
das.himuinkol@gmail.com
Subscribe to:
Comments (Atom)
