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/environment/using-an-ase.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,6 @@
2
2
title: Use and manage an App Service Environment
3
3
description: Learn how to create, publish, and scale apps in an App Service Environment. Find all the common tasks in this article.
4
4
author: ccompy
5
-
6
5
ms.assetid: a22450c4-9b8b-41d4-9568-c4646f4cf66b
7
6
ms.topic: article
8
7
ms.date: 8/5/2021
@@ -169,10 +168,10 @@ You can integrate your ASE with Azure Monitor to send logs about the ASE to Azur
169
168
170
169
| Situation | Message |
171
170
|---------|----------|
172
-
| ASE is unhealthy | The specified ASE is unhealthy due to an invalid virtual network configuration. The ASE will be suspended if the unhealthy state continues. Ensure the guidelines defined here are followed: https://docs.microsoft.com/azure/app-service/environment/network-info.|
171
+
| ASE is unhealthy | The specified ASE is unhealthy due to an invalid virtual network configuration. The ASE will be suspended if the unhealthy state continues. Ensure the guidelines defined here are followed: [Networking considerations for an App Service Environment](network-info.md). |
173
172
| ASE subnet is almost out of space | The specified ASE is in a subnet that is almost out of space. There are {0} remaining addresses. Once these addresses are exhausted, the ASE will not be able to scale. |
174
173
| ASE is approaching total instance limit | The specified ASE is approaching the total instance limit of the ASE. It currently contains {0} App Service Plan instances of a maximum 201 instances. |
175
-
| ASE is unable to reach a dependency | The specified ASE is not able to reach {0}. Ensure the guidelines defined here are followed: https://docs.microsoft.com/azure/app-service/environment/network-info.|
174
+
| ASE is unable to reach a dependency | The specified ASE is not able to reach {0}. Ensure the guidelines defined here are followed: [Networking considerations for an App Service Environment](network-info.md). |
176
175
| ASE is suspended | The specified ASE is suspended. The ASE suspension may be due to an account shortfall or an invalid virtual network configuration. Resolve the root cause and resume the ASE to continue serving traffic. |
177
176
| ASE upgrade has started | A platform upgrade to the specified ASE has begun. Expect delays in scaling operations. |
178
177
| ASE upgrade has completed | A platform upgrade to the specified ASE has finished. |
Copy file name to clipboardExpand all lines: articles/virtual-machines/linux/openshift-azure-stack.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,9 +44,9 @@ Make sure you have a valid Red Hat Subscription Manager (RHSM) username, passwor
44
44
45
45
A RHEL image (OpenShift Container Platform) or CentOS image (OKD) needs to be added to your Azure Stack environment to deploy an OpenShift cluster. Contact your Azure Stack administrator to add these images. Instructions can be found here:
Copy file name to clipboardExpand all lines: articles/virtual-machines/workloads/sap/dbms-guide-ha-ibm.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.reviewer: cynthn
14
14
IBM Db2 for Linux, UNIX, and Windows (LUW) in [high availability and disaster recovery (HADR) configuration](https://www.ibm.com/support/knowledgecenter/en/SSEPGG_10.5.0/com.ibm.db2.luw.admin.ha.doc/doc/c0011267.html) consists of one node that runs a primary database instance and at least one node that runs a secondary database instance. Changes to the primary database instance are replicated to a secondary database instance synchronously or asynchronously, depending on your configuration.
15
15
16
16
> [!NOTE]
17
-
> This article contains references to the terms *master* and *slave*, terms that Microsoft no longer uses. When these terms are removed from the software, we’ll remove them from this article.
17
+
> This article contains references to the terms *master* and *slave*, terms that Microsoft no longer uses. When these terms are removed from the software, we'll remove them from this article.
18
18
19
19
This article describes how to deploy and configure the Azure virtual machines (VMs), install the cluster framework, and install the IBM Db2 LUW with HADR configuration.
20
20
@@ -100,7 +100,7 @@ Complete the planning process before you execute the deployment. Planning builds
| Azure Load Balancer | Usage of Basic or Standard (recommended), probe port for Db2 database (our recommendation 62500) **probe-port**. |
102
102
| Name resolution| How name resolution works in the environment. DNS service is highly recommended. Local hosts file can be used. |
103
-
103
+
104
104
For more information about Linux Pacemaker in Azure, see [Set up Pacemaker on SUSE Linux Enterprise Server in Azure](./high-availability-guide-suse-pacemaker.md).
105
105
106
106
## Deployment on SUSE Linux
@@ -128,7 +128,7 @@ Make sure that the selected OS is supported by IBM/SAP for IBM Db2 LUW. The list
128
128
1. Add data disks to the VMs, and then check the recommendation of a file system setup in the article [IBM Db2 Azure Virtual Machines DBMS deployment for SAP workload][dbms-db2].
129
129
130
130
## Create the Pacemaker cluster
131
-
131
+
132
132
To create a basic Pacemaker cluster for this IBM Db2 server, see [Set up Pacemaker on SUSE Linux Enterprise Server in Azure][sles-pacemaker].
133
133
134
134
## Install the IBM Db2 LUW and SAP environment
@@ -473,11 +473,11 @@ If you performed the installation before you created the Db2 HADR configuration,
473
473
Use the J2EE Config tool to check or update the JDBC URL. Because the J2EE Config tool is a graphical tool, you need to have X server installed:
474
474
475
475
1. Sign in to the primary application server of the J2EE instance and execute:
# SQL Server Azure Virtual Machines DBMS deployment for SAP NetWeaver
@@ -316,7 +313,7 @@ This document covers several different areas to consider when deploying SQL Serv
316
313
317
314
In general, you should consider using the most recent SQL Server releases to run SAP workload in Azure IaaS. The latest SQL Server releases offer better integration into some of the Azure services and functionality. Or have changes that optimize operations in an Azure IaaS infrastructure.
318
315
319
-
It is recommended to review the article [What is SQL Server on Azure Virtual Machines (Windows)][https://docs.microsoft.com/azure/azure-sql/virtual-machines/windows/sql-server-on-azure-vm-iaas-what-is-overview] before continuing.
316
+
It is recommended to review the article [What is SQL Server on Azure Virtual Machines (Windows)](../../../azure-sql/virtual-machines/windows/sql-server-on-azure-vm-iaas-what-is-overview.md) before continuing.
320
317
321
318
In the following sections, pieces of parts of the documentation under the link above are aggregated and mentioned. Specifics around SAP are mentioned as well and some concepts are described in more detail. However, it is highly recommended to work through the documentation above first before reading the SQL Server-specific documentation.
322
319
@@ -484,9 +481,10 @@ Database Mirroring as supported by SAP (see SAP Note [965908]) relies on definin
484
481
485
482
As of Cloud-Only deployments, the easiest method is to have another domain setup in Azure to have those DBMS VMs (and ideally dedicated SAP VMs) within one domain.
486
483
487
-
If a domain is not possible, one can also use certificates for the database mirroring endpoints as described here: <https://docs.microsoft.com/sql/database-engine/database-mirroring/use-certificates-for-a-database-mirroring-endpoint-transact-sql>
484
+
If a domain is not possible, one can also use certificates for the database mirroring endpoints as described here:
485
+
[Use Certificates for a Database Mirroring Endpoint (Transact-SQL)](/sql/database-engine/database-mirroring/use-certificates-for-a-database-mirroring-endpoint-transact-sql)
488
486
489
-
A tutorial to set up Database Mirroring in Azure can be found here: <https://docs.microsoft.com/sql/database-engine/database-mirroring/database-mirroring-sql-server>
487
+
A tutorial to set up Database Mirroring in Azure can be found here: [Database Mirroring (SQL Server)](/sql/database-engine/database-mirroring/database-mirroring-sql-server)
490
488
491
489
### SQL Server Always On
492
490
As Always On is supported for SAP on-premises (see SAP Note [1772688]), it is supported in combination with SAP in Azure. There are some special considerations around deploying the SQL Server Availability Group Listener (not to be confused with the Azure Availability Set) since Azure at this point in time does not allow creating an AD/DNS object as it is possible on-premises. Therefore, some different installation steps are necessary to overcome the specific behavior of Azure.
0 commit comments