How to configure HawtIO ActiveMQ 5.10.0 interface?

Question

I am using ActiveMQ 5.9.0, which has an awesome HawtIO interface. Therefore, when 5.10.0 arrived, I also transferred my system. Now I see that the HawtIO interface does not exist inside it ... It just disappeared from the webapps folder from 5.9.0 to 5.10.0, so I tried the ActiveMQ and HawtIO tutorial , but it does not work ... How to configure the interface?

Answer 1

Alternatively, you can use HawtIO as a stand-alone web application that connects to ActiveMQ through Jolokia (up to 5.9 ways to do this).

• Download the standalone HawtIO banner here: http://hawt.io/getstarted/index.html
• Run the jar on the ActiveMQ server: java -jar hawtio-app-1.4.37.jar (put the command in a .bat-script and add a scheduled task if you want it to start when it starts.)
• Go to http: // your server : 8080 / hawtio
• Create a new connection, give it a name, use localhost as the host, 8161 as the port, and api/jolokia as the path.

Plug and enjoy!

Answer 2

As stated in Eric Williams, answer:

• Unzip the hawt-io war into the ActiveMQ \ webapps folder (e.g. hawtio).

• modify jetty.xml to include this webapp as a folder

   <bean class="org.eclipse.jetty.webapp.WebAppContext"> <property name="contextPath" value="/hawtio" /> <property name="resourceBase" value="${activemq.home}/webapps/hawtio" /> <property name="logUrlOnStart" value="true" /> </bean> 

• In the standalone default installation of 5.10.0, we also had to add three security parameters to enable broker's protection. This can be done in the activmemq or activemq.bat file. Add these parameters to the ACTIVEMQ_OPTS variable:

  • -Dhawtio.realm = ActiveMQ
  • -Dhawtio.role = admins
  • -Dhawtio.rolePrincipalClasses = org.apache.activemq.jaas.GroupPrincipal

• We did not need to remove the slf4j byte, it was not there.

Answer 3

Yes, I'm not quite sure why they decided to do this, because it was a pretty big feature that they advertised.

In any case, it’s quite simple to configure yourself by downloading hawt-io and installing it, as it was in 5.9, if you cannot get an autonomous method of work.

You will need to unzip (or at least the way I did it) WAR, and configure the jetty.xml file as it was configured in 5.9, enable hawt.io as an application.

If I remember, I think that I also ran into some class loading conflicts due to some classes that are part of hawt.io, which were newer than what was installed with the broker.