Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...

please let me know the configuration or architecture how
tomcat used. give me a layman example

Answer Posted / n.m.balaji

The Architecture of Tomcat


Tomcat 4 is a complete rewrite of its ancestors. At the core
of this rewrite is the Catalina servlet engine, which acts
as the top-level container for all Tomcat instances.


With this rewrite of Tomcat comes an entirely new
architecture composed of a grouping of application
containers, each with a specific role. The sum of all of
these containers makes up an instance of a Catalina engine.


The following code snippet provides an XML representation of
the relationships between the different Tomcat containers:


<Server>
<Service>
<Connector />
<Engine>
<Host>
<Context>
</Context>
</Host>
</Engine>
</Service>
</Server>


This instance can be broken down into a set of containers
including a server, a service, a connector, an engine, a
host, and a context. By default, each of these containers is
configured using the server.xml file, which we describe
later in more detail.

The Server

The first container element referenced in this snippet is
the <Server> element. It represents the entire Catalina
servlet engine and is used as a top-level element for a
single Tomcat instance. The <Server> element may contain one
or more <Service> containers.

The Service

The next container element is the <Service> element, which
holds a collection of one or more <Connector> elements that
share a single <Engine> element. N-number of <Service>
elements may be nested inside a single <Server> element.

The Connector

The next type of element is the <Connector> element, which
defines the class that does the actual handling requests and
responses to and from a calling client application.

The Engine

The third container element is the <Engine> element. Each
defined <Service> can have only one <Engine> element, and
this single <Engine> component handles all requests received
by all of the defined <Connector> components defined by a
parent service.

The Host

The <Host> element defines the virtual hosts that are
contained in each instance of a Catalina <Engine>. Each
<Host> can be a parent to one or more Web applications, with
each being represented by a <Context> component.

The Context

The <Context> element is the most commonly used container in
a Tomcat instance. Each <Context> element represents an
individual Web application that is running within a defined
<Host>. There is no limit to the number of contexts that can
be defined within a <Host>.

Is This Answer Correct ?    3 Yes 0 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

What is the difference between apache tomcat and tomcat?

790


How do I uninstall tomcat on mac?

786


Why do I need apache tomcat?

825


what is the output of select * from tab?

800


Is tomcat a java application?

794


What is context path in tomcat?

749


How to know your apache tomcat version?

796


Does tomcat support jms?

749


What is tomcat web xml?

771


Name some tomcat features?

805


What is difference between get and post in rest?

805


How many requests per second does facebook handle?

814


What is the highest searched on google?

746


How many connections can a web server handle?

753


Why is catalina called tomcat?

797