Fuse ESB Enterprise comes with MQ out of the box.
The activemq-web-console is though not installed by default, and you would need to do that.
From the latest 7.0.2 esb-full I do this very easily as follows
FuseESB:karaf@root> features:install activemq-web-console FuseESB:karaf@root> web:list ID State Web-State Level Web-ContextPath Name [ 216] [Active ] [Deployed ] [ 60] [/activemqweb ] activemq-web-console (5.5.1.fuse-70-097)
And the web console is accessible at: http://localhost:8181/activemqweb
If you upgrade to 7.0.2, then make sure to read the release notes about the security changes
Thanks for solution davsclaus.Any information on the same line with regards to Fuse MQ and its console.Need to do a POC with Fuse Mq and Fuse ESB.If thers is a suggestion or advice,it would really be a great help.
Can you be more specific what you mean? Both Fuse ESB and MQ Enterprise comes with ActiveMQ and the ability to install the activemq-web-console. All from within the console (aka Karaf shell).
I want to deploy a route as mentioned in the example.A simple timer route as follows:
Have activated the activemq web console.have copied camel-timer.xml to the deploy folder of Fuse MQ Enterprise.But unable to see any queues getting created through the console.I am using FuseMQEnterprise-7.0.0.
Also when i try to access the console to see the queues created there are no queues created .
FuseMq_console.JPG 98.3 KB
Ah you need to install Camel first
features:install camel features:install camel-jms features:install activemq-camel
And then you can copy the file to the deploy folder.
But still no luck even after installing camel.I have deployed the camel-timer.xml in the deploy folder.But no queues in the console.
The same scenario is working fine with apache servicemix and a queue is getting created and visible thru the console.
And what do you see in the log? Maybe some error?
The log is in the data/log directory.
And what is the bundle status for your deployed file? eg if you run
What does it say in the row for your deployed file?
Thanks davsclaus .
Now the FuseMq console is working fine.Actually the error was a parsing exception as I was passing a whole xml file as input to the queue.The bundle was active,but no queues created in the console as the input was a xml file.
So any limitations on the format of input send to the Mq?
The limitations is what the JMS spec limits.