Identity Governance Universe Import Stuck at 0% - Workpoint URL Configuration
search cancel

Identity Governance Universe Import Stuck at 0% - Workpoint URL Configuration

book

Article ID: 93081

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Suite

Issue/Introduction

When attempting to run a Universe import in Symantec Identity Governance, the task may appear to start but remains stuck at "0% in progress" indefinitely. This behavior typically indicates a communication failure between the Governance engine and the Workpoint workflow components, often due to an incorrect URL or hostname resolution issue.



The import log file shows:

09:56:54,431 INFO  [com.eurekify.services.imservice.notifications.LiveNotificationsUniverseConsumer] (pool-80-thread-7) Live Notifications for Universe TGTUniverse status HOLD: Import in progress - No Master/Model configurations (FlowId=43)

Environment

Identity Governance 14.x

Cause

The issue is caused by an incorrectly specified Workpoint URL in the Governance settings or a failure in the application server's ability to resolve the hostname of the Workpoint node.

This prevents the import process from initiating the required workflow triggers.

Resolution

Step 1: Verify and Update the Workpoint URL

  1. Log in to the Identity Governance (IG) portal as an administrator.
  2. Navigate to Home > Administration > Settings.
  3. Select Property Settings.
  4. Locate the property: tms.workflow.url.
  5. Ensure the URL is correct (e.g., http://[fqdn]:[port]/workpoint).
    • Note: Use the Fully Qualified Domain Name (FQDN) rather than a short name to ensure resolution.

Step 2: Check Hostname Resolution (Cluster/vApp)

If the URL is correct but the issue persists:

  1. Verify that all nodes in the cluster can resolve each other's hostnames.
  2. Check the /etc/hosts file (on Virtual Appliances) or DNS settings to ensure the Workpoint server's hostname matches the entry in tms.workflow.url.

Step 3: Apply and Restart

  1. In a cluster deployment, ensure the property is updated across all nodes.
  2. Restart the Identity Governance application server (Wildfly/JBoss) to commit the changes.