Standalone Server and JBoss Microcontainer Beans File
6.7. JBoss Microcontainer Beans File The stand-alone server is basically a set of POJOs which are instantiated by the light weight JBoss Microcontainer engine. Note A beans file is also needed when the server is deployed in the JBoss Application Server but this will deploy a slightly different set of objects since the Application Server will already have things like security etc deployed. Let's take a look at an example beans file from the stand-alone server: 1099 localhost 1098 localhost We can see that, as well as the core HornetQ server, the stand-alone server instantiates various different POJOs, lets look at them in turn: JNDIServer Many clients like to look up JMS Objects from JNDI so we provide a JNDI server for them to do that. If you don't need JNDI this can be commented out or removed. MBeanServer In order to provide a JMX management interface a JMS MBean server is necessary in which to register the management objects. Normally this is just the default platform MBean server available in the JVM instance. If you don't want to provide a JMX management interface this can be commented out or removed. Configuration The HornetQ server is configured with a Configuration object. In the default stand-alone set-up it uses a FileConfiguration object which knows to read configuration information from the file system. In different configurations such as embedded you might want to provide configuration information from somewhere else. Security Manager. The security manager used by the messaging server is pluggable. The default one used just reads user-role information from the hornetq-users.xml file on disk. However it can be replaced by a JAAS security manager, or when running inside JBoss Application Server it can be configured to use the JBoss AS security manager for tight integration with JBoss AS security. If you've disabled security altogether you can remove this too. HornetQServer This is the core server. It's where 99% of the magic happens JMSServerManager This deploys any JMS Objects such as JMS Queues, Topics and ConnectionFactory instances from hornetq-jms.xml files on the disk. It also provides a simple management API for manipulating JMS Objects. On the whole it just translates and delegates its work to the core server. If you don't need to deploy JMS Queues, Topics and ConnectionFactorys from server side configuration and don't require the JMS management interface this can be disabled.