<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Am 06.02.2012 09:29, schrieb Michael Wechner:
    <blockquote cite="mid:4F2F8F64.2060605@wyona.com" type="cite">
      <meta content="text/html; charset=ISO-8859-1"
        http-equiv="Content-Type">
      Am 18.01.12 17:46, schrieb simon:
      <blockquote cite="mid:4F16F761.5020704@333.ch" type="cite">
        <meta content="text/html; charset=ISO-8859-1"
          http-equiv="Content-Type">
        Am 18.01.2012 10:32, schrieb Michael Wechner:
        <blockquote cite="mid:4F169196.4040204@wyona.com" type="cite">
          <meta content="text/html; charset=ISO-8859-1"
            http-equiv="Content-Type">
          Hi Simon<br>
          <br>
          I can confirm what Balz is saying, whereas I would emphasize
          that it is mostly about flexibility.<br>
          <br>
          You can find some examples under "Deployment" of the
          documentation:<br>
          <br>
          <a moz-do-not-send="true" class="moz-txt-link-freetext"
            href="http://www.yanel.org/en/documentation/index.html">http://www.yanel.org/en/documentation/index.html</a><br>
        </blockquote>
        i was just reading <a moz-do-not-send="true"
          class="moz-txt-link-freetext"
href="http://www.yanel.org/en/documentation/how-to-add-ssl-to-apache-httpd.html">http://www.yanel.org/en/documentation/how-to-add-ssl-to-apache-httpd.html</a>
        and it seems to be a bit outdated , at least if you use an
        recent linux distro where apache above 2.2.13.  is bundled.<br>
        then  just enter<br>
        <br>
        apt-get install apache2<br>
        <br>
        sudo a2enmod proxy<br>
        sudo a2enmod proxy_http<br>
      </blockquote>
      <br>
      I have update now<br>
      <br>
      <a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.yanel.org/en/documentation/deployment-with-a-reverse-proxy.html">http://www.yanel.org/en/documentation/deployment-with-a-reverse-proxy.html</a><br>
      <br>
      accordingly.<br>
    </blockquote>
    thanks very much.<br>
    <br>
    simon<br>
    <blockquote cite="mid:4F2F8F64.2060605@wyona.com" type="cite"> <br>
      Thanks<br>
      <br>
      Michael<br>
      <blockquote cite="mid:4F16F761.5020704@333.ch" type="cite"> <br>
        HTH<br>
        simon<br>
        <br>
        <blockquote cite="mid:4F169196.4040204@wyona.com" type="cite"> <br>
          whereas I just realize that we need to replace the svn links
          by git.<br>
          <br>
          HTH<br>
          <br>
          Michael<br>
          <br>
          Am 18.01.12 10:19, schrieb basZero:
          <blockquote
cite="mid:CAOXzDSGxJs+6L-8+th45HKn5x61vQhiP+MeJpCTBs58x6Gtu=A@mail.gmail.com"
            type="cite">Hi Simon,
            <div><br>
            </div>
            <div>in larger enterprise setups there is always a web
              server in front of the application server (tomcat,
              glassfish, etc.).</div>
            <div>there are many advantages for having a web server in
              front of the app server:</div>
            <div>- you can scale better (with plugins like mod_jk or
              alike you can distribute the load over N application
              servers. Of course, the plugin must support session
              stickyness, so that request with the same session cookie
              gets forwarded to the same app server.</div>
            <div>- you can serve static content from the web server.
              this way you have much less "noise" on the app server. Of
              course: web server must have access to the content, so the
              deployment model might look different, if web and
              appserver are on physically different machines</div>
            <div>- you can easily switch to a static maintenance page:
              you configure the web server to show a certain page.
              during this time, you can modify the app servers in the
              back end. if done, you can go back to the normal
              configuration where requests are routed to the app servers</div>
            <div>- for highly secure applications, it's probably a must
              to introduce a web server, as you can much better protect
              your app server from unwanted requests (see for instance
              "perimeter authentication")</div>
            <div><br>
            </div>
            <div>downside of it is:</div>
            <div>- you have more infrastructure to maintain</div>
            <div>- more complex monitoring setup</div>
            <div>- more expensive</div>
            <div>- more complex support demand (if something goes wrong,
              you have to analyze more)</div>
            <div><br>
            </div>
            <div>cheers</div>
            <div>balz</div>
            <div><br>
            </div>
            <div><br>
            </div>
            <div><br>
              <div title="signature"> </div>
              <div class="gmail_quote">On Wed, Jan 18, 2012 at 10:10 AM,
                simon <span dir="ltr"><<a moz-do-not-send="true"
                    href="mailto:simon@333.ch">simon@333.ch</a>></span>
                wrote:<br>
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">hi
                  all<br>
                  <br>
                  just wondering why yanel resp. tomcat is mostly
                  deployed behind an apache?<br>
                  what's the reason and does someone has experience in
                  using the tomcat without an apache web server in
                  front?<br>
                  <br>
                  cheers<span class="HOEnZb"><font color="#888888"><br>
                      simon<br>
                      -- <br>
                      Yanel-development mailing list <a
                        moz-do-not-send="true"
                        href="mailto:Yanel-development@wyona.com"
                        target="_blank">Yanel-development@wyona.com</a><br>
                      <a moz-do-not-send="true"
                        href="http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development"
                        target="_blank">http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development</a><br>
                    </font></span></blockquote>
              </div>
              <br>
            </div>
            <br>
            <fieldset class="mimeAttachmentHeader"></fieldset>
            <br>
          </blockquote>
          <br>
          <br>
          <fieldset class="mimeAttachmentHeader"></fieldset>
          <br>
        </blockquote>
        <br>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
      </blockquote>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
    </blockquote>
    <br>
  </body>
</html>