| Oracle® Identity Manager Tools Reference Guide Release 9.0.3 Part Number B32457-01 |
|
|
View PDF |
| Oracle® Identity Manager Tools Reference Guide Release 9.0.3 Part Number B32457-01 |
|
|
View PDF |
This chapter describes the rule generators. It contains the following topics:
To perform field validations and enter default values into forms, which either come packaged with Oracle Identity Manager or are created by Oracle Identity Manager users, certain business rules must be applied. As an example, for the Users form, you may want Oracle Identity Manager to generate the User ID automatically by concatenating the user's first name and last name.
To do this, you must create a specific type of adapter, which is designed to modify a form's field value. You can do this by using the Adapter Factory form. Then, when you attach this adapter to the form, Oracle Identity Manager will automatically update the field value for all records of that form, and save this information to the Oracle Identity Manager database.
This type of adapter, which can generate, modify, or verify the value of a form's field automatically, is called a rule generator. Oracle Identity Manager triggers a rule generator on preinsert and preupdate.
If you create a rule generator, and it contains adapter variables, then you must map these adapter variables to their proper locations. Otherwise, the adapter will not be functional.
Also, you can attach this adapter to a provisioning process for the adapter to work. Then, once the process is provisioned to a target user or organization, Oracle Identity Manager will trigger the associated rule generator.
On occasion, a rule generator, which has been assigned to a provisioning process, may no longer be needed for the process to be completed. If this happens, then you need to remove the rule generator from the provisioning process. Similarly, after you attach one rule generator to a form field, you may need to connect a different rule generator to that form field. When this occurs, you must first remove the rule generator that is currently attached to the form field.
The following sections will show you how to:
Map the adapter variables of a rule generator.
Associate rule generators with provisioning processes.
Remove a rule generator from a form field.
In the Example 3-0, "Creating Adapters", you learned how to create a rule generator. Now, you must map the adapter variables of the rule generator to their proper locations. This will ensure that adapter will work.
To map these adapter variables, access the Data Object Manager form (from the Development Tools/Business Rule Definition folder).
This procedure will show you how to map the adapter variables for a rule generator.
Open the Data Object Manager form. Within the Design Console Workspace, the Data Object Manager form is displayed.
The following table lists and describes the various regions of the Data Object Manager form:
| Name | Description |
|---|---|
| Form Description Field | From this Lookup field, select the form that contains the field to which you are attaching the rule generator. |
| Data Object Field | This field displays the name of the data object, which is represented by the selected form. |
| Attach Handlers Tab | This tab displays:
The rule generators that are attached to the selected form. The execution schedule of the rule generators associated with this form. The order in which Oracle Identity Manager will run the rule generators. Insert, update, and delete permissions for user groups. |
| Map Adapters Tab | This tab displays:
The names of the rule generators that are associated with the form; The status of these adapters. The names, descriptions, and mapping statuses of the rule generators' adapter variables. Note: The Map Adapters tab is disabled until an adapter is assigned to the current data object. For more information about assigning an adapter to a data object, refer to Oracle Identity Manager Administrative and User Console Guide. |
Double-click the Form Description field. A Lookup dialog box is displayed, displaying the forms to which you can attach rule generators.
Select the form you want (for example, Solaris). Then, click OK.
From the toolbar, click Save.
The selected form, the form's data object, and the rule generator adapters associated with the form appear. In addition, Oracle Identity Manager enables the Map Adapters tab.
For this example, the Solaris form has been selected. Its data object (Thor.CarrierBase.tcUD_SOLARIS) appears, along with the four rule generator adapters associated with it (adpCONVERTTOLOWERCASE, adpSOLARISHMDSTRINGGEN, adpSETSOLARISASSET, and adpSETPASSWORDFROMMAIN). Oracle Identity Manager will trigger these four rule generators on preinsert.
Based on the sequence numbers of these adapters, Oracle Identity Manager will trigger the adpCONVERTTOLOWERCASE adapter first, followed by the adpSOLARISHMDSTRINGGEN, adpSETSOLARISASSET, and adpSETPASSWORDFROMMAIN adapters, respectively.
Tip:
To change the order sequence of a rule generator:Click Assign. The Event Handlers dialog box is displayed.
Select the rule generator from.
Click the up arrow and down arrow buttons to modify the order of the rule generator.
For these rule generators to work properly, you must map the adapter variables to their proper locations.
Click the Map Adapters tab.
From the Name combo box, select the rule generator, which has adapter variables that need to be mapped (for example, the adpCONVERTTOLOWERCASE rule generator).
The Map Adapters tab now displays the following:
The name of the rule generator that is to be attached to the form.
The status of the rule generator.
The names, descriptions, and mapping statuses of the rule generator's adapter variables.
Note:
To learn more about the various mapping statuses for an adapter, refer to the "Attaching Process Task Adapters to Process Tasks".Set the mappings for each variable that appears in the Adapter Variables region of the Map Adapters tab. To do so:
Double-click the row header of the variable you want to map (for example, Data). The Data Mapping for Variable dialog box is displayed.
The following table describes the various fields of the Data Mapping for Variable dialog box:
| Field Name | Description |
|---|---|
| Variable Name | This field displays the name of the adapter variable for which you are setting a mapping (for example, Data). |
| Data Type | This field shows the data type of the adapter variable (for example, String is the data type for the Data adapter variable). |
| Map To | This field contains the source and target locations of the mappings you can set for the adapter variable (for example, User Definition).
When you map the adapter variable to a location or a contact, Oracle Identity Manager enables the adjacent combo box. From this combo box, select the specific type of location or contact to which you are mapping the adapter variable. If you are not mapping the adapter variable to a location or contact, this combo box is disabled. |
| Qualifier | This field contains the qualifiers for the mapping you selected in the Map To combo box (for example, User Login). |
| IT Asset Type | This field enables you to select a specific IT Resource (for example, Solaris) when you map an adapter variable to an IT Resource, and this variable's data type is String.
If you are not mapping the adapter variable to an IT Resource, or the variable's data type is not String, this field does not appear. |
| IT Asset Property | This field enables you to select a specific field that will receive the results of the mapping (for example, User Name), when you map an adapter variable to an IT Resource, and this variable's data type is String.
If you are not mapping the adapter variable to an IT Resource, or the variable's data type is not String, this field does not appear. Important: The IT Asset Type and IT Asset Property fields are included within this window for backward compatibility. The preferred way is to create an adapter variable with a data type of IT Resource, in which case these fields will not appear. |
| Literal Value | When you map the adapter variable to a literal, type the name of the specific literal in this text box (for example, IBM).
If you are not mapping the adapter variable to a literal, this field does not appear. |
Complete the Map To, Qualifier, IT Asset Type, IT Asset Property, and Literal Value fields.
Note:
For more information on which mappings to select, refer to the "Adapter Variable Mapping Information".Click Save. Then, click Close
The Data Mapping for Variable window disappears. The Map Adapters tab is active again.
From the main screen's toolbar, click Save.
Repeat Steps 6 and 7 for all adapter variables that need to be mapped.
The contents in the Status field change from Mapping Incomplete to Ready. In addition, the mapping statuses for the adapter's variables change from No (N) to Yes (Y).
This signifies that all the adapter variables for the rule generator adapter have been mapped correctly. You are now ready to attach this rule generator to a provisioning process, so it can be triggered, once the process is provisioned to a target user or organization.
Tip:
Once you map all the adapter variables for a rule generator that is associated with a form, a quick way to see the form to which it is attached, as well as the execution schedule of the rule generator, is by accessing the Usage Lookup tab of the Adapter Factory form.Once the rule generator is assigned to a process, and the process is provisioned, the rule generator will be executed by Oracle Identity Manager.
Once you map the adapter variables of a rule generator to their proper locations, you must attach it to a provisioning process. Then, once the process is provisioned to a target user or organization, Oracle Identity Manager will trigger the associated rule generator.
Similarly, when a rule generator, which has been assigned to a provisioning process, is no longer needed for the process to be completed, you must remove the rule generator from the provisioning process.
To assign a rule generator to a provisioning process or remove a rule generator from a provisioning process, access the Event Handlers/Adapters tab of the Process Definition form. This form can be found in the Process Management folder.
Sometimes, after you attach one rule generator to a form field, you may need to connect a different rule generator to that form field. When this occurs, you must first remove the rule generator that is currently attached to the form field.
This procedure will show you how to remove a rule generator from a form field.
Caution:
If you remove a rule generator from a form, and if the class name of the form's data object matches the table name of a provisioning process, then you will not be able to assign the rule generator to that provisioning process.For example, suppose the adpCONVERTTOLOWERCASE rule generator is removed from the Solaris form. If the class name of the form's associated data object is UD_SOLARIS, then the rule generator cannot be assigned to any provisioning process with a table name of UD_SOLARIS.
To remove a rule generator from a form field, perform the following steps:
Open the Data Object Manager form.
Select the form that contains a rule generator you want to remove.
The selected form, along with its rule generators, appear in the Data Object Manager form.
Click the rule generator that you want to remove from the form field.
Click Delete.
The selected rule generator no longer appears in the Data Object Manager form. This indicates that you have removed the rule generator from the form field.
Caution:
If you attempt to remove a rule generator from a form field, and if an error box appears, then the adapter has already been associated with a provisioning process. First, detach the rule generator from the process. Then, you can remove it from the form field.
