Running java jar file to serve web requests on Azure App Service Web Apps

3 minute read | By Srikanth S.

There are several Java web servers that are supported on Azure App Service Web Apps. But if you have custom code built into a jar which allows it to act as web server, you can accomplish that as well. This blog talks about how we can achieve that. You can accomplish this with any web app from gallery/market place, but in this blog I will start with a blank web app. Below is an screenshot on how to create a blank web app


Once you have finished creating an empty web app, browse to its kudu console command prompt by accessing (remember to change yoursitename with the actual site name) and create a directory under d:\home\site\wwwroot. We will name it bin for now. clip_image002

Now we will copy our jar file into the bin folder created above. You can drag drop the jar file into d:\home\site\wwwroot\bin folder or ftp and copy the jar to d:\home\site\wwwroot\bin folder.


Now we need to setup web.config file to run this jar file. Create a web.config file in d:\home\site\wwwroot folder and add these contents:

<?xml version="1.0" encoding="UTF-8"?>




<add name="httpPlatformHandler" path="*" verb="*"

modules="httpPlatformHandler" resourceType="Unspecified" />


<httpPlatform processPath="%ProgramW6432%\Java\jdk1.8.0_60\bin\java.exe"

arguments=" -Dport.http=%HTTP_PLATFORM_PORT% -jar &quot;%HOME%\site\wwwroot\bin\demojar.jar&quot;"






Make note of these parameters in above code:

  1. processPath: This is where you specify the java executable path. You can use java 7 or 8 which are under %ProgramW6432%\Java folder.
  2. arguments
    • port.http which is set to HTTP_PLATFORM_PORT. This is where your Java Process will listen on. So you need to change your code to listen on this port.
    • path for the jar file. This will be the path to where you place the jar file. In our case, we placed it in d:\home\site\wwwroot\bin.

Also you need to include a MANIFEST.MF file in META-INF folder in your jar file. It should include which class you want to execute. This has to be set to Main-Class parameter. Below is sample code I have for running a simple web server:

package com.msft.demo;




public class Demo {

public static void main(String[] args) throws Exception {

// TODO Auto-generated method stub

// port.http is where WebApp will listen for your Java Process

String listenPort = System.getProperty("port.http");

System.out.println("listenPort is " + listenPort);

int port = Integer.parseInt(listenPort);

HttpServer azServer = HttpServer.create(new InetSocketAddress(port), 0);

azServer.createContext("/", new AzHandler());




static class AzHandler implements HttpHandler {

public void handle(HttpExchange httpExchange) throws IOException {

String response = "Demoing Azure Web Apps Jar Execution";

httpExchange.sendResponseHeaders(200, response.length());

OutputStream os = httpExchange.getResponseBody();






Also here is the sample MANIFEST.MF file for my sample application:

Manifest-Version: 1.0

Main-Class: com.msft.demo.Demo

You can also run without a manifest file, but you will need to include the jar in classpath and call out the exact class name with package path to be executed. Once you have configured your web.config and deployed your jar file, you can browse to your site and you should see this message: “Demoing Azure Web Apps Jar Execution” . You can also look into the httpplatform-stdout_*.log file and it should list the port that your Java process is listening on. If you do not want to run a jar file, there are numerous options available on Web Apps to run your java applications. For more information you can go through this article: