Skip to content

Commit 6a97ccb

Browse files
author
Cephas Lin
committed
validation
1 parent 3961bd3 commit 6a97ccb

File tree

6 files changed

+19
-49
lines changed

6 files changed

+19
-49
lines changed

articles/app-service/configure-language-java-apm.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Configure Tomcat, JBoss, or Java SE apps
3-
description: Learn how to configure Tomcat, JBoss, or Java SE apps to run on Azure App Service. This article shows the most common configuration tasks.
2+
title: Configure APM platforms for Tomcat, JBoss, or Java SE apps
3+
description: Learn how to configure APM platforms, such as Application Insights, NewRelic, and AppDynamics, for Tomcat, JBoss, or Java SE app on Azure App Service.
44
keywords: azure app service, web app, windows, oss, java, tomcat, jboss, spring boot, quarkus
55
ms.devlang: java
66
ms.topic: article
@@ -182,7 +182,6 @@ To enable via the Azure CLI, you need to create an Application Insights resource
182182
183183
::: zone-end
184184
185-
186185
---
187186
188187
> [!NOTE]

articles/app-service/configure-language-java-data-sources.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Configure Java apps
3-
description: Learn how to configure Java apps to run on Azure App Service. This article shows the most common configuration tasks.
2+
title: Configure data sources for Tomcat, JBoss, or Java SE apps
3+
description: Learn how to configure data sources for Tomcat, JBoss, or Java SE apps on Azure App Service.
44
keywords: azure app service, web app, windows, oss, java, tomcat, jboss
55
ms.devlang: java
66
ms.topic: article
@@ -12,7 +12,7 @@ author: cephalin
1212
ms.author: cephalin
1313
---
1414

15-
# Configure data sources for a Java app in Azure App Service
15+
# Configure data sources for a Tomcat, JBoss, or Java SE app in Azure App Service
1616

1717
This article shows how to configure data sources in a Java SE, Tomcat, or JBoss app in App Service.
1818

articles/app-service/configure-language-java-deploy-run.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Configure Tomcat, JBoss, or Java SE apps
3-
description: Learn how to configure Tomcat, JBoss, or Java SE apps to run on Azure App Service. This article shows the most common configuration tasks.
2+
title: Deploy and configure Tomcat, JBoss, or Java SE apps
3+
description: Learn how to deploy and configure Tomcat, JBoss, or Java SE apps to run on Azure App Service.
44
keywords: azure app service, web app, windows, oss, java, tomcat, jboss, spring boot, quarkus
55
ms.devlang: java
66
ms.topic: article

articles/app-service/configure-language-java-security.md

Lines changed: 9 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Configure Java apps
3-
description: Learn how to configure Java apps to run on Azure App Service. This article shows the most common configuration tasks.
2+
title: Configure security for Tomcat, JBoss, or Java SE apps
3+
description: Learn how to configure security for Tomcat, JBoss, or Java SE apps on Azure App Service.
44
keywords: azure app service, web app, windows, oss, java, tomcat, jboss
55
ms.devlang: java
66
ms.topic: article
@@ -12,13 +12,13 @@ author: cephalin
1212
ms.author: cephalin
1313
---
1414

15-
## Configure security for a Java app in Azure App Service
15+
# Configure security for a Tomcat, JBoss, or Java SE app in Azure App Service
1616

1717
This article shows how to confgure Java-specific security settings in App Service. Java applications running in App Service have the same set of [security best practices](../security/fundamentals/paas-applications-using-app-services.md) as other applications.
1818

1919
[!INCLUDE [java-variants](includes/configure-language-java/java-variants.md)]
2020

21-
### Authenticate users (Easy Auth)
21+
## Authenticate users (Easy Auth)
2222

2323
Set up app authentication in the Azure portal with the **Authentication and Authorization** option. From there, you can enable authentication using Microsoft Entra ID or social sign-ins like Facebook, Google, or GitHub. Azure portal configuration only works when configuring a single authentication provider. For more information, see [Configure your App Service app to use Microsoft Entra sign-in](configure-authentication-provider-aad.md) and the related articles for other identity providers. If you need to enable multiple sign-in providers, follow the instructions in [Customize sign-ins and sign-outs](configure-authentication-customize-sign-in-out.md).
2424

@@ -70,11 +70,11 @@ For JBoss EAP, `[TODO]`.
7070
7171
::: zone-end
7272
73-
### Configure TLS/SSL
73+
## Configure TLS/SSL
7474
7575
To upload an existing TLS/SSL certificate and bind it to your application's domain name, follow the instructions in [Secure a custom DNS name with an TLS/SSL binding in Azure App Service](configure-ssl-bindings.md). You can also configure the app to enforce TLS/SSL.
7676

77-
### Use KeyVault References
77+
## Use KeyVault References
7878

7979
[Azure KeyVault](../key-vault/general/overview.md) provides centralized secret management with access policies and audit history. You can store secrets (such as passwords or connection strings) in KeyVault and access these secrets in your application through environment variables.
8080

@@ -94,7 +94,7 @@ To inject these secrets in your Tomcat configuration file, use environment varia
9494

9595
::: zone-end
9696

97-
### Use the Java key store in Linux
97+
## Use the Java key store in Linux
9898

