Merge pull request #439 from SUSE/lpinne-cm

SAP-convergent-mediation-ha-setup-sle15.adoc: fixed sub-section header

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

@@ -130,8 +130,8 @@ details)
 === High availability for the {ConMed} ControlZone platform and UI
 
 The HA solution for CM ControlZone is a two-node active/passive cluster. 
-A shared NFS file system is statically mounted by the operating system on both cluster nodes. This
-file system holds work directories. Client-side write caching needs to be disabled.
+A shared NFS file system is statically mounted by the operating system on both cluster nodes.
+This file system holds work directories. Client-side write caching needs to be disabled.
 The ControlZone software is installed into the central shared NFS, but is also
 copied to both nodes´ local file systems. The HA cluster uses the central directory
 for starting/stopping the ControlZone services. However, for monitoring the local
@@ -207,8 +207,8 @@ configuration needs to be adjusted. Refer to {ConMed} documentation for details.
 - CM ControlZone is configured identically on both cluster nodes. User, path
 names and environment settings are the same.
 
-- There is only *one* ControlZone instance per Linux cluster. Accordingly, there is only one platform service and
-one UI service per cluster.
+- There is only *one* ControlZone instance per Linux cluster. Accordingly, there is
+only one platform service and one UI service per cluster.
 
 - The platform and UI are installed into the same MZ_HOME.
 
@@ -229,20 +229,20 @@ the mzadmin needs to work reliable and without customized actions or messages.
 - Name resolution for host names and virtual host names is crucial. Host names of
 cluster nodes and services are resolved locally in the Linux system.
 
-- Strict time synchronization between the cluster nodes, for example NTP, is required. All nodes of a
-cluster have configured the same timezone.
+- Strict time synchronization between the cluster nodes, for example NTP, is required.
+All nodes of a cluster have configured the same timezone.
 
 - Needed NFS shares (for example `/usr/sap/<SID>`) are mounted statically or by automounter.
 No client-side write caching is happening. File locking should be configured for application
 needs.
 
 - The RA monitoring operations need to be active.
 
-- RA runtime almost completely depends on call-outs to controlled resources, operating system, and
-Linux cluster. The infrastructure needs to allow these call-outs to return in time.
+- RA runtime almost completely depends on call-outs to controlled resources, operating system,
+and Linux cluster. The infrastructure needs to allow these call-outs to return in time.
 
-- The ControlZone application is not started/stopped by the operating system. Thus, there is no SystemV,
-systemd or cron job.
+- The ControlZone application is not started/stopped by the operating system.
+Thus, there is no SystemV, systemd or cron job.
 
 - As long as the ControlZone application is managed by the Linux cluster, the
 application is not started/stopped/moved from outside. Thus, no manual actions are
@@ -252,7 +252,7 @@ parallel, both are stopped and one of them is restarted.
 
 - The interface for the RA to the ControlZone services is the command `mzsh`. Ideally,
 `mzsh` should be accessed on the cluster nodes´ local file systems.
-`mzsh` is called with the arguments `startup`, `shutdown` and `status`. Its return
+`mzsh` is called with the arguments `startup -f`, `shutdown` and `status`. Its return
 code and output is interpreted by the RA. Thus, the command and its output need
 to be stable. The mzsh shall not be customized. Particularly environment
 variables set thru `~/.bashrc` must not be changed.
@@ -386,7 +386,7 @@ i | java-17-openjdk          | OpenJDK 17 Runtime Environment     | package
 
 Check this on both nodes.
 
-==== HA software and Java virtual machine
+==== HA software and tools
 
 // TODO PRIO2: content
 
@@ -753,8 +753,8 @@ ui is running
 0
 ----
 
-Perform the above steps on both nodes. The ControlZone services should be running on either
-node, but not on both in parallel.
+Perform the above steps on both nodes. The ControlZone services should be running
+on either node, but not on both in parallel.
 
 
 [[cha.ha-cm]] 
@@ -765,9 +765,9 @@ node, but not on both in parallel.
 [[sec.ha-bashrc]]
 === Preparing mzadmin user ~/.bashrc file
 
-For the environment variables JAVA_HOME, MZ_HOME and MZ_PLATFORM,
-certain values are required. For cluster actions, the values are inherited from the RA through related
-RA_... variables. For manual admin actions, the values are set as default.
+For the environment variables JAVA_HOME, MZ_HOME and MZ_PLATFORM, certain values
+are required. For cluster actions, the values are inherited from the RA through
+related RA_... variables. For manual admin actions, the values are set as default.
 This is needed on both nodes.
 
 [subs="specialchars,attributes,verbatim,quotes"]