HP Serviceguard Extension for SAP (SGeSAP) manual

This step assumes that the cluster as such is already configured and started. Please refer to the Managing Serviceguard user's guide if more details are required.

cmapplyconf -P ./sap.config

cmrunpkg -n <sap_installation_host> <package_name>

All virtual IP addresses should now be configured. A ping command should reveal that they respond to communication requests.

Preparation Step: IS1300

Before installing the SAP Application Server 7.0 some OS-specific parameters have to be adjusted.

Verify or modify HP-UX kernel parameters as recommended by the SAP Master Guide Part 1. Be sure to propagate changes to all nodes in the cluster.

The SAP Installer checks the OS parameter settings with a tool called "Prerequisite Checker" and stops the installer when the requirements are not met.

Check the installed Java SDK with the requirement as of the SAP Master Guide Part 1. Be sure to install the required SDK on all nodes in the cluster.

In case the J2EE engine uses security features that utilize the need for the Java Cryptographic Toolkit, it has to be downloaded both from the Sun website as well as from the SAP Service Marketplace.

Preparation Step: IS1320

Before invoking the SAP installer, some additional requirements have to be met that are described in the SAP installation documentation.

These are not specific to cluster implementations and apply to any SAP installation. They usually involve the setting of environment variables for SAPINST, like the DISPLAY variable, the temporary installation directory TMP, etc.

Installation Step: IS1330

The installation is done using the virtual IP provided by the Serviceguard package. SAPINST can be invoked with a special parameter called SAPINST_USE_HOSTNAME.

This prevents the installer routines from comparing the physical hostname with the virtual address and drawing wrong conclusions.

The installation of the entire SAP Application Server 7.0 will happen in several steps, depending on the installation type. Each time a different virtual hostname can be provided.

•First, the SAP System Central Services Component (SCS and/or ASCS) will be installed using the virtual IP contained in the corresponding Serviceguard package.

•Then, the database instance will be set up and installed on the relocatable IP address of the DB package.

•After that, the Central Instance and all required Dialog Instances are established. Virtual IPs can be used here, too. It is recommended to do this, because it preserves the flexibility to move instances

SAP Preparation 37