what makes j2ee suitable for distributed multitiered applications?

- the j2ee platform uses a multitiered distributed application model. application

logic is divided into components according to function, and the various
application components that make up a j2ee application are installed on different
machines depending on the tier in the multitiered j2ee environment to which the
application component belongs. the j2ee application parts are:

• client-tier components run on the client machine.

• web-tier components run on the j2ee server.

• business-tier components run on the j2ee server.

• enterprise information system (eis)-tier software runs on the eis server.

what is j2ee? - j2ee is an environment for developing and deploying enterprise

applications. the j2ee platform consists of a set of services, application
programming interfaces (apis), and protocols that provide the functionality for
developing multitiered, web-based applications.
what are the components of j2ee application?
- a j2ee component is a self-contained functional software unit that is assembled
into a j2ee application with its related classes and files and communicates with
other components. the j2ee specification defines the following j2ee components:
application clients and applets are client components.
java servlet and javaserver pages technology components are web
components.
enterprise javabeans components (enterprise beans) are business components.
resource adapter components provided by eis and tool vendors.
what do enterprise javabeans components contain? - enterprise javabeans
components contains business code, which is logic
that solves or meets the needs of a particular business domain such as banking,
retail, or finance, is handled by enterprise beans running in the business tier. all
the business code is contained inside an enterprise bean which receives data from
client programs, processes it (if necessary), and sends it to the enterprise
information system tier for storage. an enterprise bean also retrieves data from
storage, processes it (if necessary), and sends it back to the client program.
is j2ee application only a web-based? - no, it depends on type of application that
client wants. a j2ee application can be web-based or non-web-based. if an
application client executes on the client machine, it is a non-web-based j2ee
application. the j2ee application can provide a way for users to handle tasks such
as j2ee system or application administration. it typically has a graphical user
interface created from swing or awt apis, or a command-line interface. when user
 request, it can open an http connection to establish communication with a servlet
running in the web tier.
are javabeans j2ee components? - no. javabeans components are not considered
j2ee components by the j2ee specification. they are written to manage the data
flow between an application client or applet and components running on the j2ee
server or between server components and a database. javabeans components
written for the j2ee platform have instance variables and get and set methods for
accessing the data in the instance variables. javabeans components used in this
way are typically simple in design and implementation, but should conform to the
naming and design conventions outlined in the javabeans component architecture.
is html page a web component? - no. static html pages and applets are bundled with
web components during application assembly, but are not considered web
components by the j2ee specification. even the server-side utility classes are not
considered web components, either.
what can be considered as a web component? - j2ee web components can be either
servlets or jsp pages. servlets are java programming language classes that
dynamically process requests and construct responses. jsp pages are text-based
documents that execute as servlets but allow a more natural approach to creating
static content.
what is the container? - containers are the interface between a component and the
low-level platform specific functionality that supports the component. before a
web, enterprise bean, or application client component can be executed, it must be
assembled into a j2ee application and deployed into its container.
what are container services? - a container is a runtime support of a system-level
entity. containers provide components with services such as lifecycle
management, security, deployment, and threading.
what is the web container? - servlet and jsp containers are collectively referred to as
web containers. it manages the execution of jsp page and servlet components for
j2ee applications. web components and their container run on the j2ee server.
what is enterprise javabeans (ejb) container? - it manages the execution of
enterprise beans for j2ee applications.
enterprise beans and their container run on the j2ee server.
what is applet container? - imanages the execution of applets. consists of a web
browser and java plugin running on the client together.
how do we package j2ee components? - j2ee components are packaged separately
and bundled into a j2ee application for deployment. each component, its related
files such as gif and html files or server-side utility classes, and a deployment
descriptor are assembled into a module and added to the j2ee application. a j2ee
application is composed of one or more enterprise bean,web, or application client
component modules. the final enterprise solution can use one j2ee application or
 be made up of two or more j2ee applications, depending on design requirements.
