diff --git a/doc/install.html b/doc/install.html index e42283974..4340f690d 100644 --- a/doc/install.html +++ b/doc/install.html @@ -36,7 +36,7 @@ starting with an empty database, an empty Vitro home directory, and a Tomcat installation with no Vitro webapp. If you are upgrading a previous installation of Vitro, - you should consult the applicable “upgrade” file(s) in this directory. + you may need to adjust your procedure accordingly.



Introduction to the Vitro installation

@@ -271,7 +271,8 @@

IV. Specify deployment properties

- In the webapp directory of the Vitro distribution, copy the file example.deploy.properties + In the webapp/config directory of the Vitro distribution, + copy the file example.deploy.properties to a file named simply deploy.properties. This file sets several properties used in compilation and deployment.

@@ -636,8 +637,8 @@

V. Compile and deploy

- At the command line, from the top level of the Vitro distribution - directory, type: + At the command line, change to the webapp directory inside the Vitro distribution + directory. Then type:

                ant all

@@ -704,7 +705,7 @@

See Section X below, - for an example of overriding the VIVO context fragment. + for an example of overriding the Vitro context fragment.

VII. Start Tomcat

@@ -942,77 +943,23 @@

- Here is a simple test to see whether the ontology files were - loaded: + Step VII also shows that the Vitro self-tests ran successfully. + When Tomcat starts the Vitro webapp, it runs several tests. + If any of these tests produce warnings or error message, + you would see them instead of the Vitro home page. +

+

+ Among other things, the self-tests check

- Here is a test to see whether your system is configured to serve - linked data: + If you saw the Vitro home page in Step VII, you know that your installation passed all of these tests.

- -

- Finally, test the search index. -

- +

XIII. Review the Vitro Terms of Use

Vitro comes with a "Terms of Use" statement linked from the footer.