配置服务器时我是否做错了什么.xml将另一个域指向不是 webapps 文件夹中的 ROOT 文件夹的文件夹



好的,我有一个主域:mainDM.com(这是从 Godaddy 购买的名为 mainDM 的应用程序的域(。我还买了一个带有IP地址xxx.xx.xx.xx的Godaddy Win2000 VPS。

在 Godaddy 中,我将那个领域指向xxx.xx.xx.xx

在Tomcat服务器中,webapps文件夹中,有一个ROOT文件夹,我将mainDM应用程序的所有html文件放入ROOT文件夹中。一切都很好。那是当我打开mainDM.com我可以看到我的应用程序运行正常时。

现在,我开发了另一个名为otherDM的应用程序,我还在Godaddy中购买了一个域名otherDM.com,我也将其指向xxx.xx.xx.xx。现在打开otherDM.com时,我看不到otherDM应用程序,而是mainDM应用程序。所以我想配置server.xml,以便当我打开otherDM.com时,它将显示otherDM Web 应用程序。 注意:有一个otherDM文件夹,其中包含webapps文件夹中otherDM应用程序的所有html文件。

这是我在server.xml所做的,但什么也没发生。

<?xml version='1.0' encoding='utf-8'?>
<!-- Note:  A "Server" is not itself a "Container", so you may not
     define subcomponents such as "Valves" at this level.
     Documentation at /docs/config/server.html
 -->
<Server port="8005" shutdown="SHUTDOWN">
  <!-- Security listener. Documentation at /docs/config/listeners.html
  <Listener className="org.apache.catalina.security.SecurityListener" />
  -->
  <!--APR library loader. Documentation at /docs/apr.html -->
  <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
  <!--Initialize Jasper prior to webapps are loaded. Documentation at /docs/jasper-howto.html -->
  <Listener className="org.apache.catalina.core.JasperListener" />
  <!-- Prevent memory leaks due to use of particular java/javax APIs-->
  <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
  <Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />
  <!-- Global JNDI resources
       Documentation at /docs/jndi-resources-howto.html
  -->
  <GlobalNamingResources>
    <!-- Editable user database that can also be used by
         UserDatabaseRealm to authenticate users
    -->
    <Resource name="UserDatabase" auth="Container"
              type="org.apache.catalina.UserDatabase"
              description="User database that can be updated and saved"
              factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
              pathname="conf/tomcat-users.xml" />
  </GlobalNamingResources>
  <!-- A "Service" is a collection of one or more "Connectors" that share
       a single "Container" Note:  A "Service" is not itself a "Container",
       so you may not define subcomponents such as "Valves" at this level.
       Documentation at /docs/config/service.html
   -->
  <Service name="Catalina">
    <!--The connectors can use a shared executor, you can define one or more named thread pools-->
    <!--
    <Executor name="tomcatThreadPool" namePrefix="catalina-exec-"
        maxThreads="150" minSpareThreads="4"/>
    -->

    <!-- A "Connector" represents an endpoint by which requests are received
         and responses are returned. Documentation at :
         Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)
         Java AJP  Connector: /docs/config/ajp.html
         APR (HTTP/AJP) Connector: /docs/apr.html
         Define a non-SSL HTTP/1.1 Connector on port 8080
    -->
    <Connector port="80" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />
    <!-- A "Connector" using the shared thread pool-->
    <!--
    <Connector executor="tomcatThreadPool"
               port="8080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="8443" />
    -->
    <!-- Define a SSL HTTP/1.1 Connector on port 8443
         This connector uses the BIO implementation that requires the JSSE
         style configuration. When using the APR/native implementation, the
         OpenSSL style configuration is required as described in the APR/native
         documentation -->
    <!--
    <Connector port="8443" protocol="org.apache.coyote.http11.Http11Protocol"
               maxThreads="150" SSLEnabled="true" scheme="https" secure="true"
               clientAuth="false" sslProtocol="TLS" />
    -->
    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector port="8009" protocol="AJP/1.3" redirectPort="8443" />

    <!-- An Engine represents the entry point (within Catalina) that processes
         every request.  The Engine implementation for Tomcat stand alone
         analyzes the HTTP headers included with the request, and passes them
         on to the appropriate Host (virtual host).
         Documentation at /docs/config/engine.html -->
    <!-- You should set jvmRoute to support load-balancing via AJP ie :
    <Engine name="Catalina" defaultHost="localhost" jvmRoute="jvm1">
    -->
    <Engine name="Catalina" defaultHost="localhost">
      <!--For clustering, please take a look at documentation at:
          /docs/cluster-howto.html  (simple how to)
          /docs/config/cluster.html (reference documentation) -->
      <!--
      <Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/>
      -->
      <!-- Use the LockOutRealm to prevent attempts to guess user passwords
           via a brute-force attack -->
      <Realm className="org.apache.catalina.realm.LockOutRealm">
        <!-- This Realm uses the UserDatabase configured in the global JNDI
             resources under the key "UserDatabase".  Any edits
             that are performed against this UserDatabase are immediately
             available for use by the Realm.  -->
        <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
               resourceName="UserDatabase"/>
      </Realm>
      <Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true">
        <!-- SingleSignOn valve, share authentication between web applications
             Documentation at: /docs/config/valve.html -->
        <!--
        <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
        -->
        <!-- Access log processes all example.
             Documentation at: /docs/config/valve.html
             Note: The pattern used is equivalent to using pattern="common" -->
        <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
               prefix="localhost_access_log." suffix=".txt"
               pattern="%h %l %u %t &quot;%r&quot; %s %b" />
      </Host>
      <Host name="otherDM.com" appbase="otherDM" autoDeploy="true" unpackWARs="true">
        <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
               prefix="otherDM_access_log." suffix=".txt"
               pattern="%h %l %u %t &quot;%r&quot; %s %b" />
      </Host>
    </Engine>
  </Service>
</Server>

我确实重新启动了我的Tomcat服务器,但没有任何反应,每次我打开 otherDM.com 时,它都会显示mainDM应用程序。但是,如果我打开otherDM.com/otherDM或打开mainDM.com/otherDM那么我可以看到otherDM应用程序。

我做错了什么吗?如何解决?

"host"标签的"appbase"属性指向(如果相对的(,如您的情况,指向CATALINA_HOME下面的目录。因此,只需创建两个这样的文件夹:

[CATALINA_HOME]/mainDomain
[CATALINA_HOME]/otherDomain

并在其中创建两个 ROOT 文件夹。将应用复制到根目录中。

然后将应用库设置为:

 <Host name="localhost"  appBase="mainDomain" ...
 <Host name="mainDomain.com"  appBase="mainDomain" ...
 <Host name="otherDomain.com"  appBase="otherDomain" ...

我修复了,

首先,我按照斯特凡说的去做,创造

[CATALINA_HOME]/otherDM

并将所有html文件放入mainDM的根目录并相应地otherDM

然后,将Host添加到server.xml

<Host name="localhost"  appBase="mainDM" ...
 <Host name="otherDM.com"  appBase="otherDM" ...

最后,我需要将 ROOT.xml 添加到C:tomcat7confCatalinaotherDM.comROOT.xml

<Context 
  docBase="C:/tomcat7/otherDM/ROOT" 
  path="" 
  reloadable="true" 
/>

AN 现在它运行良好,我可以尽可能添加许多域

最新更新