Blame SOURCES/bz1751949-3-SAPInstance-metadata-improvements.patch

bdc612
--- a/heartbeat/SAPInstance	2019-02-20 12:42:55.655819263 +0100
bdc612
+++ b/heartbeat/SAPInstance	2019-02-08 10:57:02.281048136 +0100
bdc612
@@ -159,14 +159,14 @@
bdc612
   <content type="string" default="disp+work|msg_server|enserver|enrepserver|jcontrol|jstart|enq_server|enq_replicator"/>
bdc612
  </parameter>
bdc612
   <parameter name="SHUTDOWN_METHOD" unique="0" required="0">
bdc612
-  <longdesc lang="en">Usual a SAP Instance is stopped by the command 'sapcontrol -nr InstanceNr -function Stop'. SHUTDOWN_METHOD=KILL means to kill the SAP Instance using OS commands. SAP processes of the instance are terminated with 'kill -9', shared memory is deleted with 'cleanipc' and the 'kill.sap' file will be deleted. That method is much faster than the gracefull stop, but the instance does not have the chance to say goodbye to other SAPinstances in the same system. USE AT YOUR OWN RISK !!</longdesc>
bdc612
+  <longdesc lang="en">Usually a SAP Instance is stopped by the command 'sapcontrol -nr InstanceNr -function Stop'. SHUTDOWN_METHOD=KILL means to kill the SAP Instance using OS commands. SAP processes of the instance are terminated with 'kill -9', shared memory is deleted with 'cleanipc' and the 'kill.sap' file will be deleted. That method is much faster than the graceful stop, but the instance does not have the chance to say goodbye to other SAPinstances in the same system. USE AT YOUR OWN RISK !!</longdesc>
bdc612
   <shortdesc lang="en">Shutdown graceful or kill a SAP instance by terminating the processes. (normal|KILL)</shortdesc>
bdc612
   <content type="string" default="normal"/>
bdc612
  </parameter>
bdc612
  <parameter name="ERS_InstanceName" unique="1" required="0">
bdc612
   <longdesc lang="en">Only used in a Master/Slave resource configuration:
bdc612
 The full qualified SAP enqueue replication instance name. e.g. P01_ERS02_sapp01ers. Usually this is the name of the SAP instance profile.
bdc612
-The enqueue replication instance must be installed, before you want to configure a master-slave cluster recource.
bdc612
+The enqueue replication instance must be installed, before you want to configure a master-slave cluster resource.
bdc612
 
bdc612
 The master-slave configuration in the cluster must use this properties:
bdc612
 clone_max = 2
bdc612
@@ -209,7 +209,7 @@
bdc612
   <longdesc lang="en">Only used for ASCS/ERS SAP Netweaver installations without implementing a master/slave resource to
bdc612
     allow the ASCS to 'find' the ERS running on another cluster node after a resource failure. This parameter should be set
bdc612
     to true 'only' for the ERS instance for implementations following the SAP NetWeaver 7.40 HA certification (NW-HA-CLU-740). This includes also
bdc612
-    systems for NetWeaver less than 7.40, if you like to impelemnt the NW-HA-CLU-740 scenario.
bdc612
+    systems for NetWeaver less than 7.40, if you like to implement the NW-HA-CLU-740 scenario.
bdc612
   </longdesc>
bdc612
   <shortdesc lang="en">Mark SAPInstance as ERS instance</shortdesc>
bdc612
   <content type="boolean" default="false" />
bdc612
@@ -225,7 +225,7 @@
bdc612
 <action name="monitor" depth="0" timeout="60s" interval="119s" role="Master" />
bdc612
 <action name="promote" timeout="320s" />
bdc612
 <action name="demote" timeout="320s" />
bdc612
-<action name="reload" timeout="320" />
bdc612
+<action name="reload" timeout="320s" />
bdc612
 <action name="validate-all" timeout="5s" />
bdc612
 <action name="meta-data" timeout="5s" />
bdc612
 <action name="methods" timeout="5s" />