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

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 plugins 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 16 (page 45) table provides a quick summary of the pros and cons of the methods and the
suggestions on when to use.
Table 16 Installing and configuring packages in SAP environment
ConsProsDescriptionMethod
This only works for some selected SAP installations
types. For example, SAP Central Instance
SGeSAP Easy
Deployment using
• limited to certain
configurations
• fully automatic
Serviceguard
package
installations. It provides an easy and fully automaticthe
• auto-discovery
code requires all
configuration file
generation, no
deployment of SGeSAP packages belonging to the
same SAP SID.
deploysappkgs
script
package relevant
manual intervention
required.
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.
file systems to be
mounted
• Can update
existing packages
with the attributes
necessary to
protect a SAP
instance or DB with
the package.
• no GUI
• can only be used
in phase 3
approach
-
• pre-filling plugin
requires all
package relevant
file systems to be
mounted for
auto-discovery
A web based graphical interface, with plugins 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
• user guided, GUI
based setup of
packages
• easy to reconfigure
the packages, if
required
• a basic validation
of entered data is
provided
• manual edits of
package attributes
can be
cumbersome and
error prone
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)
• every package
attribute can be
edited
• the package
configuration file
contains extensive
documentation
Serviceguard Manager GUI and Serviceguard CLI
For more information about the installation option 2: package creation using the Serviceguard
Manager GUI, see the respective online help available in the Serviceguard Manager GUI. For
more information about installation option 3: package creation using the Serviceguard Command
Line Interface (CLI), see the Managing HP Serviceguard A.11.20.10 for Linux manual at http://
www.hp.com/go/ linux-serviceguard-docs.
Overview 45