test

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

ProcedureHow 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.

Steps

  1. On each node on which you plan to run the scalable SAP web application server component resource group, create a local file system.

    This file system can be defined as you choose, as in the following example.


    # mkdir /usr/sap/local/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. Copy the dialog instance from the node where it was installed to the local file systems on the other nodes.

  3. Create symbolic links to the dialog instance.

    On each node, create a symbolic link to the local file system from the required directory path for the installation, as in the following example.


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

  4. Become the SAP administration user sapsidadm in order to perform the remaining steps in this procedure.

    • If the SAP Web Application Server software was installed on the global file system, perform the remaining steps on the node where the software was installed.

    • If the SAP Web Application Server software was installed on the local file systems, perform the remaining steps on each node on which you plan to run the scalable SAP web application server component resource group.

  5. Update the script $HOME/loghost to return the physical 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, you must update the script $HOME/loghost to return the physical host name. In the following example, D84 is the full name of the dialog instance.


    if [ "$1" = "D84" ]; then
  echo `hostname`; 
fi

  6. 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

  7. Make sure that the parameter enq/serverhost in the SAP instance profile contains the name of the logical host on which the SAP enqueue server is running.

  8. Verify the instance parameters.

    Start the configuration tool with the script offlinecfgeditor.sh, which is located in the directory /usr/sap/SAPSID/JCINSTANCE_NUMBER/j2ee/configtool.

    • Ensure that the cluster_data instance parameter is set to Propertysheet instance.properties.IDxxxxxx.

    • Ensure that instance.ms.host is set to the logical host name.