• Post Reply Bookmark Topic Watch Topic
  • New Topic

allocating client interfaces  RSS feed

 
Douglas Kent
Ranch Hand
Posts: 171
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
I am seeking advice on whether it is a good idea to attempt to set up something like the following:
deploy all JSP files to a web server (in this case iPlanet), with all beans (EJB and non-EJB) deployed on a different machine with an app server (in this case BEA WebLogic). We have a third machine to serve as the DB (Oracle). My concern is this: is it worth the extra trouble of having the JSP beans have to use RMI to connect to the beans on the app server? The advantage is that the web server handles all the user interaction, allowing the app server to concentrate its resources on business logic and database interaction.
Thanks!
 
Thomas Paul
mister krabs
Ranch Hand
Posts: 13974
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I personally would not set up an environment that forces JSPs to use RMI.
 
Kyle Brown
author
Ranch Hand
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Co-locating your JSPs and EJBs in the same process (JVM) is almost always a better solution. The overhead of RMI serialization/deserialization is horrific.
Kyle
 
Thomas Paul
mister krabs
Ranch Hand
Posts: 13974
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Yes, locating your JSPs in your WebLogic server makes a lot more sense. Use your iPlanet server to serve your static pages and have all the JSP/Servlet requests pushed through to the WebLogic server.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!