WildFly System Properties: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 43: Line 43:
Represents the value of the instance's public interface.
Represents the value of the instance's public interface.


==Standalone Node==
==jboss.bind.address for Standalone Node==


One common method of externalizing this operationally is to define it as a system property at the bottom of <tt>standalone.conf</tt>:
One common method of externalizing this operationally is to define it as a system property at the bottom of <tt>standalone.conf</tt>:

Revision as of 01:44, 12 February 2016

Internal

jboss.qualified.host.name

Relevance: WildFly 9

For a host named "ap1.modcluster.local" it is set to "ap1.modcluster.local"

jboss.host.name

Relevance: WildFly 9

For a host named "ap1.modcluster.local" it is set to "ap1"

jboss.server.name

Relevance: WildFly 9

For a host named "ap1.modcluster.local" it is set to "ap1"

jboss.node.name

Relevance: WildFly 9

jboss.node.name 

Set externally with -Djboss.node.name in the startup script.

Related:

jboss.server.config.dir

Used by:

jboss.bind.address

Represents the value of the instance's public interface.

jboss.bind.address for Standalone Node

One common method of externalizing this operationally is to define it as a system property at the bottom of standalone.conf:

...
JAVA_HOME="${JAVA_HOME} -Djboss.bind.address=192.168.1.15"

The same result can be achieved by specifying the system property as a -D argument for the start script:

./standalone.sh -Djboss.bind.address=192.168.1.10

jboss.bind.address.management