Generic JMS Client with EAP/ActiveMQ: Difference between revisions
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
=Authentication= | =Authentication= | ||
By default, ActiveMQ does not allow unauthenticated connections. A connection must be created for a specific user, providing credentials. The user must be added to the "ApplicationRealm", and it must have the "guest" role - it must be associated with the "guest" group when creating the user. That identity will be used to create JMS connections. | |||
For more details on using <tt>add-user.sh</tt>, see: | |||
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | |||
:<tt>[[add-user.sh]]</tt> | |||
</blockquote> | |||
=Code= | =Code= | ||
{{External|https://github.com/NovaOrdis/playground/tree/master/jboss/activemq/simplest-activemq-jms-client}} | {{External|https://github.com/NovaOrdis/playground/tree/master/jboss/activemq/simplest-activemq-jms-client}} | ||
Revision as of 21:13, 7 February 2017
Internal
Overview
Also see:
Classpath
The classes required by the remoting and ActiveMQ client-side logic are available in $JBOSS_HOME/bin/client/jboss-client.jar so an EAP7/ActiveMQ client typically includes that JAR on its classpath.
Authentication
By default, ActiveMQ does not allow unauthenticated connections. A connection must be created for a specific user, providing credentials. The user must be added to the "ApplicationRealm", and it must have the "guest" role - it must be associated with the "guest" group when creating the user. That identity will be used to create JMS connections.
For more details on using add-user.sh, see: