RunWFexternally

Run Workflow in foreign DirX Identity domain

RunWFexternally instantiates and executes a workflow in a foreign DirX Identity domain. The RunWorkflow agent connects to the remote domain via the Ident2ForeignDomain output channel, using the instantiator (ForeignDomain) and the message server (ATS) specified as parameters, and starts the workflow named by wfname. Use this workflow when you need to trigger a maintenance or provisioning workflow that runs in a separate DirX Identity domain from the one you are operating in.

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

RunWFexternally

Category

Identity Store

Technology

Tcl-based scheduled workflow

LDAP object class

dxmWorkflow

Workflow type

-

Connected system / controller type

-

Configuration wizard

LDAP-LDAP

Active in the factory data

not set

Factory data version

7.0

Factory data path

Workflows/Default/Identity Store/RunWFexternally

Prerequisites

  • The foreign DirX Identity domain must be reachable, and the ATS message server and the ForeignDomain instantiator must be configured.

  • The Ident2ForeignDomain output channel must be configured to point to the foreign domain.

  • The workflow named by wfname must exist and be active in the foreign domain.

Workflow and Activities

Step Activity Description Agent Runs after

1

RunWFexternally

Run Workflow in foreign DirX Identity domain

RunWorkflow

start activity

Jobs and Agents

Activity Job Agent Operation Input channel Output channel

RunWFexternally

RunWFexternally

RunWorkflow

Full Import

Default

Ident2ForeignDomain

Configuration Parameters

Table 1. Parameters of job RunWFexternally
Parameter Default value

instantiator

ForeignDomain

messageserver

ATS

timeoutcreate

86400

timeoutexecute

86400

tracelevel

1

wfname

Default/Source Scheduled/LDIFfile/LDIFfile2Ident

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, RunWFexternally, which runs the RunWorkflow agent job of the same name. The agent performs a Full Import operation, connecting to the foreign domain through the Ident2ForeignDomain output channel using the ForeignDomain instantiator and the ATS message server. The wfname parameter identifies the workflow to start in the remote domain; the timeoutcreate and timeoutexecute parameters (both 86400 seconds) control how long the agent waits for the remote workflow to be created and to complete.

Operation

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

  2. The C++-based Server starts the RunWFexternally activity and launches the RunWorkflow agent job.

  3. The agent connects to the foreign DirX Identity domain through the Ident2ForeignDomain output channel, using the ForeignDomain instantiator and the ATS message server.

  4. The agent starts the workflow identified by wfname in the remote domain and waits up to timeoutcreate seconds for the remote workflow instance to be created.

  5. Once created, it waits up to timeoutexecute seconds for the remote workflow to complete.

  6. After successful completion the activity ends. If the remote workflow cannot be created or does not complete within the timeout, the activity fails.