Tomcat allows you to create multiple server instances for the same installation. The installation directory is identified as CATALINA_HOME , the instance directory is identified as CATALINA_BASE . Here are the steps: Create a base directory for the new instance, for example: /home/nogeek/tomcat1 . Create the subdirectories: mkdir -p /home/nogeek/tomcat/{bin,conf,logs,temp,w... Copy web.xml from the installation directory: cp $CATALINA_HOME/conf/web.xml /home/nogeek/tomcat... Copy logging.properties from the installation directory: cp $CATALINA_HOME/conf/logging.properties /home/no... Create server.xml under tomcat1/conf : <?xml version='1.0' encoding='utf-8'?> <Server ... Create script setenv.sh under tomcat1/bin : # Edit this file to set custom options # Tomcat... Copy startup.sh and shutdown.sh from the installation directory. Add the following two lines to the beginning of each: CATALINA_BASE=/home/nogeek/tomcat1 export CATAL... Create a soft link for catalina.sh in tomcat1/bin : $ ln -s ~/apache-tomcat-7.0.22/bin/catalina.sh cat...

Bring up the "System Properties" dialog (Start -> My Computer -> Right Click -> select Properties ) Click on the Remote tab. Check the box labeled "Allow users to connect remotely to this computer".

When a bean is deployed into the JBoss Microcontainer, it goes through these states: NOT_INSTALLED - the deployment descriptor containing the bean has been parsed along with any annotations on the bean itself. DESCRIBED - any dependencies created by AOP have been added to the bean and custom annotations have been processed. INSTANTIATED - an instance of the bean has been created. CONFIGURED - properties have been injected into the bean along with any references to other beans. CREATE - the create method, if defined on the bean, has been called. START - the start method, if defined on the bean, has been called. INSTALLED - any custom install actions that were defined in the deployment descriptor have been executed and the bean is ready...

These are the steps to create a JBoss 5.1.0 configuration with Tomcat from the built-in minimal configuration. Change directory to $JBOSS_HOME/server . Make a copy of the minimal configuration. cp -R minimal tomcatonly Copy bindingservice.beans from the default configuration. cp -R default/conf/bindingservice.beans tomcatonly... Copy login-config.xml from the default configuration. cp default/conf/login-config.xml tomcatonly/conf/ Edit tomcatonly/conf/jboss-service.xml : Add jars from the common/lib directory: <!-- Load all jars from the JBOSS_DIST/serv... Add the JAAS security manager section (copy from the default profile, and yes, JBoss tomcat can't live without the JBoss JAAS manager). <!-- JAAS security manager and realm mappin... Copy the Tomcat (JBoss web) deployer from the default configuration. cp -R default/deployers/jbossweb.deployer tomcaton... Copy metadata-deployer-jboss-beans.xml and security-deployer-jboss-beans.xml from the default profile. cp default/deployers/metadata-deployer-jboss-b... Copy...

I need to create a Tomcat only configuration for JBoss 3.2.7. These are the steps: Copy the minimal configuration to new configuration: cd $JBOSS_HOME/server cp -R minimal tomcatonly ... Copy tomcat service from the default configuration to the new configuration: cp -R default/deploy/jbossweb-tomcat50.sar tomcato... Edit jboss-tomcat50.sar/META-INF/jboss-service.xml , comment out SecurityManagerService : <!-- A mapping to the server security manager serv... and TransactionManager : <!-- <depends>jboss:service=TransactionManager<... Copy jbosssx.jar , jboss-j2ee.jar and jboss.jar from default/lib to tomcatonly/lib . Edit tomcatonly/conf/jboss-service.xml , change port 1098, 1099 to 1100, 1101. Edit tomcatonly/deploy/jbossweb-tomcat50.sar/server.xml , change port 8080 to 8081; change port 8009 to 8010. Start new configuration with: bin/run.sh -c tomcatonly

It happened on Windows XP with JBoss 5.1.0.GA. This is the stack trace: 2010-07-30 16:39:52,177 ERROR [org.jboss.kernel.pl... According to " (SOLVED) JBAS-7674 solution for JBoss 5.1?? (Windows lock on jnp-service.url) ", the problem seemed to be solved for JBoss 6. In the meanwhile for JBoss 5, disabling Windows Indexing Service seemed to solve the problem. Quote from aforementioned link: It seemed that a file was being locked for some reason, and that file was obviously necessary for JBoss to start. Some further investigation (ok, I admit, I just tried to delete all of JBoss with the faith that it would fail on the locked file), it turns out that file was some file called jnp-service.url in the data directory of the default server. After downloading...

Start remote desktop client by clicking Start and Run, then enter mstsc. Click the "Options" button, select the "Local Resources" tab, check "Clipboard" More options are available when you click the "More..." button (share local drives etc.).

Download JBoss from http://www.jboss.org/jbossas/downloads/ Set environment variables JAVA_HOME and JBOSS_HOME Open a command prompt and enter %JBOSS_HOME%\bin\run.bat ( $JBOSS_HOME/bin/run.sh on *nix). Drop your WAR or EAR file into %JBOSS_HOME%\server\default\deploy