You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by Apache Wiki <wi...@apache.org> on 2009/11/04 21:29:40 UTC

[Jackrabbit Wiki] Trivial Update of "JackrabbitOnTomcat6withJndiAndPostgresql" by tcleminson

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The "JackrabbitOnTomcat6withJndiAndPostgresql" page has been changed by tcleminson.
http://wiki.apache.org/jackrabbit/JackrabbitOnTomcat6withJndiAndPostgresql?action=diff&rev1=7&rev2=8

--------------------------------------------------

  
  Install the jackrabbit .war file.  If the system will be a dedicated jackrabbit server you can rename the jackrabbit-1.5.4.war file to ROOT.war and have it unpacked as ROOT.  This means you can access the jackrabbit instance as http://example.com:8080/ instead of http://example.com:8080/jackrabbit-1.5.4/.
  
- Create a '''${catalina.home}/common''' directory and copy ''jcr-1.0.jar'' to it.  Edit '''${catalina.home}/conf/catalina.properties''' and add ''${catalina.home/common,${catalina.home}/common/*.jar'' to the ''common.loader'' entry.  This allows us to add libraries to the server without mixing them with the standard tomcat libraries - something that's extremely helpful when things stop working and you aren't sure which library is the culprit!
+ Create a '''${catalina.home}/common''' directory and copy ''jcr-1.0.jar'' to it.  Edit '''${catalina.home}/conf/catalina.properties''' and add ''${catalina.home}/common,${catalina.home}/common/*.jar'' to the ''common.loader'' entry.  This allows us to add libraries to the server without mixing them with the standard tomcat libraries - something that's extremely helpful when things stop working and you aren't sure which library is the culprit!
  
  Finally, edit '''/etc/default/tomcat6''' to add ''-Djava.rmi.server.hostname=hostname'' to ''CATALINA_OPTS'', where you have changed 'hostname' to a public network interface.  If you don't do this the RMI library will probably pick something weird like 127.0.1.1 (NOT 127.0.0.1) and you'll spend hours knocking head-shaped holes in the wall.  You will need to use a public network interface to allow others to connect to the RMI server.