Modular Package Support in Serviceguard for Linux and ECM Toolkit

comment out the service part from the legacy package configuration file before using the

cmmigratepkg command.

b) Add the toolkit module to the new modular configuration file using "cmmakepkg -i -m [-t] "

option.

c) Modify TKIT_DIR and other toolkit specific parameters in the modular package conf file.

d) Apply the modular package configuration file.

4) Migration of modular packages that do not use toolkit modules.

a) The user has to comment out those invocations in the external script that shall start the

application server. For instance, if there is an invocation to start the Apache server in the

external script user has to comment that out. This is because the module scripts shall also

start the server. And toolkit usually throws an error if tried to start twice.

b) Add the toolkit module to the new modular configuration file using "cmmakepkg -i -m [-t] "

option.

c) Modify TKIT_DIR and other toolkit conf parameters in the modular package configuration

file.

d) Apply the modular package configuration file.

Combinational Packages with Serviceguard 11.18

When a user wants to package two applications together with Serviceguard 11.18 (i.e. two

applications in the same package) the common parameter names used by multiple toolkits such as

TKIT_DIR, MONITOR_INTERVAL, etc present a problem within the package configuration file. This

has been addressed in the Serviceguard 11.19 release using the namespace conflict resolution

feature.

For combinational packages with Serviceguard 11.18, it is recommended to treat the two

applications as two separate packages and make one package dependent on other.

To set up the combinational packages for Tomcat and Apache, set up modular packages for

Tomcat and Apache and edit all the required parameters. Then, set the dependency of apache

package on the Tomcat package. To do so, edit the dependency parameters in the package

configuration file of the Apache package as follows:

dependency_name <dep_name>

dependency_condition tomcat=up (tomcat is the name of the Tomcat package)

dependency_location same_node

This is done so that the Tomcat package should be running in order to start the Apache package

and during shutdown, if Tomcat package is halted, the Apache package will be brought down. The

user can set the dependency parameters in the Tomcat package instead of the Apache package if

they want the Apache package running first.

Priority for the Apache package should be less than the priority for the Tomcat package (or vice

versa in case the dependency parameters are edited in the Tomcat package with

dependency_condition apache=up).