Is Externalization of various properties settings in JBoss A-MQ possible ?

Solution Unverified - Updated -

Issue

  • I need to run multiple instances of JBoss A-MQ 6.0 on a given server and noticed that we need to edit number of files to change ports/users etc. Given it is a manual process so its prone to error. Is there any standard way to externalize various properties settings in JBoss A-MQ 6.0?
  • Using fabric could be a real good solution, however a non fabric alternative is needed ?
  • I am ensuring following changes a different files. The openwire connector is available on 0.0.0.0:0 and with different "activemq.port" settings, I am able to connect to 2 instances separately and do message processing. What will help here is if all such properties can be defined in a single customer configuration file and then I need to change only that file rather than changing so many files. Also, if I need to define N/W bridges, simple authentication or authorization details (user group, username, password, queue names, topic names etc.) then I can update this single file and access those values using placeholders such as "${test}" in "/etc/activemq.xml".
  • Can the following properties can be customized using external properties files?
  1. Ensure users are available in "/etc/user.properties" file for given instance.

  2. Ensure following properties are set in "/etc/system.properties" for given instance.

activemq.jmx.user
activemq.jmx.password
org.osgi.service.http.port
activemq.port
activemq.jmx.url
  1. Ensure following settings are set in "/etc/org.fusesource.mq.fabric.server-default.cfg" for given instance.
broker-name
  1. Ensure following settings are set in "/etc/org.apache.karaf.shell.cfg" for given instance.
sshPort
  1. Ensure following settings are set in "/etc/org.apache.karaf.management.cfg" for given instance.
rmiRegistryPort
rmiServerPort
  1. Ensure following settings are set in "/etc/jetty.xml" for a given instance.
jetty.port
confidentialPort
  1. Ensure following settings are set in "/etc/org.apache.activemq.webconsole.cfg" (This is not needed for JBoss A-MQ 6.0 but needed in JBoss Fuse ESB 6.0 as this file still retains default ports.)
webconsole.jms.url
webconsole.jms.user
webconsole.jms.password
webconsole.jmx.url
webconsole.jmx.user
webconsole.jmx.password
  1. Ensure following settings are set in "/system/org/jboss/amq/mq-web-console/6.0.0.redhat-024/mq-web-console-6.0.0.redhat-024-mq-web-console.cfg" for a given instance. This file contains default ports.
webconsole.jms.url
webconsole.jms.user
webconsole.jms.password
webconsole.jmx.url
webconsole.jmx.user
webconsole.jmx.password

Environment

  • Red Hat JBoss A-MQ
    • 6.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.