test

Sun Cluster Data Service for SAP Web Application Server Guide for Solaris OS

Verifying the Sun Cluster HA for SAP Web Application Server Installation and Configuration

You have installed, registered, and configured the data service for SAP Web Application Server. Now verify that the data service makes the SAP Web Application Server highly available by performing the following tasks.

See Tuning the Sun Cluster HA for SAP Web Application Server Fault Monitors for a description of the fault monitors.

ProcedureHow to Verify the Operation of the Fault Monitor for the SAP Enqueue Server

Perform this procedure on each set of two nodes where the SAP enqueue server and the SAP replica server can run.

Steps

  1. Log in to a node as superuser.

  2. Ensure that the SAP replica server resource group is offline on all nodes.

    At this point in this procedure you are testing the behavior of the SAP enqueue server resource group without the SAP replica server resource group. Therefore, the SAP replica server resource group must be offline on all nodes. Further in this procedure you will test the behavior of the SAP enqueue server with the SAP replica server resource group.

  3. Bring online the resource group to which the SAP enqueue server belongs.


    # scswitch -z  -g central-rg -h node
    -z

    Specifies that a resource group is to be brought online.

    -g central-rg

    Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP enqueue server belongs.

    -h node

    Specifies the name of the node on which the resource group is to be brought online. This node is the node that you have just logged in to.

  4. Abnormally terminate the SAP enqueue server.

    1. Determine the process ID of the SAP enqueue server, where the name of the SAP enqueue server executable file is enserver.


      # ps -ef | grep enserver

    2. Kill the process for the SAP enqueue server.


      # kill -9 pid
      pid

      Specifies the process ID of the SAP enqueue server. This ID is the process ID that you determined with the ps and grep commands.

  5. Confirm that the SAP enqueue server fails over to another node.

    Run the scstat command to confirm that the SAP enqueue server resource is offline on the first node and online on the second node.

  6. Again, bring online the resource group to which the SAP enqueue server belongs.


    # scswitch -z  -g central-rg -h node
    -z

    Specifies that a resource group is to be brought online.

    -g central-rg

    Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP enqueue server belongs.

    -h node

    Specifies the name of the node on which the resource group is to be brought online.

  7. Log in to a different node as superuser. On this node, bring online the resource group to which the SAP replica server belongs.


    # scswitch -z  -g repl-rg -h node
    -z

    Specifies that a resource group is to be brought online.

    -g repl-rg

    Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP replica server belongs.

    -h node

    Specifies the name of the node on which resource group is to be brought online. This node is the node that you have just logged in to.

  8. Again, abnormally terminate the SAP enqueue server, as in Step 4.

  9. Confirm that the SAP enqueue server resource group fails over to the node on which the SAP replica server resource group is running.

    As the SAP enqueue server resource group starts on the node on which the SAP replica server resource group is running, the SAP replica server resource group fails over to another available node. If no node is available, the SAP replica server resource group is offline.

    Run the scstat command to confirm that the SAP enqueue server resource group is offline on the first node and online on the second node. Confirm also that the SAP replica server resource group is offline on the second node. The SAP replica server resource group can be either online on another available node or offline.

ProcedureHow to Verify the Operation of the Fault Monitor for the SAP Replica Server

Perform this procedure on each set of two nodes where the SAP replica server and the SAP enqueue server can run.

Steps

  1. Log in to a node as superuser.

  2. Bring online the resource group to which the SAP enqueue server belongs.

    The SAP replica server resource is configured to be dependent on the SAP enqueue server resource.


    # scswitch -z  -g central-rg -h node
    -z

    Specifies that a resource group is to be brought online.

    -g central-rg

    Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP enqueue server belongs.

    -h node

    Specifies the name of the node on which the resource group is to be brought online. This node is the node that you have just logged in to.

  3. Log in to a different node as superuser.

  4. Bring online the resource group to which the SAP replica server belongs.


    # scswitch -z  -g repl-rg -h node
    -z

    Specifies that a resource group is to be brought online.

    -g repl-rg

    Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP replica server belongs.

    -h node

    Specifies the name of the node on which the resource group is to be brought online. This node is the node that you have just logged in to.

  5. Abnormally terminate the SAP replica server.

    1. Determine the process ID of the SAP replica server, where the name of the SAP replica server executable file is enrepserver.


      # ps -ef | grep enrepserver

    2. Kill the process for the SAP replica server.


      # kill -9 pid
      pid

      Specifies the process ID of the SAP replica server. This ID is the process ID that you determined with the ps and grep commands.

  6. Confirm that the SAP replica server either restarts or fails over.

    If the abnormal termination action in Step 5 is repeated a specified number of times within a specified time interval, the SAP replica server fails over to an available node that is not running the SAP enqueue server. If no node is available, the SAP replica server is offline.

    If the abnormal termination action is not repeated a specified number of times within a specified time interval, the SAP replica server restarts on the same node.

    Run the scstat command to determine the status of the SAP replica server.

    The maximum number of times that the application can be abnormally terminated before failing over is specified with the standard property Retry_count. The time interval is specified with the standard property Retry_interval. These properties are described in Resource Properties in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

