DirXLDIF2Ident

Workflow for synchronization of a corporate directory with DirX Identity

DirXLDIF2Ident imports directory data from an LDIF file into the Identity Store. You use it when a source directory delivers LDIF exports and you want DirX Identity to load that data as a scheduled source workflow.

The workflow runs as a single MetaCP import over channel DirXLDIF2Ident. It performs full loads, and its test setting can limit a test run to one entry.

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

DirXLDIF2Ident

Prerequisites

The MetaCP agent is available for scheduled execution.
The channel DirXLDIF2Ident is configured for the LDIF input and the Identity Store side of the workflow.
The LDIF file is available on the system where MetaCP runs.

Workflow and Activities

Step Activity Description Agent Runs after

Step	Activity	Description	Agent	Runs after
1	`DirXLDIF2Ident_MetaCP`	Activity for LDIF import	`MetaCP`	start activity

DirXLDIF2Ident_MetaCP

Activity for LDIF import

MetaCP

start activity

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

Activity	Job	Agent	Operation	Input channel	Output channel
`DirXLDIF2Ident_MetaCP`	`DIrXLDIF2Ident_MetaCP`	`MetaCP`	Full Import	`DirXLDIF2Ident`	`DirXLDIF2Ident`

DirXLDIF2Ident_MetaCP

DIrXLDIF2Ident_MetaCP

MetaCP

Full Import

DirXLDIF2Ident

Configuration Parameters

Table 1. Parameters of job `DIrXLDIF2Ident_MetaCP`
Parameter	Default value
`debug_trace`	0
`delta_mode`	full
`delta_on`	0
`exact_action`	FALSE
`init_mode`	REAL
`max_trace_entries`	100
`notify_not_ok`	0
`statistics`	TRUE
`test_mapping_only`	FALSE
`test_max_entries`	1
`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, DirXLDIF2Ident_MetaCP. This activity runs the complete LDIF import in one MetaCP job through channel DirXLDIF2Ident. Because no second activity follows, any error ends the workflow run at this point.

Operation

The scheduler starts the MetaCP activity for DirXLDIF2Ident.
MetaCP reads the LDIF content through channel DirXLDIF2Ident and applies the configured mappings.
The workflow runs in full mode and does not use delta handling. If you run it in test mode, only one entry is processed because test_max_entries defaults to 1.
In normal operation, MetaCP writes the mapped result to the Identity Store. If processing fails, the workflow ends with that job error.