Hi All, I think Carl's suggestion is a good one, and this area would be a good opportunity for a new person to get involved.
I'm assuming that we can keep is separate from the existing GSOC projects. I agree with Robert's comments about keeping the JMX inetrfaces as I do think they're useful independently, and not very expensive to implement etc. Regards, Marnie On 3/14/08, Robert Greig <[EMAIL PROTECTED]> wrote: > > On 14/03/2008, Carl Trieloff <[EMAIL PROTECTED]> wrote: > > > > I like this idea, but I don't want to have to open a WS connection to > > each broker, I would > > prefer an architecture where the interface to WS-DM could be off-loaded > > to anywhere on the network, on the > > C++ side I would think we would create a WS-DM to AMQP-mgmt bridge. C++ > > uses the > > following to get info in/out of the broker for mgmt > > http://cwiki.apache.org/qpid/management-design-notes.html > > OK this makes sense. Of course if you use a tool such as WinRM or HP > Openview or Tivoli then it can present a consolidated view of the > brokers. > > > I also want to make it possible to payload more than just broker mgmt > > info on the mgnt channel. > > Can you give some examples? > > > Question, go from AMQP-mgmt to WS-DM or to JMX then to WS-DM? I would > > think straight to WS-DM but then > > how would the Java Broker fit in? would we add the AMQP-mgnt to Java > > broker, map JMX to WS-DM on Java side > > etc... going to JMX is an easier community project, as many JMX > > consoles in open source exist, don't know of any OSS > > WS-DM ones exist > > I'm not quite sure of the question? JMX provides an adaptor so that > you can expose any MBean as WS-M. > > If I understand it, you are suggesting a separate process that speaks > AMQP-Management to brokers but itself is exposed over WS-M. In that > case, you'd implement the separate process in terms of JMX and it > would then be able to support native JMX clients and WS-M clients. > > Is AMQP management an approved AMQP spec? > > I would obviously be interested in the thoughts of other users but in > terms of priority, I am not convinced that implementing > AMQP-Management is particularly pressing for the Java broker - there > are other things our users want that offer more advantages. The reason > is that the third party management tools do not speak AMQP-Management > (and almost certainly never will). > > As it stands, by doing some testing with the Sun JMX/WS-M adapter we > can claim out of the box HP OpenView and Microsoft WinRM (and possibly > Tivoli) interoperability. > > We should think about the things we expose over WS-M or SNMP which is > what the users will interact with (indirectly). Ideally these should > be consistent across the C++ and Java projects. > > > Also, does apache WS have a WS-DM impl (Rajith..?) do you know? > > https://wiseman.dev.java.net/ is one. > > RG >
