Re: (Tomcat + JBoss) or (Apache + Tomcat + JBoss) ?
Is there anyone that installed (Apache + Tomcat + JBoss) combination all together? What are the advantages of Using Apache with Tomcat-JBoss combination or is Tomcat enough for complete web content serving? Should I run Apache with Tomcat + JBoss in a separate JVM? Tomcat + JBoss will give you a complete JEE server, with web interface. Apache can help you off-load serving static stuff from your Tomcat. The dynamic part: JSP, Servlets (EJB and other JBoss mechanisms) will not be served by Apache. Nix.
RE: (Tomcat + JBoss) or (Apache + Tomcat + JBoss) ?
Is there anyone that installed (Apache + Tomcat + JBoss) combination all together? What are the advantages of Using Apache with Tomcat-JBoss combination or is Tomcat enough for complete web content serving? Should I run Apache with Tomcat + JBoss in a separate JVM? Tomcat + JBoss will give you a complete JEE server, with web interface. Apache can help you off-load serving static stuff from your Tomcat. The dynamic part: JSP, Servlets (EJB and other JBoss mechanisms) will not be served by Apache. It's ok. But I am just wondering that; Is it helpful that using Apache with (Tomcat + JBoss) combination? I mean serving the non-dynamic contents of a website through Apache instead of using the Tomcat's internal web server. And additionaly using the EJB container of JBoss and Web Container of Tomcat for non-static parts. Thus using all three products together on a single website? Any idea? Murat.
Re: (Tomcat + JBoss) or (Apache + Tomcat + JBoss) ?
Tomcat + JBoss will give you a complete JEE server, with web interface. Apache can help you off-load serving static stuff from your Tomcat. The dynamic part: JSP, Servlets (EJB and other JBoss mechanisms) will not be served by Apache. It's ok. But I am just wondering that; Is it helpful that using Apache with (Tomcat + JBoss) combination? Functionality of Apache's HTTP/1.1 module and Tomcat's HTTP/1.1 is the same. The only difference is the performance of serving static objects. I mean serving the non-dynamic contents of a website through Apache instead of using the Tomcat's internal web server. If you can separate your static content from the dynamic parts, you can easily make such an arrangement. If not, then the only hope for you is mod_jk (mod_jk2 is still in testing). And additionaly using the EJB container of JBoss and Web Container of Tomcat for non-static parts. Thus using all three products together on a single website? The answer to this question largely depends on your website organization and purpose. It could be that you can run both Apache and Tomcat, side by side, without any integration. Apache would listen on TCP:80 and Tomcat on TCP:8080. The presentations on both servers would have explicit links, like this: http://www.domain.com:80/path/to/link.html http://www.doamin.com:8080/another/path/to/link.jsp If this looks ugly, you can try to integrate Tomcat under Apache, using mod_jk, mod_jk2 or mod_webapp. If you want Apache to serve static contenet belonging to your web application, then mod_jk is the way. Nix.
RE: (Tomcat + JBoss) or (Apache + Tomcat + JBoss) ?
Thank you for your answer. Can the JBoss EJB container be easily added to Tomcat + Apache (binded together with mod_jkxx) couple? if so how can we build-up for running all three..? As far as I know, Tomcat_JBoss couple bundled with together for enterprise usage. Can I integrate the Tomcat unit of this couple with Apache via mod_jkxx module? Thanks.. Murat. -Original Message- From: Nikola Milutinovic [mailto:[EMAIL PROTECTED]] Sent: Thursday, July 04, 2002 11:46 AM To: Tomcat Users List Subject: Re: (Tomcat + JBoss) or (Apache + Tomcat + JBoss) ? Tomcat + JBoss will give you a complete JEE server, with web interface. Apache can help you off-load serving static stuff from your Tomcat. The dynamic part: JSP, Servlets (EJB and other JBoss mechanisms) will not be served by Apache. It's ok. But I am just wondering that; Is it helpful that using Apache with (Tomcat + JBoss) combination? Functionality of Apache's HTTP/1.1 module and Tomcat's HTTP/1.1 is the same. The only difference is the performance of serving static objects. I mean serving the non-dynamic contents of a website through Apache instead of using the Tomcat's internal web server. If you can separate your static content from the dynamic parts, you can easily make such an arrangement. If not, then the only hope for you is mod_jk (mod_jk2 is still in testing). And additionaly using the EJB container of JBoss and Web Container of Tomcat for non-static parts. Thus using all three products together on a single website? The answer to this question largely depends on your website organization and purpose. It could be that you can run both Apache and Tomcat, side by side, without any integration. Apache would listen on TCP:80 and Tomcat on TCP:8080. The presentations on both servers would have explicit links, like this: http://www.domain.com:80/path/to/link.html http://www.doamin.com:8080/another/path/to/link.jsp If this looks ugly, you can try to integrate Tomcat under Apache, using mod_jk, mod_jk2 or mod_webapp. If you want Apache to serve static contenet belonging to your web application, then mod_jk is the way. Nix.
