Re: Do I need Tomcat and Apache ?

sl@my-rialto wrote:


No, but the computer running GlassFish has to have sufficient horsepower to
handle it. It runs best on a multi-core machine with 2 or more GB RAM. I ran
it quite well on a four-core machine with 4 GB RAM (Linux).

Apache Web Server (httpd - Tomcat is also an Apache project) serves static
content. It's also very powerful for things like proxying, URL management and
a bunch of other things. It is not Java EE.

Apache Tomcat serves HTML also, as well as servlets, JSP, JSF and, with
appropriate JARs, certain other elements of the Java EE alphabet soup. You
can run Tomcat without httpd.

For EJBs, queues, BPEL and certain other heavyweight parts of Java EE you
either need to assemble individual libraries, like Apache OpenEJB, into a
container like Tomcat, or you need a full-blown application server like
GlassFish, JBoss or Apache Geronimo.

I wouldn't start with the big app servers. Since you're new to Java EE,
Tomcat is the easiest to administer while you're learning. You give up EJBs
(at first - OpenEJB cures that) and other, higher-end features, but that lets
you focus on more fundamental Java EE until you gain facility with that part.

I've found the Sun Java EE tutorial helpful:
<http://java.sun.com/javaee/5/docs/tutorial/doc/>


It's a start. What part is confusing you?

Or do you really mean "overwhelming"? Just keep going a little at a time and
you should begin to conquer it.

--
Lew