Use this procedure to install scalable application server instances. This procedure assumes that you installed the central instance and the database. This procedure includes additional steps for SAP 6.10 and SAP 6.20 users to ensure that Sun Cluster HA for SAP can manage and bring online SAP 6.10 and SAP 6.20 services. SAP 6.10 and SAP 6.20 create one startsap script and one stopsap script. Other SAP versions create one of each of theses scripts for each service you create. This difference accounts for the additional steps for SAP 6.10 and SAP 6.20 users.
To configure a J2EE engine cluster with your Sun Cluster HA for SAP, after you complete this procedure, complete the additional steps in How to Configure an SAP J2EE Engine Cluster with your Sun Cluster HA for SAP with an Application Server.
To configure an SAP Web dispatcher with your Sun Cluster HA for SAP agent, after you complete this procedure, complete the additional steps in How to Configure an SAP Web Dispatcher With Your Sun Cluster HA for SAP.
The following file system layout ensures ease of use and prevents data from being overwritten.
Cluster File Systems
/usr/sap/SID -> all subdirectories except the app-instance subdirectory
/usr/sap/SID/home -> the SAPSIDadm home directory
Local File Systems
Create all SAP directories on cluster file systems.
Ensure that the central instance and the database can fail over.
Set up the lock file on cluster file system for the central instance to prevent a multiple startup from a different node.
For the procedure on how to set up a lock file on the central instance, see How to Set Up a Lock File for Central Instance or the Failover Application Server.
Ensure that all application servers can use the SAP binaries on a cluster file system.
Install the central instance and the database on a cluster file system.
See the SAP document Installation of the SAP R/3 on UNIX for details on how to install the central instance and the database.
On all nodes that will host the scalable application server, create a local directory for the data/log/sec/work directories and the log files for starting and stopping the application server.
Create a local directory for each new application server.
# mkdir -p /usr/sap/local/SID/D03
You must perform this step. If you do not perform this step, you will inadvertently install a different application server instance on a cluster file system and the two application servers will overwrite each other.
Set up a link to point to the local application server directory from a cluster file system, so the application server and the startup log file and the stop log file will be installed on the local file system.
# ln -s /usr/sap/local/SID/D03 /usr/sap/SID/D03
Install the application server.
Are you using SAP 6.10 or SAP 6.20?
Become user sapsidadm.
Make a copy of the startsap script and the stopsap script, and save these files in the SAPSIDadm home directory. The filenames that you choose specify this instance.
# cp /usr/sap/SID/SYS/exe/run/startsap \ $SAPSID_HOME/startsap_instance-number # cp /usr/sap/SID/SYS/exe/run/stopsap \ $SAPSID_HOME/stopsap_instance-number
Make backup copies of the following files because you will modify them. In the SAP profile directory, modify all the filenames for this instance. The filenames that you choose must be specific to this instance, and they must follow the same naming convention you chose in Step 8.
# mv SAPSID_Service-StringSystem-Number_physical-hostname \ SAPSID_Service-StringSystem_instance-number # mv START_Service-StringSystem-Number_physical-hostname \ START_Service-StringSystem_instance-number
Modify the contents of the files you created in Step 9 to replace any reference to the physical host with the instance number.
It is important that you make your updates consistent so that you can start and stop this application server instance from all the nodes that will run this scalable application server. For example, if you make these changes for SAP instance number 02, then use 02 where this instance number appears. If you do not use a consistent naming convention you will be unable start and stop this application server instance from all the nodes that will run this scalable application server.
Edit the start script and the stop script so that the startup log file and the stop log file will be node specific under the home directories of users sapsidadm and orasapsid.
# vi startsap_D03
LOGFILE=$R3S_LOGDIR/`basename $0`_`uname -n`.log
Copy the application server (with the same SAPSID and the same instance number) on all nodes that run the scalable application server.
The nodes that run the scalable application server are in the scalable application server resource group nodelist.
Ensure that you can startup and stop the application server from each node, and verify that the log files are in the correct location.
Create the SAP logon group if you use a logon group.
To configure a J2EE engine cluster with your Sun Cluster HA for SAP, go to How to Configure an SAP J2EE Engine Cluster with your Sun Cluster HA for SAP with an Application Server.
To configure an SAP Web dispatcher with your Sun Cluster HA for SAP agent, go to How to Configure an SAP Web Dispatcher With Your Sun Cluster HA for SAP.
If you are not using a J2EE engine cluster or an SAP Web dispatcher with your Sun Cluster HA for SAP, go to Configuring Your Highly Available Database.