Guidelines for Using the list and get Subcommands for Monitoring

The underlying assumptions for using the list and get subcommands with dotted names are:

A list subcommand that specifies a dotted
name that is not followed by a wildcard (*)
lists the current node’s immediate children. For example, the following
subcommand lists all immediate children belonging to the server node:

list --monitor server

A list subcommand that specifies a dotted
name followed by a wildcard of the form .* lists a hierarchical
tree of child nodes from the specified node. For example, the following subcommand
lists all children of the applications node, their subsequent
child nodes, and so on:

list --monitor server.applications.*

A list subcommand that specifies a dotted
name preceded or followed by a wildcard of the form *dottedname or dotted * name or dottedname * lists
all nodes and their children that match the regular expression created by
the specified matching pattern.

A get subcommand followed by a .* or
a * gets the set of attributes and their values that belong
to the node specified.

For example, the following table explains the output of the list and get subcommands used with the dotted name for the resources node.

Table 8–4 Example Resources
Level Dotted Names

Subcommand

Dotted Name

Output

list --monitor

server.resources

List of pool names.

list --monitor

server.resources.connection-pool1

No attributes, but a message saying “Use get subcommand
with the --monitor option to view this node’s attributes
and values.”

get --monitor

server.resources.connection-pool1.*

List of attributes and values corresponding to connection pool attributes.