Bài giảng Lập trình mạng 2 - J2ee architecture- Nguyễn Xuân Vinh

 two parts:Dynamic web pages containing various types ofmarkup language (HTML, XML, and so on), which are generated by web components running in the web tieA web browser, which renders the pages received fromthe serverA web client is sometimes called a thin client.Thin ClientDo not query databases.Do not execute complex business rules.Heavyweight operations are of-loaded to enterprise beans executing on Java EE Server.Java EE ClientsApplication ClientsRuns on a client machine and provides a way for users to handle tasks that require a richer user interface.SwingAWT (Abstract Window Toolkit)Command line interfaceJava EE ClientsAppletsA web page can include an embedded applet.Written in the Java programming language.Applet is a small client application that executes in the JVM installed in the web browser.Java EE ClientsThe JavaBeans Component ArchitectureThe server and client tiers include JavaBeans component to manage the data flow between the following:An application client or applet and components running on the Java EE serverServer components and a database.JavaBeans components are not considered Java EE components by the Java EE specification.JavaBeans components have properties and have get and set methods for accessing the properties.Java EE ClientsJava EE Server CommunicationsFigure - Server CommunicationJava EE Server CommunicationsFigure - Server CommunicationWeb ComponentsJava EE web components are either:Servlets: Java programming language classes that dynamically process requests and construct responses.Web pages: JSF (JavaServer Faces), JSP (JavaServer Pages).JSP: text-based documents that execute as servlets but allow a more natural approach to creating static content.JSF: builds on Servlets and JSP technology and provides a user interface component framework for web applications.Question: Static HTML pages and applets are bundled with web components during application assembly but are not considered web components by the Java EE specification.Server-side utility classes can also be bundled with web components and, like HTML pages, are not considered web components.Web ComponentsFigure - Web Tier and Java EE ApplicationsWeb ComponentsFigure - Web Tier and Java EE ApplicationsBusiness ComponentsFigure - Business and EIS TiersBusiness ComponentsFigure - Business and EIS TiersEnterprise Information SystemTierThe Enterprise Information System tier handles EIS software and includes enterprise infrastructure systemsEnterprise Resource Planning (ERP).Mainframe transaction processing.Database systems.Other legacy information systems. Example: Java EE application components might need access to enterprise information systems for database connectivity.Java EE ContainersThere are 2 Java EE Containers as follow:Container ServicesContainer TypesContainer ServicesContainers are the interface between a component and the low-level platform-specific functionality that supports the component.Before it can be executed, a web, enterprise bean, or application client component must be assembled into a Java EE module and deployed into its container.Container settings customize the underlying support provided by the Java EE server, including such services as:Security.Transaction management.JavaNaming and Directory Interface (JNDI) API lookupsRemote connectivity.Container ServicesThe Java EE security model lets you configure a web component or enterprise bean so that system resources are accessed only by authorized users.The Java EE transaction model lets you specify relationships among methods that make up a single transaction so that all methods in one transaction are treated as a single unit.JNDI lookup services provide a unified interface to multiple naming and directory services in the enterprise so that application components can access these services.The Java EE remote connectivity model manages low-level communications between clients and enterprise beans. After an enterprise bean is created, a client invokes methods on it as if it were in the same virtual machine.Container TypesFigure  -Java EE Server and ContainersContainer TypesFigure  -Java EE Server and ContainersContainer TypesJava EE server: The runtime portion of a Java EE product. A Java EE server provides EJB and web containers.Enterprise JavaBeans (EJB) container: Manages the execution of enterprise beans for Java EE applications. Enterprise beans and their container run on the Java EE server.Web container: Manages the execution of web pages, servlets, and some EJB components for Java EE applications. Web components and their container run on the Java EE server.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 Java Plug-in running on the client togetherWeb Services SupportThe Java EE platform provides the XML APIs and tools you need to quickly design, develop, test, and deploy web services and clients.Interoperate with other web services and clients running on Java-based or non-Java-based platforms.No low-level programming is needed, because the XML API implementations do the work of translating the application data to and from an XML-based data stream that is sent over the standardized XML-based transport protocolsWeb Services SupportFigure - Web Service ScenarioWeb Services SupportFigure - Implementing Web Services Using Java APIsXMLExtensibleMarkup Language (XML) is a cross-platform, extensible, text-based standard for representing data. XML data can create their own tags to describe the data.Use XML style sheets to manage the display and handling of the data.SOAP Transport ProtocolExchange between clients and web services (Client requests and web service responses) are transmitted as Simple Object Access Protocol (SOAP) messages over HTTP.SOAP is an XML-based protocol that follows the HTTP request-and-response model.The SOAP portion of a transported message does the following:Deines an XML-based envelope to describe what is in themessage and explain how to process themessage.Includes XML-based encoding rules to express instances of application-deined data types within themessage.Deines an XML-based convention for representing the request to the remote service and the resulting response.WSDL Standard FormatFigure – Publish, Lookup, Retrieve, Call Web ServiceWSDL Standard FormatThe Web Services Description Language (WSDL) is a standardized XML format for describing network services.The description includes:Name of the service.Location of the service.The ways to communicate with the service.Almost Java EE support generate WSDL for specific web service.Java SE also support tool to generate Java Classes to invoke a web service base on given wsdl file.UDDI and ebXML Standard FormatsUniversal Description, Discovery and Inte-gration (UDDI)Electronic Business using eXtensible Markup Language (ebXML)Both are:XML-based standards.To publish information on the Internet about products and web services.This information can be readily and globally accessed by clients who want to do business.Java EE Application Assembly and DeploymentA Java EE application is packaged into one or more standard units for deployment to any Java EE platform-compliant system. Each unit containsA functional component or components, such as an Enterprise bean, web page, Servlet, or Applet.An optional deployment descriptor that describes its contentInvolves 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. Once deployed on a local platform, the application is ready to run.Java EE Application Assembly and DeploymentFigure - Sun Java System Application Server File SetJava EE Application Assembly and DeploymentFigure - Module Assembly and DeploymentPackaging ApplicationsThere are 3 standard extensions:JAR (Java Archive):A Java EE application is delivered in.WAR (Web Archive): A Web application is deployed in.EAR (Enterprise Archive).A WAR or EAR file is a standard JAR (.jar) file with a .war or .ear extensionPackaging ApplicationsFigure - EAR File StructureA deployment descriptor, an XML document with an .xml extension, describes the deployment settings of an application, a module, or a componentTypes of deployment descriptorsThe two types of deployment descriptors are Java EE and runtimeJava EE deployment descriptor is defined by a Java EE specification and can be used to configure deployment settings on any Java EE-compliant implementation.Runtime deployment descriptor is used to configure Java EE implementation-speciic parametersFor exampleGlassFish Server runtime deployment descriptor contains such information as the context root of a web application, as well as GlassFish Server implementation-specific parameters, such as caching directives.GlassFish Server runtime deployment descriptors are named sun-moduleType.xml and are located in the same META-INF directory as the Java EE deployment descriptorTypes of Java EE modulesJava EE modules are of the following types:EJB modules: contain class files for enterprise beans and an EJB deployment descriptor. Packaged as JAR files with a .jar extension.Web modules: contain servlet class files, web files, supporting class files, GIF and HTML files, and a web application deployment descriptor. Packaged as JAR files with a .war (web archive) extension.Application client modules: contain class files and an application client deployment descriptor.Packaged as JAR files with a .jar extension.Resource adapter modules: contain all Java interfaces, classes, native libraries, and other documentation, along with the resource adapter deployment descriptor.Packaged as JAR files with an .rar (resource adapter archive) extension.Development RolesJava EE Product Provider.Tool Provider.Application Component Provider.Enterprise BeanDeveloper.Web ComponentDeveloper.Application ClientDeveloper.Application Assembler.Application Deployer and Administrator.Java EE Product ProviderDesigns andmakes available for purchase the Java EE platform APIs and other features defined in the Java EE specification.Product providers are typically application server vendors that implement the Java EE platform according to the Java EE 6 Platform specification.Tool ProviderThe tool provider is the company or person who creates development, assembly, and packaging tools used by component providers, assemblers, and deployers.Application Component ProviderThe application component provider is the company or person who creates web components, enterprise beans, applets, or application clients for use in Java EE applications.Enterprise Bean Developer: performs the following tasks to deliver an EJB JAR file that contains one or more enterprise beans:Writes and compiles the source code.Specifies the deployment descriptor (optional)Packages the .class files and deployment descriptor into the EJB JAR file.Application Component ProviderWeb Component Developer: performs the following tasks to deliver aWAR file containing one or more web componentsWrites and compiles servlet source code.Writes JavaServer Faces, JSP, andHTML files.Specifies the deployment descriptor (optional).Packages the .class, .jsp, and .html files and deployment descriptor into theWAR file.Application Component ProviderApplication Client Developer: performs the following tasks to deliver a JAR file containing the application client. Writes and compiles the source code.Specifies the deployment descriptor for the client (optional).Packages the .class files and deployment descriptor into the JAR fileApplication AssemblerThe company or person who receives application modules from component providers and may assemble them into a Java EE application EAR file.Can edit the deployment descriptor directly or can use tools that correctly add XML tags according to interactive selections.A software developer performs the following tasks to deliver an EAR file containing the Java EE application:Assembles EJB JAR andWAR files created in the previous phases into a Java EE application (EAR) file.Specifies the deployment descriptor for the Java EE application (optional).Verifies that the contents of the EAR ile are well formed and comply with the Java EE specification.Application Deployer and AdministratorThe company or person who:Configures and deploys the Java EE application.Administers the computing and networking infrastructure where Java EE applications run.Oversees the runtime environment.the company or person who conigures anddeploys the Java EE application, administers the computing and networking infrastructure where Java EE applications run.Oversees the runtime environment.Setting transaction controls and security attributes.Specifying connections to databases.Application Deployer and AdministratorA deployer or system administrator performs the following tasks to install and configure a Java EE application:Configures the Java EE application for the operational environment.Verifies that the contents of the EAR file are well formed and comply with the Java EE speciication.Deploys (installs) the Java EE application EAR file into the Java EE server.Java EE 5 APIsFigure - Java EE Platform APIsJava EE 6 APIsFigure - Java EE Platform APIsJava EE APIs in the Web ContainerJava EE APIs in the EJB ContainerJava EE APIs in the Application Client ContainerEnterprise JavaBeans TechnologyEnterprise JavaBeans (EJB) component is a body of code having fields and methods to implement modules of business logic.There are 2 types of Enterprise beans.Session bean Represents a transient conversation with a client.When client finishes executing, the session bean and its data are gone.Message-driven beanCombines features of a session bean and a message listener.Allowe a business component to receive messages asynchronously.Commonly, these are Java Message Service (JMS) messages.Enterprise JavaBeans TechnologyIn the Java EE 6 platform, new enterprise bean features include the following:The ability to package local enterprise beans in aWAR file.Singleton session beans, which provide easy access to shared state.A lightweight subset of Enterprise JavaBeans functionality (EJB Lite) that can be provided within Java EE Profiles, such as the Java EE Web Profile.Java Servlet TechnologyJava Servlet technology lets you define HTTP-specific servlet classes.Servlet class host applications accessed by way of a request-response programming model.In the Java EE 6 platform, new Java Servlet technology features include the following:Annotation support.Asynchronous support.Ease of configuration.Enhancements to existing APIs.Pluggability.JavaServer Faces TechnologyJavaServer Faces technology is a user interface framework for building web applications.The main components of JavaServer Faces technology are:A GUI component framework.A Renderer object generates the markup to render the component and converts the data stored in a model object to types that can be represented in a view.A standard RenderKit for generating HTML/4.01 markup.The following features support the GUI components:Input validation.Event handling.Data conversion between model objects and components.Managed model object creation.Page navigation configuration.Expression Language (EL).JavaServer Faces TechnologyIn the Java EE 6 platform, new features of JavaServer Faces include the following:The ability to use annotations instead of a configuration file to specify managed beans.Facelets, a display technology that replaces JavaServer Pages (JSP) technology using XHTML files.Ajax support.Composite components.Implicit navigation.JavaServer Pages StandardTag Library (JSTL)The JavaServer Pages Standard Tag Library (JSTL) encapsulates core functionality common to many JSP applications.Use a single, standard set of tags.JSTL can use tag forHandling low control.Manipulating XML documents.Internationalization tags.Accessing databases using SQLSome commonly used functions.Java Persistence API (JPA)The Java Persistence API is a Java standards-based solution for persistence.Persistence uses an object/relational mapping approach to bridge the gap between an object-oriented model and a relational database. Java Persistence consists of the following areas:The Java Persistence API.The query language.Object/relational mapping metadata.Java Transaction API (JTA)Java Transaction API (JTA) provides a standard interface for demarcating transactions.Provides a default auto commit to handle transaction commits and rollbacks.Java API for RESTfulWeb ServicesThe Java API for RESTfulWeb Services (JAX-RS) defines APIs for the development of web services built according to the Representational State Transfer (REST) architectural style.JAX-RS application is a web application that consists of classes that are packaged as a servlet in a WAR ile along with required libraries.OthersManaged Beans: specification is part of the Java EE 6 platform specification (JSR 316).Contexts and Dependency Injection for the Java EE Platform(JSR 299): defines a set of contextual services, provided by Java EE containers.Dependency Injection for Java (JSR 330): defines a standard set of annotations (and one interface) for use on injectable classes.BeanValidation: defines a metadata model and API for validating data in JavaBeans components.JavaMessage Service API: is amessaging standard that allows Java EE application components to create, send, receive, and read messages. It is loosely coupled, reliable, and asynchronous.OthersJava EE Connector ArchitectureJavaMail APIJava Authorization Contract for ContainersJava Authentication Service Provider Interface for Containers.Java EE 6 APIs in the Java Platform, SE 6.0JavaDatabase Connectivity (JDBC) API.Java Naming and Directory Interface (JNDI) API.Java Beans Activation Framework (JAF).Java API for XML Processing (JAXP).Java Architecture for XML Binding (JAXB).SOAP with Attachments API for Java (SAAJ).Java API for XMLWeb Services (JAX-WS).Java Authentication and Authorization Service (JAAS).Java Database Connectivity (JDBC) APIThe JDBC API has two parts:An application-level interface used by the application components to access a database.A service provider interface to attach a JDBC driver to the Java EE platform.The Java Database Connectivity (JDBC) API lets you invoke SQL commands from Java programming language methods.Java Naming and Directory Interface APIProvide naming and directory functionality, enabling applications to access multiple naming and directory services.Include existing naming and directory services, such as LDAP,NDS,DNS, andNIS.Java Naming and Directory Interface APIA Java EE component can locate its environment naming context by using JNDI interfaces.A component can create a javax.naming.InitialContext object and look up the environment naming context in InitialContext under the name java:comp/env.A component’s naming environment is stored directly in the environment naming context or in any of its direct or indirect subcontexts.Java Naming and Directory Interface APIJNDI Example – Lookup.javapackage service;import java.util.Properties;import javax.naming.*;public class Lookup { public static void main(String[] args) {	 String name = "";	 if (args.length > 0)	 name = args[0];	 try {	 // Create a Properties object and set properties appropriately	Properties props = new Properties();	props.put(Context.INITIAL_CONTEXT_FACTORY, 	"com.sun.jndi.fscontext.RefFSContextFactory");	props.put(Context.PROVIDER_URL, "file:///");	// Create the initial context from the properties we just created	Context initialContext = new InitialContext(props);	// Look up the object	Object obj = initialContext.lookup(name);	if (name.equals(""))	 System.out.println("Looked up the initial context");	else	 System.out.println(name + " is bound to: " + obj);	 } catch (NamingException nnfe) {	System.out.println("Encountered a naming exception");	 } }}HỎI ĐÁP