Managing Serviceguard Extension for SAP Version A.06.00 for Linux, December 2012

For examples of these attributes, see “Creating NFS toolkit package using Serviceguard CLI”
(page 51) section.
2. Verify the package using the cmcheckconf –P <pkg> .config command, and if there
are no errors, run the cmapplyconf –P <pkg>.config command to apply the
configuration.
Verification steps
A simple verification of the newly created base package is to test if the package startup succeeds
on each cluster node where it is configured.
SAP installation (Phase 2)
This section provides information for installing SAP into a Serviceguard cluster environment. For
more information, see SAP installation guides.
SAP instances are normally installed on one dedicated node, (referred to as <primary>). In Phase
3, the changes from the SAP installation on the <primary> node must be distributed to the other
nodes in the cluster (referred to as <secondary> nodes) intended to run the SAP instance. Once
the SAP instance is clustered, there is no concept of <primary> and <secondary> node anymore
and all the nodes provides an identical environment.
Prerequisite
• The sapnfs package must be running on one of the nodes in the cluster and is exporting the
relevant NFS files systems.
• The automount subsystem must be running and the NFS client file systems are available.
• A SGeSAP base package(s) for the SAP instances installation must be running on the <primary>
node.
For example, the primary node is the node, where the sapinst tool (now known as Software
Provisioning Manger) is executed to start the installation.
Determine the SAP instance number(s) to be used for the installation and verify they are unique
in the cluster.
Installation of SAP instances
The SAP instances and database are installed with the SAP sapinst tool.
Use either of the following commands to specify the virtual hostname, where the instances are to
be attached:
Run export SAPINST_USE_HOSTNAME=<virtual host> before running sapinst , or add
the virtual hostname to the command line
sapinst … SAPINST_USE_HOSTNAME=<virtual host>.
The sapinst tool offers various installation types. The type of installation determines the way instances
and the database are installed and the flexibility of the setup. The three installation types offered
are:
• Central system
• Distribute system
• High-Availability system
NOTE: While all three installation types can be clustered, the recommended installation type is
HA system. The HA option is available for all the Netweaver 7.x versions. After completing the
installation, the SAP system must be up and running on the local (primary) node.
For more information on the installation types, see the SAP installation guides.
58 Clustering SAP using SGeSAP packages