[
https://jira.jboss.org/jira/browse/TEIID-464?page=com.atlassian.jira.plug...
]
Ramesh Reddy commented on TEIID-464:
------------------------------------
per discussion with Van last week, this can be solved by below
- Right now, the boot strap start-up happens by looking up a property file called
"metamatrix.properties". This file has all the properties to start a server.
however if we change start up script such that, instead of looking for
"metamatrix.properties", one can supply the for example
"foo.properties", during the startup, to load a particular node then the issue
is solved. However, additional burden on the system admin/installer is to rename the
automatically created "metamatrix.properties" to "foo.properties"
after the installation is finished for a node. Since this usecase not so normal, putting
little burden on the system admin is warranted.
By default, if one does not supply a property file, it can still look for
'metamatrix.properties" file in classpath to preserve the current behaviour. .
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