HP Serviceguard Extension for SAP (SGeSAP) manual HP-UX Configuration

#-----------------------------------------------------------------------

_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 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 on which 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. In order to allow the system to run on other nodes, these changes need to be made to other cluster nodes, too. This section also includes steps to distribute the changes of the directory structure configuration performed in the section above.

• NOTE: Repeat the cluster node synchronization steps for each node of the cluster that is different than the primary.

•Cluster Node Configuration - This section consists of steps performed on all the cluster nodes, regardless if the node is a primary node or a backup node.

•NOTE: Repeat the cluster node configuration steps for each node of the cluster.

•External Application Server Host Configuration - This section consists of steps performed on any host outside of the cluster that runs another ABAP instance of the SAP system.

NOTE: Repeat this section for each host that has an external application server installed

Performing some of the iterations in parallel is fine. Use caution in any complex setup situation.

Rather than using the cut and paste mechanism you can also fill out the tables provided by first analyzing the primary host(s). Afterwards you can use the tables to synchronize all nodes.

HP-UX Configuration 45