ProcedureHow to Verify the Operation of the Fault Monitor for the SAP Message Server

Perform this procedure on each node where the SAP message server can run.

Steps

  1. Log in to a node as superuser.

  2. Bring online the resource group to which the SAP message server belongs.


    # scswitch -z  -g central-rg -h node
    -z

    Specifies that a resource group is to be brought online.

    -g central-rg

    Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP message server belongs.

    -h node

    Specifies the name of the node on which the resource group is to be brought online. This node is the node that you have just logged in to.

  3. Specify that failover is to be enabled for the resource group.


    # scrgadm -c  -g central-rg -y Failover_Enabled=True
    -c

    Specifies that an existing configuration is to be modified

    -g central-rg

    Specifies the name of the resource group to be modified

    -y Failover_Enabled=True

    Specifies that the resource group is to fail over when Retry_count is exceeded during Retry_interval

  4. Terminate the SAP message server.

  5. Confirm that the SAP message server either restarts or fails over.

    If the abnormal termination action in Step 4 is repeated a specified number of times within a specified time interval, the SAP message server fails over to an available node. If no node is available, the SAP message server is offline.

    If the abnormal termination action is not repeated a specified number of times within a specified time interval, the SAP message server restarts on the same node.

    Run the scstat command to determine the status of the SAP message server.

    Note that the maximum number of times that the application can be abnormally terminated before failing over is specified with the standard property Retry_count, and the time interval is specified with the standard property Retry_interval. These properties are described in Resource Properties in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

  6. Again, bring online the resource group to which the SAP message server belongs, as described in Step 2.

  7. Specify that failover is to be disabled for the resource group.


    # scrgadm -c  -g central-rg -y Failover_Enabled=False
    -c

    Specifies that an existing configuration is to be modified

    -g central-rg

    Specifies the name of the resource group to be modified

    -y Failover_Enabled=False

    Specifies that the resource group is not to fail over when Retry_count is exceeded during Retry_interval

  8. Terminate the SAP message server.

  9. Confirm that the SAP message server restarts.

    Because the Failover_Enabled is set to False, the SAP message server always restarts.

ProcedureHow to Verify the Operation of the Fault Monitor for the SAP Web Application Server Component

Perform this procedure on each node where the SAP web application server component can run.

Steps

  1. Log in to a node as superuser.

  2. Bring online the resource group to which the SAP message server belongs.

    The SAP web application server component resource is configured to be dependent on the SAP message server resource.


    # scswitch -z  -g central-rg -h node
    -z

    Specifies that a resource group is to be brought online.

    -g central-rg

    Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP message server belongs.

    -h node

    Specifies the name of the node on which resource group is to be brought online. This node is the node that you have just logged in to.

  3. Bring online the resource group to which the SAP web application server component belongs.


    # scswitch -z  -g webas-rg -h node
    -z

    Specifies that a resource group is to be brought online.

    -g webas-rg

    Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP web application server component belongs.

    -h node

    Specifies the name of the node on which the resource group is to be brought online. This node is the node that you have just logged in to.

  4. Terminate the SAP web application server component.

  5. Confirm that the SAP web application server component is restarted locally.

    If the abnormal termination action in Step 4 is repeated a specified number of times within a specified time interval, the resulting behavior depends on whether the SAP web application server component resource was configured as a failover or a scalable resource.

    • If the SAP web application server component resource was configured as a failover resource, the resource fails over to an available node. If no node is available, the SAP web application server component is offline.

    • If the SAP web application server component resource was configured as a scalable resource, the resource is offline on this node.

    Run the scstat command to determine the status of the SAP web application server component.

    Note that the maximum number of times that the application can be abnormally terminated before failing over or becoming offline is specified with the standard property Retry_count, and the time interval is specified with the standard property Retry_interval. These properties are described in Resource Properties in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.

ProcedureHow to Verify the Installation and Configuration of Sun Cluster HA for SAP J2EE Engine

Steps

  1. Become superuser on one of the nodes in the cluster that is to host the SAP J2EE engine.

  2. Run the scstat command to ensure all the resources are online.


    # scstat

    For each SAP J2EE engine resource that is not online, run the scswitch command as follows.


    # scswitch -e -j j2ee-rs
    -e

    Specifies that a resource is to be enabled

    -j j2ee-rg

    Specifies the name of the resource that is to be enabled

  3. Run the scswitch command to switch the SAP J2EE engine resource group to another cluster node, such as node2.


    # scswitch -z -g j2ee-rg -h node2
    -z

    Specifies that a resource group is to be brought online

    -g j2ee-rg

    Specifies the name of the resource group to be brought online

    -h node2

    Specifies the name of the node on which the resource group is to be brought online