Hi Peter
Not quite sure if we should do it this way. Maybe you
have a farm of app. servers w/o a Servlet Engine but
you need one for the MGT server. Also when a server
does down it shouldn't bother the MGT server except
it is his server but then you can just restart it
otherwise you have to make another server the MGT
server.
My design of the MGT server looks like this:
- an MBean on the MGT server knows all the server
part of the management domain
- this MBean works like an MBeanServer for JSR-77
retrieving all the informations, dealing with
events and handling state changes (start of stop)
on the servers (using the JMX RMI-Connector to
access the servers)
- the MGT server uses this MBean to create the
server side presentation (JSR-77 EJB, HTML client
etc.)
- each server others the JSR-77 components as a
MBean
Therefore it is possible to dedicate an application
server as MGT server as well. But when we go a step
further and want to integrates the JBoss 3.0 vision
of an WebOS on the same GUI we need the MGT server
before any other server are up and running.
Andy
> -----Original Message-----
> From: Peter Fagerlund [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, August 08, 2001 12:10 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] A new user interface for JBoss
>
>
> on 1-08-08 19.39, Schaefer, Andreas at [EMAIL PROTECTED] wrote:
>
> > - we have a dedicated, stripped-down application server
> > running the management server
>
> Should'ent all servers in one domain be able to be the MGT
> server for that
> instance domain ? - dynamic swap for service/fail over ?
>
> /peter_f
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
