Understanding Data Source Naming: Workflow vs. Workpoint and Reporting vs. Report Snapshot
search cancel

Understanding Data Source Naming: Workflow vs. Workpoint and Reporting vs. Report Snapshot

book

Article ID: 448646

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

When configuring data sources in Identity Manager (IDM) 15.x or using IGA Xpress, administrators may notice a discrepancy between the names used in documentation and the actual database connection labels in the user interface or configuration files.

Specifically:

  • Documentation may refer to Workflow while the UI shows Workpoint.
  • Documentation may refer to Reporting while the UI shows reportsnapshot.

Environment

  • CA Identity Manager 15.x
  • IGA Xpress 2.0
  • Upgrade scenarios from IDM 14.5 to 15.0

Cause

The differences reflect the distinction between the "Friendly Name" (used in high-level documentation) and the "Technical Name" (used by the underlying engine or architecture).

  • Workpoint: This is the technical name for the workflow engine integrated with Identity Manager. In configuration files, this is often represented as WPDS (Workpoint Data Source).
  • Report Snapshot: This is the technical database that stores data extracted from the primary store for use by the JasperServer reporting engine. In the UI, this is frequently labeled as the Snapshot Database Connection.

Resolution

When performing upgrades or new configurations, map the data sources as follows:

  1. Workflow Database

    • Friendly/Legacy Name: Workflow
    • IDM 15.x Technical Name: workpoint
    • Action: Point the workpoint data source to your existing Workflow database (e.g., from version 14.5).
  2. Reporting Database

    • Friendly/Legacy Name: Reporting
    • IDM 15.x Technical Name: reportsnapshot
    • Action: Point the reportsnapshot data source to your existing Reporting database. This serves as the snapshot store for the internal reporting engine.

Note: Always verify database connectivity after mapping to ensure the technical identifiers are correctly communicating with the underlying database instances.