Sun Cluster Data Service for SAP Guide for Solaris OS

Registering and Configuring Sun Cluster HA for SAP

This section contains the procedures you need to configure Sun Cluster HA for SAP.

Sun Cluster HA for SAP Extension Properties

Use the extension properties in Sun Cluster HA for SAP Extension Properties for the Central Instance and Sun Cluster HA for SAP Extension Properties for the Application Servers to create your resources. Use the command line scrgadm -x parameter=value to configure extension properties when you create your resource. Use the procedure in “Administering Data Service Resources” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS to configure the extension properties if you have already created your resources. You can update some extension properties dynamically. You can update others, however, only when you create or disable a resource. The Tunable entries indicate when you can update each property. See “Standard Properties” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS for details on all Sun Cluster properties.

Sun Cluster HA for SAP Extension Properties for the Central Instance

SAP configuration extension properties are as follows:

SAPSID

SAP system ID or SID.

Default: None

Tunable: When disabled

Ci_instance_id

Two-digit SAP system number.

Default: 00

Tunable: When disabled

Ci_services_string

String of central instance services.

Default: DVEBMGS

Tunable: When disabled

Starting SAP extension properties are as follows:

Ci_start_retry_interval

The interval in seconds to wait between attempting to connect to the database before starting the central instance.

Default: 30

Tunable: When disabled

Ci_startup_script

Name of the SAP startup script for this instance in your SIDadm home directory.

Default: None

Tunable: When disabled

Stopping SAP extension properties are as follows:

Stop_sap_pct

Percentage of stop-timeout variables that are used to stop SAP processes. The SAP shutdown script is used to stop processes before calling Process Monitor Facility (PMF) to terminate and then kill the processes.

Default: 95

Tunable: When disabled

Ci_shutdown_script

Name of the SAP shutdown script for this instance in your SIDadm home directory.

Default: None

Tunable: When disabled

Probe extension properties are as follows:

Message_server_name

The name of the SAP Message Server.

Default: sapms SAPSID

Tunable: When disabled

Lgtst_ms_with_logicalhostname

How to check the SAP Message Server with the SAP lgtst utility. The lgtst utility requires a hostname (IP address) as the location for the SAP Message Server. This hostname can be either a Sun Cluster logical hostname or a local host (loopback) name. If you set this resource property to TRUE, use a logical hostname. Otherwise, use a localhost name.

Default: TRUE

Tunable: Any time

Check_ms_retry

Maximum number of times the SAP Message Server check fails before a total failure is reported and the Resource Group Manager (RGM) starts.

Default: 2

Tunable: When disabled

Probe_timeout

Timeout value in seconds for the probes.

Default: 120

Tunable: Any time

Monitor_retry_count

Number of PMF restarts that are allowed for the fault monitor.

Default: 4

Tunable: Any time

Monitor_retry_interval

Time interval in minutes for the fault monitor restarts.

Default: 2

Tunable: Any time

Development system extension properties are as follows:

Shutdown_dev

Whether the RGM should shut down the development system before starting up the central instance.

Default: FALSE

Tunable: When disabled

Dev_sapsid

SAP System Name for the development system (if you set Shutdown_dev to TRUE, Sun Cluster HA for SAP requires this property).

Default: None

Tunable: When disabled

Dev_shutdown_script

Script that is used to shut down the development system. If you set Shutdown_dev to TRUE, Sun Cluster HA for SAP requires this property.

Default: None

Tunable: When disabled

Dev_stop_pct

Percentage of startup timeouts Sun Cluster HA for SAP uses to shut down the development system before starting the central instance.

Default: 20

Tunable: When disabled

Sun Cluster HA for SAP Extension Properties for the Application Servers

SAP configuration extension properties are as follows:

SAPSID

SAP system name or SAPSID for the application server.

Default: None

Tunable: When disabled

As_instance_id

Two-digit SAP system number for the application server.

Default: None

Tunable: When disabled

As_services_string

String of application server services.

Default: D

Tunable: When disabled

Starting SAP extension properties are as follows:

As_db_retry_interval

The interval in seconds to wait between attempting to connect to the database and starting the application server.

Default: 30

Tunable: When disabled

As_startup_script

Name of the SAP startup script for the application server.

Default: None

Tunable: When disabled

Stopping SAP extension properties are as follows:

Stop_sap_pct

Percentage of stop-timeout variables that are used to stop SAP processes. The SAP shutdown script is used to stop processes before calling Process Monitor Facility (PMF) to terminate and then kill the processes.

Default: 95

Tunable: When disabled

As_shutdown_script

Name of the SAP shutdown script for the application server.

Default: None

Tunable: When disabled

Probe extension properties are as follows:

Probe_timeout

Time-out value in seconds for the probes.

Default: 60

Tunable: Any time

Monitor_retry_count

Number of PMF restarts that the probe allows for the fault monitor.

Default: 4

Tunable: Any time

Monitor_retry_interval

Time interval in minutes for fault monitor restarts.

Default: 2

Tunable: Any time

How to Register and Configure Sun Cluster HA for SAP with Central Instance

