Oim 10g Tables Descriptive Essay

You use this tab to set high-level information for the task that you want to modify. For this example, the Create User task is used to create a user in the Solaris environment.

12.3.3.1.1 Modifying a Process Task's General Information

To modify the general information for a process task:

  1. Double-click the row heading of the task you want to modify.

    The Editing Task dialog box is displayed.

  2. Click the General tab.

  3. In the Description field, enter explanatory information about the process task.

  4. Optional. In the Duration area, enter the expected completion time of the process task (in days, hours, and minutes).

  5. If you want a condition to be met for the process task to be added to the Process Instance, select the Conditional check box. Otherwise, go to Step 6.

    Note:

    If you select the Conditional check box, you must specify the condition to be met for the task to be added to the process.

  6. When you want the completion status of the process to depend on the completion status of the process task, select the Required for Completion check box.

    By doing so, the process cannot be completed if the process task does not have a status of Completed.

    If you do not want the status of the process task to affect the completion status of the process, go to Step 7.

  7. To prevent a user from manually adding the process task into a currently running instance of the process, select the Disable Manual Insert check box. Otherwise, go to Step 8.

  8. To enable a user to cancel the process task if its status is Pending, select the Allow Cancellation while Pending check box. Otherwise, go to Step 9.

  9. To allow this task to be inserted multiple times in a single process instance, select the Allow Multiple Instances check box. Otherwise, go to Step 10.

  10. Click the Task Effect box.

    From the custom menu that is displayed, select one of the following:

    • Enable Process or Access to Application. If a resource is reactivated by using the enable function, all tasks with this effect are inserted into the process. If you select this option, you must also select the Allow Multiple Instances check box.

    • Disable Process or Access to Application. If a resource is deactivated by using the disable function, all tasks with this effect are inserted into the process. If you select this option, you must also select the Allow Multiple Instances check box.

    • No Effect. This is the default process action associated with all tasks. If this option is selected, the task is only inserted during normal provisioning unless it is conditional.

  11. Optional. If the process task is Rejected, you might want Oracle Identity Manager to insert a new instance of this process task (with a status of Pending).

    For this to occur, enter a value in the Retry Period in Minutes field. This designates the time in minutes that Oracle Identity Manager waits before adding this process task instance.

    In the Retry Count field, enter the number of times Oracle Identity Manager will retry a rejected task. For example, suppose 3 is displayed in the Retry Count field. If the task is rejected, Oracle Identity Manager adds a new instance of this task, and assigns it a status of Pending. After this process task is rejected for the fourth time, Oracle Identity Manager no longer inserts a new instance of the process task.

    Note:

    If either Retry Period or Retry Count is selected, you must specify parameters for the other option because they are both related.

  12. From the Child Table box, select the child table of the custom form where Oracle Identity Manager will perform an action.

    From the Trigger Type box, specify the action that Oracle Identity Manager will perform in the child table. These actions include the following:

    • Insert: Adds a new value to the designated column of the child table

    • Update: Modifies an existing value from the corresponding column of the child table

    • Delete: Removes a value from the designated column of the child table

    Note:

    If the custom process form does not have any child tables associated with it, the Child Table box will be empty. In addition, the Trigger Type box will be grayed out.

  13. Click Save.

    The modifications to the process task's top-level information reflects the changes you made in the General tab.

12.3.3.1.2 Triggering Process Tasks for Events Defined in Lookup.USR_PROCESS_TRIGGERS Fields

When a user attribute is defined in Lookup.USR_PROCESS_TRIGGERS, for each modification of the attribute, the corresponding process task is triggered for each provisioned resource. This is same for the First Name, Last Name, Display Name (USR_DISPLAY_NAME) user attributes and custom user attributes. However, for the Lookup.USR_PROCESS_TRIGGERS fields USR_STATUS, USR_LOCKED, USR_LOCKED_ON, and USR_MANUALLY_LOCKED, the attached process task is not triggered.

The following sections describe how to trigger the process tasks for the Lookup.USR_PROCESS_TRIGGERS fields:

For the USR_STATUS Attribute

It is not possible to run a task via Lookup.USR_PROCESS_TRIGGERS for the USR_STATUS attribute because this attribute is processed separatelly by Oracle Identity Manager. This attribute is changed by enabling, disabling, or deleting a user. These operations have a special effect on the provisioned resources because the coresponding process tasks are started via the Task Effect setting, as described in Table 12-3, "Fields of the General Tab of the Editing Task Dialog Box". For these three operations, the Lookup.USR_PROCESS_TRIGGERS is not used. Therefore, when the status changes, perform the following to run the process task:

For transition from Disabled to Enabled status:

  1. In the Process Definition form, create a process task named .

  2. Open the Editing Task window, and click the General tab.

  3. From the Task Effect list, select Enables Process or Access to Application.

  4. Select Conditional and specify the condition to be met for the task to be added to the process.

For trnsition from Enabled to Disabled status:

  1. In the Process Definition form, create a process task named .

  2. Open the Editing Task window, and click the General tab.

  3. From the Task Effect list, select Enables Process or Access to Application.

  4. Select Conditional and specify the condition to be met for the task to be added to the process.

For transition from Enabled/Disabled/Provisioned to Revoked status:

  1. In the Process Definition form, create a process task named .

  2. Then set this task as an Undo task for the Create User task, which is the task that creates the user and is typicaly unconditional.

  3. Select Conditional and specify the condition to be met for the task to be added to the process.

    Note:

    when the OIM user is deleted, for each completed task in each resource, Oracle Identity Manager tries to run the Undo tasks.

For the USR_LOCKED, USR_LOCKED_ON, USR_MANUALLY_LOCKED Attributes

The lock and unlock operations, are handled in Oracle Identity Manager as separate orchestrations. The orchestration is on:

Or:

The event handler that does the evaluation for Lookup.USR_PROCESS_TRIGGERS is:

This is triggered only in the following user orchestrations:

  • MODIFY: For generic fields

  • CHANGE_PASSWORD, RESET_PASSWORD: For USR_PASSWORD propagation

  • ENABLE, DISABLE, DELETE: For handling the execution of process tasks

For lock/unlock operations, the TriggerUserProcesses event handler is not triggered. Therefore, for the attributes modified through lock/unlock operations, the Lookup.USR_PROCESS_TRIGGERS is not checked.

If you want to run custom code for these operations when these fields are changed, then you can create event handlers and register them on the orchestrations mentioned in this section.

If you had done any customization to the unprotected metadata files pre-upgrade, the customization will be lost after you upgrade to Oracle Identity Manager 11.1.2.3.0.

Customization done to the following protected metadata files are retained after upgrade:

  • One thought on “Oim 10g Tables Descriptive Essay

    Leave a Reply

    Your email address will not be published. Required fields are marked *