Installation guide

standalone web dispatcher instance which will fail to work with the resource agent. The next

version of the agent can have a parameter that could be used to select which services should

be monitored. However, this does not mean that a SAP web dispatcher cannot be included in

another SAP instance that uses one of the monitored services (e.g., a SCS instance running

a msg_server and a enserver). In this case, the web dispatcher will be started and stopped

(together with the other services) by the cluster. The web dispatcher is then not monitored,

meaning a hung or dead sapwebdisp process will not cause a failover of the entire SAP

instance. However, that may be exactly what is preferred.

All operations of the SAPInstance resource agent are performed by using the startup

framework called SAP Management Console, or sapstartsrv, that was introduced with SAP

kernel release 6.40. Reference additional information regarding the SAP Management

Console in SAP Note 1014480.

Using this framework defines a clear interface for the cluster heartbeat and how it views the

SAP system. The monitoring options for the SAP system are far superior than other methods

such as monitoring the ps command for running processes or pinging the application.

sapstartsrv uses SOAP messages to request the status of running SAP processes. As such, it

can request status directly from the process itself, independent from other issues that can

exist at the time.

sapstartsrv has four status states:

 GREEN = everything is fine

 YELLOW = something is wrong, but the service is still working

 RED = the service does not work

 GRAY = the service has not been started

The SAPInstance resource agent will interpret GREEN and YELLOW as acceptable, meaning

minor problems will not be reported to the heartbeat cluster. This prevents the cluster from

performing an unwanted failover. The statuses RED and GRAY are reported as

NOT_RUNNING to the cluster. Depending on the status the cluster expects from the

resource, it will perform a restart, a failover, or do nothing.

Attribute Description Required

InstanceName The full qualified SAP instance name.

In the format: SID_INSTANCE_VHOST

e.g., RHC_DVEBMGS01_lsrhcaci

This is typically the name of the SAP

instance profile.

DEFAULT: none

Yes

DIR_EXECUTABLE The fully qualified path to sapstartsrv and

sapcontrol.

Specify this parameter if the SAP kernel

directory location was been changed