Paul
On 1/19/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
I like the idea of using an env script/bat implementation. It makes lots of
sense in many ways. I don't think one would be allowing users to directly
modify the scripts but we'd ask for their input and validate it before building
the script. So from that perspective the input mechanism is is responsible for
doing the scrubbing.
The bigger issue in my mind is the strategy for supporting multiple server
configurations. A single env script is not adequate for all possible servers
since the user may choose to run different apps on servers that are not part of
the same group.
I'm not sure how WADI is handling this from an admin / config perspective but
they have the same issue in how do we get the right information into a
particular server instance. It sounds like this will most likely be a 2.0
discussion since it will be a significant change over how were currently structured.
One possible (and simple solution) would be to:
$g/var/servers/server1/config.xml
/server2/config.xml
/server3/config.xml
Would contain the meta data used to generate unique env scripts (not very
scalable) or better yet, be used to dynamically build the java command to launch
the desired server.
I guess at some point someone might want to restrict who can configure a set of
servers based on their credentials but I think that's a bit out on the horizon.
To paraphrase Guglielmo, perhaps that is a feature that people will get from
commercial software.
Thoughts?
Matt
