Request execution
When a request executes:
Authorizers and implementers are calculated.
Authorizers approve and implementers can fulfill requests.
Component logic can be executed to modify the request,calculate attributes, and more.
Operations are executed and request is completed.
The following outlines the processes involved in request execution and what responsibilities they carry.
Workflow Manager (idwfm)
Calculates authorizers / Implementers via:
Functional.im_policy_authorization component .
Policy rules utilized by this component to calculate authorizers are in the im_policy_authorization extdb table.
These policy rules can override authorization configurations set in the Bravura Identity UI.
Custom components can calculate authorizers / implementers. These components will implement plugin IDSYNCH_AUTH_CRITERIA_MOD_PLUGIN .
While custom standalone script can also calculate authorizers / implementers via plugin IDSYNCH_AUTH_CRITERIA_MOD_PLUGIN this was more common in older versions of Identity. Custom components should be used instead wherever possible.
Calculates request attributes and modifies requests via:
Attribute calculation via:
Policy rules in the hid_policy_attrval_calculation extdb table.
Request rewrite logic from custom components.
Request modification via:
Custom components that implement request rewrite logic via plugin WF_WIZARD_PLUGIN to dynamically detach or attach actions to a request.
Executes logic from enabled components.
Manages request status. To view request status:
Bravura Identity UI
As an end user, click Requests then click on the request of interest. In the right pane, click blue text with the batch name formatted yyyymmdd-n to see request details.
SQL tables can be viewed for a lower level view into request status
reqinfo for the request's attributes.
authreq for the request's authorizers / implementers.
reqacct for the request's operations.
reqbatch for the request's status .
Calls Transaction Monitor (
idtm
) to execute request operations.The order in which operations will execute can be enforced via Operation dependencies .
See more information about the Workflow Manager Service .
Transaction Manager (idtm
)
Executes request operations directed for a Target system (for example create account / modify group membership). It does this by:
Calling the appropriate agent for the target system.
Provides the agent with input values based on what was received from
idwfm
.Receives response from target system (success / failure).
Reports results back to
idwfm
.
The
pstee
utility can be used for debugging purposes to expose the agent inputs and target outputs as .kvg files in the logs directory.On success the Bravura Identity database is updated.
For example on successful target account creation, the account will also be added into the Bravura Identity database.
On failure Bravura Identity retrIes the operation as per the intervals defined in Maintenance -> Services -> Transaction Monitor Service . The operation fails after all retries are spent.
See more information about the Transaction Monitor Service.