Your SlideShare is downloading. ×
J2Spec.doc
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

J2Spec.doc

282

Published on

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
282
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. J2EE - ENTERPRISE DEVELOPMENT AND INTEROPERABILITY WITH NON-J2EE CLIENTS SEMESTER PROJECT CSE 333 – DISTRIBUTED COMPONENT SYSTEMS PROJECT TEAM SUDHA BALLA, BETSY CHERIAN AND LANCE FIONDELLA INSTRUCTOR STEVEN A. DEMURJIAN DATE: SEPTEMBER 19, 2002 REQUIREMENT SPECIFICATION OVERVIEW There have been extraordinary changes happening in the field of enterprise software development during the past few years. Technology advances have been made to imporve server-side component architectures, the most popular standards evolved being Microsoft’s Distributed interNet Applications Architecture (DNA), Sun Microsystems’ Java 2 Platform Enterprise Edition (J2EE) and Object Management Group’s CORBA standard. While Microsoft’s DNA is a product, J2EE and CORBA are standards that enable service-based architectures for the enterprise. J2EE is a collection of enterprise technologies, by understanding which portable, object-oriented, enterprise-class applications in Java could be built. Many of the quality services offered by EJB (an integral part of J2EE) and CORBA are the same in functionality. Also, Sun and OMG support EJB / CORBA interoperability and have produced standards for the same. The EJB / CORBA mapping specification and RMI-IIOP relieve EJB off the restriction that it should be solely Java-based, thus facilitating EJB components to be
  • 2. exposed as CORBA objects and makes it well suited for cross-language interoperability. Our team’s effort in this project would be an in-depth analysis of the different technologies offered by J2EE for enterprise software development, with a great deal of focus on EJB and its interoperability with CORBA. PROJECT SCOPE Server-side Component Architectures In this segment of our project we intend to uncover issues surrounding server- side development, emphasize the need for a standardized architecture, analyze the most popular Server-side Component Achitecture standards that exist and conclude where J2EE fits in the whole scenario. The J2EE Technologies In this part, we would focus our effort in explaining the different technologies that are an integral part of the J2EE standard, which form the robust suite of middleware services that make life very easy for server-side application developers. The technologies to be looked into apart from EJB which would be given great focus, are, • RMI and RMI-IIOP • Java Transaction API (JTA) • Java Messaging Service (JMS) • Java Naming and Directory Interface (JNDI) • JDBC • Servlets and JSPs
  • 3. EJB / CORBA Interoperability and Exposing EJB to non-Java Clients CORBA is a very important technology and is quite useful for advanced middleware development, cross-language support and legacy integration. Many of the concepts in EJB came out of CORBA. CORBA offers a much broader suite of middleware features such as a time service, a distributed locking service etc., but learning the complex APIs is very difficult. In this section we would try to bring out • how EJB and CORBA complement each other, • where EJB gets its edge over CORBA, • where CORBA would be still depended on, • benefits of EJB / CORBA interoperability, • interoperabilty scenarios J2EE Patterns Learning to design in any particular technology comes from experience and from sharing knowledge on the best practices and the bad ones. Patterns are about communicating problems and solutions. They enable us to document a known recurring problem and its solution in a particular context and to communicate this knowledge to others. J2EE Patterns are proven patterns for applications developed on the J2EE platform. These patterns are a result of the committed documentation of experiences of developers at the Sun Java Center, a part of Sun Professional Services, a consulting organization focussed on building Java- technology based solutions for its customers. In this project we would attempt to
  • 4. study some of the relevant patterns for the Presentation Tier, Business Tier and the Integration Tier and apply them in our protype application. Prototype Application As a proof of concept, we intend to develop a small protype application to show the concepts we understood in our effort and how they would practically be applied in real-time projects. The application would cover the following aspects: • N - tier architecture in Enterprise applications • EJB components (Entity and Session Beans) • EJB & other Java Object communication • EJB / CORBA interoperability • CORBA / non-J2EE interoperability to show how EJB components can be exposed beyond the J2EE technology • Usage of proven J2EE patterns in the design A simple sketch of the architecture of this application would be as follows: BROWSER BASED WEB JAVA CLIENT SERVER (SERVLETS and JSPs) APPSERVER DEPLOYED JAVA CLIENT WITH EJBs, CONTAINING DATABASE THE BUSINESS LOGIC NON - JAVA CLIENT CORBA LAYER PROPOSED PLAN
  • 5. The team would approach the different areas specified as follows: Server-side Component Architectures (Betsy and Lance) The J2EE Technologies (Lance and Sudha) EJB / CORBA Interoperability and Exposing EJB to non-Java Clients (Sudha, Betsy and Lance) J2EE Patterns (Sudha and Betsy) Prototype Application (Sudha, Betsy and Lance) Biweekly meetings guarantee a minimum of three hour of discussion per week. Established meetings are from 1:00p.m. to 2:30p.m. on Mondays and Wednesdays in the library. The planned schedule for the project is as follows: Thursday, September 19th: Submit Detailed Requirements/Specification on Topic September 19th to October 22nd : Work on the first four modules of the project, study material, understand concepts and their practical application areas. Tuesday, October 22nd: Submit Midterm report October 23rd to November 22nd : Develop the prototype application applying the concepts learnt from the study. November 23rd to December 2nd : Prepare final report Monday, December 2nd: Submit Final Report and Presentation Tuesday or Thursday, December 3rd or 5th: Give presentation. REFERENCES
  • 6. Web links: http://java.sun.com http://developer.java.sun.com/developer/technicalArticles/J2EE/patterns/ http://www.theserverside.com/home/index.jsp http://java.oreilly.com http://j2ee.masslight.com/ Books: The J2EE Tutorial, Bodoff, Green, Haase, Jendrock, Pawlan, Stearns, ISBN 0-201-79168-4 Designing Enterprise Applications with the J2EE Platform, Second Edition, Singh, Stearns, Johnson, Enterprise Team, ISBN 0-201-78790-3 Mastering EJB and the J2EE, Ed Roman, ISBN 0-471-33229-1 Core J2EE Patterns, Best Practices and Strategies, Deepak Alur, John Crupi and Dan Malks, ISBN 0-13-064884-1 Professional JSP, various authors, ISBN 81-7366-211-8 Enterprise JavaBeans, Tom Valesky, ISBN 981-4035-44-0 Enterprise JavaBeans, Richard Monson-Haefel, ISBN 1-56592-605-6 Java Servlet Programming, Jason Hunter, ISBN 81-7366-056-5 Java Servlets, Karl Moss, ISBN 0-07-135188-4 CORBA, Jeremy L. Rosenberger, ISBN 81-7635-127-X COM and CORBA Side by Side, Jason Pritchard, ISBN 0-201-37945-7

×