Generic JMS Client with EAP/ActiveMQ: Difference between revisions
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
=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 | By default, ActiveMQ does not allow unauthenticated connections. A connection must be created for a specific user, providing appropriate 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: | For more details on using <tt>add-user.sh</tt>, see: | ||
Revision as of 21:14, 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 appropriate 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: