Configuring a Remote HornetQ JMS Server as a Resource Adapter: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 9: | Line 9: | ||
=Overview= | =Overview= | ||
This article describes the configuration required to deploy a cluster of two HornetQ-based JMS nodes, running as messaging subsystems within EAP 6.4 instances, within of a third JBoss EAP 6.4 | This article describes the configuration required to deploy a cluster of two HornetQ-based JMS nodes, running as messaging subsystems within EAP 6.4 instances, within of a third JBoss EAP 6.4. The cluster will be deployed as resource adapter, and thus available to the MDBs deployed on that JBoss instance. | ||
Revision as of 02:37, 18 March 2017
External
Internal
Overview
This article describes the configuration required to deploy a cluster of two HornetQ-based JMS nodes, running as messaging subsystems within EAP 6.4 instances, within of a third JBoss EAP 6.4. The cluster will be deployed as resource adapter, and thus available to the MDBs deployed on that JBoss instance.