Verifying the SAP Web Application Server Installation and Configuration

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.

Note - For more information, see the SAP documentation at http://service.sap.com/ha.

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

How to Verify the Installation and Configuration of the SAP Enqueue Server and the SAP Replica Server

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.

Become the superuser on one node, Node1.
Bring the SAP central services resource group online on Node1.
```
# clresourcegroup switch -n node1 central-rg
```
-n node1

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.
Become the administration user for the SAP enqueue server on Node1.
The extension property SAP_User for the SUNW.sapenq resource type specifies the name of the administration user.
Start the SAP enqueue server manually on Node1.
```
# enq_server_cmd pf=enq_profile
```
enq_server_cmd

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.

pf=enq_profile

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.
Confirm that the SAP enqueue server is up on Node1.
The name of the SAP enqueue server executable file is enserver.
```
# ps -ef | grep enserver
```
As user sapsidadm, verify that the SAP enqueue server has started correctly.
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
```
  -H localhost
  
  Specifies that the name of the host is localhost.
  
  -S port
  
  Specifies the enqueue port.
  
  1
  
  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.
On a different node, Node2, log in as superuser.
Bring the SAP replica server resource group online on Node2.
```
# clresourcegroup switch   -n node2 repl-rg
```
switch

Specifies that a resource group is to be brought online on a different node or zone.

-n node2

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

repl-rg

Specifies the name of the resource group to be brought online.
Become the administration user for the SAP replica server on Node2.
The extension property SAP_User for SUNW.saprepl resource type specifies the name of the administration user.
As user sapsidadm, start the SAP replica server manually on Node2.
```
$ repl_server_cmd pf=repl_profile
```
repl_server_cmd

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.

pf=repl_profile

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.
Confirm that the SAP replica server is active on Node2.
The name of the SAP replica server executable file is enrepserver.
```
# ps -ef | grep enrepserver
```
As user sapsidadm, verify that the SAP replica server has started correctly.
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
```
  -H localhost
  
  Specifies that the name of the host is localhost.
  
  -S port
  
  Specifies the enqueue port.
  
  2
  
  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.
Set up a test profile to be used with the enqt utility.
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.
Confirm that enqueue replication is working by performing the following steps.
1. Create some enqueue lock entries.
```
# /usr/sap/SAPSID/SYS/exe/run/enqt pf=app_server_profile 11
```
  SAPSID
  
  Specifies the SAP system ID.
  
  app_server_profile
  
  Specifies the full path to the test SAP profile that you set up in Step 13
2. Stop the SAP enqueue server on Node1.
```
# ps -ef | grep enserver
# kill -9 pid
```
3. Stop the SAP replica server on Node2.
```
# ps -ef | grep enrepserver
# kill -9 pid
```
4. Bring the SAP central services resource group online on Node2.
```
# clresourcegroup switch -n node2 central-rg
```
5. Become the administration user for the SAP enqueue server on Node2.
6. Start the SAP enqueue server manually on Node2.
```
# enq_server_cmd pf=enq_profile
```
7. Confirm that no enqueue entries are lost.
```
# /usr/sap/SAPSID/SYS/exe/run/enqt pf=app_server_profile 20
```
  SAPSID
  
  Specifies the SAP system ID.
  
  app_server_profile
  
  Specifies the full path to the test SAP profile that you set up in Step 13.

How to Verify That the Configuration for the SAP Message Server Is Correct for the Data Service

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.

Bring the SAP central services resource group online on a node or zone.
```
# clresourcegroup switch  -n node central-rg
```
-n node2

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.
Become superuser with superuser environment. Then become the sapsidadm user, while retaining the superuser environment.
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 following environment variables:
- 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.
Run the SAP start script for the SAP message server using the absolute path and the appropriate arguments, as in the following example.
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
```
After the SAP system starts successfully, run the fault monitor probe for the SAP message server.
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
```
Verify that the probe was successful.
The probe is successful when the return code equals zero.
Run the SAP stop script for the SAP message server to verify that the SAP message server can be stopped, as in the following example.
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
```

How to Verify That the Configuration for the SAP Web Application Server and SAP J2EE Engine Components Is Correct for the Data Service

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.

If you have configured the resource group for the SAP web application server or SAP J2EE Engine component as a failover resource group, enable the logical hostname resource for the resource group.
On the node where the logical hostname resource is enabled, become superuser, then the sapsidadm user with superuser environment.
```
# su - root
# su sapsidadm
```
Set the following environment variables:
- 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.
Start the database.
Before running the SAP start script in the next step, you must start the database.
Run the SAP start script for the SAP web application server or SAP J2EE Engine component using the absolute path and the appropriate arguments.
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
```
Change to the home directory of the SAP administration user.
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
```
For SAP web application server component only — after the SAP system starts successfully, run the probe command for the dispatcher of the SAP instance. The following command is an example:
```
# /usr/sap/SC3/SYS/exe/run/dpmon -p
```
For SAP J2EE Enginecomponent only — after the SAP J2EE engine starts successfully, verify it by deploying and running some examples. See the SAP Web Application Server Installation Guide for instructions.
Verify that the probe was successful.
The probe is successful when the return code equals zero.
Run the SAP stop script for the SAP web application server or SAP J2EE engine component to verify that the SAP Web Application Server or SAP J2EE engine can be stopped.
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
```

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