I should clarify number 2 below, I meant to ask how one would go about it from a Ode design perspective (not "how do you do JMX"). i.e. Whether or not to use reuse ProcessAndInstanceManagementImpl, and if so, which object would be responsible for creating and registering the mbean? I see that it is instantiated in ManagementService currently. One could add the creation/registration of an MBean in the enableService() method on that class, but it is Axis2 specific which doesn't help the JBI crowd. That's an example of what I was after with number 2 below. Cheers, Rich
> On 8/23/07, Rich Taylor <[EMAIL PROTECTED]> wrote: > > I'm interested in accessing the process and instance management interfaces > via JMX. I've searched the mailing list archives and see a few references > to JMX but nothing solid. I'm curious if someone has already thought about > how this would be done. I do see the org.apache.ode.bpel.jmx package > which seems to have some initial ideas. Also, I'm looking at this from the > Axis2 perspective but it should apply equally to both distros. > > Two questions come to mind: > 1. Would the MBean(s) externally expose the schema generated PM Interfaces > or would they define a new API, possibly more JMX oriented? > 2. It seems a simple starting point would be to give a > ProcessAndInstanceManagementImpl reference to an MBean then go from there. > The MBean would basically have all it needed at that point. It's not clear > how one would go about doing that, I don't have all that much JMX > experience. Would the OdeServer create the MBean, pass in a reference to > ProcessAndInstanceManagementImpl then register it with the MBean server? > > Thanks, Rich > > >
