LDIFfile2CSVfile

Workflow to convert an LDIF file to a CSV file

LDIFfile2CSVfile converts directory data that you already have in LDIF format into a CSV file. You use it when a downstream process expects tabular file data instead of LDAP-oriented LDIF records.

This workflow is a file-to-file conversion workflow. It does not load data into the Identity Store or update a connected directory; it reads the source file and produces a CSV result through the configured workflow channel.

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

LDIFfile2CSVfile

Prerequisites

An agent that can run MetaCP.
A file-based channel configuration for LDIFfile2CSVfile that provides the LDIF input and the CSV output location.

Workflow and Activities

Step Activity Description Agent Runs after

Step	Activity	Description	Agent	Runs after
1	`LDIFfile2CSVfile_MetaCP`	Converts an LDIF file to a CSV file	`MetaCP`	start activity

LDIFfile2CSVfile_MetaCP

Converts an LDIF file to a CSV file

MetaCP

start activity

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

Activity	Job	Agent	Operation	Input channel	Output channel
`LDIFfile2CSVfile_MetaCP`	`LDIFfile2CSVfile_MetaCP`	`MetaCP`	Full Export	`LDIFfile2CSVfile`	`LDIFfile2CSVfile`

LDIFfile2CSVfile_MetaCP

MetaCP

Full Export

LDIFfile2CSVfile

Configuration Parameters

Table 1. Parameters of job `LDIFfile2CSVfile_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
`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, LDIFfile2CSVfile_MetaCP. MetaCP performs the whole conversion in a single pass, so there is no handover to another activity.

If the activity ends with an error, the workflow stops immediately because no later activity can continue or complete the conversion.

Operation

When you start the job, MetaCP opens the LDIFfile2CSVfile channel and reads the LDIF source.
Because the job runs with full processing only, each execution converts the complete source file.
MetaCP writes the converted result as CSV through the configured workflow channel and then ends the job.