![]() |
|
The J2EE architecture specifies a set of packaging requirements for enterprise applications that define a scalable and modular application assembly. This is very portable and can be deployed on any J2EE-compliant platform. Packaging makes the application server-agnostic.
A J2EE application is typically assembled as an archive of one or more J2EE components - Web application, servlets, JSPs, HTML pages, classes, and other resources. The archive can be composed of one or more J2EE modules, where each module represents a basic unit of application with a set of components of the same type. Information about modules is obtained from the application.xml. The flexibility and extensibility of the J2EE component model facilitates the packaging and deployment of J2EE components as individual components, component libraries, or applications.
A J2EE module that contains one or more J2EE components of the same component type, such as Web, EJB, or Connector, can be packaged together with a single deployment descriptor appropriate to that container type. The Deploy Tool reads the ejb-jar.xml and web.xml files for EJB and Web components, and the ra.xml for connectors. The packaged .ear should also contain the application.xml file.
Pramati Server provides various resources to interact with databases, send mails, and encapsulate URLs. Resources are created on the server on which the J2EE applications are deployed. Resources provided by the Server are:
An application may also need security parameters such as realms, roles, and user names. These parameters can be set using the Console.
| © Pramati Technologies 2007 | Runs on Pramati Server | Feedback | Legal |