Host.xml: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
No edit summary
No edit summary
Line 19: Line 19:
3. The value that follows the final period (".") character in the <tt>[[WildFly System Properties#jboss.qualified.host.name|jboss.qualified.host.name]]</tt> system property, or the entire value if there is no final period (".") character.
3. The value that follows the final period (".") character in the <tt>[[WildFly System Properties#jboss.qualified.host.name|jboss.qualified.host.name]]</tt> 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.
4. The value that follows the period (".") character in the <tt>HOSTNAME<tt> environment variable for POSIX-based operating systems, the <tt>COMPUTERNAME</tt> environment variable for Microsoft Windows, or the entire value if there is no final period (".") character.


<font color=red>
<font color=red>
The following mechanism (would be preferred if it worked) does not work:
The following mechanism (would be preferred if it worked) does not work:


{{{
<pre>
<host name="${host.id:master}" xmlns="urn:jboss:domain:1.6">
<host name="${host.id:master}" xmlns="urn:jboss:domain:1.6">
     ...
     ...
</host>
</host>
}}}
</pre>


where "{{host.id}}" is defined in the startup script.
where "{{host.id}}" is defined in the startup script.
</font>
</font>

Revision as of 03:53, 12 February 2016



migrating from https://home.feodorov.com:9443/wiki/Wiki.jsp?page=Host.xml

Internal


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 as "user name" while authenticating against the Management Realm of the domain controller.

The host name can be overridden without modifying the configuration file. To ease administration and allow for the use of the same host configuration file on multiple hosts, the server uses the following precedence in determining the host name:

1. If set, the <host> element name 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.

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 "Template:Host.id" is defined in the startup script.