Http://www.blogjava.net/livery/articles/262544.html $ JBOSS-HOME/bin:
Place various script files and related files, including executable script files for JBoss startup and stop.
$ JBOSS-HOME/client:
Stores configuration information and jar files that may be used by Java client applications or external web containers, usually including the jar files required for running the EJB client.
$ JBOSS-HOME/docs:
Save the XML and DTD files referenced in JBoss (examples of how to write the configuration file in JBoss are also provided) and test scripts. $ The JBOSS-HOME/docs/examples directory has a JCA configuration file for the inaccessible database (such as MySQL, Oracle, SQL Server, S, etc.) configuration data source. The associated DTD definition file is located in $ JBOSS-HOME/docs/DTD, where you can view the meaning of an element or attribute in an xml configuration file.
$ JBOSS-HOME/lib:
The jar files required to run the JBoss microkernel are stored here. Do not store your own jar files in this directory.
$ JBOSS-HOME/Server:
Each subdirectory corresponds to a server configuration. This configuration is determined by the parameter "-C <configuration Name>" when running the script file. There are three configuration examples in the Server Directory: All, default, and minimal. Each configuration and installation service is different. Default is the default configuration.
Minimal: load only the minimal services required to start JBoss, such as log service, JNDI, and URL deployment scanner (new deployment is found), excluding web containers, ejbs, and JMS.
ALL: Start all services, including RMI/IIOP, cluster service, and Web Service deployer (default configuration is not loaded ).
When JBoss is started, if run. bat does not contain any parameters, the configuration in the server/default directory is used. To start JBoss with configurations in other directories, you can use the following parameters:
Run-C all
The above command starts JBoss with the configuration information in the all directory. You can also create a directory under the Server Directory and write the configuration file as needed.
The following uses the default directory as an example to describe the directory structure configured on the server.
Conf: the directory contains a jboss-service.xml file for the specified core service, or a file for other service configurations. For example, the jboss-log4j.xml is the configuration file of log4j
Data: This directory is the place where JBoss's built-in database hypersonic stores data and where the jbossmq (the JBoss Implementation of JMS) Stores relevant information.
Deploy: this is the location where J2EE applications (jar, war, and ear files) are deployed. You only need to copy the corresponding files to this directory. This directory is also used for hot deployment of services and JCA resource adapters. Some services are deployed to this directory by default.
JMX-console, which can be accessed after JBoss is started. JBoss periodically scans the deploy directory. When any component changes, JBoss re-deploys the program.
The jboss-web.deployer is the location where the JBoss integration Tomcat is located. You can modify server. XML in the directory to configure the startup port number.
The format of the data source configuration file must be *-Ds. xml. For different database configuration parameters, see the sample documentation under $ JBOSS-HOME/docs/examples/JCA. The parameters are described below.
Lib: stores the jar files and public jar files required for server configuration. For example, you can store JDBC jar files and log4j jar files in this directory. If these jar files already exist under this Lib, the Web application's WEB-INF/lib does not need to be placed again.
Log: stores log information. JBoss uses the Jakarta log4j package to store logs. You can also use this information directly in the program. The default log4j. xml configuration is to output logs to the server. log file in this folder. Jboss-log4j.xml is the default profile
TMP: temporary files generated during decompression during deployment.
Work: the working directory for Tomcat to compile JSP files. If a JSP error occurs, go to the directory to find the corresponding file and locate the problem.
Directory data, log, TMP, and work do not exist after JBoss is installed. They are automatically created when JBoss is running.
After JBoss is started successfully
Check http: // localhost: 8083. a blank page is displayed, which is normal.
Check http: // localhost: 1099. There will be a lot of messy characters, including your IP address and other similar information. 1099 is the default port of the jnp protocol listening name service, and the default port of RMI is the same. In JNDI, we need to use this port.
More articles: JBoss directory structure description-http://harry.iteye.com/blog/368548
JBoss directory structure description
