Managing HP Serviceguard Extension for SAP for Linux (May 2013)

SGeSAP easy deployment
This section describes the installation and configuration of packages using easy deployment (via
the deploysappkgs command, which is part of the SGeSAP product) .
This script allows easy deployment of the packages that are necessary to protect the critical SAP
components. The components that can be deployed into one or more packages are:
• System Central Services (SCS or ASCS)
• Central Instance (DVEBMGS) (if no ASCS is configured)
• Enqueue Replication Services (Both ERS for Java and ABAP)
• Database Instance
The NFS exports that are necessary to operate this environment are not part of this version of easy
deployment, and must be configured separately (for example, in the Phase 1 approach).
The SGeSAP easy deployment is invoked through command line by using the deploysappkgs
packaging-option SAPSID with the packaging-option being either the multi (multiple
packages) or the combi (combined packages) and the SAPSID being the SAP SID for which the
packages are created.
The multiple packages is the default and recommended option. This allows the distribution of
non-redundant SAP components into multiple, separate packages. It is a very flexible option, as
the individual components can failover independently, and unlike combined packages, failure of
one component does not bring down the other components. Thus "failover dependencies" can be
avoided.
The combined packages option allows the combining of the non-redundant SAP components of a
SAP system in as few packages as possible. This keeps the setup simple and can save resources.
With this option, a package initiates a failover, even if only one of the configured SAP components
configured in the package fails.
Easy deployment generates (or updates) one or more package configurations. These must be
reviewed before they are applied. The screen output reports the filename of the generated
configuration files as well as a detailed log of each step performed during generating the package
configuration.
Table 18 SGeSAP use cases for easy package deployment
ScenarioUse case
SAP instances and DB are installed. Instances and DB can be
running or can be halted. They are not configured into a SGeSAP
package yet. Easy deployment will create new packages.
Create packages from scratch
Before setting up SAP, minimal package(s) with required volume
groups and IP addresses have been created and started. No
Extend "base packages"
SGeSAP configuration has been added yet. After setting up SAP
this/these package(s) must be extended with SGeSAP related
attributes including installed instances and/or DB.
For example:Add a new SAP instance to an already configured
package
A newly installed ASCS must be part of the existing SCS package.
Easy deployment will add such an ASCS into the existing package,
if it is configured to the same virtual host as the SCS or if option
"combined" is selected.
For example:Update existing package with additionally
required resources
A new volume group related to a SAP instance must be added.
IPv6 is enabled and the virtual hostname now also has an IPv6
address which must be added. Easy deployment discovers these
new attributes and add them to the appropriate existing SGeSAP
packages.
46 Clustering SAP using SGeSAP packages