Managing HP Serviceguard Extension for SAP for Linux, December 2013

5.1.3 Installation options
Serviceguard and SGeSAP provide three different methods for installing and configuring packages
in an SAP environment.
1. SGeSAP Easy Deployment using the deploysappkgs script: This is applicable for some
selected SAP installations types. For example, SAP Central Instance installations. It provides
an easy and fully automatic deployment of SGeSAP packages belonging to the same SAP
SID.
2. A guided installation using the Serviceguard Manager GUI: A web based graphical interface,
with plug-ins for automatic pre-filling of SGeSAP package attributes based on the currently
installed SAP and DB instances.
3. The classical Command Line Interface (CLI): The commands cmmakepkg, cmcheckconf,
and cmapplyconf are used for creating a package configuration, checking the configuration,
and registering the package with the cluster.
Table 17 (page 52) table provides a quick summary of the pros and cons of the methods and the
suggestions on when to use.
Table 17 Installing and configuring packages in SAP environment
ConsProsDescriptionMethod
• limited to certain
configurations
• auto-discovery
code requires all
package relevant
file systems to be
mounted
• no GUI
• can only be used
in phase 3
approach
• fully automatic
Serviceguard
package
configuration file
generation, no
manual intervention
required.
• Can update
existing packages
with the attributes
necessary to
protect a SAP
instance or DB with
the package.
This only works for some selected SAP installations
types. For example, SAP Central Instance
installations. It provides an easy and fully automatic
deployment of SGeSAP packages belonging to the
same SAP SID.
NOTE: This method is useful only for:
• a fully automatic package configuration creation
with no manual intervention
• a SAP Central Instance and database
It assumes the SAP installation is complete and
therefore is only available in phase 3 approach.
For more information on deploysappkgs, see
manpages.
SGeSAP Easy
Deployment using
the
deploysappkgs
script
-
• pre-filling plugin
requires all
package relevant
file systems to be
mounted for
auto-discovery
• user guided, GUI
based setup of
packages
• easy to reconfigure
the packages, if
required
• a basic validation
of entered data is
provided
A web based graphical interface, with plug-ins for
automatic pre-filling of SGeSAP package attributes
based on the currently installed SAP and DB
instances.
NOTE:
• This method is useful for a guided and GUI
based package creation and registration of any
SAP configuration
• In Phase 1 approach, this method can be used
to setup a "base" package configuration before
installing SAP as well as a package
configuration after the SAP installation was
completed in phase 3 approach.
A guided
installation using
the Serviceguard
Manager GUI
• manual edits of
package attributes
can be
cumbersome and
error prone
• every package
attribute can be
edited
• the package
configuration file
contains extensive
documentation
The commands cmmakepkg, cmcheckconf, and
cmapplyconf are used for creating a package
configuration, checking the configuration, and
registering the package with the cluster.
NOTE: This method is useful for package setup
where every detail is required.
The classical
Command Line
Interface (CLI)
52 Clustering SAP Netweaver using SGeSAP packages