[cvs] [Wiki] changed: InstallHowToIIS
Wiki Guest
wiki at wiki.horde.org
Sat Sep 24 20:46:50 PDT 2005
guest [202.41.167.246] Sat, 24 Sep 2005 20:46:50 -0700
Modified page: http://wiki.horde.org/InstallHowToIIS
New Revision: 8.0
Change log: Revert
@@ -16,23 +16,23 @@
++ Install PHP 4.3.7RC1
-# Extract the files in the ZIP archive to {{C:\}}. Extracting the files will create a folder called {{C:\php-4.3.7RC1-Win32}}. Rename the folder to {{C:\php}}.
-# Copy {{C:\php\php4ts.dll}} to {{C:\Windows\System32}}.
-# Copy {{C:\php\php-ini-recommended}} to {{C:\Windows}}. Rename {{php-ini-recommended}} to {{php.ini}}
-# Just to be safe, change the permissions on {{php.ini}} to EVERYONE: Read & Execute, Read. Ignore any warning you might see when you apply the permissions.
-# Open {{C:\Windows\php.ini}} for editing
- * Search for Âextension_dir and change it to read: {{extension_dir = ".\extensions"}}
- * Search for ÂbrowscapÂ. Uncomment the {{browscap =}} line and change it to read: {{browscap = c:\windows\system32\inetsrv\browscap.ini}}
- * Search for Âcgi.force_redirectÂ. Uncomment the {{cgi.force_redirect =}} line and change it to read: {{cgi.force_redirect = 0}}
+# Extract the files in the ZIP archive to C:\. Extracting the files will create a folder called C:\php-4.3.7RC1-Win32. Rename the folder to C:\php
+# Copy C:\php\php4ts.dll to C:\Windows\System32.
+# Copy C:\php\php-ini-recommended to C:\Windows. Rename php-ini-recommended to php.ini
+# Just to be safe, change the permissions on php.ini to EVERYONE: Read & Execute, Read. Ignore any warning you might see when you apply the permissions.
+# Open C:\Windows\php.ini for editing
+ * Search for Âextension_dir and change it to read: extension_dir = ".\extensions"
+ * Search for ÂbrowscapÂ. Uncomment the browscap = line and change it to read: browscap = c:\windows\system32\inetsrv\browscap.ini
+ * Search for Âcgi.force_redirectÂ. Uncomment the cgi.force_redirect = line and change it to read: cgi.force_redirect = 0
* Search for ÂuploadÂ. By default uploads are enabled. Decide where you want the upload temporary directory to live, if necessary create that folder. Decide what the maximum allowed upload size and set: _
-<code>
-upload_tmp_dir = whatever folder you like
-upload_max_filesize = whatever size you like
-</code> _
-I use {{C:\temp}} and 64M respectively. The reason I set this directive is because if itÂs not set PHP uses %TEMP% which is {{C:\Windows\Temp}}. I like to keep temp stuff clear of my %SYSTEMROOT%. Alternately you could change the %TEMP% and %TMP% system variables and leave this directive commented out. 64 megabytes might seem a bit excessive, but I run a small installation so I donÂt worry about this as much as someone running a larger installation.
- * Optionally you can search for Âdoc_root and change it to {{C:\Inetpub}}. That way any website created under that folder will have PHP capabilities. I left this directive blank.
+ _
+upload_tmp_dir = whatever folder you like _
+upload_max_filesize = whatever size you like _
+ _
+I use C:\temp and 64M respectively. The reason I set this directive is because if itÂs not set PHP uses %TEMP% which is C:\Windows\Temp. I like to keep temp stuff clear of my %SYSTEMROOT%. Alternately you could change the %TEMP% and %TMP% system variables and leave this directive commented out. 64 megabytes might seem a bit excessive, but I run a small installation so I donÂt worry about this as much as someone running a larger installation.
+ * Optionally you can search for Âdoc_root and change it to C:\Inetpub. That way any website created under that folder will have PHP capabilities. I left this directive blank.
* Search for ÂWindows ExtensionsÂ. YouÂll need to uncomment the following:
* extension=php_domxml.dll
* extension=php_gd2.dll
* extension=php_gettext.dll
@@ -44,30 +44,30 @@
* extension=php_mime_magic.dll
* extension=php_openssl.dll
* extension=php_pgsql.dll
* You might not need all of the extensions listed here. In fact you probably donÂt but I uncommented all of the extensions reported in the ÂPHP Module Capabilities section of the Horde test script.
-# Save and close the updated {{php.ini}} file.
-# In order to get mcrypt support on Windows youÂll need {{libmcrypt.dll}}. (Refer to http://www.php.net/mcrypt). The dll is available at http://ftp.emini.dk/pub/php/win32/mcrypt/. Browse to this address, right-click on {{libmcrypt.dll}} and choose ÂSave Target asÂ
 Save the dll in {{C:\php\dlls}}
