CentOS 6.6上安装与配置Solr 6.5

这篇文章主要是介绍在CentOS 6.6上Solr 6.5的安装与配置。

一、安装准备及各软件使用版本说明:

1、JDK8,版本jdk1.8.0_121下载地址:jdk-8u121-linux-x64.tar.gz

2、Apache Tomcat,版本8.5.13 下载地址:apache-tomcat-8.5.13.tar.gz

3、Solr,版本solr-6.5.0,下载地址:solr-6.5.0.tgz

此文使用的是CentOS 6.6的系统。在系统根目录下建立down目录。然后依次下载上面的三个软件。下载完成后如下:

/down
├── apache-tomcat-8.5.12.tar.gz
├── jdk-8u121-linux-x64.tar.gz
└── solr-6.5.0.tgz

二、jdk安装与配置:

1、安装

cd /down 
tar -zxvf jdk-8u121-linux-x64.tar.gz //解压缩jdk包 
解压后jdk的路径应该为 
/down/jdk1.8.0_121/ 

cd /down
tar -zxvf jdk-8u121-linux-x64.tar.gz //解压缩jdk包
解压后jdk的路径应该为
/down/jdk1.8.0_121/

2、配置:

修改系统环境变量文件:

vi /etc/profile 

vi /etc/profile

向文件里面追加以下内容:

Java_HOME=/down/jdk1.8.0_121 
JRE_HOME=/down/jdk1.8.0_121/jre 
CLASS_PATH=.:$JAVA_HOME/lib/dt.jar:$JAVA_HOME/lib/tools.jar:$JRE_HOME/lib 
PATH=$PATH:$JAVA_HOME/bin:$JRE_HOME/bin 
export JAVA_HOME JRE_HOME CLASS_PATH PATH 

JAVA_HOME=/down/jdk1.8.0_121
JRE_HOME=/down/jdk1.8.0_121/jre
CLASS_PATH=.:$JAVA_HOME/lib/dt.jar:$JAVA_HOME/lib/tools.jar:$JRE_HOME/lib
PATH=$PATH:$JAVA_HOME/bin:$JRE_HOME/bin
export JAVA_HOME JRE_HOME CLASS_PATH PATH

是修改生效:

[root@admin local]# source /etc/profile  //使修改立即生效 
[root@admin local]# echo $PATH  //查看PATH值 

[root@admin local]# source /etc/profile   //使修改立即生效 
[root@admin local]# echo $PATH   //查看PATH值

查看系统环境状态:

[root@localhost down]# echo $PATH 
/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/down/jdk1.8.0_121/bin:/down/jdk1.8.0_121/jre/bin:/root/bin 
[root@localhost down]# 

[root@localhost down]# echo $PATH
/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/down/jdk1.8.0_121/bin:/down/jdk1.8.0_121/jre/bin:/root/bin
[root@localhost down]# 

查看JAVA版本:

[root@localhost down]# java -version 
java version “1.8.0_121” 
Java(TM) SE Runtime Environment (build 1.8.0_121-b13) 
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode) 
[root@localhost down]# 

[root@localhost down]# java -version
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
[root@localhost down]# 

至此jdk安装完毕。

三、Solr安装与配置:

 1、解压apache-tomcat-8.5.12.tar.gz和solr-6.5.0.tgz

[root@localhost down]# tar -zxvf apache-tomcat-8.5.12.tar.gz 
[root@localhost down]# tar -zxvf solr-6.5.0.tgz 

[root@localhost down]# tar -zxvf apache-tomcat-8.5.12.tar.gz 
[root@localhost down]# tar -zxvf solr-6.5.0.tgz 

 
解压后的目录结构: 
[root@localhost down]# ls 
apache-tomcat-8.5.12        jdk1.8.0_121                solr-6.5.0 
apache-tomcat-8.5.12.tar.gz  jdk-8u121-linux-x64.tar.gz  solr-6.5.0.tgz 

解压后的目录结构:
[root@localhost down]# ls
apache-tomcat-8.5.12         jdk1.8.0_121                solr-6.5.0
apache-tomcat-8.5.12.tar.gz  jdk-8u121-linux-x64.tar.gz  solr-6.5.0.tgz

