Process Internal Tickets

Sample workflow for processing tickets.

ProcessInternalTickets processes pending approval tickets that the Identity Store has generated internally — for example tickets raised by a privilege resolution or a policy-driven assignment. A ticket controller workflow watches for new tickets and delegates each one to the ticketServer, which evaluates the approval logic and takes the appropriate action (granting or revoking a privilege, sending a notification, or raising an error).

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

Process Internal Tickets

Prerequisites

Copy the workflow into your scenario and activate it in the Java-based Server.

Workflow and Activities

Activity Type Component description Description Ports

Activity	Type	Component description	Description	Ports
`error`	`error`	`provisioningActivity`	Error Activity	`Message`
`join`	`ticketServer`	`processTicketActivity`	Activity for processing tickets	-

error

provisioningActivity

Error Activity

Message

join

ticketServer

processTicketActivity

Activity for processing tickets

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 `Process Internal Tickets`
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
`consistencyrulesroot`	cn=domain_name,cn=Rules,cn=Policies,cn=domain_name
`domain`	cn=My-Company
`include`	ou, departmentNumber
`resourcefamily`	Event_Maintenance
`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 processTicketActivity uses the ticketServer component to evaluate and execute the approval logic for each incoming ticket. The retrylimit is 0, meaning tickets that fail are not retried; the error activity handles them by sending an e-mail notification through the Message port.

Operation

The Java-based Server raises a ticket-processing request whenever a new internal ticket is detected — for example when a privilege assignment requires approval.
The Java-based Server forwards the request to the processTicketActivity of this workflow.
The ticketServer component evaluates the approval logic for the ticket and takes the appropriate action.
Because retrylimit is 0, a failed ticket is immediately forwarded to the error activity for e-mail notification; no automatic retry occurs.
The workflow is delivered inactive (dxmActive is FALSE). Copy it into your own scenario and activate the copy.