Restarting the IBM Security Key Lifecycle Manager server

Restart of the server causes the server to read its configuration and accept the configuration changes, if any. To restart the IBM Security Key Lifecycle Manager server, you can run the server restart scripts, REST service, or use the graphical user interface.

1. Go to the appropriate page or directory.

   Graphical user interface

   1. Log on to the graphical user interface.
   2. On the welcome page header bar, click the <IBM Security Key Lifecycle Manager User> link. For example, click the SKLMAdmin link.

   Server restart scripts

   1. Go to the <WAS_HOME>\bin directory.

      Windows

      C:\Program Files\IBM\WebSphere\AppServer\bin

      Linux

      /opt/IBM/WebSphere/AppServer/bin

   REST interface

   Open a REST client.

2. Restart the server.

   Graphical user interface

   1. Click Restart Server.
   2. Click OK.

   Note: The IBM Security Key Lifecycle Manager server is unavailable for a few minutes while the restart operation is in progress.

   Server restart scripts

   1. Stop the server.

      Windows

      stopServer.bat server1

      Linux

      ./stopServer.sh server1

      Global security is enabled by default. Enter the user ID and password of the WebSphere® Application Server administrator as parameters to the stopServer script. The script prompts for these parameters when they are omitted, but you can specify them on the command line:

      Windows

      stopServer.bat server1 -username wasadmin -password mypwd

      Linux

      ./stopServer.sh server1  -username wasadmin -password mypwd

   2. Start the server.

      Windows

      startServer.bat server1

      Linux

      ./startServer.sh server1 

   REST interface

   1. Obtain a unique user authentication identifier to access IBM Security Key Lifecycle Manager REST services. For more information about the authentication process, see Authentication process for REST services.
   2. To run Restart Server REST Service, send the HTTP POST request. Pass the user authentication identifier that you obtained in Step a along with the request message as shown in the following example.

      POST https://localhost:<port>/SKLM/rest/v1/ckms/servermanagement/restartServer 
      Content-Type: application/json
      Accept: application/json
      Authorization: SKLMAuth userAuthId=139aeh34567m