DOC PREVIEW
UConn CSE 298/300 - Enterprise Component Comparison

This preview shows page 1-2-3-4-5-36-37-38-39-40-73-74-75-76-77 out of 77 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 77 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 77 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 77 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 77 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 77 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 77 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 77 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 77 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 77 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 77 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 77 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 77 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 77 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 77 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 77 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 77 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

An Examination of J2EE, CORBA, and .NETFigure 5. The above diagram demonstrates how CORBA might use a databaseAuthorization – What capabilities exist within an application to restrict/grant resources based on the requesting entity’s identification?3.2.1.1 Authentication3.2.1.2 AuthorizationFigure 6. J2EE Application ConfigurationEnterprise Component Comparison:An Examination of J2EE, CORBA, and .NETFinal ReportSeth FreemanPhil GriffithFrank Manni12/12/2005Prof. Steve Demurjian1. OverviewThe goal of our project was to perform a comparison of J2EE, .NET, and CORBAcapabilities for component-based application design in four important areas ofcomputing. These areas include database connectivity, Web Services, security andinteroperability. In each of these areas, we evaluated how the J2EE and .NET platformscompare with each other. Also, we identified the areas in which CORBA can be useful.By comparing these platforms for these tasks, we have identified which one is the best touse for implementation of a specific task.All large distributed applications depend on databases to store application-relateddata. We explored the facilities in J2EE, .NET and CORBA that support databaseconnectivity. We examined the different ways J2EE and .NET handle database updates,insertions and queries. We also compared the performance of J2EE and .NET in updatingand querying a sample database.Web Services allow applications to share functionality using communicationprotocols such as HTTP, SOAP and XML. We examined the facilities in J2EE and .NETto create and deploy a web service. We also explored the mechanism for each platform toinvoke the methods of a web service. Finally, we compared the ease of use ofimplementing a web service in J2EE vs. .NET, as well as the performance of each.CORBA provides similar functionality to Web Services in that it facilitates thecommunication between multiple distributed applications. We examined the benefits ofutilizing web services vs. CORBA.Security of distributed applications is paramount. Platforms used for developingdistributed applications must provide API's to enforce security. We will focus on thesecurity mechanisms performed directly by the application and application framework toenable authentication, authorization and the encryption of data. J2EE, .NET and CORBAeach include services to do this. We explored these technologies in detail and determinetheir strengths and weaknesses. We also compared the ease of use of incorporatingauthentication and authorization in applications developed by J2EE, .NET and CORBA.The interoperability of an application determines how well the application canexchange information with other applications residing on heterogeneous platforms. Thisis an important factor when designing distributed applications, because clients, servers,databases, and other components often reside on different platforms. Thus there must betools that allow the application developer to translate data and information amongdifferent platforms. We examined what support J2EE, .NET and CORBA provide tofacilitate this exchange. We also focused on remoting using J2EE and .NET and ondifferent types of interoperability that CORBA allows.2. Detailed Discussion/ScopeIn this project, we compared/contrasted the functionality of J2EE, .NET, andCORBA for component-based application development. Below is a brief description ofeach of the technologies, and their underlying components.2.1 J2EEJ2EE (Java 2 Platform, Enterprise Edition) is a specification to enable applicationdevelopers to develop multi-tier enterprise-wide distributed applications. J2EE wasdeveloped by Sun Microsystems in collaboration with leaders in the enterprise softwarearena; it focuses on providing a software platform that promotes the development anddeployment of reusable software components. J2EE is an extension of J2SE (Java Platform 2, Standard Edition). J2SE consistsof a robust set of API’s for application developers based on the Java programminglanguage. Applications developed in J2SE are compiled into Java byte code and run onthe Java Virtual Machine (JVM). The core Java API’s and the JVM together constitute theJava Runtime Environment (JRE) which is required on any hardware platform whichwants to support J2SE. Figure 1 is a diagram of J2SE v1.5 which shows the relationshipbetween J2SE, JRE, JVM as well as the numerous packages available. Figure 1. Java 2 Standard Edition version 1.5J2EE extends the J2SE by adding support for Enterprise JavaBeans components,Java Servlets, JavaServer Pages, XML technologies and Web Services. Enterprise JavaBeans are server-side components used to encapsulate the business logic of anapplication. Java Servlets are Java programs used to extend the functionality of a server.JavaServer Pages (JSP) are HTML documents embedded with Java code, used todynamically create HTML pages. XML technologies are used to allow the transfer of databetween various components in a distributed application, and are realized throughmultiple packages including Java API for XML Processing (JAXP). Web Services aresupported through Java packages such as Java API for XML-based RPC (JAX-RPC).This extra functionality provided in J2EE is what enables the development of enterprise-wide applications.2.2 .NET .NET, developed by Microsoft in 2002, is a platform designed for applicationdevelopers to quickly develop Internet-based applications. .NET supports distributedapplication development by including database support through ADO.NET, legacysupport through IIOP.NET, as well as support for Web Services and XML. The .NETFramework is the infrastructure to support .NET technologies consists of the followingcomponents, illustrated in Figure 2.Figure 2. Framework for .NETThe .NET Architecture is comprised mostly of two components. One is the .NETFramework class library and the other is the Common Language Runtime (CLR). TheCLR is responsible for providing the run time environment and services to the .NETframework. The CLR consists of many components including the garbage collector, Common Language Runtime (CLR) ASP.NET .NET Framework class


View Full Document

UConn CSE 298/300 - Enterprise Component Comparison

Documents in this Course
Java Tool

Java Tool

58 pages

Load more
Download Enterprise Component Comparison
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Enterprise Component Comparison and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Enterprise Component Comparison 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?