Using Easy Deployment in Serviceguard and Metrocluster environments on HP-UX 11i v3 - (March 2012)

The user is expected to input the applications tier base directory path (directory where instance specific installations

are done) and the Oracle Database SID, and click the [Prepare] button on the screen to trigger the generation of

required package configuration files for the SGeEBS applications tier toolkit package deployment.

The generated package configuration file for the SGeEBS applications tier toolkit package deployment will be

displayed for the user’s review. The user can edit the configuration file. To complete the SGeEBS applications tier

toolkit package deployment, the user needs to click on the [Apply] button in the same screen showing the

configuration file.

Parameter discovery and default parameters

By way of automatic package parameter discovery by the SGeEBS Easy Deployment operation, the following

package attributes are automatically populated in the SGeEBS Applications Tier Toolkit package configuration file:

• Package name

• Toolkit directory name

• Service names

• Web entry IP

• Volume group, LVM, mount point, and file system

If a separate storage has been used for EBS instance-specific and application tier stack file system, then the storage

information will be populated appropriately in the package configuration.

All other package parameters will be set to default values.

Error and exception handling

An error message will appear in the Serviceguard Manager package Easy Deployment operation log window, if the

SGeEBS package Easy Deployment operation fails for one or more of the following reasons:

• The package directory that the operation is trying to create for the package already exists.

• An unexpected error occurs during the SGeEBS applications package deployment operation.

Limitations

The Easy Deployment feature for the SGeEBS applications tier toolkit package supports only modular style of

packaging.

Easy Deployment of a Site Controller package

Introduction

The configuration of a Site Controller package is a multi-step process that requires editing multiple package

configurations. The following are the steps required to configure a Site Controller package manually.

1. Selecting the appropriate Metrocluster module while creating the Site Controller package configuration.

Ex. cmmakepkg –m dts/sc –m dts/mcxpca <pkg_name>.conf

2. Applying the empty Site Controller package configuration file with the site and node information.

3. Editing the root-most complex workload packages’ configuration and inserting the resource dependency for site

safety latch

4. Re-applying the edited complex workload packages’ configuration

5. Editing the Site Controller package configuration and entering the complex workload package information and

the Metrocluster module parameters values

6. Re-applying the edited Site Controller configuration

Please refer to the chapter on “Designing a disaster recovery solution using site-aware disaster-tolerant architecture”

in the latest version of the Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, available