We are currently developing a distributed JavaEE application. Several JBoss instances will be spreaded over several nodes and they have to communicate to each other.
Due to no knowledge about the actual deployment during development time we need a strategy how to configure the nodes without unpacking the EARs, changing the content and repacking them.
Currently we provide a system property via standalone.xml which points to the configuration directory and the application looks into it to read the configuration. This is not very fancy.
Is there an elegant way to put the configuration into the JBoss configuration directory, too, to read it from the via standard functionality? Is there another standard way to do it without additional system properties?
We currently use JBoss 7.1.0.Final and Java 1.6
UPDATE
I also found now a question qhich is quite similar, but not exactly what I want. Maybe it helps someone else: How can I store Java EE configuration parameters outside of an EAR or WAR?
Please go through the below link for Managed Domains, where you could manage the several JBoss instances seamlessly using a Domain Controller concept.
https://docs.jboss.org/author/display/AS7/Core+management+concepts