From 86ca5a3a7606016a905c3316dbe055d9568d18b5 Mon Sep 17 00:00:00 2001 From: jeb228 Date: Wed, 14 Jul 2010 14:32:20 +0000 Subject: [PATCH] NIHVIVO-721 Rebuild the search index every time the server starts. --- doc/install.txt | 26 +++++--------------------- 1 file changed, 5 insertions(+), 21 deletions(-) diff --git a/doc/install.txt b/doc/install.txt index b2c87f66..bd1c7392 100644 --- a/doc/install.txt +++ b/doc/install.txt @@ -30,7 +30,7 @@ are slightly different. Please consult developers.txt in this directory. * VI. Set Tomcat JVM Parameters * VII. Start Tomcat * VIII. Log in and add RDF data - * IX. Create an initial Lucene search index + * IX. Set the Contact Email Address (if using "Contact Us" form) * X. Setup Apache Tomcat Connector * XI. Configure Pellet Reasoner * XII. Was the Installation Successful? @@ -239,20 +239,8 @@ If you set the Vitro.smtpHost in Step IV and do NOT provide an email address in this step, your users will receive a java error in the interface. ------------------------------------------------------------------------------- - -X. Create an initial Lucene search index -Invoke the indexing servlet by requesting http://localhost:8080/vivo/SearchIndex - -You will not see any output to the browser (though this will change in future -versions). When your browser switches to a blank screen, the indexing has -completed and the search box on the Vitro portal will be usable. Individuals -that are created, edited, or deleted from the Vitro editing interface will -trigger incremental updates of the search index. - -------------------------------------------------------------------------------- - -XI. Set up Apache Tomcat Connector +X. Set up Apache Tomcat Connector It is recommended that a Tomcat Connector such as mod_jk be used to ensure that the site address does not include the port number (e.g. 8080) and an additional @@ -291,7 +279,7 @@ Locate the directive and update as follows: ------------------------------------------------------------------------------- -XII. Configure Pellet Reasoner +XI. Configure Pellet Reasoner VIVO uses the Pellet engine to perform reasoning, which runs in the background at startup and also when the knowledge base is edited. VIVO @@ -324,7 +312,7 @@ property entailments are not needed. ------------------------------------------------------------------------------- -XIII. Was the installation successful? +XII. Was the installation successful? If you have completed the previous steps, you have good indications that the installation was successful. @@ -332,9 +320,6 @@ installation was successful. * Step VII showed that Tomcat recognized the webapp, and that the webapp was able to present the initial page. * Step VIII verified that you can log in to the administrator account. -* Step X initialized the Lucene Search system. Though there is very little - feedback for a successful installation, there are dramatic indications - for failures. Here is a simple test to see whether the ontology files were loaded: * Click on the "Index" link on the upper left, below the logo. You should see @@ -368,8 +353,7 @@ Here is a test to see whether your system is configured to serve linked data: If the URI of the "test individual" is followed by "failed (400)" you are not successfully serving linked data. -Finally, test the search index (assuming you have created the initial Lucene -index in Step X). +Finally, test the search index. * The search box is on the right side, directly opposite the "Index" link. Type the word "Australia" into the box, and click on the "Search" button.You should see a page of results, with links to countries that