Configuring Tomcat 7 with Eclipse Juno


1)First download  the latest Eclipse IDE for Java EE Developers and Tomcat 7
Note:You just need to extract both Eclipse and Apache Tomcat
2)Start Eclipse! The first thing that Eclipse will do is ask you to create a new Workspace.
Select a Folder which you want to be your workspace.All your project will be created here
3)Make sure you are in Java EE perspective :Go to Window->Open Perspective->Java EE 
4)Add Server:In“Servers” area, right click -> New -> Server.

5)Here you will see list of servers that can be configured in the installed Eclipse IDE version. You will find Tomcat v7.0 Server under “Apache” folder as shown below.

Select “Tomcat v7.0 Server” and click Next.
6)Configuring Apache Tomcat installation location

7)Select the Tomcat Root folder which has bin folder and click Next.

There are no resources to be configured and hence click Finish.
8)The configured Apache Tomcat Server will be displayed in the “Servers” view.
Start Server:It is easy to manage the server instance. Right-click on the server and start and stop it to ensure its proper working.


9)Test your installation
After starting the Tomcat, open browser and type http://localhost:8080. You should see the Apache Tomcat home page as shown below.

Comments

  1. Sandeep1 April 2013 at 21:56

    sharing some tomcat interview questions with fellow developers

    ReplyDelete
  2. Akaas Developer16 May 2013 at 21:31

    Here you can find lots of:
    Tomcat Interview Questions and Answers
    Web Servers or Services Interview Questions and Answers

    Regards,
    Akaas Developer
    questions-interviews.com

    ReplyDelete
  3. Unknown26 April 2014 at 01:04

    Apr 26, 2014 1:22:17 PM org.apache.catalina.startup.HostConfig deployDirectory
    INFO: Deploying web application directory C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\examples
    Apr 26, 2014 1:22:17 PM org.apache.catalina.core.ApplicationContext log
    INFO: ContextListener: contextInitialized()
    Apr 26, 2014 1:22:17 PM org.apache.catalina.core.ApplicationContext log
    INFO: SessionListener: contextInitialized()
    Apr 26, 2014 1:22:17 PM org.apache.catalina.core.ApplicationContext log
    INFO: ContextListener: attributeAdded('org.apache.jasper.compiler.TldLocationsCache', 'org.apache.jasper.compiler.TldLocationsCache@19c29f4')
    Apr 26, 2014 1:22:17 PM org.apache.catalina.startup.HostConfig deployDirectory
    INFO: Deploying web application directory C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\host-manager
    Apr 26, 2014 1:22:17 PM org.apache.catalina.startup.HostConfig deployDirectory
    INFO: Deploying web application directory C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\manager
    Apr 26, 2014 1:22:17 PM org.apache.catalina.startup.HostConfig deployDirectory
    INFO: Deploying web application directory C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\ROOT
    Apr 26, 2014 1:22:17 PM org.apache.catalina.startup.HostConfig deployDirectory
    INFO: Deploying web application directory C:\Program Files\Apache Software Foundation\Tomcat 7.0\webapps\subbu1
    Apr 26, 2014 1:22:17 PM org.apache.coyote.AbstractProtocol start
    INFO: Starting ProtocolHandler ["http-bio-8080"]
    Apr 26, 2014 1:22:17 PM org.apache.coyote.AbstractProtocol start
    INFO: Starting ProtocolHandler ["ajp-bio-8009"]
    Apr 26, 2014 1:22:17 PM org.apache.catalina.startup.Catalina start
    INFO: Server startup in 732 ms
    Apr 26, 2014 1:22:17 PM org.apache.catalina.core.StandardServer await
    SEVERE: StandardServer.await: create[localhost:8005]:
    java.net.BindException: Address already in use: JVM_Bind
    at java.net.DualStackPlainSocketImpl.bind0(Native Method)
    at java.net.DualStackPlainSocketImpl.socketBind(Unknown Source)
    at java.net.AbstractPlainSocketImpl.bind(Unknown Source)
    at java.net.PlainSocketImpl.bind(Unknown Source)
    at java.net.ServerSocket.bind(Unknown Source)
    at java.net.ServerSocket.(Unknown Source)
    at org.apache.catalina.core.StandardServer.await(StandardServer.java:427)
    at org.apache.catalina.startup.Catalina.await(Catalina.java:766)
    at org.apache.catalina.startup.Catalina.start(Catalina.java:712)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:322)
    at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:456)

    Apr 26, 2014 1:22:17 PM org.apache.coyote.AbstractProtocol pause
    INFO: Pausing ProtocolHandler ["http-bio-8080"]
    Apr 26, 2014 1:22:18 PM org.apache.coyote.AbstractProtocol pause
    INFO: Pausing ProtocolHandler ["ajp-bio-8009"]
    Apr 26, 2014 1:22:19 PM org.apache.catalina.core.StandardService stopInternal
    INFO: Stopping service Catalina
    Apr 26, 2014 1:22:19 PM org.apache.catalina.core.ApplicationContext log
    INFO: SessionListener: contextDestroyed()
    Apr 26, 2014 1:22:19 PM org.apache.catalina.core.ApplicationContext log
    INFO: ContextListener: contextDestroyed()
    Apr 26, 2014 1:22:19 PM org.apache.coyote.AbstractProtocol stop
    INFO: Stopping ProtocolHandler ["http-bio-8080"]
    Apr 26, 2014 1:22:20 PM org.apache.coyote.AbstractProtocol stop
    INFO: Stopping ProtocolHandler ["ajp-bio-8009"]
    Apr 26, 2014 1:22:21 PM org.apache.coyote.AbstractProtocol destroy
    INFO: Destroying ProtocolHandler ["http-bio-8080"]
    Apr 26, 2014 1:22:21 PM org.apache.coyote.AbstractProtocol destroy
    INFO: Destroying ProtocolHandler ["ajp-bio-8009"]

    ReplyDelete

