This tutorial has been written for JBoss AS versions 4/5/6 We recommend checking this tutorial for WildFly and JBoss EAP 7: Deploying applications on WildFly using the Web Console and the CLI Also, if you want special focus on remote application deployment, check this article: How to deploy an application remotely with JBoss AS ?
Deploying applications with JBoss AS 4/5/6
Deploying an application with JBoss AS is a straightforward task. If you have access to the host where JBoss is installed you can simply copy the application (.jar , .war, .ear etc) into the JBOSS_HOME/server/<your config>/deploy folder.
Simply substitute <your config> with your server configuration (default, all, minimal, web, standard)
An application can be deployed in two flavours:
- Packed archive (.jar , .war, .ear)
- Exploded directory (directory whose name ends with .jar, .war, .ear)
It is advised to use exploded directory for development and packed archive for production since you can do partial redeployments of the application with exploded directory.
For example if you are deploying a Web application and you want to update just one Servlet, with exploded directory you can do it without redeploying the application.
Also remember that simply “touching” a Java EE configuration file (web.xml , application.xml) causes the application to redeploy. In the same way, touching a JBoss specific configuration file (like jboss-web.xml) will cause the application to redeploy as well.