GlassFish
GlassFish is an open source application server project started by Sun Microsystems for the Java EE platform and now sponsored by Oracle Corporation. The supported version is called Oracle GlassFish Server. GlassFish is free software, dual-licensed under two free software licences: the Common Development and Distribution License (CDDL) and the GNU General Public License (GPL) with the classpath exception.
GlassFish provides the enterprise level reliability and performance with full clustering and has a wide functionality range. It is quite cool in that it allows you to manage the central repository via the admin panel, which supports all features available in GlassFish. However, as you know, more functions = more resources.
GlassFish Installation
To get your GlassFish server in the platform, simply:
1. Log into your PaaS dashboard and click New Environment.
2. Switch to the Java tab and pick GlassFish within the application servers section as shown in the picture below:
3. Once the environment is created, you can click Open in browser button next to the GlassFish server it comprises (expand the environment in the Environments pane at the top of the screen):
4. Now you can upload the Java application WAR package and deploy it to the environment.
5. The Glassfish administration panel can be accessed directly from the platform dashboard:
Admin page will be available in a new tab.
Note:
- The platform uses gfcluster as a cluster, so if you want to modify something, please apply changes to gfcluster.
- If you have Public IP attached to application server node, the default GlassFish admin panel port (4848) can be changed in /opt/glassfish3/glassfish/domains/domain1/config/domain.xml configuration file (a server shortcut in Favorites) by adding the following string:
| |
- Glassfish Derby Internal database is switched off by default in order to decrease the resource consumption.
Resource Consumption
If we compare different application servers, GlassFish starts looking a little like a resource hog, but its greediness is offset by its functionality, reliability and numerous other advantages provided.
| Servlet containers configuration | Resources being consumed by environment | |
|---|---|---|
| Idle | With launched admin panel | |
| 1 GF | 530-540 Mb (5 cloudlet) | 800-820 Mb (7 cloudlets) |
| 2 GF (HA off) | 820-830 Mb (9 cloudlets) | 980-1000 Mb (10 cloudlets) |
| 3 GF | 1050-1060 Mb (11 cloudlets) | 1210-1220 Mb (13 cloudlets) |
| 4 GF (HA off) | 1430-1450 Mb (14 cloudlets) | 1560-1580 Mb (15 cloudlets) |
| 2 GF (HA on) | 830-850 Mb (9 cloudlets) | 1030-1050 Mb (10 cloudlets) |
| 4 GF (HA on) | 1360-1380 Mb (14 cloudlets) | 1590-1610 Mb (16 cloudlets) |