GlassFish 3.1: New Features in Admin Console


Today is the FCS of GlassFish 3.1,  there must be LOTS of blogs and screencast for this release,  the best place to check that out  is of course the Aquarium.  Everyone in the team is really excited about this release.

Just like any previous release,  I love telling everyone about all the new features that  JasonSrini,  Sumasri and I myself have worked so hard for the last 10 months to be included in the 3.1 Admin Console.   Among all these features,  I am going to list out the major ones.   Some of you who have used GlassFish v2 clustering  will like this familiar look and feel,  page layout etc. so that it will be really easy to use the Admin Console when you upgrade from v2  to GlassFish 3.1.    And for those who has only use GlassFish v3,  you should find that the additional support for clustering in the console help you tremanously for configuring clusters and other functions related to it. 

Checkout my other blog or the screencast that shows you how you can install GlassFish 3.1,  setup up remote systems,  create cluster and test an application deployed to the cluster, all in less than 12 minutes.

For the new features,  Lets start counting ...

1.  Listing,  Create, Edit and Deleting  Nodes.

In GlassFish 3.1,  a Node is a configuration object in the DAS that represents a GlassFish Installation on a host.  There are 2 types of nodes,  SSH nodes and CONFIG nodes.  You can list, create, delete or convert the nodes in the Admin Console.   This Blog by Joe  talks about this in great details.










2.  Listing,  Create, Edit and Deleting  Cluster.

After you have created the Node,  you can then create a Cluster,  with any number of remote or local instances within GUI.   And of course,  all the related functions needed for a cluster,  such as Application deployment,  Resources management,  Properties,  JMS Physical Destination etc.  are all part of the clustering support in the Admin Console.









3.  Standalone Instances support. 

An instance can be part of a cluster, or it can be a standalone instances.  Just like a cluster,  you can specify the standalone instance as a target for application deployment or  resources management.   Standalone instance also has a 'set of tab' that goes with it for additional functions such as monitoring,  properties setting etc.










4.  Application Deployments support Target

Application Deployment will prompt you to specify a target if there is any stanalone instances or clusters exist in the system.  The application listing tables also show you the # of targets that this application is dployed to, and allows you to modify the target or virtual servers AFTER the application is deployed.
If there is no standalone instance or cluster present,  the UI will be exactly like in v3, so that user dosn't need to bother with target.








5.  Application Versioning Support

Application Versioning is a new feature in 3.1.  If the application is deployed with an existing application name, followed by ":" and some other modifier,  eg, "hello:beta",  this newly  deployed application will be considered as the same application, causing the previous version 'disabled'.   You can have many version of the application,  but only one version will be 'enabled' at any one time.





6.    Support of  Password Aliasing
 
Based on request from the community and to faciliate the SSH authentication of  Nodes,  Admin Console now supports the passowrd aliasing  command.   You can now create, list,  edit and delete  Password Aliasing in the console.









7.  MultiConfig support

Since there will be more than "server-config" in the system,  as a result of creating cluster or standalone instances,  Admin Console supports multiple configs.  All the config will be listed under the Configurations tree node, and user can also copy an existing configuration by using the 'New' button in the listing table.
The table also lists all the instances or cluster that reference each config.












8.  Recover Transactions Support

You can now use Admin Console to recover transactions of a stopped instance by specifying a running instance.









9.  Resource Adapter Config Creation Enhancement

User can now specify the resource Adapter name without deploying that adapter first,   this allows better work flow for Resource Adapter.




10.  New Configuration pages

With the introduction of cluster,  there are a couple configuration page that is newely added.  This includes GMS,  Availability Services and System Properties showing you the overriden values for each instance.


















I hope that you are as excited about all the new features in 3.1 Admin Console  as  I am.   So, make sure you download GlassFish 3.1 ,  give it a try and provide your valuable feedback.





Comments:

Post a Comment:
Comments are closed for this entry.
About

anilam

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today