WildFly Interface Configuration: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
m (Ovidiu moved page WildFly Public Interface Configuration to WildFly Interface Configuration without leaving a redirect)
No edit summary
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}}


=Unsecure=
=Unsecure=
Also see:
{{Internal|WildFly_Networking_Concepts#Unsecure_Interface|WildFly Networking Concepts - Unsecure Interface}}

Revision as of 17:42, 14 March 2017

Internal

Overview

Management

Also see:

WildFly Networking Concepts - Management Interface

Public

The public interface is the network interface the standalone server node (or domain server nodes) use to receive business payload.

Also see:

WildFly Networking Concepts - Public Interface

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:

jboss.bind.address for Standalone and Domain Mode

Private

Also see:

WildFly Networking Concepts - Private Interface

Unsecure

Also see:

WildFly Networking Concepts - Unsecure Interface