AWS sap documentation change
Summary
Updated documentation to use placeholder syntax (angle brackets) for variables in hostnames, commands, paths, and service names. Reformatted some sections for clarity and consistency.
Security assessment
The changes primarily involve formatting updates to use placeholder syntax (e.g., <rhxhost01> instead of rhxhost01) and command corrections. There is no evidence of security vulnerability fixes, security feature additions, or security-related configuration changes. Updates focus on documentation clarity rather than addressing security risks.
Diff
diff --git a/sap/latest/sap-netweaver/rhel-sap-netweaver-ha-setup.md b/sap/latest/sap-netweaver/rhel-sap-netweaver-ha-setup.md index 2957d7bf7..b260b97fd 100644 --- a//sap/latest/sap-netweaver/rhel-sap-netweaver-ha-setup.md +++ b//sap/latest/sap-netweaver/rhel-sap-netweaver-ha-setup.md @@ -60 +60 @@ The commands in this section use the example values provided in [Define referenc -Install ASCS instance on `rhxhost01` with virtual hostname `rhxascs`, using the high availability option of Software Provisioning Manager (SWPM) tool. You can use the `SAPINST_USE_HOSTNAME` parameter to install SAP using a virtual hostname. +Install ASCS instance on `<rhxhost01>` with virtual hostname `rhxascs`, using the high availability option of Software Provisioning Manager (SWPM) tool. You can use the `SAPINST_USE_HOSTNAME` parameter to install SAP using a virtual hostname. @@ -63 +63 @@ Install ASCS instance on `rhxhost01` with virtual hostname `rhxascs`, using the - <swpm location>/sapinst SAPINST_USE_HOSTNAME=rhxascs + <swpm location>/sapinst SAPINST_USE_HOSTNAME=<rhxascs> @@ -65 +65 @@ Install ASCS instance on `rhxhost01` with virtual hostname `rhxascs`, using the -Install ERS instance on `rhxhost02` with virtual hostname `rhxers`, using the high availability option of Software Provisioning Manager (SWPM) tool. You can use the `SAPINST_USE_HOSTNAME` parameter to install SAP using a virtual hostname. +Install ERS instance on `<rhxhost02>` with virtual hostname `rhxers`, using the high availability option of Software Provisioning Manager (SWPM) tool. You can use the `SAPINST_USE_HOSTNAME` parameter to install SAP using a virtual hostname. @@ -68 +68 @@ Install ERS instance on `rhxhost02` with virtual hostname `rhxers`, using the hi - <swpm location>/sapinst SAPINST_USE_HOSTNAME=rhxers + <swpm location>/sapinst SAPINST_USE_HOSTNAME=<rhxers> @@ -118 +118 @@ This is applicable to both cluster nodes. An `haclient` operating system group i - usermod -a -G haclient rhxadm + usermod -a -G haclient <rhx>adm @@ -155,2 +151 @@ 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._ @@ -178,2 +172 @@ 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._ @@ -187 +180 @@ _`XX` indicates the start order. This value may be different in your install; re - # Added for Cluster Connectivity + Added for Cluster Connectivity @@ -200 +192 @@ The minimum version of `sap_cluster_connector` that complies with HA-Interface c - /usr/sap/hostctrl/exe/sapcontrol -nr 00 -function RestartService + /usr/sap/hostctrl/exe/sapcontrol -nr <00> -function RestartService @@ -204 +196 @@ The minimum version of `sap_cluster_connector` that complies with HA-Interface c - /usr/sap/hostctrl/exe/sapcontrol -nr 10 -function RestartService + /usr/sap/hostctrl/exe/sapcontrol -nr <10> -function RestartService @@ -210,3 +202,2 @@ The minimum version of `sap_cluster_connector` that complies with HA-Interface c - /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 @@ -247 +237 @@ See the following example ASCS entry for older version with `systemV` integratio - LD_LIBRARY_PATH=/usr/sap/RHX/ASCS00/exe:$LD_LIBRARY_PATH;export LD_LIBRARY_PATH;/usr/sap/RHX/ASCS00/exe/sapstartsrv pf=/usr/sap/RHX/SYS/profile/RHX_ASCS00_rhxascs -D -u rhxadmu + LD_LIBRARY_PATH=/usr/sap/<RHX>/ASCS<00>/exe:$LD_LIBRARY_PATH;export LD_LIBRARY_PATH;/usr/sap/<RHX>/ASCS<00>/exe/sapstartsrv pf=/usr/sap/<RHX>/SYS/profile/<RHX>_ASCS<00>_<rhxascs> -D -u <rhxadm>u @@ -253,3 +243 @@ To ensure that SAP instance can be managed by the cluster and also manually duri - LD_LIBRARY_PATH=/usr/sap/RHX/ASCS00/exe:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; /usr/sap/RHX/ASCS00/exe/sapstartsrv pf=/usr/sap/RHX/SYS/profile/RHX_ASCS00_rhxascs -D -u rhxadm - - LD_LIBRARY_PATH=/usr/sap/RHX/ERS10/exe:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; /usr/sap/RHX/ERS10/exe/sapstartsrv pf=/usr/sap/RHX/SYS/profile/RHX_ERS10_ -Drhxers -u rhxadm + LD_LIBRARY_PATH=/usr/sap/<RHX>/ASCS<00>/exe:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; /usr/sap/<RHX>/ASCS<00>/exe/sapstartsrv pf=/usr/sap/<RHX>/SYS/profile/<RHX>_ASCS<00>_<rhxascs> -D -u <rhxadm> @@ -256,0 +245 @@ To ensure that SAP instance can be managed by the cluster and also manually duri + LD_LIBRARY_PATH=/usr/sap/<RHX>/ERS<10>/exe:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; /usr/sap/<RHX>/ERS<10>/exe/sapstartsrv pf=/usr/sap/<RHX>/SYS/profile/<RHX>_ERS<10>_ -D<rhxers> -u <rhxadm> @@ -261,2 +250 @@ systemd -See the following example ASCS entry for newer version with native `systemd` integration. - + * See the following example ASCS entry for newer version with native `systemd` integration. @@ -264 +252 @@ See the following example ASCS entry for newer version with native `systemd` int - systemctl --no-ask-password start SAPRHX_00 # sapstartsrv pf=/usr/sap/RHX/SYS/profile/RHX_ASCS00_rhxascs + systemctl --no-ask-password start <SAPRHX_00> # sapstartsrv pf=/usr/sap/<RHX>/SYS/profile/<RHX>_ASCS<00>_<rhxascs> @@ -270 +257,4 @@ To ensure that SAP instance can be managed by the cluster and also manually duri - systemctl --no-ask-password start SAPRHX_00 # sapstartsrv pf=/usr/sap/RHX/SYS/profile/RHX_ASCS00_rhxascs + systemctl --no-ask-password start <SAPRHX_00> # sapstartsrv pf=/usr/sap/<RHX>/SYS/profile/<RHX>_ASCS<00>_<rhxascs> + + systemctl --no-ask-password start <SAPRHX_10> # sapstartsrv pf=/usr/sap/<RHX>/SYS/profile/<RHX>_ERS<10>_<rhxers> + @@ -272 +261,0 @@ To ensure that SAP instance can be managed by the cluster and also manually duri - systemctl --no-ask-password start SAPRHX_10 # sapstartsrv pf=/usr/sap/RHX/SYS/profile/RHX_ERS10_rhxers @@ -288 +277,2 @@ Temporarily mount the ERS directory. - mount <nfs.fqdn>:/RHX_ERS10 /usr/sap/RHX/ERS10 + mount <nfs.fqdn>:/<RHX>_ERS<10> /usr/sap/<RHX>/ERS + @@ -293,2 +283,2 @@ Register the ERS service. - export LD_LIBRARY_PATH=/usr/sap/RHX/ERS10/exe - /usr/sap/RHX/ERS10/exe/sapstartsrv pf=/usr/sap/RHX/SYS/profile/RHX_ERS10_rhxers -reg + export LD_LIBRARY_PATH=/usr/sap/<RHX>/ERS<10>/exe + /usr/sap/<RHX>/ERS<10>/exe/sapstartsrv pf=/usr/sap/<RHX>/SYS/profile/<RHX>_ERS<10>_<rhxers> -reg @@ -296 +286 @@ Register the ERS service. - systemctl start SAPRHX_10 + systemctl start <SAPRHX_10> @@ -301 +291 @@ Check the existence and state of SAP services. - # systemctl list-unit-files SAP* + systemctl list-unit-files SAP* @@ -303,2 +293,2 @@ Check the existence and state of SAP services. - SAPRHX_00.service disabled disabled - SAPRHX_10.service disabled disabled + <SAPRHX_00>.service disabled disabled + <SAPRHX_10>.service disabled disabled @@ -315,4 +305,4 @@ Stopping these services also stops the associated SAP instances. - systemctl stop SAPRHX_00.service - systemctl disable SAPRHX_00.service - systemctl stop SAPRHX_10.service - systemctl disable SAPRHX_10.service + systemctl stop <SAPRHX_00>.service + systemctl disable <SAPRHX_00>.service + systemctl stop <SAPRHX_10>.service + systemctl disable <SAPRHX_10>.service @@ -323 +313,2 @@ Unmount the ERS directory (classic only). - umount /usr/sap/RHX/ERS10 + umount /usr/sap/<RHX>/ERS + @@ -332 +323,2 @@ Temporarily mount the ASCS directory (classic only). - mount <nfs.fqdn>:/RHX_ASCS00 /usr/sap/RHX/ASCS00 + mount <nfs.fqdn>:/<RHX>_ASCS<00> /usr/sap/<RHX>/ASCS + @@ -337,3 +329,3 @@ Register the ASCS service. - export LD_LIBRARY_PATH=/usr/sap/RHX/ASCS00/exe - /usr/sap/RHX/ASCS00/exe/sapstartsrv pf=/usr/sap/RHX/SYS/profile/RHX_ASCS00_rhxascs -reg - systemctl start SAPRHX_00 + export LD_LIBRARY_PATH=/usr/sap/<RHX>/ASCS<00>/exe + /usr/sap/<RHX>/ASCS<00>/exe/sapstartsrv pf=/usr/sap/<RHX>/SYS/profile/<RHX>_ASCS<00>_<rhxascs> -reg + systemctl start <SAPRHX_00> @@ -344 +336 @@ Check the existence and state of SAP services. - # systemctl list-unit-files SAP* + systemctl list-unit-files SAP* @@ -346,2 +338,2 @@ Check the existence and state of SAP services. - SAPRHX_00.service disabled disabled - SAPRHX_10.service disabled disabled + <SAPRHX_00>.service disabled disabled + <SAPRHX_10>.service disabled disabled @@ -358,4 +350,4 @@ Stopping these services also stops the associated SAP instances. - systemctl stop SAPRHX_00.service - systemctl disable SAPRHX_00.service - systemctl stop SAPRHX_10.service - systemctl disable SAPRHX_10.service + systemctl stop <SAPRHX_00>.service + systemctl disable <SAPRHX_00>.service + systemctl stop <SAPRHX_10>.service + systemctl disable <SAPRHX_10>.service @@ -366 +358,2 @@ Unmount the ASCS directory (classic only). - umount /usr/sap/RHX/ASCS00 + umount /usr/sap/<RHX>/ASCS + @@ -397 +390 @@ If `systemd` is configured, create a config file that defines a dependency betwe - cat > sap_systemd_rhx.conf <<_EOF + cat > sap_systemd_<rhx>.conf <<_EOF @@ -401,2 +394,2 @@ If `systemd` is configured, create a config file that defines a dependency betwe - After=SAPRHX_00.service - After=SAPRHX_10.service + After=<SAPRHX_00>.service + After=<SAPRHX_10>.service @@ -415,2 +408,2 @@ This is applicable on both cluster nodes. To prevent the automatic restart of cr - mkdir -p /etc/systemd/system/SAPRHX_00.service.d/ - mkdir -p /etc/systemd/system/SAPRHX_10.service.d/ + mkdir -p /etc/systemd/system/<SAPRHX_00>.service.d/ + mkdir -p /etc/systemd/system/<SAPRHX_10>.service.d/ @@ -418 +411 @@ This is applicable on both cluster nodes. To prevent the automatic restart of cr - cd /etc/systemd/system/SAPRHX_00.service.d/ + cd /etc/systemd/system/<SAPRHX_00>.service.d/ @@ -425 +418 @@ This is applicable on both cluster nodes. To prevent the automatic restart of cr - cd /etc/systemd/system/SAPRHX_10.service.d/ + cd /etc/systemd/system/<SAPRHX_10>.service.d/ @@ -440 +432 @@ This is applicable to both cluster nodes. Change the password of the operating s - # passwd hacluster + passwd <hacluster> @@ -470,3 +462,2 @@ This is applicable on both clsuter nodes. Run the following command to enable an - # systemctl start pcsd.service - # systemctl enable pcsd.service - + systemctl start pcsd.service + systemctl enable pcsd.service @@ -477 +468 @@ Run the following command to check the status of cluster service. - # systemctl status pcsd.service + systemctl status pcsd.service @@ -499 +489 @@ Run the following command to back up the current configuration for reference. - # pcs config show > /tmp/pcsconfig_backup.txt + pcs config show > /tmp/pcsconfig_backup.txt @@ -504 +494 @@ Run the following command to clear the current configuration. - # pcs cluster destroy + pcs cluster destroy @@ -513,2 +503,2 @@ The following command authenticates `pcs` to the `pcs daemon` on cluster nodes. - # pcs cluster auth rhxhost01 rhxhost02 - Username: hacluster + pcs cluster auth <rhxhost01> <rhxhost02> + Username: <hacluster> @@ -516,3 +506,2 @@ The following command authenticates `pcs` to the `pcs daemon` on cluster nodes. - rhxhost02: Authorized - rhxhost01: Authorized - + <rhxhost02>: Authorized + <rhxhost01>: Authorized @@ -523,2 +512,2 @@ The following command authenticates `pcs` to the `pcs daemon` on cluster nodes. - # pcs host auth rhxhost01 rhxhost02 - Username: hacluster + pcs host auth <rhxhost01> <rhxhost02> + Username: <hacluster> @@ -526,3 +515,2 @@ The following command authenticates `pcs` to the `pcs daemon` on cluster nodes. - rhxhost02: Authorized - rhxhost01: Authorized - + <rhxhost02>: Authorized + <rhxhost01>: Authorized @@ -537,6 +525,6 @@ The following command configures the `cluster configuration` file, and syncs the - # pcs cluster setup --name rhelha rhxhost01 rhxhost02 - Destroying cluster on nodes: rhxhost01, rhxhost02... - rhxhost02: Stopping Cluster (pacemaker)... - rhxhost01: Stopping Cluster (pacemaker)... - rhxhost02: Successfully destroyed cluster - rhxhost01: Successfully destroyed cluster + pcs cluster setup --name <rhelha> <rhxhost01> <rhxhost02> + Destroying cluster on nodes: <rhxhost01>, <rhxhost02>...