Added metatdata and article ID

For search and filtering, metadata were added to the docinfo file, and
and article ID to the adoc file.

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

@@ -10,13 +10,29 @@
 <!--<subtitle>Setup Guide</subtitle>-->
     <!-- <orgname>SUSE Best Practices</orgname>-->
     <productname>SUSE Linux Enterprise Server for SAP Applications</productname>
-    <productnumber>15</productnumber>
+ <!--   <productnumber>15</productnumber>-->
 
-<meta name="series">SUSE Best Practices</meta>
-<meta name="category">SAP</meta>
+<meta name="series">Best Practices</meta>
+<meta name="category">
+    <phrase>SAP</phrase>
+</meta>
+
+<meta name="task">    
+    <phrase>High Availability</phrase>
+    <phrase>Configuration</phrase>
+</meta>
+
+<meta name="title">SAP Convergent Mediation ControlZone HA Cluster guide</meta>
+<meta name="description">This document explains how to configure an SAP Convergent Mediation ControlZone High Availability Cluster solution on SLES 15 SP4 and newer</meta>
+<meta name="social-descr">Configure a Convergent Mediation HA Cluster on SLES 15</meta>
+<meta name="productname">
+    <productname version="15 SP4">SUSE Linux Enterprise Server for SAP Applications</productname>
+    <productname version="15 SP5">SUSE Linux Enterprise Server for SAP Applications</productname>
+    <productname version="15 SP6">SUSE Linux Enterprise Server for SAP Applications</productname>
+</meta>
 
 <meta name="platform">SUSE Linux Enterprise Server for SAP Applications 15</meta>
-<meta name="platform">Convergent Mediation</meta>
+<meta name="platform">SAP Convergent Mediation</meta>
 
 <authorgroup>
     <author>
@@ -52,14 +68,21 @@
       </mediaobject>
     </cover>
 
+<revhistory xml:id="rh-art-sap-convergent-mediation-ha-setup-sle15">
+    <revision>
+        <date>2024-05-24</date>
+        <revdescription>
+            <para> </para>
+        </revdescription>
+    </revision>
+</revhistory>
+
 <!--<date><?dbtimestamp format="B d, Y" ?></date>-->
 
 <abstract>
 
-        <para>SUSE® Linux Enterprise Server for SAP Applications is
-        optimized in various ways for SAP® applications.
-	This document explains how to deploy a Convergent Mediation ControlZone
-	High Availability Cluster solution.
+        <para>SUSE® Linux Enterprise Server for SAP Applications is optimized in various ways for SAP® applications.
+	This document explains how to configure a Convergent Mediation ControlZone High Availability Cluster solution.
 	It is based on SUSE Linux Enterprise Server for SAP Applications 15 SP4.
 	The concept however can also be used with
 	newer service packs of SUSE Linux Enterprise Server for SAP Applications.

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

@@ -2,6 +2,9 @@
 
 :localdate:
 
+// defining article ID
+[#art-sap-convergent-mediation-ha-setup-sle15]
+
 // Document Variables
 :slesProdVersion: 15
 //
@@ -20,29 +23,28 @@ include::Var_SAP-convergent-mediation.adoc[]
 
 == About this guide
 
-The following sections are focussing on background information and purpose of the
-document at hand.
+The following sections focus on background information and purpose of this document.
 
 === Abstract
 
 This guide describes configuration and basic testing of {sles4sap} {prodNr}
-{prodSP} as an high availability cluster for {ConMed} (CM) ControlZone services.
+{prodSP} as a high availability cluster for {ConMed} (CM) ControlZone services.
 
-From the application perspective the following concept is covered:
+From an application perspective, the following concept is covered:
 
 - ControlZone platform and UI services are running together.
 
 - ControlZone software is installed on central NFS.
 
 - ControlZone software is copied to local disks of both nodes.
 
-From the infrastructure perspective the following concept is covered:
+From an infrastructure perspective, the following concept is covered:
 
-- Two-node cluster with disk-based SBD fencing.
+- Two-node cluster with disk-based SBD fencing
 
-- Central NFS share statically mounted on both nodes.
+- Central NFS share statically mounted on both nodes
 
-- On-premises deployment on physical and virtual machines.
+- On-premises deployment on physical and virtual machines
 
 Despite the above menionted focus of this setup guide, other variants can be
 implemented as well. See <<cha.overview>> below. The concept can also be used
@@ -55,7 +57,7 @@ NOTE: This solution is supported only in the context of {SAP} RISE
 === Additional documentation and resources
 
 Several chapters in this document contain links to additional documentation resources
-that are either available on the system or on the Internet.
+which are available either in the system or on the Internet.
 
 For the latest product documentation updates, see https://documentation.suse.com/.