[2024]Digital Global Overview Report 2024 Meltwater.pdf
Enterprise GlassFish
1. Enterprise GlassFish and Java directions Roger Freixa, Principal Product Manager EMEA FMW PM Application Grid
2.
3. Java is Critical for Oracle The Foundation for Middleware and Applications
4.
5. Java Platform Investment Continues at Oracle in All Major Dimensions Java Mobile Java Standard Edition Java Enterprise Edition Java Card Java TV Embedded Java
6. Evolution of Java in the Java Community Community Development of Java Technology Specifications
13. Next Steps for GlassFish and WebLogic Server Increase Common GlassFish/WebLogic RI Usage Enable Shared GlassFish/WebLogic Infrastructure Deliver GlassFish Server/Grow Community Enable Upsizing to Fusion Middleware GlassFish Investments Aligned Products Complementary Products JPA JAX-RS JAX-WS CDI JSF JAXB JAXP JSTL Application Migration Shared Web Tier and Plug Ins Shared Lifecycle Management OSGi Modularity Implement Java EE and Web ServicesStandards for Java Platform WebLogic Server GlassFish Server Fusion Middleware Fusion Applications Java EE 6 Java EE 5/6 WebLogic Server GlassFish Server Fusion Middleware Fusion Applications Java EE 6/7 Core GlassFish Availability/QoS Core Glassfish Admin/Operations Fusion Middleware Interoperability Fusion Middleware Java Integration
30. Enterprise GlassFish and Java directions Roger Freixa, Principal Product Manager EMEA FMW PM Application Grid
Hinweis der Redaktion
Main point: protect ourselves legally This is our standard disclaimer--we will touch on some visionary things in this talk that should not be used for contractual purposes.
Can we have a positive slide about downloads/community activity. Speak about value of the community
This slide shows how modularity works with GlassFish v3. When a web application is deployed, the web module starts and the web application is available. When an enterprise application (web pages + EJBs), the EJB container starts and the EJB is deployed, and the servlets are deployed to the servlet container that is already running. In the case of JRuby, the JRuby container does not ship out-of-the-box with GlassFish v3. However, it can be quickly installed by downloading it from the update center with a few point and clicks. After it is installed, the JRuby application can be deployed using the native JRuby container. When the EJB application is undeployed, the servlet is undeployed from the servlet container, and the EJB is removed from the EJB container. Because it was the only deployed EJB, there is no need for the EJB container, so it is stopped. The net benefit is that the application server starts faster and consumes less resources because only the required modules are started to serve the running applications. There is no configuration required, just deploy the application and GlassFish will address the required dependencies. GlassFish modularity and flexibility creates opportunity. We see organizations that already have a closed-source application server, an open source application server, and a lightweight web container for web applications, not to mention the increasing interest in running non-Java applications. With GlassFIsh v3, organizations can use with the Web Profile as a manageable, lightweight container for web applications and dynamic languages, and the full distribution for Java EE Enteprise Applications.
GlassFish flexibility (and extensibility) include administration features. GlassFish momentum is in large part due to its developer and administrative productivity. On the left-hand side is the web administration console that we get “rave” reviews on. Common tasks are readily available, such as deploying applications. Documentation, which are thorough and written by professional technical writers, is also readily available. The CLI, in the lower-left-hand pane, is optimal for administrations writing shell scripts to customize or automate deployments. It is also the primary means of integrating with 3 rd party provisioning tools. New to GlassFish v3 is the RESTful administration API, which supports HTML, JSON and XML formats. Shown to the upper-right is the HTML output. The RESTful API is useful for those wanting programmatic access to GlassFish administration and monitoring features. ISVs and OEMs have the ability to write custom administration commands and expose them through any of these administration channels. Another benefit is that there is feature parity between the administration console, CLI and RESTful API, with a few exceptions such as 'start appserver'.