• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

scea_part_II: What is the purpose of the two web server s?

 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Let us assume we use J2EE technology
(JSP/Servlet/EJB etc.) for FBN travel system
(scea partII).
If we pick weblogic or websphere, each of them
can serve as both of web server and application
server. Normally web servers are only used for
static contents, and application servers are for
dynamic contents (such as JSPs/Servlets).
For FBN system, I do not see much static contents, what is the purpose to use even two web servers for the task. I would say it is better
to cluster all machines as a cluster of application servers--- each of them serves both of static contents and dynamic contents.
Any comments about the deployment?
Thanks in advance!
Chenping Ni
 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
If you personally don't deal with any static content it doesn't necessarily mean there is none.
Every commercial web application has allot of it. Two web hosts are for a purpose of load balancing. Those will
work as a frontfacers for app servers.
 
Chenping Ni
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
All right, I will assume we have some
static content.
Thank you very much Pavel!
Chenping Ni
 
Chenping Ni
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Another choice we have is to
put all JSPs/Servlets on web servers,
and put business logic on the application server.
Enterprise Architect for J2EE technology study
guide (Mark Cade, P. 51 and P. 53)
takes that approach.
Chenping Ni
 
Ranch Hand
Posts: 116
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Another choice we have is to
put all JSPs/Servlets on web servers,
and put business logic on the application server


If you deploy jsps/servlets onto a web server, then that web server needs a servlet engine and will soon be another app server.
Honestly, I don't know where you are going with this..
Web servers are placed in front of appserver for several reasons:
1. You can place the web server outside the firewall, and route all requests to your app server that reside inside the firewall
2. You can place one or more webservers for load-balancing and/or fail-over support
You don't need to have application content on the web server, but will serve as a proxy into your app server.
Rama
[ February 25, 2003: Message edited by: Rama Raghavan ]
 
Don't get me started about those stupid light bulbs.
reply
    Bookmark Topic Watch Topic
  • New Topic