[
https://jira.jboss.org/jira/browse/TEIID-464?page=com.atlassian.jira.plug...
]
Larry O'Leary commented on TEIID-464:
-------------------------------------
Correct, $MMCONFIGNAME would be an optional, user-set environment variable that would be
used if the -config command-line argument was not passed in one of the scripts that needed
it.
If we are simply leaning toward the -config property using a path/file name value to the
bootstrap configuration file then I suppose the environment variable we look for should be
simply MMCONFIG or MMCONFIGFILE.
It does seem that the old behaviour is still better and requires less user interaction
though. The goal here should be that a user can simply execute the start and/or stop
scripts without worrying about having to pass special things to it. This is what are
users are used to doing. We are now saying that we want to force our users to use
command-line options and/or make sure they aren't replacing the wrong xxx.properties
file when installing a new host into a shared directory.
Shared Installation Option
--------------------------
Key: TEIID-464
URL:
https://jira.jboss.org/jira/browse/TEIID-464
Project: Teiid
Issue Type: Task
Components: Common
Affects Versions: 6.0.0
Reporter: Ramesh Reddy
Assignee: Steven Hawkins
Fix For: 6.1.0
We need to decide if/how we're going to support the shared
installation option. With the changes to what's stored in the
metamatrix.properties (i.e., host properties and config.name), this
now complicates how we'll install (i.e., system host setup and odbc) /
support this feature.
--
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