Java ee introduction

Java ee introduction

• 1.
  JAVA EE 7Enterprise What is ?
• 2.
  About me  SoulemaneMoumie  Programmer Blogger Open source advocate  www.moumie.org Seite 1
• 3.
  Seite 2 Introduction In theworld of information technology, enterprise applications must be designed, built, and produced for less money, with greater speed, and with fewer resources. In this regard, Java EE platform aims at providing developers with a powerful set of APIs while shortening development time, reducing application complexity, and improving application performance.
• 4.
  Seite 3 Java EE7 Platform A platform is a group of technologies that are used as a base upon which other applications, processes or technologies are developed. The most important goal of the Java EE 7 platform is to simplify development by providing a common foundation for the various kinds of components in the Java EE platform. This platform is regularly update through the addition of new technologies or new features to existing technologies.
• 5.
  Java EE ApplicationModel Application model is a notation and rules for expressing the conceptual and implementation architectures of an application. The Java EE application model begins with the Java programming language and the Java virtual machine. This model defines an architecture for implementing services as multitier applications divided into the following parts: - The business and presentation logic to be implemented by the developer. - The standard system services provided by the Java EE platform. The developer can rely on the platform to provide solutions for the hard systems-level problems of developing a multitier service. Seite 4
• 6.
  Distributed Multitiered Applications Seite 5 JavaEE multitiered applications are generally considered to be three-tiered applications because they are distributed over three locations
• 7.
  Security • The JavaEE platform provides standard declarative access control rules that are defined by the developer and interpreted when the application is deployed on the server. • Java EE also provides standard login mechanisms so that application developers do not have to implement these mechanisms in their applications. • All these features make the Java EE platform applications portable to a wide variety of security implementations Seite 6 Java EE Components • A Java EE component is a self-contained functional software unit that is assembled into a Java EE application with its related classes and files and that communicates with other components. • The Java EE specification defines the following Java EE components: - Application clients and applets are components that run on the client. - Java Servlet, Java Server Faces, and Java Server Pages (JSP) technology components are web components that run on the server. - EJB components (enterprise beans) are business components that run on the server.
• 8.
  Java EE Clients •Web Clients - Dynamic web pages containing various types of markup language (HTML, XML, …), which are generated by web components running in the web tier. This web page can include an applet . An applet is a small client application written in java that executes in the Java virtual machine installed in the web browser. - Web browser, which renders the pages received from the server. • Application Clients An application client runs on a client machine and provides a way for users to handle tasks that require a richer user interface than can be provided by a markup language. The GUI created from the Swing API or the Abstract Window Toolkit (AWT) API, but a command-line interface is certainly possible. Seite 7
• 9.
  Data flow • TheJavaBeans Component Architecture JavaBeans components have properties and have get and set methods for accessing those properties. They are used to manage the data flow between the following: - An application client or applet and components running on the Java EE server - Server components and a database • Java EE Server Communications - The client communicates with the business tier running on the Java EE server either directly. - or, as in the case of a client running in a browser, by going through web pages or Servlets running in the web tier. Seite 8
• 10.
  Web Components • Servletsare Java programming language classes that dynamically process requests and construct responses. • JSP pages are text-based documents that execute as Servlets but allow a more natural approach to creating static content. • Java Server Faces technology builds on servlets and JSP technology and provides a user interface component framework for web applications. Important: Static HTML pages ,applets, Server-side utility classes are bundled with web components during application assembly but are not considered web components by the Java EE specification. Seite 9
• 11.
  Business Components Business code,which is logic that solves or meets the needs of a particular business domain such as banking, retail, or finance is handled by enterprise beans running in either the business tier or the web tier. These enterprises bean also retrieves/sends data from/to storage, processes it (if necessary), and sends it back to the client program. Enterprise Information System Tier The enterprise information system tier handles EIS software and includes enterprise infrastructure systems, such as ERP, mainframe ,transaction processing, database systems Seite 10
