Import Provisioning Collections

Workflow to import provisioning collections. Imports the ProvisioningCollections.ldif file to a customer domain. To make this work you have to: - Create a new bind profile in the connected directory that binds to your customer domain - Use this bind profile in this workflow

Import Provisioning Collections imports a ProvisioningCollections.ldif file into a customer domain. Administrators use it to transfer the provisioning configuration — roles, permissions and groups — from a source domain (such as the factory data domain cn=My-Company) into a different customer domain. The domainmapping parameter translates the source DN prefix to the target DN prefix during the import, and an optional schema file (schemafile) can restrict which object classes are imported when useschemafile is TRUE.

Before triggering this workflow, create a new bind profile in the connected directory that points to the customer domain and configure this workflow to use that bind profile.

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 Provisioning Collections

Prerequisites

A ProvisioningCollections.ldif export file must exist and be accessible to the Java-based Server.
A bind profile must be configured in the connected directory that binds to the target customer domain.
The domainmapping parameter must be updated to map the source domain DN (default cn=My-Company) to the target customer domain DN before the workflow is triggered.

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 Provisioning 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><mapping source="cn=My-Company" target="cn=Customer Domain" ></mapping></domains>
`resourcefamily`	workflowengine
`retrylimit`	0
`schemafile`	C:\MR_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 source domain DN, and domainmapping rewrites it to the target customer domain DN during the import. When useschemafile is TRUE, only the object classes listed in schemafile are imported.

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 Provisioning Collections workflow, typically through the Identity Manager.
The perform activity reads the ProvisioningCollections.ldif file and imports its entries into the customer domain, translating the source DN prefix to the target customer domain DN according to domainmapping.
If useschemafile is TRUE, only the object classes specified in schemafile are imported.
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 domainmapping and the bind profile to match the target customer domain, and activate the copy.