You can setup your own tomcat instance which would contain just configurations you need. You won't even have to recreate all the tomcat configuration and binaries, just the ones that were not defaults. So, if you lookup multiple tomcat configuration instance (google it), and then you'll have a set of directories. You'll need to have your own startup script that points to your configurations. You can use the current startup script as a model, then in your build procedures (I've done all this with a script) have this added to the system so you can preform restart. You'd have to have a couple of other environment variables set:
export CATALINA_BASE=/path/to/your/tomcat/instance/conf/files export CATALINA_HOME=/path/to/default/installation/bin/files export SOLR_HOME=/path/to/solr/dataNconf Good luck ________________________________________ From: Bernhard Reiter [ock...@raz.or.at] Sent: Thursday, November 04, 2010 5:49 PM To: solr-user@lucene.apache.org Subject: RE: Testing/packaging question Thanks for your instructions. Unfortunately, I need to do all that as part of my package's (python-solrpy) build procedure, so I can't change any global configuration, such as in the catalina subdirectories. I've already sensed that restarting tomcat is also just too system-invasive and would include changing its (system-wide) configuration. Are there any other ways to use solr for running the tests from http://pypi.python.org/packages/source/s/solrpy/solrpy-0.9.3.tar.gz without having to change any system configuration? Maybe via a user Tomcat instance such as provided by the tomcat6-user debian package? Thanks for your help! Bernhard Am Donnerstag, den 04.11.2010, 16:15 -0500 schrieb Turner, Robbin J: > You need to either add that to catalina.sh or create a setenv.sh in the > CATALINA_HOME/bin directory. Then you can restart tomcat. > > So, setenv.sh would contain the following: > > export JAVA_HOME="/path/to/jre" > export JAVA_OPTS="="$JAVA_OPTS -Dsolr.solr.home=/path/to/my/schema.xml" > > If you were setting the export in your own environment and then issuing the > restart, tomcat was not picking up your local environment because it's > running as root. You don't want to change root's environment. > > You could also, create a context.xml in you > CATALINA_HOME/conf/CATALINA/localhost. You should be able to find those > instruction on/through the Solr FAQ. > > Hope this helps. > ________________________________________ > From: Bernhard Reiter [ock...@raz.or.at] > Sent: Thursday, November 04, 2010 4:49 PM > To: solr-user@lucene.apache.org > Subject: Re: Testing/packaging question > > Hi, > > I'm now trying to > > export JAVA_OPTS="$JAVA_OPTS -Dsolr.solr.home=/path/to/my/schema.xml" > > and restarting tomcat (v6 package from ubuntu maverick) via > > sudo /etc/init.d/tomcat6 restart > > but solr still doesn't seem to find that schema.xml, as it complains > about unknown fields when running the tests that require that schema.xml > > Can someone please tell me what I'm doing wrong -- and what I should be > doing? > > TIA again, > Bernhard > > Am Montag, den 01.11.2010, 19:01 +0100 schrieb Bernhard Reiter: > > Hi, > > > > I'm pretty much of a Solr newbie currently packaging solrpy for Debian; > > see > > http://svn.debian.org/viewsvn/python-modules/packages/python-solrpy/trunk/ > > > > In order to run solrpy's supplied tests at build time, I'd need Solr to > > know about the schema.xml that comes with the tests. > > Can anyone tell me how do that properly? I'd basically need Solr to > > temporarily recognize that schema.xml without permanently installing it > > -- is there any way to do this, eg via environment variables? > > > > TIA > > Bernhard Reiter
