WildFly Networking Concepts: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(10 intermediate revisions by the same user not shown)
Line 1: Line 1:
=Internal=
=Internal=


* [[WildFly_Concepts#Networking_Concepts|WildFly Concepts]]
* [[WildFly_Concepts#Concepts|WildFly Concepts]]
* [[WildFly Domain Mode Concepts#WildFly_Networking_Concepts|WildFly Domain Mode Concepts]]


=Management Interface=
The management interface is declared, and named as such, in the <tt><interfaces></tt> section of the server's configuration file:


=Management Interface=
<pre>
...
<interfaces>
    <interface name="management"/>
    ...
</interfaces>
...
</pre>


For more details, see:
For more details, see:
Line 11: Line 22:
:[[WildFly Management Interfaces]]
:[[WildFly Management Interfaces]]
</blockquote>
</blockquote>
=Public Interface=
The public interface is declared, and named as such, in the <tt><interfaces></tt> section of the server's configuration file:
<pre>
...
<interfaces>
    ...
    <interface name="public"/>
</interfaces>
...
</pre>
Details on how to configure the public interface can be found here: {{Internal|WildFly Interface Configuration#Public|Public Interface Configuration}}
=Private Interface=
The concept was introduced in EAP 7, to provide a way to JGroups to communicate over an interface that is not exposed publicly.
Details on how to configure the private interface can be found here: {{Internal|WildFly Interface Configuration#Private|Private Interface Configuration}}
=Unsecure Interface=
Details on how to configure the unsecure interface can be found here: {{Internal|WildFly Interface Configuration#Unsecure|Unsecure Interface Configuration}}
=Socket Binding Group=
Each socket binding group has a ''name'' which is used various other parts of the configuration to refer to it.

Latest revision as of 20:15, 7 July 2017

Internal

Management Interface

The management interface is declared, and named as such, in the <interfaces> section of the server's configuration file:

...
<interfaces>
    <interface name="management"/>
    ...
</interfaces>
...

For more details, see:

WildFly Management Interfaces

Public Interface

The public interface is declared, and named as such, in the <interfaces> section of the server's configuration file:

...
<interfaces>
    ...
    <interface name="public"/>
</interfaces>
...

Details on how to configure the public interface can be found here:

Public Interface Configuration

Private Interface

The concept was introduced in EAP 7, to provide a way to JGroups to communicate over an interface that is not exposed publicly.

Details on how to configure the private interface can be found here:

Private Interface Configuration

Unsecure Interface

Details on how to configure the unsecure interface can be found here:

Unsecure Interface Configuration

Socket Binding Group

Each socket binding group has a name which is used various other parts of the configuration to refer to it.