GlassFish - World's first Java EE 7 Application Server


3. Create Instance(s)

This has two parts: 1) Create local file system for an instance 2) Register the new instance with DAS

3.1 Local File System for Instance
We may use the following file layout to remain backward compatible with GFv2.x.

nodeagents/<host-name>/
    || ---- agent
              || ---- config
                      | ---- das.properties
    || ---- <server-instance-1>
              ||---- config
              ||---- applications
              ||---- java-web-start
              ||---- generated
              ||---- lib
              ||---- docroot
    || ---- <server-instance-2>

3.2 Registration with DAS
create-instance command can be updated to register the newly created instance with DAS.

XXX Option --nodeagent will need to become optional.

Example:

% asadmin create-instance 
          --host <dashost> 
          --port <4848> 
          --user <admin> 
          --passwordfile <pass.txt> 
          --cluster <cluster1> 
          --systemproperties <HTTP_LISTENER_PORT=58294:HTTP_SSL_LISTENER_PORT=58297> 
          --createfilesystem=true <instance1>

XXX --createfilesystem is an optional option; it creates the file system locally
XXX We may save DAS's co-ordinates in das.properties if we want to allow "start-instance" without DAS (see bellow)

Similary, delete-instance command removes a server from domain.xml. We may introduce --deletefilesystem=true option to remove the files from local machine.

Note: create-instance/delete-instance are parallel to join-domain/leave-domain concepts discussed in the clustering document.

Topic Comment
3.1 Local File System for Instance In v2, node-agent had several other files, but in v3 we only need das.properties file
3.2 create-instance 1. Create the entries in domain.xml to represent the new instance. 2. Create the entries in the filesystem on the instance node for the new instance. Until 3.1 has a node agent, need a local asadmin command that runs on the node that will have the new instance. This command needs to ask the DAS to do #1, then do #2 locally. macro command(s) create-instance & create-instance-local OR create-instance --createfilesystem primitive commands: #1 _create-instance #2 _create-instance-filesystem
3.3 Offline config We need to continue to support offline config (see blog ). If --createfilesystem=false, create-instance command should only create the configuration in domain.xml without any errors. After user is done with all configuration changes in DAS, user should be able to use --createfilesystem=true with create-instance command to create the instance locally on the remote machine where the server instance is expected to physically run. create-instance command should be able to work with existing configuration already defined in domain.xml for the named instance. We may need to keep a property to avoid two instances being created for the same instance name