WildFly Networking Concepts: Difference between revisions
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 41: | Line 41: | ||
The concept was introduced in EAP 7, to provide a way to JGroups to communicate over an interface that is not exposed publicly. | 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= | =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= | =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:
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:
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:
Unsecure Interface
Details on how to configure the unsecure interface can be found here:
Socket Binding Group
Each socket binding group has a name which is used various other parts of the configuration to refer to it.