How about you use fabric to create multiple child instances with activemq profile? That said, fabric manage the instances and take care all of those stuff for you.
Yes that would be a real good thing to do but we have an old legacy N/W of brokers (multiple Apache ActiveMQ instances running on different servers and connected via N/W connectors using simple authentication and authorization) and these details are provided by client in a single property file. Need to migrate this infra to JBoss A-MQ 6.0. This property file contains all ports (TCP/HTTP/JMX/RMI), user credentials, N/W bridge details, queue/topic details etc. Client is not willing to move from this approach and want everything in one file which their support team can manage/maintain in production as needed.
Currently this property file is imported in activemq.xml using a bean like this and we can use these property in activemq.xml file.
<bean id="settings" class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer" >
<property name="location" value="file:///<HOME>/my.properties" />
<property name="searchSystemEnvironment" value="true" />
If there is any way to configure similarly in JBoss A-MQ 6.0 also?