[Yanel-dev] deployment
Michael Wechner
michael.wechner at wyona.com
Mon Feb 6 09:29:24 CET 2012
Am 18.01.12 17:46, schrieb simon:
> Am 18.01.2012 10:32, schrieb Michael Wechner:
>> Hi Simon
>>
>> I can confirm what Balz is saying, whereas I would emphasize that it
>> is mostly about flexibility.
>>
>> You can find some examples under "Deployment" of the documentation:
>>
>> http://www.yanel.org/en/documentation/index.html
> i was just reading
> http://www.yanel.org/en/documentation/how-to-add-ssl-to-apache-httpd.html
> 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.
> then just enter
>
> apt-get install apache2
>
> sudo a2enmod proxy
> sudo a2enmod proxy_http
I have update now
http://www.yanel.org/en/documentation/deployment-with-a-reverse-proxy.html
accordingly.
Thanks
Michael
>
> HTH
> simon
>
>>
>> whereas I just realize that we need to replace the svn links by git.
>>
>> HTH
>>
>> Michael
>>
>> Am 18.01.12 10:19, schrieb basZero:
>>> Hi Simon,
>>>
>>> in larger enterprise setups there is always a web server in front of
>>> the application server (tomcat, glassfish, etc.).
>>> there are many advantages for having a web server in front of the
>>> app server:
>>> - 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.
>>> - 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
>>> - 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
>>> - 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")
>>>
>>> downside of it is:
>>> - you have more infrastructure to maintain
>>> - more complex monitoring setup
>>> - more expensive
>>> - more complex support demand (if something goes wrong, you have to
>>> analyze more)
>>>
>>> cheers
>>> balz
>>>
>>>
>>>
>>> On Wed, Jan 18, 2012 at 10:10 AM, simon <simon at 333.ch
>>> <mailto:simon at 333.ch>> wrote:
>>>
>>> hi all
>>>
>>> just wondering why yanel resp. tomcat is mostly deployed behind
>>> an apache?
>>> what's the reason and does someone has experience in using the
>>> tomcat without an apache web server in front?
>>>
>>> cheers
>>> simon
>>> --
>>> Yanel-development mailing list Yanel-development at wyona.com
>>> <mailto:Yanel-development at wyona.com>
>>> http://lists.wyona.org/cgi-bin/mailman/listinfo/yanel-development
>>>
>>>
>>>
>>>
>>
>>
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wyona.org/pipermail/yanel-development/attachments/20120206/5f7b93e2/attachment.html>
More information about the Yanel-development
mailing list