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

Adding Additional SAP Systems to SGeSAP cluster

Both packaging options will prefer to add a SAP instance to an already existing package instead of creating a new

package under certain conditions. This will happen in case an already existing package has resources configured on

which the SAP instance depends.

Example for such a situation is if a SAP Instance is installed on a virtual hostname that resolves to a relocatable

IP address of an existing package. An addition of the Instance to the existing package will be suggested with both

packaging options.

This behavior is useful to simplify SAP installations with HA option: Serviceguard packages should be manually

created and started with relocatable IP address settings first. As a second step, the SAP installer will be invoked for all

required Instances specifying these addresses. Afterwards, Easy Deployment can be used to quickly add the

previously installed SAP instances to the packages.

Synchronize SGeSAP packages to changes in Network Settings and Storage Layout

When you change the network or storage layout of a SAP System, it is mandatory to synchronize the corresponding

SGeSAP packages with the changes. Using Easy Deployment for SGeSAP you can synchronize the corresponding

SGeSAP packages easily. From Serviceguard Manager home page, click on [Configuration] -> [Package Easy

Deployment] -> [SGeSAP Package(s)] menu toolbar. On the “Deploy SGeSAP Packages” screen (figure 21) select the

SAP System ID whose network and/or Storage layout has changed. This will generate a new configuration file with

the latest network and/or storage layout. When you click [APPLY] on the “Easy Deployment Operations Log” screen

(figure 14), the existing SGeSAP package will be reconfigured with the latest network and/or storage layout.

For example, if IPv6 became enabled and the virtual hostnames that SAP uses now also have an IPv6 address,

Easy Deployment will modify the existing package configurations to include the IPv6 address.

The configuration file(s) in the Easy Deployment Operations Log screen will not be available for editing if the

package(s) of the generated ASCII file(s) exists in the cluster and the configuration is up-to-date. An information note is

displayed mentioning: “For the selected SAP System ID <ID>, the package configuration is up-to-date. Hence no

update/change is required.”

Limitations

The Easy Deployment feature for the SGeSAP package supports only modular-style packaging.

Easy Deployment feature for SGeSAP cannot be used:

• To create clusters for SAP software that could also be installed in a redundant way, including Dialog Instances,

Java instances and Web dispatcher instances

• in multi-instance database environments, for example, Oracle RAC configurations

• To create cross subnet package configurations

• To create Metrocluster or cluster filesystem-based configurations