From: Pallant, J. <pa...@fa...> - 2012-02-16 19:41:19
|
I thought I would share the final pieced of my Ubuntu Server Setup eXist set up on Linux Ubuntu Server 64 bit server – This is Virtual Machine setup – which I only had shell interface. eXist version – exist-setup-1.4.1-rev15155.jar 1 Confirm correct version of java Ø java –version java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode) 2 If you don’t have the correct version – install via command Ø apt-get install sun-java6-bin sun-java6-jre 3 Install exist Ø java -jar eXist-[version]-build-XXXX.jar –no-gui –p pathname 4 Setup wrapper > I used the help of eXist forum page – Installing eXist-db 1.4.0 on Linux<http://exist.2174344.n4.nabble.com/Installing-eXist-db-1-4-0-on-Linux-td2183146.html> as a guide, but the main problem was that the wrapper needed an executable that the linux system could use. I tried connecting it to the 32 bit version – see help at - http://estest.ucdavis.edu/trac/wiki/Help/ExistBoot. This recommends in installing installing ia32-libs first. Others recommended connecting the wrapper to the correct 64bit version. It turns out it does not ship with the 1.4.x version of eXist, but does with the 1.5x versions. You can just copy the wrapper-linux-x86-64 to the $EXIST_HOME/tools/wrapper/bin directory and link it to the wrapper file. See forum at http://exist.2174344.n4.nabble.com/wrapper-problem-td3049203.html. 5 Change Configuration Files Ø Change webapp/WEB-INF/controller-config.xml to allow .xq queries – add xq| to the following pattern in the file. <forward pattern=".*\.(xql|xqy|xquery)$" servlet="XQueryServlet"/> Ø Give the java VM engine and database cache A LOT more dedicated memory. I was told that for JVM up to 4GB can be a decent amount. I upped mine to 1GB. The default in this version is 128kb. See eXist-Tuning document.<http://exist.sourceforge.net/tuning.html> o In the $EXIST_HOME/tools/wrapper/conf/wrapper.conf – change the wrapper.java.maxmemory=128 to the amount you have allocated. o Change the database cache size. This is the cacheSize in the <db-connection> section of the $EXIST_HOME/conf.xml file. It was noted that should be about 1Ž2 the size of the memory allocated to JVM. 6 Other thoughts Ø Make sure the owner of the wrapper has permissions to the write to the /tmp directory. Ø Make sure your entire machine has enough memory (more than 1gb) Ø Take advantage of the database status link found on the “home page” of your exist setup on the lower left. Or http://yourserver:8080/exist/cocoon/status. This can provide you with good statistics of usages – “enough memory, database space etc..). NOTE: if you go to the pulldown for buffers it will show your cache and collection usage. Ø The eXist forum is extremely place to search and receive help --------------------------------------------------------- Julie Pallant Web and Systems Administrator Harvard Forest Harvard University 324 N. Main Street Petersham, MA 01366 978-756-6142 On 2/11/12 5:58 PM, "Dannes Wessels" <di...@ex...<mailto:di...@ex...>> wrote: On 10 feb. 2012, at 22:25, "Pallant, Julie" <pa...@fa...<mailto:pa...@fa...>> wrote: it crashes with following error in ssh screen: bin/startup.sh: line 62: 6322 Killed "${JAVA_HOME}"/bin/java ${JAVA_OPTIONS} ${OPTIONS} ${DEBUG_OPTS} -jar "$EXIST_HOME/start.jar" jetty ${JAVA_OPTS[@]} I don't think exist crashes, but something else is happening. Any other leads would be helpful. Hate to run both a linux and windows server just for eXist. Well that will be not necessary, existdb runs perfectly well on Linux . Maybe you had 2 instances running? Please check webapps/WEB-INF/logs/exist.log for details, but I expect that the console showed some more errors? Cheers Dannes Ps. Please could you check the java version? java --version echo $JAVA_HOME Did you install the JDK? E |