The JBoss architecture consists of the microcontainer, bootstrap beans loaded into the microcontainer, a collection of deployers for loading various deployment types, and various mbean (managed beans - Java objects that represent resources to be managed) and legacy mbean deployments.
The JBoss Microcontainer is a lightweight container for managing POJOs, their deployment, configuration, and lifecycle.
You don't have to run a monolithic server all the time, but may remove components that are not required and integrate additional services as required, into JBoss by writing your own mbeans.
The JBoss AS ships with a number of different server configurations:
<JBoss_Home>\server\
- minimal - bare-bones server, no web container, EJB, or JMS support
- default - a default set of services
- standard - the Java EE5 certified configuration of services
- all - all available services
- web - lightweight web container-oriented configuration of services
<JBoss_Home>\server\<instance-name>\deployers or deploy.
JBoss provides an embedded Hypersonic database along with a default datasource to connect applications to.
When the JBoss server is running, you can get a live view of the server by going to the JMX console application. This is a raw view of JMX beans which make up the server.
In JBoss, log4j is used for logging, controlled by conf/jboss-log4j.xml. The default output file is the server.log.
The JBoss AS comes with clustering support out of the box. Ina JBoss cluster, a node is a JBoss server instance. A cluster (partition) contains a set of nodes that work toward some goal. The JBoss AS supports two types of clustering architectures - client side interceptors (proxies/stubs), and load balancers.
0 comments:
Post a Comment