February 2008 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2 Management Interfaces

by ataylor

anonymous wrote : But, what you will want to do is make your management interface remotely accessible so you CAN plug into a production management environment (like RHQ) so I can manage your jbm services along side of my other production apps/services. Again, they will be exposed via the JMX route inside JBoss View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130827#4130827 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130827

18 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2 Management Interfaces

by ataylor

anonymous wrote : "@JMX" is not a standard annotation from the JDK libraries, so we can't have it in our core classes since it will introduce a build time dependency on whatever library that comes from (AOP?), and we don't want to force our embedded users to drag in jars they don't need. These can be moved to the configuration View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130825#4130825 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130825

18 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2 Management Interfaces

by mazz＠jboss.com

anonymous wrote : The user is not going to be starting up any other RHQ serves just so they can see the JBM interface, that would suck. Agreed. RHQ is for production management. If you want a small, simple management UI (for, say, developers to use), RHQ is not what you want to use. But, what you will want to do is make your management interface remotely accessible so you CAN plug into a production management environment (like RHQ) so I can manage your jbm services along side of my other production apps/services. So, I can import my jbm services into RHQ's inventory along with my JBossAS servers, and other managed products so, when I *do* deploy jbm in production, I can manage it with all my other things in a single management platform. Because if I have to load up your management console UI separately from my other management tools just to manage jbm, that would suck too. Its a "production" enviroment vs. "development" environment thing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130823#4130823 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130823

18 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2 Management Interfaces

by timfox

"jmesnil" wrote : | For the standalone case, the simple way is to register our POJOs as MBeans on the JVM platform MBeanServer, enable a remote access to it and use a generic JMX console (e.g. jconsole). | | 0 dependencies other than Java 5, everything is already included. | Generic JMX consoles are not as good as specialized ones but they can be sufficient if our MBeans are meaningful enough. Nice thinking....... :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130821#4130821 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130821

18 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2 Management Interfaces

by timfox

"@JMX" is not a standard annotation from the JDK libraries, so we can't have it in our core classes since it will introduce a build time dependency on whatever library that comes from (AOP?), and we don't want to force our embedded users to drag in jars they don't need. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130820#4130820 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130820

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: JMS Topics/Queues in ProfileService

by bytor99999

"scott.stark(a)jboss.org" wrote : Its still sitting on my laptop. I'll check it in later tonight. | Has this been updated? I am unable to create a new Destination through the template, not sure if it is this fix, or about the naming. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130818#4130818 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130818

18 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2 Management Interfaces

by mazz＠jboss.com

This is fine. You do not need JMX - I only brought it up because remoting 2 had MBeans and I thought jbm would still. It doesn't matter - you expose your management however you want. SNMP, your own custom management interface, whatever. Its the plugin developer that needs to connect to your jbm management interface, if you do it your own way, just have the plugin connect to it in "your way". For example, put your jbm management client libraries in the plugin jar and it can connect to it however it wants. It does not have to be JMX, forget I even mentioned it :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130815#4130815 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130815

18 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2 Management Interfaces

by jmesnil

"timfox" wrote : I don't want to end up in a situation where we have to start an MBean server just so we can expose our POJOs For the standalone case, the simple way is to register our POJOs as MBeans on the JVM platform MBeanServer, enable a remote access to it and use a generic JMX console (e.g. jconsole). 0 dependencies other than Java 5, everything is already included. Generic JMX consoles are not as good as specialized ones but they can be sufficient if our MBeans are meaningful enough. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130813#4130813 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130813

18 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2 Management Interfaces

by timfox

"mazz(a)jboss.com" wrote : Let me be clear, too - RHQ does NOT introduce ANY dependencies in YOUR managed product. You have no RHQ code in jbm at all. I only bring up JMX because that's the "standard" way to manage Java apps/services. You can do it however you want. I'm talking about the dependencies that RHQ requires to run. This all needs to run in the JBM "server" (the MC) Let me clarify. User Joe Bloggs will download the JBM "standalone" config which is a super lighweight MC installation running JBM POJOs. The idea is for that JBM instance to provide a management interface. If we use RHQ to do that it needs to be running in that MC too, so it's dependencies are very relevant. The user is not going to be starting up any other RHQ serves just so they can see the JBM interface, that would suck. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130812#4130812 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130812

18 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBM 2 Management Interfaces

by ataylor

ok, so if we are running in the app server then our management interfaces are exposed any way by the MC, we add the tag: @JMX(name = "jboss.messaging:service=JMSMessagingServer", exposedInterface = JMSServerManager.class) | so we can run RHQ with the JMX plugin and expose them that way, Standalone,we right a simple Swing app! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4130810#4130810 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4130810

18 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums February 2008