a j2ee application and each of its modules has its own deployment descriptor. a
deployment descriptor is an xml document with an .xml extension that describes a
component’s deployment settings.
what is a thin client? - a thin client is a lightweight interface to the application that
does not have such operations like query databases, execute complex business
rules, or connect to legacy applications.
what are types of j2ee clients? - following are the types of j2ee clients:

• applets

• application clients

• java web start-enabled rich clients, powered by java web start technology.

• wireless clients, based on mobile information device profile (midp)

technology.
what is deployment descriptor? - a deployment descriptor is an extensible markup
language (xml) text-based file with an .xml extension that describes a
component’s deployment settings. a j2ee application and each of its modules has
its own deployment descriptor. for example, an enterprise bean module
deployment descriptor declares transaction attributes and security authorizations
for an enterprise bean. because deployment descriptor information is declarative,
it can be changed without modifying the bean source code. at run time, the j2ee
server reads the deployment descriptor and acts upon the component accordingly.
what is the ear file? - an ear file is a standard jar file with an .ear extension, named
from enterprise archive file. a j2ee application with all of its modules is delivered
in ear file.
what is jta and jts? - jta is the abbreviation for the java transaction api. jts is the
abbreviation for the jave transaction service. jta provides a standard interface and
allows you to demarcate transactions in a manner that is independent of the
transaction manager implementation. the j2ee sdk implements the transaction
manager with jts. but your code doesn’t call the jts methods directly. instead, it
invokes the jta methods, which then call the lower-level jts routines. therefore, jta
is a high level transaction interface that your application uses to control
transaction. and jts is a low level transaction interface and ejb uses behind the
scenes (client code doesn’t directly interact with jts. it is based on object
transaction service(ots) which is part of corba.
what is jaxp? - jaxp stands for java api for xml. xml is a language for representing
and describing text-based data which can be read and handled by any program or
tool that uses xml apis. it provides standard services to determine the type of an
arbitrary piece of data, encapsulate access to it, discover the operations available
on it, and create the appropriate javabeans component to perform those
 operations.
what is j2ee connector? - the j2ee connector api is used by j2ee tools vendors and
system integrators to create resource adapters that support access to enterprise
information systems that can be plugged into any j2ee product. each type of
database or eis has a different resource adapter. note: a resource adapter is a
software component that allows j2ee application components to access and
interact with the underlying resource manager. because a resource adapter is
specific to its resource manager, there is typically a different resource adapter for
each type of database or enterprise information system.
what is jaap? - the java authentication and authorization service (jaas) provides a
way for a j2ee application to authenticate and authorize a specific user or group of
users to run it. it is a standard pluggable authentication module (pam) framework
that extends the java 2 platform security architecture to support user-based
authorization.
what is java naming and directory service? - the jndi provides naming and
directory functionality. it provides applications with methods for performing
standard directory operations, such as associating attributes with objects and
searching for objects using their attributes. using jndi, a j2ee application can store
and retrieve any type of named java object. because jndi is independent of any
specific implementations, applications can use jndi to access multiple naming and
directory services, including existing naming and
directory services such as ldap, nds, dns, and nis.
what is struts? - a web page development framework. struts combines java servlets,
java server pages, custom tags, and message resources into a unified framework.
it is a cooperative, synergistic platform, suitable for development teams,
independent developers, and everyone between.
how is the mvc design pattern used in struts framework? - in the mvc design
pattern, application flow is mediated by a central controller. the controller
delegates requests to an appropriate handler. the handlers are tied to a model, and
each handler acts as an adapter between the request and the model. the model
represents, or encapsulates, an application’s business logic or state. control is
usually then forwarded back through the controller to the appropriate view. the
forwarding can be determined by consulting a set of mappings, usually loaded
from a database or configuration file. this provides a loose coupling between the
view and model, which can make an application significantly easier to create and
maintain. controller: servlet controller which supplied by struts itself; view: what
you can see on the screen, a jsp page and presentation components; model: system
state and a business logic javabeans.