1 of 1 people found this helpful
Not sure whether I understand your question correct.
With JBoss you can have a domain for your installation, other instances on other machines can be configured as host-controller (slave) and pull the configuration from the domein-controller.
If you run the CLI command, nevertheless which installation, you are able to set the controller which you try to configure. This can be a different domain, only requirement is that the communication is compatible.
You might copy the domain directory and run different instances from the same installation by changing the domain directory if you start domain.sh.
But I would not recommend to do so because of the dependencies, it looks error-prone to me.
Let me put the question again
Its just a single server installation and the domains are planned to group related applications in one domain (segregation)
In such a situation as you have hinted it is possible to try having a copy of domain directory and using the options in.
I tried and it worked also (see below for more details), though I need to resolve some port conflicts which I am working on.
Would you recommend this approach or its better to have different installations of JBoss for the groups of related applications?
I created a copy of domain folder as domain1 with some changes in domain.xml and host.xml
When I tried with: domain.bat --host-config=domain1/domain.xml --host-config=domain1/host.xml, got the below error
[Host Controller] 18:02:15,254 ERROR [stderr] (main) java.lang.IllegalStateException: JBAS014805: Could not get main fil
e: domain1/host.xml. Specified files must be relative to the configuration dir: D:\Applications\jboss-eap-6.1.0\domain\configuration
So t tried again with: domain.bat --host-config=../../domain1/configuration/domain.xml --host-config=../../domain1/configuration/host.xml
and it started, still have some port conflicts to resolve..
For running domain mode no need to copy stuff around.
you can run domain mode on only one machine, or as many as you like.
you always have Domain Controller (DC) and Host Controller (HC) which can be on same machine or you can just have DC on one machine and as many HC as you like different machines.
so in shorty you always have one DC and one HC per machine/host.
for simple scenarios DC can also be HC and can run many server configrations on it.
every HC can run as many of "servers" as you like aka it will run different JVM instances with full AS configuration you assign them.
for your scenario you have one DC (acting also as HC) on one machine and with as many servers as you like. you can configure server groups & servers in your host.xml
or trough CLI or Admin console.
and all you need to do is start domain mode with domain.sh and everything else will start based on your configuration.
if that is what you are looking for.
given way you are approaching your problem, i think you want to have multiple standalone servers running from different config/data directories.
if you want to do that, then you should use standalone.bat not domain.bat for starting your servers.