FUSE Message Broker
  1. FUSE Message Broker
  2. MB-847

Allow for easy externalization of ActiveMQ configuration

    Details

    • Type: Enhancement Enhancement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: 5.4.2-fuse-02-00
    • Component/s: None
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      Currently many of the AMQ configuration files use the property activemq.base to load in other files, e.g.
      activemq.xml:

      activmeq.xml

      <property name="locations">
        <value>file:${activemq.base}/conf/credentials.properties</value>
      </property>      

      jetty.xml:

      jetty.xml

      <bean id="securityLoginService" class="org.eclipse.jetty.security.HashLoginService">
        <property name="name" value="ActiveMQRealm" />
        <property name="config" value="${activemq.base}/conf/jetty-realm.properties" />
      </bean>

      webconsole-embedded.xml:

      webconsole-embedded.xml

      <property name="locations">
        <value>file:${activemq.base}/conf/credentials.properties</value>
      </property>

      and others.
      In case where you want to externalize the entire ActiveMQ configuration into a folder that is not a sub folder of AMQ, there is the need to change multiple configuration files. This is error prone.

      In order to make the use of external AMQ configuration more easy to use, I suggest to
      1. introduce a new property called activemq.conf, which points to $

      {activemq.base}/conf by default in activemq script (if not already set on the shell)
      2. replace all occurences of ${activemq.base}

      /conf with {$activemq.conf} in all XML configuration files (including those in webapps/ folder)

      That way one only needs to set the property activemq.conf in order to point to an external AMQ configuration folder.

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            Timothy Bish added a comment -

            fixed, will be in the 5.6.0 release

            Show
            Timothy Bish added a comment - fixed, will be in the 5.6.0 release
            Hide
            Timothy Bish added a comment -

            Reopen so we can merge into next fuse 5.5.1 release

            Show
            Timothy Bish added a comment - Reopen so we can merge into next fuse 5.5.1 release

              People

              • Assignee:
                Timothy Bish
                Reporter:
                Torsten Mielke
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: