WildFly Interface Configuration: Difference between revisions
Jump to navigation
Jump to search
m (Ovidiu moved page WildFly Public Interface Configuration to WildFly Interface Configuration without leaving a redirect) |
|||
(2 intermediate revisions by the same user not shown) | |||
Line 6: | Line 6: | ||
=Management= | =Management= | ||
Also see: | |||
{{Internal|WildFly_Networking_Concepts#Management_Interface|WildFly Networking Concepts - Management Interface}} | |||
=Public= | =Public= | ||
Line 43: | Line 47: | ||
=Private= | =Private= | ||
Also see: | |||
{{Internal|WildFly_Networking_Concepts#Private_Interface|WildFly Networking Concepts - Private Interface}} | |||
Can be configured setting jboss.bind.address.private as shown here: {{Internal|WildFly_System_Properties#jboss.bind.address.private|jboss.bind.address.private}} | |||
=Unsecure= | =Unsecure= | ||
Also see: | |||
{{Internal|WildFly_Networking_Concepts#Unsecure_Interface|WildFly Networking Concepts - Unsecure Interface}} |
Latest revision as of 18:13, 14 March 2017
Internal
Overview
Management
Also see:
Public
The public interface is the network interface the standalone server node (or domain server nodes) use to receive business payload.
Also see:
The interface is declared in standalone.xml as:
<interfaces> ... <interface name="public"> <inet-address value="${jboss.bind.address:127.0.0.1}"/> </interface> </interfaces>
or in domain.xml as:
<interfaces> ... <interface name="public"/> ... </interfaces>
In the case of domain mode, the actual specifics are host dependent, so that is why the address is declared in a host-dependent manner.
For more details, see:
Private
Also see:
Can be configured setting jboss.bind.address.private as shown here:
Unsecure
Also see: