CombinedMaintenance

Runs some maintenance workflows

CombinedMaintenance bundles three Identity Store maintenance tasks into one schedulable workflow: policy execution (PolicyExecution), a consistency check (ConsistencyCheck) and history extraction (SaveHistory / ExtractAuditTrail). Use it when you want a single nightly or weekly schedule to cover all three operations instead of scheduling them separately.

The workflows in this reference are delivered as factory data and are loaded into the Connectivity configuration database during the initial configuration. They are samples: use the Identity Manager to copy a workflow into your own scenario and adapt the copy. Do not change the delivered objects, because a product update can replace them.

At a Glance

Name

CombinedMaintenance

Category

Identity Store

Technology

Tcl-based scheduled workflow

LDAP object class

dxmWorkflow

Workflow type

-

Connected system / controller type

-

Configuration wizard

LDAP-LDAP

Active in the factory data

not set

Factory data version

7.0

Factory data path

Workflows/Default/Identity Store/CombinedMaintenance

Prerequisites

  • The individual jobs referenced by the three activities (PolicyExecution, ConsistencyCheck, ExtractAuditTrail) must be configured in the C++-based Server.

Workflow and Activities

Step Activity Description Agent Runs after

1

PolicyExecution

Executes policies on the Identity Store

-

start activity

2

ConsistencyCheck

Checks consistency of the Identity Store

-

PolicyExecution

3

SaveHistory

Exports and removes all history information from the Identity Store

-

start activity

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

PolicyExecution

PolicyExecution

-

not set

-

-

ConsistencyCheck

ConsistencyCheck

-

not set

-

-

SaveHistory

ExtractAuditTrail

-

not set

-

-

A Tcl-based workflow runs scheduled in the C++-based Server (IdS-C). Its activities run in the order defined by the dxmPredecessorActivity-DN chain, and each activity starts a job that runs one agent with one input and one output channel. Agents exchange their data through files or directly through the meta controller, so a typical workflow consists of an export activity that writes the data of the connected system and an import activity that maps and loads that data into the Identity Store.

You start these workflows manually from the Identity Manager or attach them to a schedule.

The workflow has three activities. PolicyExecution runs first and applies all configured policies to the Identity Store entries; ConsistencyCheck follows after PolicyExecution completes and runs the consistency check via the role service agent. SaveHistory also starts from the start activity (in parallel with PolicyExecution) and runs the ExtractAuditTrail job to export and purge history records. Because SaveHistory and PolicyExecution both follow the start activity, the order between SaveHistory and ConsistencyCheck is not guaranteed; configure a sequential chain if order matters in your scenario.

Operation

  1. You start the workflow manually from the Identity Manager or attach it to a schedule.

  2. The C++-based Server starts PolicyExecution and SaveHistory in parallel.

  3. PolicyExecution applies all configured policies to matching Identity Store entries via its job; when it completes, the server starts ConsistencyCheck.

  4. ConsistencyCheck runs the role service agent to verify data integrity in the Identity Store.

  5. In parallel, SaveHistory runs the ExtractAuditTrail job, which exports all audit trail records to a file and deletes the records from the Identity Store.

  6. The workflow completes when all three activities have finished.