Skip Navigation Links | |
Exit Print View | |
Oracle Identity Analytics 11gR1 Database Administrator's Guide |
3. Resource Types Metadata Module
This chapter describes the tables that make up the Rule Engine module.
|
|
Oracle Identity Analytics can create rules that, based on attributes, assign users and roles to different components in the warehouse. For example, Oracle Identity Analytics rules can assign users and roles to business units based on HR attributes. The RULES table stores information about the rules that are created in Oracle Identity Analytics. Each rule is identified by a unique RULE_ID. The RULE_CONDITION field saves the condition that is used to define the rule. The STATUS_ID and CURRENT_VERSION_ID columns save the status and the version of the rule respectively. The TYPE_ID column identifies whether the rule is a role membership rule or a user business structure rule. In addition, the VERSION_COUNT, CREATEUSER, UPDATEUSER, CREATEDATE, and UPDATEDATE fields are used for audit purposes.
PK_RULES - column RULE_ID
None
None
|
|
The RULE_OWNERS table defines the relationship between a rule and its owner (which can be either a Globaluser or a role in Oracle Identity Analytics). The RULE_ID field refers to the rule in the RULES table, whereas the OWNER_ID field refers to either the GLOBALUSERS table or the ROLES table. The OWNER_TYPE field is used to define if the owner is a global user or a role in Oracle Identity Analytics.
PK_RULE_OWNERS on column ID
None
None
|
|
The RULE_SETS table contains grouping of rules. Every rule_set is identified by a unique ID. The RULESETNAME and DESCRIPTION fields give additional information about the rule set.
PK_RULE_SETS - primary key on column ID
None
None
|
None
The RULE_SET_RULES table is a composite table that contains rule-sets-to-rule associations.
None
None
None
|
|
The RULE_TYPES table is used to define a rule category. Two rule types are available:
Role membership rule
User BusinessStructure rule
PK_RULE_TYPES on column ID
None
None
|
|
When a condition is added or removed from a rule in Oracle Identity Analytics, a rule approval process is initiated by the system. A snapshot of the existing rule is captured and saved into the RULE_VERSIONS table prior to initiation of the rule approval process. This facilitates in maintaining a rule's history, which can be accessed to compare previous versions.
PK_RULE_VERSIONS - primary key on column VERSION_ID
None
None
|
|
The ROLE_MEMBERSHIP_RULE table contains information about the rules generated to create associations between global users and roles. The RULE_XML field is a binary representation of the rule details.
None
None
None
|
None
The ROLE_MEMBERSHIP_RULE_DATA stores information about which role to assign for a role provisioning rule.
None
None
None
|
|
The ROLE_MEMBERSHIP_RULE_SCANS tables saves information regarding the user set to be processed.
PK_ROLE_MEMBERSHIP_RULE_SCANS - on column SCAN_ID
None
None
|
None
The RM_RULE_SCAN_RESULTS table stores information about the users to add or remove when a rule scan is processing users.
None
None
None
|
|
The USER_BU_RULE_SCANS table stores information about the user set to be processed, the rule to used during the scan, and the business unit that is associated with the user. In addition, it contains general information about the scan, such as a summary and the state of the scan.
PK_USER_BU_RULE_SCANS - on column ID
None
None
|
None
The USER_BU_RULE_SCAN_RESULTS table stores information about the results of completed scans as defined in the USER_BU_RULE_SCAN_RESULTS table. This table stores information about users that are assigned and unassigned to business units as a result of the scan.
PK_USER_BU_RULE_SCAN_RESULTS - on column ID
None
None
|
|
The USER_BU_RULE_EXTENDED_ATTS table stores additional information about the business-structure-to-user association rules.
PK_USER_BU_RULE_SCAN_RESULTS - on column ID
None
None
|
|
The USER_APPLICATION_SCANS table stores information about application scans, such as the scan's start date and end date, members found and removed, and summary information.
PK_AMES - on column ID
None
None
|
None
The USER_TRANSFERS table holds users for which there is a change in some predefined property. Information stored in this table includes the unique ID of the globaluser and the transfer date.
None
None
None