dev@glassfish.java.net

Update on new GlassFish domain creation process & modified template structure

From: alok <alok.k.jain_at_oracle.com>
Date: Mon, 21 Jan 2013 21:12:24 +0530

  Hi All,


The Glassfish domain creation process has been updated to the similar
process followed in Oracle FMW Platform. Now the domain can be built
through a jar template whose location can be pass via /--template/
argument of /create-domain/ command.

This domain creation process addresses few of the pending issues :

    * This feature allow various nucleus-based products to have
      different files in the domain rather than it being hard-coded.
    * Support the ability to use arbitrary domain properties when domain
      is created.
    * Allow user to pass the jar template from any location instead of
      picking the configuration files from a fixed location... etc


Refer below link for more details on Domain Templating feature:
http://aseng-wiki.us.oracle.com/asengwiki/display/GlassFish/GlassFish4.0+Domain+Templating+One+Pager

We have also modified the Nucleus & GlassFish packaging to create jar
templates, and using these templates to create the default domain
(/domain1/) in Nucleus & Appserver distributions.
*_
Nucleus Template:_* Added a new module (/nucleus\admin\template/) to
create Jar template (/nucleus-domain.jar/ ). This module has files
specific to nucleus template and the generated template jar placed at
/nucleus\common\templates\gf/ inside the nucleus artifact.

*_Appserver Template:_ *Added a new module (/appserver\admin\template/)
to create Jar template (/appserver-domain.jar/). This module has files
specific to appserver template. During build process it uses
/nucleus-domain.jar/. The generated template jar placed at
/glassfish\common\templates\gf/ inside the appserver artifacts. _*

  Points:
*_

    * Currently we are supporting both the existing and the new domain
      creation functionality.
    * Support for old usage will go away with in the next 2 weeks, and
      if you rely on custom templates, they'll have to be converted.
    * The old artifacts will be removed at the same time the support
      of old usage is discontinued.


Thanks,
Alok