Other information to gather

You must run several actions that might provide more information to verify installation.

  • Check your free disk space. For more information, see the technote: IBM Security Guardium Key Lifecycle Manager Support Matrix
  • See whether the Db2 instance is created. If so, this validates the Db2 installation.
    To verify that the Db2 instance was created, log in as the IBM Security Guardium Key Lifecycle Manager Db2 instance owner, go to the DB_INSTANCE_HOME directory, and run:
    db2ilist
    A list of the configured instances is displayed. The instance name for IBM Security Guardium Key Lifecycle Manager such as KLMDB421 is typically in the list.
  • Start and stop the IBM Security Guardium Key Lifecycle Manager database server by using the instance owner user ID. This validates the database creation.

    To start and stop the database, log in as the IBM Security Guardium Key Lifecycle Manager Db2 instance owner, go to the DB_INSTANCE_HOME directory, and run the db2start and db2stop commands on the database.

  • Display a list of the tables in the Db2 database. This validates the Dynamic Data Language process.
    To display the list of tables, log in as the IBM Security Guardium Key Lifecycle Manager Db2 instance owner, go to the DB_INSTANCE_HOME directory, and run these commands:
    db2 connect to sklm_database user sklm_instance_owner_userid \
    using sklm_instance_owner_passwd
    
    db2 list tables
    
    db2 describe table table_name
  • Determine whether the Java™ process for WebSphere Application Server is running. A running process validates the WebSphere Application Server installation.
    To determine whether the Java process is running, stop and restart the server by going to the WAS_HOME/bin directory and running these commands:
    ./server.sh stop server1
    ./server.sh start server1
    If global security is enabled, add these parameters to the commands to stop and restart your server:
    		-username was_admin_id -password was_admin_passwd

    On Windows systems, you can also open the Windows Services console and verify that the service for the KLMProfile is started.

  • Start the IBM Security Guardium Key Lifecycle Manager application to validate the IBM Security Guardium Key Lifecycle Manager installation and the overall installation.

    To start the IBM Security Guardium Key Lifecycle Manager application, start the WebSphere Application Server, and look for the IBM Security Guardium Key Lifecycle Manager task.

Table 1. Topic change log
Date Change description
19 April 2022 Corrected the commands for stopping and starting WebSphere Liberty.
10 Sept 2021 Initial version.