Use this procedure to configure Sun Cluster HA for SAP with central instance.

  1. Become superuser on one of the nodes in the cluster that hosts the central instance.

  2. Register the resource type for the central instance.


    # scrgadm -a -t SUNW.sap_ci | SUNW.sap_ci_v2
    
  3. Add the HAStoragePlus resource to the central instance resource group.


    # scrgadm -a -t SUNW.HAStoragePlus
    # scrgadm -a -j ci-storage-resource \
    -g sap-ci-resource-group \
    -t SUNW.HAStoragePlus -x filesystemmountpoints=mountpoint, ... | 

    For more details on how to set up an HAStoragePlus resource, see “Enabling Highly Available Local File Systems” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

  4. Enable the central instance storage resource.


    # scswitch -e -j ci-storage-resource
    
  5. Create SAP central instance resources in this failover resource group.


    # scrgadm -a -j sap-ci-resource \
    -g sap-ci-resource-group\
    -t SUNW.sap_ci | SUNW.sap_ci_v2
    -x SAPSID=SAPSID -x Ci_instance_id=ci-instance-id \
    -x Ci_startup_script=ci-startup-script \
    -x Ci_shutdown_script=ci-shutdown-script \
    -y resource_dependencies=ci-storage-resource
    

    See Sun Cluster HA for SAP Extension Properties for a list of extension properties.

  6. Enable the failover resource group that now includes the SAP central instance resource.


    # scswitch -Z -g sap-ci-resource-group
    

    If you configure the central instance resource to shut down a development system, you will receive the following console message.


    ERROR  : SAPSYSTEMNAME not set
    Please check environment and restart

    This message is displayed when the central instance starts on a node that does not have the development system installed and that is not meant to run the central instance. SAP renders this message, and you can safely ignore it.

Where to Go From Here

Go to How to Register and Configure Sun Cluster HA for SAP as a Failover Data Service or How to Register and Configure Sun Cluster HA for SAP as a Scalable Data Service.

How to Register and Configure Sun Cluster HA for SAP as a Failover Data Service

Use this procedure to configure Sun Cluster HA for SAP as a failover data service.

  1. Become superuser on one of the nodes in the cluster that hosts the application server.

  2. Register the resource type for the failover application server.


    # scrgadm -a -t SUNW.sap_as | SUNW.sap_as_v2
    
  3. Add the HAStoragePlus resource to the failover application server resource group.


    # scrgadm -a -t SUNW.HAStoragePlus
    # scrgadm -a -j sap-as-storage-resource -g sap-as-fo-resource-group \
    -t SUNW.HAStoragePlus \
    -x filesystemmountpoints=mountpoint, ...
    

    For more details on how to set up an HAStoragePlus resource, see “Enabling Highly Available Local File Systems” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

  4. Enable the failover application server storage resource.


    # scswitch -e -j sap-as-storage-resource
    
  5. Create SAP application server resources in their failover resource group.


    # scrgadm -a -j sap-as-resource \
    -g sap-as-fo-resource-group \
    -t SUNW.sap_as | SUNW.sap_as_v2
    -x SAPSID=SAPSID -x As_instance_id=as-instance-id \
    -x As_startup_script=as-startup-script \
    -x As_shutdown_script=as-shutdown-script \
    -y resource_dependencies=sap-as-storage-resource
    

    See Sun Cluster HA for SAP Extension Properties for a list of extension properties.

  6. Enable the failover resource group that now includes the SAP application server resource.


    # scswitch -Z -g sap-as-fo-resource-group
    

Where to Go From Here

Go to How to Verify Sun Cluster HA for SAP Installation and Configuration and Central Instance.

How to Register and Configure Sun Cluster HA for SAP as a Scalable Data Service

Use this procedure to configure Sun Cluster HA for SAP as a scalable data service.

  1. Become superuser on one of the nodes in the cluster that hosts the application server.

  2. Create a scalable resource group for the application server.


    # scrgadm -a -g sap-as-sa-appinstanceid-resource-group \
    -y Maximum_primaries=value \
    -y Desired_primaries=value
    

    Note –

    Sun Cluster HA for SAP as a scalable data service does not use shared addresses because the SAP logon group performs the load balancing of the application server.



    Note –

    If you are using the SUNW.RGOffload resource type to offload an application server within this scalable application server resource group, then set Desired_primaries=0. See “Freeing Node Resources by Offloading Non-critical Resource Groups” in Sun Cluster Data Servicse Planning and Administration Guide for Solaris OS for more information about using the SUNW.RGOffload resource type.


  3. Register the resource type for the scalable application server.


    # scrgadm -a -t SUNW.sap_as_v2
    
  4. Add the HAStoragePlus resource to the failover application server resource group.


    # scrgadm -a -t SUNW.HAStoragePlus 
    # scrgadm -a -j sap-as-storage-resource -g \
    -g sap-as-sa-appinstanceid-resource-group \
    -t SUNW.HAStoragePlus \
    -x filesystemmountpoints=mountpoint, ... \

    For more details on how to set up an HAStoragePlus resource, see “Enabling Highly Available Local File Systems” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

  5. Enable the failover application server storage resource.


    # scswitch -e -j sap-as-storage-resource
    
  6. Create SAP application server resources in this scalable resource group.


    # scrgadm -a -j sap-as-resource \
    -g sap-as-sa-appinstanceid-resource-group \
    -t SUNW.sap_as_v2 \
    -x SAPSID=SAPSID  \
    -x As_instance_id=as-instance-id \
    -x As_startup_script=as-startup-script \
    -x As_shutdown_script=as-shutdown-script \
    -y resource_dependencies=sap-as-storage-resource
    

    See Sun Cluster HA for SAP Extension Properties for a list of extension properties.

  7. Enable the scalable resource group that now includes the SAP application server resource.

    • If you do not use the RGOffload resource type with this application server, use the following command.


      # scswitch -Z -g sap-as-sa-appinstanceid-resource-group
      
    • If you use the RGOffload resource type with this application server, use the following command.


      # scswitch -z -h node1, node2 -g sap-as-sa-appinstanceid-resource-group
      

    Note –

    If you use the SUNW.RGOffload resource type with this application server, you must specify which node you want to bring the resource online by using the -z option instead of the -j option.


Where to Go From Here

Go to How to Verify Sun Cluster HA for SAP Installation and Configuration and Central Instance.