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
Before you install the HA for SAP Web Application Server packages, verify that the SAP Web Application Server software is correctly installed and configured to run in a cluster. These procedures do not verify that the SAP Web Application Server application is highly available because you have not yet installed your data service.
The procedures in this section verify the installation and configuration of the following SAP Web Application Server components.
SAP central services, which includes these servers:
SAP enqueue server
SAP replica server
SAP message server
SAP web application server component
SAP J2EE engine
Perform this procedure on each set of two nodes or zones that can master the SAP central services resource group and the SAP replica server resource group.
For a description of the extension properties for the SAP enqueue server resource type, SUNW.sapenq, see SUNW.sapenq Extension Properties. For a description of the extension properties for the SAP replica server resource type, SUNW.saprepl, see SUNW.saprepl Extension Properties.
# clresourcegroup switch -n node1 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.
The extension property SAP_User for the SUNW.sapenq resource type specifies the name of the administration user.
# enq_server_cmd pf=enq_profile
Specifies the full path to the SAP enqueue server executable. The extension property Enqueue_Server for the SUNW.sapenq resource type contains this value. The name of the SAP enqueue server executable file is enserver.
Specifies the full path to the profile for the SAP enqueue server. The extension property Enqueue_Profile for SUNW.sapenq resource type contains this value.
The name of the SAP enqueue server executable file is enserver.
# ps -ef | grep enserver
You can verify that the SAP enqueue server has started correctly in two ways.
Run the SAP utility ensmon.
$ ensmon -H localhost -S port 1
Specifies that the name of the host is localhost.
Specifies the enqueue port.
Specifies that the probe should check the SAP enqueue server only.
If this command is run on the command line, a return code is returned on the command line.
Check the log files that are written to the directory that was current when the SAP enqueue server command was run.
# clresourcegroup switch -n node2 repl-rg
Specifies that a resource group is to be brought online on a different node or zone.
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.
The extension property SAP_User for SUNW.saprepl resource type specifies the name of the administration user.
$ repl_server_cmd pf=repl_profile
Specifies the full path to the SAP replica server executable. The extension property Replica_Server for the SUNW.saprepl resource type contains this value. The name of the SAP replica server executable file is enrepserver.
Specifies the full path to the profile for the SAP replica server. The extension property Replica_Profile for the SUNW.saprepl resource type contains this value.
The name of the SAP replica server executable file is enrepserver.
# ps -ef | grep enrepserver
You can verify that the SAP replica server has started correctly in two ways.
Run the SAP utility ensmon.
$ ensmon -H localhost -S port 2
Specifies that the name of the host is localhost.
Specifies the enqueue port.
Specifies that the probe should check both the SAP enqueue server and the SAP replica server.
If this command is run on the command line, a return code is returned on the command line.
Check the log files that are written to the directory that was current when the SAP replica server command was run.
In order to create and check enqueue lock entries in Step 14, you must prepare entries in a test SAP profile, including SAPSYSTEM, SAPSYSTEMNAME, and INSTANCE_NAME.
See the SAP document The SAP Lock Concept (BC-CST-EQ) for details about all profile parameters at http://service.sap.com/ha.
# /usr/sap/SAPSID/SYS/exe/run/enqt pf=app_server_profile 11
Specifies the SAP system ID.
Specifies the full path to the test SAP profile that you set up in Step 13
# ps -ef | grep enserver # kill -9 pid
# ps -ef | grep enrepserver # kill -9 pid
# clresourcegroup switch -n node2 central-rg
# enq_server_cmd pf=enq_profile
# /usr/sap/SAPSID/SYS/exe/run/enqt pf=app_server_profile 20
Specifies the SAP system ID.
Specifies the full path to the test SAP profile that you set up in Step 13.
Perform this procedure on each node or zone that can master the SAP central services resource group.
For a description of the extension properties for the SAP message server resource type, SUNW.sapscs, see SUNW.sapscs Extension Properties.
# clresourcegroup switch -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.
Note that, in the first su command, the “dash” (-) argument causes the environment to be changed to the environment of superuser. The second su command, which is used without the “dash” argument, causes the environment to be retained.
# su - root # su sapsidadm
Set the LD_LIBRARY_PATH variable to /sapmnt/SAPSID/exe.
Set the SAPSYSTEMNAME variable to the appropriate SAP system identification.
Add the following paths to the PATH variable: /usr/sbin:/usr/bin:/usr/cluster/bin.
Set the SAPSYSTEM variable to the system number configured for the specific instance of SAP which should be handled by the resource.
Set the HOME environment variable to the home directory of the SAP administration user.
Set the LOGNAME variable to root.
The following command is an example that runs the SAP start script for the SAP message server. You must run the equivalent command for your installation.
# /usr/sap/SC3/SYS/exe/run/startsap_msg_server r3 SCS01
The full path to the probe is specified by the extension property Msg_Server_Monitor for the SUNW.sapscs resource type. For example, type the following command or the equivalent command.
# /usr/sap/SC3/SYS/exe/run/msprot -mshost host -msport port
The probe is successful when the return code equals zero.
Verify that the SAP message server can be stopped correctly. Run the SAP stop script for the SAP message server with the full path and the appropriate arguments. The following command is an example that runs the SAP stop script. Run the equivalent command for your installation.
# /usr/sap/SC3/SYS/exe/run/stopsap_msg_server r3 SCS01
Perform the following procedure on each node or zone that can master the resource group for the SAP web application server or SAP J2EE Engine component.
If the SAP web application server or SAP J2EE Engine component is configured as a scalable resource, the resource runs on all these nodes or zones simultaneously. Therefore, you must execute this procedure on all nodes or zones that can simultaneously master the scalable SAP web application server or SAP J2EE Engine component resource.
# su - root # su sapsidadm
Set the LD_LIBRARY_PATH variable to /sapmnt/SAPSID/exe.
Set the SAPSYSTEMNAME variable to the appropriate SAP system identification.
Add the following paths to the PATH variable: /usr/sbin:/usr/bin:/usr/cluster/bin.
Set the SAPSYSTEM variable to the system number configured for the specific instance of SAP which should be handled by the resource.
Set the HOME environment variable to the home directory of the SAP administration user.
Set the LOGNAME variable to root.
Before running the SAP start script in the next step, you must start the database.
The following command is an example that runs the SAP start script for the SAP web application server component. You must run the equivalent command for your installation.
# /usr/sap/SC3/SYS/exe/run/startsap_webas_server r3 D01
The following command is an example that runs the SAP start script for the SAP J2EE Engine component. You must run the equivalent command for your installation.
# /usr/sap/SC3/SYS/exe/run/startsap_webas_server r3 JC01
For SAP web application server component only:
The dpmon utility writes files to the current directory, and this directory must be writable by the SAP administration user. In Step 3 you set the HOME environment variable to the home directory of the SAP administration user.
# cd $HOME
For SAP J2EE Enginecomponent only:
The probe utility writes files to the current directory, and this directory must be writable by the SAP administration user. In Step 3 you set the HOME environment variable to the home directory of the SAP administration user.
# cd $HOME
# /usr/sap/SC3/SYS/exe/run/dpmon -info
The probe is successful when the return code equals zero.
Verify that the SAP Web Application Server or SAP J2EE engine can be stopped correctly. Run the SAP stop script for the SAP web application server or SAP J2EE engine component with the full path and the appropriate arguments. The following command is an example that runs the SAP stop script. Run the equivalent command for your installation.
For SAP web application server component only:
# /usr/sap/SC3/SYS/exe/run/stopsap_webas_server r3 D01
For SAP J2EE Enginecomponent only:
# /usr/sap/SC3/SYS/exe/run/stopsap_webas_server r3 JC01