Re: remote method calling JMX 1.0

rajeshkannan <[email protected]>
Newsgroups gmane.comp.java.mx4j.user
Message-ID <[email protected]>
Hi Simon,
Thank you for you reply.
I have once more query on this same topic.
Remote method calling is possible using XML-RPC communication. Through
Apache's xmlrpc-1.2-b1.jar we can invoke a method which is in remote
class.Shall we use the same XML-RPC communication to invoke the remote
mbean(mbean in different server) ?

thanks again,
Rajesh.


Thanks

simonebordet wrote:
> 
> Hi,
> 
>> In our application we are trying to replace the exisintg RPC mechanism by
>> JMX.we are using weblogic 8.1 which supports only JMX1.0.
>> mx4j is using jmx1.2 which is not compatible with weblogic 8.1.our
>> requirement is basically need to call remote method through HTTP not
>> through
>> RMI (and communication between different servers).
>> We strict to use JMX 1.0 only.but JMX remoting option(JSR 160) is
>> available
>> only with JMX 1.2.So we thought of write our own implmentation i.e HTTP
>> Adaptor with JSR 77 to call remote method.
>> My questions
>> 1) want to know JMX Remoting is possible using JMX 1.0??
> 
> No.
> 
>> 2) if yes can any one provide some example codes?
>> 3) Xmojo is another open source using JMX 1.0. anyone implement that for
>> JMX
>> remoting?
> 
> I have no idea, you should ask to the xmojo project.
> 
> There are 2 things:
> 1. You need to write a web application that shows something to the user.
> In this case, even with JMX 1.0, I think it should be possible to
> write an MBean that starts a Jetty Servlet container with a deployed
> webapp that does what you want, and that communicates to the
> MBeanServer. Your MBean will have a reference to the MBeanServer
> implementing the MBeanRegistration interface.
> 
> 2. You need to call from a remote client, via Java API, using HTTP as
> transport protocol.
> In this case, the task is much more difficult, since you have to
> figure out exactly what has been standardized in JSR 160, but using
> custom code.
> Basically you need to create something called "JMXConnectorServer"
> that takes a MBeanServer; this "JMXConnectorServer" should basically
> start a Jetty Servlet container and a webapp.
> Then you have to decide the application protocol to use; you can use
> an action framework such as WebWork, so that requests from the client
> comes in the form of
> "http://host/jmx/showAttributes.action?objectName=...", and the reply
> can be an XML document.
> Then you have to write a client, something that looks like
> "JMXConnector" that converts method calls to URLs, and sends them to
> the server, and parses the XML sent by the server.
> You need to handle exceptions, to handle serialization/deserialization
> of custom classes, etc.
> It's a difficult and long task, if you believe one that has done it for
> JMX 1.2.
> 
> Simon
> -- 
> http://bordet.blogspot.com
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Mx4j-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mx4j-user
> 
> 

-- 
View this message in context: http://www.nabble.com/remote-method-calling-JMX-1.0-tf2195442.html#a6079167
Sent from the MX4J - User forum at Nabble.com.


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.