9.5 Configuring Workflow Engine

You can modify the installation properties after installing the Workflow Engine by running the Identity Governance Configuration Update utility. However, you must restart the application server that hosts the Workflow Engine for the changes to take effect. For more information, see Section 15.1.5, Using the Identity Governance Configuration Update Utility.

9.5.1 Starting Workflow Engine

To verify installation and to initialize the Workflow Engine database, you must start the application server.

  1. Log in to the application server that hosts the Workflow Engine.

  2. (Conditional) If this is the first time you are starting the Workflow Engine, complete the following steps:

    1. Delete all files and folders in the following directories for your application server:

      • Linux: Temporary directory, located by default in

        • /opt/netiq/idm/apps/tomcat/temp

        • Catalina cache directory, located by default in /opt/netiq/idm/apps/tomcat/work/Catalina/localhost

      • Windows: Temporary directory, located by default in:

        • C:\netiq\idm\apps\tomcat\temp

        • Catalina cache directory, located by default in: C:\netiq\idm\apps\tomcat\work\Catalina\localhost

    2. Delete all log files from the logs directory of your application server, located by default in:

      • Linux: /opt/netiq/idm/apps/tomcat/logs

      • Windows: C:\netiq\idm\apps\tomcat\logs

  3. Start Apache Tomcat. For more information, see Section 3.4.3, Starting and Stopping Apache Tomcat.

  4. (Optional) To observe the Apache Tomcat initialization process in Linux, enter the following command:

    tail -f path_to_Tomcat_folder/logs/catalina.out

    When the process completes, the file contains the following message:

    Server startup in nnnn ms