Skip to Content

Installation in SAP HANA SPS 07 – welcoming hdblcm(gui) to the family

December 9, 2013 | 1,073 Views |
 documentationhanainstallation serverkmlcmsap hana
Follow

In only a few short support stack (SPS) releases, the SAP HANA lifecycle management tool set has drastically grown to encompass a plethora of tools and features, including: installation, configuration, and update. Prior to the most recent SPS 07 release of SAP HANA, the unified installer was the tool available to streamline server and component installation, all at one fell swoop. For a straight-forward installation, the unified installer was a worthy installation tool, however when the need to customize individual components arose, the unified installer offered less than optimal flexibility.

Enter hdblcm(gui). The successor to the unified installer doesn’t have a snazzy name, but what it lacks in pomp and circumstance, it more than makes up for in functionality. The new SPS 07 installation tool is actually a pair of installation tools – hdblcm for CLI and hdblcmgui for GUI – which provides a unified interface to reduce installation complexity, but offers the flexibility to mix and match components and versions. They are positioned as part of the SAP HANA lifecycle management tools family, which includes seasoned favorites such as the SAP HANA lifecycle manager (HLM), hdbinst, and hdbsetup.

The introduction of hdblcm(gui) offers several advantages:

  • Component-wise installation – Individual components (SAP HANA: studio, DB, client, HLM, host agent, AFL, LCApps) can be installed or updated in combination with the server from a single interface. Likewise, all components can be installed at one time.
  • Improved configuration file – A plain text configuration file template with parameters set to their defaults can be generated and edited to be called
    during installation or update.
  • Improved interactive installation – Both as a graphical interface, by calling hdblcmgui from the command line, or as command line installation, with iteratively requested parameter entry.
  • Improved batch processing – Installation and update tasks can be called using command line options or the configuration file, without any additional input required.
  • Multi-host system installation from the graphical interface – It is now possible to install a multi-host SAP HANA system from the graphical interface. Multi-host storage and grouping options can also be configured.

  SAP HANA lifecycle management tool hdblcmgui

Both the hdblcm and hdblcmgui SAP HANA lifecycle management tools can be used to install an SAP HANA system in one of the installer modes, and with a combination of parameter specification methods.

Installer modes

Installation can be performed in one of the following modes:

  • Interactive mode (default) – Available for hdblcm or hdblcmgui. The person installing the system must enter parameter specifications iteratively until the installation process finishes.
  • Batch mode – Available for hdblcm. The installation accepts the default values for all unspecified parameters, and runs to completion without any additional input required.

Parameter specification methods

Installation parameter values can be entered in one or more of the following methods:

  • Interactively (default) – Using either command line interaction (hdblcm) or graphical interaction (hdblcmgui), most parameters are requested interactively.
  • Command line options – Installation parameters are given in their accepted syntax as a space delimited list after the program name (hdblcm or hdblcmgui).
  • Configuration file – The configuration file is a plain text file, of parameters set to their default values, that can be generated, edited, and saved to be called during installation with either the hdblcm or hdblcmgui tool.

/wp-content/uploads/2013/12/configfile_339540.png

More information

SAP HANA server installation

SAP HANA configuration

SAP HANA update

To report this post you need to login first.

14 Comments

You must be Logged on to comment or reply to a post.

    1. Stephanie Lewellen
      Post author

      Hi Pieter,

      To me this looks like a problem with sudo, since it doesn’t look like you are being asked for the root password, which would usually happen before hdblcm is executed. Could the shell for root be set incorrectly?

      Best regards,

      Stephanie

      (0) 
      1. Former Member

        I solved it, now a new error is showed with message: ‘No installation kit in map #/install.’

        Dit you have this problem ? How was the upgrade ?

        Regards,

        Pieter

        (0) 
        1. Stephanie Lewellen
          Post author

          Hi Pieter,

          I haven’t personally run into this problem, and it’s difficult for me to give advice without knowing more about your update situation. Can you provide more details? Alternatively, your questions can get more traffic if you open a new question post. That would probably be the quickest way to get feedback.

          Best regards,
          Stephanie

          (0) 
    1. Stephanie Lewellen
      Post author

      Hi Deeru,

      Have you referred to the SAP HANA Server Installation Guide, in particular, the Multi-Host System Installation section? That documentation should be a starting point for building a distributed system from scratch.

      Best regards,
      Stephanie

      (0) 
      1. Stephanie Lewellen
        Post author

        Hi Denys,

        The way you describe is the recommended installation method if you have an existing SAP HANA system, and you want to add more hosts to the system. But, if you want to install a new SAP HANA system with multiple hosts, this can be performed in one step with the new LCM tool hdblcm(gui). The multiple-host (distributed) system can be installed both on command line (using the –addhosts parameter) or in the graphical interface.

        Best regards,

        Stephanie

        (0) 
  6. Ning Tong

    Hello Stephanie,

    Thanks for sharing.

    During installation (your first picture), hana1 is public or internal hostname?

    We should use internal hostname when input, right?

    Thanks & Best Regards,

    Tong Ning

    (0) 

Leave a Reply