I find Apache useful for the following things: - Content-Expiration, Cache-Control, and max-age (mod_expires and mod_headers) - Compression (mod_deflate)
A decent article that goes into more detail: http://www.mnot.net/cache_docs/ Those two things can have a drastic impact on the performance of the midtier. There are also those applications that have more holes that swiss cheese. Using Apache in front of Tomcat let's you manipulate/validate the querystring in a way to mitigate issues inherent in the application. The other place I find it useful is with SSO related tasks, especially with legacy SSO solutions. That agent has to run somewhere. mod_jk has issues on Solaris, but they can be worked around through the configuration. There is also mod_proxy_ajp, which is now part of mod_proxy that can be used in lieu of mod_jk. I have not used mod_proxy_ajp in a production environment though, so I can't speak to it's reliability. I've not had major issues with mod_jk on Linux. Axton Grams On Fri, Nov 11, 2011 at 2:19 AM, John Baker <[email protected]> wrote: > James > > I have no idea why you are installing an Apache front end. it's pointless for > almost all deployments of Mid Tier and the mod_jk connector is no longer > reliable. > > Installing Mid Tier is easy. 1. Unpack Tomcat. 2. Set LD_LIBRARY_PATH to > tomcat/webapps/arsys/WEB-INF/lib. 3. Place Mid Tier war file in webapps, > called arsys.war. 4. Start Tomcat. > > > John > -- > SSO Plugin: Bringing BMC products together > http://www.javasystemsolutions.com/jss/ssoplugin > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
