Ident2JDBC_SyncAccountDel
Sync Workflow JDBC Accounts in state TBDEL
Ident2JDBC_SyncAccountDel processes accounts in state TBDEL in the Identity Store. It exports the relevant account identifiers with MetaCP and then passes them to JDBCImport, which deletes the corresponding accounts in the JDBC-connected database.
Ident2JDBC_SyncAccountDel is a companion sub-workflow of Ident_JDBC_Sync and is designed to run as part of that scheduled synchronization chain.
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 |
|
Category |
Target Scheduled / JDBC |
Technology |
Tcl-based scheduled workflow |
LDAP object class |
|
Workflow type |
- |
Connected system / controller type |
- |
Configuration wizard |
|
Active in the factory data |
not set |
Factory data version |
7.0 |
Factory data path |
|
Prerequisites
-
Configure
JDBCImportfor the JDBC-connected database. -
Configure
MetaCPfor the target system subtree that contains the accounts marked with stateTBDEL.
Workflow and Activities
| Step | Activity | Description | Agent | Runs after |
|---|---|---|---|---|
1 |
|
export accounts to be deleted in JDBC |
|
start activity |
2 |
|
delete accounts in JDBC |
|
|
Jobs and Agents
| Activity | Job | Agent | Operation | Input channel | Output channel |
|---|---|---|---|---|---|
|
|
|
Full Export |
|
|
|
|
|
Full Import |
|
|
Configuration Parameters
| Parameter | Default value |
|---|---|
|
0 |
|
delta-or-full |
|
1 |
|
FALSE |
|
REAL |
|
10 |
|
0 |
|
0 |
|
TRUE |
|
FALSE |
|
10 |
|
1 |
|
0 |
| Parameter | Default value |
|---|---|
|
9 |
|
full |
|
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:
-
Ident2JDBC_SyncAccountDel_MetaCPexports the accounts that are marked for deletion in the Identity Store. -
Ident2JDBC_SyncAccountDel_JDBCImportdeletes the corresponding accounts in the JDBC-connected database.
If one activity fails, the workflow stops at that point and the remaining activities do not run.
Operation
-
Start
Ident2JDBC_SyncAccountDeldirectly or letIdent_JDBC_Synccall it as part of the full JDBC synchronization run. -
The workflow first selects the accounts that are already in state
TBDELand exports them withMetaCP. -
JDBCImportthen consumes that export and removes the matching accounts from the JDBC-connected database. -
If the delete import fails, the workflow stops and the account remains in the Identity Store state that triggered the deletion attempt.
-
A successful run removes the selected JDBC-side accounts that were flagged for deletion in the Identity Store.