You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/app-service/configure-language-java.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,7 @@ You can use [Azure Web App Plugin for Maven](/java/api/overview/azure/maven/azur
25
25
Otherwise, your deployment method will depend on your archive type:
26
26
27
27
- To deploy .war files to Tomcat, use the `/api/wardeploy/` endpoint to POST your archive file. For more information on this API, please see [this documentation](https://docs.microsoft.com/azure/app-service/deploy-zip#deploy-war-file).
28
+
- To deploy .jar files to Java SE, use the `/api/zipdeploy/` endpoint of the Kudu site. For more information on this API, please see [this documentation](https://docs.microsoft.com/azure/app-service/deploy-zip#rest).
28
29
29
30
Do not deploy your .war using FTP. The FTP tool is designed to upload startup scripts, dependencies, or other runtime files. It is not the optimal choice for deploying web apps.
30
31
@@ -283,6 +284,10 @@ To edit Tomcat's `server.xml` or other configuration files, first take a note of
283
284
284
285
Finally, restart your App Service. Your deployments should go to `D:\home\site\wwwroot\webapps` just as before.
285
286
287
+
## Configure Java SE
288
+
289
+
When running a .JAR application on Java SE on Windows, `server.port` is passed as a command line option as your application starts. You can manually resolve the HTTP port from the environment variable, `HTTP_PLATFORM_PORT`. The value of this environment variable will be the HTTP port your application should listen on.
290
+
286
291
## Java runtime statement of support
287
292
288
293
### JDK versions and maintenance
@@ -297,6 +302,8 @@ Supported JDKs are automatically patched on a quarterly basis in January, April,
297
302
298
303
Patches and fixes for major security vulnerabilities will be released as soon as they become available from AzulSystems. A"major" vulnerability is defined by a base score of 9.0 or higher on the [NISTCommonVulnerabilityScoringSystem, version 2](https://nvd.nist.gov/cvss.cfm).
299
304
305
+
Tomcat8.0 has reached [End of Life (EOL) as of September30, 2018](https://tomcat.apache.org/tomcat-80-eol.html). While the runtime is still avialable on Azure App Service, Azure will not apply security updates to Tomcat 8.0. If possible, migrate your applications to Tomcat 8.5 or 9.0. Both Tomcat 8.5 and 9.0 are available on Azure App Service. See the [official Tomcat site](https://tomcat.apache.org/whichversion.html) for more information.
306
+
300
307
### Deprecation and retirement
301
308
302
309
If a supported Java runtime will be retired, Azure developers using the affected runtime will be given a deprecation notice at least six months before the runtime is retired.
0 commit comments