Changeset 26384 for gs3-extensions/fedora/README
- Timestamp:
- 2012-10-24T16:00:45+13:00 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
gs3-extensions/fedora/README
r26382 r26384 187 187 188 188 Deleting a Fedora GS3 collection is accomplished with the following 2 steps: 189 - g2f-deletecol.pl -hostname localhost -port 8383 -password pounamu -removeold -collectdir /<GS3>/web/sites/localsite/collect fedora1 189 - Run the g2f-deletecol.pl script over the collection to be deleted. Assuming the collection is called fedora1, you'd run: 190 g2f-deletecol.pl -hostname localhost -port 8383 -password pounamu -removeold -collectdir /<GS3>/web/sites/localsite/collect fedora1 190 191 - manually delete the Greenstone collection directory from the filesystem 191 192 … … 215 216 216 217 All these files get converted to filenames without the ".in" suffix upon installation, and placeholder strings in these template files get replaced. The replacements are on the strings 217 - @GSDL3SRCHOME@ ,218 - @FEDORA_HOME@ (set to gsdl3srchome/ext/fedora3) ,219 - @tomcatserver@ ,220 - @tomcatport@ ,221 - @tomcatshutdownport@ ,222 - @fedorapassw@ .218 - @GSDL3SRCHOME@ 219 - @FEDORA_HOME@ (set to gsdl3srchome/ext/fedora3) 220 - @tomcatserver@ 221 - @tomcatport@ 222 - @tomcatshutdownport@ 223 - @fedorapassw@ 223 224 Except for the first, which needs to be set when running the Fedora extension's ant targets, all the remaining ones can be specified 224 225 … … 244 245 a. The changes to web.xml are that the authorisation filters are commented out: 245 246 246 <!-- <filter-mapping> 247 <!-- 248 <filter-mapping> 247 249 <filter-name>EnforceAuthnFilter</filter-name> 248 250 <servlet-name>AxisServlet</servlet-name> … … 338 340 ******************************************************************************************************************** 339 341 340 When installing Fedora, you can choose to install it outside Greenstone, and also instruct it to use its own tomcat. However, in the following , /GS3/ext/fedora3 is still assumed to be FEDORA_HOME and hence Fedora's installation location and it's assumed tobe installed to use Greenstone's tomcat.342 When installing Fedora, you can choose to install it outside Greenstone, and also instruct it to use its own tomcat. However, in the following instructions, Fedora's installation location (FEDORA_HOME) is still taken to be /GS3/ext/fedora3, since it's assumed Fedora is be installed to use Greenstone's tomcat. 341 343 342 344 The Fedora GSearch war file will need to be unpacked in the tomcat/webapps folder of whichever tomcat Fedora is using. In the following, this is still Greenstone's tomcat. 343 345 344 Wherever Fedora is installed, that's where the digital objects and their datastreams will be stored, and that's where Fedora GSearch will create its GSearch index.346 In whichever location Fedora is installed, that's where Fedora will store its digital objects and their datastreams, and that's where Fedora GSearch will create its GSearch index. 345 347 346 348 … … 532 534 2. </GS3/ext/>fedora3/server/logs/fedora.log for Fedora error logging. 533 535 534 3. To turn on FedoraGSearch's logging of debug statements (Huge files, can reach 500 Mb in a day. Do this only when debugging): 536 3. To turn on FedoraGSearch's logging of debug statements (Huge files, can reach 500 Mb in a day if rebuilding the demo collection. So you may want to switch this off when not debugging by setting the debug level to INFO): 537 535 538 - /<GS3>/packages/tomcat/webapps/fedoragsearch/WEB-INF/classes/log4j.xml is already set to output DEBUG statements and higher logging levels 536 539 - So open </GS3/ext/>fedora3/server/logs/fedoragsearch.daily.log to look at debug messages in case fedoragsearch doesn't work as expected.
Note:
See TracChangeset
for help on using the changeset viewer.