Appendix B Dotted Name Attributes for domain.xml

This appendix describes the dotted name attributes that can be used to address the MBean and its attributes. Every element in the domain.xml file has a corresponding MBean. Because the syntax for using these names involves separating names between periods, these names are called dotted names.

This appendix contains the following topics:

Top Level Elements

The following conditions must be adhered to for all top level elements in the domain.xml file:

Each server, configuration, cluster, or node agent must have a unique name.
Servers, configurations, clusters, or node agents cannot be named domain.
Server instances cannot be named agent.

The following table identifies the top level elements and the corresponding dotted name prefix.

Element Name	Dotted Name Prefix
applications	`domain.applications`
resources	`domain.resources`
configurations	`domain.configs`
servers	`domain.servers` Every server contained in this element is accessible as server-name. Where server-name is the value of the name attribute for the server subelement.
clusters	`domain.clusters` Every cluster contained in this element is accessible as cluster-name. Where cluster-name is the value of the name attribute for the cluster subelement.
node-agents	`domain.node-agents`
lb-configs	`domain.lb-configs`
system-property	`domain.system-property`

Two levels of aliasing are available:

The first level of alias allows access to attributes of server instances or clusters without going through the domain.servers or domain.clusters prefix. So, for example, a dotted name of the form server1 maps to the dotted name domain.servers.server1 (where server1 is a server instance).
The second level of alias is used to refer to configurations, applications, and resources of a cluster or a standalone server instance (target).

The following table identifies dotted names beginning with the server name, or cluster name, that are aliased to top level names under the domain:

Dotted Name	Aliased to	Comments
`target.applications.*`	`domain.applications.*`	The alias resolves to applications referenced by the `target` only.
`target.resources.*`	`domain.resources.*`	The alias resolves to all j`dbc-connection-pool`, `connector-connection-pool`, `resource-adapter-config`, and all other resources referenced by the `target`.

The following table identifies dotted names beginning with the server name, or cluster name, that are aliased to top level names within the configuration referenced by the server or cluster.

Dotted Name	Aliased to
`target.http-service`	`config-name.http-service`
`target.iiop-service`	`config-name.iiop-service`
`target.admin-service`	`config-name.admin-service`
`target.web-container`	`config-name.web-container`
`target.ejb-container`	`config-name.ejb-container`
`target.mdb-container`	`config-name.mdb-container`
`target.jms-service`	`config-name.jms-service`
`target.log-service`	`config-name.log-service`
`target.security-service`	`config-name.security-service`
`target.transaction-service`	`config-name.transaction-service`
`target.monitoring-service`	`config-name.monitoring-service`
`target.java-config`	`config-name.java-config`
`target.availability-service`	`config-name.availability-service`
`target.thread-pools`	`config-name.thread-pools`

Elements Not Aliased

A clustered instance should not be aliased. To get a system property for a clustered instance, the dotted name attribute you should use is as follows: domain.servers.clustered-instance-name.system-property , not clustered-instance-name.system-property.