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.
If you configure the SAP web application server component as a failover resource, skip this section.
If you configure the SAP web application server component as a scalable resource, you must perform the following steps.
Update the script $HOME/loghost to return the physical hostname or a string.
A scalable resource group does not contain a logical host. Therefore, if a resource group for the SAP web application server component is a scalable SAP J2EE engine resource, you must update the script $HOME/loghost to return the physical hostname. In the following example, J85 is the full name of the dialog instance.
if [ "$1" = "J85" ]; then echo `hostname`; fi |
Create a copy of the SAP start and stop scripts, as in the following example.
$ cp /sapmnt/SID/exe/startsap_webas_server /sapmnt/SID/exe/startsap_webas_server_scal |
$ cp /sapmnt/SID/exe/stopsap_webas_server /sapmnt/SID/exe/stopsap_webas_server_scal |
Update the SAP start and stop scripts that you created in the previous step 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
For more information on how to update the SAP start and stop scripts, see How to Install and Configure the SAP Web Application Server and the SAP J2EE Engine
Make sure that the parameter enq/serverhost in the SAP instance profile contains the logical hostname of the SAP enqueue server.
Verify the instance parameters.
This step is only applicable to SAP J2EE engine instances.
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 hostname.