9999
By default, any public or private certificates [uploaded to App Service Linux](configure-ssl-certificate.md) are loaded into the respective Java key stores as the container starts. After uploading your certificate, you'll need to restart your App Service for it to be loaded into the Java key store. Public certificates are loaded into the key store at `$JRE_HOME/lib/security/cacerts`, and private certificates are stored in `$JRE_HOME/lib/security/client.jks`.
100100
@@ -105,7 +105,7 @@ More configuration might be necessary for encrypting your JDBC connection with c
105105
- [MongoDB](https://mongodb.github.io/mongo-java-driver/3.4/driver/tutorials/ssl/)
106106
- [Cassandra](https://docs.datastax.com/en/developer/java-driver/4.3/)
107107
108-
#### Initialize the Java key store in Linux
108+
### Initialize the Java key store in Linux
109109
110110
To initialize the `import java.security.KeyStore` object, load the keystore file with the password. The default password for both key stores is `changeit`.
111111
@@ -121,41 +121,12 @@ keyStore.load(
121121
"changeit".toCharArray());
122122
```
123123
124-
#### Manually load the key store in Linux
124+
### Manually load the key store in Linux
125125
126126
You can load certificates manually to the key store. Create an app setting, `SKIP_JAVA_KEYSTORE_LOAD`, with a value of `1` to disable App Service from loading the certificates into the key store automatically. All public certificates uploaded to App Service via the Azure portal are stored under `/var/ssl/certs/`. Private certificates are stored under `/var/ssl/private/`.
127127
128128
You can interact or debug the Java Key Tool by [opening an SSH connection](configure-linux-open-ssh-session.md) to your App Service and running the command `keytool`. See the [Key Tool documentation](https://docs.oracle.com/javase/8/docs/technotes/tools/unix/keytool.html) for a list of commands. For more information on the KeyStore API, see [the official documentation](https://docs.oracle.com/javase/8/docs/api/java/security/KeyStore.html).
129129
130-
# [Linux](#tab/linux)
131-
132-
1. Create an AppDynamics account at [AppDynamics.com](https://www.appdynamics.com/community/register/)
133-
2. Download the Java agent from the AppDynamics website. The file name is similar to *AppServerAgent-x.x.x.xxxxx.zip*
134-
3. [SSH into your App Service instance](configure-linux-open-ssh-session.md) and create a new directory */home/site/wwwroot/apm*.
135-
4. Upload the Java agent files into a directory under */home/site/wwwroot/apm*. The files for your agent should be in */home/site/wwwroot/apm/appdynamics*.
136-
5. In the Azure portal, browse to your application in App Service and create a new Application Setting.
137-
138-
::: zone pivot="java-javase"
139-
140-
Create an environment variable named `JAVA_OPTS` with the value `-javaagent:/home/site/wwwroot/apm/appdynamics/javaagent.jar -Dappdynamics.agent.applicationName=<app-name>` where `<app-name>` is your App Service name. If you already have an environment variable for `JAVA_OPTS`, append the `-javaagent:/...` option to the end of the current value.
141-
142-
::: zone-end
143-
144-
::: zone pivot="java-tomcat"
145-
146-
Create an environment variable named `CATALINA_OPTS` with the value `-javaagent:/home/site/wwwroot/apm/appdynamics/javaagent.jar -Dappdynamics.agent.applicationName=<app-name>` where `<app-name>` is your App Service name. If you already have an environment variable for `CATALINA_OPTS`, append the `-javaagent:/...` option to the end of the current value.
147-
148-
::: zone-end
149-
150-
::: zone pivot="java-jboss"
151-
152-
For **JBoss EAP**, `[TODO]`.
153-
154-
::: zone-end
155-
156-
157-
---
158-
159130
## Next steps
160131
161132
Visit the [Azure for Java Developers](/java/azure/) center to find Azure quickstarts, tutorials, and Java reference documentation.

articles/app-service/includes/configure-language-java/java-variants.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,9 +5,9 @@ ms.topic: include
55
ms.date: 05/17/2024
66
---
77

8-
Azure App Service runs Java web applications on a fully managed servcie in three variants:
8+
Azure App Service runs Java web applications on a fully managed service in three variants:
99

10-
* Java SE - Can run an app deployed as a JAR package that contains an embedded server (such as Spring Boot, Dropwizard, Quarkus, or one with an embeded Tomcat or Jetty server).
10+
* Java SE - Can run an app deployed as a JAR package that contains an embedded server (such as Spring Boot, Dropwizard, Quarkus, or one with an embedded Tomcat or Jetty server).
1111
* Tomcat - The built-in Tomcat server can run an app deployed as a WAR package.
1212
* JBoss EAP - Supported for Linux apps in the Premium v3 and Isolated v2 pricing tiers only. The built-in JBoss EAP server can run an app deployed as a WAR or EAR package.
1313

articles/app-service/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@
5757
- name: Configure Java SE, Tomcat, or JBoss
5858
items:
5959
- name: Deployment and runtime
60-
href: configure-language-java-deployment-runtime.md
60+
href: configure-language-java-deploy-run.md
6161
- name: Data sources
6262
href: configure-language-java-data-sources.md
6363
- name: APM integration

0 commit comments

Comments
 (0)