EKM Service Management

The CORE service bears the name (EKMEnterprise Key Management - previous name of the product.) from the days the product name was Enterprise Key Management (EKMEnterprise Key Management - previous name of the product.).

Note
For CORE servers running in FIPS modeUKC system mode that allows processing FIPS-certified and not-certified keys, see EKM Service Management in FIPS.

Note
For CORE servers running in user mode, see Service Control in the Sudo-less Installation.

EKM Service Management

To start, stop, restart the EKMEnterprise Key Management - previous name of the product. Service, and check its status - use the following OS-specific commands.

Ping EKM Service

To check CORE service status without CORE credentials, use the following CURL command with the --insecure option to bypass certificate validation.

• Linux:

  curl --insecure -X GET "https://ep1[:<port>]/api/v1/health" -H "accept: application/json"

• Windows:

  C:\Windows\System32\curl.exe --insecure -X GET "https://ep1[:<port>]/api/v1/health" -H "accept: application/json"

If everything is in order, this command terminates without output.

Examples of errors:

• If the Partner is not operational, the response is

{"message":"error code {COMMUNICATION_ERROR}, message {System is not healthy}"}

• If the EP is not operational, the response is

curl: (7) Failed to connect to 192.168.0.102 port 443: Connection refused

Terminate EKM Process

• Linux:

  ps -aux | grep ekm
  kill -9 <ekm process number>

• Windows:

  • Open Task Manager ˃ Processes
  • Search for the Java and the ekmsvc tasks.
  • If found, click the End task button.