- Posted In
- Red Hat JBoss AMQ
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?
Maybe using fabric 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 see if we can use 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.
If there is any way to configure similarly in JBoss A-MQ 6.0 also?
This will help us immediately and later we can explore on Fabric option.