I have been a Tomcat guy for the longest time but from time to time I like to play with the other guys software so it was either Jetty or Glassfish. I choose Glassfish. I’ve used Glassfish before for development testing and running rails but have not had any real J2ee apps running inside. Let’s have a look at the installation procedures for Glassfish and what you get after a few minutes of clicking.
Glassfish can be downloaded from https://glassfish.dev.java.net/downloads/v2.1-b60e.html we are going to use the latest stable (production ready) build of v2.1 b60.
I’m running this on a Linux (Centos) server so here are the steps to install and setup Glassfish WITH the cluster configurations:
[root@heimdull]# java -Xmx256m -jar glassfish-installer-v2.1-b60e-linux-ml.jar [root@heimdull]# cd glassfish [root@heimdull]# chmod -R +x lib/ant/bin [root@heimdull]# lib/ant/bin/ant -s setup-cluster.xml bla bla bla .... BUILD SUCCESSFUL Total time: xx seconds
Before we configure some custom settings lets just get this thing started…
[root@heimdull]# export PATH=~/glassfish/bin:$PATH [root@heimdull]# asadmin start-domain
Now you can access the administration console at http://localhost:4848/ by default the server does NOT bind to localhost but 0.0.0.0 so if you do not have a firewall you can access the console from outside the server too.
PS. There is a issue where the admin console might keep logging you out and asking for your credentials on every click. This is a cookie problem. Clear your browser cookies and you should be fine.
Change admin password
If you want to change the default admin user password (which is adminadmin) run the following command:
[root@heimdull]# asadmin change-admin-password --user=admin
Creating the cluster
Go to http://localhost:4848 and login. After this click on the Clusters menu option and select new, name the cluster something like my-cluster and click ok. You have now created the shell configuration for our cluster.
Now lets repeat the installation process on the cluster node. After you have installed Glassfish on the “node-agent” you are going to run a command to connect this server to the running admin-node that we installed in the initial installation steps. (Do not start the domain on the node-agent before it is connected to the admin server)
[root@heimdull]# asadmin create-node-agent --host admin-node --port 4848 --user admin my-cluster-agent-1 [root@heimdull]# asadmin start-node-agent my-cluster-agent-1Please enter the admin user name>adminRedirecting application output to /opt/glassfish/nodeagents/slave.local/agent/logs/server.logCommand start-node-agent executed successfullPlease enter the admin user name>admin Please enter the admin password>password Please enter the master password [Enter to accept the default]:> Redirecting output to /opt/glassfish/nodeagents/slave.local/agent/logs/server.log Redirecting application output to /opt/glassfish/nodeagents/slave.local/agent/logs/server.log Command start-node-agent executed successfully.
You now have a running cluster of 1 node. Login to the admin console and have a look, cluster of one, nice!
Create the server instance
You do now need to create the server instance which will be running in the cluster. Click on the clusters menu and select my-cluster. Now click the Instances menu button and click new.
Name the instance instance-1 and select the newly added node agent.
You now have the following components running/installed:
– (DAS) Domain Admin Server: This is the server that will controller the “cluster”.
– (NA) Node agent: All members of the cluster needs a nodeagent that connects to the admin server. The nodeagent needs to be started on the cluster member before the admin server can do any monitoring/administration of the member.
– (SI) Server Instance: This is where all the action is, this is the actual “server” that will be added to the server and this is where you application will be running.