Ident2Report

Workflow generating reports out of an LDAP directory

Ident2Report generates an HTML report of the Connected Directories configuration from the Identity Store. The ReportAgent reads the configuration subtree starting from the basedn parameter and produces the report named by reportname (Default/ConnDirs), writing the output through the Ident2Report channel. Use this workflow to get an overview of the connectivity configuration for documentation or audit purposes.

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

Ident2Report

Category

Identity Store

Technology

Tcl-based scheduled workflow

LDAP object class

dxmWorkflow

Workflow type

-

Connected system / controller type

-

Configuration wizard

LDAP-File

Active in the factory data

not set

Factory data version

7.0

Factory data path

Workflows/Default/Identity Store/Ident2Report

Prerequisites

  • The ReportAgent must be deployed and configured in the C++-based Server.

  • The Ident2Report input and output channels must be configured; the basedn parameter must point to the root of the Connected Directories configuration subtree.

Workflow and Activities

Step Activity Description Agent Runs after

1

Ident2Report_Report

Generate a report out of an LDAP directory

ReportAgent

start activity

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

Ident2Report_Report

ConnectivityReport

ReportAgent

Full Export

Ident2Report

Ident2Report

Configuration Parameters

Table 1. Parameters of job ConnectivityReport
Parameter Default value

basedn

cn=uid-7f001-54824-101de9c3b73—​7fbf,dxmC=uid-7f001-1b8119a-101e7a58f91—​7f0f,dxmC=uid-7f001-54824-101de9c3b73—​7fc0,dxmC=Connected Directories,dxmC=DirXmetahub

delta_mode

full

delta_on

0

reportname

Default/ConnDirs

reporttype

HTML

trace

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 a single activity, Ident2Report_Report, which runs the ReportAgent job ConnectivityReport. Unlike most Tcl-based workflows the job uses a Full Export operation: it reads configuration data from the Identity Store starting at the basedn through the Ident2Report input channel and writes the generated HTML report to the Ident2Report output channel. The reportname parameter selects which report template to use.

Operation

  1. You start the workflow manually from the Identity Manager or attach it to a schedule.

  2. The C++-based Server starts the Ident2Report_Report activity and launches the ReportAgent job ConnectivityReport.

  3. The agent performs a Full Export: it reads the Connected Directories configuration subtree starting at the basedn through the Ident2Report input channel.

  4. The report template identified by reportname (Default/ConnDirs) is applied and the result is written as HTML to the Ident2Report output channel.

  5. The generated report is available for review in the target file or directory configured for the output channel.