Verifying the 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.

Verify the operation of the fault monitor for the SAP enqueue server
Verify the operation of the fault monitor for the SAP replica server
Verify the operation of the fault monitor for the SAP message server
Verify the operation of the fault monitor for the SAP web application server component
Verify the installation and configuration of the SAP J2EE engine

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

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

Log in to a node as superuser.
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.
Bring online the resource group to which the SAP enqueue server belongs.
```
# clresourcegroup online -n node central-rg
```
-n node

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

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.
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.
Confirm that the SAP enqueue server fails over to the node where SAP replica server is online, if configured.
Run the clresource status command to confirm that the SAP enqueue server resource is offline on the first node or zone and online on the second node or zone.
Again, bring online the resource group to which the SAP enqueue server belongs.
```
# clresourcegroup online -n node central-rg
```
-n node

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

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.
Log in to a different node or zone as superuser. On this node or zone, bring online the resource group to which the SAP replica server belongs.
```
# clrsourcegroup online -n node repl-rg
```
-n node

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

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.
Again, abnormally terminate the SAP enqueue server, as in Step 4.
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 clresource status command to confirm that the SAP enqueue server resource group is offline on the first node or zone and online on the second node or zone. 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 zone or be offline.

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

Log in to a node as superuser.
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.
```
# clresourcegroup online -n node central-rg
```
-n node

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

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.
Log in to a different node as superuser.
Bring online the resource group to which the SAP replica server belongs.
```
# clresoiurcegroup online -n node repl-rg
```
-n node

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

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.
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.
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 clresource status 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 Oracle Solaris Cluster Data Services Planning and Administration Guide.

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

Log in to a node as superuser.
Bring online the resource group to which the SAP message server belongs.
```
# clresourcegroup switch -n node central-rg
```
-n node

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

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.
Specify that failover is to be enabled for the resource group.
```
# clresourcegroup set -p Failover_Enabled=True central-rg
```
-p Failover_Enabled=True

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

central-rg

Specifies the name of the resource group to be modified.
Terminate the SAP message server.
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 clresource status 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 Oracle Solaris Cluster Data Services Planning and Administration Guide.
Again, bring online the resource group to which the SAP message server belongs, as described in Step 2.
Specify that failover is to be disabled for the resource group.
```
# clresourcegroup set -p Failover_Enabled=False central-rg
```
-p Failover_Enabled=False

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

central-rg

Specifies the name of the resource group to be modified.
Terminate the SAP message server.
Confirm that the SAP message server restarts.
Because the Failover_Enabled is set to False, the SAP message server always restarts.

How to Verify the Operation of the Fault Monitor for the SAP Web Application Server and SAP J2EE Engine Components

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

Log in to a node as superuser.
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.
```
# clresourcegroup switch -n node central-rg
```
-n node

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

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.
Bring online the resource group to which the SAP web application server or SAP J2EE Enginecomponent belongs.
For SAP web application server component only:
```
# clresourcegroup switch -n node webas-rg
```
-n node

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

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.

For SAP J2EE Engine component only:
```
# clresourcegroup switch -n node j2ee-rg
```
-n node

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

j2ee-rg

Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP J2EE Engine component belongs.
Terminate the SAP web application server or SAP J2EE Engine component.
Confirm that the SAP web application server or SAP J2EE Engine 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 or SAP J2EE Engine component resource was configured as a failover or a scalable resource.
- If the SAP web application server or SAP J2EE Engine 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 or SAP J2EE Engine component is offline.
- If the SAP web application server or SAP J2EE Engine component resource was configured as a scalable resource, the resource is offline on this node.
Run the clresource status command to determine the status of the SAP web application server or SAP J2EE Engine 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 Oracle Solaris Cluster Data Services Planning and Administration Guide.

Skip Navigation Links
Exit Print View
	Oracle Solaris Cluster Data Service for SAP Web Application Server Guide Oracle Solaris Cluster