This week's book giveaway is in the Agile and Other Processes forum.
We're giving away four copies of The Little Book of Impediments (e-book only) and have Tom Perry on-line!
See this thread for details.
Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Servers

 
Arathi Raj
Ranch Hand
Posts: 90
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
Can anbody tell the diffrence between web server and application server. If we have to run a servlet or JSP does web server and application server should contain servlets and jsp engines. Do clarify me doubt.
Thanks
 
Dani Mazzuca
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
web-server: supports servlets and JSP

application server: supports not only Servlets and JSP, but also EJB and J2EE.

Dani
 
Jessica Sant
Sheriff
Posts: 4313
Android IntelliJ IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
actually Dani, that's close but not quite right:
a web server serves up static content: HTML, images, that kind of thing. It usually provides stuff like security, administration and what not too. But in its most elementary form, a webserver supports HTTP.
an application server serves dynamic content produced by Java Servlets, JSPs, and EJBs. Fully J2EE compliant application servers (BEA Weblogic, IBM WebSphere, etc.) can handle all 3, something like Tomcat only supports JSPs and Servlets and is called a servlet container or a servlet engine.
Hope that helps!
[ August 02, 2003: Message edited by: Jessica Sant ]
 
Roger Chung-Wee
Ranch Hand
Posts: 1683
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The servet container can be considered part of the web server. In my department, developers set up Tomcat as standalone, ie Tomcat's integral web server and servlet container serve up both the static and dynamic stuff for development. For production, the only container we use is WebLogic which is out-of-process (as a separate process) with the web server, so the web server loads a plug-in to communicate with WebLogic.
You can also have the servlet container running in-process with the web server. The requires the web server to load a JVM to run the servlet container (which therefore runs in the same address space as the web server). This gives the best performance but my understanding is that this isn't as stable as running the web server and servlet container in separate processes.
In both the latter modes, the web server handles to static stuff and the servlet container the dynamic stuff.
[ August 03, 2003: Message edited by: Roger Chung-Wee ]
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic