[teiid-issues] [JBoss JIRA] Commented: (TEIID-464) Shared Installation Option

[ https://jira.jboss.org/jira/browse/TEIID-464?page=com.atlassian.jira.plug... ] Larry O'Leary commented on TEIID-464: ------------------------------------- Below are my comments that I had originally posted to vhalbert. Basically, instead of using metamatrix.properties we use <configname>.properties where <configname> is the value set at configuration/installation time (the same name used in the /hosts directory. If -config option is used in start/stop scripts we use it as the <configname> of the <configname>.properties. If they don't specify -config then we attempt to match directories from hosts/ to <directoryname>.properties in config/ and if we find only one match it is used, otherwise error is thrown. ----------- If we implement what you were originally talking about for the bootstrap properties file. What if we did something like this: Bootstrap properties file gets named ${CONFIG_NAME}.properties and stored in ${MM_ROOT}/config. Host specific (non-shared) files get placed in ${MM_ROOT}/hosts/${CONFIG_NAME} (just like they currently do). startserver/stopserver (and any other scripts that rely on bootstrap properties) check for the presence of --config <config_name> command line argument or ${MMCONFIGNAME} environment variable and if present/set use it to locate the ${CONFIG_NAME}.properties file in the config directory. If the --config command-line argument is not present and the ${MMCONFIGNAME} environment variable is not set then the entry methods that need the bootstrap properties will first look in ${MM_ROOT}/hosts/ for the presence of a single match of a corresponding ${CONFIG_NAME}.properties file in the config directory. If more than one match is found then an error is returned indicating that the --config option should be used because the bootstrap properties location/name could not be determined. Scenario 1: Non-shared / single host install and host auto finds the bootstrap properties /root /root/hosts /root/hosts/MyMMxServer /root/config /root/config/MyMMxServer.properties Start the server: /root/bin/startserver ** host startup methods get executed *** No MMCONFIGNAME environment variable -- hostConfigName stays null *** No --config argument - hostConfigName stays null *** hostConfigName is null - Get list of directories in /root/hosts **** Directory MyMMxServer ***** Look in /root/config for a file named "MyMMxServer.properties" - It is there so we set hostConfigName = MyMMxServer **** No more directories in /root/hosts so we found only one match. ** hostConfigName is set to a valid value so continue to start using the properties from MyMMxServer.properties Scenario 2: Shared environment / multi-host install so user must specify --config or MMCONFIGNAME Same as scenario one but: *** hostConfigName is null - Get list of directories in /root/hosts **** Directory MyMMxServer ***** Look in /root/config for a file named "MyMMxServer.properties" - It is there so we set hostConfigName = MyMMxServer **** Directory MyMMxServer2 ***** Look in /root/config for a file named "MyMMxServer2.properties" - It is there and hostConfigName is already non-null so we have found more than one match... we need to fail with meaningful error message and exit code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira