ActiveMQ Web Console

When an ActiveMQ broker is running, an ActiveMQ Web Console is automatically created in the same VM or container. Similarily, starting an ActiveMQ Web Console with no configuration specified will create a broker embedded in the same VM or container. However, to increase reliability, you may wish to run the Web Console in a separate container from the broker.

In the Talend Runtime, the ActiveMQ Web Console is pre-configured to connect to a broker running within another Talend Runtime via tcp. So by default, it does not create its own embedded broker.

The pre-configured properties are enabled when installing the Talend Runtime and are in the <container>/etc/org.apache.activemq.webconsole.cfg file:

webconsole.type=properties
            webconsole.jms.url=tcp://localhost:61616
            webconsole.jmx.url=service:jmx:rmi:///jndi/rmi://localhost:1099/karaf-trun
            webconsole.jmx.user=tesb
            webconsole.jmx.password=tesb

Where:

• webconsole.jms.url is the URL of the broker
• webconsole.jmx.url is the JMX URL of the Talend Runtime.

In order to install the Web Console to a container, enter:

karaf@trun> feature:install activemq-web-console

This will install and start the Web Console normally accessible at http://localhost:8040/activemqweb but dependent on your configuration. See Configuring ActiveMQ Web Console for the configuration details.

• To connect to a standalone broker from a Web Console in a container, the configuration details in <container>/etc/org.apache.activemq.webconsole.cfg will need to be updated. The default, local Web Console for a standalone broker is at http://localhost:8161/admin/.

• If the default Talend configuration is commented out or deleted, a broker will start in the local container and connect to it (an error will be shown if a broker is already running).