Migrating packages from legacy to modular style

23
5. Run cmcheckconf on the new package ASCII file and resolve if there are any errors.
6. Halt the Package.
7. Apply the new package ASCII file.
Migration utility for Serviceguard toolkits and CFS packages
cmeasymigrate creates modular package configuration file for legacy style toolkit packages and/or consolidate multiple
CFS packages into a single modular package configuration file. This utility is supported only in HP-UX.
The syntax is as follows:
cmeasymigrate [legacy_package_name] [-c cfs_package_name[:cfs_package_name...]]
[-o output_directory] [-t]
cmeasymigrate accepts a toolkit legacy package for generating the modular package configuration files. The modular
package configuration files are also generated for any dependent packages (toolkit or CFS) that the specified toolkit
package may have. Default migration type for dependent legacy CFS packages is 1:1.
cmeasymigrate identifies the toolkit type of the legacy package specified, includes the appropriate modules and
generates the modular configuration file. It copies the package attributes from legacy package configuration to the
generated modular package configuration file.
The control script's customer-defined area is any code between “#START CUSTOMER DEFINED FUNCTIONS” and
“#END CUSTOMER DEFINED FUNCTION”. If the customer-defined area has code that needs to be migrated to the
modular package, then cmeasymigrate creates an external script by inserting the shell code from the control
script into the external_script file. The external script is generated from the external template found in
$SGCONF/examples/external_script.template.
The external script file will be copied on the nodes where the package is configured to run and it is ensured that the
permissions are set to 744, and owned by root. The external_script is placed in the toolkit package directory, i.e.,
/etc/cmcluster/<pkg_name>_MODULAR.
cmeasymigrate can be used to consolidate multiple legacy or modular CFS packages into a single modular package.
Either toolkit package name or CFS package names or both can be specified, but one of them is mandatory.
The logs for cmeasymigrate command are placed in /var/adm/cmcluster/cmeasymigrate/cmeasymigrate.log.
cmeasymigrate supports migration of toolkit legacy packages and CFS Mount point and Disk group packages in a
Metrocluster environment.
Note: It is recommended to use cmeasymigrate(1m) over cmmigratepkg(1m) to migrate legacy Serviceguard toolkit packages and its
dependent packages.
Supported toolkits
Toolkits Description
Serviceguard extension for RAC (SGeRAC) Toolkits—(asm, crs,
and rac)
SGeRAC toolkit legacy packages created by using 11.17 and
later version of SGeRAC can be migrated.
Enterprise Cluster Master Toolkit (ECMT)—(IBM DB2, Samba,
Tomcat, Apache, Mysql, and Oracle RDBMS)
• Sybase and EnterpriseDB toolkits don’t have legacy support.
So it is not listed.
• cmeasymigrate supports the migration of an ECMT package
that contains both Tomcat and Apache in a single package.
Software requirement
• cmeasymigrate is supported in Serviceguard A.11.20 patch PHSS_42558.
• To migrate or consolidate CVM disk group and CFS mount point packages using cmeasymigrate command Cluster File
System A.11.20.00 patch PHSS_42136 must be installed.
• ECMT toolkits should have minimum version of B.05.00 installed to use cmeasymigrate.
• SGeRAC toolkits should have minimum A.11.20 version of Serviceguard extension of RAC installed to use
cmeasymigrate feature.