Notes2Ident_Validation

Workflow for Validation between Notes and Identity Store

A validation workflow compares the content of the connected system with the state that DirX Identity holds for the corresponding target system. It runs in one of two modes, controlled by the mode parameter of the workflow:

  • InitialLoad - exports all accounts and groups and their relationships from the connected system and imports them into the target system subtree of the Identity Store in replace mode. Use this mode when you take a target system into operation.

  • Validation - detects deviations between the state known in DirX Identity and the state in the connected system, for example accounts or groups that were created or deleted outside of DirX Identity, and writes a message about each deviation into the "to do" field (dxrToDo) of the affected target system object.

Both modes update the dxrTSState attribute and the group member attributes of the affected target system objects.

Notes2Ident_Validation validates a connected HCL Notes directory against the corresponding target system subtree in the Identity Store. For both object types, NotesAgent exports the data from Notes and MetaCP imports it for validation in DirX Identity.

The workflow processes accounts first and groups second during the validation run.

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

Notes2Ident_Validation

Category

Target Scheduled / Notes

Technology

Tcl-based scheduled workflow

LDAP object class

dxmWorkflow

Workflow type

Validation

Connected system / controller type

-

Configuration wizard

Notes-LDAP

Active in the factory data

not set

Factory data version

7.0

Factory data path

Workflows/Default/Target Scheduled/Notes/Notes2Ident_Validation

Prerequisites

  • Configure NotesAgent for the connected HCL Notes directory.

  • Create and configure the HCL Notes connected directory and the corresponding target system subtree in the Identity Store.

Workflow and Activities

Step Activity Description Agent Runs after

1

Notes2Ident_ValAccount_NotesAgent

Import of accounts into Identity Store

NotesAgent

start activity

2

Notes2Ident_ValAccount_MetaCP

Export of accounts from Notes

MetaCP

Notes2Ident_ValAccount_NotesAgent

3

Notes2Ident_ValGroup_NotesAgent

Import of groups into Identity Store

NotesAgent

Notes2Ident_ValAccount_MetaCP

4

Notes2Ident_ValGroup_MetaCP

Export of groups from Notes

MetaCP

Notes2Ident_ValGroup_NotesAgent

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

Notes2Ident_ValAccount_NotesAgent

Notes2Ident_ValAccount_NotesAgent

NotesAgent

Delta Export

Notes2Ident_ValAccount

OutData

Notes2Ident_ValAccount_MetaCP

Notes2Ident_ValAccount_MetaCP

MetaCP

Delta Import

InData

Notes2Ident_ValAccount

Notes2Ident_ValGroup_NotesAgent

Notes2Ident_ValGroup_NotesAgent

NotesAgent

Delta Export

Notes2Ident_ValGroup

OutData

Notes2Ident_ValGroup_MetaCP

Notes2Ident_ValGroup_MetaCP

MetaCP

Delta Import

InData

Notes2Ident_ValGroup

Configuration Parameters

Table 1. Workflow parameters of Notes2Ident_Validation
Parameter Default value

mode

InitialLoad
Table 2. Parameters of job Notes2Ident_ValAccount_NotesAgent
Parameter Default value

delta_mode

full

delta_on

0

trace

1

tracelevel_1

1

tracelevel_2

1

tracelevel_3

1
Table 3. Parameters of job Notes2Ident_ValAccount_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

10

trace_level

1

trace_recordcount

0
Table 4. Parameters of job Notes2Ident_ValGroup_NotesAgent
Parameter Default value

delta_mode

full

delta_on

0

trace

1

tracelevel_1

1

tracelevel_2

1

tracelevel_3

0
Table 5. Parameters of job Notes2Ident_ValGroup_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

10

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.

In this workflow, the C++-based Server runs these activities in sequence:

  1. Notes2Ident_ValAccount_NotesAgent exports account data from the Notes directory.

  2. Notes2Ident_ValAccount_MetaCP imports that account data into the Identity Store validation flow.

  3. Notes2Ident_ValGroup_NotesAgent exports group data from the Notes directory.

  4. Notes2Ident_ValGroup_MetaCP imports that group data into the Identity Store validation flow.

If one activity fails, the workflow stops at that point and the remaining activities do not run.

Operation

  1. Start Notes2Ident_Validation manually or on a schedule.

  2. The workflow exports account data from Notes with Notes2Ident_ValAccount_NotesAgent and imports it with Notes2Ident_ValAccount_MetaCP.

  3. After the account pass finishes, the workflow exports group data with Notes2Ident_ValGroup_NotesAgent and imports it with Notes2Ident_ValGroup_MetaCP.

  4. Depending on the selected mode, the run either refreshes the target system subtree from Notes or records deviations between the Notes directory and the Identity Store on the affected target system objects.

  5. When the workflow finishes successfully, DirX Identity has processed both account and group data for the connected Notes target system.