An Overview of User Management Operations

8-2 Oracle Fusion Middleware Developers Guide for Oracle Identity Manager You can customize the consequences of user management operations such as create, update, delete, enable, disable, lock, unlock, and change password - also referred to as the post-processing functions of user management operations - by writing event handlers. in 11g Release 1 11.1.1, Oracle Identity Manager supports asynchronous execution of post-processing functions associated with user management operations. This significantly improves the perceived performance of user management operations. Post-processing functions associated with user management operations can be triggered programmatically on a given set of users. This capability becomes useful in situations where the users are managed directly on the data store, specifically in a reconciliation or bulk load scenario.

8.2 Extending User Management Operations with Event Handlers

The 11g Release 1 11.1.1 kernel exposes Service Provider Interfaces SPIs that are implemented to customize the functionality of user management operations. Currently, you can customize only pre-process, post-process, and validation stages of an operation for an entity. This section describes extending user management operations with event handlers in the following topics: ■ Understanding Elements in Event Handlers XML Files ■ Writing Custom Event Handlers

8.2.1 Understanding Elements in Event Handlers XML Files

Event Handlers XML files are comprised of elements and element attributes. This section describes some of the elements and element attributes within Event Handlers XML files. It also describes a mandatory namespace for the event handler XML definitions. Elements The top-level or parent element in Event Handlers XML files is eventhandlers. Table 8–1 lists and describes sub-elements that are typically defined within the eventhandlers parent element. Tip: See Writing Custom Event Handlers on page 8-4 for details about how to write event handlers. Note: Customizations of pre-process and validation functions are synchronous with the operation. However, customizations of the post-process functions are asynchronous. Table 8–1 Typical Sub-elements within the eventhandlers Element Sub-element Description validation-handler Identifies the validations that will be performed on the orchestration. action-handler Identifies the operations that will be performed at preprocess, postprocess, and action stages. Developing Event Handlers for Extending User Management Operations 8-3 Element Attributes The elements within Event Handlers XML files contain attributes. Table 8–2 lists and describes attributes that are typically defined within elements. failed-handler Identifies the event handlers that will be executed if an event handler fails. finalization-handler Identifies the event handlers to execute at the end of the orchestration. Finalization is the last stage of any orchestration. change-failed Identifies event handlers to be executed upon consequence orchestration failures. out-of-band-handler Defines event handlers for out-of-band orchestration flows such as veto and cancel. compensate-handler Identifies the event handlers that will be executed in the compensation flow of the orchestration. Table 8–2 Typical Attributes of Sub-elements within the eventhandlers Element Element Attribute Description Name The name of the event handler. class Full package name of the Java class that implements the event handler. entity-type Identifies the type of entity the event handler is executed on. A value of ANY sets the event handler to execute on any entity. operation Identifies the type of operation the event handler is executed on. A value of ANY sets the event handler to execute on any operation. order Identifies the order or sequence in which the event handler is executed. Supported values are FIRST, LAST, or a numeral. orch-target Identifies the type of orchestration, such as entity orchestration, Toplink orchestration, and so on. The following is a list of supported values: ■ oracle.iam.platform.kernel.vo.EntityOrchestration ■ oracle.iam.platform.kernel.vo.MDSOrchestration ■ oracle.iam.platform.kernel.vo.RelationOrchestration ■ oracle.iam.platform.kernel.vo.ToplinkOrchestration The default value is oracle.iam.platform.kernel.vo.EntityOrchestration . sync This attribute is operational in only the action-handler and change-failed elements. The sync attribute indicates whether the event handler is synchronous or asynchronous. Supported values are TRUE or FALSE . If set to TRUE synchronous, the kernel expects the event handler to return an EventResult. If set to FALSE asynchronous, you must return null as the event result and notify the kernel about the event result later. Note : The sync attribute must be set to TRUE for validation-handler elements. Table 8–1 Cont. Typical Sub-elements within the eventhandlers Element Sub-element Description