The Development of the Java 2 Enterprise Architecture (J2EE)

NB: We do not resell your papers. Upon ordering, we do an original paper exclusively for you.

NB: All your data is kept safe from the public.

Table of Contents

Introduction
Development and Design of J2EE
The J2EE Component Model
Conclusion
References

Introduction

The number of global 2000 enterprises using java technology has been on the increase, with more professional developers, open-source community and big industries adopting java and its enterprise component framework, java 2 Enterprise Edition (J2EE). This technology has emerged as leading component architecture for applications requiring agility, scalability and interoperability. The technology has contributed a lot to the intelligent Enterprise Architecture, therefore, facilitating Enterprise Web Services (Sierra & Bates, 2008).

Development and Design of J2EE

The need for agile, flexible and scalable techniques in the design and implementation of business applications is attributed to the rise in technology in business strategy (Sharma, Stearns, & Ng, 2002). Two significant components that have led to the fast adoption of distributed component architectures and their associated tools and platforms are the emergence of the Web and the rising awareness of object and component development models. The foundation and standards for invoking objects between different applications residing in the same server, varying servers or even varying organizations is made possible by use of distributed component architectures (Sharma, Stearns, & Ng, 2002).

According to Brevoort (2005) the J2EE platform is essentially a distributed Java application server environment that provides a set of Java extension APIs to build applications and a runtime infrastructure for hosting applications. This implies that the run-time infrastructure of J2EE specifies the roles and interfaces for applications. In doing this, J2EE allows application developers to focus on application logic by unifying access to enterprise services including transaction processing, database access and messaging via its enterprise service APIs. J2EE application programs are able to connect to external services and resources such as databases via interfaces. Some of these resources include: JDBC, a connectivity API that allows transactional, querying, retrieval and manipulation of data; JNDI, which allows access to directory services necessary when looking up distributed components; JMS, which allows asynchronous sending and receiving of messages; and Java Mail, which works in a manner similar to JMS (Brevoort, Steinley, & Spinnenweber, 2005).

The J2EE Component Model

J2EE defines a standard framework for developing a variety of enterprise applications that are available, secure and scalable (Brevoort, Steinley, & Spinnenweber, 2005). According to Brevoort (2005), the J2EE platform allows for a unified approach for enterprise-wide, distributed applications via a component-based application model. These benefits are attainable by defining a standard architecture (Brevoort, Steinley, & Spinnenweber, 2005). Specifications and compliance tests help to ensure portability of applications across the wide variety of enterprise systems capable of supporting J2EE. The Java Community Process (JCP) is served with the responsibility of creating and maintaining afore mentioned specifications by developing java technology, guiding the development and approval of Java technical specifications (Brevoort, Steinley, & Spinnenweber, 2005).

There are many technology vendors including web server, application server, database system and operating system vendors, whose role is to supply J2EE compliant products, tools and platforms. The vendors also ensure that the J2EE APIs are available to the application components via containers and provide the mapping of the application components to the network protocols as specified (Sharma, Stearns, & Ng, 2002).

Conclusion

Java has been able to expand its XML integration, owing to the emergence of web services. There are a number of similar objectives between J2EE and XML including platform independence, portability and vendor neutrality that have enabled the provision of a much improved suite of functionality (Sharma, Stearns, & Ng, 2002). J2EE has incredible XML capabilities. These enable web service development and integration, making it a vital integration element in future applications. Brevoort (2005) states that:

The portability, interoperability, reliability, and stability of Java provide a flexible foundation for the automation of many repeatable processes, and J2EEs strength is in its ability to work across heterogeneous systems both within the enterprise and the extended enterprise.

The present organizations make the use of both NET and J2EE component models, within an enterprise architecture, instead of investing in a single one (Sharma, Stearns, & Ng, 2002).

References

Brevoort, M., Steinley, M., & Spinnenweber, H. (2005). J2EE A Distributed Component Architecture Model. LiquidHub.

Sharma, R., Stearns, B., & Ng, T. (2002). J2EE connector architecture and enterprise application integration. Inc. Boston, MA: Addison-Wesley Longman Publishing Co.

Sierra, K., & Bates, B. (2008). Sun Certified Programmer for Java 6. India: McGraw-Hill Education.

Click Here To Order Now!

The Development of the Java 2 Enterprise Architecture (J2EE)

Do you need this or any other assignment done for you from scratch?

We have qualified writers to help you.

We assure you a quality paper that is 100% free from plagiarism and AI.

You can choose either format of your choice ( Apa, Mla, Havard, Chicago, or any other)