GlassFish provides 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. But as you know, more functions = more resources.
To get your GlassFish 3 server in the cloud, simply:
1. Log onto
2. Click Create Environment,
3. Pick GlassFish 3 for your application servers as shown in the picture below:
Once the environment is created, you can click Open in browser button next to the GlassFish server in the environment (expand the environment in the Environments pane at the top of the screen):
Then you can upload the Java application WAR package and deploy it to the environment. You can open Glassfish admin page from jelastic dashboard:
Admin page will be available in a new tab.
- Jelastic uses gfcluster as a cluster, so if you want to modify something, please apply changes to gfcluster.
- If you have Public IP attached the default GlassFish admin panel port (4848) can be changed in domain.xml configuration file (server folder) by adding the following string:
<http-listener id="admin-listener" port="4848" address="0.0.0.0" default-virtual-server="__asadmin" server-name="" />
- Glassfish Derby Internal database in Jelastic is switched off by default in order to decrease the resource consumption.
|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)|