{"id":2463,"date":"2015-01-26T22:23:03","date_gmt":"2015-01-26T20:23:03","guid":{"rendered":"http:\/\/www.extradrm.com\/?p=2463"},"modified":"2015-03-13T09:18:57","modified_gmt":"2015-03-13T07:18:57","slug":"solr-4-jetty-9-and-search-api-on-ubuntu-2","status":"publish","type":"post","link":"https:\/\/www.extradrm.com\/?p=2463","title":{"rendered":"Solr 4, Jetty 9 Multicore Drupal Solr Search API on Ubuntu"},"content":{"rendered":"

First let me say I love the new UI for the Solr Admin pages (download at Apache Solr<\/a>).
\n\"Solr<\/a>
\nInstall Jetty 9<\/strong><\/p>\n

Jetty 9 requires JDK 7<\/strong>, so if you don\u2019t have it installed, install it first. In Ubuntu, it is very convenient to install openjdk using apt-get.<\/p>\n

apt-get install -y openjdk-7-jdk\r\nmkdir -p \/usr\/java\r\nln -s \/usr\/lib\/jvm\/java-7-openjdk-amd64 \/usr\/java\/default<\/pre>\n
Extract the tarball of Jetty 9 to a preferred directory, e.g. \/opt. Then set $JETTY_HOME, create a new user called \u201cjetty\u201d and make it the owner of $JETTY_HOME.<\/p>\n
tar zxvf jetty-distribution-9.0.3.v20130506.tar.gz -C \/opt\r\nmv \/opt\/jetty-distribution-9.0.3.v20130506\/ \/opt\/jetty\/\r\nuseradd jetty -U -s \/bin\/false\r\nchown -R jetty:jetty \/opt\/jetty<\/pre>\n
Installing Solr Manually<\/h2>\n
Lets put all this in \/opt<\/strong><\/p>\n
# cd \/opt<\/pre>\n
Let’s make a Solr user<\/strong><\/p>\n
# adduser solr<\/pre>\n
We can now start the real installation of Solr. First, download all files and uncompress them:<\/strong><\/p>\n
cd \/opt\r\nwget http:\/\/archive.apache.org\/dist\/lucene\/solr\/4.9.1\/solr-4.9.1.tgz\r\ntar -xzvf solr-4.9.1.tgz\r\ncp -R solr-4.9.1\/example \/opt\/solr\r\ncd \/opt\/solr\r\njava -jar start.jar<\/pre>\n
Check if it works by visiting http:\/\/YOUR_IP:8983\/solr<\/code>. When it works, go back into your SSH session and close the window with Ctrl+C.<\/em>
\n<\/strong><\/p>\n
Make a place for Solr<\/strong><\/p>\n
# mkdir \/opt\/solr<\/pre>\n
Lets put all this in \/opt
\n<\/strong># cd \/opt
\nGet some files<\/strong><\/p>\n
# wget http:\/\/apache.mirror.serversaustralia.com.au\/lucene\/solr\/4.9.1\/solr-4.9.1.tgz\r\n# wget http:\/\/ftp.drupal.org\/files\/projects\/search_api_solr-7.x-1.6.tar.gz<\/pre>\n
After that, download the start file and set it to automatically start up if it hasn’t been done already:<\/strong><\/p>\n
sudo wget -O \/etc\/init.d\/jetty http:\/\/dev.eclipse.org\/svnroot\/rt\/org.eclipse.jetty\/jetty\/trunk\/jetty-distribution\/src\/main\/resources\/bin\/jetty.sh\r\nsudo chmod a+x \/etc\/init.d\/jetty\r\nsudo update-rc.d jetty defaults<\/pre>\n
Finally start Jetty\/Solr:<\/p>\n
sudo \/etc\/init.d\/jetty start<\/pre>\n
service jetty start<\/pre>\n
You can now access your installation just as before at http:\/\/YOUR_IP:8983\/solr.<\/p>\n
Copy the Solr application into Jetty (this is how we do it in Jetty 9)<\/strong><\/p>\n
# cp -a solr-4.9.1\/dist\/solr-4.9.1.war \/opt\/jetty\/webapps\/solr.war\r\n# cp -a solr-4.9.1\/example\/contexts\/solr-jetty-context.xml \/opt\/jetty\/\r\n# cp -a solr-4.9.1\/example\/lib\/ext\/* \/opt\/jetty\/lib\/ext\/<\/pre>\n
Also, you will need the context and some modules to have Solr run properly on Jetty.<\/p>\n
# cp -a solr-4.9.1\/example\/contexts\/solr-jetty-context.xml \/opt\/jetty\/webapps\/solr.xml\r\n# cp -a solr-4.9.1\/example\/lib\/ext\/* \/opt\/jetty\/lib\/ext\/<\/pre>\n
Copy the Solr config into place<\/p>\n
# cp -a solr-4.9.1\/example\/solr \/opt\/solr\r\n# cp -a solr-4.9.1\/dist\/ \/opt\/solr\r\n# cp -a solr-4.9.1\/contrib\/ \/opt\/solr<\/pre>\n
Make a place for logs<\/strong><\/p>\n
# mkdir \/opt\/solr\/logs<\/pre>\n
Everything is owned by Solr<\/strong><\/p>\n
# chown -R solr:solr \/opt\/solr\/logs<\/pre>\n
Open the \/etc\/default\/jetty file (nano \/etc\/default\/jetty) and paste this into it<\/strong>
\n# sudo nano \/etc\/default\/jetty<\/p>\n
NO_START=0 # Start on boot\r\nJAVA_OPTIONS=\"-Dsolr.solr.home=\/opt\/solr\/solr $JAVA_OPTIONS\"\r\nJAVA_HOME=\/usr\/java\/default\r\nJETTY_HOME=\/opt\/solr\r\nJETTY_USER=solr\r\nJETTY_LOGS=\/opt\/solr\/logs<\/pre>\n
Open the file \/opt\/solr\/etc\/jetty-logging.xml (nano \/opt\/solr\/etc\/jetty-logging.xml) and paste this into it:<\/strong><\/p>\n
<?xml version=\"1.0\"?>\r\n  <!DOCTYPE Configure PUBLIC \"-\/\/Mort Bay Consulting\/\/DTD Configure\/\/EN\" \"http:\/\/jetty.mortbay.org\/configure.dtd\">\r\n  <!-- =============================================================== -->\r\n  <!-- Configure stderr and stdout to a Jetty rollover log file -->\r\n  <!-- this configuration file should be used in combination with -->\r\n  <!-- other configuration files.  e.g. -->\r\n  <!--    java -jar start.jar etc\/jetty-logging.xml etc\/jetty.xml -->\r\n  <!-- =============================================================== -->\r\n  <Configure id=\"Server\" class=\"org.mortbay.jetty.Server\">\r\n\r\n      <New id=\"ServerLog\" class=\"java.io.PrintStream\">\r\n        <Arg>\r\n          <New class=\"org.mortbay.util.RolloverFileOutputStream\">\r\n            <Arg><SystemProperty name=\"jetty.logs\" default=\".\"\/>\/yyyy_mm_dd.stderrout.log<\/Arg>\r\n            <Arg type=\"boolean\">false<\/Arg>\r\n            <Arg type=\"int\">90<\/Arg>\r\n            <Arg><Call class=\"java.util.TimeZone\" name=\"getTimeZone\"><Arg>GMT<\/Arg><\/Call><\/Arg>\r\n            <Get id=\"ServerLogName\" name=\"datedFilename\"\/>\r\n          <\/New>\r\n        <\/Arg>\r\n      <\/New>\r\n\r\n      <Call class=\"org.mortbay.log.Log\" name=\"info\"><Arg>Redirecting stderr\/stdout to <Ref id=\"ServerLogName\"\/><\/Arg><\/Call>\r\n      <Call class=\"java.lang.System\" name=\"setErr\"><Arg><Ref id=\"ServerLog\"\/><\/Arg><\/Call>\r\n      <Call class=\"java.lang.System\" name=\"setOut\"><Arg><Ref id=\"ServerLog\"\/><\/Arg><\/Call><\/Configure><\/pre>\n
Then, create the Solr user and grant it permissions:<\/p>\n
sudo useradd -d \/opt\/solr -s \/sbin\/false solr\r\nsudo chown solr:solr -R \/opt\/solr<\/pre>\n
Solr is now one directory closer to Jetty than the default configuration shipped with Solr<\/em><\/p>\n
# sudo nano solr\/solr\/collection1\/conf\/solrconfig.xml
\n<!– modify the path as following as we are a directory closer now –>
\n…
\n<lib dir=”..\/..\/contrib\/extraction\/lib” regex=”.*\\.jar” \/>
\n<lib dir=”..\/..\/dist\/” regex=”solr-cell-\\d.*\\.jar” \/><\/p>\n
<lib dir=”..\/..\/contrib\/clustering\/lib\/” regex=”.*\\.jar” \/>
\n<lib dir=”..\/..\/dist\/” regex=”solr-clustering-\\d.*\\.jar” \/><\/p>\n
<lib dir=”..\/..\/contrib\/langid\/lib\/” regex=”.*\\.jar” \/>
\n<lib dir=”..\/..\/dist\/” regex=”solr-langid-\\d.*\\.jar” \/><\/p>\n
<lib dir=”..\/..\/contrib\/velocity\/lib” regex=”.*\\.jar” \/>
\n<lib dir=”..\/..\/dist\/” regex=”solr-velocity-\\d.*\\.jar” \/>
\n…<\/p>\n
<!– <lib dir=”\/non\/existent\/dir\/yields\/warning” \/> –>
\nStart Solr<\/strong><\/p>\n
# service solr start<\/pre>\n
View the Solr admin interface\u00a0 (try also port 8080 jetty)
\n<\/strong><\/p>\n
http:\/\/solr.example.com:8983\/solr\/\r\n\r\n==============================================<\/pre>\n
Add a core for a Drupal Search API project in a multicore solr server<\/strong><\/h2>\n
# mkdir -p \/opt\/solr\/solr\/[corename]\/data<\/pre>\n
Copy the search_api_solr config into place<\/p>\n
# cp -a \/opt\/search_api_solr\/solr-conf\/4.x\/ \/opt\/solr\/solr\/[corename]\r\n# chown -R solr:solr \/opt\/solr\/solr\/[corename]<\/pre>\n
Visit the Solr admin page<\/p>\n
http:\/\/solr.example.com:8983\/solr\/#\/~cores\/[corename]<\/pre>\n
If corename = drupal so to connect on a remote Solr server (not locahost), you must remove # in the url solr admin :<\/p>\n
\"connect_solr_remote\"<\/a><\/p>\n
The same thing happens with swagger.io to check an API the adding character # in url\/rest\/#<\/strong> is important to redirect you to the swagger folder API !!!<\/p>\n
NOTA : <\/strong>Be aware of removing the symbol # in solr server url when using calls via SolrPhpClient library which causes annoying json validate errors around line 206 in Service.php file.<\/em><\/p>\n

\n$LWS = new Apache_Solr_Service( ‘localhost’, ‘8983’, ‘solr\/collection1’ );
\nWithout any # in solr\/collection1<\/p>\n
<\/em>Same thing for multicore :<\/strong>
\n<\/em><\/span>$<\/em>LWS <\/em><\/em>= new Apache_Solr_Service( ‘localhost’, ‘8983’, ‘solr\/~cores\/core2\/’ )<\/em>
\n<\/em>and not<\/strong>
\n<\/em><\/span>$<\/em>LWS <\/em><\/em>= new Apache_Solr_Service( ‘localhost’, ‘8983’, ‘solr\/#\/~cores\/core2\/’ );<\/em>
\n<\/em><\/span><\/p>\n

\n<\/strong>Configuring a schema.xml for Solr<\/h2>\n
Add your database fields to index :<\/p>\n
<field name=”typeressource” type=”string” indexed=”true” stored=”true” \/>
\n<field name=”titre” type=”text_general” indexed=”true” stored=”true” multiValued=”true”\/><\/p>\n
 <\/p>\n
Phrase Query<\/strong><\/h2>\n
A phrase query matches multiple terms (words) in sequence.<\/p>\n
text:”yonik seeley”<\/strong><\/p>\n
This query will match text containing Yonik Seeley but will not match Yonik C Seeley or Seeley Yonik.<\/p>\n
Internally, a phrase query is created when the fieldType produces multiple terms for the given value. For the example above, the fieldType splits on whitespace<\/strong> and lowercases the result<\/strong>, and we get two terms\u2026 [yonik, seeley].
\nIf our fieldType had been string<\/strong>, a single term of yonik seeley would have been produced<\/span> since string fields do not change values in any way.<\/p>\n
Add a core into a multicore solr server environnement
\n<\/strong><\/h2>\n
1- First, Stop tomcat or jetty service before everything :<\/p>\n
sudo service jetty stop<\/pre>\n
2- Copy \/ rename the \/opt\/solr-distribution\/example\/collection1 to an understandable name like stores <\/strong>for example. ..\u00a0 In that case, you can execute the following command :<\/p>\n
* NotaBena :\u00a0 if you installed it using apt-get, this can be skipped by going to cd \/usr\/share\/solr …
\n* NotaBene : the collection1 core conf is more complete than the multicore (core0\/core1 samples) so try to get collection1\/conf files by copy .. in this example I suppose that I have collection1 saved from mono instance basic install …<\/p>\n
cd \/opt\/solr\/solr\r\ncp -R collection1 stores or mv collection1 stores\r\ncd stores<\/pre>\n
3- Also, if you installed Solr manually, open the file core.properties<\/strong> :<\/p>\n
sudo nano core.properties<\/pre>\n
and change the core name inside to the same name above (stores<\/strong>)<\/p>\n
4- Then, remove the data directory and change the schema.xml :
\nNota bene : with this method you can delete a whole index solr instead using curl and delete Rest calls …<\/p>\n
rm -R data\r\nnano conf\/schema.xml<\/pre>\n
5- Paste your own schema.xml in here and think to correct directories if needed according to your installation (example drupal solr search) see above what to modify in solrconfig.xml.\u00a0 There is a very advanced schema.xml in the Solr Repository for monocore collection1. You can probably find a lot more of them on the internet …<\/p>\n
7- Do not forget to make solr owner of the new core :<\/p>\n
sudo chown -R solr:solr \/opt\/solr\/solr\/stores<\/pre>\n
8- Add the new core in\u00a0 solr.xml on \/opt\/solr\/solr: (remember this solr.xml is a copy of the multicore file in examples)<\/p>\n
<cores adminPath=”\/admin\/cores” host=”${host:}” hostPort=”${jetty.port:8983}” hostContext=”${hostContext:solr}”>
\n<core name=”core0″ instanceDir=”core0″ \/>
\n<core name=”core1″ instanceDir=”core1″ \/>
\n<core name=”stores” instanceDir=”stores” \/><\/strong>
\n<shardHandlerFactory name=”shardHandlerFactory”>
\n<str name=”urlScheme”>${urlScheme:}<\/str>
\n<\/shardHandlerFactory>
\n<\/cores><\/p>\n
9- Start Jetty :<\/p>\n
sudo \/etc\/init.d\/jetty start<\/pre>\n
When you now visit your Solr instance, you should see the Dashboard with the collection somewhere under cores. think to check logs if there are any errors …<\/p>\n
JETTY PORTS and as service at boot<\/h3>\n
If you want Jetty to start when boot up, execute following code<\/p>\n
update-rc.d jetty defaults<\/pre>\n
If you want to change the port Jetty runs on, edit start.ini in $JETTY_HOME and change jetty.port<\/p>\n
sudo nano \/opt\/jetty\/start.ini<\/pre>\n
…<\/p>\n
#=============
\n# HTTP Connector
\n#———————–
\njetty.port=9090<\/strong>
\nhttp.timeout=30000
\netc\/jetty-http.xml<\/p>\n
…<\/p>\n
>>> Multicore Install<\/strong> : Read this link<\/a><\/p>\n
 <\/p>\n","protected":false},"excerpt":{"rendered":"
First let me say I love the new UI for the Solr Admin pages (download at Apache Solr). Install Jetty 9 Jetty 9 requires JDK 7, so if you don\u2019t have it installed, install...<\/p>\n","protected":false},"author":1,"featured_media":2847,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[320,139,2],"tags":[],"youtube_video":null,"_links":{"self":[{"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/posts\/2463"}],"collection":[{"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2463"}],"version-history":[{"count":0,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/posts\/2463\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/media\/2847"}],"wp:attachment":[{"href":"https:\/\/www.extradrm.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2463"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2463"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2463"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}