JBoss: Difference between revisions
No edit summary |
|||
| Line 16: | Line 16: | ||
==Stop the server== | ==Stop the server== | ||
/bin/shutdown.bat | /bin/shutdown.bat | ||
==JBoss applications== | |||
===EJB Trail=== | |||
#download EJB3Trail.ear from http://www.jboss.com/docs/trailblazer and copied to deploy directory | |||
Revision as of 22:52, 8 July 2008
Installation
- exctract jboss-4.2.2.GA.zip to C:/Uwes/jboss/
- set JBOSS_HOME to C:\Uwes\jboss\jboss-4.2.2.GA
- extend path to C:\Uwes\jboss\jboss-4.2.2.GA\bin
Configuration
The JBoss Enterprise Application Platform ships with four different server configurations. Within the jboss-4.2.2.GA/server directory, you will find four subdirectories: minimal, default, production and all - one for each server configuration. Each of these configurations provide a different set of services. The default configuration is the one used if you don’t specify another one when starting up the server.
If you want to know which services are configured in each of these instances, look at the jboss-service.xml file in the jboss-4.2.2.GA/server/<instance-name>/conf/ directory and also the configuration files in the jboss-4.2.2.GA/server/<instance-name>/deploy directory.
The directory server configuration you’re using, is effectively the server root while JBoss is running. It contains all the code and configuration information for the services provided by the particular server configuration. It’s where the log output goes, and it’s where you deploy your applications.
My own adjustments
- in C:\Uwes\jboss\jboss-4.2.2.GA\server\default\conf\jboss-service.xml line 259 RmiPort from 1098 to 1498 because of exception at startup
Start the server
/bin/run.bat
Stop the server
/bin/shutdown.bat
JBoss applications
EJB Trail
- download EJB3Trail.ear from http://www.jboss.com/docs/trailblazer and copied to deploy directory