We need to be able to configure the product statically. We need to be able to build an ISO image and install it and have it "work" when the machine boots up. This would be true for many "productized" distributions that a developer might want to create.
Forcing runtime configuration makes many of these tasks difficult or impossible.
--Kevin
From: John Clingan [mailto:john.clingan_at_oracle.com]
Sent: Thursday, May 17, 2012 2:14 PM
To: users_at_glassfish.java.net
Subject: Re: Static configuration of Glassfish
Kevin, you really want to use asadmin IMHO. Keep in mind that asadmin has a multimode, where you can run multiple commands with one invocation of asadmin (and the JVM it runs in).
On May 17, 2012, at 1:24 PM, Sathyan Catari wrote:
Please see inline..
Thanks
Sathyan
On 5/17/12 11:55 AM, Kevin Regan wrote:
We have a build and install system where starting up Glassfish (v3.1.2) in order to configure it would be problematic. Is it possible to do all Glassfish configuration statically by directly modifying configuration files?
It is possible, but not officially tested/supported. It is strongly recommended to use the interfaces(console, admin commands, REST, JConsole etc.,) available in the product binaries to access these configuration files.
Are there any parts of the configuration or deployment process that absolutely require the use of the asadmin command and a running Glassfish process? Also, is there documentation available for how to configure Glassfish through its configuration files?
Sincerely,
Kevin Regan