Re: [Axis2] JMX front end to Axis2

[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

[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

[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

[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