■Thelist command treats this complete dotted name as the complete name of a parent
nodein the abstract hierarchy. Upon providing this name to list command, it simply
returnsthe names of the immediate children at that level. For example,list
server.applications.web-modulewill list all the web modules deployed to the domain
orthe default server.
■Theget and set commands treat this complete dotted name as the fully qualied name
ofthe attribute of a node (whose dotted name itself is the name that you get when you
removethe last part of this dotted name) and it gets/sets the value of that attribute. This
istrue if such an attribute exists. You will never start with this case because in order to
ndout the names of attributes of a particular node in the hierarchy, you must use the
wildcardcharacter *. For example,
server.applications.web-module.JSPWiki.context-rootwill return the
context-rootof the web-application deployed to the domain or default server.
Thelist command is the progenitor of navigational capabilities of these three commands. If
youwant to set or get attributes of a particular application server subsystem, you must know
itsdotted name. The list command is the one which can guide you to nd the dotted name of
thatsubsystem. For example, to nd out the modied date (attribute) of a particular le in a
largele system that starts with /. First you must nd out the location of that le in the le
system,and then look at its attributes. Therefore, two of the rst commands to understand the
hierarchies in appserver are: * list "*"and <command>* list * --monitor. Consult the get
setor list commands manpages to identify the sorted output of these commands.
Server Lifecycle Commands
Theserver lifecycle commands are commands that create, delete, or start, stop a domain, or an
instance.
TABLEC–2 ServerLifecycle Commands
Command Denition
create-domain Createsthe conguration of a domain. A domain is an administrative
namespace.Every domain has a conguration, which is stored in a set of les.
Anynumber of domains each of which has a distinct administrative identity
canbe created in a given installation of application server. A domain can exist
independentof other domains. Any user who has access to the asadmin script
ona given system can create a domain and store its conguration in a folder of
choice.By default, the domain conguration is created in the
install_dir/domainsdirectory. You can override this location to store the
congurationelsewhere.
delete-domain Deletesthe named domain. The domain must already exist and must be
stopped.
ServerLifecycle Commands
AppendixC • Theasadmin Utilit y 237