SAP Landscape Management 3.0, Enterprise Edition

Installing SAP Application Instances with Virtual Host Names on Windows

You can install the current software provisioning manager implementations directly on the virtual host name. No preparation and subsequent work regarding the host names is necessary.

Prerequisites

  • You have read the installation guide of the software provisioning manager, which is available with the Software Logistics Toolset.

  • You have downloaded the latest Support Package of the software provisioning manager.

Context

To install the central instance on a different host name as the database, it is important to use distributed installation. SAP Landscape Management can run different instances of an SAP application instances in different computing nodes. For this, the instances must get their own virtual host names. This requires at least two different virtual host names for the database and the central instance. (This is valid for ABAP only; Java Enterprise Edition has no central instance.)

The convention used in landscape virtualization management is as follows:

<instance type>[<no>]<SID>

Depending on the network setup (for example, user LAN, server LAN), more host names may be needed (for example, server, client network). In this case, a host name convention could be as follows:

<instance type>[<no>]<SID>[-network]

Procedure

  1. Start software provisioning manager to install the central instance using the virtual host name of the central instance as follows: sapinst SAPINST_USE_HOSTNAME=scs<SID>
  2. When you are asked for the database host during the installation routine, enter the virtual host name of the database.
  3. The installation routine also requires the path to the JRE or JDK implementation on the local host. This depends on the local implementation. We recommend putting the used Java package together with all other SAP application instance components on the storage system and mounting it to the directory that is created especially for this SID; see the following sample implementation.
    1. Create the following directory:

      /usr/lib/java_<SID>

    2. Copy the required Java components into the FS, together with all other components of the <SID>.

    3. Mount the Java components to the following directory:

      /usr/lib/java_<SID>

    4. When the installation routine asks for the JDK directory, enter the path /usr/lib/java_ <SID> .

      The software provisioning manager procedure sets all variables (for example, JAVA_HOME) for the user <SID>adm correctly when the entered JDK is used.

      If a JRE or JDK implementation is required by the SAP application, we recommend installing it on the local host manually or with the help of operating system (OS) deployment tools.

  4. Start software provisioning manager to install the database using the virtual host name of the database as follows: sapinst SAPINST_USE_HOSTNAME=db <SID>
    The installation routine sets all database-related configuration to the virtual host name of the database.
  5. Start software provisioning manager to install the central instance using the virtual host name of the central instance as follows: sapinst SAPINST_USE_HOSTNAME=ci <SID>
  6. Make sure that the following local groups are available on each node:
    1. SAP_LocalAdmin
      Members: <domain>\SAP_ <SID>_GlobalAdmin
    2. SAP_<SID>_LocalAdmin
      Members: <domain>\SAP_ <SID>_GlobalAdmin
  7. To create the groups and add the members, use the following commands:
    1. Net localgroup /add SAP_ <SID>_LocalAdmin
    1. Net localgroup SAP_ <SID>_LocalAdmin /add adaptive\SAP_ <SID>_GlobalAdmin