ReportGeneration

Generate reports from Identity Store

ReportGeneration runs the service agent to produce the provisioning report for the Identity Store. The report summarises the target-system accounts and group memberships that the Identity Store has calculated and is used for auditing and compliance reviews. The agent generates the report in HTML format and writes it to the configured output path.

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

ReportGeneration

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/ReportGeneration

Prerequisites

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

  • The ReportGeneration in and ReportGeneration out channels must be configured.

Workflow and Activities

Step Activity Description Agent Runs after

1

ReportGeneration

Report generation via role service agent

ServiceAgent

start activity

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

ReportGeneration

ProvisioningReport

ServiceAgent

Full Import

Default

Ident2Report

Configuration Parameters

Table 1. Parameters of job ProvisioningReport
Parameter Default value

delta_mode

full

delta_on

0

ldaptrace

FALSE

ldaptracelines

0

reportformat

HTML

reportname

cn=Users with all properties,cn=Users with all properties,cn=Users,cn=Default,cn=Reports,cn=Configuration,cn=My-Company

request

generateReport

trace

1

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, ReportGeneration, which runs the ServiceAgent job ProvisioningReport. The request is generateReport and the output format is HTML. The agent reads the required data through the ReportGeneration in input channel and writes the finished report through the ReportGeneration out output channel.

Operation

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

  2. The C++-based Server starts the ReportGeneration activity and launches the ServiceAgent job ProvisioningReport.

  3. The agent reads the data it needs from the Identity Store through the ReportGeneration in input channel.

  4. The ProvisioningReport job assembles the report and formats it as HTML (reportformat = HTML).

  5. The finished report is written to the output destination configured for the ReportGeneration out output channel.