Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for SAP Web Application Server Guide |
1. Installing and Configuring HA for SAP Web Application Server
HA for SAP Web Application Server Overview
Overview of the Installation and Configuration Process for HA for SAP Web Application Server
Planning the HA for SAP Web Application Server Installation and Configuration
Supported Data Service Configurations
Configuration Planning Questions
Installing and Configuring SAP Web Application Server
Configuring Your Highly Available Database
How to Install and Configure the SAP Web Application Server and the SAP J2EE Engine
How to Modify the Installation for a Scalable SAP Web Application Server Component
How to Enable the SAP Web Application Server to Run in a Cluster
How to Enable the Stand-Alone SAP J2EE Engine to Run in a Cluster
Verifying the SAP Web Application Server Installation and Configuration
How to Verify That the Configuration for the SAP Message Server Is Correct for the Data Service
Installing the HA for SAP Web Application Server Packages
How to Install the HA for SAP Web Application Server Packages
Registering and Configuring HA for SAP Web Application Server
Setting HA for SAP Web Application Server Extension Properties
Tools for Registering and Configuring HA for SAP Web Application Server
How to Register and Configure the HA for SAP Web Application Server by Using clsetup
Setting Up the SAP Web Application Server on Non-Global Zones for HAStoragePlus Configuration
How to Set Up the SAP Web Application Server on Non-Global Zones for HAStoragePlus Configuration
How to Register and Configure HAStoragePlus Resources for the SAP Central Services Components
How to Register and Configure an SAP Enqueue Server Resource
How to Register and Configure an SAP Replica Server Resource
How to Register and Configure an SAP Message Server Resource
How to Register and Configure an SAP Web Application Server Component
Examples of Configuring the SAP Web Application Server
Using Alternate Project Identification
Tuning the HA for SAP Web Application Server Fault Monitors
Operation of the Fault Monitor for the SAP Enqueue Server Resource Type
Operation of the Fault Monitor for the SAP Replica Server Resource Type
Operation of the Fault Monitor for the SAP Message Server Resource Type
Verifying the HA for SAP Web Application Server Installation and Configuration
How to Verify the Operation of the Fault Monitor for the SAP Enqueue Server
How to Verify the Operation of the Fault Monitor for the SAP Replica Server
How to Verify the Operation of the Fault Monitor for the SAP Message Server
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.
Perform this procedure on each set of two nodes where the SAP enqueue server and the SAP replica server can run.
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.
# clresourcegroup online -n node central-rg
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.
Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP enqueue server belongs.
# ps -ef | grep enserver
# kill -9 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.
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.
# clresourcegroup online -n node central-rg
Specifies the name of the node or zone on which the resource group is to be brought online.
Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP enqueue server belongs.
# clrsourcegroup online -n node repl-rg
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.
Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP replica server belongs.
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.
Perform this procedure on each set of two nodes where the SAP replica server and the SAP enqueue server can run.
The SAP replica server resource is configured to be dependent on the SAP enqueue server resource.
# clresourcegroup online -n node central-rg
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.
Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP enqueue server belongs.
# clresoiurcegroup online -n node repl-rg
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.
Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP replica server belongs.
# ps -ef | grep enrepserver
# kill -9 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.
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.
Perform this procedure on each node where the SAP message server can run.
# clresourcegroup switch -n node central-rg
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.
Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP message server belongs.
# clresourcegroup set -p Failover_Enabled=True central-rg
Specifies that the resource group is to fail over when Retry_count is exceeded during Retry_interval.
Specifies the name of the resource group to be modified.
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.
# clresourcegroup set -p Failover_Enabled=False central-rg
Specifies that the resource group is not to fail over when Retry_count is exceeded during Retry_interval.
Specifies the name of the resource group to be modified.
Because the Failover_Enabled is set to False, the SAP message server always restarts.
Perform this procedure on each node where the SAP web application server or SAP J2EE Engine component can run.
The SAP web application server component resource is configured to be dependent on the SAP message server resource.
# clresourcegroup switch -n node central-rg
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.
Specifies the name of the resource group to be brought online. This group is the resource group to which the SAP message server belongs.
For SAP web application server component only:
# clresourcegroup switch -n node webas-rg
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.
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
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.
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.
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.