You can use upstream documentation as a source: http://docs.jboss.org/hornetq/2.3.0.Final/docs/user-manual/html/configuring-transports.html#d0e3370

Configuration examples (this will be long):

Use upstream as basis please. I think the attribute description is quite good there. Here are specific examples and notes to individual parts.


- For netty SSL (Showing only additional properties. All properties for normal Netty acceptors are also available):

<netty-acceptor name="netty" socket-binding="messaging">
    <param key="ssl-enabled" value="true"/>
    <param key="key-store-password" value="[keystore password]"/>
    <param key="key-store-path" value="[path to keystore file]"/>
</netty-acceptor>

for 1-way SSL and

<netty-acceptor name="netty" socket-binding="messaging">
    <param key="ssl-enabled" value="true"/>
    <param key="need-client-auth" value="true"/>
    <param key="key-store-password" value="[keystore password]"/>
    <param key="key-store-path" value="[path to keystore file]"/>
    <param key="trust-store-password" value="[truststore password]"/>
    <param key="trust-store-path" value="[path to truestore file]"/>
</netty-acceptor>

for 2-way SSL (i.e. mutual authentication between server and client).

Take attribute description from upstream documentation please. Parameter "need-client-auth" is not described there, but you can use just "Require 2-way (ie mutual authentication) for client connections".

I wouldn't bother with connector examples, they are pretty much same and the attribute description explains the difference between using these attributes in connectors and acceptors.


- Netty HTTP

First you need to define socket binding for new HTTP port:

<socket-binding mame="messaging-http" port="7080" />

Then you bind acceptor/connector to that socket-binding together with attribute http-enabled set to true:

<netty-connector name="netty" socket-binding="messaging-http">
    <param key="http-enabled" value="true"/>
</netty-connector>

<netty-acceptor name="netty" socket-binding="messaging-http">
    <param key="http-enabled" value="true"/>
</netty-acceptor>

Use the attribute description from upstream documentation again please, all other attributes are valid, though only http-enabled is required for this.

Please add a warning that automatic client failover is not supported for clients connecting through Netty HTTP transport.

Also add a note that this transport doesn't allow to reuse standard HTTP port 8080 (HornetQ throws BindException when you try that). You can use Netty Servlet transport for tunneling HornetQ connections through standard HTTP port (see below).


- Netty Servlet

The snippet with the servlet configuration can be used as is in there.

Acceptor will be same as is in upstream documentation, but configuration file is standalone.xml/domain.xml instead of hornetq-configuration.xml.

Connector example will change to:

<netty-connector name="netty-servlet" socket-binding="http">
    <param key="use-servlet" value="true"/>
    <param key="servlet-path" value="/messaging/HornetQServlet"/>
</netty-connector>

Again, configuration file is standalone.xml/domain.xml instead of hornetq-configuration.xml.

The example with SSL active will be:

<netty-connector name="netty-servlet" socket-binding="https">
   <param key="use-servlet" value="true"/>
   <param key="servlet-path" value="/messaging/HornetQServlet"/>
   <param key="ssl-enabled" value="true"/>
   <param key="key-store-path" value="path to a key-store"/>
   <param key="key-store-password" value="key-store password"/>
</connector>

(Ignore the part under SSL example - the paragraph starting with "You will also have to configure the Application server to use a KeyStore...". That part is not relevant for EAP.)

Please add a warning that automatic client failover is not supported for clients connecting through http tunneling servlet.

One more note: in the upstream documentation in the attribute description please ignore host and port. These are replaced by socket-binding attribute in netty-connector / netty-acceptor elements in EAP config.

Thanks Nidhi!