ODBC_Ident

Combined workflow to run ODBC2Ident and Ident2ODBC in sequence

ODBC_Ident is an orchestration workflow that runs ODBC2Ident and then Ident2ODBC. You use it when you want one scheduled job to execute the inbound and outbound ODBC exchange in a fixed order.

The workflow itself does not connect to a source or target system directly. It only chains the two sibling workflows, so its behavior depends on how those workflows are configured.

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

ODBC_Ident

Prerequisites

Configured ODBC2Ident and Ident2ODBC workflows.
The agents and source or target definitions that those two workflows require.

Workflow and Activities

Step	Activity	Description	Agent	Runs after
1	`ODBC2Ident`	Runs the ODBC2Ident workflow	-	start activity
2	`Ident2ODBC`	Runs the Ident2ODBC workflow	-	`ODBC2Ident`

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

Activity	Job	Agent	Operation	Input channel	Output channel
`ODBC2Ident`	`ODBC2Ident`	-	not set	-	-
`Ident2ODBC`	`Ident2ODBC`	-	not set	-	-

ODBC2Ident

not set

Ident2ODBC

not set

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 contains two sub-workflow calls instead of direct agent activities. It starts ODBC2Ident first and starts Ident2ODBC only after the first workflow finishes successfully.

If ODBC2Ident ends with an error, Ident2ODBC is not started. Any error in either sub-workflow becomes the result of the combined workflow.

Operation

When you start ODBC_Ident, it first calls the ODBC2Ident workflow and waits until that workflow finishes.
If the inbound synchronization succeeds, the workflow starts Ident2ODBC as the second step.
The overall run finishes only after both sub-workflows complete, which gives you one scheduled execution window for both directions.