Type: New Feature
Affects Version/s: None
Fix Version/s: None
I have received feedback from multiple sources about the usability weaknesses in asadmin. For example, the reviewer here (http://zeroturnaround.com/rebellabs/the-great-java-application-server-debate-glassfish/) mentions this:
"When looking into the "bin" folder, there were no startup scripts. So how do you start GlassFish? Actually they provide a megatool called "asadmin" that can perform various administrative tasks from starting the server to deploying an application. Basically, you can do everything with it, other than get it to make the coffee. It's a shell environment with commands and features. Some people hate it, some love it, I actually quite like it once I got used to it, although the beauty with regular startup or management scripts is that their intended behaviour is typically stated by the script name, however, asadmin hides everything from you. Realistically, you need to read some docs to get yourself going - Whaaaaat, I need to read docs to be able to start my server? Bah. Unlike Jetty or Tomcat, it's not as straightforward to get GlassFish up and running."
Here is another quote on the same issue:
"I really feel asadmin has shortcomings - it is so cumbersome to work with from the command line"
A simple solution to this problem is creating a set of wrapper scripts around asadmin geared towards beginners such as startup.sh, shutdown.sh, deploy.sh, etc that are more self-documenting.
Do let me know if anything needs to be explained further - I am happy to help.
Please note that these are purely my personal views and certainly not of Oracle's as a company.