+# Save and close the updated php.ini file.
+# In order to get mcrypt support on Windows youÂll need libmcrypt.dll. (Refer to http://www.php.net/mcrypt). The dll is available at http://ftp.emini.dk/pub/php/win32/mcrypt/. Browse to this address, right-click on libmcrypt.dll and choose ÂSave Target asÂ
 Save the dll in C:\php\dlls
++ Configure IIS6 to Allow PHP extensions
-Before you start this process I recommend adding {{C:\php;C:\php\dlls}} to the system path. From what IÂve read about installing PHP on IIS6 this is a preference rather that a must. I added it for two reasons. The first is convenience; the second and more important is because there are a number of files in the dlls folder that are required to run the PHP extensions used by Horde. If the dlls folder is not in the path you have to copy the necessary dll to {{c:\Windows\system32}} folder. So to avoid having to find and copy the appropriate dlls I strongly recommend adding these entries into the system path.
+Before you start this process I recommend adding C:\php;C:\php\dlls to the system path. From what IÂve read about installing PHP on IIS6 this is a preference rather that a must. I added it for two reasons. The first is convenience; the second and more important is because there are a number of files in the dlls folder that are required to run the PHP extensions used by Horde. If the dlls folder is not in the path you have to copy the necessary dll to c:\Windows\system32 folder. So to avoid having to find and copy the appropriate dlls I strongly recommend adding these entries into the system path.
-# Click "Start -> Administrative Tools -> Internet Information Services (IIS) Manger".
+# Click Start-Administrative Tools-Internet Information Services (IIS) Manger.
# Expand the local computer tree then click ÂWeb Service Extensions in the left-hand pane.
# Click the ÂAdd a new Web service extensionÂ
 link under Tasks in the right hand pane.
-# Enter {{PHP}} in the ÂExtension name:Â box.
+# Enter PHP in the ÂExtension name:Â box.
# Click the ÂSet extension status to Allowed check box (Should be checked).
-# Click the ÂAdd button then click the ÂBrowseÂ
 button. Browse to {{C:\php}}, change the ÂFiles of type: box to read ÂCGI exe files (*.exe)Â. Double-click on {{php.exe}}. Finally click the "OK" button twice.
+# Click the ÂAdd button then click the ÂBrowseÂ
 button. Browse to C:\php, change the ÂFiles of type: box to read ÂCGI exe files (*.exe)Â. Double-click on php.exe. Finally click the OK button twice.
++ Add PHP to IIS6 Web Sites
There is a decision to make at this point. We can add PHP functionality to the Web Sites folder or we can simply add it to the Default Web Site. The benefit to adding PHP to the Web Sites folder is that any new web site will inherit the settings. Conversely, if you choose not to configure the Web Sites folder to use PHP then youÂll have to add the functionality to each new web site as you create it. IÂll cover both options here.
# Right Click on the ÂDefault Web Site entry under the ÂWeb Sites folder in the left-hand pane and choose ÂProperties OR Right-click on the ÂWeb Sites folder in the left-hand pane and choose ÂPropertiesÂ.
# Click the ÂHome Directory tab then click the ÂConfigurationÂ
 button
-# Click the ÂAddÂ
 button. Browse to {{C:\php}}, change the ÂFiles of type: box to read ÂCGI exe files (*.exe)Â. Double-click on {{php.exe}}.
+# Click the ÂAddÂ
 button. Browse to C:\php, change the ÂFiles of type: box to read ÂCGI exe files (*.exe)Â. Double-click on php.exe.
