Win a copy of Think Java: How to Think Like a Computer Scientist this week in the Java in General forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Do we need to download both iis and tomcat to run jsp files

 
anu rani
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Do we need to download both iis and tomcat to run jsp files
 
Muhammad Saifuddin
Ranch Hand
Posts: 1324
Android Java Windows
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Welcome to JavaRanch anu rani,

Absouletly not. Internet Information Server (IIS) has nothing to do with JSP files. So no need to download both, just download Tomcat and deploy your project. Your files shall work smooth, hopefully

regarding Apache Tomcat there is link which is helpful to you.
Jakarta Tomcat for Servlet and JSP Development
[ August 29, 2006: Message edited by: Saif Uddin ]
 
Cameron Wallace McKenzie
author and cow tipper
Saloon Keeper
Posts: 4968
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Just Tomcat.

In production you often put a web server in front of your middle tier, which would be Tomcat. You can use IIS, but you could just as well use Apache, another open source project.
 
William Brogden
Author and all-around good cowpoke
Rancher
Posts: 13061
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I know of no good reason to not use Tomcat as a "production" server. Especially if your site uses JSP and/or servlets extensively, the extra steps involved in transferring request and response between IIS and Tomcat must surely be time consuming.
When I moved a client's app from a Win3k-IIS-tomcat configuration to pure tomcat they reported better response times.
As far as I am concerned the "dont use Tomcat for production" is just another annoying Java myth.
Bill
 
Jeroen T Wenting
Ranch Hand
Posts: 1847
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Not so much a myth as good advise from the past that's become meaningless over time.
Early Tomcat versions were quite slow compared to the commercial servers, especially when serving static content.
Thus it was almost always better to host static content at say Apache and link that to Tomcat for dynamic content (or another servlet engine).
 
Ben Souther
Sheriff
Posts: 13411
Firefox Browser Redhat VI Editor
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Jeroen T Wenting:
Not so much a myth as good advise from the past that's become meaningless over time.


Agreed.

These days, depending on the nature of your app, Tomcat as a standalone can be faster and more efficent that the combination of webserver, connector, and app server.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic