Ident_HiPath

Bidirectional synchronization between Identity Store and HiPath 4000

Ident_HiPath synchronizes the Identity Store and a Siemens HiPath 4000 system in both directions. It first exports data from the Identity Store to HiPath and then exports the resulting HiPath state back into the Identity Store.

This workflow is unusual in this set because both activities run with HiPathAgent rather than using MetaCP for one side of the exchange.

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

Ident_HiPath

Category

Target Scheduled / HiPath

Technology

Tcl-based scheduled workflow

LDAP object class

dxmWorkflow

Workflow type

Sync

Connected system / controller type

-

Configuration wizard

LDAP-HDMS

Active in the factory data

not set

Factory data version

7.0

Factory data path

Workflows/Default/Target Scheduled/HiPath/Ident_HiPath

Prerequisites

  • Configure HiPathAgent so that it can connect to the HiPath 4000 system.

  • Create and configure the target system of type HiPath in the Identity Store so that the workflow has a target system subtree to synchronize.

Workflow and Activities

Step Activity Description Agent Runs after

1

Ident2HiPath_HiPathAgent

Synchronization from LDAP to HiPath

HiPathAgent

start activity

2

HiPath2Ident_HiPathAgent

Synchronization from HiPath to Identity Store

HiPathAgent

Ident2HiPath_HiPathAgent

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

Ident2HiPath_HiPathAgent

Ident2HiPath_HiPathAgent

HiPathAgent

Full Export

Ident2HiPath

Ident2HiPath

HiPath2Ident_HiPathAgent

HiPath2Ident_HiPathAgent

HiPathAgent

Full Import

HiPath2Ident

HiPath2Ident

Configuration Parameters

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

FALSE

test_mapping_only

FALSE

test_max_entries

10

trace_level

1
Table 2. Parameters of job HiPath2Ident_HiPathAgent
Parameter Default value

debug_trace

0

delta_mode

delta-or-full

delta_on

1

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

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. Ident2HiPath_HiPathAgent exports the relevant data from the Identity Store and writes it to the HiPath 4000 side.

  2. HiPath2Ident_HiPathAgent exports the HiPath 4000 state back into the Identity Store.

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

Operation

  1. Start Ident_HiPath manually or attach it to a schedule.

  2. The first activity, Ident2HiPath_HiPathAgent, processes the Identity Store to HiPath direction.

  3. When that activity succeeds, HiPath2Ident_HiPathAgent runs the return direction from HiPath back to the Identity Store.

  4. Because both directions run in one chain, the second pass only starts after the first pass has finished successfully.

  5. A successful run leaves the HiPath target system subtree in the Identity Store refreshed with the latest data exchanged during the same workflow execution.