[ https://issues.jboss.org/browse/TEIID-2650?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on TEIID-2650: ----------------------------------------- Paul, To be precise, there is one *set* of Teiid configurations per domain. Different profiles in the domain can have different Teiid configurations. But yes, it is the responsibility of the domain management infrastructure to keep the domain wide configuration consistent across all Host Controllers in the domain, and that will include any Teiid subsystem configurations that exist. The Host Controllers ensure that servers gets a consistent representation of whatever portion of the domain wide config is relevant to that server. Configuration is distinct from runtime state though. The actual binaries installed on different hosts can be different, and this runtime-version attribute reflects what actual binaries are being used for a process. That doc, before getting into the teiid-domain-mode-install.cli script part, says "To start the server in "Domain" mode, install the JBoss AS 7.2 (EAP 6.1) and Teiid 8.4 on all the servers that are going to be part of the cluster." So there's a binary provisioning step that occurs before config gets applied. That doc focuses on an initial setup case where all hosts are almost certainly going to be running the same release. But once a domain is in active use, it's possible that some hosts will be upgraded to a later release while others will not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira