XMLfile2Ident

Workflow for Import to LDAP from a XML file

XMLfile2Ident imports data from an XML file into the Identity Store. You use it when another system provides a periodic XML extract that DirX Identity should load as a scheduled source import.

The workflow performs a direct file-to-Identity-Store import through one MetaCP activity and always processes the complete input file.

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

XMLfile2Ident

Prerequisites

An agent that can run MetaCP.
Access from MetaCP to the Identity Store and a file-based channel configuration for XMLfile2Ident.

Workflow and Activities

Step Activity Description Agent Runs after

Step	Activity	Description	Agent	Runs after
1	`XMLfile2Ident_MetaCP`	Import to LDAP from a XML file	`MetaCP`	start activity

XMLfile2Ident_MetaCP

Import to LDAP from a XML file

MetaCP

start activity

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

Activity	Job	Agent	Operation	Input channel	Output channel
`XMLfile2Ident_MetaCP`	`XMLfile2Ident_MetaCP`	`MetaCP`	Full Export	`XMLfile2Ident`	`XMLfile2Ident`

XMLfile2Ident_MetaCP

MetaCP

Full Export

XMLfile2Ident

Configuration Parameters

Table 1. Parameters of job `XMLfile2Ident_MetaCP`
Parameter	Default value
`debug_trace`	0
`delta_mode`	full
`delta_on`	0
`exact_action`	FALSE
`init_mode`	REAL
`max_trace_entries`	10
`min_source_entries`	0
`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, XMLfile2Ident_MetaCP. MetaCP reads the XML source and imports it directly into the Identity Store without an intermediate activity chain.

If the activity fails, the workflow stops immediately because no later step can continue the import.

Operation

When you start the workflow, MetaCP opens the XMLfile2Ident channel and reads the XML input file.
The job runs in full mode, so each execution processes the complete file content.
Because min_source_entries is 0, the workflow can also complete when the source file is empty.