Host.xml: Difference between revisions
No edit summary |
No edit summary |
||
Line 41: | Line 41: | ||
=Sections= | =Sections= | ||
==<management>== | |||
==<domain-controller>== | |||
==<interfaces>== | |||
==<jvms>== | |||
==<servers>== | ==<servers>== | ||
==<profile>== |
Revision as of 04:26, 15 October 2016
Internal
Overview
This file contains configuration details for a specific physical host in a managed domain: the name of the host, network interfaces, socket bindings. This file is not present on standalone servers. The file's location is $JBOSS_HOME/domain/configuration/host.xml.
Host Name
The host name specified as <host name="..."> is relevant if when a subordinate host controller connects to a remote domain controller. The host controller will use the host name specified here as "user name" while authenticating against the Management Realm of the domain controller.
The host name can be overridden without modifying the configuration file. The server uses the following precedence in determining the host name:
1. If set, the name <host> element attribute in the host.xml configuration file.
2. The value of the jboss.host.name system property.
3. The value that follows the final period (".") character in the jboss.qualified.host.name system property, or the entire value if there is no final period (".") character.
4. The value that follows the period (".") character in the HOSTNAME environment variable for POSIX-based operating systems, the COMPUTERNAME environment variable for Microsoft Windows, or the entire value if there is no final period (".") character.
TODO, more research needed:
The following mechanism (would be preferred if it worked) does not work:
<host name="${host.id:master}" xmlns="urn:jboss:domain:1.6"> ... </host>
where "host.id" is defined in the startup script.