# Enter PHP in the ÂExtensions: box. Make sure the ÂScript Engine box is checked. Leave ÂVerify file exists checked if you want or you may uncheck it. I chose to uncheck it.
# Click the ÂOK button twice to return to the ÂDefault Web Site Properties page. If you are applying these changes to the Web Sites folder youÂll return to the ÂWeb Sites Properties page.
# Change the ÂExecute Permission box to read ÂScripts and ExecutablesÂ
# Click the ÂDocuments tab.
@@ -79,28 +79,23 @@
++ Test the PHP installation
# First itÂs a good idea to stop and start the IIS services. I found it much easier and cleaner to do this from a Command Prompt. So open a Command Prompt and type:
- * {{net stop iisadmin <enter>}}
+ * net stop iisadmin <enter>
* Say ÂYESÂ to the following message: _
-<code>
-The following services are dependent on the IIS Admin Service service.
-Stopping the IIS Admin Service service will also stop these services.
-World Wide Web Publishing Service
-HTTP SSL
+The following services are dependent on the IIS Admin Service service. _
+Stopping the IIS Admin Service service will also stop these services. _
+World Wide Web Publishing Service _
+HTTP SSL _
Do you want to continue this operation? (Y/N) [N]:
-</code>
# The services will stop and you will be returned to the Command Prompt. To start the IIS services type: _
-<code>
net start w3svc <enter>
-</code>
# Open notepad and enter the following text: _
-<code>
<? phpinfo(); ?>
-</code>
-# Save the file as {{C:\Inetpub\wwwroot\phptest.php}} _
+# Save the file as C:\Inetpub\wwwroot\phptest.php _
CAUTION: DonÂt forget that Windows will try to add .txt to the end of the filename.
-# Open your favorite browser and go to http://hostname/phptest.php If all is well youÂll see: _
+# Open your favorite browser and go to http://hostname/phptest.php If all is well youÂll see:
+
<code>
PHP Version 4.3.7RC1
System
@@ -133,31 +128,27 @@
++ Install PEAR Using the Provided PHP Scripts
# Open a Command Prompt
-# CD to {{C:\php}}
-# Execute: {{go-pear.bat <enter>}}. YouÂll see: _
-<code>
-Welcome to go-pear!
-
-Go-pear will install the 'pear' command and all the files needed by
-it. This command is your tool for PEAR installation and maintenance.
-
-Go-pear also lets you download and install the PEAR packages bundled
-with PHP: DB, Net_Socket, Net_SMTP, Mail, XML_Parser, PHPUnit-0.6.2.
-
+# CD to C:\php
+# Execute: go-pear.bat <enter>. YouÂll see: _
+Welcome to go-pear! _
+ _
+Go-pear will install the 'pear' command and all the files needed by _
+it. This command is your tool for PEAR installation and maintenance. _
+ _
+Go-pear also lets you download and install the PEAR packages bundled _
+with PHP: DB, Net_Socket, Net_SMTP, Mail, XML_Parser, PHPUnit-0.6.2. _
+ _
If you wish to abort, press Control-C now, or press Enter to continue:
-</code>
# Press Enter to continue. YouÂll see: _
-<code>
-HTTP proxy (http://user:password@proxy.myhost.com:port), or Enter for none:
-</code>
+HTTP proxy (http://user:password@proxy.myhost.com:port), or Enter for none::
# Enter the proxy information if needed, otherwise Enter to continue. YouÂll see: _
+Below is a suggested file layout for your new PEAR installation. To _
+change individual locations, type the number in front of the _
+directory. Type 'all' to change all of them or simply press Enter to _
+accept these locations. _
<code>
-Below is a suggested file layout for your new PEAR installation. To
-change individual locations, type the number in front of the
-directory. Type 'all' to change all of them or simply press Enter to
-accept these locations.
1. Installation prefix : C:\php
2. Binaries directory : $prefix
3. PHP code directory ($php_dir) : $prefix\pear
4. Documentation base directory : $php_dir\docs
@@ -214,10 +205,10 @@
<code>
php.ini <C:\WINDOWS\php.ini> include_path updated.
Note: this entry is added at the very bottom of your php.ini.
-Current include path : .;c:\php4\pear
-Configured directory : C:\php\pear
+Current include path : .;c:\php4\pear
+Configured directory : C:\php\pear
Currently used php.ini (guess) : C:\WINDOWS\php.ini
Press Enter to continue:
</code>
# Press Enter and youÂll see: _
@@ -232,36 +223,36 @@
Press any key to continue . . .
</code>
# Press any key to return to the command prompt.
- # Browse to {{C:\php}} and double-click on {{PEAR_ENV.reg}} to import the registry information.
- # Next add the PEAR packages which are required by Horde (You should already be in {{C:\php}}, if not CD to that directory):
- * Log  From the command prompt: {{pear install log <enter>}}. Ignore the message: Optional dependencies: 'sqlite' PHP extension is recommended to utilize some features.
- * Mail Mime  From the command prompt: {{pear install mail_mime <enter>}}
- * Date -- From the command prompt: {{pear install date <enter>}}
- * Auth_SASL -- From the command prompt: {{pear install auth_sasl <enter>}}
+ # Browse to C:\php and double-click on PEAR_ENV.reg to import the registry information.
+ # Next add the PEAR packages which are required by Horde (You should already be in C:\php, if not CD to that directory):
+ * Log  From the command prompt: pear install log <enter>. Ignore the message: Optional dependencies: 'sqlite' PHP extension is recommended to utilize some features.
+ * Mail Mime  From the command prompt: pear install mail_mime <enter>
+ * Date -- From the command prompt: pear install date <enter>
+ * Auth_SASL -- From the command prompt: pear install auth_sasl <enter>
* HTTP_Request -- Has pre-requisites. Follow this path:
- * From the command prompt: {{pear install net_url <enter>}}
- * From the command prompt: {{pear upgrade net_socket <enter>}}
- * From the command prompt: {{pear install http_request <enter>}}
- * File: -- From the command prompt: {{pear install file <enter>}}
+ * From the command prompt: pear install net_url <enter>
+ * From the command prompt: pear upgrade net_socket <enter>
+ * From the command prompt: pear install http_request <enter>
+ * File: -- From the command prompt: pear install file <enter>
* Services_Weather -- Has pre-requisites. Follow this path:
- * From the command prompt: {{pear install cache <enter>}}
- * From the command prompt: {{pear install net_dime-beta <enter>}}
- * From the command prompt: {{pear install soap-beta <enter>}}
- * From the command prompt: {{pear install xml_util <enter>}}
- * From the command prompt: {{pear upgrade xml_parser <enter>}}
- * From the command prompt: {{pear upgrade xml_serializer <enter>}}
- * From the command prompt: {{pear install services_weather <enter>}}
- * Just for grins and giggles execute {{pear upgrade-all <enter>}}
+ * From the command prompt: pear install cache <enter>
+ * From the command prompt: pear install net_dime-beta <enter>
+ * From the command prompt: pear install soap-beta <enter>
+ * From the command prompt: pear install xml_util <enter>
+ * From the command prompt: pear upgrade xml_parser <enter>
+ * From the command prompt: pear upgrade xml_serializer <enter>
+ * From the command prompt: pear install services_weather <enter>
+ * Just for grins and giggles execute pear upgrade-all <enter>
++ Install !MySQL 4.0.18
-# Extract the files from {{mysql-4.0.20a-win.zip}} into a temporary folder.
-# Browse to that folder and double-click on {{SETUP.EXE}}.
+# Extract the files from mysql-4.0.20a-win.zip into a temporary folder.
+# Browse to that folder and double-click on SETUP.EXE.
# The installation wizard will start. You can simply accept all of the defaults. Click the Finish button when the installation finished.
-# Optionally add {{C:\mysql\bin}} to the system path. I do this out of convenience. It makes it easier when you execute the Horde DB scripts.
+# Optionally add ÂC:\mysql\bin to the system path. I do this out of convenience. It makes it easier when you execute the Horde DB scripts.
# Open notepad or your favorite text editor and enter the following text: _
<code>
[mysqld]
# set basedir to your installation path
@@ -272,10 +263,10 @@
[WinMySQLAdmin]
Server=C:\\mysql\\bin\\mysqld-nt.exe
QueryInterval=10
</code>
-# If you installed !MySQL into a different folder youÂll need to change the {{basedir =}} to point to your installation point. Additionally you need to add a different path to the system path variable. If you want to store your databases in a different location, create that folder structure and change the {{datadir=}} to point to that location. Beware that if you want to use back slashes in your my.ini, you need to use \\ otherwise use forward slashes.
-# Save the file as {{C:\Windows\my.ini}} _
+# If you installed !MySQL into a different folder youÂll need to change the Âbasedir =Â to point to your installation point. Additionally you need to add a different path to the system path variable. If you want to store your databases in a different location, create that folder structure and change the Âdatdir=Â to point to that location. Beware that if you want to use back slashes in your my.ini, you need to use \\ otherwise use forward slashes.
+# Save the file as C:\Windows\my.ini _
CAUTION: DonÂt forget that Windows will try to add .txt to the end of the filename.
# Open a Command Prompt and give !MySQL a test by entering: _
<code>
mysqld Âconsole <enter>
@@ -322,36 +313,36 @@
++ Install Aspell 0.05-3 with the English dictionary.
-# Double-click {{Aspell-0-50-3-3-Setup.exe}} to start the Aspell installation wizard.
-# Click the {{Next >}} button twice.
-# Change the Destination Directory to {{C:\aspell}} and click the {{Next >}} button.
+# Double-click Aspell-0-50-3-3-Setup.exe to start the Aspell installation wizard.
+# Click the Next > button twice.
+# Change the Destination Directory to C:\aspell and click the Next > button.
# Accept the defaults for the remainder of the installation wizard. The last screen will ask if you want to view manual.html. Leave it checked if you do, otherwise uncheck it and click the Finish button.
-# Double-click {{Aspell-en-0.50-2-3.exe}} to start the Aspell dictionary installation wizard.
+# Double-click Aspell-en-0.50-2-3.exe to start the Aspell dictionary installation wizard.
# The installer should find your base Aspell installation directory and simply add the dictionary so you should be able to accept the defaults for the entire installation wizard.
-# You can type {{\aspell\bin\aspell Âconfig <enter>}} at a Command Prompt to see your current configuration.
+# You can type \aspell\bin\aspell Âconfig <enter> at a Command Prompt to see your current configuration.
++ Install !WinCVS
-# Extract the contents of {{!WinCvs13b17-2.zip}} to a temporary folder.
-# Execute {{setup.exe}} to start the installation wizard.
-# Click the {{Next >}} button
-# Click ÂI accept the agreement radio button then the {{Next >}} button twice.
-# If desired change the destination directory and click the {{Next >}} button. IÂm keeping things consistent so I changed the destination directory to {{C:\!WinCVS}}.
-# If desired, change the installation type and click the {{Next >}} button. As I said earlier, IÂm only interested in the command line version so I changed the installation to custom and unchecked everything except ÂCore executable files and ÂCommand line client filesÂ.
-# Check ÂDonÂt create a Start Menu folder then click the {{Next >}} button
-# Uncheck ÂCreate a desktop item and ÂCreate a shell context menu and click the {{Next >}} button.
+# Extract the contents of !WinCvs13b17-2.zip to a temporary folder.
+# Execute setup.exe to start the installation wizard.
+# Click the Next > button
+# Click ÂI accept the agreement radio button then the Next > button twice.
+# If desired change the destination directory and click the Next > button. IÂm keeping things consistent so I changed the destination directory to C:\!WinCVS.
+# If desired, change the installation type and click the Next > button. As I said earlier, IÂm only interested in the command line version so I changed the installation to custom and unchecked everything except ÂCore executable files and ÂCommand line client filesÂ.
+# Check ÂDonÂt create a Start Menu folder then click the Next > button
+# Uncheck ÂCreate a desktop item and ÂCreate a shell context menu and click the Next > button.
# Click the ÂInstall button then the ÂFinish button.
++ Checkout Horde and Horde Framework Modules from CVS.
-The first item to consider is where to put your Horde installation. Like I said I have a relatively small installation, however I support two domains. IÂm writing this document while installing Horde on my development server which is much different than my production server. So IÂm going to choose C:\Inetpub\horde as my installation point. This seen the easiest place to put Horde, plus if you set the doc_root directive in your php.ini to {{C:\Inetpub}}, it keeps things simple. In any case, I think itÂs important to give some thought to where you want Horde to live. NowÂ
here we goÂ
+The first item to consider is where to put your Horde installation. Like I said I have a relatively small installation, however I support two domains. IÂm writing this document while installing Horde on my development server which is much different than my production server. So IÂm going to choose C:\Inetpub\horde as my installation point. This seen the easiest place to put Horde, plus if you set the doc_root directive in your php.ini to C:\Inetpub, it keeps things simple. In any case, I think itÂs important to give some thought to where you want Horde to live. NowÂ
here we goÂ
# Open a Command Prompt
-# CD to {{C:\Inetpub}}
+# CD to C:\Inetpub
# Execute the following: _
<code>
SET CVSROOT=:pserver:cvsread at anoncvs.horde.org:/repository <enter>
\WinCVS\CVSNT\cvs login <enter>
@@ -367,33 +358,33 @@
<code>
\WinCVS\CVSNT\cvs co -r HEAD framework <enter>
</code>
# Now that you have the basic framework installed you can continue to check out other modules you want. Personally I use IMP, Ingo, Jonah, Klutz (for fun) Kronolith, Mnemo, Nag, Passwd, and Turba.
-# Once youÂve got all the modules you want execute {{\!WinCVS\CVSNT\cvs logout <enter>}}.
-# CD to {{Inetpub\horde\config}} directory
-# Execute {{copy *.dist *. <enter>}}
-# If youÂve downloaded any other modules, CD into their respective config (e.g. {{\imp\config}}) folders and execute the copy command from step #10.
+# Once youÂve got all the modules you want execute \!WinCVS\CVSNT\cvs logout <enter>.
+# CD to Inetpub\horde\config directory
+# Execute copy *.dist *. <enter>
+# If youÂve downloaded any other modules, CD into their respective config (e.g. \imp\config) folders and execute the copy command from step #10.
++ Install the Horde Framework.
Before moving on we need to install the Horde Framework. Follow these steps to complete this process.
# Open a Command Prompt.
-# CD to {{C:\Inetpub\horde\framework}}
-# Execute {{\php\cli\php Âq install-packages.php <enter>}}
-Note that if you do not specify the path to the client php executable the system will generate a ÂBad Option error message. This is one because the system path specifies {{C:\php}} and the {{php.exe}} that lives there is the CGI executable.
+# CD to C:\Inetpub\horde\framework
+# Execute \php\cli\php Âq install-packages.php <enter>
+Note that if you do not specify the path to the client php executable the system will generate a ÂBad Option error message. This is one because the system path specifies C:\php and the php.exe that lives there is the CGI executable.
++ Add the Horde Site to IIS6.
-# Click "Start -> Administrative Tools -> Internet Information Services (IIS) Manger".
+# Click Start-Administrative Tools-Internet Information Services (IIS) Manger.
# Expand the local computer tree then right-click the Web Sites folder and select New then Web SiteÂ
-# The Web Site Creation Wizard will start. Simply click the {{Next >}} button to continue.
-# Enter a description in the Description: box and click the {{Next >}} button.
-# Set the appropriate IP Address and Port settings. The defaults should be fine. Click the {{Next >}} button.
-# Enter {{C:\Inetpub\}} for the path. Leave ÂAllow anonymous access to this Web site checked and click the Next > button.
-# Check Execute (Such as ISAPI application or CGI) and click the {{Next >}} button.
-# Click the {{Finish}} button.
+# The Web Site Creation Wizard will start. Simply click the Next > button to continue.
+# Enter a description in the Description: box and click the Next > button.
+# Set the appropriate IP Address and Port settings. The defaults should be fine. Click the Next > button.
+# Enter C:\Inetpub\ for the path. Leave ÂAllow anonymous access to this Web site checked and click the Next > button.
+# Check Execute (Such as ISAPI application or CGI) and click the Next > button.
+# Click the Finish button.
# Stop the Default Web Site using the Stop item button on the IIS Manager Tool bar.
# Start your new web site using the Start item button on the IIS Manager Tool bar.
If you added PHP to the ÂWeb Sites folder you can move onto the next step. Otherwise youÂll need to repeat the from the ÂAdd PHP to IIS6 Web Sites section above steps on your new web site.
More information about the cvs
mailing list