Thanks for the suggestion. This has been implemented.
Gianny
John Sisson wrote:
Gianny,
I think we should change the org.apache.geronimo.base.dir property to
be org.apache.geronimo.home.dir so it is consistent in meaning with
Tomcat's usage of the terms home and base to avoid confusion.
Gianny,
I think we should change the org.apache.geronimo.base.dir property to be
org.apache.geronimo.home.dir so it is consistent in meaning with
Tomcat's usage of the terms home and base to avoid confusion.
In Tomcat:
home = the installation directory
base = the base directory used for
+1
-dain
On Mar 1, 2006, at 2:49 AM, John Sisson wrote:
Gianny,
I think we should change the org.apache.geronimo.base.dir property
to be org.apache.geronimo.home.dir so it is consistent in meaning
with Tomcat's usage of the terms home and base to avoid confusion.
In Tomcat:
home =
Hi,
This change adds the ability to start multiple server instances against
the same bin, config-store, deploy, lib, repository and shema folders of
a Geronimo installation.
An additional instance can be set-up by copying the var folder to the
directory where you want to create a new
Can you please elaborate a bit more on what exactly this provides?
Can I now have two separate instances each with their own unique
applications/configurations/logs (i.e. config-store, deploy and var
directories) sharing the same geronimo installation binaries (i.e. bin,
lib and repository
Hi,
The second solution has been implemented.
When starting G, it is now possible to specify one of these two system
properties:
* org.apache.geronimo.server.name: name of the server to be started. If
server1 is specified, then G will use the directory geronimo
installation dir/server1; or
*
On Feb 12, 2006, at 9:17 AM, Vincent Massol wrote:
Hi David and everyone,
Any progress on this?
not yet, sorry. it is pretty easy, but I am tied up in the configid
branch right now.
david jencks
Thanks
-Vincent
-Original Message-
From: David Jencks [mailto:[EMAIL
Hi David and everyone,
Any progress on this?
Thanks
-Vincent
-Original Message-
From: David Jencks [mailto:[EMAIL PROTECTED]
Sent: lundi 30 janvier 2006 08:23
To: dev@geronimo.apache.org
Subject: Multiple servers sharing the same repo and config store
Many people have talked on
Some ideas..
Currently geronimo.sh/bat will invoke a setenv.sh script if present ( in
the bin directory ). Maybe we could enhance geronimo.sh/bin to also
invoke a setenv.sh script if present under var for a particular geronimo
instance. So the setenv.sh script in geronimo/bin gets invoked
I'm not sure if you are suggesting it would be possible for two geronimo
instances to share a var/config directory - that would not work as each
instance would be attempting to do updates of the one config.xml file.
This may also have problems with two instances trying to write log
files,
Big +1 to either :-)
Thanks David
-Vincent
-Original Message-
From: David Jencks [mailto:[EMAIL PROTECTED]
Sent: lundi 30 janvier 2006 08:23
To: dev@geronimo.apache.org
Subject: Multiple servers sharing the same repo and config store
Many people have talked on and off about how
This sounds reasonable to me. I'd prefer to have resolveServer and
always look for /var under there. If there are multiple config
stores, we'll have to figure out how the deploy tool will know which
one to use. Perhaps there should be something indicating whether the
config store is writable at
Does anyone know how other J2EE servers structure their directories
when they have multiple instances configured?
-dain
On Jan 30, 2006, at 5:04 AM, Aaron Mulder wrote:
This sounds reasonable to me. I'd prefer to have resolveServer and
always look for /var under there. If there are
Hi, In WebSphere this is the directory organization: $WAS_HOME/config/cells/$CELL_NAME applications (EAR/WAR/RAR) nodes .$NODE_NAME ..servers (JVM Configurations)
One approach that seems user friendly to me would be to allow the user
to pass an argument to Geronimo startup specifying a server root
directory. The immediate subdirectories of this server
root directory would trump those in geronimo_home for that server
instance. Using this technique would
On Jan 30, 2006, at 8:54 AM, Paul McMahan wrote:One approach that seems user friendly to me would be to allow the user to pass an argument to Geronimo startup specifying a "server root" directory. The immediate subdirectories of this server root directory would trump those in geronimo_home for
As far as directory structure, it seems that WebSphere separates the
binaries (e.g. jars, scripts) from the instance data. Each instance has
it's own copy of configuration data, installed applications, logs and
properties. The scripts (e.g. startup/shutdown) are also available in
each
As a programmer type it seems intuitive to me that the
presence of a subdir in an alternate server root overrides the default
while its absence makes the server instance inherit the
default. But its possible that I am mingling system
administration with too much OO. At any rate I agree that having
18 matches
Mail list logo
