Differences between revisions 1 and 2
Revision 1 as of 2007-07-05 10:14:47
Size: 26
Editor: 213
Comment: Initial page
Revision 2 as of 2007-07-05 10:26:32
Size: 1569
Editor: 213
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Describe SolrJBoss here. == Solr with JBoss ==
 * Solr runs fine with [http://www.jboss.org/ JBoss], see the instructions in the generic [wiki:SolrInstall Solr installation] page
 * The latest version of JBoss is recommended

=== Optional Configuration ===
==== URI Charset Config ====
If you are going to '''query''' Solr using international characters (>127) using HTTP-GET, you must configure JBoss to conform to the URI standard by accepting percent-encoded UTF-8.

Edit JBoss's "server/default/deploy/jbossweb-tomcat55.sar/server.xml" and add the following attribute to the correct Connector element: URIEncoding="UTF-8".
{{{
<Server ...>
 <Service ...>
   <Connector ... URIEncoding="UTF-8"/>
     ...
   </Connector>
 </Service>
</Server>
}}}

This is only an issue when sending non-ascii characters in a query request... no configuration is needed for Solr/Tomcat to return non-ascii chars in a response, or accept non-ascii chars in an HTTP-POST body.

=== Configuring Solr Home ===
You can configure the Solr home directory globally via "-Dsolr.solr.home" in the file "bin/run.bat". But that is often not desired because you potentially want more than one Solr installation deployed.

==== Solr Home via web.xml ====
You can configure the Solr home directory to use per webapp in the "web.xml" file. Add following snippet to the web.xml:
{{{
  <env-entry>
    <env-entry-name>solr/home</env-entry-name>
    <env-entry-value>C:\Projects\solr-trunk\example\solr</env-entry-value>
    <env-entry-type>java.lang.String</env-entry-type>
  </env-entry>
}}}

Solr with JBoss

  • Solr runs fine with [http://www.jboss.org/ JBoss], see the instructions in the generic [wiki:SolrInstall Solr installation] page

  • The latest version of JBoss is recommended

Optional Configuration

URI Charset Config

If you are going to query Solr using international characters (>127) using HTTP-GET, you must configure JBoss to conform to the URI standard by accepting percent-encoded UTF-8.

Edit JBoss's "server/default/deploy/jbossweb-tomcat55.sar/server.xml" and add the following attribute to the correct Connector element: URIEncoding="UTF-8".

<Server ...>
 <Service ...>
   <Connector ... URIEncoding="UTF-8"/>
     ...
   </Connector>
 </Service>
</Server>

This is only an issue when sending non-ascii characters in a query request... no configuration is needed for Solr/Tomcat to return non-ascii chars in a response, or accept non-ascii chars in an HTTP-POST body.

Configuring Solr Home

You can configure the Solr home directory globally via "-Dsolr.solr.home" in the file "bin/run.bat". But that is often not desired because you potentially want more than one Solr installation deployed.

Solr Home via web.xml

You can configure the Solr home directory to use per webapp in the "web.xml" file. Add following snippet to the web.xml:

  <env-entry>
    <env-entry-name>solr/home</env-entry-name>
    <env-entry-value>C:\Projects\solr-trunk\example\solr</env-entry-value>
    <env-entry-type>java.lang.String</env-entry-type>
  </env-entry>

SolrJBoss (last edited 2013-01-06 15:52:56 by UweSchindler)