Import Connectivity Collections

Workflow to import collections. Imports a set of Java-based workflows, adapts and activates it.

Import Connectivity Collections imports a set of Java-based workflows from an LDIF collection file, adapts the imported workflows to the target domain, and activates them. Administrators use it to deploy a connectivity configuration — such as a complete set of provisioning workflows for a new target system — into a customer domain without having to create each workflow manually.

The domainmapping parameter translates DN prefixes from the source domain to the target domain during the import. An optional schema file (schemafile) restricts the import to specific object classes when useschemafile is TRUE.

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

Import Connectivity Collections

Prerequisites

A connectivity collections LDIF file must exist in the location configured for the perform activity (default schema file path C:\ID_Collections\schemafile).
The domain parameter must point to the correct company DN (cn=My-Company by default).
The domainmapping parameter must be updated to map source to target DN prefixes if the target domain differs from the source.

Workflow and Activities

Activity Type Component description Description Ports

Activity	Type	Component description	Description	Ports
`error`	`error`	`provisioningActivity`	Error Activity	`Message`
`perform`	`Server`	`transportActivity`	Activity for performing the transport task	-

error

provisioningActivity

Error Activity

Message

perform

Server

transportActivity

Activity for performing the transport task

Ports

Activity Port Component description Connector Connected directory Bind profile SSL

Activity	Port	Component description	Connector	Connected directory	Bind profile	SSL
`error`	`Message`	`errorPort`	`ErrorNotifyMailConnector`	-	-	not set

error

Message

errorPort

ErrorNotifyMailConnector

not set

Configuration Parameters

Table 1. Workflow parameters of `Import Connectivity Collections`
Parameter	Default value
`timeout`	P0Y0M4DT0H0M0S
`transport`	true

Table 2. Parameters of activity `error`
Parameter	Default value
`resourcefamily`	LDAP
`retrylimit`	0
`timeout`	P0Y0M1DT0H0M0S
`waitbeforeretry`	P0Y0M0DT0H0M0S

Table 3. Parameters of port `Message` (activity `error`)
Parameter	Default value
`decrypt.attribute`	dxmPassword

Table 4. Parameters of activity `perform`
Parameter	Default value
`domain`	cn=My-Company
`domainmapping`	<domains></domains>
`resourcefamily`	workflowengine
`retrylimit`	0
`schemafile`	C:\ID_Collections\schemafile
`timeout`	P0Y0M1DT0H0M0S
`useschemafile`	FALSE
`waitbeforeretry`	P0Y0M0DT0H0M0S

A Java-based real-time workflow runs as a permanently loaded configuration in the Java-based Server (IdS-J). It is triggered by a request or an event rather than by a schedule. Each workflow consists of activities; an activity opens one port per system it talks to, and each port uses a connector to reach that system.

Most provisioning workflows contain a join activity that performs the actual work and an error activity that receives requests which still fail after all retries and sends a notification about them. The retrylimit, waitbeforeretry and timeout parameters of an activity control how often and how long a failed request is retried before it is handed to the error activity.

The event port publishes change events over JMS, and the notify port sends e-mail notifications. Neither port is bound to a connected directory.

The perform activity uses the transportActivity component with the Server type to carry out the import directly within the Java-based Server. It has no external connector ports. The domain parameter specifies the target domain DN, and domainmapping rewrites source DN prefixes during the import. After import, the Java-based Server adapts and activates the imported workflows.

Because retrylimit is 0, a failure is not retried: the request is passed immediately to the error activity, which sends a notification via the Message port.

Operation

An import request is submitted to the Import Connectivity Collections workflow, typically through the Identity Manager.
The perform activity reads the connectivity collection LDIF file and imports the Java-based workflows and related objects into the domain cn=My-Company.
DN prefixes in the imported data are translated according to domainmapping to match the target domain.
After the import, the Java-based Server adapts and activates the imported workflow configurations.
If the import fails, the request is passed immediately to the error activity (retrylimit is 0), which reports the failure by e-mail through the Message port.

The workflow is delivered inactive (dxmActive is FALSE). Copy it into your own scenario, update domain and domainmapping to match the target environment, and activate the copy.