Merge pull request #494 from SUSE/fs/SAP_applications_renaming

SAP Applications -> SAP applications

Author: chabowski

adoc/CaaSP40_DI3X_Install_Guide-docinfo.xml

@@ -23,12 +23,12 @@
 <meta name="social-descr">Installing SAP DI 3 on SUSE CaaSP 4</meta>
 <meta name="productname">
     <productname version="4">SUSE CaaS Platform</productname>
-    <productname version="15 SP1">SUSE Linux Enterprise Server for SAP Applications</productname>
+    <productname version="15 SP1">SUSE Linux Enterprise Server for SAP applications</productname>
 </meta>
 
 <meta name="platform">SUSE CaaS Platform 4</meta>
 <meta name="platform">SAP Data Intelligence 3</meta>
-<meta name="platform">SUSE Linux Enterprise Server for SAP Applications 15 SP1</meta>
+<meta name="platform">SUSE Linux Enterprise Server for SAP applications 15 SP1</meta>
 
 
 <author>

adoc/CaaSP40_DI3X_Install_Guide.adoc

@@ -179,7 +179,7 @@ The following Modules/Products are required on the respective hosts:
 
 * Load balancer host:
 
-** SUSE Linux Enterprise Server for SAP Applications 15 SP1
+** SUSE Linux Enterprise Server for SAP applications 15 SP1
 +
 or
 +
@@ -204,13 +204,13 @@ or
 
 This is only necessary if no other load-balancing device is available.
 In our setup, we describe the installation of a `haproxy` instance.
-`haproxy` is available in the SUSE Linux Enterprise High Availability Extension or SUSE Linux Enterprise Server for SAP Applications.
+`haproxy` is available in the SUSE Linux Enterprise High Availability Extension or SUSE Linux Enterprise Server for SAP applications.
 
 * Install SUSE Linux Enterprise 15 SP1
 
 * Add the "SLE 15 SP1 HA" repository
 +
-(in case of SUSE Linux Enterprise Server for SAP Applications, this is added automatically)
+(in case of SUSE Linux Enterprise Server for SAP applications, this is added automatically)
 
 * Create the `haproxy` configuration
 

adoc/CaaSP4_DH2X_Install_Guide-docinfo.xml

@@ -23,11 +23,11 @@
 <meta name="social-descr">Installing SAP DH2 on SUSE CaaSP 4</meta>
 <meta name="productname">
     <productname version="4">SUSE CaaS Platform</productname>
-     <productname version="15 SP1">SUSE Linux Enterprise Server for SAP Applications</productname>
+     <productname version="15 SP1">SUSE Linux Enterprise Server for SAP applications</productname>
 </meta>
 
 <meta name="platform">SUSE CaaS Platform 4</meta>
-<meta name="platform">SUSE Linux Enterprise Server for SAP Applications 15 SP1</meta>
+<meta name="platform">SUSE Linux Enterprise Server for SAP applications 15 SP1</meta>
 <meta name="platform">SAP Data Hub 2</meta>
 
 <author>

adoc/CaaSP4_DH2X_Install_Guide.adoc

@@ -189,13 +189,13 @@ or
 
 This is only necessary if no other load-balancing device is available.
 In our setup, we describe the setup of a `haproxy` instance.
-`haproxy` is available in the SUSE Linux Enterprise High Availability Extension or in SUSE Linux Enterprise Server for SAP Applications.
+`haproxy` is available in the SUSE Linux Enterprise High Availability Extension or in SUSE Linux Enterprise Server for SAP applications.
 
 * Install SUSE Linux Enterprise 15 SP1
 
 * Add the "SLE 15 SP1 HA" repository 
 +
-(in case of SUSE Linux Enterprise Server for SAP Applications, this is automatically added)
+(in case of SUSE Linux Enterprise Server for SAP applications, this is automatically added)
 
 * Create the `haproxy` configuration
 

adoc/CaaSP_DH2X_Install_Guide-docinfo.xml

@@ -23,12 +23,12 @@
 <meta name="social-descr">Installing SAP DH2 on SUSE CaaSP 3</meta>
 <meta name="productname">
    <productname version="3">SUSE CaaS Platform</productname>
-   <productname version="12 SP5">SUSE Linux Enterprise Server for SAP Applications</productname>
-   <productname version="15 SP1">SUSE Linux Enterprise Server for SAP Applications</productname>
+   <productname version="12 SP5">SUSE Linux Enterprise Server for SAP applications</productname>
+   <productname version="15 SP1">SUSE Linux Enterprise Server for SAP applications</productname>
  </meta>
 
 <meta name="platform">SUSE CaaS Platform 3</meta>
-<meta name="platform">SUSE Linux Enterprise Server for SAP Applications 12 SP5 and 15 SP1</meta>
+<meta name="platform">SUSE Linux Enterprise Server for SAP applications 12 SP5 and 15 SP1</meta>
 <meta name="platform">SAP Data Hub 2</meta>
 
 <authorgroup>

