Start and stop Safer Payments instances

This topic describes how to start and stop Safer Payments during regular operation.

Start a Safer Payments instance

Open a console window on the server and run:
iris console id=i
from /instancePath/cfg.
  • The console parameter activates event log message output on the console window.
  • /instancePath is the path where you want the instance configuration to be stored.
  • The parameter i is the ID of the instance that you want to start.
    Note: Both home directory and instance ID have been defined in Start the first Safer Payments instance.

Safer Payments now starts up. You must enter the SSL certificate password when you are prompted.

Each Safer Payments instance now attempts to fetch the password for the encryption keys from its sister instances. If no other instances are running yet, the encryption keys must also be entered before full operation can start. See Activate keys for details on key entry and activation.

Stop a Safer Payments instance

To stop Safer Payments, you can use a SIGTERM command. Safer Payments catches SIGTERM signals and performs a clean shutdown, similar to the API shutdown command.

Open a console window on the server and run:
killall iris

To immediately stop a Safer Payments process, you can use the SIGKILL signal. Only use the SIGKILL signal, if Safer Payments does not properly shut down after a SIGTERM command:

Open a console window on the server and run:
killall -9 iris