J2EE

THE JAVA 2 ENTERPRISE ARCHITECTURE (J2EE) (Insert Name) (Institutional Affiliation) The advancements in technology have led businesses and organizations to adopt more flexible and scalable methods of designing and implementing business applications. Distributed systems, which are adopted as a result of the emergence of the web, provide a foundation and standards of using objects within one application from another application regardless of application location (Zhiguo, 2004). The J2EE, which is an acronym for Java 2 Platform Enterprise Edition platform, gives a unified approach for enterprise-wide, distributed applications via a component-based application model. Typical features The J2EE has three major architectural elements: J2EE Servlets, Java Server Pages and the Enterprise JavaBeans. In general the application system consists of three tiers: client tier, Middle Tier and the Enterprise data tier. The above elements fall in these tiers and have been discussed below: Servlets: A servlet can be defined as the Java object that extends the functionality of HTTP server. This is the entry point into an n-tiered application, and generates dynamic content, responding to the HTTP requests with the correct responses. The servlet executes within a web container (Batchelli, 2006). Java Server Pages: These are powerful and dynamic page assembly mechanisms. The JSP combines markup with scriptlets of the inline Java code and produce a dynamic content. They enable content developers to implement the presentation layer separate from the business logic. Enterprise Java Bean This is the component model that helps in simplifying the development of middleware applications by providing automatic support for persistence, transactions, security among other services (Bodoff, et al, 2004). This component model enables the development of portable, distributable, scalable and transactional components that exist over different J2EE servers and different environments. Development process The development of the J2EE may be summarized in the following steps * Analysis of the requirements: this describes what the system is supposed to do. These include functional and non functional requirements. * Analysis of the object: this helps in understanding the problem and the gain knowledge about the problem domain. * Specification of the architecture: this is the analysis of all the parts that constitute the system. These include the structure, interfaces and communication mechanisms. * Object design: this includes all the technical factors such as the kind of platform and the language. This should address all specifications of all classes. * Implementation: this step comes after the architecture and the design issues have been addressed (Zhong, 2001). * Validation: this involves the testing of the system to understand if it works as designed and meets all the requirements. This involves unit testing, integration testing and us...