Ident2XMLfile

Workflow for Export from LDAP to a XML file

Ident2XMLfile exports data from the Identity Store to an XML file. You use it when a downstream system or reporting process expects scheduled XML output from DirX Identity.

Because the workflow is delta-capable, you can use the same definition for recurring changed-data exports and for complete baseline exports.

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

Ident2XMLfile

Prerequisites

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

Workflow and Activities

Step Activity Description Agent Runs after

Step	Activity	Description	Agent	Runs after
1	`Ident2XMLfile_MetaCP`	Export from LDAP into a XML file	`MetaCP`	start activity

Ident2XMLfile_MetaCP

Export from LDAP into 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
`Ident2XMLfile_MetaCP`	`Ident2XMLfile_MetaCP`	`MetaCP`	Full Export	`Ident2XMLfile`	`Ident2XMLfile`

Ident2XMLfile_MetaCP

MetaCP

Full Export

Ident2XMLfile

Configuration Parameters

Table 1. Parameters of job `Ident2XMLfile_MetaCP`
Parameter	Default value
`debug_trace`	0
`delta_mode`	delta-or-full
`delta_on`	1
`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 contains one MetaCP activity, Ident2XMLfile_MetaCP. That activity reads the export set from the Identity Store and writes the XML result directly.

If the activity fails, the workflow ends there because no follow-up activity exists.

Operation

When you start the workflow, MetaCP opens the Ident2XMLfile channel and reads the configured data from the Identity Store.
MetaCP serializes that data to the XML output file.
Because delta_on is enabled with delta_mode set to delta-or-full, you can run the workflow as a delta export or as a full export, depending on how you start it.