Skip to content

Commit 70237e4

Browse files
Edits.
1 parent 61375e3 commit 70237e4

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -213,7 +213,7 @@ To deploy WAR files to Tomcat, use the `/api/wardeploy/` endpoint to `POST` your
213213
214214
To deploy WAR files to JBoss EAP, use the `/api/wardeploy/` endpoint to `POST` your archive file. For more information on this API, see [this documentation](./deploy-zip.md#deploy-warjarear-packages).
215215
216-
To deploy EAR files, [use FTP](deploy-ftp.md). Your EAR application is deployed to the context root defined in your application's configuration. For example, if the context root of your app is `<context-root>myapp</context-root>`, then you can browse the site at the `/myapp` path: `http://my-app-name.azurewebsites.net/myapp`. If you want your web app to be served in the root path, ensure that your app sets the context root to the root path: `<context-root>/</context-root>`. For more information, see [Setting the context root of a web application](https://docs.jboss.org/jbossas/guides/webguide/r2/en/html/ch06.html).
216+
To deploy EAR files, [use FTP](deploy-ftp.md). Your EAR application is deployed to the context root defined in your application's configuration. If you want your web app to be served in the root path, ensure that your app sets the context root to the root path: `<context-root>/</context-root>`. For more information, see [Setting the context root of a web application](https://docs.jboss.org/jbossas/guides/webguide/r2/en/html/ch06.html).
217217
218218
::: zone-end
219219
@@ -308,7 +308,7 @@ jcmd <pid> JFR.dump name=continuous_recording filename="/home/recording1.jfr"
308308

309309
#### Timed recording
310310

311-
To take a timed recording, you need the process ID (PID) of the Java application. To find the PID, open a browser to your web app's SCM site at `https://<your-site-name>.scm.azurewebsites.net/ProcessExplorer/`. This page shows the running processes in your web app. Find the process named "java" in the table and copy the corresponding PID.
311+
To take a timed recording, you need the process ID (PID) of the Java application. To find the PID, open your service in the Azure portal. Select **Development Tools** > **Advanced Tools**, then select **Go**. In Kudu, select **Process explorer. This page shows the running processes in your web app. Find the process named "java" in the table and copy the corresponding PID.
312312

313313
Next, open the **Debug Console** in the top toolbar of the SCM site and run the following command. Replace `<pid>` with the PID you copied earlier. This command starts a 30-second profiler recording of your Java application and generates a file named `timed_recording_example.jfr` in the `C:\home` directory.
314314

articles/app-service/configure-language-nodejs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ To show the current Node.js version, run the following command in the [Cloud She
2727
az webapp config appsettings list --name <app-name> --resource-group <resource-group-name> --query "[?name=='WEBSITE_NODE_DEFAULT_VERSION'].value"
2828
```
2929

30-
To show all supported Node.js versions, navigate to `https://<sitename>.scm.azurewebsites.net/api/diagnostics/runtime` or run the following command in the [Cloud Shell](https://shell.azure.com):
30+
To show all supported Node.js versions, run the following command in the [Cloud Shell](https://shell.azure.com):
3131

3232
```azurecli-interactive
3333
az webapp list-runtimes --os windows | grep NODE

0 commit comments

Comments
 (0)