Managing Glassfish instances in a non-centralized way may prove itself to be a real pain in the ass, even with as few as four (4) nodes. One solution that has been quite simplified on version 3.1 (it existed in version 2.x but you had to deploy node-agents) is the usage of SSH as a channel to perform administration operations on remote instances. This post compreehends a short but working version of the steps described in this blog post.
- Linux system (actually, Glassfish runs on every platform with a suitable JRE)
- SSH server up and running
- Have a user configured in all desired nodes (in our case, dummy)
- Glassfish 3.1.1 as version 3.1.2 forces secure-admin mode which has brought several issues to our current testbed. Actually, we had to reinstall and reconfigure the entire scenario. So if you’re willing to install/upgrade to a newer version, do it at your own risk. You’ve been warned!
- Be sure that you have a clean Glassfish install on what is going to be your Domain Admin Server (DAS).
You can authenticate your DAS against your nodes with one of two methods:
- Password authentication
- Public key authentication
We’ll choose the last one, since it’s easier to maintain. Let’s start by assuming a node named node1.
$GLASSFISHROOT/bin/asadmin setup-ssh node1
If you don’t have a key-pair, the command above will give you the option to create one. If this is your case, be ready to provide your user password. Repeat the same command when the process is finished.
Also, be sure that the key is present in the file /home/dummy/.ssh/authorized_keys2 of the node node1, since this script will wrongly put it into authorized_keys, which is used for SSH protocol version 1 and not version 2, the most widely spread.
cat authorized_keys >> authorized_keys2
Install Glassfish remotely
asadmin install-node –installdir /home/cmlabs/ node1
Create SSH nodes
asadmin create-node-ssh –nodehost node1 –installdir /home/dummy node1
Configure cluster and deploy applications
Right now, you’re ready to create one or several node clusters. I mean, if you have executed the steps above in a handful of nodes, of course! Just point your browser to http://das_address:4848 and head up to the Clusters on the left-most pane (tree).
Be sure to setup a new configuration for each cluster and include some nodes in it. The rest of the process is quite trivial. Just remember that when you’re creating resources such as JDBC, JMS and such, you should always define the target, which may be a node, a cluster or several clusters.
- asadmin commands over SSH fail – a workaround is to repeat step Setup authentication.