Skip to content

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.
  • Labs icon Lab
  • A Cloud Guru
Google Cloud Platform icon
Labs

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.

Try for free Contact sales
Google Cloud Platform icon
Labs

Path Info

Level
Clock icon Beginner
Duration
Clock icon 15m
Published
Clock icon Jan 24, 2020

Contact sales

By filling out this form and clicking submit, you acknowledge our privacy policy.

Table of Contents

  1. Challenge

    Configure the Deployment Scanner

    1. Move into the JBoss EAP home directory:

      cd /opt/jboss-eap

    2. Access the JBoss Management CLI:

      sudo ./bin/jboss-cli.sh

    3. Connect:

      connect

    4. Move to the deployment scanner node:

      cd /subsystem=deployment-scanner/scanner=default

    5. Disable auto-deployment scanner:

      :write-attribute(name=auto-deploy-zipped,value=false)

    6. Exit the CLI:

      exit

  2. Challenge

    Add the Application to the Scanned Directory

    1. Look for the .war file in the cloud_user's home directory:

      ls ~

    2. Copy the kitchensink.war file to /opt/jboss-eap/standalone/deployments:

      sudo cp ~/kitchensink.war standalone/deployments/kitchensink.war

    3. Since we disabled auto-deployment, we need to create a marker file to trigger deployment:

      sudo touch standalone/deployments/kitchensink.war.dodeploy

    4. Immediately look in standalone/deployments -- notice the kitchensink.war.isdeploying file:

      ls standalone/deployments/

    5. 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/kitchensink or by looking at our list of deployments in either the console or the CLI.

  3. Challenge

    Disable the Application

    To disable the application, remove the kitchensink.war.deployed file. You can always redeploy the application by adding a .dodeploy marker again:

    sudo rm standalone/deployments/kitchensink.war.deployed
A Cloud Guru - Labs - Deploying an Application with the JBoss EAP Deployment Scanner
Author
A Cloud Guru

The Cloud Content team comprises subject matter experts hyper focused on services offered by the leading cloud vendors (AWS, GCP, and Azure), as well as cloud-related technologies such as Linux and DevOps. The team is thrilled to share their knowledge to help you build modern tech solutions from the ground up, secure and optimize your environments, and so much more!

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.

Provided environment for hands-on practice

We will provide the credentials and environment necessary for you to practice right within your browser.

Guided walkthrough

Follow along with the author’s guided walkthrough and build something new in your provided environment!

Did you know?

On average, you retain 75% more of your learning if you get time for practice.

Start learning by doing today

View Plans