Apache Solr<\/code> to Jetty<\/code> or Apache Tomcat especially when know that SolR has choosen Jetty as a Servlet container. Probably this choice is because it is \"light\" and can be easily embedded on the Solr distribution... so you can immediately have a running Solr server without requiring any other Servlet container (such as Tomcat, etc.). In terms of performance, not sure there will be such a big difference. Probably this depends on your own setup, for example in \"development\" I use Jetty, in production I use Tomcat, since I already am using it for other applications... In other hand, you can stop jetty service without affecting other web application. In case of stopping of Tomcat service all web applications on server are affected .... So for this tutorial we will use Jetty which need
\n<\/code><\/p>\n\n- Ensure Java version 1.7 or higher is present on the machine (java -version on cmd screen). If not, download it from http:\/\/www.java.com\/<\/a> (Java 7 is also known as 1.7<\/strong>).<\/li>\n
- Download latest Solr<\/a> (here Solr 4.9.1.zip) and unpack it somewhere.<\/li>\n
- Create a directory where your Solr configuration and Jetty will live (e.g. C:\\Solr<\/strong>, which we will refer to as <_SOLRDIR_><\/strong>).<\/li>\n
- If you don\u2019t have Solr configuration defined yet, you can just copy Solr\u2019s own example\\solr<\/strong> directory to\u00a0<_SOLRDIR_><\/strong>, such that\u00a0solr.xml<\/strong> is just inside\u00a0<_SOLRDIR_><\/strong> directory.
\n![\"WindowsSolrJetty\"](\"http:\/\/www.extradrm.com\/wp-content\/uploads\/2015\/01\/WindowsSolrJetty.jpg\")
<\/a><\/li>\n- Under the\u00a0<_SOLRDIR_><\/strong>, create subdirectory called jetty.<\/strong><\/li>\n
- Copy the following directories and the files into the\u00a0jetty<\/strong> subdirectory from the Solr\u2019s example<\/strong> directory:\n
\n- contexts<\/li>\n
- etc<\/li>\n
- lib<\/li>\n
- logs<\/li>\n
- resources (Solr 4.9+)<\/li>\n
- webapps<\/li>\n
- solr-webapp<\/li>\n
- start.jar<\/li>\n<\/ul>\n<\/li>\n
- From the command line in the\u00a0jetty<\/strong> directory, run the Solr server to make sure it works:\n
\n- java -Dsolr.solr.home=.. -jar start.jar<\/li>\n
- Ensure that Solr is accessible at: http:\/\/localhost:8983\/solr\/<\/a><\/li>\n
- Stop the server (Ctrl-C)<\/li>\n<\/ol>\n
<\/li>\n
- In case of multicore configuration, copy multicore folder to c:\\solr (if you want to add cores see end of this topic):\n
\n- java -Dsolr.solr.home=..\/multicore -jar start.jar<\/li>\n
- Ensure that Solr is accessible at: http:\/\/localhost:8983\/solr\/<\/a><\/li>\n
- Stop the server (Ctrl-C)<\/li>\n
- Here is what you see when adding a core2 to SolR
![\"Solr](\"http:\/\/www.extradrm.com\/wp-content\/uploads\/2015\/01\/Solr-Multicore-1024x433.jpg\")
<\/a><\/li>\n<\/ol>\n <\/li>\n<\/ol>\n
Jetty Service setup as a service Daemon for Windows<\/h2>\n\n- Download Apache Commons\u2019 Daemon package for Windows<\/a>\u00a0(make sure to get the Windows package that includes .exe files).<\/li>\n
- Copy platform-appropriate prunsrv.exe<\/strong> into the jetty<\/strong>\u00a0directory and rename it to SolrService.exe<\/strong> \u2013 this is the actual Windows service executable.<\/li>\n
- Copy prunmgr.exe<\/strong> into a new subdirectory jetty\/serviceui<\/strong> and rename it also\u00a0to\u00a0SolrService.exe<\/strong> (to provide default service name) \u2013 this is the UI that allows to correct some of the parameters of the service after it had been setup via the command line.<\/li>\n
- Make sure that computer\u2019s environmental variables have\u00a0JAVA_HOME<\/strong> defined for system variables, not just for user\u2019s (run sysdm.cpl <\/strong>as Administrator). The variable value should look something like C:\\Progra~1\\Java\\jre7\u00a0<\/em><\/strong>. Otherwise, attempting to start the service will produce the following message in the daemon\/service logs:\u00a0Unable to find Java Runtime Environment<\/em>.<\/li>\n
- Run the service registration (with renamed prunsrv<\/a>) as the Administrator on the command prompt after replacing <_SOLRDIR_><\/strong> with the\u00a0actual path to the Solr installation as setup above.\u00a0\u00a0The command below should be all on a single line (with spaces instead of line breaks):\n
SolrService.exe \/\/IS\/\/SolrService\r\n--DisplayName=\"Solr Service\"\r\n--Install=<_SOLRDIR_><\/strong>\\jetty\\SolrService.exe\r\n--LogPath=<_SOLRDIR_><\/strong>\\jetty\\logs\r\n--LogLevel=Debug\r\n--StdOutput=auto\r\n--StdError=auto\r\n--StartMode=java\r\n--StopMode=java\r\n--Jvm=auto\r\n++JvmOptions=-Djetty.home=<_SOLRDIR_><\/strong>\\jetty\r\n++JvmOptions=-DSTOP.PORT=8087\r\n++JvmOptions=-DSTOP.KEY=stopsolr\r\n++JvmOptions=-Djetty.logs=<_SOLRDIR_><\/strong>\\jetty\\logs\r\n++JvmOptions=-Dorg.eclipse.jetty.util.log.SOURCE=true\r\n++JvmOptions=-XX:MaxPermSize=128M\r\n--Classpath=<_SOLRDIR_><\/strong>\\jetty\\start.jar\r\n--StartClass=org.eclipse.jetty.start.Main\r\n++StartParams=OPTION=ALL\r\n++StartParams=<_SOLRDIR_><\/strong>\\jetty\\etc\\jetty.xml\r\n--StopClass=org.eclipse.jetty.start.Main\r\n++StopParams=--stop\r\n++JvmOptions=-Dsolr.solr.home=<_SOLRDIR_><\/strong>\r\n--StartPath=<_SOLRDIR_><\/strong>\\jetty<\/pre>\n<\/li>\n- Run the service:\n
\n- SolrService.exe start<\/strong><\/li>\n
- Check the log files in the log subdirectory (usually\u00a0commons-daemon.<date>.log<\/strong>) for messages.<\/li>\n
- If there is an error message, run\u00a0serviceui\\SolrService.exe<\/strong> and try to correct possible problems. An account that runs the service may need to switch to one with full access to the directories (e.g. Administrator).<\/li>\n
- Run\u00a0SolrService.exe stop<\/strong> to stop the service and try starting again. If error log shows problems with stopping and the Services control panel shows the service as \u2018starting\u2019, see the troubleshooting section below on how to kill a run-away service.<\/li>\n
- The success criteria here is being able to access Solr\u2019 Web Admin UI from http:\/\/localhost:8983\/solr<\/a> (again).<\/li>\n<\/ol>\n<\/li>\n
- In the Services control panel, change status of the service\u00a0Solr Service<\/strong>\u00a0from manual to automatic to ensure it survives restart. Try stopping and starting the service from the Services control panel to test that\u00a0it works. Use Solr\u2019 Web Admin UI to verify that\u00a0it has stopped\/started correctly.<\/li>\n<\/ol>\n
Updating Solr configuration<\/h2>\n\n- Update would usually involve changes to schema.xml<\/strong>\u00a0and \u2013 much more rarely \u2013 to solrconfig.xml\u00a0<\/strong>.<\/li>\n
- For example in this tutorial we must give the windows path to avoid warning messages<\/li>\n
![\"Solrconf\"](\"http:\/\/www.extradrm.com\/wp-content\/uploads\/2015\/01\/Solrconf.jpg\")
<\/a>Most of the time, the core can be reloaded from the Solr\u2019s Web Admin UI to account for the new configuration : we should need to comment the 2 lines <lib dir=$…<\/li>\n![\"Solrconf1\"](\"http:\/\/www.extradrm.com\/wp-content\/uploads\/2015\/01\/Solrconf1.jpg\")
<\/a>If the changes are significant (e.g. new collection or some deep server settings), the service itself may need\u00a0to be restarted.<\/li>\n<\/ol>\nUpgrading Solr<\/h2>\n\n- Download and unpack the latest 4.x version of Solr.<\/li>\n
- Stop Solr service.<\/li>\n
- Delete and re-copy\u00a0the directories into\u00a0jetty<\/strong> subdirectory as per the initial-installation instructions above, with two exceptions:\n
\n- Keep\u00a0logs<\/strong> directory, which contains production logs.<\/li>\n
- Delete\u00a0solr-webapp<\/strong> directory, which is an expanded version of \u2013 now obsolete \u2013\u00a0webapps\/solr.war<\/strong>. If this is not done, you will get version mismatch between old and new content. The\u00a0solr-webapp<\/strong> directory will be regenerated on the next Jetty restart.<\/li>\n<\/ol>\n<\/li>\n
- If you need to update schema or config, do it now while the service is down.<\/li>\n
- Restart the service.<\/li>\n
- If you are running some persistent client, you may need to restart that as well.<\/li>\n
- Test from Web Admin UI interface that the service is running.<\/li>\n<\/ol>\n
\u00a0Troubleshooting service setup<\/h2>\n
If a service is misconfigured, Java runtime not found or something else goes wrong, you may get a run-away service that refuses to start and stop properly from the control panel. In which case, you may need to use command line tools (possibly as Administrator) to find and kill the stuck service:<\/p>\n
\n- sc queryex<\/li>\n
- taskkill \/PID <PID><\/strong> \/F<\/li>\n<\/ol>\n
In here,\u00a0<PID><\/strong> is the process ID for the solr service that is stuck.<\/p>\nCreating a core in a SolR mulicore instance under Jetty<\/h2>\n
Using Multiple SolrCores
\nIt is possible to segment Solr into multiple cores, each with its own configuration and indices. Cores may be dedicated to a single application or to very different ones, but all are administered through a common administration interface. You can create new Solr cores on the fly, shutdown cores, even replace one running core with another, all without ever stopping or restarting your servlet container.
\nSolr cores are configured by placing a file named solr.xml<\/strong> in your solr.home directory. A typical solr.xml looks like this:<\/p>\n<solr persistent=”false”>
\n<cores adminPath=”\/admin\/cores” host=”${host:}” hostPort=”${jetty.port:}”>
\n<core name=”core0″ instanceDir=”core0″ \/>
\n<core name=”core1″ instanceDir=”core1″ \/>
\n<\/cores>
\n<\/solr>
\nThis sets up two Solr cores, named “core0” and “core1”, and names the directories (relative to the Solr installation path) which will store the configuration and data sub-directories. So you can add core2 by creating a folder core2 and copy the folder data and conf of core0<\/p>\n
So the File solr.xml under multicore becomes with one more core (core2) :<\/p>\n
![\"solr-multicore1\"](\"http:\/\/www.extradrm.com\/wp-content\/uploads\/2015\/01\/solr-multicore1.jpg\")
<\/a>
\n![\"Solrxml\"](\"http:\/\/www.extradrm.com\/wp-content\/uploads\/2015\/01\/Solrxml.jpg\")
<\/a><\/p>\n
\n","protected":false},"excerpt":{"rendered":"Initial setup We to deploy Apache Solr to Jetty or Apache Tomcat especially when know that SolR has choosen Jetty as a Servlet container. Probably this choice is because it is “light” and can...<\/p>\n","protected":false},"author":1,"featured_media":2847,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[320,2],"tags":[322,323],"youtube_video":null,"_links":{"self":[{"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/posts\/2324"}],"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=2324"}],"version-history":[{"count":0,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=\/wp\/v2\/posts\/2324\/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=2324"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2324"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.extradrm.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2324"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}