Installing IBM Security Guardium Key Lifecycle Manager in silent mode

You can install IBM® Security Guardium® Key Lifecycle Manager in silent installation mode. This installation method is useful if you want identical installation configurations on multiple workstations. Silent installation requires a response file that defines the installation configuration.

Before you begin

  • Complete the planning tasks. See Planning the installation.
  • Download and extract the files for IBM Security Guardium Key Lifecycle Manager to a directory. These files are available for download from the IBM Passport Advantage® website. See Software download instructions.
  • Review the considerations and restrictions for installing and configuring IBM Security Guardium Key Lifecycle Manager. See Installation guidelines.
  • IBM Security Guardium Key Lifecycle Manager includes sample response files that you can use as a template for creating your own response file. Modify the sample file for the specifics of your environment before it can be used.

    The response files are available in the root directory of the installation image files.

    Note: You can change the installation locations (installLocation parameter in the response file) of the package groups. Ensure that the non-administrator or non-root user account has access to the locations that you specify.


  1. Edit the repository location information and other details in the response file. The sample response files are in the directory in which your installation package is located.
    Note: If you enter an invalid value for the full_path_to_response_file parameter, such as an incomplete path, the installation program exits. No error message is displayed or logged.
    You must update the response file with the correct repository location. The repository location is the place where your installation package is located.
    <repository location='<user repository location>\im'/>
    <repository location='<user repository location>\'/>
    If you extracted the installation package in C:\gklm42, update repository location in the SKLM_install_Win_Resp.xml response file as shown in the following example.
    <repository location='C:\gklm42\disk1\im'/>
    <repository location='C:\gklm42\disk1\'/>
  2. To add the encrypted passwords to the relevant elements of the response file, use the IBM Installation Manager utility to create encrypted passwords.

    For information about password encryption, see Encrypted password for response file elements.

  3. (Optional) To use an existing copy of Db2® Standard Edition, update the data element in the response file.
    <data key='user.DB2_EXISTS,' value='true'/>
    <data key='user.DB2_LOCATION,' value='DB_HOME'/>
    Where, DB_HOME is the directory that contains the existing Db2 application. For more information, see Definitions for HOME and other directory variables.
    Note: Ensure that the existing copy of Db2 is at the correct version. For more information, see On Linux® systems, if the Db2 version is correct and the installation fails, see Installation with existing copy of Db2 fails on Linux systems.
  4. Open a command prompt and run the silent installation command.
    Go to the <installation package directory>\disk1 directory and run the following command.
    silent_install.bat SKLM_Silent_Win_Resp.xml -acceptLicense
    Go to the <installation package directory>/disk1 directory and run the following command. SKLM_Silent_Linux_Resp.xml -acceptLicense
  5. Verify that the installation was successful by reviewing the log files. You can view the Installation Manager logs at the following locations.

    For example, C:\ProgramData\IBM\Installation Manager\logs\native.


    For example, C:\ProgramData\IBM\Installation Manager\logs\sklmLogs\.


    For example, /var/ibm/installationManager/logs/native.


    For example, /var/ibm/InstallationManager/logs/sklmLogs/.

    For the definition of IM_DATA_DIR, see Definitions for HOME and other directory variables.

What to do next

Before you use IBM Security Guardium Key Lifecycle Manager, run the postinstallation tasks that are described in Postinstallation tasks.
Table 1. Topic change log
Date Change description
15 May 2023 Corrected the Db2 edition.
07 March 2023 Initial version.