Monday, November 10, 2014

Tomcat 7 2nd instance for the impaitent

For the quick and dirty setup of a frontend loadbalanced (VERY BASIC) configuration.


Snag Apache.


For Fedora fans thats: 

yum install httpd
yum install mod_ssl
systemctl enable httpd.service
systemctl start httpd.service

RHEL/CentOS/OEL/etc...:

yum install httpd
yum install mod_ssl
chkconfig httpd on
service httpd start

A cheat sheet for systemd:
https://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet

For Debian fans thats:

apt-get install apache2 sudo 
update-rc.d apache2 defaults 
/etc/init.d/apache2 start


Snag Tomcat.

http://tomcat.apache.org/download-70.cgi#7.0.56
Its an auto generated link based on mirrors. copy that link and paste in a wget.

wget http://apache.tradebit.com/pub/tomcat/tomcat-7/v7.0.56/bin/apache-tomcat-7.0.56.tar.gz

You will want to make two copies of tomcat for this example I am naming the instances "tomcat-1" and "tomcat-2".

wget http://apache.tradebit.com/pub/tomcat/tomcat-7/v7.0.56/bin/apache-tomcat-7.0.56.tar.gz
tar -zxvf apache-tomcat-7.0.56.tar.gz
mkdir tomcat1 tomcat2
cp -R apache-tomcat-7.0.56/* tomcat-1
cp -R apache-tomcat-7.0.56/* tomcat-2


Copy this configuration to you're tomcat-2 instance under conf/server.xml:
This file will bring up http https and ajp ports in the 9000 range (9080,9443,9009):

<?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.
-->
<!-- 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="9005" 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 9080
    -->
    <Connector port="9080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="9443" />
    <!-- A "Connector" using the shared thread pool-->
    <!--
    <Connector executor="tomcatThreadPool"
               port="9080" protocol="HTTP/1.1"
               connectionTimeout="20000"
               redirectPort="9443" />
    -->
    <!-- Define a SSL HTTP/1.1 Connector on port 9443
         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="9443" 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 9009 -->
    <Connector port="9009" protocol="AJP/1.3" redirectPort="9443" />


    <!-- 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>
    </Engine>
  </Service>
</Server>


Modify your security permissions to allow manager and example apps from default tomcat.
Replace your default tomcat-users with this one under conf/tomcat-users.xml (not production recommended):


<?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.
-->
<tomcat-users>
<!--
  NOTE:  By default, no user is included in the "manager-gui" role required
  to operate the "/manager/html" web application.  If you wish to use this app,
  you must define such a user - the username and password are arbitrary.
-->
<!--
  NOTE:  The sample user and role entries below are wrapped in a comment
  and thus are ignored when reading this file. Do not forget to remove
  <!.. ..> that surrounds them.
-->
<!--
  <role rolename="tomcat"/>
  <role rolename="role1"/>
  <user username="tomcat" password="tomcat" roles="tomcat"/>
  <user username="both" password="tomcat" roles="tomcat,role1"/>
  <user username="role1" password="tomcat" roles="role1"/>
-->
<user name="tomcat" password="password" roles="admin-gui,manager-gui" />


</tomcat-users>


This will allow you to login to the management web application as tomcat with the password of password
Create a file in you apache configuration (conf.d) directory.
Fedora: /etc/httpd/conf.d/proxy_ajp.conf
Debian: /etc/apache2/conf.d/proxy_ajp.conf


Add this to the file:

<Proxy balancer://cluster>
BalancerMember ajp://localhost:8009 loadfactor=1
BalancerMember ajp://localhost:9009 loadfactor=2
ProxySet lbmethod=bytraffic
</Proxy>
ProxyPass /manager balancer://cluster/manager
ProxyPass /host-manager balancer://cluster/host-manager
ProxyPass /examples balancer://cluster/examples
ProxyPass /docs balancer://cluster/docs

Start apache and tomcat and test. You can test each instance, individually on http://your.servers.address:8080 and 9080. Once you have validated each instance test the webserver itself. should be something like http://your.servers.address/manager If you did it right you should see in your tomcat logs when a session hits an instance:

==> /usr/local/tomcat7-2/logs/localhost_access_log.2014-11-10.txt <==
10.1.10.1 - tomcat [10/Nov/2014:20:52:33 -0500] "GET /manager/html/list HTTP/1.1" 200 15865
10.1.10.1 - - [10/Nov/2014:20:52:33 -0500] "GET /manager/images/asf-logo.gif HTTP/1.1" 304 -
10.1.10.1 - - [10/Nov/2014:20:52:33 -0500] "GET /manager/images/tomcat.gif HTTP/1.1" 304 -
10.1.10.1 - tomcat [10/Nov/2014:20:52:33 -0500] "GET /manager/html/list HTTP/1.1" 200 15865

==> /usr/local/tomcat7-1/logs/localhost_access_log.2014-11-10.txt <==
10.1.10.1 - - [10/Nov/2014:20:52:34 -0500] "GET /manager/images/asf-logo.gif HTTP/1.1" 304 -
10.1.10.1 - - [10/Nov/2014:20:52:34 -0500] "GET /manager/images/tomcat.gif HTTP/1.1" 304 -

==> /usr/local/tomcat7-2/logs/localhost_access_log.2014-11-10.txt <==
10.1.10.1 - - [10/Nov/2014:20:52:36 -0500] "GET /manager/images/asf-logo.gif HTTP/1.1" 304 -
10.1.10.1 - - [10/Nov/2014:20:52:36 -0500] "GET /manager/images/tomcat.gif HTTP/1.1" 304 -

==> /usr/local/tomcat7-1/logs/localhost_access_log.2014-11-10.txt <==
10.1.10.1 - tomcat [10/Nov/2014:20:52:36 -0500] "GET /manager/html/list HTTP/1.1" 200 15865

==> /usr/local/tomcat7-2/logs/localhost_access_log.2014-11-10.txt <==
10.1.10.1 - tomcat [10/Nov/2014:20:52:45 -0500] "GET /manager/html/list HTTP/1.1" 200 15865
10.1.10.1 - - [10/Nov/2014:20:52:45 -0500] "GET /manager/images/asf-logo.gif HTTP/1.1" 304 -
10.1.10.1 - - [10/Nov/2014:20:52:45 -0500] "GET /manager/images/tomcat.gif HTTP/1.1" 304 -


Loadbalanced. 
  This is very rudimentary as it has no session awareness. That my friend, is a 5 minute session for another day.......

No comments:

Post a Comment