File 0009-Medium-SAPInstance-Add-monitored-services-for-ENSA2-.patch of Package resource-agents.8789

From ee63caf2e8e972b7e2dc54fba0241fa08ef8af4d Mon Sep 17 00:00:00 2001
From: Fabian Herschel <fabian.herschel@suse.com>
Date: Fri, 8 Jun 2018 16:14:29 +0200
Subject: [PATCH] Medium: SAPInstance: Add monitored services for ENSA2
 (bsc#1092384)

For ENSA2 the S/4 HANA Enqueue Services 2 we need two strings to be
added to the default services list to be monitored: enq_server, enq_replicator.
---
 heartbeat/SAPInstance | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/heartbeat/SAPInstance b/heartbeat/SAPInstance
index 8cfaf22e..0654b931 100755
--- a/heartbeat/SAPInstance
+++ b/heartbeat/SAPInstance
@@ -137,8 +137,10 @@ Those services are monitored within the SAPInstance resource agent:
 
 - disp+work
 - msg_server
-- enserver
-- enrepserver
+- enserver (ENSA1)
+- enq_server (ENSA2)
+- enrepserver (ENSA1)
+- enq_replicator (ENSA2)
 - jcontrol
 - jstart
 
@@ -153,7 +155,7 @@ The default should fit most cases where you want to manage a SAP Instance from t
 You may specify multiple services separated by a | (pipe) sign in this parameter: disp+work|msg_server|enserver
   </longdesc>
   <shortdesc lang="en">Services to monitor</shortdesc>
-  <content type="string" default="disp+work|msg_server|enserver|enrepserver|jcontrol|jstart"/>
+  <content type="string" default="disp+work|msg_server|enserver|enrepserver|jcontrol|jstart|enq_server|enq_replicator"/>
  </parameter>
   <parameter name="SHUTDOWN_METHOD" unique="0" required="0">
   <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>
@@ -378,7 +380,7 @@ sapinstance_init() {
 
   if [ -z "$OCF_RESKEY_MONITOR_SERVICES" ]
   then
-    export OCF_RESKEY_MONITOR_SERVICES="disp+work|msg_server|enserver|enrepserver|jcontrol|jstart"
+    export OCF_RESKEY_MONITOR_SERVICES="disp+work|msg_server|enserver|enrepserver|jcontrol|jstart|enq_server|enq_replicator"
   fi
 
   # as root user we need the library path to the SAP kernel to be able to call sapcontrol
-- 
2.13.7