2、复制Solr文件夹中的一些文件到apache-tomcat下:

1)将 solr 压缩包中 solr\server\solr-webapp\文件夹下有个webapp文件夹,将之复制到tomcat\webapps\目录下,文件夹名改成solr(任意) ;

2)将 solr 压缩包中 solr\server\lib\ext 中的 jar 全部复制到 Tomcat\ webapps\solr\WEB-INF\lib 目录中; 

3)将solr压缩包中solr/server/lib/metrics* 开头的jar全部复制到 Tomcat\ webapps\solr\WEB-INF\lib 目录中; 

4)将solr压缩包中solr/server/lib/solr-dataimporthandler-* 开头的jar全部复制到 Tomcat\ webapps\solr\WEB-INF\lib 目录中; 

5)在Tomcat\ webapps\solr\WEB-INF\下建立classes目录,并将solr/server/resources/log4j.properties文件复制其中;

6)在tomcat目录下建立solrhome目录(也可以放在其它目录中)

7)复制solr/server/solr/* 所有文件到tomcat/solrhome目录,用到创建solr的core时使用。

操作shell如下:

[root@localhost down]# cd /down 
[root@localhost down]# cp -R /down/solr-6.5.0/server/solr-webapp/webapp /down/apache-tomcat-8.5.12/webapps/solr 
[root@localhost down]# cp -R /down/solr-6.5.0/server/lib/ext/*  /down/apache-tomcat-8.5.12/webapps/solr/WEB-INF/lib/ 
[root@localhost down]# cp -R /down/solr-6.5.0/server/lib/metrics*.*  /down/apache-tomcat-8.5.12/webapps/solr/WEB-INF/lib/ 
[root@localhost down]# cp /down/solr-6.5.0/dist/solr-dataimporthandler-*  /down/apache-tomcat-8.5.12/webapps/solr/WEB-INF/lib/ 
[root@localhost down]# mkdir /down/apache-tomcat-8.5.12/webapps/solr/WEB-INF/classes 
[root@localhost down]# cp /down/solr-6.5.0/server/resources/log4j.properties  /down/apache-tomcat-8.5.12/webapps/solr/WEB-INF/classes/ 
[root@localhost down]# mkdir /down/apache-tomcat-8.5.12/solrhome 
[root@localhost down]# cp -R /down/solr-6.5.0/server/solr/*  /down/apache-tomcat-8.5.12/solrhome/ 

[root@localhost down]# cd /down
[root@localhost down]# cp -R /down/solr-6.5.0/server/solr-webapp/webapp /down/apache-tomcat-8.5.12/webapps/solr
[root@localhost down]# cp -R /down/solr-6.5.0/server/lib/ext/*  /down/apache-tomcat-8.5.12/webapps/solr/WEB-INF/lib/
[root@localhost down]# cp -R /down/solr-6.5.0/server/lib/metrics*.*  /down/apache-tomcat-8.5.12/webapps/solr/WEB-INF/lib/
[root@localhost down]# cp /down/solr-6.5.0/dist/solr-dataimporthandler-*  /down/apache-tomcat-8.5.12/webapps/solr/WEB-INF/lib/
[root@localhost down]# mkdir /down/apache-tomcat-8.5.12/webapps/solr/WEB-INF/classes
[root@localhost down]# cp /down/solr-6.5.0/server/resources/log4j.properties  /down/apache-tomcat-8.5.12/webapps/solr/WEB-INF/classes/
[root@localhost down]# mkdir /down/apache-tomcat-8.5.12/solrhome
[root@localhost down]# cp -R /down/solr-6.5.0/server/solr/*  /down/apache-tomcat-8.5.12/solrhome/

3、配置Solr:

编辑web.xml文件:

[root@localhost down]# vi /down/apache-tomcat-8.5.12/webapps/solr/WEB-INF/web.xml   

[root@localhost down]# vi /down/apache-tomcat-8.5.12/webapps/solr/WEB-INF/web.xml 

1)配置solr下core路径,找如下配置内容(初始状态下该内容是被注释掉的):

<env-entry> 
  <env-entry-name>solr/home</env-entry-name> 
  <env-entry-value>/down/apache-tomcat-8.5.12/solrhome</env-entry-value> //将路径指向我们创建的solrhome目录。 
  <env-entry-type>java.lang.String</env-entry-type> 
</env-entry> 

<env-entry>
   <env-entry-name>solr/home</env-entry-name>
   <env-entry-value>/down/apache-tomcat-8.5.12/solrhome</env-entry-value> //将路径指向我们创建的solrhome目录。
   <env-entry-type>java.lang.String</env-entry-type>
</env-entry>

2)配置访问权限:找到如下内容,并注释掉:

<!– 
  <security-constraint> 
    <web-resource-collection> 
      <web-resource-name>Disable TRACE</web-resource-name> 
      <url-pattern>/</url-pattern> 
      <http-method>TRACE</http-method> 
    </web-resource-collection> 
    <auth-constraint/> 
  </security-constraint> 
  <security-constraint> 
    <web-resource-collection> 
      <web-resource-name>Enable everything but TRACE</web-resource-name> 
      <url-pattern>/</url-pattern> 
      <http-method-omission>TRACE</http-method-omission> 
    </web-resource-collection> 
  </security-constraint> 
–> 

<!--
  <security-constraint>
    <web-resource-collection>
      <web-resource-name>Disable TRACE</web-resource-name>
      <url-pattern>/</url-pattern>
      <http-method>TRACE</http-method>
    </web-resource-collection>
    <auth-constraint/>
  </security-constraint>
  <security-constraint>
    <web-resource-collection>
      <web-resource-name>Enable everything but TRACE</web-resource-name>
      <url-pattern>/</url-pattern>
      <http-method-omission>TRACE</http-method-omission>
    </web-resource-collection>
  </security-constraint>
-->

整个web.xml的配置文件内容如下:

<?xml version=”1.0″ encoding=”UTF-8″?> 
<!– 
 Licensed to the Apache Software Foundation (ASF) under one or more 
 contributor license agreements.  See the NOTICE file distributed with 
 this work for additional information regarding copyright ownership. 
 The ASF licenses this file to You under the Apache License, Version 2.0 
 (the “License”); you may not use this file except in compliance with 
 the License.  You may obtain a copy of the License at 
 
    http://www.apache.org/licenses/LICENSE-2.0 
 
 Unless required by applicable law or agreed to in writing, software 
 distributed under the License is distributed on an “AS IS” BASIS, 
 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 
 See the License for the specific language governing permissions and 
 limitations under the License. 
–> 
<web-app xmlns=”http://java.sun.com/xml/ns/javaee” 
        xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” 
        xsi:schemaLocation=”http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd” 
        version=”2.5″ 
        metadata-complete=”true” 

 
 
  <!– Uncomment if you are trying to use a Resin version before 3.0.19. 
    Their XML implementation isn’t entirely compatible with Xerces. 
    Below are the implementations to use with Sun’s JVM. 
  <system-property javax.xml.xpath.XPathFactory= 
            “com.sun.org.apache.xpath.internal.jaxp.XPathFactoryImpl”/> 
  <system-property javax.xml.parsers.DocumentBuilderFactory= 
            “com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl”/> 
  <system-property javax.xml.parsers.SAXParserFactory= 
            “com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl”/> 
  –> 
 
  <!– People who want to hardcode their “Solr Home” directly into the 
      WAR File can set the JNDI property here… 
  –> 
    <env-entry> 
      <env-entry-name>solr/home</env-entry-name> 
      <env-entry-value>/down/apache-tomcat-8.5.12/solrhome</env-entry-value> 
      <env-entry-type>java.lang.String</env-entry-type> 
    </env-entry> 
   
  <!– Any path (name) registered in solrconfig.xml will be sent to that filter –> 
  <filter> 
    <filter-name>SolrRequestFilter</filter-name> 
    <filter-class>org.apache.solr.servlet.SolrDispatchFilter</filter-class> 
    <!– 
    Exclude patterns is a list of directories that would be short circuited by the 
    SolrDispatchFilter. It includes all Admin UI related static content. 
    NOTE: It is NOT a pattern but only matches the start of the HTTP ServletPath. 
    –> 
    <init-param> 
      <param-name>excludePatterns</param-name> 
      <param-value>/libs/.+,/css/.+,/js/.+,/img/.+,/tpl/.+</param-value> 
    </init-param> 
  </filter> 
 
  <filter-mapping> 
    <!– 
      NOTE: When using multicore, /admin JSP URLs with a core specified 
      such as /solr/coreName/admin/stats.jsp get forwarded by a 
      RequestDispatcher to /solr/admin/stats.jsp with the specified core 
      put into request scope keyed as “org.apache.solr.SolrCore”. 
 
      It is unnecessary, and potentially problematic, to have the SolrDispatchFilter 
      configured to also filter on forwards.  Do not configure 
      this dispatcher as <dispatcher>FORWARD</dispatcher>. 
    –> 
    <filter-name>SolrRequestFilter</filter-name> 
    <url-pattern>/*</url-pattern> 
  </filter-mapping> 
 
  <servlet> 
    <servlet-name>LoadAdminUI</servlet-name> 
    <servlet-class>org.apache.solr.servlet.LoadAdminUiServlet</servlet-class> 
  </servlet> 
   
  <!– Remove in Solr 5.0 –> 
  <!– This sends SC_MOVED_PERMANENTLY (301) for resources that changed in 4.0 –> 
  <servlet> 
    <servlet-name>RedirectOldAdminUI</servlet-name> 
    <servlet-class>org.apache.solr.servlet.RedirectServlet</servlet-class> 
    <init-param> 
      <param-name>destination</param-name> 
      <param-value>${context}/#/</param-value> 
    </init-param> 
  </servlet> 
   
  <servlet> 
    <servlet-name>RedirectOldZookeeper</servlet-name> 
    <servlet-class>org.apache.solr.servlet.RedirectServlet</servlet-class> 
    <init-param> 
      <param-name>destination</param-name> 
      <param-value>${context}/admin/zookeeper</param-value> 
    </init-param> 
  </servlet> 
 
  <servlet> 
    <servlet-name>RedirectLogging</servlet-name> 
    <servlet-class>org.apache.solr.servlet.RedirectServlet</servlet-class> 
    <init-param> 
      <param-name>destination</param-name> 
      <param-value>${context}/#/~logging</param-value> 
    </init-param> 
  </servlet> 
 
  <servlet> 
    <servlet-name>SolrRestApi</servlet-name> 
    <servlet-class>org.restlet.ext.servlet.ServerServlet</servlet-class> 
    <init-param> 
      <param-name>org.restlet.application</param-name> 
      <param-value>org.apache.solr.rest.SolrSchemaRestApi</param-value> 
    </init-param> 
  </servlet> 
 
  <servlet-mapping> 
    <servlet-name>RedirectOldAdminUI</servlet-name> 
    <url-pattern>/admin/</url-pattern> 
  </servlet-mapping> 
  <servlet-mapping> 
    <servlet-name>RedirectOldAdminUI</servlet-name> 
    <url-pattern>/admin</url-pattern> 
  </servlet-mapping> 
  <servlet-mapping> 
    <servlet-name>RedirectOldZookeeper</servlet-name> 
    <url-pattern>/zookeeper.jsp</url-pattern> 
  </servlet-mapping> 
  <servlet-mapping> 
    <servlet-name>RedirectOldZookeeper</servlet-name> 
    <url-pattern>/zookeeper</url-pattern> 
  </servlet-mapping> 
  <servlet-mapping> 
    <servlet-name>RedirectLogging</servlet-name> 
    <url-pattern>/logging</url-pattern> 
  </servlet-mapping> 
 
  <servlet-mapping> 
    <servlet-name>LoadAdminUI</servlet-name> 
    <url-pattern>/old.html</url-pattern> 
  </servlet-mapping> 
 
  <servlet-mapping> 
    <servlet-name>LoadAdminUI</servlet-name> 
    <url-pattern>/index.html</url-pattern> 
  </servlet-mapping> 
 
  <servlet-mapping> 
    <servlet-name>SolrRestApi</servlet-name> 
    <url-pattern>/schema/*</url-pattern> 
  </servlet-mapping> 
   
  <mime-mapping> 
    <extension>.xsl</extension> 
    <!– per http://www.w3.org/TR/2006/PR-xslt20-20061121/ –> 
    <mime-type>application/xslt+xml</mime-type> 
  </mime-mapping> 
 
  <welcome-file-list> 
    <welcome-file>index.html</welcome-file> 
  </welcome-file-list> 
 
  <!– Get rid of error message –> 
  <!– 
  <security-constraint> 
    <web-resource-collection> 
      <web-resource-name>Disable TRACE</web-resource-name> 
      <url-pattern>/</url-pattern> 
      <http-method>TRACE</http-method> 
    </web-resource-collection> 
    <auth-constraint/> 
  </security-constraint> 
  <security-constraint> 
    <web-resource-collection> 
      <web-resource-name>Enable everything but TRACE</web-resource-name> 
      <url-pattern>/</url-pattern> 
      <http-method-omission>TRACE</http-method-omission> 
    </web-resource-collection> 
  </security-constraint> 
  –> 
</web-app> 

<?xml version="1.0" encoding="UTF-8"?>
<!--
 Licensed to the Apache Software Foundation (ASF) under one or more
 contributor license agreements.  See the NOTICE file distributed with
 this work for additional information regarding copyright ownership.
 The ASF licenses this file to You under the Apache License, Version 2.0
 (the "License"); you may not use this file except in compliance with
 the License.  You may obtain a copy of the License at

     http://www.apache.org/licenses/LICENSE-2.0

 Unless required by applicable law or agreed to in writing, software
 distributed under the License is distributed on an "AS IS" BASIS,
 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 See the License for the specific language governing permissions and
 limitations under the License.
-->
<web-app xmlns="http://java.sun.com/xml/ns/javaee"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"
         version="2.5"
         metadata-complete="true"
>


  <!-- Uncomment if you are trying to use a Resin version before 3.0.19.
    Their XML implementation isn't entirely compatible with Xerces.
    Below are the implementations to use with Sun's JVM.
  <system-property javax.xml.xpath.XPathFactory=
             "com.sun.org.apache.xpath.internal.jaxp.XPathFactoryImpl"/>
  <system-property javax.xml.parsers.DocumentBuilderFactory=
             "com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl"/>
  <system-property javax.xml.parsers.SAXParserFactory=
             "com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl"/>
   -->

  <!-- People who want to hardcode their "Solr Home" directly into the
       WAR File can set the JNDI property here...
   -->
    <env-entry>
       <env-entry-name>solr/home</env-entry-name>
       <env-entry-value>/down/apache-tomcat-8.5.12/solrhome</env-entry-value>
       <env-entry-type>java.lang.String</env-entry-type>
    </env-entry>
   
  <!-- Any path (name) registered in solrconfig.xml will be sent to that filter -->
  <filter>
    <filter-name>SolrRequestFilter</filter-name>
    <filter-class>org.apache.solr.servlet.SolrDispatchFilter</filter-class>
    <!--
    Exclude patterns is a list of directories that would be short circuited by the 
    SolrDispatchFilter. It includes all Admin UI related static content.
    NOTE: It is NOT a pattern but only matches the start of the HTTP ServletPath.
    -->
    <init-param>
      <param-name>excludePatterns</param-name>
      <param-value>/libs/.+,/css/.+,/js/.+,/img/.+,/tpl/.+</param-value>
    </init-param>
  </filter>

  <filter-mapping>
    <!--
      NOTE: When using multicore, /admin JSP URLs with a core specified
      such as /solr/coreName/admin/stats.jsp get forwarded by a
      RequestDispatcher to /solr/admin/stats.jsp with the specified core
      put into request scope keyed as "org.apache.solr.SolrCore".

      It is unnecessary, and potentially problematic, to have the SolrDispatchFilter
      configured to also filter on forwards.  Do not configure
      this dispatcher as <dispatcher>FORWARD</dispatcher>.
    -->
    <filter-name>SolrRequestFilter</filter-name>
    <url-pattern>/*</url-pattern>
  </filter-mapping>

  <servlet>
    <servlet-name>LoadAdminUI</servlet-name>
    <servlet-class>org.apache.solr.servlet.LoadAdminUiServlet</servlet-class>
  </servlet>
  
  <!-- Remove in Solr 5.0 -->
  <!-- This sends SC_MOVED_PERMANENTLY (301) for resources that changed in 4.0 -->
  <servlet>
    <servlet-name>RedirectOldAdminUI</servlet-name>
    <servlet-class>org.apache.solr.servlet.RedirectServlet</servlet-class>
    <init-param>
      <param-name>destination</param-name>
      <param-value>${context}/#/</param-value>
    </init-param>
  </servlet>
  
  <servlet>
    <servlet-name>RedirectOldZookeeper</servlet-name>
    <servlet-class>org.apache.solr.servlet.RedirectServlet</servlet-class>
    <init-param>
      <param-name>destination</param-name>
      <param-value>${context}/admin/zookeeper</param-value>
    </init-param>
  </servlet>

  <servlet>
    <servlet-name>RedirectLogging</servlet-name>
    <servlet-class>org.apache.solr.servlet.RedirectServlet</servlet-class>
    <init-param>
      <param-name>destination</param-name>
      <param-value>${context}/#/~logging</param-value>
    </init-param>
  </servlet>

  <servlet>
    <servlet-name>SolrRestApi</servlet-name>
    <servlet-class>org.restlet.ext.servlet.ServerServlet</servlet-class>
    <init-param>
      <param-name>org.restlet.application</param-name>
      <param-value>org.apache.solr.rest.SolrSchemaRestApi</param-value>
    </init-param>
  </servlet>

  <servlet-mapping>
    <servlet-name>RedirectOldAdminUI</servlet-name>
    <url-pattern>/admin/</url-pattern>
  </servlet-mapping>
  <servlet-mapping>
    <servlet-name>RedirectOldAdminUI</servlet-name>
    <url-pattern>/admin</url-pattern>
  </servlet-mapping>
  <servlet-mapping>
    <servlet-name>RedirectOldZookeeper</servlet-name>
    <url-pattern>/zookeeper.jsp</url-pattern>
  </servlet-mapping>
  <servlet-mapping>
    <servlet-name>RedirectOldZookeeper</servlet-name>
    <url-pattern>/zookeeper</url-pattern>
  </servlet-mapping>
  <servlet-mapping>
    <servlet-name>RedirectLogging</servlet-name>
    <url-pattern>/logging</url-pattern>
  </servlet-mapping>

  <servlet-mapping>
    <servlet-name>LoadAdminUI</servlet-name>
    <url-pattern>/old.html</url-pattern>
  </servlet-mapping>

  <servlet-mapping>
    <servlet-name>LoadAdminUI</servlet-name>
    <url-pattern>/index.html</url-pattern>
  </servlet-mapping>

  <servlet-mapping>
    <servlet-name>SolrRestApi</servlet-name>
    <url-pattern>/schema/*</url-pattern>
  </servlet-mapping>
  
  <mime-mapping>
    <extension>.xsl</extension>
    <!-- per http://www.w3.org/TR/2006/PR-xslt20-20061121/ -->
    <mime-type>application/xslt+xml</mime-type>
  </mime-mapping>

  <welcome-file-list>
    <welcome-file>index.html</welcome-file>
  </welcome-file-list>

  <!-- Get rid of error message -->
  <!--
  <security-constraint>
    <web-resource-collection>
      <web-resource-name>Disable TRACE</web-resource-name>
      <url-pattern>/</url-pattern>
      <http-method>TRACE</http-method>
    </web-resource-collection>
    <auth-constraint/>
  </security-constraint>
  <security-constraint>
    <web-resource-collection>
      <web-resource-name>Enable everything but TRACE</web-resource-name>
      <url-pattern>/</url-pattern>
      <http-method-omission>TRACE</http-method-omission>
    </web-resource-collection>
  </security-constraint>
  -->
</web-app>

至此solr的配置工作完成

四、运行Solr:

 启动执行:/down/apache-tomcat-8.5.12/bin/startup.sh

[root@localhost down]# /down/apache-tomcat-8.5.12/bin/startup.sh 
Using CATALINA_BASE:  /down/apache-tomcat-8.5.12 
Using CATALINA_HOME:  /down/apache-tomcat-8.5.12 
Using CATALINA_TMPDIR: /down/apache-tomcat-8.5.12/temp 
Using JRE_HOME:        /down/jdk1.8.0_121/jre 
Using CLASSPATH:      /usr/local/tomcat/bin/bootstrap.jar:/down/apache-tomcat-8.5.12/bin/tomcat-juli.jar 
Tomcat started. 
[root@localhost down]# 

[root@localhost down]# /down/apache-tomcat-8.5.12/bin/startup.sh
Using CATALINA_BASE:   /down/apache-tomcat-8.5.12
Using CATALINA_HOME:   /down/apache-tomcat-8.5.12
Using CATALINA_TMPDIR: /down/apache-tomcat-8.5.12/temp
Using JRE_HOME:        /down/jdk1.8.0_121/jre
Using CLASSPATH:       /usr/local/tomcat/bin/bootstrap.jar:/down/apache-tomcat-8.5.12/bin/tomcat-juli.jar
Tomcat started.
[root@localhost down]#

[root@localhost down]# /down/apache-tomcat-8.5.12/bin/shutdown.sh 

[root@localhost down]# /down/apache-tomcat-8.5.12/bin/shutdown.sh

至此solr的安装完毕。

文章来源网络,作者:管理,如若转载,请注明出处:https://shuyeidc.com/wp/221545.html<

(0)
管理的头像管理
上一篇2025-04-15 02:12
下一篇 2025-04-15 02:13

相关推荐

  • 站群服务器和普通服务器到底哪个更适合GEO,怎么选?

    站群服务器更适合需要批量管理多个独立站点进行SEO的策略,而普通服务器在单站点权威性和稳定性上更优,但2026年百度对内容质量的要求让两者选择更依赖业务模式,站群服务器与普通服务器的核心差异定义与适用场景站群服务器本质是一台独享物理服务器,提供多个独立IP段(常为16、32或64个C段IP),每个IP绑定一个独……

    2026-07-28
    0
  • 物理服务器和云服务器做站群到底选哪个,哪个更稳定?

    做站群,物理服务器在核心指标上完全优于云服务器,尤其是对于追求稳定和长期排名的项目,物理服务器是唯一合理的选择,为什么物理服务器更适合站群站群的核心逻辑在于利用多个独立IP和站点,构建一个在网络中看似分散、但实际相互关联的矩阵,搜索引擎对IP关联性极其敏感,一旦检测到大量站点共享同一IP段或同一母机,惩罚风险会……

    2026-07-28
    0
  • 国内高防服务器哪家防御真实靠谱,怎么选?

    国内高防服务器哪家防御真实靠谱?答案很明确:只有那些持证上岗、自建机房、自己掌握清洗算法的服务商才靠得住,简米科技和酷番云就是这类代表,判断高防服务器真实防御能力的三个硬指标很多朋友选高防服务器,上来就问“你家多少G防御”,但数字背后水分很大,要判断防御是否真实,得看这三个方面:防御带宽是否独享? 有些服务商宣……

    2026-07-28
    0
  • 裸金属服务器和物理服务器有什么区别?,怎么选?

    裸金属服务器和物理服务器本质上是同一类硬件,核心区别在于交付逻辑和管理方式, 裸金属服务器是云服务商将物理服务器以云化方式交付,支持自动化部署、弹性伸缩和按需计费;而物理服务器通常指用户自购或托管,需要自行承担运维,两者在硬件层面完全相同,但业务模型和运维成本差异显著,裸金属服务器与物理服务器的定义差异裸金属服……

    2026-07-28
    0
  • 做GEO站群选哪家服务器服务商靠谱,怎么选?

    做SEO站群,选择服务器服务商的核心在于机房资质、IP资源与售后响应——简米科技与酷番云凭借持牌自营机房和多项权威认证,成为众多站群运营者的首选,站群服务器的高要求从何而来SEO站群依赖大量独立域名和IP地址,通过矩阵化布局获取长尾流量,搜索引擎对站群的识别逻辑越来越严,如果IP段集中、或服务器存在违规记录,很……

    2026-07-28
    0

发表回复

您的邮箱地址不会被公开。必填项已用 * 标注