The directory structure of JBoss

1. Bin directory

The bin directory includes the binaries and scripts needed to start and stop JBoss. These scripts are in the. sh format in the Linux operating system and in the. bat format in the Windows operating system.

2. Client Directory

The client directory contains the library files that are required in the clients application and JBoss communication.

3. Docs directory

Configuration of sample files (database configuration files, etc.)

A more commonly used directory in this directory is the docs, Examples/jca directory, which contains examples of various data source configuration files for different databases. For example, if you use a MySQL database, you can copy the Mysql-ds.xml file under this directory to the Server/xxx/deploy directory.

4. lib Directory

Some jar,jboss are loaded at boot time and are shared by all jboss configurations. If you want to share a library file throughout the app service period, you can put the library file in the server's configured Lib directory.

5. Server directory

Various JBoss configurations, each configured in a different subdirectory, the name of the subdirectory indicates the name of the configuration, and JBoss contains three default configurations, Default,all,minimal, which can be selected at the time of installation.

Server/all JBoss is fully configured to start all services, including clustering and IIOP.

Server/default JBoss's default configuration, which contains the standard services required by most Java EE applications, but does not contain JAXR services, IIOP services, or any other clustered services.

Server/minimal This is the minimum configuration required to start the JBoss server. The minimal configuration starts the log service, Jndi server, and URL deployment scanner to find the (new) app to deploy. This jmx/jboss configuration is best for those situations where you do not need to use any other Java EE technology, but simply use a custom service. It's just a server, not a Web container, no EJB, no JMS support

Sever/default/conf contains the Jboss-service.xml file for the specified JBoss core service. It also includes additional configuration files for core services.

Server/default/data This directory stores persisted data, even if the server has a reboot where the data is not lost. Many JBoss Services store data here, such as hypersonic DB instances. The content here is the cache, clear the cache can clear the content of this side.

The Sever/default/deploy user deploys the application code (jar\war\ear file) here. At the same time, the Deploy directory is also used for hot deployment services (that is, those that can be dynamically added or removed from the running server). As a result, users can see a large number of configuration files in the Deploy directory. In particular, users can see the JMX console app (the unpackaged war file), and the JBoss server periodically scans the directory to find out if there are any component updates or modifications to automate the redeployment of components. This directory is the most frequently accessed, because the deployed code files are placed in this directory. The data source configuration file is also placed under this directory.

Server/default/lib the jar files required for the server configuration. Users can add their own library files, such as the JDBC driver, etc.

Server/default/tmp here is the cache content of the server, clearing the cache can also clear the contents of this area.

Server/default/log log files, view logs can be in this directory.

Where the data, log, TMP, and work directories are created by JBoss. If the user has not started the JBoss server, these directories will not be created.

These content is more important the most need to understand the content, I am here to write some of the content from the book to see, some of their own understanding, there are others to write the content of the PPT, so if there is the same or similar content with everyone, please forgive me, do not pursue my legal responsibility oh, hey.

Directory structure for JBoss