- A Cloud Guru
Deploying an Application with the JBoss EAP Deployment Scanner
JBoss Enterprise Application Platform provides an extensive Java EE-based application server to which we can deploy and manage our applications. Oftentimes, this can be as simple as deploying a provided WAR or EAR file to our configured server. In this lab, we'll specifically explore how to use the standalone deployment scanner to deploy our applications automatically.
Table of Contents
Configure the Deployment Scanner
Move into the JBoss EAP home directory:
Access the JBoss Management CLI:
Move to the deployment scanner node:
Disable auto-deployment scanner:
Exit the CLI:
Add the Application to the Scanned Directory
Look for the
.warfile in the
cloud_user's home directory:
sudo cp ~/kitchensink.war standalone/deployments/kitchensink.war
Since we disabled auto-deployment, we need to create a marker file to trigger deployment:
sudo touch standalone/deployments/kitchensink.war.dodeploy
Immediately look in
standalone/deployments-- notice the
When the file changes to
kitchensink.war.deployed, we'll know our application is ready. We can check this by either looking at our application at
PUBLICIP:8080/kitchensinkor by looking at our list of deployments in either the console or the CLI.
Disable the Application
To disable the application, remove the
kitchensink.war.deployedfile. You can always redeploy the application by adding a
sudo rm standalone/deployments/kitchensink.war.deployed
What's a lab?
Hands-on Labs are real environments created by industry experts to help you learn. These environments help you gain knowledge and experience, practice without compromising your system, test without risk, destroy without fear, and let you learn from your mistakes. Hands-on Labs: practice your skills before delivering in the real world.