Merge pull request #501 from SUSE/fs/fix_dead_sbp_links

fix dead sbp links

Author: chabowski

adoc/SAP-Multi-SID.adoc

@@ -123,7 +123,7 @@
 :autoYastGuide12: https://documentation.suse.com/sles/12-SP4/html/SLES-all/book-autoyast.html
 :haAdminGuide12: https://documentation.suse.com/sle-ha/12-SP4/html/SLE-HA-all/book-sleha.html
 :launchPadNotes: https://launchpad.support.sap.com/#/notes/
-:reslibrary: https://documentation.suse.com/sbp/sap/
+:reslibrary: https://documentation.suse.com/sbp/sap-12/
 :refsidadm: <sidadm>
 :refHost1: <host1>
 :refInst: <instanceNumber>
@@ -182,7 +182,7 @@ For the latest product documentation updates, see https://documentation.suse.com
 More guides and best practices documents referring to SUSE Linux Enterprise Server and {sap} can be
 found and downloaded at the SUSE Best Practices Web page:
 
-https://documentation.suse.com/sbp/sap
+https://documentation.suse.com/sbp/sap-12/
 
 Here you get access to guides for {SAPHANA} system replication
 automation and High Availability (HA) scenarios for {SAPNw} and {s4hana}.
@@ -351,7 +351,7 @@ This guide will cover the following scenarios:
 
 Configuration examples in this guide are given with cluster-controlled filesystem resources.
 Nevertheless, also the simple-mount concept based on SAPStartSrv resources
