Managing Serviceguard Extension for SAP Version B.05.10, September 2010

SCSHOST = <[J]CIRELOC>
enque/serverinst = $(SCSID)
enque/serverhost = $(SCSHOST)
Here is an example template for the startup profile START_ERS<INSTNR>_<[A]REPRELOC>:
#--------------------------------------------------------------------
SAPSYSTEM = <INSTNR>
SAPSYSTEMNAME = <SID>
INSTANCE_NAME = ERS<INSTNR>
#--------------------------------------------------------------------
# Special settings for this manually set up instance
#--------------------------------------------------------------------
SCSID = <INR>
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
DIR_PROFILE = $(DIR_INSTANCE)/profile
DIR_CT_RUN = /usr/sap/$(SAPSYSTEMNAME)/SYS/exe/runU
SETENV_00 = PATH=$(DIR_INSTANCE)/exe:%(PATH)
SETENV_01 = LD_LIBRARY_PATH=$(DIR_EXECUTABLE)
_PF = $(DIR_PROFILE)/<SID>_ERS<INSTNR>_<[A]REPRELOC>
#-----------------------------------------------------------------------
# Copy SAP Executables
#-----------------------------------------------------------------------
_CPARG0 = list:$(DIR_EXECUTABLE)/ers.lst
Execute_00 = immediate $(DIR_EXECUTABLE)/sapcpe $(_CPARG0) pf=$(_PF)
#--------------------------------------------------------------------
# start enqueue replication server
#--------------------------------------------------------------------
_ER = er.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_01 = immediate rm -f $(_ER)
Execute_02 = local ln -s -f $(DIR_EXECUTABLE)/enrepserver $(_ER)
Start_Program_00 = local $(_ER) pf=$(_PF) NR=$(SCSID)
The DIR_CT_RUN in these profiles should equal the value of DIR_CT_RUN (if specified) or
DIR_EXECUTABLE from the [A]SCS instance profile. It is essential that the binaries from [A]SCS
and ERS instances are from the same binary set.
Make sure that the [A]SCS instances are not configured for automatic restart in the SAP profile.
HP-UX Configuration
A correct HP-UX configuration ensures that all cluster nodes provide the environment and system
configuration required to run SAP Application Server based business scenarios.
Several of the following steps must be repeated on each node. Record the steps completed for
each node as you complete them. This helps identify errors in the event of a malfunction later
in the integration process. The HP-UX configuration task is split into the following sections:
• Directory Structure Configuration—this section adds implementation practices to the
architectural decisions made in the chapter "Storage Layout Considerations." It gives some
guidance on how to achieve the differences in directory structure layout for a clustered SAP
system as compared to a standard installation.
NOTE: Most of these steps in this section are only performed once on the primary host.
• The primary host is where the SAP Instance was installed. If your database is currently
running on a machine different from this, the database vendor dependent steps will have
to be done on the host where the database was installed.
• Cluster Node Synchronization—there are a couple of changes to the operating system
configuration that were performed during SAP installation on the primary node. To allow
the system to run on other nodes, these changes need to be incorporated in the other cluster
nodes. This section also includes steps to distribute the changes of the directory structure
configuration performed in the section above.
HP-UX Configuration 49