adoc/OS_Security_Hardening_Guide_for_SAP_HANA_SLES12-docinfo.xml

@@ -16,13 +16,13 @@
 </meta>
 <meta name="title">OS Security Hardening Guide for SAP HANA on SLES 12</meta>
 <meta name="description">This document guides through various hardening methods for 
-    SUSE Linux Enterprise Server for SAP Applications 12 to run SAP HANA. </meta>
-<meta name="social-descr">How to harden SLES for SAP Applications to run SAP HANA</meta>
+    SUSE Linux Enterprise Server for SAP applications 12 to run SAP HANA. </meta>
+<meta name="social-descr">How to harden SLES for SAP applications to run SAP HANA</meta>
 <meta name="productname">
-    <productname version="12 SP5">SUSE Linux Enterprise Server for SAP Applications</productname>
+    <productname version="12 SP5">SUSE Linux Enterprise Server for SAP applications</productname>
 </meta>
 
-<meta name="platform">SUSE Linux Enterprise Server for SAP Applications 12</meta>
+<meta name="platform">SUSE Linux Enterprise Server for SAP applications 12</meta>
 <meta name="platform">SAP HANA</meta>  
 
 <authorgroup>
@@ -88,7 +88,7 @@
 
 <abstract>
 
-        <para>This document guides through various hardening methods for SUSE® Linux Enterprise Server for SAP Applications to run SAP HANA.</para>
+        <para>This document guides through various hardening methods for SUSE® Linux Enterprise Server for SAP applications to run SAP HANA.</para>
 
     <para>
         <emphasis role="strong">Disclaimer: </emphasis>

adoc/OS_Security_Hardening_Guide_for_SAP_HANA_SLES12.adoc

@@ -73,7 +73,7 @@ All remaining network ports are closed. The firewall has a broad range of featur
 It is available as RPM package and can be downloaded from SUSE.
 
 Remote Disk Encryption:: 
-Starting with SUSE Linux Enterprise Server for SAP Applications 12 SP2, SUSE introduced a new feature called *Remote Disk Encryption*. 
+Starting with SUSE Linux Enterprise Server for SAP applications 12 SP2, SUSE introduced a new feature called *Remote Disk Encryption*. 
 Classical Disk Encryption - available for years – always required a passphrase entered  during boot. 
 That prevented its use in many setups because each boot needed a manual step.
 Remote Disk Encryption removes this manual step as it allows the encryption keys to be stored safely on a remote key server and to be automatically used during system boot.