-(https://documentation.suse.com/sbp/sap/html/SAP-S4HA10-setupguide-simplemount-sle15/)
+(https://documentation.suse.com/sbp/sap-15/html/SAP-S4HA10-setupguide-simplemount-sle15/)
 fits well for Multi-SID scenarios.
 // TODO PRIO1: verify simple-mount URL
 
@@ -380,7 +380,7 @@ WARNING: When adding more resources, be aware of the following risks:
 
 ==== Installation
 The installation process is described in the *SUSE Best Practices* guides for {sapS4} and {sapNW}. They can be found here:
-https://documentation.suse.com/sbp/sap
+https://documentation.suse.com/sbp/sap-12/
 
 Repeat the steps for preparing the hosts and infrastructure:
 
@@ -402,7 +402,7 @@ The tested setup was done with up to *five* SID in one cluster.
 === Example ENSA1 in a Two-Node Cluster
 //[[2nensa1]]
 As known from the setup based on the *SUSE Best Practices* document for {sapNW}
-(https://documentation.suse.com/sbp/sap -> {sapNW} High Availability Cluster 7.40 - Setup Guide),
+(https://documentation.suse.com/sbp/sap-12/html/SAP_HA740_SetupGuide_AWS/index.html),
 the cluster integration can be done with a configuration file. Create one configuration file for each SID
 and load them one by one into the cluster. The description below will help to do the steps in the right direction.
 
@@ -743,7 +743,7 @@ _As user _{sid2-lc}adm_, for example on ASCS host, check the SAP system
 === Example ENSA2 in a Two-Node Cluster
 //[[2nensa2]]
 As known from the setup based on the *SUSE Best Practice* document for {sapS4}
-(https://documentation.suse.com/sbp/sap -> {sapS4} - Enqueue Replication 2 High Availability Cluster - Setup Guide),
+(https://documentation.suse.com/sbp/sap-12/html/SAP_S4HA10_SetupGuide-SLE12/index.html),
 the cluster integration can be done with a configuration file. Create one configuration file for each SID
 and load them one by one into the cluster. The following description will help to do the steps in the right direction.
 
@@ -938,7 +938,7 @@ _As user *root*_ showing a cluster configuration for two {sap} systems
 ====
 === Example ENSA1 in a Multi-Node Cluster
 This base setup is already documented in the *SUSE Best Practices* document for {sapNW}
-(https://documentation.suse.com/sbp/sap -> {sapS4} - SAP NetWeaver High Availability Cluster 7.40 - Setup Guide - Best Practice Guide).
+(https://documentation.suse.com/sbp/sap-12/html/SAP_NW740_SLE12_SetupGuide/).
 The OS and node preparation must be done for each future cluster member:
 
 * patch level
@@ -953,7 +953,7 @@ and load them one by one into the cluster. The steps are equal to the steps desc
 
 === Example ENSA2 in a Multi-Node Cluster
 This base setup is already documented in the *SUSE Best Practices* document for {sapS4}
-(https://documentation.suse.com/sbp/sap -> {sapS4} - Enqueue Replication 2 High Availability Cluster - Best Practice Guide).
+(https://documentation.suse.com/sbp/sap-12/html/SAP_S4HA10_SetupGuide-SLE12/).
 The OS and node preparation must be done for each future cluster member:
 
 - patch level
@@ -970,8 +970,8 @@ and load them one by one into the cluster. The steps are equal to the steps desc
 //[[2nensa1ensa2]]
 
 As known from the setup based on the *SUSE Best Practices* document for {sapNW} and {sapS4}
-(https://documentation.suse.com/sbp/sap -> {sapNW} High Availability Cluster 7.40 - Setup Guide)
-(https://documentation.suse.com/sbp/sap -> {sapS4} - Enqueue Replication 2 High Availability Cluster - Setup Guide),
+(https://documentation.suse.com/sbp/sap-12/html/SAP_NW740_SLE12_SetupGuide/)
+(https://documentation.suse.com/sbp/sap-12/html/SAP_S4HA10_SetupGuide-SLE12/),
 the cluster integration can be done with a configuration file. Create one configuration file for each SID
 and load them one by one into the cluster.
 

adoc/SAP-NetWeaver-7.50-SLE-15-Setup-Guide-AliCloud.adoc

@@ -54,7 +54,7 @@ resources are provided at the {sles4sap} resource
 library: https://www.suse.com/products/sles-for-sap/#resource .
 
 This guide and other SAP-specific best practices documents can be downloaded from
-the documentation portal at https://documentation.suse.com/sbp/sap.
+the documentation portal at https://documentation.suse.com/sbp/sap-12/.
 
 Here you can find guides for {SAPHANA} system replication
 automation and HA scenarios for {SAPNw} and {s4hana}.
@@ -138,7 +138,7 @@ because of the focus of the {sapCert} certification.
 If your database is {sapHana}, we recommend to set up the performance-optimized
 system replication scenario using our automation solution {sapHanaSR}. The
 {sapHanaSR} automation should be set up in an own two node cluster. The setup is
-described in a separate best practices document available at http://documentation.suse.com/sbp/sap.
+described in a separate best practices document available at http://documentation.suse.com/sbp/sap-12/.
 In case of using ASE database together with an HADR setup, there is an example in this document.
 
 .Three systems for the certification setup
@@ -986,7 +986,7 @@ _On {myNode2}_
 The MaxDB needs min.40 GB. We use {myDevPartDb} and mount the partition to
 _/sapdb_.
 
-A detailed description can be found link:https://documentation.suse.com/sbp/all/single-html/SAP_NW740_SLE12_SetupGuide/#_installing_db_on_hacert03_example_maxdb[here]
+A detailed description can be found link:https://documentation.suse.com/sbp/sap-15/html/SAP-nw740-sle15-setupguide/index.html#id-installing-db-on-hacert03-example-maxdb[here]
 
 === Installing DB on {myNode3} (example SAP HANA)
 
@@ -995,7 +995,7 @@ indicators. Check the supported configurations at
 https://support.sap.com/en/release-upgrade-maintenance.html#section_1969201630[SAP HANA Hardware Directory]
 and https://www.sap.com/documents/2016/05/e8705aae-717c-0010-82c7-eda71af511fa.html[SAP HANA TDI].
 
-A detailed description can be found at https://documentation.suse.com/sbp/all/single-html/SAP_NW740_SLE12_SetupGuide/#_installing_db_on_hacert03_example_sap_hana[Example HANA DB].
+A detailed description can be found at https://documentation.suse.com/sbp/sap-15/html/SAP-nw740-sle15-setupguide/index.html#id-installing-db-on-hacert03-example-sap-hana[Example HANA DB].
 
 === Installing DB on {myNode3} (example ASE DB)
 

adoc/SAP-S4HA10-setup-simplemount-sle15.adoc

@@ -70,7 +70,7 @@ For additional information on the simple mount architecture, also read:
 
 The former setup with cluster-controlled file system resources as described in
 "SAP S/4 HANA - Enqueue Replication 2 High Availability Cluster - Setup Guide"
-(https://documentation.suse.com/sbp/all/html/SAP_S4HA10_SetupGuide-SLE15)
+(https://documentation.suse.com/sbp/sap-15/html/SAP-S4HA10-setupguide-sle15/)
 will remain supported.
 
 // TODO PRIO2: for the lifetime of {sles4sap} {slesProdVersion}.
@@ -90,7 +90,7 @@ Find white-papers, best-practices guides, and other resources at the
 https://www.suse.com/products/sles-for-sap/resource-library/
 
 - {SUSE} best practices web page:
-https://documentation.suse.com/sbp/sap/
+https://documentation.suse.com/sbp/sap-15/
 
 - Supported high availability solutions by {sles4sap} overview:
 https://documentation.suse.com/sles-sap/sap-ha-support/html/sap-ha-support/article-sap-ha-support.html
@@ -213,8 +213,8 @@ in this guide only manages the {sap} instances ASCS and ERS.
 If your database is {sapHana}, we recommend setting up the performance-optimized
 system replication scenario using the automation solution {sapHanaSR}. The
 {sapHanaSR} automation should be set up in an own two-node cluster. The setup is
-described in a separate best practices document available from the SUSE Best Practices documentation Web page at
-https://documentation.suse.com/en-us/sbp/sap/.
+described in a separate best practices document available from the SUSE Best
+Practices documentation Web page at https://documentation.suse.com/sbp/sap-15/.
 
 .Typical systems for the certification setup
 image::sles4sap_s4hana_simple_fs02.svg[SVG]

adoc/SAP-S4HA10-setupguide-sle15.adoc

@@ -58,7 +58,7 @@ so-called simple-mount setup. The setup with cluster-controlled file systems
 is still supported for existing clusters.
 For deploying new HA clusters, please use the simple-mount setup, described in
 "SAP S/4 HANA - Enqueue Replication 2 High Availability Cluster With Simple Mount - Setup Guide"
-(https://documentation.suse.com/sbp/sap/html/SAP_S4HA10_SetupGuide_SimpleMount-SLE15).
+(https://documentation.suse.com/en-us/sbp/sap-15/html/SAP-S4HA10-setupguide-simplemount-sle15/).
 
 [id="sec.resource"]
 === Additional documentation and resources
@@ -70,7 +70,7 @@ For the latest product documentation updates, see https://documentation.suse.com
 
 More whitepapers, guides and best practices documents referring to SUSE Linux Enterprise Server and SAP can be
 found and downloaded at the SUSE Best Practices Web page:
-https://documentation.suse.com/sbp/sap/
+https://documentation.suse.com/sbp/sap-15/
 
 Here you can access guides for {SAPHANA} system replication
 automation and High Availability (HA) scenarios for {SAPNw} and {s4hana}.
@@ -126,7 +126,7 @@ so-called simple-mount setup. The setup with cluster-controlled file systems
 is still supported for existing clusters.
 For deploying new HA clusters, please use the simple-mount setup, described in
 "SAP S/4 HANA - Enqueue Replication 2 High Availability Cluster With Simple Mount - Setup Guide"
-(https://documentation.suse.com/sbp/sap/html/SAP_S4HA10_SetupGuide_SimpleMount-SLE15).
+(https://documentation.suse.com/en-us/sbp/sap-15/html/SAP-S4HA10-setupguide-simplemount-sle15/).
 
 
 == Overview

adoc/SAP-convergent-mediation-ha-setup-sle15.adoc

@@ -66,7 +66,7 @@ https://documentation.suse.com/
 More whitepapers, guides and best practices documents referring to {SLES} and {SAP}
 can be found and downloaded at the SUSE Best Practices Web page:
 
-https://documentation.suse.com/sbp/sap/
+https://documentation.suse.com/sbp/sap-15/
 
 Here you can access guides for {SAPHANA} system replication automation and High Availability
 (HA) scenarios for {SAPNw} and {s4hana}.

adoc/SAPDI3-Requirements.adoc

@@ -62,7 +62,7 @@ The following list contains the software components needed to install {di} {di_v
 
 * {di} {di_version}
 
-* Secure private registry for container images, for example https://documentation.suse.com/sbp/all/single-html/SBP-Private-Registry/index.html
+* Secure private registry for container images, for example https://documentation.suse.com/cloudnative/suse-private-registry/html/private-registry/[SUSE Private Registry])
 
 * Access to a storage solution providing dynamically physical volumes
 
@@ -132,4 +132,4 @@ the following hardware is required to run an {di} cluster on top of {harvester}
 
 // DI 
 // RAM,CPU, Disk space
-// 320, 80, 940
+// 320, 80, 940

adoc/SAPDI3-SUSE-VMWare-VSAN-Requirements.adoc

@@ -62,7 +62,7 @@ The following list contains the software components needed to install {di} {di_v
 
 * {di} {di_version}
 
-* Secure private registry for container images, for example https://documentation.suse.com/sbp/all/single-html/SBP-Private-Registry/index.html
+* Secure private registry for container images, for example https://documentation.suse.com/cloudnative/suse-private-registry/html/private-registry/[SUSE Private Registry])
 
 * Access to a storage solution providing dynamically physical volumes
 

adoc/SAPDI31-RKE-Instguide.adoc

@@ -81,7 +81,7 @@ The following list contains the software components needed to install SAP DI 3.1
 
 * SAP Data Intelligence 3.1
 
-* Secure private registry for container images, for example https://documentation.suse.com/sbp/all/single-html/SBP-Private-Registry/index.html[SUSE Private Registry Powered by Harbor 2.1])
+* Secure private registry for container images, for example https://documentation.suse.com/cloudnative/suse-private-registry/html/private-registry/[SUSE Private Registry])
 
 * Access to a storage solution providing dynamically physical volumes
 

adoc/SAPDI31-RKE2-Instguide.adoc

@@ -85,7 +85,7 @@ The following list contains the software components needed to install SAP DI 3.1
 
 * SAP Data Intelligence 3.1
 
-* Secure private registry for container images, for example https://documentation.suse.com/sbp/all/single-html/SBP-Private-Registry/index.html
+* Secure private registry for container images, for example https://documentation.suse.com/cloudnative/suse-private-registry/html/private-registry/[SUSE Private Registry])
 
 * Access to a storage solution providing dynamically physical volumes
 

adoc/SAP_HA740_SetupGuide_AWS.adoc

@@ -149,7 +149,7 @@ resources at the SUSE Linux Enterprise Server for SAP applications resource
 library: https://www.suse.com/products/sles-for-sap/resource-library/.
 
 This guide and other SAP specific best practices can be downloaded via
-https://documentation.suse.com/sbp/sap/.
+https://documentation.suse.com/sbp/sap-15/.
 Here you can find guides for {SAPHANA} system replication
 automation and HA scenarios for {SAPNw} and {s4hana}.
 
@@ -285,7 +285,7 @@ instance
 Use the checklist in the appendix to make a note of all information needed
 before starting the installation.
 
-NOTE: With regards to the EFS/NFS filesystems, with SLES for SAP 15, it is now possible to mount these via the Operating System and remove the NFS mount & unmount control to outside of cluster.  This may simplify the ASCS / ERS environment.  Refer to https://documentation.suse.com/sbp/sap/html/SAP-S4HA10-setupguide-simplemount-sle15/index.html for more detail.
+NOTE: With regards to the EFS/NFS filesystems, with SLES for SAP 15, it is now possible to mount these via the Operating System and remove the NFS mount & unmount control to outside of cluster.  This may simplify the ASCS / ERS environment.  Refer to https://documentation.suse.com/sbp/sap-15/html/SAP-S4HA10-setupguide-simplemount-sle15/ for more detail.
 
 ==== Tagging the EC2 Instances