Download to read offline
Uploaded bySimon Ritter
Developing Enterprise Applications Using Java Technology
The document outlines the evolution and future of Enterprise Java APIs and the Enterprise JavaBeans (EJB) technology, emphasizing their significance in developing and deploying enterprise-level applications. It highlights the need for solutions that are secure, efficient, and adaptable while ensuring compatibility across various systems. Additionally, it discusses the roadmap for Java 2 Platform, Enterprise Edition, focusing on key functionalities like transaction processing, messaging, and interoperability with existing technologies.
Developing Enterprise Applications Using Java Technology
- 1. Slide 1 Developing Enterprise Applicationsusing Java™ Technology Simon Ritter Sun Microsystems, Inc.
- 2. 10/1/98 Slide 2EnterpriseJava APIs Agenda • Where the Java Platform is going • IT Needs • Enterprise JavaBeans™ technology • Enterprise Java APIs • Future • Summary
- 3. 10/1/98 Slide 3EnterpriseJava APIs Where Have We Been, Where Are We Going •Consumer Java •“Desktop” Java •“Enterprise” Java •JDK “All Things to the Enterprise” •Early Development of Consumer Java •Early Development of “Enterprise” APIs” Year 1 Java Platform •JDK All Things to Everyone Year 2 Year 3
- 4. Java 2™ PlatformDevices Java Enabled Desktop Workgroup Server Java Enabled Devices High-End Server
- 5. 10/1/98 Slide 5EnterpriseJava APIs What IT needs • Solutions that deal with heterogeneity • Successful short and long term projects • Solutions that work with existing systems • Full range of integrated functionality • Secure, reliable solutions • High-performance solutions • Adaptability to change
- 6. Purchase Customize Browse JSP/Servlet Membership Catalog Enterprise JavaBean Mail ServerDirectory Server IBM MQ VISACharge Purchase Acknowledgement Customer JNI JDBC JMSJava Mail JNDI ISP HTTP(s) Server Configuration Purchase Shipping Order Purchase Acknowledgement Enterprise Application Server Web-Based Application Architecture
- 7. 10/1/98 Slide 6EnterpriseJava APIs Focus for Enterprise JavaBeans™ Technology • Platform independence • Making it even easier – Enterprise app development and deployment – Reusable components and logic • Leveraging investments • Protecting investments • Raising the bar on performance
- 8. 10/1/98 Slide 7EnterpriseJava APIs What Is Enterprise JavaBeans™ Technology? • Server component model for Java platform • Enterprise ready • Enables business-critical applications • Easy to develop and deploy N-tier apps • Portability of components across platforms • Separates business logic from presentation • Client neutral
- 9. Broad Industry Adoption! •BEA • Bluestone • Digital Harbor • Fujitsu • Gemstone • Haht Software • IBM • Information Builders • Informix • Inline • Inprise • NetDynamics • NetObjects • Netscape • Novasoft • Novell • Novera • ObjectShare • Oracle • OrchidSoft • Persistence • Progress • Secant • SilverStream • Softera • Sybase • Symantec • Synchra • Valto • Visient • Weblogic • ZeroG
- 10.
- 11. Typical EJB UsageScenario
- 12. Enterprise JavaBeans™ Technology Benefits •Core to Java 2™ Enterprise Platform – Wrap and Embrace – Productivity – Industry Support – Architectural Independence – Write Once, Run Anywhere™ • Solutions available today
- 13. EJB Roadmap • “Moscone” –Final: Q299 – Focus: Assembly & Deployment, Compliance • “Javitz” – Final: Q100 – Focus: Legacy Connectivity • “Milano” – Final Q400 – Focus: Entity Beans & Automatic Persistence • Reference implementation – Technology Preview in Q299, FCS Q499
- 14. 10/1/98 Slide 9EnterpriseJava APIs Full Range of Functionality • EJB is transactional object middleware • IT also needs full range of functionality* – Distributed transaction processing – Object Middleware – Desktop access – Data access – RPCs – Message-oriented middleware * IDC (report #15937) Middleware grouping
- 15. 10/1/98 Slide 10EnterpriseJava APIs Enterprise Java APIs • Java APIs for rest of business-critical functionality • Why? – Meet all needs of enterprise developers – Provide a full range of functionality – Establish open playing field for enterprise server software – Leverage strong partner support – Open standards
- 16. 10/1/98 Slide 11EnterpriseJava APIs Focus of Enterprise Java APIs • Platform independence • Making it even easier – Enterprise app development and deployment – Reusable components and logic • Leveraging investments • Protecting investments • Raising the bar on performance
- 17. 10/1/98 Slide 13EnterpriseJava APIs Enterprise Java APIs • Web technologies • CORBA interoperability • Data access • Transaction processing • Messaging and publish/subscribe • Naming and Directory services
- 18. 10/1/98 Slide 14EnterpriseJava APIs Web Technologies Servlets: • Web Server extensions • Focus is Java language developer • Benefits: – Write Once Run Anywhere on Web Server – High-performance server extensions
- 19. 10/1/98 Slide 15EnterpriseJava APIs Web Technologies Java Server Pages: • API for server-side scripting in Java • Focus: Enterprise Web App Developer • JSP vs. ASP: Compiled, not Interpreted • Benefits: – Dynamic content customization – Re-useable web components – One language: Client and Server
- 20. 10/1/98 Slide 16EnterpriseJava APIs Java Client ORB C++ Server ORBIIOP CORBA Interoperability • JavaTM IDL and RMI over IIOP – Invoke operations on remote network services using OMG’s IDL and IIOP – Runtime includes fully compliant Java ORB • Benefits: – Standards-based distributed computing – Legacy systems and CORBA integration
- 21. 10/1/98 Slide 17EnterpriseJava APIs • JDBC 2.0 – Scrollable cursors – Support for SQL3 types – Full support for storing/retrieving Java object types • Benefits: – More flexible queries – Improved performance and stability – Integrates to relational and legacy data sources Data Access
- 22. 10/1/98 Slide 18EnterpriseJava APIs Transaction Processing • Distributed transaction processing • JTS: Mapping to CORBA Object Transaction Service (OTS) – Access to standard object transaction coordination – Who: IBM, Inprise, Bull, WebLogic • JTA: API for transactions – Java interface to transactional systems – Who: Transaction/DB server vendors
- 23.
- 24. 10/1/98 Slide 19EnterpriseJava APIs Messaging and Pub/Sub • JMS: Java Message Service API – Asynchronous communications – Publish and Subscribe – Reliable Queues – Guaranteed delivery – Benefits: • Single interface to MOM • Open and cross platform – Who: TIBCO, IBM, Modulus, Active
- 25. Naming and Directory •JNDI: Java Naming and Directory – Unified field theory for naming – LDAP, NIS, NIS+, DNS, File, etc. – Industry support – Benefits: • Single interface to enterprise network objects • Cross platform 10/1/98 Slide 20Enterprise Java APIs
- 26. Enterprise API Roadmap •JavaIDL: Required Classes in JDK • JTA: Version 1.0 FCS 1CQ99 • Servlets: Version 2.1 FCS • JavaServer Pages: 1.0 FCS 1Q99 • JDBC: Core, Std. Ex 4Q98 • JMS: 1.0 FCS in August • JNDI: FCS 1.1.1 September • RMI-IIOP: Beta 12/98, FCS 2Q99 • Java Mail: 1.1 FCS August 98
- 27. Enterprise JavaBeans™ Java 2 Platform EnterpriseEdition Database Objects Mail Transac- tions Messaging Directory Java 2™ Platform, Enterprise Edition
- 28. 10/1/98 Slide 21EnterpriseJava APIs Java 2™ Platform, Enterprise Edition • EJB + Enterprise Java APIs • Integrated functionality • Guarantee of complete platform • Architecture for multi-vendor support • Model of how to build apps • Adaptability to change
- 29. Why J2EE • IntegratedApplication Environment • Open platform • Integrates with your existing environments • Provides foundation for future development
- 30.
- 31. J2EE Application Model •Set of APIs not sufficient – Need to show how APIs should be used to build and deploy multi-tier applications • Define “reference” application model – Examples – Patterns – Templates • Enable tools to follow application model – Development – Deployment – Runtime
- 32. J2EE Roadmap • J2EE1.0 – Application model showing components, uses, and alphas of compliance tests – Delivery of reference implementations and compliance tests for J2EE • J2EE future releases – Additional functionality, tests.
- 33. 10/1/98 Slide 22EnterpriseJava APIs Summary: What we can provide • Solutions that deal with heterogeneity • Successful short and long term projects • Solutions that work with existing systems • Full range of integrated functionality • Secure, reliable solutions • High-performance solutions • Adaptability to change
Editor's Notes
- #2 Notes: Java Platform for Business is just the presentation title, it is not the make of a platform or anything like that. Also: “Enterprise JavaBeans™” is a trademark, so as you give this talk DO NOT say “EJB”, pronounce the whole phrase everytime and always use it as an adjective, ie Enterprise JavaBeans technology. This will preserve our trademark. BIG MESSAGES: The big message the speaker should attempt to communicate are: 1. EJBs are real and companies are providing solutions today. 2. We are continuing to respond to the needs of the enterprise developer (our target market) and we are delivering on other areas in the enterprise. 3. We plan on presenting a unifying vision in the near term.
- #3 In this talk, I’ll discuss: 1. Where Java platform has been and where it is going. 2. What Enterprise developers and IT shops need 3. A brief overview of Enterprise JavaBeans™ technology 4. A Brief discussion of enterprise Java APIs that round our enterprise story 5. Discussion of where were are going with the enteprise Java Platform in the future.
- #4 The purpose of this slide is to show how the platform developed and how we listened to customers to provide targeted platforms. Year 1: Java was all things to all people Year 2: Customers told us that they wanted a small java for consumer devices, and we delivered pJava and eJava Year 3: Customer told us that Java had tremendous value on the server so we started delivering on “enterprise class’ java
- #5 Key feature is that we are enabling a who range of enterprise devices.
- #6 What do enterprise developers and IT shops in general need these days? 1. Solutions that deal with hetero: The average large it shop has 6 different platforms. They need these as tightly integrated as possible. 2. Short & Long-term. They need technology that not only makes the productive, but also will lower TCO in the future. 3. Existing systems: IT shops will not throw out what they have. 4. Secure reliable. 5. Speed. 6. In stead of buying middleware pieces from several vendors, IT would like all functionality in one platform 7. Insulate then from future .
- #8 This is the focus of EJB. This is also the focus of the JDK. Platform independence: Now with EJB you’re middleware independent as well. Making it easier: Developer focuses on business logic. Leveraging investments: EJB is layered on existing systems. Protecting Investments: EJB leverages off of Java security model. Raising bar on performance: With EJB you now have inter-server scalability. If your EJB server hits a performance wall, you can pick up your app and move it to a higher performing platform(like StarFire™ we hope).
- #9 Enterprise Ready: There are solutions ready today Enables Bus-crit apps: You can run your business on it today. Client Neutral: EJB spec does not specify a wire protocol, so any can be used, RMI, CORBA, DCOM. This allows access to non-java clients.
- #13 Enterprise JavaBeans is core to J2EE. Here’s why it’s a good thing: Wrap and embrace: Works with what you have today Productivity: EJB allows you to focus on writing business logic and not on plumbing. Industry support: We’ve led an industry group to develop EJB and there are now 4 servers on the market(7 months after the spec release) and at least 15 others on the way. The customer will have choice. Architectural Independence: You deal with writing business logic and not dealing with the specific database or transaction server you are running on. WORA: You applications can move anywhere, since it is written in Java. This means 2 things: 1) No more platform lock 2) Interserver scalability: If you hit a performance wall you can now pick up your application and drop it into a higher performing server.
- #15 EJB is transactional middleware, but that is not enough. IDC(report #15937) groups middleware into 6 categories. EJB only deals with transactional object middleware, IT needs several more categories, like Message oriented middleware, and they needs this full range of functionality all in one place in stead of in piece parts.
- #16 How do we deal with this, via the enterprise APIs, of course. Why are we doing this, (Read the bullets). Open Standards: People want choice of vendors imple,menting open standards
- #17 Platform independence: Java but also Middleware independence Making it even easier: EJB + access to a full range of enterprise services, like MOM, Mail, etc. Leverageing investments: Works with the existing systems in your enterprise Protecting your investments: leveraging off of the Java security model as well as the existing security infrastructure Raising the bar on performance: Interserver scalabillity
- #18 The enterprise APIs can be grouped into 3 areas:
- #19 Servlets are a way to build web based services in Java. Big messages: 1. They are a high performance replacement for CGI. 2. They will run on any web server since all web servers that we know about support servlets. Servlets are Write Once Run Anywhere™. They are high-performance, since unlike CGI which starts up a process for each invocation, servets untilize threads.
- #20 Java Server Pages are the technology for doing server side scripting. They are like active server pages, but are faster since they are interpreted and not compiled. Web Server Vendors will be supporting this.
- #21 In JDK, you have RMI and JavaIDL. How do you reconcile the two? We are working on RMI over IIOP which gives you the ease of use of RMI with the standard protocol goodness of IIOP. The big message: We love CORBA so much that we made it a required part of the JDK.
- #22 JDBC Which is the standard for accessing data in Java has impoved in these ways.
- #23 JTS is our Java mapping for CORBAs object transaction service. This is a set of functionality which provides distributed transaction coordination. (NOTE: JTS is NOT a TP monitor) JTA is the interfaces for starting, stopping and committing transactions in Java.
- #25 JMS: is an API for the messge-oriented middleware market that handles not only Reliable queues like MQ series from IBM, but also Publish and Subscribe functionality like TIBCO, Modulus and active software. JNDI is the was to access all naming and directory protocols from a SINGLE interface.
- #29 This is a summary of what we talked about today: EJB + APIs provide: (read bullets) Guarantee of platform: All the pieces are there Arch: multiple vendors provide this Model: Servlets + EJB is powerful model Adaptability: You write to Java, underlying model can change.
- #30 Why did we do J2EE: 1. Integrated Application Environment: To provide a complete set of enterprise services in one place. Today, enterprises speend too much time getting various pieces of server software to talk to each other. J2EE will provide a platform where vendors can provide all services in one place. 2. Open Platform 3. Integrates with your existing environment 4. Provides a foundation for the future.
- #33 J2EE 1.0: Core functionality will be EJB, Servlets, JSPs, JDBC, JNDI. Focus will be on producing the Application programming Model. J2EE Future releases: To include additional functionality. Example: JavaMail, Embedded SQL, JTS.
- #34 We are providing what enterprises want.