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

[ https://jira.jboss.org/jira/browse/TEIID-464?page=com.atlassian.jira.plug... ] Ramesh Reddy commented on TEIID-464: ------------------------------------ Based on prior issues, I want to make sure there are two ground rules we should adhere to, before any solution is decided (1) Configuration Name != Host Name (so, any logic in code or in scripts drawing such parallels must be avoided) (2) Multiple ways to figure out, what and where are the bootstrap properties are should be avoided. Then it up to interpretation or lengthy documentation. Now.. The only thing I see different in above two solutions, is what happens when user does not supply a "-config" option? I did not like the user searching the directories for the bootstrap in hosts directories, sometimes the host directory itself is configurable. This is error prone, and does depend upon the host name look up. In the "shared" install, I see as no different than my original and Larry's suggestion. Both suggesting the burden on the user to supply the required "-config" property. - Use of the $MMCONFIGNAME in startup/shhutdown scripts seems good to as it alleviates user from supplying "-config" option on the command line all the time, if they are required. - I prefer "-config" option specifying the "full path" to the properties file, rather than just name of the configuration, this removes the need to discover where this property file is actually stored, and tieing the configuration name to <config>.properties, there is no reason for additional indirection, to derive the property file name. - Coming back to default case, we *could* write bootstrap properties during the install to two places 1. <install>/config/metamatrix.properties 2. <install>/hosts/<config>/<config>.properties For non-shared install, it will work as before, and in the shared install, user can point the "-config" or $MMCONFIGNAME to property file under the <install>/hosts directory. -- 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