Stopping the IBM Security Guardium Key Lifecycle Manager server

To stop the IBM® Security Guardium® Key Lifecycle Manager server, stop the WebSphere® Application Server Liberty and then stop Db2®.

Before you begin

Ensure that you are the database instance owner on AIX® or Linux® systems, or the Local Administrator on Windows systems.

Important: It is recommended to run these commands as the database instance owner only. Running these commands as the root user might impact the permissions for the WAS_HOME directory. As a result, the WebSphere Liberty service might fail to start after a system restart. If you ran these commands as the root user, see Guardium Key Lifecycle Manager server stop, start, restart issues and resolutions to resolve the issue.

Procedure

Stop WebSphere Liberty.

Run the following command:

Windows

cd C:\Program Files\IBM\WebSphere\Liberty\bin
server.bat stop defaultServer

AIX or Linux

cd /opt/IBM/WebSphere/Liberty/bin
./stopServer.sh

Stop Db2.
Run the following command:
Windows
```
set DB2INSTANCE=KLMDB411
db2stop
```
AIX or Linux
```
su -KLMDB411
db2stop
```

Table 1. Topic change log
Date	Change description
06 January 2023	Corrected server start stop commands.
23 August 2022	Added a step to log in as the database instance owner and a note to resolve server not starting issue.
19 April 2022	Corrected the commands for stopping WebSphere Liberty on AIX or Linux.
07 Oct 2021	Corrected the commands for stopping the WebSphere Liberty server.
10 Sept 2021	Initial version.