test

Sun Cluster Data Service for SAP Guide for Solaris OS

ProcedureHow to Install and Enable an SAP Scalable Application Server

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, SAP 6.20, SAP 6.40, SAP 7.0 and later users to ensure that Sun Cluster HA for SAP can manage and bring online SAP 6.10, SAP 6.20, SAP 6.40, SAP 7.0 and later services. SAP 6.10, SAP 6.20, SAP 6.40, SAP 7.0 and later versions create one startsap script and one stopsap script. Other SAP versions create one startsap script and one stopsap script for each service you create. This difference accounts for the additional steps for SAP 6.10, SAP 6.20, SAP 6.40, SAP 7.0 and later users.

To configure a J2EETM engine cluster with your Sun Cluster HA for SAP, first complete this procedure. Then 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, first complete this procedure. Then complete the additional steps in How to Configure an SAP Web Dispatcher With Your Sun Cluster HA for SAP.

Tip –

The following file system layout ensures ease of use and prevents data from being overwritten.

  1. 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 the 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.

  2. 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 about how to install the central instance and the database.

  3. On all nodes that 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.

    Example:


    # mkdir -p /usr/sap/local/SUN/D03


    # chown sapsidadm:sapsys /usr/sap/local/SUN/D03
    Caution – Caution –

    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. The two application servers will then overwrite each other.

  4. Set up a link to point to the local application server directory from a cluster file system, so that the application server, the startup log file, and the stop log file is installed on the local file system.

    Example:


    # ln -s /usr/sap/local/SAPSID/D03 /usr/sap/SAPSID/D03

  5. Install the application server on all nodes.

  6. If you are using SAP 6.10, SAP 6.20, or SAP 6.40, perform the following sub steps. Otherwise, go to Step 7.

    1. Become user sapsidadm.

    2. Make a copy of the startsap script and the stopsap script, and save these files in the SAPSIDadm home directory. The file names that you choose specify this instance.


      # cp /usr/sap/SAPSID/SYS/exe/run/startsap \
$SAPSID_HOME/startsap_instance-number

# cp /usr/sap/SAPSID/SYS/exe/run/stopsap \
$SAPSID_HOME/stopsap_instance-number

  7. 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 or oradbsid.

    Example:


    # vi startsap_03

    Before:


    LOGFILE=$R3S_LOGDIR/`basename $0.log`

    After:


    LOGFILE=$R3S_LOGDIR/`basename $0`_`uname -n`.log

  8. If you are using the MaxDB database, perform the following sub steps. Otherwise, skip to Step 9.

    1. Create a .XUSER.62 file in the SAPSIDadm home directory as described in How to Install and Configure MaxDB in Sun Cluster Data Service for MaxDB Guide for Solaris OS.

      Note –

      This user whose home directory contains the .XUSER.62 file is an internal database user who has permissions to start, stop, and query the database.

    2. Verify that the .XUSER.62 file is correctly configured by using the -d option of the R3trans command. You must be an SAPSIDadm user to perform this verification.

  9. 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 resource group node-zone-list, which is located in the scalable application server .

  10. Ensure that you can start and stop the application server from each node, and verify that the log files are in the correct location. For further information about updates on SAP profiles, see the SAP documentation at http://service.sap.com/ha.

    Note –

    Update the files under the SAPSIDadm home directory so that they refer to the corresponding logical hosts. This ensures that the necessary environment variables are sourced.

  11. Create the SAP logon group if you use a logon group.

Next Steps

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.