Table of Contents
Advertisement
The list command is the progenitor of navigational capabilities of these three commands. If
you want to set or get attributes of a particular application server subsystem, you must know
its dotted name. The list command is the one which can guide you to find the dotted name of
that subsystem. For example, to find out the modified date (attribute) of a particular file in a
large file system that starts with /. First you must find out the location of that file in the file
system, and then look at its attributes. Therefore, two of the first commands to understand the
hierarchies in appserver are: * list "*" and <command>* list * --monitor. Consult the get
set or list commands manpages to identify the sorted output of these commands.
Server Lifecycle Commands
The server lifecycle commands are commands that create, delete, or start, stop a domain, or an
instance.
TABLE C–2
Command
create-domain
delete-domain
Appendix C • The asadmin Utility
The list command treats this complete dotted name as the complete name of a parent
■
node in the abstract hierarchy. Upon providing this name to list command, it simply
returns the names of the immediate children at that level. For example,list
server.applications.web-module will list all the web modules deployed to the domain
or the default server.
The get and set commands treat this complete dotted name as the fully qualified name
■
of the attribute of a node (whose dotted name itself is the name that you get when you
remove the last part of this dotted name) and it gets/sets the value of that attribute. This
is true if such an attribute exists. You will never start with this case because in order to
find out the names of attributes of a particular node in the hierarchy, you must use the
wildcard character *. For example,
server.applications.web-module.JSPWiki.context-root will return the
context-root of the web-application deployed to the domain or default server.
Server Lifecycle Commands
Definition
Creates the configuration of a domain. A domain is an administrative
namespace. Every domain has a configuration, which is stored in a set of files.
Any number of domains each of which has a distinct administrative identity
can be created in a given installation of application server. A domain can exist
independent of other domains. Any user who has access to the asadmin script
on a given system can create a domain and store its configuration in a folder of
choice. By default, the domain configuration is created in the
install_dir/domains directory. You can override this location to store the
configuration elsewhere.
Deletes the named domain. The domain must already exist and must be
stopped.
Server Lifecycle Commands
237
Advertisement
Chapters
Table of Contents
