Description of problem: User has possibility to change management ports (9999,9990) for standalone, but not for domain. These ports are configured inside host configuration files. We should give user ability to configure them during installation (one configuration for all host files). Affected files: $JBOSS_HOME/domain/configuration/host.xml $JBOSS_HOME/domain/configuration/host-master.xml $JBOSS_HOME/domain/configuration/host-slave.xml Current version: EAP 6.2.0.ER3
Option to change management ports for domain has been added. http://git.app.eng.bos.redhat.com/?p=jbossas-installer.git;a=commit;h=d1fac52a1a98d2790886f69488f1d896ec86524c
Hi Miles, I am not sure, whether this is a correct solution. Management ports of each profile are stored in separate xml file in standalone mode, so it is fine to configure them for each profile (profiles are named after xml files), but these ports are shared by all profiles in domain (profiles are defined in domain.xml), so I don't think we should configure them just in domain socket bindings screen (default profile). We should create a separate screen, just for domain management port, or do you think of another solution? We may also update "Socket Binding (domain)" string to "Socket Binding (default-domain)" so it's clear that user is changing ports only for default profile of domain not for the whole domain, however this is just a suggestion.
As suggested, "Socket Binding (domain)" renamed to "Socket Binding ("default-domain)" Also management ports that effects the host.xml is in its own panel. http://git.app.eng.bos.redhat.com/jbossas-installer.git/commit/?h=eap-6.2&id=41e54825e8b0a37a840dd7ada127d99fb31297db
Verified on EAP 6.2.0.ER5 installer.