test

Sun Cluster Data Service for SAP Guide for Solaris OS

Registering and Configuring Sun Cluster HA for SAP

This section contains the procedures that 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 clresource create -g resource-group -t resource-type -p property=value resource to configure extension properties when you create your resource. Use the procedure in Chapter 2, 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 Appendix B, Standard Properties, in Sun Cluster Data Services Planning and Administration Guide for Solaris OS for details about 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 SAPSID.

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 SAPSIDadm 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 SAPSIDadm 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

Timeout 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

ProcedureHow 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.


    # clresourcetype register SUNW.sap_ci | SUNW.sap_ci_v2

  3. Add the HAStoragePlus resource to the resource group for the central instance.


    # clresourcetype register SUNW.HAStoragePlus
# clresource create  -g sap-ci-resource-group \
-t SUNW.HAStoragePlus -p filesystemmountpoints=mountpoint,... ci-storage-resource

    The resource is created in the enabled state.

    For more details about 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. Create SAP central instance resources in this failover resource group.


    # clresource create -d \
-g sap-ci-failover-resource-group \
-t SUNW.sap_ci | SUNW.sap_ci_v2 \
-p SAPSID=SAPSID -p Ci_instance_id=ci-instance-id \
-p Ci_startup_script=ci-startup-script \
-p Ci_shutdown_script=ci-shutdown-script \
-p resource_dependencies=ci-storage-resource,db-resource sap-ci-resource

    The resource is created in the enabled state.

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

    Note –

    SAP application requires that the database should be online before the SAP application can start. Setting the resource dependency value to the database will ensure that it checks for the resource to be online before starting the SAP central instance. This dependency check is necessary only if the database is on the same cluster as that of the SAP central instance.

Next Steps

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.

ProcedureHow 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.


    # clresourcetype register SUNW.sap_as


    # clresourcetype register SUNW.sap_as_v2

  3. Add the HAStoragePlus resource to the resource group for the failover application server.


    # clresource register SUNW.HAStoragePlus
# clresource create -g sap-as-fo-resource-group \
-t SUNW.HAStoragePlus \
-p filesystemmountpoints=mountpoint,... sap-as-storage-resource

    The resource is created in the enabled state.

    For more details about 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. Create SAP application server resources in their failover resource group.


    # clresource create  \
-g sap-as-fo-resource-group \
-t SUNW.sap_as | SUNW.sap_as_v2 \
-p SAPSID=SAPSID -p As_instance_id=as-instance-id \
-p As_startup_script=as-startup-script \
-p As_shutdown_script=as-shutdown-script \
-p resource_dependencies=sap-as-storage-resource,db-resource sap-as-resource

    The resource is created in the enabled state.

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

    Note –

    SAP application requires that the database should be online before the SAP application can start. Setting the resource dependency value to the database will ensure that it checks for the resource to be online before starting the SAP application server. This dependency check is necessary only if the database is on the same cluster as that of the SAP application server.

Next Steps

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

ProcedureHow 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.


    # clresourcegroup create  \
-p Maximum_primaries=value \
-p Desired_primaries=value sap-as-sa-appinstanceid-resource-group
    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.

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


    # clresourcetype register SUNW.sap_as_v2

  4. Add the HAStoragePlus resource to the failover application server resource group.


    # clresourcetype register SUNW.HAStoragePlus 
# clresource create  \
-g sap-as-sa-appinstanceid-resource-group \
-t SUNW.HAStoragePlus \
-p filesystemmountpoints=mountpoint,... sap-as-storage-resource

    The resource is created in the enabled state.

    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. Create SAP application server resources in this scalable resource group.


    # clresource create -d \
-g sap-as-sa-appinstanceid-resource-group \
-t SUNW.sap_as_v2 \
-p SAPSID=SAPSID  \
-p As_instance_id=as-instance-id \
-p As_startup_script=as-startup-script \
-p As_shutdown_script=as-shutdown-script \
-p resource_dependencies=sap-as-storage-resource,db-resource sap-as-resource

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

    Note –

    SAP application requires that the database should be online before it can start. Setting the resource dependency value to the database resource will ensure that it checks for the resource to be online before starting the SAP application server. This dependency check is necessary only if the database is on the same cluster as that of the SAP application server.

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


    # clresourcegroup online -M sap-as-sa-appinstanceid-resource-group
Next Steps

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