CorpDir2Ident

Workflow for synchronization of a corporate directory with DirX Identity

CorpDir2Ident synchronizes data from a corporate directory into the Identity Store. You use it when the corporate directory is the source of identity data and you want DirX Identity to refresh its copy on a schedule.

The workflow runs as one MetaCP job over channel CorpDir2Ident. It is designed for full synchronization runs rather than delta processing.

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

CorpDir2Ident

Prerequisites

The MetaCP agent is available for scheduled execution.
The channel CorpDir2Ident is configured for the corporate directory side and the Identity Store side of the workflow.
The source connected directory is reachable from the system where MetaCP runs.

Workflow and Activities

Step Activity Description Agent Runs after

Step	Activity	Description	Agent	Runs after
1	`CorpDir2Ident_MetaCP`	Synchronize data via LDAP2LDAP	`MetaCP`	start activity

CorpDir2Ident_MetaCP

Synchronize data via LDAP2LDAP

MetaCP

start activity

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

Activity	Job	Agent	Operation	Input channel	Output channel
`CorpDir2Ident_MetaCP`	`CorpDir2Ident_MetaCP`	`MetaCP`	Full Export	`CorpDir2Ident`	`CorpDir2Ident`

CorpDir2Ident_MetaCP

MetaCP

Full Export

CorpDir2Ident

Configuration Parameters

Table 1. Parameters of job `CorpDir2Ident_MetaCP`
Parameter	Default value
`debug_trace`	0
`delta_mode`	full
`delta_on`	0
`exact_action`	FALSE
`init_mode`	REAL
`max_trace_entries`	10
`notify_not_ok`	0
`statistics`	TRUE
`test_mapping_only`	FALSE
`test_max_entries`	0
`trace_level`	1
`trace_recordcount`	0

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 one activity, CorpDir2Ident_MetaCP. This MetaCP job performs the complete synchronization through channel CorpDir2Ident in a single step. Because there is no subsequent activity, any error ends the workflow run at this job.

Operation

The scheduler starts activity CorpDir2Ident_MetaCP in agent MetaCP.
MetaCP opens channel CorpDir2Ident, reads the source data from the connected directory, and applies the configured mappings.
The job runs in full mode and normal execution mode, so it writes real changes to the Identity Store and does not rely on delta handling.
When processing finishes successfully, the workflow run ends. If processing fails, the workflow ends with that job error.