Changeset 26384 for gs3-extensions/fedora/README

Timestamp:

2012-10-24T16:00:45+13:00 (11 years ago)

Author:

ak19

Message:

Minor changes and updates to README. It also needed to updated in the tar.gz file since the instructions on using the delete collection script hadn't been added in there yet.

File:

• gs3-extensions/fedora/README (modified) (5 diffs)

gs3-extensions/fedora/README

@@ -187 +187 @@
 
 Deleting a Fedora GS3 collection is accomplished with the following 2 steps:
-- g2f-deletecol.pl -hostname localhost -port 8383 -password pounamu -removeold -collectdir /<GS3>/web/sites/localsite/collect fedora1
+- Run the g2f-deletecol.pl script over the collection to be deleted. Assuming the collection is called fedora1, you'd run:
+    g2f-deletecol.pl -hostname localhost -port 8383 -password pounamu -removeold -collectdir /<GS3>/web/sites/localsite/collect fedora1
 - manually delete the Greenstone collection directory from the filesystem
 
@@ -215 +216 @@
 
 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 
-- @GSDL3SRCHOME@, 
-- @FEDORA_HOME@ (set to gsdl3srchome/ext/fedora3), 
-- @tomcatserver@, 
-- @tomcatport@, 
-- @tomcatshutdownport@, 
-- @fedorapassw@. 
+- @GSDL3SRCHOME@
+- @FEDORA_HOME@ (set to gsdl3srchome/ext/fedora3)
+- @tomcatserver@
+- @tomcatport@
+- @tomcatshutdownport@
+- @fedorapassw@
 Except for the first, which needs to be set when running the Fedora extension's ant targets, all the remaining ones can be specified 
 
@@ -244 +245 @@
 a. The changes to web.xml are that the authorisation filters are commented out:
 
-<!--    <filter-mapping>
+<!--
+    <filter-mapping>
       <filter-name>EnforceAuthnFilter</filter-name>
       <servlet-name>AxisServlet</servlet-name>
@@ -338 +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 to be installed to use Greenstone's tomcat. 
+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. 
 
 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.
 
-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.
+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.
 
 
@@ -532 +534 @@
 2. </GS3/ext/>fedora3/server/logs/fedora.log for Fedora error logging.
 
-3. To turn on FedoraGSearch's logging of debug statements (Huge files, can reach 500 Mb in a day. Do this only when debugging):
+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):
+
 - /<GS3>/packages/tomcat/webapps/fedoragsearch/WEB-INF/classes/log4j.xml is already set to output DEBUG statements and higher logging levels
 - So open </GS3/ext/>fedora3/server/logs/fedoragsearch.daily.log to look at debug messages in case fedoragsearch doesn't work as expected.