| 1 | Greenstone 3 (GSDL3)
|
|---|
| 2 | Copyright (C) 2003 New Zealand Digital Libraries, University Of Waikato
|
|---|
| 3 | Greenstone3 comes with ABSOLUTELY NO WARRANTY; for details see LICENSE.txt
|
|---|
| 4 | This is free software, and you are welcome to redistribute it
|
|---|
| 5 |
|
|---|
| 6 | Installing Greenstone
|
|---|
| 7 | ---------------------------------------------------------
|
|---|
| 8 |
|
|---|
| 9 | Download the appropriate installer from sourceforge.net/projects/greenstone3 and run it.
|
|---|
| 10 |
|
|---|
| 11 | See 'Installing from a Source Distribution' section below for extra notes about installing from Source.
|
|---|
| 12 |
|
|---|
| 13 | See the README-SVN.txt file for extra notes about installing directly from SVN.
|
|---|
| 14 |
|
|---|
| 15 | Greenstone 3 requires Java and Ant to run. These may be installed during
|
|---|
| 16 | Greenstone installation.
|
|---|
| 17 |
|
|---|
| 18 | Running Greenstone:
|
|---|
| 19 | ---------------------------------------------------------
|
|---|
| 20 |
|
|---|
| 21 | To start up Greenstone, select Greenstone3 Digital Library from the Start menu
|
|---|
| 22 | (Windows), or run gs3-server.sh/bat. This launches a small server program
|
|---|
| 23 | which starts up Tomcat and launches a browser. A small window pops up which
|
|---|
| 24 | allows you to change some settings for your library and restart the Tomcat
|
|---|
| 25 | server. Closing this program will stop Tomcat running.
|
|---|
| 26 |
|
|---|
| 27 | Alternatively, you can start Tomcat directly through using Ant. 'ant start',
|
|---|
| 28 | 'ant restart' and 'ant stop' starts, restarts and shuts down Tomcat,
|
|---|
| 29 | respectively. This will only start/stop a local server (one installed by
|
|---|
| 30 | Greenstone). You will need to manually start/stop an external Tomcat
|
|---|
| 31 | (see below for notes about using a version of Tomcat external to Greenstone).
|
|---|
| 32 |
|
|---|
| 33 | Once the Tomcat server is running, Greenstone will be available in a browser
|
|---|
| 34 | at "http://localhost:8080/greenstone3" (or whatever port you specified
|
|---|
| 35 | during the installation process).
|
|---|
| 36 | You can change the port number using File->Settings in the server program, or
|
|---|
| 37 | by changing the 'tomcat.port' property in build.properties, then running
|
|---|
| 38 | 'ant configure'.
|
|---|
| 39 |
|
|---|
| 40 | Building Collections:
|
|---|
| 41 | ----------------------------------------------------------
|
|---|
| 42 |
|
|---|
| 43 | You need to have Perl installed and on your PATH. Perl is included as part of
|
|---|
| 44 | the Windows binary distribution.
|
|---|
| 45 |
|
|---|
| 46 | You can build collections using the Greenstone Librarian Interface (GLI).
|
|---|
| 47 | To start GLI, select it from the Start Menu (Windows), run 'ant gli" from the
|
|---|
| 48 | greenstone3 directory, or cd to greenstone3/gli and run gli.sh/bat.
|
|---|
| 49 |
|
|---|
| 50 | Once you have created and built a collection, you can see it by clicking 'Preview collection' on the Build panel.
|
|---|
| 51 |
|
|---|
| 52 | Greenstone Admin
|
|---|
| 53 | ------------------------------------------------------
|
|---|
| 54 |
|
|---|
| 55 | The Greenstone admin tool is currently under development.
|
|---|
| 56 |
|
|---|
| 57 | Using SOAP:
|
|---|
| 58 | -------------------------------------------------------
|
|---|
| 59 |
|
|---|
| 60 | Greenstone comes with Apache Axis installed as part of the Greenstone web
|
|---|
| 61 | application. However, no SOAP services are deployed by default.
|
|---|
| 62 |
|
|---|
| 63 | To deploy a SOAP server for localsite, run 'ant deploy-localsite'. You should
|
|---|
| 64 | now be able to see all localsite's collections through the gateway servlet.
|
|---|
| 65 | (http://localhost:8080/greenstone3/gateway)
|
|---|
| 66 |
|
|---|
| 67 | To set up a SOAP server on a new site, run
|
|---|
| 68 | ant soap-deploy-site
|
|---|
| 69 | This will prompt you for the sitename (the directory name), and the site uri
|
|---|
| 70 | - this should be a unique identifier for the site's web service.
|
|---|
| 71 |
|
|---|
| 72 | For a non-interactive version, run
|
|---|
| 73 | ant -Daxis.sitename=xxx -Daxis.siteuri=yyy soap-deploy-site
|
|---|
| 74 |
|
|---|
| 75 | The service is accessible at
|
|---|
| 76 | http://localhost:8080/greenstone3/services/<siteuri>
|
|---|
| 77 |
|
|---|
| 78 | (or http://<computer-web-address>:<port>/greenstone3/services/<siteuri>)
|
|---|
| 79 |
|
|---|
| 80 | Note: Deploying a SOAP service for any site other than localsite requires
|
|---|
| 81 | the Greenstone source code to be installed. This is not installed by default
|
|---|
| 82 | for a binary distribution. To get the source code, re-run the installer,
|
|---|
| 83 | select custom install and deselect everything except the source code.
|
|---|
| 84 |
|
|---|
| 85 | Using External Tomcat:
|
|---|
| 86 | ---------------------------------------------------
|
|---|
| 87 |
|
|---|
| 88 | If you want to use an existing Tomcat, set the path to its base directory
|
|---|
| 89 | in build.properties (tomcat.installed.path). Also set the tomcat.port
|
|---|
| 90 | property to be the port you are running Tomcat on, and change tomcat.server
|
|---|
| 91 | if the web address is not localhost. Then run 'ant configure'.
|
|---|
| 92 |
|
|---|
| 93 | You will need to modify the Tomcat setup slightly.
|
|---|
| 94 |
|
|---|
| 95 | 1. Tell Tomcat about the Greenstone web app. There are two ways to do this.
|
|---|
| 96 |
|
|---|
| 97 | A. Copy the file greenstone3/resources/tomcat/greenstone3.xml into Tomcat's
|
|---|
| 98 | conf/Catalina/localhost directory. You'll need to edit the file and
|
|---|
| 99 | replace @gsdl3webhome@ with the full path to the web directory of your
|
|---|
| 100 | greenstone 3 installation. Any path separator is fine here ('/', '\\', '\').
|
|---|
| 101 |
|
|---|
| 102 | B. Alternatively, you can move (and rename) the greenstone3/web directory to
|
|---|
| 103 | tomcat/webapps/greenstone3 (i.e. the resulting directories will be like
|
|---|
| 104 | tomcat/webapps/greenstone3/WEB-INF, no web directory). This should be done
|
|---|
| 105 | after running the initial 'ant install'.
|
|---|
| 106 |
|
|---|
| 107 | You will need to set the web.home property in the build.properties file
|
|---|
| 108 | i.e.
|
|---|
| 109 | web.home=${tomcat.installed.path}/webapps/greenstone3
|
|---|
| 110 | And then run 'ant configure' to reset gsdl3home.
|
|---|
| 111 |
|
|---|
| 112 | 2. Set up the JNI libraries and Java wrappers.
|
|---|
| 113 | JNI libraries and their Java wrappers cannot go into the web app. The
|
|---|
| 114 | libraries need to be loaded by the same class loader as their wrappers. The
|
|---|
| 115 | libraries need to be in java.library.path, and I think get loaded by the
|
|---|
| 116 | system class loader.
|
|---|
| 117 | The wrappers need to be loaded by this too.
|
|---|
| 118 |
|
|---|
| 119 | These JNI bits are located by default in the lib/jni directory. There are
|
|---|
| 120 | two ways to get them into Tomcat:
|
|---|
| 121 | A: Keep all the Greenstone stuff inside the greenstone3 directory, and just
|
|---|
| 122 | modify the environment that Tomcat runs in
|
|---|
| 123 |
|
|---|
| 124 | Set LD_LIBRARY_PATH (GNU/Linux), DYLD_LIBRARY_PATH (Mac OS X) or PATH/Path
|
|---|
| 125 | (windows) to include the greenstone3/lib/jni directory.
|
|---|
| 126 | Add all the jar files in greenstone3/lib/jni directory to the CLASSPATH,
|
|---|
| 127 | then edit tomcats setclasspath.sh/bat to use the system CLASSPATH.
|
|---|
| 128 | (in setclasspath.bat, change
|
|---|
| 129 | set CLASSPATH=%JAVA_HOME%\lib\tools.jar
|
|---|
| 130 | to
|
|---|
| 131 | set CLASSPATH=%JAVA_HOME%\lib\tools.jar;%CLASSPATH%
|
|---|
| 132 |
|
|---|
| 133 | in setclasspath.sh, change
|
|---|
| 134 | # Set standard CLASSPATH
|
|---|
| 135 | if [ "$1" = "debug" -o "$1" = "javac" ] ; then
|
|---|
| 136 | CLASSPATH="$JAVA_HOME"/lib/tools.jar
|
|---|
| 137 | fi
|
|---|
| 138 |
|
|---|
| 139 | to
|
|---|
| 140 | # Set standard CLASSPATH
|
|---|
| 141 | if [ "$1" = "debug" -o "$1" = "javac" ] ; then
|
|---|
| 142 | CLASSPATH="$JAVA_HOME"/lib/tools.jar:"$CLASSPATH"
|
|---|
| 143 | fi
|
|---|
| 144 |
|
|---|
| 145 |
|
|---|
| 146 | B: Copy the files into Tomcat installation:
|
|---|
| 147 | Move the greenstone3/lib/jni jar files into tomcat's shared/lib directory.
|
|---|
| 148 | Move the greenstone3/lib/jni library files (.so for GNU/Linux, .jnilib for
|
|---|
| 149 | Mac OS X .dll for Windows) into shared/classes, and set LD_LIBARARY_PATH
|
|---|
| 150 | (GNU/Linux), DYLD_LIBRARY_PATH (Mac OS X) or PATH/Path (Windows) to include
|
|---|
| 151 | this directory.
|
|---|
| 152 | This has the advantage that you can use this for other webapps without
|
|---|
| 153 | modifying the Tomcat environment.
|
|---|
| 154 |
|
|---|
| 155 | Once all these changes have been made, you will need to restart the Tomcat
|
|---|
| 156 | server for them to take effect.
|
|---|
| 157 |
|
|---|
| 158 |
|
|---|
| 159 | Notes for Mac OS
|
|---|
| 160 | ------------------------------------------------
|
|---|
| 161 |
|
|---|
| 162 | Set JAVA_HOME to be /Library/Java/Home
|
|---|
| 163 |
|
|---|
| 164 | Notes for Windows
|
|---|
| 165 | -----------------------------------------------
|
|---|
| 166 |
|
|---|
| 167 | You can set environment variables by going to
|
|---|
| 168 | Control Panel->System->Advanced->Environment Variables.
|
|---|
| 169 |
|
|---|
| 170 | Installing from a Source Distribution
|
|---|
| 171 | ----------------------------------------------
|
|---|
| 172 |
|
|---|
| 173 | Download the greenstone-3.xx-src.tar.gz package from
|
|---|
| 174 | sourceforge.net/projects/greenstone3, and unpack it.
|
|---|
| 175 |
|
|---|
| 176 | In the greenstone3 directory, edit the build.properties file and run
|
|---|
| 177 | ant install
|
|---|
| 178 |
|
|---|
| 179 | Tomcat will be installed as part of the prepare process. To stop this set the
|
|---|
| 180 | tomcat.installed.path to be the root of an existing Tomcat installation.
|
|---|
| 181 |
|
|---|
| 182 | * Solaris notes:
|
|---|
| 183 | ** Make sure /usr/local/bin is in your PATH ahead of /usr/bin etc.
|
|---|
| 184 | ** Add /usr/local/lib to LD_LIBARY_PATH
|
|---|
| 185 | ** The gdbm database files (gs2mgdemo and gs2mgppdemo collections) were generated on a Mac, and don't seem to be compatible with Solaris. A text version of the file (database.txt) is included in the index/text directory. After installing Greenstone, and before running it, you'll need to:
|
|---|
| 186 | in greenstone3/gs2build directory: run 'source setup.bash' (Or if you have greenstone 2 already installed, run 'source setup.bash' in your greenstone 2 installation)
|
|---|
| 187 | in greenstone3/web/sites/localsite/collect/gs2mgdemo/index/text directories, run 'txt2db gs2mgdemo.bdb < database.txt'
|
|---|
| 188 | in greenstone3/web/sites/localsite/collect/gs2mgppdemo/index/text directories, run 'txt2db gs2mgppdemo.bdb < database.txt'
|
|---|
| 189 | ** GLI shell scripts may not work like "./gli4gs3.sh". In this case, run "bash ./gli4gs3.sh" etc. You will need to compile GLI by hand (run "bash ./makegli.sh" in greenstone3/gli directory).
|
|---|
| 190 | ** Set CC=gcc environment variable if you don't have cc, before running ant install.
|
|---|
| 191 |
|
|---|
| 192 | * Windows notes:
|
|---|
| 193 | ** You need to have Visual Studio installed to compile the C/C++ code. Set the path to the setup file in build.properties (compile.windows.c++.setup).
|
|---|
| 194 |
|
|---|
| 195 | Configuring your installation:
|
|---|
| 196 | --------------------------------------------------------
|
|---|
| 197 |
|
|---|
| 198 | The file build.properties contains various parameters that can be set by the user. Please check these settings before running the install.
|
|---|
| 199 | Note, either forward slash '/' or double backslash '\\' can be used as path separators in the build.properties file, but not single backslash '\'.
|
|---|
| 200 |
|
|---|
| 201 | Greenstone 3 comes with Tomcat bundled in.
|
|---|
| 202 |
|
|---|
| 203 | If you already have Tomcat running, you can set the 'tomcat.installed.path' property (in build.properties) to the base directory of your Tomcat installation, and Greenstone will not use its own Tomcat. (You can delete the packages/tomcat directory if you like.) Please read the section "Using External Tomcat" for details about how to configure Tomcat for Greenstone.
|
|---|
| 204 |
|
|---|
| 205 | Mac OS X: You need to have GDBM installed (http://www.gnu.org/software/gdbm/gdbm.html). Please set the gdbm.installed.path property (in build.properties) to the root of your gdbm installation if it is not installed in a default place. If you run GLI or GS2 collection building from the command line, you will need to set the DYLD_LIBRARY_PATH environment variable to include <path-to-gdbm>/lib.
|
|---|
| 206 |
|
|---|
| 207 | The install target will ask you if you accept the properties before starting.
|
|---|
| 208 | To suppress this prompt, use the -Dproperties.accepted=yes flag. E.g.
|
|---|
| 209 | ant -Dproperties.accepted=yes install
|
|---|
| 210 |
|
|---|
| 211 | To log the output in build.log, run
|
|---|
| 212 | ant -Dproperties.accepted=yes -logfile build.log install
|
|---|
| 213 |
|
|---|
| 214 | Recompiling
|
|---|
| 215 | -------------------------------------------------------
|
|---|
| 216 | To recompile your Greenstone3 installation, in the top level greenstone3 directory, run:
|
|---|
| 217 |
|
|---|
| 218 | ant clean (use distclean instead if you want to regenerate the C++ Makefiles)
|
|---|
| 219 | ant configure
|
|---|
| 220 | ant configure-c++
|
|---|
| 221 | ant compile
|
|---|
| 222 |
|
|---|
| 223 | The compile target does Java and C/C++ compilation. On Windows, you need to set the compile.windows.c++.setup property to be your Visual Studio setup batch file.
|
|---|
| 224 |
|
|---|
| 225 | Any sub targets can be run by themselves. Run 'ant -projecthelp' for a list of public targets, otherwise you can look at the build.xml file to see which targets depend on other ones.
|
|---|
| 226 |
|
|---|
| 227 |
|
|---|
| 228 | Notes on Versions of Third Party packages
|
|---|
| 229 | -----------------------------------------------
|
|---|
| 230 |
|
|---|
| 231 | Tomcat:
|
|---|
| 232 |
|
|---|
| 233 | apache-tomcat-5.5.12.zip: latest production quality release as of October, 2005.
|
|---|
| 234 | apache-tomcat-5.5.12-compat.zip: Tomcat 5 requires Java 1.5. If using Java 1.4, need to use this compatibility module.
|
|---|
| 235 |
|
|---|
| 236 | website: http://tomcat.apache.org/
|
|---|
| 237 | download: http://tomcat.apache.org/download-55.cgi
|
|---|
| 238 |
|
|---|
| 239 | Axis:
|
|---|
| 240 |
|
|---|
| 241 | Apache Web Services Project, SOAP implementation. Axis is a follow on project to Apache SOAP
|
|---|
| 242 |
|
|---|
| 243 | axis-bin-1_2_1.zip: latest stable release as of October, 2005
|
|---|
| 244 | website: http://ws.apache.org/axis/
|
|---|
| 245 | download: http://www.apache.org/dyn/closer.cgi/ws/axis/1_2_1
|
|---|
| 246 |
|
|---|
| 247 | All available from www.greenstone.org/gs3files if not available at their respective websites.
|
|---|
| 248 |
|
|---|
| 249 | Other Notes:
|
|---|
| 250 | -------------------------------------------------
|
|---|
| 251 |
|
|---|
| 252 | See greenstone3/docs/manual/manual.pdf for more details about the software and installation etc.
|
|---|
| 253 |
|
|---|
| 254 | Output is logged to web/logs. usage.log is a usage log, while greenstone.log is the error/message log. To change the level of logging, edit the web/WEB-INF/classes/log4j.properties file, and change the log4j.disable property. Valid values are TRACE, DEBUG, INFO, WARN, ERROR and FATAL.
|
|---|
| 255 |
|
|---|
| 256 | To prevent Tomcat showing directory listings, edit Tomcat's conf/web.xml file and set the value of the "listings" servlet parameter to false.
|
|---|
| 257 |
|
|---|
| 258 | To enable symlinks to files outside the webapp root directory, edit Tomcat's conf/Catalina/localhost/greenstone3.xml file, and set the allowLinking attribute in the Context element to true.
|
|---|
| 259 | (Note from Tomcat website: This flag MUST NOT be set to true on the Windows platform (or any other OS which does not have a case sensitive filesystem), as it will disable case sensitivity checks, allowing JSP source code disclosure, among other security problems.)
|
|---|
| 260 |
|
|---|
| 261 | The file web/WEB-INF/classes/global.properties is generated on install and contains some properties for the run time system.
|
|---|
| 262 |
|
|---|
