-: JBOSS Server- Application Deployment Methods: -

Method 1: JBOSS Server- Application Deployment using file system (Drag and Drop
Method).

Methods

***********************

 Method 1 :  JBOSS Server- Application Deployment  using file system

 Method 2 : JBOSS Server- Application Deployment using Web Console Management.

Method 3 : JBOSS Server- Application Deployment using Command Line Interface(CLI).

Method 1: JBOSS Server- Application Deployment using file system (Drag and Drop
Method ).

Step 1: start the JBOSS using script OR Run standalone.sh file from JBOSS bin Directory
        cd /JBOSS/jboss-eap-7.0/bin  { In my case}

Screenshot 1:

Step 2: copy the .war file OR use this command from .war file location:

      cp -pr Calendar.War /JBOSS/jboss-eap-7.0/standalone/deployments

 OR

 Use WinSCP.

Screenshot 2: 

Step 3: In this /JBOSS/jboss-eap-7.0/standalone/deployments folder .war file

        automatically get deployed in some time, if JBOSS App server is already started.
 for eg:  Calendar.war.deployed
                 Calendar.war

Screenshot 3:

Step 4: Check the deployed application from Console.  [ at Default Port - 8080]

           http://192.168.0.12:8080/Calendar

Where,
Calendar is Application Context root.

Screenshot 4:

Step 5: you can also verify deployments from JBOSS App server.

Screenshot 5:
 ###################Next Method-2######################
Method 2: JBOSS Server- Application Deployment using Web Console
Management.

Step 1: Step 1: start the JBOSS using script OR Run standalone.sh file from JBOSS bin
Directory
        cd /JBOSS/jboss-eap-7.0/bin  {In my case}

Screenshot 1:

Step 2: Login to console:

Screenshot 2:

Step 3: Click on Deployments and then Add

Screenshot 3:
Step 4: Select on Upload a new deployment --> NEXT

Screenshot 4:

Step 5: Click on Choose File, browse for deployment .war file --> NEXT.

Screenshot 5:

Step 6: Check the Name and Runtime Name.

        Enable: YES /No.

Where,

Enable YES --> Specifies Application Automatically started After

Deployment.

Screenshot 6:
Screenshot 7:

Step 7: Check the deployed application from Console.  [ at Default Port - 8080]

           http://192.168.0.12:8080/Calendar

Where,
Calendar is Application Context root.

Screenshot 8:
 ###################Next Method-3######################

->> Method 3: JBOSS Server- Application Deployment using Command Line

Interface (CLI).

Step 1: start the JBOSS using script OR Run standalone.sh file from JBOSS bin Directory
        cd /JBOSS/jboss-eap-7.0/bin  { In my case}

Screenshot 1:

Step 2:  Run this script line from /JBOSS/jboss-eap-7.0/bin Directory.

         to do the Deployment of Calendar Application.

./jboss-cli.sh -c controller=192.168.0.22:9990 --user=jboss --password=jboss123

--command="deploy /JBOSS/WAR_APP/Calendar.war"

 Where,
        deploy is for .war file deployment with proper path,

  Screenshot 2:    

Step 3: Run this script line from /JBOSS/jboss-eap-7/bin Directory

        to check the deployment status.
  ./jboss-cli.sh -c controller=192.168.0.22:9990 --user=jboss --password=jboss123
--command="deployment-info"

  Screenshot 3:

Step 4; check the application from Console.

Screenshot 4:

Step 5: Check the deployed application from Console.  [ at Default Port - 8080]

           http://192.168.0.12:8080/Calendar 

Where,
Calendar is Application Context root.

Screenshot 5:
Step 6: Run this script line from /JBOSS/jboss-eap-7/bin Directory
        to undeploy the same application.

./jboss-cli.sh -c controller=192.168.0.22:9990 --user=jboss --password=jboss123

--command="undeploy Calendar.war"
   
Screenshot 6:

Step 7: Run this script line from /JBOSS/jboss-eap-7/bin Directory

        to check the deployment status.

  ./jboss-cli.sh -c controller=192.168.0.22:9990 --user=jboss --password=jboss123

--command="deployment-info"

Screenshot 7: