E.1 How is the Separate Workflow Engine Installed?

By default, the Workflow Engine service is installed as part of Identity Applications installation. You can cluster it the same way as in the earlier versions without any additional configuration.

The Workflow Engine persists the workflow state information in a new database named igaworkflowdb. If an existing workflow process is in a running state, its data is moved to igaworkflowdb before the new Workflow Engine starts managing it. The Identity Applications installer copies the data from the Identity Applications database (idmuserappdb) to the Workflow Engine database (igaworkflowdb). If you are upgrading Identity Manager 4.6.x or 4.7.x to Identity Manager 4.8, use the workflow migration tool to export the data before starting the upgrade. The tool internally uses the /IDMProv/rest/access/data/migration/workflow API for migration. For more information about the migration tool, see Data Migration in the NetIQ Identity Manager Setup Guide for Linux.

The Workflow Engine uses REST service to obtain the tasks and workflow history from the Workflow Engine service.

The Identity Applications installation program automatically registers the Workflow Engine service as a client with One SSO Provider (OSP) to ensure communication with other Identity Applications components. The installer stores these connection and authentication properties in the ism-configuration.properties file.