You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Mukund Balasubramanian <mu...@infravio.com> on 2006/03/06 07:35:42 UTC
Management Model for Axis and Synapse
Guys:
I know we have spoken about this before but I propose creating a native
management model for Axis (the underlying SOAP Stack) which can be
extended to satisfy the needs of Synapse as an intermediary built on
Axis.
There are, of course, varying definitions of "management" and a wide
variety of technologies to choose from (JMX, WSDM being prime candidates
discussed in the past). But here, I shall describe some "requirements"
which I believe are independent of the underlying implementation
technology but are also inline with the JMX/WSDM definition of best
practices.
The foundation of what I call "management" will be as follows:
1. Discovery (ability to discover what's out there and what's going
on)
2. Configuration (set, get, mod configuration)
3. State (start, stop, other states?)
4. Events (useful information about what's going on so you can
subscribe to it)
5. Metrics (ditto but are aggregates)
The Infravio team has extensive experience in creating these management
foundations in a variety of different contexts and would be glad to
contribute the seed codebase for this feature set. The above constitutes
what would be an "agent" which is one piece of a management architecture
constituting an agent, a console server and a console.
One question which I had was that while this is essential for Synapse
participating in the "Web Services Management" space, there is a finite
amount of good that can come about if this was actually embedded in Axis
as well.
Would this be of interest? We are going ahead with the development of
the same for our products and thought we could contribute it if there
was sufficient interest.
Mukund Balasubramanian
PS: Can somebody forward this to Axis-Dev?
Re: Management Model for Axis and Synapse
Posted by Deepal jayasinghe <de...@gmail.com>.
yes , he did Google summer of code project and now he is trying to
improve that, as I know he has almost completed the project and need to
integrate into Axis2. But we (Axis2) can not integrate that since we are
going to have a release soon . I think its better you guys can help him
to get it into required level.
Saminda Abeyruwan wrote:
> Hi Mukund,
>
> An Axis2 developer, Chathura Ekanayaka has been engaged in developing
> a management interface for Axis2 for quite sometime now. He has done
> quite a lot of work and a wonderful mangement interface for Axis2
> using JMX as a part of Google Summer of Code projects. After doing a
> lot of improvements, it's in the verge of integrating to the Axis2
> code base with the next release. Please consult the Axis2 development
> mailing list for more information.
>
> Thank you
>
> Saminda
>
>
>
>
>
>
>
> On 3/6/06, *Mukund Balasubramanian* <mukund@infravio.com
> <ma...@infravio.com>> wrote:
>
> Guys:
>
>
>
> I know we have spoken about this before but I propose creating a
> native management model for Axis (the underlying SOAP Stack) which
> can be extended to satisfy the needs of Synapse as an intermediary
> built on Axis.
>
>
>
> There are, of course, varying definitions of "management" and a
> wide variety of technologies to choose from (JMX, WSDM being prime
> candidates discussed in the past). But here, I shall describe some
> "requirements" which I believe are independent of the underlying
> implementation technology but are also inline with the JMX/WSDM
> definition of best practices.
>
>
>
> The foundation of what I call "management" will be as follows:
>
>
>
> 1. Discovery (ability to discover what's out there and what's
> going on)
> 2. Configuration (set, get, mod configuration)
> 3. State (start, stop, other states?)
> 4. Events (useful information about what's going on so you can
> subscribe to it)
> 5. Metrics (ditto but are aggregates)
>
>
>
> The Infravio team has extensive experience in creating these
> management foundations in a variety of different contexts and
> would be glad to contribute the seed codebase for this feature
> set. The above constitutes what would be an "agent" which is one
> piece of a management architecture constituting an *agent*, a
> *console server* and a *console*.
>
>
>
> One question which I had was that while this is essential for
> Synapse participating in the "Web Services Management" space,
> there is a finite amount of good that can come about if this was
> actually embedded in Axis as well.
>
>
>
> Would this be of interest? We are going ahead with the development
> of the same for our products and thought we could contribute it if
> there was sufficient interest.
>
>
>
> Mukund Balasubramanian
>
> PS: Can somebody forward this to Axis-Dev?
>
>
--
Thanks,
Deepal
................................................................
~Future is Open~
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Management Model for Axis and Synapse
Posted by Saminda Abeyruwan <sa...@gmail.com>.
Hi Mukund,
An Axis2 developer, Chathura Ekanayaka has been engaged in developing a
management interface for Axis2 for quite sometime now. He has done quite a
lot of work and a wonderful mangement interface for Axis2 using JMX as a
part of Google Summer of Code projects. After doing a lot of improvements,
it's in the verge of integrating to the Axis2 code base with the next
release. Please consult the Axis2 development mailing list for more
information.
Thank you
Saminda
On 3/6/06, Mukund Balasubramanian <mu...@infravio.com> wrote:
>
> Guys:
>
>
>
> I know we have spoken about this before but I propose creating a native
> management model for Axis (the underlying SOAP Stack) which can be extended
> to satisfy the needs of Synapse as an intermediary built on Axis.
>
>
>
> There are, of course, varying definitions of "management" and a wide
> variety of technologies to choose from (JMX, WSDM being prime candidates
> discussed in the past). But here, I shall describe some "requirements" which
> I believe are independent of the underlying implementation technology but
> are also inline with the JMX/WSDM definition of best practices.
>
>
>
> The foundation of what I call "management" will be as follows:
>
>
>
> 1. Discovery (ability to discover what's out there and what's going
> on)
> 2. Configuration (set, get, mod configuration)
> 3. State (start, stop, other states?)
> 4. Events (useful information about what's going on so you can
> subscribe to it)
> 5. Metrics (ditto but are aggregates)
>
>
>
> The Infravio team has extensive experience in creating these management
> foundations in a variety of different contexts and would be glad to
> contribute the seed codebase for this feature set. The above constitutes
> what would be an "agent" which is one piece of a management architecture
> constituting an *agent*, a *console server* and a *console*.
>
>
>
> One question which I had was that while this is essential for Synapse
> participating in the "Web Services Management" space, there is a finite
> amount of good that can come about if this was actually embedded in Axis as
> well.
>
>
>
> Would this be of interest? We are going ahead with the development of the
> same for our products and thought we could contribute it if there was
> sufficient interest.
>
>
>
> Mukund Balasubramanian
>
> PS: Can somebody forward this to Axis-Dev?
>
Re: Management Model for Axis and Synapse
Posted by Raghavendra Vaidya <ra...@gmail.com>.
Hi,
I am prepared to contribute as a developer in this effort. I was
actually planning to start a project as an extension to Synapse to
cover the management piece.
Please let me know how do I get involved and contribute.
Regards
Vaidya
On 3/6/06, Mukund Balasubramanian <mu...@infravio.com> wrote:
>
>
>
> Guys:
>
>
>
> I know we have spoken about this before but I propose creating a native
> management model for Axis (the underlying SOAP Stack) which can be extended
> to satisfy the needs of Synapse as an intermediary built on Axis.
>
>
>
> There are, of course, varying definitions of "management" and a wide variety
> of technologies to choose from (JMX, WSDM being prime candidates discussed
> in the past). But here, I shall describe some "requirements" which I believe
> are independent of the underlying implementation technology but are also
> inline with the JMX/WSDM definition of best practices.
>
>
>
> The foundation of what I call "management" will be as follows:
>
>
>
> Discovery (ability to discover what's out there and what's going on)
> Configuration (set, get, mod configuration)
> State (start, stop, other states?)
> Events (useful information about what's going on so you can subscribe to it)
> Metrics (ditto but are aggregates)
>
>
>
> The Infravio team has extensive experience in creating these management
> foundations in a variety of different contexts and would be glad to
> contribute the seed codebase for this feature set. The above constitutes
> what would be an "agent" which is one piece of a management architecture
> constituting an agent, a console server and a console.
>
>
>
> One question which I had was that while this is essential for Synapse
> participating in the "Web Services Management" space, there is a finite
> amount of good that can come about if this was actually embedded in Axis as
> well.
>
>
>
> Would this be of interest? We are going ahead with the development of the
> same for our products and thought we could contribute it if there was
> sufficient interest.
>
>
>
> Mukund Balasubramanian
>
> PS: Can somebody forward this to Axis-Dev?
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org