Distributed Multitiered Applications The JavaBeans Component Architecture Enterprise Information System Tier UDDI and ebXML Standard Formats Java EE Application Assembly and Deployment Enterprise JavaBeans Technology JavaServer Pages Standard Tag Library JavaBeans Activation Framework Java API for XML Web Services (JAX-WS) Java Architecture for XML Binding (JAXB) SOAP with Attachments API for Java Java Database Connectivity API Java Naming and Directory Interface Java Authentication and Authorization Service Simplified Systems Integration Sun Java System Application Server 9.1 2. Using the Tutorial Examples 3. Getting Started with Web Applications 5. JavaServer Pages Technology 7. JavaServer Pages Standard Tag Library 10. JavaServer Faces Technology 11. Using JavaServer Faces Technology in JSP Pages 12. Developing with JavaServer Faces Technology 13. Creating Custom UI Components 14. Configuring JavaServer Faces Applications 15. Internationalizing and Localizing Web Applications 16. Building Web Services with JAX-WS 17. Binding between XML Schema and Java Classes 19. SOAP with Attachments API for Java 21. Getting Started with Enterprise Beans 23. A Message-Driven Bean Example 24. Introduction to the Java Persistence API 25. Persistence in the Web Tier 26. Persistence in the EJB Tier 27. The Java Persistence Query Language 28. Introduction to Security in the Java EE Platform 29. Securing Java EE Applications 31. The Java Message Service API 32. Java EE Examples Using the JMS API 36. The Coffee Break Application | Development RolesReusable modules make it possible to divide the application development and deployment processinto distinct roles so that different people or companies can perform different partsof the process. The first two roles involve purchasing and installing the Java EE product andtools. After software is purchased and installed, Java EE components can be developedby application component providers, assembled by application assemblers, and deployed by application deployers.In a large organization, each of these roles might be executed by differentindividuals or teams. This division of labor works because each of the earlierroles outputs a portable file that is the input for a subsequent role.For example, in the application component development phase, an enterprise bean software developerdelivers EJB JAR files. In the application assembly role, another developer combines these EJBJAR files into a Java EE application and saves it in anEAR file. In the application deployment role, a system administrator at the customer siteuses the EAR file to install the Java EE application into aJava EE server. The different roles are not always executed by different people. If you workfor a small company, for example, or if you are prototyping asample application, you might perform the tasks in every phase. Java EE Product ProviderThe Java EE product provider is the company that designs and makes availablefor purchase the Java EE platform APIs, and other features defined in theJava EE specification. Product providers are typically application server vendors who implement theJava EE platform according to the Java EE 5 Platform specification. Tool ProviderThe tool provider is the company or person who creates development, assembly, andpackaging 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 DeveloperAn enterprise bean developer performs the following tasks to deliver an EJB JARfile that contains one or more enterprise beans:
Web Component DeveloperA web component developer performs the following tasks to deliver a WAR filecontaining one or more web components:
Application Client DeveloperAn application client developer performs the following tasks to deliver a JAR filecontaining the application client:
Application AssemblerThe application assembler is the company or person who receives application modules fromcomponent providers and assembles them into a Java EE application EAR file. Theassembler or deployer can edit the deployment descriptor directly or can use toolsthat correctly add XML tags according to interactive selections. A software developer performs the following tasks to deliver an EAR file containingthe Java EE application:
Application Deployer and AdministratorThe application deployer and administrator is the company or person who configures anddeploys the Java EE application, administers the computing and networking infrastructure where Java EEapplications run, and oversees the runtime environment. Duties include such things as settingtransaction controls and security attributes and specifying connections to databases. During configuration, the deployer follows instructions supplied by the application component provider to resolveexternal dependencies, specify security settings, and assign transaction attributes. During installation, the deployermoves the application components to the server and generates the container-specific classes andinterfaces. A deployer or system administrator performs the following tasks to install and configurea Java EE application:
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.Legal Notices |