Starting and stopping instances

Starting and stopping instances is part of regular operations.

Start an 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 the instance path and instance ID were defined in Starting the first cluster instance.

IBM® Safer Payments starts. You must enter the SSL certificate password when you are prompted.

Each 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. For more information about key entry and activation, see Activating a keygen master key or Activating a KMIP master key.

Stop an instance

To stop an instance, you can use a SIGTERM command. IBM 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 IBM Safer Payments process, you can use the SIGKILL signal. Use the SIGKILL signal if IBM Safer Payments does not properly shut down after a SIGTERM command.

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