Need advice for Web Server architecture

I am currently working on the web server implementation for a aircraft-based LAN network. Not developing Web applications myself, I am supposed to provide to the app developpers a web server accepting the greatest possible scope of web technologies.
The choice I have to make (imposed by the client) is, based on a RedHat Linux OS, between a Tomcat 4.1.18 standalone Web server and an Apache 2.0.44 HTTP server with a Tomcat module to allow for JSP/servlet technologies. To add some complexity, Tomcat will come as part of Sun's J2EE App server.
My questions are:
-What would be the advantage of having an Apache HTTP Server, i.e what does an Apache HTTP Server provide that a Tomcat standalone doesn't?
-I know (from a previous post) that it is possible to have Tomcat as an Apache module for user-transparency, but does anyone know if it is possible when Tomcat comes embeded in J2EE?
Thank you in advance
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Apache is a web server. It serves up data for the web, like html pages, jpegs, scripts, stylesheets and so on.

TomCat is an application server (better said Framework since it itself does not do application processing but supports those things plugged into it like JavaBeans). It normally recieves a request from a web server, executes an application specific function, and returns data back through Apache to the browser.

"..that it is possible to have Tomcat as an Apache module for user-transparency."

Don't understand. An Apache module is something which gets loaded into an Apache process at start up, not every time it is required. Saves time. The Apache TomCat module (aka JServ and a host of other names) takes an http request, encodes it, and connects to the TomCat server. It passes the request data, and receives the processed data from TomCat. It passes this onto Apache (who passes it to the browser) and closes the connection*


*simplistic explaination. There are a whole host of things which take place in order to optimise the process.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Apache Web Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.