Red Hat AMQ 6
As of February 2025, Red Hat is no longer supporting Red Hat AMQ 6. If you are using AMQ 6, please upgrade: Migrating to AMQ 7.Ce contenu n'est pas disponible dans la langue sélectionnée.
5.2. Example Camel ActiveMQ Component Configuration
Overview Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
This section describes how to initialize and configure a sample Camel ActiveMQ component instance, which you can then use to define ActiveMQ endpoints in a Camel route. This makes it possible for a Camel route to send or receive messages from a broker.
Prerequisites Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
The
activemq-camel
feature, which defines the bundles required for the Camel ActiveMQ component, is not installed by default. To install the activemq-camel
feature, enter the following console command:
JBossAMQ:karaf@root> features:install activemq-camel
JBossAMQ:karaf@root> features:install activemq-camel
Sample Camel ActiveMQ component Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
The following Spring XML sample shows a complete configuration of a Camel ActiveMQ component that has both SSL/TLS security and JAAS authentication enabled. The Camel ActiveMQ component instance is defined to with the
activemqssl
bean ID, which means it is associated with the activemqssl
scheme (which you use when defining endpoints in a Camel route).
Sample Camel route Copier lienLien copié sur presse-papiers!
Copier lienLien copié sur presse-papiers!
The following Camel route defines a sample endpoint that sends messages securely to the
security.test
queue on the broker, using the activemqssl
scheme to reference the Camel ActiveMQ component defined in the preceding example: