Re: Server profiles
I made this change for the launcher and plan to make a similar change
for the server code shortly.
The name of the profile can be overridden by setting the
tuscany.profile system property - the default value for this is
launcher The root for each profile defaults to $
{tuscany.installDir}/profiles/${tuscany.profile} and again can be
overridden by specifying a system property with the name
tuscany.profileDir.${tuscany.profile}
I moved runtime.properties from etc to the profile's root directory
for simplicity as in many cases a profile may just contain it and the
system scdl. I made properties loaded from this file available
through the RuntimeInfo service (backed by default values from the
system properties). Configuration values for the runtime itself (such
as the location of the system scdl or the implementation class) can
be specified in this file on a per-profile basis.
--
Jeremy
On Jan 4, 2007, at 7:12 AM, Jeremy Boynes wrote:
One problem we had with M2 was that the launcher used a single set
of extensions for every application it ran. I think Meeraj's server
config will have a similar issue with it's ability to run multiple
runtimes at the same time (with the likelihood that the reason
someone wants to do that would be that they are configured
differently).
To address this, I am going to convert the standalone distro to
support the notion of runtime profiles by adding a profiles
directory in the root containing a subdirectory for each profile.
There will be two built-in profiles launcher and server
present by default and used by the launcher and server commands.
Each profile will contain an etc directory which would contain
the runtime.properties and system.scdl files used by that
profile's runtime. As a side benefit moving the system.scdl out of
the launcher jar will make it easier for users to change it if they
want.
I'll also add support for a new command line option ( -
Dprofile=... ) to allow the user to override the default profile
for each command.
--
Jeremy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Server profiles
Jeremy, On having the system.scdl in the etc directory .. I am assuming it is the system.scdl for the server itself, rather than the runtime that is lauched by the server? Each runtime that is launched through the startRuntime managed operation on the server will have its own system.scdl, wherever it is stored as long it is available to the boot classloader of the runtime? Would this mean the distro would be something like /install - Root installer directory /install/launcher - Launcher root /install/launcher/etc - Launcher runtime properties and system scdl /install/launcher/boot - Launcher boot libraries /install/server - Server root /install/server/etc - Server runtime properties and system scdl /install/server/boot - Server boot libraries /install/server/runtime-x - Runtime x root /install/server/runtime-x/etc - Runtime x runtime.properties and system scdl /install/server/runtime-x/etc/boot - Runtime x boot libraries /install/server/runtime-y - Runtime y root /install/server/runtime-y/etc - Runtime y runtime.properties and system scdl /install/server/runtime-y/etc/boot - Runtime y boot libraries Ta Meeraj -Original Message- From: Jeremy Boynes [mailto:[EMAIL PROTECTED] Sent: Thursday, January 04, 2007 3:13 PM To: tuscany-dev@ws.apache.org Subject: Server profiles One problem we had with M2 was that the launcher used a single set of extensions for every application it ran. I think Meeraj's server config will have a similar issue with it's ability to run multiple runtimes at the same time (with the likelihood that the reason someone wants to do that would be that they are configured differently). To address this, I am going to convert the standalone distro to support the notion of runtime profiles by adding a profiles directory in the root containing a subdirectory for each profile. There will be two built-in profiles launcher and server present by default and used by the launcher and server commands. Each profile will contain an etc directory which would contain the runtime.properties and system.scdl files used by that profile's runtime. As a side benefit moving the system.scdl out of the launcher jar will make it easier for users to change it if they want. I'll also add support for a new command line option ( -Dprofile=... ) to allow the user to override the default profile for each command. -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message has been checked for all email viruses by MessageLabs. * You can find us at www.voca.com * This communication is confidential and intended for the exclusive use of the addressee only. You should not disclose its contents to any other person. If you are not the intended recipient please notify the sender named above immediately. Registered in England, No 1023742, Registered Office: Voca Limited Drake House, Three Rivers Court, Homestead Road, Rickmansworth, Hertfordshire, WD3 1FX This message has been checked for all email viruses by MessageLabs. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Server profiles
On Jan 4, 2007, at 7:31 AM, Meeraj Kunnumpurath wrote: Jeremy, On having the system.scdl in the etc directory .. I am assuming it is the system.scdl for the server itself, rather than the runtime that is lauched by the server? Each runtime that is launched through the startRuntime managed operation on the server will have its own system.scdl, wherever it is stored as long it is available to the boot classloader of the runtime? I was thinking that each profile (and the system.scdl it contains) would apply to a runtime. The server agent would not need one as it does not contain a system component tree. The startRuntime operation would take the name of a profile and that would be used to start the runtime. The server command could be enhanced to take an optional list of profiles to start, something like: $ server start server otherProfile yetAnother Would this mean the distro would be something like /install - Root installer directory /install/launcher - Launcher root /install/launcher/etc - Launcher runtime properties and system scdl /install/launcher/boot - Launcher boot libraries /install/server - Server root /install/server/etc - Server runtime properties and system scdl /install/server/boot - Server boot libraries /install/server/runtime-x - Runtime x root /install/server/runtime-x/etc - Runtime x runtime.properties and system scdl /install/server/runtime-x/etc/boot - Runtime x boot libraries /install/server/runtime-y - Runtime y root /install/server/runtime-y/etc - Runtime y runtime.properties and system scdl /install/server/runtime-y/etc/boot - Runtime y boot libraries I was thinking instead: /install /install/bin/launcher.jar /install/bin/server.jar /install/lib/ [ jars needed by launcher, server commands] /install/profiles/launcher/etc/runtime.properties /install/profiles/launcher/etc/system.scdl /install/profiles/launcher/boot/ [ jars for launcher runtime classloader ] /install/profiles/server/etc/... /install/profiles/server/boot/... /install/profiles/otherProfile/etc/... /install/profiles/otherProfile/boot/... /install/profiles/yetAnother/etc/... /install/profiles/yetAnother/boot/... /install/profiles/... -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Server profiles
k, that makes sense. -Original Message- From: Jeremy Boynes [mailto:[EMAIL PROTECTED] Sent: Thursday, January 04, 2007 5:05 PM To: tuscany-dev@ws.apache.org Subject: Re: Server profiles On Jan 4, 2007, at 7:31 AM, Meeraj Kunnumpurath wrote: Jeremy, On having the system.scdl in the etc directory .. I am assuming it is the system.scdl for the server itself, rather than the runtime that is lauched by the server? Each runtime that is launched through the startRuntime managed operation on the server will have its own system.scdl, wherever it is stored as long it is available to the boot classloader of the runtime? I was thinking that each profile (and the system.scdl it contains) would apply to a runtime. The server agent would not need one as it does not contain a system component tree. The startRuntime operation would take the name of a profile and that would be used to start the runtime. The server command could be enhanced to take an optional list of profiles to start, something like: $ server start server otherProfile yetAnother Would this mean the distro would be something like /install - Root installer directory /install/launcher - Launcher root /install/launcher/etc - Launcher runtime properties and system scdl /install/launcher/boot - Launcher boot libraries /install/server - Server root /install/server/etc - Server runtime properties and system scdl /install/server/boot - Server boot libraries /install/server/runtime-x - Runtime x root /install/server/runtime-x/etc - Runtime x runtime.properties and system scdl /install/server/runtime-x/etc/boot - Runtime x boot libraries /install/server/runtime-y - Runtime y root /install/server/runtime-y/etc - Runtime y runtime.properties and system scdl /install/server/runtime-y/etc/boot - Runtime y boot libraries I was thinking instead: /install /install/bin/launcher.jar /install/bin/server.jar /install/lib/ [ jars needed by launcher, server commands] /install/profiles/launcher/etc/runtime.properties /install/profiles/launcher/etc/system.scdl /install/profiles/launcher/boot/ [ jars for launcher runtime classloader ] /install/profiles/server/etc/... /install/profiles/server/boot/... /install/profiles/otherProfile/etc/... /install/profiles/otherProfile/boot/... /install/profiles/yetAnother/etc/... /install/profiles/yetAnother/boot/... /install/profiles/... -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message has been checked for all email viruses by MessageLabs. * You can find us at www.voca.com * This communication is confidential and intended for the exclusive use of the addressee only. You should not disclose its contents to any other person. If you are not the intended recipient please notify the sender named above immediately. Registered in England, No 1023742, Registered Office: Voca Limited Drake House, Three Rivers Court, Homestead Road, Rickmansworth, Hertfordshire, WD3 1FX This message has been checked for all email viruses by MessageLabs. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
