Deploy Spring boot war in JBOSS EAP server

Spring boot provides embedded tomcat where we can deploy our application easily.  In this article, we will see how to Deploy Spring boot war in JBOSS EAP server.

First, we will create a war file using maven and we will deploy this war file to JBoss server.

Creating a war file.

Open eclipse and create maven project, Don’t forget to check ‘Create a simple project (skip)’click on next. Fill all details(GroupId – BootWarDeployment, ArtifactId – BootWarDeployment and name – BootWarDeployment) and click on finish. Keep packaging as the jar.

Modify the pom.xml.

pom.xml

Modify this one where you have installed JDK

 

Create package com.bootwar and define all files controller class(BookController.java), Book.java and SpringMain.java in this package. We will keep this application simple. Our main purpose is to build(create war) and deploy the application on JBOSS.

Our directory structure looks as below.

Initially, we will have nothing in our target folder since I have had already given the build, we have BootWarDeployment.war in the target folder.

Book.java

BookController.java

SpringMain.java

 

Define application.properties file in the resources folder. Although it should not mandatory because we are going to use JBoss configuration but since I haven’t tested after removing while writing the posts just add it.

application.properties

server.servlet-path=/*

 

We are good now, let’s create a war file using mvn clean install.

We can create a war file using a different way. Sometimes people use eclipse itself to build the application, also we can use the command prompt.  Here we will use CMD for the build.

Go to the code directory where we have pom.xml. For example, currently, I have my code here

Deploy Spring boot war in JBOSS EAP server

 

 

Open cmd and run command – mvn clean install

Deploy Spring boot war in JBOSS EAP server

The build is done. In the target folder, we should have a war file(BootWarDeployment.war).

interview talk – Why our war has created with this name. Can we change it? If you noticed, in pom.xml we have a tag called <finalName>${project.artifactId}</finalName> this one is responsible for the war file name. As of now artifactId(BootWarDeployment) is war name. We can give any name.

 

Deploy Spring boot war in JBOSS.

We have a war file, now we have to deploy on JBoss EAP 7. If you have already server then well and good else you need to download it.

Copy the war file and paste into the deployment folder.

 

 

Go to the bin folder and run the standalone.bat(Window batch file) file. Since we are deploying on windows.

The server will start and our war file is deployed now.

Deploy Spring boot war in JBOSS EAP server

 

Testing of the example.

 

Hit the URL http://127.0.0.1:7780/BootWarDeployment/simpleuri from the browser or postman.

Deploy Spring boot war in JBOSS EAP server

 

Note – Let’s see in the log file.

2019-01-17 21:36:32,641 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:1980/management
2019-01-17 21:36:32,641 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:1980
2019-01-17 21:36:32,641 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) started in 113340ms – Started 504 of 732 services (353 services are lazy, passive or on-demand)
2019-01-17 21:39:45,947 INFO [io.undertow.servlet] (default task-1) Initializing Spring FrameworkServlet ‘dispatcherServlet’

Dont’t use this port(1980), this is admin port there is a different application running on this port.

In standalone.xml we can see which port we are using.

In this example, I have changed the port 7780.

 

That’s all about How to Deploy Spring boot war in JBOSS EAP server. If you feel any problem to run the application leave the message in the comment box.

You may like

 

JBoss deployment docs.

Top