About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

VuFind Documentation

Site Tools

You are here: start » installation » windows
Trace:
Warning: This page has not been updated in over over a year and may be outdated or deprecated.
installation:windows

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
installation:windows [2015/12/08 19:22] – ↷ Links adapted because of a move operation demiankatzinstallation:windows [2021/10/28 11:15] (current) – [4. Install PHP] demiankatz
Line 1: Line 1:
 ====== Installation ====== ====== Installation ======
- 
-// These instructions are for use with VuFind 2.x; for earlier versions, see the [[legacy:installation:windows|1.x instructions]].// 
  
 **These instructions assume that you are installing your MySQL database on the same server as VuFind itself and that you are using an installation path of c:\vufind** **These instructions assume that you are installing your MySQL database on the same server as VuFind itself and that you are using an installation path of c:\vufind**
Line 8: Line 6:
 ===== Requirements ===== ===== Requirements =====
  
-To satisfy VuFind's dependencies, make sure you install the software versions recommended on the [[..:requirements]] page.  You may use other versions at your own risk.+To satisfy VuFind's dependencies, make sure you install the software versions recommended on the [[requirements]] page.  You may use other versions at your own risk.
  
 These instructions assume that you are installing all software components separately.  Many developers use [[http://www.apachefriends.org/en/xampp-windows.html|XAMPP]] to install Apache, MySQL and PHP as a bundle.  XAMPP should not be used in a production environment, but it may save some time for a test server -- however, it works differently than separate component installation, so watch for XAMPP-related notes as you read. These instructions assume that you are installing all software components separately.  Many developers use [[http://www.apachefriends.org/en/xampp-windows.html|XAMPP]] to install Apache, MySQL and PHP as a bundle.  XAMPP should not be used in a production environment, but it may save some time for a test server -- however, it works differently than separate component installation, so watch for XAMPP-related notes as you read.
Line 70: Line 68:
   * LDAP (optional)   * LDAP (optional)
   * Multi-Byte String (optional, but recommended)   * Multi-Byte String (optional, but recommended)
-  * MySQL 
   * MySQLi   * MySQLi
   * PDO (with MySQL)   * PDO (with MySQL)
Line 84: Line 81:
   * It is possible that PHP will install some extensions without all of the necessary library files.  If this happens, starting up PHP will lead to a series of pop-up alerts.  To fix the problem, simply edit the php.ini file (usually found in c:\Program Files\PHP\, and also available via Start Menu shortcut) and comment out (by putting a semi-colon in front) the offending modules (found in lines like extension=php_*.dll).  If you actually need some of the affected modules, you may have to track down copies of the missing files; Google searches for error messages are usually helpful for this.   * It is possible that PHP will install some extensions without all of the necessary library files.  If this happens, starting up PHP will lead to a series of pop-up alerts.  To fix the problem, simply edit the php.ini file (usually found in c:\Program Files\PHP\, and also available via Start Menu shortcut) and comment out (by putting a semi-colon in front) the offending modules (found in lines like extension=php_*.dll).  If you actually need some of the affected modules, you may have to track down copies of the missing files; Google searches for error messages are usually helpful for this.
   * If you are using XAMPP instead of separate components, the installation process won't ask you about extensions.  Instead, you will have to manually uncomment the relevant lines in your php.ini file.   * If you are using XAMPP instead of separate components, the installation process won't ask you about extensions.  Instead, you will have to manually uncomment the relevant lines in your php.ini file.
-  * If you are a Voyager library, you will also need to install the PHP OCI Driver for Oracle – see [[..:installing_the_php_oci_driver_for_oracle|this page]] for detailed instructions.+  * If you are a Voyager library, you will also need to install the PHP OCI Driver for Oracle – see [[php_oci|this page]] for detailed instructions.
  
 ==== 5. Install the Java JDK ==== ==== 5. Install the Java JDK ====
 +
 +Next install JDK (the Java Development Kit) on the server – VuFind's searching back-end and MARC indexing tools rely on Java. Note that some VuFind components may be able to run using only the JRE (Java Runtime Environment), but the JDK is strongly recommended, and required for proper MARC indexing after release 3.1.
  
 You can download the JDK [[http://java.sun.com/javase/downloads/?intcmp=1281|here]].  You should be able to use all the default installation options. You can download the JDK [[http://java.sun.com/javase/downloads/?intcmp=1281|here]].  You should be able to use all the default installation options.
Line 146: Line 145:
 === Configuring Solr === === Configuring Solr ===
  
-The config files for each Solr index are currently set up to use relative paths.  Because Windows services run in a different user context with different working directories, Solr may have problems finding its index files.  If you skip this step, you may find that searches never yield any results.  To be on the safe side, you should reconfigure Solr to explicitly point out where the index files live. +Starting with VuFind 3.0, no special Solr configuration should be necessary for the software to run correctly in Windows. If you encounter problems in VuFind 2.x or earlier, it may be necessary to edit the various solrconfig.xml files under VuFind's Solr directory to change relative paths to absolute paths. 
- +==== 8. Start Solr ====
-In the following files: +
-    c:/vufind/solr/biblio/conf/solrconfig.xml +
-    c:/vufind/solr/authority/conf/solrconfig.xml +
-    c:/vufind/solr/stats/conf/solrconfig.xml +
- +
-Find the node: +
-    \config\dataDir +
- +
-And change the relative paths currently there to: +
-    c:/vufind/solr/biblio +
-    c:/vufind/solr/authority +
-    c:/vufind/solr/stats +
- +
-For example, you would change this: +
- +
-<code xml> +
-  <dataDir>${solr.data.dir:./solr/biblio}</dataDir>  +
-</code> +
- +
-to this: +
- +
-<code xml> +
-  <dataDir>c:/vufind/solr/biblio</dataDir>  +
-</code> +
- +
-==== 8. Start VuFind ====+
  
-Now that VuFind is installed and basic configuration is complete, you can start the server running.  See the [[..:Starting and Stopping VuFind]] page for details.+Now that VuFind is installed and basic configuration is complete, you can start the Solr server running.  See the [[administration:starting_and_stopping_solr|Starting and Stopping Solr]] page for details.
  
 ==== 9. Final Configuration ==== ==== 9. Final Configuration ====
Line 210: Line 183:
 === Locking Down Configurations === === Locking Down Configurations ===
  
-Once all configuration issues are successfully resolved, you will see a "Disable Auto Configuration" link on the "Auto Configure" page.  Click this to prevent future access to the install script.  If you need access again in the future, you can re-enable it by manually editing your [[..:config.ini]] file.+Once all configuration issues are successfully resolved, you will see a "Disable Auto Configuration" link on the "Auto Configure" page.  Click this to prevent future access to the install script.  If you need access again in the future, you can re-enable it by manually editing your [[configuration:files:config.ini]] file.
  
 ==== 10. Import Records ==== ==== 10. Import Records ====
  
-Import bib records using the instructions on the [[..:importing records]] page.+Import bib records using the instructions on the [[:indexing]] page.
  
 ==== Appendix: General Notes ==== ==== Appendix: General Notes ====
Line 242: Line 215:
  
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
installation/windows.1449602558.txt.gz · Last modified: 2015/12/08 19:22 by demiankatz