As I will discuss in the comming JMX Connector HowTo the client
has the following options:
- Use the RMIClientConnectorImpl directly (this will lookup for the
remote JMX Server Connector). Then no local MBeanServer is
necessary but the client has to manage the client-side connectors
by its own
- Create a local MBeanServer and start the ConnectorFactory. The
idea behind is that this local MBeanServer manage the remote,
server-side connectors to different remote computers (not implemented
yet) on different protocols (for the client it always should look the
same). In this case you can load and start the Connector Factory
on a local jBoss instance. Then you can use the remote jBoss
instance on the same management tool as the local one (at the
moment I am not quite sure how this will works in detail but this
is one of my goals during design/coding).
----- Original Message -----
From: Juha Lindfors <[EMAIL PROTECTED]>
To: jBoss Developer <[EMAIL PROTECTED]>
Sent: Tuesday, September 05, 2000 3:01 PM
Subject: Re: [jBoss-Dev] JMX Connector implementation
>
> Hi,
>
> At 11:00 31.8.2000 -0700, you wrote:
> >Hi Geeks
> >
> >The test client will instantiate a local
> >MBeanServer and add the ConnectorFactory as first MBean. By asking the
> >ConnectorFactory your should be able to lookup in your Network the
available
> >servers and its supported protocols (not implemented yet).
>
> Is this what all the JMX clients should do (create local MBeanServer
> instance), or will the ConnectorFactory be available via JNDI for clients
> to lookup?
No, the ConnectorFactory is a client-side instance. The connector enables
the remote
client to work on a remote MBeanServer as it would be a local one. The
Connector-
Factory allows the client to lookup the network for available remote
MBeanServers
and the supported protocols (within the Connector). In comparison with the
Adaptor
the Connector enable the client to manage a remote MBeanServer locally. The
Adaptor
enables the client to manage a remote MBeanServer by sending commands to the
local
MBeanServer ("HTTP/HTML commands") and the Adaptor is running where the
MBeanServer is running. Therefore the Adaptor can only manage one remote
(client
perspectiv) MBeanServer where the Connector enables the client to manage as
many
as you like at the same time within any JMX aware client.
Have fun
Mad Andy
>
> -- Juha
>
>
>
>
