Chapter 9. Setting up AMQ Broker for HawtIO Online with Jolokia

In the deploymentPlan section, add the jolokiaAgentEnabled and managementRBACEnabled properties and specify values, as shown below.

apiVersion: broker.amq.io/v1beta1
kind: ActiveMQArtemis
metadata:
  name: ex-aao
spec:
  deploymentPlan:
    size: 4
    image: registry.redhat.io/amq7/amq-broker-rhel8:7.13
    ...
    jolokiaAgentEnabled: true
    managementRBACEnabled: false

apiVersion: broker.amq.io/v1beta1
kind: ActiveMQArtemis
metadata:
  name: ex-aao
spec:
  deploymentPlan:
    size: 4
    image: registry.redhat.io/amq7/amq-broker-rhel8:7.13
    ...
    jolokiaAgentEnabled: true
    managementRBACEnabled: false

jolokiaAgentEnabled Specifies whether HawtIO Online can discover and display runtime data for the brokers in the deployment. To use HawtIO Online, set the value to true.

managementRBACEnabled Specifies whether role-based access control (RBAC) is enabled for the brokers in the deployment. You must set the value to false to use HawtIO Online because it uses its own role-based access control.

Switch to the project in which you previously created your broker deployment.

oc project <project_name>

oc project <project_name>

Apply the changes to the CR instance by running the following command:

oc apply -f <path/to/custom_resource_instance>.yaml

oc apply -f <path/to/custom_resource_instance>.yaml