Registering and Configuring the Sun Cluster HA for SAP liveCache

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

Sun Cluster HA for SAP liveCache Extension Properties

Use the extension properties in Table 1–3 and Table 1–4 to create your resources. Use the following command line to configure extension properties when you create your resource.

scrgadm -x parameter=value 

How to Register and Configure Sun Cluster HA for SAP liveCache

Use this procedure to configure Sun Cluster HA for SAP liveCache as a failover data service for the liveCache database and SAP xserver as a scalable data service. This procedure assumes that you installed the data service packages. If you did not install the Sun Cluster HA for SAP liveCache packages as part of your initial Sun Cluster installation, go to Installing the Sun Cluster HA for SAP liveCache Packages to install the data service packages. Otherwise, use this procedure to configure the Sun Cluster HA for SAP liveCache.

Do not configure more than one SAP xserver resource on the same cluster because one SAP xserver serves multiple liveCache instances in the cluster. More than one SAP xserver resource that runs on the same cluster causes conflicts between the SAP xserver resources. These conflicts cause all SAP xserver resources to become unavailable. If you attempt to start the SAP xserver twice, you receive an error message that says Address already in use.

1. Become superuser on one of the nodes in the cluster that will host the liveCache resource.

2. Copy the lccluster file to the same location as the lcinit file.

   # cp /opt/SUNWsclc/livecache/bin/lccluster \ /sapdb/LC-NAME/db/sap

   LC-NAME

   Uppercase name of liveCache database instance

3. Edit the lccluster file to substitute values for put-LC_NAME-here and put-Confdir_list-here.

   ---

   Note –

   The put-Confidir_list-here value exists only in the Sun Cluster 3.1 version.

   ---

   1. Open the lccluster file.

      # vi /sapdb/LC-NAME/db/sap/lccluster \LC_NAME="put-LC_NAME-here" \ CONFDIR_LIST="put-Confdir_list-here"

      ---

      Note –

      The CONFDIR_LIST=”put-Confdir_list-here entry exists only in the Sun Cluster 3.1 version.

      ---

   2. Replace put-LC_NAME-here with the liveCache instance name. The liveCache instance name is the value you defined in the Livecache_Name extension property.

      For an example, see Step c.

      LC_NAME="liveCache-instance-name"

   3. Replace put-Confdir_list-here with the value of the Confidir_list extension property.

      ---

      Note –

      This step is only for the Sun Cluster 3.1 version. Skip this step if you are running an earlier version of Sun Cluster.

      ---

      CONFDIR_LIST="liveCache-software-directory"

   Example:

   If the liveCache instance name is LC1 and the liveCache software directory is /sapdb, edit the lccluster script as follows.

   LC_NAME="LC1" CONFDIR_LIST="/sapdb" [Sun Cluster 3.1 version only]

4. Add the HAStoragePlus resource to the liveCache resource group.

   # scrgadm -a -t SUNW.HAStoragePlus # scrgadm -a -j livecache-storage-resource -g livecache-resource-group \ -t SUNW.HAStoragePlus -x filesystemmountpoints=mountpoint,... \ -x globaldevicepaths=livecache-device-group -x affinityon=TRUE

   ---

   Note –

   AffinityOne must be set to TRUE and the local file system must reside on global disk groups to be failover.

   ---

   For the procedure on how to set up an HAStoragePlus resource, see Sun Cluster 3.1 Data Service Planning and Administration Guide.

5. Enable the liveCache storage resource.

   # scswitch -e -j livecache-storage-resource

6. Register the resource type for liveCache database.

   # scrgadm -a -t SUNW.sap_livecache

7. Register the resource type for SAP xserver.

   # scrgadm -a -t SUNW.sap_xserver

8. Create a scalable resource group for SAP xserver. Configure SAP xserver to run on all the potential nodes that liveCache will run on.

   ---

   Note –

   Configure SAP xserver so that SAP xserver starts on all nodes that the liveCache resources can fail over to. To implement this configuration, ensure that the nodelist parameter of the SAP xserver resource group contains all the nodes listed in the liveCache resource groups' nodelist. Also, the value of desired_primaries and maximum_primaries of the SAP xserver resource group must be equal to each other.

   ---

   # scrgadm -a -g xserver-resource-group \ -y Maximum_primaries=value \ -y Desired_primaries=value \ -h nodelist

9. Create an SAP xserver resource in this scalable resource group.

   # scrgadm -a -j xserver-resource\ -g xserver-resource-group -t SUNW.sap_xserver

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

10. Enable the scalable resource group that now includes the SAP xserver resource.

    # scswitch -Z -g xserver-resource-group

11. Set up a resource group dependency between SAP xserver and liveCache.

    # scrgadm -c -g livecache-resource-group \ -y rg_dependencies=xserver-resource-group

12. Enable the liveCache failover resource group.

    # scswitch -Z -g livecache-resource-group

13. Are you running an APO application server on a node that liveCache can fail over to?

    • If no, this step completes this procedure.

    • If yes, proceed to Step 14.

14. Is the scalable APO application server resource group already in an RGOffload resource's rg_to_offload list?

    # scrgadm -pvv | grep -i rg_to_offload | grep value:

    • If yes, this step completes this procedure.

    • If no, consider adding an RGOffload resource in the liveCache resource group.

      This configuration enables you to automatically shut down the APO application server if the liveCache resource fails over to a node on which the APO application server was running.

      For the procedure on how to set up an RGOffload resource, see Sun Cluster 3.1 Data Service Planning and Administration Guide.