AWS sap documentation change
Summary
Updated documentation with placeholder variables for SAP instance names, paths, and hostnames. Adjusted formatting for consistency and clarity in command examples.
Security assessment
Changes primarily involve templatizing variables (e.g., <slxascs>, <slxadm>) and formatting adjustments. No explicit security vulnerabilities, mitigations, or new security features are introduced. Modifications to user/group commands (e.g., usermod) are template substitutions rather than security fixes.
Diff
diff --git a/sap/latest/sap-netweaver/sap-netweaver-ha-setup.md b/sap/latest/sap-netweaver/sap-netweaver-ha-setup.md index 48cb097c9..aa8001038 100644 --- a//sap/latest/sap-netweaver/sap-netweaver-ha-setup.md +++ b//sap/latest/sap-netweaver/sap-netweaver-ha-setup.md @@ -63 +63 @@ Install ASCS instance on `slxhost01` with virtual hostname `slxascs`, using the - <swpm location>/sapinst SAPINST_USE_HOSTNAME=slxascs + <swpm location>/sapinst SAPINST_USE_HOSTNAME=<slxascs> @@ -68 +68 @@ Install ERS instance on `slxhost02` with virtual hostname `slxers`, using the hi - <swpm location>/sapinst SAPINST_USE_HOSTNAME=slxers + <swpm location>/sapinst SAPINST_USE_HOSTNAME=<slxers> @@ -120 +120 @@ This is applicable to both cluster nodes. An `haclient` operating system group i - usermod -a -G haclient slxadm + usermod -a -G haclient <slx>adm @@ -157,2 +153 @@ ENSA1 - -_`XX` indicates the start-up order. This value may be different in your install; retain the unchanged value._ +_` _XX_ ` indicates the start-up order. This value may be different in your install; retain the unchanged value._ @@ -180,2 +174 @@ ENSA2 - -_`XX` indicates the start order. This value may be different in your install; retain the unchanged value._ +_` _XX_ ` indicates the start order. This value may be different in your install; retain the unchanged value._ @@ -202 +194 @@ RPM package `sap-suse-cluster-connector` has _dashes_. The executable `/usr/bin/ - /usr/sap/hostctrl/exe/sapcontrol -nr 00 -function RestartService + /usr/sap/hostctrl/exe/sapcontrol -nr <00> -function RestartService @@ -206 +198 @@ RPM package `sap-suse-cluster-connector` has _dashes_. The executable `/usr/bin/ - /usr/sap/hostctrl/exe/sapcontrol -nr 10 -function RestartService + /usr/sap/hostctrl/exe/sapcontrol -nr <10> -function RestartService @@ -212,3 +204,2 @@ RPM package `sap-suse-cluster-connector` has _dashes_. The executable `/usr/bin/ - /usr/sap/hostctrl/exe/sapcontrol -nr 00 -function HACheckFailoverConfig - /usr/sap/hostctrl/exe/sapcontrol -nr 00 -function HACheckConfig - + /usr/sap/hostctrl/exe/sapcontrol -nr <00> -function HACheckFailoverConfig + /usr/sap/hostctrl/exe/sapcontrol -nr <00> -function HACheckConfig @@ -243 +234 @@ See the following example ASCS entry for older version with `systemV` integratio - LD_LIBRARY_PATH=/usr/sap/SLX/ASCS00/exe:$LD_LIBRARY_PATH;export LD_LIBRARY_PATH;/usr/sap/SLX/ASCS00/exe/sapstartsrv pf=/usr/sap/SLX/SYS/profile/SLX_ASCS00_slxascs -D -u slxadm + LD_LIBRARY_PATH=/usr/sap/<SLX>/ASCS<00>/exe:$LD_LIBRARY_PATH;export LD_LIBRARY_PATH;/usr/sap/<SLX>/ASCS<00>/exe/sapstartsrv pf=/usr/sap/<SLX>/SYS/profile/<SLX>_ASCS<00>_<slxascs> -D -u <slxadm> @@ -249,3 +240 @@ To ensure that SAP instance can be managed by the cluster and also manually duri - LD_LIBRARY_PATH=/usr/sap/SLX/ASCS00/exe:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; /usr/sap/SLX/ASCS00/exe/sapstartsrv pf=/usr/sap/SLX/SYS/profile/SLX_ASCS00_slxascs -D -u slxadm - - LD_LIBRARY_PATH=/usr/sap/SLX/ERS10/exe:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; /usr/sap/SLX/ERS10/exe/sapstartsrv pf=/usr/sap/SLX/SYS/profile/SLX_ERS10_slxers -D -u slxadm + LD_LIBRARY_PATH=/usr/sap/<SLX>/ASCS<00>/exe:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; /usr/sap/<SLX>/ASCS<00>/exe/sapstartsrv pf=/usr/sap/<SLX>/SYS/profile/<SLX>_ASCS<00>_<slxascs> -D -u <slxadm> @@ -252,0 +242 @@ To ensure that SAP instance can be managed by the cluster and also manually duri + LD_LIBRARY_PATH=/usr/sap/<SLX>/ERS<10>/exe:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; /usr/sap/<SLX>/ERS<10>/exe/sapstartsrv pf=/usr/sap/<SLX>/SYS/profile/<SLX>_ERS<10>_<slxers> -D -u <slxadm> @@ -260 +250 @@ See the following example ASCS entry for newer version with native `systemd` int - systemctl --no-ask-password start SAPSLX_00 # sapstartsrv pf=/usr/sap/SLX/SYS/profile/SLX_ASCS00_slxascs + systemctl --no-ask-password start <SAPSLX>_<00> # sapstartsrv pf=/usr/sap/<SLX>/SYS/profile/SLX_ASCS<00>_<slxascs> @@ -266,3 +256 @@ To ensure that SAP instance can be managed by the cluster and also manually duri - systemctl --no-ask-password start SAPSLX_00 # sapstartsrv pf=/usr/sap/SLX/SYS/profile/SLX_ASCS00_slxascs - - systemctl --no-ask-password start SAPSLX_10 # sapstartsrv pf=/usr/sap/SLX/SYS/profile/SLX_ERS10_slxers + systemctl --no-ask-password start <SAPSLX_00> # sapstartsrv pf=/usr/sap/<SLX>/SYS/profile/SLX_ASCS<00>_<slxascs> @@ -269,0 +258 @@ To ensure that SAP instance can be managed by the cluster and also manually duri + systemctl --no-ask-password start <SAPSLX_10> # sapstartsrv pf=/usr/sap/<SLX>/SYS/profile/SLX_ERS<10>_<slxers> @@ -284 +273 @@ Temporarily mount the ERS directory (classic only). - mount <nfs.fqdn>:/SLX_ERS10 /usr/sap/SLX/ERS10 + mount <nfs.fqdn>:/<SLX>_ERS<10> /usr/sap/<SLX>/ERS10 @@ -289,2 +278,2 @@ Register the ERS service. - export LD_LIBRARY_PATH=/usr/sap/SLX/ERS10xe - /usr/sap/SLX/ERS10/exe/sapstartsrv pf=/usr/sap/SLX/SYS/profile/SLX_ERS10_slxers -reg + export LD_LIBRARY_PATH=/usr/sap/<SLX>/ERS10xe + /usr/sap/<SLX>/ERS10/exe/sapstartsrv pf=/usr/sap/<SLX>/SYS/profile/SLX_ERS10_slxers -reg @@ -297 +286 @@ Check the existence and state of SAP services. - # systemctl list-unit-files SAP* + systemctl list-unit-files SAP* @@ -311,4 +300,4 @@ Stopping these services also stops the associated SAP instances. - systemctl stop SAPSLX_00.service - systemctl disable SAPSLX_00.service - systemctl stop SAPSLX_10.service - systemctl disable SAPSLX_10.service + systemctl stop SAP<SLX>_<00>.service + systemctl disable SAP<SLX>_<00>.service + systemctl stop SAP<SLX>_<10>.service + systemctl disable SAP<SLX>_<10>.service @@ -319 +308,2 @@ Unmount the ERS directory (classic only). - umount /usr/sap/SLX/ERS10 + umount /usr/sap/<SLX>/ERS + @@ -328 +318,2 @@ Temporarily mount the ASCS directory (classic only). - mount <nfs.fqdn>:/SLX_ASCS00 /usr/sap/SLX/ASCS00 + mount <nfs.fqdn>:/SLX_ASCS00 /usr/sap/<SLX>/ASCS + @@ -333,3 +324,4 @@ Register the ASCS service. - export LD_LIBRARY_PATH=/usr/sap/SLX/ASCS00/exe - /usr/sap/SLX/ASCS00/exe/sapstartsrv pf=/usr/sap/SLX/SYS/profile/SLX_ASCS00_slxascs -reg - systemctl start SAPSLX_00 + export LD_LIBRARY_PATH=/usr/sap/<SLX>/ASCS<00>/exe + /usr/sap/<SLX>/ASCS<00>/exe/sapstartsrv pf=/usr/sap/<SLX>/SYS/profile/SLX_ASCS<00>_<slxascs> -reg + systemctl start SAP<SLX>_ + @@ -340 +332 @@ Check the existence and state of SAP services. - # systemctl list-unit-files SAP* + systemctl list-unit-files SAP* @@ -342,2 +334,2 @@ Check the existence and state of SAP services. - SAPSLX_00.service disabled disabled - SAPSLX_10.service disabled disabled + SAP<SLX>_<00>.service disabled disabled + SAP<SLX>_<10>.service disabled disabled @@ -354,4 +346,4 @@ Stopping these services also stops the associated SAP instances. - systemctl stop SAPSLX_00.service - systemctl disable SAPSLX_00.service - systemctl stop SAPSLX_10.service - systemctl disable SAPSLX_10.service + systemctl stop SAP<SLX>_<00>.service + systemctl disable SAP<SLX>_<00>.service + systemctl stop SAP<SLX>_<10>.service + systemctl disable SAP<SLX>_<10>.service @@ -362 +354,2 @@ Unmount the ASCS directory (classic only). - umount /usr/sap/SLX/ASCS00 + umount /usr/sap/<SLX>/ASCS + @@ -409 +402 @@ If `systemd` is configured, create a config file that defines a dependency betwe - cat > sap_systemd_slx.conf <<_EOF + cat > sap_systemd_<slx>.conf <<_EOF @@ -413,2 +406,2 @@ If `systemd` is configured, create a config file that defines a dependency betwe - After=SAPSLX_00.service - After=SAPSLX_10.service + After=SAP<SLX>_<00>.service + After=SAP<SLX>_<10>.service @@ -429 +422 @@ This is applicable to both cluster nodes. Change the password of the operating s -For a more comprehensive and easily consumable view of cluster activity, SUSE provides additional reporting tools. Many of these tools require access to both nodes without entering a password. SUSE recommends performing this setup for root user. For more details, see _Configuration to collect cluster report as root with root SSH access between cluster nodes_ section in SUSE Documentation [Usage of hb_report for SLES HAE](https://www.suse.com/support/kb/doc/?id=000017501#:~:text=The%20hb_report%20utility%20\(on%20newer,an%20incident%20to%20be%20investigated.). +For a more comprehensive and easily consumable view of cluster activity, SUSE provides additional reporting tools. Many of these tools require access to both nodes without entering a password. SUSE recommends performing this setup for root user. For more details, see _Configuration to collect cluster report as root with root SSH access between cluster nodes_ section in SUSE Documentation [https://www.suse.com/support/kb/doc/?id=000017501#:~:text=The%20hb_report%20utility%20(on%20newer,an%20incident%20to%20be%20investigated](https://www.suse.com/support/kb/doc/?id=000017501#:~:text=The%20hb_report%20utility%20\(on%20newer,an%20incident%20to%20be%20investigated).[Usage of hb_report for SLES HAE]. @@ -443 +436 @@ Use `scp` or a temporary shared NFS location to copy an identical file on the se - scp -p /etc/corosync/authkey root@slxhost02:/etc/corosync + scp -p /etc/corosync/authkey root@<slxhost02>:/etc/corosync