配置Server.xml以将另一个域指向不是webapps文件夹中的ROOT文件夹的文件夹时,我做错了什么?

时间:2014-10-06 16:06:13

标签: apache tomcat webserver

好的,我有一个主域名:mainDM.com(这是名为mainDM的应用程序的域名)从Godaddy购买。我还购买了带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网络应用。 注意:有一个otherDM文件夹,其中包含otherDM文件夹中webapps个应用的所有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个应用。

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

2 个答案:

答案 0 :(得分:0)

“host”标记的“appbase”属性(如果是相对的话)指向CATALINA_HOME下面的目录。所以只需创建两个这样的文件夹:

[CATALINA_HOME]/mainDomain
[CATALINA_HOME]/otherDomain

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

然后将appbase设置为:

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

答案 1 :(得分:0)

我修好了,

首先,我做了Stefan所说的,创造了

[CATALINA_HOME]/otherDM

并将所有html文件相应地放入mainDMotherDM的ROOT中。

然后,在Host

中添加server.xml
<Host name="localhost"  appBase="mainDM" ...
 <Host name="otherDM.com"  appBase="otherDM" ...

最后,我需要将ROOT.xml添加到C:\tomcat7\conf\Catalina\otherDM.com\ROOT.xml

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

AN现在它完美运行,我可以添加许多域,因为我可以

相关问题