Remoting WildFly Subsystem Configuration

Internal

• WildFly Configuration
• Remoting Subsystem

Overview

WildFly 9

<subsystem xmlns="urn:jboss:domain:remoting:3.0">
    <endpoint worker="default"/>
    <http-connector name="http-remoting-connector" connector-ref="default" security-realm="ApplicationRealm"/>
</subsystem>

EAP 6.4

<subsystem xmlns="urn:jboss:domain:remoting:1.2">
    <connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/>
</subsystem>

<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
    ...
    <socket-binding name="remoting" port="4447"/>
    ...
</socket-binding-group>

Schema

https://github.com/wildfly/?

TODO: Link to .xsd.

Configuration Elements

<endpoint>

The Remoting endpoint uses the XNIO Worker declared and configured by the io subsystem. The XNIO worker's configuration is described here: io subsystem worker configuration.

<connector>

security-realm

The presence of the 'security-realm' attribute in the remoting connector configuration triggers enabling of authentication within the remoting service

<http-connector>

The connector-ref is the name of the Undertow http-listener, so if the name of that connector changes, the Remoting reference should also change.