Managing HP Serviceguard Extension for SAP for Linux, December 2013

5.5 Completing SGeSAP package creation (Phase 3b)
The three options for creating the final SGeSAP package are as follows:
Easy deployment with deploysappkgs command.
Guided configuration using Serviceguard Manager.
Package creation with the CLI interface using the cmmakepkg and cmapplyconf command.
Creating SGeSAP package with easy deployment
To create the packages with the deploysappkgs command run:
deploysappkgs combi C11
or
deploysappkgs multi C11
This command attempts to create either a minimal (combi = combine instances) or a maximum
(multi = multiple instances) number of packages. If suitable base packages are already created in
Phase 1, it extends those packages with the necessary attributes found for the installed C11 instance.
If necessary, the configuration file for the enqor multi-node package is also created. You must
review the resulting configuration files before applying them. Depending on the attributes changed
or added, cmapplyconf command might fail, and stop running packages.
NOTE:
To get complete package configurations it is recommend that SAP database and instances
are running on the node where deploysappkgs is invoked. Otherwise, attributes (especially
regarding the filesystem and volume_group module) might be missing.
deploysappkgs can also be invoked at the end of Phase2 on the primary node. However,
the created package configurations cannot be applied yet.
5.5.1 Creating SGeSAP package with guided configuration using Serviceguard
Manager
NOTE: To create a package you can use either Serviceguard Manager GUI or the CLI. This
section describes GUI steps and the CLI steps are described in the “Creating SGeSAP package
with CLI” (page 73) section.
1. Startup the Serviceguard Manager and add the SGeSAP modules to the existing base
packages, if they are not added in Phase 1.
2. Update the SGeSAP attributes with the current values, if the SGeSAP modules are already
added in Phase 1.
5.5.2 Creating SGeSAP package with CLI
NOTE: To create a package you can use either Serviceguard Manager GUI or the CLI. This
section describes CLI steps and the GUI steps are described in the “Creating SGeSAP package
with guided configuration using Serviceguard Manager (page 73) section.
The SGeSAP configuration must be added to the Serviceguard “base packages created earlier,
if they are not added in Phase 1.
An example for adding or updating the package using the command line is as follows:
1. Run the mv <pkg>.config<pkg>.config.SAVE command to add sapinstance module
to an existing package.
2. Run the cmmakepkg m sgesap/sapinstance -i <pkg>.config.SAVE
<pkg>.config command
5.5 Completing SGeSAP package creation (Phase 3b) 73