Thanks Karl. In my case, I have to deploy Solr on Windows, AIX, and Linux (all server edition). We are a WebSphere shop, moving away from it means I have to deal with politics and culture.
For Windows, I cannot use NSSM so I have to figure a solution managing Solr (at least start-up and shutdown). If anyone has experience in this area (now that Solr is not in a WAS profile managed by Windows services) and can share your experience, please do. Thanks. Steve On Thu, Apr 16, 2015 at 3:49 PM, Karl Kildén <karl.kil...@gmail.com> wrote: > I asked a very similar question recently. You should switch to using the > package as is and forget that it contains a .war. The war is now an > internal component. Also switch to the new script for startup etc. > > I have seen several disappointed users that disagree with this decision but > I assume the project now has more freedom in the future and also more > alignment and focus on one experience. > > I did my own thing with NSSM because we use windows and I am satisfied. > > On 16 April 2015 at 21:36, Steven White <swhite4...@gmail.com> wrote: > > > Hi folks, > > > > With Solr 5.0, the WAR file is deprecated and I see Jetty is included > with > > Solr. What if I have my own Web server into which I need to deploy Solr, > > how do I go about doing this correctly without messing things up and > making > > sure Solr works? Or is this not recommended and Jetty is the way to go, > no > > questions asked? > > > > Thanks > > > > Steve > > >
