Solution Directories
When installing TDI 6.0 or above, you can select where you want to keep solution files (config XMl files, properties etc).
In reply to a question about this on the newsgroup, Eddie Hartman wrote:
The idea behind having a solution directory (soldir) is so
you don't mix your work with programs. Instead of having to
navigate in Program Files to find data to backup, its easier
to store user-data off your home dir instead (%HOMEDIR%/TDI).
This also allows you to have multiple soldirs, which is very
handy when you are running multiple versions of TDI that do
not share the same Config version (e.g. 5.2 -> 6.0). If you
save a Config in 6.0 format, then 5.2 cannot read it anymore.
I have a couple of soldirs myself.
But then we have the situation that many parameters for TDI
are stored in the
global.properties file that is always
placed in your install directory. And you may want different
settings for different soldirs (for example, if you have set
up a playpen for testing/development). That is where
solution.properties comes in. The first time you start the
Config Editor (CE) with a new soldir, it lifts over
global.properties to create the new solution.properties.
At startup, TDI always reads both, first
global and then
solution. As a
result, you can choose to have an empty solution.properties
and make all your changes to global.properties; or you can choose to override desired values in solution.properties instead. A general best practice
is to have your solution.properties file as empty as possible, storing
there only configuration settings that you want to override those in
global.properties.
--
AndrewFindlay - 23 Dec 2005