Generally every user centric application requires a Search capability. With Google easily leading the Search domain, user expectations are generally high when they come to a web-application and perform a search. If giving user's the Google experience is not possible, consider Apache's Solr which is a popular, open-source Java based search tool that runs Lucene under hood.
While Solr comes packaged with Jetty and has a basic tutorial, that provides pointers on its different features, setting up the tool to run within an existing Apache Tomcat instance can require a bit of effort as there are several files and folders and it is not immediately clear which files control the configuration of the tool. This post will document the various steps involved in setting up Solr to run with Apache Tomcat 7.0.28 on a Windows server.
Step 1 : Download a copy of Solr and unzip it to apache-solr-4.0.0.
Step 2: Create new directory which will be the home of Solr c:\solr_home and copy the following files and folders into it. ( You will find them within the unzipped apache-solr-4.0.0 folder).
bin
collection1
solr.xml
zoo.cfg
collection1 is an existing example which we will load up into our Tomcat.Within the directory collection1, you'll find two other folders conf & data. Just verify that these are present.
Now we'll connect Solr to Tomcat.
Step 3: Copy the apache-solr-4.0.0.war (which you will find in apache-solr-4.0.0\dist) into your Tomcat web-apps directory.
Step 4: Finally, the last step. Tell Solr where the existing search configuration files for collection1 reside.
To do this add the location of the Solr Home directory to your Tomcat JAVA_OPTS. I am setting this value in the setenv.bat file and the declaration looks like this :
set JAVA_OPTS=%JAVA_OPTS% -Dfile.encoding=UTF-8 -server -Xms1536m -Xmx1536m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:PermSize=256m -XX:MaxPermSize=256m -XX:+DisableExplicitGC -Dsolr.solr.home=C:/solr_home
Step 5: Start Tomcat and browse to your loaded Solr instance at http://localhost:8080/apache-solr-4.0.0/#/ You should see the Solr Admin screen as below :
To check if Solr has been configured and set up correctly, select collection1 in the left hand side bar and select the query option. Enter 'solr' in the textbox labelled 'q' as shown in the screenshot below.
On submitting the query, one result is returned by Solr. On clicking on the result link, the record is displayed as an XML.
In the next post, I'll document the steps of integrating Solr with an existing web-application which is running on the same Tomcat instance with a MySQL back-end.
Step 1 : Download a copy of Solr and unzip it to apache-solr-4.0.0.
Step 2: Create new directory which will be the home of Solr c:\solr_home and copy the following files and folders into it. ( You will find them within the unzipped apache-solr-4.0.0 folder).
bin
collection1
solr.xml
zoo.cfg
collection1 is an existing example which we will load up into our Tomcat.Within the directory collection1, you'll find two other folders conf & data. Just verify that these are present.
Now we'll connect Solr to Tomcat.
Step 3: Copy the apache-solr-4.0.0.war (which you will find in apache-solr-4.0.0\dist) into your Tomcat web-apps directory.
Step 4: Finally, the last step. Tell Solr where the existing search configuration files for collection1 reside.
To do this add the location of the Solr Home directory to your Tomcat JAVA_OPTS. I am setting this value in the setenv.bat file and the declaration looks like this :
set JAVA_OPTS=%JAVA_OPTS% -Dfile.encoding=UTF-8 -server -Xms1536m -Xmx1536m -XX:NewSize=256m -XX:MaxNewSize=256m -XX:PermSize=256m -XX:MaxPermSize=256m -XX:+DisableExplicitGC -Dsolr.solr.home=C:/solr_home
Step 5: Start Tomcat and browse to your loaded Solr instance at http://localhost:8080/apache-solr-4.0.0/#/ You should see the Solr Admin screen as below :
Solr Admin Console for Collection 1 |
Default Search Interface |
Search Result for 'Solr' |
In the next post, I'll document the steps of integrating Solr with an existing web-application which is running on the same Tomcat instance with a MySQL back-end.
No comments:
Post a Comment