@@ -139,7 +139,7 @@ These settings are based on the recommendations of a security audit, which was p
 
 NOTE: Read the SUSE Linux Enterprise Server Security Guide and the SUSE Linux Enterprise Server Hardening Guide for additional measures 
 (see https://documentation.suse.com/). +
-(Choose "SUSE Linux Enterprise Server" instead of "SUSE Linux Enterprise Server for SAP Applications".
+(Choose "SUSE Linux Enterprise Server" instead of "SUSE Linux Enterprise Server for SAP applications".
 
 For each setting the following details are provided:
 
@@ -829,7 +829,7 @@ image::hana_firewall_traffic_flow.svg[alt="Example of a SAP HANA firewall networ
 
 Installation
 ~~~~~~~~~~~~
-The SAP HANA firewall is available in the repositories for SUSE Linux Enterprise Server for SAP Applications 12. 
+The SAP HANA firewall is available in the repositories for SUSE Linux Enterprise Server for SAP applications 12. 
 It extends the SuSEFirewall2 configuration by adding rulesets.
 ----
 zypper install HANA-Firewall
@@ -853,7 +853,7 @@ The configuration can be done:
 * by the YaST SAP HANA Firewall module (`yast hanafirewall`) or 
 * on the command line with `hana-firewall`
 
-Section 9.2 https://documentation.suse.com/sles-sap/12-SP4/single-html/SLES4SAP-guide/#sec-s4s-configure-firewall-hana[Configuring HANA-Firewall] of the SUSE Linux Enterprise Server for SAP Applications Guide describes the SAP HANA-Firewall YaST module and lists some advice regarding multi-tenant HANA databases.
+Section 9.2 https://documentation.suse.com/sles-sap/12-SP4/single-html/SLES4SAP-guide/#sec-s4s-configure-firewall-hana[Configuring HANA-Firewall] of the SUSE Linux Enterprise Server for SAP applications Guide describes the SAP HANA-Firewall YaST module and lists some advice regarding multi-tenant HANA databases.
 
 Prerequisites
 ^^^^^^^^^^^^^
@@ -1073,7 +1073,7 @@ All data processed by SAP HANA can contain sensitive information that need to be
 Depending on the version the data volume, redoing log files or database backups can be encrypted by SAP HANA itself. 
 For details consult the SAP HANA Security Guide (https://help.sap.com).
 
-If the internal encryption of SAP HANA should not or cannot be used, you can encrypt directories containing sensitive data via Remote Disk Encrypting available in SUSE Linux Enterprise Server for SAP Applications.
+If the internal encryption of SAP HANA should not or cannot be used, you can encrypt directories containing sensitive data via Remote Disk Encrypting available in SUSE Linux Enterprise Server for SAP applications.
 When using the internal encryption, the various encryption keys are stored on disk in the SSFS which is located by default in `<home-of-sidadm>/.hdb/<host-identity>/SSFS_HDB.DAT`.
 The SSFS itself is encrypted with the SSFS master key, normally located in $DIR_GLOBAL/hdb/security/ssfs/, which is protected only by file permissions.
 To protect this key or the SSFS, Remote Disk Encrypting can help. It will not store any key of SAP HANA directly, but can encrypt the part of the file system where the keys are located.
@@ -1083,7 +1083,7 @@ It allows to store the encryption keys safely on a remote key server.
 To mount the device, the host contacts the key server on a TLS secured connection. From there, it retrieves the necessary keys automatically to unlock the data.
 The key server should by any means be a dedicated security-hardened and protected system, since anyone with access to this system can retrieve the keys and decrypt the data.
 
-The SUSE Linux Enterprise Server for SAP Applications guide describes the setup of client and server in section 10 https://documentation.suse.com/sles-sap/12-SP4/single-html/SLES4SAP-guide/#cha-s4s-configure-cryptctl[Encrypting Directories Using cryptctl].
+The SUSE Linux Enterprise Server for SAP applications guide describes the setup of client and server in section 10 https://documentation.suse.com/sles-sap/12-SP4/single-html/SLES4SAP-guide/#cha-s4s-configure-cryptctl[Encrypting Directories Using cryptctl].
 
 
 Minimal operating system package election
@@ -1111,7 +1111,7 @@ Depending on the actual setup, further packages might be required.
 
 Required installation patterns and packages
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-The required software for SAP HANA is described in 'SUSE Linux Enterprise Server 12.x for SAP Applications Configuration Guide for SAP HANA' attached to SAP note '1944799 - SAP HANA Guidelines for SLES Operating System Installation'.
+The required software for SAP HANA is described in 'SUSE Linux Enterprise Server 12.x for SAP applications Configuration Guide for SAP HANA' attached to SAP note '1944799 - SAP HANA Guidelines for SLES Operating System Installation'.
 
 The document lists the necessary patterns and additional software packages.
 
@@ -1159,8 +1159,8 @@ zypper lr
 
 This command lists the available software repositories of a SUSE Linux Enterprise Server instance. 
 The output should show the update channel  for the particular Service Pack of  SUSE Linux Enterprise Server 12. 
-On SUSE Linux Enterprise Server for SAP Applications 12, the update channels for the Service Pack of 
-SUSE Linux Enterprise Server for SAP Applications and for the High Availability Extension should be available.
+On SUSE Linux Enterprise Server for SAP applications 12, the update channels for the Service Pack of 
+SUSE Linux Enterprise Server for SAP applications and for the High Availability Extension should be available.
 
 There are many ways to install new patches, and also to selectively install only the security updates. 
 The most common way to install security updates only is to execute the following commands:

adoc/OS_Security_Hardening_Guide_for_SAP_HANA_SLES15-docinfo.xml

@@ -16,14 +16,14 @@
 </meta>
 <meta name="title">OS Security Hardening Guide for SAP HANA on SLES15 SP1</meta>
 <meta name="description">This document guides through various hardening methods for 
-    SUSE Linux Enterprise Server for SAP Applications 15 GA and SP1 to run SAP HANA.</meta>
-<meta name="social-descr">Hardening SLES for SAP Applications 15 to run SAP HANA</meta>
+    SUSE Linux Enterprise Server for SAP applications 15 GA and SP1 to run SAP HANA.</meta>
+<meta name="social-descr">Hardening SLES for SAP applications 15 to run SAP HANA</meta>
 <meta name="productname">
-    <productname version="15 GA">SUSE Linux Enterprise Server for SAP Applications</productname>    
-    <productname version="15 SP1">SUSE Linux Enterprise Server for SAP Applications</productname>
+    <productname version="15 GA">SUSE Linux Enterprise Server for SAP applications</productname>    
+    <productname version="15 SP1">SUSE Linux Enterprise Server for SAP applications</productname>
 </meta>
 
-<meta name="platform">SUSE Linux Enterprise Server for SAP Applications 15 GA and SP1</meta>
+<meta name="platform">SUSE Linux Enterprise Server for SAP applications 15 GA and SP1</meta>
 
 <authorgroup>
     <author>
@@ -88,7 +88,7 @@
 
 <abstract>
 
-        <para>This document guides through various hardening methods for SUSE® Linux Enterprise Server for SAP Applications to run SAP HANA.</para>
+        <para>This document guides through various hardening methods for SUSE® Linux Enterprise Server for SAP applications to run SAP HANA.</para>
 
     <para>
         <emphasis role="strong">Disclaimer: </emphasis>