• USA : +1 973 910 5725
  • INDIA: +91 905 291 3388
  • info@tekslate.com
  • Login

JBoss default directory – Part 2

JBoss default directory – Part 2

The default/deployers Directory

alias-deployers-jboss-beans.xml         jboss-threads.deployer/

bsh.deployer/                           jbossweb.deployer/

clustering-deployer-jboss-beans.xml     jbossws.deployer/

dependency-deployers-jboss-beans.xml   jsr77-deployers-jboss-beans.xml

directory-deployer-jboss-beans.xml     logbridge-jboss-beans.xml

ear-deployer-jboss-beans.xml           messaging-definitions-jboss-beans.xml

ejb-deployer-jboss-beans.xml           metadata-deployer-jboss-beans.xml

ejb3.deployer/                         seam.deployer/

hibernate-deployer-jboss-beans.xml     security-deployer-jboss-beans.xml

jboss-aop-jboss5.deployer/             webbeans.deployer/

jboss-ejb3-endpoint-deployer.jar       xnio.deployer/

jboss-jca.deployer/

Contains all the JBoss AS services that are used to recognize and deploy different application and archive types.

Some files in the deployers directory:

hibernate-deployer-jboss-beans.xml – Deployer for Hibernate archives (HAR)

ejb-deployer-jboss-beans.xml – Service responsible for deploying EJB JAR files

ear-deployer-jboss-beans.xml – Service responsible for deploying EAR files

jbossweb.deployer – Service responsible for deploying WAR files

jboss-aop-jboss5.deployer – Deployer that sets up Aspect Manager Service and deploys AOP applications

The default/lib Directory

  1. Directory referred to by the bootstrap code when loading the configuration set
  2. Known within JBoss as jboss.server.lib.url
  3. This directory is for Java code (JARs) to be used both by the deployed applications and JBoss AS services
  4. If you have Java libraries that you need to be made available to all your applications/services, these can be placed in the ${jboss.server.lib.url} directory.
  5. Similarly, you would also use this directory for Java libraries that need to be used by both your applications/services, and JBoss AS services.

A typical example of this is a JDBC driver that is needed by JBoss AS to manage a pool of database connections, as well as your code, which implicitly uses it to interact with the database server.

The default/log Directory

Known within JBoss as jboss.server.log.dir

Default destination directory for JBoss AS log files (3 log files)

boot.log – logs boot process until logging service starts

server.log – takes over once the logging service is initialized from ${jboss.server.config.url}/jboss-log4j.xml

audit.log – audit security

Default startup log priority: DEBUG

STDOUT and STDERR are logged to console

By default:

  1. Log file server.log is rolled over daily (with the “.yyyy-MM-dd” extension)
  2. Existing logs are overwritten on [re]start
  3. Old log files are not automatically cleaned by the server during runtime
  4. Since the logging system is managed by Log4J it can be easily configured to:
  1. Roll over logs hourly
  2. Roll over logs by size (e.g. 500KB)
  3. Automatically remove old logs
  4. Log to SMTP, SNMP, Syslog, JMS, etc.
  5. This directory can be cleared (deleted) between JBoss restarts.
Inclined to build a profession as JBOSS Developer?Then here is the blog post on JBOSS Training Program

The default/tmp Directory

  1. Known in JBoss as jboss.server.temp.dir
  2. Used by JBoss AS to store temporary files such as unpacked service and application deployments
  3. Deployments are automatically removed on server shutdown
  4. This directory can be cleared (deleted) between JBoss restarts.

The default/work Directory

  1. Directory where compiled JSP .java and .class files reside
  2. Also contains cached TLDs
  3. Very useful for debugging problems in JSPs Many JSP errors are easier to fix when developers are able to look at the compiled .java files and match the line numbers to error/exception messages.
  4. Unless you care to preserve compiled JSPs, this directory can be cleared (deleted) between JBoss restarts.
  5. Java Server Pages (.jsp files) are automatically compiled into Java Servlets (.java file) and then into Java byte-code (.class files) by Tomcat (the embedded servlet engine running within JBoss AS).

For indepth understanding on JBoss click on:

Summary
Review Date
Reviewed Item
JBoss default directory - Part 2

“At TekSlate, we are trying to create high quality tutorials and articles, if you think any information is incorrect or want to add anything to the article, please feel free to get in touch with us at info@tekslate.com, we will update the article in 24 hours.”

0 Responses on JBoss default directory - Part 2"

    Leave a Message

    Your email address will not be published. Required fields are marked *

    Site Disclaimer, Copyright © 2016 - All Rights Reserved.

    Support


    Please leave a message and we'll get back to you soon.

    I agree to be contacted via e-mail.