test

Sun Cluster Data Service for SAP Web Application Server Guide for Solaris OS

How to Modify the Installation for a Scalable SAP Web Application Server Component

The SAP web application server component of the SAP Web Application Server platform can be configured either as a failover resource or as a scalable resource.

  1. Install the software as described in How to Install and Configure the SAP Web Application Server.

    The SAP Web Application Server software is installed on a global file system under /usr/sap/SAPSID/INSTANCE_NAME. Note that SAPSID represents the SAP system identification and INSTANCE_NAME represents the name of the SAP web application server instance.

  2. Become the SAP administration user sapsidadm on each node on which you plan to run the scalable SAP web application server component resource group.

  3. Update the profile file names and contents to match a string instead of a logical host name.

    A scalable resource group does not contain a logical host. Therefore, if a resource group for the SAP web application server component is configured to be scalable, the script $HOME/loghost does not return a logical host name. The script returns a string, for example, “scalable” to identify the instance. Therefore, you must update the profile file names and contents to match a string, for example, “scalable”, instead of a logical host name.

    1. Update the profile files for this instance in the directory /usr/sap/SAPSID/SYS/profile. Update the file names and their contents to match the string that you want to use, for example, “scalable”.

    2. Update the script $HOME/loghost, as in the following example.


      if [ "$1" = "D04" ]; then
   echo scalable;
fi

  4. On each node, including the original one, create a local file system.


    # mkdir /usr/sap/local/SAPSID/INSTANCE_NAME

  5. On each node, including the original one, copy the software from the global file system to the local file system that you created in Step 4.


    # su - sapsidadm
# cp -r  /usr/sap/SAPSID/INSTANCE_NAME/* \
/usr/sap/local/SAPSID/INSTANCE_NAME

  6. On the original node, remove the original installation directory.


    # rm -r /usr/sap/SAPSID/INSTANCE_NAME

  7. On each node, including the original one, create a symbolic link from the global file system to the local file system.


    # ln -s  /usr/sap/local/SAPSID/INSTANCE_NAME \
/usr/sap/SAPSID/INSTANCE_NAME

  8. Update the SAP start and stop scripts with unique names for the log files.

    When the SAP web application server component resource group is configured to be scalable, multiple instances of the application can be running simultaneously on different nodes. If all instances write to the same log file, they overwrite previously written information. Therefore, change the names of the log files that are specified in the SAP start and stop scripts so that they have unique names. Renaming the log files ensures that each node writes to a unique file. In the following example, the node name is appended to the log file name.

    Example of entry in script before updating:

    LOGFILE=$R3S_LOGDIR/`basename ${0}_${INSTANCE}.log`

    Example of entry in script after updating:

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