Skip Headers
Oracle® Fusion Middleware Administrator's Guide for Oracle Directory Integration Platform
11g Release 1 (11.1.1)

Part Number E10031-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

14 Understanding the Oracle Provisioning Event Engine

This chapter discusses the Oracle provisioning event engine. It contains these topics:

14.1 What Are the Oracle Provisioning Events?

The Oracle provisioning event engine sends USER_ADD, USER_MODIFY and USER_DELETE events, depending on the operation performed on the user entries in Oracle Internet Directory. Because the user will be represented by multiple entries containing base user and application-specific user information, applications can subscribe to all of the attributes in the event.

The user events are also sent when a base entry or application entry is updated. However, no events are sent when an application entry is deleted because when an administrator requests the deprovisioning of a user from an application, a USER_MODIFY event is sent to the application with a provisioning status of DEPROVISIONING_REQUIRED. Once the application acknowledges the event by returning a value of SUCCESS, the application entry is deleted by the Oracle Directory Integration Platform.

To receive notification of provisioning status changes, an application must subscribe to the orclUserApplnProvStatus;Application_Name attribute. For example, to subscribe to the provisioning status change for an application named CORP_EMAIL, an application must subscribe to the orclUserApplnProvStatus; CORP-EMAIL attribute.

14.2 Working with the Oracle Provisioning Event Engine

The Oracle provisioning event engine generates events from add, modify, and delete operations that are performed on well-defined objects in Oracle Internet Directory. The Oracle provisioning event engine uses object definitions and event generation rules to generate events. This event generation model is extensible because it enables you to define custom objects and event generation rules. The Oracle provisioning event-engine, object definitions, and event generation rules are discussed in these topics:

14.2.1 Creating Custom Event Object Definitions

Table 14-1 lists the properties that you can use to identify objects for which events can be generated.

Table 14-1 Event Object Properties

Property Description

ObjectName

Assigns a unique name to identify the object

ObjectCriteria

Identifies the LDAP object class to use for identifying the object

MustAttributeCriteria

Provides any additional attributes that are required for identifying the object

OptionalAttributeCriteria

Provides any optional attributes that may be required for identifying the object

FilterAttributeCriteria

Lists the attributes that should not be sent during event propagation


Table 14-2 lists the predefined objects for which the Oracle provisioning event engine can generate events.

Table 14-2 Predefined Event Objects

Object Name Valid Object Class Values

Entry

*

User

orclUserV2, inetorgperson

Identity

orclUserV2, inetOrgPerson

Group

groupOfUniqueNames, orclGroup, orclPrivilegeGroup, groupOfNames

Subscription

orclServiceSubscriptionDetail

Subscriber

orclSubscriber


Note:

The metadata for event objects is stored in the following container: cn=Object Definitions, cn=Directory Integration Platform,cn=Products,cn=OracleContext

14.2.2 Defining Custom Event Generation Rules

You specify event generation rules in XML format. The DTD for event generation rules is as follows:

<?xml version='1.0' ?>
  <!DOCTYPE EventRuleSet [ 
    <!ELEMENT ChangeType (#PCDATA)> 
    <!ELEMENT Rule  (#PCDATA)> 
    <!ELEMENT EventName  (#PCDATA)> 
    <!ELEMENT ResEvent (Rule*, EventName)> 
    <!ELEMENT EventRule (ChangeType, ResEvent*)>
    <!ELEMENT EventRuleSet (EventRule*) >
  ]>

The element definitions in the preceding DTD are as follows:

  • The EventRuleSet root element identifies a set of event rules for an individual event object

  • The EventRuleSet root element contains a list of EventRule elements

  • Each EventRule element depends on the value assigned to the ChangeType element.

  • The ChangeType and Rule elements determine the event name to be propagated to an application

Table 14-3 lists the event definitions that are supported by the Oracle provisioning event engine.

Table 14-3 Supported Event Definitions

Object Name Change Type Rule Event Name

USER

Add

OrclApplnUserProvStatus=PENDING_UPGRADE

USER_ADD

 

Add

OrclApplnUserProvStatus=PROVISIONING_REQUIRED

USER_ADD

       
 

Modify

OrclApplnUserProvStatus= PENDING_UPGRADE

USER_ADD

   

OrclApplnUserProvStatus=PROVISIONING_REQUIRED

USER_ADD

   

OrclApplnUserProvStatus=PROVISIONING_FAILURE

USER_ADD

   

OrclApplnUserProvStatus=DEPROVISIONING_REQUIRED

USER_MODIFY

   

OrclApplnUserProvStatus=PROVISIONING_IN_PROGRESS

USER_MODIFY

   

OrclApplnUserProvStatus=PROVISIONING_SUCCESSFUL

USER_MODIFY

       
 

Delete

OrclApplnUserProvStatus=PROVISIONING_IN_PROGRESS

USER_DELETE

   

OrclApplnUserProvStatus=PROVISIONING_SUCCESSFUL

USER_DELETE

   

OrclApplnUserProvStatus=DEPROVISIONING_REQUIRED

 
       

GROUP

Add

 

GROUP_ADD

 

Modify

 

GROUP_MODIFY

 

Delete

 

GROUP_DELETE

       

IDENTITY

Add

 

IDENTITY_ADD

 

Modify

 

IDENTITY_MODIFY

 

Delete

 

IDENTITY_DELETE

       

ENTRY

Add

 

ENTRY_ADD

 

Modify

 

ENTRY_MODIFY

 

Delete

 

ENTRY_DELETE

       

SUBSCRIPTION

Add

 

SUBSCRIPTION_ADD

 

Modify

 

SUBSCRIPTION_MODIFY

 

Delete

 

SUBSCRIPTION_DELETE

       

SUBSCRIBER

Add

 

SUBSCRIBER_ADD

 

Modify

 

SUBSCRIBER_MODIFY

 

Delete

 

SUBSCRIBER_DELETE


Note:

The metadata for supported event objects is stored in the following container: cn=Event Definitions, cn=Directory Integration Platform,cn=Products,cn=OracleContext.