Windows operator guide

Startup / Shutdown console

Start Soffid IAM console

To start Soffid console, use service manager, or execute:

systemctlnet start soffid-iamconsole.serviceiamconsole

Stop Soffid IAM console

To stop Soffid console, use service manager or execute:

systemctlnet stop soffid-iamconsole.service

Status

systemctl status soffid-iamconsole.serviceiamconsole

Logs

You can find the console logs at: /opt/soffid/iam-console-3/logs

Startup / Shutdown Synchronization servers

Start Sync server

systemctl
To start soffid-iamsync.Soffid Sync server, use service manager or execute:

net start SoffidSyncServer
Start Sync server
systemctl
To stop soffid-iamsync.Soffid Sync server, use service
 
Status
manager or execute:

systemctlnet statusstop soffid-iamsync.serviceSoffidSyncServer
Logs
You can find the console logs at: /opt/soffid/c:\program files\soffid\iam-sync/console-3\logs
System backup 
Soffid relies on a database to store almost every identity data. So, the first step to perform a daily database backup.

For Maria DB, look at: Backup and restore overview
For Oracle, look at: Backing Up The Database
For SQL Server, look at: Create a Full Database Backup (SQL Server)

Soffid console installation directory should be backed up after every installation or upgrade. Once the upgrade or installation has been done, only the log directory needs to be backed up.
Soffid synchronization servers configuration directory (conf) should be backed up just after configuration. In case of system failure, a new synchronization server should be installed and the conf directory can be restored onto it. The conf directory should be backed up on a different media than the database, due to conf directory contains the private keys that can decrypt the data stored in the database.