IBM Security Key Lifecycle Manager, Version 3.0

Installing IBM Security Key Lifecycle Manager in silent mode

You can install IBM Security 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

  • Download and extract the files for IBM Security Key Lifecycle Manager to a directory. These files are available for download from the IBM Passport Advantage website. See the Installation images and fix packs topic for details.
  • Review the Installation guidelines topic to know the considerations and restrictions for installing and configuring IBM Security Key Lifecycle Manager.
  • Review the Planning the installation topic to understand the requirements.
  • IBM Security Key Lifecycle Manager includes sample response files that you can use as a template for creating your own response file. The sample response files are in the directory in which your installation package is located. Modify the sample file for the specifics of your environment before it can be used.

About this task

Before installation, you must also read and agree to the license terms for this product. To locate the response files and license term files, look in the root directory of the installation image files. The/license subdirectory has the license files in text format.

Installation fails unless you take these steps.

In the response file, make following changes to the line that specifies the license:
  • Set the default value to true to indicate that you agree with the terms of the license.
  • Uncomment the line by removing the pound sign (#) character at the beginning of the line.

Procedure

  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 have extracted the installation package in C:\sklm27, update repository location in the SKLM_install_Win_Resp.xml response file as shown in the following example.
    <repository location='<C:\sklm27\disk1\im'>\im'/>
    <repository location='<C:\sklm27\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 how to encrypt the password, see Encrypted password for response file elements.

  3. Open a command prompt and run the silent installation command.
    Windows
    Go to the <installation package directory>\disk1 directory and run the following command.
    silent_install.bat SKLM_Silent_Win_Resp.xml
    Linux
    Go to the <installation package directory>/disk1 directory and run the following command.
    silent_install.sh SKLM_Silent_Linux_Resp.xml
  4. Verify that the installation was successful by reviewing the log files. You can view the Installation Manager logs at the following locations.
    Windows
    drive:\<IM_DATA_DIR>\logs\native.

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

    drive:\<IM_DATA_DIR>\logs\sklmLogs\.

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

    Linux
    /<IM_DATA_DIR>/logs/native.

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

    /<IM_DATA_DIR>/logs/sklmLogs/.

    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 Key Lifecycle Manager, run the postinstallation tasks that are described in Postinstallation steps.