User: schaefera
Date: 01/08/01 15:56:25
Added: jbossmgt architecture.jsp
Log:
Added Project JBossMGT as well as the current JavaDoc to the JSR-77
contribution.
I also changed the strange paths to the pictures in the head.jsp, slogan.jsp
and navigation.jsp therefore they will work also in subdirectories (from
../pictures TO /pictures).
Revision Changes Path
1.1 newsite/jbossmgt/architecture.jsp
Index: architecture.jsp
===================================================================
<jsp:include page="../head.jsp" flush="true" />
<jsp:include page="../slogan.jsp" flush="true" >
<jsp:param name="SLOGAN" value="JBossMGT: Actual Architecture"/>
</jsp:include>
<!-- CONTENT -->
<p class="head">JBoss Management Project: Architecture</p>
<p class="text">
The JBossMGT implementation must support the flexibility of JBoss but
still make JBoss manageable and JSR-77 compliant. In addition it shall
give the future developers guidelines how to add the mangement support.
</p>
<p class="head">Purpose of this document</p>
<p class="text">
This document should reflect the actual stand of the JSR-77 implementation
and support all the developers how to use JSR-77 and the JBoss specific
implementations. When you make changes please <b>add a log entry</b> at the
end of this document.When you disagree with parts of this document please
send an email to the JBoss developer mailing list and we can dicuss this
because this document should only contain what we all (or most of us) agreed
to.
</p>
<p class="head">Basic Architecture</p>
<p class="text">
These are the basic ideas of the architecture for the JSR-77 implementation
<ul>
<li>
A dedicated server host the management server knowing where the
application
servers of the management domains are.
<br><br>
According to the J2EE spec. and the JSR-77 draft an logical application
server can be build upon a farm of physical application server instances
running in multiple JVMs and computers. In JSR-77 the top most element
is the management domain where its application server are grouped into.
This management domain is loosly defined through all the application
deployed within this management domain or just how the administrator
likes to group. To implement this we need to have a dedicated server to
gather the information, handle the events and administer the servers.
Most like this will be a stripped down JBoss server just running the
management server (like IBM WebSphere does now). The rational behind the
dedicated server is that any other solution would have a problem when
the server is going down.
</li>
<li>
Each JSR-77 "Managed Object" is an JMX MBean. This MBean is either an
adjusted
MBean of an existing Module or Wrapper (JDBC Datasource) or a logical
MBean
dealing with more than one existing Module/Wrapper or when we have more
than
one logical MBean per Module/Wrapper.
<br>
Whenever possible we leverage existing modules/MBeans but when major
changes
are necessary the modules/MBeans creates the logical MBeans.
</li>
<li>
All JSR-77 MBeans belongs either to the domain "Management" or contains
the
property "type=management" (or something like this). This allows the
management
server to look up the appropriate JSR-77 MBeans.
</li>
<li>
All JSR-77 MBeans implements the appropriate JSR-77 interface(s).
</li>
<li>
For all JSR-77 MBeans implementing the Statistics Provider the
appropriate
Module delivers the statistics to avoid too much of a performance hit.
On the
other side the JSR-77 MBean executes the requested operations on the
module
to perform administration tasks.
</li>
</ul>
</p>
<p class="head">To Do List</p>
<p class="text">
This list contains all the known issues to be performed in order or their
prioprity.
Please adjust when done.
<ol>
<li>
Get an up to date version of JSR-77 interfaces and classes
</li>
<li>
Create the JSR-77 MBeans implementing the appropriate operations.
</li>
<li>
Creating the management server which is added to the JBoss server as
additional
configuration "/conf/management" with the stripped down configuration
and the
necessary libs and MBeans.
</li>
<li>
Adding some sort of security to the JMX RMI-Connector to avoid a
security issue
because an RMI-Connector is necessary for the management server and all
the
JBoss instance in the management domain.
</li>
<li>
Creating the required MEJB (by JSR-77) running as EJB on the management
server
allowing the management client to manage the management domain, its
applications
and servers.
</li>
</ol>
</p>
<p class="text">
</p>
<p class="text">
</p>
<p class="text">
</p>
<p class="text">
</p>
<p class="text">
</p>
<p class="text">
</p>
<jsp:include page="../navigation.jsp" flush="true" />
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
