Iii. J2EE
-------------------------------------------------- ------------------------------
The Java 2 Platform, Enterprise Edition (J2EE) was designed to simplify complex problems with the development, deployment, and management of multi-tier enterprise solutions. J2EE is an industry standard, and is the result of a large industry initiative led by Sun Microsystems .
It's important for you to realize that J2EE is a standard, not a product. You can not "download" J2EE. Rather you download a set of Adobe Acrobat PDF files which describe agreements between applications and the containers in which they run. So long as both SIDES OBEY THE J2EE CONTRACTS, Applications Can Be Deployed In a Variety of Container Environments.
The J2EE camp's goal is to give customers choice of vendor products and tools, and to encourage best-of-breed products to emerge through competition. The only way this would ever happen is if the industry as a whole were bought-into J2EE. To secure buy-in, Sun collaborated with other vendors of eBusiness platforms, such as BEA, IBM, and Oracle, in defining J2EE. Sun then initiated the Java Community Process (JCP) to solicit new ideas to improve J2EE over time. The reason Sun Did this is because the advice - The Best Way to Secure Buy-in to an idea is to involve Others in defining That Idea.
Java: The Foundation for J2EE
. The J2EE architecture is based on the Java programming language What's exciting about Java is that it enables organizations to write their code once, and deploy that code onto any platform The process is as follows.:
Developers Write Source Code in Java.
The Java code is compiled into bytecode, which is a cross-platform intermediary, halfway between source code and machine language.When the code is ready to run, the Java Runtime Environment (JRE) interprets this bytecode and executes it at run-time.
J2EE IS An Application of Java. Your J2ee Components Are Transformed Into Bytecode and Executed by a Jre At Runtime. Even the Containers Are Typically Written in Java.
J2EE and Web Services
J2EE has historically been an architecture for building server-side deployments in the Java programming language. It can be used to build traditional web sites, software components, or packaged applications. J2EE has recently been extended to include support for building XML-based web services AS Well. These Web Services Can Interoperate With other Web Services That May or May Not Have Been Written to the J2EE Standard.
J2EE Web Services Development Model is shown in Figure 1.
Figure 1 Developing Web Services with J2EE
Briefly, Figure 1 IS Explained As Follows:
J2EE Application IS Hosted Wtem of Service Necessary for Enterprise Applications, Such As Transactions, Security, And Persistence Services.
The business layer performs business processing and data logic. In large-scale J2EE applications, business logic is built using Enterprise JavaBeans (EJB) components. This layer performs business processing and data logic. It connects to databases using Java Database Connectivity (JDBC) or SQL / J, or existing systems using the Java Connector Architecture (JCA). It can also connect to business partners using web services technologies (SOAP, UDDI, WSDL, ebXML) through the Java APIs for XML (the JAX APIs).
Business partners can connect with J2EE applications through web services technologies (SOAP, UDDI, WSDL, ebXML). A servlet, which is a request / response oriented Java object, can accept web service requests from business partners. The servlet uses the JAX APIs to perform web services operations. Shared context services will be standardized in the future through shared context standards that will be included with J2EE.Traditional 'thick' clients such as applets or applications connect directly to the EJB layer through the Internet Inter-ORB Protocol (IIOP Rather Than Web Services, Since Generally The Thick Clients Are Written by The Same Organization That Author The IS No Need for XML-Based Web Service Collaboration.
Web Browsers and Wireless Devices Connect to JavaServer Pages (JSPS) Which Render User Interfaces in HTML, XHTML, or WML.
Reference IMplementation
In addition to the specifications, Sun also ships a reference implementation of J2EE. Developers write applications to this to ensure portability of their components. This implementation should not be used for production, but rather just for testing purposes.
Additional Services
All vendors that offer J2EE platforms provide additional features not found in the standard. Some of them impact portability, such as extended EAI functionality, E-Commerce components, or advanced B2B integration. Other features, such as load-balancing, transparent fail-over , And Caching, Do Not Affect Portability of Application Code, Because They Are Implicit Services Which Are Provided Behind-The-Scnes By The Container.
