cd /usr/share/tomcat/webapps
ln -s Mir-install-dir Mir
+7. Modify your tomcat startup script and add an LD_LIBRARY_PATH variable
+that points to the WEB-INF/lib directory of your Mir install dir. (called
+"Mir"). Add something like the following at the top of tomcat.sh (tomcat.sh
+is found in the "bin/" dir. under $TOMCAT_HOME):
+ LD_LIBRARY_PATH=/path/to/Mir-install-dir/WEB-INF/lib
-7. create a new database
+An alternaive way to avoid this is to copy any dynamic library files
+ending with ".so" in WEB-INF/lib to your jre/jdk lib directory (where the
+other ".so" files live). Or, you can skip the whole thing and live without
+"native" acceleration for image manipulation
+
+
+8. create a new database
the database name should be the same as in config.properties
as user postgres:
createdb dbname
-8. create base table
+9. create base table
psql -Upostgres dbname < dbscripts/create_pg.sql
- cat dbscript/help*.sql | psql -Upostgres dbname
- cat dbscript/populate*.sql | psql -Upostgres dbname
+ cat dbscripts/help*.sql | psql -Upostgres dbname
+ cat dbscripts/populate*.sql | psql -Upostgres dbname
-9. Add the dupe prevention trigger to the database:
+10. Add the dupe prevention trigger to the database:
cd dbscripts/dupetrigger
There, read INSTALL and follow the instructions.
-10. Set permissions
+11. Set permissions
We provide a script that sets all files' and direcories' permissions to
a quite reasonable state.
./perms.sh
-11. restart tomcat
+12. restart tomcat
-12. configure mod_jk
+13. configure mod_jk
insert the following patch into /etc/apache/httpd.conf. Edit the directories
to suit your needs.
system for file ownership/permissions problems.
-13. Add a password to your PostgreSQL user and link it to Mir (optional)
+14. Add a password to your PostgreSQL user and link it to Mir (optional)
Add a hard to guess password to the PostgreSQL user database: