JBoss default directory - Part 1
The default/conf Directory
bindingservice.beans/ jbossts-properties.xml
bootstrap/ jndi.properties
bootstrap.xml login-config.xml
java.policy props/
jax-ws-catalog.xml standardjboss.xml
jboss-log4j.xml standardjbosscmp-jdbc.xml
jboss-service.xml xmdesc/
Known in JBoss as jboss.server.config.url. Contains a bootstrap descriptor (jboss-service.xml) that defines which services are loaded for the lifetime of the instance
The files in directory ${jboss.server.config.url}
- bootstrap/*: Bootstrap descriptors for core micro container services defined in bootstrap.xml
- bootstrap.xml: Defines the core micro container beans to load during bootstap
- jboss-service.xml: Defines the core JMX services configurations
- jndi.properties: Specifies a set of properties that are passed to JNDI when new InitialDirContext() is called within JBoss
- jboss-log4j.xml: Configuration file for the logging service (Log4J) defining log filters, priorities, and destinations
- login-config.xml: Defines security realms used for authentication and authorization (JAAS)
- props/*.properties: Java property files (usually used for JAAS realms)
- java.policy: Placeholder for security permissions (Java Security Manager). Grant-All by default
- standardjboss.xml: Configuration file for the standard EJB container
- standardjbosscmp-jdbc.xml: Configuration file for the standard JBossCMP engine
- xmdesc/*-mbean.xml: XMBean descriptors for services configured in the jboss-service.xml file
- props/*: property files defining users and roles for the jmx-console
Any changes to files in this directory require a full server restart in order to take effect.
Desired to gain proficiency on JBOSS?Explore the blog post on JBOSS training to become a pro in JBOSS.
The default/data Directory
hypersonic/ wsdl/
tx-object-store/ xmbean-attrs/
- Known in JBoss as jboss.server.data.dir
- Location where some services store private content on the file system
- Hypersonic DB - built-in (by default use as the temporary message store by JMS)
- XMBeans attribute persistence (not enabled by default)
- Transaction objects (temporary storage of objects during the two-phase commit process)
- This directory is not directory exposed to the end users (e.g. though the web interface)
Unless you use Hypersonic DB, the contents of this directory (including the directory itself) can be cleared (deleted) between JBoss restarts.
The default/deploy Directory
CurrencyConverterApp.ear jsr88-service.xml
ROOT.war/ legacy-invokers-service.xml
admin-console.war/ mail-ra.rar
cache-invalidation-service.xml mail-service.xml
ejb2-container-jboss-beans.xml management/
ejb2-timer-service.xml messaging/
ejb3-connectors-jboss-beans.xml monitoring-service.xml
ejb3-container-jboss-beans.xml my-ws.war
ejb3-interceptors-aop.xml printservice.sar/
ejb3-timerservice-jboss-beans.xml profileservice-jboss-beans.xml
fortune.war/ profileservice-secured.jar/
hdscanner-jboss-beans.xml properties-service.xml
hsqldb-ds.xml quartz-ra.rar
http-invoker.sar/ remoting-jboss-beans.xml
jboss-local-jdbc.rar schedule-manager-service.xml
jboss-xa-jdbc.rar scheduler-service.xml
jbossweb.sar/ security/
jbossws.sar/ sqlexception-service.xml
jca-jboss-beans.xml transaction-jboss-beans.xml
jms-ra.rar transaction-service.xml
jmx-console.war/ uuid-key-generator.sar/
jmx-invoker-service.xml vfs-jboss-beans.xml
jmx-remoting.sar/ xnio-provider.jar/
Used for:
- Dynamic deployment content directory
- This is where applications and services are deployed
- Default location used by hot deployment service
- Contains code and configuration files for all services
Some files in the deploy directory include:
- ROOT.war: is the / root web application
- cache-invalidation-service.xml - Custom invalidation of EJB caches via JMS
- ejb2-container-jboss-beans.xml - UserTransaction integration bean for EJB2 container
- ejb2-timer-service.xml - EJB timer service bean
- ejb3-connectors-jboss-beans.xml - EJB3 remoting transport bean
- ejb3-container-jboss-beans.xml - UserTransaction integration bean for EJB3 container
- ejb3-interceptors-aop.xml - AOP for EJB3
- ejb3-timer-service.xml - alternate quartz based timer service
- hdscanner-jboss-beans.xml - hot deployment scanner bean
- hsqldb-ds.xml - Hypersonic embedded database and related connection factories
- http-invoker.sar - Detached invoker that supports RMI/HTTP
- jboss-local-jdbc.rar - JCA to DataSource adaptor for JDBC drivers
- jboss-xa-jdbc.rar - JCA to XADataSource adaptor for JDBC drivers.
- jbossweb.sar - Tomcat Servlet/JSP Engine
- jbossws.sar - The JBoss service that supports web services
- jca-jboss-beans.xml - Connection management facilities for integrating JCA adaptors into JBoss AS
- jms-ra.rar - JMS resource adapter
- messaging/connection-factories-service.xml - DLQ, ExpiryQueue JMS connection factory
- messaging/destinations-service.xml - Message persistence store service
- messaging/jms-ds.xml
- messaging/legacy-service.xml
- messaging/messaging-jboss-beans.xml - JMS security and management beans
- messaging/messaging-service.xml - Core messaging service
- messaging/remoting-bisocket-service.xml - JMS remoting service layer
- jmx-console.war - Web application that provides HTML interface to manage MBean server
- jmx-invoker-service.xml - RMI to JMX adaptor into JBoss
- jmx-remoting.sar -
- legacy-invokers-service.xml -
- jsr-88-service.xml -
- mail-ra.rar - Resource adaptor that provides a JavaMail connector
- mail-service.xml - JavaMail session service (SMTP)
- monitoring-service.xml - Configuration for alert monitors such as email or console listeners
- properties-service.xml - JavaBeans PropertyEditors and definition of system properties
- admin-console.war - admin console for JBoss AS
- scheduler-service.xml - JBoss scheduling service
- sqlexception-service.xml - Vendor-specific SQL exception handler
- security/security-jboss-beans.xml - Security domain related beans
- security/security-policies-jboss-beans.xml - Security authorization for EJB and web authorization
- transaction-jboss-beans.xml - JTA transaction manager related beans
- uuid-key-generator.sar - UUID-based key generation facility
For indepth understanding on JBoss click on: