You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Chathura Ekanayake <cc...@gmail.com> on 2005/07/06 13:09:03 UTC
[Axis2] JMX front end to Axis2
I would like to work on the JMX front end for Axis2 mentioned in
http://wiki.apache.org/ws/FrontPage/Axis2/Tasks/JMX-front. I have
received a grant under Google Summer of Code program for this project.
Goal of this is to wrap the configurable parts of Axis2 with MBeans
and provide a JMX interface to monitor and configure Axis2 remotely
using JMX services.
The plan is to create MBeans that wrap the configuration and register
them in a MBean server at the start up of Axis2. Once the MBean server
is setup, any authorized client can connect to it using the url of the
MBean server.
A separate servlet (a built in client) is created to provide the web
user interface for managing Axis2. This servlet connects to the Axis2
MBean server and performs the management tasks using MBeans.
Regards,
Chathura
Re: [Axis2] JMX front end to Axis2
Posted by Davanum Srinivas <da...@gmail.com>.
Chatura,
As long as everything works when jmx jars are absent. it should be ok.
Where is the code? (could you post it as an attachment in jira?)
thanks,
dims
On 8/8/05, Chathura Ekanayake <cc...@gmail.com> wrote:
> Hi,
>
> I developed the Axis2 JMX front using commons.modeler package. And I
> have used runtime class loading to load modeler classes as done in
> Axis1.2.
>
> I have also added functionality to publish the MBeanServer using a RMI
> connector so that it can be accessed by remote machines through RMI.
> But this requires to use the classes from javax.management and
> javax.management.remote packages. How should we use these classes?
> Should we use runtime loading to load these classes as well?
>
> And is it ok to publish MBeanServer using RMI connector, or should it
> be kept without publishing as done in Axis1.2?
>
> Regards,
>
> Chathura
>
--
Davanum Srinivas -http://blogs.cocoondev.org/dims/
Re: [Axis2] JMX front end to Axis2
Posted by Chathura Ekanayake <cc...@gmail.com>.
Hi,
I developed the code to load all jmx-rmi classes at run-time.
Now the JMX front can register any object as an MBean and publish it in RMI.
It does not depend on any jmx or jmx-rmi classes at the compile-time.
I have developed a simple MBean as a prototype, which can do following tasks:
> list all services and modules
> list faulty services and modules
> list all phases
> list all operations of a given service
> engage a module globally
> engage a module to a service
> engage a module to an operation
What would be the other possible tasks that we can do through the JMX front?
Do we need to develop an Axis2 specific JMX client other than
accessing Axis2 JMX front using jmx clients like JConsole or JManage?
I think if we develop a seperate JMX client for Axis2, we can add
functionality to save the configuration of one Axis2 engine (to an XML
file) and load the same configuration to a different Axis2 engine.
This functionality would be helpful if we want to apply the same
configuration (may be with minor modifications) to many Axis2 engines
running on different servers. But I am not sure whether this is
required, because I have no experience in server management.
It also can be developed to display the configuration information
nicely without restricting to the standard formats supported by the
normal JMX clients.
My code is at https://svn.apache.org/repos/asf/webservices/axis/trunk/archive/java/scratch/jmx-front/.
Please commit the attached patch to that URL.
Regards,
Chathura
Re: [Axis2] JMX front end to Axis2
Posted by Deepal Jayasinghe <de...@opensource.lk>.
See my comments below
Thanks,
Deepal
................................................................
~Future is Open~
----- Original Message -----
From: "Chathura Ekanayake" <cc...@gmail.com>
To: <ax...@ws.apache.org>
Sent: Monday, August 08, 2005 1:53 PM
Subject: Re: [Axis2] JMX front end to Axis2
Hi,
I developed the Axis2 JMX front using commons.modeler package. And I
have used runtime class loading to load modeler classes as done in
Axis1.2.
>>>>>>>>
What are the functionality that you are going to provide by JMX . If it can
provide much more functionality than web admin it will be great.
>>>>>>>>
I have also added functionality to publish the MBeanServer using a RMI
connector so that it can be accessed by remote machines through RMI.
>>>>>>>>>>
If you use RMI connectors there will be some proxy issues (need to open a
port)
>>>>>>>>>>
But this requires to use the classes from javax.management and
javax.management.remote packages. How should we use these classes?
Should we use runtime loading to load these classes as well?
And is it ok to publish MBeanServer using RMI connector, or should it
be kept without publishing as done in Axis1.2?
Regards,
Chathura
Re: [Axis2] JMX front end to Axis2
Posted by Chathura Ekanayake <cc...@gmail.com>.
Hi,
I developed the Axis2 JMX front using commons.modeler package. And I
have used runtime class loading to load modeler classes as done in
Axis1.2.
I have also added functionality to publish the MBeanServer using a RMI
connector so that it can be accessed by remote machines through RMI.
But this requires to use the classes from javax.management and
javax.management.remote packages. How should we use these classes?
Should we use runtime loading to load these classes as well?
And is it ok to publish MBeanServer using RMI connector, or should it
be kept without publishing as done in Axis1.2?
Regards,
Chathura
Re: [Axis2] JMX front end to Axis2
Posted by Deepal Jayasinghe <de...@opensource.lk>.
Hi Chathura;
see mt comments below;
Thanks,
Deepal
................................................................
~Future is Open~
----- Original Message -----
From: "Chathura Ekanayake" <cc...@gmail.com>
To: <ax...@ws.apache.org>
Sent: Wednesday, July 20, 2005 4:11 PM
Subject: Re: [Axis2] JMX front end to Axis2
Hi,
commons.modeler is used for model MBeans. Do we need to use model
MBeans here. I thought of using standard MBeans as the interface we
have to expose using JMX is fixed.
What are the advantages of using commons.modeler package for Axis2
JMX? Do we have to provide a dynamic interface?
>>>> I dont think we should provide this feature
I would also like to know the functionalities that we have to provide
via JMX. I have already implemented a simple prototype to provide most
of the functionalities of the Axis2 admin console.
Regards,
Chathura
Re: [Axis2] JMX front end to Axis2
Posted by Chathura Ekanayake <cc...@gmail.com>.
Hi,
commons.modeler is used for model MBeans. Do we need to use model
MBeans here. I thought of using standard MBeans as the interface we
have to expose using JMX is fixed.
What are the advantages of using commons.modeler package for Axis2
JMX? Do we have to provide a dynamic interface?
I would also like to know the functionalities that we have to provide
via JMX. I have already implemented a simple prototype to provide most
of the functionalities of the Axis2 admin console.
Regards,
Chathura
Re: [Axis2] JMX front end to Axis2
Posted by Davanum Srinivas <da...@gmail.com>.
Chatura, Srinath,
There is JMX support in 1.X using commons-modeler. Please take a look
at it before deciding.
-- dims
On 7/6/05, Srinath Perera <he...@gmail.com> wrote:
> Hi Chathura;
>
> Welcome Chathura!! Now we have too many people called Chatura :D around
>
> Let me say my views of thingy. And we should try to set up a schedule
> as the Goolgle programme needs it.
>
> 1) We need MBean(s) that wraps Axis2 ConfigurationContext (The
> Registry of all the information about Axis2), it can be one or it can
> be dozen ..
> 2) There should be a MBeans server! it can be the Tomcat one (in the
> HTTP Servlet cases) or if there is none we should start one.
> 3) When the Axis2 starts up it creates ConfigurationContext (The
> Registry of all the information about Axis2), a reference to this
> should be passed to the MBean(s) so they can alter Axis2
> 4) What information/configurations that can be managed via the JMX
> console is need to be decided!
>
> I think it is best to create a prototype (may be for the tomcat case
> .. what ever you feel comfortable) that can configure *some* setting
> in Axis2 and try to build on it. When we have something working .. we
> can get going
>
> Thanks
> Srinath
>
>
> On 7/6/05, Chathura Ekanayake <cc...@gmail.com> wrote:
> > I would like to work on the JMX front end for Axis2 mentioned in
> > http://wiki.apache.org/ws/FrontPage/Axis2/Tasks/JMX-front. I have
> > received a grant under Google Summer of Code program for this project.
> > Goal of this is to wrap the configurable parts of Axis2 with MBeans
> > and provide a JMX interface to monitor and configure Axis2 remotely
> > using JMX services.
> >
> > The plan is to create MBeans that wrap the configuration and register
> > them in a MBean server at the start up of Axis2. Once the MBean server
> > is setup, any authorized client can connect to it using the url of the
> > MBean server.
> >
> > A separate servlet (a built in client) is created to provide the web
> > user interface for managing Axis2. This servlet connects to the Axis2
> > MBean server and performs the management tasks using MBeans.
> >
> > Regards,
> >
> > Chathura
> >
>
--
Davanum Srinivas -http://blogs.cocoondev.org/dims/
Re: [Axis2] JMX front end to Axis2
Posted by Srinath Perera <he...@gmail.com>.
Hi Chathura;
Welcome Chathura!! Now we have too many people called Chatura :D around
Let me say my views of thingy. And we should try to set up a schedule
as the Goolgle programme needs it.
1) We need MBean(s) that wraps Axis2 ConfigurationContext (The
Registry of all the information about Axis2), it can be one or it can
be dozen ..
2) There should be a MBeans server! it can be the Tomcat one (in the
HTTP Servlet cases) or if there is none we should start one.
3) When the Axis2 starts up it creates ConfigurationContext (The
Registry of all the information about Axis2), a reference to this
should be passed to the MBean(s) so they can alter Axis2
4) What information/configurations that can be managed via the JMX
console is need to be decided!
I think it is best to create a prototype (may be for the tomcat case
.. what ever you feel comfortable) that can configure *some* setting
in Axis2 and try to build on it. When we have something working .. we
can get going
Thanks
Srinath
On 7/6/05, Chathura Ekanayake <cc...@gmail.com> wrote:
> I would like to work on the JMX front end for Axis2 mentioned in
> http://wiki.apache.org/ws/FrontPage/Axis2/Tasks/JMX-front. I have
> received a grant under Google Summer of Code program for this project.
> Goal of this is to wrap the configurable parts of Axis2 with MBeans
> and provide a JMX interface to monitor and configure Axis2 remotely
> using JMX services.
>
> The plan is to create MBeans that wrap the configuration and register
> them in a MBean server at the start up of Axis2. Once the MBean server
> is setup, any authorized client can connect to it using the url of the
> MBean server.
>
> A separate servlet (a built in client) is created to provide the web
> user interface for managing Axis2. This servlet connects to the Axis2
> MBean server and performs the management tasks using MBeans.
>
> Regards,
>
> Chathura
>