Hi,

Mark, thanks for bringing this topic on the table.

In the Java world, JMX (Java Management Extensions) is the weapon of
choice for the use cases you are describing. (see
http://java.sun.com/j2se/1.5.0/docs/guide/jmx/index.html)

However, in James 2.2.0 and the upcoming 2.3 release, the support for
JMX within James is limited.

But, work has started to put more management operations in. This can
currently be found in source code only (in the "trunk"). It covers
more or less all operations already available in the telnet console
(RemoteManager).
This functionality will become available in the next major release, I guess.

So this is not an answer to your question, but I am interested in
hearing from you and others what management operations are currently
missing to do the administrative work, so we can steadily improve
James' JMX interface.

When talking about manipulating the config file(s). There are many,
many configuration items within James and the list is growing for the
upcoming 2.3.
It think it would be cool to have a wizzard-like installer application
which is able to present and alter the config file content in a
user-friendly way, separating basic from advanced options, presenting
help texts, guiding the user through the whole setup process.
Maybe someone wants to start some effort in this direction?

 Bernd

On 7/25/06, Mark Brennand <[EMAIL PROTECTED]> wrote:
I am interested in what Administration solutions other JAMES users are
currently using. Still remotely managing via telnet?? Have built custom
management interface?? Using an open source management tool that I haven't
heard of??

Obviously the DB backend lends itself to direct manipulation but I am not
ready to switch all storage mail over to DB just yet. I am, however, ready
to generate a system that can directly manipulate config and environment
vars, offer reporting and analysis via log parsing etc

It would be great to hear what everyone else is doing (or even thinking of
doing).

Regards MB





---------------------------------------------------------------------
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]

Reply via email to