CertificationCampaignController

Sample workflow for monitoring certification campaigns.

CertificationCampaignController monitors the life cycle of active certification campaigns in the Identity Store. Each time a campaign changes state — for example, when all reviewers have submitted their decisions or when a campaign deadline is reached — the Java-based Server passes the triggering request to the join activity, which advances the campaign to its next state and triggers any configured follow-on actions.

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

CertificationCampaignController

Prerequisites

The DirX Identity certification feature must be configured and at least one campaign must exist in the Identity Store.
Copy the workflow into your scenario, bind it to the Java-based Server, and activate the copy.

Workflow and Activities

Activity Type Component description Description Ports

Activity	Type	Component description	Description	Ports
`error`	`error`	`provisioningActivity`	Error Activity	`Message`
`join`	`CertificationCampaignController`	`CertificationCampaignActivity`	Activity for monitoring Certification Campaigns	-

error

provisioningActivity

Error Activity

Message

join

CertificationCampaignController

CertificationCampaignActivity

Activity for monitoring Certification Campaigns

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 `CertificationCampaignController`
Parameter	Default value
`timeout`	P0Y0M4DT0H0M0S

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

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

Table 4. Parameters of activity `join`
Parameter	Default value
`domain`	cn=My-Company
`resourcefamily`	CertificationCampaign
`retrylimit`	0
`timeout`	P0Y0M1DT0H0M0S
`waitbeforeretry`	P0Y0M0DT0H30M0S

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 workflow has two activities. The join activity of type CertificationCampaignController carries all the processing logic; it uses the CertificationCampaignActivity component to advance campaign state and has a retrylimit of 0, meaning a failed request is not retried but is passed directly to the error activity. The error activity reports the failure by e-mail through the Message port.

Operation

A campaign state change event or a deadline expiry triggers a request for a certificationCampaign controller type in the Identity Store.
The Java-based Server passes the request to the join activity of this workflow.
The CertificationCampaignActivity component evaluates the campaign’s current state, determines the next action and updates the campaign object in the Identity Store accordingly.
If the join activity fails, the request is passed immediately to the error activity (retrylimit is 0), which sends a notification by e-mail through the Message port.
The workflow is delivered inactive (dxmActive is FALSE). Copy it into your own scenario, set the domain parameter to your domain root, and activate the copy.