• 12.
  Java EE Containers Containersare the interface between a component and the low-level, platform-specific functionality that supports the component. The deployment process installs Java EE application components in the Java EE containers, the server and containers are as follows: - Java EE Server: The runtime portion of a Java EE product. A Java EE server provides EJB and web containers - EJB Container: Manages the execution of enterprise beans for Java EE applications. - Web Container: Manages the execution of web pages, servlets, and some EJB components for Java EE applications. - Web Application client container: Manages the execution of application client components . Application clients and their container run on the client. - Applet Container: Manages the execution of applets. Consists of a web browser and a Java Plug-in running on the client together. Seite 11
• 13.
  Java EE ContainersServices . - The Java EE security model - The Java EE transaction model - The Java EE remote connectivity model - Web JNDI lookup services provide a unified interface to multiple naming and directory services in the enterprise so that application components can access these services. Seite 12
• 14.
  Web Services Support WebServices are web-based enterprise applications that use open, XML-based standards and transport protocols to exchange data with calling clients. These XML- based standards and protocols are: - XML: Extensible Markup Language (XML) is a cross-platform, extensible, text-based standard for representing data. - SOAP Transport Protocol: SOAP is an XML-based protocol that follows the HTTP request-and-response model. Client requests and web service responses are transmitted as Simple Object Access Protocol (SOAP) messages over HTTP. - WSDL Standard Format: The Web Services Description Language (WSDL) is a standardized XML format for describing network services (name, location, communication ways). WSDL service descriptions can be published on the Web. It can be generated using Glassfish server. Seite 13
• 15.
  Java EE ApplicationAssembly and Deployment A Java EE application is packaged into one or more standard units for deployment to any Java EE platform-compliant system. Deployment typically involves using a platform's deployment tool to specify location- specific information, such as a list of local users who can access it and the name of the local database. For deployment purpose, J2EE applications are delivered and reside in Archive files (or unit). Seite 14 J2EE Archive Type File Extension Module Type Enterprise archive EAR All modules together Java Archive JAR Enterprise Bean Module, Application Client module Web Archive WAR Web module Resource Adapter RAR Resource adapter module
• 16.
  Java EE 7APIs  Enterprise JavaBeans Technology.  Java Servlet Technology  JavaServer Faces Technology  JavaServer Pages Technology  JavaServer Pages Standard Tag Library  Java Persistence API  Java Transaction API  Java API for RESTful Web Services  Managed Beans  Contexts and Dependency Injection for Java EE  Dependency Injection for Java  Bean Validation  Java Message Service API  Java EE Connector Architecture  JavaMail API  Java Authorization Contract for Containers  Java Authentication Service Provider Interface for Containers  Java API for WebSocket  Java API for JSON Processing  Concurrency Utilities for Java EE  Batch Applications for the Java Platform Seite 15
• 17.
  Java EE 7APIs in the Java Platform, Standard Edition 7 Several APIs that are required by the Java EE 7 platform are included in the Java Platform, Standard Edition 7 (Java SE 7) and are thus available to Java EE applications.  Java Database Connectivity API.  Java Naming and Directory Interface API  JavaBeans Activation Framework  Java API for XML Processing  Java Architecture for XML Binding  Java API for XML Web Services  SOAP with Attachments API for Java  Java Authentication and Authorization Service  Common Annotations for the Java Platform Seite 16
• 18.
  GlassFish Server Tools GlassFishServer is a compliant implementation of the Java EE 7 platform. In addition to supporting all the APIs described in the previous sections.  Administration Console: web-based GUI GlassFish Server administration utility.  asadmin: command-line administration utility is used to start and stop GlassFish Server and to manage users, resources, and applications.  appclient: launches the application client container and invokes the client application  capture-schema: extract schema information from a database, producing a schema file that GlassFish Server can use for container-managed persistence.  package-appclient: package the application client container libraries and JAR files.  Java DB database: a copy of the Java DB server.  xjc: transform, or bind, a source XML schema to a set of JAXB content classes in java  schemagen: create a schema file for each namespace referenced in your Java classes.  wsimport: generate JAX-WS portable artifacts for a given WSDL file.  wsgen: read a web service endpoint class and generate all the required JAX-WS Seite 17
• 19.
  Value to Developers •Secure Solutions • Concentrate on business logic/solution, yielding • better productivity • Choice of databases and components • Use of existing investments Seite 18
• 20.
  References https://docs.oracle.com/javaee/7/tutorial/ Seite 19
• 21.
  Thank You ! Seite20