Hi,
For security reasons, the JMX server binds on a defined socket
(hostname/ipaddress + port number).
You can configure this in jmx.properties (default is 127.0.0.1:9999).
You can pass the host/port to the cli client as parameter in the command
line.
Alternatively, you could also tunnel jmx via socks ([1], never tried it...).
Tks,
- Eric
[1] http://simplygenius.com/2010/08/jconsole-via-socks-ssh-tunnel.html
On 6/05/2011 12:09, kushal soy wrote:
Eric,
thanks for quick reply.
what if I setup my client in remote system? since JMX only supported from
localhost.
Regards,
kushal
On Fri, May 6, 2011 at 3:18 PM, Eric Charles<e...@apache.org> wrote:
Hi,
All management occurs via JMX via jconsole or any other jmx client.
We provide in 3.0-M3 cli script to have command line interface.
Yyes, telnet is removed in 3.0-M3.
The commands are the same, whatever the technology used to store users
information (configurable in usersrepository.xml).
The supported technology at the moment in a classical SQL database.
There are options for LDAP (and JCR I think), but the implementation is
partial (read-only, error-prone, no recipient rewrite table,...).
Hopes this help.
Tks,
- Eric
On 6/05/2011 11:42, kushal soy wrote:
Hi,
as per my understanding There are three way by which user can be manage.
1. JMX ( only from localhost)
2. ldap
3. telnet (deprecated from 3.0M3)
is there any other way?
LDAP seems to be better choice but it introduce dependency with
LDAP
server.
Regards,
kushal
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org
