remove dup sections

Cephas Lin · Cephas Lin · commit 79042a92b763 · 2024-07-17T13:34:45.000+02:00
diff --git a/articles/app-service/configure-language-java-apm.md b/articles/app-service/configure-language-java-apm.md
@@ -184,142 +184,6 @@ To enable via the Azure CLI, you need to create an Application Insights resource
 
 ---
 
-> [!NOTE]
-> 
-
-## Choosing a Java runtime version
-
-App Service allows users to choose the major version of the JVM, such as Java 8 or Java 11, and the patch version, such as 1.8.0_232 or 11.0.5. You can also choose to have the patch version automatically updated as new minor versions become available. In most cases, production apps should use pinned patch JVM versions. This prevents unanticipated outages during a patch version autoupdate. All Java web apps use 64-bit JVMs, and it's not configurable.
-
-::: zone pivot="java-jboss"
-
-If you're using Tomcat, you can choose to pin the patch version of Tomcat. On Windows, you can pin the patch versions of the JVM and Tomcat independently. On Linux, you can pin the patch version of Tomcat; the patch version of the JVM is also pinned but isn't separately configurable.
-
-::: zone-end
-
-If you choose to pin the minor version, you need to periodically update the JVM minor version on the app. To ensure that your application runs on the newer minor version, create a staging slot and increment the minor version on the staging slot. Once you confirm the application runs correctly on the new minor version, you can swap the staging and production slots.
-
-::: zone pivot="java-jboss"
-
-## Clustering
-
-App Service supports clustering for JBoss EAP versions 7.4.1 and greater. To enable clustering, your web app must be [integrated with a virtual network](overview-vnet-integration.md). When the web app is integrated with a virtual network, it restarts, and the JBoss EAP installation automatically starts up with a clustered configuration. The JBoss EAP instances communicate over the subnet specified in the virtual network integration, using the ports shown in the `WEBSITES_PRIVATE_PORTS` environment variable at runtime. You can disable clustering by creating an app setting named `WEBSITE_DISABLE_CLUSTERING` with any value.
-
-> [!NOTE]
-> If you're enabling your virtual network integration with an ARM template, you need to manually set the property `vnetPrivatePorts` to a value of `2`. If you enable virtual network integration from the CLI or Portal, this property is set for you automatically.  
-
-When clustering is enabled, the JBoss EAP instances use the FILE_PING JGroups discovery protocol to discover new instances and persist the cluster information like the cluster members, their identifiers, and their IP addresses. On App Service, these files are under `/home/clusterinfo/`. The first EAP instance to start obtains read/write permissions on the cluster membership file. Other instances read the file, find the primary node, and coordinate with that node to be included in the cluster and added to the file.
-
-> [!Note]
-> You can avoid JBOSS clustering timeouts by [cleaning up obsolete discovery files during your app startup](https://github.com/Azure/app-service-linux-docs/blob/master/HowTo/JBOSS/avoid_timeouts_obsolete_nodes.md)
-
-The Premium V3 and Isolated V2 App Service Plan types can optionally be distributed across Availability Zones to improve resiliency and reliability for your business-critical workloads. This architecture is also known as [zone redundancy](../availability-zones/migrate-app-service.md). The JBoss EAP clustering feature is compatible with the zone redundancy feature.
-
-### Autoscale Rules
-
-When configuring autoscale rules for horizontal scaling, it's important to remove instances incrementally (one at a time) to ensure each removed instance can transfer its activity (such as handling a database transaction) to another member of the cluster. When configuring your autoscale rules in the Portal to scale down, use the following options:
-
-- **Operation**: "Decrease count by"
-- **Cool down**: "5 minutes" or greater
-- **Instance count**: 1
-
-You don't need to incrementally add instances (scaling out), you can add multiple instances to the cluster at a time.
-
-## App Service plans
-
-<a id="jboss-eap-hardware-options"></a>
-
-JBoss EAP is only available on the Premium v3 and Isolated v2 App Service Plan types. Customers that created a JBoss EAP site on a different tier during the public preview should scale up to Premium or Isolated hardware tier to avoid unexpected behavior.
-
-::: zone-end
-
-::: zone pivot="java-tomcat"
-
-## Tomcat baseline configuration
-
-> [!NOTE]
-> This section applies to Linux only.
-
-Java developers can customize the server settings, troubleshoot issues, and deploy applications to Tomcat with confidence if they know about the server.xml file and configuration details of Tomcat. Possible customizations include:
-
-* Customizing Tomcat configuration: By understanding the server.xml file and Tomcat's configuration details, you can fine-tune the server settings to match the needs of their applications.
-* Debugging: When an application is deployed on a Tomcat server, developers need to know the server configuration to debug any issues that might arise. This includes checking the server logs, examining the configuration files, and identifying any errors that might be occurring.
-* Troubleshooting Tomcat issues: Inevitably, Java developers encounter issues with their Tomcat server, such as performance problems or configuration errors. By understanding the server.xml file and Tomcat's configuration details, developers can quickly diagnose and troubleshoot these issues, which can save time and effort.
-* Deploying applications to Tomcat: To deploy a Java web application to Tomcat, developers need to know how to configure the server.xml file and other Tomcat settings. Understanding these details is essential for deploying applications successfully and ensuring that they run smoothly on the server.
-
-When you create an app with built-in Tomcat to host your Java workload (a WAR file or a JAR file), there are certain settings that you get out of the box for Tomcat configuration. You can refer to the [Official Apache Tomcat Documentation](https://tomcat.apache.org/) for detailed information, including the default configuration for Tomcat Web Server.
-
-Additionally, there are certain transformations that are further applied on top of the server.xml for Tomcat distribution upon start. These are transformations to the Connector, Host, and Valve settings.
-
-Note that the latest versions of Tomcat have server.xml (8.5.58 and 9.0.38 onward). Older versions of Tomcat don't use transforms and might have different behavior as a result.
-
-### Connector
-
-```xml 
-<Connector port="${port.http}" address="127.0.0.1" maxHttpHeaderSize="16384" compression="on" URIEncoding="UTF-8" connectionTimeout="${site.connectionTimeout}" maxThreads="${catalina.maxThreads}" maxConnections="${catalina.maxConnections}" protocol="HTTP/1.1" redirectPort="8443"/>
- ```
-* `maxHttpHeaderSize` is set to `16384`
-* `URIEncoding` is set to `UTF-8`
-* `conectionTimeout` is set to `WEBSITE_TOMCAT_CONNECTION_TIMEOUT`, which defaults to `240000`
-* `maxThreads` is set to `WEBSITE_CATALINA_MAXTHREADS`, which defaults to `200`
-* `maxConnections` is set to `WEBSITE_CATALINA_MAXCONNECTIONS`, which defaults to `10000`
- 
-> [!NOTE]
-> The connectionTimeout, maxThreads and maxConnections settings can be tuned with app settings
-
-Following are example CLI commands that you might use to alter the values of conectionTimeout, maxThreads, or maxConnections:
-
-```azurecli-interactive
-az webapp config appsettings set --resource-group myResourceGroup --name myApp --settings WEBSITE_TOMCAT_CONNECTION_TIMEOUT=120000
-```
-```azurecli-interactive
-az webapp config appsettings set --resource-group myResourceGroup --name myApp --settings WEBSITE_CATALINA_MAXTHREADS=100
-```
-```azurecli-interactive
-az webapp config appsettings set --resource-group myResourceGroup --name myApp --settings WEBSITE_CATALINA_MAXCONNECTIONS=5000
-```
-* Connector uses the address of the container instead of 127.0.0.1
- 
-### Host
-
-```xml
-<Host appBase="${site.appbase}" xmlBase="${site.xmlbase}" unpackWARs="${site.unpackwars}" workDir="${site.tempdir}" errorReportValveClass="com.microsoft.azure.appservice.AppServiceErrorReportValve" name="localhost" autoDeploy="true">
-```
-
-* `appBase` is set to `AZURE_SITE_APP_BASE`, which defaults to local `WebappsLocalPath`
-* `xmlBase` is set to `AZURE_SITE_HOME`, which defaults to `/site/wwwroot`
-* `unpackWARs` is set to `AZURE_UNPACK_WARS`, which defaults to `true`
-* `workDir` is set to `JAVA_TMP_DIR`, which defaults `TMP`
-* `errorReportValveClass` uses our custom error report valve
- 
-### Valve
-
-```xml
-<Valve prefix="site_access_log.${catalina.instance.name}" pattern="%h %l %u %t &quot;%r&quot; %s %b %D %{x-arr-log-id}i" directory="${site.logdir}/http/RawLogs" maxDays="${site.logRetentionDays}" className="org.apache.catalina.valves.AccessLogValve" suffix=".txt"/>
- ```
-* `directory` is set to `AZURE_LOGGING_DIR`, which defaults to `home\logFiles`
-* `maxDays` is to `WEBSITE_HTTPLOGGING_RETENTION_DAYS`, which defaults to `0` [forever]
- 
-On Linux, it has all of the same customization, plus:
- 
-* Adds some error and reporting pages to the valve:
-
-    ```xml
-    <xsl:attribute name="appServiceErrorPage">
-        <xsl:value-of select="'${appService.valves.appServiceErrorPage}'"/>
-    </xsl:attribute>
-    
-    <xsl:attribute name="showReport">
-        <xsl:value-of select="'${catalina.valves.showReport}'"/>
-    </xsl:attribute>
-    
-    <xsl:attribute name="showServerInfo">
-        <xsl:value-of select="'${catalina.valves.showServerInfo}'"/>
-    </xsl:attribute>
-    ```
-
-::: zone-end
-
 ## Next steps
 
 Visit the [Azure for Java Developers](/java/azure/) center to find Azure quickstarts, tutorials, and Java reference documentation.
diff --git a/articles/app-service/configure-language-java-data-sources.md b/articles/app-service/configure-language-java-data-sources.md
@@ -417,9 +417,6 @@ To confirm that the datasource was added to the JBoss server, SSH into your weba
 
 ::: zone-end
 
-[!INCLUDE [robots933456](../../includes/app-service-web-configure-robots933456.md)]
-
-
 ## Next steps
 
 Visit the [Azure for Java Developers](/java/azure/) center to find Azure quickstarts, tutorials, and Java reference documentation.
