Chapter 4. The Default Server Configuration File Set

The JBOSS_DIST/server directory contains one or more configuration file sets. The default JBoss configuration file set is located in the JBOSS_DIST/server/default directory. JBoss allows you to add more than one configuration set so a server can easily be run using alternate configurations. Creating a new configuration file set typically starts with copying the default file set into a new directory name and then modifying the configuration files as desired. Figure 4.1, “An expanded view of the default server configuration file set conf and deploy directories” below shows the contents of the default configuration file set.

An expanded view of the default server configuration file set conf and deploy directories

Figure 4.1. An expanded view of the default server configuration file set conf and deploy directories

The files in the conf directory are explained in the following section.


This is a minimalist example of the jboss-service.xml configuration file. It is the jboss-service.xml file used in the minimal configuration file set.


jboss-service.xml defines the core services configurations.

The file specifies the JNDI InitialContext properties that are used within theNS-MYC10 JBoss server when an InitialContext is created using the no-argument constructor.


This file configures the Apache log4j framework category priorities and appenders used by the JBoss server code.


This file contains sample server side authentication configurations that are applicable when using JAVAS based security.


The props directory contains the users and roles property files for the jmx-console.


This file provides the default configuration for the legacy EJB 1.1 CMP engine.


This file provides the default container configurations.


This file provides a default configuration file for the JBoss CMP engine.


The xmdesc directory contains XMBean descriptors for several services configured in the jboss-service.xml file.

The following are the files in the deploy directory and their function.


This file configures the bean shell deployer, which deploys bean shell scripts as JBoss services.


This is a service that allows for custom invalidation of the EJB caches via JMS notifications. It is disabled by default.


This is a service that provides support for J2EE application clients. It manages the java:comp/env enterprise naming context for client applications based on the application-client.xml descriptor.


The EAR deployer is the service responsible for deploying J2EE EAR files.


The EJB deployer is the service responsible for deploying J2EE EJB JAR files.


hsqldb-ds.xml configures the Hypersonic embedded database service configuration file. It sets up the embedded database and related connection factories.


http-invoker.sar contains the detached invoker that supports RMI over HTTP. It also contains the proxy bindings for accessing JNDI over HTTP.


This service configure the AspectManagerService and deploys JBoss AOP applications.


jboss-bean.deployer provides the JBoss microcontainer, which deploys POJO services wrapped in .beans files.


jboss-ha-local-jdbc.rar is an experimental version of jboss-local-jdbc.rar that supports datasource failover.


jboss-ha-xa-jdbc.rar is an experimental version of jboss-xa-jdbc.rar that supports datasource failover.


jboss-local-jdbc.rar is a JCA resource adaptor that implements the JCA ManagedConnectionFactory interface for JDBC drivers that support the DataSource interface but not JCA.


jboss-xa-jdbc.rar is a JCA resource adaptor that implements the JCA ManagedConnectionFactory interface for JDBC drivers that support the XADataSource interface.


jbossjca-service.sar is the application server implementation of the JCA specification. It provides the connection management facilities for integrating resource adaptors into the JBoss server.


The jbossweb-tomcat55.sar directory provides the Tomcat 5.5 servlet engine. The SAR is unpacked rather than deployed as a JAR archive so that the tomcat configuration files can be easily edited.


jbossws14.sar provides J2EE web services support.


hsqldb-jdbc-state-service.xml provides JMS state management using Hypersonic.


hsqldb-jdbc2-service.xml configures JMS persistence and caching using Hypersonic. It also contains the DestinationManager MBean, which is the core service for the JMS implementation.


jbossmq-destinations-service.xml configures a number of JMS queues and topics used by the JMS unit tests.


jbossmq-httpil.sar provides a JMS invocation layer that allows the use of JMS over HTTP.


The jbossmq-service.xml file configures the core JBossMQ JMS service.


The jms-ds.xml file configures the JBossMQ JMS provider for use with the jms-ra.rar JCA resource adaptor.


jms-ra.rar is a JCA resource adaptor that implements the JCA ManagedConnectionFactory interface for JMS connection factories.


jvm-il-service.xml configures the in-JVM JMS transport invocation layer.


uil2-service.xml configures the JMS version 2 unified invocation layer. Its a fast and reliable custom socket based transport that should be used for messaging between JVMs.


The jmx-console.war directory provides the JMX Console. The JMX Console provides a simple web interface for managing the MBean server.


jmx-invoker-service.sar is an unpacked MBean service archive that exposes a subset of the JMX MBeanServer interface methods as an RMI interface to enable remote access to the JMX core functionality. This is similar to the legacy jmx-rmi-adaptor.sar, with the difference that the transport is handled by the detached invoker architecture.


jsr-88-service.xml provides the JSR 88 remote deployment service.


mail-ra.rar is a resource adaptor that provides a JavaMail connector.


The mail-service.xml file is an MBean service descriptor that provides JavaMail sessions for use inside the JBoss server.


console-mgr.sar provides the Web Console. It is a web application/applet that provide a richer view of the JMX server management data than the JMX console. You may view the console using the URL http://localhost:8080/web-console/.


The monitoring-service.xml file configures alert monitors like the console listener and email listener used by JMX notifications.


The properties-service.xml file is an MBean service descriptor that allows for customization of the JavaBeans PropertyEditors as well as the definition of system properties.

scheduler-service.xml, schedule-manager-service.xml

The scheduler-service.xml and schedule-manager-service.xml files are MBean service descriptors that provide a scheduling type of service.


The sqlexception-service.xml file is an MBean service descriptor for the handling of vendor specific SQLExceptions.


The uuid-key-generator.sar service provides a UUID-based key generation facility.

The all configuration contains several addition services.


This service configures clustering communication for most clustered services in JBoss.


This provides the HA singleton service, allowing JBoss to manage services that must be active on only one node of a cluster.


farm-service.xml provides the farm service, which allows for cluster-wide deployment and undeployment of services.


This service provides HTTP tunneling support for clustered environments.


This provides IIOP invocation support.


This service provides UDDI lookup services.


This is a JMX to SNMP adaptor. It allows for the mapping of JMX notifications onto SNMP traps.


Provides AOP support for field-level HTTP session replication.

When installing EJB3 support, several additional EJB3 services are made available.


This service provides the AOP interceptor stack configurations for EJB3 bean types.


This service deploys EJB3 applications into JBoss.


This is a Java 5 version of the AOP deployer. The AOP deployer configures the AspectManagerService and deploys JBoss AOP applications.


This services provides Java EE 5 web services support.

Finally, in the EJB3 all configuration adds two additional services:


This services provides replication and failover for EJB3 stateful session beans.


This services provides a clustered cache for EJB3 entity beans.