Hang on guys, there's a difference between the "Server" part that
clients talk to and the ManagementService that bridges components
into the management space.
The TuscanyServer can start the "agent" for the management client.
With JMX, this would be the MBeanServer that we are using for all the
managed objects. It registers itself with that to provide clients
with a means to start/stop runtimes. It is performing the "host" role
for the different runtimes it spins up.
The system scdl for each runtime can define what implementation of
ManagementService it wants to use - it just defines a system
component that implements that service. A basic implementation could
reuse the MBeanServer from the TuscanyServer (getting it from the
RuntimeInfo for example) - a more complex implementation could do
WSDM for example (which probably prereqs a WS stack).
The important thing is that the containers do not know what
management protocol is being used - hence the need for an abstraction
like ManagementService rather than hooking them to JMX directly.
--
Jeremy
On Dec 28, 2006, at 2:34 PM, Meeraj Kunnumpurath wrote:
Joel,
This is what I am thinking as well, maybe tuscany server is started
as part of a bootstrap runtime that includes the management service
and it is made available to any other runtimes that is spawned
there of.
Anyway, to start with I have added some stuff into core and spi
org.apache.tuscany.core.services.management.jmx and
org.apache.tuscany.spi.services.management respectively. Once we
decide on the management annotations, we can add meat into the
AnnotationDrivenDynamicMBean class. Also, we can look at how we can
make the ManagementService implementation available as a system
service.
Ta
Meeraj
From: "Hawkins, Joel" <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: <[email protected]>
Subject: RE: Standalone server
Date: Thu, 28 Dec 2006 16:27:00 -0500
Meeraj,
>I think it would be fairly straightforward to write a generic JMX
dynamic
>MBean based on introspecting the annotated members (ops, properties
etc),
>quite similar to the reflection one already in the source tree. I
think
one
>key question is would these annotations be specific to tuscany, or
would
>they be pushed into the core SCA spec some time. If they are tuscany
>specific, what are the implications on portability of service
classes
>across different SCA implementations?
You'd hope they'd make it into the SCA spec. If not there, then at
least
into org.apache.ws.commons. :-)
>Also, regarding what Jeremy mentioned about CompositeComponent
having a
>ManagementService injected in, which in turn is defined as a system
service,
>do we have a 'chicken-and-egg' situation here. Currently, tuscany
server
>exposes the management service for remote management. Management
clients >use this service to start and stop runtimes. All system
services are >associated with a runtime. However, if the management
service is defined as >a system service, we will have to start a
runtime
to make the management >service available. However to start a
runtime we
need a management >service :)
Oh dear, this does sound grim. So the bootstrap runtime is no more?
Perhaps the system service of the management service running
inside the
individual runtimes could be 'spun off' of an already running
instance?
Cheers,
Joel
The contents of this e-mail are intended for the named addressee
only. It contains information that may be confidential. Unless you
are the named addressee or an authorized designee, you may not
copy or use it, or disclose it to anyone else. If you received it
in error please notify us immediately and then destroy it.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
MSN Hotmail is evolving – check out the new Windows Live Mail
http://ideas.live.com
---------------------------------------------------------------------
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]