Post a Comment

Popular posts from this blog

Servlet Advantages and Disadvantages

Servlet Advantage 1.      Servlets provide a way to generate dynamic documents that is both easier to write and faster to run. 2.      provide all the powerfull features of JAVA, such as Exception handling and garbage collection. 3.      Servlet enables easy portability across Web Servers. 4.      Servlet can communicate with different servlet and servers. 5.      Since all web applications are stateless protocol, servlet uses its own API to maintain  session Servlet Disadvantage 1.      Designing in servlet is difficult and slows down the application. 2.      Writing complex business logic makes the application difficult to understand. 3.      You need a Java Runtime Environment on the server to run servlets. CGI is a completely language independent protocol, so you can write CGIs in whatever languages you have available (including Java if you want to). Advantages over CGI The advantages of using Servlets are their fast performance and ease of use combined
Read more

The Deployment Descriptor: web.xml

Image
Before I explain what a deployment descriptor is, we should first understand the web application directory structure WEB APPLICATION DIRECTORY STRUCTURE: A Web application contains a structure hierarchy of directories and files in a standard layout. Such a hierarchy can be accessed in its "unpacked" form, where each directory and file exists in the filesystem separately(This  format is more useful during development) , or in its "packed" WAR file(This format is used  when you distribute your application to be installed) . Any Web Application that is to be deployed in Tomcat has to conform to this directory structure. The format of the structure can be seen in the figure below: Web Application Directory Structure Application Root Directory   - This is the root directory of the Web Application. The name of this directory is named by the developer - for example the default context we created for this module was called "stud
Read more

Session Management

What is a session? A session is pretty much what it sounds, when a user makes a page request to the server, the server creates a temporary session to identify that user. So when that same user goes to another page on that site, the server identifies that user. So a session is a small and temporary unique connection between a server and the user enabling it to identify that user across multiple page requests or visits to that site. Why should a session be maintained? When there is a series of continuous request and response from a same client to a server, the server cannot identify from which client it is getting requests. Because HTTP is a stateless protocol. When there is a need to maintain the conversational state, session tracking is needed. For example, in a shopping cart application a client keeps on adding items into his cart using multiple requests. When every request is made, the server should identify in which client’s cart the item is to be added. So in this sc
Read more