If found jmx console clients not so easy to use, this is why we went to
a new cli module (Norman is busy with it).
For the management of remote servers behind a firewall, I use web-based
jmanage (there are other ones I think) - it gives me screens such as
http://james.apache.org/server/3/images/jmx-management/jmx-domainlist.png and
has some applets to display the evolution of attributes in graphs.
Tks,
Eric
On 11/01/2011 17:46, Stefano Bagnara wrote:
2011/1/11 Eric Charles<[email protected]>:
Hi,
You downloaded a fresh snapshot, but the documentation is not so fresh...
(our fault...)
The mentioned "remotemanager" has been removed in favor of pure JMX (read
"Manage via JMX on http://james.apache.org/server/3/manage.html).
To replace the "remotemanager", a new "cli" (command line interface) which
invokes the MBeans is being developed.
In fact, you could already use it with the snapshot you downloaded, but we
still need to write the scripts to call it.
Waiting on cli, don't hesitate to give a try on jconsole to manage james.
About dealing with JMX remotely and with SSH only access, I also
succesfully used jmxclient in past (not with james, but it shouldn't
matter):
http://crawler.archive.org/cmdline-jmxclient/
Also I bookmarked this one, but never used:
http://wiki.cyclopsgroup.org/jmxterm
Stefano
PS: it is tricky to open jmx access through a firewall, this is the
bigger downside of JMX.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
