Sun Cluster 3.0 U1 Data Services Installation and Configuration Guide

Installing and Configuring SAP and the Database

Use the procedures in this section to perform the following tasks.

Install SAP and the database.
Enable SAP to run in the cluster.
Verify SAP and database installation.

How to Install SAP and the Database

This section describes how to install and configure SAP and the database and how to enable SAP to run in the cluster.

Become superuser on one of the nodes in the cluster where you are installing the central instance.

Install SAP binaries on the cluster file system.

Note -
Before you install SAP software on the cluster file system, use the scstat(1M) command to verify that the Sun Cluster software is fully operational.
1. For all SAP-required kernel parameter changes, edit the /etc/system file on all cluster nodes that will run the SAP application.
  
  After you edit the /etc/system file, reboot each node. See the SAP document R/3 Installation on UNIX-OS Dependencies for details on kernel parameter changes.
2. See the SAP document Installation of the SAP R/3 on UNIX for details on how to install the central instance and the database.

Where to Go From Here

After you install SAP and the database, go to "How to Enable SAP to Run in the Cluster".

How to Enable SAP to Run in the Cluster

During SAP installation, the SAP software creates files and shell scripts on the server on which you installed the SAP central instance. These files and scripts use physical-server names. To run the SAP software with Sun Cluster software, replace references to a physical server with references to a logical hostname. Throughout these steps, the replaceable term physicalserver represents a physical server, and the replaceable term logical-hostname represents a logical hostname. The phrase logical hostname denotes the logical hostname where traffic between the database and the application server occurs. See the Sun Cluster 3.0 U1 Concepts for more information on logical hostnames.

Perform the following steps to enable SAP to run in the cluster.

Note -

Make backup copies of the files that you will modify in the following steps.

Shut down the SAP central instance and the database.

Note -
In addition to the central instance and database, shut down any application servers that are running.

Modify all file names that include a physical-server name in the following directories.
- The sapsidadm home directory - Become the sapsidadm user before you edit these files.
- The orasapsid home directory - Become the orasapsid user before you edit these files.
- SAP profile directory - Become the sapsidadm user before you edit these files.
For example, rename the .sapenv_physicalserver.csh file as .sapenv_logical-hostname.csh.

Modify all file contents-except log file contents-that reference a physical-server name in the following directories.
- The sapsidadm home directory - Become the sapsidadm user before you edit these files.
- The orasapsid home directory - Become the orasapsid user before you edit these files.
- SAP profile directory - Become the sapsidadm user before you edit these files.
For example, change any physicalserver reference in the startup and shutdown scripts to a logical-hostname reference.

As user sapsidadm, add an entry such as the following example for the parameter SAPLOCALHOST.
SAPLOCALHOST logical-hostname
Add this entry to the SAPSID_Service-StringSystem-Number_logical-hostname profile file under the /sapmnt/SAPSID/profile directory.

This entry enables the external application server to locate the central instance by using the logical hostname.

Where to Go From Here

After you enable SAP to run in the cluster, go to "How to Verify SAP and Database Installation With Central Instance".

How to Verify SAP and Database Installation With Central Instance

Perform this procedure to test starting and stopping the SAP central instance on all potential nodes on which the central instance can run.

Create the failover resource group to hold the network logical-hostname and central-instance resources.
# scrgadm -a -g sap-ci-resource-group
Note -
You can optionally select the set of nodes on which the SAP central instance can run with the -h option to the scrgadm(1M) command.
# scrgadm -a -g sap-ci-resource-group -h nodelist

Verify that you have added all the logical hostnames that you use to your name-service database.

Run the scrgadm command to add a logical hostname to the failover resource group.

# scrgadm -a -L -g sap-ci-resource-group -l logical-hostname -n nafo0@node1,nafo0@node2

Enable the resource group.

Run the scswitch(1M) command to move the resource group into a managed state and bring the resource group online.
# scswitch -Z -g sap-ci-resource-group

Start the central instance and the database.

Start the SAP GUI to verify that SAP initializes correctly.

The default dispatcher port is 3200.

Stop the central instance and the database.

Run the scswitch command.

In the following example, the replaceable term sap-ci-resource-group represents the resource group that contains the logical-hostname resource for the central-instance resource. Switch this resource group to another cluster member that can host the central instance.
# scswitch -z -h node -g sap-ci-resource-group

Repeat Step 5 through Step 7 until you verify startup and shutdown of the central instance on each cluster node that can host the central instance.

Where to Go From Here

After you verify SAP and database installation with central instance, go to "How to Verify the Sun Cluster HA for SAP Installation With Application Server".

How to Verify SAP and Database Installation With Application Server

If you have installed and configured any application servers, perform this procedure on all potential nodes on which the application server can run. This procedure tests starting and stopping the application server.

Create the failover resource group to hold the network logical-hostname and application-server resources.
# scrgadm -a -g sap-as-resource-group
Note -
You can optionally select the set of nodes on which the SAP application server can run with the -h option to the scrgadm command.
# scrgadm -a -g sap-as-resource-group -h nodelist -n nafo0@node1,nafo0@node2

Verify that you have added all the logical hostnames that you use to your name-service database.

Run the scrgadm command to add a logical hostname to the failover resource group.
# scrgadm -a -L -g sap-as-resource-group -l logical-hostname

Enable the resource group.

Run the scswitch(1M) command to move the resource group into a managed state and bring the resource group online.
# scswitch -Z -g sap-as-resource-group

Start the application server.

Start the SAP GUI to verify that the SAP application server initializes correctly.

Stop the application server.

Run the scswitch command.

In the following example, the term sap-as-resource-group represents the resource group that contains the logical-hostname resource for the application-server resource. Switch this resource group to another cluster member that can host the application server.
# scswitch -z -h node -g sap-as-resource-group

Repeat Step 5 through Step 7 until you verify startup and shutdown of the application server on each cluster node that can host the application server.

Where to Go From Here

After you finish all procedures to install and configure SAP and the database, go to "How to Register and Configure Sun Cluster HA for SAP With Central Instance".