Modular Package Support in Serviceguard for Linux and ECM Toolkit

5
modules to the package configuration file. The modified package configuration then needs to be re-
applied.
The sequence of operations for modifying the package is:
1) #cmmakepkg –i pkg_old.conf –m <module> pkg_new.conf
This command adds a module, if required, to the already existing package configuration file
pkg_old.conf and creates a new package configuration file pkg_new.conf. The module added can
be any supported module such as a Serviceguard module or another toolkit module. Reconfigure
the package configuration file appropriately.
If the toolkit configuration file is updated after the package configuration file is created, then the
package configuration file has to be updated by issuing the following command.
#cmmakepkg –i pkg_old.conf –m <module> –t toolkit.conf pkg_new.conf
In addition to adding the package parameters, this command extracts the toolkit parameter values
from the toolkit.conf file and updates the pkg_new.conf file with these values. Modify the values of
existing attributes of the package conf file, if required.
Note:
In the case of Oracle, Samba and PostgreSQL toolkits, the toolkit configuration file has parameters
that are in turn being used by other parameters in the same file. It is the responsibility of the user to
ensure that the changes done to these parameters are reflected in the modular package
configuration file on a cmmakepkg –i –m –t file and in the toolkit configuration file on a
cmapplyconf. One such example in the Oracle toolkit is the PFILE parameter which by default is set
to ${ORACLE_HOME}/dbs/init${SID_NAME}.ora where ORACLE_HOME and SID_NAME are
other parameters in the Oracle toolkit. Hence if ORACLE_HOME or SID_NAME are changed in the
toolkit configuration file, and then the package configuration file is modified to incorporate these
changes using a cmmakepkg –i –m –t, then change the value of PFILE in the package configuration
file to reflect the new value of ORACLE_HOME or SID_NAME (if required).
2) #cmapplyconf –P pkg_new.conf
New package configuration is applied. This completes the migration of legacy toolkit to modular
toolkit.
After putting the package in Toolkit Maintenance mode
This is the mode supported by the existing toolkit scripts. Kindly refer to the toolkit README file for
more information on this mode. With Serviceguard 11.19, the package can be put in maintenance
mode provided by Serviceguard. The Serviceguard package maintenance mode is described in the
11.19 features section of this document.
Migration from legacy to modular packages
Migration tools have been provided by Serviceguard to migrate legacy packages to modular
packages. The